yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] magnamentis:
good job but :)

the easiest way to achive this goal very similarly is to use daydream on charging or docked. what will happen is that the moment you touche the screen

you're back where you left off, even without a further move needed to unlock.

main reason why i deactivated these functions on my devices is that while making phone calls, albeit the screen goes dark,

the touchscreen remains responsive, thus all kinds of apps are opening totally at random and the call can be canceled by accident as well.

thus considering to have this function only on power where i can have it with daydream and then not being able to make calls without

causing a total disorder behind a black screen, i think this is simply not ready for daily use, albeit i like the feature in general and

appreciate the ability as well as the good job done by the dev. :)

i think that if all those longing for this features in many xda-threads i'm following knew about the downsides they wouldn't be so eager anymore.

last but not least there remains the battery drain in idle which went up from 2-3% during the night to 17% during the same time period.

so what we have here is a feature that can be used without huge handicap only on charge and then causes problems in call

so not much will remain to be fun really.

regards
[Nexus 5 Original Android Development] nobnut:
You've misunderstood the tasks. They do more than you describe. Such as manually toggling S2W via a widget regardless of connection state.
[Nexus 5 Original Android Development] Han Solo 1:
Coming from a G2, the double-tap to wake, and the ability to double-tap to sleep (with Nova gestures), this is awesome!

Thanks show-p1984!
[Nexus 5 Original Android Development] tyea:
How do I setup Nova gesture double tap to make the phone sleep?
[Nexus 5 Original Android Development] Deegan87:
Tell nova to use a tasker task that puts your device to sleep when you double tap.
[Nexus 5 Original Android Development] show-p1984:
The issue with intellidemand is it's integration.

In order for it to work I would need to port faux's bogus power suspend driver, or rewrite that section of intellidemand.

Additionally it has a boost pulse interface which is conflicting as well. So more stuff to rewrite.

That would also require me to use faux's powerhal, which uses the insanity complex to send a boostpulse. I have explained this earlier for qcoms mpdecision binary: Kernel->Android->PowerHAL->Kernel. That's just ugly, especially if you can do it in the kernel without android.

That's just way too messy. If you followed my latest commits I am going towards LESS integration into other kernel parts (not to mention Binaries and Android). I am aiming at doing as much as possible in each compilation unit itself, instead of hooking into other stuff.

Yes.

I was talking about s2w and dt2w. Ofc s2s will not cause the increased drain.

Well, it maybe that they are delayed. (as everything is on Google Play)

I wrote to the support team of Google Play in order to solve this issue or get an explanation.

I would have to test that, but in general the proximity sensor on/off every 500 ms would force the kernel to wake up the system in order to do that.

Leaving the sensor on all the time might be the better choice since we could then (depends on the sensor type) use interrupts to check if the system would need to wake up.

The last report I see in the dev console which has something to do with the Scheduler section is from version 1.7.2, which is vastly outdated.

It's available in stables and betas.

That kernel used in that kmsg was not built by me and not from my sources. There were modifications, even uncommitted ones.

I cannot and will not debug other peoples messes here.

3.4.0-Bricked-Harp-g71fca74[B][COLOR="Red"]-dirty[/COLOR][/B]

I would suggest you have a talk with "Harp" about this issue.
[Nexus 5 Original Android Development] ash_arani:
Great kernel and nice features.

I tested the S2W and DT2W via terminal emulator and they work great. Being a newbie when it comes to modifying kernel features, I just created a script via SManager and have it run at boot.

Any disadvantages for doing it that way? Any advantage for doing it via the KControl app and/or using proposed methods (to activate on boot) in this thread?
[Nexus 5 Original Android Development] show-p1984:
KControl basically does the same thing.

When android tells it that the boot finished it just writes a 1 in there. Nothing special.
[Nexus 5 Original Android Development] noonecanhide:
Okay, didn't know that. So i'll try to flash your original kernel tomorrow, couldn't get it working on cm11, so i was happy to the prebuilt cm11 with That kernel from the log. Maybe i'll work with unofficial cwm tomorrow, official gives me a bootloop
[Nexus 5 Original Android Development] ash_arani:
Thanks show-p1984.

