[OFFICIAL] LineageOS 17.1 for Xperia Z3 [CLOSED] - Xperia Z3 Original Android Development

[OFFICIAL] LineageOS 17.1 for Xperia Z3 [CLOSED] - Xperia Z3 Original Android Development

Thread depreciated. There won't be anymore official LOS 17 builds for this device.
Please jump to:
The official LineageOS 18.1 thread for z3 or dedicated thread for z3dual
if you are looking for new builds.
-------------------------------------------------------------------------------------------------------------------------
{
"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 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project (AOSP) and can be used without the need to have any Google application installed.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below. There are also inofficial TWRP recovery builds available - if you want to use TWRP you need to ensure that it is compatible with Android 10.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Detailed instructions:
Install LineageOS on z3
Downloads:
Final official build of 17.1 ROM for Z3:
Google Apps (optional): Open GApps (choose ARM as Platform and Android 10)
Changelog:
Changes for z3
Source Code
The source code of LineageOS is available here. If you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The z3 device tree is available here.
The kernel source code for this device is available here. The used configuration is lineageos_shinano_leo_defconfig available at arch/arm/configs/lineageos_shinano_leo_defconfig in the kernel source.
Bug reports:
How to submit a bug report - Please do not submit anymore bug reports for 17.1 - try 18.1 first please.
LineageOS GitLab
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
Thanksgiving
Thanks to everyone who ever contributed to the custom development for this device, especially:
@nailyk
@rcstar6696
@tomascus
@Diewi
@xkeita
@drakonizer
XDA:DevDB Information
LineageOS 17.1 for Xperia Z3, ROM for the Sony Xperia Z3
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12

Remarks, Questions & Answers
Known Major Issues
Official Lineage Recovery is currently broken. There are two options:
TWRP recovery (inofficial build, optional): TWRP
Unofficial Lineage Recovery build.
WiFi issues in some countries (e.g. Iran): low speed @ 5GHz, hotspot and connection issues. This topic is related to a dirty workaround. A solution is here but will not be integrated into our official Lineage kernel.
Disk Encryption: Disk Encryption is working, however not with the default password (no password). Workaround: Set password first, then start disk encryption, not the other way round! Solved
Bluetooth Low Power may create wakelocks in certain scenarios.* Solved
Thermal throttling of CPU cores: Due to a design issue of the thermal manager ("Thermanager") when used with older kernels like ours you have to expect that the frequency throttling of the CPU cores may fail, especially after(!) the device was getting hot and is recovering. This may lead to performance issues until reboot and other issues. Workaround: reboot device after heavy use.*
Reported size of adoptable storage seems to be wrong. However, remaining free space seems to be reported accurately.
Formating a SD card as internal storage may cause the card to be reported as "corrupted".
Screen rotation may not work after a while. Solved, to be integrated into builds from mid April 2021 onwards.
You tell us (with logs please)...
* To our knowledge, these are general issues on all AOSP/LineageOS based custom ROMs for this device family (Shinano). However I would be happy to be mistaken here and if sombody has a solution.
Further hints
This ROM currently does not work with the Z3 Dual SIM variant. Here's a build for the Z3dual.
If you need Google Apps we recommend the OpenGApps "nano" package, however, I personally use the "stock" package which works as well. The ROM also seems to work with MicroG and BiTGApps.
Magisk - see this post for issues with latest Magisk versions
If you need to install a lot of apps you may run out of internal DATA storage capacity, especially if you install one of the larger GAPPS packages. These apps are initially placed on the system partition and do not cost you DATA capacity. However, every update which comes over the Play Store then fills up your data partition. Using an SD card formated as "external" storage does not help you much (unless you use a tool like app2sd which is no more recommended) and isn't encrypted. Formating the SD card as "adoptable storage" comes with the drawback that some apps do not allow to be migrated to this storage, and unfortunately this is true for some streaming music/video apps which need to store a lot of data obviously (for offline use). The solution I am using is to partition a SD card as "mixed", which gives you the possibility to offload at least some apps to adoptable storage while you still have a classical external FAT32 partition where e.g. your streaming app can save its offline files:
Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.
Follow this guide to partition your SD card. Note: all data on the card will be lost.
Restart your phone.
When you are notified that a new storage card has been detected, use it as "external". (Your internal partition has been recognized at that point already and does not need interaction.)
Go to settings / Storage. Verify that you see three entries: 1. Your internal phone storage of 16GB. This includes your SYSTEM partition. 2. Your SD card with an SD card symbol. The size shown should be the full capacity of the card. If you click on it, your "external" partition is shown (misleading) as "System" and blocked. Click on migrate data to migrate all possible apps to your adoptable storage. 3. Your sd card partition formated as mobile storage (unencrypted!).
How to create logs:
Follow How To Logcat
When creating a log, can you make sure you run the command with the -b option to include kernel messages:
Code:
adb logcat -b all
If your device randomly reboots:
Go to Settings -> System -> Advanced -> Developer options -> Store logger data persistently on device. After the reboot occured: Pull the logs from /data/misc/logd/ (root required).
If your device crashes during boot and reboots to recovery:
Code:
adb pull /proc/last_kmsg
Please submit logs from clean systems without "Exposed" or similar modifications in place
Your feedback is wanted regarding the following topics
Please have a look at lineage-18.1!
A big THANK YOU also to @ronnay ryukay for having maintained the inofficial 17.1 thread!

Thank You.
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?

mer5ad said:
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?
Click to expand...
Click to collapse
TWRP and Lineage Recovery are different things. See Post #2 for details. Current TWRP version is 3.3.1.0 iirc.

Mr.Tom_Tom said:
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code:https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12
Click to expand...
Click to collapse
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_

dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing and b. i had to regrant permissions for most apps . but that was because i m using BitGapps instead of opengapps. i confirmed it after reading the BiTGapps post!!
[edit] the permission regranting problem of bitgapps has been fixed

nikapos said:
dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing but thats maybe because i m using mindthegapps instead of opengapps and b. i had to regrant permissions for most apps.
Click to expand...
Click to collapse
Hmm, ok, sounds good. Will try it. :good:

0LDST4R said:
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_
Click to expand...
Click to collapse
download D6603_23.5.A.1.29.ftf rom and use FLASHTOOl software.

Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...

kwasior500 said:
Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...
Click to expand...
Click to collapse
not supported by device hardware. be reasonable!

NOT 4k 120FPS, 4k OR 120FPS

Upgraded from 16 to 17 (dirty flash). Most things seem to work well. A few minor issues:
- Data connection occasionally stops working. Can't figure out why, but I think when I disable/enable wifi is connected. Need to dig deeper
- Smart lock with BT device stops working after a while. Have to remove the device and re-enable
Happy otherwise. Good job!

@Mr.Tom_Tom
how can mount System to boot with RW ?

dsp3 said:
Upgraded from 16 to 17 (dirty flash).
Click to expand...
Click to collapse
Thanks for this feedback, but please do NOT dirty flash. When installing official LOS17.1 the first time, do this with a clean setup.

WiFi 5GHz (Russia) does not work. Can you make changes to the kernel?

new update with working calendar widget. i also had to boot into recovery to reflash bitgapps fo the phone to boot normally.
---------- Post added at 06:08 PM ---------- Previous post was at 06:00 PM ----------
where is the update stored if downloaded from settings->system->update? i want to make sure it is promptly deleted after install.
[edit] ok, you have the option to delete the files after install. the option is found within the update settings.

Just tested Google Duo.
No audio issues. Finally. Thanks, thanks, thanks.
So i guess there are no probs in free hand mode too.

Amazing rom. All very smooth. Thanks a lot!
Unfortunately the back camera does not work for me.
First I was able to start it and a black picture came up. Yesterday I did the new OTA update, that didn't change the problem.
This morning I wanted to save logs about the problem and now the Camera App doesn't start anymore.
Logcat:
2020-09-20 10:59:54.035 8972-8972/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.lineageos.snap, PID: 8972
java.lang.RuntimeException: Unable to resume activity {org.lineageos.snap/com.android.camera.CameraLauncher}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4205)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.PhotoModule.initializeFocusManager(PhotoModule.java:2830)
at com.android.camera.PhotoModule.onResumeBeforeSuper(PhotoModule.java:2598)
at com.android.camera.CameraActivity.onResume(CameraActivity.java:1889)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1453)
at android.app.Activity.performResume(Activity.java:7958)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4195)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)*
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)*
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)*
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)*
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)*
at android.os.Handler.dispatchMessage(Handler.java:107)*
at android.os.Looper.loop(Looper.java:214)*
at android.app.ActivityThread.main(ActivityThread.java:7356)*
at java.lang.reflect.Method.invoke(Native Method)*
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)*
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)*
By forcing stop and restart I was able to reproduce the original error. The log is too big to put it in the post, therefore in the attachment.

