Develop Bugs

[ROM] [5.1.x] [BETA] Unofficial CyanogenMod 12.1 Nightly Builds (KIW-L24 / L22 / L21)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
* See the next post.
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), use adb or any other rile explorer tool to pull a copy of
/sys/fs/postore/console-ramoops
after the reboot and provide that.
Download Links
CyanogenMod: ROM @ http://download.crpalmer.org/nightlies/kiwi-cm-12.1
Google apps addon:
I am using open GApps arm64 version.
XDA:DevDB Information
CyanogenMod 12.1 Builds, ROM for the Honor 5X
Contributors
crpalmer, crpalmer
Source Code: https://github.com/CyanogenMod/android_kernel_huawei_kiwi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 2.20.40.16x stock base
Version Information
Status: Beta
Created 2016-03-18
Last Updated 2016-03-22

Reserved
Issues:
all cores are online all the time
call recording
fingerprint sensor
flip cover / smart view case support
fm radio
other gestures (I don't even know what they are because I didn't run stock long enough to find out so if you want support tell me)
selinux is in permissive mode
With the gapps that I'm using there is also an issue with the play store app which will fail to install certain apps if you have a sdcard mounted. The workaround is to go to Settings >> Storage and unmount the sdcard and then install the app. I currently believe that this is a lingering gapps problem.
[*] These features I am not planning to implement them in 12.1 because the time to do so would be very high and they have changed entirely in 13. Hopefully the fingerprint sensor will be easy in 13 after Huawei releases the M build.

L22
Can install on L22 device?

Elmerdus said:
Can install on L22 device?
Click to expand...
Click to collapse
Not yet.
I think I just have to change the installer script to allow you to install it but at an ALPHA stage, I don't want to have added confusion of multiple devices. Once it gets more stable and more people independently figure out to change the installer script and report that it works, I'll feel more confident making the change to allow it...

Great job so far, especially figuring out the rear cam
The gapps I've been using on my test builds that seem to work is gapps-5.1.x-20150404-minimal-edition-signed.zip located here: https://www.androidfilehost.com/?fid=95916177934550851
On a side note, your source code is linked to asus moorfield kernel...is that a typo? - EDIT, I see it's changed
Again, great job!

hondajohn88 said:
Great job so far, especially figuring out the rear cam
The gapps I've been using on my test builds that seem to work is gapps-5.1.x-20150404-minimal-edition-signed.zip located here: https://www.androidfilehost.com/?fid=95916177934550851
On a side note, your source code is linked to asus moorfield kernel...is that a typo?
Again, great job!
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Great job so far, especially figuring out the rear cam
The gapps I've been using on my test builds that seem to work is gapps-5.1.x-20150404-minimal-edition-signed.zip located here: https://www.androidfilehost.com/?fid=95916177934550851
On a side note, your source code is linked to asus moorfield kernel...is that a typo?
Again, great job!
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Great job so far, especially figuring out the rear cam
The gapps I've been using on my test builds that seem to work is gapps-5.1.x-20150404-minimal-edition-signed.zip located here: https://www.androidfilehost.com/?fid=95916177934550851
On a side note, your source code is linked to asus moorfield kernel...is that a typo?
Again, great job!
Click to expand...
Click to collapse
Updated the "source code" link (I forgot about that field xda makes you fill in when I cloning another device to help me create the thread).
Speaking of the kernel, we are definitely having some serious slow downs because the source code that was officially released doesn't seem to actually match the software that was released but wimberly (is that @wimberly6, I'm not sure?) has been helping to try to get the right source released. Kudos to him for that.

crpalmer said:
Updated the "source code" link (I forgot about that field xda makes you fill in when I cloning another device to help me create the thread).
Speaking of the kernel, we are definitely having some serious slow downs because the source code that was officially released doesn't seem to actually match the software that was released but wimberly (is that @wimberly6, I'm not sure?) has been helping to try to get the right source released. Kudos to him for that.
Click to expand...
Click to collapse
Maybe @wimbet?

Omg , thanks a lot am the luckiest person . truely its a long wait thanks a lot really .gonna flash
---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------
crpalmer said:
Not yet.
I think I just have to change the installer script to allow you to install it but at an ALPHA stage, I don't want to have added confusion of multiple devices. Once it gets more stable and more people independently figure out to change the installer script and report that it works, I'll feel more confident making the change to allow it...
Click to expand...
Click to collapse
Am an L22 user. Am using previous build with camera bugs .
And I will change installer to workout and let you know .
Thanks for your build .

Thanks a lot for this guys! I'm so impressed. Do you guys know if fingerprint works on this or will in the future? Keep up the great work, I am loving this so far.

