Fix capacitive button behavior instead of turning them off (root) - T-Mobile Samsung Galaxy S6

I own a W8 and I was playing around with CSC codes this afternoon trying to figure out how to call different data icons to the signal status bar. I was changing things around left and right. Imagine my surprise when on one of my reboots my capacitive buttons started displaying the same behavior as the US variants. Apparently the capacitive button behavior is in the CSC codes.
It seems that this tweak breaks Wifi Calling in its current form.
However, if you like the behavior of the buttons and don't use Wifi Calling, whereby they only turn on when you touch the buttons themselves and don't turn on every time you touch the screen, this may be a neat little trick for you to try. You can always undo it if you notice undesirable effects. There is probably no chance of bricking your device after just editing things in the csc folder so you don't have much to lose.
All you have to do is change your sales code to a device that was not manufactured for America.
If you're lazy you can flash this zip. However, the change is very simple:
In the folder /system/csc/ open the file sales_code.dat. This file probably says TMB.
Change it to one of the following codes and reboot
KDO - Koodo
TLS - Telus
RWC - Rogers
BMC - Bell
If you have disabled the capacitive buttons in the Galaxy Buttons app or in adb you'll have to re-enable them to see these changes
Everything still functions normally on my phone even after changing the sales code to TMB, and the only thing I've even noticed this change so far is the button behavior. This makes me think there is a hidden csc string somewhere and T-Mobile/VZW in their brilliance decided to enable it.

Didn't change for me. Have you googled cc edits? There's all kinds of crazy stuff out there.

mikeyinid said:
Didn't change for me. Have you googled cc edits? There's all kinds of crazy stuff out there.
Click to expand...
Click to collapse
cc or csc?
Interesting that it didn't work for you. So many inconsistencies out there between the variations. I'm tempted to flash a T rom now and try to make it work myself.
Would you be interested in making a backup of your csc folder and trying the stock w8?
Edit: I'm also at the moment not using the keystrings.dat file. You could also try renaming TMB_keystrings.dat as a backup and leaving it uncalled or try using my KDO_keystrings instead.

Have you tried flashing 920T rom? If so, what doesn't work?
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
I replaced my csc stuff with yours. Don't see any difference.

mikeyinid said:
Have you tried flashing 920T rom? If so, what doesn't work?
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
I replaced my csc stuff with yours. Don't see any difference.
Click to expand...
Click to collapse
I just uploaded my keystrings.dat also, which is called in the contents.db. You could try either removing the file entirely or replacing it with the one I uploaded
I'm rushing out the door right now and I'm not sure when I'll have time to try flashing a T rom.
My issues with the T rom might've been isolated to too much bloat removed from XtreStoLite. I'm thinking I'll give your version a try -- basically I had two issues with apps. Opera force closed on start and Pushbullet would randomly log me out thus killing push notifications. That paired with the capacitive button annoyance was enough to push me back to stock.
One last edit: one thing I've noticed is that some variants use features.xml for csc codes and others use other.xml for csc codes. Are both are variants in line using other.xml?

Ours uses features and others. Others overrides features though.

This stuff drives me crazy! Like why can I get my shake sensor working with ambient display but you can't?
(╯°□°)╯︵ ┻━┻

Speaking of CSC codes, I recently decided to go back to stock via Kies Firmware Recovery. Model # and SN # pulled up my correct CSC firmware which is Rogers RWC. Upon flashing, and boot, it defaulted to Bell BMC and installed the Bell apps. Plugged in and tried Smart Switch and it said phone is BMC. Did a flash via Smart Switch and same thing.
Tried full firmware flash via Odin and same deal. Defaulted to BMC upon boot even with a Rogers SIM.
Tried without a SIM inserted but no dice again.
Factory resetting in stock recovery gives you a text at the bottom something along the lines of Multi-CSC BMC activated.
None of the CSC changer apps worked on the S6 even when rooted.
Finally found the old school dialer way *#272*IMEI# and got to menu for all Canadian carrier codes including the smaller regional ones and was able to pick RWC. Phone rebooted but I didn't loose anything I had installed which was a pleasant surprise!
---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mikeyinid said:
Have you tried flashing 920T rom? If so, what doesn't work?
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
I replaced my csc stuff with yours. Don't see any difference.
Click to expand...
Click to collapse
Heh heh heh. You sure you perm'd everything correctly? Mod is working perfectly for me at the moment. Just flashed your stock rom applied a bunch of changes and the lights turn off. I'm gonna reverse each step to see where exactly you ended up running into issues

What the... So, it boils down to this. The only change I made to turn the buttons off is changing the code from TMB to KDO in sales_code.dat
Good grief.
I dirty flashed over my w8 data, so incoming data wipe I guess.

@mikeyinid Freshly installed your odex'd rom, wiped all caches, data and system. Installed SU, made one single modification to the sales_code.dat and it works.
Anyone else on a T variant feel like testing this? I can see absolutely zero reason this shouldn't be working...

@mrapp when I tried it earlier I only did a hot reboot, and it didn't affect anything. I just changed it again and did a full reboot. Now I'm seeing the same behavior as you. Much better ?

mikeyinid said:
@mrapp when I tried it earlier I only did a hot reboot, and it didn't affect anything. I just changed it again and did a full reboot. Now I'm seeing the same behavior as you. Much better
Click to expand...
Click to collapse
WOOO!!!:good::laugh:

I think this breaks Wifi Calling. After changing to KDO, it would just get stuck on 'enabling'

piccit said:
I think this breaks Wifi Calling. After changing to KDO, it would just get stuck on 'enabling'
Click to expand...
Click to collapse
Indeed it does.