Keep up the great work. :)
[Nexus 5 Original Android Development] Savant:
[MENTION=4195844]show-p1984[/MENTION] hey having a problem with kcontrol it won't let me config GPU. It keeps giving me an error saying can't insert module.
[Nexus 5 Original Android Development] show-p1984:
That was explained at least 20 times.

The driver on the Nexus 5 has changed a bit too much, that's why it's currently not possible to access GPU control on a Nexus 5. I will fix it though, soon.
[Nexus 5 Original Android Development] Savant:
That was my fault for not paying attention since I just read it . Thanks and I saw it changed alot . it struck me as odd when the app says 91 compatible even the tab with GPU that's why I was confused.
[Nexus 5 Original Android Development] show-p1984:
The compatibility check just checks if the module is there. You might call that a bug. I will change that too.
[Nexus 5 Original Android Development] Savant:
Okay wanted to make sure and I wanted to let you know since it was very odd.
[Nexus 5 Original Android Development] leoaudio13:
[MENTION=4195844]show-p1984[/MENTION] : I just bought your Kcontrol app last night. However, every time i try to reset kernel voltage ( when setting it wrong but dont apply), the app force close :( pushed report via Google Play already :)

Also, do you think Aroma installer and auto UC/OC voltage to choose when installing, is a good idea? Thank you again :)
[Nexus 5 Original Android Development] Blaze420916:
I must be an idiot or something but I bought the app installed kernel and still can't get double tap to work what an I doing wrong? I've enabled it in settings but still nothing

Edit I just use terminal emulator to get it working.
[Nexus 5 Original Android Development] Valdeck:
I am looking forward to trying this kernel. I usually flop between Faux and Franco but I like some of the Dev' answers on why certain things are not included.

Has anyone who uses this kernel used Franco's and can you tell me any noticeable differences between the two before I jump in? It wont stop me from using it but I like to try and be informed I am however not great with understanding how kernels work or how to read through gethub to tell whatever the differences might be.
[Nexus 5 Original Android Development] Phazmos:
Not a while lot of differences between most popular kernels really. There's just so much horse power in this device even poorly coded roms and kernels can run well.

Franco was never known to get best battery life, but usually benchmarks slightly higher than other roms - I've used Franco on a couple devices going back a ways.

But, been running this as my go to kernel the last couple days and it's good. Smooth as any other, just as fast, useful tunables, stable, you won't go wrong flashing it. Right now, this and slimkat, 33k antutu, 15hrs with 4.5 sot, 45% left on battery - with the motox patch.
[Nexus 5 Original Android Development] Valdeck:
what is the motox patch?
[Nexus 5 Original Android Development] FuMMoD:
Moto x dalvik patch. There's a thread right here in the development forum. Search
[Nexus 5 Original Android Development] shr33kant:
Personally I'm using this kernel for it's compatibility with all roms and it's thermal management. I haven't had a chance to test between the two kernels much in regards to gaming and I don't bother with benchmarks. General UX is nice and smooth but I changed some of the settings in KControl for MPDecision -> Simple so that the boost frequencies were all 1036800Hz and the boost time is now 2000ms; this is because I felt quite some stuttering while scrolling through stuff like Twitter / G+ / Tapatalk when on the default settings. The battery on this phone in my opinion was already good and I haven't tested the whole day with these settings yet :).

All in all excellent kernel/app combination and I couldn't recommend it more because of it's compatibility, tweakability and of course the Doctor Who references (ELEVATE!).
[Nexus 5 Original Android Development] magnamentis:
not really !

hi,

so performance and batterywise there are not significant differences to recognize.

- still there is franco's color setting wich i like more

- still there is the apps wich kcontrol i like more but franco's is a bit more reliable

..probably due to the fact that it's a long time on the market already, so more time for fixes

- then there is the dev and the thread which i like bricked more, dev is very responsive and

..and explains facts and whys very patiently and detailed and people here are more friendly over all :)

- further there is s2w and dt2w in bricked which is new and thus comes with handicaps like battery

..usage in idle and touchproblems during calls, but still it's there and franco is reluctant towards it.

- last but not least, i've been using franco's kernels for a very long time and he is basically non-stop

..working on it, trying out things and implementing them quite quickly. this has sometimes lead to

..minor bugs for a short time, while bricked has ever since i'm using it been reliable, so once the

