[KERNEL] Kernel (deprimed_test) - Break It If You Can

[droidkevlar]

I was on nightly #23 and old deprimed since it seemed there were so many issues, not just with kernel but with rom too....did a clean install of #54 and latest deprimed and i just gotta say...it flys!!!! thunderbolt might have a bigger screen and 4g but i love this phone more! thank you!!!!

 

[prime]

Yeah I've searched the net, perhaps I don't know the right terms to search for, but I can't determine what the relationship is between OOM and CC...IE how I can configure OOM to utilize the CC more instead of shutting apps, even when it's set to 7. For now I think I will have to keep the CC aggresive.

From zeppelinrox's work (XDA link) try this.

nothing in there about compcache's interaction with OOM.

It has nothing to do with compcache. It has to do with keeping the application you want from dying from an OOM situation....this is what you want.

Zram uses resources to move the data to and from the compressed ram block device (this uses CPU resources as well), once a certain level is reached compcache can not restart because android can't push the large amount of compressed memory back into normal system memory. You can't use compcache in the way you want, it's not fine grained like that. You must force the desired OOM value to the application you want to stay in memory or use real SD Card swap and try to fine tune the swappiness (SD swap has the same issue with stopping or restarting..will bring the system down).

 

[kevdog]

hmm screebl doesn't seem to work with this release/kernel. Whether its an accelerometer or screebl issue -- how would I troubleshoot?
News and weather widget cant pick up location from gps -- probably another case of a bad version being used. currently have 1.3.04 installed. Is this the problem?

***Edit workaround for screebl with Gingerbread. Need to turn autorotation on or it wont work.
News and weather widget can pick up current location if you choose to allow Google to collect anonymous statistics. Lame!!! I'm smelling Steve Jobs involvement on this one.

 

[jerroedr]

i have winners 51 and newest deprimed and compcache works, but it doesnt seem to be doing much. where after having my phone on a few hours would have few thousand, now its only showing a few hundred...

 

[itchn2go]

I am on PE 5.02 and the latest Deprimed Kernel. Screeble works fine with the kernel.

hmm screebl doesn't seem to work with this release/kernel. Whether its an accelerometer or screebl issue -- how would I troubleshoot?
News and weather widget cant pick up location from gps -- probably another case of a bad version being used. currently have 1.3.04 installed. Is this the problem?

 

[itchn2go]

prime - thanks for adding the zram file back. now to get compcache to start on PE5.02 i have to go to terminal and type compcache restart as a SU. If this is not done compcache is not active after boot. Any ideas?

 

[prime]

prime - thanks for adding the zram file back. now to get compcache to start on PE5.02 i have to go to terminal and type compcache restart as a SU. If this is not done compcache is not active after boot. Any ideas?

Do you have a /etc/init.d directory? If so create a file called 99ccache with these contents:

handle_compcache

Then chmod the file to make it executable like this:

su
sysrw
chmod 0755 /system/etc/init.d/99ccache
sysro
reboot

Then you should have the proper compcache setup controllable through the menu..this is all speculation as I run stock CM7 but I believe it will work.

 

[jerroedr]

hey prime, i dont think my compcache is cacheing enough/right... i just updated to winner 51 and your most recent kernel and after hours my swapped cache under set cpu is only 396kb, but before the update it was always in the thousands and rapidly climbing mostly all the time... is this normal as it was a month between updates?

 

[prime]

I was on nightly #23 and old deprimed since it seemed there were so many issues, not just with kernel but with rom too....did a clean install of #54 and latest deprimed and i just gotta say...it flys!!!! thunderbolt might have a bigger screen and 4g but i love this phone more! thank you!!!!

My Droid is much snappier than my X and it has a physical keyboard, I can't do without that determinate sound...click.

 

[zachdroid]

Damn, newest kernel caused endless bootloops =(. Even worse my most recent nandroid was a no go. Clean install it is. Crap.

Sent from my Droid using DroidForums

 

[prime]

Damn, newest kernel caused endless bootloops =(. Even worse my most recent nandroid was a no go. Clean install it is. Crap.

Sent from my Droid using DroidForums

I can tell you why, your /system directory was full and couldn't contain the entire kernel image. As you flash without wiping the /system directory gets full of files from previous ROM flashes that normally would be wiped out.

I hate that your nandroid did not work, was it an RZR, CWR or actual Nandroid backup?

 

[zachdroid]

I can tell you why, your /system directory was full and couldn't contain the entire kernel image. As you flash without wiping the /system directory gets full of files from previous ROM flashes that normally would be wiped out.

I hate that your nandroid did not work, was it an RZR, CWR or actual Nandroid backup?[/QUOTE]

Yeah it sucked. But maybe it was time for a clean wipe anyways. The back up that didn't fly was rzr. First time it didn't work. Sucks it had to be now. So by just flashing the kernel no system files got dumped and it only took a partial image, I see. Any suggestions on a remedy?

Sent from my Droid using DroidForums

 

[prime]

I can tell you why, your /system directory was full and couldn't contain the entire kernel image. As you flash without wiping the /system directory gets full of files from previous ROM flashes that normally would be wiped out.

I hate that your nandroid did not work, was it an RZR, CWR or actual Nandroid backup?

Yeah it sucked. But maybe it was time for a clean wipe anyways. The back up that didn't fly was rzr. First time it didn't work. Sucks it had to be now. So by just flashing the kernel no system files got dumped and it only took a partial image, I see. Any suggestions on a remedy?

Sent from my Droid using DroidForums

Not exactly, previous ROM flashes contain files that updated versions (especially CM nightlies) do not contain..extraneous files that would be removed by a wipe. When you flash a kernel the routine uses /tmp which is actually a /system folder, if the /system MTD partition is full there will not be room for the kernel image and your left with no boot.img to flash to the /boot MTD partition.

You should discuss your RZR nandroid issue with RaidZero as your not the first this has happened to, perhaps he can fix the issue. What good is a recovery that creates bad backups.

 

[zachdroid]

I can tell you why, your /system directory was full and couldn't contain the entire kernel image. As you flash without wiping the /system directory gets full of files from previous ROM flashes that normally would be wiped out.

I hate that your nandroid did not work, was it an RZR, CWR or actual Nandroid backup?

Yeah it sucked. But maybe it was time for a clean wipe anyways. The back up that didn't fly was rzr. First time it didn't work. Sucks it had to be now. So by just flashing the kernel no system files got dumped and it only took a partial image, I see. Any suggestions on a remedy?

Sent from my Droid using DroidForums

Not exactly, previous ROM flashes contain files that updated versions (especially CM nightlies) do not contain..extraneous files that would be removed by a wipe. When you flash a kernel the routine uses /tmp which is actually a /system folder, if the /system MTD partition is full there will not be room for the kernel image and your left with no boot.img to flash to the /boot MTD partition.

You should discuss your RZR nandroid issue with RaidZero as your not the first this has happened to, perhaps he can fix the issue. What good is a recovery that creates bad backups.

For sure on the recovery side of things. I will take that up in a minute or so. The steps I took when the image didn't take were:

Wipe system, boot, cache, dalvik.

Install CM7 #54
Install gapps
Install newest Prime Kernel
Install link2sd pre-install
Reboot

This resulted in bootlooping at the flash screen "M".

Flashed kernel reporting #8, up an running again.

I open to any suggestions as your work, Prime, is the tops

 

[prime]

I can tell you why, your /system directory was full and couldn't contain the entire kernel image. As you flash without wiping the /system directory gets full of files from previous ROM flashes that normally would be wiped out.

I hate that your nandroid did not work, was it an RZR, CWR or actual Nandroid backup?

Yeah it sucked. But maybe it was time for a clean wipe anyways. The back up that didn't fly was rzr. First time it didn't work. Sucks it had to be now. So by just flashing the kernel no system files got dumped and it only took a partial image, I see. Any suggestions on a remedy?

Sent from my Droid using DroidForums

Not exactly, previous ROM flashes contain files that updated versions (especially CM nightlies) do not contain..extraneous files that would be removed by a wipe. When you flash a kernel the routine uses /tmp which is actually a /system folder, if the /system MTD partition is full there will not be room for the kernel image and your left with no boot.img to flash to the /boot MTD partition.

You should discuss your RZR nandroid issue with RaidZero as your not the first this has happened to, perhaps he can fix the issue. What good is a recovery that creates bad backups.

For sure on the recovery side of things. I will take that up in a minute or so. The steps I took when the image didn't take were:

Wipe system, boot, cache, dalvik.

Install CM7 #54
Install gapps
Install newest Prime Kernel
Install link2sd pre-install
Reboot

This resulted in bootlooping at the flash screen "M".

Flashed kernel reporting #8, up an running again.

I open to any suggestions as your work, Prime, is the tops

Wipe /system before flashing a new/updated ROM zip. Use CWR as well, I'm off RZR because I had issues with it.