Develop Bugs

WorkAround: MultiRom + Kernel Panic on Secondary Rom

Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.

Thank you for this. I have been flashing RIN kernel after any cm12 I've installed since installing MultiROM. Seems to work too, but the hour long wait to flash a 7mb kernel really bugs me.
Next time I flash a cm12 as secondary I'll give this a go.

Eliminater74 said:
Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.
Click to expand...
Click to collapse
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.

aclegg2011 said:
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.
Click to expand...
Click to collapse
Yes from what I have tested it works with any Compatible flashable Kernel that unzips and has a boot.img..
The above kernel that I listed on post #1 is Stable but is overclockable, If you dont want that.. Then dont use that one, It was only listed as an Example.
I use that kernel with no problems.. I dont OC my phone, but its nice to have the option to do so.
Ill test out the tootie-pop kernel the next time I feel like messing with my phone.
Now isnt a good time, Im sick, and I have already messed up my linux system and my windows system (windows 10 Enterprise build 9926).. Had to do a fresh install on windows.. my linux doesnt want to let me mount my own drives in gnome.. Says I dont have access do to some error, But I am running Ubuntu Vivid 15.04.. so thats to be expected..
So touching my phone isnt a good idea right now.. I might just end up blowing it up the way my luck is going.

Thanks to the OP. This was a quick and simple fix to a frustrating issue.
Sent from my LG-D851

After doing a little research, and finding out that the MultiRom is pretty much dead. I decided to delete it all together and stick with the one rom that seemed
very stable and likable for me. I wont say what rom that was as to respect all developers on this forum.. So I stopped all testing and experiments dealing with MultiRom..
If the Developer once again decides to post updates and fixes. I will again. try it.. but for now.. I will no longer post any workarounds or help with this MultiRom section anymore...
As you know that thread was closed in the ROM Development section..

[Kernel][LOS/CAF][M/N] Linux 3.10 custom kernel v3

Linux 3.10-based kernel for Oneplus One (bacon)
Info:
use this kernel at your own risk. Flashing it the wrong way might brick your device. I'm not responsible for any software/hardware damage.
This kernel is based on top of erorcun's 3.10 kernel. erorcun has spent an enormous time working on this project and he deserves a huge "Thank you" for having succeeded in one of the most difficult tasks in Android development: upgrading a device to a newer Linux release.
Features:
v3 (12th December)
built with O3 optimizations
CAF CPU boosting driver (replaces cpu_input_boost - might be a temporary switch)
kernel code base updated to Linux 3.10.60
sdcardfs updates
minor miscellaneous improvements
old releases:
v2.1
minor stability fix
v2 (12th November)
kernel code base updates reverted, then re-applied only up to 3.10.54
compiled with an improved set of GCC flags
tuned AIO for SSD-only machines
v1 (30th October)
built with GCC 5, UBER Toolchain and the optimal compiler flags for Krait CPUs
kernel code base upgraded to Linux 3.10.88
power-efficient workqueues
sound control by francisconfranco
CPU voltage control
cpu_input_boost by Sultanxda
sdcardfs & f2fs support
support for both LineageOS's and Sultan's camera HALs
Compatibility
The kernel is compatible with all the Marshmallow/Nougat ROMs that use either LineageOS's camera HAL or Sultan's (a.k.a. CAF's). Just make sure you download the right version
Currently, the kernel has been tested only on LineageOS 14.1, but I'm sure the CAF build is safe to flash and works properly as well.
The kernel doesn't work on Oreo (yet)!
Download
The kernel can be download from AFH: 3.10 kernel on AndroidFileHost
Thanks to:
erorcun, franciscofranco, Sultanxda, CAF & UBER, Mecca EL.
XDA:DevDB Information
Tom's Linux 3.10 kernel, Kernel for the OnePlus One
Contributors
Tomoms, erorcun
Source Code: https://github.com/Tomoms/neon_kernel_bacon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2017-12-12
Created 2017-10-30
Last Updated 2017-12-12

thanks man! any plans on oreo version?

criminality said:
thanks man! any plans on oreo version?
Click to expand...
Click to collapse
Everything will come in due time
It's one of the things I'll work on soon. Be patient, and you'll eventually get what you want

Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.

Fatsodonkey said:
Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.
Click to expand...
Click to collapse
Could you tell me the exact resolution you used?

Tomoms said:
Could you tell me the exact resolution you used?
Click to expand...
Click to collapse
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.

Fatsodonkey said:
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.
Click to expand...
Click to collapse
I'll compare the camera driver present in this kernel and the one in Sultan's kernel, then try to fix this. Unfortunately at the moment this is the best thing we can achieve, CAF camera support had always got some small problems even in erorcun's build if I recall correctly, and these problems are inevitably "inherited" by my kernel.

Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later

TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.

TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.

Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
What about encryption? Are your TWRP able to decrypt data with this kernel?

Tomoms said:
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.
Click to expand...
Click to collapse
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
TbMa said:
What about encryption? Are your TWRP able to decrypt data with this kernel?
Click to expand...
Click to collapse
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.

Mecca EL said:
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.
Click to expand...
Click to collapse
Well i am using encryption since early MM and not a single problem if developer of rom and kernel did his work fine. Biggest payoff its hit battery.
Unfortunately you cant revert encryption without formating whole internal storage, so its a little bit complicated with backups and etc

MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.

SirSoviet said:
MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.
Click to expand...
Click to collapse
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?

Tomoms said:
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?
Click to expand...
Click to collapse
I never record videos, so I don't know. I'll check later today.

@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).