SageDroid said:
Unfortunately the back camera does not work for me.
Click to expand...
Click to collapse
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.

Mr.Tom_Tom said:
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.
Click to expand...
Click to collapse
Thanks for looking into it. Yes, I wiped them all. Even the internal storage.

Related

[ROM][H815][6.0|MM][UNOFFICIAL] Lineage OS 13.0 for LG G4

FAQ
1. Q: Encryption is not possible?
A: if the GUI for encrypting the device is not working:
Its highly recommended to backup all your data including the internal storage (I recommend FlashFire or / and Titanium)
Flash my screenlock fix (search here at XDA) in TWRP.
Reboot to android.
ensure that you met all usual requirements (battery, screen lock set) and then open a terminal or adb shell. Type:
vdc cryptfs enablecrypto inplace pin 1234
Replace 1234 with your desired pin ofc.
sfX

Reserved

Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
steadfasterX said:
the kernel has security bugs which need to be addressed
Click to expand...
Click to collapse
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !

thewild said:
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
Click to expand...
Click to collapse
its the same source then the official build (and so genessix) used so it should work the same way but as my device is broken atm and I await repair I cannot test it..
Last time I checked the security patches in my build got increased to July 2017 where the latest official ones had June..
so afaik there should be no critical issues in Android but the kernel is last time updated in May 2016 (should be the same for genessix builds).
My plan is maybe to integrate the Llama kernel and backport fixes from the 14.x tree.
don't expect that this happen in the near future (we can hope though) because atm I'm quite busy with my unofficial unlock stuff.
.

OK I'll keep an eye on this thread then.
Good luck !

Any tester reports?

Netsab said:
Any tester reports?
Click to expand...
Click to collapse
Yes.. I use that ROM with my unofficial unlock testers. Atm I cannot test cell service but it boots up fine, WiFi, cam etc works fine.
sfX
Sent from my LG-H815 using XDA Labs

Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance

zeduck said:
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
Click to expand...
Click to collapse
thx for testing..
yea I rem that there was a "trick" .. Could you try this build pls: http://droid.binbash.it:58885/h815/lineage-13.0-20170912-UNOFFICIAL-h815.zip
It includes an insecure kernel which will allow to debug.
Factory Reset in TWRP
Flash in TWRP
Boot Android
Enable encryption
when it reboots open a terminal and type (linux or FWUL): while true; do adb logcat ;done
on windows ensure that once the logcat aborts that you restart it immediately again!! and use just adb logcat
if using windows or linux: ensure the terminal buffer is big enough bc thats a a lot to handle.. (go into the settings of the cmd or terminal and set it to a very high value. e.g. 5000000)
let it bootloop and boot into Android again (logcat should run all the time)
CTRL+C when its completed with the above
copy & paste the whole stuff in a text file and attach it here
sfX

Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.

zeduck said:
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
Click to expand...
Click to collapse
without logs I cannot say anything for sure...
It may can be solved by just typing the encrypt command over adb or it requires to modify the ROM..
If you like you can try the following but keep in mind that having a complete Backup is a good idea always and when I say complete I mean including internal storage which is not be backuped by TWRP!! Use e.g FlashFire app to accomplish this. I would take a TWRP backup for all (use my latest beta!!!) and then FlashFire to backup internal storage.
Encryption often fails to a wrong formatted data partition so this can be a reason as well.
Try this:
Backup as described above
In TWRP select wipe - advanced - press "Format data" button to format the data partition
Boot android
set a pin or password for the lock screen!
Encrypt
If succeeded restore backup with FlashFire
As always there is a risk and it requires some time so I would not recommend to do this on a busy day.. as you say at the weekend fe.
Then we can try to use the adb commands and if that doesn't work as well the logcat..
sfX
Sent from my LG-H815 using XDA Labs

