My S6 Edge SM-G925V worked perfectly back in India on Vodafone Band 3 LTE until marshmallow update. In the Nougat update verizon/samsung has some issue with their cellular firmware - after that i am never able to camp to any LTE network.
It was running smooth until the G925VVZW4CPD2 (6.0.1) update, all settings are ok. I tried the other popular network sim of JIO ( Band 40) that also is same. Bigger problem is that the modem crashes far too many times on the 2g/3G also. I can see the networks bar go and come in a loop again and again, making phone useless.
Verizon surely has messed something up with the latest 7.0 update, which they deny (have contacted them). There are couple of forums in Sammobile on the same. No luck with solution.
Just yesterday got one more update of 2GB which brings it to one update over 7.0. No luck. Still no LTE camping.
Do not suggest to check the APN settings i have checked they good. Anythings else or you also facing same issue ?
Can anyone show how to get the blocked service menu (via codes) working ?
Got the same problem. I immediately updated my phone from Marshmallow to Nougat via system settings.
I got the S6 Edge Verizon. Made several readings and found out that the device is unlocked, so I bought a local LTE SIM card (SMART) here in the Philippines and inserted it to the device. I applied the appropriate APN settings for the LTE and tested the connection. No luck. I wasn't able to test the LTE connectivity when I was in Marshmallow though.
I was able to connect to the internet via 3G connection and IT WAS WAAAY TO SLOW (0.5 mbps)
I tested the same settings with the Galaxy S5 (Verizon), still with a local LTE SIM card (SMART). LTE connection was immediately established (15+ mbps... not bad). This proves that my area is covered by LTE and the problem is on the S6 Edge. Is there a way to fix this?
anirudhgargi said:
My S6 Edge SM-G925V worked perfectly back in India on Vodafone Band 3 LTE until marshmallow update. In the Nougat update verizon/samsung has some issue with their cellular firmware - after that i am never able to camp to any LTE network.
It was running smooth until the G925VVZW4CPD2 (6.0.1) update, all settings are ok. I tried the other popular network sim of JIO ( Band 40) that also is same. Bigger problem is that the modem crashes far too many times on the 2g/3G also. I can see the networks bar go and come in a loop again and again, making phone useless.
Verizon surely has messed something up with the latest 7.0 update, which they deny (have contacted them). There are couple of forums in Sammobile on the same. No luck with solution.
Just yesterday got one more update of 2GB which brings it to one update over 7.0. No luck. Still no LTE camping.
Do not suggest to check the APN settings i have checked they good. Anythings else or you also facing same issue ?
Can anyone show how to get the blocked service menu (via codes) working ?
Click to expand...
Click to collapse
I have the same problem, since the update I can't connect to LTE, I've tried forcing the 4g/lte network but it simply wont connect.
so no answer to this yet huh? issue with wifes phone so i cant call her during the day but text are still getting through thank god!
I installed the new update via the smartswitch. Sw ver: NRD90M.G925VVRU4DQF3
This also did not solve the LTE camping issue on international roaming as stated in original thread, infact the modem crashes so often on 2G/3G also (GSM/UMTS)
Anyone here from verizon/samsung who can pass on the message to relevant folks that there is a major issue which they have not addressed. I am surprised such a common bug was not tested before releasing offical binary for update !! #shame.
Any updates?
anirudhgargi said:
My S6 Edge SM-G925V worked perfectly back in India on Vodafone Band 3 LTE until marshmallow update. In the Nougat update verizon/samsung has some issue with their cellular firmware - after that i am never able to camp to any LTE network.
It was running smooth until the G925VVZW4CPD2 (6.0.1) update, all settings are ok. I tried the other popular network sim of JIO ( Band 40) that also is same. Bigger problem is that the modem crashes far too many times on the 2g/3G also. I can see the networks bar go and come in a loop again and again, making phone useless.
Verizon surely has messed something up with the latest 7.0 update, which they deny (have contacted them). There are couple of forums in Sammobile on the same. No luck with solution.
Just yesterday got one more update of 2GB which brings it to one update over 7.0. No luck. Still no LTE camping.
Do not suggest to check the APN settings i have checked they good. Anythings else or you also facing same issue ?
Can anyone show how to get the blocked service menu (via codes) working ?
Click to expand...
Click to collapse
Any updates on a solution for this? I finally got around to updating my G925V OTA with Verizon, and I've run into the same issue. I hope I don't have to roll back the update manually but I guess I might have to because I have searched for a solution everywhere and have tried everything but nothing works.
Exact same issue, modem crashes constantly (I'll have signal on H/H+ only, and then it drops. Signal comes back. Then drops), and I never get LTE.
Tried all the obvious solutions (e.g. reboot, factory reset, network reset, clear cache partition, boot into safe mode, reprovisioning from carrier, confiming IMEI with carrier etc.) but nothing works.
What did you guys figure out?
lorenzopromot said:
Any updates on a solution for this? I finally got around to updating my G925V OTA with Verizon, and I've run into the same issue. I hope I don't have to roll back the update manually but I guess I might have to because I have searched for a solution everywhere and have tried everything but nothing works.
Exact same issue, modem crashes constantly (I'll have signal on H/H+ only, and then it drops. Signal comes back. Then drops), and I never get LTE.
Tried all the obvious solutions (e.g. reboot, factory reset, network reset, clear cache partition, boot into safe mode, reprovisioning from carrier, confiming IMEI with carrier etc.) but nothing works.
What did you guys figure out?
Click to expand...
Click to collapse
waiting for the solution as well. But i rolled back to 5.1.1
Purpose: The Google Play Store policy change in March has destroyed this critical functionality for many. Prior to that, using Pie produced very poor quality recordings compared to Oreo. This is how I restored call recording functionality. I will add any noteworthy contributions to this first post to make this easier than it has been for me. Many people have pulled their hair out with me to come up with this. This is simply a consolidation or our trials and errors.
This only works on Note 9 models SM-N960U and SM-N960U1 phones with boot loader version 1. To determine if you can use this procedure:
1. Go into Settings/About Phone to find the model number. It must show SM-N960U or SM-N960U1
2. Then click on "Software Information". On the "Build number", the 5th character from the right must be a 1. If it is not, this procedure will not work for you. If you don't own the phone yet, make ensure it is a 1 before you buy it.
For the SM-N960U model, this procedure will replace your carrier-specific firmware with US Unlocked firmware. It is not possible to prevent the carrier-specific firmware from updating to Pie and forcing other unwanted changes on your phone because it does not have the Blue "Software Update" program (com.wssyncmldm). When you finish, the model number will be changed to SM-N960U1. This process is reversible by flashing the phone with carrier firmware and using the standard ODIN version for that firmware.
The ramifications of moving from the carrier firmware to US Unlocked firmware are:
1. You will be able to flash to and remain on Oreo vs. being forced to Pie.
2. No carrier specific apps are flashed. (USERDATA which some refer to as bloatware)
3. Depending on whether the carrier's service is standards-based or not determines whether or not US UNLOCKED firmware will be able to make their services available.
- Verizon: No VoWiFi (Wi-Fi Calling). Everything else, including HD Voice and Carrier Aggregation work fine. My old phone didn't have it and coverage was never a problem, but if you travel, Wi-Fi calling means you have free calling to and from the US from anywhere you have an Internet connection. That could be prove quite valuable even if later you plan to get a local SIM.
- T-Mobile: Everything works except for roaming US Cellular's network. They have good coverage as of late, and the cheapest and 2nd fastest data.
- Sprint: Some users state that they retained Wi-Fi calling but I haven't heard many confirmations. I would guess if they have that, they also have VoLTE. I haven't heard about carrier aggregation, but if they do in fact have the other two, they probably have it as well. Again, my confirmation has been weak here.
- AT&T: No VoLTE or Voice over Wi-Fi. I haven't heard about carrier aggregation but it clearly doesn't play well with US UNLOCKED.
- after flashing U1 firmware. Wi-Fi calling is useful where you have no cell reception but you do have Wi-Fi and can save you a TON of money in roaming charges or purchasing an International plan. If you cannot get Wi-Fi calling and this is a requirement, you may want to cut out Android, carrier, and phone manufacturer altogether and read If they ever destroy this ability again at the end of this post.
4. You will need to download any carrier specific software you want from your carrier.
DANGER! On the "Build number" you are about to flash, ensure the 5th character from the right is a 1. If you flash one of the newer "U1" Pie updates that has a version 2 boot loader, you will never again be able to flash any version of Oreo, because they are all on version 1. You cannot flash a boot loader back to version 1.
Preparation Considerations:
- WARNING: If you use SmartSwitch to backup your phone, DO NOT press the update button when doing your backup!!! If you do, and it updates your boot loader to a newer version, it is the same as bricking the phone for someone who needs call recording because you can never be able to return to Oreo 8.1. OTOH, SmartSwitch is the only backup program for a non-rooted device that can restore almost everything back the way you had it. Download the setup.exe for the SmartSwitch for Windows, and the APK from APKPure.com. I copied both to a folder on my SD card so that I will always have a matched pair and I can restore without connecting to update software to execute the restore, and you may not want newer versions in the future. Install SmartSwitch on Windows and the phone. Before you do the backup, disconnect and forget Wi-Fi. The reason you want to do this is when you restore the phone and settings, it will also set up Wi-Fi like you had it and it will connect. The problem with that is by default SmartSwitch will start updating everything to the latest before the phone is in a position for you to stop it from happening. With no SIM or Wi-Fi, the phone interface settles first. Then you can put in the SIM and go to the play store and turn off Auto updates and notifications. The SIM doesn't become a problem as rapidly.
- I also recommend using pre-2019 Helium Backup apk and installing it as well as the Windows app version as well on your PC. Helium is more complicated to use, but is very flexible for restoring single apps such as using ADB, which works on any Android phone. Another reason you need it is SmartSwitch will only restore to a Samsung device. A Samsung device might be available or what you want when you need to do a restore. I have only 6 weeks with the Note 9 and have used Helium on my previous phones, so I'm still evaluating if Helium is what is best for the Note 9 and Oreo.
- Consider making a Downloads directory on your SD Card with sub-directories with .apk files that you will want to have available during or after setup, or are in danger of being ruined by an application upgrade so that you can readily restore them if necessary. For instance, mine contains a pre-March 7, 2019 version of SmartSwitch, old version of Helium, Automatic Call Recorder v5.43.11 or earlier, Automatic Call Recorder Pro v5.43.11 or earlier, etc.
Make these slight adjustments to the excellent procedure listed in the first post here: XDA: Confirm These Steps to Downgrade US Unlocked SM-N960U1 from Pie to Oreo
1. Prior to step 7, perform a factory reset from within Settings/General Management -> Factory data reset. If you do not, after flashing the phone, it will force a SIM or Wi-Fi connection to make you log in as a theft protection measure, during which time your phone will begin performing updates before you are in a position to implement measures to stop them. When you perform the factory reset from within Settings/General Management, it had to have been performed by someone who was logged into the phone and thus allows you to skip installing a SIM or enabling Wi-Fi during initial setup script, which in turn enables you to prevent any updates from occurring until you have made your changes.
2. Prior to 13, Do as minimal setup as possible, making sure you turn Wi-Fi off and Skip Wi-Fi. You will not be doing a restore, setting security, or setting up any accounts.
2. After 13.
a. Follow the steps shown here YouTube: HOW TO STOP FORCED OTA UPDATE NOTIFICATION from 0:25-1:49 to change app settings for both Software Update apps found in Settings/Apps and from menu select "Show System Apps". In "Battery", turn off "Allow background activity". In "Notifications", turn off everything. In "Apps that can change system settings" turn it off, but do not go past that point in the video or reboot as the video states to do afterward.
b. Back in Settings/Apps and on menu select Show System Apps. Go into Security Policy updates. In "Battery", turn off "Allow background activity". In "Notifications", turn off everything, and On lock screen set it to Do not show notifications. In "Apps that can change system settings" turn it off. *If this process runs, it aligns the phone's policy with that of the Play Store. It will not automatically update offending software, such as your call recorder, but it will list it. If it lists it, you are toast because the new policy, now implemented on your phone, will cause the now non-compliant previously useful software to hang when you try to use it. I know of no other option than to re-flash your phone and do a restore from a backup or start from scratch.
3. Reboot the phone and go into Settings/Apps/Show system apps, and ensure the Blue Software Update still shows disabled.
4. Prior to 15 install the SD card and install the SmartSwitch apk that was downloaded earlier to your SD Card using the Samsung My Files file manager.
*The following three item numbers must happen rapidly: (Have your play store credentials handy.)
5.. Insert the SIM to gain Internet access, not Wi-Fi if possible.
6. Go to the Play Store and immediately go into into Settings on the left side menu and turn off:
a. Automatic updates.
b. All Notifications
7. Go to your phone in Notifications and cancel all updates. Note: You will want any app updates to happen manually. Some will be affected by the March 2019 Play Store Policy changes that will ruin their functionality. The app developers usually will mention if there are functionality changes due to the new policy in the description area for their apps. When you go into play store and select My Apps, it will show you which ones need updating and you can decide which ones you can update and retain their functionality.
Restore Call Recording. (I use Automatic Call Recorder by Appliqato, but you can make adjustments based on the same logic.)
a. DO NOT download your software from Google Play. Sideload Automatic Call Recorder by Appliqato, sideload version 5.43.11 from an .apk from a Helium or some place like apkpure.com.
b. If you have a Pro license, restore that will need to come from a backup of version 5.43.11 or earlier. You cannot buy a Pro license any other place than the play store at the moment, and the one from Google will be too new.
Reboot and ensure all of your settings are still intact and fix any that are not. On the Blue Software Update icon, it should show a status of disabled next to it.
Going forward:
1. Backup your device with a program that can restore a single application. I've been using Helium, previously named Carbon. It is clumsy, but it makes compact backups into ZIP files, and the backup are stored as .apk files, so you can simply side load to do a restore of the app and data. Make SURE you tell it to include the applications because by default it expects to download the latest version from the play store which is NOT what you want. SmartSwtich is for changing phones or full restores. It is not a substitute for Helium.
2. Backup the PC area where the software to restore your device, firmware, and APKs are to restore your device.
3. Do not use the play store unless you have to. I've been using APKPure, but there may be other good ones also. This enables you to get older versions, which is critical for many critical apps. As I mentioned earlier, you cannot do effective call recording with the current call recording software from the play store. Look for dates prior to 2019. This also pertains to using SIP/VOIP clients because they don't allow them to access your phone book to dial with, and thus cannot keep a useful local log either. Having the APKs enables you to reinstall at any time. What you need may no longer be available from the play store in the future.
If they ever destroy this ability again, for $15/mo. to CallHippo and a data-only SIM, you can send Google, Android, and control on your life by your wireless vendor packing, plus you will have your recording, calling logs, and Voice over Wi-Fi via VOIP anywhere you can get a data connection, plus it is backed up forever. No more number porting, and if something happens to your phone, simply need to buy another phone. The only capability it needs is a data connection, so even a computer, tablet, or SIP phone will work. There are many other advantages as well. Multiple devices can respond to the same number and multiple people can answer and be talking on the same number. The only thing any of them will see is a secure connection to your VOIP vendor.
IT, thanks for this detailed post. I just want to clarify something you might want to update. Ramifications #3 for migrating to U1: wifi calling DOES work on T-mobile (but not volte), and it sounds great!
gruuvin said:
IT, thanks for this detailed post. I just want to clarify something you might want to update. Ramifications #3 for migrating to U1: wifi calling DOES work on T-mobile (but not volte), and it sounds great!
Click to expand...
Click to collapse
Thank you for the feedback. I've mentioned before on other threads that T-Mobile users are the only ones talking about Wi-Fi calling working on the U1 firmware, but I forgot to include that here. I will add than now.
However, I do have a few questions:
1. Did you flash the T-Mobile U1 firmware or the US UNLOCKED?
2. How did you activate Wi-Fi calling? Did it just work, or is there a place in the Interface in the T-Mobile U1 Firmware to put in your address?
3. Why do you believe that VoLTE is not working? VoLTE is digital voice, as is SIP/VOIP, Wi-Fi Calling/VoWiFi. VoLTE is part of the LTE protocol suite that came with LTE-A, which has been implemented on phones since the Note 4. An LTE network is a data-only wireless network just as the Internet's IP network is a data-only network. Voice cannot travel either network unless it is digitized. Wi-Fi calling (VoWiFi) requires a service at the carrier which negotiates the data stream source with your phone and transitions between wireless and the Internet without dropping the call to your carrier's PSTN server where they host your number. It's tough for me to accept that you have the far more complex VoWiFi without VoLTE. If using connection monitoring software your phone shows only an LTE connection during a call, VoLTE is being used and your nice clear calls are no mystery.
Thanks!
PS: There is only so much practical spectrum suitable for cell phones. In the US it is the FCC's job to responsibly manage the growing demand for that space. When carriers want to license bands from the FCC, there are ALWAYS catches. They made Verizon share a band with T-Mobile. Verizon and Sprint are not shutting down CDMA on their timeline, it is on the FCC's timeline for some deal they made that is part of their band licenses because it frees up those bands for LTE.(Verizon EOY 2019 and Sprint EOY 2020) Similarly, providers are telling customers that they will not support phones on their network without HD Voice/VoLTE (Added with LTE-A) past...(Verizon EOY 2019). They will GIVE you a phone, and maybe even tape money to it, to get your old phone off and keep you as a customer. The FCC isn't allowing them to suck up bands that can only be used for analog voice calls. Carriers cannot do carrier aggregation that way either to where they can balance traffic across multiple bands so they don't have some over utilized while others are under utilized. LTE-A Rel. 10 of 2011 already enabled up to 5 bands to be aggregated up to 100 mbps. For carriers like Verizon it is panic. They know there is no point in approaching the FCC for anything unless they can prove they've optimized what they have. The T-Mobile and Sprint merger is a beautiful thing. It's like sewing a head onto a body.
IT_Architect said:
1. Did you flash the T-Mobile U1 firmware or the US UNLOCKED?
2. How did you activate Wi-Fi calling? Did it just work, or is there a place in the Interface in the T-Mobile U1 Firmware to put in your address?
3. Why do you believe that VoLTE is not working?
Click to expand...
Click to collapse
1. I've read that U* firmware is carrier-specific, here in the USA, except for U1, which I have, which is USA unlocked and unbranded (no carrier). I bought the phone new with U1, un-branded, no carrier firmware, so I did not flash anything. It came with Android 8 and I immediately let it do all of its updates to bring it forward to Android 9. I think that was in June. So, no, not T-Mobile. U1 unlocked. (Love this--very little bloat, and I've used adb to disable some apps as well, namely that FaceBook TRASH)
2. There is no access to Wi-Fi Calling in the settings, however there is a Wi-Fi Calling toggle in the toggle drop-down, and I've confirmed that it indeed does switch Wi-Fi calling on and off, by walking in and out of my home wireless area while in a call and watching the Wi-Fi icon on the call screen appear and disappear and hearing the quality become very clear when on Wi-Fi calling and get less clear when switching to the carrier network.
3. I am not sure about VoLTE, because there is no toggle or VoLTE setting in settings. I had never really tested it or cared, but I just now tried a test. I downloaded the "LTE Discovery" app to see the band my phone is connected to, in realtime. I am on LTE band 4. I am at home and connected to my internet over wifi. I placed a call to my wife, and it was going over my wireless (wifi icon in call screen). Not the right condition for this test, so I turned off my phone's wifi. I then placed the same call, confirmed his call was not over wifi (and must be over the carrier network) and switched over to the LTE Discovery app to see if it had connected to a non-LTE band for the call. It was still connected to the LTE Band 4 that it was connected to before the call. I might assume this means that VoLTE worked. Even still, I don't know how to test further, since there doesn't appear to be anything that allows me to turn VoLTE on or off. Nothing in settings or no toggle in the toggle drop-down. One thing that make me hesitate to fully believe that that test call was VoLTE is that I believe Band 12 is the only band that is LTE-ONLY..... if I could make a voice call while on that band, then I think VoLTE must have been working (?). But I don't know if the LTE Discovery is doing a great job of connection monitoring for Band 4... I mean, is it possible it would show LTE Band4 while placing a voice call and switching to a non-LTE connection? I don't know.
Hope that helps!
Also, thanks for the intro to VoLTE. That helped me understand VoLTE better.
gruuvin said:
...I immediately let it do all of its updates to bring it forward to Android 9.
Click to expand...
Click to collapse
I'm on 8.1 because we need it for call recording purposes.
gruuvin said:
There is no access to Wi-Fi Calling in the settings, however there is a Wi-Fi Calling toggle in the toggle drop-down, and I've confirmed that it indeed does switch Wi-Fi calling on and off, by walking in and out of my home wireless area while in a call and watching the Wi-Fi icon on the call screen appear and disappear and hearing the quality become very clear when on Wi-Fi calling and get less clear when switching to the carrier network.
Click to expand...
Click to collapse
That's interesting. I'm on Verizon U1 US UNLOCKED connected to Wi-Fi and don't have it, but that's not a surprise. It would be interesting to see if it works on T-Mobile U1 8.1 US UNLOCKED or U1 8.1 T-Mobile. My guess is if T-Mobile, if it works with 9.0 it will work with 8.1 since phones have supported Wi-Fi calling for a long time. It would also be good to know your build number from About Phone/Software Information and what it shows in Service provider SW ver. in ???/???/???.
gruuvin said:
I turned off my phone's wifi. I then placed the same call, confirmed his call was not over wifi (and must be over the carrier network) and switched over to the LTE Discovery app to see if it had connected to a non-LTE band for the call. It was still connected to the LTE Band 4 that it was connected to before the call. I might assume this means that VoLTE worked.
Click to expand...
Click to collapse
If you go to the menu and select "System Network Setting" it will show you hidden screens and show you if VoLTE is turned on. If you go into System Info/Feedback, you can learn quite a bit about your phone that doesn't display in settings. Is Worldphone set to True or False? It would be interesting to see what Network Cell Info Lite shows on the Device-SIM tab in the Device Telephony area, and what shows on the RAW tab when you are in a call with Wi-Fi on and off during a call. Where I'm at LTE is inescapable. You can learn a lot by using Network Cell Info in concert with Force 4G LTE which can force any band, not just 4G LTE. Set it at some old supported protocol for your network in Force 4G LTE, and make sure Network Cell Info shows what you set it to. Then switch back to Auto and see that it returned to the default. That will give you confidence that Network Cell Info is showing you what is actually going on when you make a call. Eh...conversely, when you are finished playing around, make sure you set Force 4G LTE back to Auto, and confirm in Network Cell Info.
Thanks!
IT_Architect said:
I'm on 8.1 because we need it for call recording purposes.
That's interesting. I'm on Verizon U1 US UNLOCKED connected to Wi-Fi and don't have it, but that's not a surprise. It would be interesting to see if it works on T-Mobile U1 8.1 US UNLOCKED or U1 8.1 T-Mobile. My guess is if T-Mobile, if it works with 9.0 it will work with 8.1 since phones have supported Wi-Fi calling for a long time. It would also be good to know your build number from About Phone/Software Information and what it shows in Service provider SW ver. in ???/???/???.
If you go to the menu and select "System Network Setting" it will show you hidden screens and show you if VoLTE is turned on. If you go into System Info/Feedback, you can learn quite a bit about your phone that doesn't display in settings. Is Worldphone set to True or False? It would be interesting to see what Network Cell Info Lite shows on the Device-SIM tab in the Device Telephony area, and what shows on the RAW tab when you are in a call with Wi-Fi on and off during a call. Where I'm at LTE is inescapable. You can learn a lot by using Network Cell Info in concert with Force 4G LTE which can force any band, not just 4G LTE. Set it at some old supported protocol for your network in Force 4G LTE, and make sure Network Cell Info shows what you set it to. Then switch back to Auto and see that it returned to the default. That will give you confidence that Network Cell Info is showing you what is actually going on when you make a call. Eh...conversely, when you are finished playing around, make sure you set Force 4G LTE back to Auto, and confirm in Network Cell Info.
Thanks!
Click to expand...
Click to collapse
Gonna read through this and respond in a sec, but I came back to this thread to report something I found. Using QuickShortcuMaker, I was able to find and launch "com.android.settings/com.android.settings.RadioInfo". This gives a bit of interesting output and lets me toggle "Wi-Fi Calling Provisioned" and "VoLTE Provisioned". I have previously hunted for VoLTE in the settings menus quite exhaustively and never found anything, so this is great (also, both were toggled on). There is also a "Video Calling Provisioned" toggle, but it's grayed out.
Software Info screenshot attached.
So, "System Network Setting" and "System Info/Feedback" are not in settings men, so you'll have to give me a hint where to find these, because I don't know what menu you were referring to.
Trying the "Network Cell Info Lite" app now. Ahhhhh, there's the "System Network Setting" menu you referred to.
And going there only takes me into my android settings "Mobile networks" menu with no hidden anything. I'm fairly sure this has to do with the csc I have for the unbranded U1 rather than carrier branded csc. CSC controls what gets shown in menus. I went through this with my S7 Exynos version when trying various cscs and even modding my own to force wifi calling and volte.
On to "System Info/Feedback". I'm attaching a screen shot of that too.
Okay. I installed Force 4G LTE. Great tools! I'll good advice. I'll go play now.
Side note: I write backend software for sustaining a nationwide fiber transport and ip layer backbone, and I'm a stickler for engineers being precise, accurate, and thorough. Well done, IT!
Oh one more thing. Screenshot of com.android.settings.radioInfo
Allowed Network Cell Info to read phone state. World phone = false
Uhhh... I just kinda realized. This is hijacking your thread.
gruuvin said:
Oh one more thing. Screenshot of com.android.settings.radioInfo
Click to expand...
Click to collapse
GET THIS THUMBNAIL OFF OF HERE QUICK!!! It has your IMEI number on it.
The thread is about call recording and of which preventing migration to Pie by using U1 firmware is required. Any way that can also restore Wi-Fi calling on U1 firmware is what everyone wants. Using the U1 firmware with the T-Mobile SIM works, but it is also needed for Verizon and others where that doesn't work.
thanks.. ya i meant to scroll my screen up a bit more to cover my phone number and imei.... it's getting late, and I should probably get off the interwebs.
went and read up on what someone could do with my imei....
anyhow... I installed "Force 4G LTE" by DevAppliance, and maybe that's not the app you were referring to... it didn't seem to do what you suggested.... and there does seem to be a few apps out there that match that name... what's odd is by clicking on the one of two options, the one that should have let me force 4g... it loaded the com.android.settings.radioInfo I had originally come back to this thread to report... the one that actually shows the hidden VoLTE and WiFi Calling Provsioned toggles (and yes the one I screenshotted of my imei, ughh). What are the chances? Really odd!
Oh, and then I uninstalled it, because it's basically useless, besides tons of junky ads.
So what's the developer that makes the Force 4G LTE you referred to?
gruuvin said:
I installed "Force 4G LTE" by DevAppliance, and maybe that's not the app you were referring to... it didn't seem to do what you suggested....So what's the developer that makes the Force 4G LTE you referred to?
Click to expand...
Click to collapse
I posted a bad link and just now corrected it.
btw U1 or any U firmware are muti csc. so i a sense even if you have never flashed a crarrier branded frimware, their CSC is still in the odm partition part of your device. the bloat apps arent on U1 of course. now the question is how are they able to ascertain if u are on U1 or not. because at this point it is not the blacklisting of the imei on non carrier bought device from using advanced csc features as people with U carrier bought phones have reported that after flashing U1 they have either WFC or volte not working( or in some cases both).
bober10113 said:
btw U1 or any U firmware are muti csc. so i a sense even if you have never flashed a crarrier branded frimware...now the question is how are they able to ascertain if u are on U1 or not.
Click to expand...
Click to collapse
1. I'm going to toss out VoLTE because just because people say it isn't happening, doesn't mean it isn't. I've proven in a couple of instances now. If they call and only LTE is active during a call, it HAS to be using VoLTE. LTE cannot pass voice any more than IP can without it being digitized. IMO the FCC wouldn't allow carriers to communicate with LTE-A phones where they have an LTE-A network available, even if they wanted to.
2. IMO, Wi-Fi calling is the only one left standing and that we can prove only works on the U1 firmware for T-Mobile and Sprint. On the same phone, if you insert in a T-Mobile SIM your have Wi-Fi calling, and if you insert a Verizon SIM it goes away. Network Cell Info Lite shows this in the attachment that VoWiFi and ViLTE are not available with the U1.
3. When we flash Verizon's carrier-specific firmware, ViLTE and VoWiFi are available, once you fill in an address, VoWiFi must actually be standard SIP/VOIP because it makes no sense for a cell phone to have an address and an address is a VOIP requirement.
4. When you flash ANY carrier specific firmware, the the Blue Software Update icon does not show nor does ADB have access to it. USERDATA also implements the Security Policy of the carrier.
5. The next question is can VoWiFi and ViLTE be turned on remotely without a firmware upgraded. If I were to guess, I'd say yes. I already found the VoLTE hidden screen Network Cell Info Lite and I'd guess that Wi-Fi Calling is also in the base firmware that can be activated, and because it would make good business sense to be able to activate it on all devices from a flag change in a central location. When USERDATA is present, it references that. I base this on the fact that T-Mobile and Sprint activate VoWiFi and Verizon does not when no USERDATA is present.
Just a guess,
Next questions:
1. Referencing the attached picture, what determines whether or not a phone is a world phone? It's carrier unlocked and has more bands than any other phone but states it is not a world phone.
2. Do US phones incur limitations on non-US networks if they support the proper bands?
3. Do "world phones" work on US networks?
For those with a U1 unbranded variant who cannot load com.android.settings.radioInfo from their Settings menu, you can can just create a shortcut using Nova Prime launcher or some equivalent. You can use it to turn on/off Wi-Fi Calling and VoLTE. You can also use it to force your radio to connect to different bands, with more control than you get through Settings > Mobile Networks. You do not need a special app like "Force LTE Only" to do this.
Just make a shortcut to com.android.settings.radioInfo, also labeled "Device info".
gruuvin said:
Just make a shortcut to com.android.settings.radioInfo, alse labeled "Device info".
Click to expand...
Click to collapse
I'm on the latest 8.1 U1 with Verizon SIM installed and I do not have that. What are you on?
IT_Architect said:
I'm on the latest 8.1 U1 with Verizon SIM installed and I do not have that. What are you on?
Click to expand...
Click to collapse
9. When was the latest 8.1 released? Security patches?
gruuvin said:
9. When was the latest 8.1 released? Security patches?
Click to expand...
Click to collapse
The build date is 2018-12-14 - N960U1UEU1ARL1 and with the Verizon SIM installed, which makes a difference too. If you make no other changes other than plug in a T-Mobile or Sprint SIM, Wi-Fi Calling will appear before your eyes in real time.
US Note 9 Carrier-Specific vs. US Unlocked Firmware Observations & Theories moved to new thread
gruuvin said:
9. When was the latest 8.1 released? Security patches?
Click to expand...
Click to collapse
Hi gruuvin,
This thread and the one it references is by and for users who need to remain on Oreo 8.1, and this thread in particular, focuses on regaining usable call recording abilities. Android 9.0 Pie cannot do clear call recordings, and the spring 2019 Google play store policy update has destroyed people's ability to have the usable call recordings that has affected phones at least back to KitKat. These surprise malware attacks have wiped out not only the ability to to have meaningful call recording going forward, they have also destroyed previous records that they used as the a basis and proof of service for their invoicing. To us it is worse than ransomware because you can't even pay the ransom. It has also been people's automatic note taker for projects so things don't get missed, and the basis and backup of invoicing for professionals who invoice for their time. Some simply used it to not have to interrupt the flow of the conversation to write notes, and especially while driving. Moreover, often you do not know when the conversation is held if it's details will become significant later. People have been relying on this ability for many years and it was the deciding factor when choosing between Android and the iPhone. If they could use Android 9 Pie, and trust Google play store policy updates, they would not have flashed from their carrier's U firmware to U1, and investigating the possibility of a work-around to regain Wi-Fi Calling. At the moment, the only networks I'm aware of that support Wi-Fi Calling using U1 firmware's native abilities are T-Mobile and some indicate Sprint as well. This MAY be because they got into it early and as a result do not have a standards-based implementation, and must be handled by the carrier's USERDATA in the U firmware.
Thanks!