[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [z3c]

Search This thread

okij

Senior Member
Oct 24, 2012
1,694
3,667
Düsseldorf
Not working after update magisk to 19.3

Then either you haven't updated to .291 stock ROM before installing CarbonROM (so your phone doesn't have the latest bootloader) or you didn't closely follow the steps that I wrote (i.e. the phone has to be turned off completely and then you have to press both Power and Volume-Down at the same time for about 10 seconds until you see the TWRP splash screen).

Magisk 19.x can't break this way of entering TWRP, because it's part of the latest bootloader.
 
  • Like
Reactions: Myself5

nokian95ita

Senior Member
Sep 19, 2008
336
19
Then either you haven't updated to .291 stock ROM before installing CarbonROM (so your phone doesn't have the latest bootloader) or you didn't closely follow the steps that I wrote (i.e. the phone has to be turned off completely and then you have to press both Power and Volume-Down at the same time for about 10 seconds until you see the TWRP splash screen).

Magisk 19.x can't break this way of entering TWRP, because it's part of the latest bootloader.

I am on .291 stock rom but after update of magisk to 19.3 version a cannot reboot to recovery. i just tried to update the revory via adb but i toke an error message. see the attached picture
 

Attachments

  • DSC_20190701_115438_184.jpg
    DSC_20190701_115438_184.jpg
    258.3 KB · Views: 438

pawloland

Senior Member
Jan 23, 2019
182
70
I am on .291 stock rom but after update of magisk to 19.3 version a cannot reboot to recovery. i just tried to update the revory via adb but i toke an error message. see the attached picture
Don't type adb shell. You have to connect your phone in fastboot mode to pc and then flash twrp by typing "fastboot flash FOTAKernel (twrp_file_name).img".
 
  • Like
Reactions: okij

inadd

Member
Jul 1, 2019
5
1
I discovered nasty encryption behavior in CARBON-CR-6.1-NOCT-RELEASE-z3c-20190611-0407.
It's easy to reproduce:
- wipe and install rom
- select settings - ... - encrypt phone
- the phone reboots, encrypts and reboots again
- now press power button and select Restart - System
- now the phone is stuck in cr bootscreen forever

At this point you can't access your /data partition ever again, because no TWRP for z3c has decryption support and you can't even decrypt a partition dump using your computer.

The only way to get encryption work correctly in the first place is to set a password or pin before encryption or on the first reboot afterwards.
If you ever decide to remove your password or pin by setting the screen lock to swipe or to none you're stuck in cr bootscreen again.
 

nokian95ita

Senior Member
Sep 19, 2008
336
19
new problem

Goodmorning everyone
I finally made the update to the June release finally solving the recovery problem with the latest magisk 19.x release. as always this rom works very well but I still have problems with battery consumption during use while standby consumption is more than acceptable, around 2% / h. unfortunately, however, I have a serious problem that appears to be of software origin: watch the video. it happens that in the lookscreen I can lower the status bar and make the notifications and quick links appear while in the launcher and in the app it doesn't work. can you give me a hand thanks.


https://www.youtube.com/watch?v=499RD5tQ4W0&feature=youtu.be
 

leo.chirkov

Member
Oct 13, 2014
10
3
Minsk
Messaging app crashes

Messaging app crashes every time I select "Blocked contacts" in settings. Logcat output:

Code:
FATAL EXCEPTION: main
Process: com.android.messaging, PID: 5687
java.lang.AssertionError: Expected condition to be true
	at com.android.messaging.util.ar.afA(SourceFile:202)
	at com.android.messaging.util.ar.afo(SourceFile:84)
	at com.android.messaging.ui.BlockedParticipantsActivity.onAttachFragment(SourceFile:41)
	at android.app.Activity$HostCallbacks.onAttachFragment(Activity.java:7735)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1229)
	at android.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1557)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1618)
	at android.app.BackStackRecord.executeOps(BackStackRecord.java:807)
	at android.app.FragmentManagerImpl.executeOps(FragmentManager.java:2386)
	at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2181)
	at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2136)
	at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2043)
	at android.app.FragmentManagerImpl.executePendingTransactions(FragmentManager.java:799)
	at android.arch.lifecycle.f.aTm(SourceFile:42)
	at android.support.v4.app.SupportActivity.onCreate(SourceFile:67)
	at android.support.v4.app.FragmentActivity.onCreate(SourceFile:290)
	at android.support.v7.app.AppCompatActivity.onCreate(SourceFile:84)
	at com.android.messaging.ui.BugleActionBarActivity.onCreate(SourceFile:63)
	at com.android.messaging.ui.BlockedParticipantsActivity.onCreate(SourceFile:33)
	at android.app.Activity.performCreate(Activity.java:7009)
	at android.app.Activity.performCreate(Activity.java:7000)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1215)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2732)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2857)
	at android.app.ActivityThread.-wrap11(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1590)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6499)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:108)
