yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Sayan1987:
It's fine it's fine, just strange that 90% of kernels works good with trickster and just bricked is so "unique"..
[Nexus 5 Original Android Development] Remoteconcern:
Any kernel with mpdecision or an input boost (like this) will display incorrectly with Trickster. It reads the minimum frequency at the time that part of the app is opened.
[Nexus 5 Original Android Development] estallings15:
I'm glad someone has a brain. Thank you.
[Nexus 5 Original Android Development] gpvecchi:
I know how MPdecision works. But if Trickster is set to 960mhz, frequency never drops below that frequency!
[Nexus 5 Original Android Development] :
If you know how mpdecision works why are you still asking dumb questions? Check device status in trickster, it scales normally
[Nexus 5 Original Android Development] Brad331:
Here's my advanced GPU configuration. Am I using the power levels correctly? The default positions of the power level sliders are ambiguous and weird.

Also, those GPU settings get restored after reboot, even though I've turned on apply everything on reboot. :confused:

---------- Post added at 12:56 PM ---------- Previous post was at 12:46 PM ----------

Yep! Very unique. Without the quotes. No problems with KControl though, it handles Bricked's mpdecision much better (duh since same dev). I left mpdecision on (for plugging CPU cores) but input/touch even boost off - because I don't like it messing with the frequency scale all the time.
[Nexus 5 Original Android Development] gpvecchi:
That's the point: NO! It doesn't scale!
[Nexus 5 Original Android Development] Phazmos:
Try flashing the kernel again, then latest su.

I had the same thing happening, but now it's holding 300 and it is scaling down as it should.

This is on the latest slimkat
[Nexus 5 Original Android Development] HTCore:
Kexec-hardboot patch

Would you please merge Kexec-hardboot patch to your kernel to support the new MultiROM v19 mod?

I really cannot imagine use another kernel except Bricked Kernel right now.

Kexec-hardboot patch: http://xdaforums.com/showthread.php?p=48508549

MultiROM v19: http://xdaforums.com/showthread.php?t=2571011
[Nexus 5 Original Android Development] iamhacked:
So does this have faux sound yet? Or is faux sound still broken
[Nexus 5 Original Android Development] DevShaft:
Is it listed in the features list in the first post? Go have a look and you will find your answer.
[Nexus 5 Original Android Development] bud77:
[MENTION=4195844]show-p1984[/MENTION] : Any statement about Kexec-hardboot patch ?
[Nexus 5 Original Android Development] desmoloch:
HM i get strange wakelocks with stable 1212 version.

What are those event wakelocks?
[Nexus 5 Original Android Development] helloworld1:
Have the same problem. it's caused by s2w code. Even if s2w is disabled, sometimes, the wakelock is leaked.
[Nexus 5 Original Android Development] desmoloch:
Woops i forgot i enabled s2w a few days ago. Thank you!

That explains my massive battery drain :)
[Nexus 5 Original Android Development] helloworld1:
Disabling s2w resolves battery drain issue but may not resolve the wakelock issue. I disabled it but sometimes event wakelock show up and takes hours of wakelock. I think this is but in s2w code.
[Nexus 5 Original Android Development] lomniom:
Are you sure the wakelocks are not caused by other apps? Battery saver, or alarms apps for example? It might sound strange, but some of them are indeed provoking wakelocks?
[Nexus 5 Original Android Development] desmoloch:
Here are my wakelocks with s2w disabled. The only change i did, no APP installed or removed. Wakelock is still there, but only a few seconds
[Nexus 5 Original Android Development] fix-this!:
Will this kernel work on non cm based roms?
[Nexus 5 Original Android Development] KingDani1997:
Yes
[Nexus 5 Original Android Development] helloworld1:
No, this is not the user space wake lock. Rebooting will resolve the problem for a day or two and it comes back. event* wakelock takes hours of wakelock instead of seconds. I recompiled kernel with s2w not compiled, things are fine now.
[Nexus 5 Original Android Development] akaHardison:
Hello,showp,I am using stable version and it works fine right now.But your kernel doesn't have kexec-hardboot patch which is multirom need.So please add this patch in your kernel.It will be useful.Thx
[Nexus 5 Original Android Development] jac10000:
Give he the time to make it. It's sure that he will make it ;)
[Nexus 5 Original Android Development] george241312:
After latest stable performance has gone down and touch sensitivity as well double tap works when it wants too now.
[Nexus 5 Original Android Development] Phazmos:
No problem here.

