Develop Bugs

[Q] Sprint PRL's

Anyone know how to pull the PRL out of the Galaxy Nexus? I tried the *#*#8778#*#* that worked with the NS4G & QPST, but no dice. It would be nice to be able to use something like the 11115 PRL that allowed 3g roaming on older/other phones. I tend to get stuck in areas that have zero Sprint coverage for work a lot of times.
EDIT: *#*#3424#*#* Will put you in the right menu, I'm still working on figuring out how to get QPST to recognize the device though.
EDIT #2: From what I've been reading, the Galaxy Nexus will not work with QPST because it is not Qualcomm compliant...need to find VIA/Spirent PST to be able to do this? Anyone have any input regarding this?

I found a way to change the PRL. I'm not 100% sure that it actually changed the PRL and not just the number that shows in the menu though. The idea came from this thread: http://forum.xda-developers.com/showthread.php?t=1639839
So using Better Cut I followed the first step he outlined, JUST THE ONE ABOUT THE PRL THOUGH. Phone went through and did its reboot came back up.
At first it showed unknown as the PRL, MIN & My Phone Number. I went into *#*#yourmsl#*#* checked under edit and my info was correct, checked under *#*#3282#*#* and my username was correct in the data profile. Went back into about phone and everything had repopulated correctly.
Now where I am sitting its still showing me as connected to a 1xrtt network, but that very well could be because I'm in the middle of WY at the moment. I should be going into SLC tomorrow and I will try to force it to roam while I am there and see what happens.

Seems the post has been edited and no longer has instructions.
1.Download Better Cut (Google it)
2.Install on your phone however you see fit. I just downloaded the apk to my phone and installed from there.
3.Copy your chosen PRL to the root of your SD card and rename to Test (so instead of 11115.prl, it will show up as Test.prl)
4.Create a shortcut using Better Cut, go "Activity", "PRL Write"
5. Go back to where the shortcut is and click it. The phone will reboot and shortly after the PRL should show up in the "About Phone" section of your settings menu.

My friend just got a sprint nexus and he needs to force roam on it. His palm pre had this tweak working.

I've been using corporate PRL's on every phone I've had with Sprint and up until this phone, it has been very easy to do. From what I've read none of the traditional methods work because this phone does not use a Qualcomm chipset for the radio, it is using a VIA chipset. I will report back tomorrow if this actually changed the PRL or if it just changed the displayed numbers. It's hard to say in WY whether or not 3g service is actually available and from what I can tell I am rather far from the tower I am connected to.
RogerPodacter said:
My friend just got a sprint nexus and he needs to force roam on it. His palm pre had this tweak working.
Click to expand...
Click to collapse

The PRL should auto adjust as soon as you change regions. If its not changing and you're experiencing bad reception....etc...contact Sprint cause chances are you aren't alone.
Sent from my Galaxy Nexus using XDA

Actually none of the phone's I have used with Sprint in the past few years have changed as I moved around the country. The point in all of this is not about bad reception really, just that when roaming certain PRL's you will get 3g roaming as opposed to the regular 1x.
Smokeey said:
The PRL should auto adjust as soon as you change regions. If its not changing and you're experiencing bad reception....etc...contact Sprint cause chances are you aren't alone.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse

bbv203 said:
Actually none of the phone's I have used with Sprint in the past few years have changed as I moved around the country. The point in all of this is not about bad reception really, just that when roaming certain PRL's you will get 3g roaming as opposed to the regular 1x.
Click to expand...
Click to collapse
PRL's CAN be region specific. However, some networks (Sprint included) Only have 2 or 3 different PRL's (Virgin mobile's...etc..) So whatever PRL you have now should be fine unless Sprint lights up new CDMA networks or adds more spectrum. If you have an old PRL (dunno what revision it is, I'm on VZW) update it with ##873283#. Any connection issues you're having likely aren't the PRL and are probably more related to carrier issues or the notorious Galaxy Nexus Data Drops that almost every version of the phone has had.
Edit: You could always try the Sprint Partners PRL's...dunno if it will work though.
Sent from my Galaxy Nexus using XDA

Smokeey, I don't doubt that they can be region specific. But again, the only point in me doing this is for times when I am actually roaming due to the places I go for work. Ex: I have been in Wyoming for 5 weeks now, Sprint has Zero coverage here. So again it isn't about connection issues. It's about EVDO vs 1xRtt while roaming. The only time I use Roam Control or similar functions are to test the ability to get 3g while roaming.
Aside from that, I do not think this is the best way to go about changing the PRL manually on this phone, but for now it will do.
So .... with the 11115 PRL I was only getting 1x in WY, should have been 3g. Today I got into Salt Lake where there is Sprint coverage and I was still roaming, with the phone and Roam Control set to Automatic. I restored a backup of the stock ROM, refreshed profile, updated PRL and was back on Sprint 3g. Then went back and forced the manual update of the PRL back to 11115, tried switching to roam only mode and the phone stayed connected to Sprints network. By the time I got back into WY and was roaming again, it did properly switch to a roaming partners system and I still had 3g coverage. So it seems that everytime you write the PRL with Better Cut, you could get a different result. FOR ME this is fine, as long as it works when I am actually roaming.
I'm sure down the road a VIA compatible PST and associated drivers will turn up so that this can be done in a similar fashion to the way it was accomplished with QPST on other phones. But for now I am content.

I've linked to your post in my thread for how to update PRL manually. Your post was first.. so it's only right
and for completeness... here is my thread detailing how to use VIA tools the same way we used to use Qualcomm tools. I've linked back to you in the second post which details PRL writing. It looks like even with VIA chipsets.. we aren't so locked out after all.
http://forum.xda-developers.com/showthread.php?t=1696621

Looks good, I'll give it a shot soon. Hopefully it will work in a VM, stuck with 64 bit on my laptop....
autoprime said:
I've linked to your post in my thread for how to update PRL manually. Your post was first.. so it's only right
and for completeness... here is my thread detailing how to use VIA tools the same way we used to use Qualcomm tools. I've linked back to you in the second post which details PRL writing. It looks like even with VIA chipsets.. we aren't so locked out after all.
http://forum.xda-developers.com/showthread.php?p=26425227
Click to expand...
Click to collapse

link in previous post has been updated. i'll post again here just incase
http://forum.xda-developers.com/showthread.php?t=1696621
and yes, it will work in VM.

PRL write not listed in any cut or better cut
I can't find "PRL write" in either Any Cut under activities or Better Cut(v3.3) under all activities. I have Test.prl in /sdcard/. I'm running a vzw gnex on CM9.1. I've tried changing it's name to TEST.prl. I've tried several different prl files.
Anyone one have any advice.

bbv203 said:
Smokeey, I don't doubt that they can be region specific. But again, the only point in me doing this is for times when I am actually roaming due to the places I go for work. Ex: I have been in Wyoming for 5 weeks now, Sprint has Zero coverage here. So again it isn't about connection issues. It's about EVDO vs 1xRtt while roaming. The only time I use Roam Control or similar functions are to test the ability to get 3g while roaming.
Aside from that, I do not think this is the best way to go about changing the PRL manually on this phone, but for now it will do.
So .... with the 11115 PRL I was only getting 1x in WY, should have been 3g. Today I got into Salt Lake where there is Sprint coverage and I was still roaming, with the phone and Roam Control set to Automatic. I restored a backup of the stock ROM, refreshed profile, updated PRL and was back on Sprint 3g. Then went back and forced the manual update of the PRL back to 11115, tried switching to roam only mode and the phone stayed connected to Sprints network. By the time I got back into WY and was roaming again, it did properly switch to a roaming partners system and I still had 3g coverage. So it seems that everytime you write the PRL with Better Cut, you could get a different result. FOR ME this is fine, as long as it works when I am actually roaming.
I'm sure down the road a VIA compatible PST and associated drivers will turn up so that this can be done in a similar fashion to the way it was accomplished with QPST on other phones. But for now I am content.
Click to expand...
Click to collapse
Roam control works for you?

Do we know of another way to change the MSL?
I prefer mine to be 000000, but with QPST not reading it I'm stuck.
I could try and dig up a CDMA workshop, but most of those are virus ridden, and i'm not sure it would connect to it either...

bbv203 said:
I found a way to change the PRL. I'm not 100% sure that it actually changed the PRL and not just the number that shows in the menu though. The idea came from this thread: http://forum.xda-developers.com/showthread.php?t=1639839
So using Better Cut I followed the first step he outlined, JUST THE ONE ABOUT THE PRL THOUGH. Phone went through and did its reboot came back up.
At first it showed unknown as the PRL, MIN & My Phone Number. I went into *#*#yourmsl#*#* checked under edit and my info was correct, checked under *#*#3282#*#* and my username was correct in the data profile. Went back into about phone and everything had repopulated correctly.
Now where I am sitting its still showing me as connected to a 1xrtt network, but that very well could be because I'm in the middle of WY at the moment. I should be going into SLC tomorrow and I will try to force it to roam while I am there and see what happens.
Click to expand...
Click to collapse
I have used this method, but through apex launcher, Also tried it using Sprint Diagnostics options, guess trying bettercut wont hurt. I have the same issue as far as my info reflecting correctly using *#MSL & *#DATA but I have "Unknown" showing up in the My Phone Number, MIN & PRL fields, but they never repopulate for me. Any hints on what could cause this?
Thanks in advance

Preferred Network Mode Not Sticking: Let's Solve This Once and For All

So I'm on a CyanogenMod 10 nightly, and I am having the problem of the Preferred Network Mode setting not sticking, like several other users apparently, and after searching the forum I have concluded that there is no actual solution yet. Right now I can get to 4G LTE by manually setting to LTE/GSM/WCDMA in the Preferred settings, but it always reverts back after reboot. Apparently this does not happen to everybody; how should I fix this?
I posted in the CM Nightlies thread but no one seemed to notice. I hope this can get to the devs so they can fix this eventually I guess.
The following may be of use
http://code.google.com/p/cm9-msm8960/issues/detail?id=39
According to that, this is a hard-coded problem caused by the settings in the two places not matching?

Try going to your dialer and typing *#*#4636#*#*
Use that dialog to set it to what you want and hopefully it will stick then?
I never encountered this problem myself because I never want my phone on LTE as the battery life is pitiful as is and LTE only makes it worse.
Mine is set to WCDMA only on quattrimus cm10 and it sticks no problem.
Sent from my Nexus 7 using XDA Premium HD app

same here
iarejohnsmith said:
So I'm on a CyanogenMod 10 nightly, and I am having the problem of the Preferred Network Mode setting not sticking, like several other users apparently, and after searching the forum I have concluded that there is no actual solution yet. Right now I can get to 4G LTE by manually setting to LTE/GSM/WCDMA in the Preferred settings, but it always reverts back after reboot. Apparently this does not happen to everybody; how should I fix this?
I posted in the CM Nightlies thread but no one seemed to notice. I hope this can get to the devs so they can fix this eventually I guess.
Click to expand...
Click to collapse
Had the same problem, except that it dropped data service every 10 mins or so. Didn't even had to reboot. I could fix that by changing the network settings from lte/wcdma to gsm/wcdma. Another thing I witnessed when on lte that it would recover data connection when the process was restarted e.g. when activating and deactivating airplane mode.

Unlike most people, I'm actually wanting to keep it on LTE only, since I just keep data off until I need it, and when I need it I want full speed.
The phone always reverts back to GSM/WCDMA, turning off LTE.
I messed around in *#*#4636#*#* but it didn't really do anything.

I've been having the same problem on my Razer Phone 2. I don't think this is specific to the phone itself, but. I'm getting desperate for a solution. I change the preferred network type in the *#*#4636#*#* menu, I get LTE fine..... As long as I don't restart the phone or go on/off with airplane mode. Then I have to do it all over again. Does anyone know how to make this stick?

Fix weak LTE connection in ZVD firmware

If you have noticed after the ZVD update you seem to be on 3g a lot and seem to have problems staying on LTE in locations you previously had good signals, here is a fix I shared in the ZVD update thread which seems to completely resolved the issue:
1. Obtain your MSL
2. open the dialer and enter ##data#
3. Tap LTE and select edit
4. Enter your MSL
5. Select BSRTimer (defaults to 3000) and change the value to 3
6. Press back, phone should reboot
7. Profit
*does not require root
After doing this, I'm back to nearly constant LTE connectivity, where prior to the fix I was on 3g almost every time I checked.

rocket321 said:
If you have noticed after the ZVD update you seem to be on 3g a lot and seem to have problems staying on LTE in locations you previously had good signals, here is a possible fix I shared in the ZVD update thread which seems to have complete resolved the issue:
1. Obtain your MSL
2. open the dialer and enter ##data#
3. Tap LTE and select edit
4. Enter your MSL
5. Select BSRTimer (defaults to 3000) and change the value to 3
6. Press back, phone should reboot
7. Profit
Click to expand...
Click to collapse
How do I know my MSL?

