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

Root A Test For Anyone Experiencing Random Reboots in BrokenOut ROM

KA24DERACER

Well-Known Member
Hello all. I would like to offer my insights to the random rebooting problem that some people have been having on BrokenOut ROM.

Now when I first installed BrokenOut I had the "factory" No Frills CPU, the LG Connect Optimizer and I had just bought RomToolbox Pro as it had a LOT of features I liked in one very well programmed app. And at first I did have a couple of random reboots (about three or four with one of them being my fault). After thinking about it for a while I noticed that MANY of the functions of these three apps and a couple more were the same. So I uninstalled all of the conflicting apps leaving just RomToolbox. After I did that I had no more random reboots.

If you are having troubles with random reboots I would suggest trying to find ALL of the apps that have similar or identical functions and try and consolidating them. Not only will you save RAM and running processes, but Im pretty sure it will DRASTICALLY improve your stability. I would appreciate anyone who tries this and has it work for them to post so I can see if my theory is correct. Hope this helps someone.
 
The issue with random reboots in Broken Out is mainly due to overclocking. There really is no need to delete any apps that came with the ROM. All you have to do is edit the init.qcom.post_boot.sh file found inside the /system/etc directory. You then add the following lines:

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

under the lines:

Code:
    echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
	 echo 384000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

to prevent the CPU from needlessly overclocking. By default, the maximum clockspeed of the CPU in Broken Out is 1.5GHz which is more than what the processor was built to handle, considering its capacity is 1.2GHz. Like I have stated a few times in the past, overclocking is only meant for phones that have a really low clockspeed for the sole purpose of improving performance. Otherwise, it is completely useless to do so.

:)

**NOTE** I take no credit for the information given in this post. All credit goes to Dracconus for providing this same exact information in This thread.
 
Theres plenty of people getting random reboots with little to no overclock. Besides, 1.8 isnt even overclocking, thats what the chipset was designed for it was just underclocked in this phone.
 
DieandGo there's another step to that alteration. ;) otherwise the clock speeds will still revert.

And he is not wrong either. If you have more than one app trying to set the clock speed it WILL reboot, as they will conflict.

This will happen with just 2 apps performing this function, and certainly 3. So.. you actually do need to get rid of no frills CPU if you want to use rom toolbox or the optimizer app to set the clock speeds, or you will have reboots, like it or not.

I wouldn't as easily dismiss what the OP thinks. He's actually right. Some people may be rebooting because of this, and for those that are rebooting but are only using 1 app to set speeds.. different problem. Most likely they are overclocked too high like you said. My phone reboots @ 1.8 ghz, but can handle anything under it.


Edit: Jinx
 
Theres plenty of people getting random reboots with little to no overclock. Besides, 1.8 isnt even overclocking, thats what the chipset was designed for it was just underclocked in this phone.

I did say in most cases. Lol

I didn't know the processor was actually build to handle 1.8. o.O You have evidence?

----------------------------------

Anyways, what I listed above worked for me. After switching the max clockspeed to 1188MHz, the reboots stopped. Slightly overclocking doesn't make the phobe reboot (Only in very rare ocassions) Basically, the more you overclock, the more frequent reboots become. I have even heard of people being unable to successfully boot when at 1.8GHz or not being able to keep the phone on long enough after booting to change the clockspeed back to a tolerable speed by the processor.


**Edit** And true, its a bad idea to have more than one app controlling your CPU's speed. I did say there was no need to delete any BrokenOut stock apps since No Frills CPU comes as the only app for CPY management, but if you want to use another app (e.g. ROM Toolbox), you need to delete No Frills.
 
I've got mine set at 1.026ghz and it's rebooting anywhere from 4-10 times a day, the more apps I open the more frequently it reboots! I just dumped all my conflicting apps this morning so I guess I'll see if that helps.... Haven't used my phone enough today to say if it's helped any, hoping it does... I'll post a yay or nay in a day or two...
 
