Database Users

[DEV DISCUSSION / EXPLANATION] Cyanogenmod Dev relationship?

Is there a reason why the dev community cannot get behind cyanogenmod and still get donated to? Is there some kind of politics involved that will not allow this relationship? I just think I would like to see the effort into one project that is solid, without all the themes and "personal" touches you see with everything else.
In a word it doesnt seem like much progress is being made, except for some screenshots from the dude and an alpha build from eugene. If Eugene, Som, Codeworkxs thedudesandroid, and the rest of the vibrant devs worked on a gingerbread based cyanogenmod, it would benefit everyone.
Move me, flame me, just dont one line answer me.

Yours to change and modify:
https://github.com/CyanogenMod

Ideologies differ. Work ethics differ. I think a move like this would be destined to fail.
Have you personally experienced both Macnut and Nero? Both ROMS are outstanding. I think the more fragmented the ROMS are, the more ideas, experiments, and innovation will occur. I think to push devs to a single common platform would be both stifling and detrimental to the android modding community as a whole.
Besides, all the devs have the same problem... Drivers. Until we start seeing Gingerbread leaks, all devs would have the same stumbling block anyway, whether they are working as one, or separately.

i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!

angryPirate12 said:
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
Click to expand...
Click to collapse
This makes me moist.

d33dvb said:
Is there a reason why the dev community cannot get behind cyanogenmod and still get donated to? Is there some kind of politics involved that will not allow this relationship? I just think I would like to see the effort into one project that is solid, without all the themes and "personal" touches you see with everything else.
In a word it doesnt seem like much progress is being made, except for some screenshots from the dude and an alpha build from eugene. If Eugene, Som, Codeworkxs thedudesandroid, and the rest of the vibrant devs worked on a gingerbread based cyanogenmod, it would benefit everyone.
Move me, flame me, just dont one line answer me.
Click to expand...
Click to collapse
my question for you, is why does it have to be cyanogenmod? Youre asking all devs to collaborate to come up with one big super-ROM, yet it will still only be under the name of one developer, Cyanogen?? This doesnt make much sense.
So basically what youre asking is, since you PERSONALLY would prefer to run cyanogenmod on your phone, you want all other Vibrant devs to concede their own projects to assist your personal favorite developer with his project??
Why doesnt CM help with a new Team Whiskey ROM?? If your answer is because CM is more popular and has more development-power in the Android world, then you have answered your own question in regards to the "politics" that may be behind it.
I feel a lot of people (not necessarily the OP) just seek the "cyanogenmod" title to their ROM, without even really knowing what it is. They just hear the name thrown around all over the place and want to feel like they are in the loop; which is just mindless, in my opinion.
Its great to have several devs, with several different projects. It gives the average user (non-dev) options, and different things to choose from and try.
If you went to a car show, and every car had the same exact engine in it, what would be interesting in that??

what a communist suggestion

I, personally, love that there are many diff ROM's to choose from. I love having that variety. I prefer <tw> ROM's, just because they theme it pretty much how I would theme a ROM (and they scream), If I was even remotely capable of Dev'ing. Eugene makes an awsome ROM too, But not to my personal taste. On my G1 I always used cm ROM's, but the way they work at this point that's not possible for a Vibrant. So I guess what I'm saying is, I'm glad they're not all concentrating on one ROM because we would still be waiting... stuck with RFS !

I just want that Cyanogen bluetooth stack on a regular (sans Touchwiz) Galaxy S rom with TV out. The Bluetoouth stack is the only reason why I am using Cyanogen outside of the speedy OS.
Sent from my SAMSUNG-GT-I9000 using Tapatalk

I get what you mean but I have to say that I love flashing different devs roms & kernels, I would hate to be slave to one idea...I could have gone iOs for that.....get it iOs 4! I kill myself sometimes...
vibrant
GingerR2JL4

