[Q] 100mA battery drain while on STANDBY !! ARGH !! - Desire Q&A, Help & Troubleshooting

Hi guys,
as per topic title, I'm experiencing a monstruous battery drain.
In the last few weeks I devoted a lot of time in understanding how to get more juice, with very good results.
I removed (and noticed developers) every power hungry app I had. I recalibrated my battery.
Suddenly, all of this became futile, because of this 100mA battery drain while phone is in standby, EVEN with everything (wifi, radio, gps, bluetooth, everything) off.
Like the phone itself takes 100mA to just stay in standby.
Now, this is way, way higher than "healthy" (5-8mA from users experience here on xda), and means 5-6% battery lost every 30 minutes. Doing NOTHING.
What I did:
I'm using OpenDesire since 4.0.23 , upgrading to every stable version. Today I'm at 4.0.32
Also, I upgraded the radio to latest version, 32.48.00.32U_5.11.05.14
and I noticed very good improvements.
Then, I flashed the RIL.
And the battery drain began.
Today, no matter what radio I flash, which revision of OD I revert back... Nothing seems to change, the battery drain stays.
I tried to:
- full total wipe/factory reset, always. Only app installed is CurrentWidget, to measure draining ; NO settings restored with Titanium Backup
- EVERY radio since 32.41.00.32U_5.08.00.04 ; flashed by Clockwork Recovery, phone only ; every time I tried the latest radio, I both tried without and with the suggested RIL
- OpenDesire from 4.0.23 to 4.0.32 ; Tried 4.0.23 and 4.0.28 with EVERY radio ; other OD releases tried only with stock radio (32.44.00.32U_5.09.05.30_2) and latest
- Umounted sdcard; reformatted sdcard; different sdcard; no sdcard at all
- restore my nandroid backup, made before all of this, which brings me back to my stock sense days... but with the hipotethic radio mess, and the same battery drain issue.
I don't really know what else to test.
I can't just get rid of this horrible 100mA battery drain.
Anyone has hints, suggestions, solutions ?
As of now, my Desire is ... barely a phone.
Thanks

Flash a RUU and start from fresh?
http://forum.xda-developers.com/showthread.php?t=695667

Uhm... if that's the full package, with rom and radio, may be worth the try.
I hope it's doable without Windows. Only linux here...

Oh, great... I'm having issue "waiting for bootloader".
I launch RUU
phone reboots
stops on HTC screen
RUU on PC gives error 171.
Edit:
Appearently, it's very important that the phone is recognized by Windows as "MY HTC" in system resources.
So, I did:
- install HTC Sync. Reboot. Plugged in the phone. This gets installed the necessary drivers.
- DISABLED WINDOWS 7 AUTOMATIC DRIVERS SEARCH. I think this is a windows update thing, don't really remember... I'm a linux guy ^_^
- Reboot phone in bootloader (pressing power while keeping pressing VOL- ) ; then, Windows will come up with an unrecognized device called "Android 1.0"
- Manually installed drivers under c:/programs/HTC Sync/HTC Drivers.
- Started RUU
- phone rebooted. Bad windows sound told me drivers dailed. So I went there... and the "HTC bootloader" driver appeared. Then I manually installed "MY HTC" to that device... and RUU finally started !
Also, I *HAD* to start RUU from normally booted phone. Otherwise, it failed the "minimum 30% charge" check.

chareos12 said:
Oh, great... I'm having issue "waiting for bootloader".
I launch RUU
phone reboots
stops on HTC screen
RUU on PC gives error 171.
Read here and there, solution seems
unplug & replug phone leaving as is
(note - unplugging the phone exposes the white bootloader screen, wuth RUU option only ; replugging pops up again HTC screen)
restart RUU
but isn't working:
RUU on PC can't read the phone, and gives error 170.
DAMN !!
Click to expand...
Click to collapse
Having the same problem (100 mA drain/hour in standby) ever since I started experimenting with roms/radio etc.
Going back to complete stock hasn't helped me though

Oh... damn, I just succeeded with starting RUU flash.
Oh, well. Let's see how it goes.

swine... said:
Flash a RUU and start from fresh?
http://forum.xda-developers.com/showthread.php?t=695667
Click to expand...
Click to collapse
Successfully done...
but the 100mA battery drain in standby is STILL THERE
I begin to think just flashing 1-2 radios made some mess7damage that can't just be solved with another radio flash...

SetCPU
Helps my battery time.

zHk3R said:
SetCPU
Helps my battery time.
Click to expand...
Click to collapse
... and I used it myself.
But here I'm talking about the barebone power usage, no cpu spikes, no software installed.
No phone should dry that amount of power by being on total unusage.
SetCPU is awesome, but doesn't help here.

