Database Info

NTFS driver broken by .26?

Copying large file to usb flash formatted in NTFS frozen my infinity - about 50mb copied, than it freezes. Anyone else experiencing this?
Similar problem with sd-card reported in this message.

Try exFAT. Its almost as good as ntfs.

Flexz said:
Copying large file to usb flash formatted in NTFS frozen my infinity - about 50mb copied, than it freezes. Anyone else experiencing this?
Similar problem with sd-card reported in this message.
Click to expand...
Click to collapse
Confirmed this is a bug.
It just freezes.
This only happens on 9.4.5.26.
So it seems that this firmware has issues which is why it was pulled offline.
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
W/wpa_supplicant( 1873): wlan0: Failed to initiate AP scan
Click to expand...
Click to collapse
The random alloc error will cause a major system lock up.
W/Watchdog( 222): *** WATCHDOG KILLING SYSTEM PROCESS: com.android.server.wm.WindowManagerService
I/ServiceManager( 113): service 'entropy' died
I/ServiceManager( 113): service 'netstats' died
I/ServiceManager( 113): service 'battery' died
I/ServiceManager( 113): service 'vibrator' died
I/ServiceManager( 113): service 'asus_dock' died
I/ServiceManager( 113): service 'window' died
I/ServiceManager( 113): service 'usb' died
I/ServiceManager( 113): service 'sensorservice' died
I/ServiceManager( 113): service 'clipboard' died
I/ServiceManager( 113): service 'hardware' died
I/ServiceManager( 113): service 'cpuinfo' died
I/ServiceManager( 113): service 'content' died
I/ServiceManager( 113): service 'alarm' died
I/ServiceManager( 113): service 'power' died
I/ServiceManager( 113): service 'telephony.registry' died
I/ServiceManager( 113): service 'account' died
I/ServiceManager( 113): service 'network_management' died
I/ServiceManager( 113): service 'input_method' died
I/ServiceManager( 113): service 'device_policy' died
I/ServiceManager( 113): service 'package' died
I/ServiceManager( 113): service 'permission' died
I/ServiceManager( 113): service 'activity' died
I/ServiceManager( 113): service 'meminfo' died
I/ServiceManager( 113): service 'gfxinfo' died
I/ServiceManager( 113): service 'usagestats' died
I/ServiceManager( 113): service 'batteryinfo' died
I/ServiceManager( 113): service 'statusbar' died
I/ServiceManager( 113): service 'bluetooth' died
I/ServiceManager( 113): service 'bluetooth_a2dp' died
I/ServiceManager( 113): service 'BtDun' died
I/ServiceManager( 113): service 'textservices' died
I/ServiceManager( 113): service 'connectivity' died
I/ServiceManager( 113): service 'throttle' died
I/ServiceManager( 113): service 'mount' died
I/ServiceManager( 113): service 'netpolicy' died
I/ServiceManager( 113): service 'wifi' died
I/ServiceManager( 113): service 'ethernet' died
I/ServiceManager( 113): service 'uimode' died
I/ServiceManager( 113): service 'wallpaper' died
I/ServiceManager( 113): service 'location' died
I/ServiceManager( 113): service 'devicestoragemonitor' died
I/ServiceManager( 113): service 'country_detector' died
I/ServiceManager( 113): service 'notification' died
I/ServiceManager( 113): service 'search' died
I/ServiceManager( 113): service 'dropbox' died
I/ServiceManager( 113): service 'wifip2p' died
I/ServiceManager( 113): service 'accessibility' died
I/ServiceManager( 113): service 'asus_firmware' died
I/ServiceManager( 113): service 'diskstats' died
I/ServiceManager( 113): service 'samplingprofiler' died
I/ServiceManager( 113): service 'backup' died
I/ServiceManager( 113): service 'appwidget' died
I/ServiceManager( 113): service 'updatelauncher' died
I/ServiceManager( 113): service 'audio' died
W/Sensors ( 788): sensorservice died [0x9657c8]
W/Sensors ( 530): sensorservice died [0x8a5a88]
W/AudioFlinger( 123): power manager service died !!!
I/ActivityThread( 788): Removing dead content provider: settings
I/ActivityThread( 530): Removing dead content provider: settings
I/ActivityThread( 1520): Removing dead content provider: settings
I/ActivityThread( 1638): Removing dead content provider: settings
I/ActivityThread( 543): Removing dead content provider: settings
I/ActivityThread( 543): Removing dead content provider: applock_mode
I/ActivityThread( 1460): Removing dead content provider: settings
I/ActivityThread( 514): Removing dead content provider: settings
I/ActivityThread( 386): Removing dead content provider: settings
I/ActivityThread( 386): Removing dead content provider: applock_mode
I/ActivityThread( 485): Removing dead content provider: settings
I/ActivityThread( 1137): Removing dead content provider: settings
I/ActivityThread( 1299): Removing dead content provider: settings
I/ActivityThread( 927): Removing dead content provider: settings
I/ActivityThread( 1121): Removing dead content provider: settings
I/ActivityThread( 1278): Removing dead content provider: settings
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
E/wpa_supplicant( 1873): wpa_driver_nl80211_driver_cmd: failed to issue private commands
W/wpa_supplicant( 1873): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 1873): wlan0: Failed to initiate AP scan
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
W/wpa_supplicant( 1873): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 1873): wlan0: Failed to initiate AP scan
E/gralloc ( 1638): GetBufferLock timed out for thread 1638 buffer 0x4e usage 0x200 LockState 1
Click to expand...
Click to collapse
Ultimately it will lead to a reboot...
Best to steer away from flashing anything containing firmware 9.4.5.26.... if you are going to use NTFS for storage.

