Database Info

? about aosp ROM's

First of all I'm on Verizon.
I've always used tw roms on my s3 but have been considering trying out a aosp rom and an needing help selecting one.
When reviewing that particular section it seems that carbon is the most popular of the options.
I'm wanting to know the benefits of aosp over tw based roms. One thing I have noticed is that I'm thinking that the Swype feature to either call or message while in you contact list doesn't work on aosp. That's a bummer to me because that's one of if not my favorite features of tw.
Is aosp faster than tw? Is it snappier because of the file size being smaller?
When I had my fascinate I normally ran aosp because, well, that's for the most part all there was to offer once 4.0 came out.
What is in your opinion on the best aosp or aokp rom and why? What should I stay away from?
I appreciate any and all help you guys have to offer.
I look forward to your guy's suggestions.
Thanks and have a great weekend.
Aaron
Sent from my SCH-I605 using Tapatalk 2

hank3fan said:
First of all I'm on Verizon.
I've always used tw roms on my s3 but have been considering trying out a aosp rom and an needing help selecting one.
When reviewing that particular section it seems that carbon is the most popular of the options.
I'm wanting to know the benefits of aosp over tw based roms. One thing I have noticed is that I'm thinking that the Swype feature to either call or message while in you contact list doesn't work on aosp. That's a bummer to me because that's one of if not my favorite features of tw.
Is aosp faster than tw? Is it snappier because of the file size being smaller?
When I had my fascinate I normally ran aosp because, well, that's for the most part all there was to offer once 4.0 came out.
What is in your opinion on the best aosp or aokp rom and why? What should I stay away from?
I appreciate any and all help you guys have to offer.
I look forward to your guy's suggestions.
Thanks and have a great weekend.
Aaron
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I don't think you're going to find much better performance, I believe that most folks go with AOSP simply because they prefer the look and feel. Personally I thought the TW menus were ugly and childish. There are a number of AOSP roms to chose from, if you're new to it then I'd recommend CM10/CM10.1. Make sure to read all of the instructions/documentation first, there are some known issues with certain ROMs and that may turn you off. And of course do a IMEI and nandroid backup first!

CrustyMcLovin said:
I don't think you're going to find much better performance, I believe that most folks go with AOSP simply because they prefer the look and feel. Personally I thought the TW menus were ugly and childish. There are a number of AOSP roms to chose from, if you're new to it then I'd recommend CM10/CM10.1. Make sure to read all of the instructions/documentation first, there are some known issues with certain ROMs and that may turn you off. And of course do a IMEI and nandroid backup first!
Click to expand...
Click to collapse
Thanks for the reply. I'm actually not big on theming. I guess I've just been wanting to venture out but have read in some instances that people are having data and gps as well as imei problems.
I forgot about flashing slim bean awhile ago, but when I did I lost my imei and it freaked me out. I got it backed up on my computer as well as andromizer.
As far as the aosp theming goes,I don't like the blue at all but have seen some really nice themes on here and some really sharp themes on Google play.
Thanks again and hope more people chime in.
I really really really hope team glitch gets on board at some point. If those dudes start making kernels for this device I'll be sold instantly. That team knows what's up!
Sent from my SCH-I605 using Tapatalk 2

I really wish we could use voodoo sound but Samsung changed something to where that no longer works but I read on a vzw rom thread for the note 2 that someone implemented it and its working.
Sent from my SCH-I605 using Tapatalk 2

Anyone porting a pure AOSP to Doubleshot?

We seem to have a great selection of other ROMs, from CM, AOKP, etc. but I never see just an AOSP ROM for this device. It would be great to compare the "Nexus Experience" for the Doubleshot, I think.

Well, technically Cyanogen Mod is the greatest AOSP ROM out there. As far as I know nobody writes anything from the ground up. At least if I understand how everything all goes together. Now, someone may very well use their base code & do all their own coding for add-ons & customizations but I'm not sure who or which ROM you may be talking about. My wife has a Nexus 4 so I have been browsing their forums but that's the way it seems to me.

Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium

demkantor said:
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
SEE! I told ya I wasn't sure. LMAO! :laugh:

