What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

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

for the record prime, as per the 3g drop issue over in the winner00 build thread, it's def NOT deprimed, I've had 3g drop out after a call with 4 diff kernels today, clearly whatever fix they implemented for most people broke it for me, as I never had 3g issues before they "fixed" it

Thanks for letting me know.

I agree Prime, I've tested three kernels besides yours on 7.0.2 (including stock) and 3g is dropping regularly, which it wasn't for a long time on the nightlies. The 3g fix clearly broke 3g for a lot of people.

Sent from my Droid using Tapatalk
 
for the record prime, as per the 3g drop issue over in the winner00 build thread, it's def NOT deprimed, I've had 3g drop out after a call with 4 diff kernels today, clearly whatever fix they implemented for most people broke it for me, as I never had 3g issues before they "fixed" it

Thanks for letting me know.

I agree Prime, I've tested three kernels besides yours on 7.0.2 (including stock) and 3g is dropping regularly, which it wasn't for a long time on the nightlies. The 3g fix clearly broke 3g for a lot of people.

Sent from my Droid using Tapatalk

strangely enough, I've found toggling WiFi on and off (even if there's no network to connect to) bring my 3g back
 
USB Connection

Prime,

Just letting you know that as of CM7.0.2 - Deprimed 19, attempting to connect the phone to a computer through USB fails. I press "Turn on Storage," the loading spinner goes for a while, and then it just returns to the button saying "Turn on Storage."

I don't remember having had this problem before with your kernel. But honestly, it's been a while since I've tried to use it. As a side-note, I have dropbox up and running, and adb isn't broken. So, if necessary, I can still get files from my computer to my phone and vice versa, but being able to mount the SD through USB is very handy.

If you have any thoughts on how I can fix this, they would be much appreciated, as is all your work!

-HG
 
Hopefully those of you who are experiencing 3g problems are communicating your device and specific issue to Cyanogen. For me, I was one of the original submitters of the issue and with CM7.02 and latest deprime I have not had this issue since the fix. First time since CM7 branch. So for me, an original Droid 1 device, all is fixed re: 3g not returning after a call or receiving a call.:icon_ banana:
 
Reporting back:
Well, I don't know what exactly the problem was, but now I've been manually editing 20overclock on breaks at work, and the settings are working correctly now. Guess it was just some fluke, or maybe I just didn't hold my mouth right, lol. Got her stable now on 1200 with vsel 73. Gonna tweak some more and lower the top slot speed. :) Thx again for ur help, and for ur work on this fantastic kernel! dancedroid
 
I'm running Project Elite v5.0.2. In Elite Settings, I have the kernel's governor to bublebee, and the max is 900mHz, and the min is 250mHz.

I put Deprimed on my OG Droid, and got kinda confused.

I immediately ran:

su
overclock

I didn't really understand what that did except that it put it into ULV.

I then proceded to use the declock.zip, then tried to run:

su
primed

Didn't work. Says I already ran "overclock," and that I should run "deprime." That didn't work either. Same error. I rebooted after each command.

My question: What do I have to do if I want it to automatically boot up into Ultra low voltage (or low voltage), and running at 250-900mHz with the Bumblebee governor? I don't understand it very well. :o Sorry, and thanks for any help in advance.
 
I'm running Project Elite v5.0.2. In Elite Settings, I have the kernel's governor to bublebee, and the max is 900mHz, and the min is 250mHz.

I put Deprimed on my OG Droid, and got kinda confused.

I immediately ran:

su
overclock

I didn't really understand what that did except that it put it into ULV.

I then proceded to use the declock.zip, then tried to run:

su
primed

Didn't work. Says I already ran "overclock," and that I should run "deprime." That didn't work either. Same error. I rebooted after each command.

My question: What do I have to do if I want it to automatically boot up into Ultra low voltage (or low voltage), and running at 250-900mHz with the Bumblebee governor? I don't understand it very well. :o Sorry, and thanks for any help in advance.


It was my understanding that all you need to do is 1. flash deprimed kernel, 2. open terminal emulator, type:

su
primed
sysro

and there after the script creates an overclock file for you and from that point forth you are running, at boot, the ulv settings Prime has created for us. After that you just go. The governor you are looking for, bumblebee, is in the CM performance tab under settings. Go into that area of the settings select and go. I personally have had better luck with the ondemand setting, my phone feels more snappy there, but every phone is different.

I hope this helps. If you have questions as to whether everything is going like it should you can always reflash the kernel and start the whole process over again. Fortunately it isn't a lengthy thing to do.

Zach
 
I'm running Project Elite v5.0.2. In Elite Settings, I have the kernel's governor to bublebee, and the max is 900mHz, and the min is 250mHz.

I put Deprimed on my OG Droid, and got kinda confused.

I immediately ran:

su
overclock

I didn't really understand what that did except that it put it into ULV.

I then proceded to use the declock.zip, then tried to run:

su
primed

Didn't work. Says I already ran "overclock," and that I should run "deprime." That didn't work either. Same error. I rebooted after each command.

My question: What do I have to do if I want it to automatically boot up into Ultra low voltage (or low voltage), and running at 250-900mHz with the Bumblebee governor? I don't understand it very well. :o Sorry, and thanks for any help in advance.


It was my understanding that all you need to do is 1. flash deprimed kernel, 2. open terminal emulator, type:

su
primed
sysro

and there after the script creates an overclock file for you and from that point forth you are running, at boot, the ulv settings Prime has created for us. After that you just go. The governor you are looking for, bumblebee, is in the CM performance tab under settings. Go into that area of the settings select and go. I personally have had better luck with the ondemand setting, my phone feels more snappy there, but every phone is different.

I hope this helps. If you have questions as to whether everything is going like it should you can always reflash the kernel and start the whole process over again. Fortunately it isn't a lengthy thing to do.

Zach

I'm assuming this is the Overclock command I have been asking about in a couple of posts? Is this for ALL ROMS or just CM?

Thank You
 
I'm running Project Elite v5.0.2. In Elite Settings, I have the kernel's governor to bublebee, and the max is 900mHz, and the min is 250mHz.

I put Deprimed on my OG Droid, and got kinda confused.

I immediately ran:

su
overclock

I didn't really understand what that did except that it put it into ULV.

I then proceded to use the declock.zip, then tried to run:

su
primed

Didn't work. Says I already ran "overclock," and that I should run "deprime." That didn't work either. Same error. I rebooted after each command.

My question: What do I have to do if I want it to automatically boot up into Ultra low voltage (or low voltage), and running at 250-900mHz with the Bumblebee governor? I don't understand it very well. :o Sorry, and thanks for any help in advance.

Overclock script is just temporary, basically so you can check to see if kernel runs good on your phone, after a reboot it will go back to standard voltages. After install kernel can flash overclock for a temp trial, then depending on what voltages you want in SU either run primed for ulv or deprime for standard voltages. Open SU, type in su, then enter, then either primed or deprime, enter, script should run and stay.

Sent from my Droid using DroidForums
 
I'm running Project Elite v5.0.2. In Elite Settings, I have the kernel's governor to bublebee, and the max is 900mHz, and the min is 250mHz.

I put Deprimed on my OG Droid, and got kinda confused.

I immediately ran:

su
overclock

I didn't really understand what that did except that it put it into ULV.

I then proceded to use the declock.zip, then tried to run:

su
primed

Didn't work. Says I already ran "overclock," and that I should run "deprime." That didn't work either. Same error. I rebooted after each command.

My question: What do I have to do if I want it to automatically boot up into Ultra low voltage (or low voltage), and running at 250-900mHz with the Bumblebee governor? I don't understand it very well. :o Sorry, and thanks for any help in advance.

Overclock script is just temporary, basically so you can check to see if kernel runs good on your phone, after a reboot it will go back to standard voltages. After install kernel can flash overclock for a temp trial, then depending on what voltages you want in SU either run primed for ulv or deprime for standard voltages. Open SU, type in su, then enter, then either primed or deprime, enter, script should run and stay.

Sent from my Droid using DroidForums

I believe it's:
Open Terminal,
su
sysrw
primed
sysro

because you kinda need read-write permissions to create the 20overclock file. The sysrw command gives you read-write permissions, sysro gives read-only. That's how I had to do it, anyway.
 
Alright, this is what the Emulator is throwing back out:

su
sysrw
primed
cp: can't create '/system/etc/init.d/20overclock': read only file system
Disclaimer: You have enabled overclock, your device will now run the /etc/init.d/20overclock script and overclock module upon boot.
sh: can't open /etc/init.d/20overclock


What do!? :o I've already tried running de-clock, same problem.
 
Back
Top