5.3 keeps turning mobile data on

It took a while to reproduce my 'auto data turn-on' issue, and then another long time to reproduce it with LogFox recording the logs at the time (thanks for that suggestion @IsHacker ). I've now got a log that seems to capture the issue but, not being at all familiar with the logging, I'm now struggling a bit to understand more about the cause from what I can see in the logs.

For comparison, when I manually/explicitly turn on mobile data (via the drop down menu mobile data widget), I see the following in the logs -
...
1739351892.887 10032 14832 14895 D DataUsageController: setMobileDataEnabled: enabled=true
1739351892.887 10032 14832 14895 D TelephonyManager: setDataEnabled: enabled=true
1739351892.903 radio 3471 3804 D QcDataStatusNotification Service: MultiSim onChange(): subId = 1
1739351892.903 radio 3471 3804 D QcDataStatusNotification Service: onChange():uri=content://settings/global/mobile_data1 authority=settings path=/global/mobile_data1 segments=[global, mobile_data1] uriLastSegment=mobile_data
1739351892.922 radio 3471 3804 D QcDataStatusNotification Service: handleMessage: Data Enable changed to 1 on slot = 0
...

and I see something similar (but not identical) in the big problem log capture -

...
1738430214.184 radio 3471 3471 D zsj : Phone.isCarrierLockDataRadioTech, first setDataEnabled(false), then setDataEnabled(true).
1738430214.184 radio 3471 3471 D TelephonyManager: setDataEnabled: enabled=false
1738430214.187 radio 3471 3471 D TelephonyManager: setDataEnabled: enabled=true
1738430214.192 1000 623 623 E SELinux : avc: denied { find } for pid=24997 uid=10173 name=tethering scontext=u:r:permissioncontroller_app:s0:c173,c256,c512,c768 tcontext=u:object_r:tethering_service:s0 tclass=service_manager permissive=0
1738430214.197 1002 32757 567 D a2dp_codec: A2DP_GetCodecType:
1738430214.197 1002 32757 567 I chatty : uid=1002(bluetooth) btu message loo identical 1 line
1738430214.197 1002 32757 567 D a2dp_codec: A2DP_GetCodecType:
1738430214.203 radio 3471 3661 D QcDataStatusNotification Service: MultiSim onChange(): subId = 1
1738430214.203 radio 3471 3661 D QcDataStatusNotification Service: onChange():uri=content://settings/global/mobile_data1 authority=settings path=/global/mobile_data1 segments=[global, mobile_data1] uriLastSegment=mobile_data
1738430214.206 radio 3471 3661 D QcDataStatusNotification Service: handleMessage: Data Enable changed to 1 on slot = 0
...

Does anyone have any suggestions about what might be going on in relation to the '... radio ... zsj Phone.iCarrierLockDataRadioTech ... setDataEnabled(true)', how to interpret it, or where I could find more help and info about what it might be telling me?
 
  • Like
Reactions: IsHacker
It took a while to reproduce my 'auto data turn-on' issue, and then another long time to reproduce it with LogFox recording the logs at the time (thanks for that suggestion @IsHacker ). I've now got a log that seems to capture the issue but, not being at all familiar with the logging, I'm now struggling a bit to understand more about the cause from what I can see in the logs.

For comparison, when I manually/explicitly turn on mobile data (via the drop down menu mobile data widget), I see the following in the logs -
...
1739351892.887 10032 14832 14895 D DataUsageController: setMobileDataEnabled: enabled=true
1739351892.887 10032 14832 14895 D TelephonyManager: setDataEnabled: enabled=true
1739351892.903 radio 3471 3804 D QcDataStatusNotification Service: MultiSim onChange(): subId = 1
1739351892.903 radio 3471 3804 D QcDataStatusNotification Service: onChange():uri=content://settings/global/mobile_data1 authority=settings path=/global/mobile_data1 segments=[global, mobile_data1] uriLastSegment=mobile_data
1739351892.922 radio 3471 3804 D QcDataStatusNotification Service: handleMessage: Data Enable changed to 1 on slot = 0
...

and I see something similar (but not identical) in the big problem log capture -

