yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] show-p1984:
That's exactly the hack I am currently using in s2w2, but it's not more than that. A hack.

The ideal solution would be to wake up the i2c driver before the touchscreendriver wakes up.

I will pick it back to the mako in the next release.
[Nexus 4 Original Android Development] myfluxi:
The payed-app guy will use it to sell more apps, though :)
[Nexus 4 Original Android Development] show-p1984:
https://github.com/showp1984/bricked-mako/commit/f4e68589f5e4c8ad71972baf666e67107948d2a0

and

https://github.com/showp1984/bricked-mako/commit/41ac7235f277e8b4a3297441141d01bb80414a80

are in the stable currently being put together by my build bot. The first should fix your problem, whereas the second should fix hotplugged cpus not getting boosted sometimes. :)
[Nexus 4 Original Android Development] justthefacts:
I see two 05/12. One in the Beta and one in the stable. Any difference between the two?
[Nexus 4 Original Android Development] show-p1984:
why don't you use this link on the beta page:

Click me to compare master...exp on github
[Nexus 4 Original Android Development] bigeyes0x0:
I've just tested it here and it works correctly. Thanks for the quick fix, appreciate it.

Also do you mind applying this patch set http://review.cyanogenmod.org/#/c/31787/ for gamma control? I searched and saw you have worked on it before, but I dunno if you have stumbled upon this patch set.
[Nexus 4 Original Android Development] D-m-x:
Had the same Problem the first time, after a retry it did work. Kernel Settings were Stock, nothing changed.
[Nexus 4 Original Android Development] Holo_:
Not all cores are live only one core is online working causing the lag I use the kernel tuner app in the play store to turn on the other cores cpu1+2+3 small workaround to show fixes mpdecision
[Nexus 4 Original Android Development] AppReviewBros:
Has anybody tried playing games using this kernel? Do you notice smoother frame rates?

I am about to flash this kernel as I find the thermal throttling to be annoying especially when playing 3d games. Just a little scared of the phone overheating and showing the red LED light.
[Nexus 4 Original Android Development] giantflash:
Stock voltage seems very high for me. And also I don't see a reason why we can't go to 700mV. And just a suggestion: Can you maybe change the lowest frequence to 304 MHz like motley? I loved your kernel on the sensation and I'm seeing forward to this, too.
[Nexus 4 Original Android Development] ctfrommn:
It took me 2 tries. I would highly recommend using TWRP instead though.
[Nexus 4 Original Android Development] lowrider262:
lock screen is lagging a bit. running stock frequencies & settings. other than that everything's working great
[Nexus 4 Original Android Development] air2k57:
No, I am on cwm.
[Nexus 4 Original Android Development] Somairotevoli:
Those with lag, what governor are you using?

Using interactive myself with zero lag.

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] ctfrommn:
Im using ondemand and also have zero lag....something else is involved with those who are.
[Nexus 4 Original Android Development] joshnichols189:
This has happened to quite a few people that were not OCed.
[Nexus 4 Original Android Development] bruce2728:
I had a bit of lag after flashing but after letting it settle in it's been running cool and smooth all day.

Thanks for fixing the thermal limits, I was a bit worried about playing games for more than a few minutes at a time :)
[Nexus 4 Original Android Development] chrisnk204:
BRUUUUUUCE lol good to see u with a N4 any work coming soon? Loved your htc sensation work
[Nexus 4 Original Android Development] show-p1984:
Wall of quotes... :)

See below :)

Not yet.

See below.

You are 100% certain that you were running Bricked at that time? Maybe it didn't flash before and you were still on another kernel?

A log would be really important, since I am taxing my phone for 12 hours like a mad man and it never went above 71°C, it is always jumping between 64 and 71°C thanks to thermal management. (@max clock +50mv)

Just don't oc and you are peachy.

Issue experienced, identified and fixed. (at least for me and until now :))

Running multiple Benchmarks and playing GTA3 @max details without frame limiter on 1,83Ghz since 12 hours. No issue at all.

Indeed, shouldn't happen though.

on the pyramid we drive even higher voltages, with no reason to be concerned. I agree that it is soc dependent, but it is also chip dependent. Look above what I am running since 12 hours.

soon(tm).

This build is using stock voltages up to stock frequency. Use System Tuner to undervolt the frequency you feel the voltage is too high.

