[ROM] LineageOS 14.1 (official) - ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other

[ROM] LineageOS 14.1 (official) - ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other

Can this be flashed with current twrp?

Absolutely, that's what I did. Use sideload.
MrWhite0429 said:
Can this be flashed with current twrp?
Click to expand...
Click to collapse

Can't wait for those issues to be fixed so I can use it. Surprises me how fast you're working tdm

EEEEE I LOVE YOU
thank you so damn much tdm, i was scared this phone would be developmentally dead

Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
A 'Clean' install consists of the following:
Factory Reset (or manually wipe (format) Data partition - Internal Storage wipe is NOT necessary)
Manually wipe (format) your System partition <-Unnecessary
Flash your ROM
Flash GApps package <-Use opengapps arm64 7.1 micro
Flash SuperSU v2.79 <-Use the arm64 version of SU found on the LineageOS website
Wipe the Dalvik & cache <-Unnecessary
Reboot (Because of the SuperSu install, there may be a bootloop or two. It also warned me before I rebooted that I didn't have an OS installed, even though I did.)
NOTE: YOU WILL LOSE ALL OF YOUR DATA AND APPLICATION SETTINGS using this method. Be sure to do a NANDroid backup prior in case you want to restore later.
Click to expand...
Click to collapse

Glad someone else got it to work, and thanks for the instructions. Note formatting /system is not necessary, neither is wiping cache or dalvik.
If you want su, lineage has a flashable root package. Check on their site. SuperSU may work but it's not supported in any way.
I'll check the WiFi stuff, I probably missed a config or calibration file or something.
The in-call audio is probably an issue in the amplifier code. I just got that working yesterday, so no surprise there. Fix should be relatively easy.
mattx1002 said:
Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
Click to expand...
Click to collapse

I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!

tdm said:
I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!
Click to expand...
Click to collapse
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)

mattx1002 said:
LTE works perfectly fine
Click to expand...
Click to collapse
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.

Thanks I got it. I used the amp parameters from your log but still can't get in-call audio. Need to keep looking....
maestromony said:
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)
Click to expand...
Click to collapse

Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse
I'm on T-Mobile.

I'm on AT&T. LTE works for me.
Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse

Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?

Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
tdm said:
Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?
Click to expand...
Click to collapse

mekzmaz323 said:
Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
Click to expand...
Click to collapse
I agree. I'm fine with it being the same.

WiFi and lte
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
tdm said:
Here at long last, Lineage 14.1 for the Axon 7 Mini!
... I'll fill this post out more later ...
Current status: Alpha
Currently supported devices:
US variant (tulip) running 7.1.1 b14 firmware.
Known major issues:
Phone audio doesn't seem to work.
Bluetooth audio stutters incessantly, unusable.
Notification LED doesn't work.
Cannot seem to get NFC to work.
Known minor issues:
WiFi mac addr isn't set properly.
WiFi connection seems a bit flaky. (?)
Download:
lineage-14.1-20171019-UNOFFICIAL-tulip.zip
MD5=5b4ca59d5b9f69e59dc44ba28637b71a
Tested with opengapps arm64 7.1 micro.
Sources:
device_zte_tulip
kernel_zte_msm8952
Click to expand...
Click to collapse

These are known issues except for LTE. My LTE works fine and I have reports that others do also.
CRAFTER0302002 said:
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
Click to expand...
Click to collapse

Today's build is up, with handset audio working!
I think the volume adjustments may need work, but I do hear audio.

I'm off work tomorrow so I may stay up tonight and give this a try! In anyone's opinion is this stable or suitable for daily use?

Related

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

