Hey everyone, I know there are quite a few threads about different froyo roms, whether it's Kaos vs. Nonsensikal or individual froyo threads, but I didn't see a poll anywhere. Was wondering which rom people are currently using, and their opinions of that, plus other ones they have tried. This could be a good place for people to share their froyo experiences and help others decide which one(s) they'd like to try themselves!
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Froyo Poll!
- Thread starter cmotion
- Start date
-
- Tags
- htc droid eris
I ran Kaos for a while (v29 through 35.1) then wanted to try something else, went with Tazz_v8 and it was pretty good, didn't seem as smooth as Kaos on my phone. Just flashing the newest Nonsensikal 8.2 Black theme now as I've heard good things about listy's roms. Setting it up as I type...
Praetorian
Well-Known Member
Just flashed nonsensikal 8.2 so we'll see how it goes.
pkopalek
Android Expert
CELB is the most well-built CM Froyo ROM. Kaos is excellent, and he makes amazing ROMs, but his is a mixed AOSP-CyanogenMod Build.
CELB is directly synced with CyanogenMod (and therefore all of the MM's themes, the battery tweak, etc), and Conap has his lights fixed up better than anyone else.
Nonsensikal offers a nice theme, but you can get MDPI CyanogenMod themes anywhere. I'm not impressed. CELB is most functional (LED and Trackball lights working, as well as all CyanogenMod features) and I trust Conap a lot. I trust Kaos too, but I prefer the pure cyanogenmod over the AOSP/CM mix.
CELB is directly synced with CyanogenMod (and therefore all of the MM's themes, the battery tweak, etc), and Conap has his lights fixed up better than anyone else.
Nonsensikal offers a nice theme, but you can get MDPI CyanogenMod themes anywhere. I'm not impressed. CELB is most functional (LED and Trackball lights working, as well as all CyanogenMod features) and I trust Conap a lot. I trust Kaos too, but I prefer the pure cyanogenmod over the AOSP/CM mix.
I really like CELB as well, but it wasn't until the last few days that he had trackball flash as notification working, and I strongly prefer that. I'll be flashing 3.0 tomorrow, I think, to try it out again. I will say that I was a huge fan of the 2.1 CELB that Conap developed.
I haven't tried any of the themed Nonsensikals, but the vanilla is very, very good. I've been running 7.0 for the last week - it's been rock-solid.
I ran Kaos for over a month but, at this point, I don't think that I'll go back. I don't think that he tests his releases as strongly as he should. He is regularly putting out releases that break the camera, or GPS, whatever. I think that all four of them do this occasionally, but it seems to be pretty regular with Kaos. I've also had weird trouble with the market in Kaos - I never get notified of updated releases until I enter the market manually. I definitely do not have that problem with CELB or Nonsensikal.
I haven't tried Tazz, and probably won't.
My $0.02.
Just an FYI on my trackball fix...it's been implemented in Tazz's rom too and I have sent the needed files for Nonsensikal so should be in his next release if he decides to use it.
Oh and also I voted for CELBFroyo!!!!!
The source code that htc used to make the trackball "pulse" is not open source so we don't have it. The file from the 2.1 rom doesn't work with the 2.2 roms correctly so we had to edit the aosp code for the notifications. I personally could not find out how htc got it to "pulse" so I had to go with just a flashing trackball.
Batbriel
Android Enthusiast
Thank u so much for answer my question, that make sense, I'm happy that the track ball works now, its just that I was curious about the pulsing thing
thanks again
S
Sk1ppy
Guest
I've been rocking CELBFroyo for a long while now, nothing's wrong with it, that I've noticed, so it's perfect for my day to day use.
The only thing that I have noticed is the green LED stays on after the phone is fully charged and you pull it from the power until you turn the display back on.
S
Sk1ppy
Guest
So I'm back on nonsensikal 8.2 just to see if I could really tell a difference and ONCE AGAIN using launcher pro plus as I do with all the roms I use can tell no functional advantage or disadvantage from Kaos Froyo. all my apps open up with the same speed and function the same. scrolling identicle and quite frankly seem to be a function of the scroll settings. Both 100% stable (I never get reboots or rom related fc with either). Sure some minor features and themes change but overall the experience is the same (as are benchmarks once again which honestly havent changed much for both roms in several updated versions). If there was a vote for tie I'd have voted that. at this point glad to have the round battery and cute little android on the notification pulldown bar with nonsensikel yet STILL wishing I had the HTC clone keyboard I'm use to and 3d gallery from Kaos Froyo. I'm sure I could flash/push both of them somewhere sometime (as I could do the same for theming kaos). I'm going to stick with my opinion for the most part a good eris froyo rom is a good eris froyo rom with little funtional difference.
I have used the HTC_ime_mod keyboard (lowres_v22_experimental) on every Froyo ROM I've used. It takes up more screen real estate than other keyboards, but I have fat fingers, so I need that; plus, I prefer shift-key syms versus toggling between keyboard layouts that other keyboards require. And, I sometimes prefer to do things one-handed, and having a phone-keypad with XT9 is handy.
eu1
... but, back on topic.
At this point, I can't say I have a "favorite" - so I didn't answer the poll. Compared to where we were just a few short months ago, they are all vastly improved. But I will say that the re-introduction of bugs - camera, gps, et cetera - in certain ROM series seems disconcerting; and moreover, when ROM releases become nothing more than exercises in applying themes, I start to lose interest quickly. (IMHO, that's what happened to Tazz v3 - v11).
I did just switch to CELB the other day (2.9), and as soon as I got it 100% configured, 3.0 was released, so I did an overlay install of that (but with a /data/dalvik-cache and manual /cache/dalvik-cache wipe) - something I usually try to avoid.
I did this mostly because the level of professionalism Conap displays in his posts - detailed changelogs; maintaining a github source tree; kernel development work; providing improvements and changes that other devs adopt; using a hosting site that publishes MD5 sigs ... the list goes on and on. I assume that if folks are careful in their release process, they probably also exercise the same care in their development process. (And similarly, if they are sloppy with their release notes, then ... well, you get the idea.)
If there is one thing which will make me go back to a 2.1 ROM, though, it is the "rild" segfault problem which seems to affect every Froyo or CM5/6 ROM. (This is the "call appears to drop, but it didn't" behavior). Drives me nuts; after all, the Eris is a phone first, and everything else afterward.
eu1
At this point, I can't say I have a "favorite" - so I didn't answer the poll. Compared to where we were just a few short months ago, they are all vastly improved. But I will say that the re-introduction of bugs - camera, gps, et cetera - in certain ROM series seems disconcerting; and moreover, when ROM releases become nothing more than exercises in applying themes, I start to lose interest quickly. (IMHO, that's what happened to Tazz v3 - v11).
I did just switch to CELB the other day (2.9), and as soon as I got it 100% configured, 3.0 was released, so I did an overlay install of that (but with a /data/dalvik-cache and manual /cache/dalvik-cache wipe) - something I usually try to avoid.
I did this mostly because the level of professionalism Conap displays in his posts - detailed changelogs; maintaining a github source tree; kernel development work; providing improvements and changes that other devs adopt; using a hosting site that publishes MD5 sigs ... the list goes on and on. I assume that if folks are careful in their release process, they probably also exercise the same care in their development process. (And similarly, if they are sloppy with their release notes, then ... well, you get the idea.)
If there is one thing which will make me go back to a 2.1 ROM, though, it is the "rild" segfault problem which seems to affect every Froyo or CM5/6 ROM. (This is the "call appears to drop, but it didn't" behavior). Drives me nuts; after all, the Eris is a phone first, and everything else afterward.
eu1
Podivin
Android Expert
I agree EU1, regression testing (checking to make sure what worked before still works) in some of the ROMs seems to be lacking. I'd think that after fixing any given problem a couple of times that you'd put it on your list of things to test before you release a new version. If it's one of those problems that only happens when you stand on your left foot while facing east on the day of the full moon, then I can certainly understand not finding it during testing - but really, how long does it take to test the camera/gallery, and to see if the GPS locks on. I'm afraid some spend too much time making sure the new stuff works, and not enough time making sure that everything else still works...
Just wanted to let you guys know that this thread convinced me to try CELB tonight. I definitely agree that Tazz and Nonsensikal seem to push out a lot of cosmetic/theme updates, and I think Kaos is going to be focusing more on his sense project now. I'll let you know how it goes!
Praetorian
Well-Known Member
I also switch to Celb after feedback from this thead a few days ago and so far its been working really well. I don't really care about all the themes' and what not. I just want a stable rom.
I don't complain about anybody's method of testing considering they are all FREE and none have to make these available to us. I started with CELB froyo but it rebooted on me several times randomly when Kaos didn't on 3 versions so I just stopped flashing it but it performed well otherwise, which is to say like the others I've tried at that point (haven't tried since v2.5)