Database Users

[Q] Little data roaming despite disabled

I have now for the second time the problem that I have many little data roaming connections while abroad, despite data roaming is deactivated in Android. They are so small (always exactly 30 kB, which seems to be the smallest quantity my provider is billing) that it's virtually impossible to produce them with normal traffic. I always have much larger data connections, even without using my phone (at least 100kB up to 1MB and even more if I use it, of course). In this case I had 9 of those connections while little more than 24h. Last time when I had this problem half a year ago, I had those connections for an entire week with the same frequency (~10 per day).
In both incidents there was an OTA update available for the Nexus 4. This time I received the update notification at some point during my stay abroad. I had wifi connection most of the time, so I assume the update was downloaded using the wifi connection (the roaming traffic is too small for the update by far). I did not install the update until I returned back home. Last time my phone wasn't able to download the OTA update, since I had a custom rom installed at that time. It is possible that it tried downloading the OTA update for the entire stay back then (and even before and after - I noticed increased traffic over normal mobile internet at home). I switched back to the stock rom a while ago and thus was now able again to receive official OTA updates.
This time I was staying for 8 days in Chile, last time was around one week of Italy. My provider is Orange Switzerland.
What can be the cause of this? I am absolutely certain that data roaming was disabled in Android both times. Could it be that Android somehow bypasses the disabled roaming when checking for OTA updates? But it would have to do it when already knowing there is an update, so what's the point of doing this? Or could it be a provider initiated connection to notify the phone of the update? What can I do to prevent this from happening in future?
Thanks for any input!
Martin

Are you disabling mobile data and roaming or just roaming?
You could also try deleting or changing your default apn to prevent this from happening.
When I travel outside of Canada, I do not incurr any roaming charges when I turn off mobile data and roaming,

Thanks for the reply. I just disabled data roaming. I am abroad quite a lot, apart from these two incidents I never had any unexpected roaming charges. It must be somehow connected to the OTA update.
I will try disabling mobile data next time, maybe also disabling updates. But I also would like to understand how this can happen. Would it actually be possible that my provider initiates data connections to push the update notification? On the other hand my phone doesn't make those connections all the time, so it cannot just be the regular checking for updates. If it just received the notification via wifi, it would have downloaded the update via wifi immediately. So there must be some kind of mechanism I do not understand.
I also noticed that some of those roaming data connections occurred during the night, when I actually had wifi in the hotel for sure. This doesn't make any sense to me at all...

I don't want to take a chance so I disable all data connections, including roaming, as well as sync, software and app updates, and anything else I can think of that might try to access the data network.

Disabling sync etc. is not an option, since I want to use it via wifi. Besides, this must be either a bug in the Android update mechanism (which is persistent over some versions apparently) or my provider is doing something stupid. In the first case I would like to inform the devs, in the second case I won't pay for the data roaming, since I wouldn't be responsible for it.
Any ideas how to find out which one is true? Is here by chance anyone who either
a) has received a bill with many very small data roaming connections despite roaming was disabled while an OTA update was rolled out, or
b) was on the contrary abroad while the OTA update was rolled out and received the update notification via wifi, and has not seen any such roaming connections on the bill?
Thank you very much!

Wow, I can't even imagine worrying about overages and roaming charges... T-Mobile FTW!
Which custom ROM are you running? If it's not stock, there shouldn't be anything that has to do with an OTA, unless that functionality is not removed for some odd reason. Does the data usage utility show any useful information?
Sent from my Nexus 4 using XDA Premium 4 mobile app

korockinout13 said:
Which custom ROM are you running?
Click to expand...
Click to collapse
I am on stock right now. During the first incident I ran some stock ROM, but I no longer remember which one. The data usage shows me Android OS would have transferred a 15.65 KB.
Edit: T-Mobile has no roaming charges if you are outside the US?

Have the same problem. Just one week ago I was on holiday. They also charged me twice for a 30 KB connection on different days (Orange Swizerland). I first thought it's maybe because I installed a custom rom but it also happened to my brother whose phone is 100% stock.
Did you found a solution?
Regards

Interesting. So it is an Orange problem after all...
7ORO said:
Did you found a solution?
Click to expand...
Click to collapse
Not really. I now disabled the OTA update service (using the disable service app), so this cannot happen any more (I believe). Also I will switch to another provider at the end of this month, so if Orange is doing something strange, I will no longer be affected.

Same thing happened to me this month on my Nexus 6P on android 7.1
It used between 0.00mb and 0.04 mb (according to my data usage logs from the telephone company) (Telus)
Any other person figured out how this could happen and what's the solution?

had this last month. On Oreo 8.1 Stock + root Essential Phone (see here for details) https://forum.xda-developers.com/essential-phone/help/data-roaming-charges-despite-disabled-t3796715
Anybody has an idea?

three verizon nougat questions

