Database Info

[W.I.P] AOSP 7.1.1_r4 Nougat NMF26O [07.12.2016]

Builds of Android Nougat for our beloved Nexus 7 2013.
This is, again, a fork of @DevSwift1's original AOSP port (http://forum.xda-developers.com/nexus-7-2013/orig-development/p-aosp-n-7-0-google-shame-t3448008), for totally different reasons. This time because he is MIA and it would be a good idea to update with the October Security Update and beyond.
What works:
Audio
Brightness
GPU Acceleration
Bluetooth
Wifi
NFC
GPS
Location services
Camera and video recording
Video playback
MTP
Sensors
Bugs:
- Play TV and Movies DRM broken (Wildvine)
- poor 1080p video recording quality.
- Can't install Play Games (through Play. May work through opengapps aroma if you pick just that and what is in micro. Maybe one or 2 others) It can be sideloaded.
Change Log:
v0.10.0.1 (Flo only, not applicable to Deb)
- Fixed GPS.
v0.10 (0.8.9999 was "0.9")
- 7.1.1_r4, including December Security Patches (except items in the kernel)
v0.8.999
- Partial Nov Security Update. (Everything but the kernel)
v0.8.1
- Fix for CVEs: 2016-5195, 2016-5340, 2016-7117, 2016-3903, 2016-3934
- That should address all of applicable kernel patches from the Oct Security Update plus Dirty Cow.
v0.8
- Update to 7.1.0_r4 complete, and apparently fine. (well, as good as 07.2)
Download:
Flo: 0.10.0.1
Deb: 0.10.0
Old just in case, since 0.10 is a big jump:
Flo: 0.8.9999
Deb: 0.8.9999
Gapps: http://opengapps.org (micro version recommended)
If you have trouble installing Gapps, try rebooting (right back into recovery, not system) between flashing the ROM and Gapps.
Micro is a bit more than just recommended. It is the largest package that will fit in the system partition. This is basically a universal issue with Nougat that can't really be worked around without very risky tweaks to mess with the partition sizes which I'm not even sure are actually possible. (not happening)
You can install smaller packages, or "larger" using a custom config or the Aroma installer. And only slightly "larger" there. That is more useful to pick and choose to find a balance that works for you. You won't fit much more. (I do that on my Moto E which has the same issue.)
Sources: https://github.com/nbehary/manifest (the n-mr1 branch is 0.8. and master is basically untouched and still 0.7.2. I'll make master v0.8 later. )
Kernel Sources: https://github.com/nbehary/android_kernel_google_msm
Credit
@zaclimon
@DevSwift1

Two development things to mention:
- right now I'm forking as little of msm8960 as I needed to to apply the security patch. Only platform_frameworks_base and platform_system_core in my repos are current. (platform_build_core may or may not be, but it more or less is and doesn't matter for 99% of anything) I had forked them all before, but the rest aren't up to date. If you'd like to submit pull requests to help in any other repo, msg me first and I'll fork it first. (This will change over time. The manifest is the best guide for which I've updated. If I'm using mine there, it is current)
- I did ignore one of @DevSwift1's commits in system/core, since it was just pulling in my fork of it. No point, except to keep the history intact, but I was lazy. They were the same.
(ETA: oh, 3. The kernel sources are also up to date, and more current than the one in msm8960, even though the commits are backwards. He never merged the CVE patch. )

Is it possible to dirty flash over DevSwift1's version?

jerethi said:
Is it possible to dirty flash over DevSwift1's version?
Click to expand...
Click to collapse
Probably. Sorry, forgot to mention that in the OP.
I know that dirty flashing the test version I posted in the other thread a few days ago over that works, and this over the test does. So, it should work fine.

We don't have to flash gapps again if we are updating from .6 do we?
Sent from my Nexus 7 using XDA-Developers mobile app

gangrenius said:
We don't have to flash gapps again if we are updating from .6 do we?
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
You may. I always do, and didn't test without. My gut feeling is that you will need to. (I get mixed up though, the build I'm using on my Moto E always needs it, and I can't remember if here did too)

