yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] runandhide05:
I simply can not get that to reproduce on mine. I've done it with multi user second user set up pin, logged into primary set pin. Let tablet enter deep sleep and wake works fine. Rebooted several times unlocks every time, also powered off last night. Turned on just now and unlocks like a champ.

Do me a favor and try to reproduce it on your end but do not setup your exchange and see what happens.

Also i m still waiting for a log if we really want me to look at it.
[Xoom Android Development] petrossa:
How my fingers itch to install it, but phablet ui is real deal breaker. Whoever came up with that at Google needs to be brainscanned for a Microsoft implant. What a astonishingly stupid idea. :(
[Xoom Android Development] drewski_1:
Both of those (157/158) were with no Exchange set up. Just EOS ROM + Gapps and then set up PIN lock. No other User Apps installed.

I'm a Log noob. How would I capture log information if the problem only happens after Reboot, I can't get into the OS, and then need to reflash the ROM?

btw, did the error in the post from alex94kumar help at all? though his issue was with Pattern unlock vs. PIN

---------- Post added at 09:35 AM ---------- Previous post was at 09:32 AM ----------

agree. waste of space to have the bars on top & bottom of screen. maybe on a 7" tab like N7.
[Xoom Android Development] runandhide05:
Sorry I should have stated how/what to do.

Setup your pin/pattern

Once reboot Xoom, connect your Xoom to your computer.

Open terminal if on linux or command prompt if windows.

From the directory where your adb is ( located where ever your android SDK directory is under platform tools)

So for me its at c:/android-sdk/platform-tools/

Enter this

adb logcat > lockscreenfail.txt

Now logcat is running and will log the events

On your tablet now. Attempt to unlock your device. And as long as it does the error u have been having log cat will capture the issue ( well it should )

Then on command prompt stop the logcat by pressing both cntl and c at the same time. Now email me that log file named lockscreenfail.txt to my user name at gmail dot com
[Xoom Android Development] alex94kumar:
View attachment lockscreenwhatthefuck.txt

there you go sir, hope this helps
[Xoom Android Development] drewski_1:
just sent a few logs. got my fingers crossed!! :good:
[Xoom Android Development] liftman-:
i like the phablet ui, which suprised me.
[Xoom Android Development] NWinfuse:
I'm with ya on that! I think it's nice having pulldowns up top but the soft keys being moved to center bottom has taken me a little bit of getting used to.
[Xoom Android Development] petrossa:
Well, evidently a switch is a must :)
[Xoom Android Development] Alxoom33:
BRD thank you for your continued support of our Xooms. Its not dead yet! And it should have been a long time ago without your breathing life back into them. Thank you!:cool::beer:
[Xoom Android Development] sicilykill:
is anyone else experiencing slow wifi speeds on build 203?

EDIT: Never mind. Reboot fixed it.
[Xoom Android Development] Blondblueyed_girl:
Really hot over here in the UK, making me sleepy dreaming of little green androids jumping over a fence, while we patiently wait for BRDs next bit of magic.
[Xoom Android Development] uzi2:
Your patient waiting is over...

http://xdaforums.com/showthread.php?t=2372197
[Xoom Android Development] quasar12:
Just moved to EOS 4.0 #203 and wow, it is like my xoom got yet another new lease on life!! This thing has more lives than a cat!

I've been on EOS 3.0 #155 since forever. I've been itching for a new tablet, and but then thought I'd check on the status of the JB 4.2+ development.

I use mine daily to the point my laptop is rarely turned on anymore, unless I need to do some heavy typing (I write software requirements for a living). I even use the tablet to work remotely via the Citrix app.

The Good

I've overclocked it to 1.6GHz and it is very stable just as it was on EOS 3.

Overall UI Responsiveness has improved, except for the new 'recent' implementation which puts the currently-open app on 'pause' as opposed to showing an overlay.

The new notification area is nice, even if it requires some adaptation.

Hate having the soft-keys in the middle. This has been widely debated, but I thought I could live with it until i tried it! Thankfully, EOS allows this to be changed: Settings > EOS Control Center > Navigation > UI Mode = Tablet Bar for the pre-4.2 look.

Not a feature of the ROM itself, but most of my apps, Kindle books, and contacts were synced back after re-installation, so I didn't have to restore from the backup. Awesome when technology just works!

[**] Only apps set to 'auto-update' on Google Play will be automatically re-installed. Had to re-install the others manually, but it helped me revise what I actually need on the tablet.

[**]Because of the above, I didn't need to use NANDROID manager. FYI, it allows you to selectively restore data from your nandroid backup made through TWRP or some other recovery, therefore making Titanium Backup redundant.

The Bad

It seems battery life is a tiny bit less good than before, but I still get at least 2 days of charge with heavy use (i.e. at least 5 hours of web browsing per day).

I love google's swiping keyboard, although I've found that the downloaded one from the market seems more responsive and better at predicting words for some reason.

The Ugly

Live wallpapers will do Very Bad Things (TM) to performance in general, especially multi-tasking. Everything slows to a crawl after a while.

Installation Procedure

Backup EOS 3 using recovery

Install latest version of TWRP

Wiped everything except my data

Install EOS 4.0 #203 nightly and G-APPS package

Done!
[Xoom Android Development] jphillips.hd88:
Actually it will slow down again...mine slowed after the bad install of 205...had to do a wipe and clean install of 203 to get things right again
[Xoom Android Development] sicilykill:
Thanx for the heads up. :good:
[Xoom Android Development] Blondblueyed_girl:
Thanks for the heads up, seams like EOS 4 has come to a final end, long live EOS 4. Thankfully to be reborn in another form.:good:
[Xoom Android Development] bigrushdog:
Ya. Born again with a vengeance! Get your final comments in. Eos threads will be closed soon as the project is no longer supported. Look for the temp thread in General. Soon full dev threads will be up again.
[Xoom Android Development] scottgti:
IBTL
[Xoom Android Development] ChadH42:
Thanks Teameos for a great ROM.

Long live EOS!!!
[Xoom Android Development] waz675:
Thanks teamEOS for the bloody awesome roms and extending the life of my XOOM so myself and 2 kids could use jellybean on a 10inch screen in a way it should be. The way Android meant it to be!
[Xoom Android Development] istrait:
Thanks to the team for all of the hard work... I appreciate all of it...
[Xoom Android Development] tonemand:
Thanks Team EOS!

<bows deeply>
[Xoom Android Development] matt4321:
Cheers for everything EOS
[Xoom Android Development] 7ravler:
This can't end now! I'm having too much fun seeing what you had in store for my Xoom next. I guess I'll have to follow you to CodeFireX. Let the fun begin. :cool:
[Xoom Android Development] bigrushdog:
Cheers! But don't shed any tears. Eos lives on in CFX. Remember, we now have two code bases of features now. And I'm pushing code real fast. We just got a few minor kinks to work out and we can open new threads. Synergy is merging 4.3 as I type. So the adventure continues!
[Xoom Android Development] 7ravler:
Do we still need to deal with goo?
[Xoom Android Development] ATZ-007:
This is a great news!

As we know Eos is fantastic and I know Synergy from Desire HD, who is also fantastic developer.

Looking forward to the new thread and ROM.
[Xoom Android Development] Dyelon:
Just wanna say that without team Eos i would've had to spend hundreds of dollars on a new tablet. Instead, I've had so much fun AND function with my Xoom throughout my entire grad school. When I graduate next year, I'll finally buy a new one! Hahah
[Xoom Android Development] yosterwp:
Well, I was thinking about a second-gen Nexus 7, but seeing that development is still alive for the xoom, I'm going to keep my xoom for a bit instead!
[Xoom Android Development] waz675:
Don't forget to donate some of that saved dollars to the team that helped you save it.
[Xoom Android Development] Madmick:
I did several searches including "flash player", "flash video" and "Adobe flash" and this was the most relevant post (a search of just "flash" yields 451 results due to that word's use as a verb in relation to installing/updating ROMs). The link is dead, and my assumption would be that it's just one of the final apk versions Adobe released before ending support for Flash on mobile devices, except that the last Flash player for 4.0.xx devices, 11.1.115.69, is only 4.5MB. Here's the link from the official Adobe-hosted archive:

http://download.macromedia.com/pub/...roid/11.1.115.69/install_flash_player_ics.apk

Meanwhile, the zip file Run linked above is 16MB. Zip files are almost always compressed files, so I'm curious if this was a more specific adaptation of the Flash software for the EOS ROM on Android 4.2.2?

I've sideloaded the version I linked above (11.1.115.69), and tested it using the latest Dolphin + Jetpack versions, and it works, but it's not great. I can't skip forward (you get an endless loading icon), and if I try to maximize the video window, I can hear sound, but the screen is pitch black. I have to pinch zoom in order to resize the frame. It's much smoother than the sideload I tried on an unrooted Asus Transformer TF101 tablet that has an identical chipset to the Xoom- I'll give it that. The Transformer will take minutes to load a video, sometimes, and it almost never runs the video viably; there's perpetual stop-go skipping.

I don't expect great performance from dead software, but it would be nice if I could get it to work the way that it was intended to work before they abandoned it, especially since my little brother's Galaxy S3 with native flash support in its browser runs Adobe video all across the web flawlessly. Does anyone know a better way than the plain sideload I used above? I'd appreciate it. Thanks.
[Xoom Android Development] uzi2:
Your problem is not with flash, but dolphin as they dropped support for flash in Jellybean several versions ago. The stock browser and Firefox both implement it quite well.

If you wish to continue to use Dolphin as your default browser, then you can use flashify from Play to switch browsers when you want to view flash content.

Hopefully, BBC will drop it's reliance on flash soon.

Swyped from my xoom
[Xoom Android Development] wooly1:
Dolphin has reintroduced flash to it's browser from v10 onwards.

No need to use workarounds like Flashify anymore.
[Xoom Android Development] sdcoiner76:
Tried to install EOS 4 several times but it always stayed on the Motorola screen. Anyone else have this problem? I can install other ROMs just seems like this one is a problem. Thanks.
[Xoom Android Development] scottgti:
Use 203.
[Xoom Android Development] sdcoiner76:
Thanks, looks like that was the problem.
[Xoom Android Development] Madmick:
It appears wooly is correct about Dolphin's native integration because regardless of whether Flash is installed or not the setting option is there for displaying flash in the browser (Always/On Demand/Off), and BBC or CNN video is working on Dolphin even without a sideload.

However, my go-to website for testing Flash is Comedy Central, and neither Dolphin/Firefox/Stock is working regardless of whether I have that latest Adobe apk sideloaded or not. I like watching full episodes of The Daily Show and The Colbert Report and I haven't gotten them to work regardless of what I do. I tried it with and without sideload on all three of those browsers, and none works. I also can't figure out a way to try to launch the video from its frame with an external player.

Any ideas?
[Xoom Android Development] boabsmith:
Try Boat Browser or Next Browser.
[Xoom Android Development] Madmick:
No dice. This doesn't appear to be a browser issue. I'm not even sure if it's a Flash issue. I'd presume that it was a website issue, but as I said, I've tested everything on my little brother's stock, unrooted Galaxy S3, and it just tears the web up. No wonder Samsung is destroying the market.

I had some time, so I undertook a battery of tests for Dolphin rifling around some of the biggest sites on the internet with intensive video. Indeed, CNN works, but I can't maximize the window; it automatically stops. Hulu works in Dolphin, but only plays sound on stock. ESPN launches a popup frame for their video. Happy about that. I used to have the same sound-only problem with their highlight vids regardless of the browser. NBC works, but it won't maximize on stock (it will on Dolphin). I have to pinch resize. ABC works. SpikeTV works. Amazon Instant Video works. Netflix works. I tested some of the Webby Award nominees for animated and motion graphics and they all played.

Some adult sites had issues, others didn't, and some automatically launched the option to play the video in an external app. I don't understand why the last can't be standard for everything...MX Player with codec support & decoding will play literally any type of movie file I've ever known myself to view.

Anyways, if anyone can figure out how to watch CC videos on the Xoom without using a stupid Media Server Center (i.e. Playon, Plex, XBMC, My Media Center, etc.), then you'd be my hero.
[Xoom Android Development] boabsmith:
I just viewed a couple of streams from Comedy Central to test it for you. I used a proxy as I'm in UK but it streamed perfectly for me.

I just used the stock browser with this EOS ROM ( build 203 ) and with latest Flash player installed.
[Xoom Android Development] jimboogly:
Will miss the TeamEOS4 thread, its been interesting to say the least! I can honestly say that you Dev's were nothing short of miracle workers!
[Xoom Android Development] Madmick:
Well, that's just depressing. I've heard about bizarre behavior from device to device, and it's the most frustrating thing because it's impossible for me to understand what's going wrong. I have no adblockers running. I haven't modded anything. I'm literally still running EOS virtually out of the box. I've tested it on three different WiFi networks (two different providers), and it won't stream on any of them. I'll test it on my little brother's Charter, later, but man this stuff irritates me.
[Xoom Android Development] boabsmith:
What build of the ROM are you running? Possibly that could be an issue if different from mine
[Xoom Android Development] illyfilly:
Can someone clue me in too what is going on?
[Xoom Android Development] drewski_1:
EOS is joining forces with CodefireX. Go to this thread for new development

http://xdaforums.com/showthread.php?t=2372197
[Xoom Android Development] Madmick:
I'm on 203: the latest working build.
[Xoom Android Development] boabsmith:
Same as me then. My flash player version is 11.1.115.12
[Xoom Android Development] doc984:
Swipe across screen to switch screen on or off

hi all,

the feature i am going to describe is weird coz i didnt find a replacement anywhere. what i am talking about is that the screen of my xoom can be switched off when its on or switched on when its at sleep if i swipe across the screen (from beyond the actual screen) either horizontally or vertically. i discovered it accidentally and this happens only in Team Eos4 177 version of this rom. Is there any setting or an app that can do that coz i need it so much as my power button does not respond that well since some time. and i tried few roms after 177 but i dont get the same feature and i go back to 177. And i definitely want to try newer versions. Any luck?
[Xoom Android Development] drewski_1:
Elemental-X Kernel 1.2

Search for the thread here on XDA
[Xoom Android Development] grey.ghost:
Does anyone have a link to banks minimal gapps?
[Xoom Android Development] uzi2:
http://xdaforums.com/showthread.php?t=2012857

Use Core, it has updated Play and transport, which wasn't in the old minimal.

Swyped from my xoom
[Xoom Android Development] scottgti:
http://bit.ly/1c5ScV9
[Xoom Android Development] Madmick:
In that OP it says:

So does hotword detection work in this Gapps package for the Xoom? I'm guessing not, and this is only for Nexus 4 users, because from what Runandhide posted my understanding was that the lack of hotword support was a matter of Google never writing code for non-Neon devices, so it's a hardware handicap unless some independent developer writes code for Google Now on non-Neon devices from the ground up, and that doesn't seem possible because it was also my understanding that most code for proprietary Google apps was closed-source even though the OS is open-source.

In any case:

(1) what are the advantages of this Google Core Gapps package over the Gapps package listed in the OP?

(2) Is this thread obsolete? Should we be posting all this stuff in the new Codefirex thread that drewski linked? I'm guessing this will be left as a reference archive.

---------- Post added at 03:03 AM ---------- Previous post was at 02:38 AM ----------

I was hoping it may have been a stability issue with the more up to date flash version. I uninstalled the 11.1.115.69 and installed the 11.1.115.12 that you have running, and still no video. Sometimes I really do hate tech.

Maybe I should just try a full wipe. Does anyone have the link to an SBF for the Xoom? I'm talking about a full restore to out-of-the-box factory software. I'll just SBF, re-root, re-flash. See if that works.
[Xoom Android Development] uzi2:
There isn't enough system space in the Xoom for a full 4.2.2 ROM and Gapps. EOS makes use of symlinks to overcome this to an extent. With CodefireX space is even more critical as BRD explains in the thread.

EOS development has stopped at 203, but you may wish to continue with this until the CodefireX 4.3 is available. The present CodefireX is considered a test build and is missing many of the features of EOS 203. However, it is fully functional and super smooth.

Future development will be in another new thread once BRD has worked his magic.
[Xoom Android Development] Madmick:
So is this Core Gapps package viable with 203, and would you recommend it over the one from the OP I have installed?
[Xoom Android Development] uzi2:
I would stick with the EOS gapps for 203.

You will need the BaNkS gapps, if you decide to try CodefireX.

Swyped from my xoom
[Xoom Android Development] gibbs1984:
Can you post the links to the new development thread in here before it's closed BRD so that we all know where to go for some more Xoom love please? :)
[Xoom Android Development] bigrushdog:
http://xdaforums.com/showthread.php?t=2372197

That's the general discussion thread. I dropped one test build them aosp dropped 4.3 on us. So we're working to get 4.3 going. So the general thread is the only new thread for now. I'm gonna keep these Eos threads open for a bit still. There's still relevant discussion going on. I'll give a heads up before I shut them down.
[Xoom Android Development] notbrodie:
yes, it's viable and yes, it's recommendable. it lets you install the GApps you want to install (because it comes with nothing, except play store). whatever you want, you can install from play store.
[Xoom Android Development] mscott998:
Can someone help? I cannot install the latest eos update or latest cm 10.1 roms. I've tried cwm and twrp. No matter that i get stuck on motorola screen. Is there a boot loader update that I'm missing?
[Xoom Android Development] matt0301:
Don't use last EOS Rom, that isn't working. The Last one working is build 203. But, BigRushDog are in a new project guy, look in General forum. Ah, almost forgot, use search next time, it's useful man. :thumbup:
[Xoom Android Development] axeman24:
My xoom stuck both on 204 and 205. Cant get past Motorola splash either. 203 works fine though
[Xoom Android Development] drewski_1:
yes. 203 is the last working build . BRD can't delete 204 or 205.

see last page or two for new development thread as EOS joins with CodefireX
[Xoom Android Development] Ipse_Tase:
Oh man, this thread has gone cold. I will miss EOS and all their good work.
[Xoom Android Development] jbel25nyy:
Is there any trick to getting HDMI out to work? I updated to 203 last night, but the TV doesn't detect any signal from the HDMI port. This worked fine for EOS 3 Stable.

Thanks in advance for anyone's help!
[Xoom Android Development] tumpy:
I see you are jumping from thread to thread about your problem, I will suggest dreamcwli (MY 4.2.2 rom, It is the best 4.2 rom by far for the xoom infact he was the first to get most of xoom bugs fix and help team eos, he is now working on xoom 4.3...

http://xdaforums.com/showthread.php?t=1997434
[Xoom Android Development] elton.de.nascimento:
My xoom works fine...
[Xoom Android Development] hons9424:
Hi,

I just installed the 205 version but gone into brick!!!!

I installed the rom via Rom Manager, it rebooted after the installation and then stuck at the Moto Logo!!!!

Could you help?? :crying::crying::crying:

Thanks. :eek::eek::eek:
[Xoom Android Development] dsbnz:
Have a search through the thread. v203 is the last working 4.2.2 version. Hope u had a backup?.
[Xoom Android Development] hons9424:
What !!!!:eek::eek::eek::eek::eek:

I saw the 205 have 8000 downloads!!!!!:(:(:(
[Xoom Android Development] hochoch:
It can't be taken down but you should have been able to flash 203 over it after a quick dalvik wipe
[Xoom Android Development] robbo10:
Can somebody give me clue as to witch gapps work with v203, upgrading from v200. The link in the op fails to flash and the one from goo crashes :mad: Tia

Xoom Xoom Xoom………… \m/
[Xoom Android Development] hons9424:
Just installed the version 203 and is running good !!!! :good::good:

So, at this point there will be no new updates to this rom anymore. Is that correct ??:confused::confused:
[Xoom Android Development] dsbnz:
As far as I know, that is Correct. The 4.3 rom is in development currently. v203 is the last working version of 4.2.2
[Xoom Android Development] hochoch:
you can follow development of the new 4.3 rom that is being handled by former members of EOS here: http://xdaforums.com/showthread.php?t=2372197

There is also this 4.3 thread for a more vanilla/stock version of 4.3: http://xdaforums.com/showthread.php?t=2418290
[Xoom Android Development] robbo10:
Witch gapps did you use?? after the forth restore I gave up last night lol
[Xoom Android Development] pkelly517:
I suppose you could try the gapps linked in the op....
[Xoom Android Development] robbo10:
I tried those they kept failing :confused:
[Xoom Android Development] notbrodie:
use banks core gapps for 4.2.2 (he took them down, but this is supposed to be a good mirror. can't check the link because i'm at work and its blocked: http://www.adrive.com/public/wPhK9V.html)
[Xoom Android Development] hons9424:
I also tried that version but it perform weird when it runs. The screens of the different apps overlapped and some of the apps just stop working so I return to v.203.

---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------

I used the GApp 20130403.:):)
[Xoom Android Development] hochoch:
these are the most current gapps to use when flashing 203: http://goo.im/devs/teameos/roms/eos4/gapps/gapps-jb-20130413-EOS-XOOM-ONLY.zip
[Xoom Android Development] robbo10:
hmmm, I tried those a few times, I downloaded them on the Xoom, maybe I'll try the computer. thanks
[Xoom Android Development] Ipse_Tase:
Guys...I tried twice already to upgrade from Stable ESO3.0 to EOS4.0 n203...I did a factory default every time and still ended up with missing folders and unstable behavior.

Is there something I am missing in the process? I know the folder structure changes (multi-user) and all, but this is pretty annoying.

TIA
[Xoom Android Development] drewski_1:
are you using the special EOS Xoom GApps?
[Xoom Android Development] hochoch:
[MENTION=470268]bigrushdog[/MENTION] looks like the latest search update fixed hotword detection finally! (That was still broken right?!)