yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] roger321974:
hello,

i want to know why team eos do not update the changelog in jenkins in new builds?

thx
[Xoom Android Development] FormerPalmOS:
Might be because they have day jobs or families or both?
[Xoom Android Development] scottgti:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I hope they have families and jobs, but I also would love a changelog. :thumbup:
[Xoom Android Development] FormerPalmOS:
No argument there - change log would be welcome.
[Xoom Android Development] iwakpitik:
keyboard issue

Today I was flashing my xoom with the newest teamEOS release, 20130119 - 173.

I have noticed a few times today an unusual behavior of the built-in virtual keyboard on my Xoom with Jelly Bean MR1 When I type text in different apps, the keyboard suddenly and unexpectedly disappears, and text editing mode is terminated.

This premature interruption is triggered at apparently random moments after typing a different amount of text each time (from a couple to a few tens of characters), but approximately after the same amount in the same session. Rebooting the tablet fixed the issue the first time, but had no effect in subsequent instances.

What causes this problem? How can I fix it?
[Xoom Android Development] illyfilly:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Change your keyboards
[Xoom Android Development] iwakpitik:
Can you more specific?
[Xoom Android Development] jase33:
Install a 3rd party keyboard like thumb keyboard or swift key from the play store. go into settings>language & input and enable the keyboard and set it as default.
[Xoom Android Development] iwakpitik:
Thank you for the suggestion...

Now I have Swiftkey 3 for tablet ini my xoom... seem the problem go away...

Tested arround 1000 keystroke and never missed.... :good:
[Xoom Android Development] hochoch:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Google is your friend: http://teameos.org/?page_id=22
[Xoom Android Development] jase33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

172 &173 had been a bit sluggish for me. Apps were loading slow and just didn't feel right. BRD mentioned trying cm kernel. So I wiped system and caches. I replaced the boot image with the one from most current cm 10.1 for the Xoom & reflashed. Now its running like it should. No lag in launcher (using nova), no lag launching apps. I still wonder if there are stagefright issues causing graphics issues in some games but not a real problem for me.
[Xoom Android Development] gesreg:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

1/19/13

Phones

Tuna Series

All - bring back depricated SMS framework fixing Handcent issues

Maguro - update build fingerprint

Toroplus

Update toroplus build fingerprint to official 4.2.1

Bring in official 4.2.1 vendor binaries! Dramatically better battery life, radio performance, gps lock, and fixed drm for Hulu+ yippie!

Tablets

All

Fix clock digit cut on lock screen

Fix annoying Back/Ime button bug when using a hard keyboard

Xoom

Stingray - New activation helper app for clean activation on initial boot

Stingray - Removed activation app in favor of a better framework fix

TF101

Numerous AutoRotate patches fixing a number of pending issues

Nexus 7

Enable CRT screen off animation (I like it better, will make user defined soon)

All

Clean up EosControlCenter icons

Feature - control wifi off timeout when device sleeps

Enable XDA support links in ECC information, disable Rootz link for now

Bring back the Toasts in frameworks non app / services

SystemUI: respect statusbar background for themes

Add config to allow to decrease suggested wallpaper size

Fix Launcher lag with optional overlay config value

Add EOS Daydream into SystemUI. Welcome back Roach! Fling away ;D

Fix Recents Landscape Killall

1/9/13

Phones

Tuna Series

Update device tree

Update Leankernel 5.6exp2-230

Bring in usb-otg support

Update omap3 branch and libhardware branch fixing Tuna gps

Maguro - fix signal strength bug caused by importing Everest code

Tablets

TF101 - Fix system crash when changing dock keyboard layout

Grouper - Update device tree

Bring in usb-otg support

kill long press volume buttons for bug reporter

All

Bring in some cli binaries

iw, libnl, dropbear, powertop, scp, sftp, ssh-keygen, tcpdump

Update some quick settings panel icons

Update broadcom/wlan branch

Misc framework updates from CyanogenMod thanks guys

Yet another attempt to fix APN settings, should work for real now

(LTE devices) new LTE Quick Settings toggle (see, I remembered ;D )

Changelog >> http://code.google.com/p/teameos/wiki/ChangeLog

Hope it helps sir :D
[Xoom Android Development] Alxoom33:
Pretty much same quadrant scores for 173. Still can't oc @1704:p. Also, didn't crash at 1704 with dreamcwli's My Android build.

Strange:confused:
[Xoom Android Development] bigrushdog:
Check my sig for the change log until I overhaul the op's. I was gonna try adding tdr's kernel for testing in this last nightly but I forgot. I'll post a flash zip for testing and one for restore. I hope to get the lag issues resolved soon.
[Xoom Android Development] iruiz2:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

For those of you that (like me) are having some lag, I have discovered that setting the "disable HW overlays" makes my Xoom way much faster. Look for it in the developers options in Settings.

I also found that seeder 1.4.0 speeds somewhat my Xoom (you can doenload it from its xda thread, I'm mobile now so I don't have the link at hand)

On the video reproduction front, I was having some problems playing some series in mp4 h264 format: video was somewhat after the audio, which made it impossible to watch. I tried Mxplayer, Mobo... tweaking all possible setings. At the end Dice player was the solution (in case it happens to anybody)

Sent from my Xoom.
[Xoom Android Development] FormerPalmOS:
OK now I'm motivated to try 173, try turning off HW overlays and the CM10.1 kernel - mix and match - to see how NetFlix works. If/when I get to this I will report back.
[Xoom Android Development] pipesdl:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Is cifs working on eos4 for anyone, I had no issues on 3 but no luck so far on 4.
[Xoom Android Development] dragonstalker:
I can concur. Hw disable adds speed to the mix. But keybord still sucks on 173.
[Xoom Android Development] FormerPalmOS:
Before I threw in the towel on 4.2.1, I was using a free market program CIFS Manager - it worked fine with 172.

Try SmartKeyboardPro - I really like it. There is a trial version but you have to pay for it to get the good one. I found it to be worth it.
[Xoom Android Development] ahmed007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

My wifi never sleeps anyideas why use to work great on EOS 3 and stock 4.2
[Xoom Android Development] bigrushdog:
There are a couple commits in open that should resolve cifs issues, as well as various other fs mount issues.
[Xoom Android Development] FormerPalmOS:
I must be missing something. With my Xoom working fine with EOS3 (4.2 nightly 155), I grabbed boot.img from the cm10.1 zip and flashed it with fastboot boot boot.img. I am stuck in a boot loop at the eos boot animation. I had assumed that the kernel and initrd would be in the boot.img, likely all crushed together with cpio, but either there is a dependency on something else (there aren't any other obvious modules in system/lib/modules in the cm10.1 zip), or my process was incorrect.

Someone did this - cm10.1 kernel with EOS4 nightly. Care to post a quick how-to? Or did you find it not worth it so you went back to the kernel in the EOS4 nightly? I don't care about quadrant or benchmark scores, but if there is indeed a faster kernel I would use it.

---------- Post added at 09:05 AM ---------- Previous post was at 09:03 AM ----------

What I posted was wrong. Sorry about that. CIFS Manager was working on 4.2 (not 4.2.1) - EOS3 (not EOS4) nightly 155. It did not work on 169 or 172.
[Xoom Android Development] jase33:
That was me - I replaced boot.img in the .zip of the rom and reflashed. I am still using CM 10.1 kernel with EOS4 173. Runs much better for me.
[Xoom Android Development] scottgti:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I tried that yesterday and got "Failed" when I tried to flash. Any other tips? :)
[Xoom Android Development] drewski_1:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

EOS3 was 4.1, not 4.2

Maybe try a CM10 kernel, not 10.1?
[Xoom Android Development] jase33:
I used this boot.img. It is a CM10.1 for Xoom kernel. I wiped system, cache & dalvik.
[Xoom Android Development] FormerPalmOS:
I assumed (potentially mistakenly) that the kernel hadn't changed from 4.2 to 4.2.1. Now that I have EOS4 nightly 173 up and running with its stock boot.img I will try just the boot.img with fastboot again. Any reason that shouldnt work? Wish I had thought about just replacing it in the zip. Much easier.

NetFlix ran fine for about 30 minutes with HW overlays disabled. Need time to do a bigger test.
[Xoom Android Development] gibbs1984:
Is Goo down for anyone else?