I know I don't when I flash an updated systemm of rr remix on my phone . hmmm guess we'll see
Sent from my Nexus 7 using XDA-Developers mobile app
---------- Post added at 06:01 AM ---------- Previous post was at 05:44 AM ----------
Can u add in that build prop edit they shared online into this so we can use google assistant?
Sent from my Nexus 7 using XDA-Developers mobile app

just in case i want to build using your trees and kernel sources, will it be a prebuilt kernel or from source?

simplyme2908 said:
just in case i want to build using your trees and kernel sources, will it be a prebuilt kernel or from source?
Click to expand...
Click to collapse
Prebuilt, but the one the manifest currently pulls, from my repos, is built from the sources posted here. It is entirely current. (despite the fact that I built it weeks ago.)

Is root lost after dirty flashing over 0.6?
Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.0) con Tapatalk 6

jerethi said:
Is it possible to dirty flash over DevSwift1's version?
Click to expand...
Click to collapse
nbehary said:
Probably. Sorry, forgot to mention that in the OP.
I know that dirty flashing the test version I posted in the other thread a few days ago over that works, and this over the test does. So, it should work fine.
Click to expand...
Click to collapse
For me, dirty flashing this over DevSwift1's version works.
Thanks for keeping this tablet updated!

Thanks for continuing to update this rom

miki67 said:
Is root lost after dirty flashing over 0.6?
Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.0) con Tapatalk 6
Click to expand...
Click to collapse
Yes, I have to root again.

With your build the video recording doesn't work at all in any camera app. See screenshot below of google camera
Please note I dirty flashed this on top of DevSwift1's version.

Has anyone installed EX on this? How does it perform?

@nbehary
What I've found not working so far
When I try to add my google account to Google Keep, the app force closes.
When trying to install Google Play Games from the Play Store I get the following error message (see image below).
Device is reported as Google Nexus 7 2012 model when logging in with your Google account.
Other than that ROM is stable and smooth! Love Android 7.0
Great work! :good:
Edit: Installed from scratch (clean install)

Does it matter which version I currently have ?
I'm doing this for the first time, using this tutorial - http://androiding.how/how-to-install-a-custom-rom-using-twrp-recovery/

I tried to install gapps together with ROM, but GAPPS shows: "Incompatible device detected"
I downloaded ARM64 GAPPS
ERROR:
Camera error: Can't connect to the camera.
And photo quality is also bad, very grainy..

rudolph323 said:
I tried to install gapps together with ROM, but GAPPS shows: "Incompatible device detected"
I downloaded ARM64 GAPPS
ERROR:
Camera error: Can't connect to the camera.
Click to expand...
Click to collapse
Don't use Arm64, Nexus 7 is 32-bit. So you want Opengapps 7.0 arm gapps
And yeah same camera issue, hopefully it gets fixed.
Otherwise good ROM.:good:

Is the webview patch applied?
http://opengapps.org/blog/post/2016/10/06/nougat-webview/

[ROM][surnia][unofficial][7.1.2] Lineage 14.1 ROM with VoLTE(DEPRECATED)

