Hello all,
Let me start off the message by mentioning that I have been a (altogether) very happy user of cyanogen mods with my last 3 android phones.
The last and current (but it seems not for long) is an HTC One X, which is over 2 years old.
This poor thing has gone through so many ROMs that I have lost count.
It is currently running on a stable cm10.2.1, upgraded from cm10.1.3.
I have experienced sudden power offs when there were obvious battery drain, battery overheat, weird app installation issues, especially since moving to cm 10.2.1, which also caused the GPS to stop getting any satellite signals.
However, the phone has recently (a couple of weeks) leveled up into a bizarre mode:
It will power off all of a sudden, the battery levels are not low 65-75%, so I would assume it was just some process in the background, and go ahead and start the phone up again to go and check through the logs, or even disable/cleanup dodgy overreacting apps. But to my surprise, the phone passes the quietly brilliant screen, as well as the CM logo with the circling arrow and as soon as you can see the background it shows Powering off - the phone is shutting down.
For those brief couple of seconds I can see the battery indicator (top right corner) showing a small part of it in red, letting me believe the battery's status is critically low. So I let the phone charge for half an hour, and start it up again, with the same result, once the device goes past the logo and the background shows, the Powering off message appears again. The battery indicator is still showing a small red circulating section of the whole.
The next step was to go and check in recovery mode. The battery on the TWRP screen shows almost 70%, and this leads me to assume there is something wrong with the battery. But the phone is not turning off for as long as in recovery mode. I still haven't ruled out the battery issue, and will test it when I get delivered and replace the spare one I have ordered.
Reading through forums and other threads, there were people complaining that they had the same issues when the phone was trying to change from 2G to 3G and the other way around, so I removed the sim card and have restarted the phone, still the same result, powering off after boot.
I also reflashed 10.2.1 thinking that a clean installation will help getting rid of some new app/processes that might be causing this, but exactly the same powering off occurs after booting. The same happens even after a factory reset.
Usually, after half an hour of inactivity the phone would start up normally, but today it has been several hours and the behavior is not improving.
At this point I can't get into the phone other than on recovery, I can't copy from/into its storage anything, not even the nandroid backups I regularly do (and which stupidly I haven't copied over to an external storage). I could try reflashing some stock image, but even that I don't have on the internal storage.
So as you see, I am bit stuck. Phone will not stay ON long enough for me to connect to my machine and save my backups, or load any new stuff.
If you have any other suggestions other than this, or perhaps a workaround to what I have already tried, I would extremely appreciate it.
Cheers,
Mad
I have the same problem..
I have tried everything, but nothing helped me.
Now my battery is 0% and i cant do nothing - cant charge it, cant boot in bootloader.
Something heppened when you changed the bettery?
Related
I want to explain a method that actually gives me real results for resetting the batterystats after a ROM upgrade. I never thought a batterystats reset did anything and it's likely because I wasn't doing it this way. For this I use a conjunction of two things but really you could do the actually deleting of the batterystats.bin file in clockwork or by other means.
Reference Zeppelinrox's thread "Calibrating Without Downtime!" for the long version...
First, I use this Battery Calibration app from the market.
After a ROM upgrade I let my phone charge until a full charge. The Battery Calibration app helps because it'll ding which is nice.
Delete the batterystats file, and while leaving your phone plugged in, pull off the cover and reboot.
At the 2nd LG logo (i.e. - pink and white one or Backside's (?) IHO logo) pull the battery out. Sometimes I wait 5 seconds, 10 seconds 20 seconds or whenever before I pull it out- just make sure it's during that part of the boot sequence.
At some point later in the boot sequence it's recreating the batterystats.bin file in the background and presumes the battery is not charged since it's been removed.
Put your battery back in, keeping the phone still plugged in.
You may have to do this routine a few times before you can tell but what should happen is you'll have a 100% pre-reboot and after the last step it'll drop down to a lower number that will need to be charged back up.
You may want to read Zepp's post because it may help to read his instructions too.
If you see a 'please put the battery in' type message just put it in and try the instructions a few more times.
I'm regurgitating someone else's work a lot. Thank Zeppelinrox for his work. Some of my finds have been from trudging through some of his ginormous threads. I'm just trying to pull out the nuggets.
Right so, I've tried this quite a bit, and I can never get to the lock screen without battery before the phone complains that I need a battery. I've inserted it after the vibration during the boot sequence but it'll show up at 100% at the lock screen.
EDIT: OK so I did something different that netted results.
I fully charged, batterystats.bin, then reboot per normal instructions. I counted 4 bananas P) once the pink and white LG Logo came up and pulled the battery. Instead of reinserting after vibration, I let it keep going until it asked me to insert battery. I slid it in, and the phone rebooted. I left it there and once I hit the lock screen my phone read at 99% instead of the "Charged" reading I was getting. I charged for an extra 20 minutes and my phone topped off at 4199mv.
During my trials trying to get a non-charged reading at the lock screen, I looked into Battery Monitor and I was seeing 4160mv-4197mv readings, all of them varying. I did not top off at 4199 until I did it the way I just described.
I end up counting too. I guess I haven't found a perfect number so I just try pulling the battery out at random times during the 2nd LG logo. Sometimes when I go through the steps I get all the way to the Android boot screen with the message "connect your charger" for the battery status on the lock screen and I can even use my phone. I think at that point I know I've done it right since it's fully booted and had to have created the new batterystats.bin file.
Once I've put the battery back in I've seen it be as low as 91% after a reset when I've done it this way.
After reading your last sentence it looks like you're getting similar results to what I get. Now I know I'm not b.s.-ing so thanks for the feedback
I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
manderson8898 said:
I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
Click to expand...
Click to collapse
Have you tried a factory reset? I'd make tmobile replace it
was hoping to avoid the reset button. Tried it and still giving trouble it rebooted while restoring apps. I bought the tablet on ebay, I don't think TMO will take it back. oh well I'll keep poking about.
thanks,
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Wall-E said:
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Click to expand...
Click to collapse
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
manderson8898 said:
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
Click to expand...
Click to collapse
Have you considered rooting and using root apps to stop the apps from being able to do such things?
Completely stock T-Mo m8. Been running Lollipop since the OTA came through, and it has worked fine for the longest time, no problems other than a bit of lag, even after clearing the cache.
A couple of days ago, the phone began to shut down whenever (seemingly) any app was launched when on battery, and then would not boot on repeated attempts. It doesn't seem to make it past the first stage of the bootloader (first HTC screen, pre-animation), most of the time. Sometimes it will make it to the T-Mobile animation and then give up.
While plugged in, it boots and works fine 9/10 times, but sometimes gives some resistance to booting. If it is unplugged and any apps are launched, it shuts down as if the battery were removed. Though, the whole while the battery seems normal, no weird fluctuations or sudden drops in battery level.
If it is unplugged after having booted and it is relatively inactive (no apps launched, or any processes, i.e. alarms, syncing, downloads, etc.), it will remain powered on.
I have attempted to Factory Reset a couple of times, and cleared the cache a couple of times. The problem persists. I can boot into recovery, though I am not rooted.
Is my battery in need of a replacement or some such? I would like to remain fully stock if at all possible. I may be able to get a replacement phone out of T-Mobile, but would also like to avoid that.
After having headache with this problem for last one month and lost hours of testing, i finally found a problem so lets explain symptoms, maybe it will help someone.
I am using CM since first version and as all nightly version have some bugs i had them as well. So i had random reboot from time to time and i thought it's just CM bugs.
For last 1 month reboots happen most often and always when i receive or make a call.
Phone just reboot and loop at boot loader. After removing battery for few seconds phone can normally boot.
3 days ago phone started to reboot even with some heavier app's but never if i disable network. Reboots start to happen even if phone is in my pocked and i exit elevator (drop network and get again).
I tried clean installation of CM12.1, Clean installation of CM13, Wiping internal storage, Clean installation of Cloudy ROM, Removing SIM card, removing SD card i even moved back to stock ROM.
Installed more then 30 app's for monitoring everything and noting show any error, problem etc. While doing all this, i realized that this problems never happen when phone is at charger. Again, installation of 20 apps for battery calibration, voltage monitoring, logs etc. and non of them showed any problem.
Battery was regullary fully charged but noticed that it happen only with heavier usage (have call, copy bigger file, start game).
After doing that tests for entire day, phone refused to pass boot loader with battery but boot normally with charger.
So i purshesed new battery last night, phone booted normally, there is no reboots or any issue at all. Now i can compare that new battery is better since it lost only 1% of battery over the night but old battery didnt show up any problems at all. It's normally to not be that good after 1 year of usage but I didnt had any drainings, it was regularry charged etc.
So if you have similiar problem, to go to some service where you can try with new battery before buying one.
I have the exact same problem .
It driving me crazy! I will try to get new one, and reply as soon as possible ! I hope it will work.
the phone just showed me that The battery that I was using it for one year is fake -_-
Yep, same issues, phone was rebooting sometimes (at the begin, only a few reboots, only during the launch of "big" activities like GPS, or photos) then a few weeks later
I needed to connect it to the charger otherwise, after a few seconds, the phone used to reboot in loop... Until it dies...
Buying a new battery resolved all the issues, no more reboots at all
I have been using fulmics for a long time now. I live somewhere where the temperature is always something around 17-25 degrees on summer and never had an overheating problem. Now, I'm on holiday somewhere hotter (canary islands) and the 30-ish temperatures are causing my phone to reboot if i take a couple of pictures or if I open apps like pokemon go. I think this has something g to do with heat because back at the hotel, I don't have these issues at all. Even when i perform the same tasks at night, the phone does not reboot.
Now, I can't remember if I chose the stock or the the thermal throttle values upon installation but I'd like to ask, which would be the best option to avoid this issue and also, any other advice you could give in order to mitigate this issue. I asked on the fulmics thread over at xda but the mods locked it because some asshole didn't stop asking the dev for Etas. Screw that guy.
Any help would be welcome! Thanks!
Hi, there will probably be an update to fulmics 6.0 which should solve overheating problems. I'd recommend for you to move to Cloudy G3 2.5 or XenonHD with aCC kernel just for now.
I also have problems with heating. When the phone is at direct sunlight for some time it become irresponsible. I mean it don't reboot but message pop up "system ui stopped ....." and screen lock. I wonder if fulmics ROM is the reason for that. As far as I remember upon installation I choose stock settings, kernel.
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
My G2 acted like this when the battery died. Its a sure sign
GFXi0N said:
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
Click to expand...
Click to collapse