Hi !
I gave a try with lineage-13.0-20170918-UNOFFICIAL-h815.zip that I dirty-flashed over my previous lineage-13.0-20170204-UNOFFICIAL-h815 version.
Everything went fine (I had to replace the su zip/app though), except that satellite location would not work (network location was fine) : I kept getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
I'll give another try with the latest lineage-13.0-20170927-UNOFFICIAL-h815.zip.
If that fails too, I guess I'll have to clean-flash it then.
EDIT :
Bad news : after a clean flash, I keep getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.

No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying

Netsab said:
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Click to expand...
Click to collapse
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.

breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
Thanks you, I'll try.

breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
thanks for your report. btw a dmesg is very helpful in these cases but the above should be fixed on next build.
next build will also have all proprietary stuff upgraded to v20p.
sfX
EDIT
new build is up
.

Hey sfX,
When trying to dirty-flash 20170930 over 20170813, the phone gets stuck on the boot animation (for over 30 minutes).
I did not try to clean-flash it though ; I thought I'd let you know first.

Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICIAL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow

datorprofessor said:
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICAIL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
Click to expand...
Click to collapse
Better wait until I fixed the current nightlies..
nice app btw. when all is fixed i may take a look into it
Sent from my LG-H815 using XDA Labs

[ROM][10.0][UNOFFICIAL] LineageOS 17.1 for Mix 3 5G [andromeda]

Additional installation instructions if coming from stock MIUI:
In order to install a custom ROM you must have an unlocked bootloader. You can apply for this at Xiaomi's official site: https://en.miui.com/unlock/
You then need to install a custom recovery. Official TWRP builds are available, and the official maintainer has a thread with installation instructions here: https://forum.xda-developers.com/mi...covery-unofficial-twrp-xiaomi-mi-mix-t3941867
Once you have TWRP installed, boot into recovery mode. Wipe cache,dalvik,system,vendor partitions.
You are strongly advised to flash the latest modem firmware. You can grab that here: https://sourceforge.net/projects/xiaomi-andromeda/files/firmware.zip/download
WARNING: You will lose all saved files on your internal storage in the next step, make a backup of important files before proceeding
Data partition must be formatted (not wiped) to remove forced encryption. Use the bottom right "Format Data" button in the Wipe menu. You will be asked to type "yes" to confirm your choice.
At this point your internal storage will be empty. Copy the ROM from your PC to the phone, click install in TWRP and select the ROM. If you wish to install gapps/nanodroid, copy it to the phone and install after the ROM. Once you have flashed the ROM and any add ons, you must format internal storage again. Internal storage must be completely empty for the very first custom ROM boot, once a custom ROM has been installed and you want to swap to a different one, further formatting is not necessary.
Reboot back to system and enjoy custom ROM goodness

Reserved

Thanks, been waiting for this. Will test it out

Just switched to this one because Xiaomi probably won't ever release Q for andromeda. Working great so far!

Can you flash modem via twrp or do I need to use Odin?

Arcticsoldier said:
Can you flash modem via twrp or do I need to use Odin?
Click to expand...
Click to collapse
twrp

pm4rcin said:
1. After some trouble with installing (first time so...) system works fine but when I plug my usbc-jack adapter and headphones it doesn't see them. How can I fix that?
2. Another thing is no 4k option in camera app for recording.
PS. Thanks for your work delivering that ROM.
Click to expand...
Click to collapse
I got no problem with headphones here.
Stock LineageOS Snap camera can't do 60fps or 4k recording. There are plenty of camera apps on the play store that have these options.
If you want to use GCam then this port is the most compatible with andromeda, it can do 1080p/60fps and 4k/30fps video recording. https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.9.apk
This GCam port does not work with selfie camera at all, you must use the built in Snap cam for that. My suggestion would be to set the slider to open the default camera app and to have have GCam on your home screen.

Phone is not rooted, but many apps do not work because they think its rooted. I.E. Revolut, banking apps, Outlook, Teams. Is there an workaround for this?

flori.one said:
Phone is not rooted, but many apps do not work because they think its rooted. I.E. Revolut, banking apps, Outlook, Teams. Is there an workaround for this?
Click to expand...
Click to collapse
This problem with false positives happens on stock ROMs as well. When I owned a Zuk Z1, loads of apps thought the stock ZUI was a rooted custom ROM. Not a lot can be done about it because each app uses it's own detection method and the companies that make these apps obviously aren't going to broadcast the detection methods they use.
You may have success running these apps by actually rooting your phone and using Magisk Hide on the apps that don't work.

It's the first time I install a non-official Lineage ROM and I've found that both SELinux and device encryption are disabled. I also got a notification saying this was due to the ROM being built with public keys?
I don't know if this is normal and if there's something I can do to enable SELinux and searching for solutions hasn't returned any
Also, what's the keys thing about?
Thanks for your efforts!

Groctel said:
It's the first time I install a non-official Lineage ROM and I've found that both SELinux and device encryption are disabled. I also got a notification saying this was due to the ROM being built with public keys?
I don't know if this is normal and if there's something I can do to enable SELinux and searching for solutions hasn't returned any
Also, what's the keys thing about?
Thanks for your efforts!
Click to expand...
Click to collapse
I'm not on the LineageOS team so I don't have access to their build system or their private keys, hence the warning about public keys. If you really want encryption it is possible but would involve formatting your data partition again and losing all your files. Writing SELinux policy is a bigger task than porting the ROM and I'm only one guy working alone in his free time. If you try to force SELinux to enforcing mode it's quite likely the ROM won't even boot.
If you're worried about a security risk, considering you have unlocked your boot loader and installed an unknown firmware from a random person on the internet, I would say you have already made a decision concerning your phone's security. All my source code is linked in the first post, so feel free to look it over to make sure I'm not doing anything shady

Inkypen said:
I'm not on the LineageOS team so I don't have access to their build system or their private keys, hence the warning about public keys. If you really want encryption it is possible but would involve formatting your data partition again and losing all your files. Writing SELinux policy is a bigger task than porting the ROM and I'm only one guy working alone in his free time. If you try to force SELinux to enforcing mode it's quite likely the ROM won't even boot.
If you're worried about a security risk, considering you have unlocked your boot loader and installed an unknown firmware from a random person on the internet, I would say you have already made a decision concerning your phone's security. All my source code is linked in the first post, so feel free to look it over to make sure I'm not doing anything shady
Click to expand...
Click to collapse
Well, I've never read a better argument for security! I'll try to learn about writing a SELinux policy and will PR you if I can get it to work in my own device. Once again, thank you very much for your contribution!

Hello
Great Job. Hope you could be merged soon in Official build, they announce a relaxed form in order to submit devices BTW.
Also, i'm trying to get encryption working and i'm stuck.
Like my old phone, after a fresh install a go to encrypt my phone.
I have a little droid during few seconds and a reboot (without progressing bar, a classic boot).
After checks phones still unencrypted.
Just for my reminder here are the steps:
- Flash MIUI EEA
- Boot MIUI
- Fastboot > flash TWRP
- Reboot Recovery
- Wipe Cache, System, Vendor, Data
- Install firmware
- Format Data
- Install lineage
Is it correct ?

kikadisa said:
Hello
Great Job. Hope you could be merged soon in Official build, they announce a relaxed form in order to submit devices BTW.
Also, i'm trying to get encryption working and i'm stuck.
Like my old phone, after a fresh install a go to encrypt my phone.
I have a little droid during few seconds and a reboot (without progressing bar, a classic boot).
After checks phones still unencrypted.
Just for my reminder here are the steps:
- Flash MIUI EEA
- Boot MIUI
- Fastboot > flash TWRP
- Reboot Recovery
- Wipe Cache, System, Vendor, Data
- Install firmware
- Format Data
- Install lineage
Is it correct ?
Click to expand...
Click to collapse
I have testing builds with encryption enabled. The good news is the next update will have encryption enabled, bad news is you'll have to format data partition again to get it working.

The LineageOS team have added in Qualcomm's Bluetooth stack so I've uploaded a new build. You probably won't notice any changes because these are "under the hood" improvements, but if you have some high end headphones you may hear a difference!
Also this build and all future builds have encryption enabled. Unfortunately this means you will need to format your data partition in order to install this build, but this is a one time only thing. I can also confirm that F2FS is working perfectly with encryption if you wish to change filesystems. I can also confirm you can switch to a different ROM without formatting (just the usual wipes) so long as the new ROM you are installing is also encrypted. This change might mean that you can come straight from MIUI without formatting but this is completely untested by me.
Here's the link, and remember you MUST format internal storage if you are on an unencrypted build:
https://sourceforge.net/projects/xi....1-20200630-UNOFFICIAL-andromeda.zip/download

I have tried to flash after format data partition, but I had a bootloop. I was forced to do a clean install after that. I don't know why, but it's working now.
Thanks for your work

Hello, does 5G work on this custom rom?

karolwojak said:
Hello, does 5G work on this custom rom?
Click to expand...
Click to collapse
yes it does

I really need to record conversations or have. I would love to try it out if it had this function

[ROM][UNOFFICIAL][Android 11] LineageOS 18.1 [joyeuse/miatol][22/01/21]

