Database Develop

[ROM][OREO][ks01ltexx][UNOFFICIAL][PREVIEW]crDroid v4.6-DiamondJohnDroid

{
"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:
#include
/*
* Your warranty is now void.
* and I didn't give you any warranty to begin with
*
* I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, 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, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
*/
crDroid G+ community
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.
Based on Lineage with extra goodies
Installation files & steps
Downloads :
NB: MUST USE OLD BOOTLOADER AND MODEM!! see LineageOS 15.1 thread
ROM: crDroidAndroid-8.1-20180917-ks01ltexx-v4.6.1-DiamondJohnDroid.zip MD5: ba48e90509017db02d767511af7fabac
Previous build: (will disappear as I am low on space!), and I know no known reason to use the older builds.
Rom :
The following two need the Newer I9506XXUDRB1 Modem and matching bootloader => I9506XXUDRB1_I9506XXUDRA1_bootmodem.tar
crDroidAndroid-8.1-20180911-ks01ltexx-v4.6-DiamondJohnDroid.zip MD5: daa44cc297fe7a2acfeb133c5c82e27a
crDroidAndroid-8.1-20180826-ks01ltexx-v4.6-DiamondJohnDroid.zip MD5: 6da18f10f38fbd0a54efd2a40a4d9f33
The following need the old J2 Modem and matching bootloader
crDroidAndroid-8.1-20180723-ks01ltexx-v4.5-DiamondJohnDroid.zip MD5: fc8b3a842e930202380aea13842b8c9f
crDroidAndroid-8.1-20180708-ks01ltexx-v4.4-DiamondJohnDroid.zip MD5: 831ccc71211bb444dfc04105f7449ef2
crDroidAndroid-8.1-20180515-ks01ltexx-v4.2.zip MD5: c2f4de35c418d074c82e7467740c5205
deleted crDroidAndroid-8.1-20180430-ks01ltexx-v4.2-DiamondJohnDroid.zip MD5: f5231e52e269c8cfce73c56de2a12ab2
TWRP: twrp-3.2.3-0-ks01lte.img
GApps : Opengapps 8.1
INSTALLATION INSTRUCTIONS
If you don't know how, then this isnt for you. But ensure you have a NANDROID as its not for daily use or replacement of your current ROM!
See the LineageOS 15.1 thread for hints: https://forum.xda-developers.com/ga...-lineageos-15-1-unofficial-galaxy-s4-t3747831
If you get a SystemUI has stopped during the first boot, click on wait not close/stop.
SuperUser is included in the ROM, but is switched OFF by default.
DEVICE: Samsung S4 - GT-i9506 - ks01ltexx
Recommended Bootloader / Modem: I9506XXSDPL2_I9506XXUDOJ2_bootmodem
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: crDroid
SELinux: ENFORCING
Sources:
https://github.com/crdroidandroid
https://github.com/kyasu/android_kernel_samsung_msm8974
https://github.com/kyasu/android_device_samsung_ks01ltexx
https://github.com/kyasu/android_device_samsung_msm8974-common
https://github.com/LineageOS/android_device_samsung_msm8974-common
https://github.com/kyasu/android_vendor_samsung_ks01ltexx
WITHOUT THE DEVICE TREE BUILT BY @kyasu THIS ROM WOULD NOT BE POSSIBLE
see: https://forum.xda-developers.com/ga...-lineageos-15-1-unofficial-galaxy-s4-t3747831 and show some well deserved thanks!
NB: THIS BUILD SHOULD BE CONSIDERED:==>
* I WILL NOT BE DEBUGGING THIS ROM, HOWEVER, PLEASE FEEL FREE TO POST ISSUES FOR THE BENEFIT OF OTHERS
* A ONE OFF BUILD, I WILL NOT BE DOING REGULAR UPDATES
* NOT BE CONSIDERED A DAILY CANDIDATE
* JUST A PREVIEW OF WHAT THE CURRENT STATE OF SOURCE CODE IS AT
Did I mention this would not be possible without the work by @kyasu, the crDroid & LineageOS teams.

Will try it rom, tks u for support

Thanks for posting, I personally still use version 14.1 of crdroid.
But what is the purpose if you're not gonna debug and maintain this rom?
I'm sure something will pop up...
Sent from my GT-I9506 using Tapatalk

DonAndress said:
Thanks for posting, I personally still use version 14.1 of crdroid.
But what is the purpose if you're not gonna debug and maintain this rom?
Click to expand...
Click to collapse
DiamondJohn said:
* JUST A PREVIEW OF WHAT THE CURRENT STATE OF SOURCE CODE IS AT
Click to expand...
Click to collapse
I personally am currently using my own build of Nougat ResurrectionRemix, which I have also shared here at XDA. I personally wanted to check if I could build a non LineageOS Oreo ROM using @kyasu LOS device tree's. ie Hopefully, in the future, when all the source code code is more stable, I will be able to build another ROM for my personal use (which I would also share).
aaand ... https://en.wikiquote.org/wiki/George_Mallory)
DonAndress said:
I'm sure something will pop up...
Click to expand...
Click to collapse
ALL the oreo code is still VERY early days, I dont think there are even too many official devices with releases yet ie not even Alpha's. You don't need to look too far before something "pops up"
DonAndress said:
if you're not gonna debug and maintain this rom?
Click to expand...
Click to collapse
Thats one of the brilliant things of open source code. There are a team of people working on LineageOS (the basis for crDroid and ResurrectionRemix), as well as people working on crDroid and RR, as well as the work being done by @kyasu specifically for our device. Any work they do, would flow through to anyone building the ROM from source. ie "I" do not specifically need to do the debugging, hopefully. And that makes me think of another reason, maybe this build will inspire someone else to give it a go.

DiamondJohn said:
I personally am currently using my own build of Nougat ResurrectionRemix, which I have also shared here at XDA.
Click to expand...
Click to collapse
I have to check your build then. I'm aiming for most debloated rom.
maybe this build will inspire someone else to give it a go.
Click to expand...
Click to collapse
You know I would but unfortunately I'm completely noob in this area. I don't even know where to start
Sent from my GT-I9506 using Tapatalk

DonAndress said:
I have to check your build then. I'm aiming for most debloated rom.
Click to expand...
Click to collapse
Do you consider lineageos bloated?
Big thanks @DiamondJohn for providing us with some options besides LOS! By the way, was the "ks01ltexxd" in the title intended?

PixelChris95 said:
Do you consider lineageos bloated?
Click to expand...
Click to collapse
Each Dev has a right to include all the crap he wants. I'm not saying that DiamondJohn does but still, some roms are faster and more battery efficient then other.
Sent from my GT-I9506 using Tapatalk

DonAndress said:
Each Dev has a right to include all the crap he wants. I'm not saying that DiamondJohn does but still, some roms are faster and more battery efficient then other.
Click to expand...
Click to collapse
Yes that's true, but since almost every custom rom is based on LOS I wouldn't expect a huge difference. Also in my experience the apps installed by the user or Google services eat up the battery, not so much the rom (of course the system consumes battery, but most of the time it's something else, if one has unusual high battery drain). I think if you really want to save energy you probably need to throttle the CPU. And Oreo isn't too great at saving battery at the moment (I am only talking about the builds available for our device of course). I hope this will get better in the future. I am using Oreo nevertheless because it's rock stabil and I like the features.

Interesting, what features are they?
Sent from my GT-I9506 using Tapatalk

DonAndress said:
Interesting, what features are they?
Click to expand...
Click to collapse
Picture in picture mode, autofill framework and the design are the new features I benefit the most from. Might be different for others of course.

PixelChris95 said:
Do you consider lineageos bloated?
Click to expand...
Click to collapse
I'd like to hear the answer to this question.
I dont think you should be looking at ROMs like ResurrectionRemix or crDroid if you wish to be running "light", and I would also go for PICO GApps (which is what I run).
PixelChris95 said:
By the way, was the "ks01ltexxd" in the title intended?
Click to expand...
Click to collapse
nope, thanks, and corrected
DonAndress said:
Each Dev has a right to include all the crap he wants. I'm not saying that DiamondJohn does but still, some roms are faster and more battery efficient then other.
Click to expand...
Click to collapse
As this was a build straight from the source (I only changed one line to make it permissive), its the decision of the devs at the crDroid Team, not me.
By the way, whenever I have looked at the changes made in crDroid, the non-device specific code changes has always been by a single dev. I am sure its a group that decides on bigger things, like what to include, just interesting that shared (between devices) code almost seems to be maintained by a single guy.
PixelChris95 said:
Yes that's true, but since almost every custom rom is based on LOS I wouldn't expect a huge difference. Also in my experience the apps installed by the user or Google services eat up the battery, not so much the rom (of course the system consumes battery, but most of the time it's something else, if one has unusual high battery drain). I think if you really want to save energy you probably need to throttle the CPU. And Oreo isn't too great at saving battery at the moment...
Click to expand...
Click to collapse
I am running Nougat ResurrectionRemix, and to limit my battery drain, I have Greenify running VERY aggressively. I also have the CPU at standard max, but a conservative governor; Tripndroid, which doesn't seem to lag for my usage, but likes the lower frequencies.
PixelChris95 said:
I am using Oreo nevertheless because it's rock stabil and I like the features.
Click to expand...
Click to collapse
I am guessing you are running LOS. The latest build appears to have caused some "noise", which worries me as this build is based on similar code. GPS also appears to be a common issue. I tried GPS on this build and it didnt connect to any satellites (I was inside, and it was heavily overcast that day) but when I restored my daily and it didnt lock a location either (but at least connected to a few satellites). I'd be interested to know by anyone who tries this ROM if the GPS works? That's a deal breaker for me personally. The "efs" partition talk also really concerns me.

New build!
There is anew build up (see OP). This build was basically a test to see what would happen (ie would it even boot) if the SELinux was ENFORCING
Make sure you flash GApps along with the ROM before the first boot. I accidentally booted without GApps and then flashing it after caused issues.
I also tried Magisk 16.0 for root, and that appeared to work. Instead of the LineageOS add-an
I also tried flashing Viper, and that worked as soon as I switched over to permissive. I also took a log to see what permissions/SELinux statements would enable it to run enforcing.
I did appear to have issues the second time I flashed it with ADB over WiFi (it didnt pop up the request/confirmation).
I am also hoping that the GPS will be fixed soon in the LOS 15.1 builds which will hopefully flow through to crDroid:fingers-crossed:
Remember, this is unofficially an an unofficial build:silly:

does not work NFC

DiamondJohn said:
I dont think you should be looking at ROMs like ResurrectionRemix or crDroid if you wish to be running "light"
Click to expand...
Click to collapse
You don't think crdroid is light?
I've been using it for a year now and I believe it's pretty light.
Sent from my GT-I9506 using Tapatalk

DonAndress said:
You don't think crdroid is light?
I've been using it for a year now and I believe it's pretty light.
Click to expand...
Click to collapse
Feature wise, it is NOT light; as it is very featured. Those features come from code.
To me, if you truly want light, you go with a "vanila" AOSP ROM. I am NOT talking about how they run, but their contents. On a different device (xt907) I built a number of Nougat ROMs, and AICP actually seemed noticeably "snappier" to me than crDroid or RR. A ROM not being light, does not mean it is slow.
Not that's its an accurate comparison of anything, but comparing the Oreo file sizes,
LOS 15.1 = 359MB
RR v6.0.0 = 329MB (I recently did a test build, and it booted and ran :victory
crDroid v4.0 = 385MB
also, the main build section has "steps" when compiling a ROM, below are the results from the last time I compiled each of these
LOS 15.1 = 75755
RR v6.0.0 = 76872
crDroid v4.0 = 77145
On a side note, I have another device (Nexus 5, the xt907 has died) and that has an RR Oreo ROM at around 359MB and an AOSP ROM (v8.0) at 297MB.
By the way, RR is my ROM of choice, as (I think) this device is much more than capable of handling just about any ROM we can thrown at it, at least thus far for me.:good:

onenett said:
does not work NFC
Click to expand...
Click to collapse
Do you know if it works on the Oreo LineageOS builds?

out of interest
There has been over 100 downloads of the ROM. Is anyone actually using it as a daily? or simply as a preview? noting that was the actual purpose; ie a preview not a daily.

BEST ANDROID OREO ROM FOR - S4 I9506 ks01ltexx
DiamondJohn said:
There has been over 100 downloads of the ROM. Is anyone actually using it as a daily? or simply as a preview? noting that was the actual purpose; ie a preview not a daily.
Click to expand...
Click to collapse
Hi DiamonJohn,
I'm giving a daily test although this is not the case, but I'm even amazed by the result even with this state of the ROM.
In terms of apps, everything works, at least the ones I use daily basis that are; Facebook, Messenger, Inbox "2 email accounts", Outlook "1 email account", Google Keep, DropBox, Skype, Twitter, Youtube, etc..., bluetooth works and I'm going to test the GPS tomorrow when I go running
What I mean is that even though not being for daily use (for now) this ROM is not too far from that in my point of view, of course you still need a lot of work ahead and the battery does not last long but what does it matter at this stage since the RR roms happens the same :laugh:
With spirit and with head this rom can get very good at level ★ ★ ★ crDroid ★ ★ ★ Official[7.1.2][ks01lte][V3.5][09 JUN] and by the way, it's the rom I use every day and it's great.
I was going to forget to mention, Magisk Manager, Xposed and Greenify they are installed and working properly.
For now is everything and I hope this rom go forwar, I am very interested because my GALAXY S4 LTE still has much to give :good:
And I say even that this ROM in the point that is, deserves the title that I gave :angel:

pedra3000 said:
... and I'm going to test the GPS tomorrow when I go running ...
Click to expand...
Click to collapse
I would not expect the GPS to be working. It was built without a change from LOS that would fix it. But I tried including the code, which didn't appear to work for me, and only after realised that I had a hardware issue (my antenna wasn't connecting well physically on the device fixed now) I am now waiting (patiently) for @kyasu to update his actual device tree with the changes.
I have also built an Oreo ResurrectionRemix. I am hoping someone will test applying a substratum theme against one of these Oreo ROMs (although I haven't made public the RR one) I have built. That (and the GPS) are probably my roadblocks right now foir me to upgrade and thereby be more frequent with new builds; ie I dont know if Substratum works or not. I have tested Viper (another one of my personal deal-breaks, and that works)

GPS Works well
Surprise LOL, GPS works well with me!
I use Endomondo - Running & Walking and GPS and continued to work well, without having the 4G connected!
I installed the GPS TESTE to see how many satellites it picks up and the accuracy and it seemed to me everything normal (view image link)
https://www.dropbox.com/s/kycoe6blbovs78g/Screenshot_GPS_Test_20180327-082957.png?dl=0
About the Resurrection Remix I tested (Nougat) are good, but the battery is the weak point, because until now they all drain very quickly, which can not be for me to be daily use. As I mentioned, the crdroid ★ ★ ★ ★ Official [7.1.2] [ks01lte] [V3.5] [09 JUN] the battery is very good and for now is my choice for daily use.
I want to update to the OREO and so far and I have always liked crDroid for better results this your unofficial ROM is very very good :good:
Of course I'm here to test your Oreo RR

[ROMs][TREBLE] OpenKirin AOSP Collection

{
"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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei Mate 9.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei Mate 9
Contributors
OldDroid, XePeleato, rcstar6696, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27

Thanks for this! I am running the CarbonROM Beta 2 from the partner builds (released July 17). I notice that there is now an official version that is also labeled as Beta 2, but was released five days later (July 22). Can I flash the official build without going back to full stock first? Also, the newer build is significantly smaller: 599MB versus 1.6 GB. Is that because the newer build doesn't include GAPPS?
Thanks again and sorry if I missed the answers to these questions.
As an aside, I'm really liking CarbonROM. Great battery life and very smooth.

tim.malone said:
Thanks for this! I am running the CarbonROM Beta 2 from the partner builds (released July 17). I notice that there is now an official version that is also labeled as Beta 2, but was released five days later (July 22). Can I flash the official build without going back to full stock first? Also, the newer build is significantly smaller: 599MB versus 1.6 GB. Is that because the newer build doesn't include GAPPS?
Thanks again and sorry if I missed the answers to these questions.
As an aside, I'm really liking CarbonROM. Great battery life and very smooth.
Click to expand...
Click to collapse
the newer builds are xz compressed, you have to decompress them first.
If its the same rom (e.g. carbon -> carbon) you don't have to do a factory reset.
Regards

Thanks! And now I realize that I can't read and misread OmniROM for CarbonROM. Oops.
OldDroid said:
the newer builds are xz compressed, you have to decompress them first.
If its the same rom (e.g. carbon -> carbon) you don't have to do a factory reset.
Regards
Click to expand...
Click to collapse

What's the difference between OpenKirin LOS and Phusson's LOS?

kkslider1 said:
What's the difference between OpenKirin LOS and Phusson's LOS?
Click to expand...
Click to collapse
Phh LOS is a generic build meant for any device with treble support. The OpenKirin build is specifically targeted to Kirin devices.
Most of the changes are for dealing with the ways Huawei did things differently than everyone else. Also built in is the Huawei camera app, so (most of) the native camera functionality is available.

irony_delerium said:
Phh LOS is a generic build meant for any device with treble support. The OpenKirin build is specifically targeted to Kirin devices.
Most of the changes are for dealing with the ways Huawei did things differently than everyone else. Also built in is the Huawei camera app, so (most of) the native camera functionality is available.
Click to expand...
Click to collapse
Thanks! I want to try OpenKirin LOS (OKLOS), but how will I be able to flash Magisk without TWRP? OpenKirin LOS says that it requires the stock EMUI recovery, so how can I flash Magisk?
---------- Post added at 12:08 PM ---------- Previous post was at 11:38 AM ----------
Okay, so I clean flashed OpenKirin LOS Beta 5 on my MHA-L29. Fingerprint gestures are disabled/greyed-out despite the Mate 9 having a rear fingerprint sensor. Fingerprint gestures worked perfectly on Phh LOS, so I'm not sure why OKLOS isn't working on that end.
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Another issue I found: On OKLOS, the Mate 9's secondary top speaker isn't working when playing media. To be fair, it didn't work on Phh LOS either, so I'm not sure if that's an issue you guys can fix.

kkslider1 said:
Thanks! I want to try OpenKirin LOS, but how will I be able to flash Magisk without TWRP? OpenKirin LOS says that it requires the stock EMUI recovery, so how can I flash Magisk?
Click to expand...
Click to collapse
Use 'fastboot' command.
-> extract stock boot image, patch it by magisk manager, flash patched boot image by fastboot.
Or you can install (patch boot image and replace it ) in magisk manager directly.

michael_hamada said:
Use 'fastboot' command.
-> extract stock boot image, patch it by magisk manager, flash patched boot image by fastboot.
Or you can install (patch boot image and replace it ) in magisk manager directly.
Click to expand...
Click to collapse
Thanks! Much appreciated!
After a few days of running on my Mate 9, OKLOS is running super smooth! Much smoother than Phh LOS. Hoping @OldDroid and the team can address a few of the bugs listed in my earlier post. Keep it up!

kkslider1 said:
Thanks! I want to try OpenKirin LOS (OKLOS), but how will I be able to flash Magisk without TWRP? OpenKirin LOS says that it requires the stock EMUI recovery, so how can I flash Magisk?
---------- Post added at 12:08 PM ---------- Previous post was at 11:38 AM ----------
Okay, so I clean flashed OpenKirin LOS Beta 5 on my MHA-L29. Fingerprint gestures are disabled/greyed-out despite the Mate 9 having a rear fingerprint sensor. Fingerprint gestures worked perfectly on Phh LOS, so I'm not sure why OKLOS isn't working on that end.
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Another issue I found: On OKLOS, the Mate 9's secondary top speaker isn't working when playing media. To be fair, it didn't work on Phh LOS either, so I'm not sure if that's an issue you guys can fix.
Click to expand...
Click to collapse
disable the navbar to turn on navigation gestures.
This will be adressed in the next los beta so you can toggle the nav gestures with navbar enabled.
EDIT: please have a look at our telegram group if you need any guidance regarding the installation of magisk without a custom recovery (e.g. twrp).
Regards

i have a question , is it possible that ota to pie from lineageOS beat5 wihtout back to emui8

fate forget said:
i have a question , is it possible that ota to pie from lineageOS beat5 wihtout back to emui8
Click to expand...
Click to collapse
Flash new ROM & stock ramdisk (if you rooted with Magisk). Factory reset with stock recovery.

irony_delerium said:
Flash new ROM & stock ramdisk (if you rooted with Magisk). Factory reset with stock recovery.
Click to expand...
Click to collapse
thanks,I'm sorry for bothering you that,do you know how long will openkirin ROMs(for mate9) update everytime?

fate forget said:
thanks,I'm sorry for bothering you that,do you know how long will openkirin ROMs(for mate9) update everytime?
Click to expand...
Click to collapse
@OldDroid @irony_delerium This is something I'm also curious about. What is the average time between the 5 Betas for OKLOS? The changelog only shows the release date of the latest beta, not the previous versions.

kkslider1 said:
@[email protected]_delerium This is something I'm also curious about. What is the average time between the 5 Betas for OKLOS? The changelog only shows the release date of the latest beta, not the previous versions.
Click to expand...
Click to collapse
monthly security patches are guaranteed.
Regards

hello,
is there any way how the bugs should be reported?
In LOS Beta 5 I discovered that if trying to enable Bluetooth trigger in a Profile, the Settings crash. My phone is Mate 9.
PS Otherwise, the only thing I can say is Hats off to the developers! When I received the phone as a replacement (for a broken Nexus 6p) I thought "oh, crap: no Snapdragon, no LOS". This really made my day!

vedko said:
hello,
is there any way how the bugs should be reported?
In LOS Beta 5 I discovered that if trying to enable Bluetooth trigger in a Profile, the Settings crash. My phone is Mate 9.
PS Otherwise, the only thing I can say is Hats off to the developers! When I received the phone as a replacement (for a broken Nexus 6p) I thought "oh, crap: no Snapdragon, no LOS". This really made my day!
Click to expand...
Click to collapse
i'm aware of this issue. It will be adressed in the next update.
Regards

OldDroid said:
i'm aware of this issue. It will be adressed in the next update.
Regards
Click to expand...
Click to collapse
Thanks.
Although I meant it mainly as a general questions where the bugs should be brought up. In this thread? Or in the Telegram channel referenced in the 1st post? Or...?
PS I found out that NFC is not working, but that seems to be a known issue.

errors in logcat (omnirom)
Hello,
I am trying out OmniROM and I have been getting less than stellar battery life (though still acceptable). I took a look at the MatLog app and noticed a bunch of errors that keep coming up. One of them is from BatteryExternalStatsWorker: "no controller energy info supplied for wifi".
I googled around a bit and it appears this has popped up on other ROMs and it seems to be related to a missing API. There are other errors as well, many of them thrown by HWComposer: "invalid layer type change".
I have no idea if these are impacting battery life, but an error is an error.
I attached a zip with logs from MatLog.
Thanks.

Dear MR.OldDroid
Is it possible for you to add UMS (USB mass storage function, connect pc and turn Micro SD card in photo to be a removable flash disk on PC) into the Kernel? I like this function, it is much better than MTP function.
Thank you very much.

[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][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