yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Err0xx:
UPDATE: I just reflashed build 120 on my Xoom to make sure I wasn't crazy. All GApps there and accounted for.

No idea why they aren't wiping if that script is indeed running. But mine are remaining through a nightly flash.

I assume Serranom (the above poster- sorry for misspelled name if it is) is seeing the same behavior.

Sent from my Galaxy Note SGH-I717 running The Collective's AoCP ICS ROM.
[Xoom Android Development] Err0xx:
Using newest TWRP currently, used newest Rogue and CWM touch when the same behavior occurred on the EOS ICS roms
[Xoom Android Development] Err0xx:
The way it is right now I'll flash the newest gapps once and the following 15-20 nightly builds and never reflash gapps, not once. Then eventually if new gapps are released, I'll flash the next version just to update em, then never reflash unless the gapps are updated.

Had the Xoom since pre order and had it rommed since a week or so after ownership and I've done the same with gapps flashing the whole time. Never had a single real issue. *knock on wood*
[Xoom Android Development] twinkyz1979:
hmm....
[Xoom Android Development] bigrushdog:
Just to clarify, new recoveries run a backup_gapps.sh script prior to executing the ROM flash. Gapps are temporarily backed up to /tmp in root then restored after the ROM has flashed.
[Xoom Android Development] Err0xx:
I suppose that would certainly explain it then. Thanks for the info.

Sent from my Galaxy Note SGH-I717 running The Collective's AoCP ICS ROM.
[Xoom Android Development] bigdave240:
running rev 122 and it seems very fast. Not sure what the changes were yet but liking it so far

Edit: one thing i noticed is that effects like big eyes and backgrounds dont crash the camera now.
[Xoom Android Development] serranom:
Those have been working for me since 120. Think that is when they fixed it. FYI :D

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] rob62551:
+1. 122 has really improve upon all prior JB builds. Speed across all apps and UI.
[Xoom Android Development] bigdave240:
Yeah some said it was working on 120 but for me everytime i tried it it still crashed the cam until 122. Not sure why it was different for me.
[Xoom Android Development] dweezle:
I've been trying to install rev 122 / Stingray for a couple of days. I'm coming from 4.0.4 and have tried it from CWM and TWRP. I wipe everything and flash it simultaneously with Gapps 20120802. Each time it appears to load without error but when I get to the opening screen, it won't unlock. I swipe to the unlock icon, it highlights and then snaps back to the center with the locked icon. Both the camera and google load without problem. I have checked the MD5s of both the files and they check out perfectly. I've tried rev 119 and 120 same results.

I see several people posting with this identical problem. I am not sure what to try next. Any suggestions would be appreciated.
[Xoom Android Development] mikedyk43:
I had this same issue and if I remember correctly, after wiping data, I did a fresh install of the latest EOS ICS ROM. Following a successful boot, I returned to recovery and then installed the EOS JB ROM without wiping data and it has worked ever since.

Try this out and post your results.
[Xoom Android Development] bigdave240:
dead link?

---------- Post added at 07:01 AM ---------- Previous post was at 06:52 AM ----------

When you say you wipe everything are you doing a full wipe (factory reset)?. I only did cache and dalvik the first time i loaded jb and it worked but there were issues and the devs recommend a full wipe before going from ics jb. Search this thread as there were one or two others who had similar problems.
[Xoom Android Development] apollyon0810:
URL hacked

http://xdaforums.com/showthread.php?p=27421477
[Xoom Android Development] dweezle:
Thanks, I tried your method and still got the same results (could not unlock).

What did work was my wife telling me to stop messing around with this and watch "A Fish Called Wanda" with her. I am the stuff that sitcoms would have a field day with. I took the Xoom to the couch and kept fiddling with it while watching Jamie Lee Curtis's !@#%. While partially distracted I saw that Rom Manager would let me install from my SD Card via CWM. I figured, "why not". I installed, the Rev 122 alone. I checked Wipe cache and Dalvik in the Rom Manager options and off it went. It loaded fine! Then I returned to CWM recovery and loaded the gapps-jb-20120802-eos-signed.zip. All went well. Until then I had always been installing the Gapps and the nightly, as a single operation. I thought that I read that in the installation instructions.

