Related
I have a GPS problem, and despite reading a number of the threads in the forum and trying the usual fixes (downloading GPS Status, clearing downloaded data, re-downloading A-GPS data, factory reset, upgrading to 2.3.3 etc...) I still figure out what's wrong.
Symptoms are:
I do have a GPS icon in the task bar in the apps where I would expect it appear
I never get a lock
Both GPS Status and GPS Test seem to indicate I have *no* signal from any sats
I am outside when I try this
aLogcat seesm to show no NMEA data, though I've never read a logcat entry for working GPS, so I'm guessing a bit here. It does show GPS start up and shutdown lines however
It didn't work in 1.84, when I downgraded, and it still doesn't work in 2.3.3 - seems to be version independant!
Does anyone have any bright ideas? It's really irritating. As a side note, the phone isn't rooted (as I forgot to S-off when I upgraded to 2.3.3) though it could be downgraded fairly easily if there was a good reason to do it...
Thanks!
If it has never worked and you have wiped the device, re-installed etc....
Then I would guess that it may be a defective unit...
markya23 said:
I have a GPS problem, and despite reading a number of the threads in the forum and trying the usual fixes (downloading GPS Status, clearing downloaded data, re-downloading A-GPS data, factory reset, upgrading to 2.3.3 etc...) I still figure out what's wrong.
Symptoms are:
I do have a GPS icon in the task bar in the apps where I would expect it appear
I never get a lock
Both GPS Status and GPS Test seem to indicate I have *no* signal from any sats
I am outside when I try this
aLogcat seesm to show no NMEA data, though I've never read a logcat entry for working GPS, so I'm guessing a bit here. It does show GPS start up and shutdown lines however
It didn't work in 1.84, when I downgraded, and it still doesn't work in 2.3.3 - seems to be version independant!
Does anyone have any bright ideas? It's really irritating. As a side note, the phone isn't rooted (as I forgot to S-off when I upgraded to 2.3.3) though it could be downgraded fairly easily if there was a good reason to do it...
Thanks!
Click to expand...
Click to collapse
1. are you running custom roms? if so which?
2. have you updated your radio and made sure that the RIL is matching?
goofylad said:
1. are you running custom roms? if so which?
2. have you updated your radio and made sure that the RIL is matching?
Click to expand...
Click to collapse
1. Nope. The stock 2.3.3 RUU and before that the UK T-Mobile Stock 1.84 ROM.
2. Stock only, so standard RIL.
shaithis said:
If it has never worked and you have wiped the device, re-installed etc....
Then I would guess that it may be a defective unit...
Click to expand...
Click to collapse
That is my fear. It did work when I first got it, but it now doesn't on any ROM. Unfortunately I can't quite work out what changed...
If this is the problem, does anyone know a way to get back on the T-Mobile official ROM so i can take it back to the shop?
Hi there, Your best bet would be to try and downgrade, root and flash a matched ROM, RIL & radio to retest. This happened to me a while back and this was the only thing that sorted it. CoreDroid has been particularly good for GPS on my DHD, hope this helps
rory1980 said:
Hi there, Your best bet would be to try and downgrade, root and flash a matched ROM, RIL & radio to retest. This happened to me a while back and this was the only thing that sorted it. CoreDroid has been particularly good for GPS on my DHD, hope this helps
Click to expand...
Click to collapse
Yeah - I tried the Coredroid rom - no dice. Think that confirms it's hardware. Back to stock and then back to the shop for this one.
I heard rumours that early DHDs were flaky for GPS. Guess that confirms it for me...
Had exactly the same problem with mine after using the gingerbread ROM from here http://forum.xda-developers.com/showthread.php?t=1056329
Are there different versions for different countries? Maybe this only works in the US or something? I'm guessing here!
Are there different stock ROMS for different countries/ networks? I didn't write down the version numbers before updating
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
Hey!
I looked everywhere to find a solution to my GPS that's not working and ended up with this thread, where crypted offers a scripted solution, including the agps solution, using the NTP servers.
I selected the Google Build and after a Restart, the GPS locked and I was happy!
But unfortunately, it locked 260km away from my position :-/
I know that some users already experienced similar problems, but I couldn't find any solution yet.
Did I miss something?
try reading this :
http://forum.xda-developers.com/showthread.php?t=1447593
and also try this one :
http://forum.xda-developers.com/showthread.php?t=1392466
b02 said:
try reading this :
http://forum.xda-developers.com/showthread.php?t=1447593
and also try this one :
http://forum.xda-developers.com/showthread.php?t=1392466
Click to expand...
Click to collapse
Hey!
These are two of the solutions I tried, first the scripted one (I actually wanted to post this link but I accidentally took an other ^^) and then the other one.
There was no change, I also think, that both describe a similar way to solve it.
Right now, I saw, that there are two gps.conf files, one in /etc/gps.conf and one in /system/etc/gps.conf, but I don't think that this is the problem..
BTW: Heres the GPS Status - there are no Satellites showing up, is this normal?
Saftpackl said:
Hey!
These are two of the solutions I tried, first the scripted one (I actually wanted to post this link but I accidentally took an other ^^) and then the other one.
There was no change, I also think, that both describe a similar way to solve it.
Right now, I saw, that there are two gps.conf files, one in /etc/gps.conf and one in /system/etc/gps.conf, but I don't think that this is the problem..
BTW: Heres the GPS Status - there are no Satellites showing up, is this normal?
Click to expand...
Click to collapse
well, try with this too :
4. This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
9. CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
11. Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
the 11 one may get it to work ... ?
b02 said:
well, try with this too :
4. This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
9. CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
11. Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
the 11 one may get it to work ... ?
Click to expand...
Click to collapse
I tried that already (also tried different config layouts), but unfortunately, it changed nothing.
Isn't the aGPS just for finding the nearest satellites faster? So, it seems, that aGPS is finding the wrong position (maybe because of some NTP servers?) and that the normal gps still isn't even working (because I tried to get GPS running since I flashed CM7)..
Hmmm..
Saftpackl said:
I tried that already (also tried different config layouts), but unfortunately, it changed nothing.
Isn't the aGPS just for finding the nearest satellites faster? So, it seems, that aGPS is finding the wrong position (maybe because of some NTP servers?) and that the normal gps still isn't even working (because I tried to get GPS running since I flashed CM7)..
Hmmm..
Click to expand...
Click to collapse
i guess it's not working, somehow, since you can't find ANY satellite
did you try any other rom, and did gps work when u were stock ?
^^
Yes, it worked on stock rom, and i believe it also did on another (maybe Mindhaxors ROM)
But I like CM very much and would prefer not having to change, these are like two worlds for me since I tried it out ;-)
I had the same issue, using CM7 nightly. I applied the patch and GPS was showing a fixed location far away from actual location. Then I tried a combination of using another app (GPS test instead of GPS status), calibration of compass (rotating in all three axes a cuple of times) and removal of AGPS data and GPS started to work in gps test as well as on google maps. After reboot however I was not able to reproduce it. Now I don't have any fix..I'll try it tomorrow, maybe I'll have more luck.
make nand backup and try full factory reset clean dalvik cache and stuff, and reflash... try it even with new sd card or just some clean one...
p.s. flash latest nightly, or 14th january one, since it's tested ;-)
Sent from my HTC Wildfire using xda premium
I have the same issue:
CM72, GPS fix various methods tried out as in the topics linked, get "too" fast fix within minuted but around 400km away ;-( Any idea what else could be done???
Yes. Wait for sat locks and position update the first time and try not to get bored and quit. It well find you eventually and subsequent location updates will be faster...Might take 10 min or so.
Sent from my cm7.2 Wildfire S
I also have the same kind of prolem.
I tried every solution adviced but my gps is stuck to 46°59.999N and 3°59.999E.
i am with cm 7.2 and my gps workswhen i install a stock rom.
thank u in advance
img851.imageshack.us/img851/1448/screenshot1329031958236.png
I think I might be having the same problem, in my case after applying GPS patches the location returned by GPS was constant (and far away from my actual location). I am yet to understand and fix it, but I think I'm getting closer
UPDATE @estantor - yep I'm having the same issue, the GPS is either stuck at exactly the same coordinates, or lately it stopped locking on to the satellites
those are the exact coordinates where my CM72 GPS is also stuck, in the middle of nowhere in France.
Really strange, I wonder if flashing a more recent CM72 update might help?
UPDATE: DId a new flash with CM72 RC0, applied the fix and now its fast and correct ;-)!!!
playagiron said:
those are the exact coordinates where my CM72 GPS is also stuck, in the middle of nowhere in France.
Really strange, I wonder if flashing a more recent CM72 update might help?
UPDATE: DId a new flash with CM72 RC0, applied the fix and now its fast and correct ;-)!!!
Click to expand...
Click to collapse
did you install the latest nighly build? i'm still stuck :-/
which fix exactly did you apply?
Edit: GPS is working after I installed m1ndh4x0rs ROM where it worked before and reverting to my previous backup (CM7) it still shows the wrong location, though, when GPS has a weak or no signal
Out of the blue, my finger print reader has been acting up, my friend told me to post my problem here. I don't remember if I updated my phone recently, to be honest, I am pretty sure I never accepted anything. I was wondering if I may have accidentally update or something I was able to find this information:
baseband m8994F -2.6.30.0.68
bootloader BHZ10K
Do I need to update? is this a new version? old version? If its not a new update then I guess I can conclude it might be a hardware problem?
Check Settings / About Phone and report the Android Security Patch Level and Build number
If your phone is fully up to date these will be be 1/3/16 and MHC19J (or possibly MMB29V)
Have you tried deleting / re-adding your prints?
Did you install any new apps right before it started? I consistently get the pin prompt (due to unrecognized print) every time I use 'Screen off and lock'
Lastly try wiping all cache (app/cache/dalvik), that seemed to work for several redditors.
updating may not be the solution, some were actually reporting issues after they updated to MHC19J
edit: just found this - using a lock widget messing up the print scanner is a common issue
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