Related
I was wondering if anyone else has this issue. I think most people know by now the issue we all ran into with 4G after we flashed roms with the new OTA update. The 4G would just be stuck at "scanning...." and never connect.
Anyways, I did manage to fix the 4G issue using bigbiff's steps here. So now the 4G connects with no issues but there's one problem: when I leave 4G area or go indoors and come back into 4G area it won't reconnect by itself. I have to either turn on and off 4G or hit the "Scan" button.
If anyone can give me any insight or ideas as to what's going on that would be very awesome.
I have the same problem, and I have seen at least one other person mention this problem (it's kind of hard to search the forum for this problem, since all you get are the folks having problems connecting to 4G).
This started after the OTA update. If the 4G signal fades out, the 4G status remains in "scanning" even in known 4G areas. I made one 4G change to try and fix this - I changed the wimax_idle_sleep time from 10 to 300 as was recommended in the 4G problem posts.
I am wondering if anyone knows what the other 4G settings do and if any of them would fix the problem. So far the only way I know to reconnect to 4G is to turn the radio off and on.
I posted this in another forum, the more frequented one. I thought it was more applicable there since this might be an issue concerning rooting, custom ROMs, home ROM flashing, or all the above. Until I see a wave of non-rooted users complaining about this, I think Sprint has found a gotcha for rooters and flashers. Input from some ROM developers would be nice if they happen to visit this forum.
I can enter a 4g area, turn on 4g, and connect. When I leave a 4g area, turn off 4g, then turn 4g back on before re-entering 4g area and enter a 4g area, it is stuck scanning. It never attaches to the 4g network in the area I entered. If I turn 4g off and on while in 4g area, it will connect.
Are unrooted stock users having these problems? It is a real let down and PITA. Is 4g working perfectly in all scenarios for any rooted user?
Click to expand...
Click to collapse
I also think it's related to one of the images we have to flash to get root, as the behavior is definitely different than stock. I noticed this after I first rooted / nand unlocked my phone, but before I applied the new radio & wimax. On my phone, however, 4G does eventually come back up. It might take 5 minutes or more, but it does eventually reconnect.
I'm not sure that it's really a bug though. I actually prefer this behavior because it results in fewer dropped connections when switching between 3G and 4G. For streaming apps (Rhapsody, Pandora, Youtube, etc) the frequent switching forces you to have to start the stream over. I think it might have been an attempt to increase the stability of the data connection at the expense of having a 4G connection less of the time. Could be a hold over from one of the older engineering builds we had to flash during the rooting process? It's strange that the behavior persists after flashing a new radio/wimax, but maybe it's actually controlled elsewhere.
Add me to the list. This is from my post about 20 hours ago which hasn't received any bites:
I have seen various issues reported:
1) 4g won't turn on. PERIOD.
2) 4g turns on but only scans - never connects.
3) 3g/4g alternate so there is never a stable connection.
4) 4g turns on and connects but after a while disconnects and won't reconnect until it is toggled on/off with the widget or check box in settings.
I used to have #3 until I did whitslack's "start over" method and now I have #4. I've changed my wimax idle sleep time to 300 in ##data# and verified a good MAC so other than the 2 evo last resort method I think I've tried everything other than the above.
So, does anyone know if renaming/moving macaddress.tree.xml is for my issue #4? Or does anyone know a specific fix for #4?
If it matters I rooted with toast 1/2 and am still on the rooted stock ROM from whitslack's "start over" method.
Click to expand...
Click to collapse
Some Observations:
I've noticed the following differences since the OTA (with Root-from the "How to Start over with 1.47.651.1" thread):
1. The 4G reconnection problem.
2. Bluetooth no longer auto connects when my headset is in range.
3. I have been getting "Error 67 Data Connection Lost" errors. This error blocks me from 3G data connectivity for a few minutes. During this time, "Mobile Networks" shows "Turning On" in the settings.
I suspect it is one of the following:
a. There is still a radio problem with the rooted OTA
b. the PRI that has not been updated since the root crack matters with this release.
c. Sprint/HTC introduced some new bugs.
d. Some hardware settings need to be tweaked (like the timeout that folks are changing from 10 to 300).
So we need to figure out who is having this problem, and under what circumstances.
I did however note something very interesting. I have repeated this 4 times today. If the 4G disconnects and stays in scanning, if you then place a call it will immediately reconnect. This leads me to believe that it is indeed a setting, and a voice call triggers it (if you recall in May, Sprint was saying that they hope to have Simultaneous Voice and 4G - so there is probably some code to trigger 4G at this point).
What do you folks think.
sw99 said:
Some Observations:
I've noticed the following differences since the OTA (with Root-from the "How to Start over with 1.47.651.1" thread):
1. The 4G reconnection problem.
2. Bluetooth no longer auto connects when my headset is in range.
3. I have been getting "Error 67 Data Connection Lost" errors. This error blocks me from 3G data connectivity for a few minutes. During this time, "Mobile Networks" shows "Turning On" in the settings.
I suspect it is one of the following:
a. There is still a radio problem with the rooted OTA
b. the PRI that has not been updated since the root crack matters with this release.
c. Sprint/HTC introduced some new bugs.
d. Some hardware settings need to be tweaked (like the timeout that folks are changing from 10 to 300).
Click to expand...
Click to collapse
I would take C out because I have not read complaints by non-rooted users.
The latest PRI is 1.40_003. Right?
Who can bring this over? ROM developers say those features are not part of what they do. If not them, then who?
What do you folks think.
Click to expand...
Click to collapse
I think being rooted currently sucks. One of EVO's greatest strengths, connectivity, has been crippled.
sw99, did you try the move the xml file with your mac address solution? If so, I guess it didn't make any difference.
sw99 said:
Some Observations:
I've noticed the following differences since the OTA (with Root-from the "How to Start over with 1.47.651.1" thread):
1. The 4G reconnection problem.
2. Bluetooth no longer auto connects when my headset is in range.
3. I have been getting "Error 67 Data Connection Lost" errors. This error blocks me from 3G data connectivity for a few minutes. During this time, "Mobile Networks" shows "Turning On" in the settings.
I suspect it is one of the following:
a. There is still a radio problem with the rooted OTA
b. the PRI that has not been updated since the root crack matters with this release.
c. Sprint/HTC introduced some new bugs.
d. Some hardware settings need to be tweaked (like the timeout that folks are changing from 10 to 300).
So we need to figure out who is having this problem, and under what circumstances.
I did however note something very interesting. I have repeated this 4 times today. If the 4G disconnects and stays in scanning, if you then place a call it will immediately reconnect. This leads me to believe that it is indeed a setting, and a voice call triggers it (if you recall in May, Sprint was saying that they hope to have Simultaneous Voice and 4G - so there is probably some code to trigger 4G at this point).
What do you folks think.
Click to expand...
Click to collapse
I will try making a call tomorrow when this happens and report back.
I had the same problem pre-root.
I wont be able to help anybody too much with technical stuff 'cause I'm basically a non-technical guy, but I've had the same problem with wimax dropping & not reconnecting ever since the OTA update (1.47....). I went to a Sprint store & the guy just went cross eyed, so it may not be too common.
In my case the connection will SOMETIMES come back on its own with a really strong signal, but rarely.
I just rooted tonight so I have no idea if it's worse or not, but I'll find out tomorrow, eh?
I've also had difficulty with Bluetooth automatically connecting, but I have a new stereo so I don't know where the issue lies.
Burt Reynolds said:
I wont be able to help anybody too much with technical stuff 'cause I'm basically a non-technical guy, but I've had the same problem with wimax dropping & not reconnecting ever since the OTA update (1.47....). I went to a Sprint store & the guy just went cross eyed, so it may not be too common.
In my case the connection will SOMETIMES come back on its own with a really strong signal, but rarely.
I just rooted tonight so I have no idea if it's worse or not, but I'll find out tomorrow, eh?
I've also had difficulty with Bluetooth automatically connecting, but I have a new stereo so I don't know where the issue lies.
Click to expand...
Click to collapse
Interesting. So this may have nothing to do with rooting.
kamiller42 said:
sw99, did you try the move the xml file with your mac address solution? If so, I guess it didn't make any difference.
Click to expand...
Click to collapse
Nope. Didn't touch the xml file, as my 4G was connecting, and the fix was for 4G just scanning.
I still think we can tweak the WIMAX settings and make it come back faster.
sw99 said:
Nope. Didn't touch the xml file, as my 4G was connecting, and the fix was for 4G just scanning.
I still think we can tweak the WIMAX settings and make it come back faster.
Click to expand...
Click to collapse
This is basically the only thing I haven't tried.
I tried making a call to reconnect to 4g three times this morning. IT WORKED ALL THREE TIMES! Odd....
sdc177 said:
This is basically the only thing I haven't tried.
I tried the making a call to reconnect to 4g three times this morning. IT WORKED ALL THREE TIMES! Odd....
Click to expand...
Click to collapse
Well at least its faster than toggling the 4G radio - just find a friend with a mobile phone so you don't waste any minutes.
sw99 said:
Well at least its faster than toggling the 4G radio - just find a friend with a mobile phone so you don't waste any minutes.
Click to expand...
Click to collapse
Just dial your own number which takes you to voice mail and shouldn't waste minutes. I'll probably put a direct dial shortcut on my home screen until a solution comes along. Not that I'm worried about wasting my regular minutes....I used 29 of 450 on my last bill!
I can now confirm that moving/deleting the xml file does nothing for our problem. At least not on my EVO.
So, I've been looking at the WIMAX settings (using ##DATA# and my MSL).
There are some settings that look like they could be effecting this problem. Be forewarned, however, that some of the values preset are not considered "valid" when you make a change (leading me to add credence to my theory that HTC/Sprint goofed), so I'm hoping a nandroid backup will recover them. Open each parameter and deleting the values, gives you a popup of the valid values and units.
Here is what I tried so far:
wimax_idle_sleep(s) changed from 10 to 300 seconds - effect: little to none.
wimax_scan_attempt_timeout(s) changed from 1 to 20 seconds - effect: little to none. (note only 5-300 are valid values after this change).
Other parameters that look interesting and their default values:
Wimax_scan_retry(s): 300 Seconds
Wimax_entry_delays(s): 300 seconds
wimax_exit_delay(s): 2 seconds
idle_mode_timer: 60 seconds
Standby Time: 10 Minutes
handoff Threshold: 6
Anyone willing to mess with these (at the risk of losing Wimax, of course)?
That is one place I'm not going to mess around. I saw a stern warning about that recently on the dev forum.
sdc177 said:
Interesting. So this may have nothing to do with rooting.
Click to expand...
Click to collapse
I still have my doubts about that. I put a link in the General forum to this thread, and we have one response. I read around the non-tech sites with 4G forums like SprintUsers, and I don't see these complaints.
I would like to hear from a tech oriented non-rooted user.
sdc177 said:
That is one place I'm not going to mess around. I saw a stern warning about that recently on the dev forum.
Click to expand...
Click to collapse
I'm hoping someone who knows what the settings mean can shed some light. I have not had any luck googling any of these fields.
kamiller42 said:
I still have my doubts about that. I put a link in the General forum to this thread, and we have one response. I read around the non-tech sites with 4G forums like SprintUsers, and I don't see these complaints.
I would like to hear from a tech oriented non-rooted user.
Click to expand...
Click to collapse
I did see a couple of non-root complaints, but I can't find them now (not on your standard sites).
With all the excitement going on with the Wimax being alpha tested in the CM ROM it got me testing my data speeds the last few weeks.
From my understanding 3G speeds should be decent and range between 1 - 3 mbps down, and using Sprints 3G network I am not coming close to that.
I am using the SpeedTest.net app for my results, and I have read from some posts that the app might not be that accurate.
Here are the results that I have been seeing (displayed as Mbps) using the closest server to me (Random Lake, WI - even though other servers are giving me the same low scores):
1/6/11 - .18 down and .37 up
1/6/11 - .16 down and .30 up
1/2/11 - .30 down and .77 up
12/27/10 - .45 down and .27 up
12/27/10 - .34 down and .27 up
12/27/10 - .12 down and .20 up
12/24/10 - .45 down and .70 up
12/24/10 - .15 down and .62 up
As you can see, not close to the 1 - 3 range that I would expect. I am checking that the icon is showing 3G and 1X when doing the test as well. Here is some information to help deduct and (hopefully) solve my issue.
My EVO is from release day, not the 004 hardware
I'm running CM 6.1.1
CM stock kernal that comes with it - 2.6.35.9 [email protected] #1
Theme is Project_Bliss HD (modded by me to include some different emoticons and Batman themed notification shade)
I have flashed all of the latest
*Radio - 2.15.00.11.19
*Wimax - 27167_R01 (even though where I live has no 4G)
*PRI - 1.90_003
*NV - 1.90_003
I have flash a Sense ROM and update Profile and PRL
I live in Appleton, WI area if that matters at all.
So am I just looking at my results wrong? If I'm not, what are some solutions that I can look at to improve my 3G data speed? Any other test I should run or try?
Push come to shove I can always #blameshift!!
JasonK75 said:
With all the excitement going on with the Wimax being alpha tested in the CM ROM it got me testing my data speeds the last few weeks.
From my understanding 3G speeds should be decent and range between 1 - 3 mbps down, and using Sprints 3G network I am not coming close to that.
I am using the SpeedTest.net app for my results, and I have read from some posts that the app might not be that accurate.
Here are the results that I have been seeing (displayed as Mbps) using the closest server to me (Random Lake, WI - even though other servers are giving me the same low scores):
1/6/11 - .18 down and .37 up
1/6/11 - .16 down and .30 up
1/2/11 - .30 down and .77 up
12/27/10 - .45 down and .27 up
12/27/10 - .34 down and .27 up
12/27/10 - .12 down and .20 up
12/24/10 - .45 down and .70 up
12/24/10 - .15 down and .62 up
As you can see, not close to the 1 - 3 range that I would expect. I am checking that the icon is showing 3G and 1X when doing the test as well. Here is some information to help deduct and (hopefully) solve my issue.
My EVO is from release day, not the 004 hardware
I'm running CM 6.1.1
CM stock kernal that comes with it - 2.6.35.9 [email protected] #1
Theme is Project_Bliss HD (modded by me to include some different emoticons and Batman themed notification shade)
I have flashed all of the latest
*Radio - 2.15.00.11.19
*Wimax - 27167_R01 (even though where I live has no 4G)
*PRI - 1.90_003
*NV - 1.90_003
I have flash a Sense ROM and update Profile and PRL
I live in Appleton, WI area if that matters at all.
So am I just looking at my results wrong? If I'm not, what are some solutions that I can look at to improve my 3G data speed? Any other test I should run or try?
Push come to shove I can always #blameshift!!
Click to expand...
Click to collapse
i noticed this with a lot of people lately. ive started to notify a lot of people including cyanogen himself
mic.mayorga said:
i noticed this with a lot of people lately. ive started to notify a lot of people including cyanogen himself
Click to expand...
Click to collapse
Thanks for letting Cyanogen know that. So it sounds like I'm not alone in this?
Are you having any issues?
Sent from my EVO (CM6.1.1) using XDA App
A lot of those results look like they could be from when you were connected at 1x speeds. Sometimes it seems like the status bar icon doesn't update quickly for the change in network type. Also, how strong of signal do you have. If you're at the edge of data coverage, the rate might be low because a lot of packets are getting lost in transmission. Have you seen what your speeds look like in other locations? In my home town I regularly get over 2mb, but when I was traveling a few weeks ago in some places I could barely pull 300k.
I have check all over town since my apartment is further away and gets lower strenght. Im getting the same results close or far away from a tower.
Sent from my EVO (CM6.1.1) using XDA App
i started noticing this with my evo aswell, actually about yesterday, my stats are about the same in the OP, i live less then a mile from the 4g tower, i've even been about 200 yards away and gotten crappy 4g signal, anywhere from only 3-4 dl, and barely 1 ul.
Hopefully this helps. I was also experiencing 1x speeds although the phone indicated 3G. I upgraded to an EVO after modding my Hero for the past year. Thus I was pretty comfortable with rooting, installing roms, etc. within 24 hours of getting my EVO I decided to root it and try out some of the roms available.
Almost immediately after rooting using unrEVOked I noticed signiffigantly slower data speeds. (I'm not pointing any fingers, only documenting what led up to this) I first tried out the latest CM6 rom. Upon booting it indicated 1x speeds though posts that I read stated that you are actually recieving data at 3G speeds. I think that CM6 may actually be reporting the data connection accurately while the sense rom is not. Using speedtest.net's app (I know it dosen't report speeds accurately) I was consistently recieving between 80-160 kbs download and 60-100 kbs upload. I then downloaded the same app to my wifes unrooted EVO and ran a side by side comparison. Using the same server and within seconds of testing each her EVO was downloading at 800-1600 kbs download and 600-1000 kbs upload while mine was still recieving at the afore mentioned speeds. I tried updating PRL, profile, running the stock rom to no avail. I then tried RUU and unrooting without any change.
I was convinced that either Sprint was throttling my connection or the transmitter in the phone was defective or damaged. I was ready to return the phone to Radio Shack where I purchased it last week but I decided to call Sprint and inquire about the throttling issue first. Sprint assured me I was not being throttled and they also thought I may have a defective phone but they asked if I would perform a ##DATA# before returning it. Amazingly enough this worked and my data speeds have returned to 3G speeds of around 1000-1400 kbs download.
I'll detail the procedure but I make no guarantees this will work for anyone else. Also you'll need your MSL, there are guides that detail how to obtain this or you can all Sprint and ask nicely. Also I did this while stock and unrooted and I haven't tried to reobtain root again yet so if this works for you while rooted let me know. Finally I believe you'll have to perform this using the stock dialer as I don't believe that the CM dialer will work for this.
Procedure is as follows:
Open dialer and type ##3282#. (##DATA#)
You should now be taken to the epst prompt. Choose "Edit Mode"
You will now be asked for your password. This is your MSL
Next you want to choose "Data Profile"
While in Data Profile hit the "Menu" button at the bottom of the phone.
Next choose "Restore" and allow the phone to reprovision.
Let me know if this works if you try it while rooted as I'd like to reroot again but I'm a little gun shy now that it's fixed again.
I'll give that I try and see what happens. I have to flash a stock ROM first and hope that any changes follow me along back to CM ROM. I am also going to try the Wimax kernal to see if that helps since that ks reporting to be a possibility.
Sent from my EVO (CM 6.1.1) using XDA App
priceaw1 said:
Hopefully this helps. I was also experiencing 1x speeds although the phone indicated 3G. I upgraded to an EVO after modding my Hero for the past year. Thus I was pretty comfortable with rooting, installing roms, etc. within 24 hours of getting my EVO I decided to root it and try out some of the roms available.
Almost immediately after rooting using unrEVOked I noticed signiffigantly slower data speeds. (I'm not pointing any fingers, only documenting what led up to this) I first tried out the latest CM6 rom. Upon booting it indicated 1x speeds though posts that I read stated that you are actually recieving data at 3G speeds. I think that CM6 may actually be reporting the data connection accurately while the sense rom is not. Using speedtest.net's app (I know it dosen't report speeds accurately) I was consistently recieving between 80-160 kbs download and 60-100 kbs upload. I then downloaded the same app to my wifes unrooted EVO and ran a side by side comparison. Using the same server and within seconds of testing each her EVO was downloading at 800-1600 kbs download and 600-1000 kbs upload while mine was still recieving at the afore mentioned speeds. I tried updating PRL, profile, running the stock rom to no avail. I then tried RUU and unrooting without any change.
I was convinced that either Sprint was throttling my connection or the transmitter in the phone was defective or damaged. I was ready to return the phone to Radio Shack where I purchased it last week but I decided to call Sprint and inquire about the throttling issue first. Sprint assured me I was not being throttled and they also thought I may have a defective phone but they asked if I would perform a ##DATA# before returning it. Amazingly enough this worked and my data speeds have returned to 3G speeds of around 1000-1400 kbs download.
I'll detail the procedure but I make no guarantees this will work for anyone else. Also you'll need your MSL, there are guides that detail how to obtain this or you can all Sprint and ask nicely. Also I did this while stock and unrooted and I haven't tried to reobtain root again yet so if this works for you while rooted let me know. Finally I believe you'll have to perform this using the stock dialer as I don't believe that the CM dialer will work for this.
Procedure is as follows:
Open dialer and type ##3282#. (##DATA#)
You should now be taken to the epst prompt. Choose "Edit Mode"
You will now be asked for your password. This is your MSL
Next you want to choose "Data Profile"
While in Data Profile hit the "Menu" button at the bottom of the phone.
Next choose "Restore" and allow the phone to reprovision.
Let me know if this works if you try it while rooted as I'd like to reroot again but I'm a little gun shy now that it's fixed again.
Click to expand...
Click to collapse
this sorta helped me a bit, but i just also ended up flashing back to 1.77pri and nv, though i still have the latest wimax and radio and 60674prl on myn's rls5, however i'm still experiencing way below average data speeds as compared to what i used to, i have a release day evo with 0002 hardware, and .76 hboot, even my 4g's are slower then what they used to be.
FWIW, I experienced a drop in speed as well. I used to get 1-2 Mbps easy. Now all I get is around 500. Very strange.
detusueno said:
FWIW, I experienced a drop in speed as well. I used to get 1-2 Mbps easy. Now all I get is around 500. Very strange.
Click to expand...
Click to collapse
humm, something is ary here, possible throttling, or over crowded network?
tomh1979 said:
humm, something is ary here, possible throttling, or over crowded network?
Click to expand...
Click to collapse
I think with all the new phones sold over christmas the network is being hammered.
Sent from my PC36100 using XDA App
baknblack said:
I think with all the new phones sold over christmas the network is being hammered.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i really hope your right, i mean the other day with cmWimax i nailed a 7.61, now i'm lucky if im even in the 3 range for moar gee's, lol, even with reg sense rom's i'm barely in 3 range as well, i have a tower that is only about 200 yards away that is 4g and it still suxor's.
I haven't had a chance to test the above, I'm about to start to do that.
I did try out Sprints Network Speed Test and got results from it above 1.0 finally. Then I tried using the speed test app and it was giving me location in Europo to test? This morning it is back to normal and both the speed test app and Sprints website both were giving the same results - around .80.
I'm going to flash the Wimax for CM and see if that helps out. If not, then I'm going to flash a Sense ROM and do the #DATA# trick listed above.
Here is the website for Sprints speed test website. You'll need the latest Flash installed from the market for it to work.
http://www6.sprint.com/landings/speedtest/?ECID=vanity:speedtest
JasonK75 said:
I haven't had a chance to test the above, I'm about to start to do that.
I did try out Sprints Network Speed Test and got results from it above 1.0 finally. Then I tried using the speed test app and it was giving me location in Europo to test? This morning it is back to normal and both the speed test app and Sprints website both were giving the same results - around .80.
I'm going to flash the Wimax for CM and see if that helps out. If not, then I'm going to flash a Sense ROM and do the #DATA# trick listed above.
Here is the website for Sprints speed test website. You'll need the latest Flash installed from the market for it to work.
http://www6.sprint.com/landings/speedtest/?ECID=vanity:speedtest
Click to expand...
Click to collapse
ok, so using the sprint site, i/m actually where i should be as before, back above 7 for 4g, not tested 3g yet, but working on it.
EDIT: wow, my 3g still blows, lol.
tomh1979 said:
ok, so using the sprint site, i/m actually where i should be as before, back above 7 for 4g, not tested 3g yet, but working on it.
EDIT: wow, my 3g still blows, lol.
Click to expand...
Click to collapse
Glad to hear that 4G is back to where it should be. Are you on a Sense or AOSP ROM like Cyanogen?
JasonK75 said:
Glad to hear that 4G is back to where it should be. Are you on a Sense or AOSP ROM like Cyanogen?
Click to expand...
Click to collapse
myn's rls5, so yeah back on sense right now, more stable to use for using both 3/4g.
tomh1979 said:
myn's rls5, so yeah back on sense right now, more stable to use for using both 3/4g.
Click to expand...
Click to collapse
Nothing wrong with that. I'm going to start my tests this afternoon.
Sent from my EVO (CM 6.1.1) using XDA App
JasonK75 said:
Nothing wrong with that. I'm going to start my tests this afternoon.
Sent from my EVO (CM 6.1.1) using XDA App
Click to expand...
Click to collapse
i have noticed though with this release of myn's that i do keep dropping 4g and reconnecting, something that i have never did before on other dev's rom's.
Well, both attempts to fix it didn't work. The new Wimax for CM didn't give me faster speed and the flashing to Sense ROM to do the ##DATA# didn't help either.
Anyone else have any ideas?
Just was wondering if anyone else was experiencing poor signal with wifi and cell with these gingerbread roms and if there was anything that can help? I have the latest nightly installed and wifi is always at 1 bar most of the time and cell signal is 2 bars or less in a strong sprint area...thanks in advance!
Sent from my PC36100 using XDA App
I'm sure this will be fixed once a stable release is out. Keep in mind they ARE nightlies. Otherwise try wiping and reflashing
sent from my Evo on Americans REAL largest 4G network
I'm having the same issue - on build 24 on mytouch 4g (sorry for posting in wrong forum, but didn't see any mention in the mt4g forum.
Cheers,
lee
1. my service signal literally never goes over 2 bars
2. Gps keeps getting lost, it feels like it gets it for a sec updates location then freezes(Google nav)
Haven't noticed any problems with wifi
Cyanogen gives your the REAL signal strength. Compare you db in the system info to that on a sense rom. The numbers will be the same.
I installed n24 and have a full 4 bars of 3g signal! Last night I had full bars for wifi as well.
Jaimster that is what I am experiencing as well with signal...doesn't like to go over 2 bars...and wifi is weak...there is a gps fix which involves flashing a sense rom and dialing the ## code for clearing the gps...then reflashing back to the cm 7 rom...it worked for me and a lot of others...I'll try the latest nightly and see what happens with signal
Sent from my PC36100 using XDA App
Chad which baseband are you using?
ChadH42 said:
I installed n24 and have a full 4 bars of 3g signal! Last night I had full bars for wifi as well.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I normally have around 2 bars standard, though had max bars in better area coverage. They are nightlies and should be fixed once it becomes stable.
I get horrible reception on the nightlies, probably because it's a nightly and not a stable release so I'm not complaining. But, my wifi is only 1 bar if I take more then 5 steps from the router, and only gets 3 if I'm within reach of it. Cell and 3g are just as bad as I have not seen above 2 bars either, no matter where I am. Switched back to mikfroyo tonight because of it. I'm sure it will be fixed in a stable and more so in a RC though because Cyanogen and his team are pretty badass lol.
Regarding wifi at least, when the phones first came out the wifi reception was crap, it wasn't until the 3rd or 4th update did the signal strength more than double. Seems like Cyanogen is still working off the wifi drivers from the very first evo RUU still, since many people say wifi is worse on CM for 6.x and 7, compared to the latest sense.
I have the same problem too. Extremely weak wifi and cell reception. Have the exact same problem in other CM-based ROMs such as the CM7-EX.l33t. I have to be within 10 feet of my router to hold on to a connection. With other sense-based ROMs and the stock ROM, I would stay connected all over the house and my cell strength indicator was a solid 4 bars.
Using Wifi Analyzer, I get -35db with the stock sense ROM and -75db with the cm7 nightly (currently on 27).
Hope they get this fixed soon.
Jaimster said:
1. my service signal literally never goes over 2 bars
2. Gps keeps getting lost, it feels like it gets it for a sec updates location then freezes(Google nav)
Haven't noticed any problems with wifi
Click to expand...
Click to collapse
The following method has worked for many. This should fix your GPS:
Originally Posted by gmmorrell View Post
I used an abbreviated version of what GALT posted HERE
Thank you GALT!
I understand when most folks have said GPS works they are referring to lock. I am talking about tracking! I drove around the neighborhood and google maps tracked me perfectly (with a little label saying 'accurate to within 20 meters').
Admittedly, it was a 5 minute drive. I have a 3 hour one later today and I will test it again. I will use the navigation and report back.
You will need:
1. A 'sense' ROM currently running on your phone (I had Fresh 3.5.1)
2. MSL reader installed (get it from the market)
2. Have CM7 (build 17 worked for me) and the latest gapps (I used the ones from 2011-01-15) downloaded to your SD card
Steps:
1. Open MSL reader and get your MSL (jot it down)
2. Launch phone dialer and dial ##GPSCLRX#
3. It will ask you for your MSL, enter it.
4. Upon hitting OK, your phone will just say reboot in 10 secs, let it reboot.
Phew!
5. After it has rebooted, boot to recovery (i used clockworkmod 2.6.0.1)
6. Nandroid backup (if you are so inclined)
7. Wipe cache, Dalvik and then wipe data/factory reset
4. Flash CM7 b17 from your sd-card
9. Flash gapps
10. Reboot and walk through set-up. Your gapps will be downloaded from the market. Wait for all the downloads to complete.
11. Use GPS as normal and enjoy the GPS goodness
I am not a developer but this worked for me and I hope it works for you too.
Click to expand...
Click to collapse
*sigh*
Sense shows which is higher: 1X or 3G, regardless of what you're using. Sense also has 6 bars and stacks things so that what should be two bars shows up as four and so on.
This is why I hate bars, and want the -dB display from CM6 in CM7.
First off, I've read dozens of threads relating to this issue and no one seems to have come up with a solid, concrete answer, apart from returning phones for a replacement (and often still having the issue).
I recently acquired a Gnex second hand that has presented the signal loss issue. I am coming from a Nexus S which gets full blue HSDPA bars of signal indoors on my desk. When I place the same sim into the Gnex, I get nothing but an X. Every now and then it registers on the network (Showing "YES OPTUS" - my provider here in Australia), but still no signal.
When I got the phone it was running Android Revolution HD 9.0 with a non-stock kernel (I didn't take note before wiping the device). No luck there with signal. I then flashed to 4.2.2 under Android Revolution HD 10.0. Still no signal. Since then I have tried:
- Lean Kernel
- Air Kernel
- SlimBean Rom
- About half a dozen different modems/basebands, local, european, north american, etc. Finally settled on XXLA02 as that was recommended for Australian users that aren't on Telstra/Vodafone (850MHZ).
- Matching RIL's to the basebands
None of the above options made an improvement. On the air kernel, I would see the signal (using *#*#4636#*#*) chance from UMTS to EDGE to GPRS to HSDPA to EDGE etc over and over, sometimes showing one grey bar on Edge. I could go outside and see one grey HSDPA bar stay there, but you still couldn't use data. Browsers would fail and the playstore wouldn't open without a connection.
As of today I have restored the phone using fastboot to the earliest available Google factory image (4.0.4). I unrooted the phone and relocked the bootloader, just back to complete stock. The modem that comes with the google image is XXLA02. In this current state, there is still no signal inside, where I would have full bars on the Nexus S, but when outside fiddling with the service menu, selecting AUS from the GSM/UMTS band selection menu gave me a reasonable HSDPA signal. Though it was erratic. It would fluctuate from 3/4 to 0/4, to 1/4 over and over and both upstream and downstream indicators would be going, yet nothing was coming through.
Trying to open the playstore was awful, but it eventually worked. I managed to get the Speedtest.net app down after a few failed attempts and ran a test to the nearest OPTUS server. The results came back as:
Ping: 235ms
D/L: 576kbps
U/L: 35kbps
Which is not very good, really. As soon as I walked back inside to get the Nexus S, though, the signal dropped right away to nothing.
I took the sim out, tried the same test with the Nexus S in the same spot outside and got the following results:
Ping: 145ms
D/L: 2241kbps
U/L: 1169kbps
Which is a bit more typical for the area.
So I'm running out of ideas
As the phone was bought second hand, I don't have anywhere I can return the phone to for a replacement. Unless I contact Google directly, I don't think that will be of any help, really. Is there anything else left I could try, or is this just an expensive paperweight?
Thanks for reading.
By typing *#06# IMEI code on the display that appears is identical to the one on the box or under the battery?
Problems in call / sms and registration on the net I happened to corruption of files in the EFS.
Maxmaximus said:
By typing *#06# IMEI code on the display that appears is identical to the one on the box or under the battery?
Problems in call / sms and registration on the net I happened to corruption of files in the EFS.
Click to expand...
Click to collapse
Hi, Thanks for the response.
The IMEI shown with that code is the same as what is under the battery :good:
Could be damaged/disconnected antennas.
Sent from my Galaxy Nexus using Tapatalk 2
Sounds like you got a lemon. SOL.
JPBeard21 said:
Could be damaged/disconnected antennas.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Cheers for the suggestion. I know it has been opened before to replace the USB daughterboard for charging, twice. I'll see if I can get it apart and have a look.
cctoro said:
Sounds like you got a lemon. There was a batch if gnexs that had signal issues. I had a bad one, returned it and the new one was fine. Obviously you can't do that, SOL.
Click to expand...
Click to collapse
Yeah, it's sounding like I'm SOL as it doesn't seem to be a software fixable issue. Pain in the ass, really. Thanks for the info. :good:
signal dropped
My Phone some times in standby mode, GSM signal dropped/network
disconnected.
same time high strength show in my other phone.
i need restart the phone then only re-connected the network and possible
to make call .. !
SMS function also not proper.
Incoming SMS i received but outgoing SMS not work at all.
How it sole?
Build number: JRO03C.I9250XWLH2
Baseband version: I9250XXLF1
Android version: 4.1.1
Kernel Version: 3.0.31-g6fb96c9
samb0rg said:
First off, I've read dozens of threads relating to this issue and no one seems to have come up with a solid, concrete answer, apart from returning phones for a replacement (and often still having the issue).
I recently acquired a Gnex second hand that has presented the signal loss issue. I am coming from a Nexus S which gets full blue HSDPA bars of signal indoors on my desk. When I place the same sim into the Gnex, I get nothing but an X. Every now and then it registers on the network (Showing "YES OPTUS" - my provider here in Australia), but still no signal.
When I got the phone it was running Android Revolution HD 9.0 with a non-stock kernel (I didn't take note before wiping the device). No luck there with signal. I then flashed to 4.2.2 under Android Revolution HD 10.0. Still no signal. Since then I have tried:
- Lean Kernel
- Air Kernel
- SlimBean Rom
- About half a dozen different modems/basebands, local, european, north american, etc. Finally settled on XXLA02 as that was recommended for Australian users that aren't on Telstra/Vodafone (850MHZ).
- Matching RIL's to the basebands
None of the above options made an improvement. On the air kernel, I would see the signal (using *#*#4636#*#*) chance from UMTS to EDGE to GPRS to HSDPA to EDGE etc over and over, sometimes showing one grey bar on Edge. I could go outside and see one grey HSDPA bar stay there, but you still couldn't use data. Browsers would fail and the playstore wouldn't open without a connection.
As of today I have restored the phone using fastboot to the earliest available Google factory image (4.0.4). I unrooted the phone and relocked the bootloader, just back to complete stock. The modem that comes with the google image is XXLA02. In this current state, there is still no signal inside, where I would have full bars on the Nexus S, but when outside fiddling with the service menu, selecting AUS from the GSM/UMTS band selection menu gave me a reasonable HSDPA signal. Though it was erratic. It would fluctuate from 3/4 to 0/4, to 1/4 over and over and both upstream and downstream indicators would be going, yet nothing was coming through.
Trying to open the playstore was awful, but it eventually worked. I managed to get the Speedtest.net app down after a few failed attempts and ran a test to the nearest OPTUS server. The results came back as:
Ping: 235ms
D/L: 576kbps
U/L: 35kbps
Which is not very good, really. As soon as I walked back inside to get the Nexus S, though, the signal dropped right away to nothing.
I took the sim out, tried the same test with the Nexus S in the same spot outside and got the following results:
Ping: 145ms
D/L: 2241kbps
U/L: 1169kbps
Which is a bit more typical for the area.
So I'm running out of ideas
As the phone was bought second hand, I don't have anywhere I can return the phone to for a replacement. Unless I contact Google directly, I don't think that will be of any help, really. Is there anything else left I could try, or is this just an expensive paperweight?
Thanks for reading.
Click to expand...
Click to collapse
tdreji said:
My Phone some times in standby mode, GSM signal dropped/network
disconnected.
same time high strength show in my other phone.
i need restart the phone then only re-connected the network and possible
to make call .. !
SMS function also not proper.
Incoming SMS i received but outgoing SMS not work at all.
How it sole?
Build number: JRO03C.I9250XWLH2
Baseband version: I9250XXLF1
Android version: 4.1.1
Kernel Version: 3.0.31-g6fb96c9
Click to expand...
Click to collapse
I would update to the latest OTA update and verify you have the latest radios.
Edit: also make sure your sim card's contact points are clean and making a snug connection.
Sent from my Galaxy Nexus using Tapatalk 2
Resigned to just getting rid of the phone. Will try and get a newer revision of it without the signal issues.
Hey guys - my VZW Gnex (it's a refurb to replace my old one with a bad screen) has been having excessive network dropouts lately. When I boot the phone, it doesn't acquire signal for over a minute, when I place a call I lose signal afterwards, and data drops out randomly. The device will say it's connected (blue bars), although I cannot use the internet. Also, it'll randomly loose cellular connectivity, although indicate that it has signal. I'll go to send a text and it'll immediately have send errors, and I am unable to make or receive calls, even though it shows I have signal. To fix, a reboot is always necessary. This has happened on 4.3 (crDroid) and 4.2.2 (CM 10.1.3 stable). It has happened across all the different radios, 4.0.4 and up, and across several different kernels. Does anyone have suggestions, the phone isn't really usable if people can't get in touch and I'm unaware that they can't.
EDIT: When I go into the phone info menu *#*#4636*#*# when the radio has no data, it says preferred network is "unknown." If I change it, the setting immediately goes back to unknown.
U might need to go through the insurance and get another one.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
eriscentro said:
Hey guys - my VZW Gnex (it's a refurb to replace my old one with a bad screen) has been having excessive network dropouts lately. When I boot the phone, it doesn't acquire signal for over a minute, when I place a call I lose signal afterwards, and data drops out randomly. The device will say it's connected (blue bars), although I cannot use the internet. Also, it'll randomly loose cellular connectivity, although indicate that it has signal. I'll go to send a text and it'll immediately have send errors, and I am unable to make or receive calls, even though it shows I have signal. To fix, a reboot is always necessary. This has happened on 4.3 (crDroid) and 4.2.2 (CM 10.1.3 stable). It has happened across all the different radios, 4.0.4 and up, and across several different kernels. Does anyone have suggestions, the phone isn't really usable if people can't get in touch and I'm unaware that they can't.
EDIT: When I go into the phone info menu *#*#4636*#*# when the radio has no data, it says preferred network is "unknown." If I change it, the setting immediately goes back to unknown.
Click to expand...
Click to collapse
This is a known issue with 4.3 ROMs. I'm not sure about 4.2.2. It looks like CM 10.2 may have a fix for it in the next nightly. One known fix is to edit build.prop to include
ro.telepohny.default_cdma_sub=0
Thank has worked for me.
dlabadie said:
This is a known issue with 4.3 ROMs. I'm not sure about 4.2.2. It looks like CM 10.2 may have a fix for it in the next nightly. One known fix is to edit build.prop to include
ro.telepohny.default_cdma_sub=0
Thank has worked for me.
Click to expand...
Click to collapse
I've added that line, doesn't help