danieldp1990 said:
How do I know my MSL?
Click to expand...
Click to collapse
If you don't know it and you are running ZVC or higher, you have to use a flashtool, such as CDMA Workshop or use basic flasher and follow this guide: http://forum.xda-developers.com/showthread.php?t=2521276

You can also ask Sprint via chat or call customer service and generally they will tell you with no hassle at all.

rocket321 said:
if you have noticed after the zvd update you seem to be on 3g a lot and seem to have problems staying on lte in locations you previously had good signals, here is a possible fix i shared in the zvd update thread which seems to have complete resolved the issue:
1. Obtain your msl
2. Open the dialer and enter ##data#
3. Tap lte and select edit
4. Enter your msl
5. Select bsrtimer (defaults to 3000) and change the value to 3
6. Press back, phone should reboot
7. Profit
Click to expand...
Click to collapse
thanks man that fixed my nightmare

Since this thread has very little activity, I'm wondering if only a few of us had the issue? For those that had the problem that this fixed, did you sideload the update through adb, or take it OTA? I used adb and that makes me wonder if those who got it over the air didn't have the problem?

I think this problem affects everyone who took the ZVD update; I certainly have noticed significantly less LTE service since upgrading.
I haven't tried this fix yet since I'm often on wifi or in areas where I know there's no LTE, but I'll probably give it a shot eventually.
Edit: FYI, I took the all the updates OTA (never rooted, never installed customer recovery or ROM).
rocket321 said:
Since this thread has very little activity, I'm wondering if only a few of us had the issue? For those that had the problem that this fixed, did you sideload the update through adb, or take it OTA? I used adb and that makes me wonder if those who got it over the air didn't have the problem?
Click to expand...
Click to collapse

i have had a weak signal problem as well. i used the described way to get my MSL and it worked great. i then applied the change under the ##data# menu.
it seems to have worked great!! i will report back after a few days.

It helped, but I'm still having connectivity issues. Granted, my problem started during the zvc update, and as I'm typing this I just got dumped to 3G.
I did end up doing a full ##rtn# reset though. After everything finished I checked the BSRTimer and it was set to 1 instead of the 3 I set from the 3000
My connectivity is noticeably better though. Reps are saying the sites I'm connecting to are e/CSFB upgraded though. *shrug. Before kitkat I almost never lost LTE. Guess I just have to wait on them to install the carrier cards to deploy band 26.
At home when I hook LTE I usually run a -113 to -118.

BecomingDeath13 said:
It helped, but I'm still having connectivity issues. Granted, my problem started during the zvc update, and as I'm typing this I just got dumped to 3G.
I did end up doing a full ##rtn# reset though. After everything finished I checked the BSRTimer and it was set to 1 instead of the 3 I set from the 3000
My connectivity is noticeably better though. Reps are saying the sites I'm connecting to are e/CSFB upgraded though. *shrug. Before kitkat I almost never lost LTE. Guess I just have to wait on them to install the carrier cards to deploy band 26.
At home when I hook LTE I usually run a -113 to -118.
Click to expand...
Click to collapse
Yep this is a good point, I don't know that it's specifically supposed to be 3,but I do know 3000 was causing my phone to park on 3g almost all of the time, and now it is on LTE almost constantly (we have band 26 available here).
Even in my basement with the signal bar indicator showing zero bars I have maintained LTE.

tin foil
tin foil will boost signal

Now that this has been posted a while, (I also saw it posted over on S4GRU) and it seems to be helping a lot of people, which makes me feel good for my accidental discovery!
With that said, I have been watching the RDF page and it's still showing ZVD, which indicates to me that LG may not be working on another update yet. I was hoping for a fairly quick 2nd release which would fix this LTE bug and also add wifi calling.
Is there some good way to flag this issue to LG without having to get hundreds or thousands of people to call Sprint customer service about it? Somehow I suspect the average user will notice poor LTE performance and just blame Sprint coverage rather than the ZVD update. Most will not be bothered to actually call about it either. I just wish manufacturers had an engineering mailbox or forum setup where the enthusiasts could actually flag these issues so they could be fixed in the next release. Customer service will probably just tell people to factory reset their phone.
Then again, maybe someone here has a LG connection they can get the word out

