[ROM][OFFICIAL] LineageOS 18.1 [beckham][weeklies] - Moto Z3 Play ROMs, Kernels, Recoveries, & Other De

[ROM][OFFICIAL] LineageOS 18.1 [beckham][weeklies] - Moto Z3 Play ROMs, Kernels, Recoveries, & Other De

Reserved...

Using it and after an entire week now, no problems or bugs so far. I do have, however a small question: how do I make this rom to stop shortening text in icons and in the lock screen? Other custom roms will use two lines of text if the app name is too long but this one shorts it, which in some cases leads to 'not so desirable' results, like in the Wifi Analyzer App (see attached screenshots).
Changing the grid layout doesn't helped and this phone has plenty of screen resolution to avoid doing things like 'S...' instead of showing 'September' in the lock screen. Thank you very much for this awesome rom

First of all I'm really greatfull to have lineage supported on this phone.
One problem I encountered while installing the rom was that my phone refused to connect to anything other then GSM. So mobile data was not working.
I started from an older version of the stock rom, not the latest stock 9.0 rom.
This seems to be a somewhat known issue, u/i_guess_i_am_a_scout on reddit has written a guide on this for lineage 16 / 17.
Though for me it was sufficient to flash the modem and vendor partitions for slot a and b:
fastboot --slot a flash modem NON-HLOS.bin
fastboot --slot b flash modem NON-HLOS.bin
fastboot --slot a flash vendor vendor.img_sparsechunk.0
fastboot --slot a flash vendor vendor.img_sparsechunk.1
fastboot --slot b flash vendor vendor.img_sparsechunk.0
fastboot --slot b flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
boot twrp, sideload the twrp-installer and latest lineage zip
After that mobile data and LTE suddenly started to work.
Another minor issue I encountered is that "Brightness control by sliding across the status bar" does set the brightness to 100% for very low brightness levels / on the very left of the statusbar-swipe. See: https://gitlab.com/LineageOS/issues/android/-/issues/3865 .
But appart from that a very solid rom, in the one month I've been using it, there were no other issues.
Thanks.

CamposJ said:
Using it and after an entire week now, no problems or bugs so far. I do have, however a small question: how do I make this rom to stop shortening text in icons and in the lock screen? Other custom roms will use two lines of text if the app name is too long but this one shorts it, which in some cases leads to 'not so desirable' results, like in the Wifi Analyzer App (see attached screenshots).
Changing the grid layout doesn't helped and this phone has plenty of screen resolution to avoid doing things like 'S...' instead of showing 'September' in the lock screen. Thank you very much for this awesome rom
Click to expand...
Click to collapse
Just some ideas as workarounds:
1) Change the grid layout by long pressing on the home screen -> Styles and Wallpapers -> Grid -> 4x5
At first this applies only to the home screen and not the app drawer:
But after a reboot the appdrawer will also have the 4x5 layout.
2) You could decrease the font size in the settings, but that might make other things hard to read.
3) Use a third party launcher.
The lock screen month clipping issue seems to be localization related, on english this works fine.
But I guess that is not really an issue specific to the z3 play, so you probably should report it as a lineage bug report so it can be fixed for all devices.

userx14 said:
First of all I'm really greatfull to have lineage supported on this phone.
One problem I encountered while installing the rom was that my phone refused to connect to anything other then GSM. So mobile data was not working.
I started from an older version of the stock rom, not the latest stock 9.0 rom.
This seems to be a somewhat known issue, u/i_guess_i_am_a_scout on reddit has written a guide on this for lineage 16 / 17.
Though for me it was sufficient to flash the modem and vendor partitions for slot a and b:
fastboot --slot a flash modem NON-HLOS.bin
fastboot --slot b flash modem NON-HLOS.bin
fastboot --slot a flash vendor vendor.img_sparsechunk.0
fastboot --slot a flash vendor vendor.img_sparsechunk.1
fastboot --slot b flash vendor vendor.img_sparsechunk.0
fastboot --slot b flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
boot twrp, sideload the twrp-installer and latest lineage zip
After that mobile data and LTE suddenly started to work.
Another minor issue I encountered is that "Brightness control by sliding across the status bar" does set the brightness to 100% for very low brightness levels / on the very left of the statusbar-swipe. See: https://gitlab.com/LineageOS/issues/android/-/issues/3865 .
But appart from that a very solid rom, in the one month I've been using it, there were no other issues.
Thanks.
Click to expand...
Click to collapse
Glad you figured it out, which there is a message on the install page stating to make sure you're on the latest firmware before flashing the rom. Mobile data was only an issue for CDMA users in early builds of 17.1/16.0. I was missing a flag on our board config that fixed that.
As for your guide, it doesn't make any sense to flash the vendor partition, you mostly just need what gets symlinked there (i.e. fsg, modem, dsp). Vendor get overwritten during the rom installation. In your case, you were probably on a firmware version lower than the firmware version beckham's device specific blobs are from and the rom didn't agree. Regardless, I am glad all worked out in the end.
I am aware of the Brightness issue and am working on a solution. I can confirm it also happens on Evert and Lake as well.

Jleeblanch said:
Glad you figured it out, which there is a message on the install page stating to make sure you're on the latest firmware before flashing the rom. Mobile data was only an issue for CDMA users in early builds of 17.1/16.0. I was missing a flag on our board config that fixed that.
As for your guide, it doesn't make any sense to flash the vendor partition, you mostly just need what gets symlinked there (i.e. fsg, modem, dsp). Vendor get overwritten during the rom installation. In your case, you were probably on a firmware version lower than the firmware version beckham's device specific blobs are from and the rom didn't agree. Regardless, I am glad all worked out in the end.
I am aware of the Brightness issue and am working on a solution. I can confirm it also happens on Evert and Lake as well.
Click to expand...
Click to collapse
I'm not really sure which one of the flash commands fixed it in the end, it could very well only be the flash modem command.
I also started looking into the brightness issue. I'm not very experienced when it comes to android development. But if I'm right the code that controlls the status bar brightness should be here. I've experimented a bit and found that the problem occurs in the padding zone on the left, where there is left 15% of the status bar which should return the lowest brightness value.
In this case the newBrightness is set to:
int newBrightness = mMinBrightness;
and
mMinBrightness = context.getResources().getInteger(com.android.internal.R.integer.config_screenBrightnessDim);.
EDIT:
I've searched through through other device's code (Moto E 2015) and some seem to configure this value inside this device specific config file.
But how to find out what this should have as a value and why does it work for the normal brightness slider but not for the status bar swipe?