I'm getting a "Server Offline. Please hang tight while we get this resolved.".
[Xoom Android Development] davidmcw:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Same here.
[Xoom Android Development] pkelly517:
Re: flashing new gapps with 4.1.

I can't find exactly what you did to get Hotword detection working for the new Google Now/Search. I recall seeing somewhere that it had to do with renaming one of the neon libs.

If I wanted to make the same fix for 4.1,(everything running, Hotword disabled), what would it take? My XP xoom just can't handle Aero. It needs some 4.1 again.

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

https://plus.google.com/app/plus/x/...eeded&aid=z13fxzgqaojwcxjri04cizbawsjjc554e50
[Xoom Android Development] pkelly517:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Thanks, but I guess I'm just not reading the post correctly.

I renamed the lib. Enable Hotword, crash.

I copied in the lib from the xoom gapps, crash.

I used both names for the lib. Crash.

Rebooted, all ways, crash.

Hotword disabled, all good.

Edit: logcat tells me what I thought I knew. Call the lib, crash.
[Xoom Android Development] runandhide05:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

What lib are you renaming ( ie /system/lib/) if so that's the wrong one if you are using 412.

Say you have 4.1.2 installed and u used the gapps for 4.1.x it would have an older version of Google search, so you would be prompted to update. Which you do, and now the apk is in the data/app and the lib now being used is at /data/app-lib or at ... ( see pic)

so find that and replace it with one from the 4.2.1 Xoom only gapps
[Xoom Android Development] gorcutt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Some feedback from my side:

After being abandoned for a while with a touch problem I decided to give it one more chance and my Xoom checked in at the Motorola Assistance next door for a new what they call "lens" (strange name for the touch screen).

CM10.1 and EOS 4 were my choices and I ended with EOS 4 for several reasons, not the subject of this post:

1. Notice my tablet with a huge lag issue. Still investigating if this was caused by some installed program. I want to make an observation here. I received the Xoom from Motorola with ICS and of course unrooted. The tablet was very smooth with the stock firmware and after rooting it I start noticing a huge lag even with the original ROM that came on it from the Assistance. Any thoughts?

2. Theme provider and Theme chooser always closing. As I don't use themes I just uninstalled and had no problem on any users (3, wife daughter and myself).

3. EOS Settings closing if I change the tablet orientation while on that screen.

4. Go back to Obs 1, the most annoying of all.

5. radio working great MZ601, Everest here, brazilian GSM.

6. HD shooting and playing with no issues.

7. Angry birds running very smooth ;)

This is a 12 hour non tech use based observation only, so not much else to say. I feel this rom is going strong on the right way so I'm sticking with it.

EDIT: WRONG FORUM. This should have been posted on the 3G forum. Sorry for that!
[Xoom Android Development] pkelly517:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Yeah, funny how that's the exact path that the logcat pointed at, but I still tried /system/lib.

Thanks for helping those more idiot than you. :)
[Xoom Android Development] simonbarsinistr:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

The way you keep repeating this makes it look like you think eos3 was 4.2, it is 4.1.2, so you would need a cm10 kernel. Eos4 is 4.2.1, and thus you would use a cm10.1 kernel. Apparently there's enough difference in 4.1.2 and 4.2.1 to cause your eos3 running xoom to bootloop while trying to use a cm10.1 kernel.

Now that you're running 173, trying the cm10.1 kernel should work fine.
[Xoom Android Development] bigrushdog:
Ok lemme see if this helps some.

CM10.1 kernel with Eos ramdisk

Restore Eos kernel

my buddies from TeamRogue gave me the go-ahead to use this and see if we can troubleshoot the lag.

Flash the cm zip. Run some benchmarks.

Flash the eos restore. Run some benchmarks

Report back. I want benchmarks. Not "oh meh this feels better!" I want numbers! thx :cowboy::p:silly::laugh::highfive:
[Xoom Android Development] jase33:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Ran three tests in linpack and three tests in quadrant. Below is the average of the three for each kernel.

CM kernel - Performance Gov.

@1504 - Linpack - 31.86 Quadrant - 2656

@1600 - Linpack - 33.29 Quadrant - 2710

@1700 - Linpack - 35.11 Quadrant - causes reboot

EOS Stock kernel - Performance Gov.