Sorry if I am blathering, but lack of sleep and random attempts at installing this, has me a little dingy. Thanks for the help. There is something very satisfying when I bungle through something like this. I never really understand what happened, but I get obsessed until it happens. Now I just have to play with this to see, where I've landed.:highfive:
[Xoom Android Development] bigdave240:
the process for incremental updates is to flash the rom then once complete you then flash the gapps then reboot. that seems to be the consensus of the devs. We dont have have to wipe cache anymore. But you can do it all in one recovery session. Not sure what happened with yours though.
[Xoom Android Development] SamuriHL:
I let goomanager script it for me. Select the rom and gapps and have it reboot into any open recovery supporting recovery and off it goes. I just did 122 a few minutes ago with TWRP and it worked perfectly. I did have to fix goomanager to point to the proper path to my goomanager directory so that recovery can find the updates, but, it wasn't difficult. SO easy. :)
[Xoom Android Development] TheLostBuddha:
Just wanted a quick consensus.. love the Rom, running 122 currently. Smooth, fast, clean - only issue is battery. Disabled all notification settings of all apps, disabled mobile network (no plan, no data), and charged full. Unplugged and checked on it this AM and 4% battery life. Aside from grabbing bbs and troubleshooting myself (charging now to do that) any one have any quick pointers or ideas?
[Xoom Android Development] Err0xx:
That's a rogue app with some background process or something.. Yesterday on 122 I did 25h unplugged with just over 8h screen on time. It's DEFINITELY not the rom, this is the best battery life my Xoom has ever had. I use about 15% screen brightness.

Sent from my Galaxy Note SGH-I717 running The Collective's AoCP ICS ROM.
[Xoom Android Development] rob62551:
I noticed a drop in battery life last week. I luckily thought to look into settings/apps/running.

I had been viewing a movie utilizing Google Play Movies & TV. According to settings this app was running still many hours after watching movie. Stated something like transfer service was active.

Anyhow, I now make sure to stop this app if I ever use it again. According to battery stats, it was accounting for about 35% of use!
[Xoom Android Development] johnny0911:
Wow!
[Xoom Android Development] Asphyx:
Quick Question for the Devs

What would be the downside to editing my build.prop ro.build.tag to "" instead of test-keys.

I'm trying to run the Time Warner app and it checks for this property for some dumb reason to limit use to non-rooted devices.

Is there a reason for leaving that property at test-keys that I'm unaware of?
[Xoom Android Development] sovereign_313:
*cough* http://xdaforums.com/showthread.php?p=24975697 *cough*
[Xoom Android Development] trevormalachi:
Sorry if this has already been asked but there is way to many pages to read.

Just flashed this and is butter but am not picking up any 4g. Is that a known problem?
[Xoom Android Development] sovereign_313:
Did you flash the radios?
[Xoom Android Development] CIPuyleart:
I installed nightly 122 yesterday (been out of town for a week), and have now lost all internet connection except WiFi. I had no issues up through nightly 118 that I had on before updating.
[Xoom Android Development] Asphyx:
LOL yeah unfortunaly they updated the app and that one no longer works! But thanks anyway!
[Xoom Android Development] hchxoom:
Just search this thread for 4g or radios and youvll find several conversations and a fix. You will need to flash updated radios, and you'll need to do so using the latest Rogue recovery (EOS recovery wont work for this purpose). The zip to download will be among your search results. Happy hunting!
[Xoom Android Development] dccrens:
ICS To JB - So Smooth

I was on EOS ICS Stingray 99 and just jumped to EOS JB Stingray 120. WoW! the upgrade was smooth as butter. I D/L'ed the 120 zip and the GAPPS packages. Moved them to my "external" and booted into recovery. Wiped cache and dcache. Loaded 120 and GAPPS then rebooted. Everything works including 4G and WIFI. Overclocking to 1.6 is stable as all get out. The only thing I have found so far is that the ICS Browser Pro i was using FC's. But the stock browser is good enough. Another thing that I noticed is missing is the ability to have icon links on the taskbar. Did that move or go away?

Team EOS rocked this on out of the park.
[Xoom Android Development] CIPuyleart:
There are even newer radios than the previous ones then? I've had working 4G for a long time on the EOS JB roms...just this latest one broke them. I'll do some looking, but I was under the impression that the radio hadn't changed recently.

EDIT: Flashed back to build 118 and my radio is back and running. So is there an updated radio between build 118 and 122?
[Xoom Android Development] shadowace:
Advice?