[ROM][STABLE][R7S/R7Sf][OFFICIAL][9.0] LineageOS 16.0 (Qualcomm)

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Devices supported by this package :
Officially: Oppo R7S ( R7Sf / R7Sfg / Snapdragon Model Only! )
What's working :
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
GPS
What's not working :
Instructions :
Official Instructions here in LOS Wiki.
Download the latest build and gapps arm64 for 9.0
Open GApps (choose the variant you want. Recommended nano package)
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds
ROM : https://download.lineageos.org/r7sf
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
Phone model (R7Sf, R7Sfg):
LOS version:
LOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
LOSSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
[MENTION]My wife[/MENTION]: For her patience
[MENTION]Uberlaggydarwin[/MENTION]: For you know what!
[MENTION]mikeioanna & maniac103[/MENTION]: For all their amazing work on the R7 series!
Unknown Oppo Dev: For providing the PS Kernel Source Code
LineageOS Team
Donations :
Please consider donations to support development.
mikeioannina: Donating via PayPal without him LineageOS 16.0 for the R7sf would not have been possible!
XDA:DevDB Information
LineageOS-16.0 for Oppo R7S (1080p), ROM for the Oppo R7S
Contributors
mikeioanna,maniac103,celoxocis
Source Code: https://github.com/LineageOS
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.10.108
ROM Firmware Required: Unlocked bootloader
Based On: LineageOS 16.0
Version Information
Status: R7Sf entered Official builds.
Created 2019-04-17
Last Updated 2019-04-17

*reserved*

Please make sure before upgrading to LineageOS 16.0 to read the Official Instructions here in LOS Wiki carefully!
Make sure before flashing you upgrade the TWRP version with the one provided in the instructions page due to changes to support hardware accelerated encryption on our R7S!
You will run into issues if you do not upgrade to the provided TWRP version!
I recommend a clean install due to above changes.

Followed the instruction exactly but wifi does not work (mac address 02:00:00, it can not find any AP...)
If someone has this issue like me, flash back to Spectrum then boot into it and connect to some AP, then flash LineageOS again, but do not wipe anything.

Does Pixel Launcher work for you?
It crashes on my phone. A workaround: https://www[.]reddit[.]com/r/LineageOS/comments/awjvnk/lineageos_16_stock_open_gapps_pixel_launcher/

Working well so far even though I updated using twrp 3.2.3
Only issues are, app permissions seem to show up when they want and bluetooth connection can be ropey depending on device. Have one receiver with no issues but my Sennheisers cant keep a connection from two feet. Will try re-pairing.
Thanks to you all. :highfive:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?

LordAlberto said:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?
Click to expand...
Click to collapse
Why not use Magisk?

trmdi said:
Why not use Magisk?
Click to expand...
Click to collapse
I do use magisk, I need to install this beforehand or magisk doesn't work.
When I first installed 16, I read that lineage removed the su binaries so there is no root out of the box.
Bit of a pain really.

When the screen is locked, you're still able to swipe down from the status bar to expand it to show buttons. Is there any way to disable expanding the status bar when the screen is locked?

Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?

Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/

Luuta said:
Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?
Click to expand...
Click to collapse
The recommended TWRP image is actually a lower version than the official image through the TWRP app, and that's why my recovery got screwed up. I'd flashed an earlier image onto a later one. The recommended one would probably be the one to use if you were switching to Lineage for the first time, maybe? Just to warn people not to be as careless as I am!
I spent half a day messing about with getting the tools again to perform a flash from my pc. Every time, I end up relying on "Minimal ADB & Fastboot" because I have no luck getting any other driver package to work. But this package really is the smallest pack to get it done and it makes it easy to use, thank goodness.
Thanks to the developers for continuing to work on the phone. I'm loving Android 9/Lineage 16. There isn't much of a visual change, which is great. Under the hood, it's more obvious, but it's definitely running much smoother than L15 already.
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
trmdi said:
Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/
Click to expand...
Click to collapse
There will, of course, be changes, or it wouldn't be offered. Most changes are bug fixes or security updates, so you wouldn't necessarily notice any change.

Maybe the gestures are sensitive but every time I go out, the phone always opens my music player at destination. Have turned them off see if it happens again.
Never happened on 15.

Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...

LordAlberto said:
Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...
Click to expand...
Click to collapse
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...

Luuta said:
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...
Click to expand...
Click to collapse
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.

LordAlberto said:
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.
Click to expand...
Click to collapse
Ah, yes, it loses the pairing in our car, too. It's a small annoyance, can live with that!

is anyone success to install magisk on this rom ?

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
yes. I flashed it right after flashing the rom without any problem.

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
On page one of this thread I've linked the su code to get magisk to install.

[How-to] Install GSI-A roms (Ulefone Armor 6)

I started fiddling even more with installing GSI-A partitions roms into the Ulefone Armor 6 as of today. Here's how you install GSI-A roms. I have tried roms from Android 8-10 official & unofficial. Lineage, RR, Pixel Experience, & etc...
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
I did not fully test with 100 certainty these GSI-A roms below. Even the ones below that I did test have many bugs/issues. The ones below were the ones that booted correctly for me. Test at your own discretion. Some of these roms wont have SU & GAPPS.
Prerequisites:
Make sure you have an unlocked bootloader.
Make sure your phone has, TWRP installed.
Make sure you have drivers installed, here.
Fastboot & ADB tools, here.
Rom's I've tested & boot on Armor 6:
Android 10
1. (AOSP) Android 10 by phhusson
2. PixelExperience 10.0 BETA by ExpressLuke
3. Havoc OS 3.0 by ExpressLuke
Android 8
4. Resurrection Remix by phhusson
Any other GSI-A roms being supported can be found here, feel free to try out your own if you feel like it.
Installation:
1. Place your device in, "Fastboot mode"
2. Open up command prompt (cmd) on your computer, cd into the folder where fastboot & adb is in, and type, "fastboot erase system"
{
"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"
}
3. Now flash the GSI-A image to your Armor 6 system partition. "fastboot flash system (what ever your system name).img"
4. This following command will format userdata & cache. "fastboot -w"
5. Last but not least step using fastboot, is to reboot your device. "fastboot reboot"
Now, pay attention.
When you flash the system image to your device, it only flashes the minimum data size that comes with the image. You have to reboot into TWRP, Resize /data partition & format to EXT4 to get the full 128GB partition size.
6. Boot into TWRP. To do this, power off the device and press both the, "Power button + Volume up button" at the same time during which you should see the bootloader menu. To move between options to have to press the volume up, until you are hovering over, "recovery" option. Then press volume down, to select recovery and boot into it.
7. Select the, "wipe" option.
8. Select & check mark, "Data" first, then secondly, select, "Repair or change file system."
9. Resize the data partition.
10. Now change the file system format, to, "EXT4"
Now reboot the phone
That's all there's to it. Not all GSI-A images will work, if they don't work, the developer of that GSI-A has to make it so. Good luck.

thanks dude, are roms working without bugs? mobile network and gps working?
Weekend I will try to install the Ressurection Remix or Pixel Experience (10), I'm still in doubt rsr, and bring news if it's working well with me. thanks!

What is the current method we are using to bypass dm-verity?
Thanks a ton for your work.

Pergmen said:
What is the current method we are using to bypass dm-verity?
Thanks a ton for your work.
Click to expand...
Click to collapse
I format the partitions to ext4 and flashed the dm-verity zip. I'll send you the link once I get home.

SMAAALLL BR said:
thanks dude, are roms working without bugs? mobile network and gps working?
Weekend I will try to install the Ressurection Remix or Pixel Experience (10), I'm still in doubt rsr, and bring news if it's working well with me. thanks!
Click to expand...
Click to collapse
The AOSP 10 by phh, has a bug that I came about, that my computer couldn't detect my Armor 6 device. So unless you have a wireless app, you cant transfer files locally as of this version.
Pixel Experience has a bug, that you have to register your device as a custom rom with google. Otherwise the device can't download Google Play Store apps. I am currently running this version. I'm testing it more. I didn't test Havoc completely, but it doesn't come with Google Play Store.

Extosis said:
The AOSP 10 by phh, has a bug that I came about, that my computer couldn't detect my Armor 6 device. So unless you have a wireless app, you cant transfer files locally as of this version.
Pixel Experience has a bug, that you have to register your device as a custom rom with google. Otherwise the device can't download Google Play Store apps. I am currently running this version. I'm testing it more. I didn't test Havoc completely, but it doesn't come with Google Play Store.
Click to expand...
Click to collapse
oh, so I'm going to test Remix 9.0, I need USB working to test applications I develop.
Sent from my Armor_6 using Tapatalk

