Database Info

[Q] Ice Cream Sandwich on Xoom - is it much better than honeycomb?

Hi all
I've picked up a Xoom in the UK. I quite like the tablet but it has a few niggling issues. I'd like to know if these are fixed in ICS (I do not want to unlock the bootloader etc. to update in case I wish to return it). Is rooting and unlocking the bootloader reversible?
I've read ICS is notably faster and avoids the "keyboard lag" particularly evident on XDA, but would appreciate some comments on the following:
Screen Brightness: Auto sucks, it's always too low. Is this improved in ICS?
Browser: The browser doesn't fully load a page. Only the first portion is rendered, scrolling down the page means the next part is rendered. Scroll back up and the earlier part you've already seen is NOT in memory and is re-rendered. Most annoying!
Any comments appreciated.

ICS is most definitely an improvement over stock,in terms of speed and stability. Quite amazing, given that the ICS builds we have now are alpha engineering builds.
To your specific questions,I never really had a problem with autobrightness or with browser rendering... but I've been off stock so long I just may not remember the browser issues. I also converted pretty early on to Dolphin HD browser due to a few stock browser quirks, and am now playing with Boat Browser, which seems a bit lighter than Dolphin and which I like a lot so far.
At any rate, I'd suggest you read through the ICS thread of your choice thoroughly and if you like what you see, give it a try... you can always go back to stock and relock if you decide Xoom is not for you... but I can tell you it is a whole new,and much improved, device on ICS. I'm running Team EOS's version for 4g.
If you decide to giving it a try, the Universal Root thread is a must read.

Unlocking the boot loader and rooting the XOOM on 3.2 Honeycomb is absolutely reversible, I have done it myself several times with no problems
I followed this YouTube tutorial for both
http://www.youtube.com/watch?v=P7Dw1PNnmHE&feature=youtube_gdata_player
https://www.youtube.com/watch?v=LSH14xI5c8s&feature=youtube_gdata_player
Good luck, since it is reversible there is not much risk involved in rooting and unlocking your bootloader and Motorola website provides the stock system images to return your device to stock and re-lock your boot loader in just a few simple commands.....I suggest reading up allot before attempting, there are some great tutorials to familiarize yourself with ADB and the commands and such.
I rooted back on 3.2 and flashed the Team EOS ICS build and I have to say it runs amazing and I have not regretted it for a second.
Sent from my Xoom using xda premium

Thanks guys - much appreciated.
I'm interested in the Team EOS build - I'll have a good read up! I'm not alien to the root and unlock process though - looks similar to my Sensation.
Cheers!
James

Stock HC is a disappointment, EOS is in a word awesome. I use the wingray variation and overclock stable at 1.6 Ghz. I ditched stock over 6 months ago and never looked back. The same folks that bring EOS ICS brought us Tiamat HC which is what I started on after unlocking. Motorola should outsource to these guys.

Can't agree more. Stock 3.2 sucked. Slow UI, default launcher was clunky - it made the Xoom a disappointment.
ICS EOS Wingray (wi-fi), is awesome. Even the nightly builds are usually stable . Sometimes not but most of the time yes. I'm running nightly 54 and rock solid. The only bugs I've encountered are: 1) camera flash over exposes picture, 2) wi-fi off when sleep does not work.
Battery life is good as long as its not over-clocked. Over-clocked, expect it to eat the battery quicker and for most things you do - OC is not needed.
Try it out.

yes yes oh god yes.

I've just moved up to the stock rooted ICS from Tiamat HC and whilst the visuals are fairly similar, it's definitely smooooooother Well worth the move. I've also never found overclocking to be a necessity on the Xoom.

[Q] install eos or not

Hello, i'm a new wifi xoom user and i'm very tempted to use the eos rom because of the features it presents, especially the rooted parts. My hesitation comes from the fact that i know what i get, but i don't know what i lose abandoning the stock rom : hardware support, battery lifetime, application compatibility (i read that there may be problem with chrome beta for example), easy update mechanism. I hope some eos experts have answers to my interrogations.
Thank you