..app has reached that level ( there are fc's sometime, also after the recent fix ) this will probably

..be my daily driver if, but only if i will be able to tweak the gamma which will definitely be the case

..with franco's. this is basically the main reason why i'm using custom kernels on ips display devices,

..i simply don't like washed out and/or pastel colors which is a personal preference of course

hope that info can give you ( in parts subjective ) picture of the situation and i hope nobody will

start to protest, my findings are stated as neurtrally as i could and as mentioned are in parts

based upon personal preferences.

if somone who is tempted has a look into my signature he/se will see that i will not take part in any rude

and flaming discussion about which is better and so on, but of course will gladly discuss friendly

brought up differing points of view. reading this entire post you will know why i mention this last

paragraph, is from experience in certain threads :) [ uff.. now it probably comes .... but who cares ]

regards and enjoy
[Nexus 5 Original Android Development] Stylez Ray.:
This kernel + the cooler colors would be an awesome combination
[Nexus 5 Original Android Development] show-p1984:
Aroma installer: Nope. It was my worst choice to use it in some of my kernels. It isn't being updated for new devices, freezes everywhere and on some devices the touchscreen handling is a mess. Way better to use an app in my honest opinion.

(Furthermore you can't just chain flash an aroma zip with other zips and go afk until it's finished, since the flash process will halt and wait for you to do stuff in aroma, which sucks.)

KControl:

Got the bug reports, others too. After my email to Google they suddenly started to appear! Strange, isn't it? :)

Use the sidemenu, like in G+.

Either pull it out from the left side of the screen or tap the green "K" in the top left corner. Then scroll to the bottom, where you will find Sweep2wake and DoubleTap2Wake. To apply across boots use the Settings options you already have discovered.

Daleks. You gotta love them!

By the way:

IT'S THE DAY OF THE DOCTOR!

:D

(getting afk to watch the 1080p sbs 3d version now :P)

Color and Sound options will hit once Faux has stabilized them. I will pick them over then so everyone can set up their own.

There is no one true setting. People have different preferences. I am fine with the n5 colors, the n4 ones were in need to be adjusted.
[Nexus 5 Original Android Development] leafsacc:
To change your file permissions to rwxr-xr-x it looks something like this (see attached picture below).

However, it didn't work for me on the stable version. When using the stable version I used Trickster Mod for dt2w.
[Nexus 5 Original Android Development] chozyn:
Enjoying this kernel with Trickster Mod activated double tap to wake. Only weird thing with the app is will slide to wake off it still works. The kernel though is running real nice on the N5

---------- Post added at 02:01 AM ---------- Previous post was at 02:00 AM ----------

I meant with it off.
[Nexus 5 Original Android Development] show-p1984:
It will be patched in with the next version, but differently from what Trickster expects.

Trickster is expecting:

s2w_switch = 1: Both on.

s2w_switch = 2: only s2s.

That is wrong.

s2w_switch = 2 was meant to be backlight button capability like it can be seen on the HTC Sensation and various other ports.

Some third party decided to use 2 as s2s only, which is highly confusing.

Instead I will create a new file (s2w_s2sonly) which will, if set to 1, disable s2w if sweep2wake = 1.

So sweep2wake will be the main switch for both, s2w_s2sonly will override s2w.

This way we don't confuse people anymore, which usually happens if third parties start to mess with variables and go incompatible with upstream (me).

####

Pushing a KControl update which should fix most issues that were reported.

I also added a bit more debug info in the event of crashes to help figure out the tricky one. To be specific: the boothandler had an error in apply_settings(). That function is a bit longer though with all it's checks. About 1000 lines. Fairly impossible to find a simple array list out of bounds in there without specific location info, which is now generated. :)

Happy updating.
[Nexus 5 Original Android Development] Sayan1987:
Great work.

Just asking, is trickster app good to full control the kernel or like i read there can be some problem and only kcontrol is fully ok for this kernel?

And coming from Franco, is it ok if i just flash or i need also to flash the img?

Thanks!
[Nexus 5 Original Android Development] kamaliqwan:
I think maybe you should look at wireless charging..

After I'm on Bricked, I noticed that the phone is over heated when charging on wireless charger.. . and not charging as fast as before..

hope you'll fix this soon.. i can be the tester if you need one :)

Everything else is good & smooth.. great work!
[Nexus 5 Original Android Development] nobnut:
You need to use the beta version and to have busybox installed.
[Nexus 5 Original Android Development] show-p1984:
I don't regularly use Trickster so I can't answer this completely.