THIS ROM WILL NO LONGER BE UPDATED
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is this ROM about?
This ROM is based on LineageOS but with VoLTE support and some additional security features included. These builds include a lot of security and performance optimizations even for the models that doesn't have VoLTE.
Instructions:
Do NOT dirty flash over non-VoLTE CyanogenMod or LineageOS releases.
Which models support VoLTE?
VoLTE is supported on the models where the baseband firmware supports it. Some models are listed below.
XT1521: It will work for sure if your baseband is up-to-date with what moto released in 6.0.1
Other XT152x models: depends on your baseband
Note for XT1521: Your Baseband will only be up to date if you have been updated to or flashed stock 6.0.1 as released by moto at least once and never downgraded it. If you have downgraded, update your baseband file NON-HLOS.bin to the one from stock 6.0.1 . (follow instructions in other threads at your own risk.)
Note for CDMA users including XT1526 and XT1529 . There have been reported network switching issues. and I recommend CDMA users to avoid this ROM.
Where to get this ROM?
I continuously release updated builds on my github page https://github.com/vishnunaini/lineage-surnia-releases/releases
The latest Build:
2017-06-18 build
Links:
https://github.com/vishnunaini/lineage-surnia-releases/releases/tag/20170618
https://github.com/vishnunaini/line...neage-14.1-20170618-00-vishnunaini-surnia.zip
sha256: 3cde80009a026e03e742727790ebccce92a031efe279507f819aeaebefefb14d
I also GPG sign my releases you can get the detached signature on the release page below
for old releases see here https://github.com/vishnunaini/lineage-surnia-releases/releases
I will release new builds once every week or two.
Only tested on XT1521 .
BUGS:
No Major bugs or show stoppers.
Caveats:
Does NOT include root or debugging features for security reasons.
How to flash :
Download the linked zip.
If you are flashing this ROM for the first time Wipe system, dalvik, cache, userdata and data. All old data will be lost.
Flash the zip using twrp or cm recovery.
Flash your favourite Gapps. Opengapps is recommended. Get them at http://opengapps.org .
Do NOT dirty flash unless you are already using a VoLTE build. Otherwise you will see crashes.
Please use the recovery linked below if you want a tested one
Use this recovery if required: https://github.com/vishnunaini/line...oad/20161229/recommended-recovery-cm-13.0.img
Contributors:
CyanogenMod/LineageOS maintainers and contributors.
Bug reporting:
Report any build specific bugs here https://github.com/vishnunaini/lineage-surnia-releases/issues
Versions:
Android 7.1.2
LineageOS 14.1
Kernel 3.10.x with latest security updates
SELinux: Enforcing
Root: NO
If you use gapps, Always flash gapps immediately after flashing an update or else gapps wont be preserved.
Source Code:
Core: https://github.com/LineageOS
Kernel: https://github.com/vishnunaini/android_kernel_motorola_msm8916 (see branch cm-14.1-custom)
Device changes: https://github.com/vishnunaini/android_device_motorola_msm8916-common (see branch cm-14.1-custom for new volte code that syncs with upstream. see cm-14.1-volte for old code) https://github.com/vishnunaini/android_device_motorola_surnia

Cool.. Btw is there any difference between this and Seraph08's cm14.1 build except the ROM name?

Can we flash using twrp...
N what gapps are recommended..
Sent from my XT1521 using XDA Labs

You can use twrp
use opengapps for android 7.1
enter.hk said:
Can we flash using twrp...
N what gapps are recommended..
Sent from my XT1521 using XDA Labs
Click to expand...
Click to collapse

This build includes latest security updates right down to today and some additional security hardening.
I do not know about Seraph08's build but I will describe what is in my build
cm-14.1 latest
+ VoLTE
+ YAMA LSM security module(helps chrome/chromium sandboxing)
+ PXN no-execute on user_page_table
+ latest upstream security updates till 20161229
+ disable ICMP timestamps for security
+ disable ICMP pings echoes
rushabshah32 said:
Cool.. Btw is there any difference between this and Seraph08's cm14.1 build except the ROM name?
Click to expand...
Click to collapse

Going to attempt this on a 1527. Will report back when flashed....
Update... Everything works perfect on xt1527 on boost mobile, and using fire kernel. LTE works, and have not seen any camera issues.

Did you try the kernel in this ROM? Did you flash fire kernel during the ROM flash itself?
drsemaj87 said:
Going to attempt this on a 1527. Will report back when flashed....
Update... Everything works perfect on xt1527 on boost mobile, and using fire kernel. LTE works, and have not seen any camera issues.
Click to expand...
Click to collapse

vnai said:
Did you try the kernel in this ROM? Did you flash fire kernel during the ROM flash itself?
Click to expand...
Click to collapse
No, I was going to try and run with your kernel, but forgot about it and flashed fire kernel along side the ROM. I can go back and flash the stock kernel and report back...
Update.. Flashed your stock kernel, camera fails to connect. Can't get it to even try. Everything else seems OK.
Another update, don't know if it's important. I'm running a xt1526, not a 1527. Oops.

The performance is good but there is a slight delay in opening background apps which is noticeable. All in all though the rom is stable.
Pair it with pixel mod and firekernel makes it a beast and VOLTE works too.

drsemaj87 said:
No, I was going to try and run with your kernel, but forgot about it and flashed fire kernel along side the ROM. I can go back and flash the stock kernel and report back...
Update.. Flashed your stock kernel, camera fails to connect. Can't get it to even try. Everything else seems OK.
Another update, don't know if it's important. I'm running a xt1526, not a 1527. Oops.
Click to expand...
Click to collapse
VOLTE works on xt1526 ??
Hit THANKS if somebody help you

