yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] themichael:
Anyone not satisfied the the performance of our aging xooms should try the below mod. Its made to be universal for any device and has done loads to speed up my Xoom.

http://xdaforums.com/showthread.php?t=2113150
[Xoom Android Development] Ardvaark:
You on EOS 4?
[Xoom Android Development] gibbs1984:
Does that actually work or is it a placebo effect?
[Xoom Android Development] Ardvaark:
If you study this subject, it does have merit. I have not tried it. Very tempted though! Apparently some problems with it. And its in alpha stage.
[Xoom Android Development] ro.chi:
Crossbreeder works on EOS 4 (in use on umts_everest 169)

Good for 3G connection.
[Xoom Android Development] Blondblueyed_girl:
Have never used Netflix but tvcatchup works fine on my version of 203 with ElementalX-Xoom-v1.2
[Xoom Android Development] gibbs1984:
Could just be my crappy internet connection in my room for TVCatchup then.
[Xoom Android Development] Ipse_Tase:
Another failed upgrade to EOS 4/203

Last time I tried a while back (155 I think) and now again I wasted almost a day again trying to get to EOS 4 - I'm not even sure of the benefits over the perfect EOS 3 I'm running.

Mangled folder structure, stuttering, tablet not waking up from sleep when power button is pushed....am I the only one with so much trouble upgrading?

I did a factory default and restored the apps from Titanium...I know some recommend NOT restoring apps data, but to me these issues were ROM related.

When I recovered back my nandroid it seemed like night and day- fast and stable. What gives?

I'm not *****ing, just trying to understand what I did wrong.
[Xoom Android Development] themichael:
The logic behind cross breeder is very solid. A lot of the people posting have very positive responses as well. I think the people having trouble are in very specific situations. Most users should only bennefit from the mod and if not there is a unninstal zip the op provides.

Its gaining popularity and is poised to be a truly universal mod.

Let me know your thoughts but its working great for me.
[Xoom Android Development] notbrodie:
Pretty much all of the devs on the nexus 4 forums have universally panned the entropy mods. Faux123 even states that it will likely reduce the life of the eMMC in the device
[Xoom Android Development] themichael:
The way it is implemented is different than your standard "seeder," the toll on the system is almost nonexistent. Entropy optimization is only one part of the mod which encompasses many aspects of smart phones.
[Xoom Android Development] TBirdUK:
help

Can someone help, i am away with my xoom on a very slow connection, came with a few roms including 190, 193, 198 203 and a couple of others. Got gapps for xoom 20130105 and 20130413 eos xoom only and after working for ages the xoom keeps giving me gapps.google has stopped working message and play store wont work!

I have reflashed, both the rom and gapps, fixed permissions etc but still doesnt work

Any ideas?
[Xoom Android Development] bigrushdog:
Test build going out. Only change is a new kernel. Dreamcwli base with backtrack support and all the tasty modules. Let's see how it feels.
[Xoom Android Development] maxvsmith:
Crap...

Well I tried out the 203 build. I was originally on honeycomb 3.1 and I unlocked boot loader (never done before) rooted, and used the taimatR4 recovery and flashed the 203 build and google apps on it. I noticed when I was setting it up the setup process actually froze and asked if I wanted to end the task or wait. I was having lots of trouble with google now not working (did not read latest posts here until tonight) and I downloaded the 204 build through goo manager (love that) and factory rest, wiped cache, dalvik cache, and flashed the 204 build and the gapps again.

However, after I flashed the gapps I got this error.

E:Can't open /tmprecovery.log

E.Can't open /tmprecovery.log

E:Unknown volume for path [/sd-ext]

I'm not sure if this is because I have the taimatR4 recovery and I should be using cwm or twrp instead. Or maybe it's that I'm only using a 2 gig micro sd (32 is in the tf300t).

I just find it weird that the first time I flashed 203 everything loaded fine. Although I did accidentally flash the room before I wiped everything. I think I flashed it twice by accident. I think that's the reason it hiccuped when setting up the tablet. But just wondering what I should to fix this. If all I need to do is flash a newer recovery than that would be an easy fix.

Oh crap. Now I get

E:Can't make /tmp/update_binary

If I try to even reflash the rom. If anyone has any idea of what's going on please help. And that cantopentmprecovery is popping up everywhere now. Oh right and everytime I turn on the tablet it's stuck at "Android Rocks" boot image and won't go past that. Even if I turn it off it turns back on in a few seconds. Only way to stop that is to go into recovery and turn off from recovery.