KControl has no secret sauce so that only KControl can do xyz on this kernel. In fact all of KControl's functions can be performed over sysfs by any app. What KControl does with the information it can gather over sysfs can be seen with the GPU Memory overview for msm devices with adreno gpus, which is the first to be found in an app on Android.

KControl has evolved to be much more than just a kernel controller for this kernel. But enough of the sales speech :p Use Trickster if you want, just beware that I have no influence on misbehaving third party apps.

I didn't touch charging code, so there is no influence on speed or heat generated during charging. That behavior is highly unlikely to be related to Bricked, also because I myself own a Qi charger cushion and it works perfectly.

By the way: The term "over heated" is highly subjective and way overused.
[Nexus 5 Original Android Development] NuxMortis:
Awesome, thanks!

And as always, thanks for taking the time explaining everything.
[Nexus 5 Original Android Development] will444:
Woah knock on is here! Like it!

How about knock off? Making it double tap the status bar turns the screen off? Even if you don't its still reallllly cool :good:
[Nexus 5 Original Android Development] kamaliqwan:
oh so ur on orb chrger too? dang it! i hate to have a problem alone..! hahaha

but i can confirm that the overheat is after i get bricked cos i need s2w...mybe i should full wipe and flash all over again..

or just remove & reflash bricked again.. can u give any idea of setting on trickster mod? maybe that can fix it..coz i dont really know and dont want to mess with it without any guide :)

anyway thanks for your answer dude..:good:
[Nexus 5 Original Android Development] nobnut:
You can use GMD Control for that. it works a treat for me.

It's already been stated in this thread that it won't be implemented in the kernel.
[Nexus 5 Original Android Development] Sayan1987:
Thanks!

Coming from franco i wasn't sure if flashing stock img was needed,but to be sure i did it and got lot of errors, phone booted but no signal, couldn't see sdcard from pc..

So i reflashed again franco, cleaned cache and then flashed your kernel direclty without passing by stock img.

Everything seems working like a charm, but what would you say?

Maybe there's something undercover that goes in conflict, or if i don't see like above visible errors i'm fine?
[Nexus 5 Original Android Development] KingDani1997:
I am using your kernel for some days now and I must say it is ****ing great! The screen on time is more than twice compared to stock!

After I used TricksterMod for some time, I bought KControl to support you. Very nice app! I thougt there wouldn't be much difference compared to Trickster, but after one minute of using, I will never use another Kernel Control app than yours.
[Nexus 5 Original Android Development] Audioboxer:
Kernel running really smooth with K-Control :highfive:

Any chance of an auto-update kernel feature within K-Control down the line?
[Nexus 5 Original Android Development] Alfonso87:
Guys, have you switched off the advanced wifi setting "Scanning always avaible" or you left it on? [MENTION=4195844]show-p1984[/MENTION] what do you suggest?
[Nexus 5 Original Android Development] nobnut:
It depends whether you want fine location reporting for Google Now etc.

I keep it on.
[Nexus 5 Original Android Development] Alfonso87:
I would save battery more than have a fine location reporting :p What could be the best for this purpose?
[Nexus 5 Original Android Development] nobnut:
If you want more battery, turn it off.
[Nexus 5 Original Android Development] nicob:
When I try to set group_idle to 1 in KControl it sets it to 10. (back to 0 works)
[Nexus 5 Original Android Development] jlsesler:
+1. Auto update would be nice! :)
[Nexus 5 Original Android Development] chozyn:
Thank you for the reply! I will get K Control as I have been reading a lot of good things about it as well as to support the dev :good: that hooked us up with this great kernel!
[Nexus 5 Original Android Development] nicob:
Also, hotplug settings are not persistent after reboot, if enabling 'Apply MPDec settings'

My Nexus 5 ( LOWER krait version) seems to be stable at -75mV overall and:

96Mhz @ 575000

192Mhz @ 625000

249,6Mhz @ 650000

300Mhz @ 675000

345,6Mhz @ 675000

