yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] show-p1984:
The scheduler interface is borked in googles kernel release. I am still trying to figure out why and what they did to it to kill it.

Some paths are just not created, for example: The current schedulers main directory where all the configuration files reside in.

EDIT: They have just moved and I just found them.

Since KControl checks for that and can't find it that configuration part is hidden. Once I can fix it the right way in the kernel KControl should be able to show everything in the usual manner.

until then...

Deftault & available schedulers for device:

/sys/devices/msm_sdcc.1/mmc_host/mmc1/mmc1:0001/block/mmcblk0/queue/scheduler

noop deadline row [cfq] test-iosched

/sys/devices/msm_sdcc.1/mmc_host/mmc1/mmc1:0001/block/mmcblk0/mmcblk0rpmb/queue/scheduler

noop deadline row [cfq] test-iosched
[Nexus 5 Original Android Development] akaHardison:
Hello.S2W will wake the screen?This problem show up when using flar's kernel on N72nd.It will keep screen show thing without backlight.Seems he said the touch power is coming from screen power.LDO still awake.Using a lot of power.You can find this on D281's Service Manual.They are tied together. sad
[Nexus 5 Original Android Development] show-p1984:
I pushed the KControl bugfix release to the play store, may take a few hours to be visible though (as usual).

In KControl scheduler settings will look like this:

https://dl.dropboxusercontent.com/u/44206202/Screenshot_2013-11-19-03-21-41.png

https://dl.dropboxusercontent.com/u/44206202/Screenshot_2013-11-19-03-34-46.png

https://dl.dropboxusercontent.com/u/44206202/Screenshot_2013-11-19-03-34-53.png

https://dl.dropboxusercontent.com/u/44206202/Screenshot_2013-11-19-03-35-00.png

https://dl.dropboxusercontent.com/u/44206202/Screenshot_2013-11-19-03-35-08.png

With settings for each scheduler, independent of the block device they are for.

Full. Control. KControl. (Should be a slogan? Aye? :D)

Nope, sweep2wake will not do that. I improved upon flar2's patch (or rather rewrote it) so we do not keep any regulators online. The only thing we keep online is the gpio the pmic (that controls the touch panel) is tied to.

(and we don't send the reset command)

Those µC are very power efficient, because they are not that powerful. Probably still more powerful than what has driven the Columbia and Eagle back in the day though.

Either way: I can run a pmic for the better part of a month on just one 9V block battery with all leds disabled and in irq slumber mode.

See here:

https://github.com/showp1984/bricked-hammerhead/commit/7860be26c42a2c4c8ec5d7185af0a68191dfd4e7
[Nexus 5 Original Android Development] FuMMoD:
When i use this rom there's like a certain reddish hue on the screen. I don't know if it's cause the screen is not calibrated with the kernel but it is very minimal but i noticed it a lot. I flash between Franco's and this and I have to go back to franco because of it.
[Nexus 5 Original Android Development] davy917:
[MENTION=4195844]show-p1984[/MENTION] Thanks for all the explanations man.. really appreciate it! I've gotten used to "I said it doesn't work, search thread. Wait for fix."

---------- Post added at 09:48 PM ---------- Previous post was at 09:48 PM ----------

Franco changed screen calibration in his kernel, so you're probably used to his and looking at stock colors on this kernel.
[Nexus 5 Original Android Development] FuMMoD:
Wow the stock colors really suck lol. Would the OP be working on a screen calibration any time soon? I did a quick search for color throughout the thread and didn't find anything. Thanks
[Nexus 5 Original Android Development] davy917:
Pretty sure Franco is the only dev that has done anything to color, I doubt this would be a high priority because the end goal for all the devs would be full color/gamma control. Although Franco did say that all he did was change like one digit and gave more contrast in the meantime.
[Nexus 5 Original Android Development] show-p1984:
Well hackers, or devs, are usually attracted by questions. Intelligent ones. And if they are asked for the first time one might even answer a rather stupid one, once.

After all I do this not for the money (yeah, who would have thought that, huh? ^^), but because I love to solve problems, improve stuff and see the results of my work.

So if someone who has done some research comes to me with a question and I don't know the answer to that and say: "Good question!" then that is actually a compliment. That someone gave me something to chew on, which is not that often happening anymore.

So if someone tells me that the Zeebob3 of his camuro2 isn't working properly when disabling the halibob on the second fgrl, then I can help that someone by doing some research if I don't know the apparent answer.

If someone tells me: Bootloop! Fix it!, the only thing I think about that is: Useless.

He gave me no way to help him and I have no obligation to pull all the info out of his nose. Sometimes I do, because I am in a good mood and have some time left (usually when android is compiling and clogging up my laptop for 20 minutes), but that doesn't mean that everyone can expect that and be lazy. Searching the thread and the web is a good advice and saying you did when you didn't is quickly unmasked as a lie. Remember: I wrote this thread, I read every post in it. I actually know what is in here and what isn't :)

Just my 50 cents on why sometimes you get a "STFT / STFW" instead of a nice explanation.

The link in my signature elaborates on this quite extensively. People should take the time to read it.

I will pick faux's when the time is there. There is no need to re-invent the wheel and introduce fragmentation all over the place of one and the same thing.
[Nexus 5 Original Android Development] jarjar124:
Very impressed. Will see how's battery life tomorrow.
[Nexus 5 Original Android Development] FuMMoD:
Thank you. I'm subscribed to this thread and looking forward to it. I can't stand the stock screen calibration and Franco nailed it.
[Nexus 5 Original Android Development] Deegan87:
Finally, sweep2wake. Thanks [MENTION=4195844]show-p1984[/MENTION]. I've been waiting for this since release. I'm looking forward to doubletap2wake / knock-on.
[Nexus 5 Original Android Development] davidbar93:
Bootloops after flashing latest stable version... Stock rom.
[Nexus 5 Original Android Development] show-p1984:
I am testing this kernel on stock rom, without one issue.

Without a last_kmsg I can't tell you what went wrong.
[Nexus 5 Original Android Development] lexxa83:
Stock ROM so far so good
[Nexus 5 Original Android Development] wera750:
If you wiped cache you more than likely corrupted that partition and need to flash back to stock. It's a known bug.
[Nexus 5 Original Android Development] show-p1984:
adb reboot-bootloader
fastboot format cache

Should be enough in that case.
[Nexus 5 Original Android Development] thejonesyboy:
I'm trying to use an init.d script to enable sweep2wake on boot, but it's not running. The script has the correct permissions and UNIX character set.

root@hammerhead:/ # ls -al /system/etc/init.d
-rwxr-xr-x root shell 0 2008-08-01 20:00 .dummyfile
-rwxr-xr-x root shell 57 2013-11-19 12:27 01script

root@hammerhead:/ # cat /system/etc/init.d/01script
#!/system/bin/sh

echo 1 > /sys/android_touch/sweep2wake

For some reason it doesn't run on boot. It does run manually using sh:

shell@hammerhead:/ $ su
root@hammerhead:/ # sh /system/etc/init.d/01script

Any ideas?
[Nexus 5 Original Android Development] davy917:
Are you using latest official cwm? We've had multiple reports of bootloops when flashed via this recovery.

If so use the unofficial version or TWRP

---------- Post added 19th November 2013 at 12:01 AM ---------- Previous post was 18th November 2013 at 11:58 PM ----------

S2W working really well so far, and KControl update pushed and showing i/o scheduler :)

I'm also running at -75mV now and not a hiccup so far, tested on reboot and set on boot as well. I'm also PVS 2 which is even more surprising.
[Nexus 5 Original Android Development] show-p1984:
Run-parts support requires busybox. Do you have it installed in /system/xbin ?

If not, do that and reboot. Everything should work.
[Nexus 5 Original Android Development] dying4004:
mate, how do you install or enable s2w?

is it working fine in your N5?

this feature lets you to wake the phone without pressing power button, right?

cheers
[Nexus 5 Original Android Development] styr:
This happens when i try to access scheduler settings in the lastest version of KControl (1.7.1)

08:19:12.673 Error AndroidRuntime 5011 FATAL EXCEPTION: Thread-335
08:19:12.673 Error AndroidRuntime 5011 Process: de.bricked.kcontrol, PID: 5011
08:19:12.673 Error AndroidRuntime 5011 java.lang.IllegalStateException: Unable to add commands to a closed shell
08:19:12.673 Error AndroidRuntime 5011	at a.c.a.b.b.a(Unknown Source)
08:19:12.673 Error AndroidRuntime 5011	at de.bricked.kcontrol.ls.b(Unknown Source)
08:19:12.673 Error AndroidRuntime 5011	at de.bricked.kcontrol.ls.a(Unknown Source)
08:19:12.673 Error AndroidRuntime 5011	at de.bricked.kcontrol.lb.run(Unknown Source)
08:19:12.673 Error AndroidRuntime 5011	at java.lang.Thread.run(Thread.java:841)
[Nexus 5 Original Android Development] thejonesyboy:
Ahh yes. I am running stock with your kernel.

Installing BusyBox from Play store worked perfectly. Thanks mate :)
[Nexus 5 Original Android Development] george241312:
Hey man is there any way to have lmt working on your kernel ? Search v menu back don't work... :(
[Nexus 5 Original Android Development] r0cafella:
Showp my favourite poster on XDA, thank you for the knowledge Sir
[Nexus 5 Original Android Development] show-p1984:
This looks like an ui mod. The kernel does not have any knowledge of ui features (it doesn't even know about the buttons on the stock 3button bar).

Looks like that add on is just broken if those buttons don't work.
[Nexus 5 Original Android Development] psxsnake:
i see news Sweep2wake, but are not under stable, only under bets's... right?
[Nexus 5 Original Android Development] show-p1984:
at the moment, yes.

If no major faults are reported it will go stable tonight.
[Nexus 5 Original Android Development] leoaudio13:
No problem at all. Been using it since released and no hiccup so far. Also everything works even with Trickster. I will get you Kcontrol next week when mobey is in da bank hehe. Tks again show-p for gr8t kernel.
[Nexus 5 Original Android Development] swa2k4:
Once it goes stable will there be an easy way to enable it? Thanx
[Nexus 5 Original Android Development] IharpI:
There is already an APP and someone posted a script.
[Nexus 5 Original Android Development] spica123:
Just flashed latest beta and bought your app! Thank you so much!!!

Everything working flawlessly so far.

S2w was the feature I was waiting for.

One question: is it still necessary to calibrate battery after flashing something or does KitKat do this on its own now?
[Nexus 5 Original Android Development] swa2k4:
Just bought the app it's great! Very impressed with this kernel for this feature as well as the add speed of course!! Thank you!
[Nexus 5 Original Android Development] PippoX3:
[MENTION=4195844]show-p1984[/MENTION]. I Just flashed latest beta and bought your app! Great!

Thanks a lot, S2W was the feature that I was waiting for (toc toc = DTW will be the next! :D )

Everything seem working flawless (I'm on SlimKat, no SU issue).

One quest: I have some compatibility checks in fail state (GPU memory usage, Scheduler, Color Control, Sound control). Is it normal?

Thanks again.
[Nexus 5 Original Android Development] OhDae-su:
Another satisfied user! Bought KControl and a little bit of my Weihnachtsgeld :D will be on its way to you as soon as my PayPal account receives the transaction from bank account...

...and btw just read that::thumbup:

https://plus.google.com/109078966818501160423/posts/7yRWXdvpwWz
[Nexus 5 Original Android Development] IharpI:
Cool that you were so fast with implementing S2W but i am confused that you did not implement DT2W first?

Thought this would be even easier than detecting a complete gesture.

Really looking forward to the knock knock feature as i find it more intuitive then swiping on a blank screen! :D
[Nexus 5 Original Android Development] nisha86ge:
mic volume issue

Nope, I didn't change anything regarding microphones or speakers, yet.

Usually the issue you describe is caused if you have a case that doesn't leave an opening for the ambient noise mic, or you covered it by hand. On the Nexus 5 that mic is right beside the headphone jack. (that small hole)

[/QUOTE]

Thanks for the reply , but i do not have any case, googling i found out that many people has the same problem i have, from what i understood it is related to the noise cancellation (??),

could u please consider it for your future releases?

thanks
[Nexus 5 Original Android Development] DevShaft:
I do not know about scheduler which is working for me, but the other ones are not yet implemented in the kernel. These will be available at a later time :).
[Nexus 5 Original Android Development] PippoX3:
Simply when I try to reach "scheduler" it FCloses the app KControl. But maybe I'm on the last beta... :fingers-crossed:

Edit. After a pair of FCs, my compat. list now is come back to 91%... Color control now is "pass"... :confused:

Edit2. Already BusyBox 1.20.2 installed into system/xbin
[Nexus 5 Original Android Development] styr:
I`ve posted the logs of the scheduler module crash a few posts back.
[Nexus 5 Original Android Development] shr33kant:
[MENTION=4195844]show-p1984[/MENTION] I just flashed your kernel and S2W is working really nice! Gonna report back battery after a few cycles :D. Bought your app to show my support and I like your choice of name for the app version ^_^. I'm also getting the incompatibility message for scheduler but tbh I never mess with that and go with whatever is set to default. Maybe next version call the app 'DON'T BLINK!' :D.
[Nexus 5 Original Android Development] leoaudio13:
[MENTION=4195844]show-p1984[/MENTION] I think there's a minor battery drain after flashing the beta kernel with s2w. Perhaps becos of the touchscreen wake ?

---------- Post added at 08:34 PM ---------- Previous post was at 08:34 PM ----------
[Nexus 5 Original Android Development] unciviilized:
Sorry for this question guys but how do I enable S2W , I already purchased the Kcontrol app but I don't see an option for it, thanks
[Nexus 5 Original Android Development] IharpI:
Did you install the latest beta kernel?
[Nexus 5 Original Android Development] PippoX3:
Tap the green K on top, swipe the column from top to bottom, search for "sweep2Wake". But you have to flash the last kernel beta, that include the S2W.
[Nexus 5 Original Android Development] unciviilized:
Ahh got it , thanks!!
[Nexus 5 Original Android Development] Ecf17:
Will this also uninstall if one were to restore a backup? Just wondering because I haven't needed to flash something to uninstall a kernel before.
[Nexus 5 Original Android Development] cc16177:
In my experience a lot of time they will include a zip that just flashes the stock kernel as an easy way to "undo" a kernel install rather than having to re-flash your ROM or restore to a backup.
[Nexus 5 Original Android Development] PippoX3:
This because together to kernel image, were flashed also the modules. The uninstall script restore old ones with stock kernel.

Not alls kernels needs to change modules.
[Nexus 5 Original Android Development] IharpI:
Does anybody already have some information on how much battery is used by s2w?
[Nexus 5 Original Android Development] spica123:
Drain is quite high! I lost 5% in 2 h after install and full charge. Display was only 2 minutes active :confused:

Settings default, slightly underclocked.
[Nexus 5 Original Android Development] erpalma:
I confirm a slightly heavier power consumption using S2W. Now I'm on 50% with 9 1/2 hrs and 1 1/2 screen on.

I also noticed that I have a HUGE power consumption in my university using wifi. For sure it's related to broadcast traffic generated by windows and osx pc on the network. I remember that my kernel on S3 disabled bcast/mcast on wifi to solve this issue.
[Nexus 5 Original Android Development] Citizen_Snips:
Thank you for this kernel, show. Really enjoying it so far.

Sent from my Nexus 5
[Nexus 5 Original Android Development] dialmformostyn:
I read this is something to do with SE Linux? I won't pretends to be expert in this matter on any level, however. Some kernels I tried (I forget which) work with the back button etc, others do not. On the non-compatible kernels, neither LMT nor Dynamic Nav Bar were fully functional.
[Nexus 5 Original Android Development] r0cafella:
If you could provide some more info and some logs then maybe we can help :)
[Nexus 5 Original Android Development] maisi:
I just installed this Kernel and the Kcontrol app, but I'm getting an error when I try to access the GPU settings.

The error says that this is not a CONFIG_KALLSYMS_ALL kernel, does that mean that this function isn't available on this phone ?(says it would work on the compatibility thing)

Sry if this has been addressed already, search function found nothing.
[Nexus 5 Original Android Development] daweeze02:
LOL I just realized I've been running the uninstaller file each time.......doh!!!!!
[Nexus 5 Original Android Development] maisi:
Wasn't a lie, when searching for the exact error I can't even find my own post for some reason, should've searched for "gpu" , sry for that.

Thanks for the answer!
[Nexus 5 Original Android Development] erpalma:
Maybe yes, that could be related with dhcp lease time.

I can confirm a bug! Try to do a phone call and cover the proximity sensor. The screen goes off but you can terminate the call by pressing the touch. Am I the only one affected? Disabling S2W fix the problem.
[Nexus 5 Original Android Development] meatlocker:
Confirmed. Happens to me as well.
[Nexus 5 Original Android Development] Goggle81:
Yes
[Nexus 5 Original Android Development] Alpione:
Is there a way to measure the battery cost of s2w via BBS or something similar?

Thanks. This thread has been educational.

A
[Nexus 5 Original Android Development] FuMMoD:
That is a great question. I'm hoping to hear what OP has to say. I always wondered how to measure features in kernels.
[Nexus 5 Original Android Development] szucsgf:
I did a test on Mako and concluded that s2w drained approximately an additional 1% per hour. What I did:

http://xdaforums.com/showthread.php?p=46770758

http://xdaforums.com/showthread.php?p=47074261#post47074261

This is the best I came up with. Easy to replicate if anyone wants to do for Hammerhead.
[Nexus 5 Original Android Development] Emilius:
That is exactly what I got. Usually over to night (6-7 hours) battery drain is 2-4%. with s2w is 8-12%. To bad, I really like s2w function.
[Nexus 5 Original Android Development] show-p1984:
S2W itself does only use a very very very small fraction of a percent from your battery.

The main battery eating is coming from the always-awake digitizer, and on the n5 we have an additional tradeoff because we still have some power drain from the display controller.

There is no way to track that usage except setting up a test environment and doing some overnight tests.
[Nexus 5 Original Android Development] Alpione:
Agreed. When I get my wireless charger I may work more with it since it'll be useful for "at a glance" info on the charger. I may play around further when "double tap 2 wake" shows up.

A
[Nexus 5 Original Android Development] digweed4me:
has any of you change the dpi from rom toolbox pro mine is not working ?

how to activate swipe to wake features ?
[Nexus 5 Original Android Development] Starymari:
You need to make sure that your superuser is updated, I was having issues when I needed to update. Try it and see if that helps...
[Nexus 5 Original Android Development] NineInchNails:
Is search broken on XDA?
[Nexus 5 Original Android Development] Custodian:
Its not working for me either using tapa. Welcome Nineinchnails!!! Glad you have the device!
[Nexus 5 Original Android Development] show-p1984:
That just gave me an idea. Auto-enable s2w when we are charging?
[Nexus 5 Original Android Development] fatappel:
cdc15b8 with s2w enabled - proximity sensor won't wake up automatically when in-call and removed from ear. Other that that, it's pretty cool

Sent from my Nexus 5
[Nexus 5 Original Android Development] show-p1984:
I can make you a video, works perfectly for me. (I also see no reason why it shouldn't)
[Nexus 5 Original Android Development] akaHardison:
The newest version KControl has lots of FC.And I don't know why sometime it can't save my voltage setting.It's annoying.I think you can improve it.Try to learn from Android Tuner.It is easy to use.And it can save my profile(that is the point).
[Nexus 5 Original Android Development] more2come:
I am having one problem: when I'm setting custom mpsecision settings, they reset themselves after a few seconds. I'm using KControl, is it app related or kernel related?
[Nexus 5 Original Android Development] show-p1984:
No comment except: KControl is far from finished.

If you get lots of FC then why the hell says Google there were no crashes reported?

REPORT THEM.

Otherwise they will never get fixed.

Btw:

I am working on KControl on the side (Believe it or not, but my kernel requires a lot of coding since I am not only picking features from other people 'showify' them and pass them of as mine, like other devs do.) and it still can do a hell of a lot more than other apps, even way more expensive apps.

Depends, give me a log from kcontrol while setting those and they are reset:

adb logcat | grep de.bricked.kcontrol -C10

and a:

cat /sys/kernel/msm_mpdecision/conf/*

Once when you set your settings, and once when they have reset.
[Nexus 5 Original Android Development] akaHardison:
OK,but why I can't save the voltage setting after reboot?But other setting can(like mpdec)

Edit:right now I can't save any settings.
[Nexus 5 Original Android Development] show-p1984:
I would guess the BootupHandler crashes on some part of the applying process, hence only those that were already processed get applied.

Or you forgot to enable the onboot options in the Settings.
[Nexus 5 Original Android Development] Alpione:
Sounds good. Wish they still sold the Nexus orb so the phone would sit in a better position.

I'll do some testing tonight on idle battery drain with s2w just for kicks.

A
[Nexus 5 Original Android Development] akaHardison:
Report back:No FC anymore ,and setting apply and save after flashing stable 17th kernel back and wipe cache and dalvik.Everything seems fine.

The newest beta kernel seems just adjust the touch for s2w right?I just waiting next stable version.Waiting more fix.Because I don't need s2w.
[Nexus 5 Original Android Development] helloworld1:
s2w works like magic! I will test the battery drain.

Thank you for the hard work!
[Nexus 5 Original Android Development] FuMMoD:
I can't seem to get my swipe to sleep to work. How is everyone else doing it? Only on the lockscreen correct?
[Nexus 5 Original Android Development] fatappel:
It's weird. I can not recreate for video but it happened to me twice today during calls. I'll play some more.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Citizen_Snips:
Nah, it works anywhere. For me it does. Here, use this crude drawing I made you. It should help.

Sent from my Nexus 5
[Nexus 5 Original Android Development] FuMMoD:
Yes! It works perfect! Thank you!
[Nexus 5 Original Android Development] resynx:
Hehe thanks for the smile!! :D Love the drawing :victory::highfive:
[Nexus 5 Original Android Development] show-p1984:
KControl update inc, fixes bootup crashes with scheduler settings to be applied, false negative of the scheduler compatibility check and accounts for the changed s2w version file name.

new bricked beta adds dt2w. (aka knock knock)

Enable over sysfs: echo 1 > /sys/android_touch/doubletap2wake

[youtube]S2Q3hRSSRak[/youtube]

Now I put not much time in the algorithm itself, so there may be bugs.

However, test test test test test test test it.

Build is running :)

http://buildmachine.zapto.org:88/projects/10/builds/e14f7d41fecabf9e7b4b7153cdae22269cf199c7