piccit said:
I think this breaks Wifi Calling. After changing to KDO, it would just get stuck on 'enabling'
Click to expand...
Click to collapse
You could try using rwc. You also may need to add a csc code? I had a feeling this would happen.

I don't have time to look into this this morning, but if any one wants to take a look, there are two places I'm going to look. Features.xml in XtreStoLite s5 and the xtrestolite in the dev s6 forum. Or perhaps @edgarf28 would be able to chime in

I had 2 seconds to look here -- I will look more in depth later. Does this CSC code do anything to help?
Code:
<CscFeature_IMS_EnableRCSe>true</CscFeature_IMS_EnableRCSe>
Turn off wifi then disable wifi calling, then re-enable wifi connection.

@mikeyinid @piccit Can you please try adding this line to your features.xml or others.xml?
Assuming you guys still have the stock features.xml, everything you need should still be there. We don't have wifi calling up here and it may be that it never works. Rogers is a network that is/will be supporting VoLTE, so changing to RWC as your code might be something to try if you havn't tried that code yet.
Code:
<CscFeature_WFC_EnableSamsungWfc>true</CscFeature_WFC_EnableSamsungWfc>
Then just make sure you try cycling wifi calling as such:
Turn off wifi then disable wifi calling, then re-enable wifi connection.
Is VoLTE still working?
Unfortunately, I have no way of testing this service. I *do* have a t-mobile sim though. However, my device is locked to Koodo and popping in my sim still produces and Error: Invalid Sim for me

@mrapp, on stock RWC, button only lights up when you touched them and stayed off when you were just touching the screen!
Saying that, when I owned the Optimus G, it worked this way on ICS and when the Rogers update for JB came out, it remained on as long as you were touching the screen and I had to flash an Australian KDZ for it to stay off after 1.5 secs!

Related

[Q] XT862 no data on Page Plus

