Related
just see this would be nice lol
http://androidcommunity.com/nexus-one-running-450-faster-thanks-to-froyo-android-2-2-20100511/
this is being discussed about 4 threads down...
Indeed but does "running 450% faster" mean overclocking the snap dragon?
ChillRays said:
Indeed but does "running 450% faster" mean overclocking the snap dragon?
Click to expand...
Click to collapse
no it means jit and a very well written version of android
bobdude5 said:
no it means jit and a very well written version of android
Click to expand...
Click to collapse
Thanks bob. Now i'll spend the next 30 minutes searching google.com to find out what "jit" means.
ChillRays said:
Thanks bob. Now i'll spend the next 30 minutes searching google.com to find out what "jit" means.
Click to expand...
Click to collapse
30 minutes? Nah!
http://en.wikipedia.org/wiki/Just-in-time_compilation
In computing, just-in-time compilation (JIT), also known as dynamic translation, is a technique for improving the runtime performance of a computer program. JIT builds upon two earlier ideas in run-time environments: bytecode compilation and dynamic compilation. It converts code at runtime prior to executing it natively, for example bytecode into native machine code. The performance improvement over interpreters originates from caching the results of translating blocks of code, and not simply reevaluating each line or operand each time it is met (see Interpreted language). It also has advantages over statically compiling the code at development time, as it can recompile the code if this is found to be advantageous, and may be able to enforce security guarantees. Thus JIT can combine some of the advantages of interpretation and static (ahead-of-time) compilation.
Several modern runtime environments, such as Microsoft's .NET Framework and most implementations of Java, rely on JIT compilation for high-speed code execution.
Click to expand...
Click to collapse
http://www.androidspin.com/2010/02/18/jit-compiler-for-android-just-in-time-for-google-io/
JIT stands for “just-in-time” compilation or “dynamic translation”. It compiles/translates bytecode into native machine code at runtime before native execution. This allows software to run faster and perform better.
Click to expand...
Click to collapse
Thanks Paul. Much appreciated.
i lovve wikipedia
all that jibber jabber means BOOST for Android. Now can we has some mind blowing 3D apps?
I read somewhere that the speed increase will only really work with some applications and the new JIT compiler wont have much effect on things such as 3D games.. Can someone confirm this?
3D games are typically limited by the GPU, and JIT won't help too much in that regard, but if the game is CPU intensive, then it should help.
Few things really seem slow on the N1, so I'd guess this is actually better news for those with older phones. But at least more CPU efficiency means less processing time, which means slightly better battery life, even if a delay is introduced when JIT compiles something during boot/launch.
You can try out an unstable version of JIT on CM 5.0.5.3 or whatever it is. It gave the Linpack benchmark a 200% boost and things did seem a little faster when I used it a few weeks ago (I seem to recall app dock scrolling was much better). Stability was pretty poor which is why Cyan et al have been waiting for Google to fix up JIT.
Won't be better for people with older phones because they won't see 2.2 for months and months and months. Most haven't even seen a 2.1 upgrade.
And the thing that would help 3D games is Open GL ES 2.0 support and a proper SDL lib
MODS
can we get thread moved to other discussion or locked?
LevitateJay said:
I read somewhere that the speed increase will only really work with some applications and the new JIT compiler wont have much effect on things such as 3D games.. Can someone confirm this?
Click to expand...
Click to collapse
Parts of some 3D games are written in the NDK. Anything compiled natively cannot be accelerated by JIT (they are already freaking fast).
spazoid said:
can we get thread moved to other discussion or locked?
Click to expand...
Click to collapse
You see that little triangle with the exclamation point on the top right of every post? That's how you report something to mods, rather than "Mods!".
spazoid said:
can we get thread moved to other discussion or locked?
Click to expand...
Click to collapse
can u stop being a troll and go find something else to do instead of complaining and trolling forums?
Pardon me if this has already been discussed extensively, but with JIT implementation in 2.2, what speed increases can be noticeably snappier in real life use? A given would be flash support, yes, but where else? Will cold opening market, camera, browser see any change? Will initial loading up of games be affected? Swiping through home screens?
I'm all for free performance increase, but it seems that everyone is getting over excited because it can crunch out equations faster.
cxdist said:
Pardon me if this has already been discussed extensively, but with JIT implementation in 2.2, what speed increases can be noticeably snappier in real life use? A given would be flash support, yes, but where else? Will cold opening market, camera, browser see any change? Will initial loading up of games be affected? Swiping through home screens?
I'm all for free performance increase, but it seems that everyone is getting over excited because it can crunch out equations faster.
Click to expand...
Click to collapse
I can get my tip amount to my waiter 450% faster than I can now.
If that doesn't pump blood to your tool, I don't know what will.
cxdist said:
Pardon me if this has already been discussed extensively, but with JIT implementation in 2.2, what speed increases can be noticeably snappier in real life use? A given would be flash support, yes, but where else? Will cold opening market, camera, browser see any change? Will initial loading up of games be affected? Swiping through home screens?
I'm all for free performance increase, but it seems that everyone is getting over excited because it can crunch out equations faster.
Click to expand...
Click to collapse
The Nexus One does nothing but crunch out equations
Thing is, we don't know what kind of difference its going to make, but it will NOT be 450%, anyone expecting this WILL be disappointed.
The best guess we can make is running JIT enabled ROMs, when I ran one on the Hero the Linpack score jumped, but I did not notice ANY speed boost in real use
JCopernicus said:
I can get my tip amount to my waiter 450% faster than I can now.
If that doesn't pump blood to your tool, I don't know what will.
Click to expand...
Click to collapse
How about getting the waiter to tip you?
Is anyone else experiencing this? On web pages or long lists, scrolling around is not nearly as smooth as it should be. My brother has a Hero, and the Evo is not as bad as that... but it is nowhere near as smooth as an iPhone is. If I scroll around quickly, it gets pretty jumpy, where the frame rate slows down a lot. I read another thread (maybe on a different forum) where people claim that it's just the difference between the speed of scrolling and/or the "coasting" feature of the phones, but this is not what I'm referring to. I'm referring to mainly the frame rate of scrolling around and also the lag between when my finger moves and when the action takes place. It is most apparent on bigger web pages and long lists (like the Manage Application list). But it also does not happen all the time.
I have Advanced Task Killer running too, set at "Crazy" and the kill frequency set to "When screen off". Is there anything else I can do to make scrolling smoother?
I'm sick of having my friends who have iPhones playing with it, and immediately commenting on how it's not nearly as responsive.
Any ideas?
I played with an EVO in the Sprint store yesterday and noticed the same thing. While overall I found it to be really fast, in some areas (like switching between home screens) it was noticeably choppy compared to my Hero. Though I should note that my Hero is rooted and running Fresh 2.1.1.
One suggestion I might make is to not use overly aggressive settings with a task killer. This has been known to cause some odd behavior with Android including choppiness.
Working amazingly for me. As close to the smoothness of an iPhone as I've ever seen.
Have you tried a full restore? Keep checking after each app installation to figure out what (if anything) is causing the problem.
Sent from my HTC EVO using Tapatalk
Do you have Live Wallpaper running?
I do not. In fact while "conditioning" my battery, brightness down minimum, WiFi/GPS/4G/Bluetooth all off as well.
Sent from my HTC EVO using Tapatalk
How much free memory do you have?
I noticed the choppiness too but it wasn't too bad, just unfitting of a phone with such high specs.
It's because of the Live Wallpapers, some are more processor intensive than others so some it's more noticeable on than others. Put a regular Wallpaper up and everythings nice and smooth.
I don't use Live Wallpapers anymore, they were cool for awhile but after a couple months of them on my Nexus the novelty has worn off.
I notice it also even with a regular wallpaper..i mean its pretty smooth but it does lag a bit.
I notice laggy scrolling within the HTC-built applications. For example, when looking through contact information or social updates. The scrolling is really bad, and I think that just might be because of the huge amount of information the HTC apps are processing. I'm sure all the social information being pulled from every end of the Internet isn't the easiest thing for the device to do, even if it is the Evo.
Aside from that, everything else is as smooth as butter.
Still stock on mine and I haven't noticed any lag, though I use Dolphin HD and Skyfire.
I don't have Live Wallpaper running, and about 200MB of free memory.
And I don't think it's with the HTC-built applications only. I notice it in most applications. Just put an iPhone right beside it and scroll around on both... huge difference.
I just changed the settings on Advanced Task Killer to Aggressive (down from Crazy) and Every half hour (down from When screen off). Maybe this will help... we'll see. Maybe Advanced Task Killer is not the best app for this? Are there any better ones? Why didn't Google have this built in if it really helped so much with speed+battery life?
Maybe FroYo will fix this issue? Does anyone know when this will be available?
shawnee4885 said:
Maybe FroYo will fix this issue? Does anyone know when this will be available?
Click to expand...
Click to collapse
I have noticed this too at times. Froyo made my Nexus One a hell of a lot faster, it will do the same for the Evo
Still on Stock rom and no root, scrolling, pinch zoom are all smooth and fast.
theoner1 said:
Still on Stock rom and no root, scrolling, pinch zoom are all smooth and fast.
Click to expand...
Click to collapse
Have you compared it to an iPhone though?
shawnee4885 said:
Have you compared it to an iPhone though?
Click to expand...
Click to collapse
I've seen this too and mentioned it to other Android people... and was promptly called a cry baby. I am coming from a 3gs...and just thought it was silly the 1ghz chip in this phone cant compare to the 600mhz chip in the iphone.
Grims said:
I've seen this too and mentioned it to other Android people... and was promptly called a cry baby. I am coming from a 3gs...and just thought it was silly the 1ghz chip in this phone cant compare to the 600mhz chip in the iphone.
Click to expand...
Click to collapse
It's all about the quality of the programming, i'm not calling htc programers bad but it seems like some of their stuff is just slow.
Grims said:
I've seen this too and mentioned it to other Android people... and was promptly called a cry baby. I am coming from a 3gs...and just thought it was silly the 1ghz chip in this phone cant compare to the 600mhz chip in the iphone.
Click to expand...
Click to collapse
First u have to realize that the iphone was built with its gpu base OS. So all the scrolling and animation are base on gpu WITH THE HELP OF CPU. Android will be more dificult since of all its different hardware. Iphone OS is just base on iphone hardware but If iphone was running without gpu support, it would move like crap.
One example of this is zuneHD. it is base on a hardware base on tegra with gpu support and is smoother than iphone since tegra is a more capable gpu chip.
This discussion has been on and off with palmpre guys and waiting for an update to enable gpu support in the OS. Gpu support is supported in game but not in the OS for scrolling etc. Just like android.
This is the reason the iphone can run smooth at low mhz. The iphone 2g even at its low mhz still is smoother in scrolling and transiction than android because of it gpu intigrationbut ofcourse not faster. Hope this help.
Another example is compiz for linux. It create a semi gpu OS of linux and u can see how compiz on linux look light yeat better and smoother than wimdows 7 with a much lower hardware spec.
eduardmc said:
First u have to realize that the iphone was built with its gpu base OS. So all the scrolling and animation are base on gpu WITH THE HELP OF CPU. Android will be more dificult since of all its different hardware. Iphone OS is just base on iphone hardware but If iphone was running without gpu support, it would move like crap.
One example of this is zuneHD. it is base on a hardware base on tegra with gpu support and is smoother than iphone since tegra is a more capable gpu chip.
This discussion has been on and off with palmpre guys and waiting for an update to enable gpu support in the OS. Gpu support is supported in game but not in the OS for scrolling etc. Just like android.
This is the reason the iphone can run smooth at low mhz. The iphone 2g even at its low mhz still is smoother in scrolling and transiction than android because of it gpu intigrationbut ofcourse not faster. Hope this help.
Another example is compiz for linux. It create a semi gpu OS of linux and u can see how compiz on linux look light yeat better and smoother than wimdows 7 with a much lower hardware spec.
Click to expand...
Click to collapse
Thanks that explains a lot, i wasn't aware Android doesn't use GPU support in this area.
I just wanted to throw this in. I know everyone is comparing things like the scrolling framerate to the iPhone's. But there is one slight issue that a lot of developers can tell you off the bat.
JAVA
iPhone is not based on java and android UI is. This is sort of why JIT is slated to make such a big difference. Java is just laggy, especially when it comes to UI. For instance: open office, eclipse, and just about any other java based app I see on linux. GTK apps are fine in ubuntu, but when I open eclipse I just know there is a delay between when I click the "file" menu and when it actually opens.
I noticed it on my hero, and no amount of free ram or killing apps would completely get rid of it. Now I have to say going from the hero to the evo I honestly do not notice any lag. But the UI on the hero just has a solid delay EVERYWHERE you go. But I noticed it was not there as soon as I got into a game written in the dalvik way. It will come, and we will eventually be there. But I don't blame it on hardware. Core2quad in eclipse and the UI lags? Blame it on Java.
Now I know some folks will say "nu uhh. such and such java android app doesn't do that!" But almost all apps for android and sense do this if they are written in java. Some more than others.
One final thing, there are several articles about why you shouldn't use task killers. It became perfectly clear it was a bad idea on some of toast's later kernel. and yes, the memory management can be improved for root users. but for non root users, I know it is counter-intuitive but task killers have major drawbacks. Just do some searching and decide for yourself, but I noticed a huge difference on my hero when I stopped using a task killer and allowed the default memory management to take over. And honestly, on my EVO I don't EVER notice a slow down.
It sounds like everyone would benefit from using this script, but there's no specific guidance for the MyTouch 4G. I assume option 8 or 9 would be best since the phone has 512MB of ram.
Are there some roms that we shouldn't be using V6 SuperCharger with?
Link to V6 SuperCharger: http://forum.xda-developers.com/showthread.php?t=991276
You're wrong on 2 points (possibly more):
1) This script is just the same as Autokiller app, with a small addition - it can (or can't) keep launcher in memory. Nothing new and revolutionary. This app exists for a couple of years.
2) This phone has 768MB of RAM. It won't benefit from a low memory killer (or actually, different settings for an existing in OS lowmemkiller), because it has TONS of memory. I just took a look at my phone, ~100MB of memory free, and ~300MB of remaining memory is taken by CACHED apps. If you don't know what it means - please read up on Android memory management, and I'll give you the short version - it's the same as free memory, but better.
It states in the first post:
Also Note: Nothing else does what The V6 SuperCharger does!
................Not AutoKiller Memory Optimizer, Not Auto Memory Manager, Not Minfree Manager...
The Nook Color has 512 MB of ram and people have noticed a big difference using this script on Cyanogenmod.
but since the Glacier has 768MB of ram, you won't notice much change.
saranhai said:
but since the Glacier has 768MB of ram, you won't notice much change.
Click to expand...
Click to collapse
I have found it useful on ports and ROMs that aren't tweaked specifically for this phone. For instance, if TDJ made the ROM, V6 is useless. In fact, it will only hurt.
Sent from my HTC Glacier using XDA App
I use this script on my evo and its great so I just rooted this phone and flashed the mik runny ROM, I was using it for a day and only stayed at about 100mb of RAM so I decided to use v6 with option 8 and now it stays around 200mb and is running super smooth.
IDK if that helps any but I always loved v6 and know a few people that use it on a few different phones and it always works for the better.
Sent from my HTC Glacier using XDA App
Why do people that know nothing or close to nothing about OS internals, decide that they have better knowledge of memory management should be, then OS and phone designers? The same people who don't know the difference between cached and active apps, and the only number they understand is the (useless) amount of free memory? I see it all over the forums, and it amazes me each time. How do people actually try to judge if something works well or not, without getting at least some basic understanding of how the things work?
Oh well, here it comes again:
http://forum.xda-developers.com/showthread.php?t=678205
Read this. Maybe you will understand something.
Few, if any, 512MB phones and no 768MB phones need this script, or any kind of tweaking for lowmemkiller values, especially not since Gingerbread and when not running Sense (which retains the ability to cache apps, removed in Gingerbread mostly to ease running the OS on older devices). The only thing it does, is to make garbage collector work harder and kick in earlier. It doesn't make your phone "smoother", and whoever think it does - should check the meaning of the word "placebo" in the nearest dictionary. The number that stands for "free memory" means something between "close to nothing" and "absolutely nothing".
I know I shouldn't be surprised, people always tend to have strong opinions on everything, even things they sometimes don't know a thing about. But still, it's XDA-Developers, not XDA-Phone-users, so at least something should be done about it. Even if the education attempts will fail, like they mostly do.
Jack_R1 said:
Why do people that know nothing or close to nothing about OS internals, decide that they have better knowledge of memory management should be, then OS and phone designers? The same people who don't know the difference between cached and active apps, and the only number they understand is the (useless) amount of free memory? I see it all over the forums, and it amazes me each time. How do people actually try to judge if something works well or not, without getting at least some basic understanding of how the things work?
Oh well, here it comes again:
http://forum.xda-developers.com/showthread.php?t=678205
Read this. Maybe you will understand something.
Few, if any, 512MB phones and no 768MB phones need this script, or any kind of tweaking for lowmemkiller values, especially not since Gingerbread and when not running Sense (which retains the ability to cache apps, removed in Gingerbread mostly to ease running the OS on older devices). The only thing it does, is to make garbage collector work harder and kick in earlier. It doesn't make your phone "smoother", and whoever think it does - should check the meaning of the word "placebo" in the nearest dictionary. The number that stands for "free memory" means something between "close to nothing" and "absolutely nothing".
I know I shouldn't be surprised, people always tend to have strong opinions on everything, even things they sometimes don't know a thing about. But still, it's XDA-Developers, not XDA-Phone-users, so at least something should be done about it. Even if the education attempts will fail, like they mostly do.
Click to expand...
Click to collapse
I do understand that in some cases you don't need a memory manager like if your running a stock ROM or an aosp ROM that doesn't take up as much memory.
Now I haven't had this phone long enough to say if this script is all that good for this phone but I know on the evo running a sense 3.0-3.5 ROM that wasn't meant for the phone and hugs up every little bit of memory that the phone has to offer, this scrip makes those ROMs usable.
Without it or something like it the phone can't handle doing simple tasks like using an app without fc something else like the launcher.
So you could say what you want and yes maybe this phone doesn't need it since it has more RAM and ROM but I'll still try things like this to try and see if it will better the phones performance.
Sorry if that doesn't make sense I'm still half asleep.
Sent from my HTC Glacier using XDA App
The instances where i have noticed that this works is while doing benchmarking with quadrant. It has shown increased framerates for me after running the script and I also get higher scores on quadrant, about 500-1k more than without. I dont know if its usefull for much other than benchmarking though. I think the phone runs fine without it though.
What you have to understand is performance is not measured via syntactic benchmarks (ex: Quadrant). The biggest issue with people is that they don't know enough to know that they don't know, so they compare it with silly numbers (ex: score) they can't comprehend what they see, much less put numbers behind real life activities that's not applicable in controlled environment.
Now far as V6-SC script goes its almost obsolete now due to few things. 1) Hardware advancement where now minimum spec requirements for "SmartPhone" are 1ghz single core proc with 512mb ram. But so called "SuperPhone" now has dual core 1ghz-1.5ghz with 768mb-1gb ram. So it make no sense as we don't use 256-566mhz proc with 64-256mb ram because we are more then enough hardware adequate for heavy daily usage. 2) OS development which elements most of it as hardware is more and more powerful. But on software level mostly all custom base rom (ex: CyanogenMod) is highly optimized and tweaked to run on optimal performance.
Now is it all placebo effect? Mostly, but not all. But does it mean it can't be tweaked any further? (Rhetorical) No. How do I know? We (scope outside of XDA) tweaked it to the next level. How you ask?
1) Optimized ext4fs: reduced r/w rate (healthy NAND lifespan), improved journaling (corrupted data writeback integrity) = Which improves the IOPs and performance access rate.
2) HC3.x fugu binaries, patched sqlite libraries, mSD read ahead buffer fix.
3) Modified VM: OOM (Out Of Memory), LMK (Low Memory Killer), VM heap (Virtual Machine), DRA (Dirty Ratio), DBR (Dirty Background Ratio), DWC (Dirty Writeback Centisecs), DEC (Dirty Expired Centisecs), SWP (Swap), VCP (VFS Cache Pressure).
4) Increased minfree value: Background, Foreground, Empty, Hidden, Visible, Secondary, Content.
5) Optimized cache: File and Drop cache, Forced cache (resident loop).
6) Custom kernel: OC/UC, UV/SVS/VDD, BFS/CFS, RSU/VR/SP supported.
7) Custom ROM: Optimized Rom script and props (ex: CyanogenMod).
I bet my superior MT4G can own your inferior MT4G. Cuz you can't touch this as its tweaked to THE next level. I'll stick with AOSP2.3.7GB until ICS4.X is more stable and we understand more as most memory grouping and adjustments might be changed.
Sent from my HTC Glacier
Jack_R1 said:
You're wrong on 2 points (possibly more):
1) This script is just the same as Autokiller app, with a small addition - it can (or can't) keep launcher in memory. Nothing new and revolutionary. This app exists for a couple of years.
2) This phone has 768MB of RAM. It won't benefit from a low memory killer (or actually, different settings for an existing in OS lowmemkiller), because it has TONS of memory. I just took a look at my phone, ~100MB of memory free, and ~300MB of remaining memory is taken by CACHED apps. If you don't know what it means - please read up on Android memory management, and I'll give you the short version - it's the same as free memory, but better.
Click to expand...
Click to collapse
Obviously, you never tried it lol
Here... you may learn something new...
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
http://forum.xda-developers.com/showpost.php?p=20163493&postcount=6695
Below a certain threshold of free ram (ie. not enough cached), the device WILL gag...
Hundreds if not thousands of users with 1 GB ram devices use it (Atrix, SGSII, etc.) and I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
In fact, the biggest difference he notices is in the use of google maps... never a stutter.
So you're missing out.
zeppelinrox said:
[1] Obviously, you never tried it lol
[2] I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
[3] So you're missing out.
Click to expand...
Click to collapse
First of all as dev of V6-SC you would be very defensive but at same times your not charging money to normal folks for it is a good thing, so thank you. Which I can say less about other folks editing same value claiming it new. Now I don't know about Jack but let's be clear on few points.
1) I did try your so called script and didn't like the whole script manger + busybox cast AFTER the OS startup. Which normally you can achieve via daemon or init.d script after kernel is initialized by declaring and using native shell. So no need for force apply afterwards as it was utilized before it was initiated via script manager. Also V6-SC couldn't keep the selected category minfree value which changed. But in short I didn't notice anything revolutionary as it was fully optimized long before I randomly landed on Android General section and saw your post claiming it maximize the devices performance. Which I was spectacle about as from your post you did seem to have basic knowledge hopefully not from wiki/google but *nix usr exp before landing on to Android.
2) Like I said I don't know about Jacky Boy but I can GRANTEE you I have NEVER had this so called "button delay" you specified. But I did modify the sampling rate and pressure density accommodated by tweaking transition speed. But now I run min:368mhz/max:1027mhz/gov:SmartAssV2. But even when I was battery conscience before I had MP1650mAh I ran on min:230mhz/max:768mhz/gov:SmartAssV1 with custom -75 to -100 VDD using ~14mA idle and ~60-90mA active per unit scale. I never had lag with 200mb used RAM running at least 18-20pcs and 14-15svc. So what your friend is running (Atrix) is irrelevant also isolated.
3) O-RLY am I really missing out? I think ill stick to my own. But don't take this post personal as it was ment for it to be argumentative. Difference is I actually know what I'm talking about as I have strong backgrounds on...
Sent from my HTC Glacier
zeppelinrox said:
Obviously, you never tried it lol
Here... you may learn something new...
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
http://forum.xda-developers.com/showpost.php?p=20163493&postcount=6695
Below a certain threshold of free ram (ie. not enough cached), the device WILL gag...
Hundreds if not thousands of users with 1 GB ram devices use it (Atrix, SGSII, etc.) and I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
In fact, the biggest difference he notices is in the use of google maps... never a stutter.
So you're missing out.
Click to expand...
Click to collapse
I didn't need to try it to know. I tried Autokiller, I played with lowmemkiller settings and watched the results, and I did it on Nexus One with 512MB of memory. It never needed anything since Gingerbread, and unless I made the settings super-aggressive, Autokiller actually failed to make any difference whatsoever - the apps were killed based on their age and never dropped by replacing apps.
In the current system, I have 100MB free + 250MB cached apps (which is just the same as free - theoretically and practically). The main difference you're not accounting for is - Android isn't a Linux distro, it's a Linux-derived OS, with many changes for mobile activity, especially on the kernel level, especially in the memory management area. "Linux memory consumption" isn't Android memory consumption, since they manage things differently. Linux isn't build to kill running apps, its lowmemkiller can't do it. Linux doesn't have concurrent garbage collector. Many Linux examples are irrelevant. Cached apps in Android aren't cached pages in Linux, freeing cached pages in Linux isn't killing cached apps in Android, and the most important - "performance degradation" doesn't exist in Android, since you ALWAYS have enough memory for any size of task (the largest loading task requires 50MB of memory, and there's 100MB free on my phone), and concurrent garbage collection is ALWAYS present in the system, the only thing you're doing - is calling it earlier, making it actually work more and getting the system more laggy than it could be.
I understand that you want to protect your creation, but in this case, you're wrong, sorry. You won't convince me.
And yes, I don't know what "button lag" are you talking about.
HTC Glacier said:
First of all as dev of V6-SC you would be very defensive but at same times your not charging money to normal folks for it is a good thing, so thank you. Which I can say less about other folks editing same value claiming it new. Now I don't know about Jack but let's be clear on few points.
1) I did try your so called script and didn't like the whole script manger + busybox cast AFTER the OS startup. Which normally you can achieve via daemon or init.d script after kernel is initialized by declaring and using native shell. So no need for force apply afterwards as it was utilized before it was initiated via script manager. Also V6-SC couldn't keep the selected category minfree value which changed. But in short I didn't notice anything revolutionary as it was fully optimized long before I randomly landed on Android General section and saw your post claiming it maximize the devices performance. Which I was spectacle about as from your post you did seem to have basic knowledge hopefully not from wiki/google but *nix usr exp before landing on to Android.
2) Like I said I don't know about Jacky Boy but I can GRANTEE you I have NEVER had this so called "button delay" you specified. But I did modify the sampling rate and pressure density accommodated by tweaking transition speed. But now I run min:368mhz/max:1027mhz/gov:SmartAssV2. But even when I was battery conscience before I had MP1650mAh I ran on min:230mhz/max:768mhz/gov:SmartAssV1 with custom -75 to -100 VDD using ~14mA idle and ~60-90mA active per unit scale. I never had lag with 200mb used RAM running at least 18-20pcs and 14-15svc. So what your friend is running (Atrix) is irrelevant also isolated.
3) O-RLY am I really missing out? I think ill stick to my own. But don't take this post personal as it was ment for it to be argumentative. Difference is I actually know what I'm talking about as I have strong backgrounds on...
Sent from my HTC Glacier
Click to expand...
Click to collapse
Sounds like you never got it working properly.
Also, if you have init.d support no need to run anything on boot with script manager.
Maybe the rom's kernel was applying settings late.
And no my friends atrix is not isolated there is a rather big thread in the atrix forums.
SGSII users see benefits too so seems there is always room for improvement.
Jack_R1 said:
I didn't need to try it to know. I tried Autokiller, I played with lowmemkiller settings and watched the results, and I did it on Nexus One with 512MB of memory. It never needed anything since Gingerbread, and unless I made the settings super-aggressive, Autokiller actually failed to make any difference whatsoever - the apps were killed based on their age and never dropped by replacing apps.
In the current system, I have 100MB free + 250MB cached apps (which is just the same as free - theoretically and practically). The main difference you're not accounting for is - Android isn't a Linux distro, it's a Linux-derived OS, with many changes for mobile activity, especially on the kernel level, especially in the memory management area. "Linux memory consumption" isn't Android memory consumption, since they manage things differently. Linux isn't build to kill running apps, its lowmemkiller can't do it. Linux doesn't have concurrent garbage collector. Many Linux examples are irrelevant. Cached apps in Android aren't cached pages in Linux, freeing cached pages in Linux isn't killing cached apps in Android, and the most important - "performance degradation" doesn't exist in Android, since you ALWAYS have enough memory for any size of task (the largest loading task requires 50MB of memory, and there's 100MB free on my phone), and concurrent garbage collection is ALWAYS present in the system, the only thing you're doing - is calling it earlier, making it actually work more and getting the system more laggy than it could be.
I understand that you want to protect your creation, but in this case, you're wrong, sorry. You won't convince me.
And yes, I don't know what "button lag" are you talking about.
Click to expand...
Click to collapse
I was tempted to stop reading when you admit to not even using it.
If it did the same as AKMO or Auto Memory Manager why on earth would anybody bother.
I sure as hell wouldn't bother writing a 4500+ line script lol.
I totally agree that Android memory is not the same as linux (see my sig) but the similarities are there and the article I posted applies 100%.
Its not about free ram.
Its about the right balance.
In fact, many report LESS free ram, ie. better multitasking, along with better performance and smoother performance.
Because I don't think Android memory should work the same as linux memory either.
Also, you tried AKMO because you felt there could be improvement and it didn't work.
THAT'S why I wrote a 4500+ line script that blows anything else out of the water
zeppelinrox said:
Sounds like you never got it working properly.
Also, if you have init.d support no need to run anything on boot with script manager.
Maybe the rom's kernel was applying settings late.
And no my friends atrix is not isolated there is a rather big thread in the atrix forums.
SGSII users see benefits too so seems there is always room for improvement.
Click to expand...
Click to collapse
Well my highly optimized as is but I am aware of V6 and others using it but personally I would stick to my.
Sent from my HTC Glacier
I noticed this juts few days ago and did this on all my family's Nexus S.
Install Chainfire3d
from the market and then open the app and tap to install the driver. I used the normal method not the advanced. Don't set any other settings after your phone reboots. You can if you want to but a lot of aps won't work with those settings.
What this app does is it installs an intermediate open GL driver between the apps and phone GPU driver to give you better performance.
Just figured I'll share it with everyone. It really made a difference for me on ICS speed. The way I see it it should be baked it to all ICS ROMs.
isnt this just used for games?
that's why its called chainfire3D
the whole point is to trick proprietary games "apps" into thinking you have GPU that you don't
so you are able to play tegra adreno..ect games on other devices
dont think its works on anything other than games so i don't se how its helping make overall ICS faster.
ICS is already using our sgx540 just fine
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Thank you for pointing out this tweak. I too was under the impression that chainfire was just for games.
Both tapatalk and the browser feel much smoother.
Thanks
Sent from my Nexus S using Tapatalk
obsanity said:
Well, it does and it makes a difference. Try it and see for your self. Chainfire3d is not just for games.
Click to expand...
Click to collapse
im eating my words sorry i was under impression was games only
im trying now you're right things are even smoother now thanks for the tip
As advertised. Nice find obsanity, it does make things noticeably smoother on general.
Noticed speed improvements thank you man
Nexus S - CyberGR Hybrid ICS (5), Matrix Kernel (15)
Chainfire dev recommends disabling all driver settings unless being used by a specific applications, per his xda thread:
" I strongly advise that when you are NOT using Chainfire3D for something specific, you disable all the options. This is better for system performance."
Anyone know why? Is he talking about the non-default options?
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Harbb said:
I don't know exactly, but it seems like it is just to do with the specific settings (inside the default settings section). Using the driver is fine, but any of the options being ticked has the ability to make some applications go awry depending on the device. Those options, i assume, are only meant to be used when you want to use a specific app that requires or benefits from them.
Also, i've noticed great improvements in ES File Explorer scrolling. It would lag a fair bit scrolling through long folders, but now it's nice and smooth.
Click to expand...
Click to collapse
That's what I was thinking as well. Thanks.
I'm installing this now... Have you guys noticed any decline in battery life?
Hopefully not :3
Does anyone know if this has the same downside as forcing gpu acceleration in the developer setting? I remember reading the Googler's post on G+ on how it increased the memory overhead by 8mb per app, reducing the memory available for other apps and processes.
Sent from my Nexus S using Tapatalk
It doesn't force GPU rendering. Alot of the Android UI is already using GPU rendering, using this intermediate driver just somehow makes it more fluid.
Trying it now, though I don't notice much improvements in scrolling.
I use force GPU setting on my phone. With the live OC in Matr1x at 111% (max my phone can handle) it does make a bit of difference in UI. But this Chainfire3D driver makes the most difference for me.
Also, in case you are on a ROM which doesn't let you change min memory settings, I'm using MinFreeManager which is a small app that just does that. The default settings which it comes built in are for GB but you can just change them manually. I don't touch the top 3 and just tweak the bottom 3. I'm currently on:
14,19,24,32,64,128
Does it effect battery drain?
Will this eat more battery juice?
Highly doubt it, and so far havn't noticed anything particularly different on my end. You can uninstall it anyway if it does cause trouble (though might be wise to perform a nandroid backup while initially installing).
Thx man, now trying it!!
Greetzz Jojoost
Sent from my Nexus S using XDA App
What are the additional features in the pro version?
What are the additional features in the pro version?
They are not described in the market.
Anti-Aliasing features and per-app settings are the main features in the pro version. More info here.
Hi guys
Who has his device overlclocked? I installed on my N5X the TWRP and the ElementalX kernel (no root) due to the bad performance in trottling with stock kernel. In this moment I have a little overclock on the A53 cluster, I'm at 1536/1833 and it runs fine, I think that the critical point of the 808 is the A53 cluster, someone use it @ 1600MHz?
I'm looking to overclock it as well
Any ideas are welcome.
I think that overclocking the little cluster the device in little task may can use a little less the big cluster and save a little the battery Life. Antone tryed?
I know this thread is 2 years old, and I shouldn't be reviving it... I just had it. Current Nexus 5X with crDroid (which seem to be faster than stock Android) is performing like garbage. Battery and performance in general was greatly improved when I turned off background activity for a lot of 8.x unsupported apps (You can check them in the battery settings)... But it's just unbearable. Everything takes a long time to load.
I don't use anything fancy. Maps, YouTube, Chrome, WhatsApp, Keep, a couple applications now and there, and there's still free RAM. Since I've read that this one has the more powerful CPU turned off, except for demanding tasks as games, I thought some overclocking could make it work better. I'd like to push this boy as far as possible (I make myself proud when I do that), and I'm going to be overclocking it...