I think if you decide to flash the most recent Team EOS Nightly 79 you will be very very happy. If you are currently on Honeycomb it is a vast improvement in all areas that I can tell...the battery life is just as good as honeycomb, maybe even better. The new UI is much cleaner looking and just kinda sharper and more professional in my opinion than honeycomb. I have tried the stock ICS build and the latest Team EOS ICS build and to be honest the responsiveness of both are amazing compared to honeycomb, the window animations and transitions are much smoother and more fluid, the general feel is honestly that of a new tablet which I love. In my opinion, with the Team EOS build I haven't really noticed any bugs and the fact that it's rooted gives it more functionality, you can set the charging light which is a nice feature, and of course if you like you can over clock or undervolt although I find it to be perfect without doing either. Another great improvement is the browser, it opens and closes without any lag, and is much faster and cleaner when browsing, also sites that use flash seem to be much more seamless, same goes for Youtube videos. In my opinion this Team EOS ICS ROM is definitely the way to go, I have been using it as my daily driver since back when the first couple Nightly builds came out and I haven't looked back.
I would definitely recommend, if you are completely stock and on honeycomb that you go ahead and read up in these forums and then unlock your boot loader, flash a custom recovery and flash this ROM. If you took the ICS OTA update, then it's totally just personal preference as to whether or not you want to go with the rooted Team EOS ICS ROM.
In any case, hope you enjoy the XOOM experience as much as I do
Sent from my Suped up XOOM running Team EOS ICS Nightly 78!

Chrome beta works just fine.

Thanks a lot for your answers.
I currently have ics (i unlocked my french xoom to put the us stock rom in order to get it).
My wish to go on rooting is primarly for usb key and openvpn.
I would like to play some games too so that's why i wonder if the hardware support is the same or equivalent as stock rom ?
And does the eos team provides an ota update mechanism for the stable or for nighties ?
Are the same 3 languages available (us,fr,es) ?
Thanks a lot again

When Motorola gets around to releasing ICS for the Atrix 2...

my question thus becomes:
Once we get ICS officially from Motorola (and I'm guessing it'll be Android 4.0.4 and not 4.0.3 or whatever), and Jelly Bean is already floating around, will it be possible to then have some ROMs made or built for JB that will work automagically on the Atrix 2, or will the updated kernel in JB become a big hassle/issue that prevents us from using it at all, barring that nobody will most likely crack that bootloader anytime soon...?
tl;dr version: Once ICS is official for the Atrix 2, can JB ROMs be built and usable or, will the updated kernel and whatever just be yet another wall on this fortress?
I just picked up an Atrix 2 and I find it to be extremely fast and so far pretty much rock solid stable. I rooted it, installed CWM, did a Nandroid backup of the 2.3.6 stock installation for safe keeping and then installed Remus 2.0 and it's just insanely responsive and everything works as expected.
But I just watched the Google I/O keynote to see what all the fuss about JB is about and I can see it's pretty amazing considering it's an incremental upgrade for ICS more than anything else, but the performance improvements are crazy so, I'd hate to think that Motorola would work on JB for us and yet not get around to releasing it till well into 2013 which is just a bit insane.
For such a company, Motorola is so behind the curve it hurts. I do love this device, however, it's utterly fantastic for me and I plan to keep it for some time, but obviously it's more than capable of running ICS/JB from the gitgo - now it's just "ok, when?"
Thanks...

br0adband said:
my question thus becomes:
"ok, when?"
Thanks...
Click to expand...
Click to collapse
As per official information - update for ICS - Q3 of 2012 (which actually already started), more precision date - unknown

I don't think you read my post very comprehensively - I didn't nor was I asking if ICS is coming and when it'll be out as we already know that based on Motorola's schedule announcement.
I know ICS is coming, I know it's between July (like, right now) and September (which means between right now and the end of the year given Motorola's somewhat inefficient release schedules of past years.
What I'm asking again is:
When ICS is out, and when I've got it installed on this Atrix 2, is there a possibility that Jelly Bean will be ported over to this Atrix 2 considering they're very similar OSes that most likely will use the same bootloader, or ... ?
In other words, after ICS is available, are we looking at a 2013 release of Jelly Bean for the Atrix 2, if it even happens, or will it be up to talented folk in the developer community to make the best of ICS as given by Motorola?
Hope that's more clear... I don't know how else to ask the question, honestly.

I'm no dev... but I did sleep in a holley day inn last night...
The locked bootloader means that the bootloader can only load the official Moto released kernel. JB will have a new kernel so the only way to get JB is when/if Moto releases it.