{
"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 18.1 is a free, community built, aftermarket firmware distribution of Android 11, 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.
We have progressed to LineageOS 18.1
Flash instructions :
Use latest pbr recovery for miatol, supports decryption - beta available here, https://pitchblackrecovery.com/joyeuse/.
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
There is a way to fix this without the fastboot factory clean, flash and lock with the official Xiaomi tool, which was forcing you to clean and lock... now available here: https://github.com/Szaki/XiaomiADBFastbootTools
If you hose the phone, use this tool - you need to install JRE though, as the tool is Java base. Put your phone is fastboot, use the tool to download the latest global rom (or whichever). Then go to where its downloaded, extract the .xy/tar file, then go back into the tool and under "image" select the folder INSIDE the folder you just extracted, then select "clean install" and install it. This will flash the majority of imgs but will error out at the end and be unable to create the "user data" partition.
That's okay, because all of the partitions will be setup again, and you can flash any rom you want again. So when its done, and still in fastboot, fastboot flash recovery recovery.img (recovery.img being the latest joyeuse pbr recovery, you renamed to recovery.img and were in that folder in the command prompt, so it will flash that recovery) or use the tool to select that recovery and it will flash it for you and reboot into for you if you like.
(Do this step last, after Magisk, if you want to unencrypt, no worries if you don't unencrypt - PBR recovery will decrypt your data ON THE SECOND TRY OF ENTERING YOUR SCREENLOCK PIN NUMBER...), the new PBR Miatol Beta 10/14/20, fixes this issue, it is now decrypted on the first entry of the phone's lockscreen PIN. Then flash disable_dm-verity_forceencrypt.zip available here for those who want decrypted data partition: https://zackptg5.com/android.php#disverfe and other places as well.
If you are encrypted and decide to unencrypt later, you will need to flash the disable_dm-verity_forceencrypt.zip in miatol recovery, then format data. Store roms, gapps, recoveries (just in case), disable_dm-verity, magisk install and uninstall and all that stuff on the SD card, so you can use them in PBR after you format DATA (the first step after installing PBR miatol recovery), just FYI. Then do the following:
Flash ROM
Flash OpenGAPPS for android 11 nano
Boot into android, make sure its working and install Magisk Manager 8.0.7, then reboot into recovery and install Magisk 21.4 (in recovery, I did not need to extract the boot.img and patch in Magisk Manager, and reboot into recovery to flash the patched boot.img, but your results may be different): https://github.com/topjohnwu/Magisk/releases. If you want to unencrypt (no guarantees its permanent though) you need to format data, THEN FLASH MAGISK, then flash disable_dm-verity (always the last step)- I usually wipe dalvik and cache too.
USE LATEST MIATOL PBR RECOVERY, PLEASE.
SD card issues resolved with the implementation of the EXFat android driver.
Source Code: https://github.com/LineageOS
Kernel Source: https://github.com/Redmi-SM6250 or Stock kernel from Miui
Apologies for the lack of updates, was diagnosed with stage 4 metastatic cancer and this project was not on my priority list anymore...
Update 28/1/21:
Release notes:
LineageOS
Device: Unified (Miatoll)
Developers: ScaryMen1325 & Loptr4
ROM Version: 18.1
Android Version: Android 11
Build date: 22/01/2021
Status: UNOFFICIAL
Changelog:
• Fixed power related issues
• Added useful apps (thanks to Dev: Emulond for that)
• Other fixes and performance improvements
Notes:
• It's 2nd test version, if you found bugs, give log.
• Using loki kernel by default, haven't tested custom kernel.
Download here:
https://drive.google.com/file/d/1M5-cRBfrRdBdNYGzy5G9bOa1Ncf5JkE4/view?usp=sharing
Please note this is a unified release, you should do a clean install unless you're coming from a unified ROM alreadyl.
Will keep you more regularly updated now that I'm out of the hospital....

Perfect will try tonight

Belpek said:
Perfect will try tonight
Click to expand...
Click to collapse
Have you tried it?
How is it? Good for daily?

There are so many Joyeuse LineageOS ROMs I don't even know where to start.

i don't see you mentioned mobile network in bugs section; does it work? i'll try this rom in a couple hours

Tell me please. If phone will be locked with black screen and i say "ok google". Will it work? Or it will work only if screen is unlocked?

sorry if its not much, since i can't do much on this rom. flashed nikogapps, google sign-in succeded but it seems that i cant install anything from play store.
(dumb me forgot to screenshot, it only says "something went wrong" when i try to install an app from play store)
about ok google from lockscreen/screen off, i tried it, also not working. can't confirm about volte since volte still relatively new here and hasn't developed that much.

Why nikgapps? Open gapps nano is recommended.
Sent from my Redmi Note 9 Pro using Tapatalk

Flash it and using it by now, so far so good, sometimes it gets a little freeze but nothing serious, miracast reboots phone so dunno if this is a bug or not, proximity sensor is another one cuz while I was in speaking with my pal screen was on all the time and my ear activated bluetooth and DND
Have nothing to talk about VoLTE cuz in my country is not available.
ANX modules left my phone in bootloop so instead I went for GCam. Flash unofficial opengapps nano and make sure to use Wi-Fi to complete the first run.
Magisk canary works so it can be rooted.
Keep the hard work!
*Sorry if I made some writing mistakes, english is not my native language. Cheers!!

Tried flashing the latest build (02.10.20) using the latest TWRP from the thread you linked but I get the "can't install package over new build" error. Is it required to come from stock miui?

gigahurts said:
...
Newer Build:
https://mega.nz/file/PlkgiSzS#C_tIspgbtGDrweztQ83lADHyEQf4dTkIUiSAqgjVAFk
NOTE: You should be on 11.0.7.0 QJZMIXM (EU) Global firmware for this build. Also, I have a newer build, but its not ready for primetime and has issues with SMS and Call Log enabling permissions.
Oh, and BTW, if you hose your ROM/Phone, just flash vbmeta.img in fastboot to avoid using the factory fastboot img flash, otherwise you many need to wait another 7 days to unlock the bootloader.
...
The dev for this build is: @wight554, all thanks and credit go to him, he is awesome, and I, for one, seriously appreciate this ROM as it works very well for me. It is so snappy and smooth, with a super fast boot time, no reboots and generally pretty frickin AWESOME!
...
Click to expand...
Click to collapse
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.

Swiftor said:
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Click to expand...
Click to collapse
hey Swiftor,
We will continue to work on this rom. LineageOS has been around a long time, development has spread across so many devices, however, the hardware of many devices is very similar, so support will continue. The last Redmi Note 8 pro, had a mediatek SOC, and made development difficult until MIUI decided to release its source. The snapdragon platform is very mature and is more easily and readily available to develop roms for. Redmi Note 10 pro has been released in India, and has a slightly better processor 765g vs 730g, but the kernel and hardware are very similar, so I development for this phone and the Note 10 pro should parallel and continue. We are working on submitting an official 18.0 release, but have to have all hardware (and software) fully functional and as close to zero bugs as possible. I predict development to continue as long as Xiaomi continues to release new MIUI roms for this device (and they continue to release roms for phones much, much older than this).
I have updated the first post with a newer release. Let me know if you have any issues and I will try to help.
Thanks for the props too

does magisk 21 work on the latest build? really excited for android 11

So this will not be compatible with curtana devices?

Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.??

everything is working perfectly and its showing charging rapidly , it was on 88% and showing 10 minutes until full
everything is completely smooth gonna keep it for my daily use

Bantryred said:
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.
Click to expand...
Click to collapse
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse

there're few thing that you need to fix @gigahurts
1) you putting wrong kernel source. its should be this link
2) why would you mirror it when you can get it in his sourceforge

Why is today's build 590MB while all others are 1.1GB?

pwnaz said:
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
Click to expand...
Click to collapse
Sorry for the delay, Im on Curtana so dont know if it makes a difference, but I used no. 16 - mi 10 Global(11)
I also had to hide Magisk Manager

[ROM][13.0][UNOFFICIAL] LineageOS 20.0 for Mix 3 5G [andromeda]

