1287 replies to this topic

[rnh]

 

 

 

Well folks, it seems the new busybox update breaks my init.d module support at boot.  This means your not running any of the added governor / schedulers.

 

Exactly. Which is is why the universal init.d app doesn't work. It needs init.d support to add the extra governors and schedulers. I've used it before on different roms. The first thing the app does is ask to test for init.d support which busybox removed but I did it and the test shows no busybox support. Going into set cupu shows no added govs or scheds. Sorry.

[lazer]

 

Well folks, it seems the new busybox update breaks my init.d module support at boot.  This means your not running any of the added governor / schedulers.

 

Exactly. Which is is why the universal init.d app doesn't work. It needs init.d support to add the extra governors and schedulers. I've used it before on different roms. The first thing the app does is ask to test for init.d support which busybox removed but I did it and the test shows no busybox support. Going into set cupu shows no added govs or scheds. Sorry.

 

Forget the "Test" part, It is always going to report back no support. That's why you simply turn the "SWITCH" to ON at the top of the app and reboot. Then you will have the added govs and schedulars in SetCPU.. Try it!

[rnh]

Forget the "Test" part, It is always going to report back no support. That's why you simply turn the "SWITCH" to ON at the top of the app and reboot. Then you will have the added govs and schedulars in SetCPU.. Try it!

I did. No go 

[lazer]

I did. No go 

Worked fine for me. :

 

[rnh]

When i reboot I don't get mange your init.d scripts.

[lazer]

When i reboot I don't get mange your init.d scripts.

Have you toggled the button to say [ON] as in my first screenshot - previous post above?

[rnh]

of  course' I've used the app before

[lazer]

of  course' I've used the app before

My best guess for you would be to boot into recovery, Do a cache & dalvik wipe then proceed to Advanced/Fix permissions and execute that. Boot back into Blurry ,, load up Universal Init.d and try the procedure again - toggle ON and reboot.

[CrazyEddie]

Forget the "Test" part, It is always going to report back no support. That's why you simply turn the "SWITCH" to ON at the top of the app and reboot. Then you will have the added govs and schedulars in SetCPU.. Try it!

I can confirm this works using No Frills CPU as well. Thanks for the tips guys.

[MarkusMcNugen]

 

Well folks, it seems the new busybox update breaks my init.d module support at boot.  This means your not running any of the added governor / schedulers.

 

Exactly. Which is is why the universal init.d app doesn't work. It needs init.d support to add the extra governors and schedulers. I've used it before on different roms. The first thing the app does is ask to test for init.d support which busybox removed but I did it and the test shows no busybox support. Going into set cupu shows no added govs or scheds. Sorry.

 

 

Try this

 

Please Login or Register to see this Hidden Content

 

 

[garywojdan81]

Forget the init.d app. Add this line: busybox run-parts /system/etc/init.d at the bottom of the install-recovery.sh file in system/etc. Forces the execution of init.d This will work to enable init.d on any ROM. Sent from my DROID RAZR using Tapatalk 2

[rnh]

my thoughts exactly and if that doesn't work I'll dirty flash the rom

[garywojdan81]

my thoughts exactly and if that doesn't work I'll dirty flash the rom

Confirmed working for me on a clean install of Blurry1.1 in slot1.
I even modified the vold.fstab to swap the storage locations too.

Sent from my DROID RAZR using Tapatalk 2

[eye__dea]

Confirmed working for me on a clean install of Blurry1.1 in slot1.
I even modified the vold.fstab to swap the storage locations too.

Sent from my DROID RAZR using Tapatalk 2

Is your modules there after updating busybox and rebooting?  We were thinking of modifying the sysint in /bin, but I have not tested it yet cause I am stuck at work.  There are multiple ways to add init.d support and I guess the one baked in just doesn't play nice for some reason.

[rnh]

my thoughts exactly and if that doesn't work I'll dirty flash the rom

I was referrimg to the wipes. I'm not a linux person. I'll try it out Thanks Gary seen you around the various forums;

[CrazyEddie]

Is your modules there after updating busybox and rebooting?  We were thinking of modifying the sysint in /bin, but I have not tested it yet cause I am stuck at work.  There are multiple ways to add init.d support and I guess the one baked in just doesn't play nice for some reason.

Well it turns out I lied. They are not loading.I could have sworn they did after my first reboot but they certainly haven't been there after a couple reboots. I should have doublechecked, apologies.

[rnh]

Forget the init.d app. Add this line: busybox run-parts /system/etc/init.d at the bottom of the install-recovery.sh file in system/etc. Forces the execution of init.d This will work to enable init.d on any ROM. Sent from my DROID RAZR using Tapatalk 2

No go

[garywojdan81]

Yep, all modules loaded, confirmed with the baked-in tweakerz app & pegasusq/sio confirmed as default using ROM toolbox pro. What I did was: Install ROM on a clean slot1 Boot up/set up everything Verify modules/gov/sched Install stericsons busybox app & update busybox Reboot & verify failure of module load Edit the install-recovery.sh Reboot & verify module load Edit vold.fstab Reboot & verify module load & storage swap So far, for me, everything's loaded & working Sent from my DROID RAZR using Tapatalk 2

[garywojdan81]

No go

Modules don't show loaded? I edited the install-recovery.sh using root browser. What did you use to add the line and, no offense, did you save the changes?

Sent from my DROID RAZR using Tapatalk 2

[CrazyEddie]

Well it turns out I lied. They are not loading.I could have sworn they did after my first reboot but they certainly haven't been there after a couple reboots. I should have doublechecked, apologies.

UPDATE - Fix Permissions brought them back - they are all now loaded after reboot.