Also trying safe mode (pwr on while pressing menu)
...
7% / 60 minutes.
This means 3-4% / 30 minutes, or 50-60mA / 30 minutes.
Oh, I had WiFi on.
Trying with WiFi off now...

Well that's some crazy battery use mate.
I have currently installed:
* OD version .32
* Radio .30_2
I have installed other ROMs before for testing, and I have tested all the radios newer than the 30_2 one. All bar the very latest one 32.48.00.32U_5.11.05.14, as I have no need for it.
I have Current Widget set to update every 1 min, and not create a log or text file when I test my use.
With the screen off for 1 min, and then turned on, Current Widget shows either 4mA or 5mA, which is my standby power consumption!
After trying what you have with the RUU I don't know what else to suggest, but wish you luck.
#Edit# Since taking the phone off charge at 8am, I have lost 6% of battery. But so far today I have only sent one message.

chareos12 said:
Also trying safe mode (pwr on while pressing menu)
...
7% / 60 minutes.
This means 3-4% / 30 minutes, or 50-60mA / 30 minutes.
Oh, I had WiFi on.
Trying with WiFi off now...
Click to expand...
Click to collapse
... and with WiFi off, it's 3% / 30 minutes. CRAZY.

swine... said:
Well that's some crazy battery use mate.
I have currently installed:
* OD version .32
* Radio .30_2
I have installed other ROMs before for testing, and I have tested all the radios newer than the 30_2 one. All bar the very latest one 32.48.00.32U_5.11.05.14, as I have no need for it.
I have Current Widget set to update every 1 min, and not create a log or text file when I test my use.
With the screen off for 1 min, and then turned on, Current Widget shows either 4mA or 5mA, which is my standby power consumption!
After trying what you have with the RUU I don't know what else to suggest, but wish you luck.
Click to expand...
Click to collapse
Thanks mate.
Question: have you ever DOWNGRADED a radio ?
If so, did you take any particular precaution ?
Also,
Just to be sure I tried everything possible, before sending my device to repair (risking many days without it, or even they discover my rooting here and there...)
may I ask you HOW do you flash the radio ?
My procedure:
- basic: I rooted via unrevoked 3.21 - all right with root permissions and got ClockWork recovery installed and working
- I (re)boot in Clockwork
- I go to Install zip from sdcard option
- I choose the radio zip file, all downloaded from the xda thread
- I apply and confirm the radio (file name is NOT update.zip ... is this an issue ?)
- phone starts to work. A progress bar apperars, fills only by 1/10th, 1-2 seconds, then suddenly process is complete and asks to reboot from menu. So I press back, and reboot.
- Phone don't reboot. It just sits 15-20 seconds saying "flashing radio" or something, but showing no progress bar. Then phone reboots. Almost immediately, reboots again
- Phone reboots back to os usable state. radio version is changed in system infos.
If I made something wrong, or something is missing or wrong in my procedure, maybe I can still solve all of this

chareos12, as you probably know by now: I got the exact same problem.
Updating/replacing radio roms/normal roms/RIL/RUU etc has nog helped me thus far.
I have one question however, what program do you use to monitor mA usage/hour?
(Nvm, found it, Current Widget, duh.... Mine is at 87mA at the moment....)
Secondly, I will follow this topic closely and help you wherever I can.... Let's fix this!

chareos12 said:
Thanks mate.
Question: have you ever DOWNGRADED a radio ?
If so, did you take any particular precaution ?
Also,
Just to be sure I tried everything possible, before sending my device to repair (risking many days without it, or even they discover my rooting here and there...)
may I ask you HOW do you flash the radio ?
My procedure:
- basic: I rooted via unrevoked 3.21 - all right with root permissions and got ClockWork recovery installed and working
- I (re)boot in Clockwork
- I go to Install zip from sdcard option
- I choose the radio zip file, all downloaded from the xda thread
- I apply and confirm the radio (file name is NOT update.zip ... is this an issue ?)
- phone starts to work. A progress bar apperars, fills only by 1/10th, 1-2 seconds, then suddenly process is complete and asks to reboot from menu. So I press back, and reboot.
- Phone don't reboot. It just sits 15-20 seconds saying "flashing radio" or something, but showing no progress bar. Then phone reboots. Almost immediately, reboots again
- Phone reboots back to os usable state. radio version is changed in system infos.
If I made something wrong, or something is missing or wrong in my procedure, maybe I can still solve all of this
Click to expand...
Click to collapse
I think I always downgraded when trying the new batch of radios But really, yes I have changed version number up and down, and the one I found the best performer was the radio 30_2. But that may only be for me, even though a lot of other users report that it is also good. I did find much higer battery use on the 32.47.00.32U_5.10.05.23 radio, but after returning to 30_2 all was well again.
I would say the way you are doing it would be fine. And no it does not need to be called update.zip. I'm busy right now working, but will check back later if I think of anything extra. ;P

