Develop Bugs

[ROM][5.1][Flounder] Pure AOSP 3/18/15 [LMY47D]

Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03

Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545

Future FAQ if necessary (let's hope not).

Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon

Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.

mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.

gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery

USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.

build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?

Flounder still isn't listed just lunch it anyway

Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0

Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse

belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.

Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.

omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.

gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?

jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.

| ROM | LineageOS 14.1 | unofficial | 27/02/2017 | Signature Spoofing integrated |

Hello
I am going to release unofficial builds of LineageOS 14.1 for Wileyfox Crackling. The builds will be updated every month after a new security patch level is reached.
The build I made can be flashed on top of Cyanogenmod 13 build (with wiping dalvik and cache). It should work without any problems; I do not experience any.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
If it makes problems, wipe data/dalvik/cache and install again.
Besides that the ROM has two extra features:
I patched signature spoofing support into the ROM. Now it is possible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and will not affect the ROM in any way. It has to be enabled in the according settings.
Also, there's an option available to record calls now. Please respect the privacy of others.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-02-01.html"]February[/URL] | 2017-02-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170227-UNOFFICIAL-crackling.zip
Download:
Code:
[B][SIZE="2"]Openload.co:[/SIZE][/B]
https://openload.co/f/DBKYItUGllA/lineage-14.1-20170227-UNOFFICIAL-crackling.zip
https://openload.co/f/grRwId0HJJE/lineage-14.1-20170227-UNOFFICIAL-crackling.zip.md5sum
Alternativ:
[B][SIZE="2"]Free.fr:[/SIZE][/B]
http://dl.free.fr/uqIBAf8dM
The kernel and device sources I used to build the ROM can be found here:
Code:
https://github.com/lineageos

thomson.aa said:
Hello
This is my first build of LineageOS for Wileyfox Crackling.
I flashed it on top of my Cyanogenmod 13 build (with only wiping dalvik and cache) and it so far works without any problems.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
This release has the root access option disabled because LineageOS disables root for apps by default. It has to be enabled before building the rom - I didn't know that so I will provide an updated rom with root access for apps available.
Besides that the rom has one extra feature:
I patched signature spoofing support into the rom. Now it is possbible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and has to be enabled in the according settings.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-01-01.html"]January[/URL] | 2017-01-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Download:
Code:
https://openload.co/f/WCt_JxGZ-UE/lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Click to expand...
Click to collapse
Sorry thomson.aa sorry i do not have english my google translation. Work is very nice thanks one has a mistake sim card people do not see a way to solve it? I wish you continued success.

Where is the source ? You can't post this without kernel source

I dirty flashed this over crDroid and it seems to be working pretty well. Thanks.
All my app's (not many at the moment) were working fine.
Playstore thinks it's 'no carrier Wileyfox Wileyfox Swift'... but I guess that's better than 'Wileyfox Pixel XL' (crDroid).
On initial booting the status bar wouldn't pull down but works ok after a reboot.
Buttons were a bit messed up which only gave me a back button even though the usual defaults were all set. After deleting them and re-adding them they worked fine. I'm guessing this may be due to dirty flashing. Shame the button customisation is just as basic as cm13 especially after using crDroid.
Using Kernal Auditor Mod I see that the cpu only scales down to 800mhz and the gpu scales up to 400mhz. I don't know much about this but won't this make it a little power hungry?
Going through the settings, I'm thinking that LOS14 isn't quite as complete as the cm13 I was using a few weeks ago. Although I guess this is to be expected at this stage. And I'm used to the more versatile crDroid now so I'll be restoring that in a mo.
This MicroG project sounds great. It seems a bit complex to get it working as I'd like but I definitely be having a go when I get my head around it.
All in all, Great job. Keep up the good work... please. I'm already waiting for the next release.
Oh, and er... Surely you could find a better file host???

I tried to build the Image myself by using your other Thread's How-To and after flashing i had no WIFI.
Now i flashed this build and WIFI is also not working.
[Edit]
I've collected some Logs - perhaps they'll help.
[Edit2]
Now i tried another '14.1-ROM' and i've the same problem....
During all my Tests the shown MAC-Address during the 'inital install' was weird: 02:00:00:00:00:00.
Before the 14.1 Lineage i had the latest CMmod 13 running without any Problems :/

Ok - solved it....
I encrypted my Device during CM13 and always entered my Key during Boot/TWRP and Formatting/Installation of 14.1.
Now i *really* formated all the Data (and the former encryption), rebooted to Recovery and sideloaded the Image+Gapps.
Now WIFI is working.

How do I enable signature spoofing ? I can't find any relevant setting.

M.A.K said:
How do I enable signature spoofing ? I can't find any relevant setting.
Click to expand...
Click to collapse
Settings -> Apps -> Gear symbol -> App permissions -> Spoof package signature

No... it's not there for me.

M.A.K said:
No... it's not there for me.
Click to expand...
Click to collapse
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.

fred0r said:
Now i *really* formated all the Data (and the former encryption)
Click to expand...
Click to collapse
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!

thomson.aa said:
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
Click to expand...
Click to collapse
Ah, yes... got it now, thanks.

jobedius said:
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
Click to expand...
Click to collapse
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.

update to official build?
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers

Nope, its not
Mithodin said:
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Click to expand...
Click to collapse
Twrp shows error 7(the data is incompatible). You need to wipe data, cache partitions and the system partition. Then install the zip with arm64 android 7.1 g-apps.
Cheers:good:

fred0r said:
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
Click to expand...
Click to collapse
Aahhh, that makes sense if you know it! Thanks!

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

[ROM][9] LineageOS, ResurrectionRemix, AEX, PE // personal builds

This thread was formerly "[ROM][9] LineageOS 16.0 + AOSPExtended + PixelExperience // personal builds" - yes, once again, the title can't fit the full names of all these ROMs :/
This thread hosts personal builds of LOS 16.0 and other Android 9 (Pie) ROMs for Mix 2, currently built from @wight554 's trees. Similar to Oreo, full credits to Wight and others behind the scene for the bringup, allowing us to build upon the awesome work.
Currently I build the following ROMs, usually monthly (in sync with security patch):
LineageOS 16.0
ResurrectionRemix 7
AOSPExtended 6
PixelExperience 9
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
...
What's working:
Everything?
Instructions:
Coming from official MIUI? Since the new encryption has been implemented, you only need to wipe (not format) /data.
Flash any Pie firmware (firmware Stable V10.4.1.0 recommended) for builds starting from May, or firmware Stable V10.0.2.0 otherwise.
Use official TWRP or OrangeFox.
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies to Pie
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "9" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
https://github.com/wight554/
About "official" status:
Currently I don't plan to apply for "official" for any of these ROMs, because 1) Wight is the actual maintainer who did the bringup and maintenance work, and 2) I like to be able to apply changes at will to the OS itself without restrictions from the official team.
Donation:
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 16.0, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, wight554, Cozzmy13
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V10.4.1.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2018-09-25
Last Updated 2019-09-27

Reserved
Just an additional note: I'm not as enthusiastic about building ROMs as I was early this year, so expect less regular updates and/or unanswered fix/feature requests. I'm just a builder, not nearly as capable of Demon or Wight doing all the heavy lifting, so I'll only do what my ability/time permits.

Thanks for all your work, Andy

Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.

Fairtex said:
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Click to expand...
Click to collapse
Statusbar customizations like network traffic aren't merged yet, just wait.

Can we have that slide down gesture to bring the notification bar down like we had in PE Oreo? Thanks

Hey,i have a question. Is it possible to port full screen gestures from miui 10 to los 16?

Are the quick settings on the status bar still a bit off on PE edition?

Folks who have tried, please do let me know about the battery consumption. This build added some CPU governors to the kernel and defaulted little cluster to one of them, and I'm not sure of its actual impact. It's my first time fiddling with kernels and I can't guarantee the change will be satisfactory.
Fairtex said:
Are the quick settings on the status bar still a bit off on PE edition?
Click to expand...
Click to collapse
I acknowledge the lack of padding there, but I don't quite want to look into it now. It's supposed be a problem for PE upstream anyway.

Greetings!
I've downloaded the rom last night. And until now, I have no problem: the camera works perfectly, the sound sound good and gaming performance are good.
The thing which attracted me was the mention of "Lineage OS" and I'm not disappointing to see that it's so close of the official and stable version . I'm blind in context of "find the bugs", so maybe we could find some but this is not my domain.

Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen

jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Install custom navigation bar .Its work fine
Wysłane z mojego MI MIX 2 przy użyciu Tapatalka

jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Expanded Desktop is a feature that will surely be merged in the future. As the other user said, there are 3rd-party apps that can achieve the same goal. I myself am using Tiles since it places a shortcut in Quick Settings.

Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless

MrSammyMcG said:
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
Click to expand...
Click to collapse
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.

AndyYan said:
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
Click to expand...
Click to collapse
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?

MrSammyMcG said:
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
Click to expand...
Click to collapse
This is Treble-enabled but this is NOT a GSI (Generic System Image). You still flash as you would do a regular ROM, just with a Treble-enabled recovery.

Quick update to sync with Wight's updated battery data - from this build on you're supposed to use newer firmwares. OP has been updated with the mandatory new firmware requirement and TWRP build from Wight.

Thanks for your work,I have used aex for two days.It is very nice.But I notice a small problem that sometimes the fingerprint unlock is very slow and I have to touch several times to unlock it.Is it a bug of this rom?

Duble tap on screen for wake up dosent works too

[ARM32] [9.0] [GSI PORT] Havoc OS 2.9

Before you get started,
i am not responsible for bricking device, dead sdcards,
muted alarm, or even thermonuclear war.
YOU chose to do this modification,
IF you point your finger to me to brick your device,
i will laugh at you.
This is GSI port from Official Havoc OS 2.9 by @vince31fr
Supported Devices
J701X
J730X
J600X
J530X
Details
Debloated /system 1037MB to 754MB
Pixel Launcher instead of Lawnchair
Includes SF-VENDOR 3.0 (Changelogs few days later)
Added M10 Fingerprint
Build.prop tweaks
No Gapps included, flash Open GApps ARM, 9.0, Pico
0.9GB /System with GApps Pico
Credits
Me for SF-VENDOR and Editing.
@vince31fr XDA for GSI
@ananjaser1211 for Cronos Kernel
Installation steps
You need Latest TWRP 3.4.0 or higher, or OFox 11.0
Flash Exynos7870_CreateVendor_2.0.zip
Flash HAVOC_REPARTITIONER.zip
Reboot recovery
Format data, Wipe Dalvik, Cache, System, Vendor, Data, Internal storage
And Flash Havoc-OS_2.9_J6-J5_J730_J701.zip
(Optional) Flash OpenGapps (Needed for Google Apps)
Reboot and Enjoy!
Bugs
HW Keys (Use NavBar instead)
Stretched Camera in J701 (Use 720p camera to fix this)
Downloads
GDrive
Mega
Telegram Support;
SF-GROUP
Everything Allowed but; Respect others. No NSFW/ Instant ban. No Ads. Enjoy
t.me
Contributors
@ichbinahmet
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 2.9
YY-DD-MM
Created 2021-30-09
Last Updated 2021-20-10

reserved

Thank you, but I've got bootloop. SM-J730F

Spargatorul said:
Thank you, but I've got bootloop. SM-J730F
Click to expand...
Click to collapse
Do you have /vendor partition?
You should flash Create Vendor from Project Spaget.
Im using same device, stable.

Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.

Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
You using wrong recovery.

Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Use TWRP 3.5.0
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com

Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Btw, ROM updated, read description, also use lastest TWRP .
Enjoy!

ichbinahmet said:
You using wrong recovery.
Click to expand...
Click to collapse
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?

Spargatorul said:
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?
Click to expand...
Click to collapse
Yes, inthread download links updated.

I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...

how to fix no audio?, j701f

Spargatorul said:
I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...
Click to expand...
Click to collapse
Probably you using custom kernel Kraken.
Flash latest from Magisk github

ichbinahmet said:
Probably you using custom kernel Kraken.
Flash latest from Magisk github
Click to expand...
Click to collapse
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.

Spargatorul said:
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.
Click to expand...
Click to collapse
Yes KRAKEN kernel breaks ROM on magisk flash, so you need to use Cronos kernel
Im trying to fix that broken loudspeaker bug.
Thanks for reporting

not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!

So7urno said:
not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!
Click to expand...
Click to collapse
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review

ichbinahmet said:
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review
Click to expand...
Click to collapse
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up

So7urno said:
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up
Click to expand...
Click to collapse
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again

ichbinahmet said:
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again
Click to expand...
Click to collapse
That fixed the problem! Thanks!
It seems I was using a wrong TWRP....
Most of the bugs I mentioned before are gone\fixed (loudspeaker, whatsapp keypad, sdcard).
except the video recording with the "opencamera" app (recorded videos are unplayable with messed up time lapse),
I tried also "HD camera" app from playstore with same problem.
But if I record video directly through whatsapp videos are ok.
Everything else seems working fine thought, stable and fast !
are you planning to work\fix the "(HW Keys (Use NavBar instead)" bug?
I Will keep using this rom for now, great job @ichbinahmet !