TopShelf10 said:
my question for you, is why does it have to be cyanogenmod? Youre asking all devs to collaborate to come up with one big super-ROM, yet it will still only be under the name of one developer, Cyanogen?? This doesnt make much sense.
So basically what youre asking is, since you PERSONALLY would prefer to run cyanogenmod on your phone, you want all other Vibrant devs to concede their own projects to assist your personal favorite developer with his project??
Why doesnt CM help with a new Team Whiskey ROM?? If your answer is because CM is more popular and has more development-power in the Android world, then you have answered your own question in regards to the "politics" that may be behind it.
I feel a lot of people (not necessarily the OP) just seek the "cyanogenmod" title to their ROM, without even really knowing what it is. They just hear the name thrown around all over the place and want to feel like they are in the loop; which is just mindless, in my opinion.
Its great to have several devs, with several different projects. It gives the average user (non-dev) options, and different things to choose from and try.
If you went to a car show, and every car had the same exact engine in it, what would be interesting in that??
Click to expand...
Click to collapse
Agreed. It seems to be the "you want what you can't have" theory. It's going to be funny when there is finally a CM ROM and all these same ppl that wanted it are going to wonder why CM is so plain looking and isn't themed up. It's an endless cycle. CM offers support to multiple devices, which gets their name out there. But I can promise you if you've ran ROMs such as Nero + voodoo, even the best running CM isn't going to "blow it away" in performance, maybe some fun features, but that'll about do it.

I'm satisfied with TWs stuff. All I'm hoping for is that we can get drivers written to do our own ASOP roms, so we can one day have 2.3 and beyond.

im curious about this as well and being that i have no clue, i feel completely authorized to put in my .02 that i thought the primary reason we dont have cm for the galaxy was due to lack of aosp/drivers...

LOL, you sad bunch of folks think I have never flashed a rom on the vibrant? Sure I have, but they are all roms based off of samsuck files, with a theme pushed on top. This requires some skill and understanding, but it does not make you a "ROM D3V"
I am not in any way trying to push everyone to cyanogenmod, I am trying to get the "real devs" to work on things like GPS drivers and such as a whole, to benefit everyone, you think the tricks we learn as a group you cannot then use as an individual? You cannot say I am communist (lmao) because I want the devs to work together, I suppose that what people say about XDA is true, the users who are flaming me make it unbearable to have a real conversation. I mean just look there are several "FANBOY" posts already, and we are on post 13. No wonder the real devs ficking hate XDA. The sole reason I personally like cyan is because of the testing that it goes through, to make sure embarrassing bugs dont happen often. He has developed a rom for my G1, then both my Mytouch's and just miss running it on my vibrant, thats all. My G1 is sitting here running CM 6.1.0 and my phone still sits here on Ginger Clone, the best there is right now.
FYI when there was lack of drivers on the Dream/Magic someone re-wrote them, mmkay?

It has always seemed that the devs share fairly well. While they don't work together on one project, they share what is needed and form teams of likeminded people to push out better and better products. If you want to see what happens when you get everyone together and make them all focus on one big new release look at samsung itself. These small teams can operate with greater freedom to build and release mods and roms as they see fit. Xda is about sharing info and improving our machines. Would we really want to have gingerbread today without all the options and flavors that different dev teams put together. If you say yes, that's fine, but I like the variety and am happy to wait for what's next.
Sent from my SGH-T959 using XDA App

Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General

CM is not really comparable to the XDA devs' ROMs. CM is a complete ground-up build from AOSP. Nero, Macnut, etc are not; they are mods of existing unofficial Samsung ROMs. (Not to imply that Eugene/Sombionix et al's work is anything less than quality).

