Hey together,
since 5 or 6 h I do have a problem:
My One stays everytime on 4G, no change to H,3G or Edge. Means, I can not call out! Unfortunately there is no option to force my One to use only 3G, H, or Edge.
What can I do?
Best regards
Bembel80 said:
Hey together,
since 5 or 6 h I do have a problem:
My One stays everytime on 4G, no change to H,3G or Edge. Means, I can not call out! Unfortunately there is no option to force my One to use only 3G, H, or Edge.
What can I do?
Best regards
Click to expand...
Click to collapse
I don't have a ONE yet, but you should be able to turn off the mobile network in the settings. It is part of the Google design.
My current phone also has a setting under mobile network to change the network mode, which is the same is forcing it between 2g and 3g. There are play store apps that get you to that menu, although there appears to be no way to create a toggle for it from the desktop.
Hm, where can I find that point in my settings?
Bembel80 said:
Hm, where can I find that point in my settings?
Click to expand...
Click to collapse
Just lurking in these forums in anticipation of my HTC One arriving, so can't guide you through the menu yet, but I'd try these things first.
1. A quick toggle in and out of airplane mode.
2. A way to force a type of radio is to open your dialer and dial *#*#4636#*#* then select 'Phone Information'.
Scroll to the bottom and find the "Set preferred network type" drop-down menu.
I'm not sure what it will be set on as I do not have 4G, but in that menu should be an option to select GSM only. This will force the phone, if only for a while, to drop the 4G connection.
Occasionally my HTC One X would get stuck on 2G and this usually solved it. Hope it helps you.
Okay, I will try it. Thank you.
But is that normal behavior? Does it often happen?
BTW, I'm on TrickDroid 4.0.0!
Bembel80 said:
Okay, I will try it. Thank you.
But is that normal behavior? Does it often happen?
BTW, I'm on TrickDroid 4.0.0!
Click to expand...
Click to collapse
It is certainly not normal behaviour as your phone should be shutting down data to make voice calls. (Unless they have changed something recently or 4G works differently to 3G). In any case it should definitely not be preventing you from making calls!
You may be best served searching in the Trickdroid forum thread to see if anybody has had similar problems. Does that ROM have a custom recommended kernel? I haven't been in the development threads much yet.
Another thing to try if nothing works is to either flash the ROM back over the top after a cache and dalvik wipe, or extract the boot.img from the ROM if it is custom and re-flash that with fastboot. Don't forget to fastboot erase cache after flashing the kernel and before rebooting.
Then either quickly try another rom (take a backup first) or request a replacement SIM card from your network provider. I have had two faulty SIM cards, and one of them was a micro SIM with my One X which played hell with which radio it would use. It's rare but it does happen.
wnp_79 said:
It is certainly not normal behaviour as your phone should be shutting down data to make voice calls. (Unless they have changed something recently or 4G works differently to 3G). In any case it should definitely not be preventing you from making calls!
You may be best served searching in the Trickdroid forum thread to see if anybody has had similar problems. Does that ROM have a custom recommended kernel? I haven't been in the development threads much yet.
Another thing to try if nothing works is to either flash the ROM back over the top after a cache and dalvik wipe, or extract the boot.img from the ROM if it is custom and re-flash that with fastboot. Don't forget to fastboot erase cache after flashing the kernel and before rebooting.
Then either quickly try another rom (take a backup first) or request a replacement SIM card from your network provider. I have had two faulty SIM cards, and one of them was a micro SIM with my One X which played hell with which radio it would use. It's rare but it does happen.
Click to expand...
Click to collapse
My wife has an S3 mini international version that we use here in CA on 3G/4G. If her phone is on 3G, then it won't make calls. She has to reboot it when that happens. For the moment she is living with it. I may have to put a custom ROM on there for her eventually. Evidently the 3G won't allow simultaneous voice and data, and her phone detects the data and refuses to call.
I realize it is a different device, but it sounds like a similar problem.
With the above mentioned key combination I can choose appropriate networks. When I use GSM only it works like expected. But I do not want to use that combination everytime to switch from LTE to GSM. Is there any other solution?
No solution for my problem?
Bembel80 said:
No solution for my problem?
Click to expand...
Click to collapse
Take a look at these 2g/3g toggles, maybe it will help:
https://play.google.com/store/search?q=2g+toggle
Related
I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
Hi-I'm normally a Captivate user, asking here regarding my fiancee's phone, which we got after she smashed her third Aria.
I made sure I bought an AT&T 3G capable Nexus One, and then right away flashed CM7 on it.
Here are my issues:
1. The phone never ever says 3g. Always says E, even when we know we're 3g. (my captivate showing 3g, for example.)
2. There seems to be weird data issues---we use google voice for texting, and for some reason she'll often go hours or days before messages are delivered. Nobody else has this issue.
Is it possible I have a bad flash, or do I need a new modem/radio, anyone have any ideas? She doesn't really make any use of most of the CM7 features, maybe should just go back to AOSP...
At least regarding issue 1 there's a way to toggle data to stay in 3g or 2g mode through the default Power Control widget. It was a nightmare me because it doesn't change right away and I couldn't tell if it had switched bands or was in the process of doing so.
Can't help ya with the google talk issue since I don't use it.
It would help knowing what radio you are running before we let you know whether you should upgrade or not.
And how did you make sure you bought a 3G capable phone? Was it just in the description, or did you actually verify part numbers?
I would also verify you have a clean install by going into recovery and MANUALLY wiping the /system partition. If you want to be really thorough you can perform a Factory Reset/Data Wipe. This will completely erase your phone (including the OS). Then just install CM7 and the latest gapps.
Also, it does need to be said... just in case. As Eesti mentioned, make sure "Enable 2G" under Settings -> Wireless and Networks -> Mobile Network isn't enabled.
Thanks for the responses, sorry I"m just getting back.
It's currently running the 5.08 modem, which is the one everyone says to use unless you're in Korea, right?
I bought it new from a seller on ebay several months ago, and no I guess I didn't verify part numbers but I very specifically bought from a dude with perfect feedback and an auction that guaranteed it. How would I check part number?
I'll check the hard setting---I found the notification widget for 2g/3g, and it says "2g3g" with the light, tapping it makes it say 2g, so I'm assuming it's on.
I tried the "Force into 3g mode" setting by entering debug mode or whatever @ the dialer, setting it's set to WS....whatever...preferred, set it to "ws only" and it shows no signal @ all.
The s/n is behind the battery on the sticker.
For just one post that a lot a stuff well anyways, one problem I see is that on the XT860 rom it doesn´t read the SIM ID but on the XT862 it does. Since in my stupidity something tells me that that maybe related to the fact that is not reading the sim properly, I guess I will go into that route to find out what´s happening.
Just a quick update for ya.
Just installed minimoto version of the XT860 into my XT862 and it worked, the only problem is that it says invalid sim, but interestingly I can receive and make calls, signal indicator works better also. Anyways, I will try to find out how to get the rom to detect the sim correctly later.
Click to expand...
Click to collapse
Re phrasing the question, is there a way to make an xt862 into an xt860, since they are technically the same phone, just with different radios. What I want is to maybe use the phone.apk from the xt860 (that is only gsm/utms) into the xt862, in that way the phone won´t be looking for CDMA settings.
Is that possible?
Click to expand...
Click to collapse
Hi guys, I already searched on google, on xda, on droidforums and I haven´t found a way to disable the Global mode and CDMA mode, because in my country we don´t use CDMA anymore just GSM (GSM with sim card).(since 1990 something, the whole country moved to GSM).
I want my Droid 3 to just have the option between 2G and 3G (that would be Edge and 3G here), the only option I need would be GSM/UMTS. the other 2 options are CDMA and Global and I want to get rid of them.
Also because for some reason in some areas if I am in 3G and I get a call, the call will drop after making some weird sounds and I will get no signal for some minutes, and I will have to manually go into airplane mode and then out to get a signal again.
So I think, since the phone has this global mode thing, I though what the hell, let´s just disable the global mode and cdma mode and that will fix it. I mean, I believe that the phone instead of falling back to gsm mode (from 3G in lower signal areas) it goes directly to global mode, or even CDMA.
For more info, my phone is a Droid 3 XT862, from Verizon, unlocked and brought overseas, using the latest minimoto rom (I wanted something light so minimoto looked good).
I already applied some build.prop fixes and they worked but the ultimate fix would be to disable global and cdma mode.
Is it possible?
Click to expand...
Click to collapse
XDADoog said:
For just one post that a lot a stuff well anyways, one problem I see is that on the XT860 rom it doesn´t read the SIM ID but on the XT862 it does. Since in my stupidity something tells me that that maybe related to the fact that is not reading the sim properly, I guess I will go into that route to find out what´s happening.
Just a quick update for ya.
Click to expand...
Click to collapse
I was wondering if this is possible too, I know there is a line in the build prop that sets gsm to default, but it seems that my droid 3 will change that setting once in a while.
I, too, would like a permanent fix for this.
I do not use Minimoto, but I do use the XT883 radio. I have zero idea how I did it, but my Stock rom (I use SS) does NOT have the network choice. I assume this is what you were aiming for. It only shows the GSM options (2g/3g/auto toggle, Operator select, and APNs menu) and nothing for CDMA. Effectively making my Stock rom GSM only like the XT860. SIM reads fine, calls/text/data all work, no invalid SIM reading anywhere.
I've attached a couple screenshots to showcase this (if it's what you want) and my modified build.prop (incase this is actually what caused it). I've no idea what I've done to the build.prop, I've gone through and randomly changed things in my adventure of doing GSM tweaks, and I mainly use Maverick so my main modifications (that I remember) are there. Use at your own risk, though I doubt it'll do any harm (remove the .txt from the end and make sure you have proper permissions). Remember to backup your originals.
Interestingly enough im having the opposite problem on my XT862. I flashed Minimoto 1.7 to it and I get the "Invalid SIM, 911 calls only" message. Which is weird since my phone works off of CDMA. Anyone else have a clue to remedy this?
I tried your build.prop on the stock ROM with the xt883 radio, but after setting permissions and rebooting, I still have the CDMA network options present, plus the occasional "switch to global" prompt.
--posted from my phone
Skreelink said:
I do not use Minimoto, but I do use the XT883 radio. I have zero idea how I did it, but my Stock rom (I use SS) does NOT have the network choice. I assume this is what you were aiming for. It only shows the GSM options (2g/3g/auto toggle, Operator select, and APNs menu) and nothing for CDMA. Effectively making my Stock rom GSM only like the XT860. SIM reads fine, calls/text/data all work, no invalid SIM reading anywhere.
I've attached a couple screenshots to showcase this (if it's what you want) and my modified build.prop (incase this is actually what caused it). I've no idea what I've done to the build.prop, I've gone through and randomly changed things in my adventure of doing GSM tweaks, and I mainly use Maverick so my main modifications (that I remember) are there. Use at your own risk, though I doubt it'll do any harm (remove the .txt from the end and make sure you have proper permissions). Remember to backup your originals.
Click to expand...
Click to collapse
I have the 862 with the 883 radio and occasionally my phone will lose the cdma/global options entirely but then after a reboot they willl randomly reappear. The first time this happened I thought it was great lol cuz I don't need them anyways but then the box that normally pops up if you lose gsm signal asking you to switch to global popped up but said "no cdma signal detected, switching to gsm/umts mode" which is exactly the opposite of what it normally says. Kinda weird and I have no idea what would cause it since I'm using the build.prop found in the diy thread with no other changes that I would assume many others are using.
Sent from my XT862 using xda app-developers app
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
rmx36 said:
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
Click to expand...
Click to collapse
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first. EDIT: NOPE! Flashing the stock kernel from the ROM did not do it. Looks like total reformat/flash is next!
markwebb said:
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first.
Click to expand...
Click to collapse
I just got my Nexus 6 and I am also on Verizon and had the cell coverage drop too. I backed up my apps with titanium backup and did a factory reset and signal came back. I only had it for a day and went to Canada and on my way back to the US I noticed the cell bars were gone. I was just rooted and boot loader unlocked and otherwise stock. I read online that others had this issue when they got to places in the US that had little or no signal. I also noticed that under cellular network settings it loads up with Global under the preferred network type even though it has an option for "LTE (recommended)" and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected. With global selected it works perfectly with calls and LTE, so not sure what that means or if my selecting LTE made it drop the signal after going back from Canada.
Yep, total flash of factory image fixed it. Sigh. Early enough in the day for me to get everything set up again.
Same. About to do it too... I've done too many factory resets with this already. Kind of annoying.
I am in the same boat. Had no problems until I flashed bliss 1.5 then was stuck on 3g. Tried a clean flash of Slim and still stuck on 3g. I will try a stock rom but I am not very hopeful at this point. It's looking a like a reformat here as well :/
Ended up having to format everything and start from scratch again. I'm running a stock ROM now and in weary to try another cm ROM
Don't know if it'll help, but try LTE Discovery app in the Play Store. I use it from time to time to reset my data connection.
Having the same issue, running CM12 daily, have been for a week or so. Midday today it drops LTE, 3g data was working, then a few minutes later to no data. I didn't change anything, nothing new installed. I did reboot the phone at some point before this but that is all...
My only fix was to backup via trwp, restore stock rom, factory reset, reboot & let sim activate, then restore cm12 via twrp... it's a 20-30 min fix all said and done.... pita
Maybe its something Verizon is doing, because I didn't change anything and then next thing you know no data. I hope it's a simple fix for CM12 but I see this popping up more the last few days. Hopefully someone will figure it out. I like CM and prefer it over stock but I am not going to do this multiple times a day just to keep CM...
lohonda said:
...and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected.
Click to expand...
Click to collapse
I just checked and global is still an option for me. I've bounced back and forth, looking to see if anything changes..
Same thing has happened to me last night, lost connection to VZW cell and data. Looking at the field test menus, it seems like the SIM/device understand GSM but NOT CDMA anymore. So I believe the issue has something to do with that. Tried everything, but will nuke and repave most likely....also lost Global as well. and LTE Discovery shows GSM stuff nothing for CDMA
Tried the SIM in another device and it works so its not the SIM.
OK I tried a world of things to recover like some of you may have....its something in Userdata because if I flash everything but userdata it wont work. I am going to try and recover from the backup I had before this happened to see if that works....otherwise rebuild from scratch
will post back
UPDATE: So restoring a backup seems to be ok once you get the SIM back.
Having the same issue over here as well... After a month or AI of having the 6, now I randomly drop service where I would normally have full LTE. I almost NEVER get LTE now and am at most on H with a couple bars then it drops out again. Have also.noticed WiFi connection is very shakey.
Any one find a fix?
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
th3g0d said:
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
Click to expand...
Click to collapse
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
quidpro said:
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
Click to expand...
Click to collapse
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Edit: OK, just pinpointed MY issue. I have to wait for the "no service" text to change into "emergency calls only" before entering my pin or I don't have any service just the exclamation mark :/
th3g0d said:
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Click to expand...
Click to collapse
Thanks. I told her about it and she will give it a try, or just remove the pin altogether as a test. It is a weird issue. She is missing important calls from her elderly parents at night and it is rather frustrating. Turning wifi off also seems like a bad fix.
Every day I travel on the London Underground and obviously lose 4G signal when I am below ground.
Since the last update a week ago to 10.2.26.0, when I come back into a 4G area I cannot use any data services without either rebooting the phone or toggling Mobile data on and off, which is very frustrating.
The bars will show full 4G but no data will flow on any app until I do this.
Has anyone else experienced this?
Same on mine...
Yes same issue here
I had this happen to me earlier and it turned out that the access point settings had been altered at update from one firmware to the next. The system tries to install some generic APN-settings based on my operator’s name as my operator has no automatic way of installing them the usual way on this phone as it does on the more commonly used brands.
Check with your operator what the settings should look like and enter them under the access point settings for the sim-card if the current ones look off. Just an idea because I had the same problem going back to 4G from Wi-Fi. Reboot or airplane mode was the only thing to fix it for me. To be more exact it was the address for the setting “APN” that was wrong for me. The system had put an address that wasn´t a valid IP-address. Obviously, Xiaomi had tried to guess the address based on my operator name but got it wrong. As soon as I got the right setting in place all problems were gone.
This problem got worse as I had activated LTE voice calls. Before that it only happened occasionally, but with LTE-voice calls activated it happened every time I went from Wi-Fi to 4G.
gerhard_wa said:
I had this happen to me earlier and it turned out that the access point settings had been altered at update from one firmware to the next. The system tries to install some generic APN-settings based on my operator’s name as my operator has no automatic way of installing them the usual way on this phone as it does on the more commonly used brands.
Check with your operator what the settings should look like and enter them under the access point settings for the sim-card if the current ones look off. Just an idea because I had the same problem going back to 4G from Wi-Fi. Reboot or airplane mode was the only thing to fix it for me. To be more exact it was the address for the setting “APN” that was wrong for me. The system had put an address that wasn´t a valid IP-address. Obviously, Xiaomi had tried to guess the address based on my operator name but got it wrong. As soon as I got the right setting in place all problems were gone.
This problem got worse as I had activated LTE voice calls. Before that it only happened occasionally, but with LTE-voice calls activated it happened every time I went from Wi-Fi to 4G.
Click to expand...
Click to collapse
Mine is unchanged from update, and it's as indicated on my operator site
meti84 said:
Mine is unchanged from update, and it's as indicated on my operator site
Click to expand...
Click to collapse
So do you have:
wap.tim.it
or:
ibox.tim.it
gerhard_wa said:
So do you have:
wap.tim.it
or:
ibox.tim.it
Click to expand...
Click to collapse
Well, I didn't update my profile in a while, I have fastweb now... BTW I have apn.fastweb.it
meti84 said:
Well, I didn't update my profile in a while, I have fastweb now... BTW I have apn.fastweb.it
Click to expand...
Click to collapse
When I ping that address it comes up as invalid. You should see if there are alternatives.
gerhard_wa said:
When I ping that address it comes up as invalid. You should see if there are alternatives.
Click to expand...
Click to collapse
https://www.fastweb.it/myfastweb/as...ne-configura-internet-su-smartphone-o-tablet/
It's in Italian, but as you can see it's the official Fastweb guide
gerhard_wa said:
I had this happen to me earlier and it turned out that the access point settings had been altered at update from one firmware to the next.
Click to expand...
Click to collapse
Doesn't seem to be the issue. I am on EE here in the UK and the APN is correct. Can't see how toggling data off and on would resolve this if the APN was wrong anyway?
meti84 said:
https://www.fastweb.it/myfastweb/as...ne-configura-internet-su-smartphone-o-tablet/
It's in Italian, but as you can see it's the official Fastweb guide
Click to expand...
Click to collapse
I can see that but still, do a trace route for apn.fastweb.it and it can´t solve that address so there is something wrong with it. Anyway hope you will find the culprit of your problem!
I almost have the same problem .. after a phone call 4g disappears .. After the talk 4g comes back but the data connection does not work anymore .. Data off and switching on is the solution. I have send my phone back to the retailer i hope dee can fix the probleem.
I have the same issue.......latest Global Beta......switching data off and on for now....and hoping that fix is coming as it is annoying...
Okay so this is found to be experienced by others - how do we bring this to Xiaomi attention? Right now a phone that just randomly chooses to lose data capability is useless, as I lose notifications, messages, home automation activity prompts, Ring doorbell alerts, Nest smoke alarm alerts - pretty much renders the phone useless if I am not connected to WiFi, and the worst is not knowing it's stopped working till I try something.
One thing you could do if you have activated VoLTE is to deactivate VoLTE. If this makes a difference it sugests that something is wrong in your local configuration. Otherwise you may have to take it back to the seller.
Same problem here in Germany with o2.
I just found this solution to slightly another but very similar problem and I'm testing it right now.
Go to the APN settings (Settings -> SIM card Settings) and better do a reset to default (not necessary). Choose the o2 option and in a field called MVNO type select IMSI. You should be fine.
Will report back if this worked.
gerhard_wa said:
One thing you could do if you have activated VoLTE is to deactivate VoLTE. If this makes a difference it sugests that something is wrong in your local configuration. Otherwise you may have to take it back to the seller.
Click to expand...
Click to collapse
VoLTE is not enabled on my device, but this doesn't sound likely anyway - I have had the phone since the first week it was available in Europe - over 3 months - but the data stopping working only happened with a recent update. Anyway, this thread and other forums suggest this is a wider issue - can't see that sending it back to the retailer will achieve much as the replacement will likely do the same!
cool400 said:
Same problem here in Germany with o2.
I just found this solution to slightly another but very similar problem and I'm testing it right now.
Go to the APN settings (Settings -> SIM card Settings) and better do a reset to default (not necessary). Choose the o2 option and in a field called MVNO type select IMSI. You should be fine.
Will report back if this worked.
Click to expand...
Click to collapse
The APN settings are all greyed out on EE - I can read them but I can't edit them?
Any news here? I'm still stuck with this annoying problem.
I'm on MIUI 10.2. 9.0 Global and no updates available.
Just came here to say I have he same problem. Not really too annoying as all it takes is toggling airplane mode off then back on after a couple of seconds. But sometimes I don't even know the problem has surfaced and I end up missing notifications.
It happens sometimes even after I enter an elevator then leave.