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

[chikimonke]

Its the deprimed kernel not the build. I build a fully stock build and when I would turn on wifi with the stock kernel I would get a reboot but usb worked. I flashed deprimed and wifi worked but usb doesn't.

I'm not saying you're wrong, as I do not have enough knowledge to confidently state one way or the other. However, I do know that the USB data transfer was working on Build #38 with the Deprimed kernel. Now with build #39, which "fixed Usb tethering" and the same Deprimed kernel, I can no longer get the data connection unless I'm in Recovery. Mounting USB storage there still works just fine. Could it be that something that was changed in #39 caused the kernel to no longer play nice with the data connection?

 

[winner00]

Its the deprimed kernel not the build. I build a fully stock build and when I would turn on wifi with the stock kernel I would get a reboot but usb worked. I flashed deprimed and wifi worked but usb doesn't.

I'm not saying you're wrong, as I do not have enough knowledge to confidently state one way or the other. However, I do know that the USB data transfer was working on Build #38 with the Deprimed kernel. Now with build #39, which "fixed Usb tethering" and the same Deprimed kernel, I can no longer get the data connection unless I'm in Recovery. Mounting USB storage there still works just fine. Could it be that something that was changed in #39 caused the kernel to no longer play nice with the data connection?

Yea I would imagine it was the USB Tether fix the broke it. Now prime just has to update his kernel to fix it.

 

[HarvesterX™]

Here is a heads up for anyone using this with Pete's GPA builds. Before running the primed script, create the /etc/init.d directory manually. Then run the primed script from tsrminql. Now, open up the file created in the init.d directory and copy the contents. You can now erase the entire init.d directory. Now open up /etc/install-recovery.sh for editing and comment out Pete has in there. Then paste the contents you copied earlier from after running the primed script. Now everything will automatically run at startup as if normal. For some reason it wasn't taking my custom changes unless I did this..

For those that don't know, Pete's GPA builds are meant to be as close to stock as possible, so no init.d directory. Instead he hijacked the install-recovery.sh script to implement automatic overclocking of kernels so SetCPU wouldn't be neccassary. I've tested this method out and it works flawlessly, even changing the frequencies and voltages created from the primed script. I hope this helps somebody at least.

If you are in another ROM without an init.d directory, you can follow the same procedure, but you might have to create the install-recovery.sh file because it's normally removed to prevent any custom recoveries from being overwritten with the stock one upon reboot. Anyways...happy hunting. Pm me if I missed something or styes something incorrectly.

 

[pdroid]

Its the deprimed kernel not the build. I build a fully stock build and when I would turn on wifi with the stock kernel I would get a reboot but usb worked. I flashed deprimed and wifi worked but usb doesn't.

I'm running the latest deprimed

Sent from my NookColor using Tapatalk

 

[prime]

I will look at the CM ril changes and see what needs to be changed (if anything) on deprimed.

I will first integrate the updated USB gadget source, I imagine this alone should fix the tether option.

I'm still torn about my cousins death but need to do something to take my mind off it, maybe some kernel development will help.

 

[prime]

Good work.

 

[zachdroid]

Good to see you Prime

Sent from my Droid using DroidForums

 

[GodfatherIP]

Hey Prime, I was using your link2sd script with the deprimed kernel and I recently decided to update busybox to v1.19. When I rebooted my sdext apps did not come back, I tried rebooting several times but it did not help. I then deleted your script and let link2sd make its script again and everything worked. Is there any reason that your script wouldn't work with the latest busybox version? It seems odd that the link2sd script worked for me but yours did not. Thanks.

Also I am very sad to hear about your cousin. My thoughts are with you and your family during these difficult times.

 

[gambit07]

I will look at the CM ril changes and see what needs to be changed (if anything) on deprimed.

I will first integrate the updated USB gadget source, I imagine this alone should fix the tether option.

I'm still torn about my cousins death but need to do something to take my mind off it, maybe some kernel development will help.

I was extremely sorry to hear about that, I hope this will help you keep your mind off things for a while. I also wanted to ask if you might update reprimed as well to fix USB. Thanks for all your work

 

[prime]

Hey Prime, I was using your link2sd script with the deprimed kernel and I recently decided to update busybox to v1.19. When I rebooted my sdext apps did not come back, I tried rebooting several times but it did not help. I then deleted your script and let link2sd make its script again and everything worked. Is there any reason that your script wouldn't work with the latest busybox version? It seems odd that the link2sd script worked for me but yours did not. Thanks.

Also I am very sad to hear about your cousin. My thoughts are with you and your family during these difficult times.

Thanks for your thoughts. BusyBox v1.19 is experimental, but I recommend not using any busybox installer as they seem to always break compatibility.

To get a known good copy of busybox pull the cyanogen mod version from the zip, place it in the same directory as the previous busybox and run this from the same directory ./busybox --install /path/to/busybox

You will likely need to mount /system rw first as busybox is generally located in /system/xbin

 

[GodfatherIP]

Hey Prime, I was using your link2sd script with the deprimed kernel and I recently decided to update busybox to v1.19. When I rebooted my sdext apps did not come back, I tried rebooting several times but it did not help. I then deleted your script and let link2sd make its script again and everything worked. Is there any reason that your script wouldn't work with the latest busybox version? It seems odd that the link2sd script worked for me but yours did not. Thanks.

Also I am very sad to hear about your cousin. My thoughts are with you and your family during these difficult times.

Thanks for your thoughts. BusyBox v1.19 is experimental, but I recommend not using any busybox installer as they seem to always break compatibility.

To get a known good copy of busybox pull the cyanogen mod version from the zip, place it in the same directory as the previous busybox and run this from the same directory ./busybox --install /path/to/busybox

You will likely need to mount /system rw first as busybox is generally located in /system/xbin

Ok, thanks Prime. I updated because zepplinrox suggested it might get rid of the "stderr" messages I get when running his supertest script for memory management. Also I did have a major problem with the busybox installer the first time I used it: I installed to /system/bin/ instead of /system/xbin/ and somehow it broke my SU permissions! None of my programs could gain root access so I had to nandroid restore to get things working again. People should definitely be careful if they use the installer.

 

[Bear in NM]

I got rid of the busybox installer/update apk quite some time ago. I found that as busybox is at the heart of a lot of apk's, some of which are not easily apparent that updating to newer versions just was not necessary. If you are a hardcore user then it is not a problem, as you understand and can troubleshoot. For the more casual user who is not doing lots of scripting/codework, it seems best to just leave alone. And Godfather, I too get those stderr lines on a few of my GScripts, but they are not fatal.

Craig

 

[TheJeenyus]

I just ran the update_deprimed script. It dll from the dropbox but the reboot operation was not permitted. I know I can run it manually through recovery but how can I allow it for future updates?

Sent from my Droid using DroidForums

 

[TheJeenyus]

I reflashed the deprimed test.zip and everything is working smoothly now

Sent from my Droid using DroidForums

 

[droidwire]

I went back to deprimed #14 (26) due to this issue.

http://www.droidforums.net/forum/showthread.php?t=139968

Navigation Reboots - Winner/Deprimed

Sent from my Droid using DroidForums