ROM doesn't flash using TWRP 3.0.2-r1 on XT1521 it just stopped at about 45% & never crossed that

sonnu0100 said:
VOLTE works on xt1526 ??
Hit THANKS if somebody help you
Click to expand...
Click to collapse
I have no idea. I'm on boost mobile, which I don't think supports Volte. How do I find out if it works?
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
Sher1234 said:
ROM doesn't flash using TWRP 3.0.2-r1 on XT1521 it just stopped at about 45% & never crossed that
Click to expand...
Click to collapse
I believe the latest is r5, which is what I have. Try updating twrp.
Side note.. I think Bluetooth might be broken. It connects OK, but once I start music it locks up my stereo. I'll try with your kernel later, and if still have issues, I'll supply logs.
Edit. Bluetooth OK. Stereo was just frozen from cold weather.

Camera bug looks like a bug in the kernel.

I will fix my kernel and make a new release soon
drsemaj87 said:
No, I was going to try and run with your kernel, but forgot about it and flashed fire kernel along side the ROM. I can go back and flash the stock kernel and report back...
Update.. Flashed your stock kernel, camera fails to connect. Can't get it to even try. Everything else seems OK.
Another update, don't know if it's important. I'm running a xt1526, not a 1527. Oops.
Click to expand...
Click to collapse

Prefer cm-13 recovery instead. although it worked fine with twrp in my test.
Sher1234 said:
ROM doesn't flash using TWRP 3.0.2-r1 on XT1521 it just stopped at about 45% & never crossed that
Click to expand...
Click to collapse

vnai said:
Prefer cm-13 recovery instead. although it worked fine with twrp in my test.
Click to expand...
Click to collapse
I tried TWRP 3.0.2-r2 & r5 but still the same result

Try cm-13 recovery linked here https://github.com/vishnunaini/line...oad/20161229/recommended-recovery-cm-13.0.img
Sher1234 said:
I tried TWRP 3.0.2-r2 & r5 but still the same result
Click to expand...
Click to collapse

sonnu0100 said:
VOLTE works on xt1526 ??
Hit THANKS if somebody help you
Click to expand...
Click to collapse
Volte does not work on 1526 as boost mobile/ sprint does not support it.

vnai said:
Try cm-13 recovery linked here https://github.com/vishnunaini/line...oad/20161229/recommended-recovery-cm-13.0.img
Click to expand...
Click to collapse
It worked
Now on lineage 14.1 with Everything working fine except camera

drsemaj87 said:
I have no idea. I'm on boost mobile, which I don't think supports Volte. How do I find out if it works?
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
I believe the latest is r5, which is what I have. Try updating twrp.
Side note.. I think Bluetooth might be broken. It connects OK, but once I start music it locks up my stereo. I'll try with your kernel later, and if still have issues, I'll supply logs.
Edit. Bluetooth OK. Stereo was just frozen from cold weather.
Click to expand...
Click to collapse
drsemaj87 said:
Volte does not work on 1526 as boost mobile/ sprint does not support it.
Click to expand...
Click to collapse
I am using this model on a LTE only network . Tried cm14.1 but it was not able to connect call.
I think that for volte support it has to be enabled in firmware ( only asain varaint xt1521 supports volte out of box and supports on custom ron like cm14.1 and lineage os ) . If developer find a way to enable thia on these surnia models then it will be like a new suprise . Still waiting
Hit THANKS if somebody help you

[KERNEL][OP3 & OP3T] FrancoKernel - 27th Aug - r50 - OOS & custom roms

Hi all.
Compatibility:
Builds starting with r33 are compatible with OxygenOS Android Oreo 8.0.0.
Builds starting with r39 up to r44 are for Android Oreo 8.1.0 LineageOS 15.1 and custom roms built from it.
Builds starting with r45 are also compatible with Android Pie custom roms. Tried and tested with LineageOS 16.0.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from Franco Kernel Updater app
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/one_plus_3T
Follow me on socials for updates and interesting tidbits
Twitter
FK Kernel Manager video
https://www.youtube.com/watch?v=ARdNqh71D0E
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!

