yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
this is a universal software for managing kernels right?? i am already using Kcontrol...should i be switching to Trickster MoD?

and Kcontrol shows 91% compatibility...Color control n Sound control fail..whats wrng?
[Nexus 5 Original Android Development] iwebsource:
I'm also getting only 91% when starting kcontrol up.

I'm running Slimkat 2.4 and Bricked 12-12.

Do I need to install an application to enable the Color and Sound control?
[Nexus 5 Original Android Development] jwhyte:
Bricked currently does not have color and sound control. 91% is normal.
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
thnx for clarify
[Nexus 5 Original Android Development] Phazmos:
Kcontrol has more options. Trickster is more basic, but enough options for what I want to do. Simpler also makes it a little easier to use.
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
wel thats what i need....Kcontrol is bit complicated for me..
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
is there any way that i can reset all chnages to defualt in trickster mod?
[Nexus 5 Original Android Development] Phazmos:
Swype from right side of screen and uncheck the option to start on boot. Reboot and everything will go back to defaults.
[Nexus 5 Original Android Development] Savant:
If kcontrol is hard to understand then you need to learn how to use the application because then bad things won't happen .
[Nexus 5 Original Android Development] ramd4n:
I think KControl is the best app to control kernel, although for some people is very difficult to use.
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
i meant no disrespect but even in kcontrol there is warning that ' do no use this or that feature without knowing what u r doing as sum feature can be dangerous if not used as it should' i am still learning thing... anyway thnx for the suggestion

Sent from my Nexus 5
[Nexus 5 Original Android Development] sam razzy:
How is the battery life with this kernel?? Never tried it. I'm very curious to try it out.
[Nexus 5 Original Android Development] estallings15:
Better than the rest, in my experience.
[Nexus 5 Original Android Development] Savant:
Mileage may vary.
[Nexus 5 Original Android Development] sam razzy:
I'm on this kernel and I see some screen flickering whole scrolling on Facebook and some apps. Mostly I can see on Facebook. :) I'm on 20131230 build. Which is the latest one?? I can't find any recent build..
[Nexus 5 Original Android Development] Remoteconcern:
That's the most recent. I don't have any flickering.. Did you change anything in developer options?
[Nexus 5 Original Android Development] jerrylzy:
Hi showp!

I selected 650mhz in KControl, but I found no improvement in benchmarks. So how can I check if GPU OC is activated?
[Nexus 5 Original Android Development] :
Hi,

It's normal because there is not (yet) GPU overclock in this kernel (nor in other kernels, or it's a slight overclock like 489 Mhz, I tested this kernel but I don't remember), it's just that Kcontrol displayed these GPU freqs (maybe for other devices) but they are not available for the N5.

You can verify this in:

/sys/class/kgs/kgsl-3d0/gpu_available_frequencies

And:

/sys/class/kgs/kgsl-3d0/max_gpuclk

The GPU overclock needs to be hard-coded in the kernel to make it available (in short). And due to some limitations I don't think we will see this kind of high overclock for the GPU, or at least we won't gain anything (heat, memory bandwitch or something like that, etc...).

530 or 550 Mhz (I don't remember exactly) has been tested in another kernel without any improvement...

:)
[Nexus 5 Original Android Development] jerrylzy:
There is a .ko driver in showp's kernel, which he stated to be able to overclock gpu using his app.

I have a PVS 0 device and it's very hot. you are right. I should probably lower its frequency a bit.
[Nexus 5 Original Android Development] wera750:
I mean the settings the kernel boots with. I'm new to your kernel, but loving the speed so far.
[Nexus 5 Original Android Development] show-p1984:
Mpdecisions is completely configurable, as is it's screen of single core feature. Look at the second post.

That much was obvious. I meant: clocks/mpdec/thermal/scheduler/etc...