@1504 - Linpack - 25.47 Quandrant - 2582

@1600 - Linpack - 27.55 Quadrant - 2619

@1700 - Linpack - 28.68 Quadrant - causes reboot
[Xoom Android Development] russtyd:
SETCPU benchmarks (each average of 3 runs)

1st Run EOS Kernel @ 1504 - Short 931ms, Long 3932ms, Native 5342ms

CM10.1 Kernel @ 1504 - Short 125ms, Long 474ms, Native 605ms

Edit:

2nd Run EOS Kernel @ 1504 - Short 115ms, Long 474ms, Native 630ms

I did a re-flash of EOS Kernel and repeated the tests, and the results were almost identical to CM10.1 ... not sure what happened with the first run but the results look way off and guess should be ignored....
[Xoom Android Development] Alxoom33:
Sorry, No numbers, the cm10.1 kernel made my wingray unstable. Kept reebooting. Could never finish a benchmark. What about dreamcwali's kernel. I was able to run that Rom all day OCd at 1704.

Oh meh this does not feel any better;)
[Xoom Android Development] FormerPalmOS:
I'm just being too short with my posts. I meant to say I (stupidly) didn't think about a kernel difference between 4.1.2 (EOS3) and 4.2.1 (CM10.1). Just didn't type what I meant to say (substituted 4.2 for 4.1.2 in my post).

Anyway, I have EOS4 nightly 173 running with the unmodified boot.img from the CM10.1 zip. Which leads me to...

BRD - Other than the kernel, what is in the EOS initrd that is different from the CM10.1 initrd? default.prop (and other stuff)? Is there enough of (or important enough of) a difference I should flash the above if what I have (unmodified CM10.1 boot disk) is working?
[Xoom Android Development] bigrushdog:
No that's just fine. just minor irrelevant stuff.
[Xoom Android Development] emaxxim:
The kernel you posted doesn't work in my device (I have the MZ601, with WiFi and 3G), I can't boot the device with the kernel proposed from you. Maybe is only for me. But if I can I want to help you.
[Xoom Android Development] FormerPalmOS:
Same / worse problem here.

1) Working 173 nightly with EOS kernel / boot.img -> fastboot flash boot boot.img from cm10.1

Boot loop, system dying after EOS bootanimation starts.

2) Wipe Dalvik and cache after the above

No change

3) Wipe data, install test kernel from BRD

Boot loop, system dying during or after upgrading / optimizing. Some times makes it to lock screen then SystemUI force closes. Sometimes even makes it to initial set-up.

4) Make new zip with 173 nightly, remove stock boot.img, replace with BRD test boot.img, flash gapps

Same behavior as 3

5) Flash unmodified 173 nightly then BRD test zip, then gapps

Same behavior as 3

6) Flash unmodified 173 then gapps

Returned to normal

I did notice that the lag on the Android keyboard we have gotten used to with the EOS kernel is not there with the cm10.1 kernel, the one time I was able to start the initial set-up process.
[Xoom Android Development] Alxoom33:
Would they work on the Bionic?
[Xoom Android Development] russtyd:
Errrm, this is the MZ604 section..... could explain why it doesn't work on your MZ601s.... :silly:
[Xoom Android Development] scottgti:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

BRD steered the other threads here to download.
[Xoom Android Development] FormerPalmOS:
I missed that the quoted post was an MZ601 - but the kernel / initrd that BRD posted sent my MZ604 into the weeds - see a few posts back.
[Xoom Android Development] Cm9aphla:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I there any way I can return to regular tablet ui in this ROM
[Xoom Android Development] drewski_1:
no. you can get the nav buttons into the lower left, but the status & notifications will stay on top.
[Xoom Android Development] Cm9aphla:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