Edit: Okay resetting it got rid of that strange message. But even doing so it still won't go past the boot image. It won't go onto boot animation or start up.
[Xoom Android Development] uzi2:
I couldn't get past the Motorola splash screen with 204.

Is it just me?

[MENTION=4203084]maxvsmith[/MENTION] it is possible that you have just confirmed the issue with 204. You will need the latest TWRP or CWM recovery for this ROM. Wipe system and data before flashing 203 and gapps and all should be well.

Swyped from my xoom
[Xoom Android Development] Tomcar:
I second that.
[Xoom Android Development] dsbnz:
I Third that. I'm TWRP recovery 2.3.3.0, not sure if i need latest version to flash v204. Reflashed EOS v203 and all good.

Edit : updated twrp recovery to 2.5.0.0, and flashed EOS v204, still hangs at Motorola boot splash.
[Xoom Android Development] petrossa:
Me neither.
[Xoom Android Development] recognitium:
I couldn't get past boot logo after flashing 204 neither, using TWRP 2.5
[Xoom Android Development] maxvsmith:
Oh crap so it's not just me. After seeing everyone else have trouble getting past the splashscreen I feel like I jynxed everyone.

I was going to try a different build too and see if that got me anywhere. But I'll use a different recovery to at least get rid of that recovery error. I hope that build 205 fixes it.
[Xoom Android Development] Ravens97:
http://jenkins.teameos.org/

Looks like we have build 205 on the way :D
[Xoom Android Development] bigrushdog:
Guess it didn't feel too good. Sorry about that. Fresh build that reverts kernel change coming up.
[Xoom Android Development] uzi2:
Same problem with 205 here

Swyped from my xoom
[Xoom Android Development] bigdave240:
wouldn't get past the boot screen. maybe a gapps issue/ wrong gapps? restored back to 197. any suggestions?
[Xoom Android Development] Alxoom33:
Yeh, 204 didn't flash for me on TWRP 2.5.0 trying 205 now.:o

Same problem with 205, stays on boot screen. Going back to 203 for now. Thanks BRD!!!
[Xoom Android Development] uzi2:
204 and 205 are test builds that don't boot. No need to go all the way back to 197, 203 is a great build.

Swyped from my xoom
[Xoom Android Development] tadiv:
I had the same issue with 204 - could not get past the Motorola logo boot screen - restored back to 203 and it's working again...
[Xoom Android Development] tonemand:
LOL, I got so excited about seeing a new nightly, that I flashed it, saw it hang at the splash screen, then saw I wasn't alone. Going back to 203.
[Xoom Android Development] ahmed007:
even i am having the same problems with the new ones back to 203:good:
[Xoom Android Development] Taysider:
Same problem here but can't remember how to restore to previous build. Tried holding V+ power etc. but no luck. Can someone help me please
[Xoom Android Development] WarLion:
same here back to 203

Enviado desde mi GT-N8010 usando Tapatalk 2
[Xoom Android Development] Taysider:
Can you tell me the button sequence as I've forgot and stuck on splash screen
[Xoom Android Development] dsbnz:
Hold Volume Up + Power til screen blanks.

When Motorola splash appears wait 3 seconds, press Volume Down. This should "Android Recovery" at top of screen.

Press Volume Up to enter recovery.
[Xoom Android Development] WarLion:
Vol up + power to reboot