Exactly, CurrentWidget. That also reports the same mA variations as dmesg, so I take as trustable.
Yeah, let's hope it's fixable !
I fear sooo much repairing centers...

I'm no expert but it should be -2mA if in standby with everything off (including the display) and >80mA with display on. >30mA ish drawn is not possible with all hardware off/idle except by the display. That's unless you have the "Android System" bug I had where it consumes 10-30% CPU just resting.
What current discharge reading do you obtain with same everything except display on (black background)?

th3 said:
I'm no expert but it should be -2mA if in standby with everything off (including the display) and >80mA with display on. >30mA ish drawn is not possible with all hardware off/idle except by the display. That's unless you have the "Android System" bug I had where it consumes 10-30% CPU just resting.
What current discharge reading do you obtain with same everything except display on (black background)?
Click to expand...
Click to collapse
Consider that right now I'm on the stock Sense...
disabling everything (any sync/background data), wifi off and then airplane mode on, sensor off, gps off, led notifications disabled, display brightness manually on the exact 50%, black background, ONLY widget across the 7 pages is CurrentWidget - which is also the only installed app... + Estrongs file manager ...
175-185mA.
Which is
your normal 80mA + mine sick 100mA ...
as I said before, it is like the bare phone drains 100mA battery for just staying barely alive.
oh,
12 minutes uptime
Android System is accounted for 17 seconds (4636 menu)
but then, going in settings battery infos, I read
CPU total 49s
CPU foregroung 20s
Android system - usage 70%
Display - 22%
weird...
IF it is the bug you are talking about, how could it survive trough 4 OpenDesire releases and a jump back to RUU ?

The Sense ROM you have is totally default with nothing added except CurrentWidget?
You need to go barebones to figure out what is happening here. The 80-115mA baseline is from many users at 0% brightness on a black background. You need to also log your CPU usage with something like OSMonitor, System Panel or Show CPU Usage to see if Sys, Usr or IO are experiencing abnormal load. In apps like OSMonitor, see the debug errors it is showing you under Messages.
On some ROMs it has been my experience that the cell network, accelerometer and/or touchscreen goes haywire causing large battery drain in idle or use. Consistent network locations and network provider search was a key problem. That made me lose 5-10 hours from my usual battery life. There was no way that I could fix it except changing ROMs and starting from scratch. I reverted back to a clean HTC 2.2 ever since with no such oddities.
----------------------------------------------
- Sent from HTC Desire via Tapatalk -

chareos12 said:
weird...
IF it is the bug you are talking about, how could it survive trough 4 OpenDesire releases and a jump back to RUU ?
Click to expand...
Click to collapse
Admittedly, the existence of it after the change to stock RUU also had me confused. Providing you did complete wipes, that should have wiped out any soft bugs.
----------------------------------------------
- Sent from HTC Desire via Tapatalk -

Related

HTC Desire Reboot Loop Problem

