yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] gibbs1984:
Ah yeah, never used to be in the Play Store in the UK maybe that's why my .apk from the net isn't working anymore, the one from the Play Store is now working, cheers :)
[Xoom Android Development] NissanNick:
This is a awesome rom... but will tthe battery life ever be good again or are we out of luck with jb.
[Xoom Android Development] lepa71:
Would I follow the same steps if I'm coming from dreamcwli's JB 4.2?

Thanks
[Xoom Android Development] trancoss2:
with these gapps the keyboard fails, some solution.
[Xoom Android Development] mutiny:
My battery life is awesome. In fact, it puts my TF201 with CM10.1 to shame.
[Xoom Android Development] drewski_1:
Works for me. Maybe a log would help?

Edit: I'm using 1/4 gapps. Looks like that link is a newer 1/5. Not sure if that will help
[Xoom Android Development] rob62551:
+1

Typing on keyboard now.
[Xoom Android Development] trancoss2:
I fail with the new gapps, is there any solution or gapps back to Day 4
[Xoom Android Development] liftman-:
thumb keyboard is the way to fly on a tablet:fingers-crossed:
[Xoom Android Development] drewski_1:
Search for runandhide05's posts. You'll find the link to the 1/4 gapps.

---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------

I'm liking the SwiftKey Flow beta. Thumb is nice too.
[Xoom Android Development] trancoss2:
Thanks, I have the link of gapps day 4 but wanted to know if there is any solution for gapps day 5 for being more current.
[Xoom Android Development] runandhide05:
just read some posts dude. I've said it several time. And I'm not going to say it again.

Have a great day

- fix chrome FC when accessing settings

- fixed gesture type

from timduru

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

+ Auto-correction off

+ Show correction suggestions:always hide

* ( see note below) we had two options, NOT include Googles new swype to type gesture input keyboard or include it, since the point of being on the bleeding edge is to have all the cool ****, we sometimes have to compromise, Google is not supporting non neon deices anymore ( the xoom) so the libs ( think of those as drivers ) are not going to work properly with our tablet, therefore causing not everything to work perfect.

As many have said here, using a different keyboard is the best thing to do, as most third party apps will work better that what google has given us.

* Note

Think of libs as drivers, And think of Android as windows for a moment, and let me put this Super simple.

The xoom is a 386p ( for those that dont know what that is google it)

and honecomb 3.x is Windows 3.1, ( google that too if you dont know what that is)

At some time the most current OS version will just NOT work on a device,

So think of it when Windows XP came out, Sure you could technically put it on the old 386, did it work? Again, technically yes. Was it slow, unreliable? Yes, again, But people did it, When windows7 came out do you think people put it on that same machine? No at that time there was no technical way to do it, XP ran on it, but slow, not well, and the performance was that of a snail.

The point I am making here is We are on XP right now, and the next OS is likely to be the end of the Xoom ( does 4.2 JellyBean work? Technically yes, Is it without issue? NO )

But we all like being on the Bleeding Edge, and We all should now know what that comes with,

[/end rant]
[Xoom Android Development] playya:
Well said in the above statement... You want newer purchase new, if not stop complaining about stuff that was in reality not made for your device...
[Xoom Android Development] petrossa:
I'd not put much effort in making google stuff work. There are so many 3rd party apps that work fine and usually better. Just the basic Os with the absolute minimum necessary to setup your device. I delete most anyway with root uninstaller
[Xoom Android Development] vicky4112:
How to check which gapps file is uploaded

After flashing many times, I am now lost . I can check the nightly version for ROM.

Where can I check the gapps file I used during install?

Sorry if this is a stupid question.;)
[Xoom Android Development] i_am_the_one:
I have a quick question for everyone. When ever I reboot my xoom, it shuts off completely. And then it takes quite some effort just to get it to turn back on, but once I do it works fine and continues what it was doing. So say when I reboot to recovery it will shut off, then 20 minutes of hitting the power or up+power will get it on, and it will continue into recovery. After flashing an update and rebooting same thing. Once it starts just continues the boot. Has anyone ever experienced this? Is there a possible fix? I just hope my xoom isn't dying.
[Xoom Android Development] siscim23:
If you haven't downloaded any since you installed, just look wherever you put the zip when you installed it.
[Xoom Android Development] logitechor:
Hi Runandhide

