Dear all Dev's,
I offer up a reward in the form of money $$$ for who ever can make a working ROM that fits the following specification.
Android Froyo 2.2 NAND, (NO ADW, No Junk, STOCK! + any performance tweaks you might know of, I want to get a minimum quadrant score of 1800 and at 1.5Ghz min of 1900. but thats just guide line )
Kernel that supports The extended battery from HTC 2300mAh
A separate Identical ROM for use with standard battery
Both ROMS must use the Data.img file on the SD card as to allow for fast switching of the ROMs for when swapping from standard to Extended Battery with but a flash of a ROM or if there is a faster way of swapping the kernel on the go then I'm also all for it.
The Kernel Must support Over-clocking 1.5Ghz as managed by MDJ's work and minimum 245Mhz.
Good luck and I look forward to getting to pay someone for making this a reality, im sure there are others who will want this and are willing to pay a little for someones efforts.
Kind Regards
SyLvEsTeR20007
How much is the bounty?
I will have to see if it is enough for me to think of a way to cheat Quadrant by using alternate I/O means. Quadrant puts too much points to I/O and the nand isn't that fast.
Otherwise, you can lower your expectation, or break the bounty into 2 parts.
Extended battery Build
Cheat that god damned Quadrant <-- make sure you put in a really attractive one.
LiFE1688 said:
How much is the bounty?
I will have to see if it is enough for me to think of a way to cheat Quadrant by using alternate I/O means. Quadrant puts too much points to I/O and the nand isn't that fast.
Otherwise, you can lower your expectation, or break the bounty into 2 parts.
Extended battery Build
Cheat that god damned Quadrant <-- make sure you put in a really attractive one.
Click to expand...
Click to collapse
Tell me what your time is worth, you seem sure of yourself. I get a quadrant with NexusHD 2.2 1.9b of 1828 with a 1.190Ghz overclock.
I would not want to quote a price that would offend you, I dont usualy offer to do this but if my above can be met then im game.
I look forward to your reply..
Sadly, I have yet to see any of the NAND builds I am using get a score of above 1600. I see them a lot in SD builds. It is because of how Quadrant gives more scores to I/O.
data2ext and data2sd builds do gives close to sd build scores, but that's because data is in the sd card ext2/3/4 partition and the scores will vary on the speed of the card.
Just advertise the bounty, someone will take it.
EB
Frankly speaking, Quadrant is nothing. SGS has very powerful graphics but for some reasons it is usually very low at Quadrant. So the figures it shows are of very strange nature.
And as far as I know it is possible to cheat and compile a kernel that would show false figures to Quadrant without real increase of performance.
Anyway, I am chasing for kernel with true HTC 2300mah EB support. What makes me wonder is that the devs seem not to be interested in supporting it. For me the main reason for Android on HD2 (except for the obvious one that I already have this device and I do not have to pay money to use Android) is that HD2 allows to install a good battery (DHD doesn't).
So I promise to make a donation to the dev that will do that. I donated Cotulla for Magldr - that's a cool app for sure, but he already mentioned that he is not interested in EB.
Hastarin's support is fake - no full charge, no full use of the battery. And the kernels that I saw on XDA kill the camera.
That's it. Looking forward to see something good and workable
LiFE1688 said:
Sadly, I have yet to see any of the NAND builds I am using get a score of above 1600. I see them a lot in SD builds. It is because of how Quadrant gives more scores to I/O.
data2ext and data2sd builds do gives close to sd build scores, but that's because data is in the sd card ext2/3/4 partition and the scores will vary on the speed of the card.
Just advertise the bounty, someone will take it.
Click to expand...
Click to collapse
OK, BOUNTY IS £200. bring it on.
I want real full eb support!
I'm also looking for an extended battery kernel/build. I can say that even Hastarins EB Kernel (using a build on SD Card booting through MAGLDR) crashes.
I made a DMESG dump with and without the exteneded battery and there is something different:
Code:
[D:BATT] state change(3->4), full count=0, over load count=0 [-1871317519]
What is state 4?
bump.
Extended battery support is something that a lot of people need. Is is so hard to include? Android - ported, Wp7 - ported, meego, ubuntu etc, but extended battery support ..
I use Nand Mdeejay Revolution 2.2 and to be perfect it just misses extended battery support...
Good idea... pick me
try this link (below)... it has an eb kernel that you install using clockworkmod.. so ur nand roms without eb support should work after you install.. pick a nand rom you like, install new kernel, and go go go lol
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
Anyone try this app on the Inc? It does make the SD card read/write much faster. I was wondering if it was bad for the phone or the card to do this. Seems ok so far and the app was free.
Yes, I've tried it on my Inc. I'm running CM7 with Chad's incredikernel and the app didn't make any difference for me, regardless of what I set it to. I also tried manually adjusting the read_ahead files, in the off-chance that the app itself just wasn't working. I still haven't been able to achieve any performance increase.
According to Chad, however, my lack of a result is normal given my setup:
chad0989 said:
Adjusting the cache doesn't help much on .37 like it did on previous kernels.
Click to expand...
Click to collapse
From what I've read, the effectiveness of this method also depends on the card you're using.
Works great for me on Redemption Rom. No waiting to load thumbnails and phone feels a bit smoother
DROID Incredible
Yeah, been using it for a few days now and its a lot better. I would recommend this app to anyone with a larger SD card especially if you have a lot of stuff on it. its FREE!
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
How good or bad is it to Use a swap partition, pros & con's ?
mevricksam said:
How good or bad is it to Use a swap partition, pros & con's ?
Click to expand...
Click to collapse
I guess its okay to use swap. Swap increases your ram and so you can preform better multitasks.
I think the con is that the phone gets slow if your SD card is not good. But i am really not sure on this one
mevricksam said:
How good or bad is it to Use a swap partition, pros & con's ?
Click to expand...
Click to collapse
SWAP expands your RAM, so when you have it, you can open more apps than than you could without it.
If You're not trying to run many RAM-eating apps at the same time, you're only wasting your SD space.
I close every app i don't need, so SWAP i useless for me. Also i'm using Dorimanx ROM, which when SWAP is enabled has no built in task manager. If it wasnt like that, i would probably have it, just in case.
About slowing phone down: SWAP will never work as fast as RAM, since it has slower access time than native RAM. It's just to keep everything going even if you ran out of RAM, maybe a little slower, but still.
I think its better to Post this here,when its not better,than sorry!!!
-----------------------------------------------------------------
Once a brief statement for those who are not traveling so long in the Android scene:
ZRAM = ramzswap = Compcache
In order to explain more precisely ZRAM first need other terms are more clearly defined:
Swap can be compared with the swap file on Windows. If the memory (RAM) to complete the PC the data that are being used not actively outsource (eg background applications) so as to re-evacuate RAM free. To this data is written to a hard disk. If required, this data is then read back from there easily. Even the fastest SSD is slower than the RAM. On Android, there is no swap!
In ZRAM unnecessary storage resources are compressed and then moved to a reserved area in the fixed RAM (ZRAM). So a kind of swap in memory.
This Ram is more free because the data then only about 1/4 of the former storage requirements have. However, the CPU has to work in more because they compress the data has (or unpack again when they are needed). The advantage clearly lies in the speed. Since the swap partition in RAM is much faster than this is a swap partition on a hard drive.
In itself a great thing. But Android does not have a swap partition, and therefore brings Android ZRAM under no performance gain as would be the case with a normal PC.
In normal PC would look like this:
Swap = swap file (on disk) -> Slow
ZRAM (swap in RAM) -> Faster than swap
RAM -> Quick
With Android, there is no swap partition, and therefore brings ZRAM also no performance boost.
The only thing that brings ZRAM is "more" RAM. Compressed by the "enlarged" so to speak of the available memory. That's on devices with little RAM (<256MB) also pretty useful. The S2 has 1GB but the rich, and more than. There must not be artificially pushed up to 1.5 GB.
After you activate the ZRAM also has 2 disadvantages. The encoding and decoding using CPU time, which in turn has higher power consumption.
Roughly one can say (For devices with more than 512MB RAM):
Without ZRAM: + CPU Performance | + Battery | RAM
With ZRAM: CPU Performance |-Battery | + RAM
For devices with too little RAM so it makes perfect sense. But who shoots the S2 already be fully complete RAM and then still need more?
Check whether you can ZRAM runs in the terminal with
free or cat / proc / meminfo
I hope it helps to understand zRam!!!!
Thanks for the info
Yeah thanks indeed for the info - so does this mean that we must have zram disabled because of low memory ?
no its very good for devices with less ram like 289mb and we have less ram,so its useless for higher ram devices with 800-1000,but that can u read in this guide
CALIBAN666 said:
no its very good for devices with less ram like 289mb and we have less ram,so its useless for higher ram devices with 800-1000,but that can u read in this guide
Click to expand...
Click to collapse
Yeah i misunderstood thanks for explaining !
But one more doubt - its good for us anyhow if we disable it will we get more free ram ?
in your statement zram is not battery friendly. ? am i correct. ? or not?
Sorry for too many questions mate - am the noobest guy here on xda that is why
not really because the system all the time creates virtual ram and distributed, just as if the ram is not needed, because then the virtual ram not needed and the system distributes it then falls to a normal ram, but I think it also comes to the what and how much the device is made for running multiple concurrent tasks, it is recommended.
nikufellow said:
Sorry for too many questions mate - am the noobest guy here on xda that is why
Click to expand...
Click to collapse
no problem bro,thats the reason why i open this thread.and hey im noob too
Thank you
one of the best information thread on forum
thank you mate
ewat said:
in your statement zram is not battery friendly. ? am i correct. ? or not?
Click to expand...
Click to collapse
Yes you are correct as cpu will have to do more work compresshog and de compressing stuff so more power will be consumed
Nice guide
But still i dont get it
post source : www.posting-a-post-at-tapatalk.com
@CALIBAN666
ramzswap != compcache. both using compressed data on memory. both even from the same person AFAIR. the different is ramzswap using compressed swap and compcache using compressed cache.
kernel 2.6.35 source code from samsung have ramzswap support, but you need user space program to enable it (need little patch to build it for sgy but it's easy).
irfanbagus said:
@CALIBAN666
ramzswap != compcache. both using compressed data on memory. both even from the same person AFAIR. the different is ramzswap using compressed swap and compcache using compressed cache.
kernel 2.6.35 source code from samsung have ramzswap support, but you need user space program to enable it (need little patch to build it for sgy but it's easy).
Click to expand...
Click to collapse
Can u help me on enabling ramzswap?? Zram is laggy
Sent from my GT-S5360 using XDA
hell_lock said:
Can u help me on enabling ramzswap?? Zram is laggy
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
i follow this instruction but using build-in ramzswap.ko in sgy kernel source. the trivial part is compile rzscontrol for sgy. i forget how i build it but AFAIR need few patching. i'll post if i find it.
Not understood... Android has no swap? Then what is swapper for? Swapping partition?
I tried swapper for my galaxy y n i didnt liked it personally
By that time i had stock sd card
Im gonna try zram on my 16 gb class 6 sd card..i wish this thing works for me cuz after installing merruk kernel, my 50 mb ram got stuck
Sent from my GT-S5360 using xda app-developers app
swapp != zram
Rcain said:
Not understood... Android has no swap? Then what is swapper for? Swapping partition?
Click to expand...
Click to collapse
With swapper you can have an swap file or you can choose to partition your SD-Card to have an swap partition there. Swap is not used by default in Galaxy Y and swap space is optional not really needed in Android (or Unix/Linux in general).
On the other hand, zram is a whole different beast.
If I'm not mistaken a dev for ace2 already made it several month ago. It using init.d script to control the zram stuff