yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] bigrushdog:
Crap. I tested that too. Oh well. Next nightly.
[Xoom Android Development] gibbs1984:
In the naughty corner please ;)
[Xoom Android Development] FormerPalmOS:
Why no USB mass storage mode...

In order to support mass storage mode, the internal storage and(/or) external SD card have to be unmounted from Linux on the Xoom. In MTP mode, this is not required as the MTP driver arbitrates between accesses from the local OS (Linux on the Xoom) and remote OS (whatever is communicating over MTP).

Your Xoom and some of your applications might not like their "external" storage going away...
[Xoom Android Development] gibbs1984:
Tried flashing 168 and got installation aborted (bad), checked the MD5sum and it's good.

167 is working though, will try copying the ROM from my computer again. Could it just be a bad copy from the computer to the Xoom?

I'm redownloading it but the connection is sloooow!

EDIT: Transferred it again and it's working now :)
[Xoom Android Development] gibbs1984:
Anyone else having problems with Titanium Backup?

When doing a batch restore it keeps freezing or doesn't restore anything, doing it one by one is working.
[Xoom Android Development] runandhide05:
I've noticed it on all my 4.2 devices :( one at a time is the only way to get it to work.

That said its worth the 10-15 minutes figuring out how to manually do a backup/restore of your apps+data

And saves space by doing it from laptop a posed to on devices
[Xoom Android Development] gibbs1984:
Thanks, at least I know it's not just me :(

Where's best to learn how to do a manual backup/restore?
[Xoom Android Development] runandhide05:
Google...

Or

http://xdaforums.com/showthread.php?t=511835
[Xoom Android Development] Alxoom33:
168
[Xoom Android Development] kuroguy:
Should changing the color of the back softkey also change the color of the down arrow that is displayed in its place when the keyboard is displayed? It doesn't. My back key also sometimes reverts to white. Pressing it changes its color back. I'm on 168 with 1-1 googs.
[Xoom Android Development] bigrushdog:
Ok. I'm reverting the softkey commits.
[Xoom Android Development] alex94kumar:
You guys must have done something, 168 feels WAY more responsive on the homescreen.
[Xoom Android Development] :
Batch restore with Titanium works fine on my N7 using Paranoid Android 2.99 beta (4.2.1). The issue might be EOS related, although I did not experience it with previous EOS4 nightlies.
[Xoom Android Development] drewski_1:
I've had this happen on N7 + PA 2.99 beta.

A reboot and batch skipping the app it got stuck on works.

I restore user apps with data which might be the issue with the freezes.
[Xoom Android Development] petrossa:
Second that. The gluey feeling you got after a tap is gone. :)
[Xoom Android Development] :
Then TiB doesn't like some app and the issue might have nothing to do with 4.2 or EOS 4.

Incidentally I always restore apps and data. It's the data I care about! :)
[Xoom Android Development] Taysider:
+1, Whatever you're doing, however you're doing it i don't care. Just keep doing it, you guys amaze me. Fantastic work :D
[Xoom Android Development] tinfoil_dave:
Some configurations just don't play nicely with batch restore in Titanium. Switching the "App processing mode" to "AUTO, Indirect" in the preferences has fixed this in the past for me.
[Xoom Android Development] trancoss2:
someone can say that the 169's New
[Xoom Android Development] ahmed007:
Its new for sure
[Xoom Android Development] drewski_1:
Thanks for the suggestion. I'll try that out.
[Xoom Android Development] dccrens:
Update from Rogue Recovery to TWRP

Just want to say THANKS! I am running EOS 150 Stingray and I just swtched (updated) from Rogue Recovery to TWRP 2.3.3.0. Everything went smooth as silk and all is running great.
[Xoom Android Development] vicky4112:
+1 also. Just flashed 169 and it is working great. Great work and sincerely appreciate your efforts.
[Xoom Android Development] Bl4ckpheniX:
I went in with root explorer and moved files from the "O" location created by 4.2 back to the "sdcard" location and have had no issues with titanium since. of course I only restore apps and not data when making big jump in builds. The "O" Location caused problems in with my galaxy nexus as well. And doing this helped me with that device as well.
[Xoom Android Development] vicky4112:
I have to reinstall latest version of "gapps" as in the link on OP page, and also clean cache everytime I flash a new nightly. Otherwise the play and gmail etc are not working. Is this normal?
[Xoom Android Development] hipocrazy:
Rockin' Rom! Thanks Eos!!
[Xoom Android Development] uzi2:
You need to flash the updated Rom and the latest gapps in the same session. Don't worry about cleaning caches.

Swyped from my Xoom
[Xoom Android Development] WarLion:
I had the same problem I forget to install gapps at the same time when the xoom start all the google apps where not working so I go back and install only gapps then when the xoom start I had to setup just line when first boot lol all work great just to remplace the gmail widget and the cam and gallery icons, is really importan to flash gapps right after a new night is install
[Xoom Android Development] Taysider:
Don't forget to fix permissions
[Xoom Android Development] scottgti:
And don't forget to read the warning that is on the screen during the gapps flash.
[Xoom Android Development] dyskinesia:
Don't want to sit in the corner but...

With 169 seemingly random times my screen goes very dim. Can ALMOST make out what's on screen. Was able to see the brightness slider and slide it to max w/o effect so had to reboot.

Last time i had just moved brightness slider from ~50% to max and it went dim then off.

Not complaining just givin feedback.
[Xoom Android Development] runandhide05:
this is a known issue effecting just about ALL devices,

here is some more info

http://xdaforums.com/showthread.php?t=2080690
[Xoom Android Development] vicky4112:
Fix permissions ...

Please explain.
[Xoom Android Development] runandhide05:
Not needed, its included in our ROM and gapps script.

What it does is ensures that all files have correct permissions.
[Xoom Android Development] russtyd:
What runandhide05 said :)
[Xoom Android Development] dyskinesia:
Sorry. I never had it until 169 so I was not sure guess I should have known it was same one that has been discussed multiple times.
[Xoom Android Development] petrossa:
Did some juice testing. One xoom on Eos 155 and one on the 4.2 nightlies. I put the backup of the first on the second so it's running the same stuff. At present the 4.1 xoom is still on 27% but the 4.2 is empty, and whilst being used less frequently. Both with wifi always on. And I still have the impression wifi is slightly wonky on 4.2. Where 4.1 goes blue bars almost instantly, the 4.2 stays white bars for 30+ sec and some apps have slower connection times. To me this seems more like basically 4.2 stuff then eos related.
[Xoom Android Development] ugachris:
Don't know if you've checked already, but I noticed that "Keep Wi-Fi on during sleep" was on Always when I first installed a EOS 4 nightly. Could help.
[Xoom Android Development] dj_ghosie:
Gesture typing is not working with the AOSP default keyboard. The stroke appears during the swipe yert no word generated.

Anyone else having this problem?

In the meanwhile I'll keep using swype.
[Xoom Android Development] Alxoom33:
Yes

Same for me as well:)
[Xoom Android Development] drewski_1:
are there any plans to add in Wi-Fi Direct?

i seem to remember it being available at some point on EOS3 and then it disappeared and there was talk re-incorporating it.
[Xoom Android Development] runandhide05:
Its fixed, just waiting for it to get up on goo.im

In the mean time

gapps-jb-201314-EOS-XOOM-ONLY.zip - 83.55 MB

- fix chrome FC when accessing settings

- fixed gesture type

A note from timduru

In regards to the gesture typing, if you have any issues with the keyboard vanishing

Workaround for the moment is to go the keyboard settings and change to

+ Auto-correction off

+ Show correction suggestions:always hide
[Xoom Android Development] drewski_1:
thanks for all the new versions and bug-fixes, guys!

i think it's an OCD thing of mine, but can you name the GAPPS with 2 digit month & day (e.g. 20130104) which will match up with the ROM dating schema?

if not, no biggie. i just rename after downloading so everything sorts fine by filename / date. i probably should just delete the old stuff anyway :silly:

edit: and great work on the glut of post-holiday bug-fixes / nightlies :D
[Xoom Android Development] lepa71:
Can you tell me the full path where "O" location is? Thanks
[Xoom Android Development] runandhide05:
I would not suggest doing that, apps look for "sdcard" and since /data/media/0 is syminked as "sdcard" you can cause some issues doing that. And further more if you create a secondary user it will cause even more issues
[Xoom Android Development] trancoss2:
we do to clear the route O. something new in the 169.

Team Eos thanks
[Xoom Android Development] WhitestSand:
Appreciate all the hard work... When I try and enter settings in Chrome it is FC. Has had this problem in all releases, have tried