userx14 said:
I'm not really sure which one of the flash commands fixed it in the end, it could very well only be the flash modem command.
I also started looking into the brightness issue. I'm not very experienced when it comes to android development. But if I'm right the code that controlls the status bar brightness should be here. I've experimented a bit and found that the problem occurs in the padding zone on the left, where there is left 15% of the status bar which should return the lowest brightness value.
In this case the newBrightness is set to:
int newBrightness = mMinBrightness;
and
mMinBrightness = context.getResources().getInteger(com.android.internal.R.integer.config_screenBrightnessDim);.
EDIT:
I've searched through through other device's code (Moto E 2015) and some seem to configure this value inside this device specific config file.
But how to find out what this should have as a value and why does it work for the normal brightness slider but not for the status bar swipe?
Click to expand...
Click to collapse
The config option is found in our sdm660-common tree which we currently have set to "1". Default value found here is "10", which digging into stock is what is used.
I've already made the necessary changes in the common tree, I just have yet to have a chance to build and test. I legit just moved to Georgia from Vermont this past weekend. In the coming days I'll be hard at work on my supported devices in hopes to work out the remaining minor bugs.

Jleeblanch said:
The config option is found in our sdm660-common tree which we currently have set to "1". Default value found here is "10", which digging into stock is what is used.
I've already made the necessary changes in the common tree, I just have yet to have a chance to build and test. I legit just moved to Georgia from Vermont this past weekend. In the coming days I'll be hard at work on my supported devices in hopes to work out the remaining minor bugs.
Click to expand...
Click to collapse
Thanks for the information,
please don't interpret my posts here as impatience, so please take your time.
I just saw this minor issue as a possibility to get my feet wet with the lineage source.
Can I help by trying to build a version with a the modified sdm660 tree file where config_screenBrightnessDim is set to 10 and test if this fix works?

userx14 said:
Thanks for the information,
please don't interpret my posts here as impatience, so please take your time.
I just saw this minor issue as a possibility to get my feet wet with the lineage source.
Can I help by trying to build a version with a the modified sdm660 tree file where config_screenBrightnessDim is set to 10 and test if this fix works?
Click to expand...
Click to collapse
No worries! Any and all help is always appreciated, one of the benefits of open source is anyone can contribute
That's totally up to you! All the info you need to build is on the Lineage Wiki. I believe I pushed the changes to my personal github if you wanna pick them. If you wanna experiment yourself, removing that line I linked in sdm660-common (and the relevant comment above it) is what you would want to do to revert the value back to "10" as it'll just use the value in frameworks/base instead.
If you have any questions, don't hesitate to ask! Lemme if that works or not or even if it changes the behavior even slightly. We may even need to play with the value a bit.

Jleeblanch said:
No worries! Any and all help is always appreciated, one of the benefits of open source is anyone can contribute
That's totally up to you! All the info you need to build is on the Lineage Wiki. I believe I pushed the changes to my personal github if you wanna pick them. If you wanna experiment yourself, removing that line I linked in sdm660-common (and the relevant comment above it) is what you would want to do to revert the value back to "10" as it'll just use the value in frameworks/base instead.
If you have any questions, don't hesitate to ask! Lemme if that works or not or even if it changes the behavior even slightly. We may even need to play with the value a bit.
Click to expand...
Click to collapse
Well, after downloading for 5h and compiling another 5h I was able to create the new zip file.
For me the 'extract proprietary blob' part of the wiki didn't work, when executing ./extract-files.sh it got some files, but for others it reported errors:
- vendor/lib64/sensors.iio.so
- product/priv-app/ims/ims.apk
- system/app/MotoSignatureApp/MotoSignatureApp.apk
!! system/app/MotoSignatureApp/MotoSignatureApp.apk: file not found in source
- system/priv-app/ModFmwkProxyService/ModFmwkProxyService.apk
!! system/priv-app/ModFmwkProxyService/ModFmwkProxyService.apk: file not found in source
- system/priv-app/ModService/ModService.apk
!! system/priv-app/ModService/ModService.apk: file not found in source
- system/priv-app/MotCamera2/MotCamera2.apk
+ keeping pinned file with hash 260df16116b0e9f5144114454533bcda35f669e7
- system/priv-app/ProjectorApp/ProjectorApp.apk
!! system/priv-app/ProjectorApp/ProjectorApp.apk: file not found in source
not sure if I was missing a setting, this result was with "USB debugging" and "Rooted debugging" enabled in the android settings.
But extracting the files from a official zip file worked out.
EDIT:
After some testing with different brightness xml values, the lowest value that still works is 2.
This is also the lowest brightness achievable with the default brightness slider.
EDIT2:
Strange, with the integrated brightness settings I can reach lower brightness, so it should be a value less than 2. But 1 did break the brightness adjustment, so there is probably a deeper problem.

Hey, I'm still running official LOS 17.1 on my Z3. Does this build still have a working Moto Camera 2 like 17.1? I heard from other custom ROM users on Motos that it crashes for them on 18.1. if the Moto Camera 2 app is working fine, then I'll go ahead and upgrade.

Sanras said:
Hey, I'm still running official LOS 17.1 on my Z3. Does this build still have a working Moto Camera 2 like 17.1? I heard from other custom ROM users on Motos that it crashes for them on 18.1. if the Moto Camera 2 app is working fine, then I'll go ahead and upgrade.
Click to expand...
Click to collapse
Hi @Sanras,
for me the "camera 2" app is working on the most recent build of LOS 18.1 .
There is a toast "dlopen failed libmcf-jni not found" which pops up on occasionally on start, but it does not seem to affect the functionality.
If you are using TWRP booted from fastboot, you could do a full system backup before flashing, just in case.
Greetings
userx14

userx14 said:
Hi @Sanras,
for me the "camera 2" app is working on the most recent build of LOS 18.1 .
There is a toast "dlopen failed libmcf-jni not found" which pops up on occasionally on start, but it does not seem to affect the functionality.
If you are using TWRP booted from fastboot, you could do a full system backup before flashing, just in case.
Greetings
userx14
Click to expand...
Click to collapse
Ok, that's good to hear! Thank you for the information.