Strainc said:
tin foil will boost signal
Click to expand...
Click to collapse
Dumbass ?

rocket321 said:
If you have noticed after the ZVD update you seem to be on 3g a lot and seem to have problems staying on LTE in locations you previously had good signals, here is a fix I shared in the ZVD update thread which seems to completely resolved the issue:
1. Obtain your MSL
2. open the dialer and enter ##data#
3. Tap LTE and select edit
4. Enter your MSL
5. Select BSRTimer (defaults to 3000) and change the value to 3
6. Press back, phone should reboot
7. Profit
*does not require root
After doing this, I'm back to nearly constant LTE connectivity, where prior to the fix I was on 3g almost every time I checked.
Click to expand...
Click to collapse
Thanks for the information, I have located my MSL and entered DIAG, where do I locate LTE?
LS980 on ZVD

You mean data menu
Sent from my LG-LS980 using Tapatalk

secret.animal said:
You mean data menu
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Yes I went to settings, the Mobile Data and I don't see where to do step 3. (3. Tap LTE and select edit)
Thanks for the response.

1bayne said:
Yes I went to settings, the Mobile Data and I don't see where to do step 3. (3. Tap LTE and select edit)
Thanks for the response.
Click to expand...
Click to collapse
From the phone app - dial pad

rocket321 said:
From the phone app - dial pad
Click to expand...
Click to collapse
Thanks for the reply, secret.animal has helped me out.
I'm still dropping to 3G at home when I was getting LTE (Spark) Sprint must be working on the towers. :crying:

Since I made the switch over to ZVD I have been picking up LTE everywhere. The only problem I am having is that I usually have to reboot my phone for out to switch over. Will this help with that? I am on LTE/CDMA...

jayt0625 said:
Since I made the switch over to ZVD I have been picking up LTE everywhere. The only problem I am having is that I usually have to reboot my phone for out to switch over. Will this help with that? I am on LTE/CDMA...
Click to expand...
Click to collapse
Yep, if you are rebooting or toggling airplane mode to get LTE, this should fix you up.

[GUIDE] [HOW TO] Fix VS986 dropping down to 3G/H+ from 4G LTE

I've been working on a fix since a long time now. If you are in SD community then you prolly know me. Anyway I was able to fix this on two of my phones and it's working fine. I tested for 12 hours now. I'll also tell you in the end what problems I'm seeing. I'm also working on a fix for that.
I noticed that a service is started when the fallback happens but if I kill that service the network also dies. But if you follow the below method it safely starts a new service which kills the one that's responsible for killing the 4G/LTE
1. Upgrade your phone to 13B firmware
2. Root 13B
3. Now download Shortcut Master lite app from play store.
4. Now add these shortcuts to your favorites in the "Shortcut Master lite app". You can search for "LTE" and click on search button
LTEBandSelection
LTETestMain
LTE System Selection
CDMAPreference
5. Now click on "LTEBandSelection" and enable all the bands
6. Save and reboot
7. You now need to enable your data and turn off your wifi. Make sure your phone is in Global mode (in settings >> Mobile networks >> System select)
8. After your phone is rebooted open "Shortcut Master lite" app.
9. Now tap on LTETestMain
10. Select Click on CDMA preference.
Now choose Band preference and select "any"
P_REV_Preference ---> "MOB_P_REV 3
This is important.. EVDO Revision --> Rev A
11. "LTE Connect w/o IMS PDN" must be checked
12. Now go back to your main menu in shortcut master lit app
13. This step is very important. Changing the timeout is important. Tap on LTE System Selection
Except "Scan duration" add a couple zeros to all the other timers. For eg: T_mpsr timer (Min) is 200
The fallback timer will reset itself after reboot. But don't worry the configuration is already updated with the new value. For some reasons the shortcut master lite app is not picking it up.
14. Now finally click on "CDMA preference" in the main menu and make sure it has the value you set in Step 10
At step 10 or 13 your network should go away and your phone should complain about "no network". That's fine. just ignore the message.
Now finally reboot your phone. That's it. You should now have 4G LTE and it won't fallback to 3G or H+
The only problem is when I'm on a call my 4G LTE is dropped to 3G/H+. But after I hang up it goes back to 4G LTE after 12 seconds. I don't know if it's an expected behavior. But I'm trying to see if there is a fix for that.
I tested this with Tmobile. Make sure your APN settings are correct.

