Recent content by Netrunner157

Installed a SSH server and used Linux's grep command to find all instances of the 787 string. Besides 787 appearing randomly in binaries, pictures I found it exists in a shell script in /system/etc/init.qcom.post_boot.sh. Well what do you know: [email protected]:/system/etc # grep...

Is 787 hardcoded somewhere in this rom that it's usually defaulted to?

what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?

So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?

Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.

Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.

OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it...

Oh man I did not know how to use google. You opened my eyes. /s > kernel adiutor kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?

> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible. How do I do this? > Mpdecision.. Qualcomm closed source. Hate it. Is this a tool that fixes this? So many people have upgraded to Lollipop and yet how is it that I'm...

So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings. Here...

yes. Otherwise there's no order to getting these replies for the bootloader. How is it I can get my code within 5 minutes, and other users are waiting weeks? Do their bootloader requests not come in order? Is the request queue more like a lottery pool? It's automated.

wtf? I sent mine everyday for 2 weeks right as soon as I come home from work, around 4:40. I'm certain because I the phone sat on my desk unused for 2 weeks, and because of the bootloader system wipe, there was no point using it. Earlier I tried the Root guide on this subforum, which had a...

No, it's email so everything is already in text form, no need for OCR. You could do it yourself using outlooks email filter and a batch script for the rest. It's definitely automated.

Just wanted to throw this in here since no one else has mentioned it. When requesting the unlock code for your bootloader make sure your S/N is 16 digits not 12. Grab it from the back of the phone on the battery label, not from the system or whatever. I spent 2 weeks waiting for my unlock code...

make a backup of your current rom before you try the following: 1) reset the app data for your launcher and redo it 2) try a factory reset.