userx14 said:
First of all I'm really greatfull to have lineage supported on this phone.
One problem I encountered while installing the rom was that my phone refused to connect to anything other then GSM. So mobile data was not working.
I started from an older version of the stock rom, not the latest stock 9.0 rom.
This seems to be a somewhat known issue, u/i_guess_i_am_a_scout on reddit has written a guide on this for lineage 16 / 17.
Though for me it was sufficient to flash the modem and vendor partitions for slot a and b:
fastboot --slot a flash modem NON-HLOS.bin
fastboot --slot b flash modem NON-HLOS.bin
fastboot --slot a flash vendor vendor.img_sparsechunk.0
fastboot --slot a flash vendor vendor.img_sparsechunk.1
fastboot --slot b flash vendor vendor.img_sparsechunk.0
fastboot --slot b flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
boot twrp, sideload the twrp-installer and latest lineage zip
After that mobile data and LTE suddenly started to work.
Another minor issue I encountered is that "Brightness control by sliding across the status bar" does set the brightness to 100% for very low brightness levels / on the very left of the statusbar-swipe. See: https://gitlab.com/LineageOS/issues/android/-/issues/3865 .
But appart from that a very solid rom, in the one month I've been using it, there were no other issues.
Thanks.
Click to expand...
Click to collapse
The first time I installed LineageOS 18.1 I accidentally deleted all the stock rom files and GPS, GSM and bluetooth didn't work. I went back to stock rom and installed LineageOS 18.1 again without deleting all the files and the only thing that still doesn't work is Bluetooth. Still not able to resolve.

cruzdl said:
The first time I installed LineageOS 18.1 I accidentally deleted all the stock rom files and GPS, GSM and bluetooth didn't work. I went back to stock rom and installed LineageOS 18.1 again without deleting all the files and the only thing that still doesn't work is Bluetooth. Still not able to resolve.
Click to expand...
Click to collapse
@cruzdl
Strange, for me bluetooth works.
Maybe you used a different version for your stock rom or your device is different?
I have an xt1929-8, and I'm not sure if the emmc and ram size is the only difference between the versions.
Is it correct that you created the issue https://gitlab.com/LineageOS/issues/android/-/issues/4057 ?
When I have bluetooth disabled with the quick settings I also get bluetooth adress not available, but when I switch bluetooth on I have an bluetooth address that is the same as the Wifi mac address, but the last digit is one lower.
Do you have the a Wifi mac address there when you have Wifi active?

Curious if anyone has either of the camera mods working with this? I have both the Hasselblad and 360 mods and neither seem to work, with the camera just defaulting back to the built-in one or crashing.

Does anyone have any tips for diagnosing VoLTE? I'm on Tracfone MVNO with Verizon.
I saw this guy went back and reflashed the stock rom and then his started working on Mint MVNO with T-Mobile.
https://www.reddit.com/r/LineageOS/comments/qacid8
So Lineageos and Z3P are VoLTE capable.
I reflashed the full set of partitions from the latest RETUS stock zip a few times. I did get VoLTE most of the time, but not always. I'm not sure what that means if VoLTE doesn't always work with the same stock rom. I have never been able to get it with Lineageos loaded.
I'm using the recommended APN. VoLTE is enabled in settings. But I always get CDMA-1rtt for voice. During a call, I lose data.
I'm not sure how to mess with the carrier config. Maybe I should try to extract the carrier config from the stock rom and check it against the lineageos rom?

HyperChrisX said:
Curious if anyone has either of the camera mods working with this? I have both the Hasselblad and 360 mods and neither seem to work, with the camera just defaulting back to the built-in one or crashing.
Click to expand...
Click to collapse
Camera Mods dont work. I have the Hassleblad myself. Works on the stock rom not the Lineage 18.1.

I saw the lastest Weekly update added SD card encryption.
I flashed this morning. When I formatted the sd card the phone hung. But Rebooting and firmatting internal again was a success. I have rebooted and powered down a couple times and it all looks great!!!
This is a huge feature for me!
XT-1929-4 32GB

Related

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

