yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] REHolt218:
Thanks Team EOS

Since loading Nightly 183 yesterday I have been SoD free for 24 hours. I have not had to reboot once:good:

Thanks for the update and for solving the problem.
[Xoom Android Development] tomcrown1:
My Google now crashes with this update anyone else with the same problem
[Xoom Android Development] rajones19:
Confirmed. I'd be happy to just turn it off anyway, if I could get to the settings LOL. It is GREAT to not be experiencing the SoDs, though .... been great so far.
[Xoom Android Development] shpitz461:
Did you try to clear its cache? still crashes? reinstall it maybe?
[Xoom Android Development] bigdave240:
From runandhide05: Disable hot word detection...same thing we have been saying for months.

Settings》language and inputs》 voice search 》》 uncheck hot word detection

See if that helps
[Xoom Android Development] tomcrown1:
That did the trick
[Xoom Android Development] xyrcncp:
Maybe the OP should be edited to include this. It will reduce the times you guys have to keep saying this page after page after page.
[Xoom Android Development] Mjamocha:
FYI if you use TWRP for xoom:

I've been running Official Twrp 2.4.4.0 (recovery.img) for xoom along with these nightlies for a while now. It is on Goo.

I also have Themed the Official TWRP 2.4.4.0 (recovery.img) into a flashable zip,

and there are (themed ui.zips) for Xoom available for your viewing pleasure.

Links in my sig. Enjoy

Assassins Creed v.1

Assassins's Creed v2
[Xoom Android Development] bigrushdog:
I didn't know someone dropped 2.4.4.0. Good deal. And ya I still gotta update xoom to the new OP. And I'll add the hotword fail thing.
[Xoom Android Development] stevefxp:
Hello all,

I am running build 184 and got two issues:

1) Standard kb seems to stop after each word. I somewhat remember this being an issue a long time ago but looks like its still with us? What is the fix to keep the kb going?

2) NFL Mobile does not work on non-stock build. Being there is a Verizon Login app used in conjunction with this I believe there is a communication layer issue here. Each time I try to login it tells me services are unavailable or that I do not have a mobile connection. Has anyone been able to get NFL Mobile to work?

BRD I dropped you an email on item 2 and would be happy to assist where I can. I really would like to see NFL Mobile work on our Xooms, especially with the draft just around the corner.

Thanks,

Steve
[Xoom Android Development] dweezle:
I've got a problem with my Xoom. I don't think it is related to any of the EOS 4 builds, but I don't know where else to look for advice. I have been on JBEOS4, JELLYBEAN MR1 since build 151. I'm on 184 now. My tablet will frequently just freeze up. At first i thought it was because I set lock screen to "none". I confused correlation with causation, i.e. that wasn't the cause of the freezes. Sometimes the screen stays frozen for as long as an hour and then I will get impatient and Power/volume up, to reboot. Other times, the screen freezes and after a few minutes the Xoom reboots itself. I know seeing a log would help folks figure the problem but I don't know the best way to capture one, I downloaded an app called CatLog that has several 'levels" of logs; Verbose, Debug, Info, Warn, Error and "What a terrible Failure". Which level should save, and link to? What happens to the log function when the system reboots? Is it even appropriate for me to ask for help here? If not, where should I post my question?

Thanks to all the folks who put in the heavy lifting for these builds. You make my day to day Xooming great.
[Xoom Android Development] shpitz461:
You got a Stingray? Did you try any of the other ROMs? What about ElementalX kernel? Which recovery do you have? I had issues with CWM so switched to TWRP 2.3.3.0 and a few issues were gone.

Did you overclock?

Did you try with the SIM removed?
[Xoom Android Development] dweezle:
Yes, Stingray

No, haven't tried any other ROMs

I have TWRP 2.4.1.0 ( I will go back to 2.3.3.0)

I am not on ElmentalX kernal (should I be?)

I am not overclocked

Hotword detection is unchecked

Nope, I haven't tried it with SIM removed.

There is nothing in particular that will make the system lock up, it appears to happen randomly.:confused:
[Xoom Android Development] shpitz461:
Yeah, try the older TWRP, try elementalX, and report back.
[Xoom Android Development] scoobaspeaz:
It has nothing to do with TWRP or Clockworkmod...its in the kernel. CM 10.1 has the same issue. CM 10 stable has it as well. I would try ElementalX's kernel or wait for the problem to be fixed.

There is an experimental CM 10.1 build im testing right now that seems to have some positive results. Its only been a day though so I am not ready to report back it was solved. If you want you can take a look at /proc/last_kmsg after you reboot from your freeze to see what the last thing was that did not respond. For me I seen an mmc2 controller issue before it crashed.

It is sad that Team EOS has not responded to the many people posting about this issue in this forum though. They are probably working on the issue too though. Its worth noting that the CyanogenMod team has responded about it on the developers G+ page and not on the forum thread here either.
[Xoom Android Development] dweezle:
Why would only some people report having this problem? If it is something in the kernel itself, why would some have it and others not? It's all voodoo to me.:confused:
[Xoom Android Development] bigrushdog:
Why is it sad that I don't respond to every issue a user has? You use the word "response" like I'm on trial or something. If your Xoom is wonky on my build and the CM build, something is up with your xoom. You should double check for user error before asking people for "responses"
[Xoom Android Development] twinkyz1979:
Well not all hardware in every device is exactly the same some do have issues that others don't. So really unless it is something reported by a bunch of people or something easily seen in debugging logs maybe it just your hardware.
[Xoom Android Development] Mjamocha:
Dude, how dare you be so disrespectful. These Devs, are hard working people offering

FREE

software. Yes for

FREE

, across a variety of platforms, on

their own time

. They are not obligated to do anything, and they are not on call. If you are unsatisfied with the product, unroot and return to STOCK. Be grateful, have patience, and show some tact.
[Xoom Android Development] Asphyx:
I'll search in the meantime but is most everyone using this new Kernel? First time I'm hearing about it but I admit I haven't really checked for updates other than this rom.

I would have to say BRD is one of the BEST developers as far as responding to user questions and issues I have ever seen!

That statement was very unfortunate if you ask me.

You can't expect a Dev to respond to every single inquiry that isn't reported by more than one person and when a problem is discovered we usually get a fix posted within a day of finding the issue...

This is one of the best supported ROMs I have ever used and if you think this is not go try and get a fix for CM who has hundreds of developers working on issues and yet it can take a month to get as answer or a fix!

Bottomline is this Xoom is on the bare minimum cusp of what can run the latest version of JB. If your not getting good performance then go back to the older version of JB which was fine and snappy even without overclocking or go back to ICS which the unit is more than capable of handling.

But to blame performance issues on a rom that our unit is barely able to keep up with is just not right.

This version of JB is meant for the second generation of Android Tablets and like it or not we XOOM users are pretty much using a Prototype unit at best! It's a great unit I love it but the truth is this is the very first Android tablet ever made and is long past it's lifecycle as far as performance under newer Android versions are concerned.

You either live with that fact or upgrade your unit to something that is made to run the newest JB.

And Thank BigRushDog for even putting the effort into supporting a rom for a unit he no longer owns!
[Xoom Android Development] xyrcncp:
:good:

I find it amusing how worked up some people get about free stuff that THEY chose to use and knew ahead of time that is not guaranteed in any way to work 100%. It all goes back to how the interwebs has made people have some ridiculous sense of entitlement when it comes to stuff like this.
[Xoom Android Development] bigrushdog:
It's all good. No worries. Back to business. I'm gonna try updating row and s2w from flar2.if we still have issues I'm gonna revert all s2w. If that don't do it, I'll start a new kernel with flar2's kernel as a base. And he'll get a big fat "Powered By ElementalX" banner in the OP. I just need to get this thing stable because I have other things to do.
[Xoom Android Development] SamuriHL:
If you do work on the kernel, could you add a few more governors? Thank you! :)
[Xoom Android Development] rob62551:
For what it's worth, on build 184 NO problems. I have experienced the best performance of any JB 4.2 rom with this build. The ROW I/O has this tablet working the best since these great developers squeezed out miraculous manipulations on the Xoom.

S2W works as intended (I personally prefer not enabling it).

So my comment is submitted as a request to BRD and Team EOS to continue this great work. If you revert some aspects of your kernel BRD, could you please notify us of this. I will probably stay on this build (184) as I am really satisfied with its performance. Thanks good Sir!
[Xoom Android Development] Liwais:
Many people have been posting this BSOD +1.Why it is impossible to resolve this issue if on

[ROM] of BAKED stingray/wingray bb-8 (3-15-2013) Isn't present any BSOD, Simply I like EOS.no this problem on EOS is. Excuse for my English
[Xoom Android Development] REHolt218:
Not sure I understand what your comment means, but I think you are asking "what does BSOD mean" . The issue is "Black Screen of Death" or what I have previously seen as "Sleep of Death". This is where the device (Xoom in this case) goes to sleep and then refuses to wake up. In my case the screen would turn off and would not return to "on" until I re-boot my Xoom.

In my case the issue was resolved with the latest EOS 4 nightly release 184. I am not sure it has been corrected for everyone.

Hope this helps.
[Xoom Android Development] shpitz461:
Same here, tablet is finally snappy for the 1st time with 4.2, s2w works great most of the time, sometimes you would swipe and it would take a few seconds to either wake up or unfreeze itself, but that's a non-issue and only happens after many hours of sleep. I'm running ElementalX 1.0++ (built prior to v1.1 he currently has). Awesome job on EOS and Flar2's side, kudos!
[Xoom Android Development] Asphyx:
I don't think it has anything to do with the ROM...It's the fact that JB 4.2 is written for a chipset we do not have is not really suited to running as much as the newer units do...It's a performance thing on our Unit not the ROM.

I have noticed most of the time when it happens is because it is doing updates on Play Store or running some other task that is taking up most of the performance cycles and if you just hit the button and wait it eventually does come back.

It's out impatience that makes it seem like it's dead.

This has been an issue ever since 4.2 came out. and while it is inconvenient I think we have to understand the unit is just not able to keep up with it.
[Xoom Android Development] dweezle:
BRD said

Things seem to be functioning without problems now. In my original post I was asking for troubleshooting help, to find my error/errors. I didn't expect the kerfuffle that turned into a perceived criticism of the build. Like most folks here I feel fortunate to be one of the beneficiaries of the work done by the folks who continue to make ongoing tweaks and fixes to this great ROM.

I wish I could tell you which of the things actually solved the problem, but I shotgunned it and did a number things. My best guess is one of the many apps I had installed was "misbehaving". I uninstalled a couple of them and unfroze any that were frozen in Titanium. I have been on the tablet all day and have not had a single freeze. I did change my version of TWRP to a themed version of 2.4.3.0, but, as others have said here, I doubt that had much to do with my system freezes. I have become more aware of the load that I am putting on the system and try to keep it limited. Sorry to not offer more of a hint that might help anyone else having a similar problem, but, by nature, I'm not even close to being methodical. :laugh:

That's my update.
[Xoom Android Development] scoobaspeaz:
@Bigrushdog The CyanogenMod team found that the issue was with MMC deferred resume being enabled. Nvidia reference for Tegra 2 devices has this disabled. They have created a change that was merged to disable this feature again. I'm sharing this info with you so you can review and include it in your ROM if its applicable. Ever since Friday i have been using the test build with this fix included and I no longer get the "Black Screen of Death" or as its known to others "WTF do i have to press power and vol up to restart it so the screen will come on" issue :)

http://review.cyanogenmod.org/#/c/35315/
[Xoom Android Development] bigrushdog:
Very interesting. Let's see what my buddy tdr has going on here. What the heck! Let's merge that and fire off some builds.

EDIT: merged, fresh builds cooking in the Jenkins oven ;D
[Xoom Android Development] mekeleee:
wow..never had1 prob on brd eos.. builds ....my2cents...i use my tab in corp/ind environments ..daily...
[Xoom Android Development] bigdave240:
Screamin fast so far. Turned on the zram and enabled the s2w and so far no lockups. I was fine just not turning on s2w since that was definitely causing my lockups and everything else was more than perfect so now its way over the top! I love the cooperation between the dev groups. Its like a brand new toy........ Again. Many thanks

edit: let me rephrase that. Not sure it was CAUSING my lockups but it only happened when i had s2w enabled. i really like that feature but if it is just too much for my xoom i can live without it.
[Xoom Android Development] Mjamocha:
NVM...
[Xoom Android Development] SamuriHL:
Latest build is running super smooth for me. Job well done!

Sent from my Team EOS OCd Xoom
[Xoom Android Development] rosenhauer:
Wish I had the same experience. 184 and 185 both are causing it to go dead instead of to sleep. I've had to Vol+Power to revive it several times. 183 seems to be fine. I use Swipe2Wake so maybe that's the issue.

Also not sure if related but the "Enable Swipe2Wake" setting shows off (unchecked) yet it works. The "Start on boot" is selected and it's loaded so not sure if it's a display issue or that it's not fully loading?
[Xoom Android Development] REHolt218:
dumb question

Under 4.2.2 how do I take a screen shot!
[Xoom Android Development] Droidem:
I think it is power+home.
[Xoom Android Development] shpitz461:
power+vol_dn doesn't work? there should also be an option to add that to the power menu.
[Xoom Android Development] REHolt218:
Thanks, Power and Volume down works.
[Xoom Android Development] bigdave240:
I add it to the Quick Launch target so its handy.

---------- Post added at 09:43 PM ---------- Previous post was at 08:52 PM ----------

If it is checked for start on boot then it will be on after boot. The other check box is more like a toggle to turn it on and off on a per use basis. I had to leave the on boot unchecked and no longer use the s2w as it caused a lot of not waking up problems for me. Others seem to not have problems so not sure but it might be an app i have that they don't. You can turn off s2w after boot even if its checked by checking and unchecking the s2w checkbox it will stay off until you reboot again
[Xoom Android Development] Asphyx:
I have also noticed that it happens much less frequently and starts up much quicker depending on how many Widgets you use on the lockscreen...

I switched to DockClock and replaces one or two others I had running and I have reduced the frequency of those Wake delays as a result...
[Xoom Android Development] Mjamocha:
(TWRP) Dude where's the wallpaper? :beer:
[Xoom Android Development] charolastra915:
wow

First time installing ROM on tablet, all I have to say is WOW, now how do I get Google app store?
[Xoom Android Development] SamuriHL:
Did you install gapps? If not you need to.

Sent from my Team EOS OCd Xoom
[Xoom Android Development] charolastra915:
Oh OK and is that install the same as the other ROM, from clockwork. should I put zip in external or internal SD?
[Xoom Android Development] Droidem:
Wherever. Doesn't matter.
[Xoom Android Development] charolastra915:
Ok, thank you

Tapatalk!!
[Xoom Android Development] Asphyx:
No it is not the same...

Get the Gapps linked in the OP.

EOS-XOOM-ONLY is in the title...I forget the date off the top of my head.

As for internel external it doesn't matter but I like to have all my flashable zips on the SD card

If you have a good recovery installed it really shouldn't matter as it will let you select where to get the zip from to install it.
[Xoom Android Development] rob62551:
Just to add: date is 20130105.
[Xoom Android Development] charolastra915:
Thanks for the help, is it normal for the keyboard to go away in the middle of typing?

Tapatalk!!
[Xoom Android Development] bigdave240:
Known bug see here: http://xdaforums.com/showpost.php?p=37263016&postcount=1275
[Xoom Android Development] charolastra915:
Ahhh, very nice thanks, sorry im late to this party
[Xoom Android Development] Asphyx:
So far have to say 185 is the most Stable version of JB 4.2 yet.

Whatever you did there BRD on that last tweak sure did increase the reliability and Quicks I was having.

Great Job as always!

I notice a 186 has been released...Will try that one later in the week.

Unless you throw another one up before then.
[Xoom Android Development] charolastra915:
Do i have this right? Download update from goo manager and then flash with clockwork or will goomanager do it for me. I tried the first way but clockwork doest not read any zips in internal memory... Thanks for any advice
[Xoom Android Development] runandhide05:
When dealing with updating or flashing with the aid of an app.

Goo works with twrp

Rom manager works with clockworkmod recovery

So goo mamager will not flash zips if you have clockwork

And rom manager will not work if you have twrp.
[Xoom Android Development] charolastra915:
thank you once again, worked flawlessly :)
[Xoom Android Development] shpitz461:
Was s2w removed from EOS settings in 186?
[Xoom Android Development] bigdave240:
release notes says it was reverted. so i guess it was. no longer on mine anyway. but it has been stable as a rock since! but i hope they can figure out what is going on with it and bring it back.
[Xoom Android Development] DannyShane:
Can't Get EOS 4 to Flash correctly

Sorry to bother you but I do have a question about this ROM:

1. I installed the TWRP 2.4 Touch for my Stingray Xoom.

2. I then downloaded both the EOS 4 ROM, and the corresponding GAPPS package.

3. I had Stock ICS 4.0.4 Rooted on my Xoom, and decided I wanted to go ahead and get 4.2.

4. I Rebooted into TWRP Touch Recovery, and Flashed EOS 4. During flash, TWRP said "Updating partition details..." "Installing '/sdcard/EOS4-stingray-20130414-186.zip" "Checking for MD5 file..." "Skipping MD5 Check: no MD5 file found." "Built at: 2013-04-04 05:17 (PST)" "Updating Partition Details..."

5. It then says "Successful"

6. I then wiped Dalvik Cache, Cache and then Rebooted System.

7. All that happened after that was the Motorola Dual Core Logo screen comes up, then goes into the Team EOS Logo (Blue,Green,Yellow, Red Circle-ish logo) and it stays stuck on that.

8. I waited and waited, and finally did the button combo to reset Xoom (Volume Up button + Power Button), went back into TWRP Recovery, reflashed both .zip files (EOS 4 and GAPPS Package) this time without wiping Dalvik and Cache, and yet the same thing happens. Stuck on Team EOS Logo. Not sure what I'm doing wrong here? Please Help?

http://www.flickr.com/photos/94923973@N02/8653196321/
[Xoom Android Development] runner1717:
Wipe data.

Mike
[Xoom Android Development] DannyShane:
I tried wiping data as well (looks like I forgot to include that in my OP), however it still didn't work. So I just decided to go ahead and install EOS 3, the Stable Release version instead of EOS 4. Worked just fine. Maybe I'll try a little later today to see if I can get EOS 4 working for me. Thanks for the recommendation Runner1717
[Xoom Android Development] Mjamocha:
If coming from ICS 4.0 going to JB 4.2 , it might be necessary to format the system first. Please correct me if I am mistaken.
[Xoom Android Development] bigdave240:
I think I remember something about you have to do a factory reset before going to 4.2.2? It had to be installed from a clean system
[Xoom Android Development] runandhide05:
Absolutely!

If you are coming from anything other than a previous EOS4.0 rom then you MUST preform a factory reset
[Xoom Android Development] monyozt:
help.. flashing lastest build on MZ600. my signal is gone.. anyone can help me?

Or maybe there a patch for mz600 to bring my 3g signal back as I want using latest rom from teameos
[Xoom Android Development] Asphyx:
This ROM is for the 602 LTE unit not the 600....

Probably the cause of your problem but I can't say for sure...

I'm betting you need to flash the UMTS-Everest ROM to get your 3G back.
[Xoom Android Development] monyozt:
AFAIK that LTE is upgraded from MZ600 (cdma) before.. and everest is GSM device,, but my device is cdma too..
[Xoom Android Development] Asphyx:
Well it's a different radio.....

Not sure if the drivers are the same or not that's one for BRD or someone else more knowledgeable in the differences between the upgraded and non-upgraded versions.
[Xoom Android Development] monyozt:
little bit confuse... mine is MZ600 as i live at Indonesia, i use this device with CDMA network too.. but at US, most MZ 600 already upgraded to 4G LTE one, MZ602 CMIIW. and now, most developers only make for MZ602.. i hope there will be patch for MZ600 ( 3G) Version so i can install android 4.2.2 on my XOOM MZ600. thanks
[Xoom Android Development] shpitz461:
Is the reason for the new GAPPS package only to make encryption doable? Once I installed it I had ~4kb free space on system. I went back to the original EOS GAPPS from January.
[Xoom Android Development] bigrushdog:
In a nutshell, yes. But you "should" have more room than that anyways.
[Xoom Android Development] runandhide05:
Ya about 5meg if nothing else was put in the system after flashing rom and gapps only
[Xoom Android Development] rob62551:
Which Gapps To Use?

If I understand above posts about gapps, is it best for me to remain with the 20130105 Xoom Only gapps if I do not need encryption capability? Running build 187 with 20130105 gapps and all is very well with this setup. Just curious if you might see a need/benefit to flash new gapps?

Thanks all!
[Xoom Android Development] lord-dogbert:
All is well for me on the latest nightly. There is some lag bring going up the keyboard and chrome responds slower than Eos 3 stable.

Love it otherwise.
[Xoom Android Development] TheGman125:
Hey has anyone tried to pull Xoom in to the TV?
[Xoom Android Development] Mjamocha:
I will give it a go.
[Xoom Android Development] Mjamocha:
* Regarding HDMI out to the TV,

HDMI works great for me on this ROM as well. (I'm using it on my 3D Tv ) :p AWESOME!!! No reboot or loss of screen view. BTW I'm running undervolt at 912 MHz Governor (ondemand)

*New TWRP Themes for 2.5.0.0 based from Runandhide05 update. I think you will really enjoy the SteamPunk Theme! Link in my signature.
[Xoom Android Development] tselling:
Anyone able to run strikefleet omega? I had to revert to eos 3 stable to run it.
[Xoom Android Development] Mjamocha:
Hello, ello, ello ello ..... Any one home ome ome ome lol.
[Xoom Android Development] shpitz461:
LMAO
[Xoom Android Development] rob62551:
I'm here..ere...re...e!