when you see the splash logo wait 3 sec then press vol down and vol up to enter recovery
[Xoom Android Development] Taysider:
Thank you, easy when you know how. Will write it down for future use if required, again Thank you :D
[Xoom Android Development] bigrushdog:
Ok. Looks like that didn't go too well. I'll test kernels right here first before firing off builds. Also, I'll need FEARLESS testers for new project coming soon.
[Xoom Android Development] scottgti:
I want my money back. :) I have no fear, pm me. :beer:
[Xoom Android Development] matt0301:
I can be a tester too. Logcat and dmesg for me isn`t hard to make too, if you need

Enviado de meu Xoom usando o Tapatalk 2
[Xoom Android Development] petrossa:
More fearless than me you won't find :)
[Xoom Android Development] TBirdUK:
still needing help

flashed to 203 but google play store still not working, reflashed 3 different gapps and wiped cache, fixed permissions but still crashing out.

any ideas?
[Xoom Android Development] uzi2:
Why 3 different gapps?

Use the one in the OP and flash it in the same session as the ROM
[Xoom Android Development] TBirdUK:
did that and it keeps crashing out, tried several times and dont want to do a full reset as a couple off apps i've got i wont be able to reinstall for a couple of months till i get home (only got a 10k connection here!)
[Xoom Android Development] scottgti:
Wipe cache, dalvik cache, and system. Flash ROM. Flash gapps from op.
[Xoom Android Development] dcmodder:
Coming from 203, anyone else have a booting issue with 205? Tried mutiple downloads (one from goo.im app and directly from the site, including up to date gapps) and stuck at moto logo (not even boot loop) even tried full wipe. Just wondering if anyone else has had similar issues with 205.
[Xoom Android Development] uzi2:
Please read before posting - the answer is no more than a page or two back...

Swyped from my xoom
[Xoom Android Development] dcmodder:
Ah so it is. HereThanks for the heads up. Might want to have the op show a warning (checked there first)
[Xoom Android Development] notbrodie:
I`m not sure if it was just 203, or the combination of 203 and crossbreeder, but the UI smoothness has drastically increased. my xoom is running faster with stock freqs on 203 than OC`d 200. What a huge difference. I was a crossbreeder doubter, but now i`m a believer
[Xoom Android Development] TBirdUK:
Thanks for the info, tried it and still crashes out of playstore, it starts then straight back to desktop.
[Xoom Android Development] scottgti:
:eek: What about wiping data from play store and signing back in.
[Xoom Android Development] Taysider:
I take it your using the latest gapps 20130413

I had same problem but when I DL'd latest gapps problem solved
[Xoom Android Development] FAR1007:
Unroot

I Love This ROM it has been great work and following the builds but I am passing my Xoom on to another. Can someone please advise or provide a line to Unroot??
[Xoom Android Development] TBirdUK:
Thanks for the help, done the wipe of data and still starts then crashes back to desktop.
[Xoom Android Development] donrull:
Just wanted to send a thank you to the developer and everyone that has assisted with this ROM! I've been back here quite a few times since I installed the nightlies when notified by goo.im, but it would be nice if there could be some kind of heads up about nightlies that are known to not funtion. Regardless, my purpose was a sincere thank you!
[Xoom Android Development] Blondblueyed_girl:
Better still, it would be nicer if they are removed when known to be faulty in order to save further problems for everybody.

On 203 with everything running fine
[Xoom Android Development] rg1973:
Wonder what breaks it
[Xoom Android Development] Madmick:
Soft Brick?

*EDIT*

Ah, nice, I started backreading after posting, and I see that I'm not the only one with this issue. Builds 204 and 205 don't work, yet. Everyone's freezing at the boot logo. As a courtesy, here's a reposting of the restore sequence:

I'd never used Goo Manager to update a ROM before, but it seemed rather intuitive, so I watched a quick YouTube instructional on it, and I gave it a shot. First, I installed the latest version of TWRP. I booted into it to make sure everything was operating smoothly, and it did (I didn't have ROM manager or anything else installed). I was on the 205 nightly; it downloaded the 205 update. I clicked on it, and it took me to the Flash ROM screen with the 205 zip as an option. I added the Gapps package from the OP (04-13 JB for EOS Wingray), and I chose to order the ROM to flash first, then the Gapps package, because that was the instruction in the OP. I checked the box to create a backup, but I didn't choose to clear Dalvik Cache or Factory Reset since I was under the impression these weren't necessary steps with an update. I executed the install.

Now the screen is frozen. I gave it an hour, but no change. It's doesn't appear to be a bootloop. It's just frozen on the Motorola logo. It doesn't respond to holding down the power button. I was able to turn it off by holding the Power + Volume Up buttons simultaneously, but it quickly powers back on to the frozen boot logo (this seems more bootloop-like). If I repeat holding the Power + VU buttons then I see the text in the top left of the screen, "Starting Fastboot protocol support", but nothing happens.

