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. RebootNote:- 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 HereKnown 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".
Related
Hello everyone,
the question and disscussion is:
Do we get Lineage OS support in the Future? it does not matter if unofficial or official, but what do you think?
I saw the LeEco le Max 2 get some unofficial support, so it could be that some Devs will try it.
It would be awesome *_*
I think the problem is, that the community isn't that big like for the le Max 2, but maybe it will get bigger in the future.
What do you think? :good:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
I think, it's not discussion, but it is a question. So, it should be in "QUESTIONS & ANSWERS". Le Max 2 have bigger community, because this phone is cheaper and cheapest Le Max 2 was for 180-200$. This mobile is older. Our Le Pro 3 have few months and in future it could have more community and ROMs like this.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Wooow! Someone interested?
It would be awesome!
:fingers-crossed:
Who could we talk to in order to get official support?
I dont know, but to get official support there should be at first a stable unofficial lineage OS Version. I do not know much about creating ROMs but i hope someone does and will create a masterpiece for le pro 3
I hope so
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Would be awesome. I will try your build!
Good project looking forward to
manuelbvb said:
Would be awesome. I will try your build!
Good project looking forward to
Click to expand...
Click to collapse
I'll edit a link to the thread I make with to-dos based off the source code I can see.
Here's where I'll post progress!: https://forum.xda-developers.com/le-pro3/development/progress-lineage-os-13-t3546126
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
robertzas said:
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
Click to expand...
Click to collapse
For Slim, please use the fork from where I get the code. See it in github. It's TS source, so it should work.
corvus said:
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
Click to expand...
Click to collapse
I forked your repo and shared it in my post. I'll work on what you mentioned. One of my top (long term) goals is complete CTS compatibility. With safetynet passed, there'd be nothing that would really pull you back to stock.
Definitely, I'm preparing the Kernel code after code to ensure we get a very clean and functional Kernel for the future, instead of just merging the one from LeEco with more than 80% of unneeded bits due to their other devices being at the same place (shameful).
This will get a ~30MB Kernel reduced to around 12MB and thus make custom ROMs perform a lot better and boot immensely faster after all.
I'd only need one sense of common attitude which is asking LeTV to keep the Kernel source up-to-date when they launch OTAs as well, I've seen some comments regarding their image stabilization fix at latest release (OTA) which is only possible at Kernel/blob level and thus if we want to have this feature working (at least partially) we need the source code "right off the bat" to get those fixes. Please, make pressure on their forums for 5.9 x720 Kernel source code and for nougat preview builds, I'd appreciate to even help with their own EUI for that matter, I'll see if I can get in touch with them concerning those points.
Do we have someone from China or someone with experience with Chinese so we can attach our discussions there?
I do hope they keep the open source up to date, but it seems they are doing the bare minimum to apply to Google's open source policy. I'm in the US, so I have the x727 with 1 SIM. We would need someone to test with a x720 as well.
@GalaticStryder, Leeco only will post the sources needed to avoid license problems with GPL, so dont wait much help from them. But we can ask...
@jts2111, I have a 720, so I can test your builds.
@jts2111
I received my X720 this week and I could also test your experimental build.
It would be nice to already start with a LineageOS custom ROM as first ROM to avoid a lot of reinstallation / reconfiguration of apps with other kind of custom ROMs.
I'm trying to build Stock AOSP (Not LineageOS) straight from Google for the OnePlus 3/3T?
I searched for a guide, but haven't found one.
Thanks in advance!
You can't
AOSP source is available for Pixel and Nexus devices
But you can build CAF for OnePlus 3, is clean and close to AOSP
Sent from my ONEPLUS A3003 using Tapatalk
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
liam_davenport said:
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
Click to expand...
Click to collapse
That would be doing him a great dis-service. Buy using anothers base you dont learn everything you need and rely on others code way too much. Not to mention if a cm/los issue happens (underlying bug in their base code so you are waiting for them to fix it) This is the reason that whole project will not work.
Starting from scratch is a great start and a place everyone should start
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
HolyAngel said:
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
Click to expand...
Click to collapse
I mean in Biology, you don't start at the organism, you start at the atom. You start at the base and build from there.
Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Pre-Disclaimer:
THIS IS AN UNOFFICIAL BUILD. The intent is to showcase what is coming up soon. I have been working hard on getting Walleye on a level I consider DD ready, especially from a security side of things.
Please keep any problems with those builds in this thread, I don't accept any bug reports for any other builds other than my HomeBrews.
Disclaimer:
While I make every effort to test these builds as much as possible, I am not responsible for anything that may happen to your device. I ask that you do your part to know your device and know how to recover from problems before you flash or post that you broke your phone!
Support:
I spend an astonishing amount of time developing this device. I can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Ask a question in this forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
Notice:
This build includes GApps for now. We're still working on ways to not prebundle it.
Before you flash, make sure you're on the latest 8.1 stock builds (and bootloader), then flash the ROM in TWRP.
Instructions :
Boot to TWRP
Format Data (If you didn't type YES, you did it wrong!)
adb sideload homebrews.zip
reboot system
(to gain root you must first boot homebrewsROM. Then reboot and to TWRP and install Magisk 1 6.0)
See below
Reporting Bugs:
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
What is your--
Build Date:
Did you--
wipe:
all data?
install gapps when you weren't suppose to?
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
WARNING: These are my personal testing builds. They include unmerged, work-in-progress stuff such as SuperUser, Privacy Guard, Google Play services etc. DO NOT FLASH 3RD PARTY GAPPS PACKAGES!
If you see a warning about vendor partition mismatch, you can ignore that in most cases, but before reporting issues you should be on the right version (without the warning).
### RELEASES ###
https://drive.google.com/drive/folders/1NY1j-eH9demisz5Y05jeIPGXipENo5yK?usp=sharing
XDAevDB Information
LineageOS, ROM for the Google Pixel 2
CarbonROM, ROM for the Google Pixel 2
DirtyUnicorns, ROM for the Google Pixel 2
Contributors
Source Code: http://github.com/LineageOS
Source Code: http://github.com/CarbonROM
Source Code: http://github.com/DirtyUnicorns
Source Code: http://github.com/TresReinosDeLeche
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
### DONATE ###
paypal.me/JacobStermer
Created 2018-02-2
Last Updated 2018-03-Today
reserved
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
I for one am happy to see it.
iluvamk said:
I for one am happy to see it.
Click to expand...
Click to collapse
Me to ? do we need to flash twrp after the ROM like on pixel 1?
GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
Archangel said:
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
Click to expand...
Click to collapse
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Let us know how it goes brother.
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.
right now i am getting FC on Camera APP, X Google, Ok Google, and T Google something. My computer just crashed building the potential fix.
Ryche666 said:
boot to twrp.
wipe all data
adb push lineageos
reboot to bootloader
boot to twrp
adb push magisk
reboot to system.
right now i am getting FC on Camera APP, X Google, Ok Google, and T mobile something. My computer just crashed building the potential fix.
Click to expand...
Click to collapse
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
jasonsamms666 said:
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
Click to expand...
Click to collapse
Sorry, i got super anxious myself when i finally got playstore, phone, and text messaging working.
Thus the piss poor thread that i copy and pasted from taimen's lineage.
GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Ryche666 said:
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Click to expand...
Click to collapse
FWIW this is what's been done with the Essential Phone.
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
I was the same way. A **** ton of reading and a lot of PMing. It is pretty simple when you get the hang of it. This early in the game you get to see the codes that attract you to certain roms or kernels.
Right now i just need to make sure it is stable before i work on the kernel or choose what rom i am gonna stick with.
NadavCE said:
FWIW this is what's been done with the Essential Phone.
Click to expand...
Click to collapse
That's what i heard. If i knew that last weekend we would have had that much sooner.
Awesome, glad to see some work
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Chronzy said:
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Click to expand...
Click to collapse
Can you share the complete steps and details on how you flashed it? Thank you!
infamousvincci said:
Can you share the complete steps and details on how you flashed it? Thank you!
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.
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 ProcedureInstall 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?
Is there anything that would be interested in a custom kernel or maybe custom roms for this device? I can pick one up pretty cheap on eBay, just wondering what the landscape if the community is here.
From what I could see on GitHub, some developers tried to use the kernel sources, but it seems that OnePlus forgot to release some parts of it. So for now no one has created any roms or kernels, there is just an unofficial TWRP.
I'm quite good with recreating the kernel sources, I have done so for the N10, N200 5G, and a few other devices. See here. The missing parts are mostly Qualcomm specific code they keep in CAF repositories. Until my device touches down in my mailbox I'll need some testers. I'll have the kernel source completed well before then.
Sorry but personally I don't think I can help testing, since it's my main device I'd rather avoid having to erase my data every time.
That's understandable. You wouldn't happen to have a boot.img I can start with? The stock firmware doesn't have the files broken up individually.
If anyone wants to follow development:
OnePlus Nord N100 Community
You can view and join @OPn100 right away.
t.me
I have this one from the latest update (EU variant, I don't know if it changes anything):