Mr.Ak said:
@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).
Click to expand...
Click to collapse
Thank you for letting me know. I'll immediately update the thread.

SirSoviet said:
I never record videos, so I don't know. I'll check later today.
Click to expand...
Click to collapse
Nothing wrong with video recording here.

SirSoviet said:
Nothing wrong with video recording here.
Click to expand...
Click to collapse
Hmm... I'll try it myself soon. In the meantime, my main concern will be fixing MTP, and it won't take me too much, fortunately.

🤖 FLUENCE UHD PATCH 🤖 // SOSP 22.02.18 🤖

The Inventor of the Android Patch System presents​WELCOME TO FLUENCE UHD SOSP​HINT​See Post: https://forum.xda-developers.com/showpost.php?p=78928919&postcount=25 For the latest Update and News​
INDEX​POST 1 - INFOS
POST 2 - DOWNLOAD
POST 3 - INSTRUCTIONS​
ABOUT​My Projects are always aiming on delivering a clean and fluent Operating System, with the maximum level of quality in all views. Fluence UHD is back, and now bigger and better as before! Expierence the optimizations and secrets i discovered and collected over all the Years with My Work.
Enjoy the options of the AROMA Installer and get a optimized Google Stock System with 4K HDR Video Playback, better Audio Quality and even better Performance and Effiency on all Parts of the System. Forget Mods, Modules and Bootloops. The Fluence UHD Patch comes with all You need! GApps, Busybox, Magisk, init.d Support, and the hugest Collection of Android Build Optimizations... You will feel the Love i put in My Work. WORD <3
XDA:DevDB Information
🤖 FLUENCE UHD PATCH 🤖, ROM for the Google Pixel 2 XL
Contributors
Miustone, Miustone, Miustone, Miustone
Source Code: https://github.com/Miustone/SOSP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Google Factory Image: https://developers.google.com/android/images /AND Deuces Script 4.5: https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2019-02-19
Created 2019-02-13
Last Updated 2019-02-21

DOWNLOAD

Instructions:
FOLLOW THIS THREAD TO GET THE LATEST STOCK OS:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Fully boot Your Pixel into the Stock OS
Skip the Google Setup Wizard
Place the Patch on Your Device Storage
Reboot in to TWRP
Wipe Data and Dalvik Cache
Flash the Patch
Reboot in to System
Done
SOSP RELEASES
Visit my Repository from the Thread
Download the Master Branch as zip
Repack the Patch zip
Make sure META-INF and everything else is on root of the zip
Use it with the Instructions from above
Done