They are not supposed to be online all the time, mpdecision does that. If you tinker around in the core management mpdecision will detect that and pause for 10 seconds (configurable) after that it will resume normal functions.
[Nexus 4 Original Android Development] Thorsten_de:
Hi Bruce!

Nice to see you here in the Nexus 4 forum so you have got your Nexus 4 already :o

I'm lucky to I have got my Nexus 4 last week.

Now it works with CM10.1 and the Bicked-Kernel v0.5. :good:

Greetings from Germany, Thorsten!
[Nexus 4 Original Android Development] italia0101:
You know you said about running without the frame limiter on GTA ... What was the limit anyway ? Was it reaching it in the first place.
[Nexus 4 Original Android Development] show-p1984:
No idea what limit rockstar games used, all I know is this:

With frame limiter on mpdecision shuts down a few cores regularly in some situations.

With frame limiter off it doesn't (only in rare occasions) do that. Runqueue values proof that it is being taxed more.

So I naturally chose the option that taxes the phone more to test stuff. Even though I can't see the difference ^^ :p
[Nexus 4 Original Android Development] ctfrommn:
Show, any idea which "speed" chip you have? Slow, nominal, fast, or faster? Im certain this makes a difference with each persons capabilities. I though you replaced mpdecision? I must have misread.
[Nexus 4 Original Android Development] show-p1984:
cat /sys/kernel/debug/krait_variant
Your cpu uses this cpufreq table: FAST
Your krait chip variant is:
[ ] UNKNOWN
[ ] SLOW
[ ] NOMINAL
[X] FAST
[ ] FASTER

I replaced mpdecision (binary) with my in kernel mpdecision.
[Nexus 4 Original Android Development] italia0101:
Also another question , you know you changed the thermal limits... was that for the cpu temp or battery temp? or both?
[Nexus 4 Original Android Development] show-p1984:
cpu temp.

battery temp is incoming. (but not that important tbh, they usually don't get that hot and have a safety check built into them)
[Nexus 4 Original Android Development] show-p1984:
Nice to hear :)

I actually had put together my own color interface which is a hybrid between two color interfaces. So it was possible to use it with all apps out there. I will check how extensive the modification would be to merge it with that patch.
[Nexus 4 Original Android Development] myfluxi:
So you had the hack lying around for 4 months and ignored the people complaining, not giving any hints to faux or anyone? Then, after I debugged for an evening, commited the workaround, you push it retroactively?

There is no hope for the kernel scene.
[Nexus 4 Original Android Development] show-p1984:
I didn't know that faux struggled with that and I told everyone that I concentrate on s2w 2.

In fact there are a bunch of robustness checks in s2w 2, some of which would be very hard to port since they rely heavily on the new coding structure. Since you pointed out which one fixed it for the mako and this was a very simple hack it saved me hours of trial and error probing. So why shouldn't I pick that now?

I have a bunch of stuff lying around for months everybody wants. S2w for the grouper included.

I don't like the subtext of your post.
[Nexus 4 Original Android Development] myfluxi:
At least you got the message.
[Nexus 4 Original Android Development] robakrobak:
I wonder what is the highest temperature at which a processor can be operated? and what are your thermal control settings?
[Nexus 4 Original Android Development] ctfrommn:
I've had mine around 90c benchmarking without issue.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] robakrobak:
U can boil eggs on it :D However, I think it is a little too much
[Nexus 4 Original Android Development] justthefacts:
Did a chache and dalvik wipe and when I rebooted I noticed that the min freq has got stock on 918 again. Everything was behaving correctly until then.

Now it is not behaving correctly any loger. On some rebbots it holds the min value and on some reboots it will go back to 918

I'm on the latest stable.

These are the readings I get out of the phone's settings. Xenon HD

The beta gave me the same results after wiping cache/dalvik
[Nexus 4 Original Android Development] ctfrommn:
You asked what the highest operating temp was, not whether I run it that high or if I thought it was excessive :D. Mine runs in the 40-50c range if I can UV or 50-60 if I cant. Nominal chip so voltage is high.
[Nexus 4 Original Android Development] robakrobak:
today i did antutu benchmark and my phone turned off, and won't turn on. When i plugged him to charger red led shows and dissapear. After 10 min charging i turned on phone and i saw 5% battery. But when i did benchmark i had ~80% :/ dont have log files, did u know what that can be? after that phone charged from 10-80% in 30 minutes.

Sorry for my bad english
[Nexus 4 Original Android Development] jassycliq:
Happens on any kernel.
[Nexus 4 Original Android Development] show-p1984:
Bricked will never go that far up anyway. Forced shutdown from msm_thermal inside bricked will be @ 88°C.

Long before that it will throttle down to 384Mhz, and no phone will heat up anymore with that frequency. (Except if you are using your phone in a sauna or in the middle of the desert)

That happens not only if the temperature is too high (= somewhere beyond 90°C, but as explained above: With the stock bricked settings that will most likely not have been the cause) but also if the voltages are too low or another oc related hardware crap out occurred. Usually that is nothing to be afraid of. If you push your device to the limit it might push back. :)

The thing to learn about this: Whatever you did to your phone prior to that, it didn't like it. Don't do things to your device it does not like.
[Nexus 4 Original Android Development] robakrobak:
I understand but it is strange because that happend close to start bench so tenperature was about 60c. I hope with my battery is everything ok. I have one more question, is it normal that i have about 17min wake lock msm_hsic_host on 3,5h on battery?. I am new here and i saw some post about that wakelock but there is still no fix for that?

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] show-p1984:
Semi-normal. The s4 pro is a special case, as it was never meant for phones. Only once manufacturers started to put it into phones qualcomm attached a modem to it in a hurry. (There is a bunch of info about this in this thread)

If you get the red led regularly there might be something wrong with your phone. [MENTION=3424800]jassycliq[/MENTION]'s answer isn't correct. This does not happen on all kernels. I never, ever, had a red led on my phone since I am on bricked. And I am stress testing this phone regularly while overclocked (1.7Ghz). (it happened during benchmarks on stock kernel and the phone was hot)

By the way: depending on surrounding temperature and initial heat the soc can indeed increase it's temperature by 20-25 degrees in a matter of seconds while really stressed. That's why you should never, ever disable the thermal guard on this phone.
[Nexus 4 Original Android Development] jassycliq:
I have had that issue on any kernel though. I live in SoCal and currently its around 90°F outside. If I try to bench the N4, even at 1.5ghz it'll most likely RLOD. That's why I stopped benching. I should've been more thorough in my answer, explaining the circumstances and personal experience.
[Nexus 4 Original Android Development] show-p1984:
Slow/nom/fast/faster?
[Nexus 4 Original Android Development] ctfrommn:
Ouch....Ive never had a RLOD benchmarking at 1512....1782 & 1836 is a different story though. Mines nominal so it does run hot, but I think RLOD is caused by bad battery connections susceptible to extreme heat.
[Nexus 4 Original Android Development] jassycliq:
Fast. Right now my phone was left untouched and its at 60C. Sunlight isn't nice around here right now :(
[Nexus 4 Original Android Development] show-p1984:
Well bench-marking in direct sunlight isn't really smart :)

try to lower all thermal restraints (except shutdown) by 10°C.

If it fixes that: don't benchmark your phone in the sun.
[Nexus 4 Original Android Development] jassycliq:
Lol id rather not benchmark at all haha

Was just sharing real life experience. :D
[Nexus 4 Original Android Development] 8 -Ƀɪד_Įƞƒɨɖɘɭ:
Hey,

I love this Kernel it was stale and faster than others on PA3.15. However at work my device crashed and I was unable to get it going,

so I restarted the device via the power button and when I booted into Android I had no touch screen function, so I had to restore my device.

I want to re-flash it, but i'm unsure if this is a common problem or a result of me flashing?

I had 3 Kernels installed before this, could this cause it?

Thanks and great work btw.
[Nexus 4 Original Android Development] show-p1984:
How did it crash? Log?

If you had no touch function after reboot it may very well have been sweep2wake. Try it without it.

To your 3 kernels question: Depends on the kernels you used, if they modified your system heavily then yes. (There are some kernels hex patching files out there)
[Nexus 4 Original Android Development] 8 -Ƀɪד_Įƞƒɨɖɘɭ:
Thanks for the reply,

I'll give it another shot, from stock Kernel.

It did get every hot, I was only browsing Gmail when it happened and the heat on the back was getting scary.

Sorry I didn't get a log, I can try and recreate it if you want, to force the same/Similar error or bug. Just ask, happy to help!

Thanks for the help.
[Nexus 4 Original Android Development] Mo'HAWK:
Can anyone explain the mp decision settings to me? Like what each one does or should I disable it.

