Samsung Begins Production of 8 Gb RAM Chips

With the release of Android 5.0, our favorite mobile operating system has become 64-bit ready. … more

CM, Micromax and OnePlus – Sales Ban Lifted

It’s less than a week since our recent in-depth analysis of the legal battle over the … more

The History of Flagships: Part I – Sony

Every OEM aspiring to conquer the mobile world undoubtedly releases its take on the so-called … more

XDA & New Relic Performance Monitoring [Sponsored]

In other posts we’ve raved about New Relic Mobile for monitoring performance of our … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] CPU cores cannot enter offline under marginal load (not the deep sleep issue)

OP Peri Noid

25th August 2014, 07:38 PM   |  #1  
OP Junior Member
Flag Warsaw
Thanks Meter: 2
21 posts
Join Date:Joined: Aug 2014
I have an SM-N9005 Galaxy Note, running original KitKat 4.4.2 (N9005XXUENC3), rooted with Towelroot, with Xposed framework. I have a problem which consists in the CPU cores not becoming offline, when the load is marginal. All the cores run then at 300Mhz, but only one of them is really used and its load is marginal (<10%). Both process manager and the console top command show almost no activity. In a "good" state (after restart, for instance), 3 cores become offline, only the 0th one keeps working at 300MHz (which is good).

I'm not talking about the deep sleep, becouse the phone enters deep sleep without any problems - it simply doesn't turn off cores. It does not happen just after a restart, but some (random) time later.

The problem is, I cannot detect, what is causing such behavior. It seems that "something" is turning off the "offline capability". I have no idea, how to check it (and what). Has anyone noticed such weird behavior. Maybe the solution is known?
5th September 2014, 06:44 PM   |  #2  
OP Junior Member
Flag Warsaw
Thanks Meter: 2
21 posts
Join Date:Joined: Aug 2014
Seems that it's mpdecission process, that causes such behavior. Killing it from the terminal fixes the problem for a while.

Wytaptalkowane na notatniku
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes