yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] masterslacker:
Thirded! Since build 128, apps sometimes hang for a few seconds and then I get the "xxx is not responding. Do you want to close it?" message. Typically I just hit "wait" and things resume as normal. In a blue moon, the system just hangs and reboots. I had no issues while I was on 127, so I wonder if there were some proprietary drivers introduced around that time that might be causing a problem.
[Xoom Android Development] burt_ie:
Still the same here, after a few minutes if Youtube it freezes, makes a strange noise and then reboots :(

I am not sure if I should do a full wipe (factory restore) and try a fresh install of the latest build....?
[Xoom Android Development] eddyther:
I think that it is due to a YouTube incompatibility, because all the rest is working ok, and the Xoom is very smooth.

But who knows...
[Xoom Android Development] burt_ie:
I just done the two wipes from recovery, cache and delvik cache (not the full wipe factory reset option) and reinstalled build 133 and gapps-jb-20120802... just played YouTube for a little bit and all seems good again now. :)

I guess these are just teething problems... but Team EOS is still the best :D
[Xoom Android Development] kaneelias:
Have just flashed 133 and Gapps 20120802 and when trying to download any app from the Market I am getting the error

"Error, Update for XXXXXXX could not be downloaded due to an error. (Error retrieving information from server. [RPC:AEC:0])

Am I the only one with this problem? Just trying to work out if it's me or the Playstore.
[Xoom Android Development] waz675:
I was getting youtube freeze reboots before. I deleted it, downloaded the playstore version and it's been running for the past hour playing stuff that was rebooting yesterday. All going good, try this maybe?
[Xoom Android Development] kaneelias:
OK, pain in the ass. I had to delete my google account and add it again and now all seems to be working fine.
[Xoom Android Development] istrait:
Same here.... 129 was blazing and it just slowed from there.... Same system freezing thing...
[Xoom Android Development] DrGreem:
Lol sorry guys the link is this one:

http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos.zip

but it's broken!!!! Yesterday it was ok..
[Xoom Android Development] solarnz:
Temporary download mirror at http://mirror1.teameos.org/roms/eos3/nightlies/
[Xoom Android Development] TomaszD84:
OK, I'm sorry in advance for asking this, but there is so little information I'm a bit confused.

I have a stock MZ615 (EU), is there any alternative ROM I can use at all? The stock one is awful.
[Xoom Android Development] xoom68:
Do you know why some of us feel like its gone a little clunky....I think the majority of us have wiped/formatted system etc.

I just see pauses when clicking an icon on the screen to things opening, selecting close when it says various apps are not working. I look at the change log but can't see a lot happening for the last few builds, so I am unsure what is going on. Was it the oc GPU and a different kernel in earlier builds that made it more fluid ?
[Xoom Android Development] okantomi:
I think it got a bit clunky when they got rid of the overclocked gpu. I really have felt a difference. I ran an older kernel for a while, but stopped. The current EOS kernel is great and fairly smooth, but I miss my oc gpu.
[Xoom Android Development] xoom68:
Well I just put 119 on (it was the oldest one I still had on here) and apps are starting a lot quicker and updating a lot quicker. And I've only tried this, FB and messenger. I would see the tinge round the icon for a second and wait for the apps to start, in the case of messenger it would take an age to refresh, and indeed this app would take forever just to display this one favourite topic.

All I did was format system and wipe dalvic/cache same as 133, but this has the oc GPU and seems to make all the difference at this early stage. ?
[Xoom Android Development] Motawa88:
hd videos on youtube and .mkv are laggy.

@xoom68

could you upload the 119 build?
[Xoom Android Development] xoom68:
Sure...here is build 119.

http://www.2shared.com/file/Ge1j5QXT/EOS-wingray-20120714-119.html?

Don't know about YouTube as I don't use it, but this seems a lot better for my needs. :)
[Xoom Android Development] RoWeKo:
Laggy keyboard

I'm using 133 with any problems so far. But what I realize is that the keyboard (stock) is laggy and doesn't respond as quick as I'm typing. So I do a lot of misstyping.

Any1 else?
[Xoom Android Development] Motawa88:
thank you.

just installed the 119. it it is WAY more smooth than the newer onces.

got grahic glitches on gta 3 with 119 though

nova 3 is very laggy on every build. is the tegra 2 to weak?

