COMPCACHE for UD *2.5.0*!! [Instructions] Updated 12/16/10

[chewy74]

yes, i reflashed with slayers kernel and the compcache droid zip in the OP.
I checked my phone settings and i have the kernel and thought i did something wrong and reflashed the compcache droid zip for good measure.

when i go to terminal and input "compcache start" i get this message

[FONT=Consolas][SIZE=3][COLOR=#000000]$ su # compcache[/COLOR][/SIZE][/FONT]
[FONT=Consolas][SIZE=3][COLOR=#000000]Usage: /system/bin/compcache {start|stop|stats} # compcache start[/COLOR][/SIZE][/FONT]
[FONT=Calibri][COLOR=#000000]insmod: init_module '/system/lib/modules/ramzswap.ko' failed (File exists) # compcache stats[/COLOR][/FONT]

but it does start though because when i check the stats I shows its actually on and running. You will lose it after reboot and have to repeat process over aging to start it

yeah, i get that too (minus the reboot), but when i go to check if its on, its actually working. so you get the fail to start message, but it actually did start. you lose it after reboot though and its a pain to keep resetting after every reboot.

Glad it's not just me... I can't get it to work.

Typing SU, Compcache Start, only gets me an error and automatic reboot.

are you guys reflashing your kernel and the .zip after updating to 2.4? i haven't updated to 2.4 yet, just wanted to figure out a game plan for when i do try it.

 

[anuraj1]

I'm reflashing and checking on the process right now to see what is going on with the people that can't get it to work. I'll post results shortly.

 

[Smokie]

yes, i reflashed with slayers kernel and the compcache droid zip in the OP.
I checked my phone settings and i have the kernel and thought i did something wrong and reflashed the compcache droid zip for good measure.

when i go to terminal and input "compcache start" i get this message

[FONT=Consolas][SIZE=3][COLOR=#000000]$ su # compcache[/COLOR][/SIZE][/FONT]
[FONT=Consolas][SIZE=3][COLOR=#000000]Usage: /system/bin/compcache {start|stop|stats} # compcache start[/COLOR][/SIZE][/FONT]
[FONT=Calibri][COLOR=#000000]insmod: init_module '/system/lib/modules/ramzswap.ko' failed (File exists) # compcache stats[/COLOR][/FONT]

but it does start though because when i check the stats I shows its actually on and running. You will lose it after reboot and have to repeat process over aging to start it

yeah, i get that too (minus the reboot), but when i go to check if its on, its actually working. so you get the fail to start message, but it actually did start. you lose it after reboot though and its a pain to keep resetting after every reboot.

are you guys reflashing your kernel and the .zip after updating to 2.4? i haven't updated to 2.4 yet, just wanted to figure out a game plan for when i do try it.

I'm having the exact same errors.. I had compcache working fine on 2.3.0. upgraded to 2.4.0 and did the same method.. no go. also, when I check on "compcache stats" i get a "This is not typewriter" error in return? anyone got any ideas? i tried both the slayher v1.6 kernel as well as the LFY.

 

[reebz]

I got the same typewriter message after flashing 2.4. I reflashed a Slayer kernel and then the Slayer compcache droid.zip. I did the compcache start in TE and then compcache stats and was up and running.

 

[anuraj1]

So far I've confirmed that compcache is working but you have to manually start it t each boot. I'm working on a way to make it automatic. It looks like the line of code to start it automatically is in place in /etc/init.d/20userinit but for some reason it isn't working. I'll report back with what I find.

 

[sonnydroid]

So far I've confirmed that compcache is working but you have to manually start it t each boot. I'm working on a way to make it automatic. It looks like the line of code to start it automatically is in place in /etc/init.d/20userinit but for some reason it isn't working. I'll report back with what I find.

Got it to work automatic on reboot.

/system/bin/compcache start in /etc/init.d/20userinit wasn't working.. so what I did was erased /system/bin/compcache start and retyped it. Saved and exit, and erased the .bak file it created. Rebooted and compcache works automatic now

EDIT: Nevermind. It won't start anymore. For some reason it did when I first rebooted, and now that I tried it again, it doesn't. Strange...

Sent from my Droid using DroidForums App

 

[terra-]

Same issue here. First it must be stopped, then started, then its running fine until reboot. Whats curious is that is needs to be stopped initially so it appears something is starting....just not correctly....

 

[ecsnead69]

Anybody figured out how to get compcache working like in 2.3 yet??

 

[PARick]

Ok, after getting the same messages everyone else had, I gave up on compcache. Then I wnet into SetCPU and noticed it was set to ondemand (why I don't know) so I reset it to conservative, went into UD Compcache in performance and went down from 26 to default....went into TE and typed compcache stats and vola......listed them all as before. I did not type start so I assume it will start on reboot but will try after while.

 

[ecsnead69]

Sounds like you started it already, it will more than likely stop once you reboot

 

[mtnbkrbob]

ok well i had compcache working on 2.3 with a 900 slayer kernel on my droid 1. well i install 2.4 with the updated slayer 900 kernel version 1.6 and i flash the zip that allows compcache to work and i get bubkis! so what am i doing wrong.


bob

 

[mtnbkrbob]

you have to do "compcache start" first. it will give you an error but do the "compcache stats" after and it will give you the statistics

My compcache stats say "not a typewriter". I did everything the same as 2.3??

Sent from my Droid using DroidForums App

DUH!
dangit yep thats what i didnt do i shouldve remembered it because when i did it for 2.3 i got three automatic reboots before it all settled in and ran great.
well just typed compcache start into terminal waiting for it to reboot then im gonna run the compcache stats.

thanks
bob

update: got er done!

 

[PARick]

Sounds like you started it already, it will more than likely stop once you reboot

You were right. But, UD 2.4, for some reason, alwys defaults to ondemand in setcpu when I reboot. Then once I reset to something else (conservative) it works.

 

[anuraj1]

I got in touch with Blackdroid and he is aware of the issue with compcache not starting at boot. He is working on an update to address the problem.

EDIT: OP updated to show that Blackdroid is aware of the issue.

 

[thejas]

help with compcache ud 2.4

:blackdroid:***At this time, compcache will not automatically start on boot. Blackdroid is aware of the issue and is planning on releasing an update to fix it.***


Blackdroid has made it easier to get compcache working on UD 2.4.0, but there are still a couple of steps to take to make it work:

Flash a Slayher kernel from ROM Manager or here:

Froyo Kernels by slayher - CyanogenMod Forum

Flash this zip AFTER you flash the kernel to enable compcache in the kernel:

http://android.antbox.org/slayher/slayher_compcache_droid.zip

Make sure Compcache is enabled in Ultimate Settings > Performance

And after you reboot, Compcache will be working.

You can check the status of compcache by typing "su" (enter) "compcache stats" (enter) without the quotes in the terminal emulator. If it gives you stats, it is on, if it gets an error, it is off. You can also check in SetCPU under info. The items that start with "Swap" will have numbers associated with them if compcache is on, or will be zero if it is off.

Terminal emulator commands that might come in handy:

(You must type "su" without the quotes once before using these commands)

compcache start

compcache stop

compcache stats

----

What is compcache? >> http://www.droidforums.net/forum/ul...orking-ud-2-1-0-instructions.html#post1032090

trying all these things above i get this when i go into a terminal emulator and type su *enter*
compcache start *enter*
insmod: init_module '/system/lib/modules/ramzswap.ko' failed (file exists)

compcache does not work and i cannot fix it. What does the above mean?