For the past few days am facing a weird problem with my arc..
It suddenly stops charging or refuses to charge though the cable n socket are all right.
I tried different places too and it didn't charge.
After a while,i switched it off an turned it back on n it started charging.
I thought the prob was over but it keeps repeating after a day or so.
Any help or suggestions pls.
Am using Arconium 8.1 with doomkernel v22 with baseband 64..its overclocked to 1.4 GHz and smartassV2 as governor and deadline as scheduler.
Voltages are undervolted to -75 for all frequencies.
I have the same here!
I'm facing the same problem here. But with stock rooted firmware .62 (stock kernel too), i think this problem is not a software problem but a hardware, maybe the battery can be damaged.
I did the battery test in the service menu (dial: *#*#7378423#*#*) and my battery showed to be damaged, but for now it's working fine, i'm just waiting to the problem comes again to take it to the service, it still is in the warranty period, so i will see if they give me another battery.
Checked it, but it says my battery status is good.
Thanks for reply
Sent from my LT15i using XDA
Related
I just got my Epic 4G Touch today, got it rooted with CWM via the Zedomax v3 kernel. Now I'm not sure what made my phone overheat, it was super hot on both sides and even a small icon with a red thermometer popped up while it was charging. Is it the kernel itself or is it because I had it overclocked with SetCPU at 1.6ghz. I thought it would be stable but I could be wrong.
Can anybody tell me if they've had overheating issues with overclocking? If I don't overclock will I have issues with the Zedomax kernal? Thanks.
orthopak said:
I just got my Epic 4G Touch today, got it rooted with CWM via the Zedomax v3 kernel. Now I'm not sure what made my phone overheat, it was super hot on both sides and even a small icon with a red thermometer popped up while it was charging. Is it the kernel itself or is it because I had it overclocked with SetCPU at 1.6ghz. I thought it would be stable but I could be wrong.
Can anybody tell me if they've had overheating issues with overclocking? If I don't overclock will I have issues with the Zedomax kernal? Thanks.
Click to expand...
Click to collapse
im running the same kernel and i run normally at 82-97 degrees never gets to hot
what do u guys use to read your cpu temp?
r3a1ist said:
what do u guys use to read your cpu temp?
Click to expand...
Click to collapse
the setCPU widget will do it
BLOWNCO said:
im running the same kernel and i run normally at 82-97 degrees never gets to hot
Click to expand...
Click to collapse
Are you overclocking at all? I should have looked at the temp from setcpu, but once I felt how hot it was I turned it off asap. I reflashed stock kernel, and reflashed zedomax v3. I'll try it again without overclocking and see if it gets hot once more. Hopefully it doesn't.
*UPDATE: Charged the phone for 20 mins, looked at it and it had a message "Charging has been paused, temperature is too high." I checked setcpu and it was at 120F I guess I'll go back to stock kernel and charge it to see if it gets this hot.
Did the stock kernel fix this issue for you? I've had mine for 1 week, 1st day I rooted & flashed Starburst 1.9...last night I was charging (Motorola charger), streaming Netflix w/audio over BT for about 2.5 hours when phone locked up. I powered down by holding power button & when the "off" screen with the battery indicator came up it also had a flashing thermometer on the screen.
It will be in very similar conditions tonight, so I'll see if that was a fluke...hopefully it's not going to be a regular occurrence!
So has anybody else had this issue?
Carl
I charge my DHD every night over night, to make sure it has a full charge at the start of everyday. I've had my DHD for 16 months and I have had no problems with it ever. I've run many ROMS and kernels and its been rooted since the first week I got it. However it now overheats when I put it on charge almost every night.
I plug it in and the temperature will steadily rise from about 29 - 32C (which is what it runs at throughout the day) to over 40C, I've never seen what it actually reaches because since its over night I haven't monitored it that much. The highest I've seen it is 47C. After the first few occurrences of this I set a profile in setcpu to set the phone to 800Mhz when temperatures go over 38C. However this was to no avail. I then set it to underclock all the way down to 230Mhz when it goes over just 35C. But yet it still overheats when on charge so I don't think it has anything to do with my CPU? I changed kernels too but it still didn't help. The only reason this really annoys me is when it does over heat (lets say 1 in every 3 nights) I wake up and its just boot looping over and over until I do a battery pull. Which means my alarm hasn't been going off so I've had to dig out the old G1 the past two weeks just for it to act as an emergency alarm in case the DHD overheats.
I'm not sure what my problem is here, any insight?
Might want to try replacing the battery. Is it a third party bettery, those cheap "Gold 2000ma" batteries are notorious for overheating and being a bit rubbish. The other thing that might have happened is there is a short in the charging circuit which is causing the overheating.
I would say it's a 80% chance of it being a hardware problem. Try a different ROM if you are unsure.
If you have an o/c tool like no frills cpu control or anything like that, then that could be your issue too. Running high on cpu can cause overheat even when the phone is in sleep mode.
Sent from my HTC Desire HD using XDA App
Thanks for the replies.
I have my cpu overclocked during the day but I have a profile in setcpu which underclocks it to 230Mhz when the phone goes over 35C. I've seen this in affect and the cpu does downclock as expected yet my phone is still overheating.
I am using the stock HTC battery still and have had no issues with it before. I will try another ROM/kernel combo and see if it that resolves my issue just in case. Otherwise I might have to S-ON my phone again, put it back to stock and send it to HTC...
didge3 said:
Thanks for the replies.
I have my cpu overclocked during the day but I have a profile in setcpu which underclocks it to 230Mhz when the phone goes over 35C. I've seen this in affect and the cpu does downclock as expected yet my phone is still overheating.
I am using the stock HTC battery still and have had no issues with it before. I will try another ROM/kernel combo and see if it that resolves my issue just in case. Otherwise I might have to S-ON my phone again, put it back to stock and send it to HTC...
Click to expand...
Click to collapse
I had this same problem it was the setcpu app or no frills create another profile and put the setting on charging and turn setting down or add profile when screens off 122-245 set priorities to high hope this helps
If it's not a software issue, your battery might be faulty and you should switch it as soon as you can.
starkilling said:
If it's not a software issue, your battery might be faulty and you should switch it as soon as you can.
Click to expand...
Click to collapse
My Desire HD is fitted withe the original battery and its also getting hot during charging.
I've been monitoring my battery with 'Battery Monitor Widget' from the market, the recordings show that throughout the day my battery fluctuates between 20 - 30C depending on my usage. As soon as I plug it in however the battery immediately starts creeping up from low 30's to around 47C, this is where the monitoring stopped and has a huge gap until morning when I boot my phone again.
I applied a new profile in setcpu as suggested for charging instead of temperature and tested again last night, I set the charging profile to 230/384 min/max. The monitoring from last night shows the phone reached 40C by the time it'd charged to 100% and steadily started to cool back towards 30C, my phone was on when I woke up and functional so hopefully this is a temporary fix until I eventually have to get a new battery because I'm pretty certain its a hardware fault.
How long is the standard warranty for a Desire HD? If its 1 year then I'm out of luck and will have to buy a replacement...
didge3 said:
I've been monitoring my battery with 'Battery Monitor Widget' from the market, the recordings show that throughout the day my battery fluctuates between 20 - 30C depending on my usage. As soon as I plug it in however the battery immediately starts creeping up from low 30's to around 47C, this is where the monitoring stopped and has a huge gap until morning when I boot my phone again.
I applied a new profile in setcpu as suggested for charging instead of temperature and tested again last night, I set the charging profile to 230/384 min/max. The monitoring from last night shows the phone reached 40C by the time it'd charged to 100% and steadily started to cool back towards 30C, my phone was on when I woke up and functional so hopefully this is a temporary fix until I eventually have to get a new battery because I'm pretty certain its a hardware fault.
How long is the standard warranty for a Desire HD? If its 1 year then I'm out of luck and will have to buy a replacement...
Click to expand...
Click to collapse
Did you ever try uninstalling the setcpu app or any cpu controller and try that.. another thing what Rom are you using . Did you try wiping the battery stats in recovery
hopesfall190 said:
Did you ever try uninstalling the setcpu app or any cpu controller and try that.. another thing what Rom are you using . Did you try wiping the battery stats in recovery
Click to expand...
Click to collapse
Worth a try, Im using Virtuous Quattro RC3 at the moment. Although the ROM development seems to have died so I might try the other stock ICS ROM I see floating around for the DHD.
I've been told to dump setcpu about 948 times before due to performance issues it supposedly brings or other faults and I just cant tear myself away from it, I've had the widget on my home screen in the same place set up the same way for about 3 years across 2 different phones and about 20 different ROM's, I just cant seem to force myself to get rid of it.
Wiping my battery stats seems like a good idea and I'll make sure to do that tomorrow morning when my phone will be fully charged. I'll also change my ROM later this week and if I'm still getting issues I will TRY to ditch setcpu for a while. If I still have issues then I will have narrowed it down to some sort of hardware fault.
Hello Members!
I have a rather odd problem my second xperia play rooted with stock rom starts to behave strange.
I had it repaired since the connector between the screen broke (seems a common play problem).
Now to the problem my xperia play is starting to charge very fast and discharches at very fast speed aswell.
I didn't use the play for 2 months since the repair center didn't have the connector in stock.
I didn't send my battery to them because I rooted the device and if they decided not to repair it I needed to pay 40 euros to get the device unrepaired back. So yea I just sent the play withouth a battery if there was a chance they didn't want to repair it I still had a spare battery.
But they repaired my rooted device !
Anyway the battery stayed dormant for 2 months aproxx. Since yesterday I have my second play back and this problem is occuring.
Another strange thing is when I put the other battery in my play and try to charge it there the device won't charge at all
The led is on but the battery indicator doesn't show the charging icon. The other battery doesn't have this problem it behaves the same on both devices and charges normally and discharges normally aswell
Did the battery die on me ? Would wiping battery stats help ? or anything else I can try?
I assume that the battery is giving the phones wrong readings but then again doesn't explain why the other play behaves diffrently so I am very confused of course.
At the moment I discharged the battery to 0% and charging it way back up to 100%
Edit in less then one hour the battery has gone from 0 to 62%
The strange thing is my other unrooted play doesn't want to charge the battery ( led on that it charges indicator on upper right corner not)
Kind regards
Edit now testing a full discharge fired up a game with wifi on to see if the battery is giving wrong readings.
Problem still the same though when I put it in the other play charging icon not showing.
Will try to delete battery stats after this and see if this works
Any other help is appriciated
Ok things I tried so far
Full charge/discharge = did not help
Wiping battery stats = did not help
Reflashing rom + wiping battery stats = did not help.
Still same problem battery charges in old xperia play but not in new xperia play.
Really no one else that has tips ?
Kind Regards
Probably Hardware problem.
Looks like overclocked battery.
Sent from my R800i using xda app-developers app
You cant overclock the battery imo didnt overclock develice either
Verstuurd van mijn R800i met Tapatalk
I recently bought an 2ndhand Arc S that is heating up pretty bad on the top front and top back part of the phone, the middle part and lower part of the phone is not heating .Even it is newly on after 2 minutes it heats up(also in idle). Also when i shutdown the phone, it's still heating and draining the battery. It will just cool down when i remove the battery on the phone. Is it grounded?? or what?? Please help me guys i love arc s (
Edit: also when i charge the phone when it is off, it is still heating up pretty bad.
Same happens to me, i thought leaving my stock gingerbread rom and installer newer custom ROMs would be "progress".
But i get nothing but issues, 3 minutes boot times, crashes, lower battery time, heating.
Try to Lower CPU frequency.
Sent from my LT18i using XDA Free mobile app
Dear xda community,
my problem is that my battery level says my battery is charged to 4432 mAh (checked via couple of battery calibration apps), interesting thing is, that the max capacity of my original battery pack is only 3000 mAh
Things that may occured by this is, that my phone reboots frequently if i plug it off the charger. It does this in a way which makes it for me unusable, because it did not even load further than the lg logo in the bootloader, only way to fix it up again is to plug the charger back in. I tried flashing a new rom, an older rom (where these problems never came up) and also flashing the latest kernel.
I'm currently running on cm-13.0-20160309-NIGHTLY-d855.
Hope somebody can identify the problem and help me out
Best wishes,
LoCk :3
dude ur battery is gone.i had the same problem and the only fix is new battery.so go get a new one ok,it will solve ur problem i guaranty u that.