Database Develop

[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]

LineageOS 17.x Unofficial for Galaxy A3 2017​
{
"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 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* 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.
*/
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 Gerrit Code Review.​
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26

Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations

Reserved

Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)

banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home

Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.

yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM

Ok thanks. Another issue : I can't get split-screen working with any apps. And you?

Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...

That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?

starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing

MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.

starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using

Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.

The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.

MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?

Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards

Migrate doesn't detect it as an installed rom, any help?

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:

[ROM][10.0][UNOFFICIAL][MATA][microg][VoLTE][WireGuard] crDroid v6.19

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
VoLTE
WireGuard
MicroG support
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
Fastboot Flash Essential's Jan update (You can get it here)
Flash twrp, then boot into it.
Flash the rom.
Flash the twrp zip.
Optional: flash OpenGapps package of your choice.
Optional: boot into system, then flash magisk.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM https://www.androidfilehost.com/?w=files&flid=314554
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_<device codename>.txt
Known issues:
Speaker phone call volume stays at a fixed level.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
XDA:DevDB Information
crDroid, ROM for the Essential Phone
Contributors
monark88
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Flash January Stock image.
Based On: LineageOS
Version Information
Status: Testing
Created 2020-07-06
Last Updated 2020-11-09

Reserved
I was quite tired of all the mata ROMs with built-in gapps, and so many without all the great customizations that crDroid brings. We needed a ROM with Signature Spoofing for microg support. I've tested out the 360 degree camera, it's working. I tested phone calls, wifi, messaging, and microg installation. All works, can even get location with UnifiedNLP on Android 10! I tested with minmicrog and NanoDroid with magisk overlay.
If this is well received, I'll work on improving issues and getting official status.

Reserved2

Thank you. I'm going to test it.