Not working for me on Cricket (AT&T). Still will always go back to H+, 4G LTE only works when I select CDMA.

konradsa said:
Not working for me on Cricket (AT&T). Still will always go back to H+, 4G LTE only works when I select CDMA.
Click to expand...
Click to collapse
I tried it on my two phones (Both tmobile). My friend just tried it on his phone. It worked for him too.

motorhead_biker said:
I tried it on my two phones (Both tmobile). My friend just tried it on his phone. It worked for him too.
Click to expand...
Click to collapse
That's great! I hope we can figure out also what we need to do to get it to work for AT&T, I am sure it's probably just some small tweaks required.

konradsa said:
That's great! I hope we can figure out also what we need to do to get it to work for AT&T, I am sure it's probably just some small tweaks required.
Click to expand...
Click to collapse
I will try it with my roomies att sim tonight. He has a nano sim, I need to find a sim adapter.

Awesome, thank you! worked for me T-mobile.
it initially didn't work but I had to turn data off then on.
It also cycles me to 2g speed for a few seconds sometimes but that may be due to poor signal in building.

pwtzz said:
Awesome, thank you! worked for me T-mobile.
it initially didn't work but I had to turn data off then on.
It also cycles me to 2g speed for a few seconds sometimes but that may be due to poor signal in building.
Click to expand...
Click to collapse
Yeah It's due to the poor signal. I got that too. You can check your signal strength using LTE discover app.
But overall it's working fine for Tmobile. I'm gonna try and fix ATT tonight.

Is 13B the main thing in the solution? I've changed these settings before on 11A and wasn't fixed. I tried these numbers on 11A and still don't work.
Also, unless a phone supports VOLTE, it'll fall back to 3G/H for calls.

eigen said:
Is 13B the main thing in the solution? I've changed these settings before on 11A and wasn't fixed. I tried these numbers on 11A and still don't work.
Also, unless a phone supports VOLTE, it'll fall back to 3G/H for calls.
Click to expand...
Click to collapse
I tried in 11A and it didn't work for me. So I guess it needs 13B.

So I tried various combinations last night for AT&T/Cricket, but I was not able to get it to work. No matter what I tried, when I had 4G LTE, voice wouldn't work and whenever voice worked, I was back to H+.
If others are reporting that T-Mobile works reliably on 4G and nobody can figure out how to make this work for AT&T, I guess it's time to switch to T-Mobile.

konradsa said:
So I tried various combinations last night for AT&T/Cricket, but I was not able to get it to work. No matter what I tried, when I had 4G LTE, voice wouldn't work and whenever voice worked, I was back to H+.
If others are reporting that T-Mobile works reliably on 4G and nobody can figure out how to make this work for AT&T, I guess it's time to switch to T-Mobile.
Click to expand...
Click to collapse
No. Hold on. I have a solution for ATT too. I tried something last night. Actually while I was working on a solution for ATT I found that we don't even have to go through the steps I mentioned in my OP to solve the problem. It boils down to invoking a service and killing a native VZW service.
The ATT solution I have works but in low signal area 4G fades and it doesn't fallback to 3G or H+. I had to recycle data to get 3G or H+.

It's Working!!!!!!!!! Thank you!!!!!!!
You just made my life much better now!
I finally have a phone which is great and also finally have good reception!
I Love U!

motorhead_biker said:
No. Hold on. I have a solution for ATT too. I tried something last night. Actually while I was working on a solution for ATT I found that we don't even have to go through the steps I mentioned in my OP to solve the problem. It boils down to invoking a service and killing a native VZW service.
The ATT solution I have works but in low signal area 4G fades and it doesn't fallback to 3G or H+. I had to recycle data to get 3G or H+.
Click to expand...
Click to collapse
Yes, that same thing happens when you switch to CDMA mode with AT&T. Voice doesn't work then (obviously), but it also doesn't fall back to H+ automatically, when you lose 4G coverage you pretty much lose signal all together.

konradsa said:
Yes, that same thing happens when you switch to CDMA mode with AT&T. Voice doesn't work then (obviously), but it also doesn't fall back to H+ automatically, when you lose 4G coverage you pretty much lose signal all together.
Click to expand...
Click to collapse
Yeah I know. I also know why that is happening. Actually I think it's a bug in the baseband firmware. But we can fix that issue by just overriding the command that was sent by baseband firmware.