Thank you for your latest post. I love the work the developers are doing. My first 386 was bought in about1989. Modifying computers began quite awhile ago. If not for people such as yourself much of my hardware would have died a quicker death over the years. I can follow instructions and search for dolutions but am not a programmer.

Bleeding edge is part of it but also increased lifespan and use. With the limitations know. Google has a perfectly fine operating system for the Xoom. This isbetter. Much appreciated.
[Xoom Android Development] petrossa:
My very first 'screenflash' on 155. Same with as 4.2. Weird
[Xoom Android Development] iruiz2:
Well, it took a while but I finally decided to migrate to 4.2. Fells very smooth, THANK YOU Team Eos.

I took the time to update Backtrack 5 support for this version of the OS, in case anyone is interested: http://xdaforums.com/showthread.php?t=2006372

Long live to BT5 on the Xoom!!
[Xoom Android Development] FormerPalmOS:
Folks,

If you want a really kick-ass touch response, check out these two threads:

Summary - using your favorite overclocker (I use SetCPU), find your max speed (I use 1600), set the Interactive Governer, set Input Boost to 1. You can play with the other settings - but input boost is the biggie - jumps to the highspeed setting immediately upon touch input instead of waiting for the load to be high enough to trigger the boost. I use 1000000 for hispeed, 80% for the go highspeed load, 10000 for the above highspeed delay, 40000 for the minimum sample time to ramp down, 20000 for the ramp up timer.

One caveat - if you do a lot of typing, this will hammer your battery because every time you touch a letter the governer will ramp the CPU to the highspeed speed. If you do a lot of typing, you might want to not set input boost, or you might want to find a lower highspeed setting.

http://layer8problem.wordpress.com/2012/10/01/interactive-governor-settings/

http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak

You can also use SetCPU to set-up profiles. I use one to reduce the maximum CPU speed to 608 whenever the screen is off. Interactive might do this already - never checked.
[Xoom Android Development] petrossa:
This makes it scream, wow :beer:
[Xoom Android Development] bigrushdog:
Very interesting
[Xoom Android Development] Taysider:
Thanks runandhide05 for a really good post, enjoyed reading it. I can imagine at times you and the other guys at TeamEOS not forgetting BRD felt as though you were banging heads against the wall. But you've achieved tremendous work on the Xoom and I for one thank you for your hard work. There comes a point when you can only do so much to the engine, like a car engine the time comes when you need a new more powerful one. Being a bit selfish I hope the team stay together and when the time comes move to another tablet. Just let us know which one as I for one will buy it. Over the months my confidence in the team has grown, and your ability to push out some great nightlies.

Thanks guys :D:D:D
[Xoom Android Development] runandhide05:
Next device?? Lol eos is on quite a bit of devices all the gnex, n7, tf101 and a few other devices.... I know personally I've been eyeballing the n10... But not sure as of yet...
[Xoom Android Development] EDNYLaw:
Speaking for myself, who came from a Xoom (now it's the girlfriend's), the N10 is simply amazing. CES clearly throws a wrench into everything such as NVIDIA introducing the Tegra 4 with a 72 core GPU but... it's always better in the future. The N10 is truly a great device, even stock (I'm running AOKP with KT Manta kernel) it's smooth. If you end up getting one, I think you'd be very happy, I know I don't regret the purchase for a second. Of course, from the moment I got my GNex, I swore I'd never get anything besides a Nexus device again. :)
[Xoom Android Development] mattwood2000:
Hi guys been away from the forum for a while and I know this is the Wingray thread but whats up with the Stingray nightly - why no separate thread? I just flashed the EOS4 nightly for Stingray and all seems to work fine except Wifi Tether...at least what I've tested.
[Xoom Android Development] bigrushdog:
First one to buy me a n10 gets a personalized eos build and 5 hours of personal one on one android dev training with me :laugh:

Stingray and Everest are going up tonight. and I'm narrowing down the tether issue along with tdr
[Xoom Android Development] EDNYLaw:
When my girlfriend finally finished up med school and I land an actual paying attorney job... :) By then it might be the N10x3, so don't hold your breath. I'm sure I could figure out some kind of tax deduction :laugh:
[Xoom Android Development] liftman-:
yea thats the hot ticket!
[Xoom Android Development] Taysider:
Yes I know but I'm thinking out loud as to when the Xoom comes to the end, the next device that's not out yet
[Xoom Android Development] logitechor:
Using the Set Cpu settings recommended. Seems significantly faster. Sweet with latest Teameos Rom and Gapps. Thank you for the idea.
[Xoom Android Development] bigrushdog:
Ha you'll be paying off student loans till your 80! Next volunteer please.

