Related
Hello,
After getting my OTA update from ICS to JB, i had contrat problems (i couldnt see anything on my screen when i was outside with some sun, even with max luminosity).
So i decided to try CM roms. I picked the last "stable" wich is CM 9 Crespo 9.1.0. Everything went well, but i noticed my phone did freeze every 2 days, and i must remove the battery to restart it. I flashed it with Odin and did another clean install of Crespo 9.1.0 but i had the same issue. So i did dowgrade it to Crespo 9.0.0, and I still have the same problem.
Do you have any ideas what could be the problem ?
I doubt that might be a hardware problem as this problem never showed up before I installed CM, or that would be a damned coincidence...
Well i noticed that the combination of buttons vol up+vol down+power did freeze the phone also
Sounds like an issue with bug mailer. There may be other issues as well, though. Have you changed the cpu clock speeds or governors?
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Sounds like an issue with bug mailer. There may be other issues as well, though. Have you changed the cpu clock speeds or governors?
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Well no i didnt change anything about CPU. But trying to generate the bug i finally had a message just before freeze, saying "SuperUser rights have been refused to shell". I think this is part of the problem.
Problem seems to be solved thx to this post http://forum.xda-developers.com/archive/index.php/t-1610294.html
Just gave abd root access, and this buttons combination no more crashes the phone ...
I'm new to the whole Android thing but I used to install lots of roms on my trusty old Windows Mobile devices over the years. I remember then that trying out different roms sometimes meant things would stop working.
Here's my problem. I have a Nexus 7 and it works fine on stock unrooted 4.1.2. I think. I've used the Nexus Root Toolkit to (very easily) unlock and root it. When rooted on stock rom (4.1.1 or 4.1.2), it takes a couple of seconds to turn on from sleep, sometimes needs to reboot, sometimes the gyroscope/acceslerometer locks and doesn't work as it should...
Is a rooted Nexus 7 less stable/reliable than an unrooted one?
littld said:
I'm new to the whole Android thing but I used to install lots of roms on my trusty old Windows Mobile devices over the years. I remember then that trying out different roms sometimes meant things would stop working.
Here's my problem. I have a Nexus 7 and it works fine on stock unrooted 4.1.2. I think. I've used the Nexus Root Toolkit to (very easily) unlock and root it. When rooted on stock rom (4.1.1 or 4.1.2), it takes a couple of seconds to turn on from sleep, sometimes needs to reboot, sometimes the gyroscope/acceslerometer locks and doesn't work as it should...
Is a rooted Nexus 7 less stable/reliable than an unrooted one?
Click to expand...
Click to collapse
Rooting doesn't make a difference on stability (or shouldn't)
All rooting does is give you admin rights to parts of the phone not accesible without rooted. Basically...
Customer ROM's for the Nexus at the moment (and sorry about this devs but its true) are not yet up to par with the Stock ROM.
Its stable pretty fast and not bad with battery.
Hope this helps.
Right so after lots of erratic behaviour with rooted stock 4.1.2, I unrooted and relocked the boot loader. It was better already but I've also run the Forever Gone thing and it's now working perfectly.
I would like to root again but not at the expense of stability. I had previously use the Toolkit if it makes any difference.
littld said:
Right so after lots of erratic behaviour with rooted stock 4.1.2, I unrooted and relocked the boot loader. It was better already but I've also run the Forever Gone thing and it's now working perfectly.
I would like to root again but not at the expense of stability. I had previously use the Toolkit if it makes any difference.
Click to expand...
Click to collapse
Rooting and/or unlocking the bootloader will have no direct effect on stability. What you do with your device after rooting is entirely a different issue.
Wilks3y said:
Rooting doesn't make a difference on stability (or shouldn't)
All rooting does is give you admin rights to parts of the phone not accesible without rooted. Basically...
Customer ROM's for the Nexus at the moment (and sorry about this devs but its true) are not yet up to par with the Stock ROM.
Its stable pretty fast and not bad with battery.
Hope this helps.
Click to expand...
Click to collapse
This would be true if it weren't a Nexus device. We can more or less compile the same ROM that Google shipped. CyanogenMod 10 in my experience has been rock solid stable, though obviously there are still some bugs, I have encountered none. I also used EOS for a little, and that was equally great.
littld said:
Is a rooted Nexus 7 less stable/reliable than an unrooted one?
Click to expand...
Click to collapse
Nope.
IF you flash a non stock rom and/or kernel, then it depends on what you use. Read notes and user replies.
Sometimes I do get random shut downs when not in use, both while charging and not charging. I am not sure if that is a 4.1.2 issue or if it's tied to the rom I'm using. Have had it happen on two different roms.
alkemist80 said:
Nope.
IF you flash a non stock rom and/or kernel, then it depends on what you use. Read notes and user replies.
Sometimes I do get random shut downs when not in use, both while charging and not charging. I am not sure if that is a 4.1.2 issue or if it's tied to the rom I'm using. Have had it happen on two different roms.
Click to expand...
Click to collapse
I lost the ability to control the music app with my headphone controls after rooting, it didnt happen when I opened the box and played with the nexus
Some apps are written to block rooted devices but there's no way the mere act of unlocking and rooting would affect overall stability.
Sent from my Nexus 7 using Tapatalk 2
After a day on stock rom I thought it was settled but no...
The battery drained down and after that it kept getting stuck at the Google Cross animation. I spent a while re-flashing stock rom and eventually it starts up. Sometimes. The accelerator issue remains but it is less frequent.
I contacted Google who put me on to Asus. They are going to send me an RMA number and we'll take it from there.
how do you revert or reset to a factory state???
I´m new with the nexus 7 so really have no clue
To reset your device, go to "settings", then "backup & reset", and finally "factory data reset".
The difficult in waking is something I went through with my N7. I found there is a bug with the auto-brightness setting. If I use the manual option I don't experience any problems.
I rooted my N7 the day I got it (had experience with SGS and Gnex) and haven't looked back. I haven't had any other issues than the "sleep of death".
Hope this helps.
alankstiyo said:
how do you revert or reset to a factory state???
I´m new with the nexus 7 so really have no clue
Click to expand...
Click to collapse
Bit Banger said:
To reset your device, go to "settings", then "backup & reset", and finally "factory data reset".
Click to expand...
Click to collapse
If you mean stock non rooted, then the above will set you back to factory.
If you are rooted, that will not remove the root. You will need to flash a stock image to completely return to stock and then re-lock the bootloader.
I seem to have had more problems if the power runs down. I have turned off the auto brightness and I agree it's better in terms of starting up. I still have the issue with rotation not always working. Also, I notice it takes several seconds for the screen to come on when I press the power button. Is that normal?
littld said:
I seem to have had more problems if the power runs down. I have turned off the auto brightness and I agree it's better in terms of starting up. I still have the issue with rotation not always working. Also, I notice it takes several seconds for the screen to come on when I press the power button. Is that normal?
Click to expand...
Click to collapse
No, that is not normal, whether you're rooted or not.
Sent from my Nexus 7 using xda app-developers app
alkemist80 said:
If you mean stock non rooted, then the above will set you back to factory.
If you are rooted, that will not remove the root. You will need to flash a stock image to completely return to stock and then re-lock the bootloader.
Click to expand...
Click to collapse
will the toolkit help me do this???
if so will it delete the sd card??
Sent from my Nexus 7 using xda app-developers app
Okay now it's getting weird. I got an RMA number and they are due to collect it tomorrow and fix it. Since I got the RMA number it has behaved perfectly. I did make a video of the problems but since making the video I've not been able to reproduce them. The battery is down to 14% now, will see what happens when it is fully drained. One major difference is the power button instantly switches the device on whereas it used to wait a few seconds.
Can hardware just fix itself like that? I'm concerned they'll get it and say they can't detect any problems and charge me for the shipping...
I'll keep on testing until morning but if you guys have any ideas please let me know.
alankstiyo said:
will the toolkit help me do this???
if so will it delete the sd card??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've used Wug's toolkit to return to compete stock. It will wipe everything. It's a two step process, you will still need to lock the boot loader. Go read the thread in the Android development section.
Sent from my PG86100 using xda app-developers app
It's fine, even rooted so have cancelled the RMA. Hopefully it was just a short term fluke.
Several weeks on I have had no more repetition of these problems. I did have a line flicker occasionally before installing 4.2 but even that problem has gone away now. I just don't understand how the behaviour can be so unpredictable like it needed to settle into its new home or something.
As the title states. Nexus 4 random power offs. Has anyone seen anything like this?
Here is the background info:
My parents have Nexus 4 phones as do I. All of our phones were ordered at the same time about 2 months or so ago when they became available again. All phones are the 16GB version. All phones bone stock with just OTA updates, not unlocked or rooted other than how they are shipped. All using T-Mobile prepaid plans.
My phone and my father's seem fine. My mom's however seems to shutdown on its own. It is random. Initially I thought that it may be an issue where she isn't used to a smart phone and isn't charging it enough. It happens though at times while it is connected to the charger. It also has happened while carrying it off the charger.
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
I have been around android since the G1 days and run the same phone. I can't think of a setting on the phone that would power it down at a certain time or period of time. She really doesn't have much for apps and is a very light user.
Not sure what to try but I was thinking about doing a wipe of the phone to see if it helps.
Anyone else have any ideas? If the wipe doesn't help the only other thing I can think of is that there is a physical issue with the phone.
I haven't seen this on my phone but there was a period of time where HD Widgets on my N7 would cause a reboot. That was fixed with an app update. This isn't a case where the device reboots. It is a complete shutdown which I find odd. So I have seen an app cause issues kind of like this. For the most part the apps that she has on her phone, I also have on mine. Well I have way more but there really isn't anything on her phone that I am not also running.
I should add that she has the phone in a TPU case. As we all do. My case design is a little different than theirs but they have cutouts for the buttons. So it isn't a case where the case is pressing on the power button. That could be an issue with my case as it covers the power button but I haven't had that issue.
Thanks
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
BigDig said:
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I am kind of thinking. Either the battery or the smart battery chips. I think I will try a wipe first but like I said but it is odd.
sennister said:
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
Thanks
Click to expand...
Click to collapse
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
I don't want to root and have my mom run a modified ROM. They live about a half hour from me so I haven't tried a wipe of the phone yet and because of the distance I don't want to deal with the issues that sometimes come up when you go with modified ROMs when I am not there. She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things. I have to get some time to run over there and take a look at it. Maybe later next week.
I was just wondering if anyone else has had this issue. I think if a wipe doesn't help I will talk to Google. A search really didn't show much other than some people that were seeing a random reboot issue. I have seen apps doing that.
I have been through their warranty replacement process and it is a bit of a PITA. I am on my 3rd Nexus 7 due to hardware issues with the first 2. My N4 and my fathers have been rock solid.
While I have run custom ROMs in the past, I usually run stock until I find a need that requires me to root. Eventually I will probably root and go with a custom ROM on my N4 but
sennister said:
She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things.
Click to expand...
Click to collapse
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
amartolos said:
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
Click to expand...
Click to collapse
Hmm. That is a good idea. The PITA part would be to get everything loaded from my phone to hers. I really wish I could run Titanium backup without root as it would make it super easy to move the apps over. Though I don't have that much loaded on my phone. Things that are a pain to set up have configuration export methods like Tasker. It would rule out the end user being the source of the issue. I don't think that is it though. If we swap and it goes away, then I can consider the wipe as the solution. If the problem moves to me then it is a physical issue and call Google. If the problem persists with her, I load all her apps on the phone I carry as well to see if I start to have the issue or it becomes a training issue. The thing I like about this the most is that it is a clear process to rule out several things. I can go over there and sit with the phone but if it doesn't power off when I am there I don't gain much other than spending some time with my parents.
I don't think this is an issue but I did have to provide my IMEI# when doing the activations. In the past though on T-Mobile I have handed phones down to others and all we did was a SIM swap. I would imagine that is the case here.
Oh and one thing I did leave out. They were using their old cell phone chargers on the N4 phones. I told them to swap chargers and use the ones that came with the phone. The old ones may not put out enough power and the phone could in theory run down to the point where it shuts off and slowly charge from that point and I don't think it would turn back on. Keep in mind a retired user who just had a knee replacement so she is at home more often than not.
Did you find out the cause? I have the same issue happened twice today
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
noodles2224 said:
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
Click to expand...
Click to collapse
So you're saying it's a software issue?
Looks like it.. Turning off optimization or not even using WiFi at all worked..
Sent from my Nexus 4
People love Nexus devices for the latest version of Android it gets. It's the best device to get updated with the latest version and usually cheaper than other devices in the market with same specification though Nexus 6 is bit exceptional with a bit higher price tag. Latest Android version is always exciting to us but with latest Android version, comes Latest Bugs too May be I became sarcastic, though it's true. Android Lollipop is not an exceptional to come with some bugs. One of the major bug of Lollipop is the RAM leaking issue. People has faced some major RAM leaking issue on their Nexus 5 and now Nexus 6 is also facing it. For Nexus 6 it's a major issue because it's causing Nexus 6 to force reboot and mainly force shutdown. This issue has been marked as Complete on Google Forum by a Google Employee. Jump to the first page to see it and browse through all pages to see that so many people are facing the same issue so there is no need to be panic. You can expect a fix for it as it has been marked Completed by a Google Employee. But for now we need a solution for it. ALWAYS REMEMBER THAT IT'S NOT A HARDWARE BASED PROBLEM, IT'S THE PROBLEM OF THE STOCK KERNEL. SO DON'T GET PANICKED AND REPLACE YOU DEVICE.
If you want to get rid of this problem and want to stay in stock firmware then follow the following steps:
A> Non-Rooted Device:
1. Close all apps before doing heavy tasks. You may see "System" as a recent task, don't be panic, clear it. It may appear sometimes. Even some apps which you've not opened, they may show in recent apps.
2. Don't run some specific games like NOVA3. It'll not let you go forward from the first cut-scene. It'll force shut down the device. [Tested by me]
3. Do reboot your device once in an interval of 5-6 days. 3-4 days are recommended. If you notice the RAM usage daily, you can notice that the RAM usage by System/Settings starts increasing after 2 days of usage without any reboot.
B> Rooted:
If you're rooted, you're good to go for a permanent solution.
1. If you don't want to switch to any Custom ROM, then flash a Custom Kernel like Franco Kernel or ElementalX . It'll help you to get rid of the random reboot/ force shut down.
2. Flash Custom ROMs. There are plenty of custom ROMs available for Nexus 6 which are mostly based on 5.0.2 and doesn't cause problems like this. Giving a small list of the ROMs which are being used by most of the Nexus 6 users
Dirty Unicorns
Official SlimLP Alpha
Euphoria-OS
LiquidSmooth
N6 Nocturnal Limited Edition
If it helps, please do consider pressing the "Thanks" button
Actually, the memory leak is NOT a kernel problem. The reason why it affects *ALL* Nexus devices running 5.0.x is that it is actually a problem in frameworks.
Specifically... frameworks/base/services/core/java/com/android/server/display/ColorFade.java
Neither one of these are solutions and I wouldn't even call them workarounds either
doitright said:
Actually, the memory leak is NOT a kernel problem. The reason why it affects *ALL* Nexus devices running 5.0.x is that it is actually a problem in frameworks.
Specifically... frameworks/base/services/core/java/com/android/server/display/ColorFade.java
Click to expand...
Click to collapse
Source?
crachel said:
Neither one of these are solutions and I wouldn't even call them workarounds either
Click to expand...
Click to collapse
Actually I got benefited with these solutions. Not only me but also many other Nexus 6 users That's why shared
SAW_JOK3R said:
Source?
Click to expand...
Click to collapse
https://code.google.com/p/android/issues/detail?id=79729#c239
I think the actual patch they are referring to is here;
https://code.google.com/p/android/issues/detail?id=79729#c177
Incorporated into community roms as;
https://github.com/CyanogenMod/andr...mmit/d25b891dccd223bb00f45e27062e5391a55be8ff
doitright said:
https://code.google.com/p/android/issues/detail?id=79729#c239
I think the actual patch they are referring to is here;
https://code.google.com/p/android/issues/detail?id=79729#c177
Incorporated into community roms as;
https://github.com/CyanogenMod/andr...mmit/d25b891dccd223bb00f45e27062e5391a55be8ff
Click to expand...
Click to collapse
Thanks Though I think Nexus 6 is getting effected differently as it's going to either force reboot or force shutdown where as hammerhead is facing only high RAM usage.
SAW_JOK3R said:
Thanks Though I think Nexus 6 is getting effected differently as it's going to either force reboot or force shutdown where as hammerhead is facing only high RAM usage.
Click to expand...
Click to collapse
All depends on what triggers are set and how bad it gets
Nice post
Teh Ashish said:
Nice post
Click to expand...
Click to collapse
Thanks
I'm glad to see I'm not the only one seeing these problems. Where's our 5.0.2 to fix it? Happens to me almost once a day now.
mattlgroff said:
I'm glad to see I'm not the only one seeing these problems. Where's our 5.0.2 to fix it? Happens to me almost once a day now.
Click to expand...
Click to collapse
What are you running on it? I'm currently at a *week* of uptime, and no problems noticed at all.
What are people doing to get a random Shutdown/Reboot?
Had mine for a month and it never Shutdown/Reboot on me.
I read that there maybe and update in the near future?
mattlgroff said:
I'm glad to see I'm not the only one seeing these problems. Where's our 5.0.2 to fix it? Happens to me almost once a day now.
Click to expand...
Click to collapse
May be Google is planning for a direct jump to 5.1 with all major bug fix
AstroDigital said:
What are people doing to get a random Shutdown/Reboot?
Had mine for a month and it never Shutdown/Reboot on me.
I read that there maybe and update in the near future?
Click to expand...
Click to collapse
It's happening many of the devices. As it's evident that many other major issues like screen burn-in, problem in speakers etc are not present to every devices, this issue is not an exceptional It seems that Google is planning for 5.1 update for Nexus 6
doitright said:
What are you running on it? I'm currently at a *week* of uptime, and no problems noticed at all.
Click to expand...
Click to collapse
Completely stock unrooted, never unlocked on 5.0.1.
I'm also using a stock Moto 360.
Therfreeze happens when it wants to, when I'm not using the phone. I don't usually notice until I next check my phone and the lock button doesn't unlock my phone, then I look at my Moto 360 and see that its become disconnected.
mattlgroff said:
Completely stock unrooted, never unlocked on 5.0.1.
I'm also using a stock Moto 360.
Therfreeze happens when it wants to, when I'm not using the phone. I don't usually notice until I next check my phone and the lock button doesn't unlock my phone, then I look at my Moto 360 and see that its become disconnected.
Click to expand...
Click to collapse
Could be related to the watch or some other software you're running. Or an encryption related leak. Like I said, mine's been rock solid. Straight up factory except for non-encrypt and root.
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
SAW_JOK3R said:
It's happening many of the devices. As it's evident that many other major issues like screen burn-in, problem in speakers etc are not present to every devices, this issue is not an exceptional It seems that Google is planning for 5.1 update for Nexus 6
Click to expand...
Click to collapse
Lets hope for hwcrypto....
doitright said:
Could be related to the watch or some other software you're running. Or an encryption related leak. Like I said, mine's been rock solid. Straight up factory except for non-encrypt and root.
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Lets hope for hwcrypto....
Click to expand...
Click to collapse
I think encryption has nothing to do with the random reboots And if you're considering moto 360's apps for this, then I should say, No
SAW_JOK3R said:
I think encryption has nothing to do with the random reboots
Click to expand...
Click to collapse
On what do you judge that? Software crypto is a very heavy memory user. From what I've heard, the reboots seem to be related to memory pressure.
And if you're considering moto 360's apps for this, then I should say, No
Click to expand...
Click to collapse
"Android wear" has very serious tentacles that run through frameworks and gapps. Applications themselves COULD NOT be the problem since Android will just kill them when the memory hit becomes too big, but the frameworks tentacles are another story altogether.
In any case, my point about hwcrypto was more about performance improvements from AOSP 5.1 rather than random reboots.
doitright said:
On what do you judge that? Software crypto is a very heavy memory user. From what I've heard, the reboots seem to be related to memory pressure.
"Android wear" has very serious tentacles that run through frameworks and gapps. Applications themselves COULD NOT be the problem since Android will just kill them when the memory hit becomes too big, but the frameworks tentacles are another story altogether.
In any case, my point about hwcrypto was more about performance improvements from AOSP 5.1 rather than random reboots.
Click to expand...
Click to collapse
There is RAM leaking but I've noticed today that when I went to see the RAM usage after booting up from a force shutdown, then there was 1.8GB of free RAM and then I scrolled a little bit to see which apps are occupying the space. Then guess what? Bam, again a force shut down
I fixed my phone follow link https://www.xda-developers.com/nexus-6p-bootloop-fix/. Now my phone is back but I was wondering how to bring phone run 8 cores instead using 4 cores is very slow and sometime freeze. Is there any way to fix performance?
Maybe Android 8 will fix it ?
Thank you.
AFAIK the answer is no, it is not related to Android.
psuputspon said:
I was fix my phone follow by https://www.xda-developers.com/nexus-6p-bootloop-fix/. Now my phone has back again but I was wondering how to bring phone run 8 cores instead now is 4 cores is very slow and sometime freeze or Is there any way to fix performance? May be Android 8 will fix it ? Thank you.
Click to expand...
Click to collapse
No. The bootloop "fix" is a workaround that permanently hobbles your device, allowing you to make backups and remove any photos/data you need from the phone so you can transfer to your next phone. Since your phone has a hardware defect directly related to the motherboard, there is no software update that will help. Take everything you need off the phone asap and start looking for your next phone.
v12xke said:
No. The bootloop "fix" is a workaround that permanently hobbles your device, allowing you to make backups and remove any photos/data you need from the phone so you can transfer to your next phone. Since your phone has a hardware defect directly related to the motherboard, there is no software update that will help. Take everything you need off the phone asap and start looking for your next phone.
Click to expand...
Click to collapse
Um...no? I mean, it's not that it hobbles your phone. And it's not that it's just a workaround to make backups. In fact it runs almost the same. Turns out, after some digging in, @XCnathan32 found out that even a normal 6p was throtling it's 4 BIG cores from 2ghz to 800mhz, because of which the phone was heating up and marginally running better as compared to the current fix. Now it doesn't heat up and runs slightly lower (not even noticable) than what it used to.
My phone, for one, works almost identical. No dip in performance for my usual activities - no games. Occasionally I run Drastic DS for some emulated NDS games. Never had a bootloop since.
As for the original question: the bootlooping will still occur. It seems to be a hardware issue as far as what I've followed in XCnathan32's posts.
The same link that OP has, will take him to the fix with the flashable Oreo kernels as well.
Tivaldi said:
Um...no? I mean, it's not that it hobbles your phone. And it's not that it's just a workaround to make backups. In fact it runs almost the same. Turns out, after some digging in, @XCnathan32 found out that even a normal 6p was throtling it's 4 BIG cores from 2ghz to 800mhz, because of which the phone was heating up and marginally running better as compared to the current fix. Now it doesn't heat up and runs slightly lower (not even noticable) than what it used to.
My phone, for one, works almost identical. No dip in performance for my usual activities - no games. Occasionally I run Drastic DS for some emulated NDS games. Never had a bootloop since.
As for the original question: the bootlooping will still occur. It seems to be a hardware issue as far as what I've followed in XCnathan32's posts.
The same link that OP has, will take him to the fix with the flashable Oreo kernels as well.
Click to expand...
Click to collapse
Have you heard reports from people that got bootloopd again after applying the 4 core fix?
darkriff said:
Have you heard reports from people that got bootloopd again after applying the 4 core fix?
Click to expand...
Click to collapse
I haven't read any such. There may be. I believe the best person to answer this would be the creator of the bootloop fix, since people with such issues would PM him.
v12xke said:
No. The bootloop "fix" is a workaround that permanently hobbles your device, allowing you to make backups and remove any photos/data you need from the phone so you can transfer to your next phone. Since your phone has a hardware defect directly related to the motherboard, there is no software update that will help. Take everything you need off the phone asap and start looking for your next phone.
Click to expand...
Click to collapse
So the boot loop issue has been definitively identified as a hardware issue then? I just got paid out for my Square Trade insurance on my 6P and was considering going back hoping against hope that O would finally fix some of this stuff. Damn shame...
BushidoCowboy said:
So the boot loop issue has been definitively identified as a hardware issue then? I just got paid out for my Square Trade insurance on my 6P and was considering going back hoping against hope that O would finally fix some of this stuff. Damn shame...
Click to expand...
Click to collapse
BLOD is a hardware defect plain and simple. No software upgrade (or workaround) will ever change this but not all devices are affected. I think the chances of you finding a NEW 6P are pretty slim... but still possible. We have two 6P's that are approaching 2 years old and no sign of battery degradation or any other issues. I wouldn't touch a refurb at this stage. Probably the best bang for the buck would be a Pixel XL, now the new ones are in the pipeline, prices should be dropping significantly.
I get alert to update Android 8 today. It's worth to update?. Anyone who has experience update the phone with patch fixed bootloop. Is there any concern?
psuputspon said:
I get alert to update Android 8 today. It's worth to update?. Anyone who has experience update the phone with patch fixed bootloop. Is there any concern?
Click to expand...
Click to collapse
If your device is stock there is no concern and yes, you should take the update . If you had the bootloop issue and needed to apply the workaround to your device to get it working, then you will have to wait because the update would overwrite the fix.
v12xke said:
If your device is stock there is no concern and yes, you should take the update . If you had the bootloop issue and needed to apply the workaround to your device to get it working, then you will have to wait because the update would overwrite the fix.
Click to expand...
Click to collapse
I tried to OTA update but it can't install then I decided to flash stock with google image and flash to fix bootloop again then I can't open it stuck in loading animation. my device is gone now, Dead completely.
Ps. I installed twrp also before flashing is OTA problem to update