But since you are asking vaguely: yes, it boots with recommended settings.
[Nexus 5 Original Android Development] franciscofranco:
You actually have a point up to a certain extent. There is a problem on this device, which also happened with Mako is that the suspend->resume path is being called almost every second, sometimes even more than once per second and in almost every path the disable_nonboot_cpus() and enable_nonboot_cpus() are also being called. The only way to achieve the deepest power state all cores need to be offline (but cpu0 of course) you can safely see all the other cores being made online every now and then due to that suspend->resume path being called all the time thus defeating the purpose of the deepest power state and then decreasing the battery life during idle. Removing those disable/enable_nonboot_cpus() function calls and relying on our code to do that only once per screen on/off cycle and we'll be on power collapse more often - and obviously removing the overhead of going through those enable/disable calls.
[Nexus 5 Original Android Development] jazzor:
If suspend->resume is being called every second, could this be caused by wakelocks in running apps/kernel? If the device is not waking up, why would these need to be called every second? If we use a custom cpu hotplugging solution, are you suggesting that we should also be modifying the cpu.c to no-op on disable_nonboot_cpus() and enable_nonboot_cpus() functions?

In any case, are you saying there is no way to achieve the effect where a user can have the screen turned off but still be able to have processes running using all cores until they are complete and only disable the cores just before the device suspends? I thought that was the purpose of the original "early suspend" framework was that it will notify drivers that the kernel will be suspending so finish whatever tasks you are doing.
[Nexus 5 Original Android Development] show-p1984:
Ofc it's caused by wakelocks, that's the main reason why the device would wake up :) (except irqs, which we will just ignore for the sake of this argument :p)

I have all code which messes with our cpus removed from my local sources, so far it works fine, with less idle drain. I will push it as a beta soon(tm).

Afaik the old earlysuspend/lateresume was a hacky approach to work around the messy wakelocks on upstream. Since they are fixed, it was no longer needed and got removed. Which is good.

The device is still waking up a lot more often than I would like to see, but it's an improvement over the old situation.
[Nexus 5 Original Android Development] franciscofranco:
More often than you would like to see? This thing is the wakeup bargain sale, suspend, resume, suspend, resume, suspend, resume. I don't remember seeing this on my GN - the N4 did the same, endless suspend & resume loop. Is the modem sending IRQs all the time?
[Nexus 5 Original Android Development] show-p1984:
On the Nexus 4 yes, since it didn't have a modem on soc and it was attached to an usb port, iirc. (APQ8064 was never designed for phones)

The n5 soc should have a modem inside the soc, which doesn't require as many wakeup calls.

There could be a different cause. I am currently investigating on that issue a bit further with debugging enabled and echoes added to everything that is remotely connected.

I have an idea on how we could limit the wakeup calls drastically, but I will need to find a way to trick the watchdog to stop biting me. Anybody got some fresh meat? :)

Since I was working on this I didn't have much time to work on sweep2wake, but flar2 had access to my local repos (with s2w ported) and investigative status on why the touchscreen may not be sending calls in suspend. He just wrote me a pm to tell me that he has it working in suspend and will push out that patch for a review soon(tm).

So there is that. Shared development ftw. :p

EDIT:

I just pushed my code for disabling the nonboot functions into a beta. You may test it for improved sleep functionality / battery / whatever :)

If you want to watch your CPU's doing the on/off dance (or rather not doing it anymore) put this into a script (call it whatever.sh)

#/bin/bash
for ((i=0; i<4; i++)) do
echo "CPU $i:";
adb shell cat /sys/devices/system/cpu/cpu$i/online
done

and then execute:

watch -n0.5 bash whatever.sh

Beta links:

http://bricked.de/index.php?action=kdownload&device=hammerhead&release=beta&type=aosp

Changes in the last beta with that cpu mess removed:

https://github.com/showp1984/bricked-hammerhead/compare/6528532...f6719d5
[Nexus 5 Original Android Development] franciscofranco:
Well something is derping again as it looks to me its the same resume and suspend dance as on Mako.

That touchscreen may not send calls on suspend was happening on Mako indeed - is the same happening here on Hammerhead?

On my case I'm using new PM Freezer so the enable/disable_nonboot_cpus() are not being reached - that definitely helped on idle battery life.
[Nexus 5 Original Android Development] show-p1984:
I suspected (among other things) that the touchscreen could have been tied to the lcd panel regulator, so if that reg is cut off both will die. It seems to have been this case here from what flar2 told me.

On the mako and other devices the issue is a slow wakeup, which is still kinda a mystery. I know for a fact that it's a change to the linux kernel between 3.0 and 3.1, but git bisecting that code takes time as you can't just bisect the whole branch (since you would loose all board definitions and couldn't test the kernel anymore).

Basically the touch driver is trying to receive panel information but the i2c bus is not yet ready and returning error code -16 (-EBUSY). Adding a small delay fixed that but that is ugly as hell.
[Nexus 5 Original Android Development] franciscofranco:
That makes total sense! Kudos to flar2!!!
[Nexus 5 Original Android Development] theesotericone:
The three of you have just restored my faith in XDA. Carry on.
[Nexus 5 Original Android Development] george241312:
I dont want to bother but i dont know how to make scripts.. most i can do is go in the filesystem and make changes with a text editor ... or hex edit. if your unable to help me, can you please direct me to a place i can learn how to do it ? what commands do i need to add the the init.d ? i just want to throttle only after phone has reached 93C and shutdown at 95 -97C ....
[Nexus 5 Original Android Development] bkeaver:
So curious. In the latest stable version it no longer allows me to set my first core down below default 300000 on my minimum but allows me to lower the maximum. It does however allow me to lower the other 3 core minimums to 96000. I'm pretty sure the previous version allowed me to lower the first one....

edit: reverted back to previous kernel and I was wrong. I cannot set the first core below default either.. is this by design?
[Nexus 5 Original Android Development] Striatum_bdr:
I think it's better for your phone that you don't know how to script those insane values. You have all the internet to learn the init.d scripting. Don't want to be an accomplice in this thing.
[Nexus 5 Original Android Development] retaliator:
Hello, thanks for creating and posting. Unfortunately I can't download with the link in OP. Please create a mirror or take another look at.

TIA
[Nexus 5 Original Android Development] bkeaver:
There is nothing wrong with the link in the OP.. works fine for me
[Nexus 5 Original Android Development] show-p1984:
There are a bunch of tutorials on the web and on xda. If you want an example, take a look in any of my mako kernel zips, they have 3 init.d scripts in them.

This is probably because of a faulty app. Works fine in KControl:

https://db.tt/yKXadfQ1

My website is up and running.

Download links are all working fine.

Op links are working properly as well.
[Nexus 5 Original Android Development] bkeaver:
but I am using KControl to minipulate it:confused:
[Nexus 5 Original Android Development] show-p1984:
Are you sure it's not a typical pebcak error? :D

Try again :p
[Nexus 5 Original Android Development] bkeaver:
Absolutely positive look
[Nexus 5 Original Android Development] :
Re,

Ah, in any case when I tried its kernel I never be able to use the GPU overclock, maybe something is changed but I doubt the 650 Mhz GPU freq is added, or maybe I'm wrong.

Have you check the GPU freq via the paths above to see if the module/driver do something (yes I see the module you are referring "kcontrol_gpu_msm.ko")?

:)
[Nexus 5 Original Android Development] jerrylzy:
Yes, it is there. And yes, it's that module.
[Nexus 5 Original Android Development] :
You can use this app to see if the frequencies for GPU OC are actually being applied, as far as I know GPU OC doesn't work
[Nexus 5 Original Android Development] djdarkknight96:
Can't use this on the latest CM, they must have fixed their kernel and went caf. Got stuck looping the Google logo...Soooooo no more Bricked for CM N5 users. :(
[Nexus 5 Original Android Development] cgjjaf:
Yes, I am with you, same here. I also tried another kernel with dt2w and same bootloop. Oh well, let us wait and see what happens.
[Nexus 5 Original Android Development] djdarkknight96:
Fortunately there's a commit to add dt2w to CM11 but it's not been activated yet. So there's hope already in place.
[Nexus 5 Original Android Development] P.Mobile:
well this is the only kernel i have not tested.. hows performance
[Nexus 5 Original Android Development] resynx:
Performance is really slick with this kernel, and this kernel gives me the best battery life I've gotten on my N5 :D
[Nexus 5 Original Android Development] copi:
Which build version?
[Nexus 5 Original Android Development] resynx:
Hey long time no see copi! :D And I'm on the latest 12/30 :good: Although some people are reporting they have better battery life with 12/12
[Nexus 5 Original Android Development] Phazmos:
35+k antutu, while getting 8 hr sot, or
[Nexus 5 Original Android Development] copi:
Hi ngo93,, happy to see u too, saw some familiar friends from mako in n5 forum too, glad I jump in here.. once u go nexus cant look else where hehe.

