yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] drewski_1:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

SwiftKey :D
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I love thumb keyboard, the layout craps on swiftkey in my opinion. Swiftkey was trying to catch up to it in latest beta or final? last couple weeks but arrow keys and 'extras' that thumb keyboard do are still 100 times better only view :)

Each to their own view naturally of course!
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Thumb keyboard fully functional in SwiftKey

Sent from my Xoom
[Xoom Android Development] FormerPalmOS:
More on NetFlix - for developers

For the TeamEOS Developers...

NetFlix is still locking up on nightly 175 (TeamEOS kernel) even with Disable HW Overlays set (reset after boot since it isn't persistent). Here's a bit more info, though no smoking gun...

The OpenGL ES Renderer is throwing a series of 0x505 errors (out of memory). This doesn't happen (watching a live logcat) until I start NetFlix. I enabled tracing the call stack for OpenGL glGetError. The call stack (abbreviated) includes:

glDrawArrays in /data/eos-lib/libEGL.so

/data/eos-lib/libhwui.so

/data/eos-lib/libandroid-runtime.so

/data/eos-lib/libdvm.so

dvmPlatformInvoke

dvmCallJNIMethod

dvmInterpret

dvmInvokeMethod

dvmInterpret

dvmCallMethodV

/data/eos-lib/libandroid-runtime.so

android::AndroidRuntime::Start

/system/bin/app_process

/data/eos-lib/libc.so (__libc_init+35)

However these out of memory errors happen right when the player starts then they don't happen again. They don't happen when it locks up. So I don't know if this information is at all helpful.

For grins, I tried changing the build.prop OpenGL ES version to 1.1 but that didn't make a difference - still locks up.

However, the lock-up does seem to happen around the same time as a warning from ThrottleService - unable to find stats for iface rmnet0. That warning happens periodically even when NetFlix isn't running. So again, I don't know if there is any connection.

Also noticed in logcat, but likely unrelated (unless network errors are behind the NetFlix issues) during boot a warning is being generated about the net interface command library not being found (/system/lib/libnetcmdiface.so). Did you guys leave this out of your build - intentionally or otherwise?

If anyone has working NetFlix on 175, please report the NetFlix app version number. And, have you gone onto your NetFlix account (on a PC) and changed your bandwidth / video quality settings or have you left them default?

Wife is pushing again for a revert to nightly 155 (last one that has worked consistently)...
[Xoom Android Development] redhairedscot:
TL;DR: No crashes here

I flashed this morning (EOS JOP40D Nightly 175), and due to a bad case of the flu (and the new Futurama episodes), I've spent all day flat on my back watching Netflix on my xoom. I'm running Netflix 2.1.2 build 787, and I did a full factory reset/wipe cache/wipe dalvik cache, since I hadn't flashed in a while and nothing better to do. (I hadn't flashed it long enough that I just today had to look up the solution to the new "OMG KBD BROKE" error.)

I'm overclocked to 1504MHz, and I have had no crashes all day, and I've been doing netflix, youtube, and internet.. I haven't changed any quality settings on the netflix site, but I have noticed that the quality varies quite a bit.

The only performance options I've checked in the EOS control panel settings are the animation transitions, which I have set to 0.5x.

I'm not very experienced at debugging, but I'm willing to post debugging logs if you think a differential diagnosis between (working)/(not working) would be helpful. I may need to read a few FAQs first though. (Also, like I said, I have the flu, so I'm only intermittently conscious.)
[Xoom Android Development] xda_biscuits:
Thanks for clearing that up Waz675. :good:
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I might see if my old.purchase allows new swiftkey. I installed a beta (afaik) not too long ago. But I will see how it is (for xoom and n7)

Always good to have choice :D

Cheers for mentioning functionality, pegged my interest again.
[Xoom Android Development] FormerPalmOS:
I have nearly the same set-up (NetFlix 2.1.2 build 787, animations at 0.5x). I OC to 1600 MHz and I have the lock-up regardless of the Disable HW Overlays setting.

Thanks for the offer for logs - I don't think it will help - but I hope you feel better. I'm really starting to wonder if it is a network issue (packet loss or order or something) that for some reason is handled better on the previous OS version (nightly 155 didn't lock-up, same home WiFi network). And if it weren't for the fact that others have this working, I would also throw in the towel since our Xooms don't have NEON and aren't officially even supposed to work with 4.2.
[Xoom Android Development] dyskinesia:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

EOS control center crashing for me on 176

Wiped cache davlik and fixed permissions
[Xoom Android Development] hochoch:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Ditto on control center. I saw that it was added as an app. Tried clearing the data/cache from it but no luck.

edit - 177 flashed and all is good - thanks TeamEOS!!!!
[Xoom Android Development] isidar:
Not tried Control center,

But 176

OC at 1200 Lagfree ... and the fastest ever ...

Very happy with this :)

C9ngratulations to the team :)
[Xoom Android Development] bigrushdog:
My apologies on the control center derp. New builds with it fixed are up. Sorry guys.
[Xoom Android Development] jimboogly:
BRD the only appologies should be coming from the masses, you and your team have provided life to a device in other ecosystems would have been abandoned as a book end 10months ago. Thank you!