Unified both devices on this thread. Both original threads on their respective forums have been closed and users notified of it.

And r45 has been pushed for the stock OxygenOS and Pie custom roms. Visit https://francokernel.app to get r45.

Yaaaas
Sent from my OnePlus 3 using XDA Labs

Omg, thanks, your kernel is simply AMAZING.
Thanks for update
---------- Post added at 10:33 PM ---------- Previous post was at 10:09 PM ----------
franciscofranco said:
And r45 has been pushed for the stock OxygenOS and Pie custom roms. Visit https://francokernel.app to get r45.
Click to expand...
Click to collapse
Hi Franco, don't know if it related to kernel, but I can't see YouTube videos, I can hear the audio but no video. I'm on r45 oos 5.0.8
Thanks
Edit: I can't see any video, from any app, only audio.

I have the same problem. I can hear video on YouTube but I can't see. OOS 5.0.8. Latest kernel r45
Also I notice when I select first time video the screen is black with voice, when I rotate my phone and select a video from the bar on the bottom of the screen then I can see and hear the new video
Sent from my OnePlus 3T using XDA Labs

I have the video issue too on R45, was OK on R43. (r44 had wifi issues) OOS 5.0.8 OnePlus 3
Sent from my ONEPLUS A3003 using Tapatalk

spetrie said:
I have the video issue too on R45, was OK on R43. (r44 had wifi issues) OOS 5.0.8 OnePlus 3
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
xarrismoto said:
I have the same problem. I can hear video on YouTube but I can't see. OOS 5.0.8. Latest kernel r45
Also I notice when I select first time video the screen is black with voice, when I rotate my phone and select a video from the bar on the bottom of the screen then I can see and hear the new video
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
spione2013 said:
Omg, thanks, your kernel is simply AMAZING.
Thanks for update
---------- Post added at 10:33 PM ---------- Previous post was at 10:09 PM ----------
Hi Franco, don't know if it related to kernel, but I can't see YouTube videos, I can hear the audio but no video. I'm on r45 oos 5.0.8
Thanks
Edit: I can't see any video, from any app, only audio.
Click to expand...
Click to collapse
Video works just fine here, latest r45 on Havoc-OS Pie 9.0 AOSP based.
Everything works fine and smooth so far ?

nexus_vl said:
Video works just fine here, latest r45 on Havoc-OS Pie 9.0 AOSP based.
Everything works fine and smooth so far ?
Click to expand...
Click to collapse
Same on skydragon
Sent from my OnePlus 3 using XDA Labs

So I guess only on oxygen there is the problem
Sent from my OnePlus 3T using XDA Labs

xarrismoto said:
So I guess only on oxygen there is the problem
Click to expand...
Click to collapse
I guess so too, i'm experiencing this issue as well
Hope logs can help ?

Just re-uploaded r45 for stock, video playing is fixed. Apologies.

Is there anyone with 3rd Party Display panels running the Pie version of this Franco kernel on a custom ROM and having no problem with Screen wake-up?
I haven't given a try by myself. Since I Have locked my bootloader. But wanted to know if the problem related to Screen-Wakeup has been solved or not.
(OOS version of this kernel doesn't had this problem earlier) (haven't tried latest version).
Thank you!

Ok i flashed the fixed r45 and now all seems to work good (oos 5.0.8) :fingers-crossed:

Hi! How It works with pixel experience rom 9.0? Thanks!

OOS 5.0.8, all great here too
Sent from my OnePlus 3T using XDA Labs

@franciscofranco
Since kernel update on r45 m wifi isn't working at all. R43 worked fine, r44 had some connection issue but they solved after some reflashes.
Now on r45 my wifi won't activate over the tiles and in the settings menu it won't scan for networks. Already cleared cache and dalvik, flashed ROM and kernel again but it won't help
Edit: OP3 with latest oxygen

