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?
[ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Wingray
- Thread starter teameos
- Start date
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?
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
No complains here, I thought I just would let you know...
Sent from my Xoom
I run the same settings as you and 172 is smoothest / snappy-est one yet for me.
Sent from my Galaxy Nexus using xda app-developers app
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
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
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.
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
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!
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!
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...
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.
Flash. No tell.
Show her who's boss. Enjoy the dry spell.
Sent from my Xoom using Tapatalk HD
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:
CM10.1 201301114
EOS4 165:
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.
Do the tablets feel different, placebo possibly included since you know one has a lower/better score than the other.
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.
Do the tablets feel different, placebo possibly included since you know one has a lower/better score than the other.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
117
Welcome to Eos 4.0! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.
Solarnz - Project founder and backend systems admin
Bigrushdog - Project lead, Chief Developer
Kevdliu - Feature Engineer, Toro maintainer
Timduru - Frameworks Developer, TF101 maintainer
Roach - Frameworks Developer - N4 maintainer
RaymanFX - Remote branch and Experia maintainer
Runandhide05 - Xoom maintainer
UBER - Chief Graphics Designer
Sykomaniac - Maguro maintainer
Code:NX Gesture Navigation Bar Navigation Bar Color w/ Project Glass (Auto-Transparency, not the Google Project Glass :P) Softkeys Long-Press Actions Custom Navigation Bar Ring Quick Launch Targets Hide Status Bar and/or Navigation Bar Resize Navigation Bar Display All User Widgets On Lockscreen Recents Panel RAM Display and KillAll Switch Custom Quick Toggles Tiles with Brightness & Volume Seekbars EOS Status Bar Toggles Status Bar Color Battery Indicator Mods Clock Mods T-Mobile Theme Engine Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able) Default Volume Control Stream (Ring or Media) Volume Keys Long Press Music Control Disable/Enable CRT Animation Custom Screen Bahavior When Charging Custom Screen Off Wifi Delay Performance Settings Advanced power menu with reboot options. Eos Control Center MORE...
We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded. The resources we use include, but are not limited to:
Features:
Code:Phone: for T9 dialer support MMS T-Mobile Theme Engine
Branches:
and various qualcomm support related branches. We also use some qualcomm related branches from CodeAurora Forum.Code:libhardware, libhardware_legacy, system/core, system/netd, /system/vold, frameworks/native, frameworks/av, isolated frameworks/base cherry-picks,
Team EOS Xoom Nightly builds
Download
G-Apps Package
Because this is an AOSP based rom Google Apps are not included. To install Google Apps please flash the following package after installing the rom:
Gapps package
Xoom comes with Custom EOS kernel.
These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.2.2 COMPATIBLE RECOVERY.
Changlog
Contribute
Gerrit Review
Gitweb for GPL compliance54I'm gonna try and give some perspective here. 4.2 is not like past releases. Internally, much reverse compatability has been removed. That means that older devices, with older kernels and older proprietary resources will have difficulty maintaining compatibility with 4.2. So we are having to do things for the Xoom that we didn't do before. Up to this point, new Android releases just worked out the box. This is no longer the case. Many comparable devices, non nexus devices, like the Transformer 101,have had to fight a hardware battle from day one. Now it is a battle the Xoom will fight. What does this mean? If you want a flawless build , stick with 4.1.2.
It means the Xoom is getting old. Android has left Xoom behind. Eos has not. Dreamcwli has come in as well and is doing amazing work. He is VERY talented and the Xoom community is blessed to have him on board. I'm certain between all of us, we'll get things running as they should. But it takes time now. Just some thoughts42Tonight's build is probably the most epic build we've had in quite some time, and I'm excited about it! Besides tablet mode, we added something very important, JIT. It seems at some unknown point, a merge removed JIT from the build. Some of you have noticed lousy benchmarks. This is why. I benchmarked Nexus 7 before using Linpack. Before was 11Mflops. Now it's 56Mflops. At the same time, missing JIT has had little impact on user experience, as JIT primarily boosts mathematical performance.
Tablet ui feels pretty smooth. There are minor layout issues, like notification icons not playing nice with bar resize. But this is a solid round 1. I recommend slimming down the system bar some. I'll be adding more bar sizes too so we can get that perfect profile.
We get center clock now for you weirdos that like it:laugh:
Eos is now compatible with Xposed framework, which I've played with for a couple days. For those who don't know, Xposed is a VERY powerful framework that attaches itself to Zygote. Summed up in a nutshell, this allows per app manipulation of almost anything including PER APP DPI CHANGE. For those interested, I'll do a brief write up after the build drops. It won't be included in the build, but installing is simply downloading and installing apps.
Watch for that goo notification. Don't miss this update. Keep rolling with Eos. Profit. Peace.32BRD, I think you should leave the EOS 3 thread open until this release gets more stable and realiable, because as far as I'm seeing here (still didn't test, had no time for it) there are many guys with problems and lots of bugs, which is perfectly normal for a first release, but to get a more stable nightly the EOS 3 looks better now
Well, it's just an opinion, do whatever you want, you're (with solarnz) the boss here and did a great work all that time on Xoom development
Sent from my U20i using Tapatalk 2
Solarnz has given me the project so I'm the boss now. And that also means the buck stops with me. Guess it goes both ways. I closed the thread because the last 4.1.2 build is flawless and no longer being developed. Thus I'm not interested in any commentary on it. Also, it was filling with 4.2.1 bugs which, against my better judgement, i knew it would. All downloads are still available on goo for those that find 4.2.1 "challenging"
My talented and trusty maintainer Runandhide is working on some of this issues discussed. I've also fix quite a few but wanna get a couple more fixes before we do another nightly. One thing that threw me off is for some reason xoom is running in tablet UI, and it should not be. Thus you see phone settings for the Eos interface. Guess I'll just bring in tablet eos settings then. Remember I'm working blind as I don't have my xoom anymore.
Stingray lte is proving to be a challenge. I've almost got it. When i get LTE going ill move on to everest. We have some VERY talented people coming on deck who want to push Eos to the next level. New features will be coming but let's get xoom stable first.24
