Call for testing: Google/Huawei Nexus 6P (angler) owners
-
Hi all, I have received another nexus 6p to try and followed all the steps, but this time in Ubuntu 20.04.1. Worked straight off, so thank you for all your help. I have noticed the installer has updated to 0.5.5-beta. (I am using the Stable release). Thanks again and keep up the good work.
-
@Flohack I have noticed something for a while now. I have a flipcase to my phone. While I'm not able to wake the phone when open the flipcase, it turns on the screen if there is something happpening, like an alarm or an incoming call. I haven't seen any response on this so I just wanted to share my experience.
-
@Rondarius Hmm thats interesting, is it a magnetic flipcase?
BR -
@Flohack It's with a magnetic slab thats folds over the front. It's the slab that is magnetic and not the lid.
-
@Flohack I've completed the endurance test. Not sure how to post an image, but uptime is at 7 days.
-
@DjDeets Very cool. Unfortunately not for me, my device had a few freezes over the last weeks, and, naturally, as developer, I have to reboot it more often
-
Tried all four versions with the installer with no luck. If the phone was running 8.0 something is that a no go. Did the steps reccomended in pop up during install. Getting Your device cant be checked for corruption message and then stuck on Google screen.
-
@lburners can you connect a USB cable and see if you can either telnet on 192.168.2.15 or ssh on phablet@10.15.19.82 after lets say 2 minutes? Maybe the basic kernel has booted...
-
@Flohack I realize this might not be the most useful "successful test" but I left my device plugged in and forgot about it behind a couch, and the uptime is >16 days.
If you'd like me to test anything on a device that's been on that long I'd be happy to give it a shot. One thing worth noting is that whenever I do check it, it seems to be disconnected from WiFi and needs me to re-enter the password
-
@gerg hey cool ^^
Well yes WiFi has disconnection problems when the device goes to deep sleep. A kernel error from dmesg would be helpful in this case. However, it should not be needed to enter the password again, simply clicking on the stored connection works for me.
-
This post is deleted! -
just got a nexus 6p from my brother. just reformatted and now i guess ill be following flohacks steps from october 2nd.
-
This post is deleted! -
AWEsome
I just installed the rom you recommended oem 7.1.2. Then used the ubports installer 6.0 and its working on my 6P. thank ya very much -
I gotta say the experience on this is so much better than the nexus 5. One thing I noticed on mine is the camera especially the selfie looks like fish eyed. Not sure if thats software or this camera.
-
Dear All,
just a heads-up we are working now on getting the fingerprint reader done. I can already scan fingerprints, unfortunately I cannot activate the locking right now
-
@Flohack any advice for BLOD issues? I used your steps outlined in this thread (OCT 2). When attempting to flash using the installer tool, it flashes the firmware successfully then just BLOD's until I get back into the bootloader.
I even tried cheating by intercepting the BLOD, flashing TWRP again, then going into recovery.
The installer immediately sees the FS, then tries pushing the files only to fail because it's unmounted.
Any ideas?
-
@kz6fittycent humm no but can you describe exactly whats the sequence of events on the phone? So, if you begin in e.g. TWRP recovery:
- device detected
- channel selected, bootstrap checked yes (No will assume a working recovery available)
- Reboot to bootloader (it will flash new recovery)
- Reboot to recovery (You will see tiny yellow text)
- Download of partitions
- Reboot to recovery again (This time Yumi appears with blinking eyes, flashing partitions)
- reboot to live system
Thats basically how it should be. Where did you stop?
-
@Flohack said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
@kz6fittycent humm no but can you describe exactly whats the sequence of events on the phone? So, if you begin in e.g. TWRP recovery:
- device detected - YES
- channel selected, bootstrap checked yes (No will assume a working recovery available) - TRIED BOTH WAYS - see below
- Reboot to bootloader (it will flash new recovery) - see below
- Reboot to recovery (You will see tiny yellow text) - yes
- Download of partitions - yes?
- Reboot to recovery again (This time Yumi appears with blinking eyes, flashing partitions) - never happens
- reboot to live system - nope
Thats basically how it should be. Where did you stop?
- Flashed 7.1.2
- Flashed
twrp-3.2.1-0-fbe-4core-angler.img adb sideloadneeded kernel mod to prevent immediate BLOD - regardless of ROM/OS- wipe partitions in TWRP
- Start up ubports-installer (snap) - tried older version you listed and latest from
stablebranch of the snap - same results either way - bootstrap selected
- flashes bootstrap - then just BLOD's
Alternative steps taken:
- Everything's the same up until the next bullet point
- deselected bootstrap
- ignore errors
- everything is "successful" until about 75%-80% of when it's pushing system files to device when it fails. Logs show no errors. Literally nothing. Just a sudden "stop".
- tried 2 different cables and same result <- that's all that I have...
I can flash Android ROM's with the same cable and same TWRP.
What is ubports-installer actually pushing to the device when it's flashing a "new recovery"?
I believe this is the problem for me and possible others that might experience this.
- does this recovery allow for the 4-core mod or does it assume 8-cores?
Perhaps there's a workaround? I'd really like to see this working on my device.
-
Here's a truncated version of the logs I'm seeing:
"/home/james/snap/ubports-installer/320/.cache/ubports/system-image/ubuntu_command\",\"/cache/recovery/\"],\"code\":1}"} {"level":"warn","message":"lost connection to device"}
