yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] runandhide05:
Sorry, your absolutely right. A keyboard a few beers and no way to stop my ranting fingers/thoughts will often lead to a few incorrect statements.

Yes every commit must be verified. But I think what I was trying to say was that once a nightly has been built(and I could be 100% wrong) that the team is not necessarily run the nightly for days before releasing it so there is a possibility that some things may slip through the cracks. But again I could and may very well be 100% wrong and I'll be the first to admit it.

Also thanks kcrudup for all you do for the Xoom and for the continued support and absolutely awesome work in the android community as a whole
[Xoom Android Development] mikejs78:
And Apple when it comes to maps...
[Xoom Android Development] kcrudup:
... which does happen, sure. And there's definitely (a huge) value in having user feedback, as you guys will put us through things we might have never thought about trying.
[Xoom Android Development] pkelly517:
I wonder if it was the CM10 commit that was squashed.

Regardless, downloading now.
[Xoom Android Development] dkahs23:
There is still a lag in typing compared to the stable. I just tried 153 coming from stable 3 and the typing is slow. On the stable its right on.
[Xoom Android Development] WarLion:
+1

second that

Enviado desde mi Xoom usando Tapatalk 2
[Xoom Android Development] Muffycheeks:
No problem.... with typing, it's just as fast as I touch the keys.
[Xoom Android Development] dkahs23:
Its strange how it varies from tablet to tablet.
[Xoom Android Development] russtyd:
+1 :good:
[Xoom Android Development] mylegiscramped:
I also noticed a little lag in typing, but it wasn't terrible
[Xoom Android Development] eddyther:
I also have a big lag when typing.

Going back once more to 146...
[Xoom Android Development] mylegiscramped:
scratch that, things seem fine now. Maybe it was just incidental. Things seem pretty smooth now. Could have just been the app I was using at the time as well, but I don't remember what app now anyway.
[Xoom Android Development] WarLion:
i usa thumb keyboard and there is lag but is much better than early bersion anyway i like the modification oon 4.1.2 but im not able to extend the notifications with one finger anyone knows if is inplemented??

Enviado desde mi Xoom usando Tapatalk 2
[Xoom Android Development] emreng:
i noticed something today; if you make the statusbar hidden via power menu, you have laggy transitions between homescreens. anyone can confirm that over #153?
[Xoom Android Development] petrossa:
Still no lag whatsoever, typing as fast as I touch the screen. Tried several loads to see if I could get it laggy, no luck. How many people with lag have tried factory reset, then with standard launcher and no other apps installed?
[Xoom Android Development] MARIANOTE:
153 fast and smooth no delays! Thanks to all the EOS team!:good:
[Xoom Android Development] orb_526:
Honestly, I don't know if it build 153 or the latest beta 2 Apex launcher but my Xoom is super buttery today! Loving it... Thanks!
[Xoom Android Development] eddyther:
I didn't reset but I went back to 146 and the lag disappeared.
[Xoom Android Development] musashiken:
I'm one of them. I even skipped setting up my Xoom and went straight to the homescreen after a quadruple full wipe, wipe cache and dalvik and flash rom.

The 153 rom is better than the post 146 nightlies, but there's some reduced touch sensitivity especially with typing. Sometimes the homescreen is smooth but once in every few swipes, there's some stuttering like the cpu is struggling. Typing is pretty laggy though.
[Xoom Android Development] hipocrazy:
153 smooooth!!
[Xoom Android Development] golfdiesel:
Sorry that it took this long but I fanally had the time to test this build. I flashed test build 2 over build 1 and the lag is back.

The lag seems to be introduced in the changes between 146 and test build 2.

Test build 1 is perfectly smooth.

Verstuurd van mijn Xoom met Tapatalk
[Xoom Android Development] dkahs23:
Nice reply kcrudup. That make a tremendous amount of sense. Thanks
[Xoom Android Development] alex94kumar:
This.
[Xoom Android Development] petrossa:
More this. It's the only logical explanation.
[Xoom Android Development] uzi2:
...but it doesn't explain why the same people report 146 as smooth and 147 up as laggy. They have obviously given 146 time to settle, so there is every reason to suggest they have done the same with the newer builds.

Swyped from my Xoom
[Xoom Android Development] golfdiesel:
Exactly. I will do more tests when I get home.

I have run antutu with test build 1 and with test build 2. The only score that is different is the 3D score. There is a difference of 300 points between these two test builds (in the 600's compared to 900's).

The places where I found the interface lagging is when swiping between homescreens and while typing with the stock keyboard.

Google earth and other 3D apps/games are allso slower and choppier in test build 2.

Verstuurd van mijn Nexus S met Tapatalk
[Xoom Android Development] MoneyFist:
I'm glad you guys changed the EOS logo.

It resembled a Nazi swastika and it almost got me in trouble in Germany while I was on a train.
[Xoom Android Development] golfdiesel:
Here is the screenshot from the Antutu benchmark for test build 1. The Xoom was tested about 12 hours after flashing the test build.

And here the screenshot from test build 2. It was tested 10 hours after flashing test build 2.

There is a clear difference in the 3D scores which is also noticeable when playing 3D games for example.

In the real world I see the interface lagging/stuttering while swiping between homescreens and while swiping in the app menu. Typing with the stock keyboard is also suffering from a slight delay, with Thumb Keyboard this is not noticeable.

I haven't tried 153 yet because of the test builds that Solarnz is making.

Can someone post their Antutu scores with 153 for example? I am interested in the difference between the scores I posted here. I have the Xoom clocked at a maximum of 1200MHz.

Verstuurd van mijn Xoom met Tapatalk
[Xoom Android Development] alex94kumar:
Yikes.... all I can say, was that I did Nazi that coming! *prepares to get flamed for that joke*

In the big picture though, we all just have to remember the hundreds of hours TeamEos has put into the ROM, and the phenomenal job they've done. I do not have a fetish for smoothness on the home screen, I could really care less. All I care about is that the UI in other places is buttery smooth, which it is for the most part (95%of everything).

The more we obsess on the homescreen issue, the harder the jobs are for our amazing developers.
[Xoom Android Development] iruiz2:
Here's my Antutu at 1200 as requested, on 153. It looks veru similar to your score on test build 1.Ah! I never had any lags with current nightlies...

Sent from my Xoom
[Xoom Android Development] MoneyFist:
For what it's worth.

Xoom 1200mhz

Version 151

Score = 5748

3D = 679

Updated

Version 153

Score = 5965

3D = 925
[Xoom Android Development] alex94kumar:
This is for test build 2. I will flash 153, wait a few hours, and will update this post one I get those results
[Xoom Android Development] MoneyFist:
My 3D = 925 was achieved immediately after flashing.

I did a cache and dalvic wipe.

Make sure you do not use Force GPU or Disable HW overlays.

This lowers the score by 20%
[Xoom Android Development] iruiz2:
If people post Antutu values, do it at 1200 for easy comparison, yours is at 1400... :rolleyes:
[Xoom Android Development] kcrudup:
We acknowledge there was an issue with a couple of the builds, but that has been solved (and for a while now) - but what I was getting at was there's a way of comparison that leads to false results, and that some of the ways people have been testing for "lag" are inherently flawed.

For those who still see slowness, have you done what I've asked WRT the CPU load bar?

---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------

Guys, all the wiping (especially the Cache) is unnecessary 99% off the time.

For the ones who do this, what do you think it does?

---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------

Guys, all the wiping (especially the Cache) is unnecessary 99% off the time.

For the ones who do this, what do you think it does?
[Xoom Android Development] MoneyFist:
It gives the pedantics less things to ***** about.

But that has clearly backfired, because now we have a new group who are anti cache & dalvic wipers.
[Xoom Android Development] kcrudup:
Why continue to let people waste their time?!
[Xoom Android Development] MoneyFist:
Why did you double quote my post?

It was unnecessary.

By the way I wiped my cache again... because I can.

Since you are spell checking my posts, I'll spell check yours.
[Xoom Android Development] kcrudup:
XDA posting glitch.

You're not going to gain any speed, reliability nor change in features by wiping Dalvik cache, and the other "Cache" isn't used except in recovery and OTA updates and the like- the Framework knows when Dalvik needs to be invalidated and will handle it on its own. All these wipes are mostly superstition- so what I'm trying to do here is prevent other people from wasting their time (based on ill-advised information in XDA threads).
[Xoom Android Development] EDNYLaw:
First off, thanks for all your hardwork with the Xoom, I use mine every single day and I never have problems with EOS ROMs, they're great. I was curious about some of the kernel stuff. Is it possible to merge things from different kernels into the kernel for the Xoom to give some more features? Things such as color control like Franco's kernel for the Galaxy Nexus, perhaps governor controls? The colors on the Xoom are not great and would definitely benefit from some tweaking. I'm not familiar with merging and compiling kernels, but can you take things from Google's kernel source or Franco's or Imoseyn or whomever and merge them into the Xoom kernel? Again, thanks for all the hardwork, it's definitely appreciated.
[Xoom Android Development] kcrudup:
Sure, and we do that all the time. Our kernel is a mix of the Motorola "Official" kernel, with stuff from later Google kernels, Linus' kernels, and thiings I see from other ROM developers (and to them, stuff we do) that looks interesting.

If you can point me to a thread that covers it, I can look- but consider that for any given device, the display we see is a function of the display itself (and the technology behind it (i.e., TFT/((S)AM)OLED/etc.) and the display processor built into the chipset- so there's a good chance that that kernel's color controls are unique to some combination of the hardware i the GNex and wouldn't map to the Xoom's hardware. But, send me a link anyway (and FWIW, I have no issue with the colors on the Xoom).

What do you mean here? We support all the standard governors in our kernel, do you mean "more governors" or do you mean "a way to control the ones we use"? I generally use "SetCPU for Root Users" to tune CPU Governor control on my devices.
[Xoom Android Development] alex94kumar:
Perhaps we could all collaborate and agree on a foolproof method, to create testing conditions for a benchmark test? Like, the clock speed, what not to have turned on (2D rendering, HW overlays, etc), or anything else. If we do this, we can all test our devices and figure out which builds are problematic, or if they are device specific. Anyone else think this would be a good idea? or something like this
[Xoom Android Development] mylegiscramped:
I think this would be a good idea.
[Xoom Android Development] jiffy1080:
+1000 as it could help bring something more constructive than just "this build is laggy."

Any thoughts about adding a different cpu governor? I have been using a conservative governor with hot plug ability on my phone and it is freaking awesome. It is called ktoonservative. Also maybe I'm missing it but is the kernel in each nightly gpu overclocked? If not any way I can get my hands on one with it?

Keep up the great work guys. I've had this Xoom for a year and a half, have went to a tegra 3 prime, and then sold it to come back to this rock solid experience. I'm a happy camper here until a real successor is released.
[Xoom Android Development] petrossa:
Here is my Antutu with governor on lagfree, 1200 mhz
[Xoom Android Development] kcrudup:
Thanks- I'll look at his repositories.

Well, consider that your TV has not only color controls, but a better screen and is lit a lot better, too. But I'll look and see what he's done.

Yeah, I use SetCPU to change those- which have been mostly kept at stock, which is why I'm open to inputs like your values.

Yeah, that one was my fault- I'd increased the size of the audio buffers in an attempt to alleviate the stutters when playing background music, not realizing the Android audio layer would try to fill then drain the entire thing without taking into account the larger buffersize. I increased the number of buffers instead, which apparently fixed both issues.

Nah, likely I/O because of the available memory and the flash part they used in the Xooms (I've written extensively on this in the LTE Nightly thread). The CPU really isn't a factor here once you get past a certain (actual) CPU frequency.

This is good, empirically-derived information- I'll use SetCPU to try these out!
[Xoom Android Development] Dyelon:
What's the status of the rom right now? Any updates coming?
[Xoom Android Development] kcrudup:
I don't have any, but that's just kernel :D
[Xoom Android Development] alex94kumar:
kcrudup, what would you say about establishing a standardized condition for benchmark tests on different builds?

I think it would eliminate the noobs who don't follow directions
[Xoom Android Development] EDNYLaw:
Nice, I didn't even realize SetCPU allowed that type of control, I'll check that out.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Xoom Android Development] golfdiesel:
It's a great idea to have a standardized test method.

Verstuurd van mijn Xoom met Tapatalk
[Xoom Android Development] edboston:
But if noobs don't follow directions, how would having directions on how to do it eliminate the problem?
[Xoom Android Development] alex94kumar:
Lol I see what you did there
[Xoom Android Development] kcrudup:
I'm all behind it- but I honestly wouldn't know where/how we'd do this. Apparently AnTuTu Benchmark is considered somewhat standard, so perhaps that's a start?
[Xoom Android Development] petrossa:
Both my Xooms with 153 bench practically the same with Antutu, so that should be correct.
[Xoom Android Development] alex94kumar:
I do think it's a good start. However....

I propose that the standard benchmark test for any TeamEOS rom/test build shall be run

only

when the following conditions are met:

App: AnTuTu Benchmark

Test type: "Default (all)"

Processor Clock Speed: 1200MHz

Governor: Lagfree

Scheduler: Deadline

Force GPU Rendering OFF

Disable HW overlays OFF

All recent apps killed (for max ram)

Do any of you guys think something should be added to the list?
[Xoom Android Development] leejairo:
hdmi cable question

when i connect the hdmi cable to the tv, the resolution it´s only 720p... anyone knows how up the resolution at 1080p??, thanks for your answer!!:laugh:
[Xoom Android Development] golfdiesel:
Isn't 'interactive' the default governor?

Verstuurd van mijn Nexus S met Tapatalk
[Xoom Android Development] kcrudup:
Not possible- HDMI is locked to 720P on this device in the video drivers (to maintain same-rate resolution with the display, which is 1280x800 with a 1280x720 effective display size).

---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------

Yeah, but there's plenty of ways to change it (including Settings->EOS Settings->System->Performance Settings).
[Xoom Android Development] alex94kumar:
i say lagfree, because isn't that the goal we're all trying to accomplish? :D
[Xoom Android Development] golfdiesel:
;) OK, lagfree it is then :)

Verstuurd van mijn Xoom met Tapatalk
[Xoom Android Development] edboston:
I would think the test should use the defaults as released as this is probably the most common configuration. Personally, I never change the defaults.
[Xoom Android Development] alex94kumar:
i thought about that at first, actually, but for some reason didn't like the idea
[Xoom Android Development] kcrudup:
Well, "Lagfree" is really only the name the CPU Governor was given by its Dev, but it doesn't matter to me.
[Xoom Android Development] alex94kumar:
Haha, I know, just trying to add in some humor here :)
[Xoom Android Development] Sistema1927:
No lag here (never had any), but I am curious as to what the values of the referenced CPU monitor and colored bar represent. Right now I am seeing 0.38/0.65/0.7
[Xoom Android Development] mylegiscramped:
I understand the idea behind frustration in people not doing something that seems extremely basic to people that are well versed in the ways of debuging kernel and application issues, but the reality of the situation is a lot of people just don't know how and don't know where to get the information.

By creating a standardized method of debuging and submitting error reports and making that information well advertised then less people will have an issue submitting issues to developers and we will have less time wasted on dishonoring ourselves by belittling people who haven't had the chance or the guidance to learn how to do these things. So how about instead of talking down to or about people lets do something positive with our time and energy and create a tutorial about how debuging and error reporting should be done and submited. I would volunteer, but I def don't have the experience or the knowlede to do something like that.

I think what we should do is create a doccument with pictures and text describing actions and make it standard to post this information in a very obvious and apparent area. I propose that this document be created and placed hopefully stickied somewhere in the forum then in any thread thats created that has something to do with this process the document be linked to and directions be given to people in a format such as the following.

"Here is a project

This is a bunch of information about the project

Here is some links to where you can get the project 'link' 'mirror'

If you have issues with this project please submit and error report here 'link'

To create an error report please follow the instructions listed here 'link'

Thanks for the cooperation...

..."

I think things would be much more productive in that way. That's how a ticketing system works generally, or people report an issue and then someone is like oh here do this 'link', which is a link to the tutorial that should be made, then send it to us and we'll get back to you on the issue or try our best to create a fix in the next release.

That's how corporate IT organizations work, and to be honest, I'm not a fan of corporations, but they know how to do things efficiently. Effectively may not always be true, but they do tend to get **** done a lot of the time. So I don't know take it or leave it, I'm not trying to tell anyone what to do, just merely making a suggestion, I hope I'm not coming off as someone who is trying to make people do anything I just think this would be helpful not only to me, but to other.

I personally plan on becoming an android developer and if it doesn't get implemented in the near future, when I do have the knowledge and experience I will probably do it myself. Anyway, TeamEOS ya'll put out a great product I thank you very much for your time and effort, and I look forward to flashing your next build! Keep up the great work!
[Xoom Android Development] adityamunshi:
Quick review of the latest #153 nightly. Came back from CM10 for a change and i find that EOS 153 has much better battery life. You could say its a little but less responsive than CM10 but cant call it laggy. Either way, i'll be on the eos roms for a while (till i get bored again !).\

Thanks to the EOS team for a great ROM, keeping the Xoom alive.
[Xoom Android Development] alex94kumar:
Sweet

And perhaps, we could even go so far as to create a whole new thread for this standardized benchmark test for TeamEOS Roms?
[Xoom Android Development] scottgti:
#154 is out.
[Xoom Android Development] ahmed007:
154 working great :)
[Xoom Android Development] Taysider:
Why does GooManager keep wanting to download CM10 gapps-jb-20121011-signed

current EOS gapps are 20120802, correct?
[Xoom Android Development] emd2009:
Don't question GooManager
[Xoom Android Development] Taysider:
What!
[Xoom Android Development] paulieb81:
Yup, its known issue, dev said it would be fixed in tonight's nightly. We are all waiting for this fix. :)

---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------

It's working fine for me, and several others. There was talk about it not being able to get local info like calendar entries. But I was able to add a reminder, but not able to get it to tell me what is on my calendar. I am still researching online to see what are the commands it understands and what features it is supposed to have. There is a lot of talk about Google ripping out a few features last minute due to the Apple lawsuit. I dunno, I just hope it gets sorted out, as Google search is way better than Siri, Apple go suck it. You didn't create voice search.
[Xoom Android Development] elsworth1983:
I followed this guide from post number 9 and it works for me :cyclops:

---------- Post added at 06:07 PM ---------- Previous post was at 06:04 PM ----------

Have you updated to the Lastest Nightly (117) my SD card was playing up before unitl i updated when my was playing up a just rebooted the Xoom
[Xoom Android Development] Sk8er Boi:
Anyone have problems restoring apps using TB or is it just me ?
[Xoom Android Development] spy0r:
Flashed the Rom on my MZ601... everything (exept 3g of course) works fine for my but.....

my xoom won't speak :-( i can use voice search and it searches everything in google fine... but it doesn's speak to me....

Any GERMAN user with a speaking xoom here???

thanks mates
[Xoom Android Development] HuckFinn:
So I have wiped my Xoom a couple times now and I am having some strange behavior. I have not seen anyone mention this, so please forgive me if I missed it.

When I try to download anything over the stock browser or Chrome I get an error that an SD card is needed and it will not download. Also if I try to use the Amazon Market application to install and application I get a similar error. BUT I can still surf the web, download attachments with GMAIL and read files off the SD card using ES File Explorer.

Does anyone have any idea?

Just to clarify these are the steps I took each time I tried.

-Boot into EOS Recovery (touch based)

-Wipe data/factory reset

-Wipe cache partition

-Advanced>Wipe Dalvik Cache

-install zip from sdcard>External>Flash nightly (117 this time)

-install zip from sdcard>External>Latest Gapps (gapps-jb-20120712-eos.zip)

-reboot

At first I thought it might be some old ICS app screwing that up so I have tried it first thing and still the same issue.

Thanks for any help. If this is a known issue just let me know and I will wait for the next update.

EDIT> I knew as soon as I posted this I would figure it out. I was also flashing the Power Button Reboot Menu by BRD (found here) right after the Gapps in all of my previous attempts. I tried again leaving this out and now I do not have that problem. So while I can not say with absolute certainty that this caused the problem it seems to be fixed.
[Xoom Android Development] elsworth1983:
It has only spoke to me when i have asked what the weather was like in my location ?
[Xoom Android Development] uzi2:
Did it say "Hey Dude, you gotta move if you don't want rain, rain and more rain... Next time ask me a harder question"?
[Xoom Android Development] baggy247:
Nice work on this, its running great for me.

Is it possible to get it to go into the Nexus 7 hybrid UI? I've tried changing density in the build prop but I lose the nav buttons and it stays landscape