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
Related
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 -
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 .....
Hello everyone,
I've been a lurker here for a bit. Some time ago I used Unrevoked, did something wrong installing the original FroYo update and screwed up my phone. I migrated to the DX in the meantime, but this weekend I wanted to return to the Inc. I successfully revived it after a lot of trial and error.
Now my issue: I have tried several ROMs including SkyRaider and Cyanogen, but my location service is not working. Not in Google maps, search, not for weather widgets, nothing.
I'm not sure if this is related, but I have tried a few different radios thinking that could be the issue, but its not. Also, I can only seem to get a working earpiece with the V1 radios.
Any ideas on how to get my Inc fully functional again?
Thanks.
Try the latest RUU. Short of a brick or hardware problem, that will fix anything.
Search for Bezerker7 and Ultimate get back to stock thread, that'll explain how to flash the RUU and get back to stock, see if location services work on stock 2.2 unrooted, and then you can re-root and flash ROMs.
EDIT: Here's the link.
I'm assuming that this phone is not activated as you have the DX? If its not activated and on the Verizon network then it can only get a location through GPS which may or may not be turned on. I would check to make sure your GPS is turned on in the settings, or use a toggle widget, and then try Google Maps again. I also think the weather widgets don't use GPS as the default and that may have to be set in their settings too. They get their location information from the carrier.
pianoplayer said:
Try the latest RUU. Short of a brick or hardware problem, that will fix anything.
Click to expand...
Click to collapse
RMarkwald said:
Search for Bezerker7 and Ultimate get back to stock thread, that'll explain how to flash the RUU and get back to stock, see if location services work on stock 2.2 unrooted, and then you can re-root and flash ROMs.
EDIT: Here's the link.
Click to expand...
Click to collapse
Thanks guys, this worked! Any clue why it happened in the first place?
If you didn't wipe data, then all sorts of crap will happen. You're lucky if you don't bootloop. I bootlooped even when I flashed the same rom and same version over again and didn't wipe data. So maybe it wasn't that.
Maybe it was just something left over, CWM not wiping or something like that.
I really hope it wasn't a hardware defect that subsided for a while
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
time_lord2004 said:
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
Click to expand...
Click to collapse
Simply installing a custom ROM will not affect the radio partition.
Why not try a RUU to return to full stock. Find one for your phone and run that. If it still doesn't work then it's a hardware problem.
Ok, so I replaced the current 2.41.401.41 (August) ROM with the earlier 2.41.401.4 (January) in the hope that a ROM change might reset the cellular radio. It didn't. 'Turn on radio' still does not respond either.
I did this with the bootloader onlocked, but S-ON. I think my very last attempt to fix this could be to set S-OFF, in the hope that some tool might be able to access the radio partition and re-write it or reset it or something. (This is still in the slim chance that this fault really is in software and not hardware!)
Are there any xda tools that write to or reset the radio partition (when S-OFF is set)?
What the...?!!?? So I thought as one last go at this (unless someone had comments re the S-OFF/radio partition idea), I'd let the phone get the OTA update back to the latest OS. So first I executed 'fastboot oem lock'. That of course erased device and reset it again. Radio still not working, no surprise.
After that, restarted in bootloader mode to confirm it says 'relocked', then rebooted normally... and I've started receiving missed txts! WTF.
So with enough restarts/resets, it's fixed itself? Faulty hardware, yeah right. Unless it is on the turn and happens again. [Edit: Yes it has, damn.]
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
I got this disease a week ago, tried to restart, didn't help. Been tapping airplane mode like million times, nothing. Found this thread, followed your instructions guys.
time_lord2004 said:
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
Click to expand...
Click to collapse
Didn't work for me :/ moved on to zachariah's solution...
zachariah109 said:
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
Click to expand...
Click to collapse
Yes, IT WORKED.
Don't get me wrong, this is not the end.
Today. Radio doesn't work again. 5min off doesn't help anymore, unlocking-relocking bootloader ain't do **** too.
If you find any other action sequence which "fixes" radio, please share.
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
lightweaponx said:
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
Click to expand...
Click to collapse
Today I ran RUU. It didn't fix radio. Problem must be somewhere out of radio/system partitions range.
Well, I thought I'd do one final(?) post regarding this issue. I'm starting to concede that I might have a hardware fault, but it's taken a while to accept this.
About 2 weeks ago I started having problems with the 'swipe-down' at the top of the screen to look at notifications and settings (and it started responding badly in the camera app). Then it stopped responding completely... work-around was to use an 'open notifications' app.
However, I tried out 'Apex Launcher' as an alternative to the Sense interface, and swipe-down worked perfectly ok, so isn't the hardware ok? Isn't it a software issue? However, swipe-down had completely stopped working in the camera app by then (using a different camera app is acceptable work-around).
Roll forward to a couple of nights ago, I got notification and updated to android 8/Oreo, what have I got to lose! After the update completed, I can now swipe-down ok again on the home screen! But still not in the default camera app! So have I got a hardware problem or not...
But the big thing, and the biggest headache... once again after the big update (to Oreo) and reboot - once again the cellular radio was not working. I tried all my tricks of the past, nothing would make it go. A factory reset (to Oreo, not an old RUU), unlock and relock (which does a factory reset), nothing worked. Brought up phone info via *#*#4636#*#* and this seems to have had a make-over. There is now a button for 'mobile radio power' (must be a replacement for the 'turn on radio' option) which was showing as off. Turning it on seemed to do nothing (leaving it for a while and then waiting for screen refresh, this button would display as off again).
I'd probably rebooted, shutdown/gone into bootloader at least 2 dozen times, tried all combinations of everything I could think of and could not get it to wake up. At lunchtime today I was leaving the office, booting up my phone one last time and said to a workmate 'going to a shop to look at new phones'. 30 seconds later I look down at my screen... what the *(&$%*&!! I have a signal! Missed txts are coming in!
I know that now that the cellular radio is on, it'll keep running. It always has through this whole ordeal. It's just a matter of getting it to turn on in the first place, or starting after a reboot.
The fact that after installing Oreo the swipe-down works nicely (except for the default camera), and the cellular stuff works fine, once it is on, it really is difficult to conclude whether these are all software or hardware issues. But the reluctance of the system to turn on the cellular radio might be the biggest damning factor to point to it being dodgy hardware.
So the key is not to have to reboot ever again, or at least until the next flagship is out! I still have faith in the HTC stuff, but this has been frustrating...
Hope this helps someone out there!
So i've opened mine up - was due for a screen replacement anyway - tada bad contacts to the radio module (dry solder joint) physically pressed the radio module and it turned straight on. *i've added some paper layers underneath to keep *merckanikal* pressure on it (easier fix than reflowing) and now i know where it chip is i can press on the screen to add a little more if it doesn't work
It really ****ed me today however(seemed to cause phone to bsod, then reboot without radio) and the reason i've spent the last 3 hours replacing the screen and ****ing with the radio.
(whole day of work lost thanks to it. won't see that time back)
In other news i went and tested the note 8's spen - and i think i'm retiring the 10 this week. althought i've just fixed it shes' let me down for the last time.
The only negative i've gotten from the mechanical pressure is the lcd is showing a slight tinge of red now that the glue has hardened. and theirs pressure on the back of the screen. i used 4 layers of 80gsm paper (folded) to pack it out. i'm hoping as the phone heats and moves the paper will compact slightly more and the red blub on the screen will dissipate entirely -
- restarted over a dozen times to confirm the fix is atleast working for me. bootloader'd recoveried etc.. hasn't disabled the radio since..
Hope this helps for any of you still hanging onto the htc10.. (the pixel2's daddy, seriously just feels like the exact same phone*thats what she said?*)
time_lord2004 said:
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
Click to expand...
Click to collapse
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Dissmeister said:
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Click to expand...
Click to collapse
Did It Really Works
Adeel Ali said:
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Did It Really Works
Click to expand...
Click to collapse
Yes it works.
yldlj said:
Yes it works.
Click to expand...
Click to collapse
Brother Did U Tried It U Also Have HTC 10
Adeel Ali said:
Brother Did U Tried It U Also Have HTC 10
Click to expand...
Click to collapse
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
yldlj said:
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
Click to expand...
Click to collapse
Yes I Went From Oreo To Nougat Once
Adeel Ali said:
Yes I Went From Oreo To Nougat Once
Click to expand...
Click to collapse
Then erase persist. Or get back on oreo
RUU worked for me