Develop Bugs

[solved] [Q] No signal (after switching Airplane mode on/off "too quickly")

edit: solution
Flashed the latest available drivers from http://forum.xda-developers.com/showpost.php?p=32317076&postcount=5 (4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios) and this fixed the problem.
Hello,
I had an episode where I needed to reconnect to a tower/give my radio a refresh quickly so I switched Airplane mode on, then off shortly after (10-15 sec), ever since my phone has stopped receiving any kind of network signal. The GPS still works but I have no CDMA/LTE signal at all. All antenna apps indicate that I have absolutely no signal.
Things I've tried:
Switched network mode to CDMA only, then back to LTE/CDMA
Switched roaming options (auto/home)
Turned WiFi/GPS on/off (I suppose this is pretty much irrelevant)
Ran Fix Permissions from recovery (I don't recall what this does, but I figured it wouldn't hurt)
Flashed latest version of 4.0.4 radio without wiping Cache/Dalvik Cache
Wiped Cache/Dalvik Cache, flashed 4.0.4 radio
None of these have restored the signal, and I'm at a bit of a loss regarding what I should do to restore signal short of doing a complete wipe/reflash.
Any tips on debugging/troubleshooting appreciated.
Thanks!

[Q] Data Connection Issues

Before I start let me explain I've searched for the answer to this and have yet to find any concrete answers. I've had my Verizon G'Nex since release and had it rooted before Best Buy had even run my credit card. I've been running SlimKat 4.4.2 Build 5 official and CWM Touch. Ever since I updated the ROM (clean flash) to the 4.4.4 experimental I've had problems with both 3G and LTE connecting to data. I have signal, in some cases "4 bars" worth, but it never actually connects to data unless I reboot the phone - that will last for a couple hours to a couple days then it's back to no data. I completely wiped the phone - data, cache, system, and sdcard...everything that CWM could possibly let you wipe - and then sideloaded the previously stated Slimkat which worked for months prior without issue. The problem still persists, and has gotten worse. I cannot use LTE at all. It will not connect regardless of what I do.
So my question here is what parts of Android affect data connection? Is this entirely ROM dependent, or does kernel have something to do with it? I'd rather not go through the trouble of finding another ROM that has speed and features of SlimKat, or randomly flashing kernels just to find it doing the same thing.

UTMorpheus said:
Before I start let me explain I've searched for the answer to this and have yet to find any concrete answers. I've had my Verizon G'Nex since release and had it rooted before Best Buy had even run my credit card. I've been running SlimKat 4.4.2 Build 5 official and CWM Touch. Ever since I updated the ROM (clean flash) to the 4.4.4 experimental I've had problems with both 3G and LTE connecting to data. I have signal, in some cases "4 bars" worth, but it never actually connects to data unless I reboot the phone - that will last for a couple hours to a couple days then it's back to no data. I completely wiped the phone - data, cache, system, and sdcard...everything that CWM could possibly let you wipe - and then sideloaded the previously stated Slimkat which worked for months prior without issue. The problem still persists, and has gotten worse. I cannot use LTE at all. It will not connect regardless of what I do.
So my question here is what parts of Android affect data connection? Is this entirely ROM dependent, or does kernel have something to do with it? I'd rather not go through the trouble of finding another ROM that has speed and features of SlimKat, or randomly flashing kernels just to find it doing the same thing.
Click to expand...
Click to collapse
Well in not sure about this option being in your version of cwm.
However if it has wipe efs data as an option and you wiped it nothing that you do to try and fix your connections will work.
I found this out the hard way and had to buy a new gnex. Tried everything but couldn't get my efs data back.

DR3W5K1 said:
Well in not sure about this option being in your version of cwm.
However if it has wipe efs data as an option and you wiped it nothing that you do to try and fix your connections will work.
I found this out the hard way and had to buy a new gnex. Tried everything but couldn't get my efs data back.
Click to expand...
Click to collapse
No option about EFS. That's the thing that bothers me. I have voice and text, it can 'see' towers, it appears to be able to 'connect' to towers, but it's like it's not pulling an IP address or it can't contact DNS.

t999 has bars but no calls or data, in all roms

So about 6 months ago, I decided to finally try out some custom roms on my t999 after running stock for over a year. I tried a couple of roms and stuck with cm11. Every thing was great until about 3 weeks ago. Out of nowhere, my phone randomly decides to drop connection to tmo towers. Sometimes i have bars and 4g symbol and sometimes i don't have anything. When I pull the battery and restart, I am able to connect to data, make calls, and send messages for a few minutes, but then i lose everything. Randomly throughout the day, I will get signal back for a few minutes but thats it. I flashed a touchwiz rom for now so I can use wifi calling, So that still works.
So I tried to flash a different baseband modem from DocHoliday77 and none of them worked. I also tried going back to stock following DocHoliday77s guide once again, but for some reason that does not work. I launch odin3.07, put my stock firmware in the pda section, make sure only auto reboot and F reset time are checked. I connect my phone in download mode, it is detected and i start the process. The phone restarts but gets stuck at the samsung logo screen. I have tried flashing different roms and none work.
I dont think its an imei problem because I got the phone direct form tmo with a contract.
Does anyone know what I might be doing wrong? ANY help would be greatly appreciated.