ron.r said:
It's Working!!!!!!!!! Thank you!!!!!!!
You just made my life much better now!
I finally have a phone which is great and also finally have good reception!
I Love U!
Click to expand...
Click to collapse
Lol.. rep me in SD :laugh:

konradsa said:
Yes, that same thing happens when you switch to CDMA mode with AT&T. Voice doesn't work then (obviously), but it also doesn't fall back to H+ automatically, when you lose 4G coverage you pretty much lose signal all together.
Click to expand...
Click to collapse
Do you have a working fix for AT&T/Cricket? Is it different than the T-Mobile?

motorhead_biker said:
Lol.. rep me in SD :laugh:
Click to expand...
Click to collapse
Ha! You are repped!
What root did you use? and steps?
easyroot?
did you split the file and merge it back?

I must have really bad luck or something. It doesn't work for me. The Tbsr_cdma timer resets back to 2 at reboot.
Edit: Appears to be working. Nice job!

renoob said:
Ha! You are repped!
What root did you use? and steps?
easyroot?
did you split the file and merge it back?
Click to expand...
Click to collapse
Root? I just flashed the rooted sys image. That's it. instead of copying it in the FAT32 memory card just copy it to your phone's internal and you don't have to deal with split and merge stuff

If it drops out of 4G on a call then you're talking on 1X. So no video chat, no HD voice and no voice + data?

HTC One M9 - GSM Network Issue

Hello guys!
My HTC One M9 is giving me some headaches!
What is happening is that if I'm inside home, I cannot get GSM network. This happens for both voice and data.
As soon as I go outside, I get the 4G working like a charm. I could live with this, but sometimes I need to sleep inside home
From my troubleshooting around this, I found out that if I reset the phone, there is no change.
Reset network settings does nothing.
Sometimes if I restart the phone I get network, but it goes away quickly.
No change if I enable and disable the flight mode.
What does work is if I set the network mode to be 2G only, then I have the network and all works (except the data with some low speeds).
The phone is now with the build 4.28.401.3
I've tried different RUUs and it is the same thing.
Can someone help to try to understand what can be the cause for this?

.... could it be a network issue?

computerslayer said:
.... could it be a network issue?
Click to expand...
Click to collapse
Of the phone, yes.
I've tried the SIM card on another phone and it works really great! I've tried a different SIM card on this phone and it is the same thing. Loss of connectivity.

kulyboy said:
Of the phone, yes.
I've tried the SIM card on another phone and it works really great! I've tried a different SIM card on this phone and it is the same thing. Loss of connectivity.
Click to expand...
Click to collapse
Yes, I have noticed a similar issue and it has been very annoying. I know that in my area, I can get 4g+, but it only picks it up sometimes and goes away. Also, I have very strong 4g signal around my area but for some reason, it always uses 2g and sometimes gives my 4g, but rarely. I think it has something to do with the way sense automatically switches between networks.
Try typing in *#*#4636#*#*, press phone information and where it says some thing like lte/wcdma auto and select what you prefer. I chose lte/wcdma and now I only get 4g and 3g signals which is acceptable. If you want GSM or something, choose it as preferred. Play around with the different ones and see which is best for you.
If not, try a non sense rom, I don't know if that would help but give it a go.
Hope this helps,
Jev

Well, I've tried different settings, but it does the same. Only when using 2G or GSM only it works inside home.
I am yet to test with a non-sense ROM. Because for me, having an HTC is also because I like sense.
Either way, it seems to me that it can be hardware and not software.
Do someone knows what controls this network settings? A different board? A chip?

You mention applying the Nougat RUU for your phone - did you first update to Nougat via OTA?

The update was made via OTA. A regular update but this was already happening before the update.

kulyboy said:
The update was made via OTA. A regular update but this was already happening before the update.
Click to expand...
Click to collapse
:-/ Darn. Good on you for updating correctly, for sure, but that eliminates the problem I was anticipating.

Could be a carrier issue. If the other phone that has a good signal is an m9 then obviously your phone has a fault. If it was a different model and/or brand then you should learn something about "industry standards" as far as signal detection and interpretation goes. Just because one certain type/model/brand of phone has a good signal it doesn't mean another "has to".
Beamed in by telepathy.