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

[danceswithbongs]

Here is some info from running some commands or maybe they are queriesmy apologies for the length)

#cat /proc/devices
Character devices:
1 mem
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
13 input
14 sound
29 fb
81 video4linux
89 i2c
90 mtd
108 ppp
128 ptm
136 pts
180 usb
188 ttyUSB
189 usb_device
216 rfcomm
234 ts0710mux
249 hplens-omap
250 hidraw
251 DspBridge
252 hp3a-omap
253 pvrsrvkm
254 rtc

Block devices:
259 blkext
7 loop
31 mtdblock
179 mmc
254 device-mapper

#cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock4 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock0 /config yaffs2 ro,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

#ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 200 192 c00c508c 0000875c S /init
root 2 0 0 0 c0068364 00000000 S kthreadd
root 3 2 0 0 c0058dfc 00000000 S ksoftirqd/0
root 4 2 0 0 c00852a4 00000000 S watchdog/0
root 5 2 0 0 c0064c10 00000000 S events/0
root 6 2 0 0 c0064c10 00000000 S khelper
root 9 2 0 0 c006e728 00000000 S async/mgr
root 12 2 0 0 c0064c10 00000000 S suspend
root 196 2 0 0 c009e1d0 00000000 S sync_supers
root 198 2 0 0 c009ea28 00000000 S bdi-default
root 200 2 0 0 c0064c10 00000000 S kblockd/0
root 204 2 0 0 c0064c10 00000000 S omap_serial
root 211 2 0 0 c0064c10 00000000 S omap2_mcspi
root 214 2 0 0 c0064c10 00000000 S cpcap_irq/0
root 273 2 0 0 c0064c10 00000000 S ksuspend_usbd
root 278 2 0 0 c01f8e78 00000000 S khubd
root 303 2 0 0 c0064c10 00000000 S kmmcd
root 310 2 0 0 c0064c10 00000000 S bluetooth
root 325 2 0 0 c0064c10 00000000 S kondemand/0
root 341 2 0 0 c009e254 00000000 D kswapd0
root 343 2 0 0 c0064c10 00000000 S aio/0
root 344 2 0 0 c0064c10 00000000 S crypto/0
root 358 2 0 0 c017eb98 00000000 D dsi
root 394 2 0 0 c0064c10 00000000 S omap_mdm_ctrl_w
root 423 2 0 0 c01d7144 00000000 S mtdblockd
root 490 2 0 0 c02266a8 00000000 S usb_mass_storag
root 497 2 0 0 c0064c10 00000000 S qtouch_obp_ts_w
root 506 2 0 0 c0064c10 00000000 S bu52014hfv_wq
root 509 2 0 0 c0064c10 00000000 S sfh7743_wq
root 537 2 0 0 c0064c10 00000000 S bridge_work-que
root 538 2 0 0 c0064c10 00000000 S bridge_recovery
root 544 2 0 0 c02863a8 00000000 S w1_bus_master1
root 555 2 0 0 c0064c10 00000000 S kstriped
root 558 2 0 0 c0064c10 00000000 S kconservative/0
root 559 2 0 0 c0064c10 00000000 S kinteractive_up
root 560 2 0 0 c0064c10 00000000 S knteractive_dow
root 561 2 0 0 c0064c10 00000000 S kbumblebee_up/0
root 562 2 0 0 c0064c10 00000000 S kbumblebee_down
root 581 2 0 0 c0064c10 00000000 S als_wq
root 599 2 0 0 c0064c10 00000000 S usbhid_resumer
root 604 2 0 0 c0064c10 00000000 S binder
root 618 2 0 0 c03ad160 00000000 S krfcommd
root 636 2 0 0 c02a59d8 00000000 S mmcqd
root 643 2 0 0 c017e1e0 00000000 D pvrflip/0
root 651 1 164 152 c00c508c 0000875c S /sbin/ueventd
system 974 1 684 112 c02b8b5c afd0b77c S /system/bin/servicemanager
root 975 1 3740 188 ffffffff afd0be2c S /system/bin/vold
root 978 1 548 68 c02cd538 afd0c16c S /system/bin/debuggerd
radio 979 1 12608 440 ffffffff afd0be2c S /system/bin/rild
bluetooth 988 1 1140 108 c00c508c afd0c63c S /system/bin/dbus-daemon
root 989 1 732 132 c0352548 afd0b4dc S /system/bin/installd
keystore 997 1 1620 96 c02cd538 afd0c16c S /system/bin/keystore
root 1011 1 1172 248 c00c508c afd0b8c4 S /system/bin/battd
root 1017 1 1708 104 ffffffff afd0b8c4 S /system/bin/mdm_panicd
shell 1024 1 3292 180 ffffffff 00008294 S /sbin/adbd
compass 1095 1 172 32 c01cab20 0001541c S /system/bin/akmd2
media 7221 1 27980 1008 ffffffff afd0b77c S /system/bin/mediaserver
root 7222 1 4076 276 ffffffff afd0be2c S /system/bin/netd
root 7223 1 76900 10796 c00c508c afd0b8c4 S zygote
system 7232 7223 205688 64220 ffffffff afd0b77c S system_server
radio 7326 7223 99912 13396 ffffffff afd0c5bc S com.android.phone
app_58 8047 1 85788 9144 c0075aa8 afd0c858 S com.bigtincan.android.adfree
app_25 13694 7223 99672 16576 ffffffff afd0c5bc S com.swype.android.inputmethod
system 13734 7223 102812 27392 ffffffff afd0c5bc S com.android.systemui
radio 14503 979 1968 220 c00c508c afd0b8c4 S /system/bin/pppd-ril
app_17 14656 7223 112364 15720 ffffffff afd0c5bc S com.google.process.gapps
app_22 14831 7223 101608 22972 ffffffff afd0c5bc S android.process.acore
root 15048 2 0 0 c00d49f8 00000000 S flush-31:0
app_49 15053 7223 93348 17628 ffffffff afd0c5bc S com.smart.taskbar
app_44 15116 7223 90560 16560 ffffffff afd0c5bc S fi.rojekti.clipper
app_51 15127 7223 96200 21836 ffffffff afd0c5bc S aws.apps.underthehood
app_34 15166 7223 87120 13232 ffffffff afd0c5bc S com.noshufou.android.su
root 15219 15127 620 344 c0056988 afd0c44c S sh
root 15220 15219 776 320 00000000 afd0b4dc R ps