Additional installation instructions if coming from stock MIUI:
In order to install a custom ROM you must have an unlocked bootloader. You can apply for this at Xiaomi's official site: https://en.miui.com/unlock/
You then need to install a custom recovery. Official TWRP builds are available, and the official maintainer has a thread with installation instructions here: https://forum.xda-developers.com/mi...covery-unofficial-twrp-xiaomi-mi-mix-t3941867
The official TWRP for Mix 3 5G cannot decrypt A12+ encryption scheme so if you see scrambled filenames in recovery mode and want to access your files then use my unofficial build (version 3.7.0-12.0).
https://sourceforge.net/projects/xiaomi-andromeda/files/twrp-3.7.0_12-0-andromeda.img/download
Once you have TWRP installed, boot into recovery mode. Wipe cache,dalvik,system,vendor partitions.
You are strongly advised to flash the latest modem firmware. You can grab that here: https://xiaomifirmwareupdater.com/firmware/andromeda/
This only needs to be done once, once the updated firmware has been flashed you can forget about it.
WARNING: You will lose all saved files on your internal storage in the next step, make a backup of important files before proceeding
Data partition must be formatted (not wiped) to remove forced encryption. Use the bottom right "Format Data" button in the Wipe menu. You will be asked to type "yes" to confirm your choice.
At this point your internal storage will be empty. Copy the ROM from your PC to the phone, click install in TWRP and select the ROM. If you wish to install gapps/nanodroid, copy it to the phone and install after the ROM. Once you have flashed the ROM and any add ons, you must format internal storage again. Internal storage must be completely empty for the very first custom ROM boot, once a custom ROM has been installed and you want to swap to a different one, further formatting is not necessary.
Reboot back to system and enjoy custom ROM goodness

This post is reserved for FAQs and will be added to when frequently asked questions pop up.
How can I stop the slider from opening the camera?
Go to Settings->System->Gestures->Slider settings

Thanks alot for this Man! Will check it out today and let you know!

I have lineage-18.0-20201204-UNOFFICIAL-andromeda.zip installed. Can I just flash lineage-18.1-20210101-UNOFFICIAL-andromeda-signed.zip over this, wipe /cache and keep /data as is?

Hello, I really want to install this rom especially as it seems the device won't be upgraded. I've never done this before, and tried today but I soft bricked my phone . Got the standard ROM back on now.
Can someone help with what I did wrong.
I followed the instructions on this to down load recovery, https://www.xda-developers.com/how-to-install-twrp/?amp
I managed to get the phone into recovery.
I wiped the cache etc, then I installed the modem firmware which was successful.
Then I formatted the drive as the instructions.
I went to move the ROM into the device but when doing this on the PC is timed out, it wouldn't allow me to move the ROM, once I rebooted the device it continued to go into fast boot.
Any help would be welcome.

Oldmanam said:
Hello, I really want to install this rom especially as it seems the device won't be upgraded. I've never done this before, and tried today but I soft bricked my phone . Got the standard ROM back on now.
Can someone help with what I did wrong.
I followed the instructions on this to down load recovery, https://www.xda-developers.com/how-to-install-twrp/?amp
I managed to get the phone into recovery.
I wiped the cache etc, then I installed the modem firmware which was successful.
Then I formatted the drive as the instructions.
I went to move the ROM into the device but when doing this on the PC is timed out, it wouldn't allow me to move the ROM, once I rebooted the device it continued to go into fast boot.
Any help would be welcome.
Click to expand...
Click to collapse
If you are blocked into fastboot you can reflash the official firmware.
Choose the firmware format : https://xiaomifirmwareupdater.com/miui/andromeda/

pommefrite8 said:
If you are blocked into fastboot you can reflash the official firmware.
Choose the firmware format : https://xiaomifirmwareupdater.com/miui/andromeda/
Click to expand...
Click to collapse
Hi there, I installed the original ROM straight after. Just wondering what I've done wrong. Why I couldn't move the lineage os from the computer to the device.
Looks like ive managed to install it just set it up as i write....

Hey Inkypen,
Thanks a lot for the ROM, it's currently my daily driver.
What's the upgrade process between the linked Lineage 18 ROMs? Also, do you have a change log somewhere?
You mentioned in the other thread that you are more active in the Telegram chat - how can I join that?

carimatia said:
Hey Inkypen,
Thanks a lot for the ROM, it's currently my daily driver.
What's the upgrade process between the linked Lineage 18 ROMs? Also, do you have a change log somewhere?
You mentioned in the other thread that you are more active in the Telegram chat - how can I join that?
Click to expand...
Click to collapse
Apologies for the late reply, for some reason I don't get email notifications about this thread even though I'm subscribed. The Mix 3 support group can be found at https://t.me/mimix3_5G and I'm way more active there. All the admins are pretty friendly and willing to help, I'm about most of the time for help and troubleshooting. You can also get access to all the latest builds and other stuff you can't get on XDA

Hello, thank you for all the detailed explanations but I am currently having some trouble with purple/green lines at the bottom of the screen or at the edges of white tabs? I have installed lineage os and have also tried pixel experience but i have had the same results, I have reinstalled lineage a few time but still the same, with miui I haven't had this problem, so my screen isn't faulty, I will try and install the android 10 version of pixel exp and lineage os to see if there is a difference. the green and purple lines aren't too noticeable but I can't stop looking at them! maybe I have ocd?

pm4rcin said:
Hi @Inkypen, I saw that you've pushed the update yesterday but unfortunately it's not available. Did you discover a critical bug or something? Also what's the current status on that ROM. Is there something that doesn't work?
Click to expand...
Click to collapse
I uploaded a testing build to the wrong place. I've now uploaded the proper build with the May security patch. I've added an additional two extras not in official Lineage which are long screenshot and built in signature spoofing support for micro-g users.
https://sourceforge.net/projects/xiaomi-andromeda/files/R/LineageOS/lineage-18.1-20210507-UNOFFICIAL-andromeda-signed.zip/download

thx great work.

Is there any known issue with the gps?
Lately i have some problems to find my position.

ive been been on 17.1 since last year and decided to upgrade to 18.1. seems pretty stable however i get random lockup/freezes which requires me to perform a shutdown/power up by holding in the power button. i followed the guide, updated to the latest twrp and using the latest build. other than that the battery life and speed is great

Hi! Could files accept characters that are not typically accepted in Windows systems but are in Linux? Like ':', or '?'.

