Hey guys I have been running into a problem ever since I've started using custom roms for my g2x. Sometimes when I plug my phone in To charge it after I leave it there for half an hour or so j come back and the phone is extremely hot and its locked up. Cannot unlock screen or turn it on. It just looks like it is off. The only way to get it to turn back on is to remove the battery for a mjnute and then put it back in and then it will turn on. Any ideas as to why this is happening?
I had this problem before too..start with a fresh wipe but use the G2xScrubber to do this then do a format of the system, data and cache which is located mounts and storage. Then wipe dalvik and flash ROM.
Sent from my LG-P999 using Tapatalk
try enabling "Stay Awake" in the development part of the settings menu.
Charging is controlled by the bootloader and kernel. So if there is a problem with overheating, etc. during charging I would suspect the kernel first and then the bootloader. It could be you are using a custom kernel that doesn't handle charging properly.
I was having it too, if I change kernel it would be fixed?
Related
Today while in the car my GF plugged her phone into the cig charger and it said it was charging. After she unplugged it the battery still showed it was charging.. So I factory reset it and wiped dalvik cache. That did nothing. The phone boots up showing that its plugged into USB and debugging is active. So I did a full wipe and reflashed the ROM (Royal Glacier v1.2). Still having the same results. After checking the uptime I also noticed uptime and awake time are the same so the phone isnt sleeping when the screen turns off. Anyone have the slightest clue wtf happened? I thought the ROM may have just glitched but the fact that its still there after a full wipe and reflash is making me worry. Any help would be appreciated!
regP said:
Today while in the car my GF plugged her phone into the cig charger and it said it was charging. After she unplugged it the battery still showed it was charging.. So I factory reset it and wiped dalvik cache. That did nothing. The phone boots up showing that its plugged into USB and debugging is active. So I did a full wipe and reflashed the ROM (Royal Glacier v1.2). Still having the same results. After checking the uptime I also noticed uptime and awake time are the same so the phone isnt sleeping when the screen turns off. Anyone have the slightest clue wtf happened? I thought the ROM may have just glitched but the fact that its still there after a full wipe and reflash is making me worry. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware defect, it's nothing a flash can really fix, I had this issue way back on my G1 sometimes. I would call Tmo to request a replacement, the charger is confusing the phone so there's no much you can do now.
Figured.. Ok thanks for the fast reply!
Hi everyone, I've got a Nexus S 4g, SPH-D720.
This is the second time this happened to me: my phone's battery reached 0% and turned off, I turned it back on after plugging it in, and it turned off again for some reason. Tried to turn it back on, got stuck in a bootloop.
(I was running Apex 1.1.2 at the time that this happened, but it has happened before when I was on CM 9 v4.0 as well. The first time, I was using a calibrator app that told me I had more battery left than my phoen was displaying, so after it powered off I took the battery out and put it back in multiple times to see if the phone would turn on. It didn't. However, I did not do that this time, but the same thing happened.)
I tried clearing cache and flashing the same rom over the current one, but the loop persisted, and the only way to get my phone back was to do a data wipe/factory restore and reinstall everything from scratch.
The first time this happened, I had last backed my app up via Titanium 2 days prior. After the first time, I set Titanium to make backups every night, so the only thing I lost were a few text messages.
Now, I'm afraid to turn my phone if the battery dies in case this happens again and I have to erase everything. Is there any way I can figure out what the problem is? I suspect it is the ClockworkMod Touch Recovery (v 5.8.0.2), but has anyone else had this issue?
I appreciate you taking your time to read all the way through this.
What setting do you have cpu at? If its set too high your system cant handle the boot process correctly. If theres no power to handle the load itll reset itself. Wait until you get at least a solid bar or completely full and start your phone. Dont trust apps to properly tell you your battery percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
I forgot to add. The recovery is not causing the problem it has to do with battery and/ or rom/ kernel. And its not good for battery to constantly be run to zero. Thats why theres a warning to plug your phone in at a certain percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
Processor is set to 100 min 1200 max. Yeah, I did have the same kernel so that's probably it. I'll try not to turn my phone on until it's charged while off. Thanks!
(btw, the "app" I was using was a battery calibrator script)
Your welcome and i was having issues the same way and turned off set on boot and it didnt happen again. Some of these phones are touchy! im sure you know about scripting if you did it! Lol
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
In the last few weeks my sideckick "reboots" itself, as it don't ask for the pin code.. It just reboots..
But now, he reboots and the first screen that appears that says T-mobile Sidekick 4g Samsung, appears, for about 5 seconds, turns off, and reapers, that on continuous loop!
The first time it happened, I took the battery off, and when I put it back, without me turning the phone on, e started doing the loop by itself..
After a few tries taking the battery off, he came to life..
But yesterday, that happened again, and stayed that way the whole evening.. Until it run out of battery, I went home, tried to recharge and it came to life again.. I was about to going to sleep and he rebooted again, and started the loop again.. It stayed all night that way, and in the morning, it was turned off.. I thought it was the battery again, so I plug it in, and it now is in continuous loop trying to charge the battery but before it starts, it turns off and does the loop again..
I have glourious overdose rom, but never had the problem except in the last few weeks!
Heeelp!
EDIT: It was in continuous loop trying to recharge, but I unplug it, and it turned on! It had 2% battery, and is now charging on.. I rebooted in recovery, and wiped cache and dalvik cache.. Probably it will happen the same all over again during the day..
I am considering changing rom..
It could be a battery issue, but the first thing i would do is dirty flash the same ROM on top of this one (no wipes) and see if it helps. If not do a full wipe then flash a new ROM. If this still dosent fix this then i would go back to stock with hiemdall and choose to repartition at the same time, then reroot and flash a ROM.
Also make sure the contacts to the battery are clean and touching fully, if it is a battery, at least they are cheap!
hope it all works out!
This may be something that happen during root that messed it up
So if demkantor suggestions didn't help odin to kg2 then root an flash a new rom should help if not its a really bad issues with either the battery or other hard ware (like the power button broke an is constantly pushing it)
If you do fix it you want to make sure you make a backup via red/yellow cwm
Sent from my SGH-T839 using xda app-developers app
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
---Edit---
I should note that I can have all the radios on when it is plugged in, I just can not have them on when unplugged right now.
mikeoconnor said:
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not?
If you're rooted/on a custom ROM, I would make a backup of all non-system apps and settings and try to start over. The fact that you dont get that when in recovery is the biggest indicator.
First, back up all NON-SYSTEM apps/settings with Titanium backup (or something similar).
Then follow my fix >>>HERE<<< and see if that helps
I am currently on CM-10-20130728-NIGHTLY, I should also note one thing I did try was to update the ROM yesterday AFTER the problem started (problem started at 4pm I updated the ROM at 7pm), it use to be CM-10-20130526-NIGHTLY. I will look at your link and see if that works.
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I hope you are wrong, but I fear you are right. But I am going to do the steps cited above and see if that helps, right now I am doing a second back up (first was Titanium backup, now is the CWRM backup) and I am going to do the flashing stuff who knows. Don't have much to loss, and I am still open to other ideas, if any one else has them.
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
That's a distinct possibility, but not the only cause for what he's experiencing. Jumping the gun and buying new hardware usually results in money spent on hardware that wasn't needed a good portion of the time.
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
mikeoconnor said:
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
Click to expand...
Click to collapse
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
jparnell8839 said:
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
Click to expand...
Click to collapse
It is white (indicating no water damage) also the other indicators on the phone are white. I hope you are right on that that would be sweet, I will stop by the tmo store before I head home tonight. And thanks for all the help (I now have to go back and "Thank" all the posts by you two, it is appreciated)
Funny part is I took the battery out to double check the sticker (even though I was sure it was still white) and the phone died even though it was still plugged in (so I guess I need both the battery and power plug for now)
mikeoconnor said:
It is white (indicating no water damage) also the other indicators on the phone are white.
Click to expand...
Click to collapse
you might get lucky and get a free one out of it. cant hurt to ask
Thanks all I picked up a new battery today and I looks like it is working. Sadly T-Mobile did not replace it for free but the phone is working again.
Sent from my Thrive using Tapatalk 2
Going to sleep I put my phone on the charger. When I woke up it was boot looping and damn hot even to hold. I managed to turn it off, went to recovery and cleared cache and dalvik cache - after that it booted normaly (it seems). During all night (~7h) it managed to charge only up to ~45%.
The problem that I have now:
when the charger is connected screen keeps locking up and unlocking rapidly - there is nothing I can do.
I am using latest LiquidSmooth rom.
Any ideas what the hell is happening?
Edit: setting "stay awake" in developer options helped to solve the issue with rapidly locking up and unlocking while charging. Still it's a mistery what has happened
svaike said:
Going to sleep I put my phone on the charger. When I woke up it was boot looping and damn hot even to hold. I managed to turn it off, went to recovery and cleared cache and dalvik cache - after that it booted normaly (it seems). During all night (~7h) it managed to charge only up to ~45%.
The problem that I have now:
when the charger is connected screen keeps locking up and unlocking rapidly - there is nothing I can do.
I am using latest LiquidSmooth rom.
Any ideas what the hell is happening?
Edit: setting "stay awake" in developer options helped to solve the issue with rapidly locking up and unlocking while charging. Still it's a mistery what has happened
Click to expand...
Click to collapse
probably an app running on the background or use the batterystats app and it will tell you which app has been draining the battery
You enabled battery animations, atm it causes that issue like it says in the op of liquidsmooth
It wasn't the TYLT wireless charger was it? I know some people were having problems with it where it would heat up immensely.