[Nexus 5 Original Android Development] show-p1984:
Bricked sets SAFE voltages for overclocked frequencies. I always set those very moderately, meaning they might be too low for your chip.

This is intentional, as it is a brick-protection for people that set a higher frequency accidentally. I can only test PVS ID 3 properly, since that is the chip I own. Increase the voltage in steps until your phone runs stable on the desired clock to properly overclock your device.

Just one question though; Are you bitmining with the N5? Why would you need to OC it? I actually downclock it most of the time because it's just too much raw power, which is largely wasted on pure Android.

There is literally no way that this could happen, but in the unlikely case it is indeed happening: Kernel version, logcat, kernel log. :)

That's a bug in KControl. I failed =( static variable declaration in a re-used function =/

Stop pirating apps :-p

There are only a few reasons for this:

1) The Play-Store lags. It isn't uncommon.

2) You illegally downloaded the app.

3) You don't have an internet connection.

4) Your router/isp/something is blocking access to the Play-Store. This will also kill all other licensed apps. (China?)

If you know for sure that none of the above are true, get me a logcat of a clean launch of KControl + the version you use (Settings) after you completely exited it. (KControl->Overflow->Quit & swipe it away from recent apps)

It's unlikely that you are the only one with this issue though.

I don't use qcom's mpdecision. This kernel replaces it with the first custom kernel hotplug solution created, my msm_mpdecision. It's been developed for over a year and gives substantially more settings than the stock binary. It's also 100% in-kernel and opensource and a lot better tuned.

Yes. This is by design. There are several reasons why you would want this behavior (and about as many against it):

+ Race to idle is shorter; The CPU needs less time for a task and therefore can go back to being idle a lot faster.

+ You have a phone with xyz Mhz, why would you only want to use yxz-abc Mhz and rarely use what you have paid for?

+ Our CPU is capable of sooo many frequency changes per second, let's use that ability to always choose the frequency that's optimal for the task

+ Smoother Gaming/ui because the CPU can react faster to new loads. (Remember: A CPU is a SERIAL processing unit)

- More battery usage

- Higher thermal implications

- After several hours of runtime the only frequencies that are notably used will be min/max (+ touchboost frequency)

Yes. My neighbors n5 reboots with anything < stock. (It's a SNAIL, PVS ID 0)

It is 10. 1 was a typo on my end.

I had screenshots of KControl in my posts with Settings for all possible scenarios, but some user reported them as "advertising" and I had to remove them.

That's interesting, I am seeing something similar in my phone as well. That means the multirom patch worsens battery life O.O

(That's the only thing changed between the versions: https://github.com/showp1984/bricked-hammerhead/compare/c4a00d0...6633714)

Log or it didn't happen. Phone works fine for me. Try to go back to bricked_hammerhead_20131212_234158_master-c4a00d0 and see if the issue persists.

Check if it isn't your UV causing this, or a < stock min frequency.

Log or it didn't happen. Phone works fine for me. Try to go back to bricked_hammerhead_20131212_234158_master-c4a00d0 and see if the issue persists.

Check if it isn't your UV causing this, or a < stock min frequency.