Yes I'll try 12/30 then. On d other day I've tried 12/12 but surprisingly battery drain like crazy bad, same setting to mako,, how come.. it also happen with lots of kernel like franco, faux, etc.. Turns out the printer cloud is on.. Lol, really feel silly.

Btw after tried lots of color profile, I felt like stock is the best for n5, this n5 screen is really good, far different from mako. Happy with my new nexus. So if bricked kernel doesn't contain color gamma, that is fine, and reading lots of good review in here, want to try also.

12/30 here I come,, thanks bro for the advice,, and thanks show-p for this kernel.
[Nexus 5 Original Android Development] resynx:
Yup! Always good seeing familiar faces :) and of course, Nexus always ;) Enjoy the kernel friend! I'm sure you'll love it, as we all know showp does great work :highfive:
[Nexus 5 Original Android Development] jerrylzy:
What PVS bin do you have?
[Nexus 5 Original Android Development] atomico001:
i am using it on droidkang (based on cm11) and it work.

p.s. i have a bad battery and i don't know if the problem is the kernel or the rom. android.com.systemui drain all my battery :(
[Nexus 5 Original Android Development] djdarkknight96:
CM based doesn't mean they use CM's kernel.
[Nexus 5 Original Android Development] Phazmos:
3.
[Nexus 5 Original Android Development] DarkSorcerer:
Pretty impressed with this kernel. Thank you!

Sent from my hammerhead with Tapatalk
[Nexus 5 Original Android Development] z3phyr02:
Does this kernel have bad idle drain with s2w active?
[Nexus 5 Original Android Development] resynx:
All kernels with that function active have drain. I read about 2-3% per hour for it.
[Nexus 5 Original Android Development] TheInVisibleGoD:
Just started using this kernel version 12/30 with kcontrol, but for some reason I'm only getting 52% compatibility... Any idea why?

---------- Post added at 01:01 AM ---------- Previous post was at 12:32 AM ----------

My bad... For some reason, the first time I tried to flash, it failed... Now looks ok with the same 91% as reported by others!
[Nexus 5 Original Android Development] Savant:
[MENTION=4195844]show-p1984[/MENTION] where have you been?
[Nexus 5 Original Android Development] resynx:
iirc..I believe I read that he had a family emergency a little before Christmas:( Hope everything is okay.
[Nexus 5 Original Android Development] topgeardave:
Go on [MENTION=1188493]Calkulin[/MENTION] thread in Android development to make other kernels work on cm11
[Nexus 5 Original Android Development] djdarkknight96:
Thank you sir!
[Nexus 5 Original Android Development] christiansfreeman:
This is by far my fav kernel so many custom kernel settings it's ridiculous! I'm getting 6 and a half our sot with my settings one request tho can you add gamma color control? I don't like stock colors
[Nexus 5 Original Android Development] Venomous Viper 119:
Can the nxt tweaks app included in the chaos kernel be used with this kernel?
[Nexus 5 Original Android Development] akaHardison:
The developer have fun in slimrom

And KControl is going to 2.0.So just waiting for new release.
[Nexus 5 Original Android Development] cd69:
Sounds great. Can you share your settings with noobs (for custom kernels) like me. :)

Sent from my Nexus 5
[Nexus 5 Original Android Development] fonzie444:
I noticed that after some time whit screen off, double tap don't respond. Even when I do a long call, screen dont turn on when I keep away phone from ear, so I have to press the power button. I think they are two problems related to the kernel, how can I fix them?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] omvir:
Wow! Nice man! Which build and what settings are you using in kcontrol? Mind sharing the settings :)?
[Nexus 5 Original Android Development] Phazmos:
Uv by 25, wifi, gps off, no google now. I use trickster. It had the settings I'm interested in changing, and even though I did buy kcontrol, trickster is all I really needed.

That said, get the app, just to support the dev. Haven't found a kernel that comes close to this yet, and I've tried them all.

Ps - 15 hrs up, just shy of 1 hr sot, as you can see, 89% left on battery. And of course, running the always fabulous slim rom
[Nexus 5 Original Android Development] toyface:
Hi all,

I'm looking to swap from the Linaro Franco Kernel to this, been having some problems lately with bluetooth and my Smartwatch 2. I am on stock KitKat 4.4.2, do I need to install a stock kernel then install Bricked's or can I just flash with the Franco kernel installed?