is it possible that the overall performance (os and games) will improve with future builds? or do we got the maximum performance with tegra 2 on jb?
[Xoom Android Development] nadiros:
AFAIK the kernel has had gpu OC for the last few builds. I have had no issues besides a hiccup...seriously as with ANY custom ROM nightly build if you have issues then full wipe and see.

-No sh*t- JB is so early in development that CM and AOKP have yet to release official nightlies, even for Gnex which has tons more support.
[Xoom Android Development] xoom68:
Are you sure don't think so, I looked at the GPU info on 133 and no mention of it, but this build does.

This clarifiys when it changed

https://review.teameos.org/#/c/851/

Of course you are correct about builds, but I kid you not, this is a big difference....lag has gone on a few things just feels better....
[Xoom Android Development] Northantrim:
Running build 133, and I have noticed that Google is now like ICS..

http://www.imgur.com/EQRh9.png

The Google shortcut has also disappeared from the lock screen :confused:
[Xoom Android Development] scottgti:
I am flashing 134. Longest flash ever! Stalled at about 66% on the progress bar. Finally finished. :)
[Xoom Android Development] elsworth1983:
Hi can you drop a link up Goomanger says The file you requested was not found ? My bad didnt read back a post Soz

---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------

for 134 use this temp link http://mirror1.teameos.org/roms/eos3/nightlies/wingray/ What solarnz put up
[Xoom Android Development] NoP_Compiler:
Hi.

I 'unlocked' my xoom first time a few weeks ago. I flashed v127 just because it was the latest release available.

I'm not sure if I've been lucky because after v127, almost are reports are about FC's, crashes, etc...

I'm a bit scared now about updating from v127... I know this are nighlies (development) versions, but is there any way to know if a given release is more stable than the latest ones because devels have fixed previous known bugs?

Thanks anyway to Team EOS for the good work.

--
[Xoom Android Development] scottgti:
I just went back to 127 from 134. Everything I use is working great.
[Xoom Android Development] wingnutta:
TeamEOS has disappeared from developers section!!! :(:(:(:(
[Xoom Android Development] lorenza:
There are no files listed on Goo for download...

Never mind....failure to read!
[Xoom Android Development] xoom68:
Go back a page...on this thread.

http://mirror1.teameos.org/roms/eos3/nightlies/wingray/ Thank solarnz not me :)
[Xoom Android Development] uzi2:
You can't have given 134 much of a chance. What was the problem? Everything I use appears to be working well on 134.

Swyped from my Xoom
[Xoom Android Development] scottgti:
I gave it very little chance. 1 reboot and a few super slow downs- including a few "wait or close". I'm not blaming the rom, I've been on eos for a long time, but 127 has no problems for me. It may be rogue app or something else, but it doesn't affect 127 for me.
[Xoom Android Development] Motawa88:
will there be any performance issues if i do a backup from 127. install 134 and then backup back to 127?
[Xoom Android Development] Tomcar:
Format System first in CWM Menu, this will do no harm to your data.
[Xoom Android Development] bossjeeves:
also experiencing the same issue, not sure which release it started with but it starts speeding up after a few words are typed ( I use the thumb keyboard though)
[Xoom Android Development] uzi2:
You will have to bite the bullet and do a clean install at sometime, otherwise you will be stuck on your 127 backup.

I'm sure you know the drill... clean install - restore half the apps etc.

Swyped from my Xoom
[Xoom Android Development] xoom68:
Sorry to jump in here. But this makes no sense to me (not an Android Guru me right enough). But how can I/him, and definitely in my case go from 133 and think hold on something is not right, and go all the way back to 119 and everything be better, I have done all night lies inbetween.

This wipe mentality IMO only slows down the reality that things are getting better, because by the time you put all your apps back on its time for bed. :)
[Xoom Android Development] scottgti:
I didn't use a backup. That is what I find strange. I downloaded 127, wiped system, and flashed it again. I'll wipe it soon, for now it works great.

---------- Post added at 01:18 PM ---------- Previous post was at 01:08 PM ----------

This ^^^ is why I went to 127. I am having the same experiences. If only there was a nexus 7 bug that crashed all of them for a day, I think all would be resolved. :)
[Xoom Android Development] wingnutta:
TeamEOS has disappeared from developers section on goomanager :(:(:(:(
[Xoom Android Development] elsworth1983:
Hopefully this is Just a glitch fingers crossed the appear back on
[Xoom Android Development] scottgti:
Relax. Goo is going through updates, which is why we were given an alternate download site, already pointed out multiple times.
[Xoom Android Development] Motawa88:
can you guys tell me where to get 127?
[Xoom Android Development] scottgti:
http://jenkins.teameos.org/job/wingray/127/
[Xoom Android Development] Motawa88:
also noticed that the latest episode of breaking bad in HD runs smooth on 119 and lags on 130+

also, is it normal when games like gta 3, ganster rio, nova 3, modern combat 3 lag alot? or i i have to get a tegra 3 device for this?
[Xoom Android Development] Northantrim:
I also have noticed my tablet performing quite sluggishly the past few builds. Happens mostly on the home screen when moving shortcuts and widgets around and a few other places.

Also had then problem I posted here. Downloading 134 now, will see if that improves anything.
[Xoom Android Development] Motawa88:
waiting for a douche to tell us that is is just BETA and we have to shut up, not getting that we are in fact NOT complaining....
[Xoom Android Development] Northantrim:
Yeah, we aren't complaining, we are reporting. Also, we all knew to expect bugs etc before we even tried this.

Running 134 now, still lags, even in the welcome screen :confused:

Also, I forgot to TB everything before wiping..grr.

Edit: getting market error RPC:AEC:0. Done all the usual, clear data, cache and reboot.

Edit: seems to work now that I've added my alternative Gmail account.
[Xoom Android Development] elsworth1983:
Cheers again Team eos flashed 134 and its running smooth had no reboots and no Lag Loving my Xoom :laugh:
[Xoom Android Development] xoom68:
You need to switch it on after flashing it you know... :)

But honestly there is something up here. I think you have to go back to an earlier version with the OC GPU to see what I mean, you would be surprised how much quicker it was. But if you are happpy with it..who am I to judge. :)
[Xoom Android Development] elsworth1983:
:) The last time i had a reboot was 127 or 128 with youtube i just removed youtube and reinstalled it My GF plays $hitty Sims and a load more rubbish games when she is not at work but if there was a problem with it she would let me know :)
[Xoom Android Development] wesamothman:
Hey guys, team eos is doing great job developing these nightlies and every build has more features and enhancements than the prev one. So don't be scared. The only serious issue that popped up was streaming thru YouTube and that is not Ron issue at all. It is YouTube issue updates even on ICS .

To enjoy best stable latest release, do this,

Go to recovery,

Wipe data,

wipe cache,

Wipe dalvik,

Format system,

Flash latest ROM,

Flash latest gapps,

Reboot.

Go to YouTube and uninstall it if it exists, and then install this version, 4.0.8E

So far m this seems to solve you tube streaming issues and force closes.

Running great so far with no issues.
[Xoom Android Development] xoom68:
I don't know why people keep talking about YouTube and reboots. :)

A lot of us are having general problems and noticing it is not the butter it once was, more like treacle for me, and I am talking from clicking on FB/FBMessenger/Stumble/This app, Play....taking longer than it normally did to start and display Info stuff like that.

I could flash my mother in law and wipe my own butt with sandpaper, and it would not help.

If you look at the build data, some Versions have nothing noticeable done, the last few have different kernels, standard GPU from OC GPU, new Jellybean update from a leak and other stuff I have no idea about.

All some of us are saying is that there is a definate tangible/visible difference to the "butter" that everyone was talking about Initially.

Am I blaming anyone, nah, I have went back a few versions to see if it made any difference, now if I don't need to do a full wipe to see the difference, but I do to go forward...please explain how that works.

Do I love this ROM and the work EOS are doing, you betcha, all some, including me are saying is earlier builds were smoother, nothing less or more. :)
[Xoom Android Development] Northantrim:
Even if my device lags a bit here and there (seems to happen very little now :D) I'd rather have this ROM with Jelly Bean than stock with Gingerbread / ICS! So keep up the good work.
[Xoom Android Development] bigrushdog:
Just because I don't respond to every "zOmG hAlP" doesn't mean i've disappeared or anything else. I consistently spend about 30+ hours a week developing android. I see all the boards, listen on all the chans.

This is the link for our merge history the last couple weeks.

https://review.teameos.org/#/q/status:merged,n,z

I don't see anything that would even remotely cause the lag some users are reporting. My personally advice is to run with only the apps you really need. The xoom is rather dated at this point and honestly it barely has the guts to run Jellybean. But we'll keep at it until we find a blend that works. If you think a prior build ran better, run with it. Do what works for you.
[Xoom Android Development] elsworth1983:
Just like to say a BIG THANKS for all the work you and team eos put in I said it before and I will say it again thanks to you guys my UK Xoom gets jelly bean when Motorola have only just pushed out ICS hate to think how many years it would take them to push jelly bean out to the uk . Me personally I don't think they will. :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:

Sent from my Xoom using team eos jelly bean :)
[Xoom Android Development] Smokexz:
My Xoom crashed on 133 when streaming Netflix. While streaming Netflix it also constantly freezes for a second.

Sent from my Xoom
[Xoom Android Development] Scolis:
Is it me or is Team Eos missing on Goo?
[Xoom Android Development] elsworth1983:
Go back a few pages a backup link is up

Sent from my UK Xoom using team eos jelly bean :)
[Xoom Android Development] ggrant3876:
+1, awesome work guys.
[Xoom Android Development] waz675:
Going to d/l 134 now, just waking up atm. 133 etc has been smooth for me although I am using apex beta launcher, that may be helping my side of things though.

Only issue of late was youtube freeze then reboot after a lot of streaming but was fixed by deleting it and d/ling from playstore. Possibly a cache wipe could have fixed it, didn't bkther though. Happy as it all works now from a 30 second at the xoom fix.
[Xoom Android Development] elsworth1983:
Just tried stock JB and all i can say is Team Eos Jelly bean is 1000xs better :silly:
[Xoom Android Development] iruiz2:
Damm, I am getting some reboots usted watching some files on mxplayer... Happened already 3 times tonight, I'm on 132+gapps
[Xoom Android Development] elsworth1983:
Have u tried 134 :)

Sent from my UK Xoom using team eos jelly bean :)
[Xoom Android Development] eddyther:
On 134 I still have crashes.

I think that the origin of our troubles is that flashing one nighty after the other is leaving traces, or garbage that the normal wipes cannot solve.

On the other side I don't see myself doing a full wipe every time that I install a new version, so the question to Solarnz and the other developpers is:

Is there an alternative and effective way to install a new rom without wiping everything?

I'm almost sure that the wipes are in the origin of 95% of our malfunctions and troubles (the other 5% is due to some apps, like YouTube, and rom´s bugs)

Every time that I have slow downs, crashes and reboots, a full wipe solved the problem, so the key is there.

The point is if there is a practical and simple way to bypass this.
[Xoom Android Development] fidju:
Have you done a full wipe yet???

---------- Post added at 03:22 AM ---------- Previous post was at 03:21 AM ----------

Just use Titanium Backup and do a full wipe. It isn't that hard.
[Xoom Android Development] elton.de.nascimento:
Since build 128 I don't make any wipe ..now I have 134 and at this moment every works fine.
[Xoom Android Development] waz675:
Full wipe (if you don't format /system) means nothing more than a 'dirty' upgrafe except wiping app and user data. This points to that probably an app or user data is causing slowdowns etc. Look at what you install/change. True full wipe is formatting /system to remove the actual system stuff.

Just in case you aren't formatting /system.
[Xoom Android Development] runandhide05:
ok, im going to chime in here.

the "wiping of cache, dvlk, and formating of the system is not necessary, its is completely redundant,

For those of you that know a little more about android and the workings of an update zip ( the files you are flashing )

with out an update script nothing would flash,

This update script is what tell recovery exactly what to do, where to put what and so on,

it has been stated by solanz and bigrushdog several times that that script contains everything needed to simply flash and forget about it.

here is a little explanation of how this works,

inside of the zip contains a updater-script

inside the script..

run_program("/tmp/backuptool.sh", "backup");

which takes all the gapps and puts them in a nice cozy temp location and then followed by

format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");

That takes care of formating the system

then all the set_perm ( sets all the permissions to the correct value)

followed by restoring all the gApps.

finally the boot image

package_extract_file("boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");

so, basically all you have to do is simple flash the zip, thats it. these guys know what they are doing, and are VERY skilled at what they do, it is almost fool proof.

now, as for a full wipe, aka a factory reset.

all that does is formats the /data ( while not formating /data/media ( internal memory aka internal SDcard)

so if you are having problems and you think it may be because you did a "dirty install" odds are thats not it, there is probably something in /data that is causing the wonkyness, * Note that restoring anything with any restore app would place potentially ill causing apps and/or data on the /data that was causing the wonkyness to begin with.

im not jumping any one in here, im am simply attempting to further educate some that may not have known this, or possible forgot this information.

*edit forgot to add that the dlvk and cache is rebuild on boot if it has noticed any change in any of the updated apk/files/libs and so one. thats why wipeing cache and dvlk was included on the redundant list at the top of this post, i just forgot to explain why.
[Xoom Android Development] DefinityX:
Absolutely fantastic write up. I always worry that some just follow whatever walkthroughs they stumble on, not really understanding what all is involved, or what all they are really doing...

Which is really just a testament to how easy TeamEOS makes it for us. ;)

Unfortunately, in another 2 pages, and there will be another 4 people asking about which/what wipes to do when and where. :facepalm:
[Xoom Android Development] thdj:
Since build 128, I'm also having crash on my Xoom playing video files either with mxplayer or built-in gallery player. The last working build for me is the 127 one. 134 is still crashing the xoom :-\
[Xoom Android Development] elsworth1983:
This is so True :silly:
[Xoom Android Development] Eun-Hjzjined:
What w1pes do I have to do f0r a butter e0s exp3r1anc3?.....

Theres one.
[Xoom Android Development] rpete76:
@runandhide05 Thanks for the guidance, very informative. I take everything you have said on board but what confuses me is that if the issue is app related, and I am not suggesting it isn't, is why I can flash back to a previous build and everything runs great? Same apps and no crashes in streaming video and no slow down in general use. As soon as I upgrade to 128 or above it just doesn't feel as responsive and media reboots my Xoom.

I will continue to test it out as much as I can to see if I can narrow it down and will post whatever I find.
[Xoom Android Development] xoom68:
It's also like saying, the Xoom is great with JB....just don't use it. :)

All joking aside it's too easy to make fun of new people with what wipes, but there are people here with their rituals and lucky wipes that swear it makes all the difference, so you can't blame people asking on what or what not to do.

Well 135 seems OK so far... :)
[Xoom Android Development] elsworth1983:
Cheers again team eos DL 135. Good to see goomanger is back up and working :).

Sent from my UK Xoom using team eos jelly bean :)
[Xoom Android Development] fleury14:
Haha "rituals". I used to be guilty of that as well until I read somewhere that my biggest problem was titanium backup. While I still use it for restoring games/progress it's much better to take the time and reinstall other apps without the data which was messing up certain roms in the long run.
[Xoom Android Development] Taysider:
Uploaded 134 then 135 came along. I must say that the eos team are doing great work and the only problem I had was of my own making. Forgot to install the latest gapps. Which works great once latest version done. YouTube works great and have not noticed any lag. The stock keyboard is crap compared to swype or go keyboards. Congrats to EOS TEAM :D
[Xoom Android Development] emd2009:
Where can I find the latest gapps
[Xoom Android Development] eddyther:
[QUOTE

---------- Post added at 03:22 AM ---------- Previous post was at 03:21 AM ----------

Just use Titanium Backup and do a full wipe. It isn't that hard.[/QUOTE]

I know, thanks, but you only get your apps (with our without their data) back. Nothing about the general configuration, placement of the icons and widjets and so on...

Anyway, what I wanted to say is that only a full wipe will solve the problem to those having issues.

Those issues are generally related to the garbage that the normal wipes cannot erase.

About installing a previous nihty and going back to normal (like some users and myself did), I have no explanation to give, but sometimes it works!

Thanks to all the devs, because they do a great job. The problem is that they produce to many mighties :) and we want to flash all of them!

(Is this really a problem?...)
[Xoom Android Development] nckgarvey:
I hope no one minds me doing this, but with the problems people have been having with goo.im and downloading builds, I figured I would download and host it on my dev-host account as an additional mirror.

Dev-host mirror - wingray nightly build135

DISCLAIMER: This download is NOT my work, I just want to help out where I can.​