I accidentally hijacked a thread over in the Epic forum when I came across someone with my exact symptom. I figured I should move my conversation over here so my apologies if it appears that I've "double posted".
I've been searching, reading and trying various 'fixes' for a couple of weeks now with no luck, so I'm hoping someone here might be able to help me out. A little background:
I have a Droid 3 with:
Stock GB 2.3.4
System version is 5.7.906.XT862.Verizon.en.US
Baseband version: N_03.18.29P
Build number: 5.5.1_84_D3G-66_M2-10
The only modifications I made was to root the system and remove some bloatware. I was able to activate the phone on Page Plus for voice and text but no data or mms (of course since mms relies on data). Interestingly, the OTA programming *22890 fails - I had to use the Verizon programming *228 to get it to work. I'm thinking that this might be related to my problem.
After a lot of attempts to resolve, including factory reset, I realized that when I tried to write to the evdo settings the passwords were not being written. After reviewing the cdma workstation output (licensed copy of cdma ws so all functions should work) I found that it was logging "access denied" errors on those particular fields. I also can't modify the HA / AAA shared secret codes in the m.ip profile. I even tried creating a new profile and those fields were protected in the new profile as well. So something is locking those fields - which I assume is the root of my problem. The SPC is the standard 000000.
I also tried using DFS cdma tool with no luck. Something else I noticed using this tool is that there is a section for Lock Codes on the General Tab. When I read these codes from the phone, the Lock extd: field was 11111111. So far I haven't been able to find out what this field is for or how it is used. I don't know if it's related in anyway to blocking access to the data password fields, just thought it was worth mentioning.
Sorry for the long post. Hopefully there's something in my ramblings that will trigger a solution. Any and all suggestions are welcome. Thanks.....
activating and using Droid 3 on page plus should not require any programming
problem could be hardware or software
check
menu>system settings>battery & data manager>
data saver should be uncheck, unless you are trying to limit data usage
and
menu>system settings>battery & data manager>data delivery
check 'data enabled'
check 'background data'
if those are correct
I would just flash the 906 sbf and wipe data, if that does not fix problem is likely hardware
Flash xml recovery files (Stock Rom) with RSD Lite
sd_shadow said:
activating and using Droid 3 on page plus should not require any programming
problem could be hardware or software
check
menu>system settings>battery & data manager>
data saver should be uncheck, unless you are trying to limit data usage
and
menu>system settings>battery & data manager>data delivery
check 'data enabled'
check 'background data'
if those are correct
I would just flash the 906 sbf and wipe data, if that does not fix problem is likely hardware
Flash xml recovery files (Stock Rom) with RSD Lite
Click to expand...
Click to collapse
Thanks for the input. Already did all that. Kinda doubt that it's hardware though. There's always the remote possibility, but my money is on software at possibly the microcode level that's holding those fields in read-only mode.
Maybe SBF the Verizon 862 or 906 ROM?
Ya. Same as everyone else, sbf. BUT also master reset after sbf. Use the latest full sbf that I link to in my thread.
If you know all then proper settings for Ppc then Check a cricket forum for a how to flash and you'll be able to program them and then *22890 to get 3g keys.
Tldr: sbf from my thread + master reset after sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------
Your baseband may be gsm unlocked variant, I definitely recommend sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
afextwin said:
Ya. Same as everyone else, sbf. BUT also master reset after sbf. Use the latest full sbf that I link to in my thread.
If you know all then proper settings for Ppc then Check a cricket forum for a how to flash and you'll be able to program them and then *22890 to get 3g keys.
Tldr: sbf from my thread + master reset after sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------
Your baseband may be gsm unlocked variant, I definitely recommend sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've already tried to flash the sbf at the 906 level (I happened to have used the same file you referenced in your thread) but didn't do any kind of reset after I installed it. When you say 'master reset' do you mean factory reset? I've done a factory reset a couple of times but not immediately following sbf. What would the reset do that the sbf didn't already cover? Or is there another 'master reset' that I've missed? It'll be a bit of work to redo the sbf since that means reloading apps, resetting screens, etc.. Since this is the Mrs.' phone I'll need to make sure I've covered any and all other bases before I go this route.
Also, I've tried manually programming and inputting all of the programming info via cdma ws, dfs, radiocomm, and qpts all to no avail. Tried auto programming via *22890 which fails. Auto programming via *228 works but only gives me talk and text.
Thanks for all of the feedback and suggestions. Much appreciated......
do you have baseband N_03.18.29P or N_03.18.32p or other
sd_shadow said:
do you have baseband N_03.18.29P or N_03.18.32p or other
Click to expand...
Click to collapse
N_03.18.29P
so you're not on a complete 906 version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
I would retry VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip
verify the md5:8C33C373BD309AA40C8EBDB458E426F1
flash with rsdlite
sd_shadow said:
so you're not on a complete 906 version.
(Images removed)
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
[/COLOR]I would retry VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip
verify the md5:8C33C373BD309AA40C8EBDB458E426F1
flash with rsdlite
Click to expand...
Click to collapse
I was also playing around with swapping radios so that's probably why there's the baseband discrepecy. Although it's a pain it's probably prudent to spf again to ensure that everything is at a base level.
nvrpayretail said:
I was also playing around with swapping radios so that's probably why there's the baseband discrepecy. Although it's a pain it's probably prudent to spf again to ensure that everything is at a base level.
Click to expand...
Click to collapse
The 890 radio works fine on 906. You can try an esn reset on PagePlus then redo the ota programming to generate and grab new auth keys. I had to do this before on a Droid X on PagePlus.
A free reset tool can be found here. Basically it refreshes your meid in the system like a new device for new auth keys.
Skreelink said:
The 890 radio works fine on 906. You can try an esn reset on PagePlus then redo the ota programming to generate and grab new auth keys. I had to do this before on a Droid X on PagePlus.
A free reset tool can be found here. Basically it refreshes your meid in the system like a new device for new auth keys.
Click to expand...
Click to collapse
this was to be my next suggestion, if after sbf to 906 you still had no data. Basically what happened was, your previous device held the 3g signal when you swapped esn's so new key's could not be generated when otap was performed (oddly enough, the old device may still have a working data connection...)
edit: post #100, hopefully it contain's some sort of factual useful information for someone.
Skreelink said:
The 890 radio works fine on 906. You can try an esn reset on PagePlus then redo the ota programming to generate and grab new auth keys. I had to do this before on a Droid X on PagePlus.
A free reset tool can be found here. Basically it refreshes your meid in the system like a new device for new auth keys.
Click to expand...
Click to collapse
Thanks for the suggestion. Something I hadn't heard of before. Gave it a shot but no joy...... *22890 still fails and have to use *228. Programming took a long time so I was hopeful but alas still no data. arghhhhhhhhhhhhhhhh.......
afextwin said:
this was to be my next suggestion, if after sbf to 906 you still had no data. Basically what happened was, your previous device held the 3g signal when you swapped esn's so new key's could not be generated when otap was performed (oddly enough, the old device may still have a working data connection...)
edit: post #100, hopefully it contain's some sort of factual useful information for someone.
Click to expand...
Click to collapse
Interesting. Although the reset that Skreelink suggested didn't work, you and Skreelink might be onto something.
A little more background. This phone # was ported over from VZW. When on VZW we were using a Samsung SGH-U960. Since I didn't have a data plan, VZW disabled data. When I did the port to PP I activated the Droid 3 at the same time.
For grins, I just turned on the Samsung and it shows a data connection. When I try to access the web I can see the data connection active trying to access Verizon Mobile Web. Of course since I'm not on VZW, it doesn't actually work and I get a message to dial *611. I then turned on an LG phone that was used previously on VZW and it too shows a data connection but when I try to access the web from there it immediately gives me a 'network unavailable' message. So I'm wondering if somehow the data is indeed still linked to the last phone used on VZW. One more fly to throw into the ointment is that for a brief time while I was working on the Droid 3 I switched the PP service to the Samsung so the wife wouldn't be without a phone. When I was done I switched PP service back to the Droid 3 so you'd think that any crossed records would have gotten straightened out during that exchange. But who knows. Any suggestions which way to go from here?
I suggest contacting page plus
Sent from my XT862 using Tapatalk 2
sd_shadow said:
I suggest contacting page plus
Sent from my XT862 using Tapatalk 2
Click to expand...
Click to collapse
@nvrpayretail definitely contact page plus or PM me, I can swap your number to a phone here and see if it works (cust svc can do same thing).
the data block should not stick for your line after you ported, the data block is an account setting and technically you don't have an account with vzw anymore.
afextwin said:
@nvrpayretail definitely contact page plus or PM me, I can swap your number to a phone here and see if it works (cust svc can do same thing).
the data block should not stick for your line after you ported, the data block is an account setting and technically you don't have an account with vzw anymore.
Click to expand...
Click to collapse
I'll try PP but they generally take a hands off approach if you don't have one of their 'supported' phones. I can understand their position. I have a couple of retired old phones here so I can have PP swap to one of them to see if I have the same problem. Thanks anyway for the offer.
nvrpayretail said:
I'll try PP but they generally take a hands off approach if you don't have one of their 'supported' phones. I can understand their position. I have a couple of retired old phones here so I can have PP swap to one of them to see if I have the same problem. Thanks anyway for the offer.
Click to expand...
Click to collapse
Yes, thats why I suggest calling me, I work for a page plus master. Trust me, I know how hard it is to get general cust svc to do ANYTHING on a non-native device, but it's not their fault, if they did then call hold times would be outrageous or plan prices would go up to pay for all the additional csr's. I suggest that if they tell you it's not supported, then ask them for ITCC support. Or it may be ITTC support, I'm not sure what the acronym stands for but basically if the phone is not in their supported devices list but is a verizon branded 2g or 3g phone it may be in their ITTC list and they can conference chat with you and a verizon rep to further troubleshoot. Sadly, if the line is bad because of the data block being "stuck" you may have to lose the line...Porting out and back in may be an option if this is the case, but I've never tested the theory, it probably won't work - i'm sure Verizon keeps previous customer's accounts in a "dormant" state for an infinite amount of time.
afextwin said:
Yes, thats why I suggest calling me, I work for a page plus master. Trust me, I know how hard it is to get general cust svc to do ANYTHING on a non-native device. I suggest that if they tell you it's not supported, then ask them for ITCC support. Or it may be ITTC support, I'm not sure what the acronym stands for but basically if the phone is not in their supported devices list but is a verizon branded 2g or 3g phone it is in their ITTC list and they can conference call with you and a verizon rep to further troubleshoot.
edit: As explained to me by Lisa about 2 years ago...
Click to expand...
Click to collapse
Thanks again for the additional info and suggestion. I generally do every thing I possibly can before contacting vendor support since it's usually a rather frustrating experience. That's a general support comment - not targeted at PP. I've gotta be in the right mood to deal with the poor level 1 support folks (definitely not on a Friday the 13th evening ) before I call them.
I opened a trouble ticket online and will wait to see what they come back with before getting on the phone with them. Who knows, maybe a miracle will happen and some research will actually be done before they try to say 'it's not our problem'
Am I having fun yet???
edit: Alas, I received canned response #103.6 back from level 1 support. Attempting to escalate to ITT(C)C support as afextwin suggests. I don't have much confidence that it will go anywhere. Assuming things stay status quo I guess I'll see if one of my older, retired phones will work and go from there.
So, of course things went as expected with support. Escalated to level 2 and their take was "sorry, ain't our phone". I finally bit the bullet and and did a complete wipe (at least as complete as I could figure out to do, and started from scratch flashing the VZW base flash. I went straight to activate before rooting or anything and surprise, surprise ABSOLUTELY NOTHING CHANGED!!!! In the process I lost my nand backup (of course!!) so it's back to manually reinstalling and setting up everything.
I think I'm at the point where I've fought the phone and the phone won
I sincerely thank all that tried to help.

[Q] Mobile Network Settings missing data

So I just got a new M7 swapped over and decided to let it update with Sprint to the newest revision prior to S-off, unlock, etc. Now, no matter what ROM I seem to flash, my Mobile Netowrk Settings simply show Four options -
4G Settings
Network Mode
Access Point Names (gray)
Available GSM networks (gray)
I have no option to changes to home network, roam only, automatic, etc. My wife's stock phone has all the other settings in there such as roaming, automatic connections, etc.
I'm thinking I need to RUU? Reprovision with sprint? (they screwed up the first time and my SIM wasn't linked to my account when I swapped phones so they had to do that - don't know if that has any bearing.) And the phone does work - so.....
Thoughts?
Also just to add,
HBoot 1.57
Radio 1.01.20.0515
Thanks!
Bump on this....
Would an RUU to an older version work? If so - do I have to downgrade the HBOOT and firmware to do this? If yes - if someone can point me at the right thread for the process, and recommend what version to revert to it would be most helpful. Been searching all day for this, and I've found multiple threads on how to do different things, but a specific "Do this followed by this" would be great rather than bricking the phone - which is possible considering I can only seem to run a single RUU on the device (the newest one) and if I break something, I'll have nothing.
It just seems that Roaming isn't there - everything else works just fine... I'm thinking maybe it's just the radio or a setting someplace....But I'm racking my brain.
Anyways, Thanks for letting me rant.
cubexg said:
Bump on this....
Would an RUU to an older version work? If so - do I have to downgrade the HBOOT and firmware to do this? If yes - if someone can point me at the right thread for the process, and recommend what version to revert to it would be most helpful. Been searching all day for this, and I've found multiple threads on how to do different things, but a specific "Do this followed by this" would be great rather than bricking the phone - which is possible considering I can only seem to run a single RUU on the device (the newest one) and if I break something, I'll have nothing.
It just seems that Roaming isn't there - everything else works just fine... I'm thinking maybe it's just the radio or a setting someplace....But I'm racking my brain.
Anyways, Thanks for letting me rant.
Click to expand...
Click to collapse
Do the options appear with stock?
No and that's what's making me think it might be carrier related. But not sure what I could tell sprint to do. The only change on my account was adding international roaming for an upcoming trip. Maybe it's the Sim card I transferred from the old phone?
cubexg said:
No and that's what's making me think it might be carrier related. But not sure what I could tell sprint to do. The only change on my account was adding international roaming for an upcoming trip. Maybe it's the Sim card I transferred from the old phone?
Click to expand...
Click to collapse
Probably. Try going stock and doing a PRL update and all that jazz. To go stock you need to RUU. But before that could you go into the HBOOT menu (by pressing VOL DOWN + POWER) and take a picture of the menu you see there (should be some text in multiple colors with a white background), and post it here?
I did that already - went stock with the newest RUU- that works but same result. PRL update and the like all resulted in the same.. Did it last night. Let me get you a sccreenshot of the bootloader screen..
Also running on ViperOne 5.8.0 right now with TWRP installed.. Tried BadBoyz Sense 6.0 - same result. Stock - same result.. (tried both last night)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also here's the actual screen itself in mobile network:
cubexg said:
I did that already - went stock with the newest RUU- that works but same result. PRL update and the like all resulted in the same.. Did it last night. Let me get you a sccreenshot of the bootloader screen..
Also running on ViperOne 5.8.0 right now with TWRP installed.. Tried BadBoyz Sense 6.0 - same result. Stock - same result.. (tried both last night)
Also here's the actual screen itself in mobile network:
Click to expand...
Click to collapse
You'll probably have to take it to Sprint then. RUU back to stock (if not already), and make sure that on the bootloader screen it says **LOCKED**.
StormyNight said:
You'll probably have to take it to Sprint then. RUU back to stock (if not already), and make sure that on the bootloader screen it says **LOCKED**.
Click to expand...
Click to collapse
Crap.. Ok - I can do that... Have to get it back to S-On and fix that.. Have to remember how to do it... I think I used RevOne to get S-Off... can you point me to the thread to relock?
cubexg said:
Crap.. Ok - I can do that... Have to get it back to S-On and fix that.. Have to remember how to do it... I think I used RevOne to get S-Off... can you point me to the thread to relock?
Click to expand...
Click to collapse
Never mind - figured out the relock - sure I can figure out S-On as well... Thanks for the help. Off to sprint tomorrow.. maybe they can fix.. /sigh/
Resolution
So, just wanted to update this post in case anyone else ever comes looking for this info like I did. Here's what happened:
Walked into a Sprint Corp store @ 10.00 when they opened with stock locked phone running newest version from an RUU I did last night. All my data restored from the cloud, etc.
Went right up to lead tech, explained the issue, showed it to him, and he was, admittedly, baffled. We compared the screen to an M8, an M7, etc. He took the phone in the tech area, and I hung out with him whilst he worked on it. After 50 minutes of playing with it, attempting to reactivate it, so on and so forth, he finally grabbed another refurbished that came in from the center. Powered it on, and low and behold the SAME issue. (That phone was not activated). At this point, I asked him to try swapping SIMs - maybe it's a problem with provisioning. He did this - same issue on my device. Finally, he suggested swapping me into a new device to see if that help. Of course, not going to turn down a new device, but this was after almost two hours of attempts to fix things.
We get the new device turned on and after the system provisions, believe it or not - the same issue.. The phone, factory new, doesn't have roaming options. We're both staring at each other is disbelief. We then see that the phone hadn't completed it's provisioning yet - and figured we should wait another few minutes for handsfree to finish. What I saw next I hadn't seen before.
The phone rebooted itself and did an update.. Don't exactly know what it did, but it wasn't a full blown Android Update - it was something else - which I can only guess unlocked whatever options needed to be unlocked on the phone to allow for roaming - because after the unit booted back up everything that was supposed to be available was.
In summary, it looks like there is something that the phone downloads via the network from Sprint at time of initial activation to unlock certain functions in that mobile data screen (specifically the roaming). I don't know what it is - don't know if anyone knows, but I would say that if anyone ever encounters this again - the best solution seems to be going to sprint and standing there for a few hours while insisting it's a Sprint provisioning issue - because it is.
If anyone wants any other details, I'll post what I know - but that's about it.
I've got the same problem
cubexg said:
So, just wanted to update this post in case anyone else ever comes looking for this info like I did. Here's what happened:
Walked into a Sprint Corp store @ 10.00 when they opened with stock locked phone running newest version from an RUU I did last night. All my data restored from the cloud, etc.
Went right up to lead tech, explained the issue, showed it to him, and he was, admittedly, baffled. We compared the screen to an M8, an M7, etc. He took the phone in the tech area, and I hung out with him whilst he worked on it. After 50 minutes of playing with it, attempting to reactivate it, so on and so forth, he finally grabbed another refurbished that came in from the center. Powered it on, and low and behold the SAME issue. (That phone was not activated). At this point, I asked him to try swapping SIMs - maybe it's a problem with provisioning. He did this - same issue on my device. Finally, he suggested swapping me into a new device to see if that help. Of course, not going to turn down a new device, but this was after almost two hours of attempts to fix things.
We get the new device turned on and after the system provisions, believe it or not - the same issue.. The phone, factory new, doesn't have roaming options. We're both staring at each other is disbelief. We then see that the phone hadn't completed it's provisioning yet - and figured we should wait another few minutes for handsfree to finish. What I saw next I hadn't seen before.
The phone rebooted itself and did an update.. Don't exactly know what it did, but it wasn't a full blown Android Update - it was something else - which I can only guess unlocked whatever options needed to be unlocked on the phone to allow for roaming - because after the unit booted back up everything that was supposed to be available was.
In summary, it looks like there is something that the phone downloads via the network from Sprint at time of initial activation to unlock certain functions in that mobile data screen (specifically the roaming). I don't know what it is - don't know if anyone knows, but I would say that if anyone ever encounters this again - the best solution seems to be going to sprint and standing there for a few hours while insisting it's a Sprint provisioning issue - because it is.
If anyone wants any other details, I'll post what I know - but that's about it.
Click to expand...
Click to collapse
I've taken my husband's M7 to the Sprint Store, and the technician tried, but couldn't do anything at all. I thought it lost the roaming options when I downloaded the latest operating system, back around June 1. I called HTC, and the technician checked their Sprint M7, and it had the same issue, too. I'm waiting for HTC to call me and agree to replace the phone, but it sounds like the new one will most likely be the same way.
I guess I'll call Sprint and try to have them reprovision it.

Can't get VoLTE working. Euphoria ROM. VZW

Ok, this is frustrating. I can't seem to get VoLTE working. Clean flashed, and in the hidden menu there's this View attachment 3217747. I didn't ever set it to ON, so I don't know why the OFF option is there. Whenever I make a call, the LTE icon goes away, and no internet.
Not sure if this will help as I don't know what steps you have already taken, but have you gone through these steps first?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anastayja said:
Not sure if this will help as I don't know what steps you have already taken, but have you gone through these steps first?
Click to expand...
Click to collapse
Yep. added it to my plan. Is there an advanced calling app for us yet?
jova33 said:
Yep. added it to my plan. Is there an advanced calling app for us yet?
Click to expand...
Click to collapse
No, no app. Maybe you should try enabling on stock and then flashing back to Euphoria. Maybe that will help.
The rom is likely missing necessary components
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
The rom is likely missing necessary components
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
No, it's not.
Anastayja said:
No, it's not.
Click to expand...
Click to collapse
Does it have ims.apk in system apps?
Sent from my Nexus 6 using XDA Free mobile app
Before I would get the setting and it would be enabled but I coudn't do simultaneous voice/data. I flashed stock but now i get server error try again later each time. weird.
I'm completely stock verizon nexus 6 (recevied mine yesterday in the mail), but I was having same frustration you describe. Could not use hotspot and browse internet while in a voice call. And it was always in 3g.
I don't know if this will help but here is what I did.
first I did the hidden menu... *#*#4636#*#*
tapped the volte provision option and then I forced a power down.
After powering up I confirmed that the Enhanced 4G LTE was enabled in settings.
I went back into the hidden menu and confirmed that volte provision was turned on. It was because it now showed the "Turn OFF volte" option instead of "Turn On".
I retried using internet/data while in a voice call and the phone still would not allow data while in the call. I could only get 3g in hotspot and voice calls would still interrupt data.
I then learned that I had to enable HD or whatever the new service is called on my Verizon account. They said in the webpage instructions that I may have to reboot and check for system updates. And to wait about 15 minutes for it to take affect.
I rebooted, forced a check for new system updates (there were none), and then I tried retesting by turning on hotspot (still was just 3g) and trying to place a call while using hotspot and browsing from my laptop. As soon as the voice call was made I could no longer browse the internet using hotspot... basically same as it always had been. I was frustrated to the point of seriously considering returning the phone to verizon.
Then I went back into the hidden menu and changed the radio option to "USA" (the option in upper right corner of that hidden menu.) I don't know what it was set to previously but I never leave the country so USA is good enough for me.
I rebooted again and to my pleasant surprise, it showed nearly full bars in LTE and hotspot/internet worked great all while in a voice call.
*Solution? I'm not sure if it was just my repeated reboots that did it, or if it was that last radio USA option I selected, or if it just took 15 minutes or so for Verizon to update my account to enable the HD (or whatever it is called).
Again, I'm completely stock vanilla on Verizon. But my frustration sounded very much like yours so maybe this will help you situation. Good luck
[email protected] said:
Before I would get the setting and it would be enabled but I coudn't do simultaneous voice/data. I flashed stock but now i get server error try again later each time. weird.
Click to expand...
Click to collapse
No one else?
[email protected] said:
No one else?
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/nexus-6/general/verizon-nexus-6-verizon-users-volte-t3058117
This worked for a few people and it was confirmed having the same issue ur having.
People keep bring up these steps are useless but like i said i have people confirmed this works over the other method.
Hope it helps
I followed all of the steps in the tutorials with no success. I have MultiRom installed along with ElementalX as my kernel as it supports MultiRom. I installed Scott's 5.1 stock rooted rom as a secondary rom and made sure the settings were correct for VoLTE. HD Voice was working as well as voice/data over 4G. When I booted back into Euphoria, everything worked great. This is what worked for me, but your mileage may vary. It's crazy that people are having to do so many steps and workarounds to get the features active on the same hardware and essentially the same core software.

Phone must reboot

Hello everyone,
I've noticed starting last week my G4 will have a old android style pop-up stating "Device must restart to allow service to continue. Device will restart in ## seconds." It has reboot and later as the options, and will continue to pop-up if i hit later and will even do this when the screen is locked randomly. It is starting to become more often.
I have:
Rebooted phone
checked for apps at cause
Wiped phone with factory reset
updated PRL and other update options (no updates available)
Seems some people here had the same issue on their S5's but with no answer to what was causing it fully
http://forum.xda-developers.com/gal...service-to-t3049657/post60225538#post60225538
Thanks!
Government monitoring you?
I had one pop-up yesterday, we'll see what happens today. If it does I'll post back here. Thanks for the reply back!
Just had one pop-up, requiring me to restart or click later. I'm starting to get frustrated at this. My wife and my co-worker have the same phones, and they have not received this message at all before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in-case the link above does not work here direct: http://imgur.com/xGjDQdU
Does it happen on both WIFI and Cell Network?
Are you using WIFI Calling?
mswlogo said:
Does it happen on both WIFI and Cell Network?
Are you using WIFI Calling?
Click to expand...
Click to collapse
It can happen on both WiFi and Cell network. I do use WiFi calling as my work area is prone to dead signal areas for any carrier. It is completely random as I can be at home on WiFi calling or at the mall on Cellular and it reboot itself due to that message.
Jessooca said:
Did you get your issue fixed? PM me if you need help still.
Click to expand...
Click to collapse
Hi Jessooca, I sent you a PM
I am having this issue now o.k. two phones.
Our problem started after rooting. I followed @rirozizo's video guide on the cubes post. I installed "root checker" that was mentioned on that video as well.
Now every few hours I have the pop up. One time, I was able to press the square key to bring up the multi window/tab view and the name of the tan with the restart message was called Network System Provider.
The window appears, as described in the OP, and states Device must restart. Device will restart in XX seconds.
I did just try clearing the cache for Network System Provider. Hopefully that helps....
Any and all help anyone can offer will be appreciated.
Thank you
Im a troll said:
Hi Jessooca, I sent you a PM
I am having this issue now o.k. two phones.
Our problem started after rooting. I followed @rirozizo's video guide on the cubes post. I installed "root checker" that was mentioned on that video as well.
Now every few hours I have the pop up. One time, I was able to press the square key to bring up the multi window/tab view and the name of the tan with the restart message was called Network System Provider.
Any and all help anyone can offer will be appreciated.
Thank you
Click to expand...
Click to collapse
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
rirozizo said:
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thank you so much.
I will check the SIM, although, I feel pretty confident that it's something else. My reasoning is that it's happening to both our phones and started within hours of being rooted ( I rooted them within minutes of eachother). The only new app installed after rooting on either phone was root checker. The months prior had no issue at all, and Now both are having the same issue at once...unless both SIM card trays got dirty at the same time which would be very coincidental.
I well try your suggestion though. Thank you.
Im a troll said:
Thank you so much.
I will check the SIM, although, I feel pretty confident that it's something else. My reasoning is that it's happening to both our phones and started within hours of being rooted ( I rooted them within minutes of eachother). The only new app installed after rooting on either phone was root checker. The months prior had no issue at all, and Now both are having the same issue at once...unless both SIM card trays got dirty at the same time which would be very coincidental.
I well try your suggestion though. Thank you.
Click to expand...
Click to collapse
Now i don't know anything about Sprint and "american services" but did you flash the right system image specifically for your device? maybe some Sprint service is lost and it's just bugging out? just a blind guess here
rirozizo said:
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
rirozizo said:
Now i don't know anything about Sprint and "american services" but did you flash the right system image specifically for your device? maybe some Sprint service is lost and it's just bugging out? just a blind guess here
Click to expand...
Click to collapse
I appreciate your guesses! I am stumped myself so I will gladly accept any and all help.
I double checked to be sure, and yes I did use the correct files and commands.
The problem presents itself every few hours, so I will see if it continues now that I have cleared the cache I mentioned before.
Thank you again and thank you much for the wonderful videos
I see so many posts in this forum with odd issues and later find they are running unlocked in another country.
Are you in USA on a Sprint Network and getting this error?
I doubt it's the SIM card too.
If on Sprint network you might try ##72768# Hands Free Activate.
Be sure you are near a solid Sprint Signal and WIFI for backup.
Also I find adblocking software gives Sprint phones fits now.
OP Chiming in here, my phone has never been rooted, and is experiencing this issue still. I have flashed the TOT file and also done a recovery factory restore with no luck.
I can clean the sim card real quick and see how it goes today, I am however heading to a Sprint repair tech this weekend to have a new sim card placed in to see if it works.
Get your service code and do an RTN reset. It will wipe your internal storage so just click and drag from your G4 to a place on your desktop. If an RTN doesn't fix it, call Sprint.
Jessooca said:
I replied to your PM hopefully if you go through all those steps, it will fix your issues.... For whatever reason the issues seem to arise if you have factory reset your device, after you have rooted it; theres no proof that's the cause but in most cases, not all, this seems to be a perpetrator. ROOT that is, this issue has happened on various other devices, from 4.4.2 all the way up to a friends Nexus 6 running Android 6.0....
If it fixes your issues; I will share the steps here for anyone else.
Click to expand...
Click to collapse
Hi Jessooca,
I just sent you a PM as well.
Just so everyone is clear, Jessooca is amazing!
Having said that, I am both happy and sad to report that the problem may be solved ( I am not sure and will wait and see). I noticed that twice in the multi-window view brought up by pressing square (forgive me for not knowing the correct term) that the window with the restart message was titled Network System Provider.. so I googled...and then I went through my apps looking for the matching icons. I then found that the error was part of an app by "Its on." Specifically two apps matched the icon; NetworkSystemProvider with an install date of 8/1/2008 (weird?) and NetworkSystemProvider UID with a install date of 5/7/15 ( the day I took the Sprint ZV5 OTA and then rooted).
What I then did was clear the cache of both apps and then of the phone via storage. I have not noticed nay pop-ups since then so I hope that my problem is fixed.
I am also unsure what those two apps are, if they were always there, and if I can safely delete them.
Best of luck OP. I will post again right away if my problem is not resolved, and clearing the cache did nothing more than fill me with false hope!
Im a troll said:
Hi Jessooca,
I just sent you a PM as well.
Just so everyone is clear, Jessooca is amazing!
Having said that, I am both happy and sad to report that the problem may be solved ( I am not sure and will wait and see). I noticed that twice in the multi-window view brought up by pressing square (forgive me for not knowing the correct term) that the window with the restart message was titled Network System Provider.. so I googled...and then I went through my apps looking for the matching icons. I then found that the error was part of an app by "Its on." Specifically two apps matched the icon; NetworkSystemProvider with an install date of 8/1/2008 (weird?) and NetworkSystemProvider UID with a install date of 5/7/15 ( the day I took the Sprint ZV5 OTA and then rooted).
What I then did was clear the cache of both apps and then of the phone via storage. I have not noticed nay pop-ups since then so I hope that my problem is fixed.
I am also unsure what those two apps are, if they were always there, and if I can safely delete them.
Best of luck OP. I will post again right away if my problem is not resolved, and clearing the cache did nothing more than fill me with false hope!
Click to expand...
Click to collapse
i dont have these two apps (i'm on international version, so no carrier stuff here)
I updated to ZV6 this morning and got this message for the first time this afternoon.
"Device must restart to allow service to continue"
After doing some reading, the problem seems to be related to ItsOn.
http://forum.xda-developers.com/spr...nt/zip-remove-itson-sprint-of7-based-t3154181
ItsOn is difficult to remove as it has service running even when the apk files are frozen or removed.

Carrier Code/Sales Code, Features or Flop?

I found a Caller/carrier menu code (not sure of real name). I was doing some reading and stumbled across a code that when you type it in your phone keypad as if you're making a phone call it lets you select a different phone carrier and it says something about sales code. I'm with Eastlink Mobility Canada so my code is currently set at (ESK) by the way its an eastern canada cable/Internet/mobile phone provider. The code I enter in my keypad is dialed just like your placing a call. It is exactly this... *#272*356631090050396# now I don't know if this works on all phones in all regions and so on and so forth but I am on the Qualcomm Snapdragon model and running Android 9.0 the latest update. I'm curious as to what this code does exactly and what changing the carrier settings to another carrier might do for me such as unlock Wi-Fi calling or some other cool features that are being held back from my mobile provider. Could anyone shed some light on what changing these menu options could possibly do for me, and do you know if I do decide to Tinker with it, will I be able to use the same code again, and turn back my carrier to its original (ESK). Any help would be great and I apologize if this is the incorrect form for this type of thing but it is a question-and-answer situation so I thought I would put it in this section.
Thanks & cheers!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWiiTCH said:
I found a Caller/carrier menu code (not sure of real name). I was doing some reading and stumbled across a code that when you type it in your phone keypad as if you're making a phone call it lets you select a different phone carrier and it says something about sales code. I'm with Eastlink Mobility Canada so my code is currently set at (ESK) by the way its an eastern canada cable/Internet/mobile phone provider. The code I enter in my keypad is dialed just like your placing a call. It is exactly this... *#272*356631090050396# now I don't know if this works on all phones in all regions and so on and so forth but I am on the Qualcomm Snapdragon model and running Android 9.0 the latest update. I'm curious as to what this code does exactly and what changing the carrier settings to another carrier might do for me such as unlock Wi-Fi calling or some other cool features that are being held back from my mobile provider. Could anyone shed some light on what changing these menu options could possibly do for me, and do you know if I do decide to Tinker with it, will I be able to use the same code again, and turn back my carrier to its original (ESK). Any help would be great and I apologize if this is the incorrect form for this type of thing but it is a question-and-answer situation so I thought I would put it in this section.
Thanks & cheers!
Click to expand...
Click to collapse
if you change ure CSC to an other it will reset your phone and should install that said carrier's bloat. technically if you set it to XAC(unbranded) it should not install any carrier bloat. while some carriers offer volte and wificalling, i am not sure if these features will still be there. recent updates seem to point that on xac, volte should stick but wificalling might not be there.
bober10113 said:
if you change ure CSC to an other it will reset your phone and should install that said carrier's bloat. technically if you set it to XAC(unbranded) it should not install any carrier bloat. while some carriers offer volte and wificalling, i am not sure if these features will still be there. recent updates seem to point that on xac, volte should stick but wificalling might not be there.
Click to expand...
Click to collapse
Thanks for the response. That was actually what I was hoping for. It seems most carriers here have Wi-Fi calling and when I go through my system app list it even shows an application called Wi-Fi calling. The only thing is it's not functional or usable or even accessible on my phone right now. I'm hoping somebody has tried it and might be able to tell me more but thanks for letting me know what you knew about it. Have a great night my friend. I'm off to bed
TWiiTCH said:
Thanks for the response. That was actually what I was hoping for. It seems most carriers here have Wi-Fi calling and when I go through my system app list it even shows an application called Wi-Fi calling. The only thing is it's not functional or usable or even accessible on my phone right now. I'm hoping somebody has tried it and might be able to tell me more but thanks for letting me know what you knew about it. Have a great night my friend. I'm off to bed
Click to expand...
Click to collapse
should be in the phone app in the 3 dot menu ootions.
but east link just might not have it. call them or check in their site.
Thanks for the update, looks like I'm out of luck for now. Here's an image of what I see after I hit settings....
So it seems as if I'm out of luck for now. Wi-Fi calling would definitely be handy especially for overseas calling or extreme long distance. The only loss I have at the moment as if I'm calling outside my nation. Wi-Fi calling you would also have to be at home where as using data to make the call would serve the same purpose but it would run out much quicker especially if it's a video call and if it's a long call. I still want Wi-Fi calling now so maybe I will start harassing EastLink and hopefully one person well drive them mad enough to push through the option for me haha. Thanks for letting me know where to check though, have a great day bud.
I tried flashing the xac firmware which is region free but it quickly defaults back to esk on its own the first time I fire up the phone. Esk is EastLink. There must be something that tells it to reset to the current company that the SIM card is from I'm guessing. Thanks for the idea but I tried it and it failed miserably. If you know how to make it stick I'd love to know how you do it.
Try this for WiFi access
Install Activity Launcher. Search for "call" (no s), select Settings, select "com.android.settings.Settings#WifFCallingSettingsActivity", create and save the shortcut to your home screen. The shortcut should open to Wi-Fi Calling menu where you can toggle it on and off.

Categories

Resources