Summary of baseband bugs in Nexus s
1) Having network selection set to manual ( i.e selecting 302490) will result in No Service on a reboot.
Solutions:
- Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker)
- OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal.
Solutions:
-Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery.
-Use NoBars to accomplish the same thing ( tasker gives you a bit more flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-battery-saver/com.tomdryer.nobars
- Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane-edit/net.cenkalti.airplane
3) WCDMA perferred does not work.
- No solution.
These are all software bugs/baseband so hopefully they will be resolved soon by google. Voice your concern on the google mobile forum though. These are reproducible on stock, and any ROM.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
i have yet to encounter the issue on point 1
but yes i do find issue 2 very often, indeed i have set mine to WCDMA only to prevent roaming
since i installed NoBars, it seems to have taken care of the problem
need a few more days to confirm
AllGamer said:
i have yet to encounter the issue on point 1
but yes i do find issue 2 very often, indeed i have set mine to WCDMA only to prevent roaming
since i installed NoBars, it seems to have taken care of the problem
need a few more days to confirm
Click to expand...
Click to collapse
Still unacceptable that we even have to do that. This is a flagship phone and these are pretty major issues. What goods a phone that cant get signal. Pretty annoyed especially since this is a 500$+ phone.
This comes from these 2 topics
[Q] Nexus S & WIND Mobile 3G Connection Issues http://forum.xda-developers.com/showthread.php?t=928661
Sudden Loss of Data on Nexus S http://forum.xda-developers.com/showthread.php?t=882518
it's worth a topic of its own as it very clear states all the issues and work around to the problems
johoja said:
Still unacceptable that we even have to do that. This is a flagship phone and these are pretty major issues. What goods a phone that cant get signal. Pretty annoyed especially since this is a 500$+ phone.
Click to expand...
Click to collapse
I agree with that
Is there a bug report opened on google code?
I can confirm the second problem.... :/
ekerazha said:
Is there a bug report opened on google code?
Click to expand...
Click to collapse
I believe google code is for AOSP issues, for Nexus S related issues I would do the following:
1) Tweet the issue to googlenexus, and romainguy
2) Post on the forum http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
I'm surprised they still haven't acknowledged it.
johoja said:
I believe google code is for AOSP issues, for Nexus S related issues I would do the following:
1) Tweet the issue to googlenexus, and romainguy
2) Post on the forum http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
I'm surprised they still haven't acknowledged it.
Click to expand...
Click to collapse
The problem is distinguishing what is a Nexus S hardware bug and what is a Gingerbread AOSP issue, especially since the NS is the only device running 2.3.x, so we can't compare our bugs to other devices to determine if it's AOSP or device-specific.
Google does tend to close bug reports out as saying it's not a code bug.
The support/help forum does also tend to get more active replies from Google employees than you ever see on the code site.
distortedloop said:
The problem is distinguishing what is a Nexus S hardware bug and what is a Gingerbread AOSP issue, especially since the NS is the only device running 2.3.x, so we can't compare our bugs to other devices to determine if it's AOSP or device-specific.
Google does tend to close bug reports out as saying it's not a code bug.
The support/help forum does also tend to get more active replies from Google employees than you ever see on the code site.
Click to expand...
Click to collapse
Going through forums and bug reports & according to AllGamer the Samsung Galaxy S devices suffered the same issues initially but were fixed with updates (and as we all know SGS does not have 2.3+ (Also I'm not sure if it was completely fixed). Since the NS is pretty much the same device I'm not surprised.
See this for example:
http://www.howardforums.com/showthr...-after-disconnected-to-Mobilicty-to-reconnect
The work around for SGS users was a little bit better though they have an option to specify WCDMA Bands i.e) 1700mhz only. That seems to fix the problem on SGS. Unfortunately 'Pure' Google doesn't have that option built in. ( I can't confirm the fix only going on what I've read. Don't have a SGS)
Based on that I'm going to go ahead and say its not a Gingerbread issue, it's more of a baseband issue. Also I think you can flash Gingerbread to an N1 (Cyanogenmod) I sold my N1 so can't verify for sure its not a Gingerbread only issue.
back on the SGS, the problem was only with 2.1 Eclair
after upgrading to 2.2 Froyo all those voice/network dropped issues were resolved
so it's possible we might be seeing a re-lapse of the problem in 2.3 GingerBread, perhaps 2.4 might fix this?
johoja said:
Going through forums and bug reports & according to AllGamer the Samsung Galaxy S devices suffered the same issues initially but were fixed with updates (and as we all know SGS does not have 2.3+ (Also I'm not sure if it was completely fixed). Since the NS is pretty much the same device I'm not surprised.
See this for example:
http://www.howardforums.com/showthr...-after-disconnected-to-Mobilicty-to-reconnect
The work around for SGS users was a little bit better though they have an option to specify WCDMA Bands i.e) 1700mhz only. That seems to fix the problem on SGS. Unfortunately 'Pure' Google doesn't have that option built in. ( I can't confirm the fix only going on what I've read. Don't have a SGS)
Based on that I'm going to go ahead and say its not a Gingerbread issue, it's more of a baseband issue. Also I think you can flash Gingerbread to an N1 (Cyanogenmod) I sold my N1 so can't verify for sure its not a Gingerbread only issue.
Click to expand...
Click to collapse
First off, I think we need to stop saying SGS and Galaxy S phones. There are numerous existing models, and they all have slightly different hardware, including the radio chips. There are also at least four new as yet un-released, but announced models that will be called Galaxy S phones as well, and they are significantly different than the ones that are derivative of the original i9000.
For example, I have the Galaxy S i9000, and I usually specify that when referring to it. This is important, because the issues and solutions on the Galaxy S Vibrant are not the same.
My i9000 came with Eclair, and got updated to Froyo, and I NEVER had these problems with the phone on AT&T's US network. My friend is using a US Vibrant on AT&T as well and he never has had the issues, either on Eclair or Froyo. So I'm not so sure you can throw blanket statements like that around. But that's true of any issue.
More directly to your response to me, I didn't say this particular issue was or wasn't a hardware or software issue...my only point was that since the Nexus S is the only phone to have Gingerbread officially, the line between what is a device problem and what is a GB general software problem are definitely blurred. Any third party builds from the GB source may have had issues fixed on them. I remember from my N1 days that cyanogen often addressed Google bugs in his builds...
distortedloop said:
First off, I think we need to stop saying SGS and Galaxy S phones. There are numerous models, and they all have slightly different hardware, including the radio chips.
For example, I have the Galaxy S i9000, and I usually specify that when referring to it. This is important, because the issues and solutions on the Galaxy S Vibrant are not the same.
My i9000 came with Eclair, and got updated to Froyo, and I NEVER had these problems with the phone on AT&T's US network. My friend is using a US Vibrant on AT&T as well and he never has had the issues, either on Eclair or Froyo. So I'm not so sure you can throw blanket statements like that around. But that's true of any issue.
More directly to your response to me, I didn't say this particular issue was or wasn't a hardware or software issue...my only point was that since the Nexus S is the only phone to have Gingerbread officially, the line between what is a device problem and what is a GB general software problem are definitely blurred. Any third party builds from the GB source may have had issues fixed on them. I remember from my N1 days that cyanogen often addressed Google bugs in his builds...
Click to expand...
Click to collapse
I was referring to the Vibrant. Maybe it only affects that specific model as well.
http://forum.xda-developers.com/showthread.php?t=819589
http://forum.xda-developers.com/showthread.php?t=772849
I just think its a little suspicious that they have the very similar issues.
The Vibrant and the Nexus S both have the same baseband platform -
Infineon X-Gold X616 (PMB9801).
Either way. Your right until we actually hear from Google about the issue this is all speculation. Hope they fix it soon
Maybe the issue is only present for the phones that have the chipset to handle AWS ( 1700mhz)
Now the cellular radio freezing issue I complained is identified as #2? Good!
Hopefully the forthcoming radio ROM will fix this issue.
johoja said:
Summary of baseband bugs in Nexus s
1) Having network selection set to manual ( i.e selecting 302490) will result in No Service on a reboot.
Solutions:
- Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker)
- OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal.
Solutions:
-Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery.
-Use NoBars to accomplish the same thing ( tasker gives you a bit more flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-battery-saver/com.tomdryer.nobars
- Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane-edit/net.cenkalti.airplane
3) WCDMA perferred does not work.
- No solution.
These are all software bugs/baseband so hopefully they will be resolved soon by google. Voice your concern on the google mobile forum though. These are reproducible on stock, and any ROM.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
Click to expand...
Click to collapse
johoja said:
I just think its a little suspicious that they have the very similar issues.
The Vibrant and the Nexus S both have the same baseband platform -
Infineon X-Gold X616 (PMB9801).
Either way. Your right until we actually hear from Google about the issue this is all speculation. Hope they fix it soon
Maybe the issue is only present for the phones that have the chipset to handle AWS ( 1700mhz)
Click to expand...
Click to collapse
That is interesting.
I wonder if it's actually only with those that handle AWS while actually connecting to AWS. As I mentioned in my previous post, my friend is using a Vibrant I setup for him on AT&T and he has no issues like the ones described above.
I think there's just some level of black-magic or voodoo or karma with cell phones; for some of us, few issues, for others, nightmares.
Changed on its own from WCDMA only to GSM/CDMA auto (PRL)
so i was manually sync-ing my gmails
and all of the sudden i see i was from HSPDA and BAM! it changed to R (roaming)
i was like WTF !!!!!!!!!
so i immediately switched to airplane mode, and back to cycle it to see if it changes back and no, it was still stuck in Roaming mode.
so i ended up manually changing it manually back to WIND from the network selection screen
and then i went to check on *#*#4363#*#* and found out it was not on WCDMA only
which makes it really weird, as i didn't change it at all.
this is the first time it has done that to me.
have any body else seen this problem before?
good thing is, it did not enable data roaming, so hopefully i did not incur any roaming charges, ... i guess i'll see when the monthly Bill arrives
Mine switches occasionally when I lose reception. Like you, I generally keep mine on wcdma only. I have no idea why this phone does this, as it has happened on the stock rom, modaco, and cyanogenmod.
My old Nexus One never did this. Luckily it seems like that problem hasn't happened for me in the last week or two, so it isn't very common.
Never had this but on my nexus 1 I would use auto prl and would get more battery. I changed it on my nexus s and it goes back to wcdma.
If u have roaming off, u should be good.
it might be another bug related to the baseband
perhaps more people can confirm and or reproduce the issue
AllGamer said:
it might be another bug related to the baseband
perhaps more people can confirm and or reproduce the issue
Click to expand...
Click to collapse
Ive had it happen once or twice. Not sure how to reproduce it. I got annoyed because once that happens you have to re-enter the SMSC.
I leave mine on GSM/cdma (prl) and manually select the network I want. That keeps it from roaming as well.
Related
Tried searching but no luck. I was using JF ADP 1.5 and my location in google maps without using GPS was pretty accurate and up to date. I put the JF tmobile cupcake on my G1 and now my location barely even updates let alone be even remotely accurate. should I wipe my phone and see if that helps? I think I have the new radio installed. How can I verify the new radio version?
Anyone? I rely on this feature quite a bit.
Look at upgrading to jf 1.51 3.3.2 by cyanogen or thedudes 1.2a there are no location issues that I am aware of
power down
press and hold power and camera button.
you should read the radio ending "26I"
that's the lastest radio.
mrcrs said:
power down
press and hold power and camera button.
you should read the radio ending "26I"
that's the lastest radio.
Click to expand...
Click to collapse
Okay, I have the newest radio then.
Id like to just keep using this ROM. I'm just going to wipe it in a little while.
Crusher16 said:
Okay, I have the newest radio then.
Id like to just keep using this ROM. I'm just going to wipe it in a little while.
Click to expand...
Click to collapse
Well, I wiped my phone and that didn't work. Then I went back to JF ADP 1.5 and still now luck. Anyone else have any ideas?
ubernicholi said:
Look at upgrading to jf 1.51 3.3.2 by cyanogen or thedudes 1.2a there are no location issues that I am aware of
Click to expand...
Click to collapse
Done. Still the same thing.
Crusher16 said:
Anyone else have any ideas?
Click to expand...
Click to collapse
Nope and it's not your phone. It's T-Mobile. I asked here, no response (huge surprise, I know). I've asked on TMobile's "official" forums, no answer. I've asked on multiple cell phone boards, no answer. I do not want to call Customer Service AGAIN because they will blame my phone despite the fact I have 3 of them right here, right now all doing the same thing and all with various builds. Just for reference, he's one of my previous posts:
Started happening a few weeks ago. Applications that rely on the My Location service within Android fail because Android isn't receiving a location. Examples of this are the Google homepage and the multitudes of weather apps when set to Current Location. I'm inclined to believe it's a tower problem for a few reasons.
* I have multiple G1's (2 G1's,and a Dev phone) having the same issue while in close proximity to each other even after fresh Factory Resets on all of them. (and with various builds including OTA builds)
* The problem disappears when switching to 2G (confirmed with a Market app called "Cellfinder"). Cellfinder will find the tower ID as shown below but no location reported from the tower. If I bump it down to 2G the LAC and CID stay the same but are now reporting the tower location.
* The DDMS log tool within the Android 1.5 SDK shows that Android is at least trying to get a location lock but failing with various LocationManager errors saying no location was found.
* The phone's are getting service and with BetterCut & Cellfinder I can see the associated tower's LAC and CID which leads me to believe that the 3G portion of the towers are simply not reporting location back to the phone.
Customer service wants to RMA the G1 I have on record. The phone(s) is(are) not broken so I declined. I'm at a loss on who to talk to next. BTW, despite my unresolved issue your guys' techs are fantastic. I love the up beat attitudes and great service.
Click to expand...
Click to collapse
uberingram said:
Nope and it's not your phone. It's T-Mobile. I asked here, no response (huge surprise, I know). I've asked on TMobile's "official" forums, no answer. I've asked on multiple cell phone boards, no answer. I do not want to call Customer Service AGAIN because they will blame my phone despite the fact I have 3 of them right here, right now all doing the same thing and all with various builds. Just for reference, he's one of my previous posts:
Click to expand...
Click to collapse
Ah thanks for the info. I was beginning to think it wasn't something about the phone. I guess I'll give them a call, just to show that this issue does exist. Its a shame I cant use it though.
Crusher16 said:
Ah thanks for the info. I was beginning to think it wasn't something about the phone. I guess I'll give them a call, just to show that this issue does exist. Its a shame I cant use it though.
Click to expand...
Click to collapse
It is a shame. Every single background service that requests My Location is now hosed.
I am in the same boat with you guys. I can get a GPS lock, but no radio lock. And since I too rely heavily on this feature it's a major problem. What I'm concerned about is that, if I understand correctly, it is not working with a non-root phone as well now? I rooted two days ago, and before that it was fine. It's about to become a deal breaker for me. May have to un-root if it will work like that. =(
BTW JF1.51CBR43 ROM
Ok, may have spoke too soon. So here's what worked for me. If you use something like toggle settings or make a custom toggle this is not TOO inconvenient. I put my settings to 2G only, and wahla!!!!! I have My Location back and all my other location based software works.
Hope this helps! Now, if I can just get the damned Bluetooth to work, I won't have to unroot. Yep, may be another deal breaker for me.
Black G1 - Rooted
JF1.51 CRB43
Ahome - home app
mikfento said:
Ok, may have spoke too soon. So here's what worked for me. If you use something like toggle settings or make a custom toggle this is not TOO inconvenient. I put my settings to 2G only, and wahla!!!!! I have My Location back and all my other location based software works.
Hope this helps! Now, if I can just get the damned Bluetooth to work, I won't have to unroot. Yep, may be another deal breaker for me.
Black G1 - Rooted
JF1.51 CRB43
Ahome - home app
Click to expand...
Click to collapse
1) I already posted that this problem does not exist with 2G in this very thread.
2) Just this morning I started to get location data with 3G however it's not nearly as accurate as 2G. While this works fine for city level information such as weather it's rather crude.
It's been happening for a while now. I can have full signal on H, then suddenly no H, E, or G. Data does not reconnect automatically; I have to force it by switching Airplane mode On/Off. I saw something in the forums about a radio update, but I heard that removes ability to change permroot/S-OFF. Please help me clarify this, and if there is an update, is it safe and should I install it.
Stock ROM, temp-rooted with Visionary and permrooted with HBOOT/WPTHIS_OTA method. Kernel is the one linked in my signature thing [1497KHz] and pushed Wi-Fi module. Hopefully that's enough info. Let me know if you need my SSN# ...lol
Sent from my T-Mobile G2 using XDA App
Does it do this when the phone is still???
Max. (Desire z)
Don't see how that correlates with my problem? Still or moving, it happens randomly.
Sent from my T-Mobile G2 using XDA App
I have been experiencing this exact problem quite often over the last two weeks. I am using CM 6.1.1 in Chicago.
same situation happens to me...nvr seem to have a solid 3g/H in my house. While my blackberry will be having 3G all day. The g2 will fluctuates from H -> G -> E and stays like that. So annoying that ruins the experience of having a good data phone.
Same problem here! It happens from time to time, I have to switch off/on data to get reconnected.
Also happens when I turn off wifi after a long period of use, It won't reconnect to the carrier's data.
I had this when I switched over to CM 6.1.1. I thought it was CM so I flashed my backup, then decided to try it again. The problem I found was Pershoot's kernel. My data connection would drop and come up on it's own and was happening while I was using data. I've been running CM 6.1.1 with it's kernel and haven't had this problem since.
Same here running latest Virt (tmous g2) and I *think* it's running a pershoot hybrid.
I have never run Pershoot's kernel, and have always used the kernel included with CM. It seems to be recent (last two weeks) problem for me. The phone cycles from 3G->G->E->3G->H. The worst, however, is when it shows 3G->H but cannot connect to anything. The only solution is to turn off the data and let it reconnect.
I think it might actually be network related and not hardware / software. Maybe too many new phones activated around the Holidays? The reason I think this is that my Nexus One keeps having similar problems --- even on different ROMs.
Could be either?
I used to be on Mobilicity in Canada and experienced this (random disconnects from data several times a day, wouldn't automatically reconnect), switched to Wind and I haven't had this problem.
Stock G2 ROM, unlocked, s-off, su visionary
Data Problems...
Ignore my signature I'm currently on G2.
I think the problem you all have might be a TMobile problem.
I live in Madison TN / Nashville TN and I been having that data drop problem for going on a year now. Happended on every phone I been on Mytouch 3G Mytouch Slide Samsung Vibrant HD2 and now I'm on the G2 that I bought yesterday. Also had the same problem on a Nexus one.
The situation was that I will have all my bars and a 3G/H symbole and my connection would just fall a sleep with the 3G still in corner. Put phone in airplane mode and take it out airplane mode and my downloads will resume.
This process would happen after 15 min or 20 min of constant data.
2 days ago I started calling tmobile to get this fixed. Told them I didn't have this problem on ATT and Verizon so they put in a service ticket with the engineers and they claim it should be resolved in the next couple days if mot to give them a call back and to forward my call straight to level 2 tech support.
More people should complain about it.
That happended across atleast 5 different pda phones and 3 different sim cards. Yeah some of the phones had custom roms but each phone shouldn't have the same symptons.
The cellular towers in my area must really have a problem and I'm expecting a credit on my account lol.
PS connection is perfect on Edge though... Just slow...
Could it be because of overclock?? What if a certain CPU speed doesn't play well with the radio?? Just a thought...
Sent from my T-Mobile G2 using XDA App
DJAeroX26 said:
Could it be because of overclock?? What if a certain CPU speed doesn't play well with the radio?? Just a thought...
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
For that to happen to me on 5 different devices that will tell you that CPU speed has nothing to do with it. Best I can say is to reset your phone to stock and give TMobile a call and let them know the situation. If you dont, nothing will be done about it.
I say to return to stock because if you dont, there reps will try there best to put the blame on you and the custom software. But from my experience being on Nexus One / MyTouch Slide / MyTouch 3G / Samsung Vibrant / HD2 / G2 all having the same exact problem????
Yeah the problem is on TMobile end...
hypersonicx said:
For that to happen to me on 5 different devices that will tell you that CPU speed has nothing to do with it. Best I can say is to reset your phone to stock and give TMobile a call and let them know the situation. If you dont, nothing will be done about it.
I say to return to stock because if you dont, there reps will try there best to put the blame on you and the custom software. But from my experience being on Nexus One / MyTouch Slide / MyTouch 3G / Samsung Vibrant / HD2 / G2 all having the same exact problem????
Yeah the problem is on TMobile end...
Click to expand...
Click to collapse
Is it the same EXACT problem I'm describing? Or are you talking about general reception? Because some people on here with different ROMs (or radios) have mixed results. I'm in an HSPA+ area with full signal usually, but I keep having my data disconnecting. After a while it comes back, but I don't like to wait that long. I just switch radio on/off. :/
DJAeroX26 said:
Is it the same EXACT problem I'm describing? Or are you talking about general reception? Because some people on here with different ROMs (or radios) have mixed results. I'm in an HSPA+ area with full signal usually, but I keep having my data disconnecting. After a while it comes back, but I don't like to wait that long. I just switch radio on/off. :/
Click to expand...
Click to collapse
Yeah it sounds like the same exact problem to me which I had on all those other phones too. Im like you I dont feel like waiting so I switch to airplane mode on and off and the data comes back.
Or Il just drop to 2G Edge only and the connection is stable just slow though.
I couldnt find a solution online so now I got tmobile reps in the picture to get this resolved for my area though.
Count me in. I HAD a BB 9700 and it behaved the same way you guys are talking about but i didn't have to set it to airplane mode to reset the connection. I do however have to restart my G2 sometimes to get it connects to Tmobile network again. It is such an inconvenience.
I'm on stock rooted rom by fastludeh.
androidtoy09 said:
Count me in. I HAD a BB 9700 and it behaved the same way you guys are talking about but i didn't have to set it to airplane mode to reset the connection. I do however have to restart my G2 sometimes to get it connects to Tmobile network again. It is such an inconvenience.
I'm on stock rooted rom by fastludeh.
Click to expand...
Click to collapse
Yeah TMobile need to get this fixed. I plan on giving them a call back on Monday or Tuesday since my 3G connection still continues to drop.
Im currently on ALL stock on the G2. Havnt did any modifications yet.
Would changing the radio help? i see there is other radio firmware available...not sure if that will do anything for our phones. Currently sticking to my 9700 for now until this issue is fixed or if i get bored of the 9700 and jump back to the G2
fryrice8850 said:
Would changing the radio help? i see there is other radio firmware available...not sure if that will do anything for our phones. Currently sticking to my 9700 for now until this issue is fixed or if i get bored of the 9700 and jump back to the G2
Click to expand...
Click to collapse
Na I dont think changing radio will work. I tried multiple radios and custom roms on the HD2 and same situation over and over.
Having problems with everything connection on my g2 it started happening like two weeks ago. Random no service for like a minute then full bars and hspa never use to do it but now it does frustrating as heck oh on a stock froyo too wtf
Sent from my T-Mobile G2 using XDA App
First of all, hello ! I'm new around here and I just stumbled upon a problem I guess on my new phone ( the L5 II E460 ) so I decided to ask your opinion on this one cause I don't have that big knowledge about smartphones and androids to be honest
The thing is: Sometimes when I use the wi-fi connection home and toggle between the 3G data connection from once in a while the 3G Data stops working.The wi-fi connects back without no issues but if I switch to data it won't show the 3G sign up or H and I can't access anything unless I restart the phone, then everything goes back to normal ( to be honest this happened to me only twice and I have the phone since a month but it's still frustrating and first I thought my phone may be broken but after a little google search I found out that many people have this problem )
What other solutions are to stop this " problem " or whatever it is to occur again ?
Thanks.
So,no one nothing?
PeterHaze said:
So,no one nothing?
Click to expand...
Click to collapse
I toggled multiple times just to try what you reported but it didn't happen to me.
Did you update your firmware? I also recommend also a full-wipe:
1 Turn the power off.
2 Press and hold the Power/Lock key + Volume Down key + QuickButton.
3 When the LG Logo appears on the screen, release all keys.
I didn't do any firmware update atm, it's still the Jelly Bean 4.1.2
It doesn't happen often,only from time to time and the airplane mode on and off toggle seems to resolve the problem so I'm guessing there is some problem between the wifi and data settings sometimes.
PeterHaze said:
I didn't do any firmware update atm, it's still the Jelly Bean 4.1.2
It doesn't happen often,only from time to time and the airplane mode on and off toggle seems to resolve the problem so I'm guessing there is some problem between the wifi and data settings sometimes.
Click to expand...
Click to collapse
Do the update (through software update in your phone). It stays at Jelly Bean 4.1.2 it's just an update to it. Maybe it solves your problem, as it may have been a known bug. I've updated and I don't have your problem, maybe it was solved. Also do a full wipe afterwards.
Ditto... almost!
mircea89fzr said:
Do the update (through software update in your phone). It stays at Jelly Bean 4.1.2 it's just an update to it. Maybe it solves your problem, as it may have been a known bug. I've updated and I don't have your problem, maybe it was solved. Also do a full wipe afterwards.
Click to expand...
Click to collapse
I have the LG-E460 (L5 MkII) and JB 4.1.2 updated to May 28th 2013. It is just 10 days old so I have 4 days left to decide to keep or return. This is my 1st ever smartphone, so I am without any doubt a NOOB in more ways than one.
If I understand correctly, my problem seems to be similar. If I am updating the weather, twitter or facebook etc, using my home wi-fi, every now and then I get a message "Network Unavailable", despite FULL signal on my network, and the only way to restore it is to turn Wi-Fi off, then on.
It seems to work just fine by leaving Wi-Fi off, thereby using the mobile data permanently.
Could this possibly be anything to do with the type of network in use? ie, WPA2-PSK etc?
Regards to all,
Mike
MLHiFi said:
I have the LG-E460 (L5 MkII) and JB 4.1.2 updated to May 28th 2013. It is just 10 days old so I have 4 days left to decide to keep or return. This is my 1st ever smartphone, so I am without any doubt a NOOB in more ways than one.
If I understand correctly, my problem seems to be similar. If I am updating the weather, twitter or facebook etc, using my home wi-fi, every now and then I get a message "Network Unavailable", despite FULL signal on my network, and the only way to restore it is to turn Wi-Fi off, then on.
It seems to work just fine by leaving Wi-Fi off, thereby using the mobile data permanently.
Could this possibly be anything to do with the type of network in use? ie, WPA2-PSK etc?
Regards to all,
Mike
Click to expand...
Click to collapse
I experience wi-fi connection losses too, but not that often and I can live with it. If it's too often for you, return the phone as it is a bug. Others have reported it too (see the lg uk website for our phone).
mircea89fzr said:
I experience wi-fi connection losses too, but not that often and I can live with it. If it's too often for you, return the phone as it is a bug. Others have reported it too (see the lg uk website for our phone).
Click to expand...
Click to collapse
This is, sadly, the conclusion I have come to. Apart from this one issue, I love the phone and it was the only unit at this monthly price-point that, in reviews anyway, was any good! The other handsets were Samsung Galaxy Ace, HTC Desire C and Huawei Ascend Y201.
I know reviews are not always the best way to choose but, out of the four, the L5 seemed to be "the one" for me, particularly after reading users reviews and studying the spec. sheets for all.
I'm trying to save money, not spend more, so the L5 will have to stay. Because it is new to me, I'm using it WAY more than is normal, just to get to know it, so in normal use I can probably put up with it.
Thank you for letting me rant on; and thank you for a great site.
Best regards, to all,
Mike
MLHiFi said:
This is, sadly, the conclusion I have come to. Apart from this one issue, I love the phone and it was the only unit at this monthly price-point that, in reviews anyway, was any good! The other handsets were Samsung Galaxy Ace, HTC Desire C and Huawei Ascend Y201.
I know reviews are not always the best way to choose but, out of the four, the L5 seemed to be "the one" for me, particularly after reading users reviews and studying the spec. sheets for all.
I'm trying to save money, not spend more, so the L5 will have to stay. Because it is new to me, I'm using it WAY more than is normal, just to get to know it, so in normal use I can probably put up with it.
Thank you for letting me rant on; and thank you for a great site.
Best regards, to all,
Mike
Click to expand...
Click to collapse
Well, I haven't found a cure, but I have found a way round it!
It would appear to be WPA that's causing the intermittent, but common, "No Connection" message... I changed to WEP and it has now been perfect for over 24 hours.
I think I've got this right: in WEP a "key" is only sent at the outset! With WPA, a key is generated every so often and it must be that which is upsetting the L5 and causing it to "have a fit"
Any thoughts would be welcome... I do know the pitfalls of using WEP, but it has proved a point... at least I think it has.
Regards,
Mike
My 6p has worked well for some time, but for a while now it will just constantly drop carrier signal, it seems to do it more when an app is sending or receiving data. I thought maybe it was purenexus or the ex kernel, so I updated both to the current releases, there are no other mods besides root. I've never ran stock on it and the issue just started out of nowhere one day. It will usually pickup signal when it drops. Sometimes to speed it along I'll put it in airplane and then back. Sometimes that doesn't work and a reboot is needed. It's also on the latest vendor image because AFAIK that includes the modem radio. I'm kinda out of ideas, I'd like to avoid dealing with the carrier if I don't need to (t-mobile us)
Also, when on WiFi I noticed that cellular never seems to drop.
Having the same problem. It started recently and I'm not sure why. I'm on Cricket.
gr546jmn5 said:
My 6p has worked well for some time, but for a while now it will just constantly drop carrier signal, it seems to do it more when an app is sending or receiving data. I thought maybe it was purenexus or the ex kernel, so I updated both to the current releases, there are no other mods besides root. I've never ran stock on it and the issue just started out of nowhere one day. It will usually pickup signal when it drops. Sometimes to speed it along I'll put it in airplane and then back. Sometimes that doesn't work and a reboot is needed. It's also on the latest vendor image because AFAIK that includes the modem radio. I'm kinda out of ideas, I'd like to avoid dealing with the carrier if I don't need to (t-mobile us) Also, when on WiFi I noticed that cellular never seems to drop.
Click to expand...
Click to collapse
Several threads on the same dropping, cycling, having to reboot issue affecting T-Mo. Fairly new one here. You can also find a huge whinge fest thread here where every T-Mo user has tried every radio going back a year. If I were affected, I would make sure the issue was present on a bone stock device, then I would find a friend/relative and switch to a different carrier SIM, preferably a non-MVNO to see if it was resolved. It shouldn't take more than a few hours. At that point you're going to know whether it is your carrier or your device. If it is the carrier, provide them this information and ask for new SIM to be provisioned. They should also be able to look up your usage history and maybe find a solution for you. The beauty of owning a carrier unlocked phone is you can always get another carrier. If all this tells you it is a hardware issue, then you have already collected the evidence needed for a warranty claim.
Anyone else seeing this on occasion? It seems like every few days I'll have some sort of radio issues on this device, and it's continued despite having all recent software updates.
Sometimes wifi or LTE will suddenly die, even though both icons appear completely normal in the status bar...a handful of times I've had the mobile network suddenly die and have an 'x' over the status bar icon while showing zero bars. Sometimes a toggle off and back on of the problematic radio will fix the issue until next time, and sometimes a full reboot is necessary.
Aside from the minor screen tinting issue and this issue I really love the phone, but it does become somewhat annoying. And I know it's not just this device, as both OP8P phones I've had have done the exact same thing, and my wife's OP8 does the same thing too....so it's gotta be a software/VZW/etc. thing. Is anyone else here seeing similar things and/or found any resolution other than having to toggle/reboot? Thanks!
I've noticed this same thing too (OP8P on VZW) but for me it seems to only really happen at work which I find odd. Haven't found any permanent solutions myself though unfortunately. Just kinda randomly happens occasionally.
OP is working on a fix, at least for t-mobile germany. Read that in the german t-mobile support forums. Likely a bug in the SD modem. However I don't know if that addresses the wifi issue.
ch1llahh said:
OP is working on a fix, at least for t-mobile germany. Read that in the german t-mobile support forums. Likely a bug in the SD modem. However I don't know if that addresses the wifi issue.
Click to expand...
Click to collapse
Interesting...mobile data seems to be the far more often culprit in my experience (and more critical, since certain things like SMS/MMS/calls/etc. get killed dead if that goes out). Any chance you still have the link for that post?
ohlin5 said:
Interesting...mobile data seems to be the far more often culprit in my experience (and more critical, since certain things like SMS/MMS/calls/etc. get killed dead if that goes out). Any chance you still have the link for that post?
Click to expand...
Click to collapse
https://telekomhilft.telekom.de/t5/...gnal-verbindungsabbrueche/m-p/4681585#M211293
Here you go.
ohlin5 said:
Anyone else seeing this on occasion? It seems like every few days I'll have some sort of radio issues on this device, and it's continued despite having all recent software updates.
Sometimes wifi or LTE will suddenly die, even though both icons appear completely normal in the status bar...a handful of times I've had the mobile network suddenly die and have an 'x' over the status bar icon while showing zero bars. Sometimes a toggle off and back on of the problematic radio will fix the issue until next time, and sometimes a full reboot is necessary.
Aside from the minor screen tinting issue and this issue I really love the phone, but it does become somewhat annoying. And I know it's not just this device, as both OP8P phones I've had have done the exact same thing, and my wife's OP8 does the same thing too....so it's gotta be a software/VZW/etc. thing. Is anyone else here seeing similar things and/or found any resolution other than having to toggle/reboot? Thanks!
Click to expand...
Click to collapse
I have the same problem, had it when i was unrooted took the software update and kinda fixit, then reverted back and rooted the phone and took the same update and still shows the same
Thing you going through