yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] kentedman:
So.... we're assuming you have a valid data plan with Verizon and have a working SIM card installed? Technically if you've bought and activated a data plan with verizon, the 4G data will work on your Xoom even without "Activation". If you've done a factory reset and installed a clean install of EOS 164 (or 163, or 162...) then on your first boot the Xomm should start going through the set-up process. The first thing it does is try and find Data service, and then it will say "Waiting for a Network to complete Activation". It will sit on this screen for 5-6 minutes, and then finally pop up an error page saying the device could not be activated. Hit the "Skip" button and complete set-up with-out activating. At this point, your 4G connection will be working anyway (assuming again, you have a data plan). To officially get your Xoom to activate and register on the Verizon Network, now you need to go into network settings and change the Subscription type to RUIM/SIM. I'm not sure why yours keeps reverting, but you should have Data connection either way.

Honestly, I'm not sure what the difference is (if any) by using data with NV set as opposed to RUIM/SIM?
[Xoom Android Development] liftman-:
also did you update your radio firmware a while back? i think it was for 4.1
[Xoom Android Development] freeky1:
My Xoom has never been activated, but on many occasions I pulled the SIM out of my old Droid Bionic and stuck it in my Xoom. It worked fine, and if I log into the Verizon website while the SIM is in the Xoom, it shows a picture of the Xoom on my line.
[Xoom Android Development] liftman-:
did you have the sim in on the 1st boot?
[Xoom Android Development] freeky1:
When Motorola returned my Xoom to me after the 4g upgrade, it had a SIM in it. I was never prompted to activate it at any time. Any time I needed internet on my Xoom, I would just pull the SIM out of the Bionic and stick it in the Xoom, and boot up. No activation at all. I did it 20 or 30 times during the time I had the Bionic. Now I have the Razr HD, which has a micro-SIM, so I can't do it any more.

As a matter of fact, the SIM that is only Xoom right now is the one that Motorola sent me after the 4g upgrade, and it has never been activated.
[Xoom Android Development] bigdave240:
Other than the screenshot/ cam issue, 190 has been uber stable for me. I have not had even one single lockup so far. Awesome job guys!
[Xoom Android Development] atlmatt:
HELP!!!

I downloaded nightly 191 went to install it like I normally do using TWRP 2.5.0.0.

the flash failed and give me a error:

e:could not create file for updater extract in /tmp/updater

It wont go past the splash screen, but I can access recovery. I don't have a backup due to my forgetting that I swapped out my SD card which had my back up on it.

Am I screwed? I have never ran into a single issue ever that I could not easily fix, or fix from a back-up.
[Xoom Android Development] jonoathome:
Oops wrong thread..
[Xoom Android Development] Vnvjeep:
I seem to be having issues with contacts synching with my Exchange server using the "people" app. Its just showing some contacts from my gmail account. I've tried wiping cache/data, starting over, but no dice. It says its synching my contacts. I have no prob with email or calendar. Does anyone else have this issue? Any ideas? I'm on build 190.

Thanks,

-Mike
[Xoom Android Development] atlmatt:
Anyone available to answer my question? I am stuck
[Xoom Android Development] runandhide05:
If you wait maybe longer than ten minutes to repeat your question maybe someone cn help u.

Il be that someone...

Download was probably bad did u check md5 sum before flashing?

Either way, just download a rom and gapps from a pc place on your sdcard flash and processed as normal
[Xoom Android Development] shpitz461:
I downloaded it through goomanager, booted into TWRP 2.5, flashed ROM and january GAPPS, no problems. Try to re-download like RnH suggested, maybe flash recovery again.
[Xoom Android Development] Asphyx:
Well try re-flashing an older version and see if that works...

Make a backup this time and then try 191 again.
[Xoom Android Development] bigdave240:
191 gave me a bad case of the lags. Mostly browser but everything was affected. Could be just me (happened before) but i just thought i would throw it out there and see if anyone else saw it. Rolled back to 190 and all seems well now.
[Xoom Android Development] bigrushdog:
Lol you make it sound like bubble gut after backyard bbq.
[Xoom Android Development] bigdave240:
Bwahahahaha
[Xoom Android Development] freeky1:
It's nice to see you guys are still chugging along with the Xoom. I miss mine a little, but my wife still has her wifi Xoom. I rarely touch it. Happy Memorial Day!
[Xoom Android Development] te0o:
Guys, sorry for asking such a lame question, which has been probably answered a million times, but I couldn't find it in the thread. I have a MZ601 3g Xoom which is completely stock 4.0.4, even without root. Can I install an AOSP rom like this one on it and if I can - what should I do?
[Xoom Android Development] EvilDobe:
You can. You need to unlock, root/flash a custom recovery, then your rom of choice.
[Xoom Android Development] codesage:
I came from a very stable 150 release (I believe), to the 190 4.2.2 release...and since then, my netflix hasn't been working right.

Every few seconds, the screen will 'flash' what appears to be a different image (imagine something like what happens in Fight Club, minus the porn part). It's just annoying if I'm watching it on the Xoom itself, but if I play it through HDMI, every flash causes the video output through the HDMI to catch and pause, while the tablet keeps playing on normally.

I've tried clearing data/cache, and even reinstalled the app, with no help. This has happened on 190, 191 and 192 nightlies now. Anyone else seen it or have a fix?
[Xoom Android Development] reitman1:
I can confirm this has happened to mine on 192.
[Xoom Android Development] codesage:
I updated to 193, and tested it out by watching netflix normally for a few. I might have just missed it, but I don't think I saw any flashes on the screen on this one. Haven't tested it in the HD Dock yet though.

Also, I clear data/cache and uninstall/reinstall on each update
[Xoom Android Development] xyrcncp:
Has anyone experienced their xoom completely crapping out after being sleeping for a few days? I was out of town for about 2 weeks and my tablet was on its dock for that time. Came back home, tried to use it and my Google account is gone from it, rebooted a few times, nothing. I figured I'd reflash 190 (the build I had) and now it won't get to Setup. Just cycles between two errors "Process com.google.process.gapps has stopped" and "Setup wizard has stopped".
[Xoom Android Development] bigdave240:
I think you are supposed to do a factory reset then flash the rom and gapps again. at least thats what it says on on the screen when you flash. got a good nandroid? you could always go back to that and upgrade from there
[Xoom Android Development] xyrcncp:
Yeah, I had done that for 190 and nothing. Downloaded 193 and the latest gapps and reflashed and it's mostly good now.

The only thing was that during setup I got the message that data service could not activate. I did notice that under Settings > About > Status, the MDN shows mostly zeros, maybe I never noticed it before, but I thought that a while ago it showed my actual Verizon-assigned number for my tablet.
[Xoom Android Development] bigdave240:
when was the last version you had that data worked correctly?
[Xoom Android Development] xyrcncp:
Actually, data has worked fine, in 190 as well actually (before the weirdness happened). I just had never seen the message where data couldn't be activated before (even when I first flashed 190), only after flashing 193 today did I see that message. However, even though I don't see the MDN as my tablet's phone number, I have 4G data connection.

It's just all weird that without touching the tablet for 2 weeks, my Google account disappeared from the tablet.
[Xoom Android Development] runandhide05:
Can u guys give feedback on this http://xdaforums.com/showthread.php?p=42254555
[Xoom Android Development] castrand1:
Can't activate network

I just flash the latest nightly (195). This is the first one for me, as I was on the stock rom prior.

After flashing, everything worked, except for failing when trying to activate network. I tested and it seems to work. I get four bars, it states 4G.

It's fine, till I reboot. Is there a solution?

*** EDITED ***

I was wrong, I was on build 194. Just updated to 195 and all is well.

Awesome ROM.
[Xoom Android Development] bigdave240:
Yeah 194 was a bit wonky for me too. The lockups when sleeping returned and the browser seemed slow. So far no issue with 195. Seems to be great as usual from the eos team
[Xoom Android Development] rlmesq:
Is swipe to wake enabled in 195? Can't seem to find it in settings.
[Xoom Android Development] bigdave240:
Nope. Been turned off for a while now. It was pretty cool but i think it may have been causing problems but not sure.
[Xoom Android Development] bigrushdog:
When a sweep2wake enabled kernel is installed the setting becomes available.
[Xoom Android Development] Asphyx:
I'm sure it has been discussed elsewhere so apologies for my lazy A$$ asking of this...

But do the releases flash the current Kernal each time and if we use something like ExperimentalX does that patch get wiped out during a flash?

From my understanding ExperimentalX just patches whatever Kernel you have when you install it.Not sure if it actually survives subsequent flashes if the Kernel is included with them.
[Xoom Android Development] runandhide05:
Kernel is included in the rom zip, and will replace whatever u had. So say u had exp kernel then flashed eos rom you now have then kernel included in Eos
[Xoom Android Development] Asphyx:
Thanks Runandhide...

That's what I thought was going on....Not that it matters much to me as I didn't like the swipe to wake thing in the first place! LOL

It seems that's when the Wake up from sleep problems started! LOL

I'm sure there is some other goodness in ExX and I'll see if there is something in there worth reinstalling but the unit is working like a champ as is and As an Engineer I follow the if it Ain't broke don't fix it approach! LOL
[Xoom Android Development] runandhide05:
As should everyone in life. . .
[Xoom Android Development] Asphyx:
LOL at least until Goo Manager tells them there is another update and they run to flash it without checking reports first! LOL
[Xoom Android Development] rlmesq:
Ahem. I resemble that remark.
[Xoom Android Development] Asphyx:
Your not alone there...I broke the habit back when WinMo was the OS of the day! LOL
[Xoom Android Development] mekeleee:
ty
[Xoom Android Development] bigdave240:
Flashed 197. Normally a newly flashed rom runs fast and slows a bit over time. 197 seems really fast with browser pages loading very quickly. Faster than normal. Of course this is all subjective and could be just a feeling but time will tell i guess. Thanks for your efforts as usual!
[Xoom Android Development] tselling:
I am seeing disconnects with USB otg with latest (196 I think). Using Titanium to backup my user apps to external 16gb usb key via USB otg. Titanium has quit twice during the same backup saying not enough space. I check and in settings->storage I see 0gb total storage.for USB. Unmounting and remounting fixes and I continue backup. Anyone else seeing a problem with USB otg and latest EOS4?
[Xoom Android Development] dweezle:
I went from 195 to 197 and am seeing occasional random reboots. Nothing else has changed should I go back to 195?
[Xoom Android Development] JCMX:
Been running 197 here since shortly after it came available on goo. No reboots here.
[Xoom Android Development] tekrhino:
+1
[Xoom Android Development] bigdave240:
197 here too. So far no reboots or lockups while sleeping. Only one or two browser fc's
[Xoom Android Development] dweezle:
For whatever reason, the reboots have stopped. Have not had one in days. Sometimes I will get a lock up after switching apps while on the cradle, or just coming off it. Needs a reboot and all is good.
[Xoom Android Development] Neolo:
For some reason I can't launch Play Store anymore after updating to 203 nightly build. I tried to reinstall gapps and Play Store apk separately but no luck.
[Xoom Android Development] rlmesq:
The latest build for Stingray (Xoom LTE) is 197.

Maybe you should be posting in the thread for Wingray (Wi-Fi only Xoom)?
[Xoom Android Development] Neolo:
I'm sorry, wrong topic. But anyway, it seems to be google play servers issue, I can see blank categories of apps even from pc.
[Xoom Android Development] tselling:
Still having troubles with Titanium Backup and OTG USB flash 16gb flash drive with EOS 4 v197. It mainly just stops working with error message that not enough space but there is enough space... seems the USB flash drive gets disconnected... possibly when screen blanks. Going back to EOS3 for now since never had that problem. Also Nova 3 graphics when playing multiplayer were messed up (just noticed today when my son asked me to play a multiplayer game over local wifi with him... I don't normally play Nova3 myself. EOS3 is also fine with Nova3.
[Xoom Android Development] shpitz461:
NTFS vs FAT32 maybe? Files over 2GB in size?
[Xoom Android Development] tselling:
Fat32. The files are Titanium Backup files so all are under 2gb... largest is 827MB.
[Xoom Android Development] mekeleee:
yep....dinner..movie...dammit!:)... runnin...w/bt...iz,worked197..brd...if no one appreciates..ya....i m in oak sun-sat...l(week of 4th) or 7-21_27... La.... by u a beer/coffee(my girl dont let me drink:)!...if u bored...cheers!
[Xoom Android Development] bigdave240:
Running 197. Tried to copy some pics from my camera to my xoom using the usb host cable (otg) but it wont let me mount the camera. The camera senses the usb connection but it never appears in the storage list. Tried the same cable with a usb drive and it works fine and it used to work way back when(not exactly sure what was the last time or version this worked on) so i was wondering if anyone else uses a usb host cable for this?
[Xoom Android Development] Asphyx:
My first guess would be something changed in the USB power output since most of my OTG problems have been from that...

Plug the thing into a Powerd Hub yet? That usually solved any OTG problems...

I'm not on 197 so I can't confirm if there is an issue or not.

Besides wouldn't it be better to just put a memory card reader into the Xoom and pull the card out of the camera?
[Xoom Android Development] bigdave240:
nope it would be another thing to carry around. It was always sort of a last resort when i needed to send a pic to someone and the camera uses a memorystick so its not common to have an adapter etc. I dont use it that way a lot so its not a huge deal but now i need to find a small card reader that fits in my very minimal case. Not sure i have a powered hub to try but i'll look amd see just for the info of it. Thanks for answering back
[Xoom Android Development] Asphyx:
Wasn't meant so much as a solution but an attempt to troubleshoot.

If OTG works at all then the problem is likely not enough power which might be tweakable by the devs if they know thats the issues.
[Xoom Android Development] bigdave240:
i see. I will give it a shot and let you know. Thanks
[Xoom Android Development] DannyShane:
I know this probably isn't going to be a big help to you, but I still figure I should chime in.

I have the OEM Motorola OTG/Camera Connection Kit cable (picture included in post) that was discontinued back in 2011, and have just recently decided to start using it. I honestly have had absolutely no issues with mine. However I'm not using mine to connect a camera either. I'm usually connecting my AT&T Samsung Galaxy S3 to the OTG/C.C.K. cable via the USB cable that came with my phone. Not only does my MZ600 3G Verizon Xoom recognize the phone and allow for transferring of pictures and videos, but I can also transfer ANY files that are on the phone. PLUS I'M ABLE TO CHARGE MY PHONE AS WELL AT THE SAME TIME!!! And if it starts draining the battery on my Xoom too fast, I just plug in the wall charger into my Xoom while the phone is still plugged in via the OTG/C.C.K. cable and both of my devices get charged, off one wall outlet! I love this little cable! I should've been using it when I first purchased it back in 2011, but I'm really glad I was just able to hang on to it for so long.

I should also mention that my Xoom is currently running CM10.1 Jelly Bean 4.2.2, but I switch back and forth between that to Team EOS 3 and EOS 4. Not sure if that makes a difference on whether the cable works or not? Just thought I'd mention it.
[Xoom Android Development] bigdave240:
thanks for your input. everything seems to work on mine as well except the camera. i have to set my phone to mass storage and then it also works as you describe so i don't think i have a bad cable. I am looking for a powered hub to see if it works with that. my non powered hub doesn't work for sure just like the camera.
[Xoom Android Development] DannyShane:
No problem. It never hurts to share a personal experience, just wish it was a little more helpful, for you.
[Xoom Android Development] bigrushdog:
http://xdaforums.com/showpost.php?p=43270928&postcount=2502
[Xoom Android Development] bigdave240:
tried 199 but got stuck on boot screen. had to restore back to 197.
[Xoom Android Development] rlmesq:
Thanks for the warning. 199 apparently dropped on Goo while I was going through the same problem with 198. Re flashed 197 and all's good.
[Xoom Android Development] dweezle:
When I read about folks stuck at the boot screen, I still think it

might

not happen to me. This time I think I'll hold off on updating.:rolleyes:

Gotta grow up sometime.:D
[Xoom Android Development] bacon612:
Happened to me too. Restoring a nandroid now...
[Xoom Android Development] Asphyx:
As long as you make a nandroid there is no reason not to try a newly released Rom, Especially one as Mature as TEOS...

I usually wait a day unless I know the ROM has something I really want in it (such as a New kernel!) and if not I usually read the reports about other's experience before I take the leap.

As long as you make a Nadroid there is nothing to fear from trying something. I just have gotten old to the point that having it first isn't as important to me if the Tablet is doing everything I want already. Then I'll take my time to investigate what new goodies have been added.
[Xoom Android Development] REHolt218:
Having same problem with 199. Stuck on EOS Dragon logo now

Guess I'll go back to 197.
[Xoom Android Development] bigdave240:
I agree. only takes a few minutes to restore from a good nandroid. I was interested to see what a different kernel would be like too. i know there are kernels out there but i have resisted loading anything other than what was offered from eos so far. been a pretty solid path so far so probably won't change that thinking.
[Xoom Android Development] Asphyx:
Did you guys give it an extra long amount of time? Like more than 10-15 Minutes?

If I'm not mistaken New Kernels could take much longer than usual to boot up the first time.

[Edit] Also try clearing Cache just to be sure as it may not work as a normal upgrade will.

I will try it later tonite if I can, Unfortunately until we can get a test unit for BRD we are the only ones who can troubleshoot any issues on our unit.
[Xoom Android Development] bigdave240:
nope. i can try that. give me 10 or 15 and i will report back
[Xoom Android Development] REHolt218:
I went out and picked cucumbers in the garden. When I came back it was still stuck.
[Xoom Android Development] bigdave240:
well its been more than 30 minutes and still stuck. going bak
[Xoom Android Development] Asphyx:
Well it was worth a shot....
[Xoom Android Development] runner1717:
198 & 199 both lock at the Motorola screen. Cleared cache and Dalvik Cache and it made no difference. Back to 197.

Mike
[Xoom Android Development] real0325:
I finally decided to insert a SD card, but it will not mount. Anyone else having this problem?
[Xoom Android Development] bigdave240:
Put it in an android phone and format it fat32. Its the only format that will work.
[Xoom Android Development] real0325:
I'll try that, thank you.
[Xoom Android Development] admiral70:
For what it is worth. I two had issues with 198 and 199 not loading. Had to revert back to 197. Only thing I did not do was a complete data wipe. Did anyone try a complete wipe when going to 199?
[Xoom Android Development] Lobout:
Yes i have done a full wipe/factory reset with 199 and it just hangs. now I have to deal with the dreaded registering device issue. can't remember how to get around that.
[Xoom Android Development] tomcrown1:
199 hangs for me also. If you are on zoom do not upgrade at this time as 197 is the last firmware that works with zoom.

Aim thinking of upgrading, but I do not know which unit is the best to upgrade to, or wait for the next Motorola tablet.
[Xoom Android Development] dccrens:
199 hangs here too

Ok. I have been on 197 and twrp and decided to go to 199. Booted to twrp backed up 197 rebooted. Ran TitaniumBU. Booted to twrp, wiped caches and flashed 199 and Gapps. Now I reboot and get nothing but the Moto logo. Had to use power vol down, vol up to get back to twrp and restore 197.

Uuuggg... Spoke too soon. On reboot after restoring 197 I get just the moto logo. This sucks...

Edit-

Well... Had to go all the way back to a restore of 190 to get the xoom to boot. Now I am back on 190 and up and running. Very interesting that none of the ther backups 191-197 would actually restore and boot.
[Xoom Android Development] bigdave240:
I restored 197 a few times after going to 199 to see if it would work and had no problems at all. maybe your 197 bu was corrupted?
[Xoom Android Development] REHolt218:
I simply reinstalled 197 over the top of the failed 199 install and everything was back to normal.
[Xoom Android Development] dccrens:
Yes. Now that I have 190 back, I am going to reDL and reload 197. See if that works.
[Xoom Android Development] stevefxp:
I am stuck on 199 with no backup. How can I get something installed?
[Xoom Android Development] REHolt218:
As I stated 2 posts up, I simply re-installed 197 andnl all was good. Just boot into recovery and install 197 and GAPs.
[Xoom Android Development] dccrens:
If you don't have 197 and gapps on the device you might be able to pull the memory card and put in in a PC and dl 197 and gapps to it. Put it back, reboot to TWRP and reinstall.

---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------

I reinstalled 197 and GAPPS on top of the 190 restore and all is well. So what is the issue with 199?
[Xoom Android Development] twinkyz1979:
would be really nice if team eos is no longer or doing something else if one of the members would please post something letting us know.
[Xoom Android Development] dweezle:
Much of the ongoing support has been done by Bigrushdog. He has worked his butt off to keep giving us support, even after no longer owning a Xoom. I am assuming that these last 2 updates (198 & 199), were similar to what he did for WIngray on the 4th of July.

But, you know what they say about assuming...
[Xoom Android Development] twinkyz1979:
did not mean to imply anything but other forums are saying that TEAM EOS is no more i am just saying it would be nice to hear something from one of them about what is going on
[Xoom Android Development] REHolt218:
Since 198/199 were just release around the fourth I would have to say Team EOS is doing "something". I believe we are just seeing some technical difficulties due to BRD's inability to test. I went back to 197 and assume i will be rewarded by patience with an eventual fix. In the meantime 197 seems to perform pretty well.