mindaika said:
CM is not really comparable to the XDA devs' ROMs. CM is a complete ground-up build from AOSP. Nero, Macnut, etc are not; they are mods of existing unofficial Samsung ROMs. (Not to imply that Eugene/Sombionix et al's work is anything less than quality).
Click to expand...
Click to collapse
Yeah, that's the thing. The skill set involved in getting AOSP (and the rest of CM) building properly is a different skill set than modifying a Samsung released ROM.
The approaches are almost entirely opposite - whereas most ROMs here take what the vendor provides and replace the junky bits with stuff that works better, the AOSP-based ROMs such as CM start from a bare bones google source repository that never had any of that junk to begin with.
Both approaches have their merits. As should be obvious by now, the former results in much more rapid progress since you can start right away with a working build from Samsung. The latter approach can take substantially longer, since you don't have a working base to start from (especially with a device like the SGS, which has hardware very different from most CM-supported devices).

Eugene had an AOSP 2.1 rom pretty well built. Needed some kinks worked out, but there didn't seem to be a lot of interest because all everyone wanted was froyo. I'm sure we're probably see at least a couple of AOSP efforts if/when froyo officially drops.

angryPirate12 said:
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
Click to expand...
Click to collapse
Yep, codeworkx and the CMSGS team have stopped worked on 6.1 and (along with Supercurio and others) are working on an AOSP Gingerbread port for SGS.
It makes sense--no point in continuing to try to build a 2.2 without source when the 2.3 source is already out.

[Q] Adding Eris to CyanogenMod Supported Devices?

Here's what Cyanogen said on the Official CyanogenMod Forums.
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.

I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.
We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.

+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.

Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?
Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.

The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.
The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.
I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.
This comes up every so often. I guess one of us can find out what we would need to do at least...

Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.
The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.

Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.
I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."
And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
Cyanogen said:
There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.
An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.
We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for them, and we also spend much time making all of these (sometimes not so pretty) changes co-exist together without breaking other devices. The more eyes on your code, the better it will be.
That said, as much as we’d like it to be, the CMSGS project is not yet an official part of CyanogenMod. There are also a number of other unofficial ports out there which haven’t been submitted to us that we’d love to include. If you’re interested, stop by #cyanogenmod-dev on Freenode. If you didn’t get it from our mirror network or the CM forums, don’t expect it to be up to our standards.
The biggest thing to keep in mind when porting to a new device is to think about how your change is going to affect other devices. This is the biggest reason why we aren’t supporting Samsung devices other than the Nexus S yet. Don’t change hardcoded default values just to suit your device. Use the configuration options available, or add new ones with the original values as defaults. Do a build for another unrelated device after you make your changes (it helps to have another device to test with, of course) and verify it as well. Android was made for this, so do it right.
Like I’ve said so many times before, CyanogenMod is all about the community. And our community can help you too. I’d love to see more of these ports contributed to the project- it’s only going to make things better. We’ve grown from just a mod to what I’d call an “Android distribution” and we need to keep our standards high.
Click to expand...
Click to collapse

Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft

hallstevenson said:
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
Click to expand...
Click to collapse
+1 10 char......

A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices
https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn

Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. Thanks, guys!

It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.

Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,

Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)

gnarlyc said:
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
Click to expand...
Click to collapse
I thought it was a girl

tazzpatriot said:
I thought it was a girl
Click to expand...
Click to collapse
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0

refthemc said:
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
Click to expand...
Click to collapse
nope still a girl
http://www.youtube.com/watch?v=vwIa2S0YQs4

FYI: http://twitter.com/cyanogen/status/45246447385452544
@cyanogen said:
@Algamer we don't officially support the eris, it would be nice if someone doing the porting joined up with us though
about 8 hours ago via web in reply to Algamerhttp://twitter.com/Algamer/status/45235578886815744http://twitter.com/Algamer/status/45235578886815744
Click to expand...
Click to collapse

I think OUR devs are doing just fine. Why change now?
wildstang83

wildstang83 said:
I think OUR devs are doing just fine. Why change now?
wildstang83
Click to expand...
Click to collapse
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...
Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."
Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.

[Q] Gingerbread Source (Glitch fix)??

http://htcdev.com/
What does this mean for us HD2 users?

It means we might have to wait a bit longer for the actual source to come available.. But there might be some interesting things in this ROM. We will know shortly

