Related
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
jpzsports said:
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
Click to expand...
Click to collapse
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
cmlusco said:
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
Click to expand...
Click to collapse
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
It's hard to even guess unless you can get a log. If you give one of the stock based ROMs another trial for a few days, and the phone does not reboot, then it is safe to say it is not hardware. I'd start by at least ruling out the hardware possibility.
Do not use Titanium or some other app to restore any sort of data from one ROM to another. That often seems to cause a lot of people problems.
If your phone isn't that hot, I agree that heat isn't likely the problem. Mine absolutely roasts while navigating (while charging, screen on, gps and 3g antennas on, music playing, overclocked, weak original stock battery, otterbox case so it can't breathe, etc.) and it doesn't ever reboot from heat.
Everyone uses their phones differently. So what may be stable for one person might not be for others. I've come to the conclusion that there is only one person who can determine if a ROM is stable... that is the one person who uses it everyday. Just because some other people are using a ROM and getting good results, it doesn't mean that you ever will (even with you wiping/flashing/installing apps by the book).
CM9, CM10, or any and all ICS and JB roms are going to have things that aren't working right for some time still. It's just the nature of the beast. App compatibility, especially, is just one of those things. It's a testament to how good those awesome devs are that anything works on our Dinc running JB and ICS.
I never ran the ICS and JB ports for long (in fact only very short periods of time) because my problems far outweighed the benefits. There is no shame in GB working better for you. I run a variant of CM7 (which is gingerbread)... it is definitely different than stock-sense. Then I use alternate launchers (Go launcher is my favorite) to change it up even more. You can do so much customization that isn't dependent on the ROM. Then I can use something like ROM TOOLBOX PRO for even more customization.
Software is not fashion. What actually works never goes out of style (despite what the hipster kids on xda might be saying ...get off my lawn... grumble...)
jpzsports said:
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
Click to expand...
Click to collapse
I would use incredicontrol and raise all max voltages by 25 or one push of the plus button. Sometimes as phones get older the processors get worn , and have issues with not enough power or even with the stock max frequencie of 998mhz. If raising the max voltage dosent help, i would underclock down from max 998.
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
jpzsports said:
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
Click to expand...
Click to collapse
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
musical_chairs said:
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
Click to expand...
Click to collapse
That is true, if i go down to 128 i have screen on freezing issues, and random reboots.
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
Click to expand...
Click to collapse
This is certainly a clue... but I don't know what it means...
I would not think the the extended battery would produce more heat. Since both batteries should be discharging at the same rates the heat output should be the same (just that the bigger one would take longer since it has more reserve). I've ran across stories of people who had phones that went completely wonky when they tried swapping batteries or getting a new one. I really don't know anything about it, I'm still on my stock battery.
It certainly couldn't hurt to try wiping your battery stats in clockwork. There is apparently some magic methodology to do it "correctly". I don't know about that either... here is a thread.
http://forum.xda-developers.com/showthread.php?t=1359395
Well just as an update, I tried the overvolting and clearing the battery stats but still got the reboots. I installed one of the Stock Sense ROMs and it's been running great with no reboots. Apparently my phone just doesn't like non-Sense ROMs for some reason. Oh well. At least I have a working phone. Pretty amazing how fast the stock rom runs!
Well, I guess it's good to hear the hardware is ok.
You still could try out the CM10s (or other JB roms) by starting off without installing your apps (if you can live without them). App compatibility might be your problem. Let it run for a while with no additional apps added. Then, add them back slowly (one or two a day or every couple of days) from the market only. If the reboots start up later on... you will probably recognize the one that is the source of trouble.
Of course you still have plenty of options in the gingerbread family to choose from. If you've never tried out some GB AOSP/CM roms, that would be worth a try. You've got stock roms, stock roms with sense removed, and the whole variety of AOSP/CM7 (official and unofficial) to choose from. Launchers...themes... mods... etc... all kinds of ways to change from whatever you start with. The only GB roms that I ever had problems with were the official "stable" CM7.0 and CM7.1 ROMs. I've been running one unofficial CM7 build (about 99.99% of the time...except to test drive newer stuff) for almost a year. Its been the best thing that's ever happened to my phone.
I know, our device has really great battery life and I don't have anything to complain about that, but a friend of mine just got himself a new phone and his values make me a bit jealous and most of all: surprised and stunned.
He got himself a Xiaomi Redmi Note 4 (SD 625 variant, MKT variant really sucks), it has the same processor, same display and not even 700 mAh more (4100 mAh) and he got with some "dev rom" (made by Xiaomi, seems to just be the beta of that ugly MIUI 9, based on Andorid 7.0) 6h of SOT, doze seems to haven't really kicked in in that time. in their forum in the SOT thread I see people getting normally about 8-10 with up to over 12 h of SOT, most of them on stock ROM without any additions. And I'm quite irritated about that huge of a difference with not that much more battery. And he seems quite convinced that it's not on the cost of performance, you should notice that quickly on such a heavily skinned ROM.
Now my question is: how in hell is that even possible? I mean our devices seem quite comparablewith just a slight bump in battery but near-stock AOSP Android against pretty much an iOS clone. Does anyone have any idea what could cause that big of a difference? And if it's software based could that be done on our device? Because my experience and from different posts our device lasts about 5-6 h normally.
I mean I'm already lucky about my 2 days of usage with up to about 2.5 days on some weekends where I have a lot of stuff to do. But I wouldn't mind a bit of extra. But my biggest problem with that is as simple as: how? I could really use some explaination right now...
I don't have issues with device.. stock 7.1.1 with dec.patch, unlocked bootloader, with latest magisk. Also installed greenify.
Then you are one of very rare cases. My experience is about half of that.
And I also meant on stock ROM, without any modifications. So I don't know which apps you greenified, but that was not the point. I use Greenify too but more for apps that aren't supposed to run constantly in background when I only use it very seldomly.
The norm for this phone is 8+ hours SOT. Sometimes I get 10 and a few have had up to 12. Unless you're gaming 8 should be easy. 5 hours means something is wrong with your phone hardware, you have a rogue battery eating app or you're gaming. I rarely charge my phone over the weekend even when I use it a lot.
Well, neither of that is the case and I rarely see people claiming more than 6h of SOT
So the answer to your question is, it's the wrong question. The question should be, why does my battery not last very long and what apps or usage causes me to have such poor battery life? Compared to the Redmi Note 4 the Z Play is exactly where it should be.
Here's a link to the SOT thread: https://forum.xda-developers.com/moto-z-play/review/screen-time-t3643959
gsmarena battery life test 100h endurance rating: https://www.gsmarena.com/battery-test.php3?idPhone=8310#show
Here's an app to help diagnose battery condition (Accubattery): https://play.google.com/store/apps/details?id=com.digibites.accubattery&hl=en
also betterbatterystats is really helpful.
I sincerely hope you get it sorted out!
Well, gsam isn't detecting any app that's off even with root so I don't think there is any. I installed that AccuBattery app, let's see what it has to say
Removed because of ****ty q&a system...
Oh, and another thing I noticed: I get very randomly reboots, and every time the battery percentage drops massively. Just had a 30% drop. And after the reboot the battery percentage seems like frozen. Now I rebooted and plugged in the cable and got 44% again... No fast charging. Do that detection seems very off
Motorola forum isn't helpful at all. Clearing cache and dalvik didn't change anything and running around for a week in secure mode (that's how random they mostly are) or even doing a factory reset without restoring apps is out of question for obvious reasons.
That's pretty weird. Did you try a factory reset and after restore your apps? There's not a lot you can do if you're not rooted, but you shouldn't need to do much anyway on stock rom.
Only other option is full RSD lite OS restore as a last resort.
I am rooted for long, that's why I use Greenify. I know it also works without but then it's a joke. As RSD lite is, it just refuses for everyone to detect anything on Windows 10.
Factory reset is out of question for the moment, it takes way too long to do it properly (with titanium and NANDroid backup first) and I won't have that much time probably for the whole of this month. Otherwise I would most likely already have went off to the next best custom ROM since Motorola just can't get their **** together and still work on 8.0 in test for 2.5 month with searching testers for another one.
I think the next thing I'll do is to try the good old battery calibration, just have to find the file storing the statistics. I know many say that won't work but that's rubbish, it worked for me already a few times
Update: no, no change. Don't know if that funky battery percentage bug on random reboots still happen since I haven't had any again yet, but they come too random and unpredictable.
And that AccuBattery just proves to be worthless. It tries to estimate the rest capacity, but then it even fails to detect original capacity by 500 mAh. The battery sucker stats are also unrealistic. It puts chrome first with 10%, while GSam with root puts it 5th at 4.6% after kernel, Spotify, Android system and fight services. Android itself even puts it 9th with screen, phone idle, cell standby, Android OS and Bluetooth in-between.
So let's see what happens first. Motorola releasing 8.0, which I will flash through the .xml.zip, this time using flashfile.xml which should force a factory reset... Or me finding the time to switch to a custom ROM
Edit: so I got another one, bit this time no crazy battery drop. But the other times I killed of the soft reboot sequence because Magisk can have some problems with that. This time I didn't
Yesterday I was finally able to do the factory reset since those darn random reboots became too annoying and Moto's support is had just the most ridiculous ideas... In the worst way.
Either way, now OTA looks better, let's see how it will turn out in the next days
Help please.. i updated my note 8 in the latest version 11.0.4 global version and
I recently experiencing slow charging.. from 6-8 hrs of charging until its full
But the worst is when i turn off my unit (totally) it wont charge
No battery bar or anything.. please help
Thanks for the feedback
Help me please.. is it software fault or hardware pls give me feedback thanks
Well i'm on 11.0.4 Global too from the day that it came out and i don't face anything similar, the charging speed has always been really fast as the first day of usage.
Plus, you're asking for a feedback but it isn't that simple to provide one since that you've provided no further details about the situation: by what i read at the moment, you've encountered this issue only after that you've updated the device to the latest build, but on the same build this doesn't happens by my side. Do you face other issues other than battery charging speed, or not?
Now, assuming that your charger is in an optimal condition and that the phone never felt to the floor that hard to compromise battery status, are you sure you didn't made ANYTHING else that could cause this? Facing a slow charging time on stock ROM and stock charger it's really weird and if you didn't touched anything else, i just can't find an answer to justify this behavior in stock ROM.
Hi Lads,
i recieved the same bug after updating to 11.0.4.0(PCOMIXM). The device is only online since december, so quite young
What did i done so far:
- Loaded a the Ampere App to check if the smartphone regonize the chargeingcable correctly. It does
- With the app i was able to see that the current while loading is between 100mA to max 450mA.
- I switched the charger to an Qualcom Quickdash Charger here the current jumps sometime up to 4400mA but only for seconds before falling down to 10mA
- I did a factory reset twice. First with replaying the googlebackup, second without googlebackup. With no difference. Still stucking on 100mA
Is there a possibilty to get back to a earlier Version of MiUi?
Next thing i'll try is to load the smartphone over the weekend to get more then 40% battery so that i can try to switch to a custom rom.
I have a P3XL that's roughly 1 year old. It's seriously slow and laggy and stutters like none other. If i'm in Chrome and browsing reddit, it can crash from having a long page of images open. Using simultaneous apps like Spotify and Instagram kills the phone. I was using flashlight and making a call at the same time and it crashed.
I originally used stock, that was the same. Switched to Havoc OS and it's pretty much the same. I can only guess this is from poor RAM management. Battery life is crap now too. Doesn't last me till 6:00PM on a low usage day.
Any ROM suggestions? Or is there something here i'm missing? 4GB should be enough... the P2XL was absolutely fine but this is atrocious. I frequently want to toss this device across the room.
You may have a bad battery which is causing voltage/amperage problems and glitching. If you've already done a fresh clean install of the factory OS and still have issues that'd be my next guess.
Did you regularly run it below 20% or until dead?
Yeah I gotta say that sounds a battery issue or something else going on. I've been running stock Android 9 rooted with Kira kernel for about half a year now and although there is still a lot of reloading (especially when using chrome or internet browsers with lot of tabs open) it's still snappy and reloads quick. I've never had anything crash.
Unfortunately I have no clue how to test a battery for proper amperage. I know 2 ways to get an estimate on capacity with accubattery and extracting it from a bug report but I don't know if that will help with identify it or not.
It sounds almost identical to the same issue I had with my LG V20 which was a bad battery that would randomly shut down with around 15-25% capacity left when it got that low and when I changed the battery it fixed it
assassin10000 said:
You may have a bad battery which is causing voltage/amperage problems and glitching. If you've already done a fresh clean install of the factory OS and still have issues that'd be my next guess.
Did you regularly run it below 20% or until dead?
Click to expand...
Click to collapse
I guess it could be a bad battery causing voltage issues. I have done a fresh clean install of factory OS, and still have issues. I would say i'm average when it comes to running it below 20%. I don't do that often, but sometimes it does. I rarely let it die completely.
Best scenario would be to go through Google Support?
KUSOsan said:
Yeah I gotta say that sounds a battery issue or something else going on. I've been running stock Android 9 rooted with Kira kernel for about half a year now and although there is still a lot of reloading (especially when using chrome or internet browsers with lot of tabs open) it's still snappy and reloads quick. I've never had anything crash.
Unfortunately I have no clue how to test a battery for proper amperage. I know 2 ways to get an estimate on capacity with accubattery and extracting it from a bug report but I don't know if that will help with identify it or not.
It sounds almost identical to the same issue I had with my LG V20 which was a bad battery that would randomly shut down with around 15-25% capacity left when it got that low and when I changed the battery it fixed it
Click to expand...
Click to collapse
Yeah, mine is crashing hard. Hard enough that it's one of the poorest performance phones i've ever had. And that's saying a lot lol.
I'll try to use accubattery today to see what I get. It doesn't shut down at 15% thankfully.
dewie68 said:
Yeah, mine is crashing hard. Hard enough that it's one of the poorest performance phones i've ever had. And that's saying a lot lol.
I'll try to use accubattery today to see what I get. It doesn't shut down at 15% thankfully.
Click to expand...
Click to collapse
My V20 wouldn't always die at those ranges but it happened pretty frequently. Do you notice a difference with it plugged in?
I would definitely start from scratch if you really want to troubleshoot this. Backup everything then flash a stock system image from Google with the wipe all command and start from there and see. If it still does it then it is most likely a hardware issue.
Sounds more like a cache problem to me.....dodgy nand chip. Needs to be replaced no matter whats causing it. If you cant get rid of it after trying everything including swapping the active boot slot from a to be or vise versa
boe323 said:
Sounds more like a cache problem to me.....dodgy nand chip. Needs to be replaced no matter whats causing it. If you cant get rid of it after trying everything including swapping the active boot slot from a to be or vise versa
Click to expand...
Click to collapse
Thanks for the suggestions and information. I'll try this. Thanks everyone else!
I'm on Android 13 and was hoping this would sort out the overheating problem I had with Android 12 (I read in a few places that it would), but it did not. The phone gets very warm when charging, and hot when streaming video, and just generally through simple use, nothing particularly demanding. I haven't rooted this phone because I did not see the need, but I would consider it if it was the only way to fix the problem. Is anyone experiencing the same, and does anyone have a solution?
I could be wrong but generally speaking in my experience, going from one major upgrade to another the phone works a bit harder to re-train itself to your use patterns. I just did my upgrade yesterday and experienced some slight to moderate heat as well. I also noticed that battery is draining a bit faster which I think again is part of the process. I'm going to give it a week or so and if I'm right it should improve.
I'm biased because I've had my Pixel 6 Pro rooted (and updated every month) since last November, and I also use Kirisakura custom kernel with its companion apps and currently have the one app set to the maximum battery savings.
So I can't really compare to 100% stock unrooted with the stock kernel, as I'm only briefly on the stock unrooted kernel each month after I manually flash the latest update.
Several others have commented, and I've experienced too, that with Android 13, we've no longer experienced as severe higher temperatures when charging. I don't remember if the others were rooted and using the same custom kernel, or if these were general Android 13 comments, so your mileage may vary. Sorry I can't give you any more concrete information.
Good luck!
Granted this is for my 4a5g but I wouln't be suprised if/when I get a 6 that its battery performance would be less than stellar after a good days use of phone and/or screen and radio/network. i.e. stock. Before I went to Lineage on my 4a5g I think my battery would cut a good 30-50+ percent each day. I put lineage on it and I poop you not, can go from a 75% to around 20% in about 5-6+ days. I tend to have my screen brightness around a little less than 1/4th on the slider bar.
When I had an HTC M8, after around 2 or so years (this was around 2016/7 or so. got phone oct '14) on the stock firmware the phone couln't keep it on for more than a day. Ran ViperRom for a bit then switched to cm/lineage and that stretched my usability of the phone another 5 years. It got to the point where the phone would shut off when it got to around %50 charge and go ding dong and turn off--without pluggin it in I had about 8 hours run time on it. My battery was beyond gone and no way would I have gotten that usability on the stock rom.
So, to answer your question, yes, trying different roms and kernels (rooting) could be to your advantage to prolong the life and performance of your phone.
Even if you choose to run the stock OS, with root, you could disble any bloat running in background. Kill any programs/services leeching CPU (and hence battery) cycles. You could definately make it run more efficient for YOU. Maybe not for the next guy who needs his facebook, twitter, ticktok apis and stuff loaded and at the ready. Everyone is different. But they tend to make the phones (they think) for everyone. in mind and as a result, device performance and lifespan become affected.
I definitely have heating issues and this is on a warranty exchange. The 2 previous P6Ps had all the same issues as this current device.
My phone was hot on A12 (41/45°) and since i clean flashed A13 and wiped it is cold (32/35°) for the same usage.
Greetings.
Good topic.
I have bought this phone a day before. I'm facing device heating even under simple tasks like scrolling messengers, browsing etc.
Previously I had OnePlus 7 Pro (Snapdragon 855), that one was cold all time except while charging or playing games.
However, Pixel looks warm or even hot even upon light using.
I'm a bit confused about that.
Is it a common problem of this device? Or probably exactly my device is affected?
I haven't faced overheating or alerts about that, however, it feels hot for my hands that got used to feel a cold phone while low load.
Currently, I have about 37-38 degrees while browsing on XDA and writing this post.
Just wondering that digits you have?
I did a warranty exchange on my P6P for a different issue and I'm glad I did. My replacement device has much better thermals than my original. My original one would get quite hot while charging and restoring apps and was almost uncomfortable to hold and to the touch. Could always try a warranty exchange and see if the replacement device is better for you. Also, Kiri kernel has been reported to help with the thermals. I've seen several reports of users commenting that their device runs cooler. Good luck!
I had heating issues and battery issues when I first received my P6P. Once I got it out of the box, I set it up and restored backups, rooted it, updated to android 13 without wiping, rooted again, and then flashed the Kirisakura kernel. I decided to try and flash android 13 again but keeping the -w flag to wipe userdata and didnt restore my backups and I've had amazing battery life and no overheating. If you haven't yet, try doing a factory reset. As simple as it sounds it may very well help
My fully stock P6P (on A12) gave an overheat warning yesterday while we were having a day out, it was only 22°C although we were in and out of the sun as the clouds rolled by but the phone was showing 46°C after being sat in my pocket.
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
MrBelter said:
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
Click to expand...
Click to collapse
Try OnePlus 9 Pro
darkness4every1 said:
Try OnePlus 9 Pro
Click to expand...
Click to collapse
Thing is I have never experienced overheating on any phone (that i have owned) in UK before, using an Exynos as the basis of Tensor and then whacking an extra big core in it was a pretty bad idea unless you live in a fridge.