Everytime your phone boots, your clockspeed will be reset to 1.5GHz thanks to the file I mentioned in my first post.You will have to edit it to mantain the clockspeed you desire to be its max. My recommendation is 1188MHz. Also, make sure you only have one app controlling your CPU like chiweN mentioned.
 
Everytime your phone boots, your clockspeed will be reset to 1.5GHz thanks to the file I mentioned in my first post.You will have to edit it to mantain the clockspeed you desire to be its max. My recommendation is 1188MHz. Also, make sure you only have one app controlling your CPU like chiweN mentioned.

Also, when altering that file you should add pound (#) signs to:
Start Mpdecision
Start Thermald

So it looks like :
#Start Mpdecision
#Start Thermald

This is also done in the post boot file DieandGo was talking about. Some people were still having issues with the clock speeds reverting even after the alteration DieandGo mentioned was done (including me lol). Both alterations are necessary.

EDIT: if you don't want to do these changes, you could delete the file itself. Many of us have with no consequences, and your CPU settings will then stick.
 
EDIT: if you don't want to do these changes, you could delete the file itself. Many of us have with no consequences, and your CPU settings will then stick.

Actually, upon deleting the file, the clockspeed will eventually change back to 1.5GHz after every boot or reboot. At least, that is what happened to me when I deleted it. :p So I restored the file from the ROM's flashable zip. I recommend editing it than deleting it as for, as the name of the file suggests, it applies settings upon booting. There most be another file somewhere putting the clockspeed up to 1.5GHz, but editing the file ultimately corrects this.

----------------------------

Btw, name's Diego. ;) hence my ID being xDIEandGOx. My name is made up of two verbs in the English language, so I wanted to be a smartass about it. xD
 
There is a thread somewhere on this forum that has a link that says exactly what KIND of processor this phone has. And if you look up the processor on Qualcoms website youll see that it is a dual core 1.8 1024 RAM with a 400Mhz video processor. Theres like literally 10 newer phones that all use some iteration of this processor (theres 4 versions and they all are about the same except one has a max clock of like 1.0Ghz and the rest have different video card speeds). Its the same processor that the Droid Razr and a whole bunch of others have. Im pretty sure that the only reason LG turned down the clock speeds was for battery life since the phone and therefore the battery are so small. Plus theres no real reason to be anywhere past 1.5, hell even 1.2 is faster than you need for just about anything.

And nothing but deleting the file worked for me. CPU profiles didnt stick, and editing the file didnt do anything either. Only deleting it let me set the speed and have profiles stick.

EDIT: And the main reason I mentioned this, other than the fact that it worked for me, is that I know ALOT of people use LG Connect optimizer (which is a good app), BUT that app does MANY things that other programs do, like setting the scheduler and compiler and alot of build.prop tweaks. When I looked more in depth at it after I installed BrokenOut (especially since BrokenOut includes ALOT of things that the Optimizer does) there were just too many conflicts between apps for me to want to keep it running, and I never had a random reboot after that.
 
There is a thread somewhere on this forum that has a link that says exactly what KIND of processor this phone has.


Quote: "In case you haven't been following, MSM8x60 is Qualcomm's first dual-core SoC. It's two Scorpion cores, an Adreno 220 GPU, and cellular modem all built on the 45 nm process. Like the rest of Qualcomm's lineup, the x in MSM8x60 can either be a 2, denoting GSM, UMTS, and HSPA+ support, or a 6, denoting all the same thing but with CDMA2000 and EVDO. Similarly, 9 will connote LTE support when we get to that point as well. MSM8x60 comes clocked at either 1.2 GHz or a higher 1.5 GHz. The MDP we were given was the higher 1.5 GHz variant. The MSM8x60 is the successor to MSM8x55, which is single core 1 GHz Snapdragon and Adreno205,also built on 45 nm process. "


Here's the link..... AnandTech - Dual Core Snapdragon GPU Performance Explored - 1.5 GHz MSM8660 and Adreno 220 Benchmarks

Here's another link ..........LG Connect 4G Review (MetroPCS) | Boy Meets Phone
 
Thank you Ohbaby. There was another one that linked to the Qualcom website that showed all the different iterations of the chipset that this phone uses (there are four of them).

Here it is

https://developer.qualcomm.com/discover/chipsets-and-modems/snapdragon

We have the Snapdragon S4plus (with the adreno 220 its the second one)

Up to 1.7Ghz dual core and ours has the adreno 220. Unfortunately even though our chipset comes with UP TO the adreno 305, ours does not : ( , but its good enough so oh well
 
We don't have the S4 Snapdragon. We have the S3. According to the second link I posted.



Quote: "Like I said, this is MetroPCS’s first dual-core phone. LG decided to go with a Qualcomm Snapdragon SoC for this one. More specifically the Snapdragon S3 MSM8660 chipset. It features a Scorpion CPU clocked at 1.2GHz and a Adreno 220 GPU. This is the same one found in the HTC Rezound, LG Lucid, and HTC EVO 3D. For RAM the LG Connect 4G packs 1GB."

Also in your link, you could download the spec sheet for the different cpu's and see our processor there.
 
The issue with random reboots in Broken Out is mainly due to overclocking. There really is no need to delete any apps that came with the ROM. All you have to do is edit the init.qcom.post_boot.sh file found inside the /system/etc directory. You then add the following lines:

Code:
   echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
   echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
under the lines:

Code:
    echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
     echo 384000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
to prevent the CPU from needlessly overclocking. By default, the maximum clockspeed of the CPU in Broken Out is 1.5GHz which is more than what the processor was built to handle, considering its capacity is 1.2GHz. Like I have stated a few times in the past, overclocking is only meant for phones that have a really low clockspeed for the sole purpose of improving performance. Otherwise, it is completely useless to do so.

:)

**NOTE** I take no credit for the information given in this post. All credit goes to Dracconus for providing this same exact information in This thread.
technically those lines can be removed all together. And yes 1.5 is more than the 1.2 stock setting, but doesnt mean it was all it was meant to handle, just a safe avg across the lot.
 
technically those lines can be removed all together. And yes 1.5 is more than the 1.2 stock setting, but doesnt mean it was all it was meant to handle, just a safe avg across the lot.

Well, it may be able to handle a bit more than what it was build for, but in the long run, it will only cause problems. The eventual reboots is a clear sign of that, especially since they seem to be more frequent when the max clockspeed is raised over the stock limit.

At 1.2, it works perfectly fine with no issues whatsoever. It may be able to work fine for a couple more MHz, but 1.5 causes reboots from time to time.

When I said that the processor was only build to handle 1.2, I meant that it was able to handle that speed without issues. Lol

**Edit** Oh, and if those lines are removed, then the clockspeed will be reset back to 1.5GHz, thus triggering the reboots from time to time. I tried deleting it already.
 
Here's my experience with random reboots. It only happened when I'm using or opening an app that caches to sd card. So I turned off all sd card caching. Futhemore, it only happened after I upgraded my sd card from class 2 to a class 10. Either go with a class two or turn off all your apps to sd or sd caching. I've had zero reboots sinced.
 
Stock. 1.5 on broken out and 1.2 on zva. I switch from rom to rom just out of boredom and disabling cache to sd fixed reboots on both.
 
So no frills cpu is an app that came with the rom and you uninstalled it? Did you have any other problems with your connect after the rom? Did your battery life decrease after the rom?


I got rid of no frills in favor of rom toolbox.

I take steps to save battery like turning off 4g and whatnot, underclock to 810 (said 7something but I remembered I put it at 810 for some reason ) with smartass governor etc so battery exceeds stock.
 
I got rid of no frills in favor of rom toolbox.

I take steps to save battery like turning off 4g and whatnot, underclock to 810 (said 7something but I remembered I put it at 810 for some reason ) with smartass governor etc so battery exceeds stock.


Hey bro what schedule setting in the kernel settings in Rom toolbox do u use and which one do u think works the best cause I have tried them all and don't notice much of a difference between them. Thx
 
Back
Top Bottom