Edit: nvm in op......
[Nexus 4 Original Android Development] wera750:
Does faux display work with this kernel?
[Nexus 4 Original Android Development] wera750:
I killed the thread lol
[Nexus 4 Original Android Development] Emilius:
he he it's look like but don't get wrong impression, this is a killer kernel. why don't you give a shot and try it together with faux display. personally I like the colors just the way how it is.
[Nexus 4 Original Android Development] wera750:
I'm really digging the preset colors in faux display but I used to love this kernel
[Nexus 4 Original Android Development] XxVcVxX:
So how do I flash back to another kernel, I rename the thermal and mpdecision files first? Or flash the boot.img?
[Nexus 4 Original Android Development] jarjar124:
Reflash rom then kernel
[Nexus 4 Original Android Development] Emilius:
So quiet around here but I can smell KControl :D
[Nexus 4 Original Android Development] 3c:
Indeed too quite :D What's KControl?

I'm working on adding support for your kernel (msm thermal and mpdecision) should be available in a few days. Wanted to ask you if you will change the msm mpdecision interface in the future? I've already implemented support for v1 and v2, but if it will change, I'd like to add support for v3 now ;)

Nice kernel by the way, running smooth on my N4 :D

---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------

Don't think you actually need to reflash ROM, old thermal and mpdecision are left untouch by this kernel and not used. However where is the mpdecision config file? Coudln't find it!?
[Nexus 4 Original Android Development] jassycliq:
Kcontrol is the app showp is making.

Sort of on reflashing of ROM. Showp renames both mpdecision and thermal. None of the other kernels will rename them, so unless you do it manually, reflash ROM is the other way.

There is no mpdecision config file. There is a directory with the sysfs interfaces.

Its under

/sys/kernel/msm_mpdecision/conf/

You'll find everything there. Then if you need the 3phase thermal directory its at

/sys/kernel/msm_thermal/conf
[Nexus 4 Original Android Development] 3c:
Thanks for the info.

However on other kernels is there a mpdecision config file? I know the thermal config under /system/etc/thermald.conf, but nothing similar for mpdecision? I figured mpdecision has no config file originally?
[Nexus 4 Original Android Development] jassycliq:
The directories I posted have the config files. Proof in pics :P
[Nexus 4 Original Android Development] 3c:
No need for proof, I'm fully aware of those directories for which I implemented support in my app already.

I'm asking about the default config files, that should be renamed if switching back to other kernels. One is /system/etc/thermald.conf, but can't find the one for mpdecision.

By the way when I installed Bricked kernel, the thermald.conf file didn't get renamed.
[Nexus 4 Original Android Development] jassycliq:
Oh OK, sorry didn't understand the original question then. No, those are binaries so they'll be in

/system/bin/mpdecision
/system/bin/thermal
[Nexus 4 Original Android Development] 3c:
The binaries are the code to handle thermal and mpdecision, however thermal is based on a config file in /system/etc/thermald.conf, but I'm confused about mpdecision as it was mention in previous posts to rename both config file!?

Here are screenshots of the conf file and sysfs interfaces, I'm running Bricked kernel at the moment, the conf file is still there but unused.

What about a mpdecision config file? Any ideas?
[Nexus 4 Original Android Development] jassycliq:
As far as I know showp only renames the binaries. The thermal conf can be left alone because his 3phase thermal doesn't use it. And about Qualcomm's mpdecision, I don't believe there is a conf file for it.

I hope I understood correctly this time ._.
[Nexus 4 Original Android Development] 3c:
Ah sorry! my bad, got it all wrong ;) Binaries I understand, so they don't run and mess with kernel controls :D
[Nexus 4 Original Android Development] show-p1984:
My Kernel Control app :)

I don't see it changing much in the future. There might be a time where I will just hide unused hotplug files based on number of CPU cores available, but I don't see that happen anytime soon since they do not do any harm.

Thanks :)

There is none for the stock binary mpdecision. There are command parameters for it in the ramdisk though.
[Nexus 4 Original Android Development] Emilius:
Dennis, before you finish KControl maybe you should take a look new GDrive and Gmail apps. Seems like Google is making new standard for android apps. New GDrive looks awesome. Maybe you should follow and apply that same look to your KControl app. Just a suggestion...
[Nexus 4 Original Android Development] masterchif92:
There isn't gamma control on your kernel?