Still [MENTION=682170]350[/MENTION]00 in antutu
[Nexus 5 Original Android Development] deadpedal:
Same here. I have not lost any performance since update.
[Nexus 5 Original Android Development] HTCore:
I don't have any of those issues you have, I am using this kernel in two devices.
[Nexus 5 Original Android Development] sumanth08:
Hey, wonderful kernel. I'm having a small issue with dt2w, can u add pocket protection because my mobile is accidently getting wake in pocket and causing some issues. I really like dt2w feature and if this is implemented that would be awesome.
[Nexus 5 Original Android Development] terodeg:
very high CPU usage in stand bye

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Remoteconcern:
S2w/d2w enabled? That causes high drain. Otherwise the kernel has very good idle drain.
[Nexus 5 Original Android Development] Phazmos:
Look back a few pages. You'll see what up
[Nexus 5 Original Android Development] prstorero:
So after reading the last few pages I see a lot of battery drain issues resulting from the use of S2W and DT2W. I use these features on my Nexus 7 and have never had a single battery drain issue. Has there been any thought of looking at the source of (i believe) flar2's builds? I run his kernels all the time without issues from sweep features. If this was already done, i wonder if maybe it's something more unique to the N5 that causes the features to have more negative effects on battery.
[Nexus 5 Original Android Development] Remoteconcern:
Yes, it's specific (but not unique) to the N5. Showp has said that either as a cost cutting measure or just because the necessary documentation isn't available, he's not able to make the screen sleep but keep the digitiser active. Instead, the screen is kept powered up causing severe drain.

Won't be changed in all likelihood.
[Nexus 5 Original Android Development] prstorero:
Dang that's a bummer. It's a very nice thing to have instead of always reaching for the power button lol.

prshosting.org
[Nexus 5 Original Android Development] gpvecchi:
As I don't use s2w and dt2tw, is there a way to remove the 2 modules? Thanks
[Nexus 5 Original Android Development] prstorero:
In /sys/module/ there are folders for sweep and double tap, but I'm not sure if the file inside is the module or not.

prshosting.org
[Nexus 5 Original Android Development] Nickamina:
Hey [MENTION=4195844]show-p1984[/MENTION] do you have any plans to include the FIOPS scheduler? If not, why? What are your thoughts on it? Cheers
[Nexus 5 Original Android Development] maaaaars:
Sorry but I still don't understand one thing: for a better battery life is better or not to activate mpdecision?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Remoteconcern:
Leave mpdecision activated.
[Nexus 5 Original Android Development] gpvecchi:
Problem here: sometimes my signal bars becomes empty (empty, not greyed out) and I have no signal; I have to reboot.

It happens around once a day...
[Nexus 5 Original Android Development] Phazmos:
Highly unlikely it's the kernel.

No problem here, and nothing from other users about this.
[Nexus 5 Original Android Development] jwhyte:
What service provider? I have that happen every now and again T-Mobile USA toggle from LTE to 2g3g fixes it.
[Nexus 5 Original Android Development] FlyinGrub:
+1
[Nexus 5 Original Android Development] rancur3p1c:
wow, why have I not thought of this? brilliant showp strikes again
[Nexus 5 Original Android Development] parkson:
Some users have posted the same issue(s) in the N5 radio thread. Try rolling back to the KRT16M radio, assuming you are on KOT49E
[Nexus 5 Original Android Development] Red5:
With the kernel tuner apps I have, this kernel seems to have the minimum frequency locked at 960 and won't change if I apply it at 300 or 192.
[Nexus 5 Original Android Development] prstorero:
I guess it's not just me haha. I just found out earlier when BBS said the lowest was 960 even though I had set 192. Battery life still seems very good, though.

Edit: setting it to 192 again and rebooting got it unstuck :)

prshosting.org
[Nexus 5 Original Android Development] rancur3p1c:
hey showp. some feedback and test on dt2w.

I'm running faux123's m005 kernel which has your dt2w.

https://github.com/faux123/Nexus_5/blob/kk_mr1/drivers/input/touchscreen/doubletap2wake.c

Specifically, there needs to be a timer for the state machine between 2 taps of the screen, from touch_nr == 1 and touch_nr > 1. The DT2W_TIME is good for the down-up nature of a tap but we need same for between tap-tap. This will help immensely with rogue detections as happens in peoples' pocket.
[Nexus 5 Original Android Development] Red5:
What did you use to set it to 192?
[Nexus 5 Original Android Development] :
Google mpdecision, it's how this kernel works, and it's not a bug
[Nexus 5 Original Android Development] Red5:
I know what it does. Doesn't explain why the kernel is stuck at a minimum of 960 even after trying to set it lower.
[Nexus 5 Original Android Development] :
So you know what it does it ramps up on touch and the kernel control apps check frequency when you open the app (it will ramp up on touching the icon/screen), which is 960MHz try changing the boost frequency to 1036MHz or anything, close the app and open again and look at what it displays. Its the same thing on stock kernel, kernel apps display the touch boost frequency as the lowest frequency but it scales down normally. If you set 192MHz/96MHz it will scale to that when not touching the screen.
[Nexus 5 Original Android Development] FlyinGrub:
if you want to apply min freq correctly and play as you want with this kernel you will need Kcontrol ;)
[Nexus 5 Original Android Development] gpvecchi:
Thanks, it could be, I'm on latest modem and Vodafone Italy...
[Nexus 5 Original Android Development] prstorero:
As flyingrub said, kcontrol :)

prshosting.org
[Nexus 5 Original Android Development] stokholm:
I want to flash this kernel, but I have some questions first. This is my first time flashing a kernel.

1) I only want sweep2wake and sweep2lock. Is this even the best (most stock/easiest/safest) way to do it?

I don't want to use a custom recovery, if I can avoid it. I'd rather use fastboot, to learn and to stay as stock as possible.

2) Is flashing the kernel as easy as running "fastboot flash boot zImage" with zImage from the kernel directory of the zip?

3) is returning to stock as easy as running "fastboot flash boot boot.img" with boot.img from the factory image from Google?

...or am I missing something. Does flashing the zip files (install and uninstall) through custom recovery do anything I'm not doing with fastboot?

Thanks!
[Nexus 5 Original Android Development] Phazmos:
Someone can correct me if I'm wrong

1 - you can for this with a kernel or with modules. I believe there are flashable modules available. Battery life will suffer using either s2w or dt2w

2 - to flash a kernel, boot.img file, that's what you do, but I don't think you'll get any modules, and I believe these options are modules.

3 - yes, if you have the original kernel in .img form, but, in the case of this kernel, you will lose mp-decision as this kernel replaces it with it's own implementation.

Best bet is to run cwm and flash the zips. You can't go wrong that way.
[Nexus 5 Original Android Development] DevShaft:
Again for everyone complaining why their cpu/kernel control app is not working as it should.
[Nexus 5 Original Android Development] Phazmos:
I cheat - I disable touch boost in mpdecision settings!
[Nexus 5 Original Android Development] gpvecchi:
Gamma app is not compatible with this kernel, because of old drivers... Do you plan an update? Thanks!
[Nexus 5 Original Android Development] gpvecchi:
Does this kernel overclocks the bus speed as others do or not? Thanks
[Nexus 5 Original Android Development] skulldreamz:
Thanks dude for the awesome kernal and kcontrol app. I've uv -100 globally and luckily I must have got a very sturdy board cuz I can go down to -150 but there is no need. Point being my phone falls into deep sleep within minutes and I get at least 1 hour extra screen on time with your kernal. Very excited about a update!!!!!!!

If anyone knows how to make boot animations, I would be very thankful for a bricked boot animation and wallpaper. I will pay off course... thanks
[Nexus 5 Original Android Development] connecorn:
Does this kernel comes with s2w and s2l too? Or only d2w in kcontrol?

I'm using an app call TouchControl to configure these functions. And yes, with another kernel too. I just wanna try this Bricked-kernel out. So please someone?
[Nexus 5 Original Android Development] jwhyte:
All of the above with kcontrol
[Nexus 5 Original Android Development] connecorn:
Thanks buddy
[Nexus 5 Original Android Development] hd2009:
Bricked kernel + Kcontrol = a must have for all nexus 5 owners.

After trying several other kernels, this is the best I've tried so far in terms of balance between performance, cpu thermal throttling and battery usage.

I'm using it on droidkang v14 rom.
[Nexus 5 Original Android Development] gpvecchi:
Please, add compatibility for latest gamma app...
[Nexus 5 Original Android Development] estallings15:
You're welcome to compile the kernel with gamma control yourself. He knows it exists. If he wants to add it, he will.
[Nexus 5 Original Android Development] FlyinGrub:
FYI, Dev can have free times :)

