Database Users

What's the difference between the cupcake, Ion and Rogers Roms?

I understand that everyone's builds are different and with different tweaks and apps but what are the primary differences between Cupcake, Ion and Roger's based Roms?
I come from a Windows Mobile background and I know the different sys files in a rom made a world of differences from performance to features, is this the same with Android?

Here:
http://www.simonwalkerphotos.com/android/android_build_information.asp
Thats the best answer you will get, it tells you everything you need to know.
Oh and obviously the rogers rom is only for rogers .

theslam08 said:
Here:
http://www.simonwalkerphotos.com/android/android_build_information.asp
Thats the best answer you will get, it tells you everything you need to know.
Oh and obviously the rogers rom is only for rogers .
Click to expand...
Click to collapse
That's the only answer I have gotten through PMs and it is not what i am asking.
I understand the difference between the different Rom builds but what is the difference between 3 Roms with the same tweaks and apps but 1 is Ion based, 1 is cupcake based and ,1 is roger's based (and I am running a Rogers Rom on Tmob so they are not only for Rogers )

jady said:
That's the only answer I have gotten through PMs and it is not what i am asking.
I understand the difference between the different Rom builds but what is the difference between 3 Roms with the same tweaks and apps but 1 is Ion based, 1 is cupcake based and ,1 is roger's based (and I am running a Rogers Rom on Tmob so they are not only for Rogers )
Click to expand...
Click to collapse
Isn't Rogers still cupcake based?

They're all "cupcake based." The Ion version runs quick, but lacks the T-mobile features of AmazonMP3 and the IM that has Yahoo, AIM and MSN. Rogers adds Exchange support to that (and isn't only for Rogers).

mikedmeyer said:
They're all "cupcake based." The Ion version runs quick, but lacks the T-mobile features of AmazonMP3 and the IM that has Yahoo, AIM and MSN. Rogers adds Exchange support to that (and isn't only for Rogers).
Click to expand...
Click to collapse
So then if I understand correctly ion just strips down the rom and optimizes the build and rogers just adds some other support (exchange) but they are all basically the same as far as abilities and features?
What is the difference between the HTC and Google builds? I recall HTC and Microsoft having 2 separate development trees for WM6.5. Is this similar?
Thanks for the help guys, I have limited Linux experience but tons of WM experience and have had the G1 for 3 weeks now. I am still trying to wrap my head around the structure and organization of the Roms.

What is the difference between the HTC and Google builds?
Click to expand...
Click to collapse
The only differences you will really see betweek the two are the Dialer, Camera, VK, some marble game, and a PDF viewer.
I think thats all...