uninstalling etc. To no avail, is this a ROM thingy or just me?
[Xoom Android Development] joshndroid:
Fantastic job team eos on the 4.2... Heaps of customizations as well :D:thumbup:
[Xoom Android Development] runandhide05:
Look literary one page back ;)
[Xoom Android Development] istrait:
+1.... I do realize though that EOS team is probably busy, but I would like to see this.
[Xoom Android Development] joshndroid:
Anyone else have the soft key settings causing a force close on the eos control centre app or is this a known/documented issue?
[Xoom Android Development] WhitestSand:
Haha. Thanks.. Man I thought that I had just flashed the newest gapps.. I Blinked and I missed it! Keep up the great work ...
[Xoom Android Development] petrossa:
Sorry for the misunderstanding. I've put it on during sleep on purpose with both to test the wifi part. I wanted to see the difference in how quickly the bars turned blue. Which proved to me that there is indeed a wifi lag in 4.2 since they differed everytime and obviously had the same signal (checked with signal strength app)
[Xoom Android Development] trancoss2:
installed new gapps and crome open setting follows the FC any suggestions to fix it.
[Xoom Android Development] eddyther:
Chrome 's settings are working fine here with latest gaps.
[Xoom Android Development] MARIANOTE:
Fisrt of all, thanks and Good year to all EOS team membersi have a question.... can i donwgrade to ICS nandrod build by twrp or cwm from JB? what wipes i need to do?

JB works great an fast, but XBMC closes and i will try to make a mediacenter with the xoom for my room jejeje

any idea for the XBMCissue?:cyclops:
[Xoom Android Development] hochoch:
Still getting fc's on the newest gapps :( tried uninstall reinstall to no avail.
[Xoom Android Development] eddyther:
Lasts roms are 4.2. Did you try the 4.1 series, also Jingerbread?

It is a big step forward to go back to ICS, in my humble opinion.

Nighty 46 is the 4.1 that better worked for me. Give it a try.

Yo have to make a wipe of the internal memory (make first a backup) .

About the gaps, I think that you have to use the "gapps-jb-20120802-eos-signed.zip", because the lasts one's are fitted to 4.2 nighties.

Suerte che!
[Xoom Android Development] MARIANOTE:
i have the 167 installed....is not gingerbread is jellybean i think? I dont know why XBMC crashes and will try to test XBMC on ICS build. Ok need to make full wipe and that sinclude system, data, cache and another? Thanks by the answers!

Igualmente suerte chango!
[Xoom Android Development] eddyther:
Yes sorry, JellyBean...

About the J.B 4.1, try 146 (in the last post I wrote 46 by mistake!)

Enviado desde mi Xoom usando Tapatalk 2
[Xoom Android Development] NWinfuse:
155 was the smoothest build of 4.1 in my personal opinion
[Xoom Android Development] Alxoom33:
Still get FC on chrome settings with 1/4 gapps. Gestures fixed but dissappearing keyboard is a pain! Fix not with it for now. Reloaded my Thumb keyboard from Ti Backup. :cool:
[Xoom Android Development] christianpeso:
Brd, runandhide

Have u guys looked into adding the entropy fix? Couple of other device Roms are implementing it right into the rom using init.d or something else. Imoseyon nexus 7 and galaxy nexus kernels has his own version of the fix coded in the kernel.
[Xoom Android Development] pkelly517:
Did you re-install the rom when you flashed gapps?

169 + new gapps just worked for me.
[Xoom Android Development] Roseysdaddy:
Anyone know how to get the system icons (WiFi/ notifications) on the bottom with the tablet ui? Can't find the settings.
[Xoom Android Development] runandhide05:
Boot to recovery, wipe your /system flash ROM and gapps reboot profit. Guaranteed got to get rid a system apk in there.
[Xoom Android Development] bigrushdog:
There is no such thing as a tablet ui anymore.
[Xoom Android Development] marmo:
Hi all,

Is there any way to put the Volume and Brightness slider at the bottom of the notification bar on 169 nightly?

Now its always on the top.... :$
[Xoom Android Development] bigrushdog:
I'm running his his 5.5.1 230 kernel on my gnex. The kernel patch is definitely the best way to address this issue. I don't like the other solutions like daemons running. Ricardo Cirquiera of CyanogenMod says it's all BS. So I think it's safe to say the jury is still out on any true honest real performance increase.
[Xoom Android Development] bigrushdog:
I forced it on top for complex reasons. In time I'll let it roam free in the quick settings panel.
[Xoom Android Development] marmo:
Ok, thank you BRD, I'll wait until then. :)
[Xoom Android Development] Roseysdaddy:
Any way to make it look like this from the system settings?
[Xoom Android Development] tadiv:
Goo.im can't seem to find the file in this link... Any suggestions?

Tom
[Xoom Android Development] fvlserevere:
...

http://mirror1.teameos.org/roms/eos4/gapps/
[Xoom Android Development] WarLion:
what's the diference betwen the first gapps and the one from yestarday?

