Hi all,
This is my first thread here, but I'm not too noobish when it comes to technology. However, if I'm breaking a forum rule or you need more information, please ask.
I have a GNex with Verizon running 4.0.2. I am rooted and have flashed Clockwork Recovery and in the past flashed MIUI; however, it was a little sluggish for me and at the time I didn't have time to fiddle with it so I restored to a Nandroid backup I had created before flashing. As a side note, I haven't been able to get CWM Recovery to work correctly in the past as it will flash correctly (using the Galaxy Nexus toolkit) and I can boot into it directly after flashing, but after booting into Android, restarting, and attempting to boot into recovery it will give me the android/red triangle error. Not sure what that means, but if I need to use it I can usually boot into it without flashing.
Anyway, on to the meat of the problem here. Earlier today I took my phone off of WiFi to use LTE here (Bay Area, CA) but my phone wouldn't connect to the cellular network. Nothing I haven't seen before; I cycled airplane mode and the "data enabled" option and restarted to no avail. Upon rebooting, I got the "Unfortunately, the process com.android.phone has stopped" twice in a row. At this point, no bars displayed at all. Confused, I looked into Mobile Network Settings and under Network Mode it oddly stated that the preferred network mode was set to WCDMA preferred (specifically, GSM/WCDMA preferred). I can try to set it back to LTE/CDMA but it will only reset it back to GSM/WCDMA.
WiFi works, but as soon as I turn it off it will revert to the greyed out bars inside a triangle. As I type this now, there are currently two bars, but they are grey and of no use. I just tried to call someone, and the call went through, but the double "com.android.phone has stopped" dialogue box came up again
I suppose I am willing to do a stock reset, but I'd rather not due to my large amount of music, video, etc on my phone; plus, it's just no fun to throw in the towel and do a reset
Any and all help is welcome, and like I said if you need more information please ask. I googled this issue and no similar threads popped up on any forums, so I hope that if/when my issue is resolved this will serve as a guide to others who experience this issue. That is, assuming they do; my tech issues are all too often unique to my own horrendously bad luck.
gracias, dudes.
Bump since it was buried.
Now fixed with a wipe/reset. Initially I wiped/reset and restored all apps/data (including system) with Titanium Backup, but after the system data had been restored and I rebooted I encountered the same exact problem. I wiped/reset again and just let the Market redownload all my apps and the problem has since stayed away.
Any ideas on what exactly could have caused the issue, though? I'm curious.
Related
I'm rather new to smartphones and just acquired my Tbolt. Text messaging still functions correctly, but I am unable to send/receive pics. It tries for 5min to send, then says generic network failure.
Any advice?
Thank you
also, I was still able to log online, but not since I dialed ##778# then disabled my Rev.A under modem settings.
Kdeli said:
I'm rather new to smartphones and just acquired my Tbolt. Text messaging still functions correctly, but I am unable to send/receive pics. It tries for 5min to send, then says generic network failure.
Any advice?
Thank you
also, I was still able to log online, but not since I dialed ##778# then disabled my Rev.A under modem settings.
Click to expand...
Click to collapse
Well, there are three potential solutions I know of depending on your circumstances.
First, "if you ported over your number from another carrier and you are still within 72 hours of doing so, it can take up to 72 hours for a port to complete and for everything to function properly." - Verizon Tech
Second, People have reported that simply turning off the phone, pulling out the battery for 30 seconds, and then replacing that battery and booting back up resolves the problem.
Third, it doesn't sound like you had another android phone prior to the bolt, but if you did, and you used titanium backup to restore the stuff from your old phone, that is most likely the problem. Therefore, if you are rooted and ran Titanium Backup from your new bolt with information from another/old phone than this is your likely problem and you can remedy it by either wiping all data on the phone and starting over by going to Menu --> Settings --> SD & Phone Storage --> Factory Data Reset. Alternatively, you can use clockworkmod recovery to wipe all data and cache and reinstall the rom. You can still use Titanium Backup but only restore the apps, not the system settings.
I had this problem personally and spent 2 hours on the phone with Verizon unable to help me fix the solution. The Titanium Backup problem was my problem. Good luck and be sure to let me know if either solution works!
I updated to the latest nightly (9/22) to try and relieve this problem to no avail. I've been running CM Nightlies on my P4 since they've been available. I always manually download them since, for whatever reason, Rom Manager seems to detect my device as the P4-wifi. I assure you the 3G (HSPA) modem works. I have a SIM slot, with SIM that has activated service (UMTS/HSPA). My cell phone is on the same networks and it picks up signal from my carrier fine.
With that out of the way; My issue:
Two days ago, I was leaving my house to visit family, and I wasn't going to bring my charger for my Tab, so I put the device in airplane mode to conserve battery. In hindsight, I should have just asked the device to power off, but that's besides the point. When I tried turning off Airplane mode, the cellular network did not become available again; this situation has not changed since.
What I've done: Rebooted the device after switching out of airplane mode, re-entered airplane mode and left it again, updated to the latest CM. I've opened my tab and reseated the connections for SIM and antenna (at least, the connections I can reseat, I have), I've also completely disconnected power by unplugging the battery and reconnecting it. Additionally, I got into some of the hidden menus and verified that WCDMA, which, I believe is the underlying tech for the local HSPA connection, is preferred to the cell radio.
Looking at the device, if I ask it to check for mobile networks, the list comes back blank. The network status shows "UNKNOWN:0" and the lockscreen shows "NO SERVICE." instead of "NO SIM" (which is what it shows when I remove the SIM). From what I can tell the radio has shut off and will not come back on.
Throughout all this Wifi still works perfectly, so the device isn't useless, however, I'm planning to sell this device and I would like it to be as fully functional as possible when I hand it off to it's next owner, so getting this solved is very important to me. Any and all suggestions are appreciated and I'm basically willing to try anything at this point. I feel as though I've tried everything short of a factory reset, which I'm not sure if that would help (I've even wiped cache and dalvik).
In case it's relevant, I'm in Canada, carrier is Telus.
Thanks for reading.
EDIT: I've just finished restoring the device to Stock 4.0.4 (I've used this stock image before when I had issues with the device and confirmed it is fully functional) and I am still having trouble. this points to either a carrier issue or a hardware issue. I will be calling the carrier in the morning, despite believing that this isn't the case. any suggestions on what could be the problem are still welcome, I'm willing to try just about anything at this point.
@Mystik
Back in the CM 4.1.2 days on the e4gt...we had a similiar problem. Now, I don't have you're device. But when this problem arose in the epic. We had a work around where we would turn airplane mode on and power off the device. Then power the device back up. When that didn't work we had to flash a modem, then flash back to the one we wanted.
Also, make sure after you turn off airplane mode.. that the mobile data under settings/more is enabled... sometimes it will not re-enable itself.
Let me know if this works.. if not I would be happy to help you search up a fix..
Just encountered a little problem today. From the beginning: My Note 3 was rooted/TWRP'd running Vision X 3.0. Gave my wife my new G3 and took the Note 3 back. When I wiped her data in TWRP and restored a backup (same ROM) the 4GLTE icon started flashing on and off. I wiped complete again, installed a new ROM and did the same. Then I Odin'd to the new update. Same issue. I did encounter an issue with switching the phones earlier in the day. I had to get Sprint to do it via chat due to the Note 3 not being deactivated/reactivated correctly when I tried through the site. So I am guessing it could be a bad SIM card or they muffed something during activation. It will at times stop flashing and give me full LTE, but if I reboot or shut the phone off/back on it starts flashing again and the phone gets warm. It will sometimes stop/start if I mess with Connections Optimizer too, either checking or unchecking. Appears to be trying to connect to LTE but something is preventing it from locking on. I would appreciate it if anyone that has run into this before can give me some ideas. I do have a service center in town, and will go in the AM if I cannot find a solution anywhere else. I have never encountered this before.
Also in settings for data, Mobile State flashed between Connected/Disconnected and Mobile Network Type flashes between LTE/Unknown along with the LTE icon in status bar.
Tried killing data and all that. Airplane mode etc.. Sprint service center says it may happen when updating and will calm down in a couple of days..I don't think it was the update since I didn't update until after it started.
Also failed to mention when I switch to CDMA only in Data settings it will stay on 3G and doesn't flash. Has to be an LTE issue. And it is not the towers in the area because the G3 is fine.
Since it's broke anyway, going to Odin NC5 and see what happens. Tried freezing Connections Optimizer and flashing a new Kernel but didn't work either.
EDIT: Nope. That didn't work either. Ugh
Apparently it was a Sprint issue. Had to let it ride for a day or so and now back to normal. LTE is good again. Was an issue on their end when something went wrong during the phone swap.
Had this same problem with my Galaxy Grand Prime and rebooted in safe mode and it stopped. Safe mode disables all 3rd party apps. It is a 3rd party app causing the problem. I had to turn phone off, turn back on and hold volume down button after seeing Samsung logo popup, then wait for the safe mode to appear in lower left corner and release the button. Flashing stopped after that. Turned safe mode off and its still good so far. Hope this helps someone!!
Hey guys. So I've been trying to figure this out for several weeks with no luck and I was hoping you could help me. I have a Verizon LG G3 on AT&T on 10b. I can connect to 4G LTE and Edge just fine. However, when I try to make a call or receive a call on LTE, the network vanishes instantly. I'm talking from 3-5 bars to no service in within 5 seconds of calling my phone or calling from it. I've tried flashing different modems and the problem still persists. I already tried flashing the stock (what I'm on now), factory resetting, clearing the cache, etc. and have not been able to fix it. Today I called AT&T tech support and after they re-registered my phone I was able to make one phone call before the problem reappeared. When I made the call, my LTE dropped but I stayed connected through 2G/3G/Edge not sure which one.
The only other time I've had it working properly is when I had Cyanogenmod installed. However, that led to another issue. With Cyanogenmod, my phone would crash within a few minutes of booting. Most of the time I couldn't even make it through the setup. To be more specific about the crash, my screen would freeze and become unresponsive for a dew seconds and would then turn off completely. The green LED would turn on and stay on. Every time this happened I would have to pull my battery. The only way to prevent the freezing was to turn on airplane mode. If I turned off data or had the phone SIM-less it would still freeze airplane mode was the only solution.
If anyone can help me with either of these issues I would be greatly appreciative. If you need any more information or want me to post logs just let me know and I'll happily do so.
Here's a quick recap incase you don't want to read through the walls of text.
VS985 10b on AT&T
EDGE works fine
On 4G LTE network disconnects when making or recieving call
Cyanogenmod fixes network issues but freezes when not in airplane mode
Z3R01337 said:
Hey guys. So I've been trying to figure this out for several weeks with no luck and I was hoping you could help me. I have a Verizon LG G3 on AT&T on 10b. I can connect to 4G LTE and Edge just fine. However, when I try to make a call or receive a call on LTE, the network vanishes instantly. I'm talking from 3-5 bars to no service in within 5 seconds of calling my phone or calling from it. I've tried flashing different modems and the problem still persists. I already tried flashing the stock (what I'm on now), factory resetting, clearing the cache, etc. and have not been able to fix it. Today I called AT&T tech support and after they re-registered my phone I was able to make one phone call before the problem reappeared. When I made the call, my LTE dropped but I stayed connected through 2G/3G/Edge not sure which one.
The only other time I've had it working properly is when I had Cyanogenmod installed. However, that led to another issue. With Cyanogenmod, my phone would crash within a few minutes of booting. Most of the time I couldn't even make it through the setup. To be more specific about the crash, my screen would freeze and become unresponsive for a dew seconds and would then turn off completely. The green LED would turn on and stay on. Every time this happened I would have to pull my battery. The only way to prevent the freezing was to turn on airplane mode. If I turned off data or had the phone SIM-less it would still freeze airplane mode was the only solution.
If anyone can help me with either of these issues I would be greatly appreciative. If you need any more information or want me to post logs just let me know and I'll happily do so.
Here's a quick recap incase you don't want to read through the walls of text.
VS985 10b on AT&T
EDGE works fine
On 4G LTE network disconnects when making or recieving call
Cyanogenmod fixes network issues but freezes when not in airplane mode
Click to expand...
Click to collapse
I think you are talking about making calls on Voice over LTE. I am not surprised Verizon rom does not quite support it. Maybe you can try this swap boot.img hack to install AT&T rom and see if it solves your problem?
http://forum.xda-developers.com/showpost.php?p=58740774&postcount=43
Thanks for replying. That's my main theory too. However, according to my research, the VS985 didn't get VoLTE until the 12b update. I'll definitely try an AT&T ROM when I get the chance at the very least I'll probably learn something from it. Any chance there's an option to make LTE data only on this phone?
Hello,
I bought the P9000 US Edition recently, which runs the Elephone_P9000_M_20161107 ROM. After getting it, I didn't even start it up but immediately updated to the latest LinageOS with Android 6, but the SIM card wasn't detected then.
I flashed the latest official ROM 20170110, not realizing this isn't meant for the US Edition before seeing that the IMEI number was wiped, causing the SIM card not being recognized. Thankfully, I have a full backup of the original state at hand, so I could restore nvram easily and the mobile connection started working.
However, after that was solved, I encountered problems with the mobile connection:
Searching networks sometimes takes a long time, resulting in no connection at all in the meantime.
When I'm connected to 3G networks, it shows that it has a data connection (small 3G logo on the signal indicator), but I can neither make or receive calls, send SMS or use the data connection as long as it doesn't switch to 2G or 4G
The data connection problem sometime manifests with 2G and 4G, too: the small logo shows but no data comes through.
"Phone idle" is by far the largest battery consumer in the battery stats (not even the screen outweighs it at any time)
I just found out by trying that enabling and disabling airplane mode sometimes solves the problem, maybe because it results in a reset of the modem. I contacted Elephone support and they said that I had to reflash the original stock ROM for the US edition and if this didn't help, I had to send it in for repair, because flashing a wrong ROM corrupted the modem data.
After that didn't work, I even reflashed my backup, selecting each and every partition (except for the last two partition, flashinfo and sgpt[/] or something like that, for which I didn't take a backup). This seemed to alleviate the problem a bit, but not completely.
TL;DR: When the phone has a 3G connection, neither calls, SMS nor data work. Sometimes this also happens in 2G or 4G. Support says I corrupted modem data when flashing a non-US version ROM. I restored a full backup of the original state but it didn't change much.
Any suggestions on how I could solve the problem?
Are you in the USA?
I'm in Canada and using the EU version of the phone.
A solution I have found is to change the bands. This can be done by:
1) Press on the dial pad *#*#4636#*#* this will enable engineering settings.
2) In the top right press the '3 dots'
3) Press 'phone information'
4) Press 'select radio band'
5) Then choose a band based on your location or play with them see which works best exit and try that.
6) Redo the steps to change again should you need to. I typically play around with the bands to find the one that works best.
7) If this doesn't work maybe check your network APN settings? Mine are automatically filled for Bell and Rogers in Canada. When I travel in the EU it generally auto-fills as well using the network 3.
An error that occurs when I attempt to enter the 'select radio band' under 'phone information' is the error code "com.android.phone has stopped" with the toggle for 'Open App Again'. A solution I found to that problem is to soft reset the phone.
Another error I frequently encounter is "Process com.android.phone isn't responding"
Not really practical given the average user wants a device that "just works".