yesterday, i found that there was an Official OTA of HTC Sense 3.0 and android 2.3.5 for my desire S, so i decided S-ON to get the OTA.
when our phone is S-OFF, we can either using battery calibration or clear the batterystat manual.
now the problem is, my phone battery drain higher than usually after i've S-ON, can i know there're anyway to settle this problem?
instead of installing apps there're anyelse solution?
Related
I wanna know, can i beat this issue with using another battery maybe anker or mugen. Tell me your experiences guys. Anyone having same issue and using another battery can solve ?
hey mate,
i had this problem, tried every radio / rom / kernel under the sun
i brought an offical htc battery 1500mah for £15 and its all fixed
i suspect a mugen or anker would be fine aswell
Dont Overclock ull be fine
if you flashed newest radio, with old hboot this will cause that problem, either flash an older radio, or update your hboot, i prefer flashing older radio than flashing new hboot
Hey guys,
I´m new at this forum and I have a question
First I will show you some informations about my Phone:
-My Phone is S-OFF and rooted
-HBOOT 1.27.1100
-Radio 10.14.9035
-current Rom: CM9 alpha Rom
I used some different roms (first some Andorid 2.3.5 rom and later ICS Roms), but my Phone sometimes suddenly shutdown. Sometimes after a few hours, or sometimes after a few days.
It is still the same if I use the original Rom from HTC (with Android 2.3.4 with Sense 3.0).
I don´t know where the problem is ( maybe a hardware error? ), but I hope somebody can help .
I often resseted my phone, but it doesn´t take any effect. I hope there is any log on the phone which I can send you, but i don´t know where it could be
greets
Tobi
Do you use the original battery?
I got the same problems when I use an Anker battery:
http://forum.xda-developers.com/showthread.php?t=1515181
I still use the original battery...
Have you made sure the firmware is correct for each rom you experience problems with?
I assume you have updated it from original since boot = 1.27
Latest builds need 3.30
Most ics need 3.24/3.25
Some ics (now only older builds i think) and all gb run on 3.12
Check here for info:
http://forum.xda-developers.com/showthread.php?t=1412618
I think i flashed 3.30 on my Phone for the newest ICS, but the problem is, that the problem was still there when I used the original rom unrooted with the original bootloader...
Yes I think 3.30 = 1.27, I've not got round to flashing yet.
Maybe its overheating = rebooting?
It might be worth restoring to stock then sending for repair since issue was present in factory state.
stringer7 said:
Yes I think 3.30 = 1.27, I've not got round to flashing yet.
Maybe its overheating = rebooting?
It might be worth restoring to stock then sending for repair since issue was present in factory state.
Click to expand...
Click to collapse
Problem with that is that there is a chance the phone will work properly when they're going to test it... they will send it back unrepaired...
Niekjuh said:
Problem with that is that there is a chance the phone will work properly when they're going to test it... they will send it back unrepaired...
Click to expand...
Click to collapse
i don´t hope so...
It is true my phone is sometime hot, so I think it is overheating, but often it is still cold and suddenly shutdown. I think I flash it now to stock and write with amazon. Maybe I would have a bit more luck there.
Hey guys, I'm having some issues on any ICS roms where my phone would shut down at around 50-60% battery and refuse to start back up. I'm running Virtuous Inquisition 4.0 after wiping everything in 4ext, using the Super CID and the firmware found here:
http://forum.xda-developers.com/showthread.php?t=1459767
After going back to Gingerbread, I don't have the issue anymore. Any idea what I could be doing wrong on ICS? I calibrate my battery each time I flash a ROM, so I have no idea what's going on here.
try a kernel with lower clock speed
Mb try different roms? Also you may try to change the kernel and wait for a 1 or 2 days to get your system stable. random boots definetely makes life harder.
For me, same problem. If battery is 60% turns off the sensation. When I restart, it boots up home screen, and turns off again. Only on the charger it goes again.
Stock Rom , Stock Bootloader, S=on
Google translate, sorry.
install this way i have not had that problem
http://forum.xda-developers.com/showthread.php?t=1542555
fresh install maybe idk but i had two phones and all good plus people on here doing it
Hello everyone!
I'm one of the unfortunate few with an S3 chip in my HTC One S.
Thanks to developers like torxx, at least we have a TrickDroid ROM specifically made for our VilleC2 devices.
I wanted to find out if it is possible to flash stock recovery after flashing a custom ROM?
My bootloader is unlocked and I used Paul's Superboot method to root my phone. Thereafter I flashed TWRP 2.2.2.1 and left it as is since there were essentially no custom ROMs available for the VilleC2 devices at the time.
After using the phone I noticed a recurring issue with the battery, it would go gray with the "!" mark on it and would jump from 10% to 50% when I reboot the phone. Battery calibration did not solve this issue.
I successfully flashed TrickDroid 1.0 but this did not fix the battery issue either.
So I relocked my bootloader today and reloaded the RUU. The battery issue seems to have gone away, didn't get a single gray "!" occurence for the past 4 hours (and keeping fingers crossed that it doesn't occur again!).
I surmised it could be TWRP causing my battery mis-calibration and so was wondering if it was possible for me to re-root, flash TWRP, flash TrickDroid, then flash stock recovery over TWRP.
I'm very new to all this, so any advice at all would help!
Thanks in advance!
Hi everyone!
The problem occurs in the custom firmware - Maximus HD 10, CM12.1, LybertyROM, etc. When fully loaded androyd he said battery died (0%) and started off. When connecting the charge the battery was 1% witout changes, although in recovery (TWRP) showed normal levels of charge.
A temporary solution was the flashing kernel from the current ROM and clearing the cache, but after turning off the problem reappears. And I risked to remain without a connection, if not get to a computer. I tried HBOOT 2.16 / 2.15, changed the radio version does not matter.
Now I am on stock with HBOOT 2.15 and adnroid 4.1
Does anyone have ideas why this might happen?
P.S. Sorry for my English.