any one knows?
[Xoom Android Development] runandhide05:
Ya I fixed keyboard, fixed clock settings fc in daydream, and a few other thinga
[Xoom Android Development] alex94kumar:
Photosphere?
[Xoom Android Development] runandhide05:
Not yet, more important things that effect stability and usability are higher on the list.
[Xoom Android Development] alex94kumar:
Makes perfect sense. Will report issues, if any, once gapps are flashed.....
[Xoom Android Development] EDNYLaw:
I looked through the thread and didn't see anyone with HDMI issues but I don't have picture through HDMI that I did on 155. Have audio though.

Also can't get battery text to work or EOS toggles (as in enabling them doesn't bring them up).

But great job, thanks for all your hard work keeping the Xoom Alice and kicking!

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Xoom Android Development] alex94kumar:
Still having keyboard crash issues on 12-3 Gapps. Seems like word prediction is an issue. Went ahead and installed Jellybean Keyboard https://play.google.com/store/apps/details?id=com.jlsoft.inputmethod.latin.jelly.free&hl=en from the Play Store and all is fine. Seems like the best workaround for the time being
[Xoom Android Development] runandhide05:
Its because u still have the none aosp latinime on your syatem, delete it (latinimegoogle.apk) and reboot.

Or simply go to your input under settings and choose the stock aosp keyboard
[Xoom Android Development] xBlackDroid:
i've just enter to say

THANKS Team EOS!!!!!
[Xoom Android Development] alex94kumar:
ill try that. And I was using stock aosp keyboard on 12/3 gapps and it was still crashing. but its probably what you just described
[Xoom Android Development] xoom68:
EOS Devs

I am still running 155 at the moment. Been trying to run XMBC for android for non neon devices for a while now. They are constantly FCing, and the DEV is still scratching his head unable to understand why. He has asked if any of you guys would have an idea what could cause the following error.

12-05 00:04:34.260 V/XBMC (16532): 00:04:34 T:1496440264 DEBUG: Unfocus WindowID: 10007, ControlID: 95

12-05 00:04:34.530 V/XBMC (16532): 00:04:34 T:1556713656 INFO: - Created session to http://www.google.com

12-05 00:04:37.340 F/libc (16532): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 16548 (org.xbmc.xbmc)

This happens in seconds, minutes, browsing the menu, after adding an SMB share etc... for 99.9% of us Xoom owners. Any ideas ?
[Xoom Android Development] logitechor:
Been using this Rom now for a few days. Had trouble with Keyboard disappearing - turned off autocorrect features - working fine now. I like 4.2. Thank you for bringing it to us.
[Xoom Android Development] WarLion:
don't understand why I don't had that problem
[Xoom Android Development] ashwanikoul:
cant find gapps package

the link to temp gapps package leads to a file not found page on goo
[Xoom Android Development] xoom68:
That's why I said 99.9%. You seem to be the only Xoom user on 155 that can get it to work. Give me a screenshot of it running for more than an hour, then I will know you have a magic xoom. :p
[Xoom Android Development] bigrushdog:
Just a heads up on where we're at. The new gapps is up on goo. Photosphere, gesture swipe keyboard, and facelock are all removed. They may or may not come back. That's how it is for now. The next nightly, number 3, will have the phone type ui. I botched some code that was giving us tablet UI, which is the source of many issues. Much code has been cleaned up. As of next nightly, all available eos features are fully functional. More features will come once we get stableized.
[Xoom Android Development] jgardner:
BRD and all of Team EOS rock! You are the reason I love my xoom! Been using EOS since the first nightly and still love it!!!
[Xoom Android Development] jimboogly:
Thanks Runandhide05, deleted and rebooted, with no luck.

Like one of the logitechor, the solution for me was to remove auto-correct, auto caps, and pretty much anything automated for spelling.
[Xoom Android Development] bigrushdog:
No. I understand some builds have been modified to bring back the old ui. I've compromised my project enough supporting legacy devices trying to cling to the past. I'll continue developing our "tablet style bar" but I won't tear systemui apart getting back something that has been deprecated never to officially return.
[Xoom Android Development] Alxoom33:
Thank you, worked like a charm!:silly:
[Xoom Android Development] Frazer Scott:
169 is a big improvment performence wise for me. Only problem is that the keyboard closes after a few letters are typed. Using another keybord so this is no problem. 3d games have never run better for me. Big increase in fps on modern combat games. :)
[Xoom Android Development] runandhide05:
read above quote
[Xoom Android Development] lancemoreland:
Just came over from EOS 3 stable release and can confirm this behavior. Will follow the instructions above to remedy this. I did a complete wipe and started from scratch. I have my Xoom overclocked to 1.7 and this build is not as snappy as the EOS 3 stable release overclocked to 1.5
[Xoom Android Development] Kamau54:
I'm coming over from the stable eos 3.