demkantor said:
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would love to try this, and I've gone far enough to setup everything on my linux box. I got to the point of downloading the source files, and I'm not sure where to go from there. Reason being that I know that most of the phone sensors and components wont work without the proprietary drivers and other required software for the phone. I don't know where to find them, and if I managed to get them, how to integrate them into the source tree. I have looked through the developers reference thread, but not sure whats needed from there to get all the stuff needed.
I think I'm in over my head lol

Fuzi0719 said:
We seem to have a great selection of other ROMs, from CM, AOKP, etc. but I never see just an AOSP ROM for this device. It would be great to compare the "Nexus Experience" for the Doubleshot, I think.
Click to expand...
Click to collapse
I gotta say, I only just got into the ROM bizness. Was running fully stock, locked GB rom on this phone until a few weeks ago. After some research and lots of reading through these forums I settled on the Unofficial CM 10.1 JB rom here, and absolutely love it. I can't believe what amazing crew of dev's we have here that are bringing new life to this great hardware, but unsupported handset!
Suffice to say it's been my ONLY other experience compared to stock, but I'm using it as a daily driver with nearly no issues, and some have even been fixed since my first flash a few weeks ago. Can't thank this forum enough. Now if only I could post in the development forums without having to make 9 more BS posts I'd be a happy camper!

A question about stock vs. Custom ROM on a nexus device

I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app

bbabiuk said:
I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.

rootSU said:
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.
Click to expand...
Click to collapse
Very thorough. I do have one other question then...
Then AOSP ROMs for Nexus devices should by the nature of the build process have everything working similarly to the stock ROMs. Things like Bluetooth not working quite right or green tints to cameras should not occur.
Sent from my Nexus 5 using XDA Premium 4 mobile app

*should* yes, but not guaranteed. Pure aosp should work immediately after compile. However, new functions are added by developers to the aosp code base to make the roms more functional and these commits can break each other or even existing functionality
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app

air2k57 said:
I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the update. The nice thing about nexus devices is it is so simple to go back to stock. It was a real pain on my HTC one.
Sent from my Nexus 5 using XDA Premium 4 mobile app

No problem. I had htc one and it was indeed a pain. While I liked sense, I felt a need to root because of annoying apps it came with, or power saver notification that was always there. Not to mention, T-Mobile variant took ages to get updated, and when it did, it was buggy. The whole S-Off thing was a nightmare.
I've always found other devices, even nexus 4, to function better with custom ROMs and kernel. It took me awhile to root n5 though, simply because I was happy with everything. I did like ability to have center clock, or circle battery with %. However, in order to have those, you need aosp or gravity box that doesn't work with art due to xposed. Oh yea, pie I liked too, I like having more screen space.
Other than that, I am very happy stock. I ended up finding a really good mix with purity ROM and elementalx kernel. I liked elemental on HTC one a lot as well. And, it has cooler colors option, I do like the way it makes display look.
Last night I ended up unrooting and going stock to compare. Reason being, I got annoyed with bright back key in landscape and text on quick toggles in portrait ended up being cut off some. Performance wise, I am thinking that lure stock is still A bit quicker. Battery? Not sure yet, I got woken up at 7am by stupid weather alert, ended up unplugging my phone and leaving it on nightstand. It dropped from 99% to 95% in 4 hours idle. So about a % an hour. I remember Franco and elemental having better idea battery life though.
Sent from my Nexus 5 using xda app-developers app

The *toad roms

I have all kinds of Android devices and I use Cyanogenmod on all of them. I like to have the same exact system on each; saves me time, to have to learn only one. Plus I very much like CM.
But on this device, for some reason, most of the development effort seems to go to the *toad releases. Could someone elaborate why? Secondly, why use a *toad instead of the "real" Cyanogenmod?

hardy81 said:
I have all kinds of Android devices and I use Cyanogenmod on all of them. I like to have the same exact system on each; saves me time, to have to learn only one. Plus I very much like CM.
But on this device, for some reason, most of the development effort seems to go to the *toad releases. Could someone elaborate why? Secondly, why use a *toad instead of the "real" Cyanogenmod?
Click to expand...
Click to collapse
Because the official releases are posted in the CyanogenMod website under downloads>official devices...the device maintainer for cm on apexqtmo was also banned from xda
Sent from my R3L4Y 4G using xda-developers app

Ummm, What? The official device maintainer for CM is @Nardholio who is definitely still here.
The HypnoToad images started as TeamApexQ's test bed, as time went on, there were tweaks that were made that were not accepted by CM for one reason or another, but we liked them. They became part of our internal builds, which as that stabilized and diverged more from CyanogenMod, we made available as FatToad. OmniToad is based on Omnirom, not CyanogenMod. The majority of TeamApexQ likes the Omni base better, so that has become our development platform.
One of the tweaks that are part of FatToad have bitrotted a bit, and the developer of that tweak has moved on to OmniToad, and has no intention of going back and maintaining said tweak, so FatToad likely will not be seeing any more releases.
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.

Magamo said:
Ummm, What? The official device maintainer for CM is @Nardholio who is definitely still here.
The HypnoToad images started as TeamApexQ's test bed, as time went on, there were tweaks that were made that were not accepted by CM for one reason or another, but we liked them. They became part of our internal builds, which as that stabilized and diverged more from CyanogenMod, we made available as FatToad. OmniToad is based on Omnirom, not CyanogenMod. The majority of TeamApexQ likes the Omni base better, so that has become our development platform.
One of the tweaks that are part of FatToad have bitrotted a bit, and the developer of that tweak has moved on to OmniToad, and has no intention of going back and maintaining said tweak, so FatToad likely will not be seeing any more releases.
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Click to expand...
Click to collapse
XDA refuses to ban me

Nardholio said:
XDA refuses to ban me
Click to expand...
Click to collapse
i thought it was lbcoder....well thats what i was told anyway....grats on being a good maintainer Nard

hi
The difference between the original ROM and Kastvm

Magamo said:
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Click to expand...
Click to collapse
This is good to hear. Programmers of free software tend to jump ship pretty quickly and get bored with anything that is not new & cool. But Cyanogenmod should be seen as cool, since it's just awesome to have the same system on so many devices.
Thanks for the clarifications.

hardy81 said:
This is good to hear. Programmers of free software tend to jump ship pretty quickly and get bored with anything that is not new & cool. But Cyanogenmod should be seen as cool, since it's just awesome to have the same system on so many devices.
Thanks for the clarifications.
Click to expand...
Click to collapse
As a very agreeable argument...the same could go for other great ROMs too and not just CyanogenMod..just takes developers to bring em to the device including CM...to each his own and that's why there is a variety to choose from
Sent from my R3L4Y 4G using xda-developers app

[LP Roms][Poll][Note3 Revive Team] Weekly Support Rom Vote, Which do you want?

Vote for your Favourite *Unsupported* Rom to be given weeklies!​
Please Note i will only support the N9005, hlte.
Why?
Currently the amount of lollipop AOSP/CM based roms for the Note 3 is running a tad short for my liking, i believe in choice and i believe that if you have the hardware to do it, why not? I will be running this poll for a week to see which Roms you guys want to see rolling out for the Note 3 and i will roll them out to you on a weekly basis, i can probably build a few roms in a day so the top few will be what i choose to support.
If you want a Rom added to the Poll just ask me and i'll add it, so what are you waiting for? Vote and i'll start rolling them out!​

Reserved for Results
Reserved for Results

Note3 Revive Team said:
Vote for your Favourite *Unsupported* Rom to be given weeklies!​
Please Note i will only support the N9005, hlte.
Why?
Currently the amount of lollipop AOSP/CM based roms for the Note 3 is running a tad short for my liking, i believe in choice and i believe that if you have the hardware to do it, why not? I will be running this poll for a week to see which Roms you guys want to see rolling out for the Note 3 and i will roll them out to you on a weekly basis, i can probably build a few roms in a day so the top few will be what i choose to support.
If you want a Rom added to the Poll just ask me and i'll add it, so what are you waiting for? Vote and i'll start rolling them out!​
Click to expand...
Click to collapse
This one probably is just wishful thinking, due to the fact that back on JB/KK it was very difficult for the dev, now with LP it will be even more difficult.
There used to be a ROM for the S4 named BlackBox.
It was a hybrid between TouchWiz and AOSP, the dev ported AOSP frameworks and libraries to work with TouchWiz. The ROM was SICK. And not easy to do. Not sure if the ROM had an altogether different kernel or any TW kernel could work.
Wishful thinking... :/

