yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] srthimsen:
http://xdaforums.com/showthread.php?t=1782235

[RECOVERY] TWRP 2.3.2.3 (JB 4.2 Fix)
[Xoom Android Development] rohitece06:
I just wanted to report my experience after a clean install of 158+1208 gapps. everything seems to working fine although its not running as smooth as 155 (meaning before jellybean 4.2). UI stutters throughout the OS on stock setting as well as customized settings e.g., I disabled all animation, overclock to 1408, ondemand governer, force/unforce gpu rendering etc.
[Xoom Android Development] NWinfuse:
I also did a clean install and have seen none of the issues you are reporting and thats with no overclock or other tweaks to settings so not sure what is causing your issues. Did you have any of these issues while on 155 or is this all new ? you may want to go ahead and flash 160 along with 1208 Gapps and see how your experience is with that build
[Xoom Android Development] runandhide05:
If you haven't already update to nightly 160 to fix a few bugs include the lock screen issue .

Thanks :)

FYI this is a perm correct fix found by BRD
[Xoom Android Development] arrtoodeetoo:
Does this have an option to bring back the Tablet UI yet?
[Xoom Android Development] runandhide05:
we are getting everything stable before we work on features.
[Xoom Android Development] arrtoodeetoo:
Thanks. Quick and to the point. :)

I'll be jumping in when the tablet UI is back.
[Xoom Android Development] rohitece06:
These issues are new. Also I forgot to report, every now and then screen flickers. It happened on 158 and happening on 160
[Xoom Android Development] rabarkar:
I just installed 160. If feels good on the tablet. As usual, every nightly is getting better :)

The only thing I noticed is that when I dock the Xoom in the multimedia stand, I can not adjust the volume, when I press the volume keys, the volume bar appears grayed out, and I can not interact with it (I think it was reported before, but it seems to continue in this nightly). Audio sounds fine in the dock, but pretty loud.

Will continue testing it :) Thanks.
[Xoom Android Development] runandhide05:
It was reported, and I posted what you needed to do. Yet again Google went changing crap...lol

When docks in a media dock the volume rocker is set to only adjust media.

So if no media is playing you get no response when u attempt to adjust volume.

What u need to do in unlock the volume tied to the media only.

Do this, dock tablet, navigate to settings, dock, audio, and then uncheck the box for media volume lock

Then u will be able to adjust the volume as normal while tablet is docked
[Xoom Android Development] Legato Bluesummers:
Downloading 160 now. 156-8 all ran good for me. Usual errors people reported. Nothing that broke the tablet or prevented the rom from being a daily driver, at least for what I use my tablet for. Thanks for the great work Eos.

Can't wait for 160 to finish downloading. For some reason I can only pull 3g tonight at work on my phone. So download is VERY slow. :( I've rebooted many times. Something must be up with the antenna in the area

Sent from a GlaDos Baked Potato
[Xoom Android Development] runandhide05:
Until we get them on goo here is the latest gapps

gapps-jb-20121209-EOS-XOOM-ONLY.zip - 74.19 MB

Use for 160+
[Xoom Android Development] alex94kumar:
I'm loving the photosphere :D Hint: if you want to actually view it as a photosphere, just upload it to google+ and view it on a computer =)

https://plus.google.com/photos/1073...ms/5820562716699804481?authkey=CIPS-u3Ov-bNag

^Just took that on my Xoom. Was too lazy to try and make it errorless, but you guys get the idea. There's also bad lighting in my house so it will look bad. Once you click the link, click on the picture for photo-sphere!
[Xoom Android Development] Taysider:
160 & 209 gapps running very smooth fantastic job guys :D
[Xoom Android Development] uzi2:
Just for information, if anyone else cannot access streetview in Google Maps since using 4.2, it is because you are using a hidden SSID. Strange bug - Google are aware - nothing to do with this ROM.
[Xoom Android Development] dilema:
Nice place :P photosphere has some cool implications
[Xoom Android Development] gibbs1984:
OK, I've just gone from 158 to 160 but still find that it's pretty unresponsive.

I mean by opening the app draw and then swiping, it takes a good second or two to catch up and then it becomes responsive.

