Related
I've currently settled down with CronosDroid 2.13 the last few weeks and it's been ok. A little unstable at times (OC to 670ish MHz) and keep having to kill tasks all the time but it's not bad I suppose.
I wanted to try Froyo out and was looking at FroydVillain and Cronos Froyo.
I will try them both myself, but I was wonder what you guys think of FroydVillain 1.4 vs Cronos Froyo 1.02?
Any particular positive or negatives?
Froyd over Cronos
Positives:
Active Development
Dedicated Support
Probably as simple as that really.
Just try Cronos once, then you will come to know !
dreaswar said:
Just try Cronos once, then you will come to know !
Click to expand...
Click to collapse
and what exactly is he meant to do when (and it is definitely a when) something goes wrong?
I love you're argument - it is so based in faith that it is a superfluous statement. You haven't provided a single reason for the OP to use the rom aside from your own arrogance. Please provide something useful to the discussion or don't bother to post. (Edit: sorry to bash you but there are so many cronos users who have no idea what they are talking about and have never even tried another rom)
I would love to hear some genuine reasons for using Cronos (from users who have tried both, like myself) because I actually respected it as a rom, but I do believe with the most recent release of Froyo that the unsupported Cronos release is obsolete.
btdag said:
and what exactly is he meant to do when (and it is definitely a when) something goes wrong?
I love you're argument - it is so based in faith that it is a superfluous statement. You haven't provided a single reason for the OP to use the rom aside from your own arrogance. Please provide something useful to the discussion or don't bother to post. (Edit: sorry to bash you but there are so many cronos users who have no idea what they are talking about and have never even tried another rom)
I would love to hear some genuine reasons for using Cronos (from users who have tried both, like myself) because I actually respected it as a rom, but I do believe with the most recent release of Froyo that the unsupported Cronos release is obsolete.
Click to expand...
Click to collapse
OK OK OK I will accept Froyd was, is and will be ever superior Rom
Sorry to hurt you mate
For your information, I have tried all 4 Froyo Roms (available at present)
btdag said:
Froyd over Cronos
Positives:
Active Development
Dedicated Support
Probably as simple as that really.
Click to expand...
Click to collapse
+1 FroydVillain
I think both are being actively developed and have dedicated support. The thing is all the roms are getting so good now that it really comes down to personal choice. Try both and see which one you like would be my advice.
Neo Cortex said:
I think both are being actively developed and have dedicated support. The thing is all the roms are getting so good now that it really comes down to personal choice. Try both and see which one you like would be my advice.
Click to expand...
Click to collapse
+1
What guys are you saying : Cronos = Hate, what's that ?
Try the 2 Roms and you will have your personal idea.
(Cronos have their site for support and it's very active)
O interesting news that the Cronos project is back. Just be careful as the developer hasn't released his source code (which is against the GPL agreement which the Android platform is a part of, and his linux code isn't available either - once again illegal...). But lets not get into that again.
If Feeyo is providing support on his site I would keep all discussion there as you won't find much favour for the project on XDA at the moment
Edit: I take that back, just seen info about his sources - will see how things work out, maybe Feeyo will come back to XDA in the future and things can move on
This new all makes my first post mostly superfluous now too. My advise is now to try them all (froyo builds) and see which one suits you the most.
Well I've had FroydVillain 1.4 installed all day.
Trying to get used to Launcher Pro... Its cool, but just different. The dock makes a lot of other short cuts obsolete! Maybe thats why it comes with 3 homes screens as default... no way you need 7 with that dock.
What a shame there aren't more icons for it.
I'll let you guys know what I think after a few days time.
Thanks for your input!
Boogwee try here:
http://launcherpro.droidicon.com/
try both and pick. i used cronos for longer as froyd seems to have constant fix-patches which may be good but seems bad.
that said, i'd recommend elelinux.
btdag said:
O interesting news that the Cronos project is back.
It came back the day after he took it down.
Edit: I take that back, just seen info about his sources - will see how things work out, maybe Feeyo will come back to XDA in the future and things can move on
Doubt that. Personal opinion no real reason.
This new all makes my first post mostly superfluous now too. My advise is now to try them all (froyo builds) and see which one suits you the most.
I agree which ROM is better has alot to do which what you like I personally like Cronos better but before there was Cronos I tried the Villain stuff but I PERSONALLY never really cared for their ROMs they always lagged with me but I haven't tried any of their newer ones so the problems I experienced are probably solved.
Click to expand...
Click to collapse
10char.....
I have only ever used the Cronos ones.
I thought about trying a villain rom once, but i don't like the way the devs waffle on like the wideboys of XDA, so i never tried it.
Before Froyo, i only ever used the SenseHero 5.1 roms, which after some previous searching, gave me links and messages from the VR team *****ing about Stickman,
Well I stuck with Cronos for a few weeks but the last update 2.14 slowed it waaaay down do instead of going back to 2.13 I thought I would try the new FroydVillain 1.5 and I have to say it's pretty awesome! SUPER fast.
I'm even getting used to Launcher Pro instead of sense..
Thanks for the link spamianspoon, that's an awesome site..
Hi guys,
my 2 cents:
I used Feeyos Rom from the beginning, cause for my felling they were the fastest.
Since Froyo is out, i tried both, Cronos and Froyd. Till release.. i thin it was 1.0.3 or something, i was not really happy with Cronos. So i tried Froyd, which was bette at this time, but not perfect. It's just a feeling that things in the Froyd Rom take a ( really just) little bit longer.
Since Cronos 1.1.0 my opinion is clear: Go and take Feeyos Rom. It's just as fast as no Rom before at my Hero. Everything is fast and responsive.
Ah but i know one thing i miss in the Cronos Roms: MORE THEMES If you want to have very much nice looking themes you should try Villain.
But since Computerfreak ported his theme to Cronos i'm happy again I think they will be more Themes in the future.
So my opinion: Cronos Froyo
Cheers
Froyd 1.5 would have to be the fastest rom. But then again I've never tried Chronos.
Gotta say ive found Cronos Froyo to be the fastest without lag.
Hopefully MrBang will release a froyo rom, as his 1.5 was the fastest rom ive used.
did someone try the cronos 1.1.1 and froyd 1.5?
bb.
apesgrapes said:
try both and pick. i used cronos for longer as froyd seems to have constant fix-patches which may be good but seems bad.
that said, i'd recommend elelinux.
Click to expand...
Click to collapse
+1
I prefer elelinux also
Sent from my HTC Hero using XDA App
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
yusufm786 said:
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
Click to expand...
Click to collapse
check this out http://android.hd2roms.com/
StephanV said:
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
Click to expand...
Click to collapse
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
leon98408 said:
check this out - link
Click to expand...
Click to collapse
Thanks a lot. That's very helpful. I'll have a look through that
yusufm786 said:
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
Click to expand...
Click to collapse
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
StephanV said:
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
Click to expand...
Click to collapse
Ah i see. Thanks man - I got a lot to learn
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.
I see the 2 major ones are miui and cyanogenmod 7. I have cyanogenmod, but im not sure if i like it. Id like to try MIUI, but i see tons of different ones. Is there 1 official (latest) release for EVO? Thanks. Also, what is a good cyanogenmod NIghtly for evo? And whats different between those and the official release? Thanks.
Lots of new blood on tongiht, ok here we go:
Cyanogenmod has two basic release types: official and nightly.
Official releases are finished products, per say. Everything should work or at least mostly work (sometimes bugs make it in of course).
Nightly releases are just that: nightly. Those are snapshots of what the team is working on _right_now_. Because of that, NOTHING is guaranteed to work. Mind you, usually things do, but it's the bleeding edge line we walk if we want to play with the newest features first.
On the other side of the fence is MIUI. This project is closed source and run from China ... devs there do not post their code, rather post weekly updates fully compiled. From there some dedicated fans translate and port that ROM to us eager US users. There are two known teams who work on MIUI ports: www.miuiandroid.com and www.miui.us. They actually take a Nexus ROM and port it over to the EVO, then add the English translations. Because they are both pulling from the same closed source ... there is really very little if nothing different between them (I've even flashed one over the other).
In addition to the ROM, there will occasionally be "Language packs" released mid week to correct any missed translations (some apps/buttons still in Chinese, or the verbiage improved).
Biggest blemish to MIUI atm is 4G: it doesn't support it. As MIUI is released closed source the porting teams can't add the code .... and as WiMAX doesn't run in China the originating team can't be bothered to add it. If you dont mind not having 4g (maybe your city doesn't support it), everything else works and it's a fantastic ROM.
Both Roms have market apps that can help manage the whole flashing/updating process if it seems intimidating ("ROM Manager" and "MIUI ROM Downloader").
Also, i took awhile to setup a new homescreen on launcher pro, if i do a titanium backup ,will it backup all my widgets and whatnot? Im asking because im going to fresh to update my prl, whatever that is. What does that do? Thanks
It's been 2 years with this phone. I followed the original CM6 nightlies, before it even had camera. Jaybob's black ROM was one of the best I've ever ran.
I followed aosp's journey into CM7, then noticed jaybob becoming an actual developer.
I switched from Decad3nce's kernel to s0be's, and loved it.
I followed ICS, and am still amazed by it.
Sadly, I'm moving to the Evo 4G OG, and putting the best ROM I ever got, AOSP or Jaybob's 2.3, and selling it to a friend who needs a new phone for $10-20.
Thank you guys for everything.
thank you for helping to keep our heroc's alive over the years. please let your friend know if he/she needs any help at all or wants to check out the rom selection available, we will welcome him/her with open arms.
thaaanks
thaaankss