First of all thanks a bunch for this ROM. Been running it for several weeks now, everything has worked fine so far.
Today however I stumbled into an issue: USB Tethering does not seem to work for me.
- tried with 3 computers and different OSs (Windows, Linux) ... never worked
- I have another Android10-based Sony smartphone - for this one USB tethering works fine with all 3 computers
- the computers all recognize my Mi Mix 3, but fail to establish a network connection (no IP obtained?)
Does USB Tethering work for you guys? Or anybody having similar issues?
Thanks!

Sorry guys, I pretty much missed out on A12 Lineage, but I'm back with A13 Lineage for you guys! I will provide both integrated gapps builds and vanilla builds for those that don't want gapps. The official TWRP for andromeda isn't able to decrypt A12+ encryption scheme so I've ported the A12 version of TWRP and OrangeFox for our device. Don't try and install the updated recovery if you're running A11 or below, in that case stick with the official version.
Biggest change to my builds is that OTA updates are now enabled, you'll get a notification prompting to update. The builds are hosted on sourceforge and download speeds can be very slow depending on where in the world you are and which mirror it selects. It might be quicker to download updates on a PC. Not a lot I can do about it, that's the downside of free file hosting.
LOS builds: https://sourceforge.net/projects/xiaomi-andromeda/files/T/LineageOS/
TWRP: https://sourceforge.net/projects/xiaomi-andromeda/files/twrp-3.7.0_12-0-andromeda.img/download
Orangefox: https://sourceforge.net/projects/xi...A12.1-R11.1-Unofficial-andromeda.zip/download

Inkypen said:
Sorry guys, I pretty much missed out on A12 Lineage, but I'm back with A13 Lineage for you guys! I will provide both integrated gapps builds and vanilla builds for those that don't want gapps. The official TWRP for andromeda isn't able to decrypt A12+ encryption scheme so I've ported the A12 version of TWRP and OrangeFox for our device. Don't try and install the updated recovery if you're running A11 or below, in that case stick with the official version.
Biggest change to my builds is that OTA updates are now enabled, you'll get a notification prompting to update. The builds are hosted on sourceforge and download speeds can be very slow depending on where in the world you are and which mirror it selects. It might be quicker to download updates on a PC. Not a lot I can do about it, that's the downside of free file hosting.
LOS builds: https://sourceforge.net/projects/xiaomi-andromeda/files/T/LineageOS/
TWRP: https://sourceforge.net/projects/xiaomi-andromeda/files/twrp-3.7.0_12-0-andromeda.img/download
Orangefox: https://sourceforge.net/projects/xi...A12.1-R11.1-Unofficial-andromeda.zip/download
Click to expand...
Click to collapse
Hi,
first of all, thank you for your follow-up on the roms on the mi mix 3 5g.
I just have one question, why not make it official?

pirloui said:
Hi,
first of all, thank you for your follow-up on the roms on the mi mix 3 5g.
I just have one question, why not make it official?
Click to expand...
Click to collapse
I have one question for you. What benefit is there to being official? The only real perk is OTA updates, which my builds now have.
The requirements to go official for LOS are unbelievably strict, for example I wouldn't be allowed to patch the ROM to pass safetynet or be allowed to take updated device drivers from a QCOM BSP (which I already have done several times). I don't have the time or energy to work around their restrictions.

[UNMAINTAINED][ROM][12L][STABLE][G8141] ArrowOS 12.1 Unofficial VANILLA [07-04-2022]

{
"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"
}
ArrowOS
ABOUTArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end of the day, aiming to deliver smooth performance with better battery life.
Website : https://arrowos.net
Telegram Group : https://t.me/arrowos
Telegram Channel : https://t.me/arrow_os
Github : https://github.com/ArrowOS
Code Review : https://review.arrowos.net
Email : [email protected]
Blog : https://blog.arrowos.net
Paypal : https://www.paypal.me/TeamArrowOS
WHAT WORKS?Everything should works except the one mentioned in the bug list.
BUGS-TWRP can't decrypt data.
-You tell me.
INSTALLATIONCLEAN FLASH
-Flash latest 47.2.A.10.107 firmware with newflasher.
-Enter fastboot mode.
-Flash latest official TWRP.
-Boot into TWRP.
-Wipe data, cache & dalvik.
-Flash the ROM.zip followed by additional flashable like gapps/magisk.
-Format data and type "yes".
-Reboot system.
IF YOU'RE ALREADY ON ANDROID 12L ROMS
-Boot into TWRP.
-Wipe data, cache & dalvik.
-Flash the ROM.zip followed by additional flashable like gapps/magisk.
-Reboot system.
UPDATES
-Boot into TWRP.
-Wipe cache & dalvik.
-Flash ROM.zip.
-Reboot system.
CHANGELOGS07/04/2022
-Initial release.
DOWNLOADSROM
AFH Link
GAPPS RECOMMENDATION
MindTheGapps (12.1 ARM64).
MAGISK
HERE
SOURCESROM
Device Sources
Device Configurations (Maple)
Device Configurations (Yoshino)
Kernel Tree
Vendor Tree
Local Manifests
THANKS TOTux111, Rooted_Ansh, derf_elot, everyone in the Telegram Group.
Sorry if I missed someone.
ArrowOS for Sony Xperia XZ Premium
Device : Maple.
Build Type : Unofficial.
Build Variant : Vanilla, userdebug.
ROM Android OS Version : 12L.
ROM Kernel : 4.4.
ROM Firmware Required : 47.2.A.10.107.
Based On : AOSP.
Security Patch Level : March 2022.
Version Information
Status : Stable.
Current Stable Version : 12.1.
SELinux : Enforcing.
Created : 08/04/2022.
Last Updated : 04/04/2022.

Tested Rom, works well, but Android Auto Not working, Says connected to Car but wont Start.

hi,
i have a sony xperia xz premium (g8141) still running stock firmware and android 9, battery and phone in good shape, so why get a new one... Not sure if this is the right place to ask, but ... i'll give it a try ;-)
1) build is unofficial, but is it considered stable? e.g. crashes, freezes or the like?
2) is signature spoofing enabled? i want to avoid google apps and install microg instead.
Signature Spoofing
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
3) one needs this TWRP version?
Sony Xperia XZ Premium
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Download TWRP for maple
Download TWRP Open Recovery for maple
dl.twrp.me
thx