That sucks I hope thats something that they can implement in the next update.
[Xoom Android Development] drewski_1:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I think they said it wouldn't happen because of Google changes in 4.2
[Xoom Android Development] kentedman:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Im not trying to be a jerk. Serious question. If you like the layout of 4.1 better then why not just flash back to 4.1? The biggest advantages to 4.2 besides the new layout are photosphere, keyboard, and multiple users. All of which are all buggy at best.
[Xoom Android Development] alex94kumar:
dreamcwli has original tablet UI enabled on his ROM. However, his rom has less features than Eos4. It's blazing fast though
[Xoom Android Development] khanh1289:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I can't for the life of me flash the kernel.. those who are successful must have done something special.. or device specific maybe? I'm on twrp, does that matter?
[Xoom Android Development] liftman-:
in eos settings you can shrink the bottom bar, i used to hate the top bar till i shrank the bottom bar, no i love it on my n7:p
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I am of the opposite religion. It's a UI design fault I hope google will rectify one day :mad:

Sent from my Xoom
[Xoom Android Development] hochoch:
anyone brave enough to try this lagfix app yet? http://www.androidpolice.com/2013/0...agfix-aims-to-make-it-perform-like-new-again/
[Xoom Android Development] FormerPalmOS:
Unless the app includes the fstrim utility, it won't work on this ROM. And I question if it will work at all - the Xoom is old enough that the eMMC device used for /data and /cache might not support the operation. But at the end of the day, if your /data and /cache partitions have lots of empty space, even if this did work, it wouldn't likely make a noticable difference.
[Xoom Android Development] ahmed007:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I did install it and uninstalled didn't notice any change at all
[Xoom Android Development] hipocrazy:
Tried it on both my Nexus One (Evervolv 4.2) and my Xoom (Eos 4.2). No difference on Xoom, Noticeable difference on Nexus One.
[Xoom Android Development] droid75:
Awesome job with this rom. Question though, how can I disable auto-rotate screen? I can't seem to find those settings anywhere. Usually they are in the display section. Thanks.
[Xoom Android Development] Alxoom33:
Go to Settings /Accessibility there is an auto rotate screen checkbox.
[Xoom Android Development] FrankCastle:
Hi everyone.. Firstly thanks to the devs for their best work :)

I have a question re does versions and different Xoom models..I have a Verizon model but use that end I n Australia , hense I have no need or use for the 4g lte. To that end I have been using the wingray version of the rom.. Can this have any adverse effect s on my device?

I ask because recently I have had 3 power chargers die on me.. The latter 2 both purchased recently and dead in very short amount of time...

If anyone has experienced any of the same things and can point me in the right direction it would be highly appreciated!
[Xoom Android Development] vicky4112:
FrankCastle:

I have a verrizon 4G/LTE Xoom - stingray. But I am not using any of the services and basically using it as a WiFi version. So I have used Wingray Roms from the beginning and so far have not had any issues with power chargers.
[Xoom Android Development] petrossa:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I can't imagine a way how a Rom could damage a power charger without frying your logic board first.

Sent from my Xoom
[Xoom Android Development] liftman-:
my xoom was stolen last week and have some stuff i do not need.

i have a car charger and a house dock i do not need. if any one of the TEAM EOS members want them send me a pm and ill have the wife ship them out.

if no member of teameos wants them, then it will go to a xda member that has help out alot in the teameos threads!

the insurance company gave me a xyboard, nice unit but not alot of development going on. which is OK for a few weeks, I'm getting a nexus 10. my contract is up for my 4g with verizon in march:)
[Xoom Android Development] jokage:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Hmmmm where is the option for Screenshots? Or is there a hardware button combination?
[Xoom Android Development] alex94kumar:
The default screenshot combination is Power Button + Volume Down. If you go into softkey settings in the Eos Control Center, you can set a long-press on any of the softkeys to take a screenshot, also. I find the second option easier
[Xoom Android Development] paultbear:
I've run into similiar problems with the 12 volt supplies for the xoom... not the motorola ones. (Some other equipment supplies as well) . but the 'less costly' after market ones.

One melted, and another overheated to the point of failure.

I salvaged the ends and modified some heavy duty 1.5 amp 12 volt supplies with them.. and had no further problems.

I think that the draw when charging the Xoom requires an honest 1.5 amps and the low end supplies don't have it. Either that or they are just built cheaply with questionable components.

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

I've hooked my Xooms up to an old PSU. Nice stable current and ample power

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

Everyone experiencing lag, have they tried the unchecking background sync in Google Currents.

It's been around for a while as a fix for 4.2 but only just remembered about it.

I think my Xoom is smoother now but not really sure if it's a placebo effect or not...