yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Alxoom33:
no, wiping System will not do anything to your data, it refreshes the system architecture and replaces it with the framework and applications in the updated rom, while keeping the data intact.:cool:
[Xoom Android Development] russtyd:
I suspect like every overclocking experience (regardless of chip) over-volting works for some, not for others.... I even had a chip some years ago which needed undervolting to reach its best overclock (weird, but I suspect it helped calm the temperature!) and as others have stated already, its wholly dependent on the system (CPU, GPU, RAM will all come into the equation I would think).... some Xooms run at 1704 with no overvolt, some a mild overvolt, some run at 1400 and that's their limit.... if you're running at 1500/1600 stable then you've got a good one I would say (like me... 1600 stable at stock voltage makes me very happy).
[Xoom Android Development] petrossa:
If you don't mind frying your processor. No cooling at all makes for bad results at oc'ing. Perhaps if you make some kind of heatsink. Cut a hole in the back and stick a cooler in on the cpuhousing. Did that for my overheating pvr, ugly but it works
[Xoom Android Development] christianpeso:
172 running very well and smooth. Noticeable difference coming from 169. Greeat job Team EOS.
[Xoom Android Development] dyskinesia:
Wow thank you. Answered lots of questions.
[Xoom Android Development] russtyd:
LOL :rolleyes:
[Xoom Android Development] Alxoom33:
Thanks for the very informative post. It's nice to hear from.someone who is courteous and really knows his/ her stuff!:good:
[Xoom Android Development] robbo10:
New to rooted xoom and EOS, going from 169 to 172 is the proper procedure wipe caches and system or full wipe recommended? Great rom can't believe I waited so long before rooting. I feel like I have a whole new device! Thanks!

Swyped from my MeanELTE

Edit: Never mind should have read a few post back. I'll go with my first option.
[Xoom Android Development] Alxoom33:
Definitely a full factory reset is recommended :good:
[Xoom Android Development] runandhide05:
A factory reset is only needed when coming from a non eos4 nightly ROM

If you are already on an eos4 nightly then just flash ROM+gapps all wiping of cache and dlvk is taken can of with our scripts
[Xoom Android Development] drewski_1:
I've just done caches since 4.2. You should be good.
[Xoom Android Development] robbo10:
Wiped caches and system running fine, no data loss. Thanks :)

Sent from my Xoom using x.da app-developers app

---------- Post added at 05:54 PM ---------- Previous post was at 05:34 PM ----------

One quesgion, is there a slider or widget to ajust brightness on the fly, can't seem to find any, have to go in to main setings? Tia

EOS ..... xoom xoom \m/

---------- Post added at 06:01 PM ---------- Previous post was at 05:54 PM ----------

I have brightness and volume seek bar checked in settings panel control but I don't see any option. I must be missing something

EOS ..... xoom xoom \m/
[Xoom Android Development] Ryno77:
Holy crap! I just updated to the latest release and updated gapps the and this thing is fast and smooth! Drastic improvement in my opinion. Just used my wife's nexus 7 (stock) and this is definitely smoother. Thanks for the continued support on this "old" device!
[Xoom Android Development] robbo10:
Ok I feel dumb lol. Found the second notification curtain. This is awesome rom!! Thanks devs!! :beer:

EOS ..... xoom xoom \m/
[Xoom Android Development] waz675:
Even then you will not even need that. Dalvik will always fix itself when needed(the upgrading/optimizing apps thing seen at a reboot) and cache itself may be wiped in the Eos install script anyway(I think anyway)

Edit just saw runandhide explain the official explanation :p
[Xoom Android Development] mri.project:
Warning - no File_context built at 2012.01.10 .

this why Eos roms always give me hard time . instead of having simple installation i always end up with a head ache.
[Xoom Android Development] liftman-:
you do understand these are test builds and are not stable?(although i have used the nightlys as my daily driver for close to a yr.)

fill a bug report.

if you need something stable try a release!

---------- Post added at 10:02 AM ---------- Previous post was at 09:33 AM ----------

a great thread on governors:

http://xdaforums.com/showthread.php?t=1369817

for those learning about over clocking:silly:
[Xoom Android Development] bigrushdog:
Flash rom. Flash gapps. Reboot.

But just in case, please try the cm build

http://xdaforums.com/showthread.php?t=2084236

Or dream's build

