TWRP flashed to the FOTAKernel partition can only be accessed by hardware means. Starting with the phone powered off, hold both the power and the volume down buttons. When the phone vibrates (as if it was being turned on), release the power button; when the screen lights up, release the volume down button.
Sent from my Sony E5823 using XDA Labs
Cr-8.0 or Android 10 must have drilled some holes into the battery of my phone.
Lost 30% of capacity in 8 hrs over night only in standby. Didn't open any app and not only one background task was running.
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.
+ 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
- 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 (bug or feature?)
- 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
4) unlock instantly when entering last digit without confirmation
5) long press power button to turn on/off torch while display turned off
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.
Hmm... I was on LOS 17.1 (prior to CR 8.0), and sound volume (ringtone and alarm) felt a bit louder there. May be it's just my personal impression, not sure... I will not backup/restore just to test this.
But with GravityBox it not stops accepting digits after last one (if some of entered digits wrong) - I just checked. So thief will not know the lenght. AOSP devs could have fix it instead of removing.Also the fourth feature that you would like to have, was removed from AOSP and is missing since Android Nougat times, because of security concerns. It was/is dangerous because when user have - lets say 4 digit pin - and passes to many digits while unlocking the phone, it stops accepting them right after the 4th digit is passed. This behavior gives information about pin length to potential thief. It narrows down the range of possible pin codes combinations which unlock device.
But with GravityBox it not stops accepting digits after last one (if some of entered digits wrong) - I just checked. So thief will not know the lenght. AOSP devs could have fix it instead of removing.
Well, I just entered wrong PIN (random digits and press ENTER) 4 times and got penalty (see screenshot). It looks like GravityBox somehow ignore this "penalty" ONLY if you enter PIN without enter (confirmation button). For successfull bruteforcing thief should know that I could using this feature in my phone (and this is possible only if thief is friend of mine, who I told about this feature, or he is also reading this thread and has physical access to my phone, or he's goddamn genius... looks like almost impossible situations ) And in my case (Im not using encryption atm) genius-thief can easily access my data without bruteforcing anythingThat is by far a lot worse. Without the system going into a "this is wrong" state theres never a situation in which to reach "too many false attempts" allowing for easy bruteforcing of the PIN without any penalty.
Oh, yep, sorry my fault. Updated my review.As for your feature requests: both, PIN scrambling as well as longpressing the powerbutton for the torch already exist.
Dirty flashed today´s build over the 0527 one. No problems with the back camera here, in any of those releases.Dear guys,
thanks for you effort in building this ROM.
Did a clean install and everything worked fine, except main camera.
Selfie cam worked fine, but main camera did not, only showed black picture.
Tried with built in cam software and OpenCamera as well - same result.
Flashed LOS17.1 - everything worked fine as well as both cameras, no problems here.
Dirty flashed today´s build over the 0527 one. No problems with the back camera here, in any of those releases.
You`re rom works very fine, I'm using it since may! Thank you!
I've only one issue (using actual build from 20200617).
After I enable bluetooth the phone isn't going into deep sleep nomore, because of kernel wakelocks 'BTLowPower'. Also after disable bluetooth. Only restart the phone helps. Any tips?
Did you check with BetterBatteryStats (https://forum.xda-developers.com/t/app-2-2-05-oct-v2-4-betterbatterystats.1179809/)?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
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.