walkin the walk while tappin the talk
danceswithbongs

 

[meishkov]

Amazing kernel I must say. Quick question, can I change the # of slots? I've been using deprimed #20 since it came out basically. I ran 'overclock' then 'primed' and I tried editing in root explorer the /system/etc/init.d/20overclock file that gets created, and I deleted a few slots and changed the max one at the bottom to 1000. Now setCPU detected the 1000 but all the others were still there after a reboot. I also ran the cat /proc/overclock_mpu_opps and it returned everything like it was originally. Like I never edited the file. Do I have to change some order of #'s after the "echo" commands possibly??
I'm just interested in like 350, 550, 800, and 1000 if that's possible? Anybody have any advice?

 

[meishkov]

OK, well the custom frequencies in certain slots worked, but the slots I erased are still visible in setCPU. By the way, I'm not sure if it matters or not, but in /system/etc/init.d/ I have TWO 20files, 20userinit and 20overclock. But I'm assuming 20overclock got loaded. My 20overclock is attached, along with the time in state in setCPU, hahaha which is kinda funny when I look at it now, it's got frequencies all over the place now lol

 

[texstar420]

Yup happened to me as well. But I used the deprimed 1ghz kernel I think and lost Wifi. So I wiped and reflashed to cm 7.0.3 and everything is fine.

Sent from my Droid using DroidForums App

 

[0vermind]

Yup happened to me as well. But I used the deprimed 1ghz kernel I think and lost Wifi. So I wiped and reflashed to cm 7.0.3 and everything is fine.

Sent from my Droid using DroidForums App

Wanted to chime in and say that I lost wifi as well. Thought maybe I had a corrupt data partition or something, so I wiped everything including data and reflashed, and that didn't do a thing.

 

[0vermind]