Tension1312 said:
@franciscofranco
Since kernel update on r45 m wifi isn't working at all. R43 worked fine, r44 had some connection issue but they solved after some reflashes.
Now on r45 my wifi won't activate over the tiles and in the settings menu it won't scan for networks. Already cleared cache and dalvik, flashed ROM and kernel again but it won't help
Edit: OP3 with latest oxygen
Click to expand...
Click to collapse
Well when I return to stock kernel with my boot image I had the same problem. No wifi. So I reflash the rom again with clear cache and the magisk again and the problem solved. Today I flash the new edition o f the kernel r45 and works flawless!
Sent from my OnePlus 3T using XDA Labs

Can someone report battery stats on this kernel?

AnnoyingZlatan said:
Can someone report battery stats on this kernel?
Click to expand...
Click to collapse
Usage varies, try for yourself

[ROM] [Unofficial LineageOS 16] [9.0] [OPPO R7f]

EXPERIMENTAL BUILD
First off this wouldn't be possible without mikeNG, TheMuppets, LineageOS team
I'm just the cook
Devices supported: R7f, ONLY
Do not flash this rom on any other R7 variants. It will brick the device
What works:
Unknown
Haven't tested it fully. All basic functions seem to be in working order.
Will update 'What works / doesn't ' later on.
What doesn't:
Camera issue - Sometimes the camera's color appears to be inverted. Switch HDR on/off fixes it.
Installation notes
Clean install required!
Perform a full wipe when coming from 14.1/15.1
Downloads:
LineageOS 16.0 for Oppo R7f
[Gapps -> ARM ->9.0]
*Don't use the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.1-0 or higher)
Be aware. It's a initial release. Do not expect everything to be working flawlessly. Do make a full backup prior of installing
If you're not fully comfortable/sure about installing an Experimental release than please don't. I'm not responsible for any harm done

**Reserved**
Temp: Please do report any device specific issues

Very good. I will try los16 soon

Holy **** you guys are amazing! After all this time you're still making updates for the Oppo R7 series! Really impressed.
I have an Oppo R7 Plus myself. Any word on if that'll be supported some time as well?

I've tried los 16.0
no meaningful bugs.
overall, I like it very much.
work
1. Cas vooc works
2. Dt2w works
3. The battery saving display is not red
4. Wifi, hotspots work
5. The cellular network feels more stable
Not work
1. Bluetooth sometimes doesn't work
2. Showing download and upload speeds do not work
3. The camera sometimes errors if hdr is on
The rest is quite satisfied with the performance of los 16.0. if there is less and more it will be notified later.
Cmiiw
Thank you very much

Hello I am just a cook as well (just a diff one) but here is an update!
md5sum: https://drive.google.com/open?id=1x1UVAq7mPKUud9iGis4Nyo4o_5x0UBuT
zip: https://drive.google.com/open?id=1jcR2kkAHBewxSdsqs2YNZTaW-RCqITGS
rmb to update if any device-speicific bugs appear

ph03nae said:
Hello I am just a cook as well (just a diff one) but here is an update!
md5sum: https://drive.google.com/open?id=1x1UVAq7mPKUud9iGis4Nyo4o_5x0UBuT
zip: https://drive.google.com/open?id=1jcR2kkAHBewxSdsqs2YNZTaW-RCqITGS
rmb to update if any device-speicific bugs appear
Click to expand...
Click to collapse
if it's more stable. I will try as soon as possible. thank you

ph03nae said:
Hello I am just a cook as well (just a diff one) but here is an update!
md5sum: https://drive.google.com/open?id=1x1UVAq7mPKUud9iGis4Nyo4o_5x0UBuT
zip: https://drive.google.com/open?id=1jcR2kkAHBewxSdsqs2YNZTaW-RCqITGS
rmb to update if any device-speicific bugs appear
Click to expand...
Click to collapse
I've tried your update. everything went smoothly. haven't found a bug. only internet speed can be moved from center to right ??

@ph03nae,
Great to see that you also cooked a v9.0! Do I understand correctly that everything works in your version, including bluetooth and the camera?

eximiusnl said:
@ph03nae,
Great to see that you also cooked a v9.0! Do I understand correctly that everything works in your version, including bluetooth and the camera?
Click to expand...
Click to collapse
I've tried it and used it until now. the camera and bluetooth are running well. haven't found a bug.

That's great!
Here's another update!
md5sum: https://drive.google.com/open?id=1avYrsAHwaNnl2ZJQeiKXf1WU1IHUyYud
zip: https://drive.google.com/open?id=1ohuu8j-zSuvcW7w8CZaIBGx0NPQ0e1Ux

Hi ppl, here's another update!
zip: https://drive.google.com/open?id=1I3nvdnSHWaiYnLlOfAOD_7biEbBBOVEr
md5sum: https://drive.google.com/open?id=13i3E3holmHzN4bJLvwmZDYFktrwiVVo2
enjoy

MAC addresse wrong
Thank you very much!
Yesterday I tried this ROM. Unfortunately, my device's MAC address was always rusty. 02: 00: 00: 00: 00:00. I did it with the latest TWRP program but I also tried the 3.2.1 recommended by you. If the original ColorOs returned, it was good again. I've always done a full wipe. What can I do wrong?

@ph03nae,
Thanks for the update!
What version of GApps do you use? I used the full version before, but since the LineageOS 16 release is bigger, I wonder whether it will fit.

eximiusnl said:
@ph03nae,
Thanks for the update!
What version of GApps do you use? I used the full version before, but since the LineageOS 16 release is bigger, I wonder whether it will fit.
Click to expand...
Click to collapse
For lineageOS 16, I have been using the mini version of GApps instead of the full version because an error sometimes occur saying that there is not enough space for the GApps full version installation. Hope this helps!

@ph03nae,
I followed your advice and also used the mini version of the GApps and installation went flawless.
I noticed that the Pixel Launcher does not work, so you have to use Trebuchet.
I also noticed that battery life is way better than with Android 8.1 !
Thanks for your work, the phone really works fine again.

Could someone please advise me how I can tell if I have an OPPO rplusf or an OPPO rplusg. I live in Australia. Thanks in advance