m00ns0rr0w said:
hi,
i have a sony xperia xz premium (g8141) still running stock firmware and android 9, battery and phone in good shape, so why get a new one... Not sure if this is the right place to ask, but ... i'll give it a try ;-)
1) build is unofficial, but is it considered stable? e.g. crashes, freezes or the like?
2) is signature spoofing enabled? i want to avoid google apps and install microg instead.
Signature Spoofing
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
3) one needs this TWRP version?
Sony Xperia XZ Premium
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Download TWRP for maple
Download TWRP Open Recovery for maple
dl.twrp.me
thx
Click to expand...
Click to collapse
hi!
1. yes it is stable like any other a12L roms beacuse it uses the same device, kernel, and vendor tree. even though it's unofficial.
2. yes arrowos have signature spoofing enabled. so it supports microg.
3. i personally use the latest twrp from the official website. https://dl.twrp.me/maple/twrp-3.6.1_9-0-maple.img.html

isosceleshampa said:
Tested Rom, works well, but Android Auto Not working, Says connected to Car but wont Start.
Click to expand...
Click to collapse
what gapps are you using? can you please provide a logcat?

hey,
wow, cool, what a fast answer thx!
ok, so it's stable (based on whatawurst iirc, clicked a while through the many pages), signature spoofing is enabled which allows microg (will be enough for me, just a couple of apps via aurora store, nothing fancy, and google apps stuff finally gone). sounds great!
last question: how often will there will be updates/releases? every x weeks/months? and if A12L is installed: OTA updates or flash always necessary? Just curious.
well, i think i'll give it a try, maybe easter weekend. flashed only one rom (/e/OS on a samsung s5) before, but, hey, what could possibly go wrong?

is there a mirror link? I can not visit google drive in my region. Thanks guys.

Hmm... just read this thread:
[ROM] LineageOS 19.1 UNOFFICIAL - 1.6 [2022-09-18]
LineageOS 19.1 for Sony Xperia XZ1 RELEASE This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features. Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything...
forum.xda-developers.com
Do i need a microSD card to flash? Or via adb sideload?

m00ns0rr0w said:
hey,
wow, cool, what a fast answer thx!
ok, so it's stable (based on whatawurst iirc, clicked a while through the many pages), signature spoofing is enabled which allows microg (will be enough for me, just a couple of apps via aurora store, nothing fancy, and google apps stuff finally gone). sounds great!
last question: how often will there will be updates/releases? every x weeks/months? and if A12L is installed: OTA updates or flash always necessary? Just curious.
well, i think i'll give it a try, maybe easter weekend. flashed only one rom (/e/OS on a samsung s5) before, but, hey, what could possibly go wrong?
Click to expand...
Click to collapse
rom will be updated accordingly to arrowos source. maybe it's monthly or when a new security patch is up.

m00ns0rr0w said:
Hmm... just read this thread:
[ROM] LineageOS 19.1 UNOFFICIAL - 1.6 [2022-09-18]
LineageOS 19.1 for Sony Xperia XZ1 RELEASE This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features. Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything...
forum.xda-developers.com
Do i need a microSD card to flash? Or via adb sideload?
Click to expand...
Click to collapse
if you have flashed a12 before, you need to put the files in microsd/usb otg/temp directory or install through adb sideload because the twrp can't decrypt data for now (in a12 roms). but if you're on stock rom or any stock based rom that isn't a12, then you can use the internal storage in twrp.

Cool, thank you. Yes, still stock rom. So only copy it to the internal storage and flash. Sounds easy
edit: ok, i think i can remember why - with one of the android9-followers encryption was introduced...

ok, couldn't wait and did the install. some problems during the installation, will report maybe later, but the boot into the system then succeeded. did some settings (clock, timezone etc.); the problem now: the system boot seems to hang.
i tried to transfer some files (contacts and apk for f-droid) but the copy somehow got stuck. I then tried a reboot, but after sony logo and the android robot head i see the moving/glowing arrow symbol. And that's it. boot process doesn't proceed. Well... what could be wrong?

LOL... i think i know what went wrong: for login i wanted to have a PIN, and the system offered me to secure the system boot with that PIN as well. I think the system got stuck when the PIN has to be entered - but i never get offered to enter the PIN. Great

hanlincn said:
is there a mirror link? I can not visit google drive in my region. Thanks guys.
Click to expand...
Click to collapse
sorry for taking a long time, here you go
Arrow-v12.1-maple-UNOFFICIAL-20220407-VANILLA.zip | by Aviellyan for Xperia XZ Premium
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

m00ns0rr0w said:
LOL... i think i know what went wrong: for login i wanted to have a PIN, and the system offered me to secure the system boot with that PIN as well. I think the system got stuck when the PIN has to be entered - but i never get offered to enter the PIN. Great
Click to expand...
Click to collapse
did you enable secure boot?

hm, no, never saw smth like "secure boot". As i said, the only thing that i can remember: i was asked for setting a PIN for screen unlocking, and there it was offered to use that PIN for system boot as well. Nothing else.

avl.callistá said:
sorry for taking a long time, here you go
Arrow-v12.1-maple-UNOFFICIAL-20220407-VANILLA.zip | by Aviellyan for Xperia XZ Premium
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
thx bro, you did a great thing.

strange, still having problems with my SIM card. System boots, asks for SIM PIN, but then says: "Service not available". German provider congstar (telekom daughter). By default no APN is elected (available: lebara internet and telekom internet); i added the congstar apn manually -> no difference, doesn't work.
i tried a different phone, a samsung galaxy s5, with lineageOS 18.1 - no problems there. Any related issues known? someone else has this problem?

created a logcat.txt via 'adb logcat -d > logcat.txt', is attached here. some congstar related messages, not sure if they help.
i can see a couple of error messages, probably not related, not sure if interesting ;-)

strange, now it works, phone calls work... the small radio cell icon shows 3-4 bars, but with an ! - very strange... i don't trust it at the moment, will check it regularly the next days.

Develop Bugs

welcome