I am currently on 935U, Marshmallow 6.01 PL4 (phone is a verizon Edge s7), unrooted.
1) I have read that the samsung dialer is no longer on Nougat , nor is the Samsung caller id?
Can someone verify if this is true? From reading further, I am not sure if it is the aesthetics that have changed or the actual dialer. My favorite feature of the edge 7 is the suspected spam id and block that comes up as a call comes in and also, sthe small window that comes up at the top of the phone to answer a call when you are in another app. Can anyone who has taken verizon nougat tell me if these features are no longer available?
2) I have read that tethering is not available on nougat without tweaking. Is this the same as mobile hotspot? I currently use mobile hotspot for my tablet when I am traveling and wifi signal is poor. I connect to the mobile hotspot using bluetooth. Can someone verify whether or not this option is available on Verizon Nougat without tweaking?
3) Lastly, my phone has lagged up greatly lately, I am considering flashing back to verizon software and taking nougat. If I am unhappy, will I be able to go back to 935 Marshmallow (currently on PL4) or is reverting back to Marshmallow not a possibility.
thanks in advance!

I'm not sure if it's the dialer either, bit give hiya a trt. It's by whitepaper and blocks spam really well, plus you can submit numbers as well for blocking.

tmord1 said:
I am currently on 935U, Marshmallow 6.01 PL4 (phone is a verizon Edge s7), unrooted.
1) I have read that the samsung dialer is no longer on Nougat , nor is the Samsung caller id?
Can someone verify if this is true? From reading further, I am not sure if it is the aesthetics that have changed or the actual dialer. My favorite feature of the edge 7 is the suspected spam id and block that comes up as a call comes in and also, sthe small window that comes up at the top of the phone to answer a call when you are in another app. Can anyone who has taken verizon nougat tell me if these features are no longer available?
Click to expand...
Click to collapse
This has never been available on Verizon firmware. Not even on 6.0. Verizon ripped the feature out to force you to buy "Verizon Caller ID" instead.
2) I have read that tethering is not available on nougat without tweaking. Is this the same as mobile hotspot? I currently use mobile hotspot for my tablet when I am traveling and wifi signal is poor. I connect to the mobile hotspot using bluetooth. Can someone verify whether or not this option is available on Verizon Nougat without tweaking?
Click to expand...
Click to collapse
"Mobile Hotspot" and "tethering" are the exact same thing. Most people who say "tethering" are referring to PDANet or whatever, because they're on grandfathered UDPs and refuse to switch to new plans. I have Wifi, Bluetooth and USB available as options for sharing my phone's LTE connection to a computer or tablet - I can even plug my phone into my router and have my router use it as the modem for my entire home network.
3) Lastly, my phone has lagged up greatly lately, I am considering flashing back to verizon software and taking nougat. If I am unhappy, will I be able to go back to 935 Marshmallow (currently on PL4) or is reverting back to Marshmallow not a possibility.
thanks in advance!
Click to expand...
Click to collapse
Generally, "lagging" is due to rogue apps and/or a corrupt cache. I would look at any apps that have suspicious permissions (why would a flashlight app need to access your contacts, for example) and dump them, and clear the cache.
As of right now, I'm running Verizon's 7.0 side by side with U 6.0.1 on two different Edges. 7.0 is beautiful and fast, but Verizon changes too much and removes too many features. If you only have one device, I would stick with the U FW and wait till next month for the U 7.0 update. My two cents.

@raduque Really appreciate the detailed answer!

You're welcome tmord1!

x below lte signal and not internet connection help!

Hello so as stated above for some reason i have an x below my signal bar but it still says lte but not connection, ive tried the following, remove sim and put it back in (both with the phone off and on), checked my apns which i never had to mess with before (which i didnt have this issue yesterday just saw it when i got to work which i usually have lte signal), turn on and off airplane mode, turn off and on mobile data, ive tried every fix i could think of so far with none of them working.. my cell service is been paid and i checked my straight talk account to make sure, but now comes the weird part when im connected to wifi and pull down the quick toggles it shows no x under the lte (see screenshot below) does anyone know how to fix this issue i rely on my lte data for directions and gps at work.
Phone info:
Android 8.1 beta opp5 rooted
Thanks to anyone that can help!

I am having this same issue as of this morning, and I am on the Straighttalk AT&T network. I wonder if they just updated their APN network and our APN settings need to be updated too? If so, I'm not sure what settings to use.. using the straight talk website and selecting "Android 4.0" (the newest version listed), it shows the settings I'm currently using. Anyone else having/resolved this issue?

ArmStrongDickPunch said:
Hello so as stated above for some reason i have an x below my signal bar but it still says lte but not connection,
Click to expand...
Click to collapse
Borrow a (different carrier) SIM from a friend to see if it is a network issue. If the LTE works on that SIM, go to ST and have them provision another SIM for you (free). If the LTE still doesn't work, back your phone up, wipe it, flash a full image.