None of these responses really answer the first posters question. Those links are all great for showing the different features but it would be great for someone to post something that will help us understand just what those charts even mean. For example, one of the sites, Androidspin is fantastic as a chart for picking your ROM but it assumes already that you know what cupcake, doughnut, rogers, hero... is. Here in Utah, I had no idea that Rogers was a carrier. I thought it was a model of HTC phone?
Can someone explain all the different terms. Something like (pulling out of my butt cause I'm in the dark here)
Physical phones:
Dream
Magic
Hero
Operating systems:
cupcake
rosie
doughnut
Carriers:
Rogers
T-Mobile
Cyanogenmod = great for speed but lacks features
JacHeroski = based on Hero, yadda yadda yadda..
There are so many different ROM's I'm totally lost as to which one I would want to load on my G1 that is fast, stable and has lots of great features.

Man, all I can say is spend a few hours on these boards and read the stickies
Im not trying to be a **** by any means... Its just that at this point theres so many different flavors of Android out there that it would take us longer to explain it as opposed to you just readin those posts.
As far as:
Operating systems:
cupcake
rosie
doughnut
Click to expand...
Click to collapse
is concerned... In short Android is the overall OS... Cupcake is the first of many updates to the operating system which included things such as soft keyboard, MMS attachment save, etc. Rosie has NOTHING to do with Android, rather its an update created by HTC to lay over the existing home screen and provide some nice eye candy. Donut is the latest update on the verge of being released.
Check this site out to get really in depth:
http://developer.android.com/guide/basics/what-is-android.html

Cyanogen mod 6.1 Work in Prog. (copied and pasted) lol

I apologize for not keeping the site up to date, I’m a slacker We also had a database issue and lost the last post about 6.0′s release, if you were wondering why it went missing.
6.1 is the current work-in-progress and is coming together nicely. There’s a few new features like touch-to-focus in the camcorder, dismiss notifications by swiping, kernel updates for most devices, and improved performance. There will also be support for a few new devices- Acer Liquid, HTC Wildfire and Samsung Vibrant. My eye is also on the new HTC phones that are about to get released like the G2.
A lot of people ask me about adding support for their phone, but we can only support phones that we actually own. The CM team is always looking for new hackers to join up with us to add support for their favorite device. Get in touch with me if you’d like to help.
CyanogenMod is open source. The quality of code being added to CM has vastly improved because of the code review system that we’ve put in place, Gerrit. It’s the same system used by Google to manage the Android Open Source Project. It allows anyone to submit code to the project in a highly-visible way and gives us a way to examine and improve it before it’s actually merged. We want your code, so send us your patches. If there’s something you don’t like, change it.
Nightly builds of CM are always available if you’re brave and want to try out the latest code. If you’re running nightly builds, the best way to stay up to date on new changes is to follow on Twitter.
Our user base is approaching a quarter of a million users. This project has come a long way Thanks for all the support, we are only as strong as the community!

Attn1 Hope you will add this to aria as well x-)

aepowerlifter said:
Attn1 Hope you will add this to aria as well x-)
Click to expand...
Click to collapse
You just did. When you're quoting cyanogen, you should use quote tags and credit him.

saweeetttt!!!!

I can't wait!
Sent from my Liberty using XDA App

Thanks alot, now I'm going to be Rom Manager every minute waiting for the update, haha
Sent from my Liberty using XDA App

@OP
Thread moved to general.
Also, are you part of the CM team? Unless this is the case, you may want to give credit to Cyanogen for his work in your first post.

[Q] the ultimate android build? not asking which is the best..