eximiusnl said:
@ph03nae,
I followed your advice and also used the mini version of the GApps and installation went flawless.
I noticed that the Pixel Launcher does not work, so you have to use Trebuchet.
I also noticed that battery life is way better than with Android 8.1 !
Thanks for your work, the phone really works fine again.
Click to expand...
Click to collapse
You're welcome! (But just to give credit to those who actually work on the code see https://github.com/LineageOS?utf8=✓&q=oppo&type=&language= )
Also, for the issue regarding Pixel Launcher, this is a fix I used (https://forum.xda-developers.com/android/apps-games/pie-pixel-stuff-t3846138) After flashing both zips according to the given instructions, the pixel launcher app can also be updated separately using .apk files.
---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------
mvjh01 said:
Could someone please advise me how I can tell if I have an OPPO rplusf or an OPPO rplusg. I live in Australia. Thanks in advance
Click to expand...
Click to collapse
Hi, you should be able to access this information by going into settings --> about and find a field for the device ID (or something similar) if you are on the stock rom.

ph03nae said:
You're welcome! (But just to give credit to those who actually work on the code see https://github.com/LineageOS?utf8=✓&q=oppo&type=&language= )
Also, for the issue regarding Pixel Launcher, this is a fix I used (https://forum.xda-developers.com/android/apps-games/pie-pixel-stuff-t3846138) After flashing both zips according to the given instructions, the pixel launcher app can also be updated separately using .apk files.
---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------
Hi, you should be able to access this information by going into settings --> about and find a field for the device ID (or something similar) if you are on the stock rom.
Click to expand...
Click to collapse
Thanks very much for your help but I have no such field or anything similar plus I had already looked through all 'about phone' settings. I've just tried installing this ROM via the instructions but Project Spectrum fails every time

mvjh01 said:
Thanks very much for your help but I have no such field or anything similar plus I had already looked through all 'about phone' settings. I've just tried installing this ROM via the instructions but Project Spectrum fails every time
Click to expand...
Click to collapse
Correct me if im wrong but I think only the oppo r7g version has Project Spectrum available.

[ROM][Unofficial][9.0.0_r46/Pie][X/X Dualsim/X Compact/Touch] AOSP9 - 20200206 builds

Please see this post in Xperia X forum and thread about AOSP9 builds for all Loire device, including Xperia X Compact / F5321

Thank you for the info, I will try it

Insane, thank you!!!

Fantastic news. Been waiting patiently for an update the past couple months. Just flashed this and it's working very smoothly, stable and no battery drain so far. Thanks for sharing!

20200307 build: 4.9.214 and 4.9.215 kernel updates
AOSP-9-F5321-20200307-4.9.214brcmfmac.zip
An updated clean build with 4.9.214 kernel (boot.img), and proposed 4.9.215 update (boot-4.9.215.img).
Please test 4.9.215 in priority, and in case of problem fallback to 4.9.214.
Both kernels have proposed wifi/brcmfmac update.
Not sure if flashing only the boot img over previous build will work: in case it doesn't, please do a complete/clean flash...

Is there anyhow fast charge available?

Hi everyone,
I am currently using AOSP 9.0-r46 with the 4.9.213 kernel. I compiled the image by myself following the build instructions provided by sony, so my problem meight not be reletated to the build of vknecht. Anyways, I have problems with the camera. No matter what app I am using (OpenCamera, AOSP-Camera or PhotoDirector) the auto focus fails to focus far away objects under bad light conditions. Objects near by can be focused without any problems. Also the focus of an landscape fails when it gets to dark.
I guess this is related to the proximity sensor, since the focus always fails if I cover it.
Does anyone have experienced the same problem or can reproduce it?

20200422 build: 4.9.219 kernel update
Posted updated build in Xperia X forum

vknecht said:
Posted updated build in Xperia X forum
Click to expand...
Click to collapse
Great job thanks for the update :victory:
---------- Post added at 11:52 AM ---------- Previous post was at 11:50 AM ----------
legenbaer said:
Hi everyone,
I am currently using AOSP 9.0-r46 with the 4.9.213 kernel. I compiled the image by myself following the build instructions provided by sony, so my problem meight not be reletated to the build of vknecht. Anyways, I have problems with the camera. No matter what app I am using (OpenCamera, AOSP-Camera or PhotoDirector) the auto focus fails to focus far away objects under bad light conditions. Objects near by can be focused without any problems. Also the focus of an landscape fails when it gets to dark.
I guess this is related to the proximity sensor, since the focus always fails if I cover it.
Does anyone have experienced the same problem or can reproduce it?
Click to expand...
Click to collapse
I haven't come across this issue before. Are you only experiencing it with AOSP? Is your phone case or rear cover perhaps blocking the sensor in any way?

20201003 update : new boot.img with kernel 4.9.230
Updated the release post with links to new boot.img including 4.9.230 kernel.

AOSP10 build with gapps
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...

vknecht said:
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
Click to expand...
Click to collapse
I will try it soon.

vknecht said:
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
Click to expand...
Click to collapse
Excited to try this and thanks for still supporting kugo! I still use it as my primary device, running minextu's AOSP 10 (May security patch) but will flash yours too so see how it compares.

vknecht said:
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
Click to expand...
Click to collapse
Thank you for my XC, will wait for non gapps build for testing.

I'll also wait for non gapps version. By the way I suppose you build with the kernel version which reduces reboots.
Enviado desde mi Xperia X Compact mediante Tapatalk

evilorb said:
Thank you for my XC, will wait for non gapps build for testing.
Click to expand...
Click to collapse
maluus said:
I'll also wait for non gapps version. By the way I suppose you build with the kernel version which reduces reboots.
Click to expand...
Click to collapse
Indeed, these builds are with latest-best-known-as-of-yet kernel (seen as 4.9.230 version)...
Here you go for non-gapps F5321 build :
e46ecc1d097b3c3645954b5d83d03f0e AOSP-10-F5321-20201101-4.9.230.zip

vknecht said:
Indeed, these builds are with latest-best-known-as-of-yet kernel (seen as 4.9.230 version)...
Here you go for non-gapps F5321 build :
e46ecc1d097b3c3645954b5d83d03f0e AOSP-10-F5321-20201101-4.9.230.zip
Click to expand...
Click to collapse
Just flashed this and so far so good! If you accept PP donations let us know. Thanks again!

wi-fi hotspot doesn't work. it turns off itself a few seconds after turning off. is this a known issue? Also bluetooh has a problem I guess. couldn't connect with pc. pairing is succesfull but when you try to connect. goes to pairing screen again. it seems good other than that. no battery drain so far.

Hey yes this is a known issue. Might be related to the kernel not sure. The previous aosp 10 from minextu has the same problem.