Upload for todays build takes still one hour for now. You can select with Drive also older Versions of the ZIP (Acutal is V2, Uploading is V3) btw. Enjoy!
EDIT:
New Device new trouble. Got bootloops with the uploaded Version so do i have to revert some Things. Stay tuned!

I am looking forward to testing this out. I am happy we are finally getting a ROM that is based off the stock ROM. I will keep an eye out when you fix the bootloop issue. I will then download and install it on my phone and give you feedback.. Thank you!

encephalon9986 said:
I am looking forward to testing this out. I am happy we are finally getting a ROM that is based off the stock ROM. I will keep an eye out when you fix the bootloop issue. I will then download and install it on my phone and give you feedback.. Thank you!
Click to expand...
Click to collapse
I'm still fighting with Treble (A/B System // Vendor), and there is a some unusable stuff like the Debloat Part in AROMA which was needed for the Standard OEM Bloat from SONY, LG and Others. But i think i can push a clean and good working Build at the end of this Week...
Stay tuned
EDIT: Slightly updated Build will come in some Hours! I reverted my latest changes and cleaned everything up. Looks like the Kernel Patching does not work that nicely. I will try the famous Elemental Kernel for My needs...

Miustone said:
I'm still fighting with Treble (A/B System // Vendor), and there is a some unusable stuff like the Debloat Part in AROMA which was needed for the Standard OEM Bloat from SONY, LG and Others. But i think i can push a clean and good working Build at the end of this Week...
Stay tuned
EDIT: Slightly updated Build will come in some Hours! I reverted my latest changes and cleaned everything up. Looks like the Kernel Patching does not work that nicely. I will try the famous Elemental Kernel for My needs...
Click to expand...
Click to collapse
Sounds good. My fiance and I just planned a random Valentine's day trip to Nashville, TN so hopefully I will be able to try it out today or tomorrow! Got a 10 hour drive coming up soon.

encephalon9986 said:
Sounds good. My fiance and I just planned a random Valentine's day trip to Nashville, TN so hopefully I will be able to try it out today or tomorrow! Got a 10 hour drive coming up soon.
Click to expand...
Click to collapse
Sweet, have a good One :angel: Wish i had the Time with Mine. We have both to work early tomorrow

Is it absolutely necessary to wipe Data if your already running stock? Should I flash patch now or wait for the update.

mookiexl said:
Is it absolutely necessary to wipe Data if your already running stock? Should I flash patch now or wait for the update.
Click to expand...
Click to collapse
Most of the final Content is missing but You can go thru AROMA without Problems. The DPI May be also a bit low which means a Mini Setup Wizard but You can adjust that over the Display and Text Size Settings for now. It was running stable for me so far but i own my Pixel not that long and have to Test more Things Out.
BR
Oh and Yes, Data should be wiped since many Essential Things get changed on the System Part like the Multi Tasking (RAM Management) Audio Rendering, UI Rendering and so on. A Clean Start means less or even No Problems. A Backup of Stock would be also a smart move which saves Time. A compressed Image including Vendor, boot and System should Take Up under 5gb of Storage ..

Miustone said:
Most of the final Content is missing but You can go thru AROMA without Problems. The DPI May be also a bit low which means a Mini Setup Wizard but You can adjust that over the Display and Text Size Settings for now. It was running stable for me so far but i own my Pixel not that long and have to Test more Things Out.
BR
Oh and Yes, Data should be wiped since many Essential Things get changed on the System Part like the Multi Tasking (RAM Management) Audio Rendering, UI Rendering and so on. A Clean Start means less or even No Problems. A Backup of Stock would be also a smart move which saves Time. A compressed Image including Vendor, boot and System should Take Up under 5gb of Storage ..
Click to expand...
Click to collapse
Cool bro. I'll elect to to wait while you get adjusted to this device. I know your work is superb based off what you've done on devices past.

Will this work on walleye (Pixel 2)?