Unlocked the bootloader (After flashing to stock once) and flashed the following roms. Device is 6E:
PixelExperience
Resurrection Remix
UltraSuccRom
Bootloop on every one. All were ARM64, A bootable.
Interestingly, I couldn't get TWRP to boot/stick this time, either. Perhaps the official image is different? I have flashed to stock again and will go through the process of obtaining root. I will report back if flashing recovery with the TWRP app is successful.
[Update] TWRP installed through the TWRP app and can be booted through adb. I was able to successfully bypass DM-Verity. Attempting to boot into TWRP using key combinations apparently results in a system hang. I Will attempt flashing images with TWRP next.
[Update 2] No success with TWRP or Fastboot. Returning to stock...

does anyone have a link to dm verity to armor 6? thanks
Sent from my Armor_6 using Tapatalk

Pergmen said:
Unlocked the bootloader (After flashing to stock once) and flashed the following roms. Device is 6E:
PixelExperience
Resurrection Remix
UltraSuccRom
Bootloop on every one. All were ARM64, A bootable.
Interestingly, I couldn't get TWRP to boot/stick this time, either. Perhaps the official image is different? I have flashed to stock again and will go through the process of obtaining root. I will report back if flashing recovery with the TWRP app is successful.
[Update] TWRP installed through the TWRP app and can be booted through adb. I was able to successfully bypass DM-Verity. Attempting to boot into TWRP using key combinations apparently results in a system hang. I Will attempt flashing images with TWRP next.
[Update 2] No success with TWRP or Fastboot. Returning to stock...
Click to expand...
Click to collapse
My guide is for the Armor 6.
If I am not mistaken, I believe the Armor 6E has an A/B partition scheme. You can always check with the Treble Checker app on stock OS.

Extosis said:
My guide is for the Armor 6.
If I am not mistaken, I believe the Armor 6E has an A/B partition scheme. You can always check with the Treble Checker app on stock OS.
Click to expand...
Click to collapse
Unless it's wrong.

Pergmen said:
View attachment 4866669
Unless it's wrong.
Click to expand...
Click to collapse
Use A/B treble check gives A forsome reason but A ones dont work..

Pergmen said:
View attachment 4866669
Unless it's wrong.
Click to expand...
Click to collapse
Try, an GSI-A/B.
Let me know how it goes.

Extosis said:
My guide is for the Armor 6.
If I am not mistaken, I believe the Armor 6E has an A/B partition scheme. You can always check with the Treble Checker app on stock OS.
Click to expand...
Click to collapse
Extosis said:
Try, an GSI-A/B.
Let me know how it goes.
Click to expand...
Click to collapse
View attachment 4868641
Yep, Treble Checker was wrong. The Armor 6E is a/b. Thank you once again.

Pergmen said:
View attachment 4868641
Yep, Treble Checker was wrong. The Armor 6E is a/b. Thank you once again.
Click to expand...
Click to collapse
Nice! I'm so glad it worked!

Have you found any ROMs with working speakers? I haven't found any where the ringer or speaker is working.

Well, RRemix of this link was just the "bios screen", did I do something wrong?
I was able to install the latest Pixel Experience BETA and apparently it is working, I will test it in the next few days, USB is working normally.
update:
Not working NFC, Google Chrome, Rear Speaker, instagram and facebook videos lock the image and only play the audio.

SMAAALLL BR said:
Well, RRemix of this link was just the "bios screen", did I do something wrong?
I was able to install the latest Pixel Experience BETA and apparently it is working, I will test it in the next few days, USB is working normally.
Click to expand...
Click to collapse
Apparently the player is muted, I'm afraid of rebooting entrat in boot loop.
Has anyone tested the latest PixelXp and rooted?
---------- Post added at 02:08 PM ---------- Previous post was at 01:10 PM ----------
miklaw said:
Have you found any ROMs with working speakers? I haven't found any where the ringer or speaker is working.
Click to expand...
Click to collapse
I'm also without audio.
@Extosis, which system are you using?
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------

