issue when power saving mode + screen turned on - One (M9) Q&A, Help & Troubleshooting

Hi everyone,
since I updated to 2.10 software version, I have a recurring bug...
When I activate power saving mode, every time when I turn screen on the GPS icon appears and seems to be trying to locate the phone, although I have GPS deactivated and location settings set to power saving at all times.
I've tried it with many custom ROMs, stock and elementalx kernel, but it's still there. Is this a bug from HTC ? Haven't found anything regarding this on the forum.
thanks!

nuts77 said:
Hi everyone,
since I updated to 2.10 software version, I have a recurring bug...
When I activate power saving mode, every time when I turn screen on the GPS icon appears and seems to be trying to locate the phone, although I have GPS deactivated and location settings set to power saving at all times.
I've tried it with many custom ROMs, stock and elementalx kernel, but it's still there. Is this a bug from HTC ? Haven't found anything regarding this on the forum.
thanks!
Click to expand...
Click to collapse
I have no problems. You problem seems to be because of some app you have installed. Did you try to check after a full wipe without any apps installed or without restoring any backups?

thanks for your answer. Nope, haven't tested after a factory reset but I will try if I can't find any explaination... TBH, I thought as long as GPS is off (when location settings are set to battery saving) no app was allowed to use it. So if one of them does it anyway, I have to find out which one! Is it more likely to be an app with root access ?

Related

[Q] 100mA battery drain while on STANDBY !! ARGH !!

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 -

Bluetooth not turning off...

