[ROM][12.0][Begonia] LineageOS 19.0 [UNOFFICIAL] - Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe

[ROM][12.0][Begonia] LineageOS 19.0 [UNOFFICIAL] - Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe

abhi.xv said:
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation Guide
Flash MIUI 12.5 ROM
Flash 12.5 based TWRP Recovery i.e - https://t.me/RedmiNote8ProOfficial/1078326
Boot to Recovery
Wipe System, Data, Dalvik, Cache & Vendor
Flash MIUI 12.5.x based firmware zip since it does not include firmware
Flash ROM zip & Gapps since it is a Vanilla build
Flash DFE & Format data
Reboot to System
Download Vanilla BuildChangelogs:
Initial Vanilla build
Prebuilt GrapheneOS Camera
Android OS version: 12
Device: Redmi Note 8 Pro (Begonia)
Security patch level: December 2021
Build author: abhixv
Kernel Source: Kernel
Support Group: https://t.me/dreamsupportbegonia/185175
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
Is step #5 really necessary? If in step #1 a fastboot ROM is used it already contains the firmware.
Also what's the status on SeLinux and SafetyNet?
Very nice and good job!
Compass.

Compass Linux said:
Is step #5 really necessary? If in step #1 a fastboot ROM is used it already contains the firmware.
Also what's the status on SeLinux and SafetyNet?
Very nice and good job!
Compass.
Click to expand...
Click to collapse
Hello Compass,
Step #5 isn't necessary to do so, but some users ping about the brick they faced while shifting from any other rom so i usually Suggest Users to flash FW too
For now SELinux is permissive & Cts fails by default but can be fixed using mods & hide props.

I hate Android 11/12 but this looks promising.
Also can't we just use Dynamic TWRP? (Yes we can)
Installed it and the issues are:
1)From restoring a backup,it may say it can't contact google servers,in that case re-login and it should be solved.
2)I can't find OEM unlocking in the settings
3)Can't change button shortcuts.They always stay the same
Also DON'T use UnicornHorn Kernel on this ROM due to the Android version,though you'll most likely end up in a soft-brick (Learned that the hard way)

Im so curious about battery life. I've tried couple of A12 rooms for N8P and all of them had the worst battery stats. I would only get 3and half SOT which is so bad.

devidfink said:
Im so curious about battery life. I've tried couple of A12 rooms for N8P and all of them had the worst battery stats. I would only get 3and half SOT which is so bad.
Click to expand...
Click to collapse
Based on my experience,it's better than MIUI 12 (no battery drainage happened to me in both versions)

Hello! How to build this ROM? Is there an instruction?

Hi my wifi sharing connection is connected but cannot access internet
Notifications works, Facebook app too, but Chrome doesn't neither Google Play store
So weird...

Why is "Material You" theming system not working? Is this something about this particular ROM? Or is it an app problem? Or is it just for me?

Can someone help ?

Hello, I've tested the ROM and it looks good 'till now. The only problems I had were:
- first time I've installed it from stock ROM (MIUI 12.5.x) I've soft-bricked it (dunno how) - [after installing the ROM]. I couldn't get to the recovery. I mean, I've got there, but the slider didn't showed up (only the twrp banner), stayed like this for ~1 min and then automatically rebooted and then back again and so on. I've unbricked it by reflashing `boot.img` (I could get into fastboot mode). Still, after reflashing I couldn't get to the recovery (same story but not bootloop).
P.S: I've also tried a dozen other TWRPs, none worked.
I've installed the stock ROM again and reinstalled the custom one (this time the recovery problem is not present, I can access TWRP now).
- It lags a bit sometimes, for instance when you unlock it and move between screens.
- Can't adjust the volume of call when on speaker (it stays the same - loud enough).
I would like to know how to set SELinux to enforcing. `echo 1 > /sys/fs/selinux/enforce` didn't worked out.
Edit: Also, alongside the SELinux notification that pops up when the phone starts, I get another notification from Trust that says that this build was signed with public keys.

Update: I've managed to set SELinux to Enforcing mode by editing this Magisk module, but...
1. The fingerprint sensor didn't worked after that
2. Files app crashed at open
3. Couldn't take screenshots
and probably there were more issues to be discovered.