http://xdaforums.com/showthread.php?t=2087668
[Xoom Android Development] FormerPalmOS:
Nightly 169 still having problems with NetFlix. Video freezes after several minutes (usually around 5 minutes) but audio continues. Xoom doesn't lock-up or anything, just the app mis-behaves. Trying 172 now. This has been a problem for every 4.2 EOS ROM I've tried so-far. Only issue I have, but unfortunately it's a show-stopper for my wife.
[Xoom Android Development] NWinfuse:
This message pops up every time I flashed an Eos4 build and it has not signified a problem once yet. I would not worry simply because you are seeing that message, and just continue on and if you have a problem reflash the rom and gapps again.
[Xoom Android Development] Alxoom33:
Themes

Looking for themes that play well with the Theme Chooser in EOS4, current builds. Finding a lot of CM 7, 8, 9 and 10 themes that seem to have phone UI's.

Any suggestions? :D
[Xoom Android Development] FormerPalmOS:
No joy with 172. Abandoning JB :(
[Xoom Android Development] lorenza:
I used to get errors like that but it was because the path in the web address of the download site had eos3 in it. I changed it to eos4 and voila, download! Dont k ow if thats your issue but it cleard up mine.
[Xoom Android Development] petrossa:
I like freehand. Makes buttons hand drawn. Nicely done
[Xoom Android Development] FormerPalmOS:
NetFlix working fine on EOS3 nightly 155.

I will try EOS4 if any of the developers find and fix this problem, otherwise I'm sure I will be happy with EOS3.
[Xoom Android Development] gibbs1984:
Never used any themes before, can anyone recommend any?
[Xoom Android Development] jase33:
Hmmm...I just finished watching an hour and a half movie without any issue. I don't use it much...once every couple months actually. I'm on 172. Is it an intermittent issue? Or only some xooms and not others?
[Xoom Android Development] iruiz2:
I updated yesterday to 172 from 169. 169 was running ultra-smooth, the fastest rom on my xoom to date. Maybe because I updated it with a full wipe? 172 was slower, still ok, but noticeable slower, so I am reverting back. Running at 1400 overclock, and 0.5 animations.

No complains here, I thought I just would let you know...

Sent from my Xoom
[Xoom Android Development] kmcrane:
I run the same settings as you and 172 is smoothest / snappy-est one yet for me.
[Xoom Android Development] Booga Booga:
Not sure if this has been reported or not (tried to look for it) but if you're in eos control center and have auto rotate on, then rotate the device, eos control settings will crash. Sorry if someone else already has said this :x
[Xoom Android Development] illyfilly:
Latest nightly, anyone else have keyboard problems? It keeps on disappearing. Can't type anything.
[Xoom Android Development] ionSeven:
Yep, same here...3rd party keyboards work though
[Xoom Android Development] alex94kumar:
For all issues about keyboards, just use jellybean keyboard from the market. Flawless, and it has a thumb keyboard split mode (default mode is the aosp style keyboard that we're all used to seeing). Zero issues at all with it
[Xoom Android Development] FormerPalmOS:
It's been a consistent issue since the first EOS4 nightly I tried. Would happen every time within 5 minutes of viewing. We had never had the issue before on ICS/EOS2 and for at least a 30 minute session on EOS3 155 it didn't crop up. I have wondered if the overclocked GPU could be the cause. The Xoom has been rock solid at 1600 MHz for over a year and a half but if the TeamEOS kernel folks changed something in the GPU overclocking in EOS4 vs. EOS3, that could cause the problem to appear on some Xooms and not others.

Now I wish I had tried some of the developer options like forcing software rendering instead of GPU rendering. Might have been able to narrow the problem down better.
[Xoom Android Development] runandhide05:
GPU is not overclocked, and half way thru eps3 it was, but then brought back down to 300 about half way thru the eos3 nightlies
[Xoom Android Development] bigrushdog:
Look in development settings. Should find what you seek.
[Xoom Android Development] scottgti:
I've always wondered what the recommended developer settings are.
[Xoom Android Development] lpasq:
We gotz butter :) 172 has my Xoom near to EOS Honeycomb sweetness. So much so that I gave my N7 to an employee as a reward for bustin' ass. OC 1408 no UV and Interactive squeezes my chip set just right. She ain't dead yet. Thanks boys!
[Xoom Android Development] alex94kumar:
Man, I bet people like having you as a boss(?) lol
[Xoom Android Development] FormerPalmOS:
Yup - know it's there, where it is and what they do. The key part was "wish I had" - as in retrospect - as in I already re-flashed back to EOS3 155 and it's working so my wife is now in "tell me again why you want to go back to something that is probably broken mode." No appreciation for us geeks...
[Xoom Android Development] kentedman:
I always answer that with ..."tell me again why you need another pair of red shoes?" .... yep, sleepin on the couch again.

Honestly, I havent played with the multiple users very much. It was a bit unstable last time I tried, but if that's working better, thats a great argument for the reason to upgrade on a shared tablet.
[Xoom Android Development] prostang:
does anyone else have issues with the Xoom rebooting when turning up the volume?
[Xoom Android Development] pkelly517:
Flash. No tell.

Show her who's boss. Enjoy the dry spell.
[Xoom Android Development] drewski_1:
not yet . . . <knocks on wood>
[Xoom Android Development] shpitz461:
Here's mine on Stingray, both tablets (yes, I have 2 of them) are o/c to 1.5GHz. Only one of them is actually activated for 4G.

CM10.1 201301114

EOS4 165:
[Xoom Android Development] waz675:
For starters, a process (or more) may have been running, say polling emails, backup info (*WHATEVER*) on the lower score one, or not but there may have been which can interrupt the benchmarking software hence giving lower scores. Ultimately, benchmarks aren't a great way to get a 'definite' source of a problematic device, especially on a single run. Multiple runnings, averaging the scores (bell curve, remove highest and lowest scores which may seem 'out' of the normal score), mean and the like to try to guage if one install is better than the other. Plus since the environments most likely aren't the same, besides the obvious 4G thing, it would be hard to see a somewhat/exact similar score.

Moral, for me anyway, unless a device is obviously slower, say frames skipping etc in gaming, things taking lot longer to load than another 'same model' device (and ROM), benchmarks are just an indication of a possible experience. Take with a grain of salt, same as advice over the internet from people when you have no idea of what their qualifications for giving said advice are. :p

Do the tablets feel different, placebo possibly included since you know one has a lower/better score than the other.
[Xoom Android Development] bigrushdog:
With that big of a difference there's something wrong with our build. If somebody gets motivated try flashing the cm boot image. See if it's the kernel.
[Xoom Android Development] simonbarsinistr:
Does it matter that it was build 165, so 7 builds and a lot of fixing ago?

Edit: Nevermind, I just benched with similar results and I'm running 172.
[Xoom Android Development] prostang:
This has been an issue since the JB OTA.
[Xoom Android Development] Alxoom33:
I ran a benchmark yesterday on 172 and it was very slow, around 2800+, just ran a benchmark with dreamcwli's latest My_Wingray build flashed today over my 172 data with a system wipe and got much higher benchmark, both with performance governer. Also, I have several widget running simultaneously, which I presume slow things down.

Even worse after restoring 172, same Xoom, but had to turn down to 1600 due to reeboots at 1706.
[Xoom Android Development] extremetempz:
Team EOS Outdoing Yourselfs

a fast smooth stable rom with 172 with -150mv undervolting i just cant get that homescreen to butter no matter what launchers or such its just laggy and have you guys thought of a 3.0+ linux kernel
[Xoom Android Development] bigrushdog:
Not from us this late in the game. I'm gonna try, just as a test, a build with the stock cm kernel.
[Xoom Android Development] scottgti:
Where would one find this test build? :D
[Xoom Android Development] Alxoom33:
I use Android Overclock, which has profile setting for oc'g 172. I use the built in of program in dreamcwli's My Wingray because it did not play well with Android Overcklock. Is it just the oc'g programs that are causing the issue with EOS4? Could the issue be solved by having a baked in oc'g in the EOS System settings?
[Xoom Android Development] scottgti:
Like this.
[Xoom Android Development] Alxoom33:
Lol, embarrassed# ! I thought that. I saw them before :) I am going to run benchmark w/o Android OC and see what we get.
[Xoom Android Development] Alxoom33:
After being kindly corrected, I froze Android OC and used the internal EOS Performance settings of are 1600 with Performance governor (tried 1704 like with the dreamcwli My Xoom Rom but it crashed and reebooted with EOS4 172) The benchmarks were better, but still 1000 points below CM 10.1 and My Xoom results shown above. See results attached:
[Xoom Android Development] gibbs1984:
Not a fix to the issue of the lag on the homescreen but I played with the setting of the Apex Launcher and set the 'Minimum scrolling time' to '20' or '10' and you don't see any lag moving from 1 homescreen to the other. Probably cause it's actually not scrolling I suppose but at least it looks better.

I'm not a programmer so this will probably be a stupid question but since dreamcwli's ROM doesn't have homescreen lag can't you implement his changes?
[Xoom Android Development] petrossa:
Why bother? Almost any launcher works better then the stock one. I use adw which rolls smooth
[Xoom Android Development] Alxoom33:
I use Homesceen for the circles widget and Nova for the nice backup and restore feature that works accross different rom platforms.

:cool:
[Xoom Android Development] whatllitbenext:
THANK YOU!

You guys are the BEST!

Hadn't really done anything with your nightlies since Eos 2-ish.

I come back and you're all, like, JB and whatnot and totally current.

I downloaded the new CWM, EOS4, and gapps, got everything running and just sent you $5 (that's probably not enough but I'm pretty broke right now) to show you my appreciation.

Thanks, you boys!
[Xoom Android Development] kakrikakri:
Shifting to EOS 4

Hi guys,

I am shifting to EOS 3 to EOS 4 nightlies. I had a doubt if you could answer them.

After performing a factory reset, can I restore only the 'Data' from the nandroid backup of the old system to the 4.2 nightly?

And also could any of you suggest which nightly from 155-172 is the best. I mean less lag and best performance.

Cheers TeamEOS, thanks for keeping my Xoom alive and kicking !

Thanks
[Xoom Android Development] petrossa:
155 is less demanding on the hardware so if you are only looking for that you should stay on eos3. EOS4 uses more juice and needs to be oc'd/tweaked to run smoothly,172 runs best . But after that it has lot's of advantages over eos3
[Xoom Android Development] waz675:
172 is smoothest for me and every game (street fighter 4,final fantasys and a heap of other title) work very nice with no obvious slow down for JB 4.2/EOS4. Haven't felt the need to overclock this like I did with eos3 nightlies.

Edit. I use nova prime with a few settings changed to get home screen the quickest so possibly stock launcher or another launcher on stock may not give a smoothness that is exactly desired since I've seen a few people talk about smoothness and forgot I did a bit of playing around with launcher settings to get it a smoothness that I like.

If you ever want to restore a nandroid backup (ie go back to 4.1 JB for example,) JB 4.2 puts all data from sdcard to '0' directory due to adding multi user functionality so you will need to move the relevant data from '0' in sdcard back to the root sdcard directory then you can restore a nandroid backup.
[Xoom Android Development] gcounts:
It may have been asked already but how do I remove the persistent search bar?
[Xoom Android Development] aR_ChRiS:
Use another launcher such as Apex/Nova
[Xoom Android Development] runandhide05:
OK well I can assure you that its fixed on latest merged commits + gapps. So just hang in there and all will be well. ;)

Thanks for the report btw
[Xoom Android Development] Sushibagel:
So how's this ROM working for everyone? Good enough to be a daily driver? I've been eyeballing this and really want to try it, but I use my Xoom daily for work so I need it to be semi functional. I don't mind some instability (I know it kinda goes with running nightly ROMs) I just need something I can use.
[Xoom Android Development] tdarren:
There is quite a lot of frame stutter especially at the launcher and there are areas such as the setup that incorrectly identify the device as a "Phone" not a Tablet.

Android 4.2 is making my tablet look like a phone.
[Xoom Android Development] Taysider:
The UI is causing the device to have the phone. This will be fixed soon enough.

Flashed 157 with the new gapps running great. The inclusion of the soft key setting is great, missed having menu long press as screenshot. Now it's back.

Fabulous Work Guys :highfive:
[Xoom Android Development] sibax:
Early days but this ROM appears to be running well. The "problems" with the ui I don't actually recognise as a problem as such but more a matter of preference. I'd like to see this included as an option as I actually prefer the soft keys in the middle and the notifications and quick settings at the top as can be seen on the latest nexus tabs.

Big eos fan keep up the great work.
[Xoom Android Development] alex94kumar:
can't wait to see all eos settings enabled in the next nightly!
[Xoom Android Development] Sushibagel:
I agree in that I'd like an option for the UI preference. I personally, don't like having the soft keys in the middle of my screen, but I do however like how they implemented the notification and power widget shades on the the Nexus tab UI.
[Xoom Android Development] Booga Booga:
When the new gapps package comes out, can we just flash it over what we have now ? (running 157 with newest gapps from 2012-21-03) or will we need to wipe data then install the new gapps?
[Xoom Android Development] NoP_Compiler:
You can tell people that is a Galaxy Note 3 :D

--
[Xoom Android Development] alex94kumar:
For those of you with keyboard issues, Jellybean Keyboard from the Play Store is a good alternative. I currently find myself using the 10" split keyboard, which is great for tablets. It has the stock-style keyboard also
[Xoom Android Development] WarLion:
I like it more thumb keyboard
[Xoom Android Development] EDNYLaw:
Is anyone else having issues with no picture over HDMI? I want to make sure it's not just me. If this is a known issue, are there plans to fix it? EOS on 4.1.2 worked perfectly and I'm going to be giving my Xoom to my girlfriend (I just got a Nexus 10) and she's going to use it to stream to her tv. Thanks guys, appreciate all the work!

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Xoom Android Development] runandhide05:
ok gents, im going to say this,

if you turn off or 1/2 the animation it is a quick SOB!! freaken fast and smooth for a 2year old tablet!

your going to LOVE the next nightly :D

---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------

let me go find my HDMI cable ( middle/ just finished moving and its packed somewhere....) and il see whats what and let ya know bud

i just tore thru my garage looking in every box, and can not seem to find it, do me a favor and run a logcat and connect hdmi to it and tv and then stop logcat and il look at it and see what i can find
[Xoom Android Development] alex94kumar:
I can confirm that there is no video over HDMI in 157, buy audio runs flawlessly
[Xoom Android Development] fleury14:
On 157 when I try to swipe up the home icon to get to Google now the screen becomes unresponsive.
[Xoom Android Development] alex94kumar:
Only until you hit the power button and turn the screen off
[Xoom Android Development] runandhide05:
that has been fixed and merged to gerrit, next nightly will solve that, and as BRD stated, we are going to the phablet UI for now, whats happening is that it thinks the softkeys are were they "should be" which is in the middle of the botton bar, if you longpress home, then move over to the middle of the botton bar and touch and slide up you will see what i mean.