I've turned off all animations too and I've over clocked it to 1504mhz (although it says it's not set on boot)...

Actually finding that ICS was a lot more responsive in all areas, this feels very sluggish. Is it just me?

I know it's in very early stages but thought I'd mention it.
[Xoom Android Development] Taysider:
Did you do a factory wipe? I did from 158 to 159 and get no as in zero lag without boosting cpu speed
[Xoom Android Development] isidar:
Hi to All,

Just put 160 with 1209 ... and must say everything is great, and quite fast, even a VPN-conection I must use through a sandbox is working faster as with anything else ...

I also like very much the buttons in the middle and the two dropdown in the upper ends, it took only a few clicks to get used to them and for me it is an improvement :)

Can you post again the link to buy yoy a beer? Would love to buy a sixpack :))

The only thing I have a little prob with is the three time issue with the old system and the new /0 ...

But I will ask about that in another post when I can explain it better!

Thank yoy vert much! I'm so happy with my Xoom and with Team EOS !!!

:)

Isidar :)
[Xoom Android Development] gibbs1984:
I did a Factory Reset when coming from 140 something but going from 158 to 160 I just flashed over the existing ROM.

Shouldn't need to Factory Reset from 158 to 160 should you? It's not a major update?

I wouldn't really call it lag as such (don't know if that's the proper term) more that it feels really heavy and slugish. Once it's scrolling it's really smooth but to get it going it can feel slow.

I've done a YouTube video to try and show it, doesn't happen all the time and now my values of Lagfree, 608MHz and 1504MHZ have stuck it seems a lot better than the default values of 216MHZ and 1000MHZ (obviously I suppose).

Sorry about the quality I thought I had uploaded it in 720p quality but obviously not and also the poor cameraman, shaky hands ;). From around 26 - 30 seconds you can see how long it takes to open the app draw and then when I swipe my finger it takes a second to realise and then move:

Linky.
[Xoom Android Development] recognitium:
First of all thank you very much for this is awesome update to Xoom. Running pretty fast, almost no glitches at all, apart from some screen flashing when I don't tweak animations and over clock.

I join @Isidar in my will to invite you some beers.

I was testing something that didn't work out though. Even though my generic Bluetooth keyboard and mouse are identified and pair well, neither has worked at all. Before 156 keyboard was perfect, and mouse had a kind of well-known bug. Actually I started testing it wishing the Bluetooth mouse bug had been fixed.

Anybody else having this kind of minor issue?

If recalled on how to do it I can send logcats.

Thank you either way. EOS rules.

Sent from my Xoom with EOS 4 Build 160, gapps 12/09
[Xoom Android Development] mancowmilitia:
I'm going to be coming to 160 from 155. I will do a clean install, but I see that the latest TWRP is needed for 4.2 ROMS. Should I install TWRP v2.3.2.3 now (ie - works OK w/ 155), or wait until after flashing 160?
[Xoom Android Development] srthimsen:
Now, before flashing any 4.2 ROM.
[Xoom Android Development] istrait:
Just flashed from 158 to 160 and it flys... Thanks again team eos....
[Xoom Android Development] ggrant3876:
My Rogue Recovery works just fine.

http://xdaforums.com/showthread.php?t=1235170
[Xoom Android Development] runandhide05:
Grant that recovery will leave another /0 on data/media/ each time u flash a 4.2 base ROM

As for donation links BRD has his link in his signature / under his avatar while on desktop ( does not show up in tapatalk ) unless u click his user name
[Xoom Android Development] Jethro10:
How would one remedy the fault once you had it?

ie. removing the extra /0/0/0 's

J
[Xoom Android Development] lpasq:
i know the thanks button keeps threads from clutter but i really wanted to put words to my gratitude to teameos bigrushdog & runandhide05! bigrushdog tattooed my xoom years back with his kernel that saved it from a day one brick being part of the early adopter recovery/root black screen of death squad. then with solarnz took us out for ice cream. now teameos keeps the g1 of google tablets alive and kicking. i have no need for n10 boys. awesome!!! love my n4 and the n7 is pretty nice but the xoom is special to some of us. an 8"-9" nexus slate is my hope though to one day be my daily driver tab. until then and as long as the eosxoom handles my content consumption duties...life is good!!!

merry christmas bigrushdog: 99S44326RB765494F / runandhide05: 6F9622839P214603E
[Xoom Android Development] runandhide05:
Thank you so much!

With any file manager that has root access copy the content from those to the first /0 located at /data/media/

So it should look like this

/data/media/0all of your content

Then just delete the access /0/0/0
[Xoom Android Development] bigrushdog:
Was that you that made my in box light up and made me feel all fuzzy? :laugh::good:

Well it's seems Xoom may have a little life left after all. When me and kevdilu drop this

Life will be a little better. :cool:

Thanks a ton. Oh, now that I fixed lockscreen and let people back on their Xoom :rolleyes: I can work on things like smarter navbar buttons and that pesky LTE. :victory:
[Xoom Android Development] logitechor:
Testing the Roms is great. I realize it takes time to work out issues. 4.2.1 seems different then 4.1.2 in a number of ways. Thank you for your efforts.
[Xoom Android Development] EDNYLaw:
Hey BRD, thanks for all your work, it's really appreciated. Since you opened the door for a sneak peak at what is to come, I'm just wondering if you're having any luck with the HDMI issues. No pressure, ETA's or anything like that, you just made it sound rather complicated when you mentioned something and I was just curious if you worked it out or it looks promising. Thanks again for all your work and effort, if you need someone to test anything for the HDMI issues, let me know and I'm happy to help out. Great job all around Team EOS!
[Xoom Android Development] tdarren:
I know Team EOS and many others support TWRP but I much prefer the simplicity of Clockworkmod, Koush and others have the experience and I think its less clunky than TWRP. TWRP is for the advanced users, I mean, Who puts a status bar with a clock and a home button in a recovery? Is there really a need.

I personally use Rogue touch recovery and will remove the 0's when needed just because I can't stand another recovery.

But I give my full support in he development of Eos ROMs and Kernels. Hope Eos has plans to expand to my HTC One X in the future :)
[Xoom Android Development] aR_ChRiS:
There's an unofficial CWM 6.0.1.9 port from another member in the xoom development section if you want CWM instead of TWRP
[Xoom Android Development] NWinfuse:
I understand having a preference but have you actually used TWRP? It couldn't get much simpler and it does the job without the need to go in and remove 0's after the fact
[Xoom Android Development] tdarren:
Would I need to remove the 0's using this?

Edit: Fantastic, thanks very much for notifying me of this.

---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------

I have used it once. I only use a recovery to flash things for my device, not to tell the time or whatever extra it does.
[Xoom Android Development] aR_ChRiS:
Since 6.0.1.5, CWM has no more /0 issues in 4.2, so you don't need to remove the 0's anymore.
[Xoom Android Development] alex94kumar:
Can't wait for more awesome features to be added! Les'go!!!
[Xoom Android Development] CatfishKnight:
Google search update..

If this has already been address sorry.

I found out that after flashing the latest ROM' the Google search works just fine until I update the Google Search in Play Store.

Then when I try to Google search it crashes when trying to entry letters.

:)
[Xoom Android Development] runandhide05:
For the time being either

A) uninstall update

B) keep newest Google search but got to

Device settings >> language and input

Google voice settings and disable hot word detection
[Xoom Android Development] CatfishKnight:
Cool thanks. I reflashed my good saved ROM before I updated to the Google Search latest in Play Store.

So it is working now.

So I can update to lastest Google Search and then disable hot word detection, OK.

OK I just updated Google Search and disabled hot word detection and it didn't crash. Thanks runandhide.
[Xoom Android Development] adityamunshi:
anyone else have severe lag on #160 ?
[Xoom Android Development] lpasq:
You're welcome :D
[Xoom Android Development] iamanoopmk:
Nope... Its running well. Of course not as smooth as 4.1.2 but definitely no severe lags...
[Xoom Android Development] manicmoose:
Yeah....there's some lag, but I think team eos guys are expecting it, so hang in there....
[Xoom Android Development] power182:
A couple issues

Thanks for the upgrade!

Two things; first Google Now crashes every time I open the application. Second, when I try to download a movie I purchased from Google play I get the error "Couldn't fetch license (error 0)". I know they used to block rooted devices but I thought they lifted this ban? It works some time ago?

Clean install was done and using 160 and gapps 1209. Any ideas?

Thanks again for everything and keeping my device relevant!
[Xoom Android Development] HuckFinn:
Regarding Google Now, search is your friend. Just one page back you will find the answer.

http://xdaforums.com/showpost.php?p=35329721&postcount=369
[Xoom Android Development] power182:
It's not the search that is crashing is the loading of the "cards". I'll try the fix anyways when I get home.
[Xoom Android Development] iamanoopmk:
Just FYI

Google now doesn't crash here... Mine is MZ601
[Xoom Android Development] runandhide05:
It hot word detection just like someone already pointed out, since hoyword loads as soon as u open it that why it crashes,

Disable it and you'll be fine
[Xoom Android Development] power182:
Thanks - any idea on the license issue with movies?
[Xoom Android Development] alex94kumar:
can't wait! i also cant wait for photosphere to work :D
[Xoom Android Development] fromthestars:
Sorry if this has been mentioned, but long pressing an icon or widget in portrait mode doesn't work. I same for swiftkey/stock keyboard
[Xoom Android Development] runandhide05:
Brd fixed that too and it also has been merged and should be in next nightly
[Xoom Android Development] alex94kumar:
i know devs hate this, but i must ask it... any ETA on the next/more functional nightly?
[Xoom Android Development] edboston:
Probably the next night. *grin*
[Xoom Android Development] alex94kumar:
i hope! :D
[Xoom Android Development] briansuperduper:
Can't wait to try this out...but even more excited for eos 4 stingray!
[Xoom Android Development] arrtoodeetoo:
I can't wait to try this out, but I have to hold out until the Sixaxis app is working with 4.2. Mario Kart is a daily event around here thanks to my XOOM (and I love that it makes my iPad 4 owning roommates say stuff like "I wish my iPad could do that!" :D)
[Xoom Android Development] golfdiesel:
I have noticed that when you restore data from a backup that you should not restore the bookmarks. By restoring them you will loose the sync option. This was also the case when my Nexus S received the OTA for JB.

Verstuurd van mijn Nexus S met Tapatalk
[Xoom Android Development] alex94kumar:
Will we have to go through the tablet setup every time we flash gapps?
[Xoom Android Development] perezj30:
Bluetooth keeps turning off

Just installed the new ROM and things are going well. One thing I am running into trouble with is the BT setting. By default bluetooth is off, and when you try to turn it on, it turns itself back off. Just wanted to bring it to your attention. Thanks again to all the devs that make these updates available.
[Xoom Android Development] XxLordxX:
BRD, I think you should leave the EOS 3 thread open until this release gets more stable and realiable, because as far as I'm seeing here (still didn't test, had no time for it) there are many guys with problems and lots of bugs, which is perfectly normal for a first release, but to get a more stable nightly the EOS 3 looks better now :)

Well, it's just an opinion, do whatever you want, you're (with solarnz) the boss here ;) and did a great work all that time on Xoom development :D
[Xoom Android Development] ArtoD2:
Is there a toggle for Phablet/Tablet UI?
[Xoom Android Development] XxLordxX:
BRD mentioned that they were still working on it, so I think there's no such feature now as it's only the first build and they were working on it after the release of this build :)

"This Story Ends Where It Began"
[Xoom Android Development] Darkman:
Thank you TeamEOS for your hard work and nice ROM again!

One question... i can not decombilie the systemui and the framework-res... i have update the SDK and the apktool to the latest version. Have any one a tip? It is the first 4.2.1 files they i want to decombilie...

I want to make the 1% Batterie MOD and USSD for the EOS4 ROM.

send from the streets......
[Xoom Android Development] dragonstalker:
What APK tool are you using or are you trying to use the Android SDK? Instead try using the DSI kitchen
[Xoom Android Development] LQQKS:
Any plans for Xoom MZ601?

Sent from my rooted Xoom MZ601

running CM10 JellyBean 4.1.2

using XDA Premium app \o/
[Xoom Android Development] huckl3b3rry:
The amazon app store force closes on me as soon as it starts up. Sorry if someone mentioned it already. Thanks for the continued work!
[Xoom Android Development] Jethro10:
Same with me.

also Amazon Kindle doesn't fully load, gets the kinda splash screen thingy then that's it.

Looking good though, for a first release. Bodes well.

J
[Xoom Android Development] bigrushdog:
Solarnz has given me the project so I'm the boss now. And that also means the buck stops with me. Guess it goes both ways. I closed the thread because the last 4.1.2 build is flawless and no longer being developed. Thus I'm not interested in any commentary on it. Also, it was filling with 4.2.1 bugs which, against my better judgement, i knew it would. All downloads are still available on goo for those that find 4.2.1 "challenging" :rolleyes:

My talented and trusty maintainer Runandhide is working on some of this issues discussed. I've also fix quite a few but wanna get a couple more fixes before we do another nightly. One thing that threw me off is for some reason xoom is running in tablet UI, and it should not be. Thus you see phone settings for the Eos interface. Guess I'll just bring in tablet eos settings then. Remember I'm working blind as I don't have my xoom anymore.