If we can find some solid middle ground values for this input business maybe I can cook something in.
[Xoom Android Development] runandhide05:
Tax session is right around the corner...
[Xoom Android Development] vicky4112:
Thank you very much. My XOOM is really fast with the recommended set up.

Cheers.
[Xoom Android Development] dj_ghosie:
Nightly 171 arrived!
[Xoom Android Development] scottgti:
So, I fully charged my XOOM. Green led was on. I tapped power button and nothing. I let it sit for 10 minutes and the same happened. I did receive a notification while unresponsive and the notification light flashed. I then forced reboot. The screen was working on reboot, but it was unresponsive to touch. The power menu and volume buttons worked, but no touchy. So, I forced reboot again and went to recovery. On the 6th try it made it through the teamwin screen. Everything looks normal in recovery, but still no touch. Any ideas? Thanks.

Latest nightly, not the latest Gapps, twrp 2.3.2.3

---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------

Of course on the 20th reboot, right after I post that ^^^, it unlocked.
[Xoom Android Development] WarLion:
did you install any rom or just went dark for you or what did you do
[Xoom Android Development] scottgti:
It was working perfectly and i let it sleep. I couldn't wake it, not the first time this has happened to me, reboot has always fixed it. After reboot, touch didn't work on rom or recovery, but screen did. Rebooted many, many times to rom and recovery, and no touch. After I posted, the unlock ring finally worked. I just updated to newest nightly, gapps, and twrp. All seems fine now. Maybe just a rogue app. :confused:
[Xoom Android Development] WarLion:
this sound like a bad screen sorry to heatd that mate
[Xoom Android Development] scottgti:
That's what I thought for about 12 hours. Seems all good now. :thumbup:
[Xoom Android Development] petrossa:
Try clean install without using restore backup and you'll find out
[Xoom Android Development] WarLion:
I had that problem 6 months ago one day my xoom die after seem fix itself send to motorolaand they send me a brand new one
[Xoom Android Development] gibbs1984:
Going to ask a strange question. I know these are nightlies and we don't always get them every night (not moaning at all!) but why when we don't get one the next time we do we miss a number out? I.e. 169 to 171?

Not moaning and just a general observation and obviously it makes no difference to anything and I still get the same awesome performance but have wondered for a while now.

:)
[Xoom Android Development] logitechor:
When you check out the Jenkins build 170 failed.
[Xoom Android Development] gibbs1984:
Ah I see, so it would have been there but something went wrong and it failed?
[Xoom Android Development] Taysider:
171 plus gasps 0105 running smoothly, not 100% sure but it seems to be running faster. ;)
[Xoom Android Development] WarLion:
I'm just came to said the exact same thing lol
[Xoom Android Development] istrait:
Ditto.. I have a rouge app that is slowing me down though that I need to track down...

Is slow until I kill all the running processes once and it speeds up... how to do the tracking though,.........
[Xoom Android Development] alex94kumar:
Cheers to BRD/teameos for a busy day of releasing eos 4 for the rest of our family of Xooms! *high fives*

---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------

kinda late on this, but i do agree with the fact that this helps a lot. never would've thought to set it up this way! This question is directed to Runandhide or BRD, and this may sound like a stupid question, but is is possible to somehow work this setup (as described in the quote) into the rom itself?
[Xoom Android Development] runandhide05:
I'll answer that one.

Simple answer would be no.

Longer answer would be " not everyone's tablet is created equally"

Longest answer not everyones tablet can handle heavy OC. Mine personally can not go over 1500 and is very unstable at anything above 1400, and also doing this would cause a plethora of " my battery sucks" posts.

That said, it would take someone just a few seconds to set that up once and not need to do it anymore.
[Xoom Android Development] drewski_1:
Maybe the over clock, but how about the governor tweaks? I :D
[Xoom Android Development] alex94kumar:
Or maybe have a setting in the System section of Eos Control Panel that says "Boost Touch Input", and apply a light overclock (say 1200 max, or something that will be more universal) as described in the quote? That way users can turn the function on themselves. And that way they won't have to install a 3rd party app. Just a thought
[Xoom Android Development] petrossa:
Poor Teameos:p the more you give them the more they want
[Xoom Android Development] alex94kumar:
Haha, I'm just throwing out a suggestion, even though I expect it to get shot down ;)
[Xoom Android Development] MashBill:
Install SetCPU.
[Xoom Android Development] MARIANOTE:
Downloading 171

