Related
Just a quick question for you guys: I recently purchased an Infuse from the marketplace here, and so far I've gotten an absolute TON of lag using the device. I've flashed Infused 1.5 and Bionix with the Infusion kernel, and so far the lag has gotten better, but it's not totally cleared up. I'm definitely not new to Android, but I haven't seen anything like this before. I know that Quadrant isn't a reliable benchmark, but I'm scoring about 1900, OCed to 1.5Ghz.
Just to give an example: I'm using desktop visualizer to add some custom icons to my screen. When I go to select an icon image, it's fine, but it freezes for about 90 seconds when a list of my apps comes up.
Anyone experience this before? And if so, how did you solve it? If this was widespread, I'd imagine there would be complaints all over here.
Which app are you using to set your overclock settings, how many clock speeds do you have enabled, are you under or over volting, and *which governor* are you running?
I have seen some similar problems here when I was using conservative governor with poor choices of clock speed. Right now Infusion 1.5.2 kernel has some issues with not liking the ondemand governor, so I reduced my number of available clock speeds so it would jump to the top more quickly while using the conservative governor.
Also, did you use either the return to stock, or the ultimate unbrick flash before you flashed your ROM? If it was a used Infuse, I would do one of the above before I start looking anywhere else, then reflash your rom/kernel of choice.
I'm using SetCPU with the OnDemand gov (400/1500), no undervolting. I have a profile set to underclock it to 300/700 on conservative when I'm charging, but that's about it.
I think I'm going to use GTG's unbrick/return to stock and root the thing myself, I figured I'd ask before I did anything drastic. My UI is a ***** to set up every time, and I hate wiping because of it.
Just a quick note, I've had some serious lag using the oc kernel... Like real world usage got worse after oc'ing
Sent from my SAMSUNG-SGH-I997 using XDA App
Although it is counter intuitive to the way governors should work I have seen less lag on Infusion 1.5.2 when I use conservative. The ondemand governor seems to be having some issues with the most recent update. If you flash back to 1.0 Infusion you get a max overclock of 1.4, but it is much more stable IMHO. Also FFC is presently broken in 1.5.2 and will hard freeze the phone (battery pull).
I'm debating flashing back to community kernel, but I am going to wait and see how long it takes my battery to drain because I am using some undervolting. You might try using conservative governor and only enable 100, 400, (800 or 1000), (1200 or 1300) and 1500. Honestly the infuse is my first smartphone, but I've tinkered with desktop hardware the last 15 years. It literally amazes me everytime I pull the battery out of this phone and feel how light it is.
I also used the desktop vis app and yes it lagged when chosing apps however it seemed to get better after three or four times but that seems to be the only place it lags for me im using the oc-uv kernal 1.0 clocked to 1.4 seems bulletproof compared to later versions im getting great speed and batt life with this kernal but i had the same lag in the same event as you
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
entropism said:
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
Do you use spareparts?
usually yes, but I dont believe I installed it yet on the infuse. Why?
lag on stock also
I'm 100% stock & get lag also. Definitely in the situation you describe, when the app list comes up for adding shortcuts to any homescreen. Takes forever for that list to come up. Secondly, simply from running for a while, i have to kill all the apps using the built in task manager in order to get it to run smoothly again. It's like it never closes an app. I'm new to android, but guessing this is a problem inherit to android. Can't see how samsung or at&t could have screwed this soo badly to cause it to never close an app. Hoping memory management is better in Gingerbread.
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
yeah, the longer I have the phone the more it lags it seems
probably going to push me towards the Evo3D
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
superweapons said:
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
Click to expand...
Click to collapse
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
entropism said:
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
Click to expand...
Click to collapse
I don't do much. Twitter, "Web" (some mozilla stock ish), SMS, phone, Android Market app (browsing), and Maps. I've had it lag up using only those. Far less often, I use Yelp... that's about it.
Not supposed to kill apps? When I kill them it fixes the problem. Maybe it *should* be killing apps?? If its supposed to flush their state to disk... it seems to be doing a poor job at it.
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
hydrogenman said:
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
Click to expand...
Click to collapse
I'd more readily assume the 512MB RAM is the issue. Looking forward to SGSII
SolusCado said:
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
Click to expand...
Click to collapse
It's the stock card that came with the phone. Any way to check? The apps are installed to it... so removing it I wouldn't have the apps available anymore.
A little update: I returned back to stock and re-rooted. I installed 3E, then CWM, then threw on Infused 1.5 and Infusion, OCed to 1.6Ghz and slightly undervolted (about 25-100mv along the range) using SetCPU.
As of right now, it still lags on occasion, but not as bad as it did. Quadrant is giving me a whopping 1300 average score, with a low of 800 and a high of 1600. This is just pathetic.
Hi, i have searched the forums, but haven't been able to find an answer, simply put i don't believe my xoom is overclocking. I have been testing it with an app called neocore, but have tried quadrant as well. It doesn't matter if i am at 1000 or 1700 Neocore always says that my xoom runs at between 34-36 fps, which is the same as when it was bonestock, quadrant is the same. No change in animation speed or results no matter what i have set the clock too. I currently have eos nightly 77 for 4g on my xoom, I was using the stock kernel that came with the rom, and recently downloaded the.3.0.5 tiamat overclock kernel, which after flashing think it was the same(I am a noob). I was originally trying to use android overclock to adjust my settings, now have completely uninstalled it and using eos's settings, no change. What am i doing wrong, or have missed?
Thanks for any help you can give me
For increased smoothness in animation, etc, I believe it is the overclocked gpu that helps as opposed to the cpu. Not all the eos kernels are overclocked. Quadrant score appears to be meaningless. Believe me, the eos kernels permit overclocking. What governor are you using? Is your setting stable?
I have it currently at interactive, after you mentioned the governer, i put it to performance and ran the neocore benchmark to see what would happen, 38.2. Well if it requires a gpu overclock that would make sense that i am not noticing a difference with the apps i am using. But raises another question,what is a overclocked cpu good for? More apps running at once? My overclock is ALLOT more stable with 77, i was previously on 74. Before it would get glitchy allot more often, and random reboots on anything above 1000. 1400 and i was having to watch the temperature, 1500 seemed to work the best, but still got random reboots (still better than what I got on honeycomb. I still get glitches here and there on 77, but still have yet to get a.random reboot.
Unrelated to my topic, thank you so much for your guide to rooting and romming, i had read a couple others and hemmed and hawed about whether to do it, even though my mouth watered about the benefits, your guide made me clap my hands together and say "let's do this"
I went back over the kernel I downloaded and flashed, it is the team tiamat overclocked gpu 3.0.5 kernel that was realeased 2/19/2012... sorry, this stuff is new to me so I am learning as i go along
Draxin said:
I went back over the kernel I downloaded and flashed, it is the team tiamat overclocked gpu 3.0.5 kernel that was realeased 2/19/2012... sorry, this stuff is new to me so I am learning as i go along
Click to expand...
Click to collapse
No problem...the EOS nightlies are on a newer kernel, but I think the lastest don't have oc gpus.
Imoseyon gave me permission to link his kernel here on XDA. Please thank Imo on here or RootzWiki, and please donate to him if u can.
ICS and JB kernels are available.
v 4.0 is the newest version for TW JB 4.3 ML1 only.
Older versions are available (4.1.2)
Experimental builds are also posted on RW. I personally dont want to link them here since I cannot help if something goes wrong. So keep an eye on the RW thread if you can help in testing.
Link to OP/ICS kernel http://rootzwiki.com/topic/31329-ke...el-minimalistic-kernel-ics-v13-jb-v03-112512/
Link to JB kernel changelog https://github.com/imoseyon/leanKernel-d2vzw/wiki/TW-ChangeLog
Link to source https://github.com/imoseyon/leanKernel-d2vzw
All credit goes to Imoseyon
Please feel free to post results from Roms.
OK so running this on jelly beans b 4 and it is super fast. Works like a champ! Great work imoseyon. I tried ktoonsez and this way smoother on touchwiz. Like butter baby!
Sent telepathically
Are there any custom governors with this kernel?
Sent from my SCH-I535 using Tapatalk 2
No just three. Not as many options but already set out of the box so to speak. Changed my io scheduler to deadline and let her rip.
Sent telepathically
I hope to have interactiveX running on it before the 1.0 release.
Also, you can find the change logs here: http://revision.io/embeds/leanKernel-galaxys3-tw
Thanks for sharing.
Running fine on clean Rom 5
Sent from my SCH-I535 using Tapatalk 2
does not work with Taste of Beans 3.5k at all..
color flux
removed boot animation
reboots
battery gets SUPER HOT!
had to do a batt pull, boot into recovery, and go from there.
Ran fine when it first booted...benmark scores were very high...running very smooth...
Then after a reboot things got kinda wonky...
Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...
I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...
...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...
Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...
Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...
The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...
Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Metfanant said:
Ran fine when it first booted...benmark scores were very high...running very smooth...
Then after a reboot things got kinda wonky...
Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...
I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...
...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...
Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...
Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...
The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...
Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Click to expand...
Click to collapse
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.
Imoseyon said:
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.
Click to expand...
Click to collapse
So it would be "stress" related sorta...but more heat related specifically?...its a bummer because my phone does not like 1900mhz at all...and really starts to heat up/lag at that clock speed...
So if the kernel is going to "reset" all the time I'm gonna have to stick with 747 because its the only one (except stock vzw jb) that sticks no matter what I throw at it
Edit: I will however say...the kernel is completely compatible with Synergy 118...and like I said before...when it initially booted the phone was screaming...and performing better than ever...
So keep up the good work and I'll keep my eye on things...
I didn't run your kernel on ICS...wishing I had tried it out now lol
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Despite what a previous user said I'm running this on tasteofbeans 3.5 with no issues. I've ran both 0.2 and now 0.3
Sent from my SCH-I535 using Tapatalk 2
Has anyone ran this kernel over CM10 nigthlies?
Sent from my SCH-I535 using Tapatalk 2
TheGman125 said:
Has anyone ran this kernel over CM10 nigthlies?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This is for TW roms not for aosp roms, imos has his aosp kernel in rootz
Sent from my SCH-I535 using xda app-developers app
Sorry to hear Met. My phone has never run so well. I'm not experiencing any heat ups or problems set at 1700mzh. When I I run Vellamo it lists the kernel max at 1900mhz but when I check setCPU its locked at 1700mzh. I ran LK on ICS and it was simply amazing. It was the only thing I missed moving to JB. Plz remember that this kernel is just days old and it will continue to get better with updates from Imo. Keep the reports coming guys, it's the best thing to do to help.
What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.
Sent telepathically
Any chance of Call Recorder kernel support Imo? I only ask becaues several of your kernels for other phones I have owned did support it.
jdub251 said:
What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.
Sent telepathically
Click to expand...
Click to collapse
I would not use KTweaker with this kernel. I remember reading some where its specific for KT kernel. I have had issues using Android Tuner and system tuner on previoulsy used Rom/Kernels as well. I use SetCPU and it works great, I know its a paid app but its so worth it especially if you plan on using custom kernels. Theres a free setCPU version floating around but that app isnt supported anymore.
V.3 locks my cpu to 1900mhz...so i reverted back to v.2 and all is well. 11180 antutu bench mark @ 1520mhz, 10080 @1900mhz
For the ppl not needing to OC try v.2, u might have better results.
For those of us that have dealt with lag on JB 4.1.2 and are using Touchwiz I've created this thread to spitball, trouble shoot or even complain about it.
From what I understand it's Android 4.1.2 related. I've been reading that it's an issue with TW and 4.1.2 itself. Some have suggested that using a custom launcher will help get rid of the lag. I've seen this be true on Nova. I have been able to get no lag on TW only by not having any widgets on the home screen. This leads me to believe that part of the lag is a result of having to render the widgets and load the information there within.
Others complain of lag during gaming (Temple Run 2 is a big one). I've looked through the forums, and searched multiple threads and it appears that other S3 variants and even tablets like the Tab 2 is having issues with 4.1.2. My G Note 10.1 had it as well.
So in the hopes of figuring out what the culprit actually is or even to vent frustration at such things here we are.
If there is a thread already like this MODs please let me know and/or close it. :good:
I don't use any widgets and I get crazy lag while playing ingress. I've only ran touchwiz and its lagged on all. Sucks but not that big of a deal.
Sent from my SCH-I535 using xda app-developers app
I also get lag and/or lockups on occasions. On stock rooted 4.1.2. So is not just CleanROM. I may go back to 4.1.1. I can't seem to find enough benefit to stay on the current stuff. I've tried different kernels, etc. No dice. The only game I play is candy crush, and it's HORRIBLE. Everything moves in slow motion. LOL. It sticks how the mods handled this, I feel it is relevant. It's an issue, well known. There are MANY complaints about it.
I've had the same issues with Candy Crush. No lag on 4.1.1, and tons of lag in 4.1.2. Like you said, it almost looks like the app is in slow motion. I have yet to find a solution to this.
Man you guys are right on the money. I've reverted back to 4.1.1 because of all the lag. I'm currently on GalaxyMod Rls 13, which to me has the least amount of lag. Homescreens don't redraw, menus are smooth (for the most part anyway, you scroll back to the top of the settings menu and it tends to jump on occasions, no matter what ROM I'm using). I hope 5.0 addresses these issues. I remember how excited I was when 4.1 first dropped... Arguably the best build Android has ever made.
Sent from my SCH-I535 using xda premium
Some say they don't get lag. Just a theory here, but I went the OTA route, then rooted and unlocked. Got lag, even flashing back to 4.1.1. Thing is, I still had the current OTA partitions. So, I Odined back to K3. TADA! No more lag. Makes me think that possibly those that took the OTA are getting the lag because of the partitions that are updated. Those NOT experiencing lag are ones still on K3 partitions, but have flashed up to MB1 ROMs. Maybe? Just a theory.
countryfolk07 said:
Some say they don't get lag. Just a theory here, but I went the OTA route, then rooted and unlocked. Got lag, even flashing back to 4.1.1. Thing is, I still had the current OTA partitions. So, I Odined back to K3. TADA! No more lag. Makes me think that possibly those that took the OTA are getting the lag because of the partitions that are updated. Those NOT experiencing lag are ones still on K3 partitions, but have flashed up to MB1 ROMs. Maybe? Just a theory.
Click to expand...
Click to collapse
Which K3 tar did you use? I'd like to try this myself on my wife's phone. Thanks.
NVM I got it.
Sent from my Nexus 7 using XDA Premium HD app
I have two s3 phones in the family. One of them is on cleanrom and one is on stock unrooted. Both of them suffer from lag. We do not play games on our phones. The last that we notice is when doing things like texting. The keyboard is really slow to come up. And when the auto correct list comes up, it is very slow. Scrolling also seems to bog it down. I am not sure what is going on, but it is a definite step backward from 4.1.1. I how that there is a solution that does not involve going back to 4.1.1.
Sent from my Nexus 7 using Tapatalk 2
usmaak said:
I have two s3 phones in the family. One of them is on cleanrom and one is on stock unrooted. Both of them suffer from lag. We do not play games on our phones. The last that we notice is when doing things like texting. The keyboard is really slow to come up. And when the auto correct list comes up, it is very slow. Scrolling also seems to bog it down. I am not sure what is going on, but it is a definite step backward from 4.1.1. I how that there is a solution that does not involve going back to 4.1.1.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I wonder if the GS3 suffers from graphic redraws? Maybe it's not caching the images perpetually, only drawing them when needed. I've noticed this when it loads widgets, scrolling through menus, and when you have a lot of notifications(the drop down shade hesitates when it's opening and closing). I don't think it's hardware, as there are a few HTC phones with the same adreno GPU and they don't lag. My previous phone, the EVO 4G LTE, didn't lag at all, and they share the same adreno graphics hardware. Hero's Axis Rom addresses most of these issues, as my experience with his roms have been positive. It's not completely gone, but it's better than stock. I'd recommend using his rom if you have these issues.
fix, maybe?
Hey, all. So I had gotten the i757m, same problem as here. Got a new one from Bell, and it was slow as hell too.. Here's what I did.
I disabled everything I could, all the bloatware.
100% HD Games
Asphalt 6
Google Play Books
Google Play Movies
Google Play Music
GPS Navigator(Let's be real here, it sucks anyways.. use google maps)
Let's Golf 3
Mobile TV
Sympatico.ca
Yahoo! Finance
Yahoo! News
This helps(after a 4.1.2 upgrade via kies)
Next step: Developer options
Turned off animations(Transition Animation Scale)
under apps > Do not keep activities check box. Destroys processes after the user leaves them. Not so awesome for multitasking, but hey, whatever works, right? 262 MB used 1.7GB free . Seems like a win to me.
Do you guys overclock? This is just a theory, but overclocking or undervolting overclocking or flashing too many times seems to slow down phones. Have any of you guys tried to go back to stock and then factory reset and started over? I think that might help. Also, I do see lag, however I only see minimal lag, maybe its because I rarely have anything on my phone? I am also on stock kernel and that seems to work the best for me right now, I used to run custom kernels, but some of them keep causing issues and weren't stable enough or gave me worse battery life. I will try the new leankernel as I like leankernel from the galaxy nexus and have previously tried lean before and had a good experience. Hopefully this at least partially answers the OP's question
Well there have been 3 Touchwiz kernels that worked for me and that's leankernel, kt747 and Zeus. I only overclock to 1.8 ghz or 1.6 ghz those speeds give me the least problems.
I just ran temple run 2 just fine. Here is my setup. MOAR ver.18 latest firmware mf1, KT747 kernal.
undervolt
1175 1160 1160 1150 1150 1125 1125 1100 1100 1050 1050 1050 1025 1000 1000 950 950 925 925 900 900 900 900 880
min 189
max 1512
i/o cfq
governor
ktoonservative
screen off set too 810mhz
Thats it.
I get at least 22hrs of charge with 39% left. I can't let drain down fully because i need it to be fully charged every night before bedtime. I basically charge it fully before bed and i'm left with 39 to 20% by 9pm the next day. I'm on wifi at home and 4glte at work.
---------- Post added at 11:26 PM ---------- Previous post was at 11:23 PM ----------
last night i had a 3% battery drain within 5hrs. I think that's pretty awesome. While i'm asleep.
I'm with Verizon running BoneStock 3.2 and no lag at all. Fastest ROM I've used so far. With stock kernel
Sent from my SCH-I535 using xda app-developers app
I currently have the OmniRom 4.4.4 insalled on my Xoom Wingray device. I poked around and saw the EOS Rom. I'm really torn if I want to go and re-wipe and rebuild my device on the EOS rom. What's the pros and cons of each rom based on opinions of the users running each one. Please no flames or fanboys, just honest things you like about your particular Rom.
AlphaW0lf2014 said:
I currently have the OmniRom 4.4.4 insalled on my Xoom Wingray device. I poked around and saw the EOS Rom. I'm really torn if I want to go and re-wipe and rebuild my device on the EOS rom. What's the pros and cons of each rom based on opinions of the users running each one. Please no flames or fanboys, just honest things you like about your particular Rom.
Click to expand...
Click to collapse
This whole section seems to be lacking people who are willing to or have experience with each releases. But what are your thoughts on Omnirom? Why did you choose that over CM 11 and now looking at EOS. Trying to get as much info as possible before i consider flashing this old tablet and squeezing more life out of it
I chose the Omnirom because it was the first I heard about. I wanted android 4.4.2 and it seemed all google searches pointed to Omni. Now after running it for a week or two I deal with bugs that I don't want to fight with forever. Volume control doesn't work, random chrome crashes and now tablet reboots. I tried to reach teamomni but no luck. And EOS has built and published nightlies more recently than omni. I know I'm pushing this tab!et beyond its years. I figure this is the end of the road for this device, so I want to squeeze every ounce out of it. I can't thank both teams enough for their work. It's more than I would be capable of ever doing.
AlphaW0lf2014 said:
I chose the Omnirom because it was the first I heard about. I wanted android 4.4.2 and it seemed all google searches pointed to Omni. Now after running it for a week or two I deal with bugs that I don't want to fight with forever. Volume control doesn't work, random chrome crashes and now tablet reboots. I tried to reach teamomni but no luck. And EOS has built and published nightlies more recently than omni. I know I'm pushing this tab!et beyond its years. I figure this is the end of the road for this device, so I want to squeeze every ounce out of it. I can't thank both teams enough for their work. It's more than I would be capable of ever doing.
Click to expand...
Click to collapse
This is what I'm doing as well. Hadn't used the Xoom in forever but figured I'd try to squeeze more life out of it at this point until Nexus 8 or 9 (whichever it's called) comes out. I was running Omni and kept getting "bug reports", so I've switched to EOS due to the fact that they are more actively publishing updates to the ROM.
Only been on EOS for a day or so, but so far so good. With No-frills CPU control installed the Xoom seems to be running fine with no bugs to report. Settings in no-frills:
CPU Max: 1.504 GHz
Min: 456 MHz
Gov: ondemand
i/o scheduler: row
I just want to restate that I value the time and effort of ALL of these developers who graciously give up hours of labor to do this work. I would hope no one is offended by any of my previous statements of issues.
Omni vs TeamEOS
At first I've installed Omni. I was very happy with it. But after some time I've got performance problems. Also Chrome was freezing many times while browsing around.
So I decided to switch to TeamEOS. I was a fan from EOS since the early days. They kept my Xoom alive. But unfortunenatly I got the same problems on TeamEOS with Chrome. It kept freezing.
Read http://forum.xda-developers.com/showthread.php?t=2738705 if you have the same problem.
At last I am also happy with TeamEOS and it's difficult to say which ROM is better. There are some differences in the preferences and Omni ROM seems to be a bit ahead but at last I'm ok with was TeamEOS offers.
fricklr said:
At first I've installed Omni. I was very happy with it. But after some time I've got performance problems. Also Chrome was freezing many times while browsing around.
So I decided to switch to TeamEOS. I was a fan from EOS since the early days. They kept my Xoom alive. But unfortunenatly I got the same problems on TeamEOS with Chrome. It kept freezing.
Read http://forum.xda-developers.com/showthread.php?t=2738705 if you have the same problem.
At last I am also happy with TeamEOS and it's difficult to say which ROM is better. There are some differences in the preferences and Omni ROM seems to be a bit ahead but at last I'm ok with was TeamEOS offers.
Click to expand...
Click to collapse
The chrome issue boils down to a tegra video driver. It's closed source and has not been updated since the last official release which I believe was 4.1.2
This issue effects many things video related some of it you may see most of it you'll never notice. Since its a closed source driver it's likely to be and issue we will just have to deal with
sent from space
runandhide05 said:
The chrome issue boils down to a tegra video driver. It's closed source and has not been updated since the last official release which I believe was 4.1.2
This issue effects many things video related some of it you may see most of it you'll never notice. Since its a closed source driver it's likely to be and issue we will just have to deal with
sent from space
Click to expand...
Click to collapse
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
After some days of using TeamEOS... The battery usage seems to be much more better!
On the other side TeamEOS freezes from time to time. Only a reset helps.
But hey, there's KK on my Xoom
AlphaW0lf2014 said:
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
Click to expand...
Click to collapse
Are you able to cast screen with chromecast ?
I have de Omni 4.4.4 on my xoom and the cast screen do not work, even with mirror enabler app.
Xoom won't be able to, doesn't matter which Rom, it's hardware level, even if I add all the required files to the make file and enable it as soon as you try it reboots. It's the same issue with screenrecord
sent from space
AlphaW0lf2014 said:
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
Click to expand...
Click to collapse
I've used each of the Kit Kat builds and I finally settled on TeamEOS. This ROM had the most updates and continued to have development after nightlies stopped for Omni and CM. I believe each of these ROM's are really great and each have given new life to our tired Xoom's. The only way you can really tell which ROM is best is to try them and see which you like the most. Hopefully, someday we'll be asking the same questions about which Lollipop version is best, or that may just be wishful thinking. TeamEOS is baked already OC'd to 1400 and you can tweak it higher if you want (I use 1600). I've downloaded Trickster MOD from Google Play and I use it to control governor and other settings. As far any SOD's, I believe you can really minimize the concern if you use Trickster MOD and adjust your CPU min to at least 312 or higher. I had an occasional problem with Chrome so I switched to Chrome Beta and it seems to cause less problems. Some folks will have problems while others seem to get by OK. The stock browser is still pretty decent and gives good performance. I also have the Dolphin Browser but don't tend to use it very much.
---------- Post added at 08:15 PM ---------- Previous post was at 08:11 PM ----------
fricklr said:
After some days of using TeamEOS... The battery usage seems to be much more better!
On the other side TeamEOS freezes from time to time. Only a reset helps.
But hey, there's KK on my Xoom
Click to expand...
Click to collapse
Try downloading Trickster MOD from Google Play and using it to set your cpu min to at least 312 or higher. This may help with freezes.