Related
UPDATE 6/2/14: The M7VZW is now officially supported! Download link is now pointing to the official downloads to avoid downloading one of my unofficial builds. I'm not the official build maintainer however.
-----------------------------------------
About Carbon
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.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We 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 addressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device 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.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Contributors
CarbonDev, daxmax
ROM OS Version: 4.4.x KitKat
Based On: AOSP
-----------------------------------------
-----------------------------------------
Source:
CarbonROM: https://github.com/CarbonDev
Cyanogenmod: https://github.com/CyanogenMod
Kernel: https://github.com/CyanogenMod
ART supported?
Via Nexus S7ven
[ROM][AOSP][Unofficial] CarbonRom KitKat [m7vzw] 2-24-14
fullmetal509 said:
ART supported?
Via Nexus S7ven
Click to expand...
Click to collapse
It never occurred to me to check to see if there was something I needed to add in to the device files to support changing the runtime.
EDIT: I'll check to see if the lines are in the build target. I always err on the side of caution and ART wasn't a concern since this was a build for me.
EDIT 2: Testing ART support now.
EDIT 3: Seems to be working just fine. I'll run ART on my phone for now and test.
Thanks for the birthday present pal, I've been hoping to see this ROM for a while now!
Sent from my HTC6500LVW using Tapatalk
TheAppleAndroidGuy said:
Thanks for the birthday present pal, I've been hoping to see this ROM for a while now!
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Nice. Happy birthday.
ART support
Just a quick update on ART support. After enabling it in developer options and rebooting, things seem to be fine so far. It took a bit after switching the runtime the first reboot but after the 'upgrade' finished there were no FC's and the phone seems to be functioning normally. Any apps that have issues with ART will still have issues though obviously. Having said that, so far so good.
Yesssssss, mmuzzy. We new more mmuzzy in our lives.
Sent from my One using XDA Premium 4 mobile app
Hey mmuzzy! Good to see you around in these parts, I ran your rom for my nexus 7 2012 a while back. You beat me to the unofficial Carbon-rom haha.
skiman10 said:
Hey mmuzzy! Good to see you around in these parts, I ran your rom for my nexus 7 2012 a while back. You beat me to the unofficial Carbon-rom haha.
Click to expand...
Click to collapse
Thanks. Ah, sorry about that. I didn't see that.
mmuzzy said:
Thanks. Ah, sorry about that. I didn't see that.
Click to expand...
Click to collapse
Its alright. My first unofficial port of a ROM so it is taking some time.
Sent from my HTC6500LVW using Tapatalk
skiman10 said:
Its alright. My first unofficial port of a ROM so it is taking some time.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Check your PM.
mmuzzy said:
Hey guys,
Here is an unofficial build of the CarbonROM I made for myself and I thought I'd share since it seems to be working pretty well for me. Your mileage may vary though so please nandroid as you normally would when crack flashing. If one of the normal devs was already working on CarbonROM this wasn't me trying to step on toes. I don't intend to do this nightly, or at all if an official build is in the works.
In the meantime, enjoy.
ROM: http://goo.im/devs/mmuzzy/m7vzw/carbon//CARBON-KK-UNOFFICIAL-20140224-1729-m7vzw.zip
GAPPs: http://goo.im/gapps/gapps-kk-20140105-signed.zip
I've linked the 'standard' GAPPs but I've also had good luck with PA and Banks versions of GAPPs.
Sources:
CarbonROM: https://github.com/CarbonDev
Cyanogenmod: https://github.com/CyanogenMod
Kernel: https://github.com/CyanogenMod
Thanks to CarbonROM, Cyanogenmod, Flyhalf205, santod040, buckmarble, and everyone else who give us all these great ROMs to chose from.
Click to expand...
Click to collapse
Hell yes. Finally. Props to you, sir!
Is this running the unified CM kernel, or something else? Not that it matters too much, I'm gonna flash it anyway...
Can you post in the OP any bugs or things not working? How is battery life on this?
123421342 said:
Can you post in the OP any bugs or things not working? How is battery life on this?
Click to expand...
Click to collapse
I haven't found anything glaringly broken yet. Battery life is decent. I have hours of deep sleep overnight.
Sent from my One using Tapatalk
thedrizzle said:
Hell yes. Finally. Props to you, sir!
Is this running the unified CM kernel, or something else? Not that it matters too much, I'm gonna flash it anyway...
Click to expand...
Click to collapse
I was viewing on my phone and missed the question. Sorry about that. It's running the CM kernel which seems to be running smoothly as of yesterday.
Tried to download gapps. Says "404 not found"
Sent from my HTC6500LVW using Tapatalk
pita said:
Tried to download gapps. Says "404 not found"
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Yup. Not sure why that is. I linked from the GAPPs page on Goo.im but even clicking on the link from http://goo.im/gapps gives the same results.
Alternative GAPPs downloads:
Cyanogenmod: http://wiki.cyanogenmod.org/w/Google_Apps
BaNkS: http://forum.xda-developers.com/showthread.php?t=2012857
OP updated with alternatives also. Thanks for pointing it out.
I guess it's just my phone but every time I install this my phone starts roaming until I factory reset it
Sent from my HTC6500LVW using Tapatalk
jtj1825 said:
I guess it's just my phone but every time I install this my phone starts roaming until I factory reset it
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I didn't run into that at all. If you dirty flashed I probably would have recommended wiping anyway.
mmuzzy said:
I was viewing on my phone and missed the question. Sorry about that. It's running the CM kernel which seems to be running smoothly as of yesterday.
Click to expand...
Click to collapse
No worries...thanks for the reply. I may flash the EliteLunar kernel since it has a few nice features that the CM kernel doesn't, but I'll agree that the CM kernel does run nice and smooth. Thanks again for the port...I hope we can keep this going until Carbon either devs for the m7 or lets someone be an official maintainer. Carbon has been my favorite ROM since its inception.
thedrizzle said:
No worries...thanks for the reply. I may flash the EliteLunar kernel since it has a few nice features that the CM kernel doesn't, but I'll agree that the CM kernel does run nice and smooth. Thanks again for the port...I hope we can keep this going until Carbon either devs for the m7 or lets someone be an official maintainer. Carbon has been my favorite ROM since its inception.
Click to expand...
Click to collapse
I'll keep my eyes on the changelog. Now that I've got everything set up it's no big deal to build a ROM now and again when the changes warrant it until an official port.
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
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 t0ltetmo build as the OmniROM spec is drawn up for the t0lte and adapted by the t0ltetmo 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-20150322-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150313-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150223-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150206-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150107-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150101-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141220-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141216-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141208-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141014-t0ltetmo-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0ltetmo 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.
1st!! Yeah! Thanks for another great rom amd contribution to our community!
Coug is definitely one of the greats in our GN2 community. Total warrior in my book. Grateful for his time and talent.
Awesome build, but I am not getting any mobile data. I used Philz recovery. Anything I am missing here?
EDIT: Just tried with the latest TWRP also, still no mobile networks.
Mrzoops said:
Awesome build, but I am not getting any mobile data. I used Philz recovery. Anything I am missing here?
EDIT: Just tried with the latest TWRP also, still no mobile networks.
Click to expand...
Click to collapse
What does your APN show?
Nice.
Great Job
This instal went smooth and all seems to be working great. Nice rom TY
After a short sabbatical, T889 OmniRom is back. Still 4.4.4 KK.
What happened to the other omnirom thread?
Coug76 said:
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 t0ltetmo build as the OmniROM spec is drawn up for the t0lte and adapted by the t0ltetmo 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-20141208-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141014-t0ltetmo-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0ltetmo 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.
Click to expand...
Click to collapse
Just a Heads up. Your file link is sending us to the att version...i didnt realize it until i tried to flash it and recovery advised it as such. I found th file by looking up your profile there it listed the correct t889 file. Downloading now.
butwhydoitalk2u said:
Just a Heads up. Your file link is sending us to the att version...i didnt realize it until i tried to flash it and recovery advised it as such. I found th file by looking up your profile there it listed the correct t889 file. Downloading now.
Click to expand...
Click to collapse
So it is. Did you DL the version from October then? I'll upload the correct version in a minute. I'll also do a clean build after the I walk the kids to school.
Coug
AngryDinosaur said:
What happened to the other omnirom thread?
Click to expand...
Click to collapse
UtkarshGupta is taking a step back to focus on more important things in life. He is working to hand off Omni for Note 2 to a new maintainer if one can be found.
Coug76 said:
So it is. Did you DL the version from October then? I'll upload the correct version in a minute. I'll also do a clean build after the I walk the kids to school.
Coug
Click to expand...
Click to collapse
I was able to find the file in your profile. So i downloaded it. I am currently running it and so far so good. Thanks.
butwhydoitalk2u said:
I was able to find the file in your profile. So i downloaded it. I am currently running it and so far so good. Thanks.
Click to expand...
Click to collapse
Thanks for the heads up. I have corrected the link and it is the 12/08/14 build. I just synced the repo for both Omni and CM and will run a build for both this morning. I should be able to post new builds this afternoon or evening depending on what the afternoon allows.
New build is up
EDIT: I pulled the DL link as the build was broken.
New build is up.
Coug76 said:
New build is up.
Click to expand...
Click to collapse
Could that new maintainer be you? Because cougmade omni is pretty slick, smooth sailing. ?
Thanks for the build.
Coug76 said:
UtkarshGupta is taking a step back to focus on more important things in life. He is working to hand off Omni for Note 2 to a new maintainer if one can be found.
Click to expand...
Click to collapse
I'm too much of a novice to take that role. That and my wife would invite me to find other living arrangements.
New build is up.
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.