0xreloadedd said:
Hello, I've tested the ROM and it looks good 'till now. The only problems I had were:
- first time I've installed it from stock ROM (MIUI 12.5.x) I've soft-bricked it (dunno how) - [after installing the ROM]. I couldn't get to the recovery. I mean, I've got there, but the slider didn't showed up (only the twrp banner), stayed like this for ~1 min and then automatically rebooted and then back again and so on. I've unbricked it by reflashing `boot.img` (I could get into fastboot mode). Still, after reflashing I couldn't get to the recovery (same story but not bootloop).
P.S: I've also tried a dozen other TWRPs, none worked.
I've installed the stock ROM again and reinstalled the custom one (this time the recovery problem is not present, I can access TWRP now).
- It lags a bit sometimes, for instance when you unlock it and move between screens.
- Can't adjust the volume of call when on speaker (it stays the same - loud enough).
I would like to know how to set SELinux to enforcing. `echo 1 > /sys/fs/selinux/enforce` didn't worked out.
Edit: Also, alongside the SELinux notification that pops up when the phone starts, I get another notification from Trust that says that this build was signed with public keys.
Click to expand...
Click to collapse
I wouldn't suggest enabling SELinux on this ROM because it's doesn't work properly. Try using Dynamic TWRP for the recovery and flash a fastboot stock ROM instead of recovery ROM because recovery ones do not contain the proper firmware.

do you have a set of build files for this?
eg: https://github.com/LineageOS/android_device_xiaomi_begonia

where is the gapps file?

LoS20 = https://drive.google.com/file/d/1aOe8krfBWI5YFtypr3PjXN3KY3gHVUnj/view

Related

[ROM][Unofficial] LineageOS 13.0 for OnePlus 2 [06/01]

I know some of you may wonder why even post something as old as marshmallow. I still get a lot of use from LOS 13, and have been building it for myself for a while. I figured I'd upload the latest with Jan security patches, for those who want it. Happy flashing.

Not sure about the support we'll get from LOS going forward. They never merged February security patch, but they may have just been busy. We'll see.

does it have hal3 with hdr and all that cool quality we used in marshnallow?

chxei said:
does it have hal3 with hdr and all that cool quality we used in marshnallow?
Click to expand...
Click to collapse
It does, HAL3 and hdr
I run mine with amplify, greenify, android n-ify, gravitybox, and alert slider app

monark88 said:
LOS 13.0 Unofficial, ROM for the OnePlus 2
Click to expand...
Click to collapse
wow, this is great!
thank you mate!

You can get volte by flashing the kenzo patches. Just saying.

I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.

Woodzrul said:
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Click to expand...
Click to collapse
The download link now points to a signed version. You can download it here:
https://www.androidfilehost.com/?fid=673956719939814327

using 22nd Jan build since yesterday.
I missed so much the great customization that CMTE brings to LOS!
as far as I can see 'til now, there's no issue at all with your ROM.
excellent work, thank you!

utkarsh102 said:
You can get volte by flashing the kenzo patches. Just saying.
Click to expand...
Click to collapse
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?

GuyGotMadNameGame said:
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
Click to expand...
Click to collapse
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.

utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
I'll add this to the first post

utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
Thanks for this. I updated first post.

Does anyone know of any cm13 theme which properly themes all the essential apps?

This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!

aiwan3 said:
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
Click to expand...
Click to collapse
I've got a new build, but nothing is significantly changed. I've been working on a custom kernel for MM, with extra governors and upstream merges. I'm running this ROM myself, so you can bet when there is a security patch, I'll upload it for us all.
I'm with you on anything above android 6.0. When LOS 14.x kernel was reworked, I was on RR unofficial. I remember the drastic changes. I compiled this not soon after and have been on it since. I've watched on the forums as everyone has scrambled after HAL3, and balancing HAL3 with HDR (or the lack there-of) and all the non-sense that goes with it.
Meanwhile we've got manufacturer supported blobs and code for everything our phone was meant to do, in a nice stable OS.
If you're reading this, and thinking about trying it, just download the ROM, flash xposed (or use xposed magisk) and get Android N-ify, Amplify, Greenify, Alert Slider, and GravityBox. You'll be kicking it on the OP2 old school, updated, and stable.

That's right. Many people don't seem to be very methodical when testing new ROMs. Mostly noted on comments about battery life. I don't use my phone much as the majority of my daily work / comms happens on PC - so its easy for me to see changes when I update the phone. I don't use gapps either, so my testing is purely based on the kernel and the ROM performance. This ROM can go up to 5-6 days in idle / light usage, whereas the latest official LineageOS 14.x is probably around 4 days same use. Feel free to test. Same applies to boeffla-kernels, they consume much more battery on idle than the LineageOS stock.
I'm not a developer myself but it's easy to understand that all this hacking for newer Android versions than the source code provided by manufacturer, can very easily lead into problems. It could be ok, but unfortunately many people always think that the latest is always better. I think it's fair to say that new android versions just complicate the menus and slow down devices more than the useful features provided. As long as security is updated, I don't really see any need for Oreo in my phone.
It's nice to hear that you are also testing for new things in kernel, I might test them if provided as separate update.zip. However I assume most people using LOS 13 or your build are probably after stability.

Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?

Jackill said:
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Click to expand...
Click to collapse
Lol, for the most part (and in my opinion) yes.
The catch is that if you like the latest cutting edge features, we don't have that built-in here. All we offer is a stable phone that has ALL of the features working in some form or another, without wondering what will break in the next build.
For the record, I still flash Oreo ROMS on MultiROM to stay aware, but I run this as a daily driver.

[ROM][OFFICIAL][NIGHTLIES] LineageOS 17.1 Harpia

Reserved

Always giving thanks to @facuarmo and @Akyanonimous for the great support

Help. i tried to flash this ROM and my phone have bootloop.

I was a long term user of Pixel Experience ( Android 9 / Pie) and enjoyed it's stability. As it is no longer maintained I thought I would try out some of the latest Android 10 / Q ROMs to see how they compared. I still kept the zip file for Pixel on my SD card by way of a fall back if I wasn't happy with the latest unofficial Android 10 ROMs.
I gave Havoc OS a try for a few days and to an extent I liked it with the ability to very much set up the ROM as you like with multiple customisation options. I , however, found that the overall experience wasn't very good with quite a bit of lag and some random crashes of apps etc. I am sure with future updates it will be a much better ROM and I may well give it another try out.
After Havoc I went back to Pixel Experience for a few weeks until the next unofficial Android 10 ROM was released. Thus far I have been very happy with Lineage 17 with no bugs , lag , crashes or issues at all thus far. The only slight grumble is that the music app widget is not really required on the ' 2nd page ' and indeed was just a big black blob. I deleted it straight away. I will probably continue to use this as my daily driver for some time to come and give thanks to @jeferson1979 and any other Devs who contributed for all their hard work and for us to be able to keep our old Harpia phones going with the latest android version.

Indiawallah71 said:
I was a long term user of Pixel Experience ( Android 9 / Pie) and enjoyed it's stability. As it is no longer maintained I thought I would try out some of the latest Android 10 / Q ROMs to see how they compared. I still kept the zip file for Pixel on my SD card by way of a fall back if I wasn't happy with the latest unofficial Android 10 ROMs.
I gave Havoc OS a try for a few days and to an extent I liked it with the ability to very much set up the ROM as you like with multiple customisation options. I , however, found that the overall experience wasn't very good with quite a bit of lag and some random crashes of apps etc. I am sure with future updates it will be a much better ROM and I may well give it another try out.
After Havoc I went back to Pixel Experience for a few weeks until the next unofficial Android 10 ROM was released. Thus far I have been very happy with Lineage 17 with no bugs , lag , crashes or issues at all thus far. The only slight grumble is that the music app widget is not really required on the ' 2nd page ' and indeed was just a big black blob. I deleted it straight away. I will probably continue to use this as my daily driver for some time to come and give thanks to @jeferson1979 and any other Devs who contributed for all their hard work and for us to be able to keep our old Harpia phones going with the latest android version.
Click to expand...
Click to collapse
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).

Sakul94 said:
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Click to expand...
Click to collapse
I have indeed installed the latest Lineage 17.1 Rom and it works great. I , too , have the latest TWRP and found it very straight forward to install the zip file for Lineage , with ARM GAPPS for Android 10 and the latest Magisk for rooting my device. I assume when flashing the Rom etc you did a clean install by doing an Advanced wipe of Davlik/ART Cache , System , Data and Cache before proceeding. Good luck and hope you are able to get it going.

Indiawallah71 said:
I have indeed installed the latest Lineage 17.1 Rom and it works great. I , too , have the latest TWRP and found it very straight forward to install the zip file for Lineage , with ARM GAPPS for Android 10 and the latest Magisk for rooting my device. I assume when flashing the Rom etc you did a clean install by doing an Advanced wipe of Davlik/ART Cache , System , Data and Cache before proceeding. Good luck and hope you are able to get it going.
Click to expand...
Click to collapse
Yes, i did every step to flash this ROM but no result. The phone have bootloop.

latest TWRP for harpia is 3.2.3-r1. find that here - https://forum.xda-developers.com/devdb/project/?id=16870#downloads
try that and see if it bootloops.

bacanos said:
latest TWRP for harpia is 3.2.3-r1. find that here - https://forum.xda-developers.com/devdb/project/?id=16870#downloads
try that and see if it bootloops.
Click to expand...
Click to collapse
Thank you very much. You are an genius.

@jeferson1979 Your roms are what a rom should be! I have never thought that android 10 can run this smooth in this tiny device. All Thanks to you. Rom is very stable and is best rom available right now after AEX pie which is again your offering.
Unlike past developers your focus is more towards usage and fixing things rather than pure compiling/half baked pieces and that's what old time developing was...
Thanks to keeping this device alive. I use it because of it's light and small and easy to carry.
Now the only thing remaining is- I guess SELinux.

Thanks for all the work, I will flash this later today and post my feelings. Would it be possible to make this an official build? I loved the automatic updates via OTA from the official builds.

The ROM works great, however SELinux is not enabled, would it be possible to enable it?

Sakul94 said:
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Click to expand...
Click to collapse
Liteh said:
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Click to expand...
Click to collapse
you can manually set SELinux to enforcing by enabling the terminal shell in the Developer options and using the command, "setenforce enforcing"
this enables enforcing but i have no idea if the SELinux policy is written or doing what it needs to be doing, and this manual enforcing only lasts until reboot. does anyone know more on this subject?

Liteh said:
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Click to expand...
Click to collapse
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing

jeferson1979 said:
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
Click to expand...
Click to collapse
That's great, I'll be waiting for the next update. After a day using it, I have to say that it is indeed a wonderful ROM, very fluid and responsive.

Flashed this ROM, till now everything works great. Thank you!
Gesendet von meinem GM1903 mit Tapatalk

jeferson1979 said:
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
Click to expand...
Click to collapse
Can you please also release Android GO variant of Lineage. Recently I have seen one Go device, and it was so smooth even with 1GB RAM. We have 2GB so I guess Android GO will improve responsiveness and battery life slightly? Please correct me if I'm wrong.

newinnov said:
Can you please also release Android GO variant of Lineage. Recently I have seen one Go device, and it was so smooth even with 1GB RAM. We have 2GB so I guess Android GO will improve responsiveness and battery life slightly? Please correct me if I'm wrong.
Click to expand...
Click to collapse
You will see some minor improvement at memory management, but we will loose in other side. Maybe we can do some tests

I agree with newinnov. In fact i think it should be nice for the LineageOS team to keep supporting older devices (like ours) officially but in Android GO form. It would keep millions of phones out of landfills.
In our case I think the benefits overcome the loses. At this point i'm sure all of us are using our g4p for bare minimun tasks like whatsapp, email, browsing, social networking, and such. Mostly no functionality-intensive apps. Given that all of that can be done with Android GO i don't think we would lose that much

[DISCONTINUED][ROM][PAYTON]LineageOS 19.1 (Android 12.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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Introduction
This is the official Lineage OS thread for the Motorola Moto X4, codename payton.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install via Lineage Recovery
Please follow the official instructions
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Update LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to install via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
How to upgrade from the previous version via Lineage Recovery
Please follow the official instructions
Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to upgrade from the previous version via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
ADB sideload the newest weekly build or copy it to your device and install the zip
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
Notes
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download
Official:
LineageOS Downloads
download.lineageos.org
Unofficial test builds:
https://osdn.net/projects/lineageos-for-payton/releases/p17369
Google Apps (GApps)
MindTheGapps:
Codefire - Listing of gapps
GCam Mods
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
Contributors
erfanoabdi, SevenRock, ThE_MarD, Moto sdm660 devs, the Lineage Team
Source Code: https://github.com/LineageOS
ROM Firmware Required: Official Pie

Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org

Heyyo, a new test build is going up! lineage-19.1-20220416-UNOFFICIAL-payton contains Moto Camera 2 app and fixes for offline charging as well
Release lineage-19.1 lineage-19.1-20220416-UNOFFICIAL-payton - lineageos-for-payton - OSDN
Release lineage-19.1 lineage-19.1-20220416-UNOFFICIAL-payton - lineageos-for-payton #osdn
osdn.net
VERY special thanks to SevenRock for doing the majority of the LOS 19.1 trees for Moto sdm660 and payton

I decided to take the plunge tonight, waste a few hours and try out the 20220416 test build. So far so good, though I'll grant you I've only had it running for a couple hours. The install going from 18.1 to 19.1 went smooth. I'm not sure if audio will end up a little weak when calling someone. When I did a Voice call from my google number to my phone number, and then played back the message, my voice sounded a bit weak vs the voice mail prompts. I need to try it with a real phone call and see if others think I sound weak.
Apps seem to be running fine so far, though I'm a fairly light user. The only issue I've seen is TWRP 3.5 seems to get stuck in a boot loop when rebooting to recovery from lineageOS 19.1 but didn't when rebooting from TWRP. My new laptop doesn't seem to like fastboot, so I need to try lineage recovery install from another computer and see if that fixes it. I know TWRP isn't officially supporting Android 12 yet, and suspect this isn't an issue with your build. This did prevent me from trying Magisk, so that will need to wait too.
Can't say I'm a fan of the new "Material You" theme. The new quick tiles are annoyingly large. I need to figure out how to get a sound toggle tile to work right. But again, those are general OS issues and nothing to do with the build you did!
I'll see how it fairs over the next couple days and let you know, but so far seems good. Thanks for the build!

I installed this rom but can't get Magisk installed. Anyone know how?

Heyyo guys, for TWRP please try my latest test build
[OFFICIAL&TESTS]TWRP for the Motorola Moto X4 (Payton)
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com

I installed the 16 Apr build Sun night using NikGapps 13 Apr stock (excluding Pixel Launcher since I'd had issues with it on the prev build) and the Fi add-on. Other than having to clear storage/cache for Conn Services and Fi, everything has been working really well. Setup was much smoother this time, MotoCam2 is really nice, and also no random reboots like on the 22 Mar build.
When upgrading from the 22 Mar to 16 Apr build though, I got a boot loop and had to clean install. I'd had the same issue in the past back when I used the unofficial 18.1. Is this a known issue? Official 18.1 builds never had this problem. I guess next time I'll first try disabling security unlock.
Btw, is this really 12.1 and not 12.0? The phone settings only indicate '12'. I used the 'S' gapps and not 'SL', fwiw. Thanks!

The 4/16 build has been running fine for me the last few days. I may need to decrypt to get a working recovery it seems. Other than that the couple things that look like they're missing from settings are:
I don't see anywhere to adjust the color palette. It's purely based on wallpaper derived colors. Sounds like stock 12 supports modifying, does lineageOS not? I really don't like having my colors dictated by the wallpaper.
Accesibility/Vibration & Haptic strength -- this menu has no haptic strength control despite the name. It'd be nice if it did. I know this has existed in at least some of the past ROMs, though can't recall if that was Havoc or LineageOS.
Otherwise bluetooth, wifi, calling, messaging all seem good as does interaction.
I also ended up using NikGapps 13 simply because that was what I had good luck with on 18.1.
I'm not sure about the bootloop jeremywh7 saw as I went directly from 18.1 to the 0416 19.1 build with a clean install. If there's another test build and once I get a recovery working, I can try doing a dirty flash for an upgrade. I know on 18.1 I was able to dirty flash w/o a problem.

So far so good but I haven't done extensive testing yet. I got Magisk working.

Nice

Heyyo @jeremywh7, LineageOS 19.1 is Android 12.1 so you must use Android 12.1 (12L) GApps which might be your bootloop issue.
The color palette is indeed picked by the wallpaper which is annoying... It thinks my background of my family should mean my color is a skin-colored pink... oof lol

ThE_MarD said:
The color palette is indeed picked by the wallpaper which is annoying... It thinks my background of my family should mean my color is a skin-colored pink... oof lol
Click to expand...
Click to collapse
Yeah, I'd agree that's not a great choice on it's part! So I take it that for LineageOS 19.1 at least it's expected to have no control of this? I was under the impression that with stock Android 12 you could disable the automated picker and manually choose a color which I don't see in 19.1. If true that sounds like going with a 3rd party tool do do so

@ThE_MarD
Congrats!!! First official Lineage OS 19.1 payton build from the roaster
My question: Is it safe to dirty flash 19.1 as upgrade from an (last) official build of 18.1 (No GApps installed)? Wait for TWRP 3.6.1_11 or latest 3.6.1_9 is working for that?

Heyyo. Exciting times! First official build of LOS 19.1 for payton is up!
@jtnc, tbh no idea as I haven't really checked into the material you stuff lol...
@wkn000 you can upgrade without wiping data, please follow the instructions in the first post.
You can use the latest test build of TWRP or use Lineage Recovery

I did a factory reset and have flashed the first official build of LOS 19.1. I then immediately sideloaded NikGapps-core-arm64-12.1 before the first boot but I only got the LOS startup dialog, and there doesn't seem to be any Gapps.
I also tried the same proceedure but using MindTheGapps-12.1.0 (20220416), but no still no Gapps.
Are there any tricks for loading Gapps using adb and lineage recovery, or does this only work with TWRP.

WackyDoo said:
[...] I then immediately sideloaded NikGapps-core-arm64-12.1 before the first boot but I only got the LOS startup dialog, and there doesn't seem to be any Gapps.
Click to expand...
Click to collapse
Immediately, w/o a reboot? You have to reboot into recovery after flashing an A/B ROM (to switch to the newly flashed ROM - #6 in the install steps) before flashing Gapps/etc. ;-)

jeremywh7 said:
Immediately, w/o a reboot? You have to reboot into recovery after flashing an A/B ROM (to switch to the newly flashed ROM - #6 in the install steps) before flashing Gapps/etc. ;-)
Click to expand...
Click to collapse
I was following the upgrade instructions ( https://wiki.lineageos.org/devices/payton/upgrade ) since I was coming from the previous version of LineageOS?? The upgrade instructions specifically mention that we should not reboot before flashing extra addons like gapps.
I will try the install instructions linked in the OP later, skipping the unlocking and, I guess, not running the copy_partitions script since I already ran than with the previous ROM.

I followed the same instructions and got the same result coming from the previous lineage version. I went back into the lineage recovery, reflashed the GAPPS and rebooted. Had a little trouble signing into my Google account as the 2 step authentication notification struggled to come through on the phone. I got around this by setting myself up as another user rather than the "owner". Everything seems to be working OK except the bluetooth connection to my car. The phone is connected and contacts appear on the car dashboard along with the battery and signal strength indicators- but calls don't come through the car - only to the phone's own speaker and microphone.

I followed the instructions and it updated to 19.1 without issue. Now, though, about every 5 minutes or so I get a "popup" or whatever it's called that says "Intent Filter Verification Service keeps stopping". Somewhat annoying. If I "force stop" the Intent Filter Verification Service app, it stops doing it, obviously. But upon reboot it starts right back up again. I don't have any of the gapps installed, but I do have microg, unsure if that's related. Overall though, it works pretty well.

To avoid boot loops,
Keep in mind to reboot to recovery between each sideload
Sideload lineage 19
Reboot to recovery
Sideload gapps
Reboot to recovery
Sideload Magisk
Power Off

[UNOFFICIAL][ROM][T585] LineageOS 18.x [11.0][64 BIT][Treble]

LineageOS 18.x Unofficial for Galaxy Tab A6 2016
{
"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.
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways
*
* 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.
*/
Click to expand...
Click to collapse
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
Camera (both photos and video)
Sensors
Vibration
Others I have forgot
What isn't working?
You tell me .
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest Twrp build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In Twrp format data. (Menu > Manage Partitions > Data > Format Data)
In Twrp 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
MediaFire
• Recovery
Twrp
• Support
Telegram group
• 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.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDAevDB Information
[UNOFFICIAL][ROM][T585] LineageOS 18.x [18.0][64 BIT][Treble], ROM for the Samsung Galaxy Tab A Series
Contributors
ROM OS Version: Android 11
ROM Kernel: Stock M10 Kernel
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Stable
Created: 2022-10-27
Last Updated: 2022-10-27

I keep seeing this "Make sure you have flashed the repartition script." mentioned - what exactly IS that script and why do we need it? I know I didn't need to flash that when flashing a custom A10 rom a year or 2 ago

Kostareka said:
LineageOS 18.x Unofficial for Galaxy Tab A6 2016View attachment 5744907
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.
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
Camera (both photos and video)
Sensors
Vibration
Others I have forgot
What isn't working?
You tell me .
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest Twrp build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In Twrp format data. (Menu > Manage Partitions > Data > Format Data)
In Twrp 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
MediaFire
• Recovery
Twrp
• 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.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDAevDB Information
[UNOFFICIAL][ROM][T585] LineageOS 18.x [18.0][64 BIT][Treble], ROM for the Samsung Galaxy Tab A Series
Contributors
ROM OS Version: Android 11
ROM Kernel: Stock M10 Kernel
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Stable
Created: 2022-10-27
Last Updated: 2022-10-27
Click to expand...
Click to collapse
screen cast not working on samsung note 3

Nimueh said:
I keep seeing this "Make sure you have flashed the repartition script." mentioned - what exactly IS that script and why do we need it? I know I didn't need to flash that when flashing a custom A10 rom a year or 2 ago
Click to expand...
Click to collapse
Because t585 does not contain a vendor partition, so this script repartitions the device and makes a partition for the vendor .

Kostareka said:
Because t585 does not contain a vendor partition, so this script repartitions the device and makes a partition for the vendor .
Click to expand...
Click to collapse
I didn't need that on A10, why do I need it now? Or is that because it's a GSI?
I wish flashing roms didn't get more + more complicated every year

Nimueh said:
I didn't need that on A10, why do I need it now? Or is that because it's a GSI?
I wish flashing roms didn't get more + more complicated every year
Click to expand...
Click to collapse
Yes, you need it because the ROM has become GSI, you can try Android 12 using lineage 18 vendor .

Kostareka said:
Yes, you need it because the ROM has become GSI, you can try Android 12 using lineage 18 vendor .
Click to expand...
Click to collapse
OK, thanks for the explanations ... I think I'll stay on my old A10 rom instead. I don't want to mess with partitions and stuff.
Thanks for all your work though

Thanks for the support for T585. Hope you continue supporting it.

Can you flash "any" Android 12 GSI after flashing it or only Android 11 GSI works?
And can you flash it on T580?

ar0177417 said:
Can you flash "any" Android 12 GSI after flashing it or only Android 11 GSI works?
And can you flash it on T580?
Click to expand...
Click to collapse
Yes you can boot android 12 gsi

Kostareka said:
Yes you can boot android 12 gsi
Click to expand...
Click to collapse
Can you make this for T580. Tried this partiton script but got /vendor (invalid argument) error

Hi
I have SM T585 U7
And I flashed (lineage16) on it, then I used ( repartition script) and flashed recovery (3.7.0.gtaxllt) and (lineage 18.1) and I did not like it very much, so I deleted it and also deleted (vendor) and flashed (lineage 16) again and restarted it, and it remained standing on the recovery logo and it did not It works until I flashed (cf root t585) via (odin), so it booted, but whenever I re-install any TWRP, it just stays on the logo and does not boot.
I got bored and wanted to restore the original system and downloaded it and put it in the (odin) and the flashing was successful, but the device continues to restart to no avail
I flashed TWRP again and found system (0
system img (3180
I do not know where the problem is, although the ROM is the original ROM, and the flashing is done successfully in Odin, but without a system
And it continues to restart. The Odin files that I used are the official AP.CP.HOMECSC .CSC.BL
I just want to return the original rom
Do you have a solution.
Thanks

I really need some help
I just installed this ROM successfully yesterday and it was working just fine on my sm-t585
But...
For some reason today it decided to brick my touch
Only the hardware buttons are functional and it's 50% charged so it's gonna take a lot of time for me to try to shut it down
So does anyone have any clue why that happened and how to fix it
(Note: the 2 touch buttons next to the home button are touch as well and they are also bricked)
Edit: I remembered that I installed the repartition script twice and now I have 2 vendors can I get rid of one ?! And how
Edit² : I did some troubleshooting and I found out what caused the touch problem...... It was the darn battery saving mode but now am wondering if anybody encountered the same problem

Development [ROM][UNOFFICIAL] ArrowOS 13.1[Android 13][renoir][20230623][EOL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
Code:
/*
* 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.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
In call (on speaker) and the screen turns off, the sound goes off for like 5-7 seconds..common issue
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source- https://github.com/ArrowOS
Device Tree Source-
https://github.com/RobertGarciaa/android_device_xiaomi_renoir
https://github.com/RobertGarciaa/device_xiaomi_sm8350-common

-Notice-
Build for personal use.
This rom will be uploaded irregularly.
Custom roms will be uploaded only when i want to build with updated source.
I'm busy so I can't see the reply.
I just created a thread to show where custom roms are uploaded.
Active feedback is difficult.
Because Im not rom maintainer and specialist, If you have problems with this ROM, try another ROM.

Flashing Instructions:-
First Time Install / Clean Flash
- Before proceeding any further, make sure you have downloaded all the files required for successful installation i.e., ROM zip (Arrow-*.zip), boot.img, vendor_boot.img, dtbo.img. firmware from the download link above.
Recovery is included in boot.img and vendor_boot.img.
1. Reboot to bootloader (fastboot)
2. Connect your phone to PC
3. fastboot flash boot_ab boot.img
4. fastboot flash vendor_boot_ab vendor_boot.img
5. fastboot flash dtbo dtbo.img
6. fastboot reboot recovery
7. Select Wipe data/factory reset & confirm
8. Go back and select Apply update from ADB
9. adb sideload Arrow-*.zip(or drag down the rom zip to cmd)
10. reboot recovery and select Apply update from ADB
11. adb sideload gapps*.zip (only if there's a gapps, recommend nikgapps)
12. After installation complete, Reboot system. Use Arrow OS 13.1!
Update / Dirty Flash
1. Download proper flashable ZIP for your device
2. Reboot to Recovery
3. Select Apply update from ADB
4. adb sideload Arrow-*.zip(or drag down the rom zip to cmd)
5. reboot recovery and select Apply update from ADB
6. adb sideload gapps*.zip (only if there's a gapps, recommend nikgapps)
7. Reboot to System and Use Arrow OS 13.1!

Update history(only what's important)
2023/1/2 : December security patch, The issues mentioned in PE have been resolved
2023/1/7 : January security patch. Face Unlock. Need for flashing firmware miui global 13.0.9
-----------------------------The tree used has changed a lot.
2023/4/4 : 13.1(Maybe Beta quality). Clean Flash. Only Vanilla, Update MIUI 14 blob, Include MIUI 14.0.3.0.TKIMIXM Global firmware, And so on
2023/4/5 : (Hotfix) Label lahaina wakeup nodes
2023/4/14 :
April Security Update
Latest Lineage os kernel
Sync saikiran's Tree(Add xiaomi part, Enabled Dolby Vision in Netflix,...)
2023/4/24 :
Sync Latest Arrow OS source And Some Tree
Latest Lineage os kernel
Merge kernel 5.4.241 into android11-5.4-lts
2023/5/10 :
May Security Update
Update kernel version to 5.4.242
Update Perf system libs to LA.QSSI.13.0.r1-09700-qssi.0
Enable AOSP Surfaceflinger
Fix some problems
2023/5/12 :
Change to Derpfest kernel To improve Battery Backup(except for KernelSU)
2023/5/30 :
Update Latest Tailwind kernel
Build kernel with slim clang
Switch to Pixel libperfmgr
Tune Performance stabilization to improve battery backup
Update CarrierConfig from MIUI 14
Switch to Aperture Camera app
Provide more stable auto brightness
2023/6/09 :
Fix bootloop problem
Sync Latest Arrow os source
And so on
(Hotfix) Fix Pixel power libperfmgr HAL denials
(Hotfix) Fix random reboot problem, Sync Lineage os 20 tree, Update Latest Tailwind kernel
2023/6/19 :
Fix random reboot problem Perfectly
Update Latest Tailwind kernel
Switch to AOSP Clang 17
Drop CPU input boost
Add Missing Hals
And so on
(Hotfix) Add Missing Hal
(Hotfix)
Fix problem with developer options not launching, Sync Latest Arrow OS source(include Face unlock), Add Missing Hals
2023/6/23 :
Fix random reboot problem
Update June security patch
and so on

Nice to see!
I am a happy user of your PE project atm. Only downside I noticed was increase in battery usage and a little worse RAM management.
Have you noticed if the battery has proven to be better with ArrowOS? I think I might transfer to this OS.

Hammerlig said:
Nice to see!
I am a happy user of your PE project atm. Only downside I noticed was increase in battery usage and a little worse RAM management.
Have you noticed if the battery has proven to be better with ArrowOS? I think I might transfer to this OS.
Click to expand...
Click to collapse
1. Pixel likely roms have battery drain problem.
pixel launcher battery drain issue.
project elixir and evo replace pixel launcher with launcher 3.
arrow os use launcher 3 and dont has many additional features
2. change awaken os kernel to los kernel.
awaken os kernel has battery drain and memory management issue.
3. I saw an info in the lisa telegram group that the arrow os battery life was good.
Theoretically, it should be better.
I can't help it if I can't do this no matter how hard I try

Hi mate the rom is perfect, one question though when I'm in call (on speaker) and the screen turns off the sound goes off for like 5-7 seconds and comes back, it repeats occasionally. Do you have any idea why or I'm missing something.

razor_1911 said:
Hi mate the rom is perfect, one question though when I'm in call (on speaker) and the screen turns off the sound goes off for like 5-7 seconds and comes back, it repeats occasionally. Do you have any idea why or I'm missing something.
Click to expand...
Click to collapse
This case is my first time, so I'm not sure how to care.
When I have used the phone, it never happened.
If you attach your logcat, it will be helpful to solve the problem.
I'm not an expert(just build rom using source), but if I know the cause and solution to the problem, I'll reflect it in the next update.

razor_1911 said:
Hi mate the rom is perfect, one question though when I'm in call (on speaker) and the screen turns off the sound goes off for like 5-7 seconds and comes back, it repeats occasionally. Do you have any idea why or I'm missing something.
Click to expand...
Click to collapse
Thanks for reporting the bug.
I confirmed it.
I'll have to look at the common tree(I don't know if I can solve it)

I think something else is the issue not the rom all android 13 roms have the same issue test it with ricedroid, pe plus etc. I think its more like a permission to run in the background.

razor_1911 said:
I think something else is the issue not the rom all android 13 roms have the same issue test it with ricedroid, pe plus etc. I think its more like a permission to run in the background.
Click to expand...
Click to collapse
Resolving this part will take some time.
Thank you for your good comments.

Why I can't find the smooth display in settings?

Jonson Lam said:
Why I can't find the smooth display in settings?
Click to expand...
Click to collapse
I don't know.
Arrow OS doesn't seem to exist.

Are the system navigation buttons invertable on this rom pls?

Also has anyone dirty flashed from Lineage 19 2Jan23 rom pls? Any issues? All working ok?

To clarify I meant dirty flash from Lineage 19.1 version..... Benefits of this arrow rom over that?

TheDon13 said:
To clarify I meant dirty flash from Lineage 19.1 version..... Benefits of this arrow rom over that?
Click to expand...
Click to collapse
need clean flash. First Time Install / Clean Flash. i wrote it.

Sorry for stopping the build every time.
When I build a rom, I always try to keep building until the end. But that doesn't work.
Since I am a beginner, I lack build skills. So every time the problem occurs, I have to build a new ROM.
Originally, I used the awaken os tree to build, but the baseband was blown away while applying the new tree. Thanks to that, the sim was not recognized.
It's a ruined build anyway, so I'm going to build evolution x based on the Lineage os tree and apply the awaken os tree.
This is definitely a tree specific to renoir, so it should be stable.

Letmeseeforest said:
Sorry for stopping the build every time.
When I build a rom, I always try to keep building until the end. But that doesn't work.
Since I am a beginner, I lack build skills. So every time the problem occurs, I have to build a new ROM.
Originally, I used the awaken os tree to build, but the baseband was blown away while applying the new tree. Thanks to that, the sim was not recognized.
It's a ruined build anyway, so I'm going to build evolution x based on the Lineage os tree and apply the awaken os tree.
This is definitely a tree specific to renoir, so it should be stable.
Click to expand...
Click to collapse
Ruined build??

TheDon13 said:
Ruined build??
Click to expand...
Click to collapse
Always before sharing a rom, I test it out to see if I have any problems.
I relied on the lisa side tree.
But i have a situation where the baseband is blown off, but I don't know how to fix it.
So I rebuild the tree stably again, and build a new evolution x.
I'll keep building.

Better Mobile App

welcome