Related
Hey guys, i searched on google for this question but i wanted to listen the XDA members and developers opinion about this subject...
What is the huge difference (for our Defy) between CM7 and CM9?
i try both of the roms and i think CM7 with android 2.3.7 is a lot better than CM9 which is 4.0.3 and i cant find any good advandage for CM9, so now i still use CM7 because of its smoothness and stability..
What do u think?
thanks and sorry for my english =p
4.0.3
I upgraded from CM7 2.3.5 (Green Lens) to Eppy's CM9 ICS 4.0.3 5th March Nightly (as well as the latest Google apps package). Followed the instructions to a tee and have not had one FC or any issues to report.
Pros
The battery (deep sleep) is amazing.
Battery life is extended by about a day and I am using the phone and 3G more than previous.
Camera Fine
Video Camera (recorded 3 x tests of 5 -7 mins) and no problems
Cons
The only negative is on screen custom brightness the capacitive buttons are not illuminated. But I know where those bad boys are even when they are not illuminated.
I was massively sceptical and reluctant of upgrading to ICS after reading all of the issues people were having, however follow the Guide and all is sweet.
I recommend it!
thanks for your quick answer, but i mainly wanted to ask what is the main difference between the two roms. I cant see something very different and also in Quadrant test with CM7 i get score 2300 but with CM9 only 1750. I dont know why, i thaught that newer versions should get higher score...
I think Quadrant isn't capable of using all the processor while in ICS, I remember reading that video acceleration wasn't working 100% either
I was using CM9 for a time.. but after it make some lags and using 100% of CPU, i decided return to CM7.1 .. For me CM9 has many bugs yet.
The HUGE difference is that CM7 is Gingerbread, while CM9 is Ice Cream Sandwich (more or less, as both are running on a Froyo kernel).
So CM9 brings most of the ICS's goodies: better battery life, better interface, optimisations, etc. and a few still unsolved bugs.
I'll try it too this weekend or the next (depending on the available time).
Cheers!
I saw this thread over at the Galaxy Nexus forums, and since I figured more people than just me might want to know more about the different ROMs, I thought it was worrth a thread here as well.
What I'm interested is a quick reference thread for the various Jellybean ROMs. Run by who, what's the aim, etc. Basically a quick reference guide to assist people (like me) decide which ROM fits my needs.
So far, these are the Jellybean builds that I know about for the TF101:
Team EOS 3 Jellybean nightlies
RaymanFX's 4.1.1 AOSP builds
CM10 preview edition
JellyBro (CM10 kang)
AOKP KANG
Let me know if you see anyone missing.
It would be nice for each ROM to have a a post which lists its key features:
Aim of the ROM. Tweaks, Stability, Speed, AOSP-like cleanness, etc
State. In active development, experimental, mature, stable, abondoned, etc.
ROM base, if any. Based on AOSP, AOKP, CM, etc.
Release-type/frequency: Nightly, interval, fixed releases, etc.
Non-stock/AOSP features. Swag, Toggles, Theming, OCing, etc.
Basically enough info to assist making a decision, without aiming for pages and pages of stuff which noone will ever bother to write (or read). See this post for an example of what I'm thinking about.
Feel free to recommend a non-default kernel for the ROM, but the focus should be on what the ROM itself offers out of the box.
Sounds good? Anyone wants to give it a go?
User summaries of the various ROMs.
I'm not guaranteeing that I will be able/willing to include all reviews here. If things get out of hand, I will edit this post to indicate so.
Team EOS 3 Jellybean nightlies:
2012.08.02: josteink
2012.08.02: fone_fanatic
RaymanFX's 4.1.1 AOSP builds:
None
CM10 preview edition:
None
JellyBro (CM10 kang):
None
AOKP KANG:
2012.08.02: K900
I've been meaning to make a thread like this, but I still have yet to find the time.
I read through all the JB threads about a week ago and Team Eos seemed to have the least amount of bugs so I chose it over the other options.
I'll start off by saying I've been using it daily since build #53 [2012-07-24] and I'm currently on build #54.
That said, here's what I've noticed so far:
Speaker volume is a bit low.
When using the HDMI out cable, sound plays via TF101 speakers, not TV speakers.
Video effects (Silly Faces) in Camera cause camera to crash.
GPS doesn't work.
Other than that, it's a very stable rom and working great. Dock functions 100%. Very responsive, stable and fast.
Also I'm using Guevor's JB Kernel 693. I just noticed 696 was released yesterday, so flashing that now .
Feel free to ask any questions about the rom. Maybe some time next week I can flash all the JB kernels out there and put them through their paces .
Note this rom is a GREAT daily driver, unless you really need GPS or use HDMI out very often, I highly recommend it.
I'm also running Team EOS nightlies and I'm very happy with it.
Here's my quick summary:
ROM: Team EOS nightlies
Non-stock/AOSP features.. Notification toggles. Overclocking. (Themes added in build #55?)
Aim...................... Stability
ROM base................. Team EOS
State.................... In active development
Release-type............. Nightly
Build(s) tested.......... 2012.07.23 to current (2012.08.01). With and without dock.
Not working / problems:
Audio generally low. (Seems to be a general JB problem across devices?)
HDMI audio out
Have encountered 2 sleeps of death while using it for around 2 weeks.
Everything else seems to be working.
My only complaint so far is lack of a status-bar battery-widget for the dock, like you have in Megatron (ICS). But I don't think any other of the JB ROMs available has that one either.
Great idea!
Will keep this thread under close observation :good:
CalvinH said:
Great idea!
Will keep this thread under close observation :good:
Click to expand...
Click to collapse
If you try any of these ROMs out, feel free to contribute
josteink said:
I'm also running Team EOS nightlies and I'm very happy with it.
Here's my quick summary:
ROM: Team EOS nightlies
Non-stock/AOSP features.. Notification toggles. Overclocking. (Themes added in build #55?)
Aim...................... Stability
ROM base................. Team EOS
State.................... In active development
Release-type............. Nightly
Build(s) tested.......... 2012.07.23 to current (2012.08.01). With and without dock.
Not working / problems:
Audio generally low. (Seems to be a general JB problem across devices?)
HDMI audio out
Have encountered 2 sleeps of death while using it for around 2 weeks.
Everything else seems to be working.
My only complaint so far is lack of a status-bar battery-widget for the dock, like you have in Megatron (ICS). But I don't think any other of the JB ROMs available has that one either.
Click to expand...
Click to collapse
Check out Dual Battery Widget from the play store. It has an option for having the dock battery level show in the status bar.
Also I'd like to add I haven't had a single SOD on Team Eos nightlies (been on since #53). But I have had a few reboots, all but 1 have occurred while not using the tablet.
Sent from my Transformer TF101 using xda premium
Officialzies for AOKP
Aim of the ROM. Tweaks, Stability, Speed, AOSP-like cleanness, etc
AOKP.
State. In active development, experimental, mature, stable, abondoned, etc.
In development.
ROM base, if any. Based on AOSP, AOKP, CM, etc.
AOKP.
Release-type/frequency: Nightly, interval, fixed releases, etc.
Frequent releases but no fixed timing.
Non-stock/AOSP features. Swag, Toggles, Theming, OCing, etc.
AOKP.
I've tried both AOSP build 3, and CM10 Kang.
I am eagerly awaiting a stable jellybean rom I can daily.
Using RaymanFX's 4.1.1 JB
Hi guys, thought I'd share this info. I'm using RaymanFX's ROM and overall it's running well. My only issue so far is that Google Now crashes right after launching. It was working before I started adding new apps, so I'm guessing there is a conflict with another app. Unfortunately I don't know which one it is. I'm guessing maybe gmail, Google maps, or Google +. I haven't tested the HDMI or used in the dock yet but WiFi and graphics seem good. The ROM itself is extremely lean, no bloat to speak of.
I had to flash the ROM a second time to get it working but it's possible that I goofed it up the first time because it does take a bit to do the initial boot and I was getting impatient and thought it locked up and rebooted.
I'll probably try the EOS ROM next.
Nonek said:
Team EOS nigthly.. Rayman has not updated this one in awhile and has been working on other projects. I'm not sure actually how good CM10 is, but I've run both this and TeamEOS and I changed to a TeamEOS / KAT 1.14 (now) combo and I have never looked back.. TeamEOS has the most fleshed out version of JB in my humble opinion.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
If just install the rom 0.7 from raymanfx. The first time from me i root my tf101 !
It work great, some small functionnality are missing on the keyboard but it gives a second life to our baby.
Sent from my Transformer(4.2.1 rom 0.7) using xda app-developers app
Yep, I' using 0.7 from Raymanfx also. Its great to have the mutli-user support, but I think it comes with significant overhead and I'm not sure the TF101 can handle this.... still testing and will keep everyone informed.
Hey Guys!
I am pretty new to the world of flashing ROMs, and am trying to experiment as much as I can! I recently rooted my phone (myTouch 4g) to escape the HTC Sense bloatware and kind of escape the gingerbread environment and use custom ROMs that people have developed. Of course, I've had my phone since 2010, and its been working great since. Not looking forward to getting a new phone anytime soon (it does what I want it to do well).
That being said, I currently am experimenting out CM7.2, was curious to hear what ROMs people who use the myTouch 4G as their daily drivers use. I am considering trying out one of the ported CM10.1 ROMs later tonight.
Looking forward to hearing from all of you guys!
~Darkgiants
Last Cyanogenmod 7 nightly.
I might also recommend Coderzs 4.2.2 Slimbean, Team Inferno's ShenduOS 4.2.1, or my AoCP 4.2.2 lol.
For ICS I recommend Synthetic Nightmare's AOSPx. Also I'm porting a CyanogenMod7 Type of rom, but with more features
Whatever I tried to install on it (including few JB-based ROMs) I always go back to CM7. Anything else is either less stable or uses battery or something is not working well (like camera on JB).
darkgiant said:
Hey Guys!
I am pretty new to the world of flashing ROMs, and am trying to experiment as much as I can! I recently rooted my phone (myTouch 4g) to escape the HTC Sense bloatware and kind of escape the gingerbread environment and use custom ROMs that people have developed. Of course, I've had my phone since 2010, and its been working great since. Not looking forward to getting a new phone anytime soon (it does what I want it to do well).
That being said, I currently am experimenting out CM7.2, was curious to hear what ROMs people who use the myTouch 4G as their daily drivers use. I am considering trying out one of the ported CM10.1 ROMs later tonight.
Looking forward to hearing from all of you guys!
~Darkgiants
Click to expand...
Click to collapse
I use Albinoman's 8/24 build of AOSP 4.3 / CM 10.2. It has a few very minor issues but in daily use I find it's very stable...
too stubborn
Too stubborn to use CM7 I fought installing it and keep working with SlimBean 4.3 even though it is still buggy, well mostly for me. I should just back down to 4.22, but hmm here comes that stubborn issue.
I was on a small vacation, and now am about ~7 days till I move into my college dorm and start my college life. Here are few things I figured I should mention:
I am currently using the CM10.1 AOSP JellyBean ROM by albinoman887 (http://forum.xda-developers.com/showthread.php?p=40665477), so far, its been awesome!
Though, there are few concerns about this ROM as a daily driver:
1. The battery life, it really does die out way too fast. It obviously is a concern for me, being in college, I would like to have something mobile and something that can last me an entire day without having to plug my phone into a charging unit. Of course, I was not expecting a perfect ROM for battery life that would be capable of running the latest Android, so all in all, the battery issue evens out, and should not be a shocker to anyone trying out the ROM.
2. I currently am running everything off of a 8GB Micro SD card, which is now full (I am waiting for my 32GB card to come in within the next few days), but when I do use apps such as SnapChat, or Instagram, it prevents me from using my camera with various errors every time. I suspect this to be the full SD memory card, I will make sure to post an update on this issue.
3. The ROM itself is FAST. I mean FAST. It really sets a definition of "multi-tasking" on the myTouch 4G.
There is a new September update for this ROM (I am going to install this update once I get my new SD card) and will also touch on how the update is, and what was resolved. As of right now, this ROM is beautiful, does require a bit of elbow geese to configure the settings to your likings, but that is the payoff.
I have tried CM7 briefly, escaped the ROM, its the most stable ROM anyone can ask for, but I personally don't want to go back to Gingerbread.
Thanks a lot XDA forums for allowing the opportunity to mess with our phones!
I bought myTouch 4g about 2 years ago. Sense Rom was installed for most of its lifetime; mysense (stock), Sense 3, then Sense 3.5, and now sense 4.1. Currently using ViperTouch 2.1.4 sense rom it is the most stable sense rom I found where all the hardware are functional. Battery life has not bad when keeping in 2G mode. I switch it to 3G with I need to browse something. Before ViperTouch I used CM 10.1 from albinoman887 for about 3 month to try out JB, it was really smooth and clean lightweight. I decided to go back to Sense after headphone heatup, camera and mic not working properly. I tried out CM 10.2 Android 4.3 albinoman887, it was smooth for the most part, but i couldn't use it as daily driver same 10.1 issues were resolved. So Sense 4.1 ICS is my current daily driver.
icyknight said:
I bought myTouch 4g about 2 years ago. Sense Rom was installed for most of its lifetime; mysense (stock), Sense 3, then Sense 3.5, and now sense 4.1. Currently using ViperTouch 2.1.4 sense rom it is the most stable sense rom I found where all the hardware are functional. Battery life has not bad when keeping in 2G mode. I switch it to 3G with I need to browse something. Before ViperTouch I used CM 10.1 from albinoman887 for about 3 month to try out JB, it was really smooth and clean lightweight. I decided to go back to Sense after headphone heatup, camera and mic not working properly. I tried out CM 10.2 Android 4.3 albinoman887, it was smooth for the most part, but i couldn't use it as daily driver same 10.1 issues were resolved. So Sense 4.1 ICS is my current daily driver.
Click to expand...
Click to collapse
You should try 2.5.3, its smoother
Sent from my myTouch 4g using xda app-developers app
Amazon had a delay with my SD card! I will get it tomorrow, expect an update post within the next two days!
Sent from my myTouch 4G using xda app-developers app
I am using AOCP now but currently looking for a bug-free ROM.
As far as I know, there are still a few bugs in 4.2.2 including:
1. Headset heat up when plugged in.
2. Green line in camera.
3. Signal drop after a missing call.
4. Camera flash delay.
Is there any 4.1 and above ROM without those problems? Please let me know. 1. and 3. is really annoying to me. Thank you!
I am using PAC rom . it's really awesome
Sent from my GT-P3100 using xda app-developers app
pshadoww said:
I am using AOCP now but currently looking for a bug-free ROM.
As far as I know, there are still a few bugs in 4.2.2 including:
1. Headset heat up when plugged in.
2. Green line in camera.
3. Signal drop after a missing call.
4. Camera flash delay.
Is there any 4.1 and above ROM without those problems? Please let me know. 1. and 3. is really annoying to me. Thank you!
Click to expand...
Click to collapse
I think AoCP only has the Signal Drop?
N_otori0us_ said:
I think AoCP only has the Signal Drop?
Click to expand...
Click to collapse
Yes, but it's a little bit annoying so I'd go back to a bug-free version
And somehow the game I'm playing (Rage of Bahamut) doesn't display right in some screen.
Tried ShenduOS and everything looks great. Until I find the 'phone' is not working, lol.
Hey guys!
So, I have been rocking this current ROM for a while now! I must admit, I've had few problems recently, but so far it works and gets the job done. I am now in the process of debating if I should revert down to one of the most stable ROMs for this phone (CM7.2) or to continue rocking this current ROM and try to see if I can help in terms of fixing current issues.
My classes start tomorrow! I will post an in-depth update on my issues this weekend!
???
darkgiant said:
Hey guys!
So, I have been rocking this current ROM for a while now! I must admit, I've had few problems recently, but so far it works and gets the job done. I am now in the process of debating if I should revert down to one of the most stable ROMs for this phone (CM7.2) or to continue rocking this current ROM and try to see if I can help in terms of fixing current issues.
My classes start tomorrow! I will post an in-depth update on my issues this weekend!
Click to expand...
Click to collapse
The coronel mustard rom with the candle stick kernel?
Give us a clue.
pshadoww said:
I am using AOCP now but currently looking for a bug-free ROM.
As far as I know, there are still a few bugs in 4.2.2 including:
1. Headset heat up when plugged in.
2. Green line in camera.
3. Signal drop after a missing call.
4. Camera flash delay.
Is there any 4.1 and above ROM without those problems? Please let me know. 1. and 3. is really annoying to me. Thank you!
Click to expand...
Click to collapse
Keep an eye on N_otori0us_, he's been really making some moves trying to fix 1. 2 you usually see patches from OP's in thier thread to fix it.
At least you don't have the screen flicker bug also.
tonyMEGAphone said:
The coronel mustard rom with the candle stick kernel?
Give us a clue.
Keep an eye on N_otori0us_, he's been really making some moves trying to fix 1. 2 you usually see patches from OP's in thier thread to fix it.
At least you don't have the screen flicker bug also.
Click to expand...
Click to collapse
If you see a bug in my roms. Tell me lol.
There's a fix for green line that coderzs made. And the. 64 is a temporary fix for the headset heat.
Not sure what else to fix though...
Sent from my myTouch 4g using xda app-developers app
putting work in
I was referring to how you are trying to fix the headset issue overall, not how you have any bugs in your roms.
Now I've been using PACman_GLACIER 19.3 for 2 weeks. Very stable, fast and no bug (except sometimes when it boots up, Link2SD notifies me to hot reboot to make SD partition mount)
You should check out the links in this thread.
http://forum.xda-developers.com/showthread.php?t=2429325
Especially those of you who like ViperTouch. They are from a Chinese forum so you'll need to translate but the ROMs can be set to English on setup.
I might call it an end with my current ROM... it is currently becoming way too unstable for my abilities as a daily driver. Current issues include:
1. Battery life - I literally drop from 100% to 60% in a matter of 2 hours only using Wi-Fi for browsing the New York Times.
2. Phone screen flickers when locked (may be linked to battery life)
3. Certain apps that require a camera just do not cooperate
4. Green like in all pictures + picture quality not the same versus when the ROM was installed freash
5. Crashes and freezes a lot
Overall, this ROM was good, but as time progressed, its performance decreased as well.
Currently about to try Albinomans latest Jelly Bean ROM, or even try out the AoCP rom!
Hi, I'm planning to try some KitKat ROM for my Mi2S. What you can recommend? It doesn't needs to be based on MIU, but it must be fast stable and battery safe.
I read good recommendations for MoKees ROM, but I want have more tips from you guys.
Thank you for any tips
Hello, Mokees Rom is a very good rom, with tones of features, but I prefer official CM11 from M1cha. It's not so "heavy" and for me it's ideal for daily use.
Hi, thanks for the tip. I'm currently on the MoKee, but I will probably test also official CM. MoKee is fine, but not so slight as I expected. I must say that old MIUI v5 was better.
Im using omni as daily. Personally I think micha's kernel is better than mokee one. The best thing is test the ROMs you might be interested and choose the best for your needs
I'm just testing latest sMIUI v6. I was fighting with some some settings ther, but finally I fixed most of the issues, so I will probably stay for some time with this ROM. Anyway the performance still to perfect as with MIUI v5.
what about battery usage?
battery usage seems to be fine. cannot say objectively, because my usage differs in last days, but its approx. 1-2 days. i'm still using, wifi, bt, gps, & data
Ihave tried many roms and I have to say that the pacman is so far the best cause is the one with most customizations. Love it.
Not sure how this thread lasted this long but.
Thread closed
Im on Sarthak's CM14 and battery life is not very good. So which one is the best atm?
Tagion said:
Im on Sarthak's CM14 and battery life is not very good. So which one is the best atm?
Click to expand...
Click to collapse
Both roms are in alpha / beta stages. Stability is not something to be expected from those roms .
Wait for the development to proceed and eventually a stable build will be released.
Roms out of the box will always give you good performance. If you want battery savings look into tweaking kernels with KA. Or flash custom kernel like Arsenic or Starkiller.
It's a subjective choice, Sarthak has fixed Mobile Data, GPS & SD Card issue completely.
Ashwin is busy with his exams hence he cannot devout much time to his builds.
AOSP still lacks Tri-State & GPS and will probably never get Gestures.
Its upto you as always. Don't really see a point in these kind of threads.
why not both?