422,4Mhz @ 700000
[Nexus 5 Original Android Development] openlatedotorg:
Does kcontrol have led settings like trickster (I haven't used led settings on it yet, just known it's available in paid version)
[Nexus 5 Original Android Development] gaetanolip:
Hi,does the kernel support NTFS and swap? Thanks

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Alfonso87:
[MENTION=4195844]show-p1984[/MENTION] Gr8 kernel. You are Chuck Norris approved. Take my money (aka i just bought your app). Continue your developing!

EDIT: got a crash of your app when tring to go in schedule settings. I have reported it. I'm on stock with ART.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] iamhacked:
Wow! This kernel runs so much better than stock. Thanks!
[Nexus 5 Original Android Development] Dennis0201:
Can someone help me how to use Kcontrol to activate D2TW? It seems doesn't work for me...\

Thanks.
[Nexus 5 Original Android Development] show-p1984:
That's the stock boot img. There will be all kinds of malfuntions if you flash it on another rom than STOCK.

That was what I was going for :p

Thank you for this kind review.

It's planned for version 2.0, or shortly after. Profile support will be the 2.0 update.

Off gives you battery, on better location.

Personal preference. I for my part always leave wifi on. I am just lazy though.

That was a typo from me, I meant 10.

The kernel only accepts those steps. What KControl does is this: It tries to set your value, then reads the value again and gives that back to you. So in case the kernel rejected the value, you will see it reset to the old one, or bumped by the kernel.

Only when setting simple settings? or also advanced?

Which ones?

KControl version?

It's currently not possible to control leds over KControl. That might be something for a future update. (way future, so don't expect it next month. I have big plans for KControl on my TODO list)

#Should-be-fixed

Not really rocket science. Tap the green K or slide out the nav area, scroll to the bottom, select dt2w and check the checkbox.

If you want it to stick through reboots Settings->onboot->on and Settings->DT2W->on

showp1984@jarvis:~/WORK/kernel/bricked-hammerhead$ cat .config | grep SWAP
# CONFIG_SWAP is not set
showp1984@jarvis:~/WORK/kernel/bricked-hammerhead$ cat .config | grep NTFS
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y

#####

GPU Control fixed for the Nexus5! :)

https://plus.google.com/u/1/108262968419038009038/posts/Bz2v17H5Vha

Will be in the next KControl and bricked version *tease* :)
[Nexus 5 Original Android Development] iamhacked:
I don't know if this has been asked before, but will this ever get faux sound?
[Nexus 5 Original Android Development] show-p1984:
Yes, soon(tm).

Waiting for those features (color/sound) to stabilize.

#####

KControl update released! If you use the beta I just cooked up (http://bricked.de/index.php?action=kdownload&device=hammerhead&release=beta&type=aosp) then you will have GPU Control and Sweep2sleeponly in KControl 1.9 - "Silence must fall" which will be pushed out by the play store within the next hours.

There were also bugfixes applied to fix the 2 remaining crash reports in my dev console.

Would you like to know more?

http://bricked.de/kcontrol_changelogs.php

PS:

Some crashes I see are due to wrongly setup or stone old busybox installs. There are people actually still using busybox 0.x (I used that last time on my hTC Hero...).

Update your busybox versions! And don't use smart install :)
[Nexus 5 Original Android Development] nealkoy:
Same thing happens to me when selecting scheduler tab and I justin downloaded the app yesterday . I'm running stock 4.4 dalvik by the way.
[Nexus 5 Original Android Development] MWilkenson:
with GPU settings what would you recommend for battery?

Will the cooler thermal settings be better for battery? Do we apply that to every setting in that section?
[Nexus 5 Original Android Development] show-p1984:
12500 µV = 12.5mV.

Wikipedia should have helped with that, or Google.

Dial down the clock speed to about 320. This will underclock the gpu by 130Mhz, and it will also use less voltage to run at that frequency if you dial down all top 3 power levels for example. (the driver will always use the first occurence if more than one power level has the same frequency)

You can also play with io_fraction

Yes.

Yes, I wrote that, didn't I?
[Nexus 5 Original Android Development] styr:
Will the sources for the gpu control module be publlished?
[Nexus 5 Original Android Development] show-p1984:
Ofc, they are already for ages. Both tegra and msm.

MSM: https://github.com/showp1984/kcontrol_gpu_msm

Tegra: https://github.com/showp1984/kcontrol_gpu_tegra
[Nexus 5 Original Android Development] styr:
Thank you, i`m a moron, i`ve asked before checking. :D