{
"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, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
It can be used without any need to have any Google application installed.
You will need to provide your own Google Applications package (gapps).
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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for unofficial LineageOS 13.0 builds for LG G4 model H815 only.
Its a continuation of the official one as it was abandoned back in July and I still prefer MM (N has still bugs and does not support encryption).
Known issues:
the kernel has security bugs which need to be addressed
its in testing state as I cant test it atm.. please report back! PLEASE MAKE A FULL BACKUP BEFORE TESTING!!
Installation:
First time flashing LineageOS 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install latest TWRP from the official twrp.me website
Perform a nandroid backup of your current ROM (optional but recommended)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
Google Apps:
OpenGApps (choose arm64, 6.0, nano)
TWRP Recovery:
https://twrp.me/devices/lgg4.html
Full Stock ROMs:
H815 V20D
Bootloader:
Remember ---> Flashing bootloader is risky so you flash at your own risk!
H815 V20D
Modem:
H815 V20D
ROM:
Last known fully working is 20170813! Sorry have to fix the blobs first!
Nightlies: http://droid.binbash.it
Sources:
Android: https://github.com/LineageOS
Device: https://github.com/steadfasterX/los_android_device_lge_h815
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8992
G4 common device tree: https://github.com/LineageOS/android_device_lge_g4-common
Proprietary files: https://github.com/TheMuppets/proprietary_vendor_lge
.
XDA:DevDB Information
lineage-13.0-unofficial, ROM for the LG G4
Contributors
steadfasterX, codeworkx, genesixxbf3
Source Code: https://github.com/steadfasterX/los_android_device_lge_h815
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader unlocked, v20A (or greater) bootloader stack
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-08-21
Created 2017-08-21
Last Updated 2017-11-03

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

Reserved

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

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

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

Any tester reports?

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

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

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

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

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

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

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

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

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

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

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

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

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

[ROM][8.1.0]LineageOS-15.1[Joan][Treblelized][Unofficial]

{
"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 8.0 (Oreo), 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.
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Hotspot
Flash
GPS
What's not working :
Boot doesnt work all the time (just dont reboot the phone, i guess)
GSIs (Generic System Images) work fine though for some reason
DAC(?)
Selinux is permissive
Exfat (when enabled makes system slow down, and eventually crash)
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions :
Download the build
If you dont have a vendor partition yet, create one GUIDE
Reboot to recovery
Flash the latest build
Reboot
Downloads :
Here
H932 Build
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
lineage-15.1-treble branch
XDA:DevDB Information
LineageOS 15.1 - Treble, ROM for the LG V30
Contributors
SGCMarkus, rashed97
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-10-03

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 13.05.2018
- Initial release
Release 16.05.2018
- Fixed boot (temporarily disabled sdcardfs)
Release 18.05.2018
-enabled sdcardfs again (fixed, took the OP5(T) driver, not the broken LG one)
-reduces system image size by around 10MB, so our friends who repartitioned have a bit more room for that, same for vendor
Release 21.05.2018
-updated to latest LineageOS sources
-enabled burnin protection in overlays
-re-enabled exfat driver in the kernel (may cause issues for some sdcards, may need to reformat them, as they could "load" forever and make the system crash eventually)
-cherry-picked https://review.lineageos.org/c/Linea..._base/+/210106 (should fix acccess to wide angle camera on apps that support it)
Release 01.06.2018
- Updated Autobrightness from Taimen (Pixel 2 XL), as it has the same panel
- Enabled the AoD option (you might have to unlock the phone twice or so though, LOS source is currently broken, nothing i can do)
- Updated to latest LOS sources
- Nuked lge/common and moved gestures into our tree
Release 22.07.2018
- Updated blobs to H930 V20R
- fixed vibration becoming dull after a while
- all other past changes from normal LOS since last update here
- updated source
Release 29.08.2018
- Updated Source
- Updated blobs to H930 21a
- Vibration motor ready for P GSIs

Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Does this work on the US998?
A. Hasn't been tested yet. Try it out and report (but make a backup first as always).

Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!

okaiuz said:
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
Click to expand...
Click to collapse
The reboot problems only occur with the 2 LineageOS builds, not with GSIs (or i was just really extremly lucky, but i doubt that).
On LOS i have a ~20% boot chance (did once 35 boot tries after another...), and on GSIs it boot always like 6 or 7 times after another. Suppose it works there, really unlikely i was that lucky lol
The GSI of LOS by phhuson also works btw (just no double tap 2 wake).
I would actually love to make way more ROMs.... I even had a CrDroid test build once (to check if its only LOS with that problem), but sadly im out of space now.... dont have more space than for LOS :/

Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!

okaiuz said:
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
Click to expand...
Click to collapse
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)

SGCMarkus said:
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
Click to expand...
Click to collapse
i have to thank you again for you work!
Thursday i'll try to partition my v30+ and try your treblelized los!
i give a chance even to phh los, aosp and rr!
i 'll yo know my experience, hoping that you can fix the boot problem!
Regards!

i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.

donky kong 017 said:
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
Click to expand...
Click to collapse
Use Viper4Android and the predicament is solved.

Nikola Jovanovic said:
Use Viper4Android and the predicament is solved.
Click to expand...
Click to collapse
does viper use the quad DAC. AFAIK no. ATM i use the V30 Quad DAC and Ainur Sauron

As it also counts for this, i will simply refer to my post in the other LOS thread
https://forum.xda-developers.com/showpost.php?p=76536335&postcount=20

you're the best!
tnx to phh also!

how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?

elba96 said:
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
Click to expand...
Click to collapse
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too

SGCMarkus said:
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
Click to expand...
Click to collapse
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?

maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?

Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.

okaiuz said:
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Click to expand...
Click to collapse
Yes, you can still use the non treblelized version
Still working on adding features though, fixing major bugs first ^^
Doblix said:
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
Click to expand...
Click to collapse
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
elba96 said:
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
Click to expand...
Click to collapse
My testers say its ready for daily usage
Couldnt test for battery life yet myself. Didnt have the time to setup everything a new... University life is tough

SGCMarkus said:
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
Click to expand...
Click to collapse
Yes vendor is listed there and I could also format it. I am at university right now and reverted to stock to be able to use it (which can be flashed fine btw.), I will see when I find the time to flash again and post the log here then.

[ROM][All Quark][8.x]Resurrection Remix

{
"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"
}
ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
Resurrection Remix Features list (Click Here)
Changelogs:
Device specific (Click Here)
Resurrection Remix OS - Oreo source and Quark Changelog (Click Here)
What's working :
Everything.
Known Oreo Bugs :
TWRP can't backup or decrypt data encrypted on Oreo: no know workaround, one day TWRP will support it.
Can't swipe/draw the pattern in lockscreen : Screen lock pattern is set with the extra option of patterns "Directly show pattern view" and ambient display enable all at the same time, will bug ambient display for the wave or pick featuring of gestures, this doesn't bug when you received a notification, disable one or the other until the bug is fixed.
No SIM Card or no Cell Signal: Sometimes very rare bug this days, the device can finished the booting up process and have a no sim card or zero/null network signal level in status bar preventing from making/receive a call or anything related to SIM status be OK for use, Don't confuse this with a slow to be recognized SIM or network status so before try the fix wait a minute or two to see if the signal comes up. To fix: Go back to recovery and wipe Dalvik / Art Cache and Cache then reboot back to system, if this doesn't help try the "GPS / Radio" from #2 post.
"Odd looking" screenshots: if you enable Smart Pixels featuring in Settings > configurations > interface or any pixel filter related app this may happens. To fix: Disable the featuring
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Download Links :
ROM:
AFH ROM Click Here
Gapps:
MindTheGapps:
MindTheGapps Main Click Here
MindTheGapps Mirror Click Here
Choose MindTheGapps-8.1.0-arm-date_version.zip
MindTheGapps Old releases Click Here, in case latest version is NOK
Open GApps:
Open Gapps Click Here
Choose Platform: ARM, Android: 8.1, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.
Open GApps old releases Click Here, in case latest version is NOK
Gapps recommendations from LineageOS Google apps options (click here)
TWRP For Quark:
TWRP Use laste Mod version that I release Click Here
Installation instructions:
Download the latest build and GApps.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Additional ROM Features (apart from Resurrection Remix features) :
Kernel improves
Turbo Toast app, (app to display a Toast message informing the connection of Turbo Charger like Stock ROM "TurboPower connected")
fgl27 Mod Kernel Adiutor, a app to control many aspects of the kernel give the user total control of kernel functions and information on how the devices is running deep sleep time, battery status, logs etc.
Permission to install Motorola apps direct from play *included VVM (VVM may only be accessible with the link, click here and chose open with play)
Notification LED support
All the custom featuring of LineageOS available for Quark:
LineageActions, similar to Moto actions, used to control quark sensor to enable gestures for ambient display, pick-up and Wave to wake the screen, Actions Double-Twist and Chop-Chop to lunch the camera or flash light, etc.
Support for all quark models (XT1225, XT1250 and XT1254)
Crossflashing & Configuration Override (You can crossflash radio image for a different variant of the phone, but the automated setup will not pick it up. Thus you'll need to manually override it through fastboot) check CM13.0 thread #1 post for how to and files CM-13 thread click here
Plus many others featuring, improves and bugs fixes that I have add/done for the past years to custom ROM for quark
Developer donation link:
To donate via paypal click here
No other donation option is available.
Source :
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][8.x]Resurrection Remix, ROM for the Motorola Moto Maxx
Contributors
fgl27
Source Code: https://github.com/ResurrectionRemix/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-01
Last Updated Check Changelog click here

Below are some of the helps and or workarounds for the most occurring problems.
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2)Check the boot reason prop "ro.boot.bootreason" if it is like the example bellow set to power_key_press the device didn't reboot it sled power off.
Code:
[ro.boot.bootreason]: [power_key_press]
Check the prop using :
Kernel Audiutor app > logs section > search in a log > mark getprop > search key word "reason".
If the Random power off are related to battery, BCL can help mitigate the problem.
BCL can be controlled via BHB27 kernel adiutor Power and battery section.
Lowering the BCL Max frequency or Making the number of hot unplugged core higher will help to mitigate the CPU power.
But if the problem persist is necessary to change the BCL low and high voltage threshold to higher values to make BCL to start sooner, the recommendation is to set they to 3700mV (Low) and 4000mV(High) and if the problem is resolved after that, the device stops randomly power it self off, lower the values 100mv it until you find a perfect value, or if the problem persist make the values 100mV higher.
Is also recommended to set the battery "Automatic power saver" from default 15% to a higher value, with is today max at 25%
If the device did just reboot just share a log as recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This a Nougat and UP problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the ROM phone app also has a dedicated option for voice calls