Hi team...
hit a problem with my evo.. and its frustrating the h$ll out of me..
Bluetooth is coming on "on boot"...
Running rooted stock Sence with plenty of programs in it..
As usual with things new.. tried a heap then yanked plenty out and now down to the basic's.. Running juice defender and Battery saver plus battery Indicator..
K.. as indicated bluetooth is turning itself on on boot and the only way I can turn it off is to go in to "Airplane mode.."
It seems to turn it off.. well it shows turned off...
Note: it wont turn off via a widget and or in the settings.. as when you hit that button it will "grey out" and show.. "turning off" but seems to hang in this mode..
I checked with Battery Indicator and it shows that bluetooth has been using 23% of the battery today... now thats a fair chunk in anyones terms.. considering how much effort we put in to extending the batts life..
O I do run with a extended batt..
ok.. to my way of thinking.. either I got a bug in the system and or its going like something in this thread from years ago on another pc of hardware...
http://forum.xda-developers.com/showthread.php?t=227706
K.. what I would love to do is freeze all bluetooth programs and triggers..
so... i kinda need a list to know which ones to freeze and work backwards from there.. (I got all the tools to do this and as said are "rooted")
Bluetooth.apk?
BrcmBluetoothservices.apk?
or.. is there a "hard" shut down I can do?
any help would be great and I am sure someone has had this problem before.. but at this stage over the last week.. Google it and going through threads has not yielded a fix as yet..
few specs on the software..
Firmware : 2.1 update 1
Baseband version : 2.15.00.07.99
Kernel: 2.6.29-789bf291
Build number: [email protected] test2 (really.. whats this?)
Software number: 1.47.706.1
PRL Version : 1.71_003
PRL version: 00202
Thanks in advance..
Did you ever resolve this issue? I'm now having this same exact issue.
fbazaldua said:
Did you ever resolve this issue? I'm now having this same exact issue.
Click to expand...
Click to collapse
No.. not yet..
As said I have to use the Airplane mode to shut it off... but it still shows up in Batt usage as draining .. so I say its not fully off..
I am wondering if it is a "radio" problem and or some pc of software is calling it on boot..?
anyone else get this problem?
You should be able to freeze both Bluetooth.apk, and BrcmBluetoothservices.apk. That'll stop it for sure, it can be done with titanium backup. Also you can try flashing the radio, and I also assume you have tried rebooting?
I have tried re-booting and it still comes on. I've turned off the phone completely and re-started and it still comes on upon booting up.
I rooted my phone a month ago without any problems. I also installed myn's Warm 2.2 (RLS5) without any problems. Nothing has changed since then. Then just last week my spouse noticed the bluetooth on her phone on boot up. Since yesterday this has also started to happen on my phone as well. All of a sudden this has started to happen on our phones for no apparent reason. Any help would be greatly appreciated.
Have you tried freezing the app in titanium backup?
No I haven't tried freezing the apks in Titanium Backup, but why should I? I want to find out what's causing this so that maybe it can be fixed instead of just turning it off.
Also, I'm already running the latest radios. I didn't have to "update" to the latest radios for myn's because I was already running the latest radios mentioned. Why would I need to re-flash the radios? Since November when we purchased our phones, and for the last month since rooting we've had absolutely no problems with our phones.
Are you running any programs like juice defender or anything? Because it is indeed off for bluetooth to start acting possessed.
No sir. I don't use Juice Defender, task killers, or any custom kernel. All the apks I have I've downloaded since rooting. Like I mentioned, nothing's changed. Just too weird and very frustrating.
Lawlz, no need for sir..., but have you tried re-flashing the rom lately?
No I have not tried re-flashing the ROM, but why would I if I haven't had any problems until now? What would have caused it to become "corrupted" or problematic so as to cause the bluetooth to come on during boot up?
If I can't find a solution within the next couple of days I guess I'll re-flash the myn's ROM. However, I prefer to find the solution to what's causing the problem. I just don't want to continue re-flashing radios, ROM, etc. every time this happens.
Well I don't know exactly what caused it, and it could just be a random bug. Though re-flashing can solve it, and it might not happen again.
If it helps, my signature is below with the setup I'm running. Maybe something isn't "compatible" and it's just manifesting itself now. Nevertheless, I will more than likely just re-flash the ROM if the problem persists. Thanks for your responses. I will update in a couple of days.
Well I was just about to go into Titanium Backup and turn off the bluetooth apks when I noticed it's not listing any of my apps under Backup/Restore!! I've gone to Menu > Setting > Applications > Manage Applications > Titanium Backup and I've cleared data and cache. Forced stopped it, uninstalled, and then re-booted. I then re-installed, downloaded BusyBox, and still my apps won't show up. I wonder if this is part of my problem with Bluetooth turning on at bootup, but now how do I fix TB?
I am having the same problem with mikfroyo 4.5 randomly now also . I went into titanium backup pro and froze the brc Bluetooth file and some Bluetooth widget but didn't see a .apk to freeze mine has used 18% ugh
I was able to fix the bluetooth not turning off problem by clearing data/cache/dalvik and then restoring to my latest backup before I started having problems. I am happy to report that this solved the problem for me without having to re-flash the ROM again. I don't know what might have messed up the bluetooth, but I'm glad it's fixed. I hope this works for anybody else having the same problem.
As for TB it was showing 0 elements in Backup/Restore. I went to Menu > Filters > Clear > Apply, and then closed TB. Next, I went to Astro > sdcard > Titanium Backup folder > Edit > Select All > Delete. After I deleted all the files in that folder I closed Astro and then went back to TB > Backup/Restore and all my apps were there again, even all the frozen ones. For safe measure I froze the bluetooth apps mentioned above, and then I proceeded to perform another batch backup of all my apps and data again.
Thanks for replies crew..i will play around with it the next few days and report back..its been frustrating me for months and as you can see by the time date on the first post i had thought i had something wrong with the phone..
Sent from my HTC evo