my only regret is not being able to wrap my head around the programming to be part of the team in a useful way.

j
[Xoom Android Development] rob62551:
Thanks

Thanks BRD!

As my Xoom is reaching its 2 year anniversary, I know it runs this great due to the wonderful efforts of Team EOS!
[Xoom Android Development] MARIANOTE:
Working by mistake with latest Gapps (non EOS) from goomanager... only googlemusic crashes, and unninstaled... other stuff very well! OC 1408 with native performance center and no issues! Thanks to all EOS TEAM! EOS RULES!:D
[Xoom Android Development] FormerPalmOS:
Fixed nightly 176 - two hours into a NetFlix movie and no lock-up, just one or two buffering issues. I'm wondering if there were buffering issues before but NetFlix was not handling them properly.

Note - I do not have HW Overlays disabled (just the 0.5x animations as discussed previously) and I have the speed slowed back to 1000 (battery life). Going to try back at 1600. Just to rule out something in the HW that is locking with video because of overclock (though this would be the first thing in almost two years that hasn't worked at 1600).

Anyway - this is good news so-far.
[Xoom Android Development] drewski_1:
cool. glad it looks to be sorted! :good:
[Xoom Android Development] alex94kumar:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Anyone try the new ElementalX kernel on eos4? Does the launcher lag still exist?
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Just when I'm about ready to start celebrating...

I've had several (>5) lock-ups now with 177. By lock-ups I mean full-on freeze requiring the Xoom equivalent of the Windows three finger salute. First thing I tried was getting rid of my undervolting and that didn't help. Then I tried backing the OC back to 1504. Keeping in mind that my OC and UV settings have worked fine for the last year I'm not convinced either is the cause. I cannot attribute any application or usage as a common event though I do suspect the Gyroscope 3D live wallpaper since I recently installed that. I have removed it. Lets see what happens.
[Xoom Android Development] ahmed007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

177 working great so far :thumbup:
[Xoom Android Development] Geeba:
I've just managed to root my Xoom... can I just flash this ROM over the stock kernel? I have no idea how to flash a kernel and was hoping just to be able to use Team EOS ROMs... :confused:
[Xoom Android Development] dsbnz:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Fist thing youd want to check, is which recovery youre using. The first post has links to recommended recoveries.
[Xoom Android Development] Alxoom33:
I personally like TWRP 2.4.1. Works great for 4.2 roms. BTW, 177 working well OC at 1600 with interactive governer. :cool:

BRD, (or other Team Eos membes) would you advise using your 12.16.2012 Neon gapps for the Bionic, or the Goo.im 12.12.2012 gapps posted as compatible with CM 10.1 neon devices?

Are there major differences between the two and are your's based on the 12/12 or the prior goo.im gapps release? I wish EOS would add the Bionic to your roster, even though it has neon and has a locked bootloader (arghhh.....) it is soo similar to the Xoom, it seems that bionic development would be a natural extension

Thanks in advance, sorry for going off topic. :D
[Xoom Android Development] Geeba:
Ahhh cheers - is it ok to use the very latest recovery as they seem to be later than the ones in the first post?
[Xoom Android Development] dsbnz:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I'm using the latest twrp 2.4.1.0. Works great.
[Xoom Android Development] bigrushdog:
In theory those gapps would work on any Neon compatible device. But they are my personal gapps, work great for me, but I don't support them officially in any capacity. But I've been using it for months now, so we'll leave it at that. Don't use them on Xoom. Very bad things will happen. As a team, we decided a while ago to only support devices we own. So if someone wants to add a device to our growing roster, we'll need a maintainer for it. And if anyone has a N4, there's a special goodie hiding on goo.
[Xoom Android Development] Geeba:
Cool ok I've flashed 2.4.1.0 - can I now flash this ROM? I have a UK Xoom thats been GED'd

Do I wipe? can I install on stock kernel etc?
[Xoom Android Development] runandhide05:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Kernel is included in the zip. Do a full wipe ( factory reset ) then install ROM plus gapps from the OP
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Sofar no issues with 177 smooth as silk. I use revolving wallpaper.

Sent from my Xoom
[Xoom Android Development] Taysider:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Goto play store and DL 'goomanager' (GM) which is very good. The gapps zip ends in 20130105. DL the latest ROM which is linked as is the gapps in the first post on this thread, you can also DL it from GM. After GM is installed it will put a folder on your internal memory. Using GM after you have installed the latest zip, 177 GM will let you know when an update is available, then just follow the prompts. There is also tick boxs for clearing cache etc.

Hope this helps :)
[Xoom Android Development] Muffycheeks:
Keyboard still pops out when typing. Especially when using the back key. I have tried the "fix" to no avail and would rather have an older board installed....that works!!!
[Xoom Android Development] Geeba:
Installed it... very nice.... a little laggy if I'm really honest on the main swipe screens, but the only thing that worries me is trying to install some games back on for my son and I get "Package file was not signed correctly" :confused:

Any ideas?
[Xoom Android Development] dyskinesia:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Try a reboot

And possibly a fix permissions

Those usually work for me
[Xoom Android Development] dragonstalker:
What specifically were you trying to install. I have not had any lag issues or problems with installer.
[Xoom Android Development] istrait:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Anyone having issues with the new Google now? Mine closes right after it loads...
[Xoom Android Development] TheMainCat:
No problems that I can see. Google Now opens, show the cards, searches...
[Xoom Android Development] Geeba:
Two reboots fixed it... it was just the usual angry birds etc for the kids... all good thou they have installed ok.

Dont get me wrong, its really nice! and everything (well except XBMC :crying:) seems to be working... but coming straight from a stock GED that was only running at stock CPU speeds, even overclocking this to 1.5Ghz the mains screens just aren't as smooth/buttery as the stock software.... :confused:
[Xoom Android Development] Taysider:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Have you DL'd the latest update this might help
[Xoom Android Development] ahmed007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Disable hot word detection n Google now should work if u have updated to new one
[Xoom Android Development] Geeba:
Just another quick question... should this ROM be able to see FAT32 USB sticks? It mounts fine via my OTG cable but shows the full size of the drive and not the files on it.. :confused:
[Xoom Android Development] gibbs1984:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I get this from time to time when updating apps in the Play Store, restart normally fixes it.
[Xoom Android Development] Taysider:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

All my sticks are fat32 and I see all files
[Xoom Android Development] Alxoom33:
Yes, just checked. Closed immediately.
[Xoom Android Development] runandhide05:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Remember people we had to modify the last Google now to work with hot word detection enabled to work on non neon devices. So as before we clutter the thread with Google now isn't working. Disable hot word detection. And then wait for a fix.
[Xoom Android Development] Geeba:
Is there anything I need to do? my OTG cable works with mouse/keyboard etc...

Astro file manager say no files... FAT and FAT32 sticks all mount..
[Xoom Android Development] ahmed007:
thats what i said as well but people hardly read these days or go back and forth on pages seeking answers to there questions any ways we r all here to help cheers
[Xoom Android Development] istrait:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

ID10T error on my part... I forgot about this.

Thanks
[Xoom Android Development] drewski_1:
+1. immediately closing after App Updated.

EDIT: saw fix. will disable Hotword this evening.
[Xoom Android Development] Alxoom33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

OK, thanks. Done! And it worked:) Thanks runandhide p)
[Xoom Android Development] ahmed007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Is YouTube closing for anyone when try to open cleaned data n all but its not working using 177
[Xoom Android Development] Geeba:
Finding 177 almost unusable... the keyboard keeps disappearing, really bad lag on typing and the home screens... even with an overclock :(
[Xoom Android Development] simonbarsinistr:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

The keyboard has been a known issue with 4.2 fit the xoom, lots of posts in this thread about it. Simplest fix is replacing it with a third party keyboard. Excessive lag doesn't seem to be a problem for all, and with the differences in individual set up, nailing down the cause could be tough. I know people were disabling hardware overlays in developer options with some success in reducing lag.
[Xoom Android Development] Taysider:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

177 for me is working great. Using SwiftKey Flow Beta
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Best keyboard I've ever used is thumb keyboard and noticed it was on sale for $1.something (this week?). Tried latest swiftkey flow and tablet versions and still think they aren't a speck on thumb keyboard, at least on a tablet size real estate
[Xoom Android Development] Taysider:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I'll have to give thumb ago :)
[Xoom Android Development] Geeba:
Love the features of the ROM and appreciate the work gone into it but I really need a daily driver... coming straight from stock I'm just not sure on it....
[Xoom Android Development] FormerPalmOS:
By definition, Jelly Bean (Android 4.2.1) is NOT SUPPORTED on the Xoom since the Xoom's Tegra 2 doesn't support the ARM NEON SIMD extensions, which are used in the code base. Therefore the ROM and Google Apps for this device are by necessity a hack job (a damn fine one - props to the EOS team). If you want a supported device running a supported release of the OS, but with the features and quality the Team EOS team is known for, try their Ice Cream Sandwich (Android 4.1) release, nightly 155 (the last one). It was very stable, certainly good enough to be a daily driver, and with the Android 4.1 OS flag you will never accidentally end up with an unsupported application.
[Xoom Android Development] Mrenoux:
177 working flawlessly, Swype beta.
[Xoom Android Development] gibbs1984:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I used Thumb keyboard on my Xoom for nearly 2 years but recently switches to SwiftKey cause its predictive text is a millions times better but its features and layout aren't as good, wish they would combine the two!
[Xoom Android Development] kmcrane:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Lol! I couldn't have said it any better myself! I bought thumb, but only beta test SwiftKey...
[Xoom Android Development] ahmed007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

OK reinstalled YouTube n its working now
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Yeah I would love a combination but I can't say I find the predictions any different on thumb vs swiftkey. They both spit out the words I am typing most of the time. Might be the content, but for me I can't find any difficulty finding words to predict.

Do you use auto correction or predicted words up that you can use at your leisure? I use the predicted text that you pick words appearing up top and pretty much every word was up top to use if I wanted it.

I just find that thumb having all keyboard characters at my finger tips for the most is so damn handy. Swiftkey for me is too many presses to find non alphabetic letters/characters. Horses for courses naturally :)
[Xoom Android Development] drewski_1:
In addition to current word auto-completion, Swiftkey does prediction of the next word after you finish the current one.
[Xoom Android Development] sindamc:
Ups wrong topic
[Xoom Android Development] FormerPalmOS:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Well, spoke too soon. Another lock-up. So we are abandoning Jelly Bean and going back to ICS. Too bad - the multi-user capability was almost like having two tablets.
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Damn, always bad when you have deal breaker bug(s). Sorry to hear that. Still, beats my issue, I can't use my xoom now. Kids spilt a drink, presuming water on it a couple weeks ago. It won't boot without being on my dock and powered on. Also switches off if the power is disconnected.

