Develop Bugs

Overclocking XDAndroid Rhodium

So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks

You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.

devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.

Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...

Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.

devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.

Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.

I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.

so nothing on the OC for 2.1 yet?
bump

I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.

on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying

O.S.K. byebye command is msmvkeyb_toggle=off

OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.

Not so smooth interface, could be due to OC?

Hello,
Until yesterday i never OCed my desire, I had DJ Droid rom and it was always smooth and slick in terms of interface and apps jumpiness.
Yesterday I decided to try the 1384Mhz rom from OpenDesire. Done full wipe of course, installed the ROM, then after the installation my Desire was pretty hot (probably due to all sync apps work) even before i installed set cpu or did any OC.
Then I said, ok lets try OC, I installed Set CPU, And tried 1300Mhz level and also the maximum levels. and it froze up, i had to pull off the battary and reboot.
Then I tried 1272, Again froze up during browsing...
Then I tried 1Mhz and ran stress test for long, no errors no freez ups.
However, OpenDesire wasnt slick and smooth for me, I mean during sliding the apps menu, it was not smoooth i felt some slowdowns... same about the main interface windows slide right/left. especially with live wallpapers from some kind.
Is it normal? Could I damage something in my CPU/GPU due to this OC? Which causing this?
I tried even full wipe and again from zero placing the OD rom...still had same feeling of none smoothness.
thanks

Any ideas?

I had this problem. I usually leave my Desire overnight so it can sync, titanium backup, fix permissions etc.
After installation of OD, I find that just signing in, then rebooting, installing extras like statusbar then rebooting, then titanium restore, fix permissions, then a reboot usually sorts me out, leaving my desire on sync overnight (market is very slow after fresh install for me =/)
Very long process
OD supports ext3 for A2SD+. Some users have reported that they had problems with several A2SD roms because they haven't got a ext2/3 partition, or a ext4 which I don't think is supported on OD. This can slow a rom down severely, as the phone is looking for the sd-ext partition.
Final mention would be setCPU itself.
Saying this, I have had issues with the performance scaling or whatever it is called... the "interactive", Ondemand, powersave etc.
I dont trust interactive scaling atm (had alot of FC on Pinkys and OD 3.5), as it seems relatively new, and still has some kinks.
Sticking with ondemand, with a sampling rate of about 20k and a CPU threshold of about 85%, I have pretty good performance. I have found that upon starting up setCPU on OD 3.5.2, the settings are 20k/11% which could be your problem.

Tried now GeFrost, well the apps icons panel ( 5 pages long...) when sliding again had freezy/laggy feeling....I've wiped GeFrost and installed LeeDroid rom with Sense UI, Now i feel good again I suspect that "none sense UI" Simply not for my touch and feel style... Sense UI feels much more smoother just like DJ droid rom i had...
So my CPU isnt damaged and could not get damaged from what I did... right?

rommark said:
So my CPU isnt damaged and could not get damaged from what I did... right?
Click to expand...
Click to collapse
Your CPU could have been damaged from overclocking - I'm not saying that it has been, but there is always an element of risk when you overclock.
If you really want to overclock, my advice is to always start low and then incrementally increase. If you get to a point where the phone starts to become unstable, drop the speed back down a notch.
Furthermore - not all CPUs are made equal. Just because someone else manages to overclock their CPU to 1384MHz doesn't mean that you will be able to - it's just the luck of the draw.
Regards,
Dave

Hey,
Thanks for your answer.
Well on regular clocks its not freezing up to the level where I need pull off the battary...Something that indeed happened to me on OD with OC.
So far LeeDroid rom works smooth.
How can i find out if my CPU got damaged?
Anyone else had such lock ups which needed battary pull off, with OC on Desire?
Thanks!

Whenever you use a OC kernel, you run the risk of damaging the internals.
Non of the internal components are EXACTLY the same. Some can support lower voltages, some can substain higher Clockspeeds.
My lockups with OD is purely on the SetCPU settings.
Have you got a EXT3 partition on your SDcard? Because I see LeeDroid supports Froyo A2SD, while OD&DeFrost Ports are all LegacyA2SD
This may be the problem, instead of a issue with your internals, as the internals would most likely fail/rapidly overheat altogether if there was a problem.

Well I think my desire is warm as usual... not warmer. Only time it was really warmer then usual. Was when i just installed the OD rom and market was syncing all my massive list of apps all together which i think caused CPU over work but thats was even before i installed set cpu and did any OC....
Anyways LeeDroid now works i think as smooth as DJ droid. without any OC.
As for your question about EXT3 How do i check that? could this cause the lock ups with set cpu while using OD oced?
thanks

ext3 is a linux filesystem partition that you would of installed onto your SDcard, either by RomManager or Linux LiveCD/Linux OS
As your unsure, I'm pretty certain that you have not partitioned your SDcard. With A2SD+ (which are both on the OD and Frost roms), the phone is told to read Apps and delvik cache from the SDcard. This means no applications are actually installed on the phone, but the "internal" memory is now the ext3 partition on your SDCard.
Ext3 is required for both OD and De/GeFrost roms.
With this, it sounds like your CPU is fine, as LeeDroid is running fine, and that you are using Froyo A2SD.

Danifamous said:
ext3 is a linux filesystem partition that you would of installed onto your SDcard, either by RomManager or Linux LiveCD/Linux OS
As your unsure, I'm pretty certain that you have not partitioned your SDcard. With A2SD+ (which are both on the OD and Frost roms), the phone is told to read Apps and delvik cache from the SDcard. This means no applications are actually installed on the phone, but the "internal" memory is now the ext3 partition on your SDCard.
Ext3 is required for both OD and De/GeFrost roms.
With this, it sounds like your CPU is fine, as LeeDroid is running fine, and that you are using Froyo A2SD.
Click to expand...
Click to collapse
Thank you for your kind help.
Should Desire feels warmy in hand during its being connected to computer's USB?
Thanks!

Yea, thats usual. There is still power coming from the computer to charge the battery, so its fine.
I've had my phone hit about 50 Celsius on several occasions, while I've fell asleep ontop of it while playing music, and so far, no visible damage to performance etc
Again, the issues with OD just seem to be based around the lack of a ext3 partition on your SDcard, so don't worry too much about the CPU being damaged.
Just be cautious in the future with OC, and never OC more than you need It can drain more battery, and end up breaking your phone (in extreme cases).

Danifamous said:
Yea, thats usual. There is still power coming from the computer to charge the battery, so its fine.
I've had my phone hit about 50 Celsius on several occasions, while I've fell asleep ontop of it while playing music, and so far, no visible damage to performance etc
Again, the issues with OD just seem to be based around the lack of a ext3 partition on your SDcard, so don't worry too much about the CPU being damaged.
Just be cautious in the future with OC, and never OC more than you need It can drain more battery, and end up breaking your phone (in extreme cases).
Click to expand...
Click to collapse
Thank you so much,
So indeed OD / Gefrost was an EXT3 issue (lock ups, super slow down and lock ups which caused battary pull offs). How can i confirm this?
While DJ droid and LeeDroid working smooth with Sense UI.
thnx!

Only way is to reformat the SDcard, either with Rom Manager which is easiest (available for free on Android Market) or a Linux variant. This will remove all data currently on the SD, so back up everything
Add a ext3 partition to your SDCard (swap size is unnessacary), and install OD/GeFrost.
There will be a major boost in performance compared to previous times.

a simple way to get rid of lag (most of it)

hi everyone, i'm no expert on phone, so don't kill me if i sound stupid
been using my galaxy S for about 4 months now. and yes it does lag compare to the iphone, or other HTC phones. so i been trying to find out, what's going on? why is my top end phone lagging? here's what i found:
1) when does it start to lag badly?
i installed system panel which gives me a nice list of active and inactive apps, and how much free ram i have left. the phone ALWAYS starts to lag like crazy when ram gets below 60mb. this is a problem - samsung is not giving us enough free ram to play with as once we run a few apps (market, internet especially), we're reaching the 60mb point already. when the phone gets to the 60mb mark it tries to manage the apps by closing some less important ones. but it lags BADLY while doing so.
what's gonna happen is the phone gonna get into this never ending cycle of closing apps and laggin as it's stuck in around the 50mb-60mb mark.
i can solve this by going to system panel and closing all inactive apps. then the ram is gonna go back to around 140mb. however after opening a few apps, once again it goes back to below 60mb and the lag starts again.
2) autokiller
guys been saying autokiller is great and they go with the aggressive settings. i tried it and it made the phone worse. why? because instead of killing apps at the 60mb mark it starts killing apps even sooner! that's wasting battery, wasting free ram, and making the phone even slower. we don't have enough free ram to begin with, so we should make max use of it. here's how i do it:
1) root the phone. install autokiller from the market.
2) instead of using high aggressive settings, use the LOWEST settings. i use advanced mode and then enter all values to 8mb only.
now it is awesome!! the phone never lags until you get it down to around the 20mb mark. you now have around 40mb of extra ram to use (of course autokiller does use some ram but no big deal). the lag starts much latter. u may not think 40mb is a lot but it is in practice!
if you dont believe me, you can try it. it may or may not work for u, but it's definitely working for me. of course, once the ram falls below 20mb, it may be a good idea to close some inactive apps yourself, LOL
but really, samsung should give us at least 100mb more free ram, i can't believe i even have to do this!

Well you point one issue that lag happens, but almost every custom kernel/Rom use memory tweak that Make you around 40MB more to start with.
And yes autokiller don't work good.
The program in the phone is the best to use.
The main lag issue is the filesystem.
Even these can be fixed with many different kernel/Rom.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram

i don't disagree with what you're saying. but a few things to add:
1) i have not applied lag fix myself but i have a friend who has. i dont feel his phone is much quicker than mine in reality. also, his phone crashed after a few weeks and he had to do a hard reset. what we REALLY need is more ram. if we have lots of ram, who cares about the file system? we don't even need any swap from the file system. just let everything stays in ram where it is the quickest.
2) i'm not using any custom roms. if custom roms give me extra 40mb, and then i adjust the auto killer setting to low, that gives me 80mb extra to play with. great.
autokiller DOES work good i feel if you're doing what i'm saying. maybe u have already tried what i'm doing, i don't know, but if you have not, then i highly recommend you to try it.

like i said i'm no expert on this, but autokiller is so easy to install and adjust, and that i feel anyone here can use it
maybe flashing custom firmware is easy to do, i haven't tried it, but it sounds complicated to do for me, and i don't want really big changes on my phone, i want it to be extremely stable and safe as i use it a lot for business. i don't really want to risk any data or risk reinstalling stuff.
so maybe i sound uneducated but like i said i suggest everyone to try this method if they're newbies and don't wanna do too much

I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!

i have a buddy with a moto milestone and his phone lags just the same as ours. his phone has even less free ram than ours and so his is constantly lagging. sometimes he can't even take a phone call while listening to music becoz his phone only has like 50mb of free ram after starting up. so, just a point of reference - our galaxy is crippled with just not enough free ram, i heard stories of nexus one having 200+ free ram after startup and that's why they dont lag like us, so at the end of the day we're fighting a losing batter becoz samsung didn't give us a good enough phone

Mycorrhiza said:
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
Click to expand...
Click to collapse
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.

You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.

supraman123 said:
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
Click to expand...
Click to collapse
If we know the amount of time and money Samsung spend on developing RFS...

So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.

I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App

Mycorrhiza said:
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
hi, thank u, can u tell me how to secure the data? or u have any good links to show me? thanks

jjwa said:
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
Click to expand...
Click to collapse
i hope it will work good for u also

xmonkee said:
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
Click to expand...
Click to collapse
i'm quite disappointed at the ram issue also. coming from a n97 mini which seriously lacks ram, i was hoping by going for a high end phone like the galaxy, i aint gonna have to worry about ram and closing apps manually all day, however in reality the Galaxy aint much better than the n97 at multi tasking. of course, it's far better than the n97 at everything else.