sirobelec said:
This one probably is just wishful thinking, due to the fact that back on JB/KK it was very difficult for the dev, now with LP it will be even more difficult.
There used to be a ROM for the S4 named BlackBox.
It was a hybrid between TouchWiz and AOSP, the dev ported AOSP frameworks and libraries to work with TouchWiz. The ROM was SICK. And not easy to do. Not sure if the ROM had an altogether different kernel or any TW kernel could work.
Wishful thinking... :/
Click to expand...
Click to collapse
That is probably beyond my skills as ive never ported, only built from source, however i'll get in touch with the developer of that Rom and see if he is willing to lend a hand to try get that going for the Note 3, i honestly thought there would be more interest on this thread thou..
Any AOSP/CM roms you want for weeklies haha?

Note3 Revive Team said:
That is probably beyond my skills as ive never ported, only built from source, however i'll get in touch with the developer of that Rom and see if he is willing to lend a hand to try get that going for the Note 3, i honestly thought there would be more interest on this thread thou..
Any AOSP/CM roms you want for weeklies haha?
Click to expand...
Click to collapse
As odd as it is, I got used to the close-to-stock TW ROMs. Don't mistake me, AOSP ROMs are fast as Hell, way more moddable, more beautiful, and I like that. However, for the way I use my Nope 3, close to stock suits my needs better.

sirobelec said:
As odd as it is, I got used to the close-to-stock TW ROMs. Don't mistake me, AOSP ROMs are fast as Hell, way more moddable, more beautiful, and I like that. However, for the way I use my Nope 3, close to stock suits my needs better.
Click to expand...
Click to collapse
It's rare you find a samsung device where people are actually happy with Touchwizz
So is no one interested in suggesting weeklies for an AOSP Rom? Or perhaps i should make a custom stock (Not that there are enough already)?
I honestly thought there would be more interest in this thread! What's going on guys??

Note3 Revive Team said:
It's rare you find a samsung device where people are actually happy with Touchwizz
So is no one interested in suggesting weeklies for an AOSP Rom? Or perhaps i should make a custom stock (Not that there are enough already)?
I honestly thought there would be more interest in this thread! What's going on guys??
Click to expand...
Click to collapse
I believe it might be something like this...
The user base needs something entirely different from the two (three if you count MIUI) options, we've got used to it. And some people might have the ideas for something different but lack the skills to do it. On one side you have AOSP (most of the AOSP ROMs function and behave almost the same; simple fact, not bashing the work of anyone, I don't have the knowledge to bash it ), on the other - TouchWiz. Both have their uses.
I lack the knowledge on how to do it, apparently the whole team of Samsung that makes TouchWiz doesn't (xDDDDDDDDDDDDD)... to combine all the functionality of the device at it's top performance with a really sleek UI implementation that's different enough to make the user treat and use the device differently.
Otherwise, I'd theme TW with black, grey, blue, holo colors n stuff and make the UI look like the control panel of some spaceship seen in sci-fi. The device itself carries the "Galaxy" moniker, ffs, and Samsung made it sound and look like a f***ing toy!
Making an AOSP ROM then stabilizing it, from what I've read, is no easy task for the whole Google team, it seems...
I am afraid that the Note 3 simply lacks the attraction to crackheaded devs who would tear Ubuntu Touch's a** in half, merge it with AOSP then slap that combination on top of whatever's left of TouchWiz. xD We have most of the major AOSP ROMs, can't tweak too much TW because of it's damn closed source, and... that's that. :/
Sorry if this was incoherent.
P.S. I am also sorry if any of this seems disrespectful, I don't mean it to be, given the fact that you're willing to actually build the ROM that's most demanded. Wish you luck.

Those are 2 recognize ROMs since my Nexus 5. :laugh:

ps000000 said:
Those are 2 recognize ROMs since my Nexus 5. :laugh:
Click to expand...
Click to collapse
Well when i hit 10 posts, and perhaps a little more interest is gathered in the thread then i can get these builds of vanir and nameloss rolling out to the community.
I am suprised thou i really am that no one seems to use AOSP/CM roms on the galaxy note 3!