Just a quick question. How is this one running so far? I see a few bugs that are being handled, but overall, how's it running for everyone?
[Xoom Android Development] alex94kumar:
Everything is buttery for me except the homescreen on 169. This is such a huge improvement over previous eos4 builds. I am amazed at the progress here! great job BRD, RnH, and Dreamcwli!
[Xoom Android Development] logitechor:
Really liking eos 4 169 and Jan 4 Gapps. All seems. Thank you.
[Xoom Android Development] Kamau54:
Looks like I better join the crowd then.

:highfive:
[Xoom Android Development] eddyther:
I have it installed in the last nighties and I didn't feel any improvement at all.

Enviado desde mi Xoom usando Tapatalk 2
[Xoom Android Development] mutiny:
I'm forever grateful to Team EOS for their work. Thank goodness I never sold my Xoom. Look at my sig. Xoom development is more than alive and kicking while TF201 has been 6 feet under for months and has already almost finished decaying. Unbelievable.
[Xoom Android Development] bigrushdog:
Roach is supposed to come back after the holidays. We'll see.
[Xoom Android Development] mutiny:
That would be super appreciated! :) I'll be buying you guys beer next week for this work on the Xoom. This tablet is still a beast thanks to you guys. You'd never thought this was a generation one Android tablet from the Honeycomb days. Simply awesome.
[Xoom Android Development] SAHorowitz:
I know it is not necessarily specific to this rom, but has anyone got google videos to play? I heard Google fixed it, but I am still getting rental period expired on new rentals. I I believe it is from rooting the device.

Thanks.
[Xoom Android Development] bigrushdog:
Ya. The guys that have rolled with us from day one. Their xooms have been to hell and back! I'm surprised we haven't heard of xooms just dropping dead at this point.
[Xoom Android Development] mutiny:
Awesome dev support. ;)
[Xoom Android Development] dj_ghosie:
It's not really the ROM that's causing the crash. The main cause is that the XBMC codes don't play well with Tegra2 CPU, it's well documented in the XBMC thread at XDA. I'd suggest you to take a look at that thread to get a better understanding of the situation.

If you are going to use the Xoom as the heart of the media centre, just use it as it is and maybe using an android phone as a remote control.

Edit: here's the link. http://xdaforums.com/showthread.php?t=1813089
[Xoom Android Development] dilema:
I've had eos since day one, never changed! Few hiccups, but stellar overall. You guys are the reason I hadn't had to buy a new tablet, it still dies everything I want and more!
[Xoom Android Development] Alxoom33:
Yeah still crazy after all these years!
[Xoom Android Development] trancoss2:
I installed the new gapps doing a wipe cache and dalvik cache and in entering the crome adjustment follows the FC. some solution.
[Xoom Android Development] MARIANOTE:
Thanks man! Great information!
[Xoom Android Development] runandhide05:
See above quote
[Xoom Android Development] trancoss2:
then I have to do a clean cache and dalvik cache and a factory reset, sorry for my ignorance wonder why ?
[Xoom Android Development] bigrushdog:
Because the xoom is now unofficially supported in aosp and we've had to do some hacking around to get things working. Also getting gapps right has been trial and error because Google is no longer publishing non neon gapps, which is what xoom uses.
[Xoom Android Development] scottgti:
Not a factory reset. Wipe system. Flash ROM. Flash gapps. Reboot.
[Xoom Android Development] trancoss2:
but to do a wipe systen not erased all systen wipe after flashing the gapps plus I have to re-flash the ROM and install apps.?
[Xoom Android Development] gibbs1984:
Anyone else able to use Pokerstars?

I've reinstalled my backup .apk and also installed from a new .apk but I still get the following message:
[Xoom Android Development] gibbs1984:
Also, what values do you have your CPU set at?

I'm currently on minimum of 760MHz and 1600MHz.

What does everyone else use that is stable and smooth?
[Xoom Android Development] runandhide05:
I do not understand what you are trying to say,

Here step by step.

Download this http://db.tt/o62DmDSy

And the latest ROM.

Place both zips anywhere u will remember.

Reboot into recovery.

if TWRP go to wipe and select wipe system ( system do not include any of your third party apps or data)

Now back to home screen of twrp and click install, select the ROM zip, then add another and select the gapps I linked above. Now select install, after it is complete select reboot.

If cwm recovery select format, then format the system.

Then select install, install ROM , then install gapps.

Reboot and profit. All your data and apps will still be there.
[Xoom Android Development] trancoss2:
Thanks man. ?
[Xoom Android Development] :
I can use it, i installed it from the market w/out backup