Awesome job, not use overclock and fast response
[Xoom Android Development] logitechor:
Thanks for the response. Funny how the Xoom'sare different. Mine is one of the early Canadian models and has handled 1600 stable. Occassional clitches with some Roms. Setcpu has been a program I bought along time ago for my phone. Just now using it with the Xoom. Easy and handles the changes necessary very simply.

Thank you for thegreat Rom.

---------- Post added at 12:51 PM ---------- Previous post was at 12:47 PM ----------

I noticed that in the Teameos Review page a successful merge of CM10.1 and CM10.1 is using Teameos Gapps. I follow both threads and have used both Roms. Thank you.
[Xoom Android Development] vicky4112:
On 171 now. This time did install the nightly and gapps in one session and it worked like a charm. So far quite smooth. I use the SetCPU setting as per an earlier thread.
[Xoom Android Development] alex94kumar:
I have setcpu already
[Xoom Android Development] eddyther:
Hi,

I have setcpu installed, bit I don't see where can I set the Input Boost.

Edited: sorry, I found it!
[Xoom Android Development] tonemand:
Yeah, been doing the nightlies and custom gapps. At some point I noticed general funkiness like sluggishness, etc, but nothing that was a huge detriment to standard usage, but after reading others clearing up minor issues with the wipe of /system, I did the same, and things are smooth and quick, running on stock settings (no tweaks via SetCPU), getting the usual big thumbs-up from me to Team EOS. I'm really digging this ROM! It's been a pleasure having your work proudly displayed on my Xoom since the Hammerhead days.
[Xoom Android Development] vicky4112:
It should be under the governor tab with the rest of the settings.
[Xoom Android Development] petrossa:
If you have the incorrect governer as default you need to reboot first with the new settings else the governer tab won't work
[Xoom Android Development] JohnnyDanger:
Hello all. Decided to try EOS on my Xoom. Im not sure if the issue Im having is a problem, or if Im just not being patient enough. Ive installed EOS and gapps and rebooted. Now I just see the boot animation (the new one) on the screen. Its been like that for 15 minutes or so. Does it just take a long time for the initial boot or did something go wrong? Id appreciate any info.
[Xoom Android Development] petrossa:
Should reboot normally. Did you do a factory reset?
[Xoom Android Development] JohnnyDanger:
I did do a factory reset first. Im installing it from TWRP. There has to be something Im missing, but cant think of what that might be. I restored my previous install and tried installing EOS again, but got the same result.
[Xoom Android Development] gibbs1984:
I'm on 169 so I don't know if it's been fixed in 171 but when taking a video and pressing stop with the red button it works fine but if you touch anywhere else on the screen (say in the centre) then the camera app Force Closes and the video is lost.
[Xoom Android Development] siscim23:
Try going back into recovery and clearing cache and dalvik. If not, do a factory reset and install again.

It does take a long time the first time, but not 15 minutes long
[Xoom Android Development] WarLion:
first redownload the files,

do a factory reset with twrp make sure you are using the last for android 4.2

install eos rom and add gapps the last is 20120105

after install do a wipe cache and dalvik

edit

sorry I lost a year, the gapps is 20130105
[Xoom Android Development] Alxoom33:
Sorry Run, you got a lemon! Most Xoomis Oc at 1600 no problem! :laugh:

I've been at 1600 since honeycomb days. Not bragging, just saying. I believe Steady Hawkins could run consistently at 1700.:cool:
[Xoom Android Development] NWinfuse:
I've never had a problem OCing to 1700 granted I generally don't run over 1600 just for the simple fact that 1600 is fast enough for me and I don't see any reason to tax the system
[Xoom Android Development] drewski_1:
my Xoom reboots after a few minutes on 1700 :(
[Xoom Android Development] Alxoom33:
Unfortunately, mine does the same!:highfive:
[Xoom Android Development] JohnnyDanger:
Got it to install on my xoom. Redownloaded and went through the process again. Worked. Problem Im having now is my xoom seems so sluggish at times. For example, my wife and I play Draw Something. When I took my turn and went to draw, there is a definite lag to drawing. I cant even draw a straight line cause when I move my finger across my screen, the drawing cant keep up with it. Any ideas how to correct something like this?
[Xoom Android Development] runandhide05:
take a look at this,

it seems to help out a lot of peps

http://xdaforums.com/showpost.php?p=36402475&postcount=1032
[Xoom Android Development] themichael:
1700 is bolted the same as 1600 on eos kernel. You might even be better off at 1700 since it can theoretically complete tasks faster and thus less load.

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

How is the launcher lag on the new releases compared to 166
[Xoom Android Development] siscim23:
Not sure about 166, but I went from 165 to 169 and noticed the home screens smooth out a bit.
[Xoom Android Development] alex94kumar:
Launcher lag is a lot better on the newest release. Its actually somewhat manageable. When you apply input boost on setcpu its even better
[Xoom Android Development] scottgti:
172 is out. I'm running @1000. I'm not using setcpu. Everything I use works great, except autocorrect. :D
[Xoom Android Development] kentedman:
anyone notice any dramatic effects on battery life by implementing the input boost tweak?
[Xoom Android Development] petrossa:
Hard to say. It really depends on your typing frequency.
[Xoom Android Development] narako9:
Its been few days now that I get the notification to update through goo manager and when I try to download the file I get download error, going the the Jenkins site directly and clicking on the file gives me the file you requested was not found. Anybody else having this problem?
[Xoom Android Development] logitechor:
Does anyone havealink to thechanges with build 172. Thank youi.
[Xoom Android Development] bigrushdog:
We disabled jenkins download. It's on goo.im.

Check my sig. I'll be linking in the op soon too.
[Xoom Android Development] narako9:
Thank you, didn't know that.
[Xoom Android Development] logitechor:
Perfect. Thanks much.
[Xoom Android Development] DefinityX:
Anyone else notice this? Sounds like an issue with the device taking a picture during video (awesome feature)... Is this one of the non-Neon device bugs we're stuck with?
[Xoom Android Development] gibbs1984:
If I have set a governor and CPU frequencies in the EOS Control Center and also in SetCpu which one will override the other on boot?
[Xoom Android Development] alex94kumar:
That or however much you touch the screen at all on a daily basis
[Xoom Android Development] logitechor:
Very good question. I have had settings not stick very well. Maybe I need to shut off some setting in the Rom and thenuse SetCpu's settings. Will report back.
[Xoom Android Development] alex94kumar:
settings dont stick if you do a vol-up+power button reboot
[Xoom Android Development] :
My keyboard is FC'ing. What can I try to fix it? It has happened since i installed 0105 gapps

Thanks
[Xoom Android Development] runandhide05:
Turn off all auto correct and show suggestions in the settings
[Xoom Android Development] alex94kumar:
Or install Jellybean Keyboard from the play store

I'm using it now in thumb keyboard mode. You can make it look like the stock keyboard also
[Xoom Android Development] Alxoom33:
Love 172, working great! However, still dosen't work on OC'g at 1704. :( Fc'ing, back to 1600. :silly:
[Xoom Android Development] liftman-:
this is difference in chip lots- mine is most stable @1400, runs 1500 ok but doesn't feel smooth, @1600 mine reboots after a few mins.

i keep mine set @1200 for balance of speed and battery performances.

if i was gonna hdmi and leave it plugin i would set it @1400

you have to find your sweet spot and go with it.

some may run smooth @1700 doesn't mean you or i will:cowboy:

another note on overclocking, it produces heat, long team excessive heat will degrade the life of all electrical components!
[Xoom Android Development] Winesnob:
Very few Xoom 's will OC to 1704. Nothing to do with the ROM, has everything to do with the hardware.
[Xoom Android Development] Alxoom33:
Yes, unfortunately. I wonder if over-volting would work?:rolleyes:
[Xoom Android Development] Cm9aphla:
Is there any way I can update this ROM without wiping data
[Xoom Android Development] iruiz2:
If you are running a eos4 jellybean 4.2.1 rom, it shold be enough to wipe cache, dalvik (and system if you want to be thorough), that leaves your data untouched. If you have another rom, not wiping data will probably cause all sorts of problems. Use Titanium...

Sent from my Xoom
[Xoom Android Development] dyskinesia:
Wiping system doesn't mess with data?

Only time I've ever wiped system is with a full wipe and then it was just as an extra just in case I thought.