Prime or anyone else with the knowledge, I am in need of a little assistance.
And by a little I mean a lot.
I have been using link2sd for a long time and the ext partition would be mounted /dev/block/mmcblk0p2.
I use the ext4 driver like Prime had recommended.
I don't know how I messed things up, but it may have been messing around with Swapper 2 and the linux swap partition. I think what ever I did screwed up all of my mount points.
I can no longer even mount the sdext in recovery to format and if I try to restore a pre mess up backup, it isn't allowing the sdext to mount so the nandroid doesn't fully restore.
I get the following error message on recovery: can't mount /dev/block/mmcblk0p2 (file exists)
So restoring the ext gets skipped. I tried.flashing new ROMs to see if that would overwrite whatever was the cause, but no luck. Flashed gb and froyo ROMs but still no luck.
Also I can't seem to find out what exactly exists on mmcblk0p2 or how to move those files to the correct location.
It won't show when running bb commands cat process mounts.
Though it shows the fs mounted to obb and asec and yaffs.
Any assistance would be like manna from above.
I think there is an outside chance that java coding now resides there, but that its merely this quacks weak attempt at a cursory diagnosis.
Help me all you Obi Wan Kenobis, you're my only hope.
My OG has gone from ahhh to AAAHHH!
That's no way for an OG to live.
Thanks to any and all with ideas
There are no dumb suggestions, just dumb people.
Like dumb stupid heads who totally screw their phones mount points up due to incompetence.
Good thing I don't know anyone that would do such a moronic act. I mean that person sounds like a real fool, dumb as rocks.

By an og I figure you mean original ganster? And what rom are you using? Cause CM7 or just gingerbread by defualt allows apps to sd without any special partitioning and such. I've never had good results with swapper, and it always caused more frustration, I would gladly revisit it if it helped improved my battery life which is right now at max 10h standby. But anyways. Why don't you use compcache? or tweak the task killer settings? Just curious why you picked swapper.....?

Minimal use here the last couple days with 88hrs and 42mins of uptime. Battery has 30% left. Android OS and Wi-Fi only used 2% here. LauncherPro used 8%. No CompCache used and have BumbleBee selected. Feels very snappy with no lag. I'm thinking BFS is a great feature! This is running Project Elite 4.2 with a max CPU of 900Mhz.

Dayyyyumm dude!!!! Wanna trade? lol. 10h max on standby here.

You wouldn't have a /proc/overclock directory until you load the overclock module, by default the values stored in /proc/overclock/mpu_opps will be the stock voltages (vsel) until modified

Here are the stock vsel values:

900mhz = vsel:63
800mhz = vsel:62
700mhz = vsel:62
600mhz = vsel:62
550mhz = vsel:56
400mhz = vsel:39
250mhz = vsel:39

Quick question about these voltages. So, since 600, 700, and 800 are the same voltage, does that mean you will get the same battery life on 800 compared to 600? Perhaps better battery life cause things are running faster but on the same voltage? Also if someone were to limit the max screen off to 250, they wouldn't see any different compared to 400 because the voltages are the same? This thought just came to me.

Also, last question, what's the lowest voltage I can go without bricking my phone? Thinking of maybe a min screen off of 100MHz?

 

[DanDroidX]

I am at 50% after 10hrs of normal use on Bumblebee governor at 1GHz. I rarely have it get lower than 50% before I have to drive somewhere and it goes into the car dock and gets plugged in. I wipe BattStats after each rom flash and it to get down to 20 or 30% before charging it. That seems to make a huge difference.

 

[stlcity]

Sorry if this has been asked before :does deprimed work on Droid incredible running cm7. Thanks

 

[quickhonda]

Also, last question, what's the lowest voltage I can go without bricking my phone? Thinking of maybe a min screen off of 100MHz?[/QUOTE]


You can't go that low without causing issues. The biggest of which will be lost calls and messages because the processor will too slow to fire up the programs to accept them in time. It will also cause the processor to fall behind on normal stuff which make the phone lag each time you wake it up and it has to ramp up the speed and quickly catch up. Lots of people have experimented with the lowest numbers but the general agreement is never go below 250 and anything above 400ish is overkill.

 

[zachdroid]

Sorry if this has been asked before :does deprimed work on Droid incredible running cm7. Thanks

No I don't think so. Deprimed is for the d1 only

Sent from my Droid using DroidForums

 

[Maverick0984]

A week or two ago, I actually started using the stock CM kernel. Hate to say it, but it runs much better for my phone at least :-/. I tried several configs and voltages with deprimed and things just weren't nearly as stable as they are now. I dunno, just my $.02. I ran primed, reprimed, deprimed, it all, over the course of a couple months? I don't even know anymore.

 

[meishkov]

Might just be the horrible memory hog known as gingerbread. It's been happening more and more to me. Like since early today, when I feel my phone vibrating before it starts ringing, the screen won't come on for about 7-8 seconds and then the Answer or Decline buttons will come up about 5 seconds after that. Missed a call without even being able to answer, very annoying.
I wouldn't say that it's the kernel for me, more like gingerbread, in running services I only have about 22 or 22MB free, and when I open the browser, it gets EXTREMELY laggy, which I'm assuming is because of lack of memory, since I've seen the Browser take up as much as 34MB before when it would stay loaded in memory and I could check running services or auto memory manager to see what's running.
I turned off JIT a few days ago, so that might have something to do with it, but it was running just fine originally, and I've heard JIT doesn't even help with the OG Droid, even though I usually have it enabled.
Been trying to figure out the whole swap partition thing, but I'm a little confused.

Like ever since Froyo, I've had some apps on my SD, now do I have to move those back to the Phone before I partition the card, or they'll get erased?? It looks like using ROM manager to do it is the easiest way, but after creating the 64MB swap partition, along with the 512MB ext2 or 3 or 4 partition, not sure which ext partition to even use, does it automatically create the necessary scripts to run everything? Haha, kind of a long post, they sure add up quickly. Any ideas anybody?

 

[bigee1212]

Might just be the horrible memory hog known as gingerbread. It's been happening more and more to me. Like since early today, when I feel my phone vibrating before it starts ringing, the screen won't come on for about 7-8 seconds and then the Answer or Decline buttons will come up about 5 seconds after that. Missed a call without even being able to answer, very annoying.
I wouldn't say that it's the kernel for me, more like gingerbread, in running services I only have about 22 or 22MB free, and when I open the browser, it gets EXTREMELY laggy, which I'm assuming is because of lack of memory, since I've seen the Browser take up as much as 34MB before when it would stay loaded in memory and I could check running services or auto memory manager to see what's running.
I turned off JIT a few days ago, so that might have something to do with it, but it was running just fine originally, and I've heard JIT doesn't even help with the OG Droid, even though I usually have it enabled.
Been trying to figure out the whole swap partition thing, but I'm a little confused.

Like ever since Froyo, I've had some apps on my SD, now do I have to move those back to the Phone before I partition the card, or they'll get erased?? It looks like using ROM manager to do it is the easiest way, but after creating the 64MB swap partition, along with the 512MB ext2 or 3 or 4 partition, not sure which ext partition to even use, does it automatically create the necessary scripts to run everything? Haha, kind of a long post, they sure add up quickly. Any ideas anybody?

the ram issue sucks for us OG droid users. but i have the same problem you mentioned, happens sometimes when i get a call and it locks up. the odd thing is that the dialer is always in the foreground (-16 oom value) so it should be responsive... try compcache and see what happens.

256 ram should be good for a phone tho, iphone 3gs has 256 ram and i think iOS 4 was offered to 3gs users with its pseudo multitasking. so i know it can work, its just all memory management of the OS, and gingerbread seems to need better hardware..... problem is nothing is a worthy upgrade yet. galaxy s2 or bionic is what im waiting for.

 

[meishkov]

Yea a reboot usually seems to be the ONLY true remedy to get it fresh and running smooth. Compcache restart doesn't really seem to do the trick for me either. I copied everything from my SD to my PC and am trying to figure out making the ext and swap partitions. If doing it through ROM Manager do the necessary scripts get created that enable/manage the swap partition? I know link2sd can take care of the ext2 or 3, whichever one gets created by RM, once it gets created...but I've had alot of apps on my SD since Froyo came out, now do I have to move all of them individually back to the phone, since the SD gets erased?? These are the small details that have prevented me from starting this.

 

[johnlgalt]

Pleasantly surprised to see Con Kolivos' hand in kernel writing - I thought he had dropped out of kernel writing a couple o years back....

@ExpertonTech says this is the way to go for his builds, so I'm about to use the latest deprimed and have at it. Wish me luck!