Hello all. Just curious how much available ram other captivate users have on avg. W/ salty bean I run avg. of 90-110 MB. I thought maybe going down to ICS would help but when I installed Paranoid droid-ICS I ran between 70-95mb.
The reason I am asking is because I experience long pauses of inactivity or freezing. I have already wiped and reinstalled Rom
Captivate /Salty Bean 4.1.2
Thenewguy1 said:
Hello all. Just curious how much available ram other captivate users have on avg. W/ salty bean I run avg. of 90-110 MB. I thought maybe going down to ICS would help but when I installed Paranoid droid-ICS I ran between 70-95mb.
The reason I am asking is because I experience long pauses of inactivity or freezing. I have already wiped and reinstalled Rom
Captivate /Salty Bean 4.1.2
Click to expand...
Click to collapse
Your ram sounds right. My guess is that it's coming from a rogue app, get a app like OS Monitor to see if there's one going up the roof.
Also, what settings are you running on? (governor and such)
Smartassv2 No clocking.
OS monitor shows system and os monitor at the top of the list.
Captivate /Salty Bean 4.1.2
Thenewguy1 said:
Smartassv2 No clocking.
OS monitor shows system and os monitor at the top of the list.
Captivate /Salty Bean 4.1.2
Click to expand...
Click to collapse
Have you tried different governor?
Did you get this problem on other ROMs?
Thenewguy1 said:
Smartassv2 No clocking.
OS monitor shows system and os monitor at the top of the list.
Captivate /Salty Bean 4.1.2
Click to expand...
Click to collapse
These are my settings in the Devil config app... Ram settings - XL, Screen off Min/MaxFreq checked with default values, Governor Profiles - Smooth, I/O Scheduler - noop, CPU Governor - smartassV2. Everything else leave as is.
I've run these settings on Salty Bean as well as Helly and most everything else and they work the best for me. I've always noticed a lag on Salty when I first install it, but when I get settings changed it runs like butter.
Ya I have had similar issues on other ROMs I tried paranoid droid ICS.
I am now using the settings above and rebooted. I'll give it a try for a while and see how it goes.
Thanks for all the responses
Captivate /Salty Bean 4.1.2
Wow no change in RAM but now my phone can actually keep up with me while texting. Instead of me typing everything then a cpl seconds later it appears on my screen.
Captivate /Salty Bean 4.1.2
Thenewguy1 said:
Wow no change in RAM but now my phone can actually keep up with me while texting. Instead of me typing everything then a cpl seconds later it appears on my screen.
Captivate /Salty Bean 4.1.2
Click to expand...
Click to collapse
Yeah for the most part the ROM does a good job on its own managing ram. Its just getting the kernel settings tweaked. Glad its working well for you. If you want to try for a little more speed you can try over clocking but it might cause random reboots.
Sent from my SGH-I897 using xda app-developers app
I have always been curious to experiment with under/over clocking for battery/speed. But don't have a very good understanding of it. I know basics. Maybe I'll just have to read up on it and give it a try.
Captivate /Salty Bean 4.1.2
Thenewguy1 said:
I have always been curious to experiment with under/over clocking for battery/speed. But don't have a very good understanding of it. I know basics. Maybe I'll just have to read up on it and give it a try.
Captivate /Salty Bean 4.1.2
Click to expand...
Click to collapse
I've read about people over clocking to 1200-1400 but its never worked out for me. My phone just doesn't like it and starts doing random reboots
Sent from my SGH-I897 using xda app-developers app
Related
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
yellowfuse said:
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
Click to expand...
Click to collapse
Were you using Glitch before, or some other custom kernel? I didn't think cyanogen's stock kernel supported overclock. If you install a new nightly you have to reinstall your overclocking kernel.
I have been using cyanogenmod only. I never purposefully installed a custom kernel then the rom. Just used Odin to root/clockwork and so forth. Never heard of Glitch. Through out all of my custom rom experiences with the captivate I have been able to use the sys. settings or osmonitor to overclock to a max of 1.3ghz. I have tried miui or whatever its called for about five minutes. other than that just cm6/7, then updated to cm9. in the past whatever kernel i had, stayed in effect, i guess.
I will do a search for custom kernels for cm9 on captivate.
I havent seen any yet, but who knows. I am used to simply stunning roms and the moto droid one. That was great! SS/chevy~ would always have links to the latest kernels avail. for the current builds etc. Good job too.
SO... the search continues.
*Mystery: If I cant even change cpu settings in osmonitor (up or down), yet it lets me enable root mode, what does that mean? The greyed out overclocking area in perfomance settings (up or down)???
I need to learn more"!"
As mentioned, glitch kernel b6 is a great ics kernel. Flash over CM9 and install nstools from the market to control all the kernel settings such as oc/uv, voltages etc etc.
Sent from my glitched ICS Captivate using XDA App
The options are greyed out because the stock kernel currently doesn't support overclocking. Glitch is awesome, and Semaphore kernel is pretty nice too.
Sent from my CM9 ICS i897 Captivate
IcyGlitch for OC, and Semaphore for 400MB mem.
Well Glitch has 387 MB of free RAM
both kernels are good
I want my 13 MB! They are unused so occupying them is unforgivable. IcyGlitch is solid kernel, and I hope 400MB will be added.
b-eock said:
Well Glitch has 387 MB of free RAM
Click to expand...
Click to collapse
I am currently running beans custom stock ROM v5 and I haven't ran synergy yet but I was wondering which ROM was better. Before I get Beans v6 I'd like to have some input on which ROM was better based on battery life/other things.
Sent from my SCH-I535 using Tapatalk 2
Well I started with bean R2 when I first rooted. Then tried synergy which my buddy had phenomenal battery life with. I however didn't even though I was running less and theoretically should have had better. I gave it a week but didn't see any improvement. Went back to bean but tried his updated 3.1. Was better than synergy In my opinion as far as battery life goes but had some quarks with it. Next day he came out with V5 so I flashed that. Had worse battery life than 3.1 but better than synergy. Meanwhile my buddy was still getting better battery life with his synergy. I decided to go back to the original R2 I had at first. It is the best performing For ME. I would try each and see what you like better. I was on my the boat all day today (again, currently running R2) and got 84% 12 hours. Keep in mind most of that was minimal use of texts and web browsing. Mist was screen off with with setcpu screen off profile (348). Still was nice to have a full day with it turned on even if screen was off and then still have a full battery to use when I got off the river.
For me...bean R2 for the win. I don't mind wiping and trying a promising ROM but I also like having a solid ROM that gets me what I want/need without having to worry about what the next new thing is.
Sent from my SCH-I535 using xda app-developers app
I'm also using beans r6. Everything seems a lot smoother...but my phone does run hot. He has the default CPU set at 1.9 gighz. Sometimes it doesn't clock down with the app. I'm going to try synergy when they release the new version...but its hard not to like beans.
Sent from my SCH-I535 using xda app-developers app
I used both, beans r5 kept rebooting on me but the battery life seemed better than stock. Then i switched to synergy 1.3 and it is an awesome rom. 4x5 homescreen alone is worth the upgrade from bean, but the battery is just a little less than bean r5. I have no tried r6 but i dont think i will because i just flashed CM10 an hour ago and couldint be happier. I forgot how much i miss stock android JB (used to have galaxy nexus). its a lot smoother and better to use and look at obviously. Only thing i dislike about the rom is the hardware buttons back and menu dont turn off they stay on if the screen is on, but its not that bad. I saw Flash CM10 you will be happy!
CM10 is a half working rom at this point, don't know how anybody uses it as a reliable daily driver, as for clocking on Bean's rom, you can control it yourself, just run the cpu bin from a terminal window, or use rom tools or setcpu
I use beans but I use beans 3.1 before the stupid overclocked kernel and before kexec kernel /recovery
Sent from my SCH-I535 using Tapatalk 2
p-slim said:
I use beans but I use beans 3.1 before the stupid overclocked kernel and before kexec kernel /recovery
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
the overclock issue is fixed...beans b6 rocks! actually i never had that issue anyways.
I think I'm going to stick with beans r6 I'm loving the jelly bean theme. If your complaining about battery on beans because of the kernel just under clock it or use power saving, your phone will not run hot and you will get better battery life. If you want a higher clock speed use 1512 or 1674 MHz, you may run a little hotter and your battery may drop a little faster than if you were on power saving though.
Sent from my SCH-I535 using Tapatalk 2
bobcaruso said:
CM10 is a half working rom at this point, don't know how anybody uses it as a reliable daily driver, as for clocking on Bean's rom, you can control it yourself, just run the cpu bin from a terminal window, or use rom tools or setcpu
Click to expand...
Click to collapse
I have to disagree strongly with the assertion that CM10 is a "half working rom." If you're not one of the people experiencing data connectivity issues, the current bugs are: bluetooth audio, MMS, camera autofocus with stock camera app (for some), and that native wifi tethering only works unsecured (usb & bluetooth tethering work fine.)
I used it as my daily driver from 7/21 on, and the only thing I personally missed was secure wifi tethering. If the above bugs don't affect things that you use, CM10 is much snappier overall than any of the 4.0 based roms.
I actually decided to try Beans again just to see if I missed any touchwiz features (smart stay, direct dial, etc.)
synergy
I'm currently running synergy v1.3, but i liked v1.2 a lot better. Mainly because the grid size was changed so now widgets look a little weird on my phone =/ but other than that i haven't had a problem. Battery life is insanely good. I used bean's rom when it first came out, got me 50gb of dropbox for free which was awesome. The stock apps weren't on the first build though, that's why i switched over to synergy. I think Bean's rom has them back on though. I suggest trying them both and making backups, they're both very good
Yea Im running Beans v6 just upgraded from either 3 or 2, and yea its wicked fast. I guess with Synergy there are more themes but they should work on Beans too. Anyway it is definitely worth a try just backup beforehand :good:
kabro91 said:
Yea Im running Beans v6 just upgraded from either 3 or 2, and yea its wicked fast. I guess with Synergy there are more themes but they should work on Beans too. Anyway it is definitely worth a try just backup beforehand :good:
Click to expand...
Click to collapse
yeah synergy 1.4 just came out late last night, and it is nice with the google now baked in. try it out
They are both good. It's a subjective preference and you won't know which you prefer until you try both.
Saauron said:
I have to disagree strongly with the assertion that CM10 is a "half working rom." If you're not one of the people experiencing data connectivity issues, the current bugs are: bluetooth audio, MMS, camera autofocus with stock camera app (for some), and that native wifi tethering only works unsecured (usb & bluetooth tethering work fine.)
Click to expand...
Click to collapse
LOL, all those bugs certainly sound like it is half working (or not working depending on how you look at it).
I tried it for a few days & will definitely agree that's it's way to buggy to be a daily driver at this point.
IMHO, to be a daily driver all the native functions the system came with have to work 100%
Yeah synergy 1.4 is insanely snappy and quick. To a noticeable degree. I love v6 of beans though, but synergy just goes without having to be pushed
But I still use both just to get my flash fix, lol. Beans has more of what I'm looking for (aosp theme) with stock feel.
Sent from my Galaxy S3 using Tapatalk 2
Just the thread I was looking for! I am currently getting tired of the random bugs with CM10, but I'm wondering if I can just flash Synergy or Beans the way I have been flashing CM10 builds using the Kexec recovery. It looks like Beans does this method, but I just want to confirm before I brick my phone
Synergy
I'm using Synergy atm and I love it so far..... Battery life is amazing....
FreeRefreshments said:
I am currently running beans custom stock ROM v5 and I haven't ran synergy yet but I was wondering which ROM was better. Before I get Beans v6 I'd like to have some input on which ROM was better based on battery life/other things.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think both are great RomS. I personally have synergy installed right now because it was just released. There are some things I like about synergy and some things I like about beans. With beans you can flash different kernels without any problems but when I try to flash different kernels on the synergy1.4 I keep getting bootloop. Beans and synergy both seem to be pretty good on batter but I also use CPU sleeper which might also help.
Sent from my SCH-I535 using xda app-developers app
adriang1984 said:
I think both are great RomS. I personally have synergy installed right now because it was just released. There are some things I like about synergy and some things I like about beans. With beans you can flash different kernels without any problems but when I try to flash different kernels on the synergy1.4 I keep getting bootloop. Beans and synergy both seem to be pretty good on batter but I also use CPU sleeper which might also help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good call, I'm gonna start using CPU Sleeper now
adriang1984 said:
I think both are great RomS. I personally have synergy installed right now because it was just released. There are some things I like about synergy and some things I like about beans. With beans you can flash different kernels without any problems but when I try to flash different kernels on the synergy1.4 I keep getting bootloop. Beans and synergy both seem to be pretty good on batter but I also use CPU sleeper which might also help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah. 1.4 isn't compatible with custom kernels, I'm waiting for a possible fix until I flash 1.4 just because Imoseyons lean kernel is amazing on this phone. I've gotten a day and a half on a single charge with 4 he's and 29 minutes in screen time..plus I also use CPU sleeper with the lean kernel you can also have your phone speed charge..and I mean really fast compared to stock.
Current~Samsung Galaxy S3 SynergyRom 1.3 & Imo's Lean Kernel v12 Oc'd @ 1.9ghz
~Acer Iconia A500 Stock
Past~Droid X Gummy ICS 1.2
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.
Hey guys, I currently am running Slim bean 4.2.2 build 4 on my NS4g. Sadly, I'm thinking Jelly Bean has to go... I love Jelly Bean and all the features, but since I updated to Jelly Bean, my phone has been running so friggin slow. To the point where it hangs doing simple things. I can't stand it anymore and I just need this thing to last til Sept at least. I've also tried other Jelly Bean based ROMs with similar problems. AOKP was less slow, but it had some weird annoying bugs that bothered me. CM10 was even less slow but I got raped on battery life.
So, sadly, I'm thinking I need to go back to Ice Cream Sandwhich. My phone ran it great back when I had it, but I'm gonna miss JB... Unless anyone has any other ideas? Maybe completely wipe and reformat my SD card? That's the only thing I really thought of. Thought it might clean things up a bit. But my other question was which ICS ROM should I switch to? I was thinking AOKP Milestone 6, CM 9.1, SlimICS, or...?
Thanks in advance.
I recently got my gf a nexus s but hated all the slowdowns and reboots on all jb roms I tried, until I tried jellyshot with marmite 8.5 bigmem kernel. She loves her phone now, hope tbis helps
Sent from my SPH-L900 using Tapatalk 2
xopher.hunter said:
I recently got my gf a nexus s but hated all the slowdowns and reboots on all jb roms I tried, until I tried jellyshot with marmite 8.5 bigmem kernel. She loves her phone now, hope tbis helps
Sent from my SPH-L900 using Tapatalk 2[/QUOTE)
Thanks, I keep hearing good things about the Mar mite Kernel. Ill check out Jellyshot.
Click to expand...
Click to collapse
Try rasbeanjelly also.
Sent from my Nexus 4 using xda app-developers app
Use greenify app from play store. It might help!
How does rasbeanjelly compare to the other JB ROMs? And I just read somewhere else about greenify. Ill look into that as well.
latest hellybean rom with devil kernel(it comes with the rom) is really fast and stable. never had a random reboot with it. try it
I had terrible lag in all the JB roms too. What I did was searching for an efficient kernel. I found marmite, which is fast and stable. I am using the bigmem version with its stock settings, you don't need to OC at all.
As for ICS, I thought it was smoother too, t I found out, it was only because it had less resource-heavy animations. There is a solution for this. Nova launcher has the option to overwrite the default JB animations and change it to ICS ones. In my case it really made a huge difference. If you want to try this, you only have to upgrade your rom to build 5, since Nova is the new default launcher in Slim.
Hope this helps,
Cheers.
ottoemezzo said:
I had terrible lag in all the JB roms too. What I did was searching for an efficient kernel. I found marmite, which is fast and stable. I am using the bigmem version with its stock settings, you don't need to OC at all.
As for ICS, I thought it was smoother too, t I found out, it was only because it had less resource-heavy animations. There is a solution for this. Nova launcher has the option to overwrite the default JB animations and change it to ICS ones. In my case it really made a huge difference. If you want to try this, you only have to upgrade your rom to build 5, since Nova is the new default launcher in Slim.
Hope this helps,
Cheers.
Click to expand...
Click to collapse
As of right now, I am now rocking Rasbean with Matr1x Kernal and I must say, WOW, what a difference. So far the lag has become a minimum problem, depending on what I am doing. Also, the battery life is much better now too. I never OC or anything like that. I had greenify installed but found that most the apps I use cant go into hibernation except the ones I do want updating in the background. As far as animations, I disable those anyways. They are enabled on my Nexus 7, but that can handle it much better than my phone lol. So now I am generally satisfied until I can get the Galaxy S 4. Or if something else happens to come out that is better by the end of the year, but I highly doubt it.
Hi all, I have been happily on cm 4.1.2 for awhile because it has been stable and this is primarily a device for my kids. Lagfix and greenify have been wonderful for good performance.
What is your experience with 4.2.2 and 4.3? Is it worth going to 4.2.2 for performance and stability? I am old school and really like the lower only status bar in 4.1.2 which is gone after that from my knowledge. Perhaps there is an exposed framework change that gets the old interface back. Ha!
I was waiting to see what might happen with 4.3 since that performs better on all my devices including rezound. It looks pretty stable. Maybe I should go for that.
Any comments on path appreciated.
weaverinva said:
Hi all, I have been happily on cm 4.1.2 for awhile because it has been stable and this is primarily a device for my kids. Lagfix and greenify have been wonderful for good performance.
What is your experience with 4.2.2 and 4.3? Is it worth going to 4.2.2 for performance and stability? I am old school and really like the lower only status bar in 4.1.2 which is gone after that from my knowledge. Perhaps there is an exposed framework change that gets the old interface back. Ha!
I was waiting to see what might happen with 4.3 since that performs better on all my devices including rezound. It looks pretty stable. Maybe I should go for that.
Any comments on path appreciated.
Click to expand...
Click to collapse
I'd say that 4.2.2 and 4.3 aren't going to give you much in the way of performance, and may even perform worse. The problem is, there really are no drivers. The 4.2.2 and 4.3 ROMs are still using 4.1.x kernel code and 4.1 drivers, so I really don't think there's much to be gained other than being able to say you're on the latest version of Android. If 4.1.2 is working alright for you, I'd say to leave well enough alone.
oldblue910 said:
I'd say that 4.2.2 and 4.3 aren't going to give you much in the way of performance, and may even perform worse. The problem is, there really are no drivers. The 4.2.2 and 4.3 ROMs are still using 4.1.x kernel code and 4.1 drivers, so I really don't think there's much to be gained other than being able to say you're on the latest version of Android. If 4.1.2 is working alright for you, I'd say to leave well enough alone.
Click to expand...
Click to collapse
Thank you. Glad to have confirmation that things are as good as they seem on 4.1.2. I know the size of the system partition is a real problem for newer builds.
Interesting in the way of performance though because I thought trim was built into 4.3. Also, when I moved on my rezound from 4.2.2 to 4.3....wow what a difference. I really have no reason to move off of that phone because it performs so well.
Say, what clocking do you run it at? I have seen that it runs well from 800 to 1500 Mhz on the top side.
All the best....
weaverinva said:
Thank you. Glad to have confirmation that things are as good as they seem on 4.1.2. I know the size of the system partition is a real problem for newer builds.
Interesting in the way of performance though because I thought trim was built into 4.3. Also, when I moved on my rezound from 4.2.2 to 4.3....wow what a difference. I really have no reason to move off of that phone because it performs so well.
Say, what clocking do you run it at? I have seen that it runs well from 800 to 1500 Mhz on the top side.
All the best....
Click to expand...
Click to collapse
My Xoom is running stock JZO54M/4.1.2 with a locked bootloader and no root. haha Clock speed is 1 GHz stock. Also, I think people are overblowing the trim in 4.3. Yes, it has auto-trim, but it just runs it sporadically. Plus, trimming only helps so much. Increased memory requirements isn't something trim will be able to get you out of.