Did you factory reset after you flashed the firmware in Odin? That's the only way it will boot coming from cm.. You may just need a new sim if flashing to stock won't fix it.. And BTW T-Mobile doesn't do contracts

Cannot SEND SMS Tried Everything Please HELP :(

All of a sudden today I cannot send SMS.
I was on a really old build of Cyanogenmod12 (April 22nd I believe) as any time I tried to update to newer Nightly builds I lost all Sprint service could not make/receive calls or texts, etc.
I decided I was pretty fed up with CM12 so I decided to go ahead and migrate to AICP. I wiped everything TWICE in recovery, loaded up AICP and it works fine, I get LTE signal, etc. However I cannot SEND SMS, I can RECEIVE SMS I just cannot SEND. I had done some data restores with Titanium and I figured that somehow some way that might be messing with things. So I did another 100% fresh install after wiping everything.... I can send/receive calls, receive SMS but I cannot SEND SMS
I am really at a loss here guys, ANY help would be greatly appreciated

*#*#4636*#*# change it to CDMA wait 30 seconds send an SMS and do *#*#4636*#*# again change it back to late/CDMA n should be ok
Sent from my SM-N910P using XDA Premium HD app

pbedard said:
*#*#4636*#*# change it to CDMA wait 30 seconds send an SMS and do *#*#4636*#*# again change it back to late/CDMA n should be ok
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I stayed up all night last night working on this, let me update the thread with what I have done so far.
I was looking at some stockish ROMs and I noticed that there were warnings on some of them stating that you needed to have the Sprint OTA 5.0 update installed prior to flashing, which I actually never got. My phone came out of the box with Kit Kat and I never installed the 5.0 update, I went straight to CM12 5.0 instead. So I had a theory that there might possibly have been some sort of network data profile, etc or something out of that official 5.0 OTA that I never got that was somehow causing me problems. I decided to revert back to complete bone stock.
I wiped everything and flashed the N910PVPU1BOB7 file (MD5 = 7304e42cf0e241553d8db9e3c3eeed81) which was the official Sprint 5.0 OTA. Loaded it up, updated the PRL, Network Data Profile, etc, etc, etc.... everything works (relatively speaking...... TouchWiz sux balls of course). I have LTE signal, I can send/receive calls, I can send/receive SMS... all good.
So at this point I decided to re-wipe and flash AICP, with the emotion Kernel (latest builds on all). Load it up.... same problem as before. I have LTE signal (stronger than on the stock Sprint ROM), I can send/receive calls, I can receive SMS but I still CANNOT SEND SMS
I tried a few things at this point. I tried to manually reset the Sprint network connection on the phone by dialing ##72786#, this did not work, it returned an error "incorrect MIM code". I tried the *#*#4636*#*# that I have seen suggested in multiple places, this also did nothing, it returned an error "incorrect MIM code". I also noticed on the "mobile networks" tab, and this is true for BOTH CM12 and AICP, that it has the setting at "Global" by default and everything works with exception of sending SMS. Now when I click that tab it only has 3 options LTE, 3g, 2g.... for some reason "global" is not an option, neither is CDMA. Whenever I select LTE it automatically drops me from the Sprint network PERMANENTLY until the ROM is re-flashed there is no way to reverse this. I cannot even dial the manual programming codes "*#* etc" as it just simply says "no network service". If I try to automatically connect to the sprint network through the network operators tab it does in fact find Sprint as my provider, however if I click on Sprint to connect it processes for about 2-3 minutes and then simply returns an error of "cannot connect to the network at this time, please try again later". Again the only way to reverse this is to re-wipe and re-flash again which puts it into the unselectable "global" network setting by default where then I will have LTE signal, I can send/receive calls, and can receive SMS but not send SMS.
So that is where I am at, I stayed up all night last night wiping, flashing, and testing different things over and over. Nothing seems to work 100%, except the stock 5.0.1 OTA which is what I am on now. I really hate TouchWiz and for some reason I get a much weaker LTE signal on stock compared to either CM12 or AICP (I have no clue why this is). I am really at a loss here why everything works on the custom ROMs except for sending SMS..... willing to try almost anything to go back to a custom ROM.
Let me know if you guys have any other ideas.

Well great news I have finally resolved the SMS send issue
pbedard said:
*#*#4636*#*#
Click to expand...
Click to collapse
pbedard had tried to help me with the above post (which I appreciate, thank you), and I have seen the same advice in other threads. One slight problem though, he slightly mistyped the manual programming code it is actually *#*#4636#*#* not *#*#4636*#*# which I had tried entering ohhhhh I dont know 30 times? :silly: And it always returned an "invalid MMI code".
I had tried everything and after spending a full day on TouchWiz I was determined to fix the issue so I could go back to a custom ROM. I was even manually creating and deleting APNs, etc. Nothing would work. Right as I was about to finally give up (after literally 12hrs of researching the issue and testing fixes) I was reading the official CM 12 thread and came across the "fixes" post:
http://forum.xda-developers.com/showpost.php?p=57613217&postcount=3
Because I had tried entering the manual programming code so many times I happened to notice that the last 4 key strokes were not what I had been entering. I entered the correct programming code, boom the Phone Info menu pops right up I follow the directions and what do you know send SMS finally works .... wow what a relief, I am on the latest AICP release on the emotion Kernel and everything works like a charm.
Also by setting the phone to LTE/CDMA through the manual programming menu I have the strongest LTE signal by far, full 100% bars at all times (I live right next to a Sprint tower). I have never understood why I only got 1-2 bars on the stock ROM and 3-4bars on CM12/AICP through the default settings. Anyway thanks for help and I will list out exactly what I did to get it working.
- 100% Stock ROM
- CF Auto Root and TWRP install through Odin
- Reboot to recovery
- Wipe Dalvik cache, system , data, and cache
- Reboot to recovery
- Flash emotion kernel (optional)
- Flash latest AICP build (or custom ROM of your choice)
- Flash latest stock Gapps
- Reboot system
- Confirm Google Messenger is the default SMS app (it will already be if you flashed 5.1 stock Gapps)
- Dial *#*#4636#*#* ("Testing" menu screen will pop up, select "Phone Information")
- Scroll down to "Set preferred network type" click it and scroll up and set it to "CDMA auto (PRL)"
- Wait until 3G signal comes online (takes about 10 seconds)
- Change "preferred network type" to " LTE/CDMA auto (PRL)"
- It should take another 10 seconds for LTE signal to come online and you should be good to go to send and receive SMS ! :good:

[Q] Preferred network mode won't stay on GSM/WCDMA/LTE on Lollipop 20e

Every time I change my network mode to GSM/WCDMA/LTE (Auto) it goes back to GSM/WCDMA (Auto) after an hour or two. I can get LTE in my area and I do after changing the network mode setting manually, but after an hour or two my phone goes back to GSM/WCDMA and I loose LTE. I've tried going into the test menu and choosing my preferred network mode but it won't stay. My build.prop file has not been edited. I don't have the LTEconfigs.apk to delete.
Any ideas on what to do?
edit: I restored system partition from a backup. I'm fine now.

Have you at any point downgraded to KK from LP, then upgraded again back to LP? Because the same thing happened to me after downgrading, and then upgrading again.

redduc900 said:
Have you at any point downgraded to KK from LP, then upgraded again back to LP? Because the same thing happened to me after downgrading, and then upgrading again.
Click to expand...
Click to collapse
No, I never downgraded. I went from 10m to 10r to 20b to 20e, each time doing a complete system flash.

i have the exactly same problem except i am currently on 20g. I even reflashed the stock rom again and it still returns to GSM/WCDMA after reboot or idling for 1-2 hours. I changed the setting under the hidden menu as well and still didn't work.
any help is greatly appreciated.

This is a baffling problem. I have heard that both the cause and the cure is flashing back to KK and then back to LP. Among a multitude of other solutions with no real common thread. Having said that the one that makes the most sense is restoring your EFS backup, if you have one. For me I didn't have one.
Here is my experience, I wish I could say what was the real fix.
Started out at 10r and flashed CM12 as soon as I got the phone last Jan. About 6 months ago I had the common prob of the exclamation mark on my signal and no data. Used the LTE toggle to fix and lived like that for 6 months. Back in the fall I decided to go back to stock to see if it would fix. Flashed a stock zip of 20e. At 1st this was a disaster, I had no data and incidentally no APN. Oh by the way I have a TMO GS on at&t. Even after creating an APN no luck. I happened to have a live TMO SIM so I did a factory reset with the TMO SIM installed during 1st boot. This SIM is a prepaid w/o data, but it did attach to LTE. I then created an at&t APN swapped SIMs and LTE data worked. But now I had the problem of LTE not sticking. Usually dropped after a power cycle or going off WiFi, the later was not 100% reproducible, the former was. From a data standpoint I was better off as I no longer got the exclamation mark and no data. But OMG stock LG sux!
So along comes CM13. I see one guy that still had to do the LTE toggle, I figure not worth jumping in. But couldn't resit the pull of sticky Marshmallow and CM nighties. So I rooted and installed CM13. Amazingly I no longer have any data or LTE issues. Again, I wish I could give a clear path to fix. But maybe others can pull from my experience.
Good luck and if you get it working back up your EFS! Can be easily done via TWRP.