Excited about this. Thanks for the hard work. Looking forward to try it if you get the encryption support worked out (I use a work app that is fine with root, but requires encryption).

Thank you. Will try when it is stable!

I am very glad to see CM build. Great Job guys.
will install on my L-22 with stable build. till then waiting............

@crpalmer , @hondajohn88 , bro's .
ROM is quite cool on my L22 .
Found no bugs .
fingerprint not implemented yet but no worries .
Thanks again the ROM is super smooth and battery backup is decent so far .

Wow! This great news, thanks for all the hard work, really appreciate this! I am an L-22 user and will wait for a "proper" release since this is my only phone right now, but kudos on bringing this to us in such a short span of time!

L22
gopinaidu77 said:
@crpalmer , @hondajohn88 , bro's .
ROM is quite cool on my L22 .
Found no bugs .
fingerprint not implemented yet but no worries .
Thanks again the ROM is super smooth and battery backup is decent so far .
Click to expand...
Click to collapse
Oh you install on L22 work???
(Sory for my english)

tamcdonald said:
Thanks a lot for this guys! I'm so impressed. Do you guys know if fingerprint works on this or will in the future? Keep up the great work, I am loving this so far.
Click to expand...
Click to collapse
Oops, I forgot that on my list of issues. Short answer: no and it won't in 12.1. See the second post for a longer answer.

Wow this ROM is freakin smooth..great job crpalmer this forum appreciates what you do. Most normal daily things work on this phone just can't use fingerprint but man it's a big difference in speed with this rom
Sent from my KIW-L24 using Tapatalk

Any ETA on l21 edition?

crpalmer said:
Oops, I forgot that on my list of issues. Short answer: no and it won't in 12.1. See the second post for a longer answer.
Click to expand...
Click to collapse
well now i have a reason to root my phone. And its like now the party starts.... closely monitoring the thread now on. Thank you for your valuable time for giving this sweet pie

gopinaidu77 said:
@crpalmer , @hondajohn88 , bro's .
ROM is quite cool on my L22 .
Found no bugs .
fingerprint not implemented yet but no worries .
Thanks again the ROM is super smooth and battery backup is decent so far .
Click to expand...
Click to collapse
This one is all @crpalmer, likely with help from @ciwrl, @deadman96385 &@inkslinger. I did not contribute to this.
I'm looking into getting the fingerprint scanner working, but with my limited skills & possible missing stuff in the kernel source, the excellent devs working on this ROM will most likely figure it out long before I can.
This is a great ROM for an alpha. It is indeed smooth

[Testing]Cyanogenmod 13 - Unofficial

Hey guys,
I've just managed to make a build of Cyanogenmod with lots of help by a guy called sultanqasim (actually he did most of the work), thanks a lot bro
Probably it's very bugy. Let's call it Pre-Alpha. Anyway, the build is ready and I need guys who'd like to try it out.
I chase GDrive for the first CM build. All Beanstalk builds are uploaded to the official Beanstalk AFH.
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
NFC
Broken:
Audio through built in speakers or headphones
RIL
Camera
Mic
Various other smaller things
Some Sprint users also report that it doesn't work for them. Just try it out if you like. Every tester's report takes the project a bit closer to stable builds.
Download Cyanogenmod (GDrive)
Download Beanstalk (AndroidFilehost)
To flash it:
in TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
in TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
flash the file by pushing it to your sdcard or you can use adb sideload. Also you can flash GApps optionally.
reboot into the system
Looking forward to your reviews. Thanks a lot
Good luck to all of you
Remember: I'm not responsible for anything that could happen as a result of following my instructions or anything else.
XDA:DevDB Information
[Testing][ROM] Cyanogenmod 13 - Unofficial, ROM for the HTC 10
Contributors
krassermensch, sultanqasim
Source Code: https://github.com/sultanqasim
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2016-06-10
Last Updated 2016-07-13
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!

Nice!

Moderator Information,
Thread re-opened to allow OP to upload file on XDA host.

Can't wait for CM13 on this phone. I know Squid2 has been a ton of work into this, from what I know, already a solid month behind the scenes.

device boots up? display?

thought this thread was closed till a download link was posted...
i don't seem to find any link or me gone blind lolll
edit:- just read that its opened for uploading the link so it seems upload is in progress

Maybe change the title with correct spelling of " Unofficial "

We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?

psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
i guess we would need to wait for the upload to be finished to see if its any different or the same as the Op doesn't seem to be much of responding to any comments

@krassermensch - Can you give us a list of what is and isn't working in your experience, at least?

psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.

krassermensch said:
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
Click to expand...
Click to collapse
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?

psych0r3bel said:
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
Click to expand...
Click to collapse
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon

I'm really glad to see this coming along! Keep up the good work. I'm not much of a tester normally but I think Im going to give it a shot later tonight and let you know what issues I can find.

krassermensch said:
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
Click to expand...
Click to collapse
So glad to see the credits given, and insight to what testers will find.
Didn't want to see any drama, I thanks for putting the time in and squid for laying these ground work!
Sent from my HTC 10 using XDA-Developers mobile app

@krassermensch, thanks for your efforts but... If you're going to publish his work, how about updating the OP with his bug list and the title with pre-alpha. Just so users have more information, instead of the vague "it might be buggy". We know its buggy. Specifics about what works and doesn't is what people would like to know.
This still accurate?
squid2 said:
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
Click to expand...
Click to collapse

Moderator Information,
Thread has been moved to general, as the OP is only hosting the work for another user.

Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.

matteosaeed said:
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
Click to expand...
Click to collapse
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.

rav101 said:
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
Click to expand...
Click to collapse
Sweet. I can test more at nights when I am at home. Doing the nanodroid now of this build.
---------- Post added at 09:17 PM ---------- Previous post was at 08:52 PM ----------
question, I am trying to go back but I am getting the failed to mount '/system' (invalid argument), any tips on how to bypass that?

[KERNEL] Lucky [O]

Lucky-Kernel​For​Exynos-Variant's​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* 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.
* If you dont like this Kernel, Stay away from this thread!
*/
What to say... I come from Samsung Galaxy Nexus and its development until the beginning of September 2016...
I did a one-year break from kernel programming, and I came back here for you. To bring you a good kernel for this device that still has a lot to give.
My work is on kernel source, I add, delete, modifing code, but with a criterion, that everything, must make sense
I consider the kernel as beta, although it is very stable, I will update the kernel when needed, with the necessary security patches, and a few extra grays
Android8.0
This kernel Boot on 8.0(lineage-buid) but I think also on AOSPExtended rom 8.0 it will Boot..
Android7.1
EDIT: Don't Boot.. thank's to @spookcity138 for news
Good download at all, and let me know your opinion
XDA:DevDB Information
[KERNEL] Lucky [O], Kernel for the Samsung Galaxy S5 Mini
Contributors
Fenix46, hennymcc, spookcity138
Source Code: https://github.com/Fenix46/android_kernel_samsung_kminilte
Kernel Special Features:
Version Information
Status: Beta
Beta Release Date: 2017-11-11
Created 2017-11-11
Last Updated 2017-11-12

Reserved

Del.

Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards

Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.

tester02 said:
Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards
Click to expand...
Click to collapse
Yep, with official twpr, flash without problem, this error 11 is related to the twpr for Oreo... however, I've add some commit on kernel source, and my work is this, add commit, and update the kernel

spookcity138 said:
Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.
Click to expand...
Click to collapse
@spookcity138 thank's for welcome However Thannk's again for feed on 7.x rom... this error is related at updater-script.. on Oreo the first line "assert" is not present, so cause this.. but with official twpr flash go fine, I think to change the updater-script if cause another problem

I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.

CHEF-KOCH said:
I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.
Click to expand...
Click to collapse
what changes did you want to find on the kernel? did you see the commit series I added? Do you think the changes are all in the name of who works on the kernel? for those who work on ROMs as @hennymcc or @spookcity138 or other's they can very well take my base and insert it to build the ROM..

I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.

CHEF-KOCH said:
I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.
Click to expand...
Click to collapse
What you saw, that you think is old, are needed on Nougat as well, because interfaces better the kernel, with the modules, because our kernel don't have support on kernel Device Three.. and it's just the beginning of this, because my main job will be to reformulate the theard for a rom. Nothing to take away from the kernel LOS, and I did not want to create useless controversies. if you do not want to use this kernel, it does not change anything. however if you look good on the download section, find the zip package to download.

Twrp 3.1.1 official, SM-G800F, AospExtended Oreo. Error 11 by flashing.

Where is the Download Link?

Open xda in Browser, under downloads
(look at the middle of my Screenshot)

MikeT. said:
Open xda in Browser, under downloads
(look at the middle of my Screenshot)
Click to expand...
Click to collapse
Thanks

. . .

[ROM][11.0] Yet another AOSP project [OP5/5T][ALPHA][26-10-2020]