That's all I wanted to hear, at least from one other person as a confirmation. Nothing surprising, but somewhat of a disappointment I suppose.
/me kicks Motorola in da shinz, hard... then does it again...

I wouldn't be so sure that it's never going to happen. People have accomplished CM9 and AOKP (both ICS ROMs) on the Razr, Droid 3, and Droid Bionic (all of which atm are still on GB) that uses the GB kernel (and just about all of those ROMs are flashable on the A2, just without a working radio). So there's a good chance that the same thing will happen with ICS to JB, and since it's an incremental upgrade then I think it would be easier to do.

cogeary said:
I wouldn't be so sure that it's never going to happen. People have accomplished CM9 and AOKP (both ICS ROMs) on the Razr, Droid 3, and Droid Bionic (all of which atm are still on GB) that uses the GB kernel (and just about all of those ROMs are flashable on the A2, just without a working radio). So there's a good chance that the same thing will happen with ICS to JB, and since it's an incremental upgrade then I think it would be easier to do.
Click to expand...
Click to collapse
Yes, this is true. What most seem to not realize or maybe even know, is that the jump from GB to ICS was huge in the kernel space because honeycomb was completely jumped over and skipped in the phone space. What this means is that all of the upgrades from HC were merged into the ICS kernel, so the jump from Gingerbread to ICS was a huge one. The jump from ICS to JB will be much smaller, and it will have a lot more performance tweaks and increases from ICS. So this should be more doable. The real issue is that we need the ICS kernel first to start looking into JB.

Yeah I intentionally qualified my reply since I'm not familiar with the enhancements that went into the GB, ICS and the JB kernels...
I would have expected that the project butter enhancements in JB would have required significant kernel level changes. I take it that the kernel level work to support project butter happened with the ICS release... and now the UI layer in JB is more or less just leveraging that foundation.

apinkel said:
Yeah I intentionally qualified my reply since I'm not familiar with the enhancements that went into the GB, ICS and the JB kernels...
I would have expected that the project butter enhancements in JB would have required significant kernel level changes. I take it that the kernel level work to support project butter happened with the ICS release... and now the UI layer in JB is more or less just leveraging that foundation.
Click to expand...
Click to collapse
No You may have misunderstood, just a little.
The jump to JB from ICS will be smaller.... Than the jump from GB to ICS. Yes there are a going to be some hefty changes for project butter, but only in in the performance and virtual space areas of the kernel, since every thing in the android app space is handled by the jvm, so there are a lot of enhancements to how the virtual space is handled, that is really what project butter does, as well as the changes in kernel to do that. Now Project butter also changes the vsync timings in the OS as well, and I am pretty sure we can port or figure out some of the changes and make some of that up in ICS as well.
We will most likely be able to run JB "ROMS" without ALL the project butter enhancements once we are on ICS, but that will be more than likely not until closer to the end of the year that we will begin to see some ported ROMS for JB that are capable of running on this phone.

It would be nice to see that... I like Moto hardware but the locked bootloader can be a bit of an annoyance.

CM 10.1 (JB 4.2) on my Cappy = awesome

Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.

Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse

daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yeah Factory reset is recommended. And its Working great. I must ask you to consider updating to 4.2, 10.1 nightly build. Its literally flawless...
Sent from my SGH-I897

cm10.1 really cool. Waiting for slim android 4.2

Several days ago I did the upgrade to 10.1 from 10 without the factory reset - no problems, but wipe the caches). You need to clear the clock data first and do the upgrade from the boot screen (not the update screen in about phone). Do a backup just in case you have problems.
for further info go to :donandroid.com/how-to-update-cm10-to-cm10-1-with-cwm-recovery-581

ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
+1
Sent From the Land of Defrag

if you do Erase SD Card, does it erase internal storage instead?

I tried the stable version of CM10, and it seemed to work great except for one thing. I could connect to my employer's Exchange server at all. I tried all kinds of things and it just couldn't connect. I took it to the IT guys and they fiddled with it for a while and couldn't get it to work either. A little quality time with Google told me that JB has a bug that sometimes makes it impossible to connect to corporate exchange accounts. I ended up switching to CM9. Do you know whether CM10.1 fixes that? If so I think I'll give it a try.

ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
Slim 4.2.1 has been available in beta for a week or two now... I've not encountered any problems with beta 2 so far.
http://forum.xda-developers.com/showthread.php?t=2060386

falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!

thank quá hay :

