Xoom Team Eos Jelly Bean vs Official Jelly Bean OTA - Xoom Q&A, Help & Troubleshooting

Hi,
I am a little sick of the stuttering of Jelly Bean on my Xoom wifi - as I understand it, it's because of the Xoom's poor performing flash read write speeds, which is something that won't go away. My only question is: does the Team Eos Jelly Bean rom mititgate this lag a bit? Or is it still present regardless of what rom is flash on the device?

Countless threads about this already.
However, my opinion us that the first soak and release just wasn't up to par...hence the current soak.
Ive tried both and have notice stutter on both of them. I'm using stock for now because I like it.
Sent from my vivow using xda premium

I am using a 4G Xoom with the latest EOS JB nightly. Honestly for the first couple of weeks the stuttering was pretty bad, but over the past month or so things have gotten much better. I would personally recommend giving EOS a try for a few days and see. I would be surprised if you don't see a difference.

Related

[Q]When is the 3G 4G Xoom going to get Ice Cream get Ic

When is 3G 4G Xoom going to get Ice cream?
i been asking that forever. I don't know what the deal is with Verizon not pushing out updates. I just don't get it. From what I read on Droid life is its ready to go but up to big red to push it out.
Just like the gnexus still stuck on 4.02 first carrier to have the phone last one to push out the ota WoW
Yeah it's very annoying. The problem is Verizon's testing procedures (or so I've been told) are VERY strict. Add to the fact that the Xoom isn't a priority device for VZW anymore, and yeah...we continue to wait. The WiFi-only Xoom has had ICS since December, and (again, so I've heard), Google had the ICS ROM for the 3G/4G Xoom ready not long after that. To add further insult to injury, Google and VZW pushed out an update to the 4G Xoom in February that was just a Honeycomb update (3.2.6) to fix data connectivity coming out of airplane mode. Annoying.
With the Galaxy Nexus, at least two 4.0.4 builds have been pushed to devices as part of a soak test (IMM30B and IMM76K), but neither made the cut apparently. But since they went out over the air, we have the files and can run those if we want to. With the Xoom, there hasn't even been so much as a soak test, that we're aware of anyway.
I wish I knew as well.
I've tried all of the custom ROMs and have had problems with each one. I've gone back to the Honeycomb stock ROM in each instance. As snappy & nice as the ICS is with the custom ROMs, the stock Honeycomb has been the most stable ROM ever, imho. I'm very excited about ICS coming out, but only if it's as rock solid as Honeycomb is. I'll wait a couple of more months so that VzW can get it right the first time.
Definitely. That Honeycomb 3.2.6 stock ROM is solid as a brick ****house. That's why I love it.
Don't know about you but I have had ICS on my Xoom for a while. Thanks Team EOS. And it is much better than anything Verizon would put out.
dimitri407 said:
Don't know about you but I have had ICS on my Xoom for a while. Thanks Team EOS. And it is much better than anything Verizon would put out.
Click to expand...
Click to collapse
The stock ROM on the Verizon Xoom is still created and updated by Google. It just needs VZW approval before it gets released. TeamEOS isn't stable enough for my liking. Tried playing SimCity lately?
oldblue910 said:
The stock ROM on the Verizon Xoom is still created and updated by Google. It just needs VZW approval before it gets released. TeamEOS isn't stable enough for my liking. Tried playing SimCity lately?
Click to expand...
Click to collapse
What's wrong with SimCity? (I don't game, so I'm really asking.)
Is the real issue perhaps merely that the game's not ICS-tablet-aware?
Sent from my LTE EOS Xoom via XDA Premium
It freezes constantly. It'll run fine, then all of a sudden just hang forever, giving you the wait/force close dialog box. I don't think it's an ICS or app issue since people running stock ICS on the WiFi Xoom say it works fine.
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
[SimCity]freezes constantly. It'll run fine, then all of a sudden just hang forever, giving you the wait/force close dialog box.
Click to expand...
Click to collapse
Interesting. I haven't seen any indications of that in the main EOS threads.
Did you see anyone else collaborating this issue? Were you overclocked at all? Also, at one point we switched to overclocking the GPU by default, and I wonder if that's the issue (after all, my kernel improvements wouldn't have made any difference to a game, and we're nearly stock in anything else that matters).
I wasn't overclocked. OC always makes me nervous! Could be with the GPU...not sure. What I do know is that the issue was still there as of the stable 2.0.0 release.
Sent from my Galaxy Nexus using Tapatalk 2
Pls share a link with the instructions to install ICS on an LTE Xoom. Thanks in advance.
Sent from my Galaxy Nexus using XDA
jbe219 said:
Pls share a link with the instructions to install ICS on an LTE Xoom.
Click to expand...
Click to collapse
Uh, didja maybe check here on XDA?
My answer is "never." VZW will never release ICS for this thing. It was seriously doomed from the start.
That said, EOS has created an excellent stingray rom. Again, STINGRAY. And again, EXCELLENT rom. I'm not playing SimCity, but the Sims works very well and since the app was updated, it works even better. It was freezing on restart but now it doesn't do it anymore, which is something to say about how solid EOS' rom is--a problem with the app and not the rom.
Sent from my Xoom using xda premium
sbrownla said:
My answer is "never." VZW will never release ICS for this thing. It was seriously doomed from the start.
Click to expand...
Click to collapse
Oh dear, not this again. Last year it was "We'll never get LTE" and/or "We'll never have writable SD-Card". It's obvious the tech is there, most likely it's due to either compliance issues (and with VZ that probably means they're trying to lock something down or take something away in the ROM they're intending to release ... the bastards) or they're waiting 'till some as-yet-unannounced LTE tablet(?) device comes out first. Apparently there's a ROM in testing at VZ, if the leaked screenshot has any credibility.
Tomorrow
Sent from my Galaxy Nexus
bwcorvus said:
Tomorrow
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well there's a blast from the past! Hit the irc sometime
Hello ,
I've a question about teameos 2.0
I have a motorola xoom 601 and it has official rom 3.2.
I want to flash teameos 2.0 rom, but my device hasnt been rooted yet.
Yo flash this rom mention about that on this link [ROM][ICS] Team Eos ICS 2.0.0 [Updated 2012/4/27] Do I have to root my device or Can I apply these installation steps directly ?
Thank you..

Wait for OTA JB or go with EOS JB?

Was wondering should I just wait for OTA JB update or just flash custom EOS JB rom.Just restored my Xoom to factory about a month ago.I know how to flash/restore/recover from brick but just wanted some opinions on this.
Try it and see yourself. You might love JB so much, you won't want to wait for OTA.
Besides, EOS will give more features and performance enhancements.
my opinion
Use JB from team Eos is a GREAT experience...
You will love with its smoothness and responsiveness.
Now I use build #93, and its blazing fast. I love it.
I started use it since #84, #88 and #92.
I love this ROM, but now I think about going back to stock ICS, why?
1st, I notice that battery life still greater on ICS, even working on the same 3g network all the time. (I rarely use WiFi)
2nd, I found that on #93 'auto' brightness didn't work correctly, the screen won't decrease its brightness on darker surrounding.
3rd, I can't use Google voice translator, it won't recognize my voice.
That's why I wanna go back to ICS. Maybe my reason didn't bother you, but that's matter for me.
So, if you can ignore a little problem that you might find on JB, I can say that you should try it now, you will amaze for its smoothness.
But now, I will wait for a moment and go back to ICS.
It such a great great great experience with JB, an Amazing work by Team EOS:good:....
ota JB will have JB kernel and new binary file ( dirver ?) for camera etc , anc can upgrade radio baseband
EOS JB have ICS kernel , ICS (some HC ) binary file ... but have some tweak like over/down clock , color change of clock ....
no waiting
I didn't have to wait. I'm not rooted or invited to the soak test. On a whim I deleted the cache from the framework app and then checked for updates.
The OTA downloaded and I'm on 4.1.1 now. Your mileage may vary...
one more for EOS
I would consider EOS especially since returning to stock is relatively simple. My options for the update were limited - Canadian Eh
Also I've been using the ICS from EOS since I got my tablet -- May 3 rec'd the tablet and on May 5 I installed ICS using the nightlies from EOS, never looked back and have had few issues, none serious.
EOS roms and the Xoom- makes that 3 year old tablet perform like some of the newer wonder tabs and for way less money.
However you go, I am sure you will like JB android... it seems to be somewhat smoother and troublefree.

[Q] Call quality on JB

Hi, I'm experiencing serious problems if I install a Jelly Bean based rom on my Sensation 4g (TMOUS). Although the other party can hear me clearly, I can't hear them, but the sound is lagging, distorted or there is no sound at all. I only experience this on calls (both by cell network and by VOIP apps). If I'm using a headset the problems are gone. Media plays back fine too.
All problems disappear if I install an ICS rom (currently Revolution).
Does anybody else experience similar problems or know a fix?
I'm using jelly bean paranoid Android by Dragun Korr and my calls are all clear. Perhaps this is rom related. The issue could lie in the rom itself. Have you tried other jelly bean roms to test and see if it's that particular rom that's causing the issue? I would experiment and see if call quality returns with a different jelly bean rom. If after installing a different rom, the issue still persists then you will know this is device related. Do some experimenting and see. It's likely that once you flash a different jelly bean rom, the issue will disappear.. but do some experimenting and see. It's strange because on different jelly bean roms my data had terrible issues, once I flashed this jelly bean rom those issues went away. So do try another jb rom and see if the issue is still present or fixed. Best wishes.
Sent from my HTC Sensation using xda premium
realsis said:
I'm using jelly bean paranoid Android by Dragun Korr and my calls are all clear. Perhaps this is rom related. The issue could lie in the rom itself. Have you tried other jelly bean roms to test and see if it's that particular rom that's causing the issue? I would experiment and see if call quality returns with a different jelly bean rom. If after installing a different rom, the issue still persists then you will know this is device related. Do some experimenting and see. It's likely that once you flash a different jelly bean rom, the issue will disappear.. but do some experimenting and see. It's strange because on different jelly bean roms my data had terrible issues, once I flashed this jelly bean rom those issues went away. So do try another jb rom and see if the issue is still present or fixed. Best wishes.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
realsis, thanks a lot for pointing this out - I've already tried different JB roms, but I gather they were all based on Bruce's CM10 version... I've installed ParanoidDragün now, and call quality is flawless again
I'm still curious why I had those issues with Bruce's Kang and similar roms, as nobody else seems to run into this issue... I've already tried different radios and firmwares, but nothing helped.
Guess I'll just have to avoid this rom, although I really like it (ParanoidDragün seems nice too though).
Anyway I'm happy now realsis, thanks a lot
Your welcome, you know I was also wondering the very same question. I have terrible trouble with the Cm roms myself. I thought I was the only one? I can't receive data on anyone of them. I'm so glad you got your issue fixed! I've never had any trouble myself with paranoid Android. I'm using kernel 3.0.53 and battery life is wonderful! Data is strong and calls are clear. There must be something in Cm that's messing with our data quality. For me, I had no data at all so, yes it's very strange that some can run it without issue, while others like you and I can not.. well, I'm very happy you are able to run jelly bean now without problems! Take care
Sent from my HTC Sensation using xda premium

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?

Solid fast stable rom? Stingray

Still on 4.1.2 without bigpart. I really don't have time to go through 3-5 roms and see what works well. I don't use verizon data so I can easily flash a wifi only rom. Can anyone recommend a super stable, fast 4.4.4 rom that I could go with?
I was thinking that 4.2 never really made for the xoom and I have not been here in awhile so I don't know if 4.3 or 4.4 would be best but since 4.4 is supposedly faster on older devices, I might lean toward that.
Stingray roms would be okay too but I suspect there is a more solid rom. Your comment appreciated.
bump, i would like an answer to this as well. looking to finally root my xoom
Well, I don't know, I've bitten the BigPart Bullet 2 months ago and started with the Omni ROM and am still happy with it.
Did you have any issues with Google Chrome on 4.4.x?
I had a old Xoom MZ6001 laying around ,stuck on android 3.0 which was useless even as a paper weight :laugh:.
So Thought nothing to lose and googled how to mod it or update it and stumbled upon this great site.
After many head scratching hours.
I managed to unlock root and install [ROM][4.4.4] OmniROM - Everest - bigPart.
I was amazed at the performance of it since i updated and kids haven't put it down.
In short wana says thanks .
Great site BTW :good:
pvhien said:
Did you have any issues with Google Chrome on 4.4.x?
Click to expand...
Click to collapse
I use stock browser.
Oh and my Xoom is a Wingray, if that makes a difference. for TS. I think EOS or Omni room with BigPart is a definite improvement over stock ROM.

Categories

Resources