Where'd I go wrong? I'm guessing that I wasn't meant to reinstall the Gapps package since I wasn't wiping the data? How do I fix this? Will I need to perform an SBF and where's the thread for instructions on that? Thanks.
[Xoom Android Development] scottgti:
205 is broken. Go back to 203.
[Xoom Android Development] Madmick:
Haha, you're a fast draw, pilgrim.
[Xoom Android Development] Geeba:
Holy cr@p!!!! I flashed 205 and thought I'd killed my xoom! gesssssss 3 days before my holiday! and just as I'd finished loading the 64gb mSD card up with movies!
[Xoom Android Development] dkahs23:
Wow....doesn't anyone read back before they flash something to see if there has been any problems......Gesh...
[Xoom Android Development] Geeba:
Problems are usually very few and haven't really ever affected me... not booting at all is something I wasnt expecting to be honest
[Xoom Android Development] uzi2:
The idea is to read before you post (Forum rule 1) ...
[Xoom Android Development] Madmick:
Cute. I ran a search of "Goo Update" and read through about three dozen posts that didn't turn up anything that revealed the misstep I presumed that I'd made, so I made my post. My assumption was that the fault was with me, and had nothing to do with recency, or nightlies, so forgive me for making the same mistake that over half a dozen other posters in here also made. I made a point of editing my post with the fix once I'd found it.

Sheesh. Let the mods moderate, maybe.
[Xoom Android Development] kmcrane:
For a dying device, one would think any chatter, even repetitive questions, are good. There will be a day where these forums are dead. We're here for the same thing yet we bicker.. My 2 cents.. I don't say much but I read everything.
[Xoom Android Development] Muffycheeks:
AGREED!!!
[Xoom Android Development] bigrushdog:
Regrettably I don't have perms on goo to delete files or else I would. I'll try to get a clean build up.,
[Xoom Android Development] Ardvaark:
Thank you!!:fingers-crossed:
[Xoom Android Development] Blondblueyed_girl:
Not blaming you brd we all have limits and we were brought up with the premise that you don't bite the hand that feeds you.:D
[Xoom Android Development] miillaaad:
download the ROM and Report later

tanx a lot
[Xoom Android Development] drewski_1:
???

whoever this was addressed to, 203 is the last stable build on Goo.

don't try 204 or 205
[Xoom Android Development] 48dodge:
I can't change the settings on my goo manager. Still getting a notification every hour even though I have it set for 24hrs. Any chance to just resubmit 203 as 206 until you make changes? As an aside does anyone here use the stock browser? It had been my favorite because of quick controls but the lag grew unbearable. Didn't know if it was a gapps issue since it appeared to get slightly worse after the last gapps release. Testing other browsers out now.
[Xoom Android Development] Blondblueyed_girl:
Have been using stock browser ever since the Xoom came out, because like you I like the quick controls. Generally speaking I haven't noticed any lag effect. The only problem I sometimes get is a distortion effect in some parts of the screen, generally its a graphic, sometimes text mainly on the left side of the screen. Don't know if its software or hardware related. Flash works fine and most of the time the browser is OK. May try another browser to see if it still happens.
[Xoom Android Development] Muffycheeks:
One word. Uninstall !!!
[Xoom Android Development] 48dodge:
Uninstall goo? I almost did but brd sounded like he was updating soon. Not a big issue but I always get excited when the notification pops up.
[Xoom Android Development] trunzoc:
BRD, any chance you can just rebuild 203 as 206 and upload that to stop the update reminders?
[Xoom Android Development] scottgti:
Just turn off notifications. If that doesn't work, it isn't brd's problem.
[Xoom Android Development] 48dodge:
The suggestion was not to remove it. It was to repost 203 as 206. How is that a bad suggestion? He's done something similar before
[Xoom Android Development] Moscow Desire:
Knock it Off Please

Folks need to knock it off with the off topic flaming. Keep things related to the thread.

Cheers

MD
[Xoom Android Development] shanigami:
Arrogant posts pointing out people's missteps are just as useless as the post they refer.

Just a little food for thought there...
[Xoom Android Development] bigrushdog:
New project almost online. Will have test builds soon. I think you guys will feel your xoom enjoying a fresh breath of speed!
[Xoom Android Development] paultbear:
Hooray.

Even though I hardly qualify as a power user, I am really happy to see some ongoing Xoom support. I've tried several roms and keep coming back to the Eos roms.. first on my xoom and then the nexus 7 and now the nexus 4 ( this will stay stock for a bit :o)

Thanks to all of Team EOS - hoping to see you around here for a long while yet.
[Xoom Android Development] petrossa:
Same here. Quality work by a committed team.
[Xoom Android Development] wingnutta:
My wife loves you BRD.. you prevent me splashing out on a new tablet!!!! :laugh: She appreciates your work as much as i do and she never uses my xoom!!! :good:
[Xoom Android Development] notbrodie:
[MENTION=507808]BRD[/MENTION] can't wait to see what you've got cooked up!
[Xoom Android Development] gadgetfl:
I am hoping for a 1080p IPS display resolution hack and a 128gb SSD drive compression mod. Come on.. You can do it.

Wah wah :silly:
[Xoom Android Development] bigrushdog:
Yep. This build comes pretty close. Got one little xoom snag to work out. Due to optimization, all the libraries and apps are larger. And, as you guys know, xoom system partition is already nearly full. So the xoom build will end up being the most unbloated build ever. Many things like Calculator will need to be installed as user apps. But I'll make a tidy little side package for all the extra bloat. Should have a successful build tonight.
[Xoom Android Development] adoublearonn:
Will this ROM support the DM9601 based USB to Ethernet adapters?
[Xoom Android Development] bigrushdog:
Yes. I'm using the exact same kernel and device tree. It looks like we'll have to come up with yet another gapps solution. /system is simply too small. I think tonight I'll open a discussion thread in general for testing builds and figuring out gapps.
[Xoom Android Development] dsbnz:
BRD, Is there any specific benefit to having gapps in system, as opposed to installing from Play Store as user apps? Ive been using Banks Minimal Gapps package (i think its about 8.5mb) which just contains the bare essentails. The system partition has approx 32mb free, using v203 build Wingray. It works without problem (as far as i can tell), but i dont know if i'm missing out on something doing it this way? If not, would it be easier to do the same, have minimal gapps, and each user install apps from Play to meet their own requirements?
[Xoom Android Development] petrossa:
Me too I prefer the smallest gapp possible. At least half I never use, the rest seldom. I guess playstore is the only one I use really. All the rest is even annoying at times
[Xoom Android Development] bigrushdog:
It looks like Banks Minimal Gapps will likely be the solution going forward

http://xdaforums.com/showthread.php?p=43796331#post43796331

New project testing and discussion thread. No builds just yet, but i'm hoping for tonight or tomorrow.
[Xoom Android Development] trunzoc:
Are you doing a TiBu restore in between there?
[Xoom Android Development] jodtalingchan:
Hello there, first of all, thank you teameos for the incredible work for our xoom! I just wonder that how to set animation transition to off like 4.1.2 version. I notice that thee is no developer menu anymore in the setting. Not sure if animation transition can be set or not ...

Thank you

---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------

And one another thing for your info, overclock value doesnt stick on boot. Is it the same for everyone?
[Xoom Android Development] kuroguy:
Sorry. Flashed 158 and the 1207 gapps. Camera just says there was an error launching now. I'm sure it'll get worked out eventually. Keep up the great work team eos.

Never mind. It was apps organizer causing the problem.
[Xoom Android Development] uzi2:
Camera works fine with 158 and 1207. You will need 1208 for calendar.

Swyped from my Xoom
[Xoom Android Development] Duncank:
And when you press the "next song-button" in that window? Does the album art and song information appear? I've had this for a very long time now. If I remember correctly, it only happens when I launch Google Music from the widget, but I'm not sure about that.
[Xoom Android Development] drewski_1:
I did a TiBu restore before setting up the PIN. User apps only.
[Xoom Android Development] yosterwp:
Actually, in Android 4.2 the developer menu is hidden by default. To un-hide it, go to Settings -> About -> And hit Build Number 7 times. As you hit it a toast notification should popup telling you that you are unlocking developer settings.
[Xoom Android Development] tdarren:
Yep, that's exactly what happens,you have the same thing as me, but I launched it from the app drawer.

It also does it when I press the notification of Google Play Music in the notification panel.
[Xoom Android Development] lorenza:
This is posted a few pages back. Go to about tablet in settings. Tap on build number 7 times and developer options will appear.

Sorry I didn't see that someone already posted the answer.
[Xoom Android Development] xoom68:
How to mount an external Drive

Download Stickmount from the Play store

Try and mount the drive once and then browse to Sdcard/Usbstorage/sda1 with ES or Root Explorer, it will be empty. Leave browser open there.

Unmount.

Mount drive. Open up file browser again. and you will be able to see all files, and other applications will see them as well :)

Of course once the folder is created, its a case of browse, then mount.

Cant take the credit for it, read it in the Stickmount thread.
[Xoom Android Development] drewski_1:
Did 157+12/8 gapps and 158+12/8 gapps with Factory Reset. No TiBu restore of user apps.

Same thing. PIN unlock works in current session, but doesn't after reboot.