yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] bigdave240:
I see it too but since i am usually muted i didnt notice it. But it seems that different things have different delays. Clicking on the home is about a second. But opening a new browser tab is faster. Dont know if it was like that before. I'll restore an old nandroid and see if it was different.

Edit: I am back at 136 and there isnt any delay on stuff that had a delay for me on 143. Going back now......
[Xoom Android Development] bacon612:
Just loaded 143. I've been noticing a little lag when I swipe between home screens that wasn't there before 140. Anyone else see this? I'm over locked to 1.5ghz and using on demand governor. It so noticeable that it has me googling "project butter"
[Xoom Android Development] kcrudup:
Nothing has changed that should make a difference in your home screens, though.

---------- Post added at 07:20 PM ---------- Previous post was at 07:12 PM ----------

<grumble>

OK, I'm pushing back the Audio buffer size to stock (but keeping the higher number of buffers).
[Xoom Android Development] bacon612:
OK. Maybe its just me. I'm thinking about doing a full wipe. Its been awhile.
[Xoom Android Development] kcrudup:
That really shouldn't be necessary, though.

Do me a favor: Turn on Settings->Developer Options->Show CPU Usage, and keep an eye out for a blue bar at the top right of the screen. When you get lag, tell me if it's more than 1mm or so long.
[Xoom Android Development] dboftlp:
b/c I'm full of **** ;) derp

for some reason it just started working...

the bit about screwing it in was just for ****s & giggles, didn't you find it funny? I did, but in my own defense I do always say "I think I'm really funny... but I'm not..."

Swyped from my GNex running TeamEOS 3 nightlies.
[Xoom Android Development] tomcrown1:
Has anyone noticed that the stock browser is acting wacky?

Ie I go to xda forum and the page keeps reloading.

Dolphin browser works fine.
[Xoom Android Development] jdg1:
I thought it was just me. I keep getting a service connection error and video loops. started after flashing 143.

I don't use Dolphin but Chrome seems OK but a little slow.
[Xoom Android Development] kcrudup:
Don't see that here. Replying to you from the stock Browser.

We didn't change anything that would affect this, anyway.

---------- Post added at 11:47 AM ---------- Previous post was at 11:46 AM ----------

What's a "video loop"?
[Xoom Android Development] bigdave240:
I had the connection warnings for quite a while. Thought it was my router. Everything else is working ok so far for me. Only vids that loop are the ones that are supposed to lol
[Xoom Android Development] kcrudup:
Detail these for me, please? I've never seen them.
[Xoom Android Development] bigdave240:
I will let you know as soon as it happens again. Its a popup that says something about connection error with an ok button. Its been happening for as long as I remember but i tthought my router was the cause because i sometimes get dropouts on the 2.4 channels but not the 5ghz ones. You click on ok and it doesnt appear that anything has happened. Like i said, i willtry to capture it if it happens again. Pretty infrequent though
[Xoom Android Development] wesamothman:
If I may, can you try to flash this browser-stock and check?

http://db.tt/zxOsDiEH
[Xoom Android Development] tomcrown1:
I check with the browser you wanted me to flash and it just stated browser stopped.

I uninstall the browser through titanium backup and reinstall stock browser.

I have noticed that if I am not in desktop mode everything is fine.

In desktop mode then things go wacky.
[Xoom Android Development] TheRandom1:
Has anyone else had an issue where the notification light keeps flashing (dimly) after clearing out all notifications? Only way I have found to turn it off is to reboot. I am on 143.
[Xoom Android Development] SamuriHL:
Just a note I'm now seeing this issue too. Thanks!
[Xoom Android Development] jdg1:
Its when a flash video gets stuck playing a portion over and over again.
[Xoom Android Development] sovereign_313:
I also noticed a delay before Google now (tapping the mic in the upper leftish corner, by the word Google) has a delay before it accepts speech input. I have to wait 2 to 3 seconds before it will be ready to recognize speech. It appears like it's ready, but won't actually register the entire word (starting off) unless I wait.
[Xoom Android Development] freeky1:
Terrible delay now when typing into browser. Using Dolphin Browser and have sounds on when typing.
[Xoom Android Development] REHolt218:
I have not noticed any of these problem's. I am running 143 and it runs smooth and fast.

Could this be an issue of conflicts with different software running?
[Xoom Android Development] mptpro:
Same problem here. Been happening for the last few nightlies. Drives bucking fonkers.
[Xoom Android Development] xyrcncp:
Same here, the delays are pretty bad. Went from Stable to 142 to check it out. Noticed the dim notification light as well.

Tried going back to the backup I made of stable, but I get an error that /system can't be restored. So I'll just flash stable again.
[Xoom Android Development] freeky1:
I'm glad yours is running great on 143. That doesn't help me. I flashed back to 142 and everything is fine. I flashed back to 143 again, and all the lag came back. I flashed back to 142 again, and all is fine again. If it's a problem with software conflicts, then it's build 143 conflicting with everything.
[Xoom Android Development] bigdave240:
Read back a couple of pages and look for kcrudup's explanation. It is clear what the issue is and i am sure it will be fixed. Might want to go back to what worked for you and wait for the next update.
[Xoom Android Development] sovereign_313:
Ticking issue is gone for me in 144.
[Xoom Android Development] SamuriHL:
Sweet. That was affecting quite a few things for me. I went back to 142 until a fix was released. Upgrading to 144 as we speak.
[Xoom Android Development] bigdave240:
Delay seems to be gone now. I didnt use the notification lite but turned it on now and it seems to be normal so not sure if it got 'fixed' or I am just lucky but everything seems normal now with 144. Thanks kcrudup!

Kcrudup, here is a screenshot of the network error that happens occasionally. Not terribly annoying but you asked for more info.
[Xoom Android Development] tomcrown1:
In 144 I do seem to get some lag will typing. It is a small lag so I can live with it.

Things do seem to load faster thou.
[Xoom Android Development] freeky1:
I upgraded from 142 to 144 on Sunday and immediately got the lag back when typing into any browser (stock, Dolphin, Chrome, Firefox), although not as much lag as 143. I immediately flashed back to 142, and all lag is gone. Please undo whatever was changed after 142.
[Xoom Android Development] kcrudup:
144 just turns 143 into 142. Only change is to revert the larger buffersize for audio packets.

Of all my tests, I never noticed to see if the typing tick was affected, but I'm used to it being a little off the touch.

It's too bad about that piece of collateral damage, 'cause the benefit to music players and such was really nice. Far fewer stutters when listening to music while web-browsing.
[Xoom Android Development] dboftlp:
Wow, this was reverted b/c of a supposed lag in the tick sound on a keyboard?... Can we overrule? Especially since the actual reversion didn't cure the hypochondriac & they flashed the same thing twice?

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] rob62551:
Yes you can, stay on build 143! That's what so great about nightlys.
[Xoom Android Development] Mjamocha:
LOL, :good: I didn't experience any the tiny issues being claimed, even then nothing is ever going to be perfect for everyone.

:highfive:
[Xoom Android Development] G8orDroid:
ooh, ooh, Android 4.1.2

(Of course, I'm fairly certain there's very little in it to enhance what we already have. We probably have most of it already)
[Xoom Android Development] kcrudup:
FWIW, I've kept it changed in my private builds, as I care far less about selection ticks than I do non-stuttering BT.

However, there were two parts to my fix:

- Increase the number of audio buffers from 2 to 12 (having more of them allows the system to fill them up, so then it's up to the kernel to dispatch them instead of having it have to make a (delayable) context-switch to have userspace fill the same couple of buffers up so quickly

- Increase the size of each buffer above from 4K to 16K (having them be larger means more samples can go in and be routed out w/o having to involve user-space. The Speaker/Headphone Audio (via I2S) and the HDMI Audio (via SPDIF) on the Xoom is done via DMA, so pauses and stutters in the audio aren't an issue of the kernel/CPU being fast enough, but if the buffers are small they have to be replenished more often (and/but if disk-I/O is going on and that prevents the kernel from switching, or ties up the I/O subsystem, then userspace can't replenish the buffers in time, and you get a pause or stutter in the audio). However, apparently some parts of the Android Framework and/or Audioflinger must be trying to either fill the entire buffer (with silence, perhaps) or is trying to write out the entire buffer (not sure which) so the larger buffersize results in audio latency.

It was the 2nd commit that was reverted (audio buffers are back to 4K). The increased number of buffers still helps prevent audio stutter, however.
[Xoom Android Development] sovereign_313:
Just out of curiosity, would it be plausible to have an if or something to toggle it in EOS settings? I realize that one is a sub-system, and one is not, but something like that would be cool.
[Xoom Android Development] rob62551:
4.1.2

Build 145 out with update to JB 4.1.2

Working good so far. I am noticing better smoothness. Apps seem to work such as Netflix and YouTube.

Typing has improved from lag found in last few builds. Enjoy!
[Xoom Android Development] EtchG:
Was this fixed? I have installed 145 and notice the lag is back. Again, it starts off fine, but the more motion there is (mostly with games right now) the more the screen "sticks" like it is moving over speed bumps.

My Xoom has never been a fan of over clocking video, so it might be a combination of that and whatever kernel commits are currently in place.
[Xoom Android Development] TechnoManiac97:
what about US 3g versions?

have you got rom for it?
[Xoom Android Development] kcrudup:
I'm now thinking we're talking about two different things. What I'd done before that I thought was slowing down was to change the default I/O Scheduler away from CFQ to Deadline (the CFQ I/O scheduler is faster than the Deadline I/O-S) and to increase the I/O readahead size to 1MB. The problem with the latter was that under low-memory conditions you'd get slowdowns (sometimes large ones) as the system then tried to find the 1MB before it could read in your programs or data.

I turned all that down to 128KB (readahead isn't as valuable on Flash disks as rotational ones) and moved us to the SIO scheduler, which is faster than even CFQ.

... so I'm not sure what's going on with your situation; those kinds of changes shouldn't make a difference with a game- in fact, my Xoom is faster than ever (admittedly, I've given up on the EMMC and am running off a 64GB external Micro SD-Card ... more on that sometime later), but the overall changes should have sped things up for everyone.
[Xoom Android Development] rlmesq:
The 3g Xoom is an obsolete device due to owner inattention. Why would a developer bother?

There was a period when everybody with a 3g Xoom got the LTE upgrade for free. Anybody who snoozed through the upgrade period probably wouldn't take the time to flash a custom ROM.
[Xoom Android Development] kcrudup:
Actually, as far as I know, we do maintain a device called "Stingray_CDMA", which is the 3G-only variant of the Xoom (NOTE: that is NOT the same as a device that's been sent into Moto for the refurb but has no active LTE or VZW account- for those, you'll use the "MZ602" build and flash the LTE radios anyway).

It's pretty much right in the middle between the WiFi-only device and the LTE device, so save a few changes they're all pretty much identical (all of my kernel enhancements and such go into all Xoom-branded products, for example).

It has a "Jenkins" ((Nightly) build-server) page too, where you can retrieve Nightly builds and see Changelogs.
[Xoom Android Development] sovereign_313:
I have to disagree. I think that's an unjustified judgmental generalization. I had to contact Motorola and pay them money to upgrade mine to LTE. Did I miss the window? Sure. Not because I didn't give it the attention, but because, quite frankly, I didn't want to be without it for 5 or more days. Some people may stay on 3G because the speed (while not 4G) isn't horrible, and seriously consumes less battery than the LTE radio (or switching between them). I purposely did not upgrade, and have been running custom roms the week I got the device.
[Xoom Android Development] rlrbjr:
I have an MZ602 and I have deactivated with Verizon (for the same price I can get unlimited data using my phone's hotspot when not at home).

I've been running the MZ602 nightlies (currently on 145 but I see 146 is available). Based on the comment above I gather I would be better off running the MZ604 nightlies.

I have a couple questions about that.

(1) What are the advantages of my switching?

(2) when switching from MZ602 (stingray) to MZ604 (wingray) should I wipe or can I (as usual) dirty flash? Thanks.
[Xoom Android Development] kcrudup:
Sh!t- that was a typo-I'd meant to say "MZ602".
[Xoom Android Development] TechnoManiac97:
:confused:

do you know that there are lots of other countries except USA?

Do you?

So how I must upgrade to LTE in Ukraine? Do you know what is it???

Do you know that we haven`t got LTE internet at all???

how can I update my device from 4.0.4 (from eos team) to 4.1 (not from eos team) using my mac?
[Xoom Android Development] Mjamocha:
Thank you EOS for the awesome 4.1.2 ROM , and all of your hard work.

Themed & Tweaked... Mjamocha ABYSS Tribute to EOS ROM (screenshot Settings, and Browser themed as well)

​

​
[Xoom Android Development] wesamothman:
Nice theme buddy :)
[Xoom Android Development] khanh1289:
May we please haz new Gmail.apk in new Gapps package?! :D
[Xoom Android Development] dboftlp:
Gmail -> http://d-h.st/Jm4

& the new play store -> http://d-h.st/kFC

was just thinking the same thing!

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] Moricon:
Thanks. Play store worked fine but gmail errored out. Do I have to do something special for that one?
[Xoom Android Development] Moricon:
Try this again

---------- Post added at 09:36 PM ---------- Previous post was at 09:35 PM ----------

Crazy app tonight... Play store was fine but gmail did not install. Do we have to do anything special? Please see screenshot above. Thank you
[Xoom Android Development] jodtalingchan:
I uninstalled the old gmail and reinstall apk. it works fine.
[Xoom Android Development] dboftlp:
What he said ^

I used TiBu to backup, remove & then after restore data & no problems on my Xoom & my GNex

yes, both run EOS3 ;)

I did reboot after uninstall, fwiw

hopefully we get a new gapps to flash for simplicity.

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] jm9843:
A couple of issues that I've noticed in build 146:

* Google Now doesn't respond to voice for invoking voice search (i.e. "hey Google"). This has worked, not worked, and then worked again in prior builds.

* Single finger gestures for expanding/collapsing notifications doesn't work (was added in 4.1.2)
[Xoom Android Development] khanh1289:
Make sure you re-flash gapps to enable the voice activation.

Maybe the fiber features is only for phones?!
[Xoom Android Development] bigdave240:
I have always had to reflash gapps in order to get the google now voice thingy to work. You can tell if it is there by looking at the input line. If it only says Search then you hsve to flash gapps and then it will say Search or say Google and then work. At least that is what has worked for me.
[Xoom Android Development] freeky1:
Yeah, this is true. Whenever I flash to a newer version, I also flash the GAPPS before restarting, and I have not had any issues with them at all.
[Xoom Android Development] Asphyx:
Just one more statement for Flash GApps after every flash and never have an issue.

On a side note...Should the OP be changed to reflect the 4.1.2 update or has that yet to actually be incorporated into the builds?

Just flashed 147 and it's much faster (as it usually is on first flash) but I have noticed faster redraws of the homescreen.
[Xoom Android Development] Mechcondrid:
hey i did a thread search and i didnt find anything mentioning if the hdmi HDCP output is working on the us 4g moto xoom, im currently running eos 3 stable release and no matter the option in the drm check menu does any hdcp content play over micro hdmi. I just get a big red x while the audio still plays.
[Xoom Android Development] buzzdroidx:
Sadly I am experiencing the same issue. I have searched for solutions,but have not found anything helpful. If I do find something I will let you know
[Xoom Android Development] Asphyx:
HDCP support should only affect Copy Protected video if I'm not mistaken.

I play a ton of HD video just fine but none of it is copy protected.
[Xoom Android Development] khanh1289:
Is it just me or the recent builds since 4.1.2 is pretty laggy? I didnt experience much lag before 4.1.2
[Xoom Android Development] Picolini:
Flashed fine, everything seems to be working great.

However, I've got no mobile data. Just a blank triangle next to the battery and it's saying I'm out of service area (which I'm not). Wifi works fine, but no 3G/4G. Any idea?
[Xoom Android Development] REHolt218:
What version did you come from? Could be a radio problem.
[Xoom Android Development] Picolini:
I installed it over an older EOS ICS 4.0.x build, not sure which one. Didn't see anything about flashing a radio for this ROM on the first post. Checked again just now. Am I missing something?

Flash process for this ROM was pretty standard,

Wipe data/cache/dalvik. Flash the ROM, flash gapps.

edit: Also, battery life has gone down easily twice as fast since I flashed this ROM. Could possibly be linked to the lack of signal, might be searching constantly. But I'm at 30% after 11 hours, with a total of maybe one hour of actual usage. I can usually use this about 2 hours through out the day and let it sit in between, and it'll last 2-3 days.
[Xoom Android Development] sovereign_313:
Sounds exactly like an unflashed radio. The battery problem plus no wan... I'd bet on it.
[Xoom Android Development] bigdave240:
Go here to get the radios: http://goo.im/devs/teameos/radios

to flash it use the rogue recovery or it wont flash right. Other recpovery might work but definately not the eos recovery. Flash the radio and all of your problems you described will be fixed.
[Xoom Android Development] Stratus41298:
I tried this with CWM 4.* and it flashed but did nothing.

Installed rogue recovery found on this forum and followed the instructions. I now have 4G!!!! I haven't had 4G in a long time!

It took me about ten minutes minus nandroid backup time to install rogue and the radio.

Thanks so much!

EDIT: Oh, and the Rogue Nandroid is SOOO MUCH FASTER.
[Xoom Android Development] bigdave240:
glad it worked out. Just being helpful after sovereign_313 pointed out what was wrong.
[Xoom Android Development] Mechcondrid:
Well it also affects the Google play movies app as it requires hdcp so nothing from the movie market will play
[Xoom Android Development] grncherry:
Help. I don't know if I have a problem or not. I am on nightly 148. According to TB I have 0kb of free space left in System Rom. I cleared both caches and no change. Does this present a problem or should I not be concerned. I hesitate to run the pittpatt. initial. zip from the ICS days to free up some space. Any enlightenment would be appreciated.
[Xoom Android Development] kcrudup:
None at all. Technically speaking, the ROM is the only thing that should be going in there, and it's set Read-Only. In fact, any space not used in the System ROM should be considered "wasted".
[Xoom Android Development] grncherry:
Thanks very much for the timely response. I am relieved to get the information. I also want to thank you and your team for the great work that you are doing for our mighty Xoom.
[Xoom Android Development] bigdave240:
Goo. Im is soooooo slow today. Dl'ing 148

Finally flashed it. The browser seems somehow much faster. Didnt see that in the rn's. Hope it stays this way with use. Nice job guys
[Xoom Android Development] rob62551:
In as such kcrudup, is it best to have apps located in system/apps as apposed to data/apps? If so what is the actual benefit aside from use of space within the system partition?

Also, would it not benefit one to have say, 10mb free for themes? Thanks for any and all advise!
[Xoom Android Development] kcrudup:
Actually for most apps, it doesn't matter where an app goes, with a few exceptions.

Android does reserve some System Permissions that can only be granted to ROMs which reside in the /system partition, as an aid to security (since 99% of the time these are apps considered "trusted" by the manufacturer or ROM-maker). However, other than, that, "/data/app" should be considered a writable extention of the read-only /system/app that ships with your device (and updates to System apps end up in /data/app, as well).

The system partition is expected to only have the contents of the ROM in it, and is expected to be mounted read-only; IOW, it won't matter how much space is or isn't left in it, as you're not supposed to be writing anything into it, "adb remount" aside.
[Xoom Android Development] rlmesq:
HBO GO is broken with the latest release, but I'm not sure whether it's the app or the ROM. It isn't the data issue reported with earlier versions; instead, I get a pop-up that says, "HBO GO login is currently not available on this device. Please try again later. We apologize for the inconvenience."

I may try flashing an older version of the ROM to see if it works.
[Xoom Android Development] rob62551:
HBO works on mine. I have seen a few times where I'd have to reinstall video service apps (Netfix, Xfinity Play and such) after flashing a new build.
[Xoom Android Development] rlmesq:
Just wiped cache & Dalvik, re-flashed 148 & gapps, and it now works.

I usually wipe the caches when flagging a ROM, but didn't due to advice on this thread (from devs who are, admittedly, much more tech savvy) that it isn't necessary. I think I'm going to revert to the old habit of wiping when I flash a ROM in the future.
[Xoom Android Development] kcrudup:
Do you flash GApps every time? If not, then actually flashing it is what did it (the DRM services like what HBO GO (et al.) need come from the GApps).

FWIW, I never wipe caches.
[Xoom Android Development] rlmesq:
Yep, I always flash gapps. Maybe I had a brain-fart the last time and forgot, but I don't think so.
[Xoom Android Development] glock20c:
Good battery life.:thumbup:
[Xoom Android Development] bigdave240:
yeah. Seems the best so far. Not sure what was fixed to do this or if its just a coincidence but loving it!
[Xoom Android Development] jphillips.hd88:
+1.
[Xoom Android Development] grncherry:
I have done an extensive search but found no answer, so I'll pose the question. Can anyone enlighten me on why the gps is so inaccurate. It pinpoints your location fine, but the pointer indicates you are facing 180 degrees from where you actually are. I've experimented with this from several locations, hundreds of miles apart, with the same outcome. At first, I thought it was my home location but now I have ruled that out. Is it my unit or is this a universal bug with JB? By the way, the same happens with my S2 running a JB rom. Thanks in advance.
[Xoom Android Development] bigdave240:
on my xoom it only reads correctly if the e screenview is oriented to landscape. If it goes to portrait then it is off. Maybe your issue too?