Anyone tested the latest havoc 3.0?
updates:
-PixelExperience 10 ExpressLuke 28-10-2019:
fluid, a more stable, speaker does not work, nfc does not work, bluetoth works, headset works, insta / face videos only plays audio, some apps do not work, is the best I have tested;
-PixelExperience 10 ExpressLuke 16-10-2019:
unstable, not registered with play protect, speaker doesn't work, headset doesn't work, crashed and couldn't test anymore;
-Havoc 3.0 latest 10-11-2019;
fluid, less stable than pixel, no gapps, nfc apparently works, no speakers;
-RRemix phhuson gapps:
it's just the ulefone boot screen
-Evolution, Havoc2..9 and RRemix 7.0.3:
bootloop
I could not download any rom hosted on GitHub, very bad server, but I am going back to Stock while not updating update for PixelXP, I could not boot any rom from android 9 and all that flashed openGapps bootloop
edit:
If you are testing and finding solutions, please give feedback.
any android pie working well?

Are all Armor 6 devices without sound or only some? The 6E has sound on both AOSP and PixelExperience, if that information helps at all with figuring out the problem.
Observed issues with GSI images for 6E users (Tests ended November 9th):
-Spazzy GUI elements, specifically gifs and videos embedded in apps (It's pretty funny though)
-Extremely inaccurate battery charge reporting (Especially on PixelExperience, possibly unsafe)
-Cannot receive incoming calls (I'm on Verizon's network, which shouldn't be working to begin with, so your mileage may vary)
-Only boots once. Clearing the data partition is necessary to boot again.
-Screencasting (Doesn't work on stock either)
Observed working:
-Bluetooth audio
-Graphics processing unit
-Storage access on Windows over USB
-External Speaker and headphone output
-Camera and flash (Makes an audible click when closing on both GSI roms and stock. Strange.)
-All Play Store apps (That I tested)
-SMS, outgoing calls
The more information we have out there, the closer we get to... whatever we're trying to accomplish. Best of luck everybody.

Pergmen said:
Are all Armor 6 devices without sound or only some? The 6E has sound on both AOSP and PixelExperience, if that information helps at all with figuring out the problem.
Observed issues with GSI images for 6E users (Tests ended November 9th):
-Spazzy GUI elements, specifically gifs and videos embedded in apps (It's pretty funny though)
-Extremely inaccurate battery charge reporting (Especially on PixelExperience, possibly unsafe)
-Cannot receive incoming calls (I'm on Verizon's network, which shouldn't be working to begin with, so your mileage may vary)
-Only boots once. Clearing the data cache is necessary to boot again.
-Screencasting (Doesn't work on stock either)
Observed working:
-Bluetooth audio
-Graphics processing unit
-Storage access on Windows over USB
-External Speaker and headphone output
-Camera and flash (Makes an audible click when closing on both GSI roms and stock. Strange.)
-All Play Store apps (That I tested)
-SMS, outgoing calls
The more information we have out there, the closer we get to... whatever we're trying to accomplish. Best of luck everybody.
Click to expand...
Click to collapse
That actually helps guide me in the right direction, thanks!

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

{
"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"
}
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

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.

Thank you very much for supporting our cute device
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?

Found a BUG: can't set PIN/pattern to lock screen, getting bootloop after try to set it and reboot.
I use z3c as my daily driver, so I need screen lock, can't use this ROM until fixed. Hope I'm not only one who faces this bug.
BigBrother84 said:
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Click to expand...
Click to collapse
Not sure about these apps, but at least GravityBox[Q] and App Locale 2 I can NOT get working on this ROM with EdXposed v0.4.6.0_beta(4471) (YAHFA). As well as on latest february build of LOS 17.1 (but worked fine on january build). May be I should try some newer versions of EdXposed (like ones from "canary" repo or something), but I need screenlock bug fixed first to use this ROM and more of free time. Btw, everything works perfect on LOS16.

Hooin Kyoma said:
Wiped all except micro sd. Stuck at "Setup wizard keeps stopping", system unusable. With and without gapps.
Ok I just clean-reinstalled ROM and made first boot WITHOUT SIM CARD INSERTED and it's boot fine. Btw my SIM card PIN-locked (if it's important) and it never caused any problems in LOS17.
Also I reserve this post for my review.
Thank you @Myself5 for continue work with our lovely z3c.
Click to expand...
Click to collapse
The Setup Wizard is still work in progress, and we just discovered nobody tested it with a SIM so far. We'll take care of it, thanks.
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?

Myself5 said:
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Click to expand...
Click to collapse
Tried with and without encryption. With and without Gapps. With and without SIM card. Always same result. Everytrhing fine until you set screen lock PIN either from Setup Wizard or from Security settings. First of, unlock method stays "Swipe" after set PIN. And if you reboot, system's boot to desktop and auto-soft-reboot (without sony logo) after few seconds. And yes, this not happening on LOS17.1

Installation immediately fails for me.
Code:
Patching system image unconditionally...
E1001: Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200208-1428.zip'[/COLOR]
Updating partition details...
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
Failed to mount '/appslog' (Invalid argument)[/COLOR]
...done
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
E:Error creating fstab[/COLOR]
Tried to update from your previous CR7 build (CARBON-CR-7.0-OPAL-UNOFFICIAL-z3c-20190819-2110), using TWRP 3.2.1 from here. Nothing actually got written, so previous installation is fine.

yxagasasgas said:
using TWRP 3.2.1
Click to expand...
Click to collapse
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.

Hooin Kyoma said:
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Click to expand...
Click to collapse
Doesn't work for me, just blackscreens and reboots. Tried installing it both via TWRP app and fastboot (although strangely enough, even though adb worked, fastboot didn't in Windows, had to boot to Linux), no dice, so went back to my previous TWRP for now.
Would be nice to know what's up with that, but I haven't fiddled with any of this in a long time. Ever since CarbonROM appeared, my Z3C pretty much "just worked" and I never had to do much of any fiddling.

New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.

Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
f8d3b9c5519b91baba7a917d99b7f09e CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200225-1530.zip

Myself5 said:
PIN issue is fixed
Click to expand...
Click to collapse
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.

Hooin Kyoma said:
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
the camera was not working for me as well, but after some restarts it fixed itself. i dont know how that happened (even tried the xperia camera port from magisc) but i cannot confirm weather that did the trick..

Hooin Kyoma said:
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.

okij said:
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
Click to expand...
Click to collapse
Thanks for the tip mate. But it didn't help in this case.
Btw, today I installed (again) latest LOS17, tuned it, rebooted many times, played with microG/magisk/xposed modules - camera worked fine all the time.
Next (steps to reproduce): wiped cache, dalvik, data and system, installed only CR-8.0 (20200225), rebooted to system, skip anything, camera WORKS! Did nothing, just rebooted again, and got "Can't connect to the camera"! I think this is a BUG and hope I'm not the only one who faces it.
I still have a question about Carbon Fibers menu, why it lack items/options? I can't even reposition statusbar clock to right without using "third-party" apps like GravityBox xposed module.
Also, kind of "feature request": time to time I use adb from PC (we all do i think), and I hate to connect cable to micro-USB port, cuz it's weak and can break soon if use freqently. I use magnetic port/cable for charging and "ADB over network" toggle in Developer Options for ADB operations. One of the reasons why I prefer LOS is because of this "must have" thing, they even have tile in QS for toggle it quickly! Can it be added to CR?

the "cant connect to the camera" returned unexpectedly..

Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?

Thank you for your hard work!
Does encryption work properly?
What works
Viper4android works
Sony Device Dummy works with official Sony apps
Spotify works

Myself5 said:
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Click to expand...
Click to collapse
Great, this looks interesting indeed!
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1 (because everything is working well and rock stable on this older version and thankfully you still release monthly security patches for it.)
Have you done some thorough testing of cr-8.0 on the Z3/Z3c devices before making it now official and is everything working (e.g. full camera support and proper in-call audio, which had problems on shinano devices on Android 9 and 10 before)?
If so, I might give it a try this weekend.
Thank you and keep up the great work! :good:

okij said:
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1
Click to expand...
Click to collapse
I tried dirty-flash on my cr-6.1, but without success - I can't boot my phone because it stuck in boot animation.

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz

So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.

mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now

lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !

[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo

Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.

Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"

Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/

I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.

mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?

@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.

@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse

&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.

betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.

@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?

Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.

betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD

Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build

Database Info

welcome