bassguy60 said:
Will this work on walleye (Pixel 2)?
Click to expand...
Click to collapse
Yes
Can aynone tell Me btw why there is no MTP in TWRP? Reovering the Device after testing a Patch means always a full flash with Factory Image for Me. Followed by a boot in the System where i have to use PTP to copy my ZIP. Cruel to develop like that TWRP is the other painful Point. Wish the Pixel would have a classical Recovery Partition...
EDIT: Seems like we have to boot once after flashing Stock to be able to flash Magisk and get a booting System!? That could be the Reason why my full stock rom wasn't booting. Feeling me a bit dumb right now...
EDIT2: I will push more Time in a full Stock ROM to get a Monthly updated Base for my Changes. Once i got a fully working ROM can i start with adding AROMA Options and Stuff like that. I think the only Problem with My ROM was the patched Kernel which don't wanted to boot and not the deodexing or the Updater Script... Any help with it is welcome

Miustone said:
Expierence the optimizations and secrets i discovered and collected over all the Years with My Work. Enjoy the options of the AROMA Installer and get a optimized Google Stock System with 4K HDR Video Playback, better Audio Quality and even better Performance and Effiency on all Parts of the System. Forget Mods, Modules and Bootloops. The Fluence UHD Patch comes with all You need! GApps, Busybox, Magisk, init.d Support, and the hugest Collection of Android Build Optimizations... You will feel the Love i put in My Work. WORD <3
Click to expand...
Click to collapse
Uh.. secrets? Maybe you're a non-native English speaker and used the wrong word, but what 'secret optimizations' can there be in something that is opensource?
Could you elaborate on the collection of Android Build Optimizations you are using? Can't see for ourselves because the link to source code is 404.

bobbarker2 said:
Uh.. secrets? Maybe you're a non-native English speaker and used the wrong word, but what 'secret optimizations' can there be in something that is opensource?
Could you elaborate on the collection of Android Build Optimizations you are using? Can't see for ourselves because the link to source code is 404.
Click to expand...
Click to collapse
Hey,
Secrets is maybe not the right Word. It's more like many Developers and even OEMs don't know about all the Stuff of Android. I discovered Bug fixes, functions and Features which are now used in a wide range of Mods and ROMs and even OEM Firmwares, and while never getting Credits for it am i aware about where it popped up first in the Web ? I was the First One for example who got all real Pixel Features on a non Pixel Device by porting a lof of System Stuff and Not only by changing one or two Files. I also ported MIUI in the past which was mind opening for Me Back in that Time...
The Secrets i use here are just a greatly tested bunch of Configs for the Hard and Software of our Android Devices in other Words.
And yeha, sorry for My English! It's not the best ?

What should I do if my phone freezes? I have this issue everytime. If I reboot into TWRP and then flash the Patch again, I get an error

gogixx said:
What should I do if my phone freezes? I have this issue everytime. If I reboot into TWRP and then flash the Patch again, I get an error
Click to expand...
Click to collapse
I discovered this issue only with attached USB Cable, have you tried it without? As usual can you just press the bottom right edge a few times and you will complete the installer without Problems when this happens.
I'm still working on a full stock zip... Possible that i end up with raw images :/

Sorry if I sound as a noob, but what does it means "press the bottom right edge"? It stucks on 82% and there is nothing to press. ?

gogixx said:
Sorry if I sound as a noob, but what does it means "press the bottom right edge"? It stucks on 82% and there is nothing to press.
Click to expand...
Click to collapse
It's the spot where You clicked to go to the next Page in AROMA. Press it 4 or 5 Times and it will exit AROMA to TWRP. It's a ugly AROMA bug which never got fixed in the last 4 Years...

Alright, just to let You know Guys. Making Stock ROMs from actual Google Images is cruel. There is almost no benefit against flashing with a PC except for the need to have a PC. The Patch will be the only Thing that works just fine if we want Stock Edits...
I'm actually ripping everthing out of the Patch and i'm redoing the Scripts and hope it will work. Cross the Fingers!
Can anyone tell me btw how to create a working backup of stock with TWRP? Looks like my backups won't start..

