yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] fuzzyAI:
I think I found the reason. It wasn't just swipe, a single touch would wake the screen, no matter how long you leave it alone.

I went to Semaphore Manager and see that the touchwake is OFF & dt2w is ON. Turn OFF dt2w (touchwake is still OFF) and I can still wake with single touch. Turn touchwake ON and then OFF again, voila, no more single touch.

I don't know how the kernel could messed up the setting, because I turn OFF touchwake ever since I have dt2w ON and dt2w was working just fine and until some unknown moment.

Will report back if this ever happen again.

### Edit 1:

I found the reason now. With touchwake OFF, dt2w ON and Disable touchwake during call ON, normally it would behave like intended. Once you pick up a call, the whole screen can be single touch wake.

Can anybody reproduce ?
[Nexus 4 Original Android Development] "D":
Hi,

Stock 4.4.2 odex ?
[Nexus 4 Original Android Development] stratospr:
I have the same problem (the phone wakes with a single tap). I can reproduce it and confirm that it happens after you pick a call...

I'm on latest omnirom with 2.0.1 test version
[Nexus 4 Original Android Development] stratosk:
Please disable the option "Touchwake disable" in Semaphore Manager if you don't use touchwake.

This option will disable touchwake during calls and will re-enable it after call end.
[Nexus 4 Original Android Development] fuzzyAI:
Already did this. Dont you think the "Disable touchwake during call" option should be disable if user turn off Touchwake ?

It's very easy to miss since I first try touchwake and think of it as a subcondition of touchwake enabled.
[Nexus 4 Original Android Development] stratosk:
I will try it.
[Nexus 4 Original Android Development] dmourao:
I'm getting about 1.3%/h in idle time with dt2w ON. Is it about the right number?

Been using it for 2 days, no problems till now.
[Nexus 4 Original Android Development] stratosk:
I haven't run any test for battery drain, but it seems ok to me.

Did you test your consumption without double tap?
[Nexus 4 Original Android Development] Psichi:
I would kill for 1.3%/h. I am usually in the 4-7%/h due to some wake lock that I have yet to track down.
[Nexus 4 Original Android Development] snak3ater:
With no major wake locks and good signals...1% drop per hour is normal...1.3% is okay with dt2w turned on..
[Nexus 4 Original Android Development] dmourao:
I'll test this night with dt off and report tomorrow. :thumbup:
[Nexus 4 Original Android Development] stratosk:
New version 2.0.2

- Linux kernel 3.4.77

- Reworked double tap to wake functionality
[Nexus 4 Original Android Development] twowheeler:
Yay. Turned out this was the perfect timing to check xda. Flashing now.

Don't think I will use double tap, I'm rather a fan of touchwake. But damn, I admire how you made it work. Superb! Keep up the good work.
[Nexus 4 Original Android Development] fr3quency:
Νταξ... ότι θα έβρισκα Έλληνα με γαμάτο κέρνελ δεν το περίμενα, πραγματικά!

Keep up the awesome work, cheers!
[Nexus 4 Original Android Development] Arju:
Just å Quick question. When you say you reworked dt2w functionality, are there any different changes in the dt2w in v2.0.2 vs v2.0.1?

And thank you again!!
[Nexus 4 Original Android Development] jimyiak:
Αν θέλουμε.. Είμαστε καλοί... Gonna flash and report!!

neXus⁴ running kitkat 4.4.2
[Nexus 4 Original Android Development] qtekker:
Thank you for your efforts.

I have a question. Everybody is talking bout double tap. But my phone always wake up with single tap. In all versions. How come?
[Nexus 4 Original Android Development] Rohit02:
i think that what it is called Touch to Wake.? :confused: ;)
[Nexus 4 Original Android Development] stratosk:
Just a commit, that tries to resolve issue with unresponsive touchscreen.
[Nexus 4 Original Android Development] stratosk:
Please disable touchwake in "Tweaks" tab and "touchwake disable" in SAI tab.
[Nexus 4 Original Android Development] qtekker:
Thanks! I didn't know that double tab conflicts with touchwake.
[Nexus 4 Original Android Development] bankgg:
Just upgraded to 2.0.2 with faux sound version (Jolie) after it's released a bit. Until now, I have 2 unresponsive screen issues when using d2tw. Just a report :D
[Nexus 4 Original Android Development] gialakias:
No problems here with the version 2.0.2. Works great.
[Nexus 4 Original Android Development] Arju:
Would be very useful if you managed to get a last_kmsg file from your phone when your screen started getting unresponsive so that it would be easier to track down what's causing the unresponsiveness.
[Nexus 4 Original Android Development] stratosk:
Please report the issue to the respective thread.

I can't be sure if the issue is due to Semaphore, or due to wrong merge to Jolie kernel or conflicts or something else.
[Nexus 4 Original Android Development] ephumuris:
Loving this kernel and the double tap to wake. Set up with double tap to sleep too. Really happy and surprised the Semaphore app is free! Just wish I knew how to undervoltw
[Nexus 4 Original Android Development] Gu$houn*:
Post #2 of this thread provided by [MENTION=3750240]stratosk[/MENTION]

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] snak3ater:
The great thing is that dt2w is working only by tapping in the middle of the screen..Now my phone does not wake up by itself while inside pocket :good:
[Nexus 4 Original Android Development] dmourao:
Without dt2w, from 96 to 94 in around 9 hours.

View attachment 2534162
[Nexus 4 Original Android Development] snak3ater:
And what happened after 9hrs when you started using your phone?

A sudden drop of 5-6%?
[Nexus 4 Original Android Development] dmourao:
It's 9:36 now, I'm on 3G and it still 92. No drop.
[Nexus 4 Original Android Development] Arju:
Have you made any changes in the kernel settings?
[Nexus 4 Original Android Development] dmourao:
Just noop to cfq, other then that all default.
[Nexus 4 Original Android Development] Arju:
Awesome! Would be interresting to see how much SOT it would give with heavy usage. Guess I'll test it out some day I have time.
[Nexus 4 Original Android Development] chavocarlos:
Yesterday at night with 2.0.2 version I had my first unresponsive screen, double tap didn't wake the phone, only power and volume buttons (I use Gravity Box). It waked with power button and received notifications, but the screen never responded, long pressing the power button showed the power options but can't select anyone. I had to restart the phone with button combinations.

Swype in status and navbar doesn't work too.

My phone had been without use about one hour, before that d2tw worked perfectly.

PD: Sorry my english.

Regards [MENTION=3750240]stratosk[/MENTION]
[Nexus 4 Original Android Development] snak3ater:
It's strange to see many people complaining about screen unresponsiveness..Been using the test version and now 2.0.2...No issues so far.

I wonder what makes the screen unresponsive..I don't use xposed btw..
[Nexus 4 Original Android Development] chavocarlos:
Yes, for me is strange too, but more strange is how you don't have any issues, really I tried disabling all Xposed modules, but never tried uninstalling Xposed ... anyway [MENTION=3750240]stratosk[/MENTION] few pages back posted that he experienced one time this issue, and he doen't use Xposed too.

I am not complaining nothing, only feedback to [MENTION=3750240]stratosk[/MENTION] in case he find helpful my comment.
[Nexus 4 Original Android Development] snak3ater:
You are not the first one..I see more people having same issue..I will keep on using 2.0.2 and see if i get any issue like that
[Nexus 4 Original Android Development] rogers11:
Also no problems here since yesterday evening. And I use Xposed.
[Nexus 4 Original Android Development] chavocarlos:
I want to provide a log, just in case this issue appears but in terminal emulator logcat shows "unable to open log device", I have logger module activated in Semaphore Manager, something seems don't work.
[Nexus 4 Original Android Development] karthi89:
But the default is cfq isn't it?
[Nexus 4 Original Android Development] Mercado_Negro:
No, default is no-op.
[Nexus 4 Original Android Development] dmourao:
Same here :good:
[Nexus 4 Original Android Development] stratosk:
I can't reproduce it and it didn't happen to me again, but I guess the bug is still there.

A small tip until I fix it:

When it happen again, turn on the screen with the power button the touch the screen with 10 (yes ten) fingers and then release. :)
[Nexus 4 Original Android Development] snak3ater:
I used to do it in Touch Control App...I had this screen unresponsive issue in Touch Control...

Touching the screen with all fingers solves this problem..Screen comes back to life again..
[Nexus 4 Original Android Development] chavocarlos:
Not in my case, I just turn on d2tw (and turn off touch to wake) when [MENTION=3750240]stratosk[/MENTION] suggestme the 10 fingers trick. Now the screen is unresponsive again and 10 fingers trick don't work :silly:.

I tested putting my 10 fingers after and before turn on the screen with power button.

Update: Screen come back to life when long tap ONE finger, and swipe other finger beside it. :)
[Nexus 4 Original Android Development] WiwiPouPou:
[MENTION=3750240]stratosk[/MENTION], what is the default GPU gov ? On Hellscore in trickster we can see the freq going back to 27mhz when idling, on Semaphore it stays on 320Mhz, even scales up to 320 on idling if was below...

Is that a misreading from trickster ? Thanks for your amazing work !

Example : open Trickster in info, just idling a little = scale to 320

Play with the screen up and down : 128MHz

Idling again : 320

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] snak3ater:
10 fingers was just an example..The point is that keep on tapping the screen with many fingers :p

Yet to see that issue in dt2w but this trick alwaysworked for while using TC app..

Don't know the reason but Semaphore was the only kernel which had screen unresponsive issue with TC app...Kernel itself is fine..Something was wrong with TC...Now Dt2w showed up and brought same issues with it..Still i use it because i really like this feature :D

---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------

Default Gpu Gov in Semaphore is ondemand..There is no conservative or simple Gpu gov in Semaphore..
[Nexus 4 Original Android Development] chavocarlos:
Me too. I will keep using d2tw while the trick works.
[Nexus 4 Original Android Development] WiwiPouPou:
Yep thx, but it doesn't means that idle freq had to be 320Mhz !

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] snak3ater:
idling freq is 320 in Semaphore..Yeah just saw in trickster..But it is 320 in other kernels as well..eg Matrix

It might be trickster app bug
[Nexus 4 Original Android Development] WiwiPouPou:
Yes, that's what need to know, hellscore idle at 27MHz, it's not magic, maybe it's just a setting ?

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] thracemerin:
The stock idle frequency is 320, that's the frequency displayed when the GPU is asleep and is 100% normal. Hellsgod changed it in his kernel.
[Nexus 4 Original Android Development] snak3ater:
Might be because of the different Gpu governor used in Hellscore..No other Kernel does scaling like Hellscore
[Nexus 4 Original Android Development] chavocarlos:
An update, this trick does the work, but kill (or lock) the swype feature in Android, LMT launcher don't work, and swipe left menu in Play Store too. ... but I will keep d2tw! :D
[Nexus 4 Original Android Development] WiwiPouPou:
That's strange no ? Why dont scale down, and worst why scaling it up ?

I really would like to read an explanation ! :) Just curious, what could be thé benefit ?

Scaling it down is that the secret of hellscore for biggest SOT ?

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] thracemerin:
if its idle it goes into power save mode which is similar to being hotplugged off, the power usage is extremely minimal.
[Nexus 4 Original Android Development] WiwiPouPou:
Even when on 320 MHz ?

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] thracemerin:
yes, if its idle it goes to 320 before going into powersave,
[Nexus 4 Original Android Development] WiwiPouPou:
OK thanks, good to know !

Hellsgod (again) just ported LoUIs API for L2 cache to reduce cycle waste cpu cycles when hotplugging (correct me if im wrong), when i search for it i found doc from 2012, so any chance we got it already ? :)

Envoyé depuis mon Nexus 4 avec Tapatalk 4
[Nexus 4 Original Android Development] stratosk:
Hello my friend!

It will be nice to have you in this forum!

N4 is an awesome device.
[Nexus 4 Original Android Development] Anubiszx:
Hi, first of all, thanks for your work! I've been following you since two years ago with my SGS and your fantastic kernel :).

I have two questions for you guys.

Is Light Manager working for you?

Is it normal that the LED turns red almost with everything? Like when using chrome to charge a webpage, or opening almost any app that makes the phone work a little...

I'm in the stock ROM with this kernel and no other tweaks.

Thanks in advance.
[Nexus 4 Original Android Development] stratosk:
The thermal trigger works in the range 47 - 62 degrees. And yes, CPU temperature gets high pretty easily.
[Nexus 4 Original Android Development] eep2378:
Led trigger for thermal sensor I think is a great little piece of code. Opens up many possibilities for further tweaking :D 0.7 is running flawlessly ATM. Thanks :)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] francoislefrancais:
Hello, i'm using you kernel since some day and decided to download the app but can someone explain how work touch wake and what is touch screen filters and SAI (pickup phone) :confused:

And i don't understand these new things

My led become sometime red since I flashed 0.7 today

"- leds: Do not remove trigger when brightness = LED_OFF (fixes conflicts between LED trigges and notification lights)

- touchwake: Introduce new LED trigger (name touchwake) that switch on LED when the touchwake is active.

- leds: Add LED trigger for thermal sensor (switch on LEDs when temperature >= 47, with brightness proportional to the temperature)

- mako: Use default triggers: Blue - touchwake, Red - thermal, Green - battery full

- more clean ups to config (remove tracers, KALLSYMS)

LED triggers is a kernel API that helps to handle LEDs and match standard actions with a specific LED.

We have a nice RGB LED and I consider that we can use it a little bit more than the standard notifications.

We can use LED triggers for mmc controller, when battery charging or full etc.

I will also do some work in Semaphore Manager to handle LED triggers."
[Nexus 4 Original Android Development] chago123:
stratosk are you planning to add UV feature on your next release?
[Nexus 4 Original Android Development] stratosk:
Touchwake: keeps the phone awake (screen is off) for small period. When you touch the screen, the phone awakes. It works only if the screen goes off due to inactivity.

Touch screen filters: as the name says, filters for the touch events. They are disabled by default (as in stock kernel). You may experiment with different values.

SAI - pickup phone: it tries to answer the phone when it is ringing. When the phone is ringing a service will 'pick it up' as soon as you put the phone near your ear.

It's just use of RGB LED for different events. When the touchwake is active the blue led will be switched on, when your phone exceeds a temperature the red led will be switched on and finally the green led when the battery is full.

I'm sorry no plans for OC/UV
[Nexus 4 Original Android Development] BlueFlame4:
It might be a good idea to set up a FAQ in the second post, stratosk :D I keep reading all those questions over and over again :>
[Nexus 4 Original Android Development] stratosk:
Yes, you right. In my TODO list. :)
[Nexus 4 Original Android Development] ore616:
SEMAPHORE...... So good to see you here mate.

Giving this a good run as I loved your previous work. Thanks again :)
[Nexus 4 Original Android Development] stratosk:
New version 0.7.5

- Linux kernel 3.4.44

- leds: Switch off LED when thermal trigger deactivated

- Change some compiler flags (hopefully little bit better performance)

- Remove many ugly debug messages in WiFi driver, and a message in charger driver.
[Nexus 4 Original Android Development] reginickneo:
Red LED isn't disabled by default in 0.7.5 version.
[Nexus 4 Original Android Development] TRSolebum:
...true...

but it will switch off, when you disable the thermal trigger...which didn`t work in 0.7 ;)
[Nexus 4 Original Android Development] Fabio3105:
ok, and how i can disable the thermal trigger??
[Nexus 4 Original Android Development] TRSolebum:
Terminal Emulator:

su

echo none > /sys/class/leds/red/trigger

that`s it :)
[Nexus 4 Original Android Development] Fabio3105:
i'm sorry, but i don't understand because i never used terminal emulator...

how do i do??

can you tell me please?
[Nexus 4 Original Android Development] Sanael:
I try a second time. (:

---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------

Open the terminal.

Paste the first line. Enter.

Paste the second line. Enter.
[Nexus 4 Original Android Development] TRSolebum:
sure, just install Android Terminal Emulator from Google Play

open the app

type "su"

press enter -> grant Superuser rights to Terminal

type "echo none > /sys/class/leds/red/trigger"

press enter
[Nexus 4 Original Android Development] Fabio3105:
perfect, thanks so much...

at the end of the second enter i type exit twice and the app is closed. is it right?
[Nexus 4 Original Android Development] Elting:
And after a reboot I have to do it again?
[Nexus 4 Original Android Development] hellsgod:
I haven't ported it, just picked ;)

hells
[Nexus 4 Original Android Development] fuzzyAI:
Is there any benefit of having min frequency = 192Mhz ?

I saw alot of kernel going below 320Mhz, and always wonder why stratosk keeping 320 on his kernel ?

# Quick note: no unresponsive screen on 2.0.1 for two day since the last problem. Just flashed 2.0.2 ^_^
[Nexus 4 Original Android Development] :
From my understanding,

320 provides a more fluid response and performance ,especially when waking the device.

192 has the tendency to possibly be more power efficient (more battery friendly), but you sacrifice that with a slight decrease in performance on wake-up.

It all depends on how the developer implements the behavior, the kernel settings the user configures, and how the user uses his or her phone.
[Nexus 4 Original Android Development] stratosk:
GPU and CPU freqs will remain stock on Semaphore.

I can't see any benefit for reducing min freq on CPU

If GPU is in sleep state, current frequency doesn't have any affect.

I don't know why the stock driver changes freq to 320 before sleep, but maybe there is a reason.
[Nexus 4 Original Android Development] Arju:
Just have to say after testing v2.0.2. DT2W is working perfectly as I want it to and as mentioned by someone before it works by tapping in the middle of the screen and not all over the place. Now I don't need to be concerned for my clumsy fingers turning the screen on, on its way into my pocket.
[Nexus 4 Original Android Development] ihancioglu:
Hi everybody,

Anybody needs to sleep the device with gesture, you can install JB LockNow in the playstore.

https://play.google.com/store/apps/details?id=jp.iggy.android.jblocknow

This will turn google now gesture to Lock device. It is very handy for who is using stock rom. :good:

Thanks,
[Nexus 4 Original Android Development] xflori:
What are the best settings for a long battery?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] Coolgoly:
I'm happy with interactive (hi speed freq 1134 ,go hi speed load 93) + deadline + undervolt 137,5 for all.
[Nexus 4 Original Android Development] snak3ater:
Max cores 1...interactive governor..max cpu speed 384mhz..best battery life :thumbup:
[Nexus 4 Original Android Development] musa47:
What? Max 384mhz? :P troll much?
[Nexus 4 Original Android Development] snak3ater:
Yeah.. Best battery life with these settings.. But no guarantee about performance :D

Try these settings and start reading a book on your phone.. When battery dies.. take battery stats screen shots & post it in battery impression thread.. best way to showoff :p
[Nexus 4 Original Android Development] Gu$houn*:
You forgot the airplane mode, important too ... :D

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] ZioGTS:
[MENTION=3750240]stratosk[/MENTION], since the introduction of DT2W feature, the activity indicator in battery stats screen is broken. No activity detected anymore, even when screen is on and I'm using the phone or making a call. The activity bar stays black. Did a clean install of latest Purity and Semaphore, activity stopped being detected as soon as I enabled dt2w in Semaphore manager app. Disabling it afterwards does not restore activity bar functionality. Here's a screenshot:

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] yak84:
The problem on purity side not semaphore.
[Nexus 4 Original Android Development] Italico:
SlimKat 2.4 Beta and Semaphore 2.0.2 here, everything shines.

Only a thing, StratosK, I have visible but unoffensive screen flashing during reboot or shutdown. Seems everything is fine, thought

Inviato dall'Ombelico del Mondo
[Nexus 4 Original Android Development] stratosk:
Weird issue, my friend.

But everything seems normal on my side (stock ROM).
[Nexus 4 Original Android Development] Gu$houn*:
It's on ROM's side, purity has now this weird "feature", your kernel is simply flying ...

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] ZioGTS:
On Purity side they say it's kernel related... I guess I'm stuck between a rock and a hard place.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Gu$houn*:
Weird, I have been using two kernels with purity today /franco -> jolie, flashed over stock/ and on both it was/is there ... but I think it is no biggie, some non crucial thing is not working properly, what ever ... ;)

P.

EDIT//

both kernels in one screen /the spots are recovery/rebooting I think/
[Nexus 4 Original Android Development] chavocarlos:
I disabled LMT launcher and I didn't have any issues in last 12 hours, it's weird but I think that LMT launcher is creating some conflict.

When the screen back to life after unresponsiveness, LMT launcher stopped working.

Today at morning I unchecked "Autostart service" in LMT, and restarted the phone, d2tw keep working well but can't start LMT service manually. It's weird.
[Nexus 4 Original Android Development] stratosk:
I'm sorry for your issue, my friend.

Obviously there is a conflict. But I can't reproduce it to resolve it (or find out what's going on).

As I said on stock seems OK.
[Nexus 4 Original Android Development] rogers11:
No, not really. I'm on stock (with Xposed) but the "problem" exists also here.

The screenshot from 15:38 shows the graph after unlocking with double-tab. No activity shown.

The screenshot from 15:39 shows the graph after unlocking with the power-button. Activity is shown (including the formerly missing activity from 15:38).

No major problem because it repairs itself.
[Nexus 4 Original Android Development] ZioGTS:
In my case it does not "repair itself"... :(

Anyway, thanks for your reply [MENTION=3750240]stratosk[/MENTION] !

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] stratosk:
I'm not sure if this an "issue" or you just need to refresh the battery statistics page.
[Nexus 4 Original Android Development] ak:
Because the GPU freq reported by the kernel isn't correct.

There is a fix made by [MENTION=4152171]myfluxi[/MENTION] for this problem.
[Nexus 4 Original Android Development] artifex21:
Its a bug introduced with some new cm commits...
[Nexus 4 Original Android Development] dmourao:
Stock with dt2w, xposed and GB, everything seems to be fine here.

View attachment 2536753