Featuring request at this moment are not welcome, featuring will be add naturally through ROM updates, in 2019 after a lot of new featuring have be add if something really need is missing please report.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP, even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up

Many thanks for your work! (p.s. still waiting for battery arrival, no update yet if you remember I promised).
Is there a custom kernel for Oreo?

olegfusion said:
Many thanks for your work! (p.s. still waiting for battery arrival, no update yet if you remember I promised).
Is there a custom kernel for Oreo?
Click to expand...
Click to collapse
Looks like the kernel is custom by bhb27 (he listed "kernel improves" in the additional features).
Thanks @bhb27 for this!
Sent from my DROID Turbo XT1254 using Tapatalk

marinegundoctor said:
Looks like the kernel is custom by bhb27 (he listed "kernel improves" in the additional features).
Thanks @bhb27 for this!
Click to expand...
Click to collapse
More ROMs will appear now that @bhb27 has an Oreo compatible kernel to use.

ChazzMatt said:
More ROMs will appear now that @bhb27 has an Oreo compatible kernel to use.
Click to expand...
Click to collapse
Absolutely! @bhb27 will be the baby-daddy of many Oreo ROMs lol!
Sent from my DROID Turbo XT1254 using Tapatalk

Well I'm going to download and install this on the morning to see how it does on my xt1254. Anyone else try it yet?
Sent from my DROID Turbo XT1254 using Tapatalk

The ROM is good and enough stable! The question:
1. I couldn't install Magisk Manager somehow. Is it not compatible yet?
2. Luckypatcher system services.jar patch is making bootloop. Is there a some secure setting in 8.1 about that?
Both apps are compatible with 8.1 by their changelog.

Security pattern doesn't work because of selinux I guess, don't try switch it on

olegfusion said:
Many thanks for your work! (p.s. still waiting for battery arrival, no update yet if you remember I promised).
Is there a custom kernel for Oreo?
Click to expand...
Click to collapse
No I will make a new one, the Nougat with all the custom featuring and the port for Oreo did't work.
I probably release a beta one in a week or two.
Let me know when you have news.
marinegundoctor said:
Looks like the kernel is custom by bhb27 (he listed "kernel improves" in the additional features).
Thanks @bhb27 for this!
Sent from my DROID Turbo XT1254 using Tapatalk
Click to expand...
Click to collapse
Those are in relation to quark stock kernel, my stock have some general kernel improves but very little in relation to the custom one.

smooth like nexus 6 my friend, but when listening to music with earbud hangs, and when in restart only black screen

bhb27 said:
No I will make a new one, the Nougat with all the custom featuring and the port for Oreo did't work.
I probably release a beta one in a week or two.
Let me know when you have news.
Click to expand...
Click to collapse
Battery should arrive in 2-4 days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:35 PM ----------
SWEVEX said:
smooth like nexus 6 my friend, but when listening to music with earbud hangs, and when in restart only black screen
Click to expand...
Click to collapse
wipe dalvik cache/cache partition helps to return back to normal.

Poweramp License verification
Thank you for 8.x oreo
Flashed the rom and MindTheGapps-8.1.0-arm-20180610_023943.zip followed by clean modem status and
Radio_Flasher_Stock_MPGS24.107-70.2-2.zip
I have a problem with poweramp license verification.
Screenshot attached with logs.
Thank you very much

pankaj72 said:
Thank you for 8.x oreo
Flashed the rom and MindTheGapps-8.1.0-arm-20180610_023943.zip followed by clean modem status and
Radio_Flasher_Stock_MPGS24.107-70.2-2.zip
I have a problem with poweramp license verification.
Screenshot attached with logs.
Thank you very much
Click to expand...
Click to collapse
After having license issues with another app {on 7.x.x though), I had to uninstall the app, use a root browser (I use FX File manager) to go into /data/data or /system/data/data (I forgot which) and delete the folders associated with the app. Then reinstall it and all was good for me.
Sent from my DROID Turbo XT1254 using Tapatalk

i have the same problem with poweramp in nougat 7.1.2 i solve this problem installing the old gapps, i have gapps 7x in my pc from month past and i flash the gaaps and now is good for me, the license check

pankaj72 said:
Thank you for 8.x oreo
Flashed the rom and MindTheGapps-8.1.0-arm-20180610_023943.zip followed by clean modem status and
Radio_Flasher_Stock_MPGS24.107-70.2-2.zip
I have a problem with poweramp license verification.
Screenshot attached with logs.
Thank you very much
Click to expand...
Click to collapse
Seems like it's a known issue with the latest Play Store update. Flash this package (Play Store v10.6.30), clear data for the Play Store and try launching Poweramp again.
PSA: Latest Play Store update breaks license verification for paid apps
Apps such as Greenify and Poweramp unable to verify purchase with 280618 build of gapps