I have an interesting problem, kind of. Bought my phone second hand as supposedly unlocked & debranded but on boot up it after the HTC logo I get the Virgin Media logo, not really an issue though. Anyway the problem is when I switch the phone off and then switch on again it boots up fine to the home screen and then it will reboot itself and carries on doing this. i.e. boot up to home screen then reboot again continuously.
To get out of this reboot loop I have to remove the sim & boot the phone with no sim in it then switch off and insert my normal Vodafone phone sim and switch on again. after that the phone is fine until I power down and then the same thing happens.
Anybody else experienced this or got any ideas?? It came with 1.15.405.4 firmware already installed and I have tried reflashing with the same firmware using the goldcard method & it worked but the problem remains. When the sim registers on the network is when the reboot loop seems to start.
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
TieT said:
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Click to expand...
Click to collapse
Maybe it's a dumb question - But I'm having some issues that doesn't seem to get solved by a factory reset - Would it be an idea to reflash it for this, so the phone gets a fresh rom?
How would I do it specifically? Do you know of a guide somewhere?
sudman said:
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
Click to expand...
Click to collapse
have you tried a different sim card ?
Ye tried a different sim card, boots fine and all is good till you reboot the phone and then the same happens again. Anyways flashing was a disaster this time round as I was doing it on my work pc and Symantec kicked in thinking it found a virus with adb.exe and halted the process & quarrantined the file. Now everytime I try and reflash on a different PC I get the dreaded error(110):file open error. Disconnect the phone & all I get is a black screen & HTC logo. Nice. Thanks Symantec you've just bricked my Desire!!
*UPDATE* - Fixed.
Removed the battery, left it for a few hours then reflashed on a different pc and it flashed fine. Then thought I'd try & repeat so reflashed with the older rom from here (originally used the newer rom posted on Modaco) and got the error again and again couldn't flash back to the newer. Removed the battery left for an hour and then could reflash again and get it working!! Wierd
I had the same problem.
My Solution: remove battery, remove the SIM, put battery reboot, turnoff, remove battery, put SIM, put battery, boot
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
sorry, wrong thread
same here.
Tequila98 said:
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
Click to expand...
Click to collapse
i have the exact same problem!! any solution? after that the phone will boot loop over and over! damn!
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
hmmp
as long as i know, i did not install anything on my phone lately so thats the problem so far and i think tequila98 also having the same problem as me, cause when i remove my sim card the phone works fine. but ive reset my phone yesterday and not restarting so far hope this will continue.
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
jxleung said:
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
Click to expand...
Click to collapse
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Ehsan021 said:
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Click to expand...
Click to collapse
It's probably hardware problem with motherboard. Therefore I recommend you to take your phone to repair center and they should replace mobo with new one. That's what I did and now everything is ok.
I am having the exact same problem. Seems to be related to the SIM.
But the SIM works fine in another phone.
Did anyone find any more information?
If you get random reboots its most likely ther motherboard there is a massive thread about it on the forums. You need to send it off to a HTC repair centre.
Just got this problem.
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Tnx.
R
Edit:
Restored backup and is working fine again.
nandroid backup loop
rottunix said:
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Click to expand...
Click to collapse
I have the same problem.
rottunix said:
Restored backup and is working fine again.
Click to expand...
Click to collapse
I will try it. Maybe the backup is not only a backup but also a remove? Strange.
I will comment if this works also for me.
EDIT: Restore helps

2.29.405.2 update bugfest - any way to roll back?

Did the 2.29.405.2 update OTA initially and noticed problems. So reinstalled it from SD card but no help.
Bought sim free, unbranded/locked and never rooted:
Cannot dial out from phone lists or contacts. Going to phone and clicking on an entry in the call list does not launch phone call any more. Going to contacts, opening one and clicking on an available phone number does not launch phone any more.
The only way I can make a call is to punch it in on the keypad! Grrr.
Wifi connects to my home base after a reboot but, after an undetermined amount of time it drops the connection and cannot get it again. Going to Wifi settings shows it scans, connects and tries to obtain IP address. After a short time it gives up, turns wifi off and starts over. Again & again.
Cannot get it to connect again without another reboot.
This is a crippling loss of functionality for me. Can anyone suggest a way to roll back this update so my phone works as id did?
Many thanks all,
M1
First try a hard rest(you will lose all personal data on the phone,pictures and other stuff on the SD will be fine). If that does not work try either the 2.29.405.2 or 2.10.405.2 RUU.
More info - to my horror, around 15 minutes after I had tried and failed to make calls from contacts the phone started making them one after the other as if they were stuck in a spool or something! Ouch - any thoughts?
Backup everything you can and flash the same ruu from shipped roms.
Sent from my HTC Desire using XDA App
> flash the same ruu from shipped roms
where do I find this? - android noob!
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
And if it works, keep it safe!
Sent from my HTC Desire using XDA App
Thanks to all for help on this. Decided worth a trouble shoot before a hard reset and culprit seems to have been an app - extended controls widget. Removed this and all seems well again.
Try this one. This definately works! i have used it.
http://forum.xda-developers.com/showthread.php?t=768256
I was stuck at 2.29 update.
Then i used this guide and windows tool.
So i did this process and it rolled my phone back to stock android 2.1 rom 1.X
The first version that the phone was bought with.
This tool will boot the phone into bootloader and load a stock 1.x rom ota off the sd card as the tool will extract it to sd card and then load it.
This will wipe all your data not sure about the sd card as i dont remember any of that because i formatted my sd card after i had used the tool.
Thats because i had rooted my phone and tried custom sense hd rom.
The only reason i had was of the battery usage as the consumption was very badly increased and that the 2.29 rom was unstable.
PS: I did first try the htc service in Denmark. They couldn't help me and said i was stuck with the 2.29 rom update. :/
After my phone got rolled/flashed back to stock android 2.1.
The next day in the morning i could upgrade again to android 2.2 rom ver. 2.10 OTA from htc servers.
Maybe this works for you as i did for me and others.
Turns out it wasn't the app.
After a couple of days playing ok my sim free stock htc desire is unstable again.
Cut me off mid call - went to phone and clicked on last call entry - absolutely nothing happened, repeated with same problem. Exited phone to home screen then opened contacts and tried to make call from there - same behavior, a complete hang.
No web access either so opened wifi manager to find it hanging on "obtaining IP address" from my home network and continually shutting down and restarting wifi automatically at this stage.
Noticed general UI lag and several apps failing to open too.
Left phone alone and again, around 10 minutes later all of the actions - including trying to make the phone calls started running one after the other. Like everything had been caught in a spool or something. After this all seemed OK until it happened all over again later.
Although the UI seemed OK and some apps worked as expected, the only way to get phone and wifi working whilst it was hung was a warm boot.
Dreading a hard reset as it's going to waste another day or two getting everything reconfigured just so (can't find a back up solution that does everything - multiple mail account settings etc) but looks like only option.
Will try going back to mikep99's suggested rom as soon as I have time and will not be responding to an HTC OTA auto update offer again.
Grrr.
I still suspect an app conflict.
Can anyone recommend a util that might give me a clue which app / sys process could be hogging system / radio resources?
just got another OTA update pushed to me. installed (nothing to loose) and Congratulations my phone has been updated to 2.29.405.5.
Not sure whats going on here as that was the update I got 2 days ago. This time round it was only 4.8mb download so I'm assuming it's an update update. Hope it fixes things .....