Does anyone have the same bug?
 

BENETNATH

Senior Member
Jan 7, 2011
1,569
861
Hi
I've got the pleasure to use this ROM as daily driver.
Thanks again to all people involved , especially @Myself5
Today, I wanted to install novelist from play store, it's a writing app and I has a save feature inside. Sadly, I can't use it. I've asked to the coder and he told me that his app is using android storage access framework .
Is this feature available in cr?
Can anyone give a try and tell me if this is linked to my phone or the ROM ?

Thanks
 

hubert-bangol

Member
Jul 3, 2007
25
1
Hi
I've got the pleasure to use this ROM as daily driver.
Thanks again to all people involved , especially @Myself5
Today, I wanted to install novelist from play store, it's a writing app and I has a save feature inside. Sadly, I can't use it. I've asked to the coder and he told me that his app is using android storage access framework .
Is this feature available in cr?
Can anyone give a try and tell me if this is linked to my phone or the ROM ?

Thanks

Hello,

I've installed Novelist from Play Store and it is working very well (Xperia Z2C + CR last revision).
 

Attachments

  • Screenshot_Novelist_1.png
    Screenshot_Novelist_1.png
    44.2 KB · Views: 185
  • Screenshot_Novelist_2.png
    Screenshot_Novelist_2.png
    124 KB · Views: 189

CalveinX

Senior Member
Dec 31, 2013
132
35
34
Guarulhos
Anyone using MHL and/or Dualshock 3 (Sixasix App)?

Edit: Tried Sixaxis, sadly no support

Will try MHL later on, but some say it's only output 1080p30hz
 
Last edited:

okij

Senior Member
Oct 24, 2012
1,694
3,667
Düsseldorf
@Myself5: I just got a notification for the new cr-6.1 2019-08-24 release.

Is there a difference to the older 2019-08-11 release, like a newer Android security patch level?

The 2019-08-11 release still had June patch level, IDK if Google released a newer one in the meanwhile.
 
  • Like
Reactions: allerd

Myself5