this rom is amazing thanks for you amazing job bhb27 ,but i found a bug, audio in games not working i test 3 different games and no have sound in games only in games, but this rom is awesome thanks for your job bro!!

audio on call and video call of whatsapp does not work is mute my microfone for whatsapp calls for me
Enviado desde mi Moto MAXX mediante Tapatalk

Hi there, thank you very much for this excellent rom.
So far so good, just two issues:
- whatsapp audios doesn't work, i mean can't hear on both ear or speaker.
- bluetooth connects to my car, but can't play any kind of sound, music or telephone call, anything.
Hope i was clear, lol
Thank you m8
PS: is that a mate on your profile picture ?

Development [ROM] crDroid v8.2 | Android 12 [UNOFFICIAL] [March 3]

{
"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/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (N/A)
gapps (Included with build due to specific requirements)
Magisk 24.0 or newer for root (after first boot) - (Download from here)
First time installation:
these steps assume you already have an unlocked bootloader
Install fastboot on your PC if not installed already.
Place downloaded rom zip in the same folder as the fastboot.exe
Open command prompt inside that directory or use the change directory command to change after launching command prompt
Reboot Phone to bootloader (adb,button combo, whichever way you like to do it)
Once at bootloader screen type the following into command prompt exactly as shown minus the quotes, replacing <filename.zip> with the actual filename of the downloaded rom including the .zip extension: "fastboot -w update <filename.zip>" THIS WILL WIPE YOUR DATA PARTITION!!!!
Now just sit back and wait, the device will reboot a couple times during the process. just leave it be and do not unplug it from the PC until it has booted to the Setup Wizard Welcome screen.
Update installation:
Place newly downloaded rom zip inside same folder as fastboot.exe
Reboot device to bootloader
Open command prompt inside same directory as fastboot.exe and rom zip
type "fastboot update <filename.zip>" (without the quotes). Your device will reboot a couple times throughout the flashing process. This will update your device with specified rom.zip without wiping your userdata. But FYI there have been times where a new bug was discovered that was not actually a bug and was fixed with a fresh installation after wiping userdata. It's just the nature of the game with flashing developing ROMs
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://android.googlesource.com/device/google/raviole-kernel
Download:
ROM CrDroid v8.2 UNOFFICIALraven fastboot flashable zip w/GAPPS
Changelog: CrDroid v8.2 raven changelog
Known issues:
In Settings Submenu for the Ambient Music/Now playing feature it always says there is no internet connection when you go to those settings menus but the feature still works as it should. Working to resolve as we speak.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Donate specifically to myself the current device maintainer for raven to maybe buy me a coffee or something Never expected, but much appreciated!

Reserved

Reserved

Awesome, man. Also, one could say this about these builds: "a build is never late. Nor is it early. It arrives precisely when it intends to"

Congrats ! Finally a custom build for P6P. Great work @albinoman887

Hola
Thanks for an awesome release. So many of us are very grateful for time and effort that you put into this.
Cheers.

albinoman887 said:
This is an UNOFFICIAL build.of crDroid v8.2 based on Android 12 for the Google Pixel 6 Pro.. I did NOT create this ROM, it is an Open Source project by the community for the community and has many many contributors , some from this very thread!. thanks to all who have contributed to CyanogenMod/LineageOS/crDroid and all other Custom ROM projects over the years.
Code:
[B]IMPORTANT[/B]
* Builds are done when they are done, and not a second sooner. Please no build begging.
* Do NOT be rude.
* If you don't get a reply from me in a timely manner about your bug, sorry i do this in my spare time
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.
Built from latest crDroid Android 12 source
All Hardware features (calls/Wifi/Bluetooth etc) all working!
All the usual crDroid specific customization options, including but not limited to - Custom Monet theme settings, Navigation Bar Customization, Many Fonts, Custom Icons and other UI tweaks as well as the following additional Pixel Specific features unofficially added
Quick-Tap
Ambient Music - Now Playing
Pixel Launcher
Smartspace
Less padding on Gboard portrait mode as the keys seem unusually narrow to me otherwise (even on stock)
Android Intelligence Service related things in Settings report "No Internet" when indeed there is . examples are the Now Playing Settings page in Sound. When enabled it will say No Internet below the toggle switch but the feature still works. I narrowed it down to a priv-app permissions issue. Seems to only be cosmetic though so don't worry.
PAY ATTENTION!! DIFFERENT THEN MOST DEVICES! CURRENTLY TWRP DOESNT SUPPORT OUR DEVICE SO FASTBOOT MUST BE USED INSTEAD! GAPPS IS ALSO INCLUDED IN THE BUILD DUE TO SAME LACK OF TWRP!
(if you are comfortable with fastboot just run the following commands from fastboot if you are unsure of the procedure please read on IT IS DIFFERENT THEN TWRP!
Code:
(boot to bootloader)
fastboot -w
fastboot update crDroid-v8.2<builddate>-UNOFFICIAL-raven_fastboot.zip
Boot to bootloader
from terminal/command prompt: fastboot reboot bootloader
if you are coming from a different rom wipe userdata by typing fastboot -w
now type fastboot update filename.zip where filename is the name of the downloaded zip. (e.g, crDroid-v8.2<builddate>-UNOFFICIAL-raven_fastboot.zip)
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Devs
crdroid Devs
@delet_thiskthx
Me
Not expected by any means but always brings a smile to my face when I see it, If anyone wants to Paypal me a couple bucks my way it would really help cuver all the coffee and smokes i go through debugging stuff haha
Thanks and happy flashing!
Mar 3
* Initial XDA Release (no changes)
Mar 1
* Initial internal test Release
* Fixed VoLTE not being enabled with some carriers
* Added Quick-Tap function from Stock
* Added Ambient Music - Now Playing function from Stock
* Fixed HvmSVManager from crashing
* Re-enabled background blur
* Fixed color space corruption with some wallpapers when exiting AOD mode
[ROM]: crDroidAndroid-12.0-20220301-raven-v8.2_fastboot.zip
Gapps: TEMP INCLUDED WITH ROM IMG UNTIL ITS FLASHABLE VIA CUSTOM RECOVERY
[Download Archive]: All ROMs
https://github.com/crdroidandroid
https://github.com/Albinoman887/android_device_google_gs101
https://github.com/Albinoman887/android_device_google_raviole
https://gitlab.com/Albinoman887/vendor_google_raven
XDA:DevDB Information
crDroid v8.2| Android 12 for Google Pixel 6 Pro (raven), ROM for the Google Pixel 6 Pro
Contributors
albinoman887
Source Code: http://github.com/Albinoman887
ROM OS Version: Android 12
ROM Firmware Required: Latest BL and MODEM are recommended
Based On: crDroid
Click to expand...
Click to collapse
Great news! Thanks for the P6P custom Rom @albinoman887 and crew.

Thanks dev and team, it's running great, I had no issues with installation.....let the game begin.
Thanks again. Donation sent.

@albinoman887 nice to see someone step up and start pumping out some builds! I was starting to worry that I'd have to blow the cobwebs off my dinosaur and come out of inactive status. Thanks for your efforts.

I love this ROM. great work. I'm getting everything set up now. I have one question tho. I use smart launcher but can't get material you icons to apply and don't see the theme icons option in wallpaper/style. Am I doing something wrong or did I miss something? Thanks in advance

AlphaKoi said:
I love this ROM. great work. I'm getting everything set up now. I have one question tho. I use smart launcher but can't get material you icons to apply and don't see the theme icons option in wallpaper/style. Am I doing something wrong or did I miss something? Thanks in advance
Click to expand...
Click to collapse
I have had this issue before on stock. The full list of options didn't show up until enough time passed and a phone reboot after the wipe and re-flash. That's what happened to me, so perhaps you're facing the same, temporary issue.

Can't wait to flash this after work. My main issue with this phone is using stock navigation bar. It's so finicky with the taps it sometimes goes 3-4 times back. I hope this ROM has fixed the sensitivity on the navigation bar. Like I said, can't wait! Thanks for the hard work OP.

chopt51 said:
Can't wait to flash this after work. My main issue with this phone is using stock navigation bar. It's so finicky with the taps it sometimes goes 3-4 times back. I hope this ROM has fixed the sensitivity on the navigation bar. Like I said, can't wait! Thanks for the hard work OP.
Click to expand...
Click to collapse
Its a great ROM and to me everything is smooth like butter. Flash and enjoy

AlphaKoi said:
Its a great ROM and to me everything is smooth like butter. Flash and enjoy
Click to expand...
Click to collapse
Has the stock navigation bar received any fixes? If you softly tap on the back button does it fly back 4-5 pages?

Joe) how well does this rom work on oneplus 6t?

chopt51 said:
Has the stock navigation bar received any fixes? If you softly tap on the back button does it fly back 4-5 pages?
Click to expand...
Click to collapse
Sadly I couldn't say. I don't use stock navigation. I use gestures. That much is very smooth. I would assume it's the same

AlphaKoi said:
Sadly I couldn't say. I don't use stock navigation. I use gestures. That much is very smooth. I would assume it's the same
Click to expand...
Click to collapse
Anyway you could disable gestures in the settings, enable navigation bar. Then lightly tap the back button and see if it is overly sensitive resulting in multiple back taps? Thanks in advance. I'm at work. Will test tonight anyway.

chopt51 said:
Anyway you could disable gestures in the settings, enable navigation bar. Then lightly tap the back button and see if it is overly sensitive resulting in multiple back taps? Thanks in advance. I'm at work. Will test tonight anyway.
Click to expand...
Click to collapse
I did it. Seems smooth on my end. No lag. No additional keystrokes. Nothing janky. I hope you love the ROM like I do

AlphaKoi said:
I did it. Seems smooth on my end. No lag. No additional keystrokes. Nothing janky. I hope you love the ROM like I do
Click to expand...
Click to collapse
you are right. I flashed the ROM and the navigation bar is fixed for me. I appreciate the help in testing. The ROM is great!
Edit: spoke too soon. Problem still here. Must be my device.

albinoman887 said:
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/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (N/A)
gapps (Included with build due to specific requirements)
Magisk 24.0 or newer for root (after first boot) - (Download from here)
First time installation:
these steps assume you already have an unlocked bootloader
Install fastboot on your PC if not installed already.
Place downloaded rom zip in the same folder as the fastboot.exe
Open command prompt inside that directory or use the change directory command to change after launching command prompt
Reboot Phone to bootloader (adb,button combo, whichever way you like to do it)
Once at bootloader screen type the following into command prompt exactly as shown minus the quotes, replacing <filename.zip> with the actual filename of the downloaded rom including the .zip extension: "fastboot -w update <filename.zip>" THIS WILL WIPE YOUR DATA PARTITION!!!!
Now just sit back and wait, the device will reboot a couple times during the process. just leave it be and do not unplug it from the PC until it has booted to the Setup Wizard Welcome screen.
Update installation:
Place newly downloaded rom zip inside same folder as fastboot.exe
Reboot device to bootloader
Open command prompt inside same directory as fastboot.exe and rom zip
type "fastboot update <filename.zip>" (without the quotes). Your device will reboot a couple times throughout the flashing process. This will update your device with specified rom.zip without wiping your userdata. But FYI there have been times where a new bug was discovered that was not actually a bug and was fixed with a fresh installation after wiping userdata. It's just the nature of the game with flashing developing ROMs
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://android.googlesource.com/device/google/raviole-kernel
Download:
ROM CrDroid v8.2 UNOFFICIALraven fastboot flashable zip w/GAPPS
Changelog: CrDroid v8.2 raven changelog
Known issues:
In Settings Submenu for the Ambient Music/Now playing feature it always says there is no internet connection when you go to those settings menus but the feature still works as it should. Working to resolve as we speak.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Donate specifically to myself the current device maintainer for raven to maybe buy me a coffee or something Never expected, but much appreciated!
Click to expand...
Click to collapse
OK. I need a video tutorial, many thanks?

Development Paranoid Android Topaz 1 - POCO F4 / Redmi K40S [MUNCH]

{
"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"
}
We are very excited to announce Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* You tell us
Requirements
Make sure you've latest platform tools for Android.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels are NOT supported the kernel says it supports PA and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Paranoid Android Topaz released
Instructions (fastboot method)
* Reboot to fastboot
* fastboot update --skip-secondary --skip-reboot aospa*.zip
* Reboot into recovery
* Wipe Data / Factory Reset
* Reboot to system
Instructions (recovery method)
* Reboot to recovery (twrp or ofox)
* Flash firmware (miui 14 global)
* Flash rom
* Format data
* Reboot to system
Kernel source
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!

Screenshots

reserved

any custon setting?

Boom_Hacker said:
any custon setting?
Click to expand...
Click to collapse
i found thank you

Is camera working here? even if is an AOSP or MIUI?

Looks cool~

OMG I can tell you guys, it's maybe the BEST ROM EVER for Poco F4, It has the Oxygen OS Camera with all the effects working. The look n' feel is awesome!! so clean, so fast, so compatible with everything you need.
I didn't find any issues so far.
Just give it a try, FOR REAL!!

i have installed with recovery method and i had spark os previously and it overwriten over it like an update instead of clean update.
Anyway after that i wanted to first clean everything and then flash the ROM but i cant seeem to boot twrp from fastboot.
"fastboot boot recovery" does not work. tried both orangefox and twrp. This might be a bug.
I think i have to flash someother rom first and then boot into TWRP.

tinted said:
i have installed with recovery method and i had spark os previously and it overwriten over it like an update instead of clean update.
Anyway after that i wanted to first clean everything and then flash the ROM but i cant seeem to boot twrp from fastboot.
"fastboot boot recovery" does not work. tried both orangefox and twrp. This might be a bug.
I think i have to flash someother rom first and then boot into TWRP.
Click to expand...
Click to collapse
you using wrong command you need to boot into recovery by 'fastboot boot filename.img'
or flash recovery as boot by 'fastboot flash boot filename.img' after installing rom it will automatically change to aosp recovery also boot will restore

Siddk said:
you using wrong command you need to boot into recovery by 'fastboot boot filename.img'
or flash recovery as boot by 'fastboot flash boot filename.img' after installing rom it will automatically change to aosp recovery also boot will restore
Click to expand...
Click to collapse
i am using the correct command, I was just lazy to include the .img in the comment i wrote. I did not try the "fastboot flash boot filename.img" though. This issue might also be because of the ROM overwriting last ROM.
Anyway, i reinstalled MIUI fastboot rom and then did " fastboot boot filename.img" and it worked this time. And then installed paranoid android after clean wipe. Everything working now.
INITIAL IMPRESSIONS of ROM,
wifi strength is little less. 5 Ghz wifi is disconnecting frequently and staying on 2.4ghz. I has to manually connect to 5ghz wifi multiple times even when i am right next to router.
5G on Jio is not working, used to work in spark OS I used. although i did change from 14.0.2 indian firmware to 14.0.4 indian firmware. I dont think newer firmware should break 5G but we nevere know.
since 5G is in trails we get unlimited data so 5G support would be nice. Also, i get 500mbps siting at home so that is a plus as well.
Wireless display casting is working.
standby battery seems very good.
I miss HBM. I feel like display could get little more brighter but i cannot do side by side testing so i might be wrong.
battery percentage inside a circle battery indicator would be nice, otherwise it is taking lot of status bar space. if not that then circle indicator instead of bar would be better to read the battery status.

tinted said:
i am using the correct command, I was just lazy to include the .img in the comment i wrote. I did not try the "fastboot flash boot filename.img" though. This issue might also be because of the ROM overwriting last ROM.
Anyway, i reinstalled MIUI fastboot rom and then did " fastboot boot filename.img" and it worked this time. And then installed paranoid android after clean wipe. Everything working now.
INITIAL IMPRESSIONS of ROM,
wifi strength is little less. 5 Ghz wifi is disconnecting frequently and staying on 2.4ghz. I has to manually connect to 5ghz wifi multiple times even when i am right next to router.
5G on Jio is not working, used to work in spark OS I used. although i did change from 14.0.2 indian firmware to 14.0.4 indian firmware. I dont think newer firmware should break 5G but we nevere know.
since 5G is in trails we get unlimited data so 5G support would be nice. Also, i get 500mbps siting at home so that is a plus as well.
Wireless display casting is working.
standby battery seems very good.
I miss HBM. I feel like display could get little more brighter but i cannot do side by side testing so i might be wrong.
battery percentage inside a circle battery indicator would be nice, otherwise it is taking lot of status bar space. if not that then circle indicator instead of bar would be better to read the battery status.
Click to expand...
Click to collapse
CAF based rom use different recovery make sure you using correct one sparkos recovery not works on caf
5G should work try to enable with code

Siddk said:
CAF based rom use different recovery make sure you using correct one sparkos recovery not works on caf
5G should work try to enable with code
Click to expand...
Click to collapse
No bruh its the same recovery caf and for Aosp

Siddk said:
CAF based rom use different recovery make sure you using correct one sparkos recovery not works on caf
5G should work try to enable with code
Click to expand...
Click to collapse
sorry but i dont know what you mean by code.

"Hey Google" works super responsively from screen off state.
Netflix supports HDR 10.
Google Sounds app for ringtones seems to be bugged. Tried installing/updating with 3rd party apk and it still buggy. majority sounds dont work at all

tinted said:
Hey Google works super responsively from screen off state.
Netflix supports HDR 10.
Google Sounds app for ringtones seems to be bugged. Tried installing/updating with 3rd party apk and it still buggy. majority sounds dont work at all
Click to expand...
Click to collapse
only for you its work for me installed official topaz1 paranoid
https://builds.paranoidandroid.co/aospa-topaz-1-munch-20230426.zip

REDOTHELLO said:
only for you its work for me installed official topaz1 paranoid
https://builds.paranoidandroid.co/aospa-topaz-1-munch-20230426.zip
Click to expand...
Click to collapse
sorry but what is working for me? i am confused by your comment

can anyone else confirm that their Google pay and Phone pay are able to activate the bank accounts, this might be SBI bank account related as well but sms verification failing from two days.
EDIT: its working, it is as stupid as selecting wrong sim for verification. But I was selecting SIM1 which was supposed to be my main SIM card and I double checked afterwards in the SIM tray and my main sim card is in SIM 1 slot but in software it is reversed somehow
Can using Indian MIUI firmware instead of Global firmware be the issue?

Does this Custom ROM Support Dolby Atmos by Ryzuki ?

Hand down best battery life among all ROMs i tried, it's not even close. I never get more than 5hrs since i enable every feature there is.
I still have to test with some of my apps that run constantly in background, like Google fit activity tracking, Resilio Sync(file backup),wavelet(audio convolution, basically corrects my earphones to more neutral signature),password manager, earbuds software, mi band app.

Develop Bugs

welcome