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

[jengas kahn]

look man, clearly you put a lot of hard work into what you do. its rare to see this level of dedication in anything, let alone something that can be so confusing to many of us. I would rather spend hours trying to figure out how to get my 20overclock customized to my phone as perfectly as possible than go flash some generic kernel that won't run half as well as any of yours. It can get frustrating... sorry for the words.
Don't stop doing what you do.

Sent from my Droid using Tapatalk

 

[prime]

look man, clearly you put a lot of hard work into what you do. its rare to see this level of dedication in anything, let alone something that can be so confusing to many of us. I would rather spend hours trying to figure out how to get my 20overclock customized to my phone as perfectly as possible than go flash some generic kernel that won't run half as well as any of yours. It can get frustrating... sorry for the words.
Don't stop doing what you do.

Sent from my Droid using Tapatalk

I never meant to make you think there were words, no worries at all.

I enjoy doing this (been at it for years), I'm not going anywhere. (=

 

[captdroid]

Prime, tried your latest primed #14 with CM 6.1.2 (decided to stay with 6.1.2 instead of moving up to CM build 248 for now). Ran ok but had slowness with wifi when I tested on both CM build 248 and CM 6.1.2.

Back using mtwebster stock kernel at the moment. I plan on re-installing your original mtwebster stock kanged kernel with overclock mod and compcache fix (don't use compcache though). That kernel with overclock tweaks ran the best for me at least on CM 6. I do have deprimed test #12 running on my g/f sons phone at the moment running CM 6.1.2. I'll have to ask him how it's working.

I'll keep an eye on things with your kernel development in particular the deprimed and decide when to try that one again on CM 6. Assuming I don't end up back on CM 7 which at this time seems unlikely. But who knows what may transpire in the dev community before things are said and done for the D1

Right now with CM 7 Gingerbread I am feeling like a need a hardware upgrade to run that sucker properly.. lol

 

[foxdog]

So is primed kernel the one to go with?

 

[foxdog]

Primed kernel is running super smooth for me so far

 

[prime]

Prime, tried your latest primed #14 with CM 6.1.2 (decided to stay with 6.1.2 instead of moving up to CM build 248 for now). Ran ok but had slowness with wifi when I tested on both CM build 248 and CM 6.1.2.

Back using mtwebster stock kernel at the moment. I plan on re-installing your original mtwebster stock kanged kernel with overclock mod and compcache fix (don't use compcache though). That kernel with overclock tweaks ran the best for me at least on CM 6. I do have deprimed test #12 running on my g/f sons phone at the moment running CM 6.1.2. I'll have to ask him how it's working.

I'll keep an eye on things with your kernel development in particular the deprimed and decide when to try that one again on CM 6. Assuming I don't end up back on CM 7 which at this time seems unlikely. But who knows what may transpire in the dev community before things are said and done for the D1

Right now with CM 7 Gingerbread I am feeling like a need a hardware upgrade to run that sucker properly.. lol

Thank you for trying it and getting back.

The latest winner00 build is doing great for myself, I got about 11 hours of HEAVY use yesterday (6 hours 10 minutes of screen on time) on my primed kernel...this is a new record for me.

damn phone died before I could grab a final screenshot, here are a couple of shots at %15 battery

 

[itchn2go]

@ Prime...

Tried the Primed Kernel but could get ext2/3 to be recognized. reinstalled de_primed and all worked again.

 

[prime]

@ Prime...

Tried the Primed Kernel but could get ext2/3 to be recognized. reinstalled de_primed and all worked again.

I found out the ext2/3 drivers cause marked CPU usage simply being loaded, on primed I modularized them.

I am using link2sd on primed with the ext4 driver, the two images above are while using this combination.

You have to modify the /etc/init.d/11link2sd file to use the ext4 driver.

Here is my /etc/init.d/link2sd for primed:

#!/system/bin/sh
#added by link2sd
modprobe ext4
sleep 1

Change your file to read the same on primed or deprimed and all should be fine upon boot.

 

[captdroid]

Prime, tried your latest primed #14 with CM 6.1.2 (decided to stay with 6.1.2 instead of moving up to CM build 248 for now). Ran ok but had slowness with wifi when I tested on both CM build 248 and CM 6.1.2.

Back using mtwebster stock kernel at the moment. I plan on re-installing your original mtwebster stock kanged kernel with overclock mod and compcache fix (don't use compcache though). That kernel with overclock tweaks ran the best for me at least on CM 6. I do have deprimed test #12 running on my g/f sons phone at the moment running CM 6.1.2. I'll have to ask him how it's working.

I'll keep an eye on things with your kernel development in particular the deprimed and decide when to try that one again on CM 6. Assuming I don't end up back on CM 7 which at this time seems unlikely. But who knows what may transpire in the dev community before things are said and done for the D1

Right now with CM 7 Gingerbread I am feeling like a need a hardware upgrade to run that sucker properly.. lol

Thank you for trying it and getting back.

The latest winner00 build is doing great for myself, I got about 11 hours of HEAVY use yesterday (6 hours 10 minutes of screen on time) on my primed kernel...this is a new record for me.

damn phone died before I could grab a final screenshot, here are a couple of shots at %15 battery

No problem. I am liking your original overclock mod once again running CM 6.1.2. Another thing I encountered running CM7 is limited memory issues. The programs I need to have running all the time are just to much with CM7 loaded up on a D1 (can't have them unloading and loading constantly to maintain performance) but with CM6 works perfectly, fast, and great battery life.

 

[danceswithbongs]

Love reading this, as a Link2Sd addict.
Are you saying de or re will both mount running that altered script, no extra module needed to be loaded?
And creates the ext2 folder or do you create that beforehand?
Thanks and great news.
danceswithbongs
Prime you the primest

@ Prime...

Tried the Primed Kernel but could get ext2/3 to be recognized. reinstalled de_primed and all worked again.

I found out the ext2/3 drivers cause marked CPU usage simply being loaded, on primed I modularized them.

I am using link2sd on primed with the ext4 driver, the two images above are while using this combination.

You have to modify the /etc/init.d/11link2sd file to use the ext4 driver.

Here is my /etc/init.d/link2sd for primed:

#!/system/bin/sh
#added by link2sd
modprobe ext4
sleep 1

Change your file to read the same on primed or deprimed and all should be fine upon boot.

 

[Bear in NM]

Capt,

Prime mentioned this memory "fix" in the long CM thread, back a few pages. The application Auto Memory Manager. You may remember this app as a way to kill programs in memory, back in the day. It fell out of favor for managing memory as you should not need to kill apps in this day and age. The twist is that the program can be used to force priorities up for applications and processes, thereby managing the opposite side of the management equation. I have loaded it again to test, thanks to prime mentioning it.

Funny how sometimes things come around full circle.........

Craig

 

[prime]

Love reading this, as a Link2Sd addict.
Are you saying de or re will both mount running that altered script, no extra module needed to be loaded?
And creates the ext2 folder or do you create that beforehand?
Thanks and great news.
danceswithbongs
Prime you the primest

@ Prime...

Tried the Primed Kernel but could get ext2/3 to be recognized. reinstalled de_primed and all worked again.

I found out the ext2/3 drivers cause marked CPU usage simply being loaded, on primed I modularized them.

I am using link2sd on primed with the ext4 driver, the two images above are while using this combination.

You have to modify the /etc/init.d/11link2sd file to use the ext4 driver.

Here is my /etc/init.d/link2sd for primed:

#!/system/bin/sh
#added by link2sd
modprobe ext4
sleep 1

Change your file to read the same on primed or deprimed and all should be fine upon boot.

You mean the /data/sdext2 that link2sd uses to mount the partition to?

 

[captdroid]

Capt,

Prime mentioned this memory "fix" in the long CM thread, back a few pages. The application Auto Memory Manger. You may remember this app as a way to kill programs in memory, back in the day. It fell out of favor for managing memory as you should not need to kill apps in this day and age. The twist is that the program can be used to force priorities up for applications and proceeses, thereby managing the opposite side of the management equation. I have loaded it again to test, thanks to prime mentioning it.

Funny how sometimes things come around full circle.........

Craig

I was unaware of Auto Memory Manager until I read primes post about it. Thanks prime! It definitely works well the ability to adjust the internal Android task manager. Problem is at least for me is I just don't have enough memory to run what I need simultaneously on CM7 Gingerbread without performance taking a hit when compared to CM6. CM6 does a fine job on it's own the task management (and I suspect with more memory so does Gingerbread) but with more memory available for apps. AMM is worth a try for anyone running Gingerbread and depending your apps may work out using it to make adjustments.

Edit: Those priority changes for specific apps don't necessarily stick, you will see the priority changing back (the developer comments on this his website). They definitely don't stick after a reboot. But the overall task management adjustments do stay and on reboot.

 

[danceswithbongs]

You mean the /data/sdext2 that link2sd uses to mount the partition to?

yep, just wanted to know if I needed to run the make directory commands for it. Also are you running on a Droid? As sometimes with certain ROMs or Kernels with Moto phones you need to insmod an ext2.ko script you place in modules.
Thanks for any info as this may be my new every ROM kernel

Funny how sometimes things come around full circle.........

Craig

Bear, as an animal you should know this...it's the circle of liiiife...

 

[Bear in NM]

Dances,

Yup, it is just funny with android as back in the day folks felt like with the limited ram they needed to "kill" everything. Now that google/moto is killing everything, folks need just the opposite. Some days you eat the bear, some days the bear eats you...

Capt,

Thanks for the tid bit. I have not had a chance to check things over with the app as I tend to be on the lean side of multi-tasking, but I will certainly check the boot persistence, or lack thereof. As an additional side, I wonder if the program Tasker might be more robust here, if you can nail down the exact processes you need fixed. I did see a tweek whereby you could use Tasker to force the 3g back after a call, but I took a look at the program and at first blush seems a little more complex than I want to fiddle with right now. It is a bit pricy, but looks to be a very robust program.

Craig