Who are we?​YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Bug reporting:​
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Downloads​
Downloads
cheeseburger (OP5) : https://drive.google.com/file/d/11S4K-_SGOJLyHFd9hX_P_Uj_2Ai4wzQL/view?usp=sharing | https://yaap.angerycat.tk/YAAP-11-Alpha-yaap_cheeseburger-20201025.zip
dumpling (OP5t) : https://drive.google.com/file/d/1B4JIzRcl3iLmq7imzYvhrNQ3ESjfRe8U/view?usp=sharing| https://yaap.angerycat.tk/YAAP-11-Alpha-yaap_dumpling-20201025.zip
Flashing Procedure​Install TWRP (Latest codeworkx is recommended)
Coming from a different rom / OS you'll need to clean flash:
1. Wipe data (Factory reset)
(1.1.) If coming from stock OS you may need to format internal storage
2. Flash rom
(2.1.) Flash mods (magisk, no veirty if on ext4 decrypted.)
3. Rejoice
For dirty flash just skip step 1, 1.1
and possibly 2.1 if your mods support addon.d (ex: Magisk)
It does not matter when you flash the firmware zip, and you only need to flash it once per firmware version
XDA:DevDB Information
Yet another AOSP project, ROM for the OnePlus 5
Contributors
poad42
Source Code: https://github.com/yaap
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS stable 10.0
Based On: AOSP
Version Information
Status: Alpha
Created 2020-09-15
Last Updated 2020-09-15

Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Alert slider, Panel modes, HBM stuff
Permissive kernel
SafetyNet
Broken:
Encryption
Note: The ROM includes gapps with some pixel additions .

Feel like buying me some coffee for my efforts?
Donation link: https://paypal.me/generichandle
Join our chat : https://t.me/yaapop5 or https://t.me/yaapcommon

Screenshots

Congrats and Thanks for the Wonderful Support. Downloading the same...

woah! thank you so much for you work. I'm excited!

Great job Devs thank you

awesome, this is not a alpha, this is a beta :good: (my first post)

>barebones AOSP
>includes Gapps
Ok

d1n0x said:
>barebones AOSP
>includes Gapps
Ok
Click to expand...
Click to collapse
Barebones AOSP in regards to the UI because the dev's previous NitrogenOS had a bunch of customisations. I don't think that's very hard to understand. The objective is to be as barebones as possible, Gapps have nothing to do with being barebones or not.

Hello! Thank you in advance for doing this great project. It is possible to make a ROM Similar to Oxygen OS 11? I really liked this new Oxygen aesthetic. Thank you again for doing this for us.

Spider-Vice said:
Barebones AOSP in regards to the UI because the dev's previous NitrogenOS had a bunch of customisations. I don't think that's very hard to understand. The objective is to be as barebones as possible, Gapps have nothing to do with being barebones or not.
Click to expand...
Click to collapse
Yes it does. It isn't as barebones as possible in its current state because GApps is unnecessary for Android to run. It also increases the file size of the rom. False advertisation.
Besides, I've never, ever seen an initial AOSP rom for a new Android version that includes GApps on XDA. Heck, I've never seen a "barebones" AOSP rom that includes GApps. I think that's quite telling.

