Related
[Q] Issue with 1.47.401.4 : often get "Limited Service" and hard to get signal back
Hi there,
Since 1.47.401.4 (and never before with 1.28.x), I'm experiencing issues with the radio, especially voice:
1/ I often get a "Limited Service" warning in places where I could easily get a decent signal to give a call.
2/ Each time I got the "Limited Service" warning, it can take ages before the signal gets back (after I moved to some other place).
3/ Sometimes, I need to reboot the terminal to get the voice signal back.
I did perform a full wipe (factory reset) on my phone and install the rom again (using the roms.zip method within the bootloader) but it didn't really solve this issue.
I also cleaned the sim card contacts, just in case, but this was useless.
I also chose "GSM auto (PRL)" in the phone settings, this helped a bit, but still this annoying issue remains.
If someone got a clue, I'm interested ! And if anyone is experiencing such weak/bad signal issue, I'm interested in your feedback.
Cheers.
Hboot: 098.002 S-ON
Radio: 20.28I.30.085 AU_3805.06.02.03_M
~babel said:
Hi there,
Since 1.47.401.4 (and never before with 1.28.x), I'm experiencing issues with the radio, especially voice:
1/ I often get a "Limited Service" warning in places where I could easily get a decent signal to give a call.
2/ Each time I got the "Limited Service" warning, it can take ages before the signal gets back (after I moved to some other place).
3/ Sometimes, I need to reboot the terminal to get the voice signal back.
I did perform a full wipe (factory reset) on my phone and install the rom again (using the roms.zip method within the bootloader) but it didn't really solve this issue.
I also cleaned the sim card contacts, just in case, but this was useless.
I also chose "GSM auto (PRL)" in the phone settings, this helped a bit, but still this annoying issue remains.
If someone got a clue, I'm interested ! And if anyone is experiencing such weak/bad signal issue, I'm interested in your feedback.
Cheers.
Hboot: 098.002 S-ON
Radio: 20.28I.30.085 AU_3805.06.02.03_M
Click to expand...
Click to collapse
I have the same problem! 1.28.x was OK, bet the newest one in terms of receiving signals is just terrible!
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
~babel said:
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
Click to expand...
Click to collapse
In complete contrast to what you two are saying..(see my old thread where I had this problem with the older radios http://forum.xda-developers.com/showthread.php?t=1133785)
I'm now running on the latest radio but not the latest ROM (as I use LBC MOD which is currently based on a 1.36 ROM) and I no longer experience this problem.
My conclusion being that the newest Radio is better.
Thanks for your feedback.
Would you then say that the "Radio_20.28I.30.085 AU_3805.06.02.03_M" was the answer to your phone bad signal issues ? Then, I might need to use another rom an check if that helps...
Anyway, did you try to change/update phone/radio settings mode (__http__www_google_com_support_forum_p_android_thread_?tid=42655c79e5837499&hl=en) ?
~babel said:
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
Click to expand...
Click to collapse
I have this problem as well and have emailed HTC but received no reply yet.
Also sometimes it all looks okay and allows calls out but incoming calls go straight to voicemail.
Well, HTC will probable ask you to send your phone for repair.
Actually, this is what they've just replied to my email. But I won't send my phone for a simple flash that I could do my-self !
It seems this is a known issue of the HTC phones (there are plenty of such reports on the internet).
Although this problem hasn't effected my calls on the latest radio version, I do agree that I've often seen what looks like severe signal fluctuations, from zero bars to full bars etc, I've also read about this being an issue on the incredible s
I'm hoping that further rom and radio upgrades will improve this.
Sent from my HTC Desire S using XDA Premium App
It seems that the "Limited Service" issue is caused by a signal loss (i.e. using the elevator for instance) that is never followed by an automatic "good signal" retrieval (i.e. after leaving the elevator and going to a place where signal is usually very good).
~babel said:
Thanks for your feedback.
Would you then say that the "Radio_20.28I.30.085 AU_3805.06.02.03_M" was the answer to your phone bad signal issues ? Then, I might need to use another rom an check if that helps...
Anyway, did you try to change/update phone/radio settings mode (__http__www_google_com_support_forum_p_android_thread_?tid=42655c79e5837499&hl=en) ?
Click to expand...
Click to collapse
I'm afraid that I don't understand what this question? could you PM me?
did it mean did I switch my phone to WCMDA only? if so the answer is NO, mine is set to Auto as around where I live and work there is reasonably good signal.
ben_pyett said:
did it mean did I switch my phone to WCMDA only? if so the answer is NO, mine is set to Auto as around where I live and work there is reasonably good signal.
Click to expand...
Click to collapse
yes, this is what i wanted to know anyway, this didn't change anything for me.
Have you progressed any?
I tried flashing to 1.28 via the RUU at http://forum.xda-developers.com/showthread.php?t=1002506 but it doesn't appear to want to do a downgrade.
I don't seem to get getting the no service at the moment but I am having problems with incoming calls going to voicemail when the phone claims to be connected.
I put my SIM (giffgaff, a MVNO on O2-UK) into my old phone (an XDA Zest) and put an O2-UK SIM into the HTC. At times I could call the XDA with no problem but calling the HTC went to voicemail - two phones next to each other on the same network....
Of course I can't say if this was a problem with 1.28 as I wasn't looking for it but I suspect 1.47 is the problem.
As expected HTC want me to send the phone back which I think I might do and try and persuade them to downgrade it for me.
yes some progress, at last ! I followed the step by step procedure to s-off the rom 1.47.401.4 rom (http://forum.xda-developers.com/showthread.php?t=1194488) and then downgrade to the 1.28.401.7 rom that I was using originally. And now everything works fine...
i could say that once again i learnt that newer doesn't mean better
~babel said:
yes some progress, at last ! I followed the step by step procedure to s-off the rom 1.47.401.4 rom (http://forum.xda-developers.com/showthread.php?t=1194488) and then downgrade to the 1.28.401.7 rom that I was using originally. And now everything works fine...
i could say that once again i learnt that newer doesn't mean better
Click to expand...
Click to collapse
What method did you use to do the downgrade?
I was thinking of trying the method here http://forum.xda-developers.com/showthread.php?t=1190992 which I don't think needs s-off.
Update: I tried the non S-OFF method and have downgraded to 1.28 - I'll see how it behaves now.
I used the PG88IMG.zip method. Basically, you need to copy the roms.zip extracted from the RUU installer to the root of your /sdcard and then reboot your phone to the bootloader.
~babel said:
I used the PG88IMG.zip method. Basically, you need to copy the roms.zip extracted from the RUU installer to the root of your /sdcard and then reboot your phone to the bootloader.
Click to expand...
Click to collapse
I ran the RUU exe directly which seemed less involved. It's looking good so far but I'll need to get out and about and see how it behaves in different locations.
I'll not be in such a hurry to install an OTA next time...
ercm03 said:
I'll not be in such a hurry to install an OTA next time...
Click to expand...
Click to collapse
i see what you mean
solved using the first steps on http://forum.xda-developers.com/showthread.php?p=16796075#post16796075
-------------------------------------------------------
same problem here... tried the PG88IMG.zip method but it said "main version is newer" or something like this... so it didn't work..
do I have to do something before that? I used this ruu:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
and currently installed is this:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed
where can I get a rom.zip that works?
After earlier saying that I'd not experienced this limited service problem, I have now witnessed this a couple of times.
Although, since I applied this
20.4130.0818U_3817.07.00.19_M RADIO I haven't, will re-update post if I do!
This is the Radio that came with the recently leaked Sense SAGA Sense v3.0 ROM and appears to work fine with LBC mod.
does anyone know if one can install this radio over 1.47 with s-off and no root? and if yes - how?
Hi,
I'm having trouble with my Nexus S, and it might have started after installing Jelly Bean (though probably not). The phone is somtimes unable to connect to 3G, and sometimes unable to call/receive calls. More often not working than working, both of them. I tried factory resetting and I also tried my SIM card in another phone (and another SIM card in my phone), with the same result. Something must be wrong with my phone, the only question is if it is a software error or hardware error.
Anyone have any tips? Perhaps how to check if the radio hardware is working (some app perhaps?)? Any ideas on what else I might try? The phone has been working perfectly for more than a year, so it's really odd it suddenly has problems. Anyone had similar problems?
Thanks in advance!
1. Are your NS is rooted...??
2. did you try another JB Custom Rom..???
or
3. is it still working good when you downgrade to ICS or other ICS Custom ROM...???
Then, if thats way still have same result, its might be hardware problem.
novelys said:
1. Are your NS is rooted...??
2. did you try another JB Custom Rom..???
or
3. is it still working good when you downgrade to ICS or other ICS Custom ROM...???
Then, if thats way still have same result, its might be hardware problem.
Click to expand...
Click to collapse
I rooted it yesterday to be able to try custom roms (tried Cyanogenmod 9). Same problem. I then returned it to stock, which made it reflash everything, and still the same problem. I'm starting to believe it's a hardware error. Are there any diagnostic tools available to check the radio module?
Thanks for answering!
jeinor said:
I rooted it yesterday to be able to try custom roms (tried Cyanogenmod 9). Same problem. I then returned it to stock, which made it reflash everything, and still the same problem. I'm starting to believe it's a hardware error. Are there any diagnostic tools available to check the radio module?
Thanks for answering!
Click to expand...
Click to collapse
Well, just try a radio that's for your model, search for nexus s radios in xda you should be able to find a thread which has all The radios, and choose appropriately.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Maybe you have to get the correct access point name from your provider. If I do a clean flash I have to input it by hand as otherwise I cannot connect as well.
Sent from my Nexus S
kwibis said:
Maybe you have to get the correct access point name from your provider. If I do a clean flash I have to input it by hand as otherwise I cannot connect as well.
Sent from my Nexus S
Click to expand...
Click to collapse
That may explain the data connection but not the calls.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Billchen0014 said:
That may explain the data connection but not the calls.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Click to expand...
Click to collapse
True, I read the post to quickly!
Sent from my Nexus S
Thanks everyone for all tips, help and suggestions! I ended up replacing my Nexus S (a... questionable reseller bought it for $120, maybe to use for spare parts for other phones becuase I told him about the problems I was having) with a used Galaxy Nexus. Must have been a hardware error.
Sorry for the late reply/checkback!
Alrighty, I have a One S S4, rooted, running ViperOneS 1.2.1.
Not the first time I've run a custom on here, I've been bouncing back and forth between Viper and Cyanogen, usually without issue. Normally, I've been using CWM recovery...
My problem is that I can't get a new radio to install. I've reinstalled Viper a few times, full wipe and all, reinstalled CWM, and finally, just tried using TWRP. CWM says that it updated, but nothing changes, TWRP just gets stuck saying that it is updating, but never does (have to force a shutdown)
So...anybody else run into this problem? I can't find an answer anywhere, and I have no idea what to do next, because I want to keep Viper on here, but right now, my mobile is alright, but I get no WiFi (and the solution that I'm being told is to install a new radio (would that even fix a WiFi issue))
Please help...
Mage42384 said:
Alrighty, I have a One S S4, rooted, running ViperOneS 1.2.1.
Not the first time I've run a custom on here, I've been bouncing back and forth between Viper and Cyanogen, usually without issue. Normally, I've been using CWM recovery...
My problem is that I can't get a new radio to install. I've reinstalled Viper a few times, full wipe and all, reinstalled CWM, and finally, just tried using TWRP. CWM says that it updated, but nothing changes, TWRP just gets stuck saying that it is updating, but never does (have to force a shutdown)
So...anybody else run into this problem? I can't find an answer anywhere, and I have no idea what to do next, because I want to keep Viper on here, but right now, my mobile is alright, but I get no WiFi (and the solution that I'm being told is to install a new radio (would that even fix a WiFi issue))
Please help...
Click to expand...
Click to collapse
It's probably the hboot you have on your phone not letting you flash the radio ? As for Wi-Fi you probably need to just flash the Wi-Fi partitions. You need to find out what hboot you're on as well as if you don't know how to check which radio you're on you should look into that. About phone software baseband and more something like that.
Sent from my HTC One S using xda premium
ickedmel said:
It's probably the hboot you have on your phone not letting you flash the radio ? As for Wi-Fi you probably need to just flash the Wi-Fi partitions. You need to find out what hboot you're on as well as if you don't know how to check which radio you're on you should look into that. About phone software baseband and more something like that.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
As far as radio, it's 1.08ts.50.02.16_10.08e etc
As far as hboot version....nothing has changed since the time I could reprogram my radio
I'm pretty versed with the phone, I'm asking here, because you will know more than I do...but I know my some of my phone, and I definitely know how to program...but I don't experiment as much as I want to, and I want to know how to fix my phone..
sorry, little drunk at this time, don't want to sound like an ass...
If I think that I'm missing a basic step, I'll ask =)
The hboot, as far add I've know hasn't changed, but I don't know what does. Old versions of recovery, no luck. Had programming issues, get stuck in booloops etc, make it work right...n dint know why the radio won't program out of nowhere =(
Hi all, I aren't a new user but have attached my Google account on this log in so....meh.
I understand that from update 4.4.3 and upwards many N5 users experience loss of their mobile network where switching to aeroplane mode then back again is the only way to rectify this? I was fine until I recently swapped to Virgin (UK) which uses the EE network, ever since this my calls go straight to voicemail unless I manually select the provider myself.
I was having a whale of a time with CM11 and only found out this issue after tearing my hair out for a couple of weeks but it is something I cannot have because I need my phone to be available *always* due to issues with my mum. So what I have now done is backdated my system to 4.4.2 which seems to have worked *but* I now get the system update notifications which I have dealt with but I now seem to have messed up the Play Store
Is there any one solution for this problem where I can have everything actually working as it should? 4.4.2 stock seems to run a lot better and seems a lot quicker in all honesty, quicker than even CM11 than is the gods honest truth.
Please help I dearly love this phone and need it to work for personal reasons and I aren't in a position to buy another right now (quit joib to look after mum etc) have I tugged at your heart strings enough yet?
Flash 4.4.4 but flash the 4.4.2 radio then?
On my carrier in Australia, I've never had a single drop issue, on all versions of the radio.
I live in Ohio and my connection is awesome with ATT. The only problem I have with network is my house and church. Lol Everywhere else like work is awesome. I think the network you choose is the major player in this. The phone itself is great on network.
Lethargy said:
Flash 4.4.4 but flash the 4.4.2 radio then?
On my carrier in Australia, I've never had a single drop issue, on all versions of the radio.
Click to expand...
Click to collapse
I tried a search for this but it was a confusing minefield for a novice like me. I dont suppose you have any pointers as to where and how I get to do the 4.4.2 radio fix do you please?
tremlar said:
I tried a search for this but it was a confusing minefield for a novice like me. I dont suppose you have any pointers as to where and how I get to do the 4.4.2 radio fix do you please?
Click to expand...
Click to collapse
Factory images. Then use fastboot to flash it while in bootloader. Link to tutorials are in the first link of my signature.
Lethargy said:
Factory images. Then use fastboot to flash it while in bootloader. Link to tutorials are in the first link of my signature.
Click to expand...
Click to collapse
To 100 % prove it to myself I did the stock system updates, first to 4.4.3 then to 4.4.4 straight after I rang myself from a landline and it went immediately to voicemail. I then tried to install Cyanfox and that fails on the set up wizard as did liquid
linaro, both using the correct gapps and several versions.
So my next try is an older CM M3 iirc because I think doing the radio thing is a bit beyond my skills Lethargy
tremlar said:
To 100 % prove it to myself I did the stock system updates, first to 4.4.3 then to 4.4.4 straight after I rang myself from a landline and it went immediately to voicemail. I then tried to install Cyanfox and that fails on the set up wizard as did liquid
linaro, both using the correct gapps and several versions.
So my next try is an older CM M3 iirc because I think doing the radio thing is a bit beyond my skills Lethargy
Click to expand...
Click to collapse
theres an easier solution than that...! grab a baseband/radio here http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 download the zip file to your phone then flash it in your custom recovery. it takes seconds and can flash as many radios as you like until you find the perfect one for you
simms22 said:
theres an easier solution than that...! grab a baseband/radio here http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 download the zip file to your phone then flash it in your custom recovery. it takes seconds and can flash as many radios as you like until you find the perfect one for you
Click to expand...
Click to collapse
simms22 you may just be the sexiest person alive, just updating cm then I shall give this a try.
Will report back, appreciated massively so far guys.
Edit - well, it seems to of worked, I am getting some weird google log in errors but I aren't sure if that is related. Letting it download the apps etc then will mess some more tomorrow but the phone definitely rang and didn't go to voicemail. simms 22 you are a gem, thank you very much.
My Nexus 5 which I upgraded from a 5.01 to the 5.1 (stock Google rom, without wipe) has a very big battery problem: the device never reaches deep sleep.
I have some years experience in identifying wakelocks, but this wakelock is new. And the strange thing is: I can't even find a thing on Google. Nothing!
The wakelock is a kernelwakelock (PowerManagerService.Wakelocks). I investigated at partial wakelocks which wakelock it is. It's a wakelock called 'ProxyController'. It's related to the phone process/app.
I wiped cache, tried different Kernel (elementalx). Changed CPU gov, wiped dalvik, changed network, refreshed some settings. Disabled unused apps. I even reinstalled the image and other files through recovery. But nothing helps.
Also I noticed, it might be related, that sometimes my phone reboots or it looses sim and signal. (Which worked perfect in 5.01!). All problems started after 5.1 upgrade.
Ofcourse I can do a full wipe, or revert back or try a custom rom. But I hope it is possible to fix, because besides these weird problems it was / is perfect!
Edit: Important, I couldn't be called either. Also calling someone was difficult and the phone process kept freezing. My phone (and then the phone part) was totally broken! Radio of 5.01 did fix. Read comments below!
Have you tried flashing an older radio.img version and/or a clean flash?
Elluel said:
Have you tried flashing an older radio.img version and/or a clean flash?
Click to expand...
Click to collapse
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
cognosco said:
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
Click to expand...
Click to collapse
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Elluel said:
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Click to expand...
Click to collapse
Yes I fear that too.
However, it started immediately after the 5.1 upgrade, before all was good...
It also seems there might be a link with screenoff/standby. When it's in standby and I switch the device on I see it has no connection or is reconnecting. As if something goes wrong with the connection then. Maybe important information.
I will investigate further. Ofcourse all new tips, ideas and infos are welcome. I will also keep you updated.
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Update: a few days later. Running 5.1 rom with 5.01 radio and all seems ok and fixed!
cognosco said:
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Click to expand...
Click to collapse
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
DarkSorcerer said:
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
Click to expand...
Click to collapse
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
cognosco said:
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
Click to expand...
Click to collapse
Hi,
Thank you for your quick answer. I'll try it first thing in the morning.
It is weird indeed.. My provider is the equivalent of Orange. As with you, it only started to happen after the update to 5.1.
I'll report back. Thanks!