they can have a familly too, and perhaps they want to spend time with their family :good:
[Nexus 5 Original Android Development] gpvecchi:
I use Windows. I haven't find any guide on how to compile with it...
[Nexus 5 Original Android Development] estallings15:
If your machine has the power, you can run a virtual machine. Alternatively, there are Linux installers that will retain your original OS. Having another OS on your machine is a great idea for several reasons. I highly recommend it. Once that's done, you'll have your choice of guides.
[Nexus 5 Original Android Development] gpvecchi:
Yep, thanks! I'd not go for dual boot (Windows 8.1...), I could run a virtual machine, but I don't know absolutely nothing about Linux... :D
[Nexus 5 Original Android Development] skulldreamz:
You just admitted you have everything in front of you to start to learn and tackle Linux but you don't want to. I'm not trying to be a **** but I get frustrated when I read posts liked this because I'm a recovering heroin addict and I finally decided one day after my brother and best friend were coping dope in Baltimore and were gunned down so I put down the needle and picked up a book and haven't looked back since. I know it's hard and intimidating but just learn in baby steps and don't get overwhelmed. Good luck my dude...
[Nexus 5 Original Android Development] gpvecchi:
Sorry, but if you don't know anything about engine, will you start remapping a Ferrari?

I think I can understand something about Linux before compiling a kernel...
[Nexus 5 Original Android Development] estallings15:
While I agree that you shouldn't be afraid to jump in and try when you have a working PC and there are a ton of guides available to walk even those with no Linux knowledge through compiling, I don't think this is the place to discuss it. We don't want to clutter the thread.

Cheers.
[Nexus 5 Original Android Development] skulldreamz:
My apologizes, I didn't mean anything negative. Back to my favorite kernal now :)
[Nexus 5 Original Android Development] show-p1984:
Foreword:

First of all I wish a merry Christmas to all of you.

I was a-wall a while since we lost 2 members of our family in the week before Christmas within 2 days. And then there was Christmas. So... That's that.

I am slowly coming back now to work on this and my other kernels as well as KControl.

Usually I don't. The linux kernel updates are for the most part device support updates, which we don't need. (Since our devices never change)

If I see anything worthwhile in those updates I will, though I am rather interested in building a shared 3.12 device tree for all my nexii. :)

I will soon(tm).

Neither sweep2wake nor doubletap2wake use any kind of wakelocks.

It's a good scheduler, but it's 'new'. If you talk to any kernel dev: new = unstable. Unstable is bad. I have had a few crashes with it on my devices and reported the bug in the appropriate place. Let's just give it a few more months to stabilize properly.

The Completely Fair Scheduler (CFS) on the other hand was merged into the linux kernel with version 2.6.23 and has been the default scheduler ever since. It's rock stable and provides and overall good performance and experience. As alternatives I fancy deadline on some devices (With the correct settings).

Unrelated. This is a baseband issue for some people and is related to the new radio.

There is indeed an issue where the min frequency is not set properly on the hammerhead. This is caused due to LG's hack to only activate 2 cpus during boot time, hence the frequencies on the other 2 cannot be set properly. This will be fixed in a future update soon(tm).

There is: https://github.com/showp1984/bricke...ivers/input/touchscreen/doubletap2wake.c#L159

Because of NO drivers.

soon(tm).

*coughs*

https://github.com/showp1984/buildscript_example
[Nexus 5 Original Android Development] estallings15:
[MENTION=4195844]show-p1984[/MENTION]

I'm very sorry for your loss.

Thanks for dropping by and clearing things up.
[Nexus 5 Original Android Development] HTCore:
I'm very sorry to hear that and thanks for head up.

Merry Christmas.
[Nexus 5 Original Android Development] rancur3p1c:
wow sorry to hear that! :(

I seem to be able to get it to wake when I put 5-9 seconds between taps.

I incorrectly assumed this meant tap_time_pre and touch_nr were keeping track of the down-up nature of a tap (e.g. no singular taps longer than 700ms accepted), so when I asked before I asked wrongly.

I don't have the capacity to debug it. Could someone at least replicate? before we bother showp to look into it:

1. enable DT2W

2. tap once (normal tap, make sure it's a solid tap and doesn't get missed/too fast of a tap)

3. wait 5-9 seconds

4. tap again

5. screen should wake

this is on faux123's 005 kernel. I've verified in his github, that this function and related ones contain the same code.

If you can/can't reproduce, please report kernel using.
[Nexus 5 Original Android Development] FlyinGrub:
same thing here the timer is arround 5sec
[Nexus 5 Original Android Development] Rashiel:
Hej,

showp - i´m sorry to hear that.

Hope it´s not so bad anymore?

A little question..

On Nexus 4 the Sweep2Wake Feature don´t use that much battery, that the N5 does..

Is there any reason for this?
[Nexus 5 Original Android Development] hd2009:
i have a stupid question... is bricked fully compatible with cyanogenmod ?
[Nexus 5 Original Android Development] Rashiel:
Should be.

Nandroid and then happy flashing ;)
[Nexus 5 Original Android Development] akaHardison:
I dig something out in service manual.The screen power is tied with touch's power.So if you turn on s2w or dt2w,you will be taken lots of power.

