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

Root REAL BrokenOut CPU Fix (no deleting files)

D

Dracconus

Android Enthusiast
This doesn't require you to delete a file; but instead modify it to what was supposed to be in the file.

Setup:

1. Download Root Explorer (or a similar free root browser)
2. Make sure you're browsing as root.
3. Mount the system with read/write privileges (each explorer does this differently, so if you need help use google, or just ask :D )
4. Browse to /system/etc/
5. Open init.qcom.post_boot.sh with a txt editor
6. Add this:

Code: 
echo 1800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1800000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

under
Code: 
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
[code]

so that it looks like this...
[code]
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1800000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

7. Save the file
8. Reboot, and enjoy.
9. Press the thanks button if I helped you - Makes me smile, and know you love me :P
 
well... tried it again with the notepad mentioned and still nothing so can some PLZZZZ post a link with the fix already included??? ::(
 
Still staying at 1512 for me.

Not sure if i am doing anything wrong concerning this.
The profiles won't stick unless i delete the Post boot file. WHen they are deleted, and I restart, it will default to 1512, I would then go into romtoolbox and set my profiles. Only then does the clock speeds stick.

This is happening to my phone, the wifes phone and my bro in law's phone.
 
Ok, I added the post_boot again.

It works, the clocks are sticking, only upon reboot does the clock speed now jump to 1800 then i would still have to reset the profiles.

Is that supposed to happen when restarting?

Temp also dropped a few degrees.
 
VeNoMzRevenge said:
Ok, I added the post_boot again.

It works, the clocks are sticking, only upon reboot does the clock speed now jump to 1800 then i would still have to reset the profiles.

Is that supposed to happen when restarting?

Temp also dropped a few degrees.
Click to expand...

Yes, the clocks will be set at 1800 on boot because as 'smart' as the cpu's are supposed to be for cell phones they really aren't. Profiling helps that issue, but not as much as it could.

Anyways, This should work for everyone, as it's got the information that was apparently missing to make it stick on everyone's connect.
To the people that are saying they didn't have problems, neither did I the first flash, but a few after that didn't stick. I know that there's another issue deeper in the rom, but there's not really a way to find that unless you made the rom. The only person that would be able to pinpoint that issue without a shit ton of unnecessary debugging would be MtMichaelson.
If this does NOT fix your problem then that isn't really that much of an unexpected occurrence since this is a bug really similar in operation to the way that LG did a shitty job checking the wifi code.
Every phone will be different, but to those that need a fix, definitely try this first, and then if you need to delete feel free to. I'm just providing a real coded method of fixing it versus a method that involves deleting files. Let's face it: If they weren't necessary they wouldn't exist...
 
Learn something new everyday, thanks for the information.

So, I don't really have a problem anymore. Thank you for the script and thanks for the info.
 
Code: 
echo 1800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1800000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
Click to expand...

Code: 
case "$target" in
    "msm8660_surf" | "msm8660_csfb" | "cayman")
    [COLOR=Red]    #start mpdecision[/COLOR]
    [COLOR=Red]    #start thermald[/COLOR]
    ;;
esac
[/CODE]
By adding a # to start mpdecision and start thermald disables these lines from starting.Power off after editing this file. The cpu setting are sticking even without any profiles. This is a temporary fix till we can find out what is causing these two lines to override our custom settings. Im currently at max 756 min 384 with gov set to interactive. If this works for you set gov to interactive. This is better then deleting the entire file.
 
rav2012 said:
Code: 
case "$target" in
    "msm8660_surf" | "msm8660_csfb" | "cayman")
    [COLOR=Red]    #start mpdecision[/COLOR]
    [COLOR=Red]    #start thermald[/COLOR]
    ;;
esac
[/CODE]
By adding a # to start mpdecision and start thermald disables these lines from starting.Power off after editing this file. The cpu setting are sticking even without any profiles. This is a temporary fix till we can find out what is causing these two lines to override our custom settings. Im currently at max 756 min 384 with gov set to interactive. If this works for you set gov to interactive. This is better then deleting the entire file.
Click to expand...


This is what worked for me.

I tried adding the max frequency code and renaming the file (added.bak) to disable it but adding the # was what finally worked.
 
As stated, I just deleted the damn thing lol. I got tired of messing with it, and this fix here causes it to freeze for me. No negative impact after deleting the file a month ago.

I probably will just leave it deleted. Its working right without, I see no reason to try to fix something that's not broke.
 
BWAHAHAHAHAHA I'M SUCH AN IDIOT. I couldn't find the code that I was supposed to add to those lines to so I searched and searched for about five minutes reading over every word. Then I realized that I had flashed back to a stock ROM and wasn't on BrokenOut anymore. That's why I couldn't find the code lol.
 
hYpHyPuRpLe said:
BWAHAHAHAHAHA I'M SUCH AN IDIOT. I couldn't find the code that I was supposed to add to those lines to so I searched and searched for about five minutes reading over every word. Then I realized that I had flashed back to a stock ROM and wasn't on BrokenOut anymore. That's why I couldn't find the code lol.
Click to expand...

That's what happens when you steal my win >_> (longest thread thing lol) jk
Bet you got frustrated huh?
Happened to me too :P
 
Adding the two lines of code as well as the #s did in fact work for me as well, my settings in No-Frills CPU are sticking, however in the event of an unclean shutdown (like a crash or a toggled reboot into recovery), No-Frills will not apply whatever clock frequency I have set and will revert back to defaults which in this case is 384 Ghz Min and 1.782 Ghz max.

Unfortunately for me, my phone seems to crash more often than not when the max clock is set to 1.782 Ghz so my phone got stuck crashing and rebooting a few times until it finally decided to man up and work long enough for me to go into No-Frills and lower the cpu speed, I also went ahead and opened init.qcom.post_boot.sh and changed the 1800000s to:

echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

now my phone defaults to stock speed (1.188 Ghz) in the event of an "unclean shutdown" but I can still overclock my phone as far as 1.728 Ghz (anything higher will crash and reboot) using No-Frills CPU and the settings will stick.

So I would definitely recommend using 1188000 instead of 1800000 when adding the two lines as well as adding the #s to start mpdecision and start thermald and then adjusting No-Frills CPU to your desired clock speeds, hope this helps prevent some reboots. ;)
 
You must log in or register to reply here.
Back
Top Bottom