I totally agree with OP on this one!
But Autokiller is not the only app that can fix the lag.
One Click Lag Fix 2.0 can root your SGS (Eclair only), lagfix it (with EXT2) and it can even do some additional tweaks like minfree (same as the Autokiller app) and fix the Scheduler.
With minfree Samsung put these values in "/sys/module/lowmemorykiller/parameters/minfree":
"2048,4096,5120,5632,6144,7172"
But best is:
Aggressive: "1536,2048,4096,21000,23000,25000"
or
Strict: "1536,2048,4096,15360,17920,20480" - I prefer this one

btw when you've a lot of ram free the ram is mostly used to cache file system reads ^.^
this explains that a little

Im using the 341MB of free ram so that gives me an instant 40MB ontop of the stock kernel, never seen the phone had less than 60mb free with this kernel, with my usage it doesnt even go under 95mb free.

I am also running one of those kernels that gives extra RAM. And I have all my partitions Ext4 lagfixed. But my phone still seems quite slow at times. My RAM was above 80MB free at that time though, so probably not related to any minfree/Autokiller thing at all. Which means there are way more causes to get rid of I guess.

I don`t know how you guys have problems with the lag, I use the stock samsung JPO, not even deodexed with zankinz 23 kernel and NO-RFS all ext4 lagfix and the phone is running perfectly, no lag whatsoever, the RAM is somewhere near 220 mb free after reboot. After deodexing and optimizing the apk`s the phone should run even better. I was determined to change my SGS with a Desire HD, but now I`m really thinking of keeping it.

[Q] Ideas for more speed?Kernel?Tweak?Different ROM?

Hi,
actually i running CM7 XboarderMOD V3.0.1 with Kernel [email protected]#1 downclocked Wake 245/768 Ondemand Sleep 245/315. Launcher GO EX With some AddOns
Batterylife is not really good but quite ok.
Now im looking for a ROM which is more faster, or only a Kernel.
What can i try.
Since today i have a new problem: suddenly the Music player starts to play any song without request that. what the hell is wrong with this thing.
I was figuring out to try the actual ILWT-388, but not shure if its really faster.
What could increase my device speed? Whats about EXT4 or all the Kernels.
My Device is actually starting random apps without request (no idea if this is normal or not) but it runs out of Memory and i need to terminate the processes via the launcher. then i have 100/367MB RAM available. What do you think about a SWAP partition? (i use a class 10 SD Card) If swap is kindly necessary; how to install/activate it?
Hope my english is readable
Thanks for some discussions.
So far Nissl

XboarderMOD? It's pretty old honestly...
If you want CM7 you can go for a number of choices...
Personally, I've tried ILWT and EliteMod and they're both excellent.
ILWT is absolutely amazing because you can customize it before installing, and being able to do that is absolutely essential for people who go back and forth through ROM's. It also has plenty of memory free (I always have close to 150MB free when idle), and is very, very, VERY fast.
For EliteMod, I honestly haven't tested it nearly as much but it has great battery life if you take advantage of all the tips the dev offers. It's also in the same league with ILWT when it comes to speed.
To increase speed, I'd go with SuperCharger V6 using the SuperMinFree Calculator's settings. (Go to the Cust-OOM-izer, it will prompt if you want to use them there)
One other thing I've tried was "Sick Speed Tweaks". It is pretty nifty, here it is: http://forum.xda-developers.com/showthread.php?t=1267945
Lastly...swap, if anything, is going to degrade your battery life and SDCard lifespan (quite drastically in some cases). It's a BAD idea to use it, even on a Sense 3.X ROM, much less for a CM7 one, which already has tons of RAM free.

i Thank you so much bro.
i want to try ILWT first then on my second G2 the EliteMod.
I post my experience later.
Thanks again.

One Question: Which launcher should i try for enjoy most speed?

nissl said:
One Question: Which launcher should i try for enjoy most speed?
Click to expand...
Click to collapse
LAuncherPro or zeam launcher! The best in my opinion!
Inviato dal mio HTC Desire Z usando Tapatalk

I use ADW EX (paid version). It's totally worth it as it's really smooth, and is theme-able. If you don't want to pay I guess what you're already using (GoLauncherEX) and the above suggestions are quite nice.

So here again.
Im running ILWT 388b and its ok, the ram problem is gone, for now.
One simple question. Im setting with "ILWT CM7 Settings " the CPU clock to Ondemand 245/576 MHZ but it will not hold these settings. It sets to 245/1113 by itself.
Anyone an idea to prevent this?

You can use Clock Daemons, like CPU Tuner or SetCPU, it works wonders

Here are 2 Clock settings in the Menu in the CM7 Settings and in ILWT Tools.
My problem could be that the two menu have a conflict. Settings i set seems to reset by itself (the other setting menu?)
I already tried it with edit the configurationfile manually. Seems that is not working, too.
Should i edit the OC-Kernel setting conf?
i dont know what to do, cause i don't really want to install another SetCPU app or something. =)
now the settings with the config file from ILWT tools are:
Wake 245760/768000 conservative
sleep 245760/245760 conservative
charge 245760/1017600 ondemand
temp 245760/768000 conservative
battery 245760/768000 conservative
I think it scales higher than 768mhz because i got every time more than 2000points with Quadrant, same if i set the OC to Ondemand till 1GHZ.

LAuncherPro is fastest launcher i had (including GO Launcher and ADW launcher) .. It´s simplier than other two, but much faster.

dev options for graphics apps question

Having been talking to various people about various art apps. The concensus seems to bee that beyond 2000 x 2000 most devices suffer from lag and performance issues with drawing programmes. My assumption is that this is due to both processor and RAM demand but have wondered if playing with some of the settings in the dev options would help with this.
I know that android is designed to ballance apps in the background on the fly, but when your main use it to use just the one app, would playing with the "limit background processes", "force gpu rendering" and other options I perhaps have not considered help with the performance of the app in question (even if its at the cost of having a slower tablet in general due to having to load up processes on the fly rather than having them stored in RAM)?
Would this also help with resource intensive games?
I already turn all the animation options off, have a plain background and limit the number of widgets on my homescreens in order to free up as much as possible for my art apps in question.
I also use Greenify to limit apps opening on their own accord and use a gaming booster than shuts down other background apps and stops them opening when said art apps are in use.
I used to OC, but have gone back to 1600mhz and 533mhz for the CPU and GPU respectively having had concerns with how hot my tablet gets in the edge of the screen under load.

hertsjoatmon said:
Having been talking to various people about various art apps. The concensus seems to bee that beyond 2000 x 2000 most devices suffer from lag and performance issues with drawing programmes. My assumption is that this is due to both processor and RAM demand but have wondered if playing with some of the settings in the dev options would help with this.
I know that android is designed to ballance apps in the background on the fly, but when your main use it to use just the one app, would playing with the "limit background processes", "force gpu rendering" and other options I perhaps have not considered help with the performance of the app in question (even if its at the cost of having a slower tablet in general due to having to load up processes on the fly rather than having them stored in RAM)?
Would this also help with resource intensive games?
I already turn all the animation options off, have a plain background and limit the number of widgets on my homescreens in order to free up as much as possible for my art apps in question.
I also use Greenify to limit apps opening on their own accord and use a gaming booster than shuts down other background apps and stops them opening when said art apps are in use.
I used to OC, but have gone back to 1600mhz and 533mhz for the CPU and GPU respectively having had concerns with how hot my tablet gets in the edge of the screen under load.
Click to expand...
Click to collapse
I don't use any apps for drawing and rendering. But, within the last month, I have noticed a huge improvement in performance swapping out my class 10 SD card for a professional quality 633x SD card. I would think any card capable of both 65+ MB/s read and write should help with bottle necks. Though you want to set your app to use the SD card for saving, as it will utilize caching to SD card. I have setup my device to point to SD card for most all app saves and caching. Some apps will use system cache, so unless you are able to tweak further, there is no way to unlimit stock caching. Though I do have trickster mod (Though it is very limited with stock ROM), and found bumping from 128 read ahead cache to 256 to 384, as it seems best with how I utilized my ultra fast SD card. Also you may set the Governor as well, but I have a feeling that is pretty much the same as what you are doing in Greenify. As for antivirus apps, they all have some ways of checking what is going on. If you can temporarally disable and test it may help.