But flar2 and showp didn't agree with me.

/for developer:you can see the TestPoint in service manual.Screen's power is shared with touch's.If any wrong please tell me
[Nexus 5 Original Android Development] Rashiel:
Thanks - but that sounds, that i need to sell my N5 and buy the G2...

I like the "knock-knock"feature.. Won´t live without it :(

Hope maestro showp will find a good solution!
[Nexus 5 Original Android Development] gpvecchi:
Question on K-control: how to remove the inserted module for GPU? And I can't find the setting for read ahead buffer size...

Thanks!
[Nexus 5 Original Android Development] akaHardison:
That is a hardware problem(I guess).And come on.G2 is good? The rear button is ....Knock knock need power,too.You should know nexus has original android and update fast.And nexus has some special function.But if you have to use knockknock.Nobody will stop you.:smile
[Nexus 5 Original Android Development] show-p1984:
Why would you want to?

The module only does somthing when you modify the advanced gpu settings in KControl, otherwise it does nothing.

If you still want to, here are some linux module ops:

Show all modules loaded:

lsmod

Remove a module:

rmmod modulename.ko
[Nexus 5 Original Android Development] hd2009:
Im asking because dt2w sometimes reboots the system.
[Nexus 5 Original Android Development] laggo:
I'm sorry to hear of your loss. I was in a similar situation last year when I lost two family members between Christmas and New Years. Hope you and your family are doing as well as one can, after such events.
[Nexus 5 Original Android Development] gpvecchi:
Thanks, I would like to remove it because I had to switch back to Trickster as K-Control does not have read ahead buffer size, so the module is actually useless for me...

What's its name? Thank you!
[Nexus 5 Original Android Development] :
The module won't affect anything if you don't use it, so just leave it alone
[Nexus 5 Original Android Development] prstorero:
I believe it's Sys/module/kcontrol_gpu_msm/

prshosting.org
[Nexus 5 Original Android Development] connecorn:
Knock Knock is good. But I cannot tololate that much power consumption :(

The screen also keeping waking itself no matter how much I put it in deep sleep mode. Both test confirmed from using Kcontrol and TouchControl.
[Nexus 5 Original Android Development] hd2009:
I think that bricked is not 100% compatible with cyano, or droidkang which i am using right now.

I'm testing phantom kernel and im not experiencing any issue with dt2w.
[Nexus 5 Original Android Development] gpvecchi:
Do you confirm that K-Control can't set read ahead buffer size? Thanks!
[Nexus 5 Original Android Development] parkson:
Now that you mention it I can't find it either. Normally I leave it at default, which is usually 256, 512, or stock 128. Can never tell a difference in usage/feel while adjusting RAB anyway
[Nexus 5 Original Android Development] gpvecchi:
I tried some SD benchmark tools, it seems that 1024 give some Mb/sec boost (more than 10...)
[Nexus 5 Original Android Development] UgoBoss:
Just tried Trinity and ElementalX but I'm back always back to Bricked ! Awesome work show-p ! :)

Just a question, my GPU max frequencie doesn't stick at boot.. And yes I've checked the box 'apply GPU settings on boot'..
[Nexus 5 Original Android Development] ChriKn:
Having the exact same thing using Franco and dt2w. Got it when tapping the screen 3 times with 5 seconds between each tap.

Another thing is the unlock sound during calls. Don't know if it is common...
[Nexus 5 Original Android Development] show-p1984:
New stable is up! Supporting multirom! :)

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

(and my scripts fix that annoying smp freq reset issue)

/system/lib/modules/kcontrol_gpu_msm.ko

That is actually a mistake :/

I had it commented-out for testing other stuff and forgot to re-add it. There will be an update soon.

I tried 5 minutes to reproduce this, no dice.

Exact steps to reproduce please? :/
[Nexus 5 Original Android Development] gpvecchi:
Thanks for the update! I see also a new beta, wich one is most recent? May I suggest to use a name that let's identify them easier?;)