Funny I would see this. I had the exact same idea yesterday. I finally got around to building crDroid v6.7 with the LineageOS 17.1 kernel as you have. I also used the LineageOS 17.1 device files, and TheMuppets vendor files, (https://github.com/TheMuppets/proprietary_vendor_essential). I then installed Magisk and MinMicroG NoGoolag edition. I find that this ROM so far has been working fine. The only real issue I have found is that Aurora Droid which is installed from the MinMicroG package seems to crash during the first launch sync. However, relaunching it and syncing resolves the issue. This didn't seem to happen when building LineageOS 17.1 with full signature spoofing when I was testing that. Not entirely sure though if others will see that, or if it was my build.
I really hope to see your build get more testing, and get official status!
Best of luck!

TDP95 said:
Funny I would see this. I had the exact same idea yesterday. I finally got around to building crDroid v6.7 with the LineageOS 17.1 kernel as you have. I also used the LineageOS 17.1 device files, and TheMuppets vendor files, (https://github.com/TheMuppets/proprietary_vendor_essential). I then installed Magisk and MinMicroG NoGoolag edition. I find that this ROM so far has been working fine. The only real issue I have found is that Aurora Droid which is installed from the MinMicroG package seems to crash during the first launch sync. However, relaunching it and syncing resolves the issue. This didn't seem to happen when building LineageOS 17.1 with full signature spoofing when I was testing that. Not entirely sure though if others will see that, or if it was my build.
I really hope to see your build get more testing, and get official status!
Best of luck!
Click to expand...
Click to collapse
I did have one force close of NLP backend with minmicrog, but it cleared up after the initial crash. NanoDroid beta had no issues. It's comforting to know others are interested in gapps-less (or less gapps ) ROMs, to the extent of building their own!

monark88 said:
I did have one force close of NLP backend with minmicrog, but it cleared up after the initial crash. NanoDroid beta had no issues. It's comforting to know others are interested in gapps-less (or less gapps ) ROMs, to the extent of building their own!
Click to expand...
Click to collapse
Speaking of NLP, and location services in general, I do notice in the microG self-check mine appears to not have the proper permission to access location in the background, and it seems the permissions is unknown. I see the permissions as "android.permissions.group.UNDEFINED", and I am unable to grant it permission. Did you notice this as well? Or, were you able to provide all permissions without issue?

TDP95 said:
Speaking of NLP, and location services in general, I do notice in the microG self-check mine appears to not have the proper permission to access location in the background, and it seems the permissions is unknown. I see the permissions as "android.permissions.group.UNDEFINED", and I am unable to grant it permission. Did you notice this as well? Or, were you able to provide all permissions without issue?
Click to expand...
Click to collapse
The only thing I had to do finish microg setup was run this from ADB or termux.
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
I've attached screenshots of my microg self-check results and locations permissions. The only unticked box is last known location, which I think is because I haven't used it since last flash..
EDIT: attachments weren't loading.. uploaded here

Thanks! I have already granted signature spoofing, and that appears correct. I'll check into this more later.

Thanks for the rom, I saw two issues related to Lineage tree, VoLTE not work for me, I fix with a Magisk module and codec aptx don't work too.

mpena said:
Thanks for the rom, I saw two issues related to Lineage tree, VoLTE not work for me, I fix with a Magisk module and codec aptx don't work too.
Click to expand...
Click to collapse
Thank you for reporting the issues. If I may ask, what magisk module did you flash to fix VoLTE?
EDIT: i think i found it here

monark88 said:
Thank you for reporting the issues. If I may ask, what magisk module did you flash to fix VoLTE?
EDIT: i think i found it here
Click to expand...
Click to collapse
Yes that is

Something I have noticed with my build is that the status bar clock freezes, and the network monitor when enabled in the crDroid settings disappears from the status bar quite frequently. The time on the lock screen and clock app appear correct always. Rebooting the system or system UI, as well as locking and unlocking a few times corrects it. But it happens again after the next lock or so. Is this something you have noticed with your build as well? Or, are you not seeing these issues?

So far so good. I love performance on this rom. The only issue for me is crdroid launcher. I'm replace it with pixel launcher + quickswitch and everything working so smooth. I'm waiting for the next build in future for more optimize.

Any chance to have the wireguard module baked in the kernel?
Thanks for this gappless signature spoofing enabled Rom!
Finally one that works out of the box

foueddyf said:
Any chance to have the wireguard module baked in the kernel?
Thanks for this gappless signature spoofing enabled Rom!
Finally one that works out of the box
Click to expand...
Click to collapse
I will add WireGuard support in the next release. Thank you for your suggestions, and feedback!

mpena said:
Thanks for the rom, I saw two issues related to Lineage tree, VoLTE not work for me, I fix with a Magisk module and codec aptx don't work too.
Click to expand...
Click to collapse
foueddyf said:
Any chance to have the wireguard module baked in the kernel?
Thanks for this gappless signature spoofing enabled Rom!
Finally one that works out of the box
Click to expand...
Click to collapse
New release is up. It has WireGuard and VoLTE enabled by default. Tested both, both working. Be aware that there could be a DNS leak for wireguard using kernel right now.
Screenshots for proof
Download is in first post, or you can shortcut here.
Dirty flash worked fine for me, but ymmv.

monark88 said:
New release is up. It has WireGuard and VoLTE enabled by default. Tested both, both working. Be aware that there could be a DNS leak for wireguard using kernel right now.
Screenshots for proof
Download is in first post, or you can shortcut here.
Dirty flash worked fine for me, but ymmv.
Click to expand...
Click to collapse
Bluetooth fixed ? Need gappless but also need aptx.
Also ymmv?

Your Mileage May Vary (YMMV) - basically saying that your results may not match exactly to the ones shown.

dememted1 said:
Bluetooth fixed ? Need gappless but also need aptx.
Also ymmv?
Click to expand...
Click to collapse
I made no changes in regards to aptx. Is there an essential ROM that does have aptx working? I can look at how they've implemented and try to recreate.
Failing that, I don't foresee myself implementing aptx into this ROM.

[ROM][UNOFFICIAL][11][lavender] LineageOS 18.1

{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS 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.
What's working:
Everything (if it's not true - tell me)
Features:
4.4 EAS kernel with generater energy model
QS panel 3x3, 3x2 when there is not enough space on the screen (TODO: Make a magisk module to change the QS panel)
Fixed traffic indicator location
Removed black QS status bar background
Oldcam blobs
Instructions:
Reboot to Recovery (Prefer OrangeFox)
Format data, wipe cache, dalvik
Flash fresh firmware (optionally)
Reboot to recovery again
Flash the LineageOS build and any other addons you want (for example, Magisk)
Reboot to the system
Downloads:
ROM: here
Firmware: here. All firmwares for lavender are supported (Prefer latest Global Stable)
NanoDroid with MicroG: here. MicroG will work without the need to patch the system, signature spoofing already exists, but only for MicroG! Flash via Magisk recommended.
NikGApps: here
XDADevDB Information
LineageOS, ROM for the Xiaomi Redmi Note 7
Contributors: ElXreno
Source Code: https://github.com/LineageOS
Device Source: https://github.com/ElXreno/android_device_xiaomi_lavender
Kernel Source: https://github.com/ElXreno/android_kernel_xiaomi_sdm660
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
Based On: AOSP
Version Information
Status: Stable
Telegram links: Support chat && Channel
Created 2021-02-01
Last Updated 2021-02-14

LineageOS 18.1 MicroG
Release date: 31/01/'21
Changelog:
Initial build
Traffic indicator moved to the right side
Removed black QS status bar background
Something else
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS 3x3
Download: SourceForge | MEGA

The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?

WOLFLIFEX said:
The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?
Click to expand...
Click to collapse
* I am not responsible for what may happen to your device, it is simply a solution that worked for me *
I found a solution for this problem the problem was in the NikGApps the shortest solution is:
1
Flash the rom first then reboot
2
Boot up, set the device normally and turn it off
3
Start recovey and flash NikGApps ( preferably the latest Canary version:
https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-R/03-Feb-2021/ )
4
Reboot.

LineageOS 18.1 MicroG
Release date: 14/02/'21
Changelog:
IORap selinux denials fixed
AOSP Surfaceflinger used
Fluence recording enabled
Other changes
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS panel 3x3, 3x2 when there is not enough space on the screen
Thanks:
@VerpaPhallus & @projectfluid for his device tree & kernel
Download: MEGA | IPFS

I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance

Babloo1989 said:
I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance
Click to expand...
Click to collapse
I recommend you to make a clean install, but you can try dirty. As for stability: almost everything is stable, but I would not recommend it if stability is critical.

ElXreno said:
What's working:
Everything (if it's not true - tell me)
Click to expand...
Click to collapse
So, everyone writes that even if the ROM has easily discoverable bugs, BUT, how stable is this ROM? I'm trying to find a good one for a daily driver that won't let me down in an emergency but so far it seems that all the ones I've seen are either a beta or have obvious bugs even though they're called "official" The only one I would potentially end up on is MIUI.

Can it be used as daily Driver?

Netflix and other apps thar block rooted phones are working fine?

Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.

evil-google said:
Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.
Click to expand...
Click to collapse
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.

Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.

evil-google said:
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.
Click to expand...
Click to collapse
i am also using los Q because i find it the most stable one. I m using loscam patch in Q as well for better video quality although.
And the camera issue wont get fixed until and unless someone takes over the development of los. currently it has no maintainer and tge builds we get are automated with los source side changes, not device side changes.

Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
@Walden0, I thought I might give your suggestion a try before downgrading to 17.1 version. Can you please clarify the following?
1. To add the old camera blob, I could install this zip via Yellowfox Recovery?
2. How can I find out which kernel will support this oldcam blob?
Many thanks.

I have never heard of yellowfox recovery but if its based on twrp then most likely it should be able to flash the zip. (maybe you mean orangefox, if yes then you can flash)
The kernel should have "oldcam" or "old" in its name.

Walden0 said:
I have never heard of yellowfox recovery
Click to expand...
Click to collapse
Just being color blind!!...of course, it is Orange Fox Recovery!!
Interestingly, after I did my post, I just opened Settings->Apps->Camera and pressed 'force stop'. Then I started Open Camera which is what I normally use and so far it appears to be behaving OK. I tried a few still shots and one or two short videos - no freezing as yet but it is too early to know. I will keep testing over the next couple of days and see how it goes.
Thanks for your prompt response.

Just to report that the work around by disabling the Camera app so far have fixed the problem.
Any one who has the same problem may want to try out the following steps;
1. Go to Settings->Apps->Camera->Force Stop
2. Then use an installed app such as Open Camera
Note this is not a permanent solution but a work around and this has to be done each time the phone is rebooted.
EDIT: updated to 6 Dec 21 version and the camera behaves even worse than with the initial install! The above fix does not work anymore although it worked most of the time with the November update.

This ROM was abandoned, pitty, much more polished than official https://forum.xda-developers.com/t/...8-1-for-redmi-note-7-lavender.4381893/page-10.
But both suffer from the same issue: no Mass Storage Gadget so that UMS can work to make memory as USB drive.

[ROM] [UNOFFICIAL] LineageOS 18.1 for the Essential PH-1 (mata)

LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
Do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader.
Code:
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Essential PH-1 (mata): GitHub Release Page (link was changed to 2021.03.12 Build)
Google Apps
Google Apps are not included in this build. At this time I do not plan to release gapps included builds. Users who require this will have to build or flash gapps their own.
Source
Device | Kernel | Proprietary blobs
Here's a local_manifest for those who want to build at home.
Known Issues
Wi-Fi WPA3 Network Connection (Connection to WPA2 Wi-Fi still works.)
Essential Camera App (Need to install Google apps.)
Release Signature (Signed with test-key. You can sign using your release-keys.)
Prerequisites
Unlocked bootloader
February 2020 Release | QQ1A.200105.032
Fastboot and ADB set up
Installation
Make sure you meet the prerequisites before continuing!
Using Fastboot
1, Flash February 2020 Stock Firmware (Run flashall.bat)
2, Flash LineageOS images (fastboot flash ***_a ***.img)
3, Erase userdata (fastboot -w)
(Reboot to Recovery and install Gapps)
Using TWRP
1, Install TWRP image
2, Reboot to TWRP (Power + Volume UP)
3, Start ADB sideload
(If your phone doesn't work touch panel, connect to PC using USB-C cable and enter this command in terminal.)
adb shell twrp sideload
4, Install LineageOS ZIP via sideload (adb sideload ***.zip)
5, Erase userdata
(Install Magisk and Gapps imitate steps 3 and 4)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Contributors
conochy (github.com)
(I don't speak English as my main language, so sometimes the sentences are strange or I can't understand comments correctly.)
Source Code: https://github.com/LineageOS
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"
}
Version Information
Status: Beta
ROM OS Version: Android 11, LineageOS 18.1
ROM Kernel: Linux 4.x
Based On: LineageOS
Security Patch 2020-03
Released Date: 2021-03-12
Created 2021-03-11
Last Updated 2021-03-12

Cool, Thanks man.

Ok, First issue using the "lineage-18.1-mata-magisk.img"

dememted1 said:
Ok, First issue using the "lineage-18.1-mata-magisk.img"
Click to expand...
Click to collapse
I noticed that I was building with the WITH_SU=true option.
I'm currently creating a build that doesn't have LineageOS SU.
If you're in a hurry, you can use LineageOS su removal (arm64) Version 16.0 to solve this problem.
(In my environment, I was able to solve it by using this.)
Thank you!

I have just released a new version.
The conflict Magisk SU and LineageOS SU has been resolved.
New version : GitHub Release Page (2021.03.12 Build)
Old version : GitHub Release Page (2021.03.11 Build)
(The link in the first post has been changed to a new one.)

｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
I have just released a new version.
The conflict Magisk SU and LineageOS SU has been resolved.
New version : GitHub Release Page (2021.03.12 Build)
Old version : GitHub Release Page (2021.03.11 Build)
(The link in the first post has been changed to a new one.)
Click to expand...
Click to collapse
Ace thanks. Great work.

Thanks for this ROM.
What GApps are you using? I normally use NikGapps, but it fails to install...

MuddyDog said:
Thanks for this ROM.
What GApps are you using? I normally use NikGapps, but it fails to install...
Click to expand...
Click to collapse
I'm using NikGApps.
But in this LineageOS build, the NikGApps installer doesn't work, so I created a GApps Magisk module instead.
NikGapps Core, Basic Magisk Module installers, and a module that removes LineageOS apps whose functions overlap with Basic.
*It is used personally, I do not guarantee complete operation.
GitHub Module Download Page
Also, the official NikGApps installer has files to install in [Installer-File].zip/AppSet/[AppName]/[AppName].dat.br
If you extract [AppName].dat.br with 7-zip etc. and copy the files in it to the corresponding location of /system with a file manager, you can install it manually without using the Magisk module or the official installer.
Example: __etc__permissions -> Copy the files in that folder to /system/etc/permissions/
Example2: ___priv-app___PrebuiltGmsCore -> Copy the files in that folder to /system/priv-app/PrebuiltGmsCore/
If you want to use Google Setup Wizard, you need to format /data after manual installation.

｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
I'm using NikGApps.
But in this LineageOS build, the NikGApps installer doesn't work, so I created a GApps Magisk module instead.
NikGapps Core, Basic Magisk Module installers, and a module that removes LineageOS apps whose functions overlap with Basic.
*It is used personally, I do not guarantee complete operation.
GitHub Module Download Page
Also, the official NikGApps installer has files to install in [Installer-File].zip/AppSet/[AppName]/[AppName].dat.br
If you extract [AppName].dat.br with 7-zip etc. and copy the files in it to the corresponding location of /system with a file manager, you can install it manually without using the Magisk module or the official installer.
Example: __etc__permissions -> Copy the files in that folder to /system/etc/permissions/
Example2: ___priv-app___PrebuiltGmsCore -> Copy the files in that folder to /system/priv-app/PrebuiltGmsCore/
If you want to use Google Setup Wizard, you need to format /data after manual installation.
Click to expand...
Click to collapse
Excellent, thanks again.
Are you planning to maintain this ROM through to Official Release?... or is it a personal project?
Either way, your work is greatly appreciated.

MuddyDog said:
Excellent, thanks again.
Are you planning to maintain this ROM through to Official Release?... or is it a personal project?
Either way, your work is greatly appreciated.
Click to expand...
Click to collapse
Sorry, I have no plans to continue building LineageOS 18.1 until official distribution begins.
The reason is that my Essential Phone was physically broken today.
(Please be assured that this LineageOS 18.1 Build is not the cause)
Therefore, I will not build for this model until we get it second hand again.
(If I build in the future, I'll post it in this thread to let you know.)
(However, considering the official build start time of LineageOS 17.1 last year, I think that the LineageOS 18.1 build will be officially distributed around next month.)

Thanks for this rom; enjoying trying it out.

Does VoLTE work properly on this ROM?

Hi,
For those who can't wait.
I've followed the instructions from
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡​(https://github.com/conochy/LineageOS/tree/mata-18.1.)​
You can download the files here :
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

And how do you like it? Any mejor bugs?

It's my daily driver since March 12, but I don't use Magisk and Gapps.
I was on ArrowOS before. They seems on par, at least for my usage

Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.

｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
Click to expand...
Click to collapse
Thank you for all the hard work. I really appreciate that.

｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
Click to expand...
Click to collapse
Hey i'm having an issue where my cellular radio keeps connecting and disconnecting rapidly. Anything I can try to fix this? I've tried both your latest build and the official build.
Edit: Ive now observed the behavior after a fresh install. It only starts to happen after the device has been restarted. It will operate fine up until that point.
Edit 2: When I roll back to recovery lineage-17.1-20210329-recovery-mata.img and lineage-17.1-20210329-nightly-mata-signed.zip everything seems to work fine. So the issue must be in the latest builds.

Chirtan said:
Hey i'm having an issue where my cellular radio keeps connecting and disconnecting rapidly. Anything I can try to fix this? I've tried both your latest build and the official build.
Edit: Ive now observed the behavior after a fresh install. It only starts to happen after the device has been restarted. It will operate fine up until that point.
Edit 2: When I roll back to recovery lineage-17.1-20210329-recovery-mata.img and lineage-17.1-20210329-nightly-mata-signed.zip everything seems to work fine. So the issue must be in the latest builds.
Click to expand...
Click to collapse
On my phone, there was no particular problem with the connection of the cellular line (Japan, NTT docomo).
LineageOS 18.1 has some network bugs, such as Wi-Fi (WPA3), which I think are related as well. However, I think it will be fixed in the near future.
The official update for 2021.04.05 fixes some networks and APN, so give it a try.

｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
On my phone, there was no particular problem with the connection of the cellular line (Japan, NTT docomo).
LineageOS 18.1 has some network bugs, such as Wi-Fi (WPA3), which I think are related as well. However, I think it will be fixed in the near future.
The official update for 2021.04.05 fixes some networks and APN, so give it a try.
Click to expand...
Click to collapse
Installed the latest update still getting mostly the same symptoms. LTE network connecting and disconnecting rapidly still. Only difference is the device will no longer crash haha. I connect via Koodo mobile in Canada in case anyone else is having a similar issue.
I have a second essential phone I'm going to test this out on.

[ROM][UNOFFICIAL][capricorn][9] LineageOS 16.0

{
"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 (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.
Updating LineageOS from recovery​
Download LineageOS installation package.
Reboot to recovery.
Flash the package.
Reboot to system
Installing LineageOS from recovery, coming from other ROMs​
Download LineageOS installation package.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the previous menu and tap Advanced Wipe, then select the Cache and System partitions and then Swipe to Wipe.
Sideload the LineageOS .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success.
(Optionally): If you want to install any add-ons, repeat the sideload steps above for those packages in sequence.
info_outline
NOTE: If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
Once you have installed everything successfully, run ‘adb reboot’.
Official installation instructions from Lineage.
Downloads :
https://drive.google.com/drive/folders/1CwLCOM3_ouBL3K2nfi682V9hlcKAHmf6?usp=sharinghttps://mega.nz/folder/PlsEySYJ#1YtIgUgGrhO2vCUxx6xkmw
The purpose of this thread is to continue the support of Lineage 16 for Mi5S.
I am no developer, therefore I can't promise fixing bugs or changing the functionality.
The builds are done the official way and no software is added or removed afterwards.
My target is to do a build at least once a month.
XDAevDB Information
[ROM][UNOFFICIAL][capricorn][9] LineageOS 16.0, ROM for the Xiaomi Mi 5s
Contributors
Unicastbg
Source Code: https://github.com/LineageOS
First Created 2021-04-05
Last Updated 2022-04-20
Security patch level January, 2022
Latest build: lineage-16.0-20220420-capricorn-OTA
Changelog (for all LOS16 devices): https://www.lineageoslog.com/16.0

Tanks for this one, before i test it, what is best ROM you all use on mi5s, right now i am on PE-10, didn't update it for like 6 months. Now i want fresh installation, and i don't need latest anything, just OS that works, it is as fluid as it can be. So:
-this
-PE10
-PE11
-Official LoS16
-Unofficial LoS18
-or something else, what is best right now? Did anyone test more then one ROM.

Official LOS anything is gone for Mi5s. LOS16 was official, but due to the fingerprint issues it will never get 17.1 or 18.
I personally use LOS16 because everything works. And we still have regular security patches.
I have tried briefly the LOS18 and found it's not to my liking.
This is what I wrote in 18.1's forum (Link) based on my experience:
Well... Not sure if related somehow to Viper4Android, but the fingerprints are getting deleted after some time. And after restart. But when present, I think it unlocks faster than compared to LOS 16. However there are a few design features of Android 11 that made me switch back to 9.
Viper4android currently not working.
Apps that rely on fixed SU folder will fail.
Cannot disable Camera - Lens Cap app.
Cannot record calls. There might be a better app that does it ok, but I haven't searched much.
And finally - cannot limit the battery charge percentage - have it charged to 90% for example. I've tried with Floppy kernel as well.

The only thing that I really miss is the EIS that we had in MIUI. But the customization there is very limited compared to Lineage.
I haven't played much with other ROMs, maybe PE has it all sorted out and EIS and the fingerprint reader are both working just fine...

I've been waiting for a security patch for a while, but I think that was it for LOS 16. Had some blind hopes since we got updates after the official end. I'll be checking for updates for a while and if such appear, will update the build.
Update - to my surprise we got security and other updates!

Hmmm i tested this one, for now i found just one problem, if you unlock phone with pin, home button is "fingerprinet sensor" and not home button until you put finger.
And i got problem on install, i couldn't use OpenGApps aroma version (there was 2 problems, it asked for android 7 version, and then asked for arm not arm64 version, and any of this didn't work), othere openGApps versions worked. After install i have problem, banking app doesn't work (tested on othere phone, it works), so probably something from google is missing, if i don't find what i will must go on PE ROM. On install i used pico GApps (i really dont wan't googles bloatware), i will try with FULL version of GApps tonight, if it doesn't work i will must go on othere ROM-s.
But it is "ok" ROM, for now.

We got the July security updates today. I'll do another release tomorrow (done, forgot to update this post).
Using 3 banking apps, haven't had problems so far. About GAPPS, I've followed the official links and got the Nano version.

Hey guys, are you still using LOS 16 on your Mi 5s phones? Is there still need for up to date builds? I'm asking this because if it turns out no one's using this LOS version, then there's no need for newer builds. Like or reply if you want to continue receiving updates. I can also make custom builds with custom software installed, as per your liking. AdAway built in for example.

unicastbg said:
Hey guys, are you still using LOS 16 on your Mi 5s phones? Is there still need for up to date builds? I'm asking this because if it turns out no one's using this LOS version, then there's no need for newer builds. Like or reply if you want to continue receiving updates. I can also make custom builds with custom software installed, as per your liking. AdAway built in for example.
Click to expand...
Click to collapse
Yes, I am using. I installed lineageos 18.1 but it's graphical performance wasn't as good as 16.0, animation looked like stuttering it was awkward. So I installed your ROM. I preper vanilla lineageos 16.0 over prebuilt packages included.

unicastbg said:
Hey guys, are you still using LOS 16 on your Mi 5s phones? Is there still need for up to date builds? I'm asking this because if it turns out no one's using this LOS version, then there's no need for newer builds. Like or reply if you want to continue receiving updates. I can also make custom builds with custom software installed, as per your liking. AdAway built in for example.
Click to expand...
Click to collapse
Yes, I am using it, super stable and smooth. And everything works! Thanks for your work, it would be great to have monthly builds!

ukiz said:
Yes, I am using it, super stable and smooth. And everything works! Thanks for your work, it would be great to have monthly builds!
Click to expand...
Click to collapse
Tell me about SOT?
The LOS18 is a mess for this phone and the LOS17, is bad too? Is only for use a lastest version of Android.
Thanks

mind_pt said:
Tell me about SOT?
The LOS18 is a mess for this phone and the LOS17, is bad too? Is only for use a lastest version of Android.
Thanks
Click to expand...
Click to collapse
I cannot say much about the SOT as my phone has a really bad battery, but the rom works just as well as the official one did.

ukiz said:
I cannot say much about the SOT as my phone has a really bad battery, but the rom works just as well as the official one did.
Click to expand...
Click to collapse
Thanks for your reply. But you don't convence me, to use the same android version I prefer use the MIUI.eu version.
Any other ROM

unicastbg said:
Hey guys, are you still using LOS 16 on your Mi 5s phones? Is there still need for up to date builds? I'm asking this because if it turns out no one's using this LOS version, then there's no need for newer builds. Like or reply if you want to continue receiving updates. I can also make custom builds with custom software installed, as per your liking. AdAway built in for example.
Click to expand...
Click to collapse
Thanks for the updates. My Mi5s is going strong, battery life as good as ever. I run battery charge limit and charge to 80%, recharge from 40%. Get plenty enough use during the day and it's very quick to charge when needed.
Coming up to 5 years, of use, it's the longest I've used the same phone. With everything working well including my banking apps it does what I need!
While it would be good to have a later android version, 16 works well on this device - appreciate your time to keep it updated.

EpicSauce said:
Thanks for the updates. My Mi5s is going strong, battery life as good as ever. I run battery charge limit and charge to 80%, recharge from 40%. Get plenty enough use during the day and it's very quick to charge when needed.
Coming up to 5 years, of use, it's the longest I've used the same phone. With everything working well including my banking apps it does what I need!
While it would be good to have a later android version, 16 works well on this device - appreciate your time to keep it updated.
Click to expand...
Click to collapse
I appreciate your feedback! My Mi 5s is also the only phone I've ever used for that long. And yes, Android 9 is getting old, but it will run for an year or two more. And by that time our phones will probably have some hardware defects forcing us to move to something newer.

I am also still using the mi5s, I am on the last official 16.0. I appreciate your effort and will install an update now.

frank7d said:
I am also still using the mi5s, I am on the last official 16.0. I appreciate your effort and will install an update now.
Click to expand...
Click to collapse
I've compiled the next build with the latest security patches. Uploading later today.

I tried to install your latest build.
I got a boot loop. After a couple of seconds the mi symbol again and again.. Then also installed the latest los 16 from january, to no avail.
Fortunately I managed to restore from backup, on the second try.

frank7d said:
I tried to install your latest build.
I got a boot loop. After a couple of seconds the mi symbol again and again.. Then also installed the latest los 16 from january, to no avail.
Fortunately I managed to restore from backup, on the second try.
Click to expand...
Click to collapse
What was the previous rom you used? Have you had such issues with previous builds, if coming from LOS16?

I am on official los16. (Updated from los15 in 2019) Regularly updated via its updater until January 2021. Magisk 23.0