ok so we are all aware of all the various android builds out there for different phones. some with sense, some stock. all the chefs have their own basic formula for the perfect rom when they try to cook them for us. now most builds we apply to our phones are mod's of builds for other phones. After working with so many builds and liking certain features of each, but only available to each, i found myself asking the following question.
Companies like htc, etc. are assigned to build a certain phone with a certain android build with certain features activated/deactivated (ex. some builds have tethering, but tmobile said to cut tethering option out of g2. or some builds have a 2g/3g on off option where as others don't) this must mean that there is a general android build they start with that has all features and they just decide to keep/omit things they want or things carriers don't want. (or add some version of sense ui to it or touchwiz). My question is, is there a general ultimate android build that is available that has every feature there? i'm not a developer so i've never cooked a rom, but it would be awesome to have one build with everything and a simple way for users to decide which options they want or to omit. i know it sounds simple in theory and will never be that easy. but it would be awesome to have one general build with all options and can choose which ones i want to use or not to use vs. a developer selecting them for me.
this is a major problem with many winmo builds i've worked with compared to android builds, but its still something that bugs me when i try a rom and say damn i wish there was a 2g/3g on off in the network options vs having to dig for gsm/wcdma options. like i said in theory it sound easy and i'm sure its not, thats why i give all the chefs credit. but just throwing it out there in case something were to exist like that. thanks

I think I understand what you mean.
I've played with the Android SDK and the BASE 2.2 (what we know as Froyo) has all you mention (tethering etc), but looks kinda bland, this may be that I'm now so used to Sense and it's niceties that anything less than Sense to me just looks wrong.
If you want to see Android as Google intended for us all to use just download the SDK and start a 2.2 session with no modifications and you'll see the differences that carriers and the cooks here do, it's amazing work.
Also, almost all cooks here in XDA will try and give you access to everything the phone itself can do, that's part of the fun of running a rooted OS.

thanks for the tip about trying out the sdk Reno, i'm gonna check it out this weekend. Don't get me wrong, i love all the fun of flashing and its an addiction since 2007 on my HTC 8525/G1/HD2 lol. and i give mad props to all the chefs, god knows if i started messing with code, my phone would be a brick an hour later lol. Android chefs are really good and don't tweak much like winmo chefs do at times which i like. so many builds for winmo you'll find are scraped down to bare minimum because the chefs wanted a bare rom that gave u the "most space and fastest speed" which all went to hell once u install crap you want on it anyway, but half of the features and options have been deleted! thank God android chefs are good with keeping things there.
woohoo sdk fun friday night! will i become a chef? do chefs need to wear the silly hat?

I'll be perfectly blunt you'll need more than just the SDK to get a build made. I only downloaded it out of pure curiosity. You'll hopefully see in the attachments exactly what default Froyo looks like and realise even more what a godsend these guys here are.
I would honestly love to make my own build (more for my own fun and use than for general consumption) but I realise after many hours of reading and research that it's ridiculously hard work and these guys deserve every penny we can afford to donate for their toil.
Going back to the original point though: I think to create one overarching build that upon install you could pick: stock/sense/launcherpro or whatever other flavour there is available out there would actually be impossible. The look of the build is so deeply embedded in the build itself and requires so many different parts of the operating system itself to be changed you would need several copies of each file with the different variations for each look/style you'd end up with HUGE download sizes and it would be more difficult to keep up with when there is an update.
As things stand now, I know I could never drop my Sense builds, I love hastarins kernel tree, and I have my favourite small group of cooks that I follow, and that helps me limit what builds I download and test. Having a couple of small spare memory cards helps and only cost me £20 or so to give me that choice.

Reno i feel that you are correct. i couldn't resist and went to download the SDK after replying to your post. its still downloading a bunch of things and as i read the android developer page i'm enticed to hit the cancel button! I think i'll just go back to picturing the chefs as the magicians and let them entertain, instead of being the guy who tries to figure out all the tricks lol.

[Q] Established android ROM for HD2?

Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..

First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.

yusufm786 said:
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
Click to expand...
Click to collapse
check this out http://android.hd2roms.com/

StephanV said:
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
Click to expand...
Click to collapse
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
leon98408 said:
check this out - link
Click to expand...
Click to collapse
Thanks a lot. That's very helpful. I'll have a look through that

yusufm786 said:
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
Click to expand...
Click to collapse
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!

StephanV said:
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
Click to expand...
Click to collapse
Ah i see. Thanks man - I got a lot to learn

A request to All developers

This is a request to all the developers developing for HD2, If you want a fully working, fully stable build on HD2 with top performance you would have to stop treating your device as Bravo, everywhere i look from recoveries to kernel i see Bravo, Evo, Passion. For God's sake the phone is different from all other snapdragon phones.The display, the drivers etc are different. Also please stop keeping the source of your edited files to yourself, if you open source them, they can be improved upon and HD2 can be made faster and better device. Also developers thing beyond overclocking. There are other things HD2 needs in the kernel. If you waste your energy in just overclocking then i would say its pretty dumb. Just a kind request to everyone. Your device is htcleo/leo not bravo/passion/supersonic. They are similar but not same. use htcleo as device name in build, init rather than bravo/passion/supersonic. Your device isnt a mix of device anymore, its a different device that stands apart

im not a dev but ... yes , is time when all work must be unified.

+1 on this.
All devs should work together and share their results.

Bump.
This thread needs to be looked at and acknowledged. Charansingh is trying hard to get our device working to its best possible method and not just patch everything constantly. If some kernel developers (Tytung, rafpigna, iamgpc, etc.) set up conversations with charansingh, I'm pretty sure all outstanding issues could be worked on and we could even fix issues we didn't know we had. Come on, devs! Work together to bring our HD2s to truly compete with android devices out there as a native solution!

Definitely worth a bump

Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.

rottenjello138 said:
Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.
Click to expand...
Click to collapse
The Nexus is a native Android device. Of course the ROM development will be different. It's a miracle we have Android on the HD2 at all. It was always going to be a painful development process. That said, wise words from charnsingh.
Keep rocking, Devs.

I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.

mzebrowski13 said:
I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.
Click to expand...
Click to collapse
if you read craefully pongster thread,his build still use desire base..from source of desire

ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Hhhmmm I don't want to be a Pongster lawyer And I hope that HE will not feel offended but let me quote some parts of tread Hyperdroid CM7
Drawing inspiration from the Desire AOSP based Custom ROMs
Click to expand...
Click to collapse
Again, THIS is NOT a PORT... its Completely Built FROM SOURCE, Fully Optimized and Tweaked for the HD2!
Click to expand...
Click to collapse

ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
The source is built from the following: Base is Pure AOSP, Framework Tweaks and Settings is Redux, Cool Features & Functions from CyanogenMod.
Click to expand...
Click to collapse
from the gbx thread.

ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Have you bothered checking the source I use? and the device specific stuff by charan for the HD2 in there? I don't use the desire base. The source of the ROM is something any device can use, given the right kernel and proprietary libs the device may need. Just like CM7 is not just for the HD2, but for a myriad of different devices, the source can be used by anyone with the right device specific stuff.
In my ROM, I use the device specific stuff that charan has done for CM7 HD2 (with a few edits for GBX overlays and HD2 specific Settings).
Like charan has mentioned, most of what we currently have here (ROMs) are ports/kangs from other devices. In fact my old SD build was one of them.
His hard work paved the way for a device specific ROM, that being the CM7 RC's he builds (and you can build, which I also do for testing, from source) and the GBX I build now. If you take the source and add the device specific stuff (drivers, ramdisk, kernel, libs) you can build a ROM for other devices using the the device specific stuff available in the CM7 git. (Desire HD, Nexus One, etc. can be built using the source on Git)
As I understand it, from my limited knowledge on this, the device specific stuff is where the difference lies, from the 2D and 3D drivers, to the overlays for every device, down to the kernel for each device.
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.

pongster said:
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.
Click to expand...
Click to collapse
Well said pongster
Sent from my HTC HD2 using XDA Premium App

Hes right,we have to treat our HD2 like a native android device otherwise were not gonna advance that far if we treat it like anougher device.Our HD2s are amazing so lets advance and be happy

I'm in no way a dev, but its great to see common sense prevailing. I wish I had more time to get my head into these ROM's/kernal's etc but I don't. And I for one am eternally grateful for all the hard work done on this site to keep the likes of me interested in the HD2. It's a crackin phone, lets keep it that way!

i agree with you in lots of things but some roms just have to be ported.
htc won´t release a sense build for the hd2 or just a rom to get ported.
guys that want sense just need a ported rom.
and sorry buti dont´t think this is right in the development section.
maybe you should contact them on irc

I agree it would be nice if everything was done just for the LEO, but Im not going to say anything bad about Typoon his ports rock, are uber stable, and anything but half baked.

The reason why the bravo/passion base is used is:
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
d) Sense ROM's aren't open source.
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal.
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!

DarkStone1337 said:
The reason why the bravo/passion base is used is:
Click to expand...
Click to collapse
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
Fixed- We only need to change the fingerprint of the build, same is done for bravo etc using passion fingerprint for gingerbread
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
Fixed - It works
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
Fixed - The CM7 nightlies and RC i am compiling.
d) Sense ROM's aren't open source.
Fixed - For sense Roms it isnt an option
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal. It is there lol
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!

i am not a dev but there are some roms in this forum that we must give credit to as not being half baked like motomans mytouch rom everything work on it and it is very snappy and responsive also typhoons rom is really good too i can see from there rom that there are those who really treat hd2 like a really android phone