Sent by my pure Nexus 4 using tapatalk 4
[Nexus 4 Original Android Development] jassycliq:
No gamma. He's working on a hybrid version.
[Nexus 4 Original Android Development] masterchif92:
Thx but is already include or not?

Sent by my pure Nexus 4 using tapatalk 4
[Nexus 4 Original Android Development] jassycliq:
No.
[Nexus 4 Original Android Development] guru_shastri:
is there sound control in this?
[Nexus 4 Original Android Development] show-p1984:
Someone else already wrote me an email with that suggestion, as I am going to write him:

I don't like swipe-from-the-edge-of-the-screen gestures to open a menu. I hated it in ubuntu touch and I still hate it in the new Google Drive (which I luckily don't even use).

Additionally to not-liking-it, it also would not work with my current setup. I have 2 levels of fragments in KControl, adding this option would need me to move everything into one giant activity which has a few fragments and therefore include 3 levels of fragments. That is simply not possible without very very very much headaches. As it stands I already had to extend the fragment classes to amend fragment within fragment (2 lvl) functionality (eg: the mpdecision tab will make use of that)

There is also the issue of resource management. If you use multiple activities in an app Android will only load and keep stuff in memory of the activities you are using, once an activity is destroyed it's resources are freed. Using one giant activity would not allow this.

E.g.: You are only opening the cpu graph to look at it and press home.

Currently: only that one activity (+ the MainMenu with all the buttons) will be active, which is a fairly small footprint.

Using the sidebar layout everything would have been instantiated and set-up and it would need to keep running in memory. (rather large footprint)

That is bad. It surely works for something as simple as Drive, or Gmail, whose settings are only 1 level deep. You switch to an option and that's it. Beneath every button in KControl hides a new activity which adds a layer with sometimes 4 additional depth steps, and 5 of the activities use update threads to keep the interface updated (which Drive does not need to care about).

There is also the issue that there doesn't seem to be a reliable way to determine which fragment the user is currently looking at. I can grep when they are first initialized, but not when a fragment is already initialized and the user just returns back to that. That missing functionality is the main reason why I can't just switch to the new layout. I wouldn't care very much about 1-2 Mb more RAM usage, but the inability to stop and restart the update threads when they are needed would need them running constantly. Which is a no-go. (Gpu: 100ms intervals, cpu: 1sec - high load - reused for graph without the usage calculation which lowers the load considerably, thermal: 1sec, mpdec: 500ms)

[/WallOfText]

Asked multiple times already, KControl will amend this soon(tm)
[Nexus 4 Original Android Development] tlf55:
What setting do i have to put on Mp-decision value to do that Core 3 and 4 are VERY hard to enable, and VERY easy to disable ?

So i want to core 3 and 4 to disable as fast as it can !

and enabling it very low in time and very hard ..

what do i have to change in these config ?

my value value are

runqueue thresholds

Hotplug_cpu1 12

unplug cpu0 0

hotplugcpu2 20

unplug cpu1 7

gotplug cpu3 25

unplug cpu2 10

hotplug cpu4 0

unplug cpu3 18

And temps in ms

hotplugcpu1 140

unplugcpu0 0

hotplugcpu2 140

unplugcpu1 190

hotplugcpu3 140

unplugcpu2 190

hotplugcpu4 0

unplugcpu3 190
[Nexus 4 Original Android Development] show-p1984:
Higher runqueue hotplug values will let the cpu jump in later. (if runqueue > value => plug in another cpu)

Higher runqueue unplug values will let the cpu be disabled sooner. (if runqueue < value => unplug the slowest cpu)

The times are more like a delay. If the cpu was hotplugged in the last XXXms, no action is being taken. (The defaults are set very low, lowering them further is not recommended as unexpected behavior might occur. e.g.: Unplugging a cpu that is currently being hotplugged, or the more likely scenario hotplugging a cpu that is currently being unplugged, since unplugging takes slightly longer)

I suggest you experiment with those values a bit.

Btw if you want to disable cores 3 & 4 all together, just set max_cpus to 2. (sorta transforms your mako into a dual core)
[Nexus 4 Original Android Development] tlf55:
Oh thanks ! last question is it possible to have 2core boost on touch ? a bit like Mpdecision (qualcomm) but at lower freq ?

I put boost fuction on but it seems it only work core per core ..
[Nexus 4 Original Android Development] show-p1984:
Only online cores will be boosted. However if you want to disable boosting for cores 3&4 just set the boost freq of those to your current min freq.