Nexis 6P stuck on Google boot screen
-
@sagrotan So does it work now?
-
Yes, it works!!! I have just inserted the SIM Card and can make phonecalls ;O) Network also works.
The only thing is a high energy consumption, but I think I can live with that.
Yip yip hurray - this was my first experience flashing a ROM ;O)best regards
sagrotan -
@sagrotan high power consumption is also normal. Hopefully, Florian, or someone else, will figure out what triggers the performance cores to sleep.
Or, just wait until the majority of N6Ps turn into 4-core devices....
-
@rocket2nfinity Or we decide as a community to limit to 4 cores for all users
-
@Flohack No!.... Let me burn it until it's dead!
.... or at least until it gets twitchy enough.Seriously, I do think most will likely need to go to 4 cores at some point. This thing gets hot under load running all 8. It wasn't designed to have all 8 running all the time. But as long as I still have 8, might as well use them.
-
The counter argument would of course be that it would be simpler to keep everyone on four cores, and could prevent a fire or two. This thing runs quite hot using Libertine or anything processor intensive. And most "dead" N6Ps can be revived on 4 core. So, 4 core keeps everyone running.
So, considering whether to go four core only is something the community should discuss.
-
Yeah that was my thinking. From my first N6P, the only I killed during repair, I know that most workflows are ok with 4 cores as well.
We anyways do not have the CPU-intense games or other apps that would benefit from 8 cores working at the same time. Sadly also the CPU governor that allows proper schedulding of 4 little and 4 big cores was lost somewhere in the kernel tree and is not possible to be activated anymore (support was discontinued already when Google still pushed for that feature).
So current governor sees 8 equal cores, and just assigned them randomly. That means big cores are already being used when little ones would be enough.
-
I have tried everything I have found from about 6 posts on this website to install Ubuntu Touch onto my Nexus 6p. I am using ubports-installer_0.8.1-beta_win, android 7.1.2 (N2G47H, Apr 2017) with twrp-3.4.0-0-angler installed. I have formatted the data and cache via TWRP. I keep getting stuck at the Ubports Recovery screen where it shows me Reboot system now, Ubuntu actions and Android actions. It will never go past this screen. I try and reinstall via the ubports installer without bootstrap and still nothing. Do I need to format more than just the data and cache partitions? Any help? Thanks!
-
@konvikted Wipe everything in TWRP first before installing android, then just cache and data after enabling USB debugging in android. Then flash UT via installer or manually. The windows installer was buggy, so if it hasn't been fixed, manually might be best. See the Nexus 6P testers thread.
-
@konvikted Wipe everything except vendor. If the device was encrypted before, format data instead of wipe. system partition is also used. But we need to have the vendor partition from Google
-
Thank you so much for the help on this thread. The moral of the story, pay attention to what the pre-requisites say! You really do need to revert to the stock 7.1.2 version of Android for UBports to work properly. Once I reverted to that version, the installer still showed errors, but I just ignored them and pressed the "Try again" and it worked (filing bug report as I type). Now I am excited to see all of the features of the OS!
Thanks again!
-
Thank you @rocket2nfinity & @Flohack! So I went back to a clean 7.1.2 install with TWRP and all other steps. I formatted everything mentioned and still nothing. I reinstalled everything and then formatted and wiped and it worked... Don't see why this would make a difference logically but I got it to install lol. Any reasons why the Nexus 6p drains battery so fast even when unused?
-
@konvikted All 8-cores are running all the time. And it's possible your battery may be nearing end of life.
-
@rocket2nfinity thanks! Brand new battery though, just replaced it a few weeks ago. The 8 cores I saw earlier in a post. All 8 running even when the phone is not being used?
-
@konvikted As long as it's powered on yes. We've talked about defaulting all devices to 4-core because it runs as long as it used to on just 4-cores. But that would deprive those who have it, the advantages of being on 8. So, we sit at an impass until something tips the scale, such as the majority burning out their performance cores.
Power managment has not been succesful so it runs on full 8 as it pleases. The only way to fix that is to go to 4-core only.
-
@rocket2nfinity Great explanation, thanks! Makes sense. Guess it depends on what people are doing on their phone. For me I just want a non Google/Apple phone to text/call with!
-
@konvikted well if you turn it off with the power button, the cores are suspended as much as possible, but they will wake up for wifi events and certain modem events. Also push client wakes up from time to time to check notifications.
However, I also notice that sometimes push messages only appear when I turn on the phone. That would indicate a sleep that is too good
-
@flohack Yes I have noticed that messages only will appear when I wake the phone. I mean the power usage isn't horrible, the phone will last about 20 hours without use... not bad considering it's simply a backup non Google/Apple phone. Great port though