Any help greatly appreciated

Tom.
[Nexus 5 Original Android Development] jwhyte:
If Franco's uses a modified or not stock ramdisk flash stock kernel before bricked.
[Nexus 5 Original Android Development] toyface:
Thanks very much, I just wanted to check :)

Tom.
[Nexus 5 Original Android Development] ppog:
I flashed this over Franco r32, no problems that I can see.
[Nexus 5 Original Android Development] Pens and DreamS:
Is this Kernel compatible with latest cm?
[Nexus 5 Original Android Development] jwhyte:
No flash the caf update from caulklin and it should work fine

http://xdaforums.com/showthread.php?t=2626961
[Nexus 5 Original Android Development] fonzie444:
Up!
[Nexus 5 Original Android Development] Nickamina:
Since you posted this I've been UV'd by 25 too with fantastic results on Slim and codefireX. Great tip, thanks for sharing.
[Nexus 5 Original Android Development] :
should I enable ART with this kernel? or it causes problems? ^^
[Nexus 5 Original Android Development] :
Hi,

ART runtime has nothing to do with the kernel...

ART runtime is not compatible with Xposed Framework for example, for more info take a look here: Dedicated Runtime Thread (ART vs Dalvik) or here also: Switching runtime between Dalvik and ART.

:)
[Nexus 5 Original Android Development] P.Mobile:
this kerne hasent been updated in months huh?
[Nexus 5 Original Android Development] Citizen_Snips:
The developer is going through personal / family issues right now. He was nice enough to come back and update his kernel with the MultiRom kexec patch for us. Please be respectful and give him however much time he needs. You can read back in the thread if you want to know what's up...
[Nexus 5 Original Android Development] Remoteconcern:
What would you suggest changing anyway? This kernel has best performance and battery life out of all of them on XDA for me, and is stable too. So I don't know what you think should be changed :)
[Nexus 5 Original Android Development] :
how do you guys undervolt/underclock this kernel? with trickster mod? what values should I change? XD
[Nexus 5 Original Android Development] resynx:
You can use Trickster or showps KControl, any kernel tweaking app will work. I would start with a global -25 to all of the values and move slowly from there once you deem it is stable. Every phone will handle a different amount of UV :)
[Nexus 5 Original Android Development] Citizen_Snips:
I use KControl
[Nexus 5 Original Android Development] :
using trickster here ^^ you mean lowering CPU voltajes? the ones on the right or the left? or just the max min frequencies?
[Nexus 5 Original Android Development] netwokz:
Ok. I tried a while back and it didn't work out. But now that cm has moved to a caf kernel, which one of caulkins zips and in which order is everyone using to get bricked to work with cm11?

Sent from my Nexus 5
[Nexus 5 Original Android Development] samcrocr:
He's providing us a free product. Don't complain
[Nexus 5 Original Android Development] hd2009:
Is bricked discontinued ?

I think it's one of the best kernels, but it lacks of some important features like color and audio boost.

I also think that Kcontrol is a very powerful and user friendly program to control a kernel, but it' s not receiving the attention it deserves. However, one important feature it lacks is the profile loading (battery, performance) , like chaos kernel.
[Nexus 5 Original Android Development] Phazmos:
Those features may not be important to some users. This is still the best kernel - top battery - top performance - for this device.
[Nexus 5 Original Android Development] EdgA#1:
Yes, its really one of the Best Kernel!!!

and I think showp is typing on the New kcontrol 2.0 :)

Bricked - Hammerhead - SlimKat
[Nexus 5 Original Android Development] Citizen_Snips:
Give him time everybody. If he wants to come back to development, he will. He just needs some time, please respect that. Real life comes first.
[Nexus 5 Original Android Development] hd2009:
You' re wrong. The best kernel now is chaos, especially with cm roms like droidkang.

It' s true, but you need to implement them if you want people to use your software, especially when almost all of the kernels around already have that features.
[Nexus 5 Original Android Development] Phazmos:
We don't bother with cm anymore, haven't in a long time.

Chaos didn't come close to bricked, and now that it only supports caf, it never will on aosp roms.
[Nexus 5 Original Android Development] hd2009:
"We" ?

Maybe i'm missing something but i don't understand your point of view.