Developers of ROMs - G1 Android Development

Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.

Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.

Agreed! (This text is just to pass 10 char limit)

Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.

but arnt all these builds just different attempts at getting a working 1.5 build?

Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.

well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!

Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.

momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)

harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.

The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?

Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave

I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.

Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.

As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.

momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave

I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.

Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.

Related

Updated "Stock" ROM?

One thing I'd love to see here but really never have is an updated "stock" ROM based on the official HTC and/or AT&T ROMs.
What I mean would be a ROM that looks and feels like the stock ROMs in terms of appearance, configuration, and included software, but which uses some enhanced "under the hood" changes -- newer OS builds, possibly updated software versions, and maybe some "bug fix" tweaks, but no new software, no new interfaces, no new icons, no big changes in behavior.
I think would offer two nice things to the community: a solid ROM for users who want something basic and familiar, and a good baseline for comparing different OS builds and the like.
I have zero cooking experience, however, so I think it's a little beyond my current skills -- and I don't even know if there's some big technically infeasible part of this proposal. I would, however, be happy to help coordinate a project if this idea appeals to anybody with a little more knowledge.
Or, if this idea HAS been done and somebody can point me to it, I'd definitely appreciate it.
I have one of those in my Kitchen, I might release it if I ever get all the bugs out.
3.34 HTC WWE ROM with the Latest Official Blackstone ROM ported into it.
In the mean time, why not request it : http://forum.xda-developers.com/showthread.php?t=410975
Thanks
Dave
typo said:
One thing I'd love to see here but really never have is an updated "stock" ROM based on the official HTC and/or AT&T ROMs.
What I mean would be a ROM that looks and feels like the stock ROMs in terms of appearance, configuration, and included software, but which uses some enhanced "under the hood" changes -- newer OS builds, possibly updated software versions, and maybe some "bug fix" tweaks, but no new software, no new interfaces, no new icons, no big changes in behavior.
I think would offer two nice things to the community: a solid ROM for users who want something basic and familiar, and a good baseline for comparing different OS builds and the like.
I have zero cooking experience, however, so I think it's a little beyond my current skills -- and I don't even know if there's some big technically infeasible part of this proposal. I would, however, be happy to help coordinate a project if this idea appeals to anybody with a little more knowledge.
Or, if this idea HAS been done and somebody can point me to it, I'd definitely appreciate it.
Click to expand...
Click to collapse
Take a look a the NATF(Not A Treo Fan)'s ROMS. They are the ATT version with some of the bloatware stripped out. Much better performance. This was the first ROM I ever flashed because I liked how close it was to stock.
look up the user nothrills. all his roms are stock with performance mods; afcourse haven't seen him release anything of late so don't know where he went off to.

Dear ROM Devs...

Thank you for all of your hard work on the D2. With the X, the competition is stiff, and it seems/feels like there are more of us that "ended up" with a D2 out of a warranty replacement than actually made the decision to buy one.
With that said, I am formally starting a bandwagon for an actual "stock" Android OS ROM. None of this color changing, applications because i like them, better home screen, etc., etc., stuff. I want to see an "actual" Android vanilla ROM for the D2.
I can't be the minority in this request.
I appreciate all of the work that you guys do, I really do. If I had the time to invest in this, I'd build the damn thing myself, but I dont, so I have to rely on you guys.
Thanks.
I'm on the bandwagon.
I believe doing this would require cracking m-shield/efuse in order to get a custom kernel in place, which to my knowledge hasn't been done, nor am I even sure if anyone is actively working on it.
psionicalpha said:
I believe doing this would require cracking m-shield/efuse in order to get a custom kernel in place, which to my knowledge hasn't been done, nor am I even sure if anyone is actively working on it.
Click to expand...
Click to collapse
i'm not asking for a kernel. i'm asking the ROM developers to go stock with their approach as opposed to customizing. That's why i used quotes on "OS". I want a clean ROM that reflects as much as the actual Android OS as possible.
640k said:
i'm not asking for a kernel. i'm asking the ROM developers to go stock with their approach as opposed to customizing. That's why i used quotes on "OS". I want a clean ROM that reflects as much as the actual Android OS as possible.
Click to expand...
Click to collapse
If you root your device you can clean out the stock rom yourself. Follow the remove bloatware guide. Once you clean it out you can install launcherpro which IMO is the best home replacement out there. I believe it will be some time before there is a vanilla rom for the d2. We will always need the dialer and a few other apps that are tied into other blur apps.
MotoBoy said:
If you root your device you can clean out the stock rom yourself. Follow the remove bloatware guide. Once you clean it out you can install launcherpro which IMO is the best home replacement out there. I believe it will be some time before there is a vanilla rom for the d2. We will always need the dialer and a few other apps that are tied into other blur apps.
Click to expand...
Click to collapse
removing "bloat" doesn't cut it for me. i'm already running launcherpro without root and it gets me by. the ROM devs are working hard to bring things back to normal and they're doing a good job. i just don't want to have to pick between a broken phone icon and a black notification bar.
i'm not asking for miracles. i recognize that most of blur is limiting this activity. that's why i'm asking for just a clean ROM. as apks become available and more of blur can be replaced, the ROM will get better.
640k said:
i'm not asking for a kernel. i'm asking the ROM developers to go stock with their approach as opposed to customizing. That's why i used quotes on "OS". I want a clean ROM that reflects as much as the actual Android OS as possible.
Click to expand...
Click to collapse
It is harder than you think. Moto modified many services that build with dependencies on the kernel. If we had access to Motos kernel source, then we could just build the vanilla rom directly with google source and be done. Since this is not currently an option, you need to have services that happen to be compatible with the kernal and Motos current structure which is also difficult. Its easy for simple apps that can be switched out like mail and such. But not everything is that easy to swap out. Pull and replace some services on your phone and your phone won't start, because an alternative will not work because the blur service is expressly called, or expected to function in a very "Moto way".
I don't think people are avoiding the stock approach because they don't want stock, I think it hasn't happened (yet) because Moto has made it difficult. Right now its like a Jenga tower. We keep pulling blocks to see which one won't cause the tower to fall. Pull the wrong one...oops we won't pull that one next time. If we could rebuild it from scratch, it would be much easier, because you could build it in the image you wanted opposed to doing surgery to mimic what you want.
facelessuser said:
It is harder than you think. Moto modified many services that build with dependencies on the kernel. If we had access to Motos kernel source, then we could just build the vanilla rom directly with google source and be done. Since this is not currently an option, you need to have services that happen to be compatible with the kernal and Motos current structure which is also difficult. Its easy for simple apps that can be switched out like mail and such. But not everything is that easy to swap out. Pull and replace some services on your phone and your phone won't start, because an alternative will not work because the blur service is expressly called, or expected to function in a very "Moto way".
I don't think people are avoiding the stock approach because they don't want stock, I think it hasn't happened (yet) because Moto has made it difficult. Right now its like a Jenga tower. We keep pulling blocks to see which one won't cause the tower to fall. Pull the wrong one...oops we won't pull that one next time. If we could rebuild it from scratch, it would be much easier, because you could build it in the image you wanted opposed to doing surgery to mimic what you want.
Click to expand...
Click to collapse
this i get, and recognize. but if you read through current ROMs (all two of them), there ARE tweaks that i just don't want/agree with.
i dealt with this alot with WinMo and i've avoided putting ANY ROM on my D1. blur is so terrible, all i want is my D1 one back.. but in my D2's body.
I think these ROM developers simply have no choice but to do the tweaks they've done because Moto services can't just be taken out, they have to be replaced instead of the original so the phone would still work.
We just have to wait, time solves everything, even Moto
facelessuser said:
It is harder than you think. Moto modified many services that build with dependencies on the kernel. If we had access to Motos kernel source, then we could just build the vanilla rom directly with google source and be done. Since this is not currently an option, you need to have services that happen to be compatible with the kernal and Motos current structure which is also difficult. Its easy for simple apps that can be switched out like mail and such. But not everything is that easy to swap out. Pull and replace some services on your phone and your phone won't start, because an alternative will not work because the blur service is expressly called, or expected to function in a very "Moto way".
I don't think people are avoiding the stock approach because they don't want stock, I think it hasn't happened (yet) because Moto has made it difficult. Right now its like a Jenga tower. We keep pulling blocks to see which one won't cause the tower to fall. Pull the wrong one...oops we won't pull that one next time. If we could rebuild it from scratch, it would be much easier, because you could build it in the image you wanted opposed to doing surgery to mimic what you want.
Click to expand...
Click to collapse
640k said:
this i get, and recognize. but if you read through current ROMs (all two of them), there ARE tweaks that i just don't want/agree with.
Click to expand...
Click to collapse
Apparently you don't get it. As stated, stock Android will require the kernel source, which we don't have.
As a former Ion and Nexus One owner who flashed probably a hundred ROMs, I can honestly say Froyo and root is enough to make me happy. Many of the tweaks custom ROMs offered are now built in (they came from AOSP to begin with) and the hardware has advanced to the point that swapper and overclocking aren't necessary. Frankly I'm not sure what more you could want that isn't possible without root and launcher replacements.
640k said:
this i get, and recognize. but if you read through current ROMs (all two of them), there ARE tweaks that i just don't want/agree with.
i dealt with this alot with WinMo and i've avoided putting ANY ROM on my D1. blur is so terrible, all i want is my D1 one back.. but in my D2's body.
Click to expand...
Click to collapse
I am like you. On my D1 I only used OEM ROMs that I modifed myself. I did the same to my D2 and it runs just like my D1. Their are only two differences. Backup assistant services is still running in the backgroud and I still have the messaging app. I removed all blur widgets and all the bloatware I don't need. If I can get rid of the backup assistant I would be very close to plain ROM. Once you remove everything you can safely you are not too far away from a vanilla ROM.
karnovaran said:
Apparently you don't get it. As stated, stock Android will require the kernel source, which we don't have and likely never will.
As a former Ion and Nexus One owner who flashed probably a hundred ROMs, I can honestly say Froyo and root is enough to make me happy. Many of the tweaks custom ROMs offered are now built in (they came from AOSP to begin with) and the hardware has advanced to the point that swapper and overclocking aren't necessary. Frankly I'm not sure what more you could want that isn't possible without root and launcher replacements.
Click to expand...
Click to collapse
Well said. This is not my first android phone either. I have also used Cyanogen and others. Root is more than enough for me.
Back in the day, the custom Roms were pushing us into new territories, giving us features we didn't already have; that was why I wanted them. Now I have everything I need with stock and root. There are so many replacement launchers, lockscreens, etc. Going vanilla is just icing on the the cake; if it ever happens at all.
All of blur's UI flaws and app quirks hardly bug me much at all; I can happily live with them if I have to. Overall, the Droid 2 is a great phone as it is ( with root of course ).
I think i might get my head bitten off for this but id be happy with a stock deoxed rom with the stupid bloat apps removed.
I've come to like the blur widgets and features, well except for the contacts sync issue with facebook.
jerseyh22accord said:
I think i might get my head bitten off for this but id be happy with a stock deoxed rom with the stupid bloat apps removed.
I've come to like the blur widgets and features, well except for the contacts sync issue with facebook.
Click to expand...
Click to collapse
If you goto droidforums.net and in the Xeudoxus ROM section you will see the xultimate thread which is what you need to deodex a rom yourself. If you have the android sdk installed already it is not much work to do. Just follow the instructions and read through the thread for problems that may pop up.
karnovaran said:
Apparently you don't get it. As stated, stock Android will require the kernel source, which we don't have.
As a former Ion and Nexus One owner who flashed probably a hundred ROMs, I can honestly say Froyo and root is enough to make me happy. Many of the tweaks custom ROMs offered are now built in (they came from AOSP to begin with) and the hardware has advanced to the point that swapper and overclocking aren't necessary. Frankly I'm not sure what more you could want that isn't possible without root and launcher replacements.
Click to expand...
Click to collapse
apparently you don't get it.
you're not reading what i'm asking. there are ROM devs out now, doing the work. they can debloat and use as many stock apps as possible (or as available). i'm not asking for miracles. i'm asking devs not to customize what they're doing.
i'm asking for standard looks, not black themes. i'm asking for stock apps, where possible. i'm asking for it to work.
don't come in here and thread crap because you don't understand what i'm saying/asking.
MotoBoy said:
If you goto droidforums.net and in the Xeudoxus ROM section you will see the xultimate thread which is what you need to deodex a rom yourself. If you have the android sdk installed already it is not much work to do. Just follow the instructions and read through the thread for problems that may pop up.
Click to expand...
Click to collapse
I know, i did it before i ran 928droid's theme and epic's rom to change the text to white in the notification bar. Lost it when i restored my nandroid of stock but i could do it again. Just saying if i flash a rom i want it deoxed
I am working on this. Please just wait.
Newbie here. I have rooted my D2, but I haven't yet installed a new ROM. Is there any way that I can use a D1 ROM in my D2?
Sent from my DROID2 using XDA App
640k said:
apparently you don't get it.
you're not reading what i'm asking. there are ROM devs out now, doing the work. they can debloat and use as many stock apps as possible (or as available). i'm not asking for miracles. i'm asking devs not to customize what they're doing.
i'm asking for standard looks, not black themes. i'm asking for stock apps, where possible. i'm asking for it to work.
don't come in here and thread crap because you don't understand what i'm saying/asking.
Click to expand...
Click to collapse
Maybe I (and others) misinterpreted, but you said stock and vanilla multiple times.
Sorry, but I just don't take well to people starting threads like this. Either do the work yourself, contact a developer directly to inquire about their intentions, or sit tight and wait. It's this kind of "gimme" attitude in forums that scares away talented people.
What the hell? Do it yourself. Are you really acting like this because you don't like black notification bars? If it upsets you so much, learn how to change it. Requests are fine. Acting indignant because you don't know what "I want a vanilla ROM" means is rude.

