[10][OFFICIAL] CarbonROM | cr-8.0 [z3c]

Search This thread

xavier_843

Member
Sep 10, 2020
5
0
Can you guys tell me which twrp version you use? I'll look into the issue asap.

Thanks for your support!

Both of my z3c have TWRP 3.3.1-0 and reliably do not stop the CarbonROM boot animation as soon as I install the latest update.
After wiping SYSTEM partition and installing 20200826-0627 and open_gapps-10.0-pico-20200831 everything is fine (until the next update).

---------- Post added at 01:13 PM ---------- Previous post was at 01:10 PM ----------

Thanks for your support!

Both of my z3c have TWRP 3.3.1-0 and reliably do not stop the CarbonROM boot animation as soon as I install the latest update.
After wiping SYSTEM partition and installing 20200826-0627 and open_gapps-10.0-pico-20200831 everything is fine (until the next update).

BTW: With the one that started making trouble with the two previous updates, I also tried wiping all partitions and wiping all partitions plus a new SDcard.
 

Flitzepiepe

Member
May 11, 2020
7
2
boot loop after weekly update

Same issue with the last weekly update CARBON-CR-8.0-PAX-WEEKLY-z3c-20200916-1548.zip.
Tried it also on my second z3c where lineageOS 17.1 was installed. Did a factory reset and tried to install the weekly update mentioned above. Installation CarbonROM and Magisk seemed to be successfull, then I had to reboot but the simlock unlock screen is not reached and the phone shuts automatically down after a while.
As mentioned in a previous post I am running TWRP 3.3.1.
 

xavier_843

Member
Sep 10, 2020
5
0
BTW: With the one that started making trouble with the two previous updates, I also tried wiping all partitions and wiping all partitions plus a new SDcard.

After ending up with two phones being unable to update, I installed NeoAdrians Lineage official build on that phone.
The TWRP recovery was not able to flash that image, so I flashed Lineage recovery replacing TWRP in recovery partition.
It today did the second update in a row without any problems.
 

Flitzepiepe

Member
May 11, 2020
7
2
After ending up with two phones being unable to update, I installed NeoAdrians Lineage official build on that phone.
The TWRP recovery was not able to flash that image, so I flashed Lineage recovery replacing TWRP in recovery partition.
It today did the second update in a row without any problems.

I could installed LineageOS 17.1 with twrp-3.3.1-z3c-20200212.img. I did it as described in the LineageOS Wiki.
 

Flitzepiepe

Member
May 11, 2020
7
2
boot loop after weekly update

After having problems with all weekly updates since CARBON-CR-8.0-PAX-WEEKLY-z3c-20200826-0627.zip I could install the newest one. As described earlier the updates installed but the simlock screen was not reached after booting and the phone shut dwon after a while. Now I remembered that some apps do not run after an update due to conflicts with my installed substratum theme version (e.g. Whatsapp). So I deactivated my substratum theme completely. Now I could install the newest weekly udpate and the simlock screen is reached and everything works fine again! So the problem is solved and has nothing to do with the weekly udpates but with the substratum theme. I apologize for the trouble caused!
 

Myself5