Sorry to keep asking questions, but what source is needed? I see the source for the GB kernels for various phones - what exactly is missing?
Just trying to understand better.

MikeG4936 said:
Sorry to keep asking questions, but what source is needed? I see the source for the GB kernels for various phones - what exactly is missing?
Just trying to understand better.
Click to expand...
Click to collapse
Asking questions is never wrong .. The source files contain drivers for the different phones, which is why they are all released seperately. Every device has different hardware, and the Desire has the closest resemblence to the hardware found in our HD2. This is also why many think the Desire source will really help in the development of Gingerbread ROM versions on the HD2 (like it did before on the previous Android releases, for example the camera).
What has been released on HTCdev.com (if I understand correctly), is the ROM upgrade itself, and not the actual kernel source. It may seem weird, because it is the only 'official' ROM upgrade that has been put up on HTCdev.com yet. They are not releasing it OTA (over the air) to all Desires, so they had to put it somewhere easy to be found by devs. This is why it has been put up on that page, which might have been confusing (because many would think it actually is the kernel source). As far as I can see, the package only contains the upgrade itself and 2 APK's. Usually it takes a while longer for this to become available, but per Linux license they are obliged to release it. Eventually.
I think there will be some interesting APK's in this ROM nevertheless.. We'll just have to wait until someone (one of the dev's) has explored the ROM thoroughly.

but it can't be to long from now till the sources are released.

BLAST3RR said:
Asking questions is never wrong .. The source files contain drivers for the different phones, which is why they are all released seperately. Every device has different hardware, and the Desire has the closest resemblence to the hardware found in our HD2. This is also why many think the Desire source will really help in the development of Gingerbread ROM versions on the HD2 (like it did before on the previous Android releases, for example the camera).
What has been released on HTCdev.com (if I understand correctly), is the ROM upgrade itself, and not the actual kernel source. It may seem weird, because it is the only 'official' ROM upgrade that has been put up on HTCdev.com yet. They are not releasing it OTA (over the air) to all Desires, so they had to put it somewhere easy to be found by devs. This is why it has been put up on that page, which might have been confusing (because many would think it actually is the kernel sournce). As far as I can see, the package only contains the upgrade itself and 2 APK's. Usually it takes a while longer for this to become available, but per Linux license they are obliged to release it. Eventually.
I think there will be some interesting APK's in this ROM nevertheless.. We'll just have to wait until someone (one of the dev's) has explored the ROM thoroughly.
Click to expand...
Click to collapse
Excellente. Couldn't have said it better. The update's been out for almost a week. And from videos that I've seen, HTC did not upgrade the Sense version to 2.1 or 2.0 for the matter.
But of course all we need is the kernel source.
I'd also like to ask any of the devs:
Will a new kernel need to be compiled when the Desire gingerbread source is released? Hint hint: Rafpigna 2.1?
Also, I'm not familiar with the OC deal, but is it possible to overclock over 1.5 ghz on our HD2? I've seen 1.9 ghz on Desire Z/G2, and almost 1.8 ghz on the DHD.

BLAST3RR said:
Every device has different hardware, and the Desire has the closest resemblence to the hardware found in our HD2. This is also why many think the Desire source will really help in the development of Gingerbread ROM versions on the HD2 (like it did before on the previous Android releases, for example the camera).
Click to expand...
Click to collapse
Does this mean that the the HD2 is on it's "last breath" with Android? Since the Desire isn't getting updated past Gingerbread...
What about Nexus One then? It is pretty much a redesigned Desire.
Or is this necessary for Sense ROMs only, and AOSP ROMs will still work?
Wouldn't it be possible to port something like Leedroid HD then? Since it's on the Desire and it works perfectly..

SilverHedgehog said:
Does this mean that the the HD2 is on it's "last breath" with Android? Since the Desire isn't getting updated past Gingerbread...
What about Nexus One then? It is pretty much a redesigned Desire.
Or is this necessary for Sense ROMs only, and AOSP ROMs will still work?
Wouldn't it be possible to port something like Leedroid HD then? Since it's on the Desire and it works perfectly..
Click to expand...
Click to collapse
With Sense builds it is the end of the road I guess.. At least for any Android releases after Gingerbread. With the other builds I am not sure.. We have quite some driver source available, and with that we can probably simply compile them on the newer AOSP and non-sense ROMS. Sense is really a problem when it comes to source, because it is proprietary software written by HTC (no full source for Sense to simply cross-compile their libs). This is also why it is so hard to make decent Sense-builds whenever a new major Android release comes out. I could be wrong here though.
Let's wait for a dev to come over and shed some light ..

Grr... It's a bad day to own both the Desire and the HD2.

SilverHedgehog said:
Grr... It's a bad day to own both the Desire and the HD2.
Click to expand...
Click to collapse
True.. But I for one never could have dreamed my HD2 to be top-notch more than a year later.. It certainly was one of my best buys ever. Imagine life when we'd still be stuck on that creepy WM6.5

BLAST3RR said:
True.. But I for one never could have dreamed my HD2 to be top-notch more than a year later.. It certainly was one of my best buys ever. Imagine life when we'd still be stuck on that creepy WM6.5
Click to expand...
Click to collapse
Haha, that's true, I guess... I never even got to touch WM6.5 on my HD2, I bought it from Ebay with WP7. Tried it and didn't like it that much. So now I'm wondering which phone should be my primary, HD2 or Desire..

BLAST3RR said:
With Sense builds it is the end of the road I guess.. At least for any Android releases after Gingerbread. With the other builds I am not sure.. We have quite some driver source available, and with that we can probably simply compile them on the newer AOSP and non-sense ROMS. Sense is really a problem when it comes to source, because it is proprietary software written by HTC (no full source for Sense to simply cross-compile their libs). This is also why it is so hard to make decent Sense-builds whenever a new major Android release comes out. I could be wrong here though.
Let's wait for a dev to come over and shed some light ..
Click to expand...
Click to collapse
I'm confused - why would the HD2 be on it's last legs?
People are still developing ROMs for my G1 - hell, there's even a honeycomb rom for my G1. Until people quit developing for the HD2, I guarantee it will be on par with other devices.

captainreynolds said:
I'm confused - why would the HD2 be on it's last legs?
People are still developing ROMs for my G1 - hell, there's even a honeycomb rom for my G1. Until people quit developing for the HD2, I guarantee it will be on par with other devices.
Click to expand...
Click to collapse
It's just the Sense development that will be near to impossible to be perfect.. The rest will be continued as long as there are developers interested in our HD2.

captainreynolds said:
I'm confused - why would the HD2 be on it's last legs?
People are still developing ROMs for my G1 - hell, there's even a honeycomb rom for my G1. Until people quit developing for the HD2, I guarantee it will be on par with other devices.
Click to expand...
Click to collapse
The hd2 development won't die, merely the Sense ROM development unless HTC make an ice cream sandwich update for the Desire (which is unlikely but possible as Google have stated ics has been designed to work on all Android devices to date). AOSP ROMs will probably continue as long as the device stays popular.
Sent from my HTC HD2 überphone

I just went on this sure cause I got an email from htc saying the site launched. Now I know we need the kernel source, but I just noticed this in the kernel source page:
Android 2.3 (Gingerbread) Upgrade for HTC Desire
Or is that not enough?
Sent from my HD2 using XDA App

CM, Splashmod and rempuzzle

Hello,
I'm pretty new to custom ROMs, searched for a while the forum and other source and came to the conclusion that CM7/9, Splashmod and rempuzzle are by far the most popular ROMs for the HTC Wildfire. However, very rarely I found information about the advantages or reasons to choose one over the others.
Hence, could you guys using the ROMs above briefly explain what has driven your decision for that particular ROM?
Thanks!

CyanogenMod7:
Gingerbread 2.3.7
Highly customizable
Lots of themes to choose from
Pretty stable
CyanogenMod9
ICS 4.0.4
A bit less customizable
Lots of themes to choose from
Sorta stable
Rempuzzle
Froyo 2.2.1
Rock solid stability
In my tests, faster than CM7/9
HTC Sense (If you want it)
Can't really vouch for Splashmod, as I've never used it.

gerope said:
Hello,
I'm pretty new to custom ROMs, searched for a while the forum and other source and came to the conclusion that CM7/9, Splashmod and rempuzzle are by far the most popular ROMs for the HTC Wildfire. However, very rarely I found information about the advantages or reasons to choose one over the others.
Hence, could you guys using the ROMs above briefly explain what has driven your decision for that particular ROM?
Thanks!
Click to expand...
Click to collapse
I've started with CM7 when I rooted my Willy, used the stable first and also nightlies, RC's etc. later. I didn't try out many ROM's as I didn't have much time to make a lot of experiments and I've been pretty much satisfied with CM7.
At the moment I'm on the LeWa port which I like much as it feels snappier and faster than CM7. Going to try the Mokee OS port when I find the time as it looks good, too.
In general I'd like to mention a few things (to give you an idea which direction to look first):
CM7 is the most stable ROM. Reasons: it's not only a port but a true ROM developed (also) for the Buzz, huge professional developer community, huge user community, short update frequency, clean structure etc.
Most ROM ports for the Buzz are based on CM7.
CM7 and ports are faster (because lighter) than sense based ROMs (although I've read reports that Rempuzzle was pretty fast, too - but I don't have any personal experience with sense based ROMs)
CM9, although already working and stable, could still be considered as experimental. ICS has been developed for devices with a GPU which our Willy doesn't have - that can't be just discussed away or worked around without any shortcomes.
Sense based ROMs (if I'm not mistaken) are all on Froyo until this point.
There's a lot more to know for sure - but perhaps it's already some basic knowledge to work with.
I'd like to mention that there are some even more basic things, like custom mtd partitions. If you want to tweak performance from the ground up (and don't plan to use a sense based ROM) you seriously should think about it: http://forum.xda-developers.com/showthread.php?t=1233340
I'm sure that a few others will give their impressions and suggestions, too. If you have any questions you can't find answers in the forum: this is a small but still very active community

Thanks for your replies.
As for ICS roms, am I right that the most popular ones are the unofficial CM9, AOKP Milstone 6 Port and [v4] KoolMIUI 2.6.8 Beta 1?

gerope said:
Thanks for your replies.
As for ICS roms, am I right that the most popular ones are the unofficial CM9, AOKP Milstone 6 Port and [v4] KoolMIUI 2.6.8 Beta 1?
Click to expand...
Click to collapse
Pretty much, yes.

Lesicnik1 said:
Pretty much, yes.
Click to expand...
Click to collapse
Which one would you consider best in terms of updates and improvements which are included in future releases?

gerope said:
Which one would you consider best in terms of updates and improvements which are included in future releases?
Click to expand...
Click to collapse
unofficial cm9 for sure.

But what about [ROM][Port][ICS][4.0.4] AOKP milestone 6?
As far as I understand it's based on CM9, so it should receive the updates alike, yes?

gerope said:
But what about [ROM][Port][ICS][4.0.4] AOKP milestone 6?
As far as I understand it's based on CM9, so it should receive the updates alike, yes?
Click to expand...
Click to collapse
It depends lot upon the developer,aokp has been well maintained by tathanhlam66(forgive me if mis spelled) but its not necessary to rebase it on every cm9 release.I guess he will rebase it once a major cm9 update is out.
Sent from my HTC Wildfire using xda app-developers app

SplashMod is very good rom but my rom, BetterSplash, is Better with big B . Today or tomorrow i will post BetterSplash here so wait guys .

A ROM made specifically for the N4

Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!

you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025

aokp is good man...there is no difference

I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse

Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).

Thanks everyone.
simms22 said:
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
Click to expand...
Click to collapse
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
[email protected] said:
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
Click to expand...
Click to collapse
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Ace42 said:
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Click to expand...
Click to collapse
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?

the information is there, screenshots arent needed. but you should stay with cm then, if youre looking for an op and not a rom.
anyways, you do realize that all the nexus 4 roms are built from source? there no need to port roms to any nexus since all the sources are available for every nexus. so to say, all nexus roms are built specifically for the nexus 4, even cm. just because a rom exists on multiple devices, doesnt mean that its ported. most non nexus roms are ported to non nexus devices because they dont have sources available. this doesnt happen to nexus devices.

this is identical with a thread i remember seeing in the gnex forums a while back. anyways, they are all made for the nexus 4. they use drivers that are specific to our phone. if you flash it on another device, it wont work. AOSP is AOSP, that's the point of it. you won't get any extra device specific features if a rom is only built for the nexus 4 vs cyanogenmod which is out for a bunch of phones. the only way that happens is if your phone has a hardware feature another one doesn't ie: NFC.

TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Hi. There are many things to argue here is this post but I will try to help to get you some information to get you on the right track. First off there are two versions if you will of Android, one being "AOSP" or the "Android Open Source Project" and "Google Android". Google Android is what shipped with your device, and has Google owned proprietary in it that is closed sourced, most of the development done in a Nexus forum will come from using AOSP Android. Its the same Android that ships with your device but it does not contain any of Google's proprietary and its completely open-source, however some of the coding needed for a specific devices hardware is not open-source, there's more I can go into on that but I'll stop in short by saying the Nexus4 is probably one of the best devices to be working on platform level coding since all of the binaries needed are properly licensed and most of the hardware coding is open-source. So now that's out of the way. Most of the roms here are forks of AOSP with some being forked from AOKP, CyanogenMod and PA, in order for a developer to build a Nexus4 rom they have to use the provided hardware binaries in combination to the software coding to produce said roms, so ALL of the roms here are built directly for this device. Where confusion come in at is that some of the developers do not have a Nexus4 and build based of the availability of someone being a guinea pig. Also you will have to know whats in you device, such words as "krait optimizations" should not be a hook to get you to try a rom nor should a screen shot since most of the roms look stock besides the few that are themed, ok if they're themed they probably should have a pic, but seriously know your hardware so that you are not just letting a buzzword give you a placebo effect, and remember a roms OP most times doesn't do any justice for the experience you will have from that rom so its best to just try what ever sounds interesting blindly...

TheeWolf said:
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Click to expand...
Click to collapse
you can't really optimize a rom for a specific device.
they are nearly the same for all devices, and there is no point in optimizing it for specific hardware.
what you can optimize is the kernel, the part that contains the device specific drivers and basically controls the hardware. these are already built and optimized for the nexus 4.
but that doesn't mean that fixes and improvements for other devices have negative effects on the nexus 4.
also, device specific changes in changelogs are mostly kernel related.

TheeWolf said:
Thanks everyone.
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
Click to expand...
Click to collapse
Dude, first try and test a rom before you form and vent your opinion based on nothing.

Thank you everyone for the explanations.
gee2012 said:
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Click to expand...
Click to collapse
As I have said, I have already flashed many ROMs, I am not basing my opinion on nothing. I have not opened this thread is not to find out "what is the best ROM" - more than a year of messing with Android and being here in XDA got me understanding there is no such thing, no best ROM. The purpose of this thread is get me some answers, to see if what I am saying is even true.

If Cyanogenmod is the same for every device then riddle me this:
Why is there a different .zip for each device?
You are not going to find a better all around ROM than CM dude. In CM each device has its own tree with many device specific commits and custom changes. You sound very ill-informed asking the questions you are asking; I am surprised you haven't received a lot more flame for it.