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

Search This thread
By:
Advanced…
O

okij

Senior Member
Oct 24, 2012
1,695
3,668
Düsseldorf
Myself5 said:
... the next scheduled builds will at least have August (probably September though) patchsets.
Click to expand...

Yep, I can confirm that today's build has August patch level. Thanks a lot @Myself5! :cool:

BTW, I've two questions:

1. Could you include the patch for LZMA compressed recoveries that @NeoArian wrote of in this post for the next build (or has it probably already been merged)?

2. According to this post that I read on a ROM thread by @followmsi, there's a fix by Vladimir Oltean for MiraCast (which is still broken on cr-6.1 and most likely also cr-7.0). From what I found, it must be this commit and maybe also one or more of these commits: Link 1, link 2 and link 3. Could you please have a look at these commits and if possible merge them? It would be great if MiraCast could be fixed on CarbonROM too. :)
 
  • Like
Reactions: allerd, Klaus N. and casouzaj
K

Kockowan

Senior Member
Sep 7, 2010
274
37
Hello,
while trying to update to latest CARBON-CR-6.1-NOCT-RELEASE-z3c-20190911-0529.zip Z3compact does not reboot to recovery... :(
While phone reboot short time red led lights, afterwards violett led lights and previous CR-6.1 is booted.

Entering recovery by on/off button menu isn't possible too...
Entering recovery by power + Vol- doesn't work...

Where has the recovery been gone?

Latest Magisk-19.3 is installed too, root is available, no further problems (except the missing recovery).
Any hint how to reactivate recovery?

Edit:
I did restore recovery by Flashtool in fastboot mode, did try it with TWRP-3.2.1 and newer TWRP-3.2.3, but after flashing the recovery only recovery mode boots up, normal CR-6.1 system isn't bootable...

Thanks + regards!
 
Last edited:
O

odiad

Senior Member
Jun 12, 2007
197
17
Sony Xperia XZ2 Compact
Kockowan said:
Hello,
while trying to update to latest CARBON-CR-6.1-NOCT-RELEASE-z3c-20190911-0529.zip Z3compact does not reboot to recovery... :(
While phone reboot short time red led lights, afterwards violett led lights and previous CR-6.1 is booted.

Entering recovery by on/off button menu isn't possible too...
Entering recovery by power + Vol- doesn't work...

Where has the recovery been gone?

Latest Magisk-19.3 is installed too, root is available, no further problems (except the missing recovery).
Any hint how to reactivate recovery?

Edit:
I did restore recovery by Flashtool in fastboot mode, did try it with TWRP-3.2.1 and newer TWRP-3.2.3, but after flashing the recovery only recovery mode boots up, normal CR-6.1 system isn't bootable...

Thanks + regards!
Click to expand...

Hi, do you installed twrp in "fotakernel" ? In the past my twrp was also sometimes gone after flashing. I found anywhere a homepage where somebody described to flash it via fastboot:
fastboot flash FOTAKernel twrp-xxx.zip. out was a German homepage, found by "Z3 compact fotakernel"
But - I don't know if this works with each twrp-version.

To avoid trouble in flashing process I am used to modify updater-script in ROM. I delete anytime first sentences in this file until "ifelse". I am not sure if this effort makes sense, but from that point flashing never failed.
I flashed current version of room "dirty" and everything is okay (everything what I am doing with my mobile)

Greetings Odiad
 
K

Kockowan

Senior Member
Sep 7, 2010
274
37
odiad said:
Hi, do you installed twrp in "fotakernel" ? In the past my twrp was also sometimes gone after flashing. I found anywhere a homepage where somebody described to flash it via fastboot:
fastboot flash FOTAKernel twrp-xxx.img
Click to expand...
Thanks for that hint. It guides me to
https://github.com/topjohnwu/Magisk/issues/1418
Thre is a known issue with Magisk 19.x.
Fixing should be possible by accessing init/init_main.cpp:
https://github.com/koron393/android...mmit/5be3e4b2723da9233f4f638ca4a5d0e515453442
But how to access/correct this file by adb.exe on phone or in TWRP-recovery.img by editing?

Any hint? Thx...
 
fablerbjörn

fablerbjörn

Member
Aug 6, 2019
5
3
I am using the latest version, CARBON-CR-6.1-NOCT-RELEASE-z3c-20190911-0529.
Screen auto-rotation stops working in about 4-5 hours after boot and is only fixable by rebooting.
Can this be fixed?
 
  • Like
Reactions: odiad
O

okij

Senior Member
Oct 24, 2012
1,695
3,668
Düsseldorf
@Myself5: Could you give us some feedback for those questions / suggestions that I posted two weeks ago? I'm not sure if you've missed them. TIA! :)

okij said:
1. Could you include the patch for LZMA compressed recoveries that @NeoArian wrote of in this post for the next build (or has it probably already been merged)?

2. According to this post that I read on a ROM thread by @followmsi, there's a fix by Vladimir Oltean for MiraCast (which is still broken on cr-6.1 and most likely also cr-7.0). From what I found, it must be this commit and maybe also one or more of these commits: Link 1, link 2 and link 3. Could you please have a look at these commits and if possible merge them? It would be great if MiraCast could be fixed on CarbonROM too. :)
Click to expand...
 
  • Like
Reactions: 0LDST4R and liberteus
S

sabotage154

Senior Member
Apr 24, 2011
113
7
is always on vpn > block vpn supposed to work on this ROM? i have it setup but when i disconnect from VPN, i get the always on VPN notification on the OS but the stock carbon rom browser still has access to the network. Is this feature supposed to work or that feature doesnt work on these ROMS?
 
linolino

linolino

Member
Aug 4, 2008
43
8
Nuremberg
Hi anybody an idea how to fix
- do not remember what might be the last action which f**ked up my system.
- had last Oct Rom active (incl. Magisk 19.3, EdExposed) -- ofcoures no TWRP backup

On a maintenance reboot...did wipe (was set to rm -rf) Cache/Dalvik in TWRP...
but boot of system failed just went to TWRP [3.2.3-0] again (all the time I tried)

Hence logcat was not really helpful for me
-wiped again ...
-removed SD card, rebootLoopTwrp
-removed SIM card, rebootLoopTwrp
-used "mm" MagiskManager Console to deactivate modules, rebootLoopTwrp

Twrp on start is not asking for my PIN, do not remember, should it ask me??

-did wipe of system and installed oct 11th + gapps -- still rebootLoopTwrp

stuck for >two weeks already

Any advice (not having to kill my DATA partition, preferably)?

Thanxx
lino
 
B

betacrypt

Senior Member
Jan 17, 2018
290
141
Thank you so much for continuing to update this rom + latest security patches. It runs beautifully on my device and the battery life is fantastic. I'm not a fan of Pie or 10 - this rom is the best option imo!
 
  • Like
Reactions: nikapos and okij
B

BardoM

Member
May 14, 2018
7
6
Hello everyone.

I've just installed a CarbonROM in a recently acquired xperia z3c and apparently everything was ok:
- I unlocked bootloader.
- I flashed twrp-3.3.1-0.4-z3c.img from here in FOTAKernel.
- I installed last CarbonROM, GApps and Magisk.

Until now I had only entered recovery via hardware reboot (pressing the power ON and volume DOWN buttons), or fastboot via pressing volume UP button and connecting USB cable....
but right now I realize I cannot reboot recovery via:
- power menu
- pressing Vol-Down key when the pink LED light shows
- adb reboot recovery
In every case the device reboots system but not recovery. Same case for 'adb reboot fastboot'.

I thought the problem would be magisk but uninstalling magisk doesn't fix anything.

Any clue what is happening?
Thanks.
 
NeoArian

NeoArian

Recognized Developer
    • Nov 25, 2017
    1,261
    2,861
    Sony Xperia Z2
    Sony Xperia Z3 Compact
    BardoM said:
    Hello everyone.

    I've just installed a CarbonROM in a recently acquired xperia z3c and apparently everything was ok:
    - I unlocked bootloader.
    - I flashed twrp-3.3.1-0.4-z3c.img from here in FOTAKernel.
    - I installed last CarbonROM, GApps and Magisk.

    Until now I had only entered recovery via hardware reboot (pressing the power ON and volume DOWN buttons), or fastboot via pressing volume UP button and connecting USB cable....
    but right now I realize I cannot reboot recovery via:
    - power menu
    - pressing Vol-Down key when the pink LED light shows
    - adb reboot recovery
    In every case the device reboots system but not recovery. Same case for 'adb reboot fastboot'.

    I thought the problem would be magisk but uninstalling magisk doesn't fix anything.

    Any clue what is happening?
    Thanks.
    Click to expand...

    This problem is caused by the recovery ramdisk compression method. In new twrp builds for this device we usually use LZMA but that isn't currently supported by CarbonROM's sony init. You can not do much yourself, except using an old TWRP with gzip compression or wait until https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923 is getting merged into carbonrom.
     
    • Like
    Reactions: okij, BardoM and chillma
    You must log in or register to reply here.

    Similar threads

    Myself5
    [10][OFFICIAL] CarbonROM | cr-8.0 [z3c]
    Replies
    104
    Views
    15K
    A
    ascendant512
    Myself5
    [9][UNOFFICIAL][BETA] CarbonROM | cr-7.0 [z3c]
    Replies
    102
    Views
    23K
    Myself5
    Myself5
    NeoArian
    [OFFICIAL] LineageOS 17.1 for z3c
    Replies
    228
    Views
    27K
    7
    7ig3rsh4rk
    NeoArian
    • Locked
    [EOL][ROM][Z3C][OFFICIAL] Resurrection Remix-OS 6.2.0 [A8.1.0]
    Replies
    125
    Views
    30K
    engloa
    engloa
    squabbi
    • Locked
    [ROM][OFFICIAL] CyanogenMod 12 Nightlies for the Xperia Z3c
    Replies
    11
    Views
    30K
    gregbradley
    gregbradley

    Top Liked Posts

    24 Hours All time
    • There are no posts matching your filters.
    • 63
      Myself5
      Myself5
      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
      View
      38
      O
      okij
      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.
      View
      20
      Myself5
      Myself5
      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.
      View
      19
      Myself5
      Myself5
      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.
      View
      16
      Myself5
      Myself5
      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.
      View

    New posts