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.
Related
Hi.
Like me, people that own this mobile phone need to wait for huge efforts from people like Arco to develop a ROM with the last android version and the whole bug fixes and improvements of the OS.
After all that, we need to trust what developers could have done inside that same ROM, the same we get in this 'black market' and pray they didn't do any kind of malicious developments, this, if the source code/blobs didn't come with them already. Forgetting about the security side, if we look at the new features and upgrades of the same OS, again, we will need to wait for people like Arco to get time to develop all we want. So, my question is:
What need to be done for people that use this mobile phone to have the Replicant Android version?
Web references:
- replicant.us
- fsf.org/blogs/community/donate-to-replicant-and-support-free-software-on-mobile-devices
- linux.com/news/embedded-mobile/mobile-linux/759834-fully-free-android-rom-advances-to-jelly-bean/?&co=f000000013912s-1248979074
- wired.com/wiredenterprise/2013/10/replicant/
:good:
vcatpt said:
Hi.
After all that, we need to trust what developers could have done inside that same ROM, the same we get in this 'black market' and pray they didn't do any kind of malicious developments, this, if the source code/blobs didn't come with them already. Forgetting about the security side....
Click to expand...
Click to collapse
Seriously, do you expect this to be different with a Repilcant ROM?
There will be still a Dev behind this who will compile the ROM, add bugfixes and so on.
So if you are afraid of malware being added by a Dev, you can simply download the sources and compile your own ROM. No matter this is CM or Repilcant.
CM is open source and you can watch the entire code to what a Dev has done to it. There is no conspirancy and there is no need to become paranoic.
Therefore I do not see a single reason why a Replicant ROM should be better compared to Arcos CM releases.
I can't explain me better than the references I post in the first post. But for sure, if every project follow the philosophy that Replicant uses, development could improve so much about the SECURITY and so much about the TIME for the news features/improvements, is ridiculous what people need to wait to get an upgraded software (no question about any developer here ofc). And I know life is not perfect, but at some point things need to be done in a credible and systematic way, and this android variant with the name Replicant seems fine to me.
honeyx said:
Seriously, do you expect this to be different with a Repilcant ROM?
There will be still a Dev behind this who will compile the ROM, add bugfixes and so on.
So if you are afraid of malware being added by a Dev, you can simply download the sources and compile your own ROM. No matter this is CM or Repilcant.
CM is open source and you can watch the entire code to what a Dev has done to it. There is no conspirancy and there is no need to become paranoic.
Therefore I do not see a single reason why a Replicant ROM should be better compared to Arcos CM releases.
Click to expand...
Click to collapse
hum..
http://redmine.replicant.us/projects/replicant/wiki/SamsungGalaxyBackdoor
https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor
As many of you know the GSM Note 2 is supported by Team OmniROM in a unified build format. This work is inspiring to me as the team split from CM for altruistic reasons. I have come to consider OmniROM my AOSP branch of choice due to their philosophy toward security and development.
I see a niche for our community where some of our members may be uncomfortable utilizing the unified build for any number of reasons.
My product is no more than a straight source built t0lteatt build as the OmniROM spec is drawn up for the t0lte and adapted by the t0lteatt spec on the OmniROM github. All source is available at the OmniROM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-Omni commits or "fixes" with very few exceptions. If it is broken in the unified build it will be broken in this one as well.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in OmniROM commits that looks promising I expect that I would post a new build. Getting to the point where stuff wasn't broken took some serious banging of the head.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial OmniRom .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
omni-4.4.4-20150323-t0lteatt-COUGMADE.zip
omni-4.4.4-20150313-t0lteatt-COUGMADE.zip
omni-4.4.4-20150224-t0lteatt-COUGMADE.zip
omni-4.4.4-20150206-t0lteatt-COUGMADE.zip
omni-4.4.4-20150107-t0lteatt-COUGMADE.zip
omni-4.4.4-20150101-t0lteatt-COUGMADE.zip
omni-4.4.4-20141220-t0lteatt-COUGMADE.zip
omni-4.4.4-20141216-t0lteatt-COUGMADE.zip
omni-4.4.4-20141208-t0lteatt-COUGMADE.zip
omni-4.4.4-20141014-t0lteatt-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0lteatt git
DonkeyCoyote Samsung Vendor git
Props and credit to:
The OmniROM team.
UtkarshGupta for providing advice in working through build issues on compiling OmniROM and maintaining for t0lte.
Rmanne for assistance in getting my previous efforts in getting the unofficial CM ROM running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Mine
10/14/14 - I know the camera is a bit weird with how it won't connect after a while. This is present in the unified build as well.
Thank you for this! my Att Note 2 is far from dead and the way Att and the other "Providers" want to charge for every single little stinkin' thing.. (A 40$ SmartPhone charge from ATT? NO WAY) is ridiculous I plan to make this phone last quite a while if possible and folks like YOU and stuff like THIS make that possible! Thank you sir!
This type of thing is my way of giving back to the community and developing my understanding of the software we rely on.
does tethering work with this rom?
Main Difference From OmniROM
I have installed both OmniROM and this variant but I can't tell the difference. Can you explain?
Thank you very much in advance.
fresnogamer said:
I have installed both OmniROM and this variant but I can't tell the difference. Can you explain?
Thank you very much in advance.
Click to expand...
Click to collapse
The only difference is this is built from source with the I317 build prop baked in from the start. It is nothing earth shattering. Some folks really prefer a ROM built for the specific model they use.
New build is up. Still KK.
i cant install it... Status 7 , installation aborted
Edit: I installed the newest TWRP recovery and it worked ... thanks a lot, i'll be trying this ROM
Edit 2: Lost root access?
New build is up.
EDIT: I pulled the DL link as the build was broken.
New build is up.
New build is up.
Change log?
Coug76 said:
New build is up.
Click to expand...
Click to collapse
Forgive my ignorance if I am missing it.
Is there a change log indicating updates between releases?
Awesome Rom BTW.
parakleet said:
Forgive my ignorance if I am missing it.
Is there a change log indicating updates between releases?
Awesome Rom BTW.
Click to expand...
Click to collapse
omni.cmxlog.com/4.4/t0lte/
Coug76 said:
omni.cmxlog.com/4.4/t0lte/
Click to expand...
Click to collapse
Cold Blooded
THanks
Happy New Build!
Coug76 said:
Happy New Build!
Click to expand...
Click to collapse
This one did not like a dirty flash.
Clean flash worked well though.
parakleet said:
This one did not like a dirty flash.
Clean flash worked well though.
Click to expand...
Click to collapse
Thanks for the feedback.
New build is up.
New build is up.
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
CJ-Wylde said:
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
Click to expand...
Click to collapse
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
You rock, thank you for the quick response! I'm not even sure what kind of rom I desire. I just know it would be neat to go full on basic AOSP and add from there without some of the clutter and bugs introduced with CM's stuff, although CM has always been an enjoyable experience. Whoot for guys like you!
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
mythos234 said:
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
Click to expand...
Click to collapse
thenextdon13 said:
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
Click to expand...
Click to collapse
They talked about device tree here. An example for a pure AOSP one for the device LG H815 is here:
https://github.com/cile381/android_device_h815
See this for an explanation :
http://wp.me/p6ZeCY-3p
AOSP source contains the sources to build a ROM which are the same for all devices and a device tree is a device specific description on how to build or as the above link states:
“A device tree is a tree data structure with nodes that describe the physical devices in a system”
.
Sent from my LG-H815 using XDA Labs
Thank you, steadfasterX.
That provides some clarity, although I think there is still a bit missing for me--
Ugh, i can't post links because of spam rules.. :-/ makes describing things harder.
How did you find the github cile381/android_device_h815 as being the AOSP tree for that phone? My understanding was that the AOSP main repo is here:
android.googlesource.com
And so related to my question previously.. i guess i'm confused specifically who the 'we' is that mythos234 references, and where that source would be located...
many thanks!
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
It goes back to 6.0.1 but no further.
It will do both, apparently.....
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk
MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol
The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.
Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk
Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris
jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.
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".