Nexus 6p Flashing Issue
-
@sjackson The envelope is empty, its not a pending notification
- it will turn green if you got anything. Send yourself an SMS to test...As for LED: It is
- white solid for charing
- green solid for 100% charged
- green blinking for a notification pending
- orange blinking for critical battery level
-
Oh, ok cool. Thanks for taking the time to explain.
I figured out the led when I unplugged it lol. It's acutally been a while since I have had a phone with a notification/charging led. I bought this device specifically because it's got support for ubuntu touch, it wasn't my old phone.So far I am really liking the overall feel of this OS. Also, youtube playback is pretty good on this device considering it's age.
I am trying to get pip3 going, and I seem to be having a problem with apt. If I run sudo apt-get update. I have been getting a message since last night that there is a temporary failure resolving the repos. at ports.ubuntu.com as well as repo.ubports.com. Not being able to resolve both leads me to believe it is a problem on my end.
Running sudo apt-get full-upgrade ends with unable to backup 70-android.rules and dpkg error code (1).
Have you come across anything like this? If so, do you know how to fix it?
This OS is very slick, and I also have a pinephone coming.
I realize we aren't exactly ready to banish google and apple yet, but this is coming along very nicely. If I can get opencv running on these cameras, and the i2c/serial busses working on the pinephone (eventually). I will be really happy.
Thanks in advance!
-
@sjackson Rootfs is read only by design. Apt update will not work. Use system update to update the system and apps
-
Thanks. I found the documentation on how to change this.
I however ran into an issue with ADB.
With developer mode enabled, and the phone on. ADB finds no devices.In bootloader, ADB finds no devices.
In the ubports recovery ADB finds the device, however it is unauthorized.
and adb shell gives me this message.
- daemon not running; starting now at tcp:5037
- daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Does this indicate that I did something wrong in the installation?
The install script that came with the factory 7.1.2. android image didn't work due to changes in fastboot, so I flashed the images manually.
Also, something strange I noticed. This is a 32 gig device, it is reporting in the OS and the bootloader as 64.
Sorry for the bother, and thanks for the help!
-
@sjackson Might I ask what you are trying to do?
Changes made via apt will get over-written on the next update. ADB to external devices is not functional. SSH is the way to access the device from a computer. I can't say about recovery mode. Never tried adb there.
adb via ssh, or terminal, errors out because it is looking at the anbox kernel. But, you don't have the rest of anbox installed. If you follow the anbox instructions without installing the kernel, you will get it running - sort of. The base anbox works, but apps appear as a black screen because the patched driver is in kernel 5.8 and hasn't been backported. Otherwise software rendering must be applied. That runs very slow though.
-
The why would be so I can use this device as a linux sbc with a screen, cameras, etc built in. Build applications that have arm64 support. I would really like to have the ability to use it as a powerful remote sensor. Python3 is already installed although it very old, but there is no python IDE in the store that I can see. PIP, wheel, and whatever is included in the python setuptools are not installed.
-
@sjackson
Those are not installed because Ubuntu Touch is designed to be an os for phones.
It's fine to do it like this but out of curiosity why not use a Rasberry Pi 4 ? -
@SJackson There's a buid of Mobian I think I saw someone working on using halium/hybris. But haven't seen anything about it in a while. There's also Postmarket, but no build for N6P. Those might be better choices for your application.
-
This post is deleted! -
I got the Universal installer to work.Had to flash the userdata.img file. I figured since I was coming from a custom ROM i might have too because i had to do it before when flashing to a Pixel Rom. I grabbed that image from the first availible stock ROM 6.0. If you get stuck flashing back to stock with the boot.img, see this thread. https://www.reddit.com/r/essential/comments/ihhedy/psa_solution_fastboot_error_couldnt_parse/
Hope this helps someone.
