Related
for those of you that dont know video share does not work on the htc fuze it your settings say wap.cingular. att has tried to fix this with no success still waiting on a call back from them. we know that the settings should say ims.cingular butmanually changing it does not work it has to come from htc like that. so it anyone has any suggestion please post. and yes i do have the service from att and it works on other video share phones.
I have had alot of issues with differant devices and VIDEO SHARE, to that i will say this; have them remove the soc code(feature) and then add it back to the account after a soft reset on your device. This has been the process that has corrected mine for many of my devices.
Any relief on this? curious if it is the ROM I am using or if it really isnt working.
iceberg1824 said:
for those of you that dont know video share does not work on the htc fuze it your settings say wap.cingular. att has tried to fix this with no success still waiting on a call back from them. we know that the settings should say ims.cingular butmanually changing it does not work it has to come from htc like that. so it anyone has any suggestion please post. and yes i do have the service from att and it works on other video share phones.
Click to expand...
Click to collapse
strangely my phone sometimes says ims.cingular and I cannot connect and it asks for a password on boot up. Most of the time it is wap.cingular. Weird...
As for videoshare, you have to be on a 3g (H) connection to stream data and talk at the same time. I haven't tried the videoshare, but I will test and see what I get....any other ideas?
Video Share Checklist
I just thought I'd share my experience with getting Video Share to work properly on the FUZE (and on my LG VU) So here it is:
Checklist
3G Service Area: you (and the other party) MUST be in a 3g service area, with at least 2 bars, why 2 bars you ask? well, quality of service mainly, less than 2 bars and your 3G will be very slow, remember you're trying to transmit alot of data with Video share.
A Data Plan: This was a shock, but not really... if you don't want to be charged for every KB of data sent / received in addition to the 35 cents per minute pay per use or whichever plan you have, you must have a good data plan to cover the charges... I don't understand why AT&T feels they must double charge, once for the feature and then for the data to use that feature, MMS Messages do the same... if they charge a high rate for MMS, you shouldnt be charged for the associated DATA, what a rip!
Video Share PPU, Starter, or Premium service (the service itself) -- not much to say but DUH, also the receiver must have this service and an appropriate data plan as mentioned above or you will never see the option on your phone during a call.
IMS APN Feature: (FREE) Although the guy I finally got a hold of to make this all work (who had a thick accent and was hard to understand, but knew what he was doing) told me that video share will work with wap.cingular, there have been reports that it doesn't. When you provision Video share the network automatically changes your APN to ims.cingular, IMS APN feature must be on your account for access or it could give you all sorts of problems form "forbidden" on browsing to rejected emails/mms. If you have a 3G phone this is most likely on your account, it is the new higher speed apn for 3G, maybe that's why the internal customer service code for it is "3GMM" hmm....
Correct settings in your phone: I'm not going to go into those details here, but its obvious, you must have the correct settings.
Correct IMEI: Here's the fun one, I had tried everything above as mentioned in scattered posts throughout the net only to call at&t several times getting frustrated over not getting any results, the final time I called them I ended up talking to some guy in a "special department" related to video share issues. After reviewing all settings on my account he finally figured out the problem (which took him about 2 minutes after getting transfered) the IMEI numbers for my phones were not listed in the system. (blame the dealer I bought the phones from as they are supposed to enter this) there are several places the IMEI's get listed, and I'd think they could easily pluck this information from the network when the phone registers but no, I read him my IMEI information from both lines on my account that video share didn't work for (the FUZE and the VU), he had us remove the batteries as he sent the updates across the network, and BAM the very next call between the phones and video share works like a champ. What this boiled down to is the network didn't know what type of phone I had and what features to turn on and what to do to make the phones talk to each other in a compatible form. I'd think this would cause all sorts of other issues with the network too, not just for video share.
A final note on this: if you change phones, make sure you call and have the IMEI information updated, if I change my FUZE for another FUZE it would probably work, but if I swap the device out for a different model it would not necessarily pick the most compatible features for my phone...
Privisioned Dates: When you go to your online account management and add features, it says they are immediately effective, sometimes this is true, but in the case of my account it likes to post-date to the next bill cycle. This is especially true when you visit an AT&T store, it will definitely post-date there. I had 3 IMS APN features and Video Share features on my account, all with different dates, this is because, I tried to add and 2 people at the store tried to add, to make sure Video Share and IMS are on your account and active / effective TODAY you have no choice but to call customer service and tell them you want them on your account effective immediately. While it will appear on your account management that you have it, don't trust it as it only checks for the feature, not the active dates.
And finally the internet connection: Some people have noted that your connection must be active before the call, this is not true although it is very helpful. The video share negotiation takes place over the phone control channel, when it is determined that you both have the service and compatible phones it will send a message to both phones. They will then try to turn on their data connections and verify with the server whether or not the option should be turned on. If your data is active before the call your video share button will be available instantly as it is for me. If it is NOT then it will take ~20 seconds or more to connect to the net and contact the server to verify, then turn on the option for you. Just make sure your internet works in general and that you can connect and you should have no problems during a normal call.
I hope this helps at least some of the people out there having this issue, and maybe some others having other issues with the network. Sorry for the long post
vs is ok now
OK this is a miracle finally got my HTC fuze to do video share. When I started this thread I was so mad at ATT and htc. Well here is the deal I had tried just about every avenue to get this to work and after reading whitehawk82 post, one of his points stood out.
FIRST make sure you have the latest sim card from ATT and IMS APN Feature is activated, now be aware that ATT needs to reset your entire data service so the ims.cingular can kick in on the ATT fuze. To make sure this is working when you turn on your fuze it will automatically connect to ims.cingular as with all video share phones.
SECOND now that you are connected you would think it would work, well not quite that easy. Now you need to re-install original ATT fuze rom and finally when you go to contacts live video share call will no longer be grayed out. Put back all your info manually for best results sprite restore may put back some incorrect settings.
whitehawk82 said:
I just thought I'd share my experience with getting Video Share to work properly on the FUZE (and on my LG VU) So here it is:
Checklist
3G Service Area: you (and the other party) MUST be in a 3g service area, with at least 2 bars, why 2 bars you ask? well, quality of service mainly, less than 2 bars and your 3G will be very slow, remember you're trying to transmit alot of data with Video share.
A Data Plan: This was a shock, but not really... if you don't want to be charged for every KB of data sent / received in addition to the 35 cents per minute pay per use or whichever plan you have, you must have a good data plan to cover the charges... I don't understand why AT&T feels they must double charge, once for the feature and then for the data to use that feature, MMS Messages do the same... if they charge a high rate for MMS, you shouldnt be charged for the associated DATA, what a rip!
Video Share PPU, Starter, or Premium service (the service itself) -- not much to say but DUH, also the receiver must have this service and an appropriate data plan as mentioned above or you will never see the option on your phone during a call.
IMS APN Feature: (FREE) Although the guy I finally got a hold of to make this all work (who had a thick accent and was hard to understand, but knew what he was doing) told me that video share will work with wap.cingular, there have been reports that it doesn't. When you provision Video share the network automatically changes your APN to ims.cingular, IMS APN feature must be on your account for access or it could give you all sorts of problems form "forbidden" on browsing to rejected emails/mms. If you have a 3G phone this is most likely on your account, it is the new higher speed apn for 3G, maybe that's why the internal customer service code for it is "3GMM" hmm....
Correct settings in your phone: I'm not going to go into those details here, but its obvious, you must have the correct settings.
Correct IMEI: Here's the fun one, I had tried everything above as mentioned in scattered posts throughout the net only to call at&t several times getting frustrated over not getting any results, the final time I called them I ended up talking to some guy in a "special department" related to video share issues. After reviewing all settings on my account he finally figured out the problem (which took him about 2 minutes after getting transfered) the IMEI numbers for my phones were not listed in the system. (blame the dealer I bought the phones from as they are supposed to enter this) there are several places the IMEI's get listed, and I'd think they could easily pluck this information from the network when the phone registers but no, I read him my IMEI information from both lines on my account that video share didn't work for (the FUZE and the VU), he had us remove the batteries as he sent the updates across the network, and BAM the very next call between the phones and video share works like a champ. What this boiled down to is the network didn't know what type of phone I had and what features to turn on and what to do to make the phones talk to each other in a compatible form. I'd think this would cause all sorts of other issues with the network too, not just for video share.
A final note on this: if you change phones, make sure you call and have the IMEI information updated, if I change my FUZE for another FUZE it would probably work, but if I swap the device out for a different model it would not necessarily pick the most compatible features for my phone...
Privisioned Dates: When you go to your online account management and add features, it says they are immediately effective, sometimes this is true, but in the case of my account it likes to post-date to the next bill cycle. This is especially true when you visit an AT&T store, it will definitely post-date there. I had 3 IMS APN features and Video Share features on my account, all with different dates, this is because, I tried to add and 2 people at the store tried to add, to make sure Video Share and IMS are on your account and active / effective TODAY you have no choice but to call customer service and tell them you want them on your account effective immediately. While it will appear on your account management that you have it, don't trust it as it only checks for the feature, not the active dates.
And finally the internet connection: Some people have noted that your connection must be active before the call, this is not true although it is very helpful. The video share negotiation takes place over the phone control channel, when it is determined that you both have the service and compatible phones it will send a message to both phones. They will then try to turn on their data connections and verify with the server whether or not the option should be turned on. If your data is active before the call your video share button will be available instantly as it is for me. If it is NOT then it will take ~20 seconds or more to connect to the net and contact the server to verify, then turn on the option for you. Just make sure your internet works in general and that you can connect and you should have no problems during a normal call.
I hope this helps at least some of the people out there having this issue, and maybe some others having other issues with the network. Sorry for the long post
Click to expand...
Click to collapse
And this is why Video Share will NEVER take off. It's too ****ing complicated to get working on 2 devices, and it is completely USELESS. Seriously... I talk to people online and we both have webcams, but we don't get on cam just to talk. We just talk. Video is such an unnecessary part of every day communication.
Getting GSM (& Straight Talk) working on the Droid Bionic running Jelly Bean 4.1.
If you're here I'm sure you know now that it is possible, contridictory to all those who claim it's not because of these specs or that data sheet or press release.
Apparently it has the exact same radio / chipset as other Moto World phones it's just not for lack of a better term "unlocked".
BTW...If I was to recommend an order to do the "trifecta" in, this would be the last step. I doubt it would effect rooting. But MOST of the problems I ran into updating to JB had to do with the fact I originally did this when I was still on ICS, then it caused a bunch of probs while trying to update. Namely all of the "System 7" errors. See that thread for more.
****FIRST AND FOREMOST*****
Make copies of every file you change in their current untouched state, before editing, and if you can't, keep notes of their current values.
Also do not do this with the SIM in, it's not required for anything other than testing and getting a signal at the end.
This, from my experience, is also the cause of the "android.phone" shut down error loop.
IF you get that, shut the phone down in between hitting the "ok" button of the error loop and remove the SIM and continue. Once you finish and have reception it shouldn't return.
Follow the build.prop edits shown on the XDA thread "Bionic working on T-MO."
*You have to have root access to edit this file. I use ES File Explorer, use in "root" mode and enable R/W for everything. Whatever file explorer you use I'm sure it's similar, just look thru the settings.*
Then I saved changes & rebooted, and did the RadioComm part. Apparently this is the step that turns on / unlocks the GSM radio.
When you open RadioComm and it asks what setting to start on pick, same as chipset setting (will edit & update w exact in a minute don't have it open right now, you have to scroll about midway down the list tho.)
*If the big box in the middle right doesn't fill up with code, or totally turn green after you make the change to the first (16) numbers & save, somethings wrong and the edit didn't save. restart the steps & make sure they're right. Close RadioComm. You're done with it (...for now)
Disconnect Phone & Reboot.
After boot go to Dialer and type *#*#4636#*#* (*#*#info#*#*), should go right to a menu & pick Phone Info. go down to "set preferred network type" & pick WCDMA. back out and should be done.
People have said this won't stay set for them. Following all the instructions, I've not had a problem keeping a network set. I believe this is controlled with one of the build.prop edits. There are suggested fixes out there, if you go thru the settings and edits and you're still having a prob, try those.
In truth, mine defaults to GSM/CDMA auto (PRL), but it doesn't seem to effect my service, and I believe that will auto switch between networks which is fine with me becasue I can't get CDMA with the GSM sim anyways.
If you just want GSM, that should be it. Power down, put your SIM in and reboot. If you have AT&T or T-Mo, the APNs are already loaded and should default after phone reads SIM.
If you get "unknown SIM" dialog just click "ok". It will come up every time you reboot your phone tho so if you want to put an end to it, there's a quick build.prop edit that fixes it. Will Post exactly when I find it again.
but it's something like changing:
vzwphone=1 to
vzwphone=0 (only for ref until I get it up).
****Straight Talk (At&t SIM)
Before putting in SIM and after Preferred Network change.
go to Dialer, ##7764726 (##program) & hit "call" / phone button, enter "000000" for SPC password & "Verify".
Go down to #13 APN Controls,
then APN Config Edit.
Touch menu button on phone (4-squares) & New APN.
These are my settings & Voice, Data & MMS all work.
Name: Straight Talk AT&T
APN: att.mvno (make sure "MVNO" had this as MNVO and couldn't figure out what was wrong)
MMSC: http://mmsc.cingular.com
MMS proxy: 66.209.11.33
MMS port: 80
MCC: 310
MNC: 410
APN type: default,supl,mms,hipri,dun (no space betw commas)
That's it. anything not listed above was left blank or as it defaulted.
power down put in SIM, and in a few minutes you should have service.
If you do, try going on internet, if that works, try sending yourself a picture msg.
All have worked for me.
****BTW - 2 things....make sure you have Wifi turned off, & you have mobile data enabled / on. (the mobile / packet data "On" thing was the issue with my Captivate Glide not getting data & MMS and it drove me nuts, then to find out it was just a switch & bang worked great.)
I hope this helps at least someone.
Cheers.
the one issue I still kinda have....
For whatever reason I get great data speeds.
typically 4.5 - 6+ Mbps down & 1.5 - 2 up.
but my voice levels are typically high -80's to -105 dbms
which equals at best, a not steady 3 bars.
Usually only 2 bars (mid -90's dbms) and quite often the little spec of a triangle.
I've tried the RadioComm Hex edit & adding lines to the build.prop to get boost signal reception that others have said helped them. Neither have done anything for me. (found here)
Currently still have both "running".
also tried this build.prop change
vzwglobalphone=1 to
vzwglobalphone=0
still no change.
The reason this is kinda an issue for me is my daily is currently a Samsung Captivate Glide and I Consistantly am at 4+ bars and high 70's. I don't know why I shouldn't get same reception in same areas, especially because I read that Moto radios are better than Samsung ones.
I do wonder if it's because the other is a "native" GSM, but then I think that the Moto is too, it was just "turned off" before.
Again I'm not a Dev, but I do want this to be my daily, so I'm willing to try pretty much anything since I have a back-up. So if anyone who knows more than me or has found a fix that works for them, please share.
i have followed your directions to the letter but still get bootloop. can u b a lil more detailed on how to save the build.prop to prevent this
@ smutta - Do you mean the android.phone shut down error? THe only time I experienced a boot loop was when I updated to JB, and that's when I was getting the "motorola dual core" boot animation loop. The result of that in my case was the "system 7" errors I mentioned in the JB update thread. Those are a result of, lack of a better way of putting it, the checksum's not matching what the update is looking for. Any hacks / changes you've made will seem to cause it to error out and the boot loop. Please check that thread too.
good luck.
MoodSwinger said:
@ smutta - Do you mean the android.phone shut down error? THe only time I experienced a boot loop was when I updated to JB, and that's when I was getting the "motorola dual core" boot animation loop. The result of that in my case was the "system 7" errors I mentioned in the JB update thread. Those are a result of, lack of a better way of putting it, the checksum's not matching what the update is looking for. Any hacks / changes you've made will seem to cause it to error out and the boot loop. Please check that thread too.
good luck.
Click to expand...
Click to collapse
Thank you i got it working and with a few roms also
@MoodSwinger
I am very new to this whole hack thing.
I've read, read, and read some more about trying to find the right way to do this.
I've successfully (through a combination of steps on here and other threads) got my (previously Verizon) Bionic on the Straight Talk network. I have voice, text, and data. Now, I'm running into a few of things that I can't seem to fix.
1st- My radio signal is real low (1 bar to 3 max) The network does not read 3G, it reads "H" ... What does that mean? I've never seen "H".
2nd- The phone seems to have a hell of a time detecting the SD card. Sometimes it does, but most of the time it doesn't.
3rd- I usually have no problem getting my apps back on from my Google account that backs them up after I would FXZ. I usually have to re- download them, but they are at least there. That doesn't happen anymore. I don't know how to recover them. This might have something to do with not having the proper signal. ???
What do you think I should do from here? Any input?
I have a feeling that a couple of tweaks in the build.prop would do the trick, but I'm not sure which ones to modify.
Also, I called Straight Talk and they gave me a more suitable APN for my area(I guess):::::
Name:
Straight Talk
APN:
tfdata
MMSC:
h t t p://mms-tf.net (without the spaces in the http, of course)
MMS Proxy:
mms3.tracfone.net
MMS port:
80
----------------
The rest he told me to just let it default, and that it would fill in itself if need be.
Otherwise, I tweaked the build.prop just like you illustrated in your post.
Thanks for the help, or even pointing me in the direction of an amazing Motorola radio tech.
I have root and I have flashed thru radiocomm the 1877 values.
I get the android.phone FC every time I switch to anything GSM or WCDMA related in phone testing.
I can't find the current workable build.prop edits, am trying to get it to work on Simple mobile.
Also what does renaming / deleting the stk.apk and atk.odex do?
Current edits
persist.radio.ap.phonetype=2 and changing the value to 1.
^only for JB
ro.telephony.default_network=7 (to set GLOBAL preferred network type)
ro.mot.phonemode.vzw4gphone=0 (to make possible APN edit)
telephony.lteOnCdmaDevice=0 (to fix signal strength and wrong carrier)
ro.telephony.ril.v3=signalstrength (to fix non-updating signal strength indicator)
I probably knew what it did at some point but I've since forgotten.
gsm help!!
hey guys i have my droid running both cm 10 and liquid v 2.9 . ive done all the build.prop edits and then some and when i set the prefered network it keeps finding aTT instead of t-mobile which is what im asumming it should be on for metro...i really need help been at this a while on and off i feel like im real close.
Deadman001 said:
Current edits
persist.radio.ap.phonetype=2 and changing the value to 1.
^only for JB
ro.telephony.default_network=7 (to set GLOBAL preferred network type)
ro.mot.phonemode.vzw4gphone=0 (to make possible APN edit)
telephony.lteOnCdmaDevice=0 (to fix signal strength and wrong carrier)
ro.telephony.ril.v3=signalstrength (to fix non-updating signal strength indicator)
I probably knew what it did at some point but I've since forgotten.
Click to expand...
Click to collapse
with this changes on build.prop you get strong singnal and no more signal drops?
MoodSwinger said:
Getting GSM (& Straight Talk) working on the Droid Bionic running Jelly Bean 4.1.
If you're here I'm sure you know now that it is possible, contridictory to all those who claim it's not because of these specs or that data sheet or press release.
Apparently it has the exact same radio / chipset as other Moto World phones it's just not for lack of a better term "unlocked".
BTW...If I was to recommend an order to do the "trifecta" in, this would be the last step. I doubt it would effect rooting. But MOST of the problems I ran into updating to JB had to do with the fact I originally did this when I was still on ICS, then it caused a bunch of probs while trying to update. Namely all of the "System 7" errors. See that thread for more.
****FIRST AND FOREMOST*****
Make copies of every file you change in their current untouched state, before editing, and if you can't, keep notes of their current values.
Also do not do this with the SIM in, it's not required for anything other than testing and getting a signal at the end.
This, from my experience, is also the cause of the "android.phone" shut down error loop.
IF you get that, shut the phone down in between hitting the "ok" button of the error loop and remove the SIM and continue. Once you finish and have reception it shouldn't return.
Follow the build.prop edits shown on the XDA thread "Bionic working on T-MO."
*You have to have root access to edit this file. I use ES File Explorer, use in "root" mode and enable R/W for everything. Whatever file explorer you use I'm sure it's similar, just look thru the settings.*
Then I saved changes & rebooted, and did the RadioComm part. Apparently this is the step that turns on / unlocks the GSM radio.
When you open RadioComm and it asks what setting to start on pick, same as chipset setting (will edit & update w exact in a minute don't have it open right now, you have to scroll about midway down the list tho.)
*If the big box in the middle right doesn't fill up with code, or totally turn green after you make the change to the first (16) numbers & save, somethings wrong and the edit didn't save. restart the steps & make sure they're right. Close RadioComm. You're done with it (...for now)
Disconnect Phone & Reboot.
After boot go to Dialer and type *#*#4636#*#* (*#*#info#*#*), should go right to a menu & pick Phone Info. go down to "set preferred network type" & pick WCDMA. back out and should be done.
People have said this won't stay set for them. Following all the instructions, I've not had a problem keeping a network set. I believe this is controlled with one of the build.prop edits. There are suggested fixes out there, if you go thru the settings and edits and you're still having a prob, try those.
In truth, mine defaults to GSM/CDMA auto (PRL), but it doesn't seem to effect my service, and I believe that will auto switch between networks which is fine with me becasue I can't get CDMA with the GSM sim anyways.
If you just want GSM, that should be it. Power down, put your SIM in and reboot. If you have AT&T or T-Mo, the APNs are already loaded and should default after phone reads SIM.
If you get "unknown SIM" dialog just click "ok". It will come up every time you reboot your phone tho so if you want to put an end to it, there's a quick build.prop edit that fixes it. Will Post exactly when I find it again.
but it's something like changing:
vzwphone=1 to
vzwphone=0 (only for ref until I get it up).
****Straight Talk (At&t SIM)
Before putting in SIM and after Preferred Network change.
go to Dialer, ##7764726 (##program) & hit "call" / phone button, enter "000000" for SPC password & "Verify".
Go down to #13 APN Controls,
then APN Config Edit.
Touch menu button on phone (4-squares) & New APN.
These are my settings & Voice, Data & MMS all work.
Name: Straight Talk AT&T
APN: att.mvno (make sure "MVNO" had this as MNVO and couldn't figure out what was wrong)
MMSC: http://mmsc.cingular.com
MMS proxy: 66.209.11.33
MMS port: 80
MCC: 310
MNC: 410
APN type: default,supl,mms,hipri,dun (no space betw commas)
That's it. anything not listed above was left blank or as it defaulted.
power down put in SIM, and in a few minutes you should have service.
If you do, try going on internet, if that works, try sending yourself a picture msg.
All have worked for me.
****BTW - 2 things....make sure you have Wifi turned off, & you have mobile data enabled / on. (the mobile / packet data "On" thing was the issue with my Captivate Glide not getting data & MMS and it drove me nuts, then to find out it was just a switch & bang worked great.)
I hope this helps at least someone.
Cheers.
Click to expand...
Click to collapse
i have done many bionics using this radiocomm hack, everything works on stock, but when i try AOKP rom 4.2 (milestone 2) , custom rom, my sms do not work (inmeadtly receive a message not sent error) any ideas why?
No, no ideas. Is it just SMS or MMS too? or all data? can you get on the internet? does it work w WIFI?
I have been wanting to try the AOKP rom, but I installed the MS1 and at that time it didn't work w GSM, so I haven't gotten around to trying it even since the GSM patch had come out. Does the MS2 have the GSM "Built in"? If I can use it w Safestrap I'' give it a shot and see if I can fig it out.
arana1 said:
i have done many bionics using this radiocomm hack, everything works on stock, but when i try AOKP rom 4.2 (milestone 2) , custom rom, my sms do not work (inmeadtly receive a message not sent error) any ideas why?
Click to expand...
Click to collapse
Honestly, every straight talk modded phone i have seen that isnt getting sms has a problem within the apn settings. The ones you quoted in that post are the best i have used but depending on where you live, you may have to use the tracfone version. Or it ay be something totally different and unique.
MoodSwinger said:
No, no ideas. Is it just SMS or MMS too? or all data? can you get on the internet? does it work w WIFI?
I have been wanting to try the AOKP rom, but I installed the MS1 and at that time it didn't work w GSM, so I haven't gotten around to trying it even since the GSM patch had come out. Does the MS2 have the GSM "Built in"? If I can use it w Safestrap I'' give it a shot and see if I can fig it out.
Click to expand...
Click to collapse
I got it fixed, just tweaked some biuld.prop settings , that was the problem, i had made the buildprop tweaks only in the stock one, so no wonder the aokp had problems, and to answer your question , everything works, WIFI, DATA, just by installing it you will not get GSM working you have to do:the the radiocomm edit, the build.prop edit, i even got FM radio working again on JB, no the MS2 doesnt work as GSM until you make the changes, but ponce you do , everything GSM is in there in the aokp menus (apn edits, etc)
I have my bionic going on straight talk w/At&t. Under settings>mobile networks>Network operators I have the choice to search networks and select from a couple of different At&t options, a t-mobile option or I can set it to "choose automatically." Should I keep this on choose automatically or should I select one of the At&t networks it detects, and is there a difference? The two at&t bands appear to operate at the same frequency whereas the T-mobile network looks like a smaller range. I'm trying to optimize signal/data. Thanks in advance.
***UPDATE*** I left my house for the first time today since getting my phone going on GSM w/AT&T StraightTalk and I had 4 bars of reception and full 3g downloads and full messaging capabilities. I'm satisfied with the results and I think any difference in signal strength may come from having been spoiled on Verizon's coverage, even though I never got good reception at my house with verizon either so I guess I can't expect more from someone else.
I can root, flash recovery, flash the TBH GSM.zip hack -- As soon as I reboot from CWM I recieve the error "Encryption Unsuccessful" screen.
I am on 0A.78 - restoring with cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip (It is the only build that won't err on flash.)
After Restore, I use Oracle VM Ware to root with Root_Bionic_JB_20130501-4.ova
I then install BionicBootstrap.apk - I reboot into CWM, then BAM- Encryption error all over again......
Any ideas? I've been all over the Android boards and can't find much help. I have only had SIM detection and service 1 time previously- I tried to make a call and the phone would not connect. I had to do a manual reboot and I was right back where I started.
You can't use Bionic BootStrap recovery on any build after ICS and you also can't use the TBH zip method anymore.
You have to use RadioComm or other NV access tool to make the edits manually along with the build.prop edits needed.
Is there an actual STEP BY STEP guide? I had it working on stock 4.1.2 ... as soon as I flashed a custom recovery I was right back to Encryption unsuccessful. I was up for 24 hrs + last time when I managed to get it going, so needless to say I'm a little fuzzy on the details of how I managed it.
finally
I had an awful time of trying to use my stock ROM with ST AT&T; I damn near lost my mind.
Most threads fail to mention (or as a newbie I couldn't decipher) that a custom ROM is the way to go, and oh so amazing.
SS slot 2, changed a few lines in build.prop including my default network to WCDMA preferred (which I could not do in stock), easily added APN using the ST Data Settings app, and it is going pretty good so far. The only problem I am experiencing is the absence of my car dock, but that is a whole 'nother thread!
Thanks for all y'all's help! Very brilliant!
I have rooted my phone, and am trying the radiocomm hack, but, radiocomm is not recognizing my phone. how can i get radiocomm to recognize my device is connected?
FYI for Sprint Customers (who travel),
As many jet-setting Sprint customers are aware, when traveling overseas, getting data on an overseas network requires editing the Build.prop file to add the "ril.sales_code=LOL" and "ro.csc.sales_code=LOL". Maybe not even many, but I sure had to get my phone to work on Meteor in Ireland before it would allow me to add the APNs.
When you return from your wonderful vacations and get back on the Sprint Network, you may need to go back into your Build.prop file and either delete those two entries or comment them out (e.g. make them #ril.sales_code=LOL and #ro.csc.sales_code=LOL). Otherwise, your ## service codes (e.g. ##72786#, ##3282#, etc...) won't work.
Found this out when I had to call Airave support and they needed me to reprovision my phone. First question when the ## codes were entered and nothing happened was "Is your phone rooted?" My answer was "Of course not!" Bringing us to the next FYI.
Since I actually needed to receive calls from the US, I put my Meteor SIM card in my Motorola Photon 4G. If you have an Airave 2.5 device AND you have ANY need to use an old mobile phone, specifically one you've upgraded from and will likely have your same MSID/MDN in it, make absolutely sure you turn it off or on airplane mode so that it can't connect to your Airave 2.5 device. You'll be able to make and receive calls and receive texts, even use data, but will not be able to send texts. Instead you'll get an Error 34. I had to call Airave support to fix it. (1-866-556-7310 for those who need it, may get a busy signal initially, just call back, someone gets right on the line) They had to change my MSID and make me do a reprovision via ##72786#.
You guys may or may not have any of these issues and it may only relate to me, but wanted to put this little warning buoy in the water for everyone else.
Anyone else running the G5S+ on Sprint? It's working fairly well for me other than a couple of IPv6/IPv4 connection issues. However, is it normal for Cellular network settings to not include any kind of APN settings/options? We have six different devices on our family Sprint account -- Nexus 6, Samsung Galaxy S5 Active, Samsung Galaxy S3, iPhone 7, iPhone 6+, and now the G5S+. All of the other devices have a way to edit the APN settings, even when running the stock, unrooted ROM. I'm waiting to root my G5S+ until after an official Oreo update. Is this a limitation of the stock ROM?
My concern is mostly for when I travel out of the country. I know from past experience I'll need to be able to select the proper APN to get the best connectivity, but I've also needed to select the correct APN locally sometimes like when my phone(s) freak out and only connect to the CDMA_0 APN so I'm stuck on 3G.
internetpilot said:
Anyone else running the G5S+ on Sprint? It's working fairly well for me other than a couple of IPv6/IPv4 connection issues. However, is it normal for Cellular network settings to not include any kind of APN settings/options? We have six different devices on our family Sprint account -- Nexus 6, Samsung Galaxy S5 Active, Samsung Galaxy S3, iPhone 7, iPhone 6+, and now the G5S+. All of the other devices have a way to edit the APN settings, even when running the stock, unrooted ROM. I'm waiting to root my G5S+ until after an official Oreo update. Is this a limitation of the stock ROM?
My concern is mostly for when I travel out of the country. I know from past experience I'll need to be able to select the proper APN to get the best connectivity, but I've also needed to select the correct APN locally sometimes like when my phone(s) freak out and only connect to the CDMA_0 APN so I'm stuck on 3G.
Click to expand...
Click to collapse
There should be, even on stock. Might be a problem with the sim - contact Sprint for help
Phazmos said:
There should be, even on stock. Might be a problem with the sim - contact Sprint for help
Click to expand...
Click to collapse
Oh, I already have contacted Sprint several times, and had the SIM switched out 3x now. This is a different type of Sprint SIM than I had in my Nexus 6. I think it's probably going to require root and modifying the build.prop or even a custom ROM, which I don't really want to do until the Oreo OTA comes out or at least a much more stable custom ROM than what we have now for this phone.
The Sprint network has gotten a little weird. First this new 3-in-one SIM, which seems to have locked-down APN settings, and then this phone also only has an IPv6 IP#, which is causing a couple problems with monitoring my IP security cameras at both my homes (neither of my ISP's are fully on IPv6 yet), but also even Google Weather and the Android Wear Play Store won't connect on my Asus ZenWatch 3 paired through this phone and only using mobile data. If I connect the phone to wifi (anywhere -- home, public, etc.), the IP cameras, Google Weather, and Wear Play Store all work fine. It's just bizarre that Sprint isn't running a dual stack IPv4/IPv6 network until everything is IPv6. Most things work fine on my phone -- regular Play Store, Netflix, all social media, and even TeamViewer and Plex, which both are hosted the same IPv4 networks that have the IPv4 security cameras . I guess it's because all these other services are running some kind of dual stack configuration at their end, but I'm very surprised that Google Weather and the Wear Play Store apparently is not.
I've yet to find anyone else who is using this phone on Sprint to confirm that they're encountering the same thing I am.
internetpilot said:
Oh, I already have contacted Sprint several times, and had the SIM switched out 3x now. This is a different type of Sprint SIM than I had in my Nexus 6. I think it's probably going to require root and modifying the build.prop or even a custom ROM, which I don't really want to do until the Oreo OTA comes out or at least a much more stable custom ROM than what we have now for this phone.
The Sprint network has gotten a little weird. First this new 3-in-one SIM, which seems to have locked-down APN settings, and then this phone also only has an IPv6 IP#, which is causing a couple problems with monitoring my IP security cameras at both my homes (neither of my ISP's are fully on IPv6 yet), but also even Google Weather and the Android Wear Play Store won't connect on my Asus ZenWatch 3 paired through this phone and only using mobile data. If I connect the phone to wifi (anywhere -- home, public, etc.), the IP cameras, Google Weather, and Wear Play Store all work fine. It's just bizarre that Sprint isn't running a dual stack IPv4/IPv6 network until everything is IPv6. Most things work fine on my phone -- regular Play Store, Netflix, all social media, and even TeamViewer and Plex, which both are hosted the same IPv4 networks that have the IPv4 security cameras . I guess it's because all these other services are running some kind of dual stack configuration at their end, but I'm very surprised that Google Weather and the Wear Play Store apparently is not.
I've yet to find anyone else who is using this phone on Sprint to confirm that they're encountering the same thing I am.
Click to expand...
Click to collapse
I'm glad I never used Sprint, mainly cuz I've heard of so many problems with them over the years, and where I am it's basically att or Verizon if ya want any kind of coverage (rural + mountains = shirty cell coverage). Did you get the phone from Sprint? I'm wondering if it's locked down for Sprint - last time I used a locked down device was about 6 years ago. I always thought apns were handled by the os, but if it's locked down, it could be handled by the sim. Now I'm curious - what would happen if you popped in a sim from one of those other devices that do work?
Unlock, root and roms - not many available right now (new devices always take a while - especially if uptake is slow), but what's out there now are pretty much stable enough for daily use. This device is supposed to get Oreo, but probably not till sometime next year (I'm not running it yet but only cuz the features I want aren't there yet). Ipv6 implementation - lol - I've worked with a few network engineers over the years and when the talk of ipv6 started up, they went crazy. Implementing it, even on a small scale isn't an easy thing, imagine on a nation wide, or world wide scale. It started about 5 years ago, and it'll probably take another 5+ before everything is compatible. Anyway, I ramble - good luck , I do hope it gets sorted out for ya!
Phazmos said:
I'm glad I never used Sprint, mainly cuz I've heard of so many problems with them over the years, and where I am it's basically att or Verizon if ya want any kind of coverage (rural + mountains = shirty cell coverage). Did you get the phone from Sprint? I'm wondering if it's locked down for Sprint - last time I used a locked down device was about 6 years ago. I always thought apns were handled by the os, but if it's locked down, it could be handled by the sim. Now I'm curious - what would happen if you popped in a sim from one of those other devices that do work?
Unlock, root and roms - not many available right now (new devices always take a while - especially if uptake is slow), but what's out there now are pretty much stable enough for daily use. This device is supposed to get Oreo, but probably not till sometime next year (I'm not running it yet but only cuz the features I want aren't there yet). Ipv6 implementation - lol - I've worked with a few network engineers over the years and when the talk of ipv6 started up, they went crazy. Implementing it, even on a small scale isn't an easy thing, imagine on a nation wide, or world wide scale. It started about 5 years ago, and it'll probably take another 5+ before everything is compatible. Anyway, I ramble - good luck , I do hope it gets sorted out for ya!
Click to expand...
Click to collapse
No, it's a carrier independent unlocked phone that I bought from BestBuy.com (because they offered the best price for the 64gb version through a Cyber Monday sale). Except for the iPhone (and maybe the newer Samsung models), Sprint phones don't have removable SIMs -- they're built-in to the phone making them a special Sprint-only phone. That's the way my Samsung Galaxy Note 2 was. After my Note 2, I bought an unlocked Google (Motorola) Nexus 6 and used a SIM to use it on Sprint (and had access to APN setting as soon as I activated the phone), but that SIM isn't compatible with the G5S+ even though they're both Motorola phones, have the same radios, etc. I'm pretty sure my current problem is the SIM, but I don't think it's unsolvable. I just think I'll need to root and mod or ROM the device to get access to those settings. I know this is one of Sprint's newest SIMs (they have like 22 different SIMs), so I'm sure this is just another attempt by Sprint to lock down unlocked carrier independent phones on their network to help reduce excessive roaming (on Verizon towers) which costs Sprint money.
I've been on Sprint for like 15 years. The only reason I stayed on them is because the others aren't really any better, and Sprint is the only one who truly offers unlimited everything (which is really good to have for a family of six). Starting like 3 years ago (when Sprint and Samsung abruptly abandoned the Samsung Galaxy Note 2 rather early), I refused to buy Sprint locked-down phones because they require to sign another 2 year contract commitment. Whereas right now if Sprint ticks me off (like they did a couple of years ago when they sent me a $500 bill for "free" international roaming), I can just immediately drop them and move on with no penalty and even take my phone with me.
This is the first Android phone I've owned that I haven't immediately rooted. I even rooted all my family's locked Sprint phones. There just isn't much support for this phone from 3rd-party devs (yet or maybe ever since it's just a "special edition" upgrade?), so I really want that OTA Oreo update in place before I root it. I came pretty close to immediately rooting this phone, but then decided not to when saw some people had problems getting it back to stock enough to take the OTAs from Moto. I actually like the Moto Android (along with a heavily themed Nova launcher) experience enough to not feel the overwhelming need for a custom ROM, so about the only thing I really want root for is to get a better camera app (preferably Google Camera), wifi tethering, and Titanium Backup. I'm even getting used to the stock Moto camera app, so I'm not really feeling the pressing need for the Google Camera as much. I wouldn't mind getting LineageOS 15 on here, but there isn't an official version and it doesn't seem very stable yet on any device. I tend to keep my phones for a while (three years for my Nexus 6 and Note 2), so I tend to outlast most 3rd-party dev ROM support, which is why I tend to just go with LineageOS (and before that CyanogenMod) which doesn't just vanish one day like individual dev ROMs do. We'll see what happens. Hopefully this phone will start seeing more developer activity. I was originally going to get the Moto G5+, which does have a lot more dev support, but considering how long I tend to keep phones, it didn't make sense not to buy the latest/greatest version.
I'm sure it will all eventually work out. Worst case scenario is that during a European vacation next Summer I won't be able to take full advantage of Sprint's free low speed international data roaming and texting, but even then I can always just grab a local PAYG SIM and use it.
internetpilot said:
No, it's a carrier independent unlocked phone that I bought from BestBuy.com (because they offered the best price for the 64gb version through a Cyber Monday sale). Except for the iPhone (and maybe the newer Samsung models), Sprint phones don't have removable SIMs -- they're built-in to the phone making them a special Sprint-only phone. That's the way my Samsung Galaxy Note 2 was. After my Note 2, I bought an unlocked Google (Motorola) Nexus 6 and used a SIM to use it on Sprint (and had access to APN setting as soon as I activated the phone), but that SIM isn't compatible with the G5S+ even though they're both Motorola phones, have the same radios, etc. I'm pretty sure my current problem is the SIM, but I don't think it's unsolvable. I just think I'll need to root and mod or ROM the device to get access to those settings. I know this is one of Sprint's newest SIMs (they have like 22 different SIMs), so I'm sure this is just another attempt by Sprint to lock down unlocked carrier independent phones on their network to help reduce excessive roaming (on Verizon towers) which costs Sprint money.
I've been on Sprint for like 15 years. The only reason I stayed on them is because the others aren't really any better, and Sprint is the only one who truly offers unlimited everything (which is really good to have for a family of six). Starting like 3 years ago (when Sprint and Samsung abruptly abandoned the Samsung Galaxy Note 2 rather early), I refused to buy Sprint locked-down phones because they require to sign another 2 year contract commitment. Whereas right now if Sprint ticks me off (like they did a couple of years ago when they sent me a $500 bill for "free" international roaming), I can just immediately drop them and move on with no penalty and even take my phone with me.
This is the first Android phone I've owned that I haven't immediately rooted. I even rooted all my family's locked Sprint phones. There just isn't much support for this phone from 3rd-party devs (yet or maybe ever since it's just a "special edition" upgrade?), so I really want that OTA Oreo update in place before I root it. I came pretty close to immediately rooting this phone, but then decided not to when saw some people had problems getting it back to stock enough to take the OTAs from Moto. I actually like the Moto Android (along with a heavily themed Nova launcher) experience enough to not feel the overwhelming need for a custom ROM, so about the only thing I really want root for is to get a better camera app (preferably Google Camera), wifi tethering, and Titanium Backup. I'm even getting used to the stock Moto camera app, so I'm not really feeling the pressing need for the Google Camera as much. I wouldn't mind getting LineageOS 15 on here, but there isn't an official version and it doesn't seem very stable yet on any device. I tend to keep my phones for a while (three years for my Nexus 6 and Note 2), so I tend to outlast most 3rd-party dev ROM support, which is why I tend to just go with LineageOS (and before that CyanogenMod) which doesn't just vanish one day like individual dev ROMs do. We'll see what happens. Hopefully this phone will start seeing more developer activity. I was originally going to get the Moto G5+, which does have a lot more dev support, but considering how long I tend to keep phones, it didn't make sense not to buy the latest/greatest version.
I'm sure it will all eventually work out. Worst case scenario is that during a European vacation next Summer I won't be able to take full advantage of Sprint's free low speed international data roaming and texting, but even then I can always just grab a local PAYG SIM and use it.
Click to expand...
Click to collapse
I've been following the few thread there are on this phone since I got it (about a month now), and others have had the same (no apn settings or can't change them) issue, but I just figured it was noob issues as I've always modified the apn and never had a problem, on stock or any of the roms available now, and I've tried them all. I'm an old tech guy (in age and computer experience - took my first computer class in 77) and at this point it's in my blood and I'm to old to change my ways! Still curious though - what do ya mean by the by sim wasn't compatible? Granted I'm on straight talk, but been using the same SIM - starting with the n5, then 6p, now g5s plus - I just cut it down to size when it went to the micro format. I to hope to see more work for this thing. Almost makes me want to get back into building again (been like 6+ years since I built a rom) but I just don't want to spend the time, which I don't really have anyway. I thought about the g5+, but I can't go back to a smaller screen. Yeah it wasn't much smaller, and has same cpu, and probably a better camera, but this pig will do. And with finger print actions and expanded desktop, screen is the same size as my 6p (which I was extremely happy with till the big cores shirt the bed - still running though). Wish the camera was as good, but if I really want to take a good picture, I have my nikon d5100 (hacked of course)!
Again, good luck, I'm sure you'll get it fingered out eventually!
Phazmos said:
I've been following the few thread there are on this phone since I got it (about a month now), and others have had the same (no apn settings or can't change them) issue, but I just figured it was noob issues as I've always modified the apn and never had a problem, on stock or any of the roms available now, and I've tried them all. I'm an old tech guy (in age and computer experience - took my first computer class in 77) and at this point it's in my blood and I'm to old to change my ways! Still curious though - what do ya mean by the by sim wasn't compatible? Granted I'm on straight talk, but been using the same SIM - starting with the n5, then 6p, now g5s plus - I just cut it down to size when it went to the micro format. I to hope to see more work for this thing. Almost makes me want to get back into building again (been like 6+ years since I built a rom) but I just don't want to spend the time, which I don't really have anyway. I thought about the g5+, but I can't go back to a smaller screen. Yeah it wasn't much smaller, and has same cpu, and probably a better camera, but this pig will do. And with finger print actions and expanded desktop, screen is the same size as my 6p (which I was extremely happy with till the big cores shirt the bed - still running though). Wish the camera was as good, but if I really want to take a good picture, I have my nikon d5100 (hacked of course)!
Again, good luck, I'm sure you'll get it fingered out eventually!
Click to expand...
Click to collapse
25-year career network engineer here myself -- I was on the internet since before it was called the internet (I guess "world wide web" didn't sound as kewl ). At this point in my life, I don't find technology as "fascinating" as I used to, and I pretty much just want it to work for me right out of the box. I know, I know...pipe dream. What's annoying for me is that I know this is a Sprint SIM/network issue (especially the IPv6 part), but to actually communicate with someone who even understands my questions is impossible because they're not working the help desk chat lines. Oh, well...I could go on and on with all kinds of funny stories, but the short of it is that I usually just fix my issues myself.
By the SIM being incompatible I mean just that. I took the SIM out of my Nexus 6 (which I loved, especially the camera -- broke my heart when it started randomly rebooting after 3 years of faithful service) and popped it in the G5S+ and it said "Incompatible SIM" and wouldn't register on the Sprint network. So, I took it to a corporate Sprint store (where I got the SIM for the Nexus 6) and thankfully a very knowledgeable employee was there, who said, "Yep, the G5S+ takes a specific model number of nano SIM." He popped that specific SIM in the G5S+, and it pretty much came right up on the Sprint network without an issue except for the APN thing and the IPv6 thing (which I discovered later). I have spoken with a mid-level Sprint network tech who told me that the whole IPv6 isn't my SIM as much as it's when I added that SIM and phone to the Sprint network. He said all new phones after a certain date are only getting IPv6. They supposedly were going to do something to my account that forced me back on IPv4, but it didn't actually work. They also said that it would only be for a few months anyway, because they're planning on converting everyone over very soon.
This phone is 1/2" smaller than my Nexus 6, but I actually like that. I feel like I'm on a tiny phone again...haha. Anyone I tell that to quickly points out that my G5S+ is a huge phone. I didn't think I'd like the fingerprint scanner, but I really do. I also thought I'd miss the dual front speakers on the Nexus 6, but I don't really even notice it since this speaker is so loud. I do miss the Nexus 6 camera which was superb, but I'm actually getting the hang of the G5S+ camera. I'm finding myself using the "professional" (manual) mode feature a lot, but I only change the ISO to 200 and leave everything else automatic and the pictures are vastly improved. If Moto would just provide an update that would allow post-processing to be turned off, it might actually be a very good camera. I too have a couple of really nice dedicate digital cameras that can take care of anything I really need in higher end photography or video. I've always only used my phone camera because I always have it with me. For tourist stuff, family events, etc., I always bring my real camera(s) anyway.
I've created my own custom ROMs and kernels before, but it's always just been modifying or adding to someone else's work, so I just used it myself and never released it here on XDA or anything. Depending on how things go for others, I might try doing my own LineageOS builds, but I'd much rather see an official build get going for this phone and just use that. But I said, I really don't mind that stock Moto ROM that much. It's pretty much vanilla Android, and once I root it a lot of the little customizations that go into most ROMs could probably be applied to the stock ROM in the form of a mod. We'll see.
Thanks again for the replies and commiserations!
internetpilot said:
25-year career network engineer here myself -- I was on the internet since before it was called the internet (I guess "world wide web" didn't sound as kewl ). At this point in my life, I don't find technology as "fascinating" as I used to, and I pretty much just want it to work for me right out of the box. I know, I know...pipe dream. What's annoying for me is that I know this is a Sprint SIM/network issue (especially the IPv6 part), but to actually communicate with someone who even understands my questions is impossible because they're not working the help desk chat lines. Oh, well...I could go on and on with all kinds of funny stories, but the short of it is that I usually just fix my issues myself.
By the SIM being incompatible I mean just that. I took the SIM out of my Nexus 6 (which I loved, especially the camera -- broke my heart when it started randomly rebooting after 3 years of faithful service) and popped it in the G5S+ and it said "Incompatible SIM" and wouldn't register on the Sprint network. So, I took it to a corporate Sprint store (where I got the SIM for the Nexus 6) and thankfully a very knowledgeable employee was there, who said, "Yep, the G5S+ takes a specific model number of nano SIM." He popped that specific SIM in the G5S+, and it pretty much came right up on the Sprint network without an issue except for the APN thing and the IPv6 thing (which I discovered later). I have spoken with a mid-level Sprint network tech who told me that the whole IPv6 isn't my SIM as much as it's when I added that SIM and phone to the Sprint network. He said all new phones after a certain date are only getting IPv6. They supposedly were going to do something to my account that forced me back on IPv4, but it didn't actually work. They also said that it would only be for a few months anyway, because they're planning on converting everyone over very soon.
This phone is 1/2" smaller than my Nexus 6, but I actually like that. I feel like I'm on a tiny phone again...haha. Anyone I tell that to quickly points out that my G5S+ is a huge phone. I didn't think I'd like the fingerprint scanner, but I really do. I also thought I'd miss the dual front speakers on the Nexus 6, but I don't really even notice it since this speaker is so loud. I do miss the Nexus 6 camera which was superb, but I'm actually getting the hang of the G5S+ camera. I'm finding myself using the "professional" (manual) mode feature a lot, but I only change the ISO to 200 and leave everything else automatic and the pictures are vastly improved. If Moto would just provide an update that would allow post-processing to be turned off, it might actually be a very good camera. I too have a couple of really nice dedicate digital cameras that can take care of anything I really need in higher end photography or video. I've always only used my phone camera because I always have it with me. For tourist stuff, family events, etc., I always bring my real camera(s) anyway.
I've created my own custom ROMs and kernels before, but it's always just been modifying or adding to someone else's work, so I just used it myself and never released it here on XDA or anything. Depending on how things go for others, I might try doing my own LineageOS builds, but I'd much rather see an official build get going for this phone and just use that. But I said, I really don't mind that stock Moto ROM that much. It's pretty much vanilla Android, and once I root it a lot of the little customizations that go into most ROMs could probably be applied to the stock ROM in the form of a mod. We'll see.
Thanks again for the replies and commiserations!
Click to expand...
Click to collapse
Lmfao - I know exactly how ya feel! I "retired" about 5 years ago, but people ask what did for a living and I say computers - then the questions start coming. I don't mind really, but I'm more thrilled by hitting a good golf shot than talking computers again. Now when they ask what I do I say , play golf! And leave it at that. Still, I just can't help myself when it comes to noobs - I still help folks out when I can, although my patience is much shorter than it used to be. It still amazes me how people do things without knowing their arse from a hole in the wall (xda has become pretty much a source of amusement for me nowadays). I did the same with roms, never went public with any - mostly cuz I didn't have the patience for stupid questions about things I've explained clearly. Some just don't appreciate the humor in giving a stupid answer to a stupid question! Oh well! Really most roms out there have more bloat than a stock rom - way too many "features" I'll never use - all I need is date in status bar (why this isn't a stock feature is beyond me), status bar brightness (auto brightness is always either to bright or to dim) and keyboard cursor control - anything more is useless and if I don't use it, I don't want it. I like things lean and mean. Really the main reason I root is to load a custom hosts file, I've been ad free for too long to start seeing them now. I thought about the n6 when it came out, but I only had the n5 for a year and wasn't ready to upgrade and 6 in did sound big (shamu was a perfect name for it). Of course I did jump on the 6p when it came out, and loved it, now I can't do anything smaller than 5.5 (that may be more a comment on eyes that are almost 60 yrs old though). At this stage, bigger is definitely better! And look at that, I ramble again (nothing on the golf channel so I run on). Anyway, pleasure chatting - and best of luck with the issue - sounds like it'll be short lived. And may be with the trouble - it is a decent device, plenty of power for most uses (only slowness I see is working big spreads in open office) and with my usage 10+ hrs of screen on time is easy to hit and have something like 20% battery left. A good deal for the $$ spent. Enjoy!
Okay, after looking into it more, here's what I think is happening/going to happen. I found a dial code that got me to a really good phone information screen (*#*#4636#*#*). I also found a site that stated country by country the compatibility of the US version of this phone when used internationally. It can pretty much get 4G in just about every country, so the Sprint international roaming feature should at least get me 2G, which is all they advertise anyway. Through the above dial code, I can choose from a lot longer list of Preferred Network Types, including GSM only, GSM/WCDMA, TD-SCDMA, etc. When I select these, it tries unsuccessfully to connect to that network type, and when it can't it just reverts back to LTE/CDMA (the Sprint default). I think that the APN option won't show up on the menu until I successfully connect to a network other than Sprint's. I'll find out next Summer as we're planning on going to Europe. At least I now know for sure that this phone can operated internationally just fine, so I can always go the PAYG SIM route. I looked into it on previous trips with my Nexus 6, and there are travel websites that tell you exactly the best SIM service to get for each country.
Otherwise, like I said, it seems to be working fine on Sprint. On my Nexus 6 I would have problems with it switching APNs on me from the Sprint LTE APN to the one of the 3G CDMA APNs so I'd lose 4G LTE service until I switched it back. I haven't had that problem with my G5S+ so far, so I haven't "needed" the APN option in the menus yet. Hopefully I won't. I'm about to go from Virginia to Florida for the Christmas holidays, so it will be interesting to see how things work in a different location. Sprint service at my Florida house isn't exactly stellar (none of the providers are), so it should be a good test of this phone and the lack of access to APN settings.
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
internetpilot said:
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
Click to expand...
Click to collapse
Ok yes I'm on Sprint. So I can get to those apn settings but I can't add an apn.. exactly how do you do that.. Yes I can edit the only existing one just can't add any.
edit APN settings for IPV4
also posted here: https://forum.xda-developers.com/mo...ing-ipv4-address-sprint-t3747256#post76243857
First please forgive this post if it is not helpful, I didn't see a solution and came up with something that worked for me, so hope it will help others.
Problem: On my Moto XT1806 GS5+ I was getting no IPV4 connectivity only IPV6 (tested with app: Ping & Net by Ulf Dittmer from the play store).
The main issue this caused was that I couldn't view my security cameras via Sprint's network., It would only show cameras on my home WIFI.
To verify I used Ping & Net to try to ping google.com. The app gives you the option to use IPV4 or IPV6, as you can guess IPV6 succeeded and IPV4 gave no results at all.
With some guesswork I did the following to fix this:
Solution:
open dialer and typed *#*#DATA#*#* or *#*#3282#*#* selected apn settings then internet.
at the top right tap the 3 dots and select edit this prompted me to enter a passcode which after several guesses ended up being 6 zeros "000000". (maybe this is in the instructions somewhere? Don't know didn't look, kinda figured it would be posted already if it was).
then I was able to change the APN NI from x.ispsn to n.ispsn.
Waited a few seconds, turned on airplane mode and then turned it back off and then I was on 3G with IPV4. It would be even better if it was LTE with IPV4, I will continue to experiment, or maybe someone can step in and save me the trouble. maybe cinet.spcs?
Anyway it works for now as a workaround and I can look at my security cameras away from home again, hooray.
gravityecho said:
also posted here: https://forum.xda-developers.com/mo...ing-ipv4-address-sprint-t3747256#post76243857
First please forgive this post if it is not helpful, I didn't see a solution and came up with something that worked for me, so hope it will help others.
Problem: On my Moto XT1806 GS5+ I was getting no IPV4 connectivity only IPV6 (tested with app: Ping & Net by Ulf Dittmer from the play store).
The main issue this caused was that I couldn't view my security cameras via Sprint's network., It would only show cameras on my home WIFI.
To verify I used Ping & Net to try to ping google.com. The app gives you the option to use IPV4 or IPV6, as you can guess IPV6 succeeded and IPV4 gave no results at all.
With some guesswork I did the following to fix this:
Solution:
open dialer and typed *#*#DATA#*#* or *#*#3282#*#* selected apn settings then internet.
at the top right tap the 3 dots and select edit this prompted me to enter a passcode which after several guesses ended up being 6 zeros "000000". (maybe this is in the instructions somewhere? Don't know didn't look, kinda figured it would be posted already if it was).
then I was able to change the APN NI from x.ispsn to n.ispsn.
Waited a few seconds, turned on airplane mode and then turned it back off and then I was on 3G with IPV4. It would be even better if it was LTE with IPV4, I will continue to experiment, or maybe someone can step in and save me the trouble. maybe cinet.spcs?
Anyway it works for now as a workaround and I can look at my security cameras away from home again, hooray.
Click to expand...
Click to collapse
Just found easier/better way to get/test IPV4: dial *#*#4636#*#* select phone info, from this screen you can run ping test to see if IPV6 and/or IPV4 is working. In my case, changing network type from "LTE/CDMA auto (PRL)" to "CDMA only" gave me a pass ping on IPV4.
This seems like a much easier/faster/better method than previous post and is now my preferred workaround method.
gravityecho said:
Just found easier/better way to get/test IPV4: dial *#*#4636#*#* select phone info, from this screen you can run ping test to see if IPV6 and/or IPV4 is working. In my case, changing network type from "LTE/CDMA auto (PRL)" to "CDMA only" gave me a pass ping on IPV4.
This seems like a much easier/faster/better method than previous post and is now my preferred workaround method.
Click to expand...
Click to collapse
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
internetpilot said:
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
Click to expand...
Click to collapse
Yeah after talking to support at my ISP (Cox who doesn't support IPv6 yet at least in my area), Sprint (who would love to sell me another phone), Motorola (who suggested I reset app preferences and restart) and Best buy (who didn't have a clue but again would love to sell me another phone), yesterday I had enough and returned it. It's staggering how many people in tech support fields have no idea what IPv4, IPv6, and APNs are. One support person at sprint thought IPv4 meant Iphone 4... Back to my trusty Note 4 with it's emmc problem and cinet.spcs.
internetpilot said:
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
Click to expand...
Click to collapse
I just recently bought a G5S Plus to replace my G5 Plus, because the screen on my G5 is cracked and I was going to fix the screen, but then I've found that the Micro USB port on the bottom is also growing "lose" (I HATE!!!! Micro USB because they always wear out on my phones).
Anyway, I went to "activate" my new G5S+ on the Sprint web page and it just said sorry they can't help w/that, I have to "Speak to someone for assistance" (but they didn't show me what phone number to call).
Glad to see the phone will actually work on Sprint! (Since I already bought it, it would be a big deal for me if it did not!).
I have not rooted mine yet, but plan to soon. I am just not sure what ROM to use yet because it seems like these days there is no such thing as a custom ROM without problems. I sure miss the days of my Samsung Galaxy S3 when most ROMs I tried seemed to be basically flawless and better than Stock, or, at least as good, in every way.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
internetpilot said:
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
Click to expand...
Click to collapse
Damn, wow, that really sucks. I have this phone, it's too late to return it, and I've got about 6 months left of my "unlimited everything" from sprint for approximately $3 per month.
critofur said:
I just recently bought a G5S Plus to replace my G5 Plus, because the screen on my G5 is cracked and I was going to fix the screen, but then I've found that the Micro USB port on the bottom is also growing "lose" (I HATE!!!! Micro USB because they always wear out on my phones).
Anyway, I went to "activate" my new G5S+ on the Sprint web page and it just said sorry they can't help w/that, I have to "Speak to someone for assistance" (but they didn't show me what phone number to call).
Glad to see the phone will actually work on Sprint! (Since I already bought it, it would be a big deal for me if it did not!).
I have not rooted mine yet, but plan to soon. I am just not sure what ROM to use yet because it seems like these days there is no such thing as a custom ROM without problems. I sure miss the days of my Samsung Galaxy S3 when most ROMs I tried seemed to be basically flawless and better than Stock, or, at least as good, in every way.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
Damn, wow, that really sucks. I have this phone, it's too late to return it, and I've got about 6 months left of my "unlimited everything" from sprint for approximately $3 per month.
Click to expand...
Click to collapse
Yep, welcome to my world! I think we're the only two people on the Moto G5S Plus on Sprint here! I was a little surprised when the SIM from my Motorola Nexus 6 didn't work in the Moto G5S Plus, but that's probably the reason you have to talk to someone or go to a Sprint store to activate it because this phone does require a rather specific SIM that's different from the previous Moto G and E models. At least Sprint finally solved the IPv6 issues that were going on when I first got this phone. That was pretty bad. It got better when my home internet providers (Comcast and Verizon at two different houses) finally upgraded to IPv6, but Sprint really shouldn't have pulled the trigger on implementing IPv6 so early. To this day only like 25% of the entire internet is on IPv6 and in the world only like 50 countries have more than 5% of IPv6 implemented.
I've literally tried every ROM posted here and even the unofficial versions of very popular ROMs (that have always worked for me on my Android phones with Sprint) like Dirty Unicorns, Resurrection Remix, LineageOS, etc., all do the same thing. They all seem to be using the same proprietary blobs or base or whatever (I'm not a developer), and they just simply don't work (or are at least VERY sketchy) on Sprint. I've been rooting/ROMing Android since my first phone almost a decade ago (HTC EVO 4G), and never had these problems on Sprint before this phone. My immediate previous phone was also a Motorola (Google Nexus 6), and I never had any problem with Sprint and custom ROMs on that phone.
I actually just recently flashed everything back to unrooted stock Nougat, took the Oreo update and all the security updates, and didn't even bother to re-root it. Sprint put a free 50GB/month wifi hotpot on every phone on my account, and the Camera2 API is activated in the stock Oreo ROM, so other than flashing a custom ROM, those were my two main reasons for rooting and they're no longer needed. So, I'm currently happily running stock unrooted Oreo with Nova Launcher.
This little trick will change your measly 1 bar signal to nearly max bars and give you a solid consistent signal in places you normally would hardly have a connection. At least it did for me.
This goes a bit beyond enabling VoLTE from your SIM Card Network settings which if you haven't done you should enable before trying this... Of course you may not have the same results I had. I found it works best from Stock ROM no root needed I'm currently on 9.0.12 but tried it on 9.0.11 and Beta 5.
Like any mod you should make a backup now and proceed with caution. (By caution I mean don't deviate from instructions goofing around in any engineering mode is never wise)
You should try check your internet speed now (Google internet speed! And take note of it then run the same test to see if your able to improve at all.
Step 1: Optional step but for best results open dialer and type: *#*#4636#*#* From this Testing Menu select Phone Information. Once in phone info select LTE/UMTS auto (prl) for preferred Network type. Then scroll down a bit and make sure VoLTE is switched on. Exit the phone info screen.
Step 2: Open Dialer again and type: *#800#
A Warning Message to Engineering Mode will popup. Press Enter.
Step 3: Click on the first option Called OnePlusLogKit
Once in the LogKit scroll down until you see the menu called: FunctionSwitch now click and select it.
Step 4: There's 3 checkboxes of interest in this menu... VoLTE Switch, VoWifi Switch and VT Switch. I enable all three but some may have better luck not enabling VT Switch. After enabling each option it'll try and reboot your phone just say no until you have all you want enabled.
Now reboot and profit.
I can tell you without a doubt that if your using a stock OOS Rom and using TMobile as your provider that these changes will not eat up your battery any more than normal and altho depending on your location and towers speed availability this can and will increase your overall speed and your ability to maintain a solid connection in low signal areas! It forces carrier aggration meaning it makes the modem in your phone connect multiple times over varied frequencies to achieve the highest level of connection. Like your old 4g phone x 3 up to 6 put together. So your speeds can be 600% improved. Of course the phone is technically supposed to do this on its own which it can occasionally but only in absolutely optimal situations. So not when you really need it too. Lol. So altho it might not work on carriers without this tech or overseas if u live in North America and use TMobile this will drastically help your phone whether you instantly notice it or not trust me it does!
f you notice anything negative or battery draining or your phone becomes even more radioactive simply go back into the menu and disable the Functions. If this helped you at all throw me a like. Enjoy.
Omg you have saved me. A million thanks. I switched to TMobile after getting this phone and the internet speed has been utterly garbage I've been going through hell with tech support trying to get useable speed. As you can see this made a world of difference.
Is there a way to do this ob pixel 2 xl?
Same...
bladestonez said:
Omg you have saved me. A million thanks. I switched to TMobile after getting this phone and the internet speed has been utterly garbage I've been going through hell with tech support trying to get useable speed. As you can see this made a world of difference.
Click to expand...
Click to collapse
Wow judging by your screenshot that's like 600% increase in service/speed!! Glad that I could help! I was in exactly the same spot you were in. For the life of me couldn't figure out why my Moto e got better service out here in the boonies I'm lucky to get a bar at that time.... Tried countless different methods techniques and apps with no success. Finally I talked T-Mobile into sending me a signal booster but that would only Boost whatever signal it could pickup itself.... So I have it 50yards from the house with an extension cable in a sealed bucket wrapped in towels just to get around 2-4mbs a sec download speeds n that was shotty every blizzard id get no service or **** would blow over n grounds frozen so unless I want to pay $150 for internet I can't watch anything n my son couldn't play his Fortnite.... I finally figured it out a couple days ago n haven't noticed any negative or side effects from the mod. If I get into an area with LTE+ and CA I can go faster than my buddies AT&T5Ge lol or around 130Mbs but before the hack in the same spot I'd average around 15mbs. I'm curious if people are having speed improvements with WiFi signals I don't have a good one so I couldn't test it. I can confirm flashing the Oos based custom roms or Magisk ROMs either before or after greatly slows/lags/retards signal quality and speed. I'm going to work on a ROM that doesn't and also has tethering throttle bypass built in... I'm thinking the reasons they slow everything down is because their all overseas ports rather than base it off a 6t stock.... Anyways thanks again for sharing ur results bladestonez and I
Appreciate the screenshot!:laugh::good::victory:
WillowTree said:
Is there a way to do this ob pixel 2 xl?
Click to expand...
Click to collapse
I'm sure there is to some extent as long as the device has a newer qcom modem and supports Carrier Aggregation & VoLTE in theory this would work for it. But without having the device to test with I couldn't tell you how to do it. Your probably gonna b messing around with dialer codes that lead to engineering modes. Sorry wish my Pixel2 didn't run off last year I'd be a lot more help.:crying:
Why has to be LTE/UMTS? Mine has everything enabled except network type is LTE/WCDMA. It seems there is not too much difference.
Sent from my ONEPLUS 6T using Tapatalk
ma678 said:
Why has to be LTE/UMTS? Mine has everything enabled except network type is LTE/WCDMA. It seems there is not too much difference.
Click to expand...
Click to collapse
UMTS is mainly for MMS support while normal texts are already sent through lte. Anyone who's CDMAless should be on LTE/umts
I have tmobile and verizon dual sim setup, does this apply to this guide too?
It doesn't.
ma678 said:
Why has to be LTE/UMTS? Mine has everything enabled except network type is LTE/WCDMA. It seems there is not too much difference.
Sent from my ONEPLUS 6T using Tapatalk
Click to expand...
Click to collapse
For all intensive purposes step 1 isn't necessary but if your using tmobile I've found that it will give you a more solid and reliable connection. But ur right this is an optional step however like @sonic1675 said unless your using Verizon or some cdmaish why have anything cdma related enabled? For step one any network type is allowed. But for TMO from my own personal experiences I prefer to use the LTE/umts but to each his own real question is did the mod work well on your Wcdma/LTE setup?
It's 4Anyone.
@humblehyper Verizon is fine to try it with. If u could do a before and after speed test comparison with screenshots to show your fellow vzw folk it works that'd be awesome.
But yeah this mod will work on OnePlus 4,5, 6/6t any carrier any location as long as the engineering apps are accessible and the same as the lay out describe...
gigilie said:
I'm sure there is to some extent as long as the device has a newer qcom modem and supports Carrier Aggregation & VoLTE in theory this would work for it. But without having the device to test with I couldn't tell you how to do it. Your probably gonna b messing around with dialer codes that lead to engineering modes. Sorry wish my Pixel2 didn't run off last year I'd be a lot more help.:crying:
Click to expand...
Click to collapse
I appreciate that you atleast answered. I do want a oneplus 6t but waiting for a good deal to buy it for.
Do you know anybody i can get help from?
Tmo here. I get better service without the VT
Last 2 test disabled vs previous 3 enabled vs previous 2 disabled
Thanks for the tip... Now to try by work... My first couple test scores
I'm also on T-Mobile and followed the guide. Definite improvement with download speeds, upload is still meh.
All 4 tests are done in the same location, the top 2 are the results after making the changes, and the result at the very top in orange (?) is single mode testing because I use AdGuard.
In case anyone is wondering why my Speedtest app looks different, it's because I use a smaller display size.
EDIT: Fixed screenshot upload, as AdGuard for some reason broke it.
Hey, why can't I activate VoLTE in the first step? The switch is grey and cannot be checked.
Did anyone try to check if VoLTE/VoWifi work after doing this? I have an unlocked Tmo variant but converted to OOS with active dual sim cards and I lost internet everytime while on a call. I was curious to try but did not work for me. I might be wrong but I think this trick might help ppl with single sim card or with other carriers like AT&T and Verizon from another forum here https://forum.xda-developers.com/oneplus-6t/help/att-verizon-volte-vowifi-calling-t3860031.
gigilie said:
This little trick will change your measly 1 bar signal to nearly max bars and give you a solid consistent signal in places you normally would hardly have a connection. At least it did for me.
This goes a bit beyond enabling VoLTE from your SIM Card Network settings which if you haven't done you should enable before trying this... Of course you may not have the same results I had. I found it works best from Stock ROM no root needed I'm currently on 9.0.12 but tried it on 9.0.11 and Beta 5.
Like any mod you should make a backup now and proceed with caution. (By caution I mean don't deviate from instructions goofing around in any engineering mode is never wise)
You should try check your internet speed now (Google internet speed! And take note of it then run the same test to see if your able to improve at all.
Step 1: Optional step but for best results open dialer and type: *#*#4636#*#* From this Testing Menu select Phone Information. Once in phone info select LTE/UMTS auto (prl) for preferred Network type. Then scroll down a bit and make sure VoLTE is switched on. Exit the phone info screen.
Step 2: Open Dialer again and type: *#800#
A Warning Message to Engineering Mode will popup. Press Enter.
Step 3: Click on the first option Called OnePlusLogKit
Once in the LogKit scroll down until you see the menu called: FunctionSwitch now click and select it.
Step 4: There's 3 checkboxes of interest in this menu... VoLTE Switch, VoWifi Switch and VT Switch. I enable all three but some may have better luck not enabling VT Switch. After enabling each option it'll try and reboot your phone just say no until you have all you want enabled.
Now reboot and profit.
If you notice anything negative or battery draining or your phone becomes even more radioactive simply go back into the menu and disable the Functions. If this helped you at all throw me a like. Enjoy.
Click to expand...
Click to collapse
Wow!! Works like a charm!!!
Will this work with any operator, or t-mobile only? I'm from Argentina, here i have Claro and no VoLTE, VoWiFi and nothing like that.
Sent from my OnePlus6T using XDA Labs
On VZW I was on and have tested this previously, LTE/TD-SCDMA/UMTS as this was the default. It performed fine. I switched to LTE/UMTS, the signal/speed is basically identical.
Default bands are usually 13 with both primary and neighbor but sometimes switches to band 4 or vanishes as only a primary and no neighbor on both settings. So, obviously just telling the radio it can use TC-SCDMA even CDMALess makes no difference since my SIM and phone is provisioned by VZW to only use LTE/UMTS anyway.
So going from LTE/TC-SCDMA/UMTS to LTE/UMTS Auto (PRL) from the original doesn't really do anything for the tower it connects to for me personally or speeds.
Also, the other tweaks did nothing but make things slower in the other menu.
Error: "Connection problem or invalid MMI code" after dialing *#800#. any idea? tia
unlocked TMO OP6t, converted to Int'l OOS 0.0.12 Dual Sim
ysfk7 said:
Error: "Connection problem or invalid MMI code" after dialing *#800#. any idea? tia
unlocked TMO OP6t, converted to Int'l OOS 0.0.12 Dual Sim
Click to expand...
Click to collapse
Use stock dialer. Google dialer doesn't work.