[ROM][All Quark][9.x]LineageOS

ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open GApps:
Open Gapps Click Here
Choose Platform: ARM, Android: 9.0, 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
Instalation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM 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
Changelogs:
LineageOS - Pie source and Quark Changelog (Click Here)
What's working :
Everything.
Known Pie Bugs :
TWRP can't backup or decrypt data encrypted on Oreo or Pie: 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: Very rare bug this days, the device can finish 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.
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...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][9.x]LineageOS ROM for Quark
Contributors
Felipe Leon (fgl27)
Jagrav Naik
Gabriel Gomez
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Created 2019-24-05
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 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 is a Nougat and U 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

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

Hello, thanks for make this version for the quark..
i have this issue, when i ve flashed this rom and then the gaaps, when i restart to bootloader and then select start (for boot os), still freeze on "warning bootloader unlocked" and not start the os., do you know what may be happening with this issue?
Thanks you again!

strik3x said:
Hello, thanks for make this version for the quark..
i have this issue, when i ve flashed this rom and then the gaaps, when i restart to bootloader and then select start (for boot os), still freeze on "warning bootloader unlocked" and not start the os., do you know what may be happening with this issue?
Thanks you again!
Click to expand...
Click to collapse
OK, that is a kernel issue, I was testing with this
https://forum.xda-developers.com/showpost.php?p=79591822&postcount=1981
didn't notice the issue...
if you wanna to use this ROM please flash that zip after gapps, and all will work.
Or wait until I released a new one later today.

OK all download links are working/booting now.

fgl27 said:
OK all download links are working/booting now.
Click to expand...
Click to collapse
Now i can install without issues. Thanks you!!
Enviado desde mi Moto MAXX mediante Tapatalk

This rom is definitely more smoother than rr.
Thnx @fgl27 for this.

very fluid this rom, everything is fine, just add the Pie navigation bar and disable the physical buttons, keep updating.

I push a new update.

@fgl27,sir can u plz add back button mappings in buttons section????

zahids12345 said:
@fgl27,sir can u plz add back button mappings in buttons section??
Click to expand...
Click to collapse
No adding featuring. if los add will be there.
I barely have free time to fart if I start adding thing I will not have time even for that, as featuring take too much time to make.

@fgl27, it's ok sir

Does this rom have pocket detection?

zahids12345 said:
@fgl27,sir can u plz add back button mappings in buttons section????
Click to expand...
Click to collapse
RR is the ROM for buckets of features. LOS is always bare bones.

I push a updated.

Boa noite @fgl27 gostaria de reportar um bug, ele acontece tanto na LineageOs Pie quanto na Ressurrection Remix Os Pie, ao espelhar o aparelho na Smart TV O Som continua saindo pelo celular. No Android Oreo isso não acontece...
Desde já, Obrigado...

certified rom? (bank apps working?)

Moto Maxx 2019 said:
Boa noite @fgl27 gostaria de reportar um bug, ele acontece tanto na LineageOs Pie quanto na Ressurrection Remix Os Pie, ao espelhar o aparelho na Smart TV O Som continua saindo pelo celular. No Android Oreo isso não acontece...
Desde já, Obrigado...
Click to expand...
Click to collapse
this is a english only website.
google disable the wifi display featuring, so devs are working on bring it back, the audio is already working on latest ROM version from today.
This is not related to Google Chromecast, if you have a Google Chromecast receiver device the issue is not there, as google only disable wifi display in favor of they cast devices implementation, with will work better so if you have the Google Chromecast option always give that a priority I have here and it works way better then the wifi one.

I push a updated.

[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo)

Resurrection Remix Oreo​
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021

Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5

Has anyone tried it yet?

DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.

jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.

hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.

jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.

> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?

asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.

Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.

How does Resurrection Remix compare to CrDroid?

asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.

hockeymikey said:
Resurrection Remix Oreo​
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.

jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.

jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.

Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?

muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.

This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?

muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.

Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere