• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root (Guide) Unleash the Dual Core!! (Enable CPU1)

Sepero said:
Bard, your script here will work with BootBuddy. I would just recommend that users rename the file to 10init.qcom.post_boot.sh

Simply drop the script in the boot_buddy_scripts folder and it's good to go. Cheers
:o
Click to expand...

I never tried BootBuddy :) but I will definitely check it.
 
rhino889a said:
One thing i noticed here. Setcpu settings seem to effect the 0 core not the 1core. That may are may not help desired manipulations.
Also would use cause (wear) like cpu0 might wearout quicker without this more even setting. Or maybe less heat factor for the 0 core.?

To above post Limiting the frequency may actually cause cpu1 to be more online anyways.. Just guessing.
But i know what you are saying .i sometimes leave my settings at 384 0r the 500 something setting. Seems to alot of my needs just fine.


So now i am wondering because i never thought to check cpu1 till recently. Without this mod. If you use setcpu or ther app to limit to say 720. Is it actually limiting the second core to 720. I never thought to check as the moniitir aop i used,before did not reveal the cpu1 speed.

Jpizle for my curiousity can you verify that cpu1 does not go above 800?
Click to expand...

Another interesting info :)

I tested with CPU control function in Rom Tool Box Pro and it gave me unexpected result.

When I tried to underclock CPU to 1GHz with Rom Tool Box Pro, it underclocked CPU1 instead of CPU0.

If you see my screenshot, CPU0's max is 1.5 but CPU1's max is 1.0
I put CPU1 offline then tested again. Result was same Rom Tool Box was changing clock speed of CPU1.

Since devices & apps are all different, unless you use specific app that can control each CPU, actaul applied result may not be same as desired outcome.
 

Attachments

  • Screenshot_2013-02-27-05-05-48[1].png
    Screenshot_2013-02-27-05-05-48[1].png
    58.4 KB · Views: 131
Dont worry jpizzle. I understand your point. My point is some of us may never be fully happy till we are in full control of our phones. We want what we want.manipulate it for our needs.maybe try something and decide its not what we want.
For me now,this is only step one. The benifit of this teamwork had revealed more things i deem inadequate. I feel a need for lower min frequency and ability to have full control of cores. Like setcpu written to controth both cores.

To admit the truth this phone is great when i opened the box.you know.It almost equal to my dell e1405 laptop.and three times more powerful than my first computer. Coming from optimus m,and admire this phone is like a Google server. But i have come to realize that half the codes and scripts i see are designed to actually LIMIT what is possible.
Its like my phone is my Old Chevy. I pull er out of the garage and rip through the neighborhood throwing chunks of rubber and and pavement everywhere. I get it back in the garage before the police show up.I look at it and say wow that was cool. Alright lets modify the carbs, tweak the clutch ,set new points and get ready for the next RIPRIDE.
Good is only good enough when i cant make it better.
 
so if i try this and i dont like the toll on my battery can i undo it very easy or will i have to use the unbrick guide?
 
h4x0rj3ff said:
so if i try this and i dont like the toll on my battery can i undo it very easy or will i have to use the unbrick guide?
Click to expand...


Good question.

The solution is make init.qcom.post_boot.sh file back to original.

Follow Hard way Step5 -> 4 backward.


If your script looks like this.
chmod 220 /sys/devices/system/cpu/mfreq
chown root.system /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online


Change back to this (delete echo 1 and change 444 to 664).
chmod 220 /sys/devices/system/cpu/mfreq
chown root.system /sys/devices/system/cpu/cpu1/online
chmod 664 /sys/devices/system/cpu/cpu1/online



Later, I will post original init.qcom.post_boot.sh file for easy back up as well.
 
Save a copy of the orginal .replace the original if not liked. Or use the bootbuddy way .dont like it delete the script. I personally added .bak to the original and pasted the new one. That way the original is still tgere. Remember reboot is necessary
 
h4x0rj3ff said:
so if i try this and i dont like the toll on my battery can i undo it very easy or will i have to use the unbrick guide?
Click to expand...

The script can very easily be enabled and disabled by using BootBuddy. Also, a new update for BootBuddy has just been released, version 1.3.

To use this script with BootBuddy, simply do this

  1. Download Bard's cpu script
  2. Rename it to something like 10init.qcom.post_boot.sh or 10bards_max_cpu.sh ;)
  3. Put it in your devices boot_buddy_scripts folder
  4. Then reboot your phone to activate it
To disable it, just remove it from your boot_buddy_scripts folder, and reboot.

Cheers
 
I am going to assume if bootbuddy is on external sd and a script bootloops or any other bad effects simplg remove sdcard reboot and all is well
Or maybd i havd 3 sdcards each has a different set of scripts loaded. Just pop in for different settings
 
rhino889a said:
I am going to assume if bootbuddy is on external sd and a script bootloops or any other bad effects simplg remove sdcard reboot and all is well
Or maybd i havd 3 sdcards each has a different set of scripts loaded. Just pop in for different settings
Click to expand...
Correct!
 
As i mentioned before copy the original one and save it somewhere or simply add .bak to the original then paste the new one. Dont like it delete it and delete .bak from original file name then reboot.

You already have the file

init.qcom.post_boot.sh to init.qcom.post_boot.sh.bak
 
Can someone plz give be directions on how to use the app to force cpu 1 online . I know its a drainer but maybe that app that someone posted on a post could make up for it by turning cpu1 to sleep while screen off . Thanks in advance
 
I know it has to do with tweaks options , but i cant find it in rom tool box pro . I did it once before a long time ago but the app has been updated since .
 
I would , but i dont think i have original ones . Correct me if im wrong anyone , ill post up just let me know where to find that file or files . Thanks
 
<Stupid_Question> If we can mod one of these scripts to turn on CPU1, why can't we mod a script to skip aboot and sbl1/2/3 encryption checks? </Stupid_Question>
 
2GigayteSD said:
<Stupid_Question> If we can mod one of these scripts to turn on CPU1, why can't we mod a script to skip aboot and sbl1/2/3 encryption checks? </Stupid_Question>
Click to expand...


I don't know exact boot sequence but as file name says (init.qcom.post_boot.sh), this file seems like it gets called after all major booting is over.

Some of you may read this artible @ XDA forum regarding MSM8960 CPU. SLB1/2/3 gets excuted very early stage.

MSM8960_BA_secure_boot_1.jpg


(Warning very technical and long lol)
http://forum.xda-developers.com/showthread.php?t=1856327
 
You must log in or register to reply here.
Back
Top Bottom