theoctagon said:
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
Click to expand...
Click to collapse
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?

CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897

laughingT said:
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
Click to expand...
Click to collapse
So for a stable fast ROM, you would suggest CM 10.0 over AOCP or some of the other 4.1.2 "final" version ROMs like SlimBean?

depends on your personal preference I suppose. you need to get to CM9 at least, preferably 10.0, to flash slim bean, right? So, if it runs well on 10.0, then you could go slim bean
you wrote that you just want the basics, nothing fancy. so, yes, CM10.
Sent from my SGH-I897

daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yes, I did. And I didn't really have any problems with Semaphore, it just seemed a little laggy.

RichMD said:
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
Click to expand...
Click to collapse
I would highly recommend Sephhi's [ROM][4.2.1]Captivating (Xperia Themed)
It is CM10 based and is stripped down to run smooth.
http://forum.xda-developers.com/showthread.php?t=2057574

Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?

BELbX said:
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
Click to expand...
Click to collapse
Try hellybean 4.2. Hellybean came a long way from when i used it a while back! It's a much smaller and light weight package as compared to the xperia one. Barely any issues. Boot times and first boot are quick. Over clocking is fun again too. I thought it was oc'd at first for being smooth. It's so smooth and stable. One or two things, but nothing compared to others. I like the xperia one but it's heavier with more to be worked. It's running better then aokp 4.1 with semaphore.
Sent from my SGH-I897 using xda app-developers app

3g Problem
I just flashed 4.2.1 AoCP 5 and lost my 3G. Anyone know what's up?

JB Rom - Stability

My friend has been running CM7 for what seems like forever. The phone stopped charging and was boot looping. I was able to get it into recovery and fixed. However, I don't know what he did over the last week to mess it up. It seemed like the ROM was glitchy for a few weeks now.
Anyway, I don't use an infuse, I have an atrix. Looking through all the JB roms, it looks like many are stable. I will be leaving for the week in the morning, and I would like to reset and flash the infuse with JB. Could anyone suggest a JB rom that I can flash and feel comfortable leaving him with that is stable. I see avatar has OTA updates and is stable, but once I flash the phone, that's it. It's a rom I would have to leave him with. He wants no more fussing.
OR
Is there an ICS or Gingerbread suggested for stability? He's used to using Cyanogen, so I'd like to stick with some form of that, or JB.
Any help would be greatly appreciated. Like I said, I'm on an Atrix, so the infuse I'm a noob on.

I've been running SlimBean for about the past month maybe longer. I've never experienced any random reboots or anything on it. The only problem that I've had (this will be a problem on all JellyBean roms) is that sometimes the pulldown notifications don't work. The quick fix is just to do a system UI restart, but it will still have to be done about 2 times a day. The battery life isn't great on JellyBean roms for infuse either, but it's worth it in my opinion because 4.2.2 is a much better user experience than gingerbread.

odinfire said:
My friend has been running CM7 for what seems like forever. The phone stopped charging and was boot looping. I was able to get it into recovery and fixed. However, I don't know what he did over the last week to mess it up. It seemed like the ROM was glitchy for a few weeks now.
Anyway, I don't use an infuse, I have an atrix. Looking through all the JB roms, it looks like many are stable. I will be leaving for the week in the morning, and I would like to reset and flash the infuse with JB. Could anyone suggest a JB rom that I can flash and feel comfortable leaving him with that is stable. I see avatar has OTA updates and is stable, but once I flash the phone, that's it. It's a rom I would have to leave him with. He wants no more fussing.
OR
Is there an ICS or Gingerbread suggested for stability? He's used to using Cyanogen, so I'd like to stick with some form of that, or JB.
Any help would be greatly appreciated. Like I said, I'm on an Atrix, so the infuse I'm a noob on.
Click to expand...
Click to collapse
On the latest BeanStalk I haven't even had the statusbar freeze,build before that was only glitch I noticed. If you want to ensure rock solid stability I would recomend this though
http://forum.xda-developers.com/showthread.php?t=1524081

elbscorp said:
On the latest BeanStalk I haven't even had the statusbar freeze,build before that was only glitch I noticed. If you want to ensure rock solid stability I would recomend this though
http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
Now you know better than that. Thanks for the link and the suggestions.

never used beanstalk, but I'll throw my 2 cents in for slimbean. http://forum.xda-developers.com/showthread.php?t=2005016