ArmStrongDickPunch said:
Hello so as stated above for some reason i have an x below my signal bar but it still says lte but not connection, ive tried the following, remove sim and put it back in (both with the phone off and on), checked my apns which i never had to mess with before (which i didnt have this issue yesterday just saw it when i got to work which i usually have lte signal), turn on and off airplane mode, turn off and on mobile data, ive tried every fix i could think of so far with none of them working.. my cell service is been paid and i checked my straight talk account to make sure, but now comes the weird part when im connected to wifi and pull down the quick toggles it shows no x under the lte (see screenshot below) does anyone know how to fix this issue i rely on my lte data for directions and gps at work.
Phone info:
Android 8.1 beta opp5 rooted
Thanks to anyone that can help!
Click to expand...
Click to collapse
I called STW tech support, and they told me I had the wrong APN... I updated my APN settings (but really it was nothing other than changing the ID, so I don't think it had any real effect) and still had no data. After checking downdetector.com, it appears there is a widescale data outage with straight talk (or more specifically, AT&T). One of the commenters stated the following:
"I can confirm the issue is DNS. If you have the ability to changes the DNS on your phone, you can restore service. If you have Android + Root, I used DNS Override successfully. Just set DNS Servers to Google's"
I just used DNS Override ($2 app) to set my DNS servers to Google's and that resolved my issue. Hope that helps. If you don't want to spend $2, there are some free apps that also will change the DNS servers for you, and there are other methods detailed here: https://forum.xda-developers.com/ge...ide-how-to-change-dns-android-device-t3273769

Update: earlier that day ot seemed to resolve itself while i was driving at work amd got to my destination which was about an hour away and once i looked at my phone ot no longer had the x and had full service amd working lte so idk maybe it was cell tower maintenence but don't know for sure but the issue hasn't happened again tho but thanks for everyone for the help and suggestion!

Accidentally sideloaded verizon full image

So I was rooting my Google store bought pixel 4 and missed a step. Needless to say I had to sideload a full ota to recover it. But I'm pretty sure I accidentally loaded the verzion version. I got all the verizon apps that showed up when I rebooted the phone. I went back and wiped everything in recovery mode and tried sideloading QD1A.190821.007.A3 and it keeps erroring out. This is the firmware that Im 90% sure what was on my phone. Is there a way to get back to factory google store firmware or am I screwed now? I am on a verizon sim but phone was bought on launch day from the google store. Its also noted that I am currently on QD1A.190821.014 firmware. This doesn't appear to be the verizon firmware.

The Verizon apps appear not based on which ROM version you load, but instead based on whether you have a Verizon SIM in the phone during setup.
If you loaded the wrong ROM onto the phone, you may not be able to recover by sideloading an OTA. You should be able to recover by doing a complete reflash of the image you want (the image version, not the OTA version).
What error is it giving you?

I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.

BubbaGumprc said:
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
Click to expand...
Click to collapse
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.

Jon8RFC said:
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Click to expand...
Click to collapse
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?

bobby janow said:
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
Click to expand...
Click to collapse
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.

Jon8RFC said:
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Click to expand...
Click to collapse
My wife has a Verizon device Pixel 3 locked bl and I have a Pixel 4 and they both have MVS disabled and both can call on wifi. I just tested again to make sure. Really, I'm the only one? Gotta love that. I hate that they can get into my device without my knowing and see what and when I installed stuff.

No data roaming on custom ROMs for Z00ED

I've had stock MM for two years, but recently it was starting to get really slow so I decided it was time to install a new OS. I've tried XenonHD, Lineage 16, AOSP and Lineage 17 but all have the same issue: I just can't get the mobile data to connect. I've tried all the common fixes for this issue suggested on the internet, like toggling airplane mode on/off etc, and I've checked that the APN settings are correct, allow data roaming is enabled and my data plan is still active.
I think it's some kind of issue with the ROMs, because someone else has mentioned that XenonHD won't connect to data while roaming. I'm currently residing in a European country that isn't my home country, and using the SIM from my home country since the provider has good value for money data plans and the EU has recently made it illegal for them to charge extra for roaming within its borders. So I think the devs need to catch up with the times and realise that data roaming is now fundamentally important for some users. Unfortunately, it looks like they have abandoned the ROMs they have put out, so I won't be getting any help from them directly. Does anyone else have any idea what I could do, apart from reinstalling stock MM? And I'd rather not buy a local SIM card right now since I'll anyway be moving to a different country in a few months.

I've since also tried ViperOS and MIUI 8, but still no data. From Lineage 17 onwards, my phone was also showing the wrong time and date, so there seems to have been some additional issue with the network connection (even though I could make and receive calls). I also noticed that if I would try to manually connect to the other available network here, immediately I would get the message "Unfortunately, the process android.com.phone has stopped."
So I've gone back to stock MM for now and the data came back. I would still appreciate if someone could fix this issue with the custom ROMs though so that I could use one. I think they are faster than stock and it would be nice to explore their features. It's a shame I can't use them just because of one issue. I will probably still need the data roaming when I move to another European country in a few months time.