[Q&A] ★☞ [Rom][4.3] AllianceRom - Build 23 THE Most Customisable TW ROM

[Q&A] ★☞ [Rom][4.3] AllianceRom - Build 23 THE Most Customisable TW ROM
Q&A for ★☞ [Rom][4.3] AllianceRom - Build 23 THE Most Customisable TW ROM On ANY Device [04/11/14][Aroma][ML1]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for ★☞ [Rom][4.3] AllianceRom - Build 23 THE Most Customisable TW ROM On ANY Device [04/11/14][Aroma][ML1]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

alliancerom glitch anyone?
I have the Verizon Galaxy S3 i535, & I'm using Saferoot/Safestrap with AllianceRom (Build 22/Base Version AllianceROM_I535VRUCML1/Android 4.3/Kernel 3.0.31). I've been having a problem recently where, if my phone dies, when I charge it & power it back on, I have to do a Safestrap Reboot followed by a System Reboot to get it to boot properly. If I don't do these things, it will boot up for about 2 min, & then just reboot itself without warning over & over again. I was wondering if anyone else has ever experienced anything like this, or knows the cause (whether hardware- or software-related) & permanent solution for it?
I was also wondering if you have to completely reinstall AllianceRom to change the launcher you want to use with it (I currently have Apex Launcher set, but wanted to try out another of AllianceRom's options). If so, what would be the easiest way to do this with Safestrap?
Any help any of the brilliant people on this awesome forum can provide in either case would be MUCH appreciated!

SadPanda284 said:
I have the Verizon Galaxy S3 i535, & I'm using Saferoot/Safestrap with AllianceRom (Build 22/Base Version AllianceROM_I535VRUCML1/Android 4.3/Kernel 3.0.31). I've been having a problem recently where, if my phone dies, when I charge it & power it back on, I have to do a Safestrap Reboot followed by a System Reboot to get it to boot properly. If I don't do these things, it will boot up for about 2 min, & then just reboot itself without warning over & over again. I was wondering if anyone else has ever experienced anything like this, or knows the cause (whether hardware- or software-related) & permanent solution for it?
I was also wondering if you have to completely reinstall AllianceRom to change the launcher you want to use with it (I currently have Apex Launcher set, but wanted to try out another of AllianceRom's options). If so, what would be the easiest way to do this with Safestrap?
Any help any of the brilliant people on this awesome forum can provide in either case would be MUCH appreciated!
Click to expand...
Click to collapse
I don't know about the reboots but if you want to try a different launcher you can just download pretty much any of them through the play store or the Android apps section of the forum.

Samsung Galaxy s3 modem
Hello, I'm trying to flash the alliance Rom for the Verizon galaxy s3, it shows I need to download the modem zip and flash that too, but it appears the link is down. Does anyone have a download they can share? Thanks in advance!
Ethan9987

dpeeps74 said:
I don't know about the reboots but if you want to try a different launcher you can just download pretty much any of them through the play store or the Android apps section of the forum.
Click to expand...
Click to collapse
Well I was thinking maybe the launcher I was using had somehow gotten corrupted, & so I was just going to try a different one. When you initially install AllianceRom it has you select the launcher, features, etc. So I was thinking I may have to go through that process again to get a Fresh install. Then, if the issue didn't reoccur, I would be able to say that the problem likely WAS with the launcher. Just not sure.
To add to my problem, lately it seems like if the phone gets really hot (like if I'm playing certain games for any length of time), it will start giving "... has stopped working" errors like crazy, & then the phone will reboot itself. Again, not sure if this is the launcher or hardware. It kinda seems like hardware, but I was just hoping to find an easier fix than "buy a new phone". Does anyone else have this much trouble with the S3??

Upgrading from Beans 20 to Alliance Rom
Hi all,
I haven't flashed a different ROM in a while, but I was tired of 4.1.2, and wanted to move to the Alliance Rom. I've seen lots of conflicting reports of how to do this. I still have TWRP 2.6, and I'm not sure if that's an issue. I also have the MF1 modem, and it seems that the note is to upgrade to the ML1 modem (However, when I click on the link, I get an error "This Page is Not Available", which is a separate problem).
My experience with flashing has always been:
1. Download latest Rom version
2. Reboot into Recovery
3. Wipe Data/Factory Reset twice
4. Wipe cache and dalvik cache
5. Install Rom
6. Reboot (First Boot may take up to 10 mins)
7. Read through Frequently asked questions
9. Let Phone sit for 5-10 minutes (You need to do this)
10. Reboot again
11 Enjoy
But in this case, it seems I need a new modem (which I want to make sure to install first), need to confirm that there isn't an issue with the file structure, and possibly install a later version of TWRP. Am I overthinking this, or am I on my way to bricking my phone?

Q&A Help?
Does anyone watch the Q&A section of this thread? I've only gotten 1 response to my problem, & very few posts to the Q&A section period. I'm just wondering if anyone really even looks at this section to provide help to us noobs, or if our questions just go out to the void??

modem link not working timeing out
im trying to install this on a friends phone for him...do i need to flash the modem if he is on jellybean allready he is on mf1 not ml1 if this isnt big diffrenece can i jus flash the rom and be done..if not id like to flash the medem file just in case like i didfor another friend but cant get it to download link keeps timeing out a mirrior link would be great ..thank you in advance for this rom and hard work i love this rom and every version of it i recomend it to everyone with samsung phone..he has a samsung galaxy s3 still on jellybean switched networks to strighttalk..now cant accsess his mobile data ..thought maybe flashing a new rom mite fix this as well build num last 3 digets mf1 ....currently on stock rooted rom ..flashed a diff rom diddnt work out tried flashing syenergy rom cause it was jelly bean based and he cant get ota updates no more ..so thought be better to stay with jellybean based rom..im bout to try a kitkat rom in my experiance ive flashed higher firmwares than the phones base firmware and i was fine..is this ok ?..really jus need a mirrior link for your modem file and i can try otherr stuff on my own..but yourresponse would be alot of help

Alliance Rom S3 CDMA Data not responding
Hi,
I have just flashed Alliance Rom 4.3, everything is fine, problem is my CDMA data is not working, its not giving any reponse.restored back my hyperdrive 4.1 with this data is working fine , need help in flashing alliance rom 4.3 with no data issue for cdma evdo....request to help.

Hi..If you want to install Alliance Rom 4.3*, you need to have TWRP 2.7*...dowload it, use Odin to update TWRPthan flash 4.3.
Sent from my SCH-I535 using XDA Free mobile app

I think no one
Sent from my SCH-I535 using XDA Free mobile app

Any way to reset all colors?
Hi,
Some time ago I dabbled a little in customizing the colors and I have managed to make many in-app menus impossible to read. I've tried just about every option I can think of to get the menus back, but to no avail...
My question is this: Is there any way to just reload all the default settings? Preferably just the color settings, but I could live with all settings if need be.
Thanks for your help!
-Nicco
p.s. Love this ROM!

ALLIANCE ROM BUILD23-Samsung GS3 i535, Contact List Crash
Dev,
Firstly...Thank you very much for an outstanding ROM. In my opinion, I believe that this ROM is better that CM, Paranoid, MOAR or the others due to it's extensive customization abilities. After Getting all of my bugs fixed, I do plan to donate. Here is my problem:
I did a factory reset, twice....wiped delvik and cach, twice.....installed Alliance ROM. Everything went smooth, (I do have the ML1 baseband installed previously). Whenever I tap on a contact name I get "Unfortunatly, contacts has stopped". I am unable to see the contact info. Please help with this. I also noticed that the build numbers are up to around 30-32.....Do I have the most recent release for my Verizon S3?
Thank you very much.
DScuglia

VRCML1 Modem
I haven't tried rooted my phone since last year, so not completely sure what to do.
I used Casual to root, flashed insecure Aboot, and flashed Touch wiz recovery. Right now, I am on 4.1.2 android and trying to follow the instructions for AllianceRom. It says I should Install the 4.3 ML1 Modem, but the link seems to be dead. I found other models with different numbers, can those be used instead?

VRUML1 can be googled
nounta1016 said:
I haven't tried rooted my phone since last year, so not completely sure what to do.
I used Casual to root, flashed insecure Aboot, and flashed Touch wiz recovery. Right now, I am on 4.1.2 android and trying to follow the instructions for AllianceRom. It says I should Install the 4.3 ML1 Modem, but the link seems to be dead. I found other models with different numbers, can those be used instead?
Click to expand...
Click to collapse
If you Google d2vzw_ML1 modem, download the zip to your extcard, then reboot into recovery, wipe delvik and cache, I would do a factory reset, then go into twrp and install the modem. reboot, then install alliance rom......make sure that you use titanium back up to back up apps only (not data), then when you reboot after the rom install, redo the wifi, go to app store, download titanium back up, go into titanium and restore apps....BOOM

Issues with Encryption
To carry over to a more appropriate section from the main thread, I am having issues with Encryption. One of the reasons I moved over to a TW ROM from CM11 was the fact that Encryption is required for me, and I heard that TW ROM's are a little more successful with it on the S3 instead of CM11, which I have not been able to get to work.
So anyways, I have an MF1 baseband rooted Verizon S3. It's not locked down and is running TWRP 2.8.4 Recovery. I installed the ROM and went straight to Encryption after initial Setup. Talon4x4 noted in the main thread that he needed to use a PIN of at least 6 characters, but this does not appear to be an option for me. There is no ADM (Android Device Management) on my phone so security policies are completely settable by me. If I use a 7 character PIN, the Encryption system states that I must use a full password. As seen in this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After changing to a complex password (letters and numbers >6 characters), I can then Encrypt. But as noted in the previous thread, the phone goes to the Android logo for about 30 seconds and then restarts. When restarting, it does not ask for a password to unlock. Additionally, returning to the Encryption screen provides the option to Encrypt again, so it does not appear that anything is actually happening.
Anyone have any advice or hints that I might be able to use to troubleshoot? Thanks again for the ROM though! From what I'm using, it's great! Just got to get Encryption working to be able to keep it
EDIT:
Went through the process again, this time with it connected to adb so I was able to pull logging. I'm pasting the output below (after cleaning out the other noise). It looks like the problem is that it's not un-mounting the /data partition successfully. Can't imagine why since it's a brand new flash on a completely wiped device. If anyone else has some ideas I'd love to hear it!
Code:
FS_MIN_LIMIT frequency : 1350000 uid : 1000 pid : 669 pkgName : ACTIVITY_RES
[email protected]
I/MountService( 669): encrypting storage...
D/VoldCmdListener( 136): cryptfs inplace {}
I/CryptfsEE( 136): Just asked init to shut down class main
V/AT_Distributor_diag( 158): fd_uart (-1), fd_atd(7)
V/AT_Distributor_diag( 158): [UART DIAG : fd_atd < 0, fd open error
V/AT_Distributor_diag( 158): [UART DIAG] :
I/CryptfsUT( 136): /mnt_1/sdcard_1 sucessfully unmounted
I/CryptfsUT( 136): /mnt/shell/container sucessfully unmounted
I/CryptfsUT( 136): /data/data1 sucessfully unmounted
I/CryptfsUT( 136): /storage/PersonalPage sucessfully unmounted
I/CryptfsUT( 136): /mnt/shell/personalpage sucessfully unmounted
I/CryptfsUT( 136): /mnt/shell/emulated sucessfully unmounted
I/CryptfsUT( 136): /data_1 sucessfully unmounted
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 19, action 1)
E/ProcessKiller( 136): [email protected] /system/bin/drmserver (150) has open file /data/system/databases/drmdatabase.db
W/ProcessKiller( 136): [email protected] SIGHUP to process 150
D/ProcessKiller( 136): Wait for death /proc/150
I/ServiceManager( 135): service 'SurfaceFlinger' died
I/ServiceManager( 135): service 'display.qservice' died
I/ServiceManager( 135): service 'drm.drmManager' died
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 18, action 1)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 17, action 1)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 16, action 1)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 15, action 1)
I/ServiceManager( 135): service 'telephony.registry' died
I/ServiceManager( 135): service 'content' died
I/ServiceManager( 135): service 'package' died
I/ServiceManager( 135): service 'mdm.remotedesktop' died
I/ServiceManager( 135): service 'usagestats' died
I/ServiceManager( 135): service 'user' died
I/ServiceManager( 135): service 'multiwindow' died
I/ServiceManager( 135): service 'batteryinfo' died
I/ServiceManager( 135): service 'bluetooth_manager' died
I/ServiceManager( 135): service 'bluetooth_secure_mode_manager' died
I/ServiceManager( 135): service 'netpolicy' died
I/ServiceManager( 135): service 'meminfo' died
I/ServiceManager( 135): service 'container_service' died
I/ServiceManager( 135): service 'entropy' died
I/ServiceManager( 135): service 'textservices' died
I/ServiceManager( 135): service 'AtCmdFwd' died
I/ServiceManager( 135): service 'lock_settings' died
I/ServiceManager( 135): service 'mount' died
I/ServiceManager( 135): service 'device_policy' died
I/ServiceManager( 135): service 'log_manager_service' died
I/ServiceManager( 135): service 'enterprise_license_policy' died
I/ServiceManager( 135): service 'DirEncryptService' died
I/ServiceManager( 135): service 'wifi' died
I/ServiceManager( 135): service 'wifioffload' died
I/ServiceManager( 135): service 'wfd' died
I/ServiceManager( 135): service 'cpuinfo' died
I/ServiceManager( 135): service 'power' died
I/ServiceManager( 135): service 'gfxinfo' died
I/ServiceManager( 135): service 'dbinfo' died
I/ServiceManager( 135): service 'account' died
I/ServiceManager( 135): service 'sensorservice' died
I/ServiceManager( 135): service 'activity' died
I/ServiceManager( 135): service 'appops' died
I/ServiceManager( 135): service 'permission' died
I/ServiceManager( 135): service 'display' died
I/ServiceManager( 135): service 'network_management' died
I/ServiceManager( 135): service 'input_method' died
I/ServiceManager( 135): service 'tvoutservice' died
I/ServiceManager( 135): service 'mini_mode_app_manager' died
I/ServiceManager( 135): service 'commontime_management' died
I/ServiceManager( 135): service 'motion_recognition' died
I/ServiceManager( 135): service 'voip' died
I/ServiceManager( 135): service 'samsung.smartfaceservice' died
I/ServiceManager( 135): service 'dreams' died
I/ServiceManager( 135): service 'connectivity' died
I/ServiceManager( 135): service 'servicediscovery' died
I/ServiceManager( 135): service 'updatelock' died
I/ServiceManager( 135): service 'dropbox' died
I/ServiceManager( 135): service 'country_detector' died
I/ServiceManager( 135): service 'devicestoragemonitor' died
I/ServiceManager( 135): service 'location' died
I/ServiceManager( 135): service 'wallpaper' died
I/ServiceManager( 135): service 'notification' died
I/ServiceManager( 135): service 'search' died
I/ServiceManager( 135): service 'hardware' died
I/ServiceManager( 135): service 'sec_analytics' died
I/ServiceManager( 135): service 'wifip2p' died
I/ServiceManager( 135): service 'accessibility' died
I/ServiceManager( 135): service 'window' died
I/ServiceManager( 135): service 'input' died
I/ServiceManager( 135): service 'audio' died
I/ServiceManager( 135): service 'usb' died
I/ServiceManager( 135): service 'serial' died
I/ServiceManager( 135): service 'uimode' died
I/ServiceManager( 135): service 'kiesusb' died
I/ServiceManager( 135): service 'samplingprofiler' died
I/ServiceManager( 135): service 'backup' died
I/ServiceManager( 135): service 'appwidget' died
I/ServiceManager( 135): service 'diskstats' died
I/ServiceManager( 135): service 'LEDService' died
I/ServiceManager( 135): service 'battery' died
I/ServiceManager( 135): service 'vibrator' died
I/ServiceManager( 135): service 'CustomFrequencyManagerService' died
I/ServiceManager( 135): service 'edmnativehelper' died
I/ServiceManager( 135): service 'scheduling_policy' died
I/ServiceManager( 135): service 'alarm' died
I/ServiceManager( 135): service 'license_log_service' died
I/ServiceManager( 135): service 'application_policy' died
I/ServiceManager( 135): service 'remoteinjection' died
I/ServiceManager( 135): service 'harmony_eas_service' died
I/ServiceManager( 135): service 'phone_restriction_policy' died
I/ServiceManager( 135): service 'enterprise_policy' died
I/ServiceManager( 135): service 'statusbar' died
I/ServiceManager( 135): service 'clipboard' died
I/ServiceManager( 135): service 'clipboardEx' died
I/ServiceManager( 135): service 'netstats' died
I/ServiceManager( 135): service 'wifi_policy' died
I/ServiceManager( 135): service 'sip' died
I/ServiceManager( 135): service 'phone' died
I/ServiceManager( 135): service 'phoneext' died
I/ServiceManager( 135): service 'isms' died
I/ServiceManager( 135): service 'simphonebook' died
I/ServiceManager( 135): service 'iphonesubinfo' died
I/ServiceManager( 135): service 'media.audio_flinger' died
I/ServiceManager( 135): service 'media.player' died
I/ServiceManager( 135): service 'media.camera' died
I/ServiceManager( 135): service 'media.audio_policy' died
I/ServiceManager( 135): service 'android.security.keystore' died
I/ServiceManager( 135): service 'nfc' died
I/ServiceManager( 135): service 'secontroller' died
I/ServiceManager( 135): service 'nfccontroller' died
I/ServiceManager( 135): service 'TvoutService_C' died
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 14, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 13, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 12, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 11, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 10, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 9, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 8, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 7, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 6, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 5, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 4, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 3, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 2, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 1, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 0, action 2)
E/CryptfsUT( 136): Giving up on unmount /data (Device or resource busy)
I/dumpstate(10846): begin
I/dumpstate(10846): done
E/CryptfsEE( 136): Error (null) after framework is shutdown, no data changed, restarting system

rune-san said:
EDIT:
Went through the process again, this time with it connected to adb so I was able to pull logging. I'm pasting the output below (after cleaning out the other noise). It looks like the problem is that it's not un-mounting the /data partition successfully. Can't imagine why since it's a brand new flash on a completely wiped device. If anyone else has some ideas I'd love to hear it!
Code:
FS_MIN_LIMIT frequency : 1350000 uid : 1000 pid : 669 pkgName : ACTIVITY_RES
[email protected]
I/MountService( 669): encrypting storage...
D/VoldCmdListener( 136): cryptfs inplace {}
I/CryptfsEE( 136): Just asked init to shut down class main
V/AT_Distributor_diag( 158): fd_uart (-1), fd_atd(7)
V/AT_Distributor_diag( 158): [UART DIAG : fd_atd < 0, fd open error
V/AT_Distributor_diag( 158): [UART DIAG] :
I/CryptfsUT( 136): /mnt_1/sdcard_1 sucessfully unmounted
I/CryptfsUT( 136): /mnt/shell/container sucessfully unmounted
I/CryptfsUT( 136): /data/data1 sucessfully unmounted
I/CryptfsUT( 136): /storage/PersonalPage sucessfully unmounted
I/CryptfsUT( 136): /mnt/shell/personalpage sucessfully unmounted
I/CryptfsUT( 136): /mnt/shell/emulated sucessfully unmounted
I/CryptfsUT( 136): /data_1 sucessfully unmounted
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 19, action 1)
E/ProcessKiller( 136): [email protected] /system/bin/drmserver (150) has open file /data/system/databases/drmdatabase.db
W/ProcessKiller( 136): [email protected] SIGHUP to process 150
D/ProcessKiller( 136): Wait for death /proc/150
I/ServiceManager( 135): service 'SurfaceFlinger' died
I/ServiceManager( 135): service 'display.qservice' died
I/ServiceManager( 135): service 'drm.drmManager' died
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 18, action 1)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 17, action 1)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 16, action 1)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 15, action 1)
I/ServiceManager( 135): service 'telephony.registry' died
I/ServiceManager( 135): service 'content' died
I/ServiceManager( 135): service 'package' died
I/ServiceManager( 135): service 'mdm.remotedesktop' died
I/ServiceManager( 135): service 'usagestats' died
I/ServiceManager( 135): service 'user' died
I/ServiceManager( 135): service 'multiwindow' died
I/ServiceManager( 135): service 'batteryinfo' died
I/ServiceManager( 135): service 'bluetooth_manager' died
I/ServiceManager( 135): service 'bluetooth_secure_mode_manager' died
I/ServiceManager( 135): service 'netpolicy' died
I/ServiceManager( 135): service 'meminfo' died
I/ServiceManager( 135): service 'container_service' died
I/ServiceManager( 135): service 'entropy' died
I/ServiceManager( 135): service 'textservices' died
I/ServiceManager( 135): service 'AtCmdFwd' died
I/ServiceManager( 135): service 'lock_settings' died
I/ServiceManager( 135): service 'mount' died
I/ServiceManager( 135): service 'device_policy' died
I/ServiceManager( 135): service 'log_manager_service' died
I/ServiceManager( 135): service 'enterprise_license_policy' died
I/ServiceManager( 135): service 'DirEncryptService' died
I/ServiceManager( 135): service 'wifi' died
I/ServiceManager( 135): service 'wifioffload' died
I/ServiceManager( 135): service 'wfd' died
I/ServiceManager( 135): service 'cpuinfo' died
I/ServiceManager( 135): service 'power' died
I/ServiceManager( 135): service 'gfxinfo' died
I/ServiceManager( 135): service 'dbinfo' died
I/ServiceManager( 135): service 'account' died
I/ServiceManager( 135): service 'sensorservice' died
I/ServiceManager( 135): service 'activity' died
I/ServiceManager( 135): service 'appops' died
I/ServiceManager( 135): service 'permission' died
I/ServiceManager( 135): service 'display' died
I/ServiceManager( 135): service 'network_management' died
I/ServiceManager( 135): service 'input_method' died
I/ServiceManager( 135): service 'tvoutservice' died
I/ServiceManager( 135): service 'mini_mode_app_manager' died
I/ServiceManager( 135): service 'commontime_management' died
I/ServiceManager( 135): service 'motion_recognition' died
I/ServiceManager( 135): service 'voip' died
I/ServiceManager( 135): service 'samsung.smartfaceservice' died
I/ServiceManager( 135): service 'dreams' died
I/ServiceManager( 135): service 'connectivity' died
I/ServiceManager( 135): service 'servicediscovery' died
I/ServiceManager( 135): service 'updatelock' died
I/ServiceManager( 135): service 'dropbox' died
I/ServiceManager( 135): service 'country_detector' died
I/ServiceManager( 135): service 'devicestoragemonitor' died
I/ServiceManager( 135): service 'location' died
I/ServiceManager( 135): service 'wallpaper' died
I/ServiceManager( 135): service 'notification' died
I/ServiceManager( 135): service 'search' died
I/ServiceManager( 135): service 'hardware' died
I/ServiceManager( 135): service 'sec_analytics' died
I/ServiceManager( 135): service 'wifip2p' died
I/ServiceManager( 135): service 'accessibility' died
I/ServiceManager( 135): service 'window' died
I/ServiceManager( 135): service 'input' died
I/ServiceManager( 135): service 'audio' died
I/ServiceManager( 135): service 'usb' died
I/ServiceManager( 135): service 'serial' died
I/ServiceManager( 135): service 'uimode' died
I/ServiceManager( 135): service 'kiesusb' died
I/ServiceManager( 135): service 'samplingprofiler' died
I/ServiceManager( 135): service 'backup' died
I/ServiceManager( 135): service 'appwidget' died
I/ServiceManager( 135): service 'diskstats' died
I/ServiceManager( 135): service 'LEDService' died
I/ServiceManager( 135): service 'battery' died
I/ServiceManager( 135): service 'vibrator' died
I/ServiceManager( 135): service 'CustomFrequencyManagerService' died
I/ServiceManager( 135): service 'edmnativehelper' died
I/ServiceManager( 135): service 'scheduling_policy' died
I/ServiceManager( 135): service 'alarm' died
I/ServiceManager( 135): service 'license_log_service' died
I/ServiceManager( 135): service 'application_policy' died
I/ServiceManager( 135): service 'remoteinjection' died
I/ServiceManager( 135): service 'harmony_eas_service' died
I/ServiceManager( 135): service 'phone_restriction_policy' died
I/ServiceManager( 135): service 'enterprise_policy' died
I/ServiceManager( 135): service 'statusbar' died
I/ServiceManager( 135): service 'clipboard' died
I/ServiceManager( 135): service 'clipboardEx' died
I/ServiceManager( 135): service 'netstats' died
I/ServiceManager( 135): service 'wifi_policy' died
I/ServiceManager( 135): service 'sip' died
I/ServiceManager( 135): service 'phone' died
I/ServiceManager( 135): service 'phoneext' died
I/ServiceManager( 135): service 'isms' died
I/ServiceManager( 135): service 'simphonebook' died
I/ServiceManager( 135): service 'iphonesubinfo' died
I/ServiceManager( 135): service 'media.audio_flinger' died
I/ServiceManager( 135): service 'media.player' died
I/ServiceManager( 135): service 'media.camera' died
I/ServiceManager( 135): service 'media.audio_policy' died
I/ServiceManager( 135): service 'android.security.keystore' died
I/ServiceManager( 135): service 'nfc' died
I/ServiceManager( 135): service 'secontroller' died
I/ServiceManager( 135): service 'nfccontroller' died
I/ServiceManager( 135): service 'TvoutService_C' died
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 14, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 13, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 12, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 11, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 10, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 9, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 8, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 7, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 6, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 5, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 4, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 3, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 2, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 1, action 2)
W/CryptfsUT( 136): Failed to unmount /data (Device or resource busy, retries 0, action 2)
E/CryptfsUT( 136): Giving up on unmount /data (Device or resource busy)
I/dumpstate(10846): begin
I/dumpstate(10846): done
E/CryptfsEE( 136): Error (null) after framework is shutdown, no data changed, restarting system
Click to expand...
Click to collapse
So an update to this, I got the issue figured out. I actually found the answer under the S4 forums here with a post by jsda
jsda said:
I solved this issue on my Samsung Galaxy S4 2014 (P600).
I was able to encrypt the device after disabling SuperSU (which came with the auto-root rom) and rebooting.
Click to expand...
Click to collapse
SuperSU was what was creating the issue. After going into Application manager and turning it off, the /data partition unmounted successfully and Encryption started like it was supposed to! I just turned SuperSU back on when it was done. Now I have this excellent ROM + Encryption.

Same Issue for me....
I too installed this incredible rom, but noticed that everytime I tried to access my contacts...boom....Unfortunately, Contacts has stopped..........I tried force closing, clearing data and cache, changing clock to 24hr mode (don't know how that affects anything), uninstalling...reinstalling...crying....swearing....finally I installed "contacts +" app. It works.....so, the issue might be with Google.

Hello m8s... I'm not used to TW anymore and was hoping a kind fellow could point me in the direction where the built in ringtones are stored...

pyrite123 said:
Hello m8s... I'm not used to TW anymore and was hoping a kind fellow could point me in the direction where the built in ringtones are stored...
Click to expand...
Click to collapse
/system/media/audio/ringtones
Sent from my SCH-I535 using Tapatalk

WiFi/Bluetooth stop working periodically

Occasionally my Android Wear will disconnect from my M8 and won't reconnect. When this happens, the M8 can no longer see any 2.4ghz AP's either... Only 5ghz.
It takes rebooting the phone to get it to see bluetooth / wifi again.
What's going on here? Is this fixable?
I've also noticed that my moga is pretty laggy when I use it on the M8.
5.0.1

No one else has issues with this? I my phone bad then?

I got some logs... This is crazy:
Code:
05-27 08:46:41.508 7861-7861/? E/bt_osi_config﹕ config_new unable to open file '/etc/bluetooth/ble_stack.conf': No such file or directory
05-27 08:46:41.518 7861-7880/? E/BluetoothAdapterService﹕ checkA2dpState: returning
05-27 08:46:41.518 7861-7880/? E/BluetoothAdapterService﹕ checkHfpState: returning
05-27 08:46:44.858 8090-8090/? E/qcom-bluetooth﹕ /system/etc/init.qcom.bt.bluedroid.sh: Bluetooth QSoC firmware download failed: exit code
05-27 08:46:58.758 7861-7880/? E/BluetoothAdapterState﹕ Error enabling Bluetooth
05-27 08:46:58.758 953-1015/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at com.android.server.BluetoothManagerService.sendBluetoothStateCallback(BluetoothManagerService.java:684)
at com.android.server.BluetoothManagerService.bluetoothStateChangeHandler(BluetoothManagerService.java:1352)
at com.android.server.BluetoothManagerService.access$3200(BluetoothManagerService.java:61)
at com.android.server.BluetoothManagerService$BluetoothHandler.handleMessage(BluetoothManagerService.java:1086)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:155)
at android.os.HandlerThread.run(HandlerThread.java:61)
at com.android.server.ServiceThread.run(ServiceThread.java:46)
05-27 08:46:58.758 953-1015/? E/BluetoothA2dp﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.bluetooth.BluetoothA2dp$1.onBluetoothStateChange(BluetoothA2dp.java:126)
at com.android.server.BluetoothManagerService.sendBluetoothStateCallback(BluetoothManagerService.java:684)
at com.android.server.BluetoothManagerService.bluetoothStateChangeHandler(BluetoothManagerService.java:1352)
at com.android.server.BluetoothManagerService.access$3200(BluetoothManagerService.java:61)
at com.android.server.BluetoothManagerService$BluetoothHandler.handleMessage(BluetoothManagerService.java:1086)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:155)
at android.os.HandlerThread.run(HandlerThread.java:61)
at com.android.server.ServiceThread.run(ServiceThread.java:46)
05-27 08:46:58.768 4526-4541/? E/BluetoothInputDevice﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothInputDevice$1.onBluetoothStateChange(BluetoothInputDevice.java:227)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.768 4526-4542/? E/BluetoothPbap﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothPbap$1.onBluetoothStateChange(BluetoothPbap.java:121)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.768 953-1015/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at com.android.server.BluetoothManagerService.sendBluetoothStateCallback(BluetoothManagerService.java:684)
at com.android.server.BluetoothManagerService.bluetoothStateChangeHandler(BluetoothManagerService.java:1352)
at com.android.server.BluetoothManagerService.access$3200(BluetoothManagerService.java:61)
at com.android.server.BluetoothManagerService$BluetoothHandler.handleMessage(BluetoothManagerService.java:1086)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:155)
at android.os.HandlerThread.run(HandlerThread.java:61)
at com.android.server.ServiceThread.run(ServiceThread.java:46)
05-27 08:46:58.768 1154-25739/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.768 1585-2287/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.768 4526-4940/? E/BluetoothMap﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothMap$1.onBluetoothStateChange(BluetoothMap.java:64)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.778 4526-4541/? E/BluetoothPan﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothPan$1.onBluetoothStateChange(BluetoothPan.java:208)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.778 953-1015/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at com.android.server.BluetoothManagerService.sendBluetoothStateCallback(BluetoothManagerService.java:684)
at com.android.server.BluetoothManagerService.bluetoothStateChangeHandler(BluetoothManagerService.java:1352)
at com.android.server.BluetoothManagerService.access$3200(BluetoothManagerService.java:61)
at com.android.server.BluetoothManagerService$BluetoothHandler.handleMessage(BluetoothManagerService.java:1086)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:155)
at android.os.HandlerThread.run(HandlerThread.java:61)
at com.android.server.ServiceThread.run(ServiceThread.java:46)
05-27 08:46:58.778 1585-2119/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.778 1585-1618/? E/BluetoothHeadset﹕ java.lang.IllegalArgumentException: Service not registered: [email protected]
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1135)
at android.app.ContextImpl.unbindService(ContextImpl.java:1914)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:550)
at android.bluetooth.BluetoothHeadset$1.onBluetoothStateChange(BluetoothHeadset.java:239)
at android.bluetooth.IBluetoothStateChangeCallback$Stub.onTransact(IBluetoothStateChangeCallback.java:55)
at android.os.Binder.execTransact(Binder.java:454)
05-27 08:46:58.808 953-1015/? E/BluetoothManagerService﹕ recoverBluetoothServiceFromError
05-27 08:46:59.808 7861-7861/? E/BluetoothServiceJni﹕ Callback env check fail: env: 0xb72ba470, callback: 0xb83ff978
05-27 08:46:59.808 7861-7861/? E/BluetoothServiceJni﹕ Callback: 'adapter_state_change_callback' is not called on the correct thread
QSoC firmware download failed?

Is encryption possible at all with systemless root?

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?

Android 12 cellbroadcastreceiver permission denial causing high CPU usage in com.android.phone process?

(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.