...
1738430214.184 radio 3471 3471 D zsj : Phone.isCarrierLockDataRadioTech, first setDataEnabled(false), then setDataEnabled(true).
1738430214.184 radio 3471 3471 D TelephonyManager: setDataEnabled: enabled=false
1738430214.187 radio 3471 3471 D TelephonyManager: setDataEnabled: enabled=true
1738430214.192 1000 623 623 E SELinux : avc: denied { find } for pid=24997 uid=10173 name=tethering scontext=u:r:permissioncontroller_app:s0:c173,c256,c512,c768 tcontext=u:object_r:tethering_service:s0 tclass=service_manager permissive=0
1738430214.197 1002 32757 567 D a2dp_codec: A2DP_GetCodecType:
1738430214.197 1002 32757 567 I chatty : uid=1002(bluetooth) btu message loo identical 1 line
1738430214.197 1002 32757 567 D a2dp_codec: A2DP_GetCodecType:
1738430214.203 radio 3471 3661 D QcDataStatusNotification Service: MultiSim onChange(): subId = 1
1738430214.203 radio 3471 3661 D QcDataStatusNotification Service: onChange():uri=content://settings/global/mobile_data1 authority=settings path=/global/mobile_data1 segments=[global, mobile_data1] uriLastSegment=mobile_data
1738430214.206 radio 3471 3661 D QcDataStatusNotification Service: handleMessage: Data Enable changed to 1 on slot = 0
...

Does anyone have any suggestions about what might be going on in relation to the '... radio ... zsj Phone.iCarrierLockDataRadioTech ... setDataEnabled(true)', how to interpret it, or where I could find more help and info about what it might be telling me?
From the log, I can definitely see you have those evenwell apps installed, even though you said you didn't. I can see these evenwell apps in your log: PermissionController, DataUsageController, TelephonyManager (not sure if this one is evenwell).
I think DataUsageController is responsible for this. Disable it from settings > apps & notifications, since you can't find it through pm list packages. Then, give feedback if it still happens.
 
The only mention of 'permissioncontroller' in the pm list packages output is -
package:com.google.android.overlay.modules.permissioncontroller
... Doesn't this imply it's a fairly standard package/component of android?

DataUsageController is mentioned elsewhere and seems to be a standard android component: https://android.stackexchange.com/q...ponsible-for-capturing-mobile-wifi-data-usage

The same goes for TelephonyManager: https://www.w3schools.blog/telephonymanager-android

Also, none of these appear in the full listing of apps under settings > apps & notifications. Neither are do they appear in the 'list packages' adb listings, except for permissioncontroller, which appears as shown above.

What is it about these 3 systems/packages that makes you think their origin is evenwell and so should be disabled? I don't have any reason to doubt you but it would be nice to understand what is it about these 3 that raises a red flag for you.

There is mention that nokia have, for a while now, ended their use of evenwell apps (https://dontkillmyapp.com/nokia), which tallies with the fact that I have nothing in my 'list packages' that matches anything from -

The very first log entry I included above would seem to be the closest to the problem, which is -

738430214.184 radio 3471 3471 D zsj : Phone.isCarrierLockDataRadioTech, first setDataEnabled(false), then setDataEnabled(true).

As far as I can tell, this is a 'radio and phone-related information' log, at (D)ebug level, but ... is it from some system or package called 'zsj'? I can't find any mention of 'zsj' or the 'isCarrierLockDataRadioTech' function/event anywhere. Are the pair of identical numbers a process ID from which the log entry originates and therefore something that I might be able to gather a little more information?
 
From what I can tell from this earliest suspect log entry that pretty much says it's turning on mobile data -

1738430214.184 radio 3471 3471 D zsj : Phone.isCarrierLockDataRadioTech, first setDataEnabled(false), then setDataEnabled(true).

I think the two numbers (3471 3471) are probably a process ID (PID) and by executing -

ps -A

I get -

USER PID PPID VSZ RSS WCHAN ADDR S NAME
...
radio 3471 920 16150904 63104 0 0 S com.android.phone
...

which looks to me like it's this 'com.android.phone' process that is quietly turning on my mobile data.
However, does anyone know where I might be best looking for help from someone who knows more about this 'com.android.phone' package and
 
From what I can tell from this earliest suspect log entry that pretty much says it's turning on mobile data -

1738430214.184 radio 3471 3471 D zsj : Phone.isCarrierLockDataRadioTech, first setDataEnabled(false), then setDataEnabled(true).

I think the two numbers (3471 3471) are probably a process ID (PID) and by executing -

ps -A

I get -

USER PID PPID VSZ RSS WCHAN ADDR S NAME
...
radio 3471 920 16150904 63104 0 0 S com.android.phone
...

which looks to me like it's this 'com.android.phone' process that is quietly turning on my mobile data.
However, does anyone know where I might be best looking for help from someone who knows more about the internals of this 'com.android.phone' package and the Phone.isCarrierLockDataRadioTech log message that comes from this process?
 

Members online

Forum statistics

Threads
952,051
Messages
6,955,112
Members
3,162,541
Latest member
fariba