Since I use my devices so I'm mobile, needing to be on power defeats that. I'd take ics rather than on power all the time. And far as I can tell, it wasn't much drink since we don't fill their cups that much. I wasn't here at the time so can't verify that exactly on amount.

Hope to find one cheap though. Wanting to find someone who thinks the xoom is too old to be cool heh (touches nose. We know a little different huh)
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Should you want to get rid of it pm me, all my Xooms are permanently on dock

Sent from my Xoom
[Xoom Android Development] Geeba:
Wasn't android 4.1.1 that google released for the xoom Jelly bean? :confused:

I wonder how far Team EOS will be able to push the 4.2.x stuff on the Xoom with the NEON issues... could it be time for the Xoom to grace ebay! :eek:
[Xoom Android Development] FormerPalmOS:
Hmmm, according to Android revision history, you are correct. Starting at 4.1 (API level 16) it was Jelly Bean. So to correct my post, starting with API level 17 (JB 4.2.0) NEON is supported which means the XOOM isn't - officially - unless you have friends in the development community :)

For waz675 who's Xoom went for a swim (albeit a pretty shallow one), I recommend DontLetMyKidsAnywhereNearMyStuff.apk - works wonders. If you are really adventerous, you can disassemble the Xoom, thoroughly clean the circuit board and charging / USB / dock connectors anywhere you see evidence of something other than water having intruded (use only deionized or distilled water), dry it thoroughly (but gently) with compressed air, then let it air dry some more to be absolutely sure there is no water left, and see how it goes.
[Xoom Android Development] Alxoom33:
Sorry guys, still love my Xoom wingray. Holds it's charge all day, runs 177 flawlessly with no fcs. Been ocg at 1600 forever weigh interactive governor and profiles for overheating and low battery using android oc. May be untreated in selling at some point. Pm me and we can keep in touch if/when we have a mutual intrest.
[Xoom Android Development] waz675:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Yahoo I know about taking components apart to clean etc. Was a hardware and software hacker for over 20 years closer to 30. Coded my first game about 33 years ago but a severe injury from nerve damage trauma 7 years ago basically has killed my right arm and shoulder. Chronic pain and loss of movement has seen to it I can't work in my career of a Unix admin.

Memory and not being able to handle screwdriver etc properly is severely impacted and also a reason I let the kids use my xoom and other various devices as it helps me not having to gimp chase them around the house.

Or else I would have been an OK developer on here heh. Used to crack PC games and apps in 90s and kernel hacking on Linux as using it since pre 1.0 kernel but as mentioned with memory I lost probably 95% of coding skills/memory. Being stuck in hospital and home screaming from nerve damage until it got managed OK saw to that.

OK sorry for off topic talk. 3yr old woke me after 3 or 4 he's sleep as she wanted us for comfort. Can't get back to sleep while daughter sleeping next to me and wifey just left at 5:30am to goto fitness class. Booooored heh
[Xoom Android Development] bigrushdog:
I think the root of this is that simply Tegra is junk silicon. They may have got lucky with Tegra 3 on N7 but their over promises and inconsistent chips is why Nvidia is in the crapper. Just my humble opinion :p