I was about to slap on an EOS nightly build for JB and decided I would go ahead and update my recovery as well. So I did a full backup in titanium of all my apps and data. Then I booted into the CWM recovery I had back at my first root and did a backup there. I then installed the rogue touch recovery, did a full factory reset and wipe, and installed my new ROM, and the gapps package along with it.

Upon reboot I only get to recovery, it will never boot into the rom. I restored the backup I have made today and got the same result.

any advice?
[Xoom Android Development] Mjamocha:
You might need to use your old CWM recovery, to restore your backup.
[Xoom Android Development] bigdave240:
havent seen a newer one. Maybe the rom you dl'd was corrupt?
[Xoom Android Development] dweezle:
I flashed into EOS JR003H Nightly 122 (9636727). Wifi connection is fine. I am not on a data plan with this device. Is there some way for me to check if my 3G and 4G is functioning?
[Xoom Android Development] hchxoom:
No, I misread what you came from and thought you didn't have the radios required. Agree with BigDave, I'd try a fresh download and reflash... I haven't seen any problems reported with 4g connectivity since the first two iterations of EOS JB.
[Xoom Android Development] wesamothman:
Don't use rouge touch recovery, it has its issues, use eos r6 recovery normal version , not touch... or twrp touch recovery, just search the dev section for both and flash either one.

Twrp recovery, http://xdaforums.com/showthread.php?p=28988754

Eos r6, http://xdaforums.com/showthread.php?p=24956587
[Xoom Android Development] thingnblah:
Throughout this thread rogue has been recommended as the go to recovery, what are the issues that it has??? I have been using rogue since AOKP without issue.
[Xoom Android Development] wesamothman:
I don't mean to be sending negatives here , but it is a choice of preference,

All appreciations to the devs of recoveries, they are great... but I checked the thread of rouge touch recovery and saw some ppl complaining about success/failure or might be that it won't be working that nice with aokp systems... it is your choice at the end, but no harm if you try twrp :)

And again , no misunderstanding please, devs are great, their 'products' are greater.
[Xoom Android Development] shadowace:
Thanks, that did the trick! Flashed over to TWRP, re-did the wipe, installed JB nightly, Gapps,and booted. Everything looks great. Really appreciate the help!

Shadow
[Xoom Android Development] wesamothman:
Great and I am glad I helped and all is OK now at your end :)
[Xoom Android Development] thingnblah:
I didn't take it as negative I was just curious as to the issues you had seen/heard of. I have been contemplating moving to TWRP but the general consensus has been that rogue is the recovery to use for EOS 3.0. In the end I will most likely move to TWRP, it has been great on my EVO LTE.
[Xoom Android Development] SamuriHL:
I use TWRP. With Open Recovery support, flashing things from goomanager is SO easy and nice.
[Xoom Android Development] TheRandom1:
I have been using Rogue for months without a single issue.
[Xoom Android Development] dboftlp:
Moved to Rogue with EOS 3, no issues, rock solid, love it. Have been hearing great things about TWRP & the added bonus of goomanger automation has me... considering it. I'm gonna go out on a limb & say I won't be able to restore any previous backups made with Rogue if I switch to TWRP, am I right?

tia,

@dboftlp

Swyped from my GNex running TeamEOS 3 nightlies.
[Xoom Android Development] serranom:
That is correct if you want to restore. Nandroid back to your backup you want then nandroid with twrp and so on I just backed up my current with twrp. Everything was working great so didn't worry about my other nandroids. But again that was just me. I have used rogue , eos, twrp, and regular cwm. I like twrp my self.

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] G8orDroid:
Where did you get a version with Open Recovery support? I'm using runandhide's port and it doesn't seem to support it.
[Xoom Android Development] SamuriHL:
I got it from goomanager. twrp 2.2.1 I think. I'm not 100% sure on the version.
[Xoom Android Development] bigrushdog:
Yes it does. Change the goo manager path to /data/media/goomanager and make sure whatever you wanna flash is in that directory. In recovery you will get a screen full of fail. Ignore it. It works fine.
[Xoom Android Development] SamuriHL:
Yup. That's what I did and it works perfectly.
[Xoom Android Development] kcrudup:
Oh ... <ahem> ... um, ... uh, ... well ... uh ...

I only do the kernels anyway! :D
[Xoom Android Development] Mjamocha:
LMAO!

Any chance of a Developement Overlay for Jellies? We Miss the goodies and BT5 candies.
[Xoom Android Development] sovereign_313:
I feel cheated... what's a Development Overlay?
[Xoom Android Development] G8orDroid:
Doh, that makes sense. Didn't even think about the path and new mount points being the problem. Thanks.

Edit: Perfect timing too, I get to test it on 123.
[Xoom Android Development] dboftlp:
123 is up. Looks like a few changes were committed by the team. [informational]

From jenkins:

Changes

Initial implementation of Soft Key controls (1 of 2)

Merge "Implement SoftKey Long Press actions (2 of 2)" into jellybean

Universal Activity picker dialog.

Implements its own OnComponentSelectedListener with interface.

The callback passes a flattened ComponentName string. Can be easily

used with LongPressActions or any custom button.

Thank you TeamEOS for continuing to build on this awesome ROM!

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] SamuriHL:
Soft Keys! YES!!!!
[Xoom Android Development] trevormalachi:
Can someone post the radios cause I can't seem to find them
[Xoom Android Development] Droidem:
should be here. http://goo.im/devs/teameos/radios/
[Xoom Android Development] CIPuyleart:
I thought about doing that, then got sidetracked. Pulled down build 123 this morning and flashed it, and everything is working. Thanks! :good:
[Xoom Android Development] shadowace:
4g issues

I am also struggling with 4g connection issues. I flashed the radio update from this thread (via twrp) and then flashed build 123. Still no luck, any suggestions on what else to try?
[Xoom Android Development] kcrudup:
A build was leaked today that's allegedly the Official VZW MZ602 build; I've incorporated the changes (which didn't break anything here, at least) and they should be in the build that runs later tonight.

Try that; but if you still have problems after that (and your radios were truly flashed correctly (read thru this ENTIRE thread!)), I'm not sure what to tell you. What exactly do your "4G connection issues" entail?
[Xoom Android Development] SamuriHL:
Sweet!! That's going to rock.
[Xoom Android Development] kcrudup:
Don't get your hopes up too much- the changes that I know are going in are extremely minor (a new MZ602-based (and hopefully-legitimate) build fingerprint, which is pretty much only used in the market) and while I don't have any idea what exactly went into the new RIL/LTE/VZW code, we weren't really broken before with the ICS versions of same (once we made a Java compatibility fix).

Of course, once it hits the country as whole, maybe there'll be improved connectivity for some.
[Xoom Android Development] SamuriHL:
Is there a new radio version I assume?
[Xoom Android Development] shadowace:
just wont connect to Verizon 4G. I can test the SIM in another Xoom and it is fine. Will reread about radio flash to ensure I didn't miss anything.

does anyone think TWRP could be the issue? I read to only use rogue to flash the radios, but with my recent bad luck with rogue I kind of hate to put it back.
[Xoom Android Development] Spectredroid:
I could only flash radios with rogue. Nothing else worked for me.
[Xoom Android Development] Droidem:
Has anyone noticed that .nomedia files do not work for the gallery?

Sent from my Team EOS JB Xoom
[Xoom Android Development] Err0xx:
Used twrp to flash radios and I'm fine. 4G is the same 4 bars at my house as always. On build 123.

Sent from my Galaxy Note SGH-I717 running The Collective's AoCP ICS ROM.
[Xoom Android Development] sovereign_313:
I was able to coerce Motorola to upgrade my tablet to 4G/LTE after they closed the official upgrade window (cost me $55 bucks, but what the heck ya know?) and just got it back yesterday. I had to call VZW and tell them about it, and read them off my sim number... they did something crazy on their end, and then going to settings / wireless & networks / More / Mobile networks and clicking "Verizon data service" it basically worked after like 15 minutes. *shrugs*
[Xoom Android Development] TheLostBuddha:
Just a quick update.. BBS showed me the issue. What was going on was i had pulled my sim out as i was no longer using the wireless on it - turns out I had ril inquiries constantly keeping my xoom awake. Switched to the wingray rom and im at 92% after 28 some hours. Thanks again everyone for the great rom.
[Xoom Android Development] freeky1:
That was nice of them to upgrade you after the fact. You're the first person I have heard of them doing that for.

When I need 4g on my Xoom and don't feel like tethering to my phone using Foxfi, I just pull the similar card out of my Bionic and stick it in the Xoom.
[Xoom Android Development] CIPuyleart:
So...got to work this morning and my tablet was showing three bars but said "No Internet Connection." Tried turning on WiFi and it wouldn't connect to our network at all. Rebooted, and nothing. All of this was on build 123 that was working fine yesterday. Flashed back to build 120 (the last build that has not given me any 4g issues) and all is fine again.

Going to give build 124 a try this morning...this is getting frustrating.

Update: Build 124 is up and running with full 4G connection. WiFi won't connect here at work still (will have to test at home tonight to determine if it's related to the Xoom or the work WiFi). Rebooted several times, and still have connection each time. Guess I'll have to see if I can get it to deep sleep so I can wake it up and then see if the connection sticks.
[Xoom Android Development] Droidem:
Not sure if the fresh install did it or even if it was nightly 123 but the .nomedia file works now

Sent from my Team EOS JB Xoom
[Xoom Android Development] joshrys:
I'm having some poor battery life on JB which i wan't having on ICS. So i installed CPU spy and i am getting 0% deep sleep. Any others noticing this? any suggestions as to what the culprit is or a possible fix? I am on build 123 and using the kernel that comes loaded in the rom.
[Xoom Android Development] wesamothman:
Deep sleep is not ROM issue, mine sleeps link a baby, there must be some app waking up your device or WiFi .. install betterbatterystat app from the market, and reboot your device, hen look it for n hour or so, then open the app and check the stats.
[Xoom Android Development] thingnblah:
Have you flashed the radios??? What does it say under baseband in settings???

He is getting 0% deep sleep, most people that have had this issue have fixed it by flashing the new radios. It could be an app but checking the baseband is quick and so is flashing the radios.
[Xoom Android Development] dboftlp:
Looks like lots of goodies in 124. I'm still on 122, so will probably flash this as soon as it's finished downloading.

Done, brb :D

http://jenkins.teameos.org/job/stingray/124/

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] simonmiller1:
I'm not getting any deep sleep either. I just flashed this on my Xoom (Stingray) after not using it for months. I've also had a few random reboots and one sleep of death. Would flashing the baseband/radios help? I'm currently not using the 4G plan, just wifi, but it is 4G upgraded with a SIM.
[Xoom Android Development] Draxin:
I personally haven't noticed much difference with the battery from ICS but, I am getting quite a few random reboots and unresponsive apps. Mainly when I am using apps that require wifi (I don't use 4G.) Netflix is really bad, had four last night on it alone in a two and a half hour period. Xoom is going into deep sleep fine.

Forgot to add, I am on 123 right now, had the randoms with 122 as well though
[Xoom Android Development] bigdave240:
Under settings, system there is a new selection for wifi regulatory domain. I had to selecg the usa to get wifi working
[Xoom Android Development] telcodave:
quick question: If i am already on this rom, do i need to do a full wipe to flash an updated version?
[Xoom Android Development] PC Jona:
hey guys...stupid question i cant solve....any way of changing the number of home screens? i only want one...i have 5 -_- helpp
[Xoom Android Development] SamuriHL:
Nope. Just update it.
[Xoom Android Development] PC Jona:
helpppppppppp -_- dont want to use another launcher.
[Xoom Android Development] Draxin:
Keep all your apps on one and don't flick your finger????? That is what I do now, used to use Nova, it's ok, I just don't care enough to reinstall it after switching from ICS.

If it is the wallpaper you are worried about, you can use a free app called "multi picture live" That would put your wallpaper to size of screen and it would be on each homescreen rather than stretched
[Xoom Android Development] joshrys:
Yeah, I hadn't worried about it too much until yesterday so I flashed rogue recovery then the radios, ROM, and gapps. Baseband says CDMA_3.1a something. I get 4g connection fine like this. Just put betterbatt on and will let it sit for a while and report back. Also read in about halfway back someone said to disable mobile data and see if that helps. Trying that also.

Thanks for the assistance!
[Xoom Android Development] trevormalachi:
I seem to be at a loss with finding any kernels for JB. Am I just blind or no?
[Xoom Android Development] twinkyz1979:
Why do you need another kernel other than the one it comes with?

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

Then don't complain about what comes with it.
[Xoom Android Development] tumpy:
thanks, this option work for me after i download the offline us voice speech recognition pack....
[Xoom Android Development] tomcrown1:
Is flash dead with jelly bean?

If it is die anyone miss it?

I do not know if it is worth upgrading because I may not get flash.