[Q] CM7 Random Reboot and RE Setup Issue

Hi,
I am having a really odd and very frustrating issue with the latest CM7 Stable Build on my device.
I have been using the latest stable since its release back in November.
I ensured a clean wipe and install of CM 7.1.0.1 and setup my phone accordingly and Nandroid Back Up around a Week later as the Device was behaving as intended.
Sadly, I am now plagued with the following issue which occurs without any common trigger....
I will be using the device which will be behaving normally and it will suddenly, normally when screen is off... reboot and enter a Boot Loop (CM7 Robot will either be frozen solid or will keep rebooting to CM7 Robot) which seems to continue until a battery pull.
I will then restart the device and it sometimes boots straight away though sometimes hangs for a while. Once booted it boot to the 'Setup your device' Screen, from which point onwards you are required to Re-Enter your Logins for Google and such like. All settings and sync profiles are normally missing/deleted so requires setting up of all apps requiring logins etc.
As you can imagine, the above is quite an inconvenient as it normally happens when I actually need to use the device
I have tried reinstalling a clean CM7 over the top as well as wiping and formatting the SD card.
Neither seem to have solved the issue.
Any help anyone can give would be greatly appreciated.
It is also worth noting that while the device will charge off USB, it will not allow usb tethering or any form of USB Mounting etc.
Cheers
Jason
Device Spec:
Phone: HTC Wildfire Alpharex S-Off
Android: 2.3.7
OverClocked: 518.4MHz-691.2MHz (SmartAssV2)
VM Heap Size: 24m
ROM: CyanogenMod-7.1.0.1-buzz
Radio: 13.55.55.24H_3.35.20.10
Recovery: ClockworkMod 2.5.0.7
Kernel: 2.6.35.14-nFinity arco(at)tuxbox #1
Custom MTD Partitons using S2E
cm7 issues.
sounds like your in quite a pickle my friend.
i used to get your reboot issues (the bootloops) but that was because my phone was overclocked to over 700. i never got the setup device screen though.
when you say youve tried a clean install over cm7 have you factory reset the device as well as deleteing the dalvik cache??
also my sound stupid but have you tried your backup to see if it starts again??
it sounds like something has became quite corrupted.
have you installed any new apps recently or changed anything in the system files of the phone?
also when you have to go through the set up are all your apps still there afterwards? And when you first flashed it did the tethering work at all?
Heavy_metal_man.
heavy_metal_man said:
when you say youve tried a clean install over cm7 have you factory reset the device as well as deleteing the dalvik cache??
Click to expand...
Click to collapse
Yup
heavy_metal_man said:
also my sound stupid but have you tried your backup to see if it starts again??
it sounds like something has became quite corrupted.
Click to expand...
Click to collapse
Yup and while it does restore to a point where I can use my phone quite quickly after however I'm very cautious after - typically it happens a couple of weeks later
heavy_metal_man said:
have you installed any new apps recently or changed anything in the system files of the phone?
Click to expand...
Click to collapse
No real new recent apps installed and no mods to the system files that I can recall.
heavy_metal_man said:
also when you have to go through the set up are all your apps still there afterwards? And when you first flashed it did the tethering work at all?
Heavy_metal_man.
Click to expand...
Click to collapse
All my apps are still installed but many apps require re-setup or accounts for sync require re-adding. Phonebook requires import of contacts however messages remain in place.
I can't recall I think it did or at least USB-Storage did
Do you have a SD ext partition?
I ask because I had similar problems (randomly losing data) with an ext 4 partition, repartitioning my card using ext 3 solved it, also put your dalvik cache and data back into phone memory if it isn't already as that can also cause instability.
Sent from my HTC Wildfire using xda premium
Try this....
Run an RUU for wildfire.
- Download (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24 _ 3.35.15.19_release_141106_signed) from android forums.
- Connect phone to PC and run RUU
- This downgrads phone OS to eclair (android 2.1)
- Let it do the bizniss
- Re-root with unrevoked 3
- Re-Flash CM7 and gApps
Many thanks Scratch and Arkose,
Since my post last week I have since formatted the SD Card as well as Wiping the Phone as much as possible.
I then flashed and installed the latest CM7 Stable, Radio Package as well as re-setting up the EXT Partition this time as Type 3.
Once up and running I reinstalled all Apps.
Seems to be running okay so far.
Long may it last hopefully.
If not will try last suggesion
Great stuff. Let us know how it goes
Sent from my HTC Wildfire using XDA App
A quick update...
Still having issues
I'm noticing that randomly phone process will crash for no apparent reason/cause, normally when off Wifi and on Mobile Data.
Last night was the worst its even been though... at a critical moment when I needed the phone to work... it decided it was having none of it.
Phone kept switching Airplane Mode On and Off causing process.android.com to crash along with most other services So I rebooted only to find that it now was either stuck in Airplane Mode or couldnt enable to Radio (No Phone Signal at all) so I did a battery pull while trying to walk home in the pitch black and rebooted.
The Saga continued even after a battery pull, I eventually as I got in the door was able to use the 'Torch' and recieve a phonecall before all the processes crashed once more...
So I did a battery pull, left the phone for five mins and rebooted. All was well for a while, enabled Wifi, phone seemed happy.
Had to reboot a short while ago, after recieiving a phonecall and text.... grrr... anyone have any suggestions?
I had problem with process restarting. Adw launcher process I downloaded Go Launcher ex I have no problems now.
Sent from my HTC Wildfire using Tapatalk

[Q] WiFi is draining the battery. Please help!

Hello dear WFS users,
I'm facing a very annoying and unpleasant problem on my Wildfire S sinse I have unlocked the Bootloader via HTC Dev.
The WiFi antenna sucks the life out of my Marvel's battery (I'm pretty sure this is the reason for the battery drain). I have made numerous factory resets, but non of my attempts to fix this actually work. For now I keep my device in a very "factory" state, without any 3rd party apps installed, without root and without a custom recovery. Yet, my battery can hold on for up to 10 hours of NO custom usage when WiFi is on. When Wifi is off, everything is ok. I check the battery stats in Settings -> About phone on a regular basis and every time they show one and the same thing: the phone just won't go in sleep mode while WiFi is on. Now, I have read about such problems with some extra apps, but all I have installed on the phone are the latest versions of the default apps (Gmail, Facebook, Maps, new Google Search, Market, Youtube). I use no widgets, except for the HTC Clock+Weather; I have deleted all Sync accounts, except Gmail. They have never created any problems, anyway. Just for reference, I haven't messed with my WiFi router/connection.
So please help me, what could be the issue here? What is keeping the WiFi on to drain the battery even when the phone should sleep? And how to fix this? I have Europe Marvel (RUU 2.13.401.2) with unlocked bootloader (1.08.0099) - it says "unlocked" on the top and all... Should I maybe reinstall the 2.3.5 RUU, or the bootloader unlocking .exe? Please, it's very urgent! Thanks in advance!
vctrdnl said:
Hello dear WFS users,
I'm facing a very annoying and unpleasant problem on my Wildfire S sinse I have unlocked the Bootloader via HTC Dev.
The WiFi antenna sucks the life out of my Marvel's battery (I'm pretty sure this is the reason for the battery drain). I have made numerous factory resets, but non of my attempts to fix this actually work. For now I keep my device in a very "factory" state, without any 3rd party apps installed, without root and without a custom recovery. Yet, my battery can hold on for up to 10 hours of NO custom usage when WiFi is on. When Wifi is off, everything is ok. I check the battery stats in Settings -> About phone on a regular basis and every time they show one and the same thing: the phone just won't go in sleep mode while WiFi is on. Now, I have read about such problems with some extra apps, but all I have installed on the phone are the latest versions of the default apps (Gmail, Facebook, Maps, new Google Search, Market, Youtube). I use no widgets, except for the HTC Clock+Weather; I have deleted all Sync accounts, except Gmail. They have never created any problems, anyway. Just for reference, I haven't messed with my WiFi router/connection.
So please help me, what could be the issue here? What is keeping the WiFi on to drain the battery even when the phone should sleep? And how to fix this? I have Europe Marvel (RUU 2.13.401.2) with unlocked bootloader (1.08.0099) - it says "unlocked" on the top and all... Should I maybe reinstall the 2.3.5 RUU, or the bootloader unlocking .exe? Please, it's very urgent! Thanks in advance!
Click to expand...
Click to collapse
What radio version?
You mean the baseband, right? It's 47.23a.35.3035H_7.53.39.03M, the default one which came with Android 2.3.5, I believe. You'd need S-Off to change radio, right? Anyway, I'm S-On with unlocked bootloader. Just before unlocking the da*n thing I had no problems whatsoever.
Edit: I run the stock ROM and Kernel, too. Very peculiar issue...
vctrdnl said:
You mean the baseband, right? It's 47.23a.35.3035H_7.53.39.03M, the default one which came with Android 2.3.5, I believe. You'd need S-Off to change radio, right? Anyway, I'm S-On with unlocked bootloader. Just before unlocking the da*n thing I had no problems whatsoever.
Edit: I run the stock ROM and Kernel, too. Very peculiar issue...
Click to expand...
Click to collapse
radio version, 5th line:
radio
RADIO-7.53.39.03M
I haven't messed with it in any way...
Why dony you try some app like juice defender and set it to turn off wifi when you want... But thats not a solution... Maybe before flashing anything, contact htcdev.. In last case you should flash some sense rom, since i see you want all stock..
Sent from my HTC Wildfire using xda premium
Thanks for your suggestions, b02. Although I like Sense I'm not a Sense-freak and I'm willing to try various ROMs. But at this point I don't want to flash anything new because I have to find out the real reason standing behind this WiFi issue. I have to be sure there is no hardware problem (fingers crossed). Juice Defender would be just a workaround and not a resolution of the problem, too.
So, I have dug extensively in the Settings menu and I found something I didn't even know it was there before.
In Settings > Wireless & networks > Wi-Fi settings I press the Menu button and two further options appear in the bottom of the screen: Scan and Advanced. Next, I press Advanced and the first option to be seen here is Wi-Fi sleep policy. It gives me 3 further options: After 15 minutes, Never when plugged in, Never, which obviously determine if/when the WiFi should go to sleep. By default (after numerous Factory resets and after I discovered this thing ) the selected option was Never, so I changed it to After 15 minutes.
Now, this change has worked for me, at least partially. The huge battery drain on standby has stopped for now. Yet, I'm not sure this has been the originally selected option before I encountered this issue. Could someone please check this for me? What is the selected option by default for him/her in this menu?
Only in this way I could be entirely sure whether I have found the solution or just a workaround. For now, WiFi needs 1-2 seconds to turn on when I bring the device out of Sleep mode. I have to say I don't remember such a behaviour before so I'm not sure what I have actually accomplished. Furthermore, I think the battery drain is still too big when I just browse the menu and the settings (with WiFi on). Something seems to operate in the shadows or whatever else...
Please help! Thanks a million!
So it turns out there was some error, which occured when I unlocked the bootloader of the phone. It was preventing WiFi from sleep and therefore draining the battery. I went to a friend to perform S-Off for me. Then he installed the Stock 2.3.3 ROM + Hboot 0.90.0000 + the respective radio (7.46.something) on the top (he had this ROM version in his computer). So now my phone is OK. The bootloader info states the phone is S-Off; the "***Unlocked***" signature is gone.
I have a couple of questions:
1. Is it safe to perform an OTA Update to 2.3.5 when S-Off? An update invitation has already appeared in the notification bar.
2. I intend to try m1ndh4x8r's ROM out. Do I need to flash the 2.3.5 official ROM before that at all?
vctrdnl said:
So it turns out there was some error, which occured when I unlocked the bootloader of the phone. It was preventing WiFi from sleep and therefore draining the battery. I went to a friend to perform S-Off for me. Then he installed the Stock 2.3.3 ROM + Hboot 0.90.0000 + the respective radio (7.46.something) on the top (he had this ROM version in his computer). So now my phone is OK. The bootloader info states the phone is S-Off; the "***Unlocked***" signature is gone.
I have a couple of questions:
1. Is it safe to perform an OTA Update to 2.3.5 when S-Off? An update invitation has already appeared in the notification bar.
2. I intend to try m1ndh4x8r's ROM out. Do I need to flash the 2.3.5 official ROM before that at all?
Click to expand...
Click to collapse
about first id, since now you are unlocked, why do u care for that update.
as for second u dont need anything but to flash recovery, and rom u are willing to install...
have in mind that u need to clean cache,dalvik and factory reset, and you will need to install google apps in order to have martket gmail and so on ...
good luck