poad42 said:
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Broken:
Alert slider, Panel modes, HBM stuff (all need source side changes)
Permissive kernel
SafetyNet
Note: The ROM includes gapps with some pixel additions .
Click to expand...
Click to collapse
So what can be done for broken (how can we do side changes .. Permissive kernel any link for that
Tq exited for ur reply

SirSoviet said:
Yes it does. It isn't as barebones as possible in its current state because GApps is unnecessary for Android to run. It also increases the file size of the rom. False advertisation.
Besides, I've never, ever seen an initial AOSP rom for a new Android version that includes GApps on XDA. Heck, I've never seen a "barebones" AOSP rom that includes GApps. I think that's quite telling.
Click to expand...
Click to collapse
Well, actually a lot of 'AOSP' roms are just 'LineageOS based but with the AOSP interface'. Even in this case some repos are based on the LineageOS repos:
https://github.com/yaap/device_oneplus_cheeseburger/commit/62baf1aa2596ecc100b36890f2245ba832ff3cfc

robertogl said:
Well, actually a lot of 'AOSP' roms are just 'LineageOS based but with the AOSP interface'. Even in this case some repos are based on the LineageOS repos:
https://github.com/yaap/device_oneplus_cheeseburger/commit/62baf1aa2596ecc100b36890f2245ba832ff3cfc
Click to expand...
Click to collapse
The device tree was created by los yes, but has been extensively reworked both in Q and R, the cheeseburger tree is just a bunch of makefiles. The common tree is the one that has most of the stuff. So its not los based with an aosp interface or anything like that lol. Its just its own thing.

Thank you for freely sharing your great work. It is much appreciated! :highfive:

poad42 said:
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Broken:
Alert slider, Panel modes, HBM stuff (all need source side changes)
Permissive kernel
SafetyNet
Note: The ROM includes gapps with some pixel additions .
Click to expand...
Click to collapse
It's purely already amazing bro, thx
Will redo a donation soon, keep my NOS Nand Backup for trying this A11

poad42 said:
The device tree was created by los yes, but has been extensively reworked both in Q and R, the cheeseburger tree is just a bunch of makefiles. The common tree is the one that has most of the stuff. So its not los based with an aosp interface or anything like that lol. Its just its own thing.
Click to expand...
Click to collapse
1st thing first: Congrats for working so frequently to bring up Android 11 for oneplus 5 & 5t. Brother I've suggestion not to react for users who don't understand the efforts of dev's hard work, I know how much time it takes and from where that time we manage? We cut down that time from our family, our rest and by changing our sleeping pattern. It's not our business, We're doing this just for hobby not for money. But instead of appreciation getting questions. I haven't seen if anyone has asked politely that " Sir please correct barebones word because you've included GApps". Brother again I'll say don't answer to users who always seeking your writing mistakes but not measuring your efforts and hard work.

[Thread Cleaned]
As outlined in our Forum Rules:
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
Click to expand...
Click to collapse
Please respect the wishes and decisions of the developer. You may provide constructive criticism but spewing disbelief for a feature or module that is or isn't present does not comply with the above rule.
Keep in mind there are plenty of alternatives to choose from and realize how lucky you are with a device that gets so much development love.
If you are wondering why your post was removed or edited, please feel free to drop me a PM.
Have a great day and keep it safe!

Thanks for your work mate! Great to have R for OP5. I planned to change my phone, but if I can have R as daily driver, I may wait a bit more
Do you plan to stay "barbone" or will you gradually port nitrogen's features to R?

ROM ❯ PIXEL 3a ❯ UNOFFICIAL ❯ ProtonAOSP 11

ProtonAOSP • Pixel 3a
Android 11 ROM​
ProtonAOSP is a minimal custom Android 11 ROM focused on UI/UX and performance, with a touch of privacy.
Instead of customization it is focused on more smoother experience.
Installation
1. Unlock Bootloader
2. fastboot flash boot boot.img
3. Reboot to factory and factory reset
4. adb sideload rom.zip
5. Reboot​Note:- Rom already comes with gapps included so no need to flash them
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Download Here​Known issues
No eSIM support(I plan to add in next build)
Join the Telegram group for support
Kernel source code
ROM source code
This is just a side project, I may or may not maintain it in future.
A huge thanks to @kdrag0n for the amazing rom and the work done on this rom.

Reserved

I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.

96carboard said:
I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.
Click to expand...
Click to collapse
1. Soon I'll push source
2. I do have microg build for sargo as it is my main device, but not for bonito, so I did not post here on xda, if you want it join the support link group in the thread. Regarding google crap, for some users flashing gapps externally had less fluid experience so I did it.

I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?

96carboard said:
I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?
Click to expand...
Click to collapse
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.

FoxA said:
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.
Click to expand...
Click to collapse
Thank you very much. I'll give that a go

Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
sorry, I don't have the device anymore.

The link download is not working, please update it

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
Here's a current source.
I don't know if it's trusted, or who the maintainer of this unofficial build is though. Just found it via telegram.
ProtonAOSP - Browse /ProtonAOSP at SourceForge.net
sourceforge.net

Nice one. It's really handy to be able to revive old, unsupported devices like the Pixel 3a, which is a perfectly usable phone and can be picked up for next to nothing.
Some of us don't care about de-googling our phones and really just want to extend their lifespan with security updates, so having gapps baked in to ProtonOASP is really nice. Especially when we're just trying to help out our non-technical friends get a bit more life out of their old phones. A consistent, familiar user experience is all they really want.
I was wondering though: Does your build (or any build of ProtonOASP) come with verified-boot signatures so that the device's bootloader can be locked down after the ROM is installed, or is CalyxOS the only option for this?
Unfortunately, Calyx are very puritanical when it comes to de-googling, and microG is just a terrible substitute for interacting with Google services. I tried it on the Pixel 3a, and it doesn't even sync the contact list from your Google account. My non-technical friend was not impressed.

GrapheneOS still has builds up for 3a, however new builds were terminated as of February. While it doesn't ship with gCrap preinstalled, installation is trivial as they've built a compatibility layer to make it work correctly (and much MUCH more securely) as user-installed software, which you can install from the program "Apps".