yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Asphyx:
There are lots of reasons for developers and beta testers who are working with them to flash every nightly. For one you want to see if the intended fix actually fixed what it was you were going for!

Report the result to the Devs so they know Joy, No Joy.

And sure they are all pretty stable especially where this project is concerned.

But you can't possibly know how stable it is unless you use it for more than a day. What fixes one thing can affect something else in a bad way and you would never know that unless you spend the time and put it through it's paces. Especially where things like battery life are concerned.

I'm not saying you should not chase nightlies or flash your unit once a day if thats what you enjoy.

I'm just saying after 10 years of flashing a new rom everyday it isn't much of a kick for me anymore or more fun than using all the things they added to it that I have yet to try!

To each his own but having 5 extra checkboxes to play with (that in most cases I will set and touch only once) is not worth the time spent everyday just to get it today as opposed to the even more feature rich stable version they will release 10 days from now!

If there is a new feature it's not like I'm going to lose it in those 10 days!

So I pick and choose based on the reported issues posted here, Note things that have issues in the version I have so they know roughly where and when the bug may have started.

But feel free to flash all you want, I used to, just don't anymore!
[Xoom Android Development] RobBull69:
I'm not disagreeing with you. I don't necessarily flash every nightly build. If I get a build that runs real well, I'll stay with it until I see a new feature that I really want merged or read real positive reports about performance.
[Xoom Android Development] LesismoreTN:
I know that some folks are having reboot issues and reported already, but I thought I'd throw in my experience as well. I came from ICS to JB #120. I was previously using CWM, but for this time, I used TWRP for recovery. I did the usual wipe, Dalvik and user caches (but did NOT see the step to format system,) then flashed #120, Gapps, then rebooted.

I did NOT do a restore of any kind, just some select apps from the Market, namely YouTube, Pandora, Astro and ADW Ex. Started seeing reboots, and in particular, freezing in YouTube. Sound would get stuck (sort of D-D-D-D-D-D) and the only fix was to Vol-UP and Power.

I've posted a video showing the freeze. You can hear the sound studdering, and see that all buttons are negative response: only rebooting fixed. Pandora was playing in BG and Astro was in forefront. Here it is:

For some reason, the YouTube tags not working for me but here's the URL:

http://www.youtube.com/watch?v=nSN1wOZjSdA&feature=youtu.be

Since then, I've switched to Rogue Recovery, and tried every nightly up to #126 and Gapps 802. I've done the full wipe and formatted system each time to be sure. After this last go, I have not even started any streaming apps, just sitting in Astro at the folders view, and have seen two reboots so far. I've double-checked to be sure I'm running at 1000 MHz and not OC'd in error.

What possibly could I have done wrong I wonder? Anything to try, or just keep bumping nightlies?

All is appreciated. :D
[Xoom Android Development] Draxin:
I am not having it as frequently as you but, yeah, I am still having reboot issues. Since so few have had issues since 125 with the kernel fixes(which slowed my reboot issues down alot), I have pondered if possibly it is down to individual devices that are having problems now. How certain xooms can do better at different OC's than others. Their saying that jb is getting to the limits of the xoom.

I am the first to admit that I don't know jack about jack though. :D

Kcrudrup had asked that anyone having reboot issues should pm him, that he has something for us to try.
[Xoom Android Development] Asphyx:
Yep I pretty much read the changelogs everyday and only fash more than once a week if the one I decided to flash shows instability.

I have only seen one random reboot in Nightly 125 and it was again during video playback but the video wasn't playing at the time of the crashed (it was paused for a phone all) and while in pause the unit rebooted.

But I have not seen any other random reboots other than that one.
[Xoom Android Development] bigdave240:
Sort of funny, as i was reading this post it rebooted. Only had the browser open with about 5 tabs on it. Running 126 :crying:
[Xoom Android Development] LesismoreTN:
Oops, hope I didn't jinx you!

I agree about the OC'ing, that's why I checked. I've had no issues running up to about 1500 on HC and ICS. Since I'm not sure about this particular kernel, I've stuck with 1000 MHz.

Tomorrow's another day closer to perfection!
[Xoom Android Development] wesamothman:
This is working YouTube version with signature modified. Uninstall the one you have, install this one, YouTube seems much better with is one.

http://www.mediafire.com/?m05du99p7sj20wh
[Xoom Android Development] bigdave240:
Interesting, goo.im doesnt show 126 anymore? Must still be doing maintenance there. Dl count is at 0 for the two roms it shows.something else i noticed is that when it did reboot my max speed was reset from 1504 to 1000.
[Xoom Android Development] wesamothman:
Download mirror provided by solarnz.

http://mirror1.teameos.org/roms/eos3/nightlies/stingray/
[Xoom Android Development] kcrudup:
Nah, just leave your caches be.

Really. If the Framework thinks they need to be redone, they'll wipe and rebuild them on their own ("Android is updating apps"). It should only be necessary as a last resort (i.e., the machine instantly reboots upon first boot, or immediately returns to the Boot Animation, or apps immediately FC or don't come up at all).

Ditto wiping, unless you're coming from HC. I'm just trying to spare you guys from unnecessary wiping and (Now, that being said, for those who don't mind wiping I've got a filesystem change for /userdata that requires wiping, but will speed up access to the flash and reduce lag, sometimes greatly. Stay tuned, as I'll be announcing that in a day or so after I button it all up and make it ready for Prime Time).

---------- Post added at 07:02 PM ---------- Previous post was at 06:33 PM ----------

So, about the reboots: For the longest time (around October '11), the TeamEOS kernels for the Xoom have been overclocking the GPU from 300MHz to 400MHz; it worked great and we never really got anyone complaining about it. Right around the time we got JellyBean, however, we ended up in a "perfect storm" of video issues: (1) apparently JB uses the GPU far more than ICS, putting more strain on it at 400MHz, and (2) I'd added into the kernel an optimization that came from NVidia to remove a CPU<->GPU synchronization aid that was deemed unnecessary (and probably innocuous under ICS) with a standard-speed GPU.

So, some of you guys got spontaneous reboots (especially when watching YouTube, with certain animated wallpapers, and/or watching videos), and eventually, so did I. After tracking it back, first I'd turned down the GPU speed back to 300MHz, but that didn't fix it for everyone, so I reverted back the NVidia patch, and at the same time turned back the GPU speed to 400MHz- unfortunately, that fixed one possible reboot source but brought back another.

So, it's now obvious that we've got to be stock-clocked in the GPU for JB now, so we're going to revert back to that. I've known this for a couple of days, but haven't pushed the change until I'd not only tested it on my own Xoom (as I did continue to see reboots myself before my fix) and to verify that there were no other isuses (as I've upgraded the compiler for- and the way we build- the kernel).

Look for a permanent fix in the next day or so. In the meantime, for those I've asked to PM me if you're seeing reboots, I'll have a link up soon for a boot.img that you can "fastboot flash boot" on (unfortunately, no update.zip-able image).

BTW, if you're a Benchmark Whore (like me :)) you'll notice ~20% or so decreased scores in graphics-based testing. I'm gonna miss my 29.8 NenaMark score, but I'd miss stability while watching YouTube even more!

I thank you guys for sticking with TeamEOS throughout all this, and be assured that quality and stability is always Goal #1 with us, as if it doesn't work, y'all won't use it.

(TL;DR: I know what the problem is, have fixed it, and you'll all have it soon.)
[Xoom Android Development] SamuriHL:
Awesome man. Thanks for that!
[Xoom Android Development] dboftlp:
There's a button for that :)

I'm rockin EOS 3 nightlies on my LTE Xoom.
[Xoom Android Development] SamuriHL:
Yes, and I clicked it. ;)
[Xoom Android Development] Asphyx:
I know JB and project butter specifically uses the Vertical Interval (probably controlled by the GPU) to get some of it's butteriness to happen.

So it makes sense that it would require the CPU and GPU to be in lockstep and synced in some way no?

Just glad you know all about it. The latest setup seems to be pretty good with only occasional blurps here and there.
[Xoom Android Development] cydetrakd:
Thank you Team Eos for your hard work put into Eos3 it is smooth, stable and getting the majority of the features i loved in your Hc & Ics roms. My have we come along way i remember flashing the first 4g Hc rom and fell in love since day one. You guys were also the first ones to support Ics and now Jb is coming along nicely with improvements all the time.

I just flashed B127 and it is really nice to have the soft key customizations especially back to kill on long press which i found myself doing all the time since i was so use to it for months now great that it works now lol. I miss the long press for reboot into recovery but the custom app addition is very nice since i can hold down my Home key for the Drive Docs which helps me keep up with my Diablo3 auctions lol very handy. I couldn't be any happier :cyclops: . Team EOS donations coming your way once i get some paypal cream from D3.
[Xoom Android Development] sovereign_313:
:D

W00T! 128!
[Xoom Android Development] bigdave240:
only had 128 for a few minutes but it seems ok so far. will try to stress it out a bit but if kcrudup says its fixed i will take that to the bank. LOL.
[Xoom Android Development] REHolt218:
After posting a description of my wonderful battery life back on 125 I'm afraid I have to join the ranks of those with battery issues.

On 127 and now 128 my battery usage has taken a major dive. I have not added any new software, although there may have been some app updates. On 125 I went around 23 hours with moderate use of 4g and wifi and still had over 60% battery. Today I have only had it off the charger for 7 ½ hours and I am already @ 58%. A good bit of that time has been with the radio's turned off.

I will download one of the recommended battery monitoring apps and see if I can pinpoint an app problem. The battery screen under settings doesn't show much.
[Xoom Android Development] Motawa88:
can somebody tell me why german not works with voice? it understands me but it does not respond(only google search)
[Xoom Android Development] kcrudup:
Well, I found yet another problem, so I'm gonna have to put a one-day hold on that deposit before your funds become available :eek:
[Xoom Android Development] bigdave240:
You da man!
[Xoom Android Development] Asphyx:
Did you download the German Language pack for GNow?

So does that mean the Video patch is in 128 but you found something else?
[Xoom Android Development] Sandso9:
Is there any mirrors for 128 goo.im is extremely slow for some reason =/
[Xoom Android Development] kcrudup:
Yes. It's embarrassing for me (I'll post the gory details of what this other one was, once I verify I got it this time), but yeah, I have another fix.
[Xoom Android Development] thingnblah:
Perhaps too early to tell for sure but 128 is smokin fast!!!
[Xoom Android Development] kcrudup:
As of 128 the Linaro ARMv7 optimized string functions are in, plus now we build Android optimized for the Cortex-A9 architecture of the Tegra2. Enjoy :D
[Xoom Android Development] wesamothman:
Here is download mirror provided by solarnz,

http://mirror1.teameos.org/roms/eos3/nightlies/stingray/
[Xoom Android Development] Sandso9:
Omg awesome thanks!!!
[Xoom Android Development] TheRandom1:
I don't think I mentioned this lately, but I sure do love this ROM. You guys on Team EOS are fantastic! Especially your honesty. I don't care if something gets messed up, crap happens but instead of ignoring the issues, you guys (and/or girls, who knows) own up, take credit for the issue and get it fixed.

So for that, and all of the great things you guys have done, I say thank you! (and keep it up, please!)
[Xoom Android Development] electroman987:
I have had a great experience coming from eos ICS nightly 100 to jb nightly 127.

I used eos recovery: backup, wipe user cache, wipe dalvik cache, install.

No reboots, no freezes (although I haven't used YouTube or any other streaming apps), etc...

Great experience so far.

Thx eos for your great work.:D

Edit: my only issue so far is not having access to my external sd...

Using root explorer paid.

Any suggestions?
[Xoom Android Development] TheRandom1:
What are you using to access your external? It moved from ICS to JB, so your app probably is still trying to look in the old area. It's been covered a few times in this thread.
[Xoom Android Development] bmhanson:
Do you not see it in /storage/sdcard1 ?
[Xoom Android Development] Asphyx:
Embarassed should not enter into your head unless you hadn't found it! LOL

Nice to hear Linaro has been incorporated now if Goo could just get thier upgrade done and make your life easier! LOL
[Xoom Android Development] razorseal:
thinking if I just wait couple more days and by monday we should have something that has most stuff working.
[Xoom Android Development] serranom:
That is awsome that worked.. I just have to be patient and wait for the devs... :D

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] razorseal:
:)

ok, it shows vzw, and even shows '4g' but as soon as I disconnect wifi, i loose vzw, and i get 'no internet connection'

:confused:
[Xoom Android Development] bigdave240:
yup. thats all you get for now. they are working on fixing that for us. but the radios are recognized now.
[Xoom Android Development] wILLRoiD:
does it work on 3d gsm eu xoom?
[Xoom Android Development] Tom_S:
I have the issue.
[Xoom Android Development] razorseal:
ahh ok...

---------- Post added at 02:41 PM ---------- Previous post was at 02:34 PM ----------

ok, 2 more things I realized. perhaps they've been asked, but I didn't see it

1. gmail will not pull my inbox... just say no conversations. if I go to all mail, I do see emails.

2. I can't find youtube in market??

---------- Post added at 02:41 PM ---------- Previous post was at 02:41 PM ----------

they found a fix for this I think. read back a little bit, should be there
[Xoom Android Development] atlmatt:
http://www.mediafire.com/?ligfqo1mpwk1cag

You tube apk 720p HD playback
[Xoom Android Development] twinkyz1979:
I would really appreciate it if someone could fix the mount issue with the power button menu mod. I think others would really appreciate too. I removed the link on all posts i could find and edit because of the problem it caused.
[Xoom Android Development] yankele:
So just to make sure, no team EOS softkeys recovery right?
[Xoom Android Development] johnny0911:
I think goo inside me is down, I have tried the links and app nether are working.
[Xoom Android Development] bigdave240:
Yup. down for me too.

edit: never mind. its back up now
[Xoom Android Development] jawonder:
No 3G/4G and Google Now force closes, hope these get fix soon so i can come back on it. Thanks OP.
[Xoom Android Development] cadiken:
Dude, Google Now works. Delete the folder /system/media/video then re-flash gapps. BRD is working on the 4G and might have that fixed tonight. I'm enjoying this soooo much.
[Xoom Android Development] johnny0911:
Good to go, jb is running great aside from the obvious beer is on me team EOS. Thank you
[Xoom Android Development] razorseal:
How do you launch google now?
[Xoom Android Development] serranom:
The app Google in apps but u have to delete the video file like it says couple post back and reflash gapps

XOOM running EOS Nightly JB

If anything helped you, remember to THANK that person.
[Xoom Android Development] bigdave240:
Did you have to change the permissions to delete it? Nothing i have give me a delete function.
[Xoom Android Development] jawonder:
Yup that did it Google now is working fine . Thanks bro .
[Xoom Android Development] edjm711:
You can also launch it by swiping up on the lock screen or the home button.
[Xoom Android Development] bigdave240:
Since flashing 128 i have had my xoom go into a stuck state twice where it looks like it has gone into standby but wont wake up and gets hot like it is running something while i. In that state. Only way to wake it has been a reboot. Anything you need me to look at?
[Xoom Android Development] Draxin:
I would have to second that, you guys are doing developmental builds to create fantastic ROM's, there are gonna be kinks to be worked out. Keep up the great work guys!!!!

---------- Post added at 09:02 AM ---------- Previous post was at 08:32 AM ----------

I personally am sticking with 127 til Kcrudrup tells me which .zip he wants me to try, or sends me a fastboot image. 127 Has been the most stable of the bunch for me so far, and all good things come to those who wait :)
[Xoom Android Development] bigdave240:
[QUOTE

I personally am sticking with 127 til Kcrudrup tells me which .zip he wants me to try, or sends me a fastboot image. 127 Has been the most stable of the bunch for me so far, and all good things come to those who wait :)[/QUOTE]

Naw. I have been a beta tester since win95 and love trying out what the devs release. They need the feedback so they can fix what is found. But i understand wanting to stay with what works too. just a personal decision.
[Xoom Android Development] kcrudup:
<grumble>

Yeah ... next time this happens, if you have "adb" can you do:

adb shell vmstat

for about a minute or two and send me that output? I know exactly what happened, I'll bet- you were caught up in an "I/O Storm", and the machine never got to service your PowerOn request before the screen-off timer kicked in (so the screen never came on). Your machine was probably running just fine, otherwise.

The other thing I'm working on lately is fixing lag caused by a combination of our using a relatively-older kernel (2.6.39.4), our slow EMMC flash disk, and believe it or not, not enough RAM (732MB isn't really enough anymore as the size of the OS and Apps increase to fill the vacuum).

Have you noticed that when the Xoom first boots, everything is so fast, then after a while, things start to slow down? Well, what's happening is that when RAM begins to fill with Apps, libraries and disk data, the system does what it can to page out memory that's not needed (disk-cache data that hasn't been used in a while, parts of programs that haven't been executed in a while (which can be reloaded from disk if necessary) and if all else fails, there's a "low-memory-(app)-killer" that runs in the kernel and forcibly shuts down apps (this is the reason why sometimes you'll switch back to a large-memory-footprint app like the Browser, and the tabs will all have to reload).

A lot of that involves what's called "paging" back and forth from the EMMC flash disk. When the stale data gets written out, we're doing writes to the flash filesystem- and those operations can take a LONG time (relative to the speed of reads, and of the CPU) and because of the way the flash disk works, while that slow write is happening, no reads (which are a lot faster) can run- so when the memory starts to get full of running programs (and/or is doing a lot of I/O (especially write I/O)) the system ends up slowing down:

- dirty data is being written out, while

- new programs (or parts of programs that were paged out and now need to run) are being read in, while

- the system is spending CPU cycles trying to scan memory and free blocks

so we end up in a condition called "thrashing". I've been spending a LOT of time trying to reduce this as much as I can: I've been working on doing ANYTHING I can to get the write thruput up, and have been tweaking both the V(irtual) M(emory) parameters and the I/O Scheduler parameters in an effort to keep the number of random writes down, to prioritize reads over writes, and to avoid "I/O Storms", where we spend a lot of time hitting the flash disk.

it's a lot of work, mostly due to the limitations of the device and kernel I have to work with, but it's coming along. Unfortunately, it still hits me, too (I can't run "Google Earth" with Hi-Res images and sync "Google Currents" at the same time without running into the same issue you do) but I'm making progress- I've got unreleased patches that are working much better than stock, and as soon as I'm satisfied with them, they'll go into a nightly.
[Xoom Android Development] bigdave240:
Awesome explanation ! I will do adb if it happens again.
[Xoom Android Development] brittoking:
Anyone able to get Google music working on these nightlies? I can get a "play library" widget with options like "my library/videos/play store/etc" but when I choose the Google music headphones icon I get "play store has stopped" message every time and the widget is then completely unresponsive? I've tried deleting the app and side loading the apk but it won't install and the play store itself says Google music is not installed but then gets an error when I try to install it? Sorry for asking again guys but I love me some music and with EOS roms there's so little to complain about I thought I'd ask! Lol ;)

If I happen to be of help to you, please hit THANKS, as I have low self-esteem and crave validation! Running TEAM EOS ICS
[Xoom Android Development] Moricon:
Sorry but I am not having issues. On 128
[Xoom Android Development] bigdave240:
I had heard of a couple of others with this issue and a search turned up your posts but also someone else who fixed theirs by deleting the updates to play. Take a look at post #606. Hope it helps
[Xoom Android Development] brittoking:
Thanks for the response. I too saw that post but when viewing my apps in settings I'm not given the choice to remove updates to the play store? I can force stop/disable (which I did with no luck trying the widget then)/clear data/cache. Tried all of the aforementioned options to no avail though. I'm currently on 128 running the latest gapps from 7/26 I believe. I hesitate wiping the entire device and starting over because of the A: amount of games/data and apps installed and B: I don't really see how wiping would fix the issue technically? Thanks again for the response(s)

If I happen to be of help to you, please hit THANKS, as I have low self-esteem and crave validation! Running TEAM EOS ICS
[Xoom Android Development] bigdave240:
The latest gapps is 802. http://goo.im/devs/teameos/roms/eos3 save that as a shortcut and you can easily get to gapps or nightlies. I wonder if you need to format \system then reload gapps. You could (and should!) do a nandroid backup the a factory reset to see if it clears your issue. You would then at least know it is something that got corrupted and could either go back to the nandroid you saved or reload your stuff and move forward.
[Xoom Android Development] sovereign_313:
*scratch scratch* so uh... I've had two mornings of no rom flashes *scratch scratch* what gives? *scratch scratch scratch*

:eek:

Sovereign
[Xoom Android Development] TheRandom1:
Have you rebooted your Xoom? I've found on this (and my rooted/ROM'd Revo) that if i don't reboot, apps won't update and Goo won't tell me I have a new update.
[Xoom Android Development] sovereign_313:
Well, I'm not seeing them in http://mirror1.teameos.org/roms/eos3/nightlies/stingray/ or http://goo.im/devs/teameos/roms/eos3/nightlies/stingray, so I'm guessing it's not that :(
[Xoom Android Development] bigdave240:
Patience lol. The "nightlies" aren't necessairly nightly.