[Q] Debug Battery Drain - com.android.systemui

Hi,
I'm using s4 mini LTE I9195 with CM11 M6, f4ktion 1.4.0 kernel, BN3 modem, TWRP 2.7 recovery
All was working fine, average battery drain on idle was 1%-2% (not great, but fine), and suddenly it rocketed to drain 15%-30% per hour.
I usually use Android Tuner's battery measure stats to track drain statistics over time.
After checking it, I"ve noticed that it () the drain) started in the middle of the night.
So it's not due to "I launched this App, and then..." It just went nuts on it's own...
I've checked which process is to blame and the first one with max battery consumption is:
com.android.systemui (with KitKat logo) followed by Android System, then Screen, and then all the usuals.
I tried to do reboots, disable wifi/nfc/rotation/data/sync/anything else/kill user apps - no effect ...
It still drains about 20% per hour on system and systemui for the whole day now :crying:
And I have no idea what causing it / how to revert it...
So, do you have any suggestions on how to trace this bug?
What to search for in logs?
Any thing else?
I'm not a big pro on android OS subsystem, so advises are welcomed!
I'd love to help, but I actually stumbled upon this thread while googling to help myself
I'm using Note 2 (N7100), running CM11 - newest nightly (although I flashed it today, after slightly recharging the battery once I noticed the problem) and Devil3 kernel.
I'm having the same issue - yesterday everything was fine, I've left the phone to charge over night and display time as usual and in the morning nothing seemed out of the ordinary, until 6 hours later. After those 6 hours my battery was fully depleted (whereas normally lasts whole day and is not even close to being depleted). com.android.systemui and Android System seem to be the problem for me too.
I've also tried turning off some functions, uninstalling some apps, turning off notification privileges for others. Even, as said earlier, flashed newest nightly. Nothing helped. Using phone with without flashing Devil3 kernel didn't help.
Anyone have any ideas?
Just try to flash stock software and again CM.
Try a older version of CM11, and if stability is a priorty stay on CM 10.2
OK, so I've tried a few things, and had a few surprising outcomes:
I've analyzed the CPU load with various tools, as Android Tuner, OS Monitor, and All-In-One Toolbox.
Most of them reported Android System using 30% CPU, and com.android.systemui using 25% CPU, all on the highest frequency.
But All-In-One Toolbox recognized top process instead of Android System as Lockscreen android process, so maybe there is a hint there...
(and I don't use any custom lockscreen stuff beyond stock CM's one)
So, backed up the current troublesome system (let's call it BKP_NEW), just in case, and decided to restore a full NANDroid backup I had from a week ago (and the issue is just from yesterday).
Restored all 6 partitions (/system, /boot, /cache, /efs, /modem, /data), rebooted, and....
...The issue was still present! Crazy battery drain just as before!
Very confusing... Then I went for a factory reset - it fixed the issue, but I have to start from scratch with all the SW installs and config, and I don't have a week to waste setting everything up again, and potentially running into the same issue some time later.
So, I've decided to move further back, and restored a two week old NANDroid backup > reboot > No issue presents
But it was just too weird, since the delta between 1-week old and 2-week old backup is infinitesimal.
So, out of curiosity I've decided to restore the BKP_NEW (the one of the system with the issue present)... and after the restore it works just fine! (WTF?!?!)
After thinking on it for a while, my conclusion is that there was some problem with some part of system that was wiped/fixed in TWRP's Factory Reset, but is not touched/overwritten during the NANDroid 6-partition restore.
But again, this is just my assumption, need someone more knowledgeable to confirm this possibility...
(maybe @ne0zone75 can advice on this?)
Since that, all is working fine (at least so far).
And if my assumptions are correct, @Ksenios, you can try to do this, and still have working system with all apps and configs (If youre comfortable with recovery / backups management).
hi,
(passing bye from google - just a note)
com.android.systemui cpu high usage (about 37%),
on my huawei media pad x2 (gem702l) but only while charging (and just sometimes), if that gives something for someone, any clues why ?

Categories

Resources