Recognized Developer
  • Mar 17, 2011
    3,376
    9,648
    23
    myself5.de
    @Myself5: I just got a notification for the new cr-6.1 2019-08-24 release.

    Is there a difference to the older 2019-08-11 release, like a newer Android security patch level?

    The 2019-08-11 release still had June patch level, IDK if Google released a newer one in the meanwhile.
    nope.

    There are some issues with our filehost (BasketBuild.com) ATM and currently no access to the old builds, which is why we started a new build for all devices and uploaded them to our own server (depending on how that is doing that will probably stay the default setup, its faster anyways, lol).

    Though, we've decided to go the Lineage route and use their backport of the ASBs. We're currently working on merging them so the next scheduled builds will at least have August (probably September though) patchsets.
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 63
      IfblItr.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... and at CarbonROM Gerrit.

      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!

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

      We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.

      Get CarbonROM
      Changelog
      Join the CarbonROM Discord server
      GitHub
      Gerrit
      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: 8.x Oreo
      ROM Kernel: Linux 3.x
      Based On: AOSP

      Version Information
      Status: Stable

      Created 2018-04-01
      Last Updated 2018-07-19
      38
      User experiences and issue list for 2019-03-11 Release

      First of all, thanks to @Myself5, @rcstar6696 and all other members of the CarbonROM team for the release of CarbonROM 6.1 Oreo for our device! :good::victory:

      User experiences with CarbonROM 6.1:
      • Installation was smooth. I flashed cr-6.1 and OpenGapps ARM 8.1 on top of my working cr-5.1 installation (dirty flash), so all of my apps and their settings were kept. MindTheGapps 8.1.0 arm, which are recommended by the Carbon devs, are also working fine. Keep in mind that there is no guarantee that a dirty flash works in all cases, so you might have to wipe your data partition. This generally is recommended when updating to a new Android version anyway.
      • Besides of some small issues (see below), everything runs stable and the system is snappy and smooth. Thermal management and charging speed is fine.
      • Magisk 16.0 works fine, as well as Xposed Framework (SDK 27) v90-beta3 or alternatively Systemless Xposed (SDK 27) v90.1-beta3 Magisk module. However, there are some force-closes of background apps every now and then, caused by the beta status of Xposed v90.
      • My Xperia Torch Boost Magisk module is still working well on cr-6.1.
      • Selinux is set to enforcing, just as it was in cr-5.1.
      • I found out that Android Messages SMS/MMS app has a high battery drain, which e.g. is also reported for Pixel devices on Android 8 Oreo, so a general bug by Google. Because of this, I switched to Textra SMS (of course you can also use one of the other SMS/MMS apps around), which fixes the battery drain.

      Improvements in comparison to cr-5.1:
      • The camera button now acts exactly like in Sony Stock ROMs, so now focussing and taking pictures is possible with Stock Sony Camera. You can also invoke the Stock Sony Camera by long-pressing the camera button, just like in Stock ROMs, but this doesn't work when the device is off or locked. In this case you can use a double press on the power button, which can be enabled in Carbon Fibers settings.
      • Booting the device is noticably faster than on cr-5.1.
      • Lower battery drain than on cr-5.1.
      • Better, more uniform design.
      • The ROM is being updated to the latest Android Security Patches.
      • Apps can be "locked" in the Recent Apps, so when pressing the Clean All button, they keep running.
      • 4K video recordings are possible.

      Missing features in comparison to cr-5.1:
      • There is no option to turn on Network Traffic Indicators yet. (This has been added in 2018-04-05 Weekly.)
      • Default Camera-App does not allow to save photos to sd-card, puts photos in wrong orientation and is all around very limited. However, there are good alternatives like Open Camera and the Stock Sony Camera. (Since 2018-05-01 Weekly, Snap Camera is used again.)

      Issues in Carbon ROM 6.1:
      1. Video recording doesn't work yet with the built-in Camera app, as well as with several other apps like Open Camera and the Stock Sony Camera. Until this is fixed, you can use Footej Camera for video recording as a workaround. (This has been fixed in 2018-05-08 Weekly by @AdrianDC and Milos Ratkovic.)
      2. DoubleTap2Wake isn't working yet. (This has been fixed in 2018-04-11 Weekly.)
      3. The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. (See @Myself5's reply in post #14.)
      4. The gyroscope doesn't work properly yet with certain apps, e.g. Vr Tester - Gyroscope Sensor App and Accelerometer Gyro Tester. (Obviously this is a bug of those apps or of Oreo in general, since @Myself5 could reproduce it on his Pixel 2 XL device, running on stock ROM. Many other apps that use the gyroscope are working fine on cr-6.1.)
      5. Saving and accessing files on SD card doesn't work for certain apps and tools, which could be a Linux permission or SELinux denial issue. For further information and partial workarounds, see post #45, post #49 and post #51. (This has been fixed in 2018-06-05 Weekly.)
      6. Screen Cast still isn't working for me with 2018-04-11 Weekly (I tested this with a Sony and an LG Smart TV which both connected fine to my Z3c on stock ROMs), even with the new boot image from post #103 which is working with @Myself5's Fire TV stick and Wireless Display Adapter. This has been fixed in 2018-04-17 Weekly.
      7. WiFi isn't working on 5 GHz band in some countries, as has been reported in post #1634 on the Z2 cr-6.1 thread, including links to posts with possible workarounds and fixes. There's also an article in the xda wiki with further information. Since 2018-05-01 Weekly, Germany (DE) is used as Wifi country code, but there have been several reports by users from other countries that this doesn't work for them, so is not an universal fix. As a workaround, until this is fixed, you can use my Magisk module from post #195, which you have to change to your own country code by following the instructions that I gave there. Edit: @marcogiannetta posted an improved Magisk module in post #373 which changes the Wifi Country Code accordingly to the system language. A similar issue (wifi dosent connect in Iran) also has been reported on the bug tracker and is being looked after by the devs. Edit: According to post #2092 on the Z2 thread, this issue can also be fixed by installing WiFi regional problem solver Xposed module.
      8. Music files can't be played from SD card with Vanilla Music, Sony Music and several other players. This issue was fixed in 2018-05-08 Nightly, but reappeared on 2018-05-15 Nightly. Until this is fixed again, you can use jetAudio HD Music Player as a workaround. (This has quickly been fixed again in the 20180515-2340 Weekly build.)
      9. When making a screenshot via the Power menu, most of the time the Power menu itself is visible in the screenshot. There should be a slight delay (just 1/10th second might already be sufficient), so the Power menu is already hidden again before the screenshot is taken. This has been fixed in 2018-07-05 Weekly.
      10. Apps like Netflix, MyCanal and MagineTV don't work because DRM WideVine is not supported yet, whereas in CarbonROM 5.1 it was supported. This has been fixed in 2018-08-15 Release.
      11. Lock screen rotation has been removed since 2018-09-11 Release. It was a useful feature when using the phone in landscape orientation e.g. in a car holder and IMO should be added again. Edit1: As a workaround, I made LockscreenRotationEnabler Magisk module which adds this functionality by adding a setting to 'build.prop'. Edit2: Lock screen rotation can also be enabled with GravityBox [O] Xposed module.
      12. NFC extended length isn't supported, which is needed e.g. for reading identity cards with apps like AusweisApp2. (This has been fixed in 2019-03-11 Release.)
      13. NFC-HCE isn't supported, which is needed for Google Pay. (This has been fixed in 2019-03-11 Release.)

      Wish list for some further improvement of Carbon ROM 6.1:
      1. Long press camera button to wake and launch camera app when the screen is off or the phone is locked. Edit: I found a workaround which I described in this post.
      2. A toggle to switch to dark UI theme for quick settings. Edit1: The dark UI theme can be forced with ForceDarkModeOreo Xposed module. Edit2: ForceDarkModeOreo unfortunately is one of the Xposed module which cause random app crashes, so it's not advisable to use it. Let's hope that the devs will add this feature eventually.
      20
      I'll create a new thread in the upcoming days, but for now this should suffice:

      https://dl.myself5.de/z3c/CarbonROM

      SELinux is permissive and encryption is probably broken, also GPS seems a bit sketchy. Everything else works.

      You definitely need to cleanflash as there are different signing keys compared to the official builds used.

      Merry Christmas and Happy Holidays to all of you.

      P.S. To the Z3 users lurking: You'll get the same post in about an hour.
      P.P.S: I wouldn't recommend using this with Gapps ATM, they seem to make the phone horribly slow. I am looking into that.
      19
      In other news, @rcstar6696 got video recording stable and I fixed the media playback issue from external media.

      Both is merged and will be included in tomorrows Weeklies.

      P.S. That includes 4K and [email protected] Suck it, Xperia XZ1.
      P.S.2: There also is no green line in any recordings. Things Just work as you're used to ;)

      I also looked into the camera saving pictures on the external SD card as well as the 0 Byte copy issue. Camera seems to be fine now, and the 0 Byte copy issue is not happening when using the builtin File explorer or FX File Explorer. Fairly certain its an app introduced issue but I couldn't figure out what said apps might require to work properly.
      16
      Small update: new build will come later. The Gapps issue (which turned out to be a general issue with anything that requires a bit more cache) is fixed, and SELinux will be enforcing (mainly thanks to @drakonizer) I gotta finish up some SELinux rules for shinano specific (cam doesnt work atm) but I think I'm able to finish that up today.

      Big thanks to @okij for the donation :)

      EDIT: We found an issue with the camera where the camera is no longer working after you reboot. It only works on first boot. We're working on fixing it ATM. New build will come once that is fixed.
    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