Stingray lte is proving to be a challenge. I've almost got it. When i get LTE going ill move on to everest. We have some VERY talented people coming on deck who want to push Eos to the next level. New features will be coming but let's get xoom stable first.
[Xoom Android Development] runandhide05:
No, don't rent movies threw there, maybe a log cat would be helpful. And I'll take a glace and see what the issue is
[Xoom Android Development] power182:
I'll run one tonight - PM it to you?
[Xoom Android Development] runandhide05:
Ya that or just just email it directly to me at my name at gmail dot com
[Xoom Android Development] runandhide05:
For the audio while in media dock.

As I had suggested, this is how you unlock the volume.

New:

4.2 brought in new feature while device is docked in a media dock the volume with only control media and music, if no media or music is playing the volume rocker will be unresponsive, ( greyed out)

To allow volume to adjust normally as if it were not dock do the following

must dock tablet to access setting!

Device settings >> sound >> dock section clock audio and then uncheck mark box "for music and media "

See video to step by step

https://www.youtube.com/watch?v=uvjtNLMzcHg&feature=youtube_gdata_player
[Xoom Android Development] kentedman:
However if you use your dock for audio (either with headphones or external speakers) unchecking that box will no longer play audio through your dock. But if you leave it checked then programs that like to hijack the volume control (such as Netflix, and hulu plus) start behaving really badly when trying to adjust volume while in the dock. Its all a bit botched up at the moment.
[Xoom Android Development] runandhide05:
Lol welcome to 4.2.1.... Google did a great deal of botching quite a few things...

Thanks for the heads up tho
[Xoom Android Development] power182:
Sent to your gmail account. Thanks!
[Xoom Android Development] DefinityX:
If it's the same issue that was posted recently with it throwing up a "Failed to fetch license error", there is a fix a few pages back that worked. (deleting the license files in a couple specific folders) but I can't vouch on the working with 4.2... I'm still on the last 4.1.2 nightly.
[Xoom Android Development] FrankCastle:
i am lagging when swiping between home pages - but im not sure if this is normal or im doing something wrong (i came form eos3 to eos4 #159 and now 160)
[Xoom Android Development] alex94kumar:
I'd expect to see lag until BRD and RnH get everything stabilized
[Xoom Android Development] laur3n.newm4n:
Where's the option to show the LED charge light while the device is charging? I ran a search for LED Charge in this thread, but nothing came back.
[Xoom Android Development] HuckFinn:
Settings> System (Under EOS Settings)> Device Settings
[Xoom Android Development] laur3n.newm4n:
Thanks! Another thing I've been having problems with is Daydream. When I go to Settings > Display > Daydream and try to click the little settings icon next to Clock to change it from digital to analog, Settings force closes. I'm on the 160 build, and it worked fine on the 158 build. I did do a wipe in between the two flashes.

I've also been having Root Explorer tell me it can't copy&paste into system/app (even when R/W is enabled) because I'm low on space. But I'm not. This has happened on both the CM 10 (which is 4.1) builds, and on these EOS 4.2 builds. Titanium Backup says I have 60.1MB free in the System ROM portion, 29 GB free in the "sdcard", and 16GB free in my external sdcard.
[Xoom Android Development] runandhide05:
Use the latest gapps for xoom only
[Xoom Android Development] laur3n.newm4n:
I am. I made sure I re-flashed them when I went from 158 to 160 too.

EDIT: Just reflashed them and the Settings app is still force closing when trying to change clock's Daydream settings.
[Xoom Android Development] mhausig:
I installed 160 last night and after some struggles and initial slow performance almost everything seems to be running ok. However the Kindle app won't progress past the splash screen. I tried clearing the cache, uninstall/reinstall but so far nothings worked.
[Xoom Android Development] runandhide05:
Look in your system/app and see if DeskClock.apk is in there
[Xoom Android Development] laur3n.newm4n:
DeskclockGoogle.apk is there - should I rename it?
[Xoom Android Development] runandhide05:
Are u using the gapps dated December 9th?

Flash these

gapps-jb-20121209-EOS-XOOM-ONLY.zip - 74.19 MB
[Xoom Android Development] laur3n.newm4n:
I was using the 20121208 ones because those were the ones that were available when I downloaded the 160 build from GOO.IM .. I'll flash the 20121209 ones though.
[Xoom Android Development] runandhide05:
Sorry, the gentalman with the goo login info is officially retired so its a little harder to get the goo info up to date, I just keep posting any new ones in the thread until its uploaded to goo.
[Xoom Android Development] fleury14:
A little off topic but has anyone else used the beautiful widgets daydream option on the Xoom? Looks great on the large screen