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

[Purplehaze]

I have rum cm, ud, ss, and gpa15 and all, for me, have had the data issue. I have tried every kernel and done everything short of a prayer meeting over my phone to fix it. That is until I found this thread. I installed deprimed and the farking data issue went away. From what I've read all the new og Droid roms use the cvpcs fix. Well his *fix* didn't work for me. I am not sure what the hell Prime did, but YAYYYYY, my data works again. Running gpa15 with deprimed at 1100. Only issue is SD card won't mount on a quick reboot. Long live Prime, all hail Prime -)

Edit: compcache is broke on this rom as well.

 

[mightybrick]

I have rum cm, ud, ss, and gpa15 and all, for me, have had the data issue. I have tried every kernel and done everything short of a prayer meeting over my phone to fix it. That is until I found this thread. I installed deprimed and the farking data issue went away. From what I've read all the new og Droid roms use the cvpcs fix. Well his *fix* didn't work for me. I am not sure what the hell Prime did, but YAYYYYY, my data works again. Running gpa15 with deprimed at 1100. Only issue is SD card won't mount on a quick reboot. Long live Prime, all hail Prime -)

Edit: compcache is broke on this rom as well.

Compcache works great with deprimed and CM7. Give it a shot.

 

[Purplehaze]

I have rum cm, ud, ss, and gpa15 and all, for me, have had the data issue. I have tried every kernel and done everything short of a prayer meeting over my phone to fix it. That is until I found this thread. I installed deprimed and the farking data issue went away. From what I've read all the new og Droid roms use the cvpcs fix. Well his *fix* didn't work for me. I am not sure what the hell Prime did, but YAYYYYY, my data works again. Running gpa15 with deprimed at 1100. Only issue is SD card won't mount on a quick reboot. Long live Prime, all hail Prime -)

Edit: compcache is broke on this rom as well.

Compcache works great with deprimed and CM7. Give it a shot.

What is the latest stable version of cm7?

 

[dfuser312553]

http://mirror.teamdouche.net/?type=stable&device=sholes

 

[DanDroidX]

I think Prime is gone.

Sent from the Droidforums App via a Neurocellular Processing Unit.

 

[KJW979]

I think Prime is gone.

Sent from the Droidforums App via a Neurocellular Processing Unit.

No answer to your email, well just hope/ pray he is OK.

Sent from my Droid using DroidForums

 

[jerroedr]

hope all is well sir prime! good vibes your way

 

[speedfreeq]

So I'm loving this kernel! Best battery life I've seen with GB. I'm a little confused about using the scripts, though. Some of them seem to be working fine, others not so much.
In terminal, I type "su" and get the indication that permissions are enabled. Then "sysrw" and it tells me system is mounted re writeable.
I type "overclock" and I get the list of ULV vsels, and it tells me I'm primed.
However, when I type "primed," it gives me conflicting feedback; it first tells me it can't create the 20overclock file because the file system is read-only. Then it tells me that the kernel is now primed at boot and reminds me to run "deprime" to revert... then it again says the etc/init.d/20overclock file can't be created.
Using Root Explorer to check, the file is definitely not there. Any ideas on how to overcome this glitch?
Otherwise, the kernel is the bomb... the only ULV that's ever worked for me.

Sent from my Droid using DroidForums

 

[pigpen]

#primed and #overclock are the basically the same command. #overclock will leave your phone in a state with ulv kernel settings until you reboot. #primed will leave your phone in a ulv kernel state until your issue the command #deprime

If you issue both of those commands in the same terminal, your basically getting an error on the second command cause the process' has already be started. you dont need to run them both. one is for a temporary state, the other is for a more permanent state thru reboot, until you issue #deprime command.

 

[ryocoon]

So I'm loving this kernel! Best battery life I've seen with GB. I'm a little confused about using the scripts, though. Some of them seem to be working fine, others not so much.
In terminal, I type "su" and get the indication that permissions are enabled. Then "sysrw" and it tells me system is mounted re writeable.
I type "overclock" and I get the list of ULV vsels, and it tells me I'm primed.
However, when I type "primed," it gives me conflicting feedback; it first tells me it can't create the 20overclock file because the file system is read-only. Then it tells me that the kernel is now primed at boot and reminds me to run "deprime" to revert... then it again says the etc/init.d/20overclock file can't be created.
Using Root Explorer to check, the file is definitely not there. Any ideas on how to overcome this glitch?
Otherwise, the kernel is the bomb... the only ULV that's ever worked for me.

Sent from my Droid using DroidForums

Ah! There is the issue... I think the scripts themselves make calls that enable system RW, and then set it back to ReadOnly afterwards.
that might be the issue. Otherwise, how would he write the 20overclock files when you run "primed" ?

 

[speedfreeq]

Okay. I went back and rebooted. Theoretically, this should have cleared the overclock from the script, right?
Then I opened a #su shell in terminal and tried to run the #primed script with no other inputs. It gave me the same errors as outlined above, simultaneously telling me the file couldn't be created, but running # deprimed would revert, then again that the 20overclock file was not created. I then tried running the script after #sysrw, with the same result. So I tried the #overclock script in the same shell, AFTER these failures, and it worked flawlessly. Tells me I'm primed, shows me vsels, reminds me to run #deprimed to revert.
For whatever reason, on my D1 with PEv5.0.2 (Android 2.3.2), the scripts in the kernel cannot write the 20overclock file, even when /system is mounted rw. Why??

Sent from my Droid using DroidForums

 

[zachdroid]

Have you tried reflashing the kernel? Then trying the primed command.

Sent from my Droid using DroidForums

 

[speedfreeq]

On your suggestion, I tried reflashing, with no success. So what I had to do was use Root Explorer to set the /system and the /etc folder permissions to rw, then go back into the terminal shell, where the #primed script finally worked. The 20overclock
file is now present where it ought to be. Don't know why the sysrw script was not setting permissions correctly for the subfolders?
Sent from my Droid using DroidForums

 

[Nausicaa]

Anyone ever use this with quick clock? They don't seem to play together, I get freezes and whatnot, its strange that some stuff works, it sets my minimum vsel on 125 as 13 or something and it still works, except its very slow.

 

[Samurai26]

Just a quick question, is the deprimed kernel LV? FYI I don't use the Milestone Overclock app, I use SetCPU

Sent from my Droid using Tapatalk