I'm running the factory Marshmallow image on my N5(on tmobile) clean installed, and i noticed that MMS messages wont download to my phone. They fail after a while. Anyone else experiencing this? Any ideas on things to troubleshoot? I already checked APN...looks ok.
Nevermind. Uninstalled pushbullet, rebooted, and now its working. Waiting for pushbullet update...
I had the same problem. I was able to clear the app data for Pushbullet and then my MMS started working again
I've had the same issue all day and didn't even think of Pushbullet.
I went into Settings > Apps > App Permissions (Click the gear icon) > SMS and I disabled Pushbullet there.
Works like a charm now.
I don't use Pushbullet for SMS often... But I did enjoy having that feature from time to time. Hopefully an update will be released soon.
Looks like its any app that accesses the SMS database not just PushBullet. I had an issue with SMS Backup+ as well. I posted on the Google forums but here's all I could get from the logcat that seems related:
10-16 01:23:16.608 785 1624 D MmsServiceBroker: sendMessage() by com.google.android.talk
10-16 01:23:16.621 785 1624 W MmsServiceBroker: MmsService not connected. Try connecting...
10-16 01:23:16.621 785 785 I MmsServiceBroker: Connecting to MmsService
10-16 01:23:16.628 785 785 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1285 com.android.server.MmsServiceBroker.tryConnecting:240 com.android.server.MmsServiceBroker.-wrap3:-1 com.android.server.MmsServiceBroker$1.handleMessage:82 android.os.Handler.dispatchMessage:102
10-16 01:23:16.645 1612 1612 W System : ClassLoader referenced unknown path: /system/priv-app/MmsService/lib/arm
10-16 01:23:16.654 1612 1612 D MmsService: onCreate
10-16 01:23:16.658 785 785 I MmsServiceBroker: MmsService connected
10-16 01:23:16.660 1612 1635 D MmsService: sendMessage
10-16 01:23:16.665 1612 1635 D MmsService: Current running=0, current subId=-1, pending=0
10-16 01:23:16.665 1612 1635 D MmsService: Add request to running queue for subId 1
10-16 01:23:16.668 1612 8898 I MmsService: MmsConfigManager loads in background mcc/mnc: 310/410
10-16 01:23:16.670 1612 8899 I MmsService: [[email protected]] Executing...
10-16 01:23:16.670 1612 8899 I MmsService: mms config for sub 1: null
10-16 01:23:16.670 1612 8899 E MmsService: [[email protected]] mms config is not loaded yet
10-16 01:23:16.675 1612 8899 D MmsService: getAutoPersisting
10-16 01:23:16.692 1612 8899 D MmsService: Schedule requests pending on SIM
10-16 01:23:16.693 5228 7527 E Babel_SMS: MmsSender: failure in sending mms. requestId=1 resultCode=7 httpStatusCode=0
10-16 01:23:16.693 5228 8884 E Babel_SMS: MmsSender: permanent failure with status code 7
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: SendMmsRequest: failed to send message dpt
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: dpt
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at dpy.a(SourceFile:2202)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at dpy.a(SourceFile:93)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at dqb.a(SourceFile:150)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at dqb.a(SourceFile:84)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at dgr.a(SourceFile:93)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at cbv.b(SourceFile:106)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at cbs.d(SourceFile:335)
10-16 01:23:16.694 5228 8884 E Babel_SendMmsNetworkRequest: at cbt.run(SourceFile:81)
Click to expand...
Click to collapse
Interesting. I haven't setup SMS Backup since I flashed 6.0.
Hopefully a fix is on it's way.
Related
Previously, on regular 4.4, I was able to keep Wi-Fi on and have it set to always keep Wi-Fi on during sleep. My phone got great battery life and usually slept just fine when the screen was off.
Since updating to 4.4.1 and now 4.4.2, both my phone and my wife's phone will not sleep if Wi-Fi is connected. I am getting a large percentage of bam_dmux_wakelock in conjunction with a hot phone.
(Both of these threads weren't any help http://forum.xda-developers.com/showthread.php?t=2523162 and http://forum.xda-developers.com/showthread.php?t=1811365 in this situation).
Because my wife's phone is having the issue and she never installs apps, I can rule out any new app causing the problem.
I looked into the logcat and it appears that, with Wi-Fi on and connected, the phone will constantly switch between Wi-Fi and a mobile connection.
Here are some relevant logcat snippets:
Code:
D/ConnectivityService( 770): ConnectivityChange for WIFI: CONNECTED/CONNECTED
D/ConnectivityService( 770): Policy requires mobile teardown
E/ConnectivityService( 770): Unexpected mtu value: [email protected]
D/MobileDataStateTracker( 770): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
D/MobileDataStateTracker( 770): default: Received state=DISCONNECTED, old=CONNECTED, reason=dataDisabled
D/MobileDataStateTracker( 770): default: setDetailed state, old =CONNECTED and new state=DISCONNECTED
D/ConnectivityService( 770): ConnectivityChange for mobile: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 770): Attempting to switch to WIFI
D/ConnectivityService( 770): Attempting to switch to BLUETOOTH_TETHER
Along with:
Code:
D/ConnectivityService( 770): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 770): tryFailover: set mActiveDefaultNetwork=-1, prevNetType=1
D/ConnectivityService( 770): Attempting to switch to mobile
D/ConnectivityService( 770): Attempting to switch to BLUETOOTH_TETHER
D/MobileDataStateTracker( 770): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
D/MobileDataStateTracker( 770): default: Received state=CONNECTING, old=DISCONNECTED, reason=dataEnabled
For the time being I cannot have Wi-Fi on or else my phone will get hot and drain the battery in a couple of hours.
Is anyone else experience this? This only started happening with the 4.4.1 and now 4.4.2 updates.
Looks like somehow my router started sending incorrect MTU values. I changed it from "auto" to 1500 and now everything is as it was before.
The following logcat tipped me off:
Code:
E/ConnectivityService( 770): Unexpected mtu value: [email protected]
ConnectivityService.java has the message defined here:
Code:
if (mtu < 68 || mtu > 10000) {
loge("Unexpected mtu value: " + nt);
return;
}
No issue here!
Hi,
I'm noticing every few hours (quite random) mobile data gets disconnected (although the cell reception is fine, 5 bars, just the data icon (H+) disappears for a few seconds.
Logcat says:
Code:
02-14 09:47:00.006 D/MobileDataStateTracker(19308): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-14 09:47:00.016 D/MinimalTextWidgetBase(19983): Pushing update request. Reason: Tick
02-14 09:47:00.016 D/MobileDataStateTracker(19308): default: Received state=CONNECTING, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.016 D/MobileDataStateTracker(19308): default: setDetailed state, old =DISCONNECTED and new state=CONNECTING
02-14 09:47:00.026 D/MinimalTextUpdateService(19983): onStart:update
02-14 09:47:00.026 D/MobileDataStateTracker(19308): fota: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=fota
02-14 09:47:00.026 D/MobileDataStateTracker(19308): fota: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.036 D/MobileDataStateTracker(19308): dun: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=dun
02-14 09:47:00.036 D/MobileDataStateTracker(19308): dun: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.036 D/MobileDataStateTracker(19308): ia: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=ia
02-14 09:47:00.036 D/MobileDataStateTracker(19308): ia: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.036 D/MobileDataStateTracker(19308): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
02-14 09:47:00.036 D/MobileDataStateTracker(19308): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.046 D/MobileDataStateTracker(19308): hipri: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=hipri
02-14 09:47:00.046 D/MobileDataStateTracker(19308): hipri: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.046 D/MobileDataStateTracker(19308): ims: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=ims
02-14 09:47:00.056 D/MobileDataStateTracker(19308): ims: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.056 D/MobileDataStateTracker(19308): mms: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=mms
02-14 09:47:00.056 D/MobileDataStateTracker(19308): mms: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.056 D/MobileDataStateTracker(19308): cbs: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=cbs
02-14 09:47:00.056 D/MobileDataStateTracker(19308): cbs: Received state=DISCONNECTED, old=DISCONNECTED, reason=pdpReset
02-14 09:47:00.096 D/MinimalTextUpdateService(19983): The screen is currently off. Skipping update.
02-14 09:47:02.256 D/MobileDataStateTracker(19308): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-14 09:47:02.256 D/MobileDataStateTracker(19308): default: Received state=CONNECTING, old=CONNECTING, reason=(unspecified)
02-14 09:47:02.846 D/dalvikvm(19678): GC_CONCURRENT freed 394K, 8% free 12936K/13968K, paused 2ms+1ms, total 13ms
02-14 09:47:02.856 D/MobileDataStateTracker(19308): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-14 09:47:02.856 D/MobileDataStateTracker(19308): default: Received state=CONNECTED, old=CONNECTING, reason=connected
02-14 09:47:02.856 D/MobileDataStateTracker(19308): default: setDetailed state, old =CONNECTING and new state=CONNECTED
02-14 09:47:02.856 D/ConnectivityService(19308): ConnectivityChange for mobile: CONNECTED/CONNECTED
02-14 09:47:02.856 D/ConnectivityService(19308): ConnectivityChange checkMobileProvisioning for TYPE_MOBILE or ProvisioningNetwork
02-14 09:47:02.856 D/ConnectivityService(19308): checkMobileProvisioning: E suggestedTimeOutMs=60000
02-14 09:47:02.856 D/ConnectivityService(19308): setProvNotificationVisible: E visible=false networkType=5 extraInfo=null url=null
02-14 09:47:02.856 D/ConnectivityService(19308): checkMobileProvisioning: params={ url=http://clients3.google.com/generate_204 mTimeOutMs=60000 [email protected]}
02-14 09:47:02.856 D/ConnectivityService(19308): checkMobileProvisioning: X
I have the latest radio from 4.4.2 and running OmniRom with the stock kernel (have tried franco and get the same behaviour). Have tried a different sim from a different carrier and still happens.
Any idea what can be the problem?
Who's your service provider?
Sent from my Nexus 5 using Tapatalk
nemofbaby2010 said:
Who's your service provider?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Have tried both Vodafone and Telecom NZ, same thing happens.
The Vodafone sim doesn't have LTE provisioned so it's only using HSUPA+, the Telecom SIM has LTE enabled and working fine but problem persists between them.
Is your APN configured correctly?
Sent from my Nexus 5 using Tapatalk
nemofbaby2010 said:
Is your APN configured correctly?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It is. Everything works as expected and I rarely notice this happening but I see it in the openvpn logs (as the openvpn client reconnects on android).
Sometimes it happens when I have the screen on and doing some browsing, other times it happens with the screen off (I notice in the openvpn server logs).
Could it be a selinux issue?
Under device info where it says SE for Android
I think enforcing is bad
I'm fuzzy on the subject
Sent from my Jedi MasterX Note 2
I found the problem but not a solution.
This only happens when I'm connecting to an OpenVPN server through UDP.
If the server is using TCP, everything is fine.
Once it goes to UDP, it causes data drops.
As strange as that may be..
Very common issue, its software related towards the modem/ RIL
https://code.google.com/p/android/issues/detail?id=63524
https://productforums.google.com/fo...e=footer#!topic/nexus/hTUtTzQbEKc[1-25-false]
The wifi on my Moto G (1st Gen/XT1032) won't turn on - on stock 5.0 and 5.1, the toggle slides across and immediately slides itself back. On Cyanogenmod, the toggle is greyed out altogether.
Got a log via ADB, seems to say it can't load the wifi driver at /persist/WCNSS_qcom_wlan_factory_nv.bin.
Here's the relevant section from the log. Shows what happens when I try to toggle wifi on:
Code:
09-01 01:07:57.423 D/WifiService( 916): setWifiEnabled: true pid=3928, uid=1000
09-01 01:07:57.423 E/WifiService( 916): Invoking mWifiStateMachine.setWifiEnabled
09-01 01:07:57.434 W/Settings( 1526): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
09-01 01:07:57.435 W/ContextImpl( 1526): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1455 android.content.ContextWrapper.sendBroadcast:376 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:401 android.database.ContentObserver.onChange:130 android.database.ContentObserver.onChange:145
09-01 01:07:57.440 W/Settings( 1526): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
09-01 01:07:57.440 W/ContextImpl( 1526): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1455 android.content.ContextWrapper.sendBroadcast:376 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:401 android.database.ContentObserver.onChange:130 android.database.ContentObserver.onChange:145
09-01 01:07:57.445 E/WifiStateMachine( 916): setting operational mode to 1
09-01 01:07:57.598 D/Checkin ( 3437): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
09-01 01:07:57.647 W/ueventd ( 6429): type=1400 audit(0.0:5): avc: denied { read } for uid=0 name="WCNSS_qcom_wlan_factory_nv.bin" dev="mmcblk0p29" ino=12 scontext=u:r:ueventd:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
09-01 01:07:57.686 D/Checkin ( 3437): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
09-01 01:07:57.704 E/WifiStateMachine( 916): Failed to load driver
09-01 01:07:57.704 E/WifiStateMachine( 916): setWifiState: unknown state
09-01 01:07:57.706 I/SBar.MotoNetworkCtrlr( 1336): onReceive: WifiManager.WIFI_STATE_CHANGED_ACTION Received
09-01 01:07:57.706 I/SBar.MotoNetworkCtrlr( 1336): updateTelephonySignalStrength[0]: No service
09-01 01:07:57.709 E/WifiStateMachine( 916): setSuspendOptimizations: 2 true
09-01 01:07:57.709 E/WifiStateMachine( 916): mSuspendOptNeedsDisabled 4
09-01 01:07:57.714 W/Settings( 1526): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
09-01 01:07:57.715 W/ContextImpl( 1526): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1455 android.content.ContextWrapper.sendBroadcast:376 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:401 android.database.ContentObserver.onChange:130 android.database.ContentObserver.onChange:145
09-01 01:07:57.716 W/Settings( 1526): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
09-01 01:07:57.716 W/ContextImpl( 1526): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1455 android.content.ContextWrapper.sendBroadcast:376 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:401 android.database.ContentObserver.onChange:130 android.database.ContentObserver.onChange:145
09-01 01:07:57.727 D/Index ( 3928): Deleting data for locale 'en_GB' took 3 millis
09-01 01:07:57.732 D/Index ( 3928): Indexing locale 'en_GB' took 5 millis
09-01 01:07:57.867 D/Checkin ( 3437): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
09-01 01:07:57.957 D/Checkin ( 3437): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
I think this is the critical item, seems to say it can't read the file?
Code:
09-01 01:07:57.647 W/ueventd ( 6429): type=1400 audit(0.0:5): avc: denied { read } for uid=0 name="WCNSS_qcom_wlan_factory_nv.bin" dev="mmcblk0p29" ino=12 scontext=u:r:ueventd:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
I've tried replacing the file (in case it was corrupted) and also setting permissions to 777. Neither change helps!
I don't know what else might cause it to be unable to load the wifi driver. Can anyone who know more than me offer any suggestions?
Just in case it could be useful to know, I'm running this, specifically the StockOnlyDebloated one (M4B30X as of writing), with SuperSU 2.78 systemless root.
The problem I'm having is that encryption refuses to ever start if I try to activate it. Everything shuts down, the green android thing is displayed, then the screen goes blank and it stays that way. My logcat in the moments preceding the supposed beginning of the encryption process reads as follows:
Code:
11-11 23:51:20.435 989 2940 D CryptdConnector: SND -> {7 cryptfs enablecrypto inplace password [scrubbed]}
11-11 23:51:20.442 149 159 D Cryptfs : Just asked init to shut down class main
11-11 23:51:20.442 989 1289 D VoldConnector: RCV <- {651 emulated 5}
11-11 23:51:20.445 289 289 I ServiceManager: service 'android.service.gatekeeper.IGateKeeperService' died
11-11 23:51:20.447 989 1288 D MountService: Volume emulated broadcasting ejecting to UserHandle{0}
11-11 23:51:20.448 1402 1402 D MtpService: onStorageStateChanged /storage/emulated/0 mounted -> ejecting
11-11 23:51:20.448 1402 1402 E MtpService: Missing MtpStorage for /storage/emulated/0
11-11 23:51:20.456 989 1301 E NetdConnector: got -1 reading with start = 0
11-11 23:51:20.456 989 1301 E NetdConnector: closing stream for netd
11-11 23:51:20.456 989 1301 E NetdConnector: Communications error: java.io.IOException: Connection refused
11-11 23:51:20.457 989 1301 E NetdConnector: Error in NativeDaemonConnector: java.io.IOException: Connection refused
11-11 23:51:20.457 989 1320 E mDnsConnector: got -1 reading with start = 0
11-11 23:51:20.457 989 1320 E mDnsConnector: closing stream for mdns
11-11 23:51:20.458 989 1320 E mDnsConnector: Communications error: java.io.IOException: Connection refused
11-11 23:51:20.458 989 1320 E mDnsConnector: Error in NativeDaemonConnector: java.io.IOException: Connection refused
11-11 23:51:20.556 159 159 W vold : type=1400 audit(0.0:794): avc: denied { read } for name="fd" dev="proc" ino=7289 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
11-11 23:51:20.556 159 159 W vold : type=1400 audit(0.0:795): avc: denied { getattr } for path="/proc/148/cwd" dev="proc" ino=59003 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:20.556 159 159 W vold : type=1400 audit(0.0:796): avc: denied { getattr } for path="/proc/148/root" dev="proc" ino=59004 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:20.566 159 159 W vold : type=1400 audit(0.0:797): avc: denied { getattr } for path="/proc/148/exe" dev="proc" ino=59005 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:20.460 989 1035 I ActivityManager: Start proc 7171:com.android.externalstorage/u0a8 for broadcast com.android.externalstorage/.MountReceiver
11-11 23:51:20.668 289 289 I ServiceManager: service 'user.xposed.app' died
11-11 23:51:20.668 289 289 I ServiceManager: service 'user.xposed.system' died
11-11 23:51:20.669 289 289 I ServiceManager: service 'android.security.keystore' died
11-11 23:51:20.711 289 289 I ServiceManager: service 'nfc' died
11-11 23:51:20.741 288 288 I lowmemorykiller: ActivityManager disconnected
11-11 23:51:20.741 288 288 I lowmemorykiller: Closing Activity Manager data connection
11-11 23:51:20.860 149 158 E FrameworkListener: read() failed (Connection reset by peer)
11-11 23:51:20.931 289 289 I ServiceManager: service 'telecom' died
11-11 23:51:20.931 289 289 I ServiceManager: service 'user' died
11-11 23:51:20.931 289 289 I ServiceManager: service 'procstats' died
11-11 23:51:20.931 289 289 I ServiceManager: service 'meminfo' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'gfxinfo' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'dbinfo' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'cpuinfo' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'permission' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'processinfo' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'sensorservice' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'battery' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'usagestats' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'webviewupdate' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'scheduling_policy' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'telephony.registry' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'media.camera.proxy' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'account' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'content' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'vibrator' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'consumer_ir' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'alarm' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'window' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'input' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'batterystats' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'appops' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'power' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'display' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'bluetooth_manager' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'input_method' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'accessibility' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'mount' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'uimode' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'lock_settings' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'deviceidle' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'device_policy' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'statusbar' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'clipboard' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'network_management' died
11-11 23:51:20.932 289 289 I ServiceManager: service 'textservices' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'network_score' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'netstats' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'netpolicy' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'package' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'activity' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'wifip2p' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'wifi' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'wifiscanner' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'rttmanager' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'ethernet' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'connectivity' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'servicediscovery' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'updatelock' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'notification' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'devicestoragemonitor' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'location' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'country_detector' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'search' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'dropbox' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'wallpaper' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'audio' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'DockObserver' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'midi' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'usb' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'serial' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'jobscheduler' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'backup' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'appwidget' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'voiceinteraction' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'diskstats' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'samplingprofiler' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'commontime_management' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'dreams' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'assetatlas' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'graphicsstats' died
11-11 23:51:20.933 289 289 I ServiceManager: service 'print' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'restrictions' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'media_session' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'media_router' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'fingerprint' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'trust' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'launcherapps' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'media_projection' died
11-11 23:51:20.934 289 289 I ServiceManager: service 'imms' died
11-11 23:51:20.935 290 290 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb6b24000
11-11 23:51:20.935 290 290 D SurfaceFlinger: Screen type=0 is already mode=2
11-11 23:51:20.941 289 289 I ServiceManager: service 'simphonebook' died
11-11 23:51:20.941 289 289 I ServiceManager: service 'iphonesubinfo' died
11-11 23:51:20.941 289 289 I ServiceManager: service 'isms' died
11-11 23:51:20.941 289 289 I ServiceManager: service 'phone' died
11-11 23:51:20.942 289 289 I ServiceManager: service 'carrier_config' died
11-11 23:51:20.942 289 289 I ServiceManager: service 'sip' died
11-11 23:51:20.942 289 289 I ServiceManager: service 'isub' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.sound_trigger_hw' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.radio' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.audio_flinger' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.player' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.resource_manager' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.camera' died
11-11 23:51:21.004 289 289 I ServiceManager: service 'media.audio_policy' died
11-11 23:51:21.005 289 289 I ServiceManager: service 'drm.drmManager' died
11-11 23:51:21.051 7186 7186 I BootAnimation: boot animation disabled
11-11 23:51:40.717 159 159 W vold : type=1400 audit(0.0:798): avc: denied { read } for name="fd" dev="proc" ino=7289 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
11-11 23:51:40.717 159 159 W vold : type=1400 audit(0.0:799): avc: denied { getattr } for path="/proc/148/cwd" dev="proc" ino=59003 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:40.717 159 159 W vold : type=1400 audit(0.0:800): avc: denied { getattr } for path="/proc/148/root" dev="proc" ino=59004 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:40.717 159 159 W vold : type=1400 audit(0.0:801): avc: denied { getattr } for path="/proc/148/exe" dev="proc" ino=59005 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:40.747 149 159 E ProcessKiller: Process daemonsu:0:650 (3619) has open file /data/data/eu.chainfire.supersu/logs/L14789021760000.GRANTED.ADB shell
11-11 23:51:40.750 149 159 E Cryptfs : unmounting /data failed: Device or resource busy
11-11 23:51:40.757 159 159 W vold : type=1400 audit(0.0:802): avc: denied { read } for name="fd" dev="proc" ino=7289 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
11-11 23:51:40.757 159 159 W vold : type=1400 audit(0.0:803): avc: denied { getattr } for path="/proc/148/cwd" dev="proc" ino=59003 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:40.757 159 159 W vold : type=1400 audit(0.0:804): avc: denied { getattr } for path="/proc/148/root" dev="proc" ino=59004 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:40.757 159 159 W vold : type=1400 audit(0.0:805): avc: denied { getattr } for path="/proc/148/exe" dev="proc" ino=59005 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:51:40.783 149 159 E ProcessKiller: Process daemonsu:0:650 (3619) has open file /data/data/eu.chainfire.supersu/logs/L14789021760000.GRANTED.ADB shell
11-11 23:51:40.783 149 159 W ProcessKiller: Sending Killed to process 3619
11-11 23:51:40.864 149 159 D Cryptfs : Just asked init to shut down class main
11-11 23:51:40.864 149 159 W vold : emulated unmount requires state mounted
11-11 23:52:00.876 159 159 W vold : type=1400 audit(0.0:806): avc: denied { read } for name="fd" dev="proc" ino=7289 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
11-11 23:52:00.876 159 159 W vold : type=1400 audit(0.0:807): avc: denied { getattr } for path="/proc/148/cwd" dev="proc" ino=59003 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:52:00.876 159 159 W vold : type=1400 audit(0.0:808): avc: denied { getattr } for path="/proc/148/root" dev="proc" ino=59004 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:52:00.876 159 159 W vold : type=1400 audit(0.0:809): avc: denied { getattr } for path="/proc/148/exe" dev="proc" ino=59005 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
11-11 23:52:00.906 149 159 E Cryptfs : unmounting /data failed: Device or resource busy
11-11 23:52:00.906 149 159 W SocketClient: write error (Broken pipe)
11-11 23:52:00.906 149 159 W SocketClient: Unable to send msg '200 7 -1'
As you can see, the encryption begins, everything shuts down nicely, then /data fails to dismount because something in it is still in use and everything goes dead silent (it's been more than half an hour and logcat still gives no signs of activity). If I force a reboot, everything works fine and dandy as if the encryption never occured, because it didn't.
I've done the searching, and the closest thing to this issue I've found is this thread, but there's no solution there, only the exact same problem.
I strongly suspect that systemless root is the cause of this, because after the failed /data dismount attempt, /su shows up as still mounted, /su is the mount point of /data/su.img, and also gives a "device busy" error if I try to dismount it manually, probably because of the running sukernel and daemonsu processes. I could kill those, but something about them (like the fact that there's one named daemonsu:mount:master) makes me feel like that's not a good idea at all, so I haven't tried yet. Disabling root in SuperSU changes nothing.
Any clues on how to fix or at least work around this?
SuicideFlasher said:
Just in case it could be useful to know, I'm running this, specifically the StockOnlyDebloated one (M4B30X as of writing), with SuperSU 2.78 systemless root.
The problem I'm having is that encryption refuses to ever start if I try to activate it. Everything shuts down, the green android thing is displayed, then the screen goes blank and it stays that way. My logcat in the moments preceding the supposed beginning of the encryption process reads as follows:
Code:
8< snip >8
As you can see, the encryption begins, everything shuts down nicely, then /data fails to dismount because something in it is still in use and everything goes dead silent (it's been more than half an hour and logcat still gives no signs of activity). If I force a reboot, everything works fine and dandy as if the encryption never occured, because it didn't.
I've done the searching, and the closest thing to this issue I've found is this thread, but there's no solution there, only the exact same problem.
I strongly suspect that systemless root is the cause of this, because after the failed /data dismount attempt, /su shows up as still mounted, /su is the mount point of /data/su.img, and also gives a "device busy" error if I try to dismount it manually, probably because of the running sukernel and daemonsu processes. I could kill those, but something about them (like the fact that there's one named daemonsu:mount:master) makes me feel like that's not a good idea at all, so I haven't tried yet. Disabling root in SuperSU changes nothing.
Any clues on how to fix or at least work around this?
Click to expand...
Click to collapse
For as long as I remember, I never was able to do the initial encryption on Marshmallow with systemless SuperSU installed.
As you found out, /data cannot be unmounted because /data/su.img is still mounted on /su.
I was always able to workaround that problem by:
booting into twrp
making a full backup (with system, boot and data)
reinstalling my rom (stock or custom), wiping data but not sdcard
booting into the rom, encrypt
boot back into twrp and restore
Alternately, you can try uninstalling SuperSU, encrypt and reinstall SuperSU.
That would work, but I found my own workaround in the meantime.
Reboot into recovery
Rename /data/su.img to anything else
Reboot into system
Rename it back to su.img (this can be done at any point from now on)
Encrypt
???
Profit!
One boot with su.img unavailable didn't break anything, to my knowledge.
UPDATE: If you're using the original kernel that came with your rom, you can just fastboot boot the original boot.img from the package. This will give you a one-time unrooted boot with a single command.
Hi, thanks for sharinv this hints!
I'm about to try this solution with Samsung S7... I'm wondering about step 4. I can't find this file after reboot into system. I guess, it's because /data is not mounted. I also tried to mount it manually (it should be /dev/sda15 according to what I saw in TWRP). I guess, I won't be even able to mount, since root is deactivated, right?
Any ideas, how I can access this file in order to rename?
As far as I understand, I won't be able to access this file from TWRP after encryption (since TWRP doesn't support Samsung encryption).
bruzzy said:
Hi, thanks for sharinv this hints!
I'm about to try this solution with Samsung S7... I'm wondering about step 4. I can't find this file after reboot into system. I guess, it's because /data is not mounted. I also tried to mount it manually (it should be /dev/sda15 according to what I saw in TWRP). I guess, I won't be even able to mount, since root is deactivated, right?
Any ideas, how I can access this file in order to rename?
As far as I understand, I won't be able to access this file from TWRP after encryption (since TWRP doesn't support Samsung encryption).
Click to expand...
Click to collapse
Did you succeeded? Did you encrypt the data partition and survive?
(New forum member here, hope I chose the right topic. Cross-post from https://android.stackexchange.com/q/249383/37933, hope that's OK. Thanks!)
Every since my Nokia 5.3 was upgraded to Andoid 12 recently, the battery suffers from processes com.android.phone and qcrild using the CPU a fair amount. It is not completely reproducible, but it happens especially when the the phone is locked, or at least the screen is off.
I observe that increased CPU usage via adb shell top -u radio.
At that same time adb shell dumpsys phone shows a lot of the following:
Code:
❯ adb shell dumpsys phone
------- PhoneGlobals -------
mPrevRoamingNotification=0
mDefaultDataSubId=1
mDataRoamingNotifLog:
isSmsCapable=true
2022-11-23T13:56:23.510818 - dataAllowed=true, reasons=Data allowed reason: NORMAL
2022-11-23T13:56:23.512116 - dataAllowed=true, reasons=Data allowed reason: NORMAL
[snip rest of the output]
And that seems to always immediately follow these adb shell logcat -d phone warnings about ...without a qualified user and Permission Denial to read the phone state:
Code:
11-23 13:56:23.460 1681 3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1206 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2880 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 android.os.Binder.execTransactInternal:1184
11-23 13:56:23.461 1681 3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2884 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455
11-23 13:56:23.462 1681 3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2891 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455
11-23 13:56:23.463 1681 2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)
11-23 13:56:23.463 1681 2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid 1001)
11-23 13:56:23.464 1681 3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2895 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455
11-23 13:56:23.465 1681 2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)
And that results in a lot of logging that seems to be about refreshing the data about my mobile carrier (onRefreshCarrierInfo()), which may be where the CPU time is actually spent (following log capture is from a later occurrence):
Code:
11-23 14:18:08.592 2936 2936 D ServiceStateProvider: subId=1
11-23 14:18:08.592 2462 2640 I CustomizedNetworkIcon: getConfigValueByKey: oem_key_rat_name_of_4g_int=0
11-23 14:18:08.595 2462 2640 I CustomizedNetworkIcon: getConfigValueByKey: oem_display_lte_icon_int=1
11-23 14:18:08.597 2936 2936 I Telephony: TelecomAccountRegistry: onSubscriptionsChanged - reregister accounts
11-23 14:18:08.598 1676 2040 D CompatibilityInfo: mCompatibilityFlags - 0
11-23 14:18:08.598 2936 2936 D Telephony: isEmergencyPreferredAccount: subId=1, activeData=1
11-23 14:18:08.598 1676 2040 D CompatibilityInfo: applicationDensity - 280
11-23 14:18:08.598 2936 2936 D Telephony: isEmergencyPreferredAccount: Device does not require preference.
11-23 14:18:08.598 1676 2040 D CompatibilityInfo: applicationScale - 1.0
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: onReceive Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 cmp=com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver (has extras) }
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: onServiceStateChanged, ss: 0
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: networkOperator: 20416
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: update supported roaming operator as
11-23 14:18:08.601 2936 2936 I Telephony: isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
11-23 14:18:08.601 2936 2936 I Telephony: isRttSupported: false
11-23 14:18:08.601 2936 2936 I Telephony: isUserRttSettingOn: false
11-23 14:18:08.601 2936 2936 I Telephony: alwaysAllowWhileRoaming: false
11-23 14:18:08.601 2936 2936 I Telephony: isRoaming: false
11-23 14:18:08.601 2936 2936 I Telephony: isOnWfc: false
11-23 14:18:08.607 2462 2640 E CustomizedImsIcon: customizedVoLTEandVoWiFiIcon:
11-23 14:18:08.608 2462 4440 I CustomizedImsIcon: [0] customizedImsIcon:++
11-23 14:18:08.608 2462 4440 D CustomizedImsIcon: isAirplaneModeOn: false
11-23 14:18:08.608 2462 4440 D CustomizedImsIcon: customizedImsIcon:clear all vowifi icon which is added with TAG when airplane is off
11-23 14:18:08.608 2462 4440 I CustomizedImsIcon: [0] isOperaterCustomized:mccmnc=20416
11-23 14:18:08.609 2462 4440 I CustomizedImsIcon: [0] isOperaterClaroCustomized:mccmnc=20416
11-23 14:18:08.609 2462 4440 I CustomizedImsIcon: [0] isCustomizedBySkuId:isCustomized=false
11-23 14:18:08.609 2462 4440 D CustomizedImsIcon: getSimCount: simCount=1
11-23 14:18:08.610 2462 4440 I CustomizedImsIcon: [0] isWifiCallingAvailable: isImsRegistered is false
11-23 14:18:08.610 2462 4440 I CustomizedImsIcon: [0] isShowVoWiFiIcon: isAllowed=false
11-23 14:18:08.612 2462 4440 I CustomizedImsIcon: [0] isAllowShowVoLteIcon:OEM_ALLOW_SHOW_VOLTE_ICON_BOOL=false phoneId=0
11-23 14:18:08.612 2462 4440 I CustomizedImsIcon: [0] isShowVolteIcon: isAllowed=false
11-23 14:18:08.613 2462 4440 I CustomizedImsIcon: [0] customizedImsIcon:--
11-23 14:18:08.615 2936 2936 I Telephony: reRegisterPstnPhoneAccount: subId: 1 - no change
11-23 14:18:08.615 2936 2936 D CallNotifier: updatePhoneStateListeners: update CF notifications.
11-23 14:18:08.616 2936 2936 I NotificationMgr: updateCfi: subId= 1, visible=N
11-23 14:18:08.616 2936 2936 I NotificationMgr: updateMwi(): subId 1 update to false
11-23 14:18:08.618 2462 2462 D KeyguardUpdateMonitor: received broadcast android.intent.action.SERVICE_STATE
11-23 14:18:08.618 2462 2462 V KeyguardUpdateMonitor: action android.intent.action.SERVICE_STATE serviceState={mVoiceRegState=0(IN_SERVICE), mDataRegState=0(IN_SERVICE), mChannelNumber=1656, duplexMode()=1, mCellBandwidths=[], mOperatorAlphaLong=Simpel, mOperatorAlphaShort=Simpel, isManualNetworkSelection=false(automatic), getRilVoiceRadioTechnology=14(LTE), getRilDataRadioTechnology=14(LTE), mCssIndicator=unsupported, mNetworkId=-1, mSystemId=-1, mCdmaRoamingIndicator=-1, mCdmaDefaultRoamingIndicator=-1, mIsEmergencyOnly=false, isUsingCarrierAggregation=false, mArfcnRsrpBoost=0, mNetworkRegistrationInfos=[NetworkRegistrationInfo{ domain=CS transportType=WWAN registrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[VOICE,SMS,VIDEO] cellIdentity=CellIdentityLte:{ mCi=70817281 mPci=66 mTac=527 mEarfcn=1656 mBands=[] mBandwidth=2147483647 mMcc=204 mMnc=16 mAlphaLong=Simpel mAlphaShort=Simpel mAdditionalPlmns={} mCsgInfo=null} voiceSpecificInfo=VoiceSpecificRegistrationInfo { mCssSupported=false mRoamingIndicator=1 mSystemIsInPrl=-1 mDefaultRoamingIndicator=-1} dataSpecificInfo=null nrState=**** rRplmn=20416 isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=PS transportType=WWAN registrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=CellIdentityLte:{ mCi=70817281 mPci=66 mTac=527 mEarfcn=1656 mBands=[] mBandwidth=2147483647 mMcc=204 mMnc=16 mAlphaLong=Simpel mAlphaShort=Simpel mAdditionalPlmns={} mCsgInfo=null} voiceSpecificInfo=null dataSpecificInfo=android.telephony.DataSpecificRegistrationInfo :{ maxDataCalls = 20 isDcNrRestricted = false isNrAvailable = false isEnDcAvailable = false LteVopsSupportInfo : mVopsSupport = 3 mEmcBearerSupport = 2 } nrState=**** rRplmn=20416 isUsingCarrierAggregation=false}], mNrFrequencyRange=0, mOperatorAlphaLongRaw=Simpel, mOperatorAlphaShortRaw=Simpel, mIsDataRoamingFromRegistration=false, mIsIwlanPreferred=false} subId=1
[...snipping a lot more similar logging...]
What could be wrong? Or at least, how can I further debug this?
After more research, my current best quess is that the Qualcomm RIL driver (presumably via qcrild) very often sends a '1002 unsolicited response (voice) network state changed' event: com.android.phone logs
Code:
D RILJ : Unsol response received; Sending ack to ril.cpp [PHONE0]
D RILJ : [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED [PHONE0]
often 10+ times per second.