see attachment to get an idea of what i am talking about to make sure we are talking about the same thing, first one is problem, second attachment is it now fixed
[Xoom Android Development] alex94kumar:
Will that nightly drop sometime tonight? or tomorrow? Only reason i ask is because I use a bluetooth keyboard at school with my Xoom and have been unable to in the latest nightlies because of it not working.... and I dont want to go back to 4.1 =/
[Xoom Android Development] jimboogly:
Ill grab mine, and let you guys know (on 156 about to flash 157)

Just tried on 157 with dec 03 gapps, and like the above post, no video, but audio is flawless also.
[Xoom Android Development] EDNYLaw:
Thanks guys, good to know I didn't bork something. If nobody has by then, I'll run a logcat in an hour or so

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Xoom Android Development] AHinMaine:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

I did some light testing on mine. My best quadrant ever on build 172 (after dozens while I experimented with undervolting) was 2818. Typically it averages about 15% less than that. I put yesterday's cm10.1 nightly on, tibu restored all my apps, two reboots, double checked my running apps to make sure I was mirroring my previous conditions reasonably well, and locked my CPU at 1704/performance. First quadrant out of the gate was 4162.

Anything informative I can do while I've got it installed?
[Xoom Android Development] Alxoom33:
That's consistent with what I found testing against CM 10.1 and My-Android ROMS. Strange thing is that I feel that the EOS4 172 works just as well and as smoothly as the others despite the low quadrent scores. It is still my preferred. DD.:silly:

I'm curious to find out what BRD and the rest of team EOS discover in their analysis of this issue.
[Xoom Android Development] AHinMaine:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies - Wingray / WiFi Only

Definitely, I prefer it for the DD as well. The EOS control panel alone makes it worth it.

It may be a tiny bit slower, but it's *far* more stable. CM is very crashy in some sections of the settings, and 3 or 4 SOD occurrences already.
[Xoom Android Development] FormerPalmOS:
No solid data here - just an idea.

IIRC, over time, there have been kernel and/or ROM tweaks to Stagefright (the Android video rendering engine, again IIRC). It's possible that there is something new in JB MR1 (4.2) with Stagefright that is breaking NetFlix for me and is affecting quadrant scores, but otherwise not affecting the ROM. This is inconsistent with games performing well on EOS4 (unless those games use their own rendering engines and don't use Stagefright - if indeed this might be where this is an issue).

Don't know if this triggers any alcohol-dazed brain cells - just throwing it out there.

Still on EOS3 155 since NetFlix works reliably there.