My home button is not functioning.

Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
I'm running CM 6.1.1 Stable on my G2 (just a couple weeks old) and I've noticed that my home button doesn't work sometimes. It works about 95% of the time, but then it will do the occasional hiccup where nothing happens. If I touch it a few more times it will eventually start working again. Not sure what it is, but I read in another thread here that it could have something to do with how the CM ROM is configured for capacitive touchscreen sensitivity. And I believe I read that this has only been reported in CM and not other ROMs.
dutman said:
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Does it completely not working??, delayed maybe??
Sent from my HTC Vision using XDA App
Had this issue yesterday. I did a factory wipe from Clockwork and reflashed CM. Fixed it.
even iam facing the problem, but i guess mine is worst as the all(4) softkeys doesn't respond, but when i press it, i receive the feedback i.e it vibrates.
2nd issue: my physical keyboard layout is pretty much messed up, the symbol key which i press on my keyboard doesn't display the exact symbol
it would be kind if someone offer some solution for this
Rom: CM 6.1.1 (even tried nightly build #85)
Build: HK
P.S: i never had those problems in the stock rom
I'm having the same problem with CM6.1.1. I noticed it after installing Twidroyd app. I couldn't exit it via the home button...had to back all the way out. Uninstalled and still having the problem. Doesn't seem to be working at all now.
I had this sort of problem with my G1, I flashed the BiffMod ROM and some day, the phone just randomly did a factory reset, the background is set to how it was when I first flashed it and the home screen was back to normal like how it was when I first flashed it. My home button would not work, when I pushed the end call button to put the phone in sleep mode, it would turn off but if I were to press it again,the screen would turn on but it didn't go to the lock screen it just turned on. To fix it I went into recovery and wiped all five(I'm using Amon_Ra's recovery on it) then I booted back up and my home button worked again and when I put the phone to sleep, it turned back on like normal with the lock screen. That has happened a few times, some times when I did the wipe, every thing would start working again and my home screen still had everything placed where it is suppose to be. You could try to wipe everything, but I can't guaranty it because I don't even have my G2 yet so this has never happened to me on a G2.
i wiped everything data / cache ,flashed GingerVillain 1.4 , the softkeys won't work even in this rom, the only place where softkeys work is HTC's Stock rom. iam just wondering is it due to my build, as its Hong Kong build, so there is a possibility that the keymap for softkeys are different?
Update: Fixed! http://forum.xda-developers.com/showpost.php?p=9353194&postcount=1

Power menu issue DHD runnin ARHD 6.1

Hi all,
i've been using ARHD Roms since a few months and never had any serious issues with that (except proximity sensor fail ..) but now i'am a bit clueless.
Since flashing ARHD 6.1 (using SuperWipe first, no other Mods, everything was fine after flashing) and using it a few days i noticed two things:
First: Random Force close of different apps. I saw that even SuperUser app does FC every single time. Cleared cache - fine.
Second: I noticed that i somehow pressed 2 or more keys at the same time (i can reproduce it now - hold "power" button and shortpress "home"-button) and did a "screenshot" out of the box (in the ARHD FAQ-Thread is an info which says it does not work without modifications/3rd party tools) and - now it comes - ecaxtly since this day my power menu doesn't work anymore.
Long-pressing doesnt work, i can even hold it for 20 seconds and nothing happens until i stop pressing, then the screen goes off but no power menu appears - so the hardware of the button is fine, i still can power on the phone as well
Tried rebooting several times, even flashed ARHD 6.1 again (checksum is fine) but the issue still exists... everytime i'd like to reboot i need to use rom manager and boot in recovery or remove battery.
Is this a known bug? found nothing via search function :/
You can try this post:
http://forum.xda-developers.com/showpost.php?p=17623012&postcount=51332
Thanks, enabling the Secure Credentials fixed the problem. Unfortunately only until reboot, then the box isn't ticked anymore and i've to enable it again - but thanks anyway, i can live with that for now.
Strange issue ... i wondered why not more useres experiencing it, my phone is "stock" arhd 6.1 without any mods or somehting like that ...
I can confirm that his happends to me alot too.
On the same rom.
Still no solutions other than Secure credentials?
Same situation here. Although I update to 6.1.5 the problem still happens. Any idea rather than secure credential ?

[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

Categories

Resources