Official Handler of CM7 D/S

So in case you did did know, Cyanogen has said that they are not dropping D/S support but rather Cyanogen himself was stopping the managing of the D/S branch (he was previously the one in charge of D/S). This is why we are seeing these "unofficial nightlies"
Cwirl has come out and said that the team is looking for someone to manage the D/S branch. They want someone who uses the D/S as their daily.
Has anyone taken this position?
I am hoping Firerat or Ezterry will be the white knight for D/S
Come on some one please.... take charge for D/S
I dont want to make my "Dream" a paper weight which is not wrecked actually ;-)
I believe that Ezterry or Firerat would do that.
A lot of you are familiar (and have asked) why we don't just have/ask Ezterry and Firerat to take over maintainership. While I like this idea, it would be up to them to decide if they wanted to do so, and, personally, I wouldn't want to feel like CM squashed their creativity and personal efforts. They are doing their own thing right now, and deserve all the props to them for it. If they want to take part in CM, then awesome, we'd welcome it. But thats gotta be a choice they make. Their work can be found on XDA, and is currently your best chance of a 100% Gingerbread install for the DS line.​
via:ciwrl at CM
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
konnspiracy said:
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
Click to expand...
Click to collapse
Not to mention I like their stuff way better than anything CM.
konnspiracy said:
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
Click to expand...
Click to collapse
Personally, I would love to see etzerry/firehat to work with CM. So far I've observed all they have to do is maintain an overlay and the rest almost happens by magic and by itself (such as AOSP bugfixes, cm-features, etc)
Also, joining forces in a such scenario like it is now would work better for D/S users.
I hope that they commit their progress to CM also because it looks like that ezterry work is working better than current CM D/S development. It would be better for everyone since there are a lot of CM-users that freakly test every CM-nightly. More people = more fun
However, I do understand ezterry and firehat position. I believe that working apart from CM allows faster development and to get away from cyanogen and cyanogenMOD project shadow...
Personally, now ezterry/firehat development away from CM looks to work great, but in the feature I think I trust more in a big, constantly maintained project like CM
luminoso said:
Personally, I would love to see etzerry/firehat to work with CM. So far I've observed all they have to do is maintain an overlay and the rest almost happens by magic and by itself (such as AOSP bugfixes, cm-features, etc)
Personally, now ezterry/firehat development away from CM looks to work great, but in the feature I think I trust more in a big, constantly maintained project like CM
Click to expand...
Click to collapse
I have never been a fan of CM and done all I can to stay away from his roms and bases but that is just personal choice and the base for my next bit.
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
@Terry & Firerat - Simply, thank you.
Kinda mixed feelings. i think there's a lot to be gained from joining forces, in terms of faster access to bug reports and bug fixes. More eyes on the code can only be a good thing, particularly at the kernel level. At the user level, with the various customizations, not sure if there's much to be gained.
But I gotta admit, I really like the notification bar power widget, and miss it when I'm on a plain Froyo build. (Which right now is only on my TP2. And if I could get a decent/stable CM6.1 for my TP2, I'd run it happily.)
shadowch31 said:
@Terry & Firerat - Simply, thank you.
Click to expand...
Click to collapse
+1 !
shadowch31 said:
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
Click to expand...
Click to collapse
They are all based on CM because CM provides what developers need to do whatever they want. An actively maintained source. That's even one more reason that, independently of Terry/Firehat developing is own ROM or not is always a plus to merge their achievements on CM.
Note that I am not against/favor whatever should Terry/Firehat in particular do. They do whatever they want! I am just using as an example to discuss general android/xda/etc development philosophy
Theres no reason they need to merge. Its not like either team doesn't openly share their source code. New code and bug fixes flow both ways. And in the long run, its always better to have more choices.
Ohsaka said:
Theres no reason they need to merge. Its not like either team doesn't openly share their source code. New code and bug fixes flow both ways. And in the long run, its always better to have more choices.
Click to expand...
Click to collapse
+1 I'm scared if they join CM we will never get their insightful answers to our questions. How many times has Terry or Firerat been the one to shed light on your problem? Most everyone here has benefited or been enlightened by these two devs. I can't speak for everybody but Cyanogen has never wasted his time on my problems. I hope they do whatever they want to do. It's time to buy new phones and I want the phone that these two devs move to next.
I took up Tmobile on their offer for a free G2.....i feel kind of like a traitor.....but i love the phone
hopefully they do keep updating the phone along with cm...im keeping my old one and will continue updating and playing with it.....
and i highly recommend the g2
I agree with shadow... I think the days of CM for the G1 should come to an end. It has been a wonderful run, but yes...it is time for something else for these phones...
Here is what I posted in this thread: http://forum.xda-developers.com/showthread.php?t=916770
"Who cares? I mean really.. I'm not trying to be a douche by any means. But think of this... We have TONS upon TONS of stuff for the G1 already... Metamorphs to make it "look" like Gingerbread, ton of apps, etc...
Why not let the newer phones have their chance too??
I say we take the software that has been bestowed upon us and improve it. Make it fast, more stable, etc. I mean really... Do we honestly need 45 ringtones, 27 notifications, news and weather, and all that extra "bloatware" in these ROMS right out the gate?
I think maybe we should focus on making a ROM or ROMS smaller, faster, nicer, etc. I know I for one don't "need" all that extra stuff in the ROM... And if I did, I could install it my SD card, keeping the ROM lightweight, fast and stable.
Now, I am not developer, but I damn sure am NOT afraid to try new stuff on my phone. Look at my sig... The ROM I'm running is stupid fast and stupid stable, and I still stripped out over 10MB of "extra" stuff, and still have all the functionality that it was meant to have."
**Just an example of some of the "extra" things we could do to these phones... Think of the PSP field... People, including myself, have modded these to the extreme! Lighted triggers, etc... Check out my sig and click on the last link...
Awesome discussion going on here. I really like the ezterry and firerat's work for gingerbread on D/S. These two developers are really superior developers in the android community. They both work at the source level producing totally authentic roms. Also Looking at cm they are also still at the nighlies and we are at alpha. It does take time to port something new and at the speed we are going is really amazing we had basically nothing working at the beginning. Now almost everything works on the ezterry's gingerbread for D/S. What we need now is just some speed enhancement and some bugfixes. I believe over no time we will have a really good gingerbread rom that can be a daily driver. Also there are people working on the CM7 for dream sapphire as well. I am sure we will definately see CM7 stable on our devices as well even if it takes some more time.
shadowch31 said:
I have never been a fan of CM and done all I can to stay away from his roms and bases but that is just personal choice and the base for my next bit.
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
@Terry & Firerat - Simply, thank you.
Click to expand...
Click to collapse
I take a whole different approach. Cyanogen really has been here for us for a very long time. He was not the first, nor he will not be the last great modder. But you cannot say that the impact CM made is not significant. May I ask, one year before now, what mod did you run on your phone? Cyanogen? Dwangs? Enoms? Bens? WG-build? Kings? Hero? I'm willing to say that you probably tried all of them. They all had their ups and downs, but do you know which one of them is still on my nandroid? CM4.2.15.1. For me, that was the most stable build.
Many phones came out since then and devs came and went. Some were skilled wonders like cyanogen and some just copied and pasted bits and pieces. I particularly remember Eclair. It was basically kick ass when we had the first builds out even though everything was broken. I used to use king's 1.9 as it was the fastest. Slowly, everything started falling into place. Live wallpapers were taken apart and optimized, features were added, NCommander helped to reverse engineer the camera, 3D drivers came in (which F*cked up the Live Wallpapers, a problem we still have to this day lol, just try to run the nexus LWP on OE and tell me how crazy smooth it is). The only problem left was the camcorder. By then OpenEclair led by Wes Garner was the best. Finally 1.3 came out and it was amazing. Wes opened a new thread on the very promising OE2.0, but that quickly faded. From that point, I can't remember how much time has passed. People were over the thrill of eclair and going back to donut. Then out of nowhere CM comes out with the test builds of CM5.0.7. EVERYTHING WORKED! Noone else was able to do this. He wrote drivers from scratch. Just ask Jubeh, he was never able to make the camcorder work on his AOSP build. The kernel was a much newer 2.6.32, performance was amazing. It really breathed new life into my phone.
By the time of Google IO when Froyo dropped by, CM was at 5.0.8 and he decided to expand his team from just the Nexus, Droid, and G1 to 7 more devices like the desire and the hero. That is probably when our phones started to suffer a little. Instead of being more tailored to our specific device, it became more tailored to the higher end phones. CM6 finally rolled out and everyone was super exited again. The system required more resources than Cyan's hacked together drivers could deliver. People started complaining, and this is when the complaints about Cyanogenmod really started coming in. When the MT3G OTA rolled out a few months later people in the G1 section had a little bit of a sour taste from CM. People complained and moaned, and hell, some guy even cursed him out on twitter for an issue with MMS (who remembers "FIX THE ****ING GODDAMN SMS"). I think that was the last straw for Cyan, he put the G1 more as a backburner than a daily driver, I mean, Who would you invest time with, a community that cares for your work (Nexus) or one that complains and curses him out (G1)? If we were a little more patient and more supportive I'm sure most of you guys complaining now really wouldn't be.
Since then I've got a G2. I love the phone, and I love CM. Gingerbread is awsome, neocore tops at 58 FPS, quadrant easily reaches 3000, the works. I've really been removed from the G1 section since then, so I can't really comment on ezterry's roms (Somehow my G1 has an exploded battery lol, and I haven't used it in weeks).
I really did not mean to write a story, and thanks for those who took the time to read it, and sorry if anything is out of chronological order. I guess the moral of this whole long story, is that you should treat your devs with respect. You guys are sitting with 3 year old hardware, and just because someone isn't here anymore to defend his work doesn't mean you **** on his work.
Lol, I'm too melancholic, so I 'm just gonna list the things I remember most about this section.
-my first time flashing a radio. My phone rebooted and I was going totally crazy
-use the search! Don't post in development! Your mom is ugly! posts
-"bricking my phone" I spazzed out when I accidentally did a fastboot wipe and my phone wouldn't turn on LOL
-first time I saw the droid red eye boot up on my phone and using LWP's
-the whole incident with Kingklick when he used his winzip skills to copy jubeh's rom, and ended up with all his threads closed. Poor guy (where we got "kanged from")
-Using CM6 for the first time with all the extra options under CM parts!
-Before Firerat the genius came up with custom MTD, we had to run hero roms with system apps in both system and data, and everything else on sdcard!
I better stop now, its getting late lol. I guess my sig sums it up best:
"Thanks to all the devs that make me love my phone!"

Not sure what all the talk is about CM v.X ROM is all about

Hey all,
I have been using this site for all my research on what ROM to run, what Kernel works best, bla bla bla....its the best site by far on the net for the Android platform.
I recently (January 14th) switched over from an Iphone to the Evo 4g and I truly believe that the Droid platform is far superior, especially with the help and dedication to the developers of kernels and roms!
My question is that I keep reading all the "you have to try" and "the BEST rom is" statements about the CM roms. So, I loaded cm v6.1.2 today and maybe its just me, but I am not understanding what all the "gotta have it" is about on this ROM.
4g did not work, i did not have swype, little lines appears on the screen frequently.
I have tried soo many roms/kernels combos, it would make your head spin. I keep going back to Warm 2.2 with netarchy kernel 4.3.1.
Am I missing something?
Thanks!
Well, many people have other phones and CM works much better on them than it does on the Evo. ROM selection is part personal choice, and part maturity of the ROM. Needless to say that if you are flashing, then hopefully you are reading the change-logs and comments to see what the issues are prior to flashing said ROM. Failure to do so may cause you to be confused about what people are excited about when you dislike an individual ROM.
My question is that I keep reading all the "you have to try" and "the BEST rom is" statements about the CM roms. So, I loaded cm v6.1.2 today and maybe its just me, but I am not understanding what all the "gotta have it" is about on this ROM.
4g did not work, i did not have swype, little lines appears on the screen frequently.
Click to expand...
Click to collapse
Hi, TPADriod. Welcome to the wonderful world of Android. I am not an expert myself, but I've been using CM on my Droid (1) for a while and I can give you some opinions about CM from my personal perspective.
First of all, you are right that 4G on Evo is not currently workable on CM. However, I heard that the latest nightly builds already have 4G working, and it's very likely that CM7 will ship with 4G enabled. If you are not interested in experimental build and 4G is a must for you, my advice is to wait until it's ready.
Secondly, Swype is a commercial product. CM cannot and will not violate a company's legal right and distribute someone's work. Swype is currently having an open-beta and you can try getting it yourself by going to their website and sign up for the beta. I've been using it ever since I switched to CM. HOWEVER, when the beta is over, you may need to pay for a license to continue using it. If this is a problem to you, you may want to try reverting to the original EVO (you did back up, right?) Then use Titanium Backup to create a back up of the installer and the Swype app -- I am not sure if it would work, though.
Now, at this point you may wonder why we should go through all these troubles to install a third-party ROM. If you are happy with your un-modified EVO 4G, enjoy using the Sense UI, and have no problem dealing with HTC's update schedule, you have no reason to install CM, or any other third-party ROM on any Android devices.
What CM brings to us, is an experience that's very close to what Google envisions. Some people don't like it -- this is especially true to people who like transition effect,
or richer design elements. The stock UI of Android, before Honeycomb arrives, is as plain as possible. But many people like its cleaniness and no non-sense approach.
In addition, once you install CM, the bloatwares installed by your carriers are gone. Now, some people may not agree that they are bloatwares. But some do. On the other hand, CM put back some stuffs that the carriers may intentional take out, or disallow, ex, wifi-tethering, OpenVPN, etc.
On top of that, CM may enable your phone to be over-clocked. My Droid can be over-clocked up to almost 100% higher than stock, while cutting down battery consumption, and remaining stable.
Last but not least, you get a much better update schedule than you will get from the manufacturer and the carrier. Being over 1 year old, there's little chance my Droid 1 will see the light of official 2.3 update. With CM 7, I've been running 2.3 for about a month. Even though it's a nightly build, I can feel how much faster it is than the stock Droid running Froyo. When CM 7 is finalized, I have no doubt that it will be the best experience I can get from my Droid.
My advice to you is, if you enjoy your EVO as is. May be you should just stay away from CM. However, down the road, the desire from HTC and Spring to keep your EVO update will probably fade. At that time, if you still want to hold on to your EVO, may be you should check out CM again, and it may give your EVO an entirely new life.

[Q] Differences - Prime and Revolver

What is the difference between the 2 ROMS?
When I do a search all I see are comments like "I'm using X and it's great!"
If there's a list of ROMS with notes about what makes one so great over the other that would be appreciative.
I would like to know this as well.
robojerk said:
What is the difference between the 2 ROMS?
When I do a search all I see are comments like "I'm using X and it's great!"
If there's a list of ROMS with notes about what makes one so great over the other that would be appreciative.
Click to expand...
Click to collapse
I think an even better question is "What is the difference between STOCK, Revolver and Prime?"
Revolver 2.5's changelog contains "Improved battery life". Compared to what? Stock 3.2 (8.6.5.9)? Prior Stock 3.2? Prime? Revolver 2.1?
Similarly, PRIME 1.8.2 changelog shows "Choice of Touchpad Circles or Mouse Arrow" and "Lots of bugs fixed (Rotate, Compass, Wifi disconnects)", etc. Are these not in the STOCK 8.6.5.9 as well? (yes, they are)
Disclosure: I've run all versions and don't see much difference between any of them, but I'm currently on PRIME 1.8.4
jhanford,
Good point. That's what I do not understand about these "custom" roms. Seems like they offer the same functions/features as the stock rom so I do not know what exactly is the advantage of using them.
Install them and test them yourself, the proof of wether or not they are better can only be judged by your own user experience and not by what others proclaim.
I noticed a significant performance improvement after flashing Revolver compared to stock.
My browser also no longer randomly locks up and quits when going to sites with flash advertisements. YMMV, of course.
There's not really much difference between the three of them since the source code isn't released and not a lot can be changes. The latter two "custom" roms just have a few tweaks included that make it slightly faster and they usually include special kernel modules such as tunneling, governors, and sound improvements/fixes.
I've ran all three and the difference is minimal as of the current firmware since a lot of stuff is now fixed. Before 3.2 Prime and Clemsyn/Revolver were a lot more useful since IMO they were a lot faster than the official version of 3.1.
I am currently on latest version of Prime but very tempted to give Revoler a try. The only thing stopping is that I do not want to waste the countless hours that I put in to create the "Hubs"
I don't think you'll see significant customizations until Ice Cream Sandwich and the next generation of tablets come out. If you look at the overall history of custom ROMs on Android, they've basically fallen into two camps:
1. Taking something from a newer device that's not officially available for given older device and porting it. That can be new versions of the OS itself, or it could be vendor customizations like newer versions of Sense in the HTC world. Right now, all Honeycomb tablets are getting fast updates to the latest version. As for vendor customizations, there aren't heavy customizations to begin with. Vendors are mostly competing on hardware design right now, throwing in a few widgets and apps that may or may not be useful. But usually customization ports stay within a brand (i.e., an older HTC Sense device gets a newer HTC Sense version). That can be for both technical and legal reasons (even within vendors it might be a legal gray area, but it's generally tolerated). But we're still in the first generation of Honeycomb tablets for all vendors, so even the small customizations that vendors are doing are already on the devices in question.
2. Building a customized ROM from the OS source, aka Cyanogen. Since Honeycomb isn't open source, no dice there. ICS is supposed to return to an open source license.
I don't mean to trivialize what the authors of the custom ROMs that do exist have accomplished. I haven't even tried them yet. There even may be significant improvements they have been able to do within the limits of what they have. But overall, it's going to be nothing like what exists on the phone side, where vendors are improving their custom skins from one generation to the next, there are 3+ major generations to work with, and the source is available. Tablets will get there in a generation or two.
Also remembr that the custom roms are deodexed. The hulu flash mod only plays well with the deodexed roms. But really there isnt much differences bc there is no source so that limits the dev capabilities for now
Sent from my Samsung Epic
ajamils said:
I am currently on latest version of Prime but very tempted to give Revoler a try. The only thing stopping is that I do not want to waste the countless hours that I put in to create the "Hubs"
Click to expand...
Click to collapse
What hubs do you speak of?
Rackers said:
What hubs do you speak of?
Click to expand...
Click to collapse
Check the thread here.
Back to topic: I took the plunge and installed latest Revolver. So far, I have not found any difference between Revolver and Prime or maybe I just haven't tested it enough yet.
Have you noticed any difference in battery life between the two?
Rackers said:
Have you noticed any difference in battery life between the two?
Click to expand...
Click to collapse
Not really. Then again, I haven't used it much since I flashed revolver.

Categories

Resources