Recognized Developer
  • Mar 17, 2011
    3,375
    9,646
    23
    myself5.de
    After having problems with all weekly updates since CARBON-CR-8.0-PAX-WEEKLY-z3c-20200826-0627.zip I could install the newest one. As described earlier the updates installed but the simlock screen was not reached after booting and the phone shut dwon after a while. Now I remembered that some apps do not run after an update due to conflicts with my installed substratum theme version (e.g. Whatsapp). So I deactivated my substratum theme completely. Now I could install the newest weekly udpate and the simlock screen is reached and everything works fine again! So the problem is solved and has nothing to do with the weekly udpates but with the substratum theme. I apologize for the trouble caused!

    Thanks for clearing it up after your found the cause and glad that you can finally enjoy Carbon. Now we only need to figure out what causes the issues for @xavier_843
     

    xavier_843

    Member
    Sep 10, 2020
    5
    0
    Thanks for clearing it up after your found the cause and glad that you can finally enjoy Carbon. Now we only need to figure out what causes the issues for @xavier_843

    stupid me - I did two changes at a time and now the second phone successfully updated to CR-8.0-PAX-WEEKLY-z3c-20201007-0512

    A post in the z3c LOS thread mentioned that update problems were caused by opengapps.
    I installed the same version of opengapps on the carbonrom phone as on the LOS phone, then wanted to install a update that previously failed but instead the new carbonrom update installed and phone booted and did not end in the usual boot loop.

    btw: both phones show errors when writing ZIPs (e.g. carbonrom updates, opengapps) - "E:Unable to decrypt FBE device" - but work w/o problems.
     

    xavier_843

    Member
    Sep 10, 2020
    5
    0
    again in a boot-loop

    It is me again. After successful update last week, today's update brought back the boot-loop. This time the SONY logo only.
    Wiping SYSTEM and installing previous version also ended up in a boot-loop - but with the CR logo.
    Wiping SYSTEM and installing last know good version before previous version (26/08) also ended up in a boot-loop with the CR logo.
    Only way out was wiping SYSTEM and restoring the backup I made with the previous version. Now phone runs w/o probs.
    Any ideas?
     

    xavier_843

    Member
    Sep 10, 2020
    5
    0
    It is time for a new feedback: versions from week before last week and this week were updating fine. All other versions (since 21/10) ended up in a infinite boot loop (SONY logo).
    The only thing I changed was switching "safe mode" to "off" in CarbonROMs update settings.
     

    m0d

    Senior Member
    Nov 3, 2010
    1,048
    419
    I recently updated ROM and in setup it asks if you want to restore apps and data from backup.
    This is an amazing feature, but which backups are supported? twrp?

    Thank you
     

    ascendant512

    New member
    Aug 22, 2013
    4
    0
    This is an amazing feature, but which backups are supported? twrp?
    The only backup restore feature I saw when setting it up was the one that is built in to Android. I briefly checked to see if it supported the "transfer from another phone" option and it seemed to just exit out or crash. I expect it would work if you backed up to your Google account the way Android prompts you in the backup settings.


    In other news, has anyone got device encryption working on this ROM? I upgraded from CarbonROM 5.1 (Android 7) with my device encrypted, and it failed to boot (after typing in the passcode, it rebooted to recovery automatically). That was disappointing, but not catastrophic. I formatted my /data to switch back from encrypted to unencrypted and "reinstalled" and it worked, but then when I turned on device encryption it only rebooted to a SONY logo. I tried a couple times and left it overnight, but it would only work after that if I did the power reset and reformatted /data to "unencrypt." The behavior was the same with a fresh /data + enable encryption: prompt for passcode, then reboot to recovery. I don't know what logs would be useful to provide, since there are so many reboots involved.
     

    Andrei001

    New member
    Jul 31, 2018
    1
    0
    tell me what could be the problem with the wrong thing, the wifi wrote connected without access to the Internet, although your home network on another device works
     

    Samare

    Member
    Nov 6, 2014
    30
    8
    I also had this situation. The upgrade from 6.1 to 8.0 ended with an unusable result, so I installed it on a cleaned (all wiped and data formated) phone. Everything started working, but the battery quickly drained even in power save mode. I tried to disable many options, but it didn't work. Then I flashed the newer twrp-3.3.1-z3c-20191212-sar.img (was 3.3.0 and not "sar") and tried to install LineageOS 17.1 for z3c. Everything worked and the battery discharged that with CarbonROM cr-6.1 [z3c] - slow. Then I installed CarbonROM 8.0 on a cleaned (all wiped and data formated) phone cr-8.0 [z3c] and everything is beautiful for me. Discharge 2 percent in three hours a night.

    After a few days........
    The quick battery discharge is back and I can't resolve it. I returned to CB6.1
    Did you check with BetterBatteryStats (https://forum.xda-developers.com/t/app-2-2-05-oct-v2-4-betterbatterystats.1179809/)?

    I noticed heavy battery drain (the phone was getting hot, zero deep sleep) on every Android 9 et 10 roms.
    I checked with BetterBatteryStats on the microG LineageOS 17.1 (Android 10) version and found out the culprit was the process media.extractor.

    It turns out that happens because of some corrupt or unsupported media file on the microsd card or the internal storage. After removing the card, no more battery drain, so I have to check the files (the filesystem is ok).

    Anyway, it seems like a bug in media.extractor.
    Here's how I worked around it: https://forum.xda-developers.com/t/official-lineageos-17-1-for-z3c.4160347/post-84723935
     
    Last edited:
    • Like
    Reactions: armorgeddon

    f0k

    Member
    Jan 1, 2021
    13
    0
    A few days ago I updated to CARBON-CR-8.0-PAX-RELEASE-z3c-20210220-0416 via CarbonDelta. Rebooting got stuck and then automatically rebooted to TWRP. When trying to reboot to the system, it again gets stuck and reboots to TWRP. I tried flashing 20210220-0416 and 20210127-2325 from within TWRP 3.3.1-0 (without wiping anything), but the result is the same.

    Any suggestion on how to proceed from here? The previous update went fine. What changed in between is that I added an SD card as adoptable storage. I bought the phone second-hand with CarbonROM preinstalled, so I'm not too familiar with the installation process. Shall I wipe the system partition first or is it overwritten anyway? What will I lose when I do so? (I know now that I could have done a backup with TWRP before updating, but I didn't know before and wasn't particularly scared about updating.)

    Side question: Is there a way to obtain the full kernel log to figure out what went wrong on booting? In /proc/last_kmsg I only find the end of the log file. I'm not sure if this is helpful: last_kmsg

    Thanks for supporting this device and thanks in advance for any advice!
     

    Samare

    Member
    Nov 6, 2014
    30
    8
    A few days ago I updated to CARBON-CR-8.0-PAX-RELEASE-z3c-20210220-0416 via CarbonDelta. Rebooting got stuck and then automatically rebooted to TWRP. When trying to reboot to the system, it again gets stuck and reboots to TWRP. I tried flashing 20210220-0416 and 20210127-2325 from within TWRP 3.3.1-0 (without wiping anything), but the result is the same.

    Any suggestion on how to proceed from here? The previous update went fine. What changed in between is that I added an SD card as adoptable storage. I bought the phone second-hand with CarbonROM preinstalled, so I'm not too familiar with the installation process. Shall I wipe the system partition first or is it overwritten anyway? What will I lose when I do so? (I know now that I could have done a backup with TWRP before updating, but I didn't know before and wasn't particularly scared about updating.)

    Side question: Is there a way to obtain the full kernel log to figure out what went wrong on booting? In /proc/last_kmsg I only find the end of the log file. I'm not sure if this is helpful: last_kmsg

    Thanks for supporting this device and thanks in advance for any advice!
    First do a nandroid backup in TWRP: Enable compression and disable space checking (make sure the backup succeeds though - you can move files from your SD card to your computer from TWRP to make space). Space checking doesn't take into account compression.
    Select the SD card (Select Storage) and backup Boot, Data, EFS and System: It's even safer to copy the TWRP folder with the backup to your computer.

    Wipe Dalvik + Cache:
     

    f0k

    Member
    Jan 1, 2021
    13
    0
    Thank you for the nice guide! I had already tried that and got some error regarding formatting the cache. This time it went through fine:
    Code:
    E:Unable to decrypt FBE device
    Updating partition details...
    ...done
    Updating partition details...
    ...done
    Full SELinux support is present.
    MTP Enabled
    Wiping Cache & Dalvik...
    Cleaned: /data/dalvik-cache
    -- Dalvik Cache Directories Wipe Complete!
    Formatting Cache using mke2fs...
    Done.
    Updating partition details...
    ...done
    Unfortunately, this didn't help anything. It's still getting stuck on booting and then resorting to reboot into TWRP.

    Q1: Does it make any difference to wipe the system partition before flashing, or is the system partition overwritten with an image anyway?

    Q2: Is there any way to obtain a full kernel message log, not just the part in /proc/last_kmsg?

    Any other idea what to try? I'd like to avoid doing a factory reset, as I don't have a recent backup of everything. (I have an older backup of my apps, and a nandroid backup done after the failed update.) Thanks a lot in advance!
     

    Samare

    Member
    Nov 6, 2014
    30
    8
    Thank you for the nice guide! I had already tried that and got some error regarding formatting the cache. This time it went through fine:
    Code:
    E:Unable to decrypt FBE device
    Updating partition details...
    ...done
    Updating partition details...
    ...done
    Full SELinux support is present.
    MTP Enabled
    Wiping Cache & Dalvik...
    Cleaned: /data/dalvik-cache
    -- Dalvik Cache Directories Wipe Complete!
    Formatting Cache using mke2fs...
    Done.
    Updating partition details...
    ...done
    Unfortunately, this didn't help anything. It's still getting stuck on booting and then resorting to reboot into TWRP.

    Q1: Does it make any difference to wipe the system partition before flashing, or is the system partition overwritten with an image anyway?

    Q2: Is there any way to obtain a full kernel message log, not just the part in /proc/last_kmsg?

    Any other idea what to try? I'd like to avoid doing a factory reset, as I don't have a recent backup of everything. (I have an older backup of my apps, and a nandroid backup done after the failed update.) Thanks a lot in advance!
    Q1: It shouldn't because most ROMs wipe it when installed. But you can try it anyway. If it still doesn't work, try wiping Data to make sure that ROM does work. Just make sure to not wipe Internal storage since the nandroid backup doesn't include it (folders like Pictures, ...).

    Q2: Here's a list: https://android.stackexchange.com/questions/14430/how-can-i-view-and-examine-the-android-log
    I'd start with adb logcat since your last_kmsg shows that adbd is started.

    One thing to check is that you didn't let TWRP install its app after flashing the ROM (if it did in your version). I got a boot loop after that and had to remove the app using the File manager inside TWRP.
     

    f0k

    Member
    Jan 1, 2021
    13
    0
    Q2: Here's a list: https://android.stackexchange.com/questions/14430/how-can-i-view-and-examine-the-android-log
    I'd start with adb logcat since your last_kmsg shows that adbd is started.
    Thank you! I had already tried that, but adb is stuck at "- waiting for device -". Good spot that adbd is already running! Presumably it's not working because there's no UI for me to confirm debugging access on the phone. I never ticked the "always accept" box.

    I was thinking of something to place in init.rc as suggested here: https://stackoverflow.com/a/25533212/12436673
    That is, I've appended the following to my init.rc:
    Code:
    # write log to cache
    service persistentLogging /system/bin/logcat -r 1024 -n 9 -v threadTime -b all -f /cache/logs/log
        user system
        group system log
        disabled
    
    on post-fs
        mkdir /cache/logs 0775 system log
        start persistentLogging
    On rebooting, it creates /cache/logs with the correct permissions (so the mkdir command went fine), but it remains empty... Comparing with the manual, the logcat command looks completely fine: https://developer.android.com/studio/command-line/logcat.

    One thing to check is that you didn't let TWRP install its app after flashing the ROM
    Doesn't seem so, it's not in /data/app.

    What I noticed is that the device issues a short click sound every few seconds while it's trying to boot. I hope it's not a hardware issue that wasn't linked to the update, but just came up because of the reboot.

    If it still doesn't work, try wiping Data to make sure that ROM does work. Just make sure to not wipe Internal storage since the nandroid backup doesn't include it (folders like Pictures, ...).
    Good idea. I'll try that when I'm brave enough.
     

    f0k

    Member
    Jan 1, 2021
    13
    0

    Attachments

    • logcat.zip
      847.3 KB · Views: 1

    Samare

    Member
    Nov 6, 2014
    30
    8
    Good find!

    About the needle, searching for "signal 9" is a good starting point. And a little above it, starting at line 3958:
    Code:
    03-20 16:52:09.068   668   668 E System  : ******************************************
    03-20 16:52:09.069   668   668 E System  : ************ Failure starting system services
    03-20 16:52:09.069   668   668 E System  : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms: android.permission.CONTROL_INCALL_EXPERIENCE, com.google.android.gms: android.permission.MANAGE_SOUND_TRIGGER, com.google.android.gms: android.permission.REMOTE_DISPLAY_PROVIDER, com.google.android.gms: android.permission.CONTROL_DISPLAY_SATURATION, com.google.android.gms: android.permission.CONTROL_KEYGUARD_SECURE_NOTIFICATIONS, com.google.android.gms: android.permission.MODIFY_PHONE_STATE, com.google.android.gms: android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS, com.google.android.gms: android.permission.START_TASKS_FROM_RECENTS, com.google.android.gms: android.permission.INTENT_FILTER_VERIFICATION_AGENT, com.google.android.gms: android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST, com.google.android.gms: android.permission.ALLOCATE_AGGRESSIVE, com.google.android.gms: android.permission.PACKAGE_USAGE_STATS, com.google.android.gms: android.permission.NOTIFY_PENDING_SYSTEM_UPDATE, com.google.android.gms: android.permission.CAPTURE_AUDIO_HOTWORD, com.google.android.gms: android.permission.ACTIVITY_EMBEDDING, com.google.android.gms: android.permission.PROVIDE_RESOLVER_RANKER_SERVICE, com.google.android.gms: android.permission.TETHER_PRIVILEGED, com.google.android.gms: android.permission.RESET_PASSWORD, com.google.android.gms: android.permission.RECOVER_KEYSTORE, com.google.android.gms: android.permission.CAPTURE_AUDIO_OUTPUT, com.google.android.gms: android.permission.BLUETOOTH_PRIVILEGED, com.google.android.gms: android.permission.LOCAL_MAC_ADDRESS, com.google.android.gms: android.permission.MANAGE_SUBSCRIPTION_PLANS, com.google.android.gms: android.permission.RECEIVE_DATA_ACTIVITY_CHANGE, com.google.android.gms: android.permission.READ_PRIVILEGED_PHONE_STATE, com.google.android.gms: android.permission.MANAGE_VOICE_KEYPHRASES, com.google.android.gms: android.permission.SCORE_NETWORKS, com.google.android.gms: android.permission.MODIFY_DAY_NIGHT_MODE, com.google.android.gms: android.permission.DISPATCH_PROVISIONING_MESSAGE, com.google.android.gms: android.permission.INTERACT_ACROSS_USERS, com.google.android.gms: android.permission.READ_LOGS, com.google.android.gms: android.permission.READ_DREAM_STATE, com.google.android.gms: android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS, com.google.android.gms: android.permission.BACKUP, com.google.android.gms: android.permission.SUBSTITUTE_SHARE_TARGET_APP_NAME_AND_ICON, com.google.android.gms: android.permission.LOCK_DEVICE, com.google.android.gms: android.permission.OVERRIDE_WIFI_CONFIG, com.google.android.gms: com.android.voicemail.permission.READ_VOICEMAIL, com.google.android.gms: android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME, com.google.android.gms: android.permission.SET_TIME_ZONE, com.google.android.gms: android.permission.CALL_PRIVILEGED, com.google.android.gms: android.permission.REGISTER_CALL_PROVIDER, com.google.android.gms: android.permission.LOCATION_HARDWARE, com.google.android.gms: android.permission.ACCESS_NETWORK_CONDITIONS, com.google.android.gms: android.permission.UPDATE_APP_OPS_STATS, com.google.android.gms: android.permission.READ_OEM_UNLOCK_STATE, com.google.android.gms: android.permission.PROVIDE_TRUST_AGENT, com.google.android.gms: android.permission.RECOVERY, com.google.android.gms: android.permission.GET_APP_OPS_STATS, com.google.android.gms: android.permission.START_ACTIVITIES_FROM_BACKGROUND, com.google.android.gms: android.permission.SEND_SMS_NO_CONFIRMATION, com.google.android.gms: android.permission.MODIFY_AUDIO_ROUTING, com.google.android.gms: android.permission.MODIFY_NETWORK_ACCOUNTING, com.google.android.gms: android.permission.REAL_GET_TASKS, com.google.android.gms: android.permission.READ_WIFI_CREDENTIAL, com.google.android.gms: android.permission.USER_ACTIVITY, com.google.android.gms: android.permission.MANAGE_USB}
    03-20 16:52:09.069   668   668 E System  :     at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:3055)
    03-20 16:52:09.069   668   668 E System  :  
    03-20 16:52:09.070   668   668 E Zygote  : System zygote died with exception
    03-20 16:52:09.070   668   668 E Zygote  : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms: android.permission.CONTROL_INCALL_EXPERIENCE, com.google.android.gms: android.permission.MANAGE_SOUND_TRIGGER, com.google.android.gms: android.permission.REMOTE_DISPLAY_PROVIDER, com.google.android.gms: android.permission.CONTROL_DISPLAY_SATURATION, com.google.android.gms: android.permission.CONTROL_KEYGUARD_SECURE_NOTIFICATIONS, com.google.android.gms: android.permission.MODIFY_PHONE_STATE, com.google.android.gms: android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS, com.google.android.gms: android.permission.START_TASKS_FROM_RECENTS, com.google.android.gms: android.permission.INTENT_FILTER_VERIFICATION_AGENT, com.google.android.gms: android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST, com.google.android.gms: android.permission.ALLOCATE_AGGRESSIVE, com.google.android.gms: android.permission.PACKAGE_USAGE_STATS, com.google.android.gms: android.permission.NOTIFY_PENDING_SYSTEM_UPDATE, com.google.android.gms: android.permission.CAPTURE_AUDIO_HOTWORD, com.google.android.gms: android.permission.ACTIVITY_EMBEDDING, com.google.android.gms: android.permission.PROVIDE_RESOLVER_RANKER_SERVICE, com.google.android.gms: android.permission.TETHER_PRIVILEGED, com.google.android.gms: android.permission.RESET_PASSWORD, com.google.android.gms: android.permission.RECOVER_KEYSTORE, com.google.android.gms: android.permission.CAPTURE_AUDIO_OUTPUT, com.google.android.gms: android.permission.BLUETOOTH_PRIVILEGED, com.google.android.gms: android.permission.LOCAL_MAC_ADDRESS, com.google.android.gms: android.permission.MANAGE_SUBSCRIPTION_PLANS, com.google.android.gms: android.permission.RECEIVE_DATA_ACTIVITY_CHANGE, com.google.android.gms: android.permission.READ_PRIVILEGED_PHONE_STATE, com.google.android.gms: android.permission.MANAGE_VOICE_KEYPHRASES, com.google.android.gms: android.permission.SCORE_NETWORKS, com.google.android.gms: android.permission.MODIFY_DAY_NIGHT_MODE, com.google.android.gms: android.permission.DISPATCH_PROVISIONING_MESSAGE, com.google.android.gms: android.permission.INTERACT_ACROSS_USERS, com.google.android.gms: android.permission.READ_LOGS, com.google.android.gms: android.permission.READ_DREAM_STATE, com.google.android.gms: android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS, com.google.android.gms: android.permission.BACKUP, com.google.android.gms: android.permission.SUBSTITUTE_SHARE_TARGET_APP_NAME_AND_ICON, com.google.android.gms: android.permission.LOCK_DEVICE, com.google.android.gms: android.permission.OVERRIDE_WIFI_CONFIG, com.google.android.gms: com.android.voicemail.permission.READ_VOICEMAIL, com.google.android.gms: android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME, com.google.android.gms: android.permission.SET_TIME_ZONE, com.google.android.gms: android.permission.CALL_PRIVILEGED, com.google.android.gms: android.permission.REGISTER_CALL_PROVIDER, com.google.android.gms: android.permission.LOCATION_HARDWARE, com.google.android.gms: android.permission.ACCESS_NETWORK_CONDITIONS, com.google.android.gms: android.permission.UPDATE_APP_OPS_STATS, com.google.android.gms: android.permission.READ_OEM_UNLOCK_STATE, com.google.android.gms: android.permission.PROVIDE_TRUST_AGENT, com.google.android.gms: android.permission.RECOVERY, com.google.android.gms: android.permission.GET_APP_OPS_STATS, com.google.android.gms: android.permission.START_ACTIVITIES_FROM_BACKGROUND, com.google.android.gms: android.permission.SEND_SMS_NO_CONFIRMATION, com.google.android.gms: android.permission.MODIFY_AUDIO_ROUTING, com.google.android.gms: android.permission.MODIFY_NETWORK_ACCOUNTING, com.google.android.gms: android.permission.REAL_GET_TASKS, com.google.android.gms: android.permission.READ_WIFI_CREDENTIAL, com.google.android.gms: android.permission.USER_ACTIVITY, com.google.android.gms: android.permission.MANAGE_USB}
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:3055)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:122)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:3116)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21986)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.SystemServer.startOtherServices(SystemServer.java:1998)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.SystemServer.run(SystemServer.java:513)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.server.SystemServer.main(SystemServer.java:354)
    03-20 16:52:09.070   668   668 E Zygote  :     at java.lang.reflect.Method.invoke(Native Method)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    03-20 16:52:09.070   668   668 E Zygote  :     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:918)
    03-20 16:52:09.070   668   668 D AndroidRuntime: Shutting down VM
    --------- beginning of crash
    03-20 16:52:09.070   668   668 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
    03-20 16:52:09.070   668   668 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms: android.permission.CONTROL_INCALL_EXPERIENCE, com.google.android.gms: android.permission.MANAGE_SOUND_TRIGGER, com.google.android.gms: android.permission.REMOTE_DISPLAY_PROVIDER, com.google.android.gms: android.permission.CONTROL_DISPLAY_SATURATION, com.google.android.gms: android.permission.CONTROL_KEYGUARD_SECURE_NOTIFICATIONS, com.google.android.gms: android.permission.MODIFY_PHONE_STATE, com.google.android.gms: android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS, com.google.android.gms: android.permission.START_TASKS_FROM_RECENTS, com.google.android.gms: android.permission.INTENT_FILTER_VERIFICATION_AGENT, com.google.android.gms: android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST, com.google.android.gms: android.permission.ALLOCATE_AGGRESSIVE, com.google.android.gms: android.permission.PACKAGE_USAGE_STATS, com.google.android.gms: android.permission.NOTIFY_PENDING_SYSTEM_UPDATE, com.google.android.gms: android.permission.CAPTURE_AUDIO_HOTWORD, com.google.android.gms: android.permission.ACTIVITY_EMBEDDING, com.google.android.gms: android.permission.PROVIDE_RESOLVER_RANKER_SERVICE, com.google.android.gms: android.permission.TETHER_PRIVILEGED, com.google.android.gms: android.permission.RESET_PASSWORD, com.google.android.gms: android.permission.RECOVER_KEYSTORE, com.google.android.gms: android.permission.CAPTURE_AUDIO_OUTPUT, com.google.android.gms: android.permission.BLUETOOTH_PRIVILEGED, com.google.android.gms: android.permission.LOCAL_MAC_ADDRESS, com.google.android.gms: android.permission.MANAGE_SUBSCRIPTION_PLANS, com.google.android.gms: android.permission.RECEIVE_DATA_ACTIVITY_CHANGE, com.google.android.gms: android.permission.READ_PRIVILEGED_PHONE_STATE, com.google.android.gms: android.permission.MANAGE_VOICE_KEYPHRASES, com.google.android.gms: android.permission.SCORE_NETWORKS, com.google.android.gms: android.permission.MODIFY_DAY_NIGHT_MODE, com.google.android.gms: android.permission.DISPATCH_PROVISIONING_MESSAGE, com.google.android.gms: android.permission.INTERACT_ACROSS_USERS, com.google.android.gms: android.permission.READ_LOGS, com.google.android.gms: android.permission.READ_DREAM_STATE, com.google.android.gms: android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS, com.google.android.gms: android.permission.BACKUP, com.google.android.gms: android.permission.SUBSTITUTE_SHARE_TARGET_APP_NAME_AND_ICON, com.google.android.gms: android.permission.LOCK_DEVICE, com.google.android.gms: android.permission.OVERRIDE_WIFI_CONFIG, com.google.android.gms: com.android.voicemail.permission.READ_VOICEMAIL, com.google.android.gms: android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME, com.google.android.gms: android.permission.SET_TIME_ZONE, com.google.android.gms: android.permission.CALL_PRIVILEGED, com.google.android.gms: android.permission.REGISTER_CALL_PROVIDER, com.google.android.gms: android.permission.LOCATION_HARDWARE, com.google.android.gms: android.permission.ACCESS_NETWORK_CONDITIONS, com.google.android.gms: android.permission.UPDATE_APP_OPS_STATS, com.google.android.gms: android.permission.READ_OEM_UNLOCK_STATE, com.google.android.gms: android.permission.PROVIDE_TRUST_AGENT, com.google.android.gms: android.permission.RECOVERY, com.google.android.gms: android.permission.GET_APP_OPS_STATS, com.google.android.gms: android.permission.START_ACTIVITIES_FROM_BACKGROUND, com.google.android.gms: android.permission.SEND_SMS_NO_CONFIRMATION, com.google.android.gms: android.permission.MODIFY_AUDIO_ROUTING, com.google.android.gms: android.permission.MODIFY_NETWORK_ACCOUNTING, com.google.android.gms: android.permission.REAL_GET_TASKS, com.google.android.gms: android.permission.READ_WIFI_CREDENTIAL, com.google.android.gms: android.permission.USER_ACTIVITY, com.google.android.gms: android.permission.MANAGE_USB}
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:3055)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:122)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:3116)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21986)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.SystemServer.startOtherServices(SystemServer.java:1998)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.SystemServer.run(SystemServer.java:513)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.server.SystemServer.main(SystemServer.java:354)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    03-20 16:52:09.071   668   668 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:918)

    Starting in Android 8.0, manufacturers must explicitly grant privileged permissions in the system configuration XML files in the /etc/permissions directory. As of Android 9, implementors must explicitly grant or deny all privileged permissions or the device won’t boot.

    I suggest installing Open GApps ARM Android 10 Pico.
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 10
      uK2Q5sA.png

      CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

      Please feel free to look, build, and use our code at CarbonROM's GitHub...

      What is PAX?
      Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
      PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover ;)

      Disclaimer:
      While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.

      Support:
      We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:

      1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
      2) Read our FAQ, which can be found on our website. Carbon FAQ
      3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
      4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.

      Download
      Join the CarbonROM Discord server
      Meet us on Telegram
      Homepage
      GitHub
      Kernel source


      Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!



      XDA:DevDB Information
      CarbonROM, ROM for the Sony Xperia Z3 Compact

      Contributors
      Myself5, CarbonROM
      Source Code: https://github.com/CarbonROM

      ROM OS Version: Android 10
      ROM Kernel: Linux 3.x
      Based On: AOSP

      Version Information
      Status: Nightly

      Created 2020-02-08
      Last Updated 2020-05-06
      7
      Hum this new OP looks interesting.

      And what is this Twitter Post?

      And did someone say May Security Patches?
      5
      My feedback about CR8.0 (weekly build 20200513-0206) with gapps pico, magisk 20.4 and ~75 user apps.
      Using TWRP 3.3.1-z3c-20191212-sar from here
      Xposed (RiRu 20.2 from magisk repo, EdXposed-YAHFA-v0.4.6.2.4529 from here) works without problems (1st screenshot).
      I'm not using internal data encryption because of compatibility problems between ROMs/versions, tired to restore backups each time I flash new ROM.
      About 700MB of RAM free just after boot, with stock launcher.
      Battery drain fast, but my battery is very old, no complain.

      Pros:
      + reliably fast
      + everything works including GPS, BT, calls/data, hotspot and all my apps
      + no problems with audio routing and mic sensitivity
      + camera is ok but I use OpenCamera anyway

      Cons/bugs:
      - still no 5ghz wifi in Russia (I use my magisk-patch to fix this, may also help with other regions, try if you meet this bug)
      - ongoing call can be hanged accidentally by double-tap in any place of turned off display (e.g. by cheek) if tap-to-wake feature is active (here is my workaround using Automate tool, works like a charm). I'm not sure if this bug belongs only to my phone or to any z3c, but it was like forever on any AOSP-based ROM, starting with Android 7.
      - broken size for "Aeroplane mode" button/icon in power menu (see 2nd screenshot)
      - ringtone sound become a bit quieter after half a second from start of incoming call
      - overall loudspeakers volume is not loud enough

      Features I'd like to have in this ROM:
      1) choose clock position in statusbar (only at left in CR8.0)
      2) brightness control by sliding in statusbar without opening it
      3) mess up digits on the PIN unlock screen [Carbone Fibers > Buttons > Scramble PIN]
      4) unlock instantly when entering last digit without confirmation
      5) long press power button to turn on/off torch while display turned off [Carbone Fibers > Buttons > Toggle torch]
      6) restrict/disable power menu while phone locked
      7) disable notification panel while phone locked
      8) set minimal time between notifications on per app basis
      9) wake by volume rocker buttons
      10) increasing ringing volume
      11) debugging over network (settings in devs options, absent in CR)
      Most of this stuff available in LOS and AEX roms, but also all (except: 7,10,11, with bugs: 6) can be achieved in CR by using GravityBox xposed module.

      Thank you @Myself5 for continue work with our lovely z3c.
      5
      Due to reports of complications with Google Apps we pulled the PAX builds for Z3 and Z3 Compact. I'm working on a fix and hope to release fixed builds ASAP.

      If you had any weird issues, then that's why. Sorry for that.

      When those builds get released however, they STILL require a clean install over CR-6.1. Dirty flashing does not work.

      We found and fixed the cause. Builds for the Z3 and Z3 Compact are in the process of getting re-released. Sorry for the issues.
      5
      New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone