yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] redvw74:
I'm running semaphore from the first versions. It's my favorite kernel. Can't help it.

Didn't have any serious problems with dt2w implementation. Only sometimes when I wanted to end a call my screen went black and couldn't terminate it. Eventually the call terminated by itself.

After testing some days the latest test kernel I don't have that little issue anymore.

Thanks for your continued work and effort, all those months, Στράτο!

Στάλθηκε από το Nexus 4 μου χρησιμοποιώντας Tapatalk
[Nexus 4 Original Android Development] earlgrey_44:
DT2W

If I'm interpreting the above quote correctly, some devs are concerned that Stratosk's approach to DT2W burns too much battery. (If I'm misunderstanding, somebody jump in please.)

I did another "battery drain when phone sleeps" observation with DT2W on last night. Total average battery drain was about 1%/hr on my configuration.

Now that I've fixed my flash-damaged installation, :rolleyes: , my standby drain is about half what it was before, and well within the range of acceptability. No evidence here that any major battery drain results from this DT2W implementation.

As far as I can see, more good news for 2.0.4.
[Nexus 4 Original Android Development] ihancioglu:
I have some data about battery consumption with DT2W.

from 23:00 to 07:30 - while I am sleeping ; (All tests exactly same setup / Stock rom)

show-p's version (I was used it at thracemerin's kernel) was %4

First versions of Statosk's was %6

Stratosk's reworked at 2.0.2/3/4 was %3-4

So If you compare it with show-p's version , I don't think it drains more.

Also there are so much bugs in showp's version. First double tap attempt not working mostly, I was plug in charger while screen off, touch screen was unresponsive..

on 2.0.4, DT2W looks stock feature, everything as it should..

Thanks.
[Nexus 4 Original Android Development] "D":
[MENTION=3750240]stratosk[/MENTION]

it is sooooooooooooooooo good :D (2.0.4)

big thanks my friend.

best regards from Germany.
[Nexus 4 Original Android Development] stratosk:
If we are talking about double touch to wake, there are no "listeners" in the kernel.

I read _a lot_ about how to implement this functionality and I'm almost 100% sure that this is the correct method to do it:

1) Touch screen generates an IRQ and the touch screen IRQ handler starts the processing

2) We _have to_ hold a wake lock to process the touches and detect the double tap in the center of the screen

3) Wake up the device/kernel but a power key press/release simulation.

There is a small battery drain, but we can't do much about this.

LG uses an Atmel touch screen in LG G pad (and maybe in LG G2) that is capable to go to sleep. But our hardware can't do this.

So, we have to live with this battery drain if we want to use this feature.

At the end, I'm happy that I can wake up the device with double tap on every attempt. :)

Thank you for your tests!
[Nexus 4 Original Android Development] leninke:
I can't believe that.just f....ing perfect. you're the master stratosk.thank you
[Nexus 4 Original Android Development] Fremen567:
As for the battery life, my experience is that even with dt2w enabled I get better battery life than on the stock kernel. So even if this functionality drains a little bit of battery it's not a big deal, and I really enjoy using it.

Thanks a lot for all ur hard work man.
[Nexus 4 Original Android Development] stratosk:
New version 2.0.5

- Linux kernel 3.4.78

- input: lge_touch_core: Fix double tap to wake unresponsive touch screen issue

- cpufreq: interactive: Enable input boost by default
[Nexus 4 Original Android Development] jimyiak:
Αύριο ρεπό αρα Flashing day..148 hours up and everything great..i wanted to make it work flawless to use double tap to wake..strato why you don't use custom rom?το σκεπτικό σου πες μου.. ;)

neXus⁴ running kitkat 4.4.2
[Nexus 4 Original Android Development] stratosk:
1. I like stock ROM because I love simplicity.

2. I need a stable environment to develop Semaphore. I have to be sure that Semaphore works OK on stock ROM which is the base of all ROMs.
[Nexus 4 Original Android Development] dmourao:
Pretty good considering that dt2w was activated and used quite often. Let's see how far it will go!
[Nexus 4 Original Android Development] ephumuris:
I wish my battery life were as good!

On stock rom an average day i'd get 3.5 hours screen on time. (Bluetooth always on for my Pebble)

On ParanoidAndroid with semaphore i got 2 hours screen on. (Bluetooth always on and dt2w)

On ParanoidAndroid with semaphore 4 hours 15 minutes screen on. (Disabled bluetooth and disabled dt2w, 1.35ghz max clock and undervolted.)

So today my test will be PA with latest semaphore and bluetooth on all day for my pebble watch. No dt2w. See how i fare with that!

I really want to use dt2w though :)
[Nexus 4 Original Android Development] Arju:
As soon as I saw v2.0.5 I flashed it. It's working great so far. Will report back after some battery cycles. Thank you [MENTION=3750240]stratosk[/MENTION]!
[Nexus 4 Original Android Development] leninke:
I'm on latest omni,with dt2w, for me is perfect so.
[Nexus 4 Original Android Development] gregorypeg1000:
I just flashed the latest build after 500hours of uptime on version 2.0.0. This kernel is a stability and performance beast!!!
[Nexus 4 Original Android Development] in.abhi9:
If touch wake is enabled, is there any way to active it by setting any sys param?

I want to do something like, when some notification comes in, touchwake should be triggered by tasker
[Nexus 4 Original Android Development] Midomad:
Simply disable it and use dt2w ;)

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] in.abhi9:
LOL! I couldn't found anywhere and have to do like that
[Nexus 4 Original Android Development] stratosk:
Please use this command:

echo 0 > /sys/devices/virtual/misc/touchwake/enabled
[Nexus 4 Original Android Development] in.abhi9:
I dont want to enable or disable, but I just want to trigger it (so if i touch, it should wake up)
[Nexus 4 Original Android Development] themike10452:
that's what 'enable' means. Make your tasker push the command (echo "1" > /sys/...) to enable touch wake - so when you touch your phone it will wake up - when a notification is pending, and then echo "0" instead of "1" to disable it when there are no more notifications, or put it on a timer or something.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Original Android Development] in.abhi9:
Thanks for the reply,

I never want to disable it. It should work normal (when goes screen off, touch screen actives till specified delay)

So when new notification comes, screen shouldn't light up, but touchscreen should activate automatically till specified delay in semaphore manager. This can be done by the tasker, like to enable or disable we echo 1 or 0 but when It is already enabled and to active touch screen sensor, is there any param to set?
[Nexus 4 Original Android Development] themike10452:
one moment dude. Do you know how touch wake works? it only works if your screen goes off by itself after timeout. So if your phone is locked you can't wake it with touch to wake. You have to use double tap to wake which always wakes the device. You have to enable it and disable it after the notifications are gone. Touch wake will not do good for you.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Original Android Development] pyr0sphere:
View attachment 2548532

Phone didn't charge last night on 2.0.5 with double tap to wake on.

Woke up, turned it off, and it charged fine. Using a wireless charger

No wake locks during that time
[Nexus 4 Original Android Development] in.abhi9:
OK! Thanks anyway
[Nexus 4 Original Android Development] rogers11:
This must have some other reason. My N4 with DT2W on charged at home and in car today (v2.0.5).
[Nexus 4 Original Android Development] microMXL:
loved this kernel on my i9000, so I can use that 1.5.1 kernel on cm 10.2?
[Nexus 4 Original Android Development] stratosk:
I really don't remember what's going on, on those old version.

Reading the change log I would start from 1.5.5
[Nexus 4 Original Android Development] microMXL:
thanks mate, actually flashed 1.7.6 but colors look funny, gotta check in semaphore manager
[Nexus 4 Original Android Development] stratosk:
If you want to test this Semaphore Manager version, I would be happy to read your feedback. :)
[Nexus 4 Original Android Development] stratosk:
It's incompatibility with CM. I don't remember in which was the last Semaphore version that worked OK. (Please start from 1.5.5)
[Nexus 4 Original Android Development] Arju:
Works great! I like the revamp of the menu structure. Kinda integrates with the kitkat design of style Google is going for. Thank you for the app!
[Nexus 4 Original Android Development] Italico:
Thanks for the app, Statosk. Just a suggestion, on dark theme the left bar background color is too light to be readable. The font color instead is ok and will be even with darker surroundings

Inviato dall'Ombelico del Mondo
[Nexus 4 Original Android Development] jpmccarthy:
+1 on that :)
[Nexus 4 Original Android Development] Midomad:
Look very nice :thumbup:

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Gu$houn*:
I second that, hard to read but otherwise great job [MENTION=3750240]stratosk[/MENTION] it looks very nice!!!

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] myfluxi:
You are wrong, the devs are wrong. Research KGSL_STATE_SLUMBER.
[Nexus 4 Original Android Development] a g bell:
Going to ask a noob question but how can make all 4 cores scale up at the same time using cfq and ondemand ?

It goes with out saying l have disabled hotplug driver already

Sent from Tapatalk
[Nexus 4 Original Android Development] capoooro:
Nice The new manager... Google style

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] racerboy3801:
Is anyone here experiencing lock screen freezes? I've tried multiple roms and the issue still persists.

Cheers
[Nexus 4 Original Android Development] pyr0sphere:
Does touch input just stop working? I've had that too but wasn't sure if it was Viper4android doing it or the new kernel. Installed both yesterday
[Nexus 4 Original Android Development] lilgiz:
I like the addition of the kmsg logging, but I would definitely prefer that you keep the ability to swipe between pages. Trickster tried removing the swiping a few months ago and received tons of negative feedback. They ended up adding it back, while keeping the new menu functionality.
[Nexus 4 Original Android Development] racerboy3801:
Yeah touch-screen completely stops working. A reboot is required to fix it. I don't have V4A installed, so i'm guessing it's not that. I've tried 2.0.5 on both omni (latest nightlies) and aospa b.4 and it happens with both roms.

Maybe it's related to double-touch to wake, i've had it enabled the whole time.
[Nexus 4 Original Android Development] pyr0sphere:
Me too for double touch to wake. Looks like I can turn Viper back on and turn off Double Tap for now
[Nexus 4 Original Android Development] racerboy3801:
I'll disable dt2w for a few days and see if the issue persists.
[Nexus 4 Original Android Development] themike10452:
The new sema manager looks good :good:

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Original Android Development] stratosk:
I'm not sure about this. It's definitely an ugly back to do this. There is no reason to keep both navigation drawer and swipe tabs. The point is that with the new design, I have more possibilities to expand the UI.
[Nexus 4 Original Android Development] stratosk:
I'm not sure, I understood your question.

What do you mean that you want your cores "to scale up at the same time"?
[Nexus 4 Original Android Development] themike10452:
guys could anyone test this gamma profile and let me know what you think?

255 255 253

0 39 103 1 3 0 2 0 1

Thanks.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

I got first problem with DT2W on 2.0.5. Double tap does not wake up the device. Once wake up the power button then continue to work.

I have attached dmesg.

Thanks,
[Nexus 4 Original Android Development] yak84:
OT

Hi guys a little question, where are the thermal control files location?

rom @ system, kernel @ ramdisk?

I'm asking because I wanna know if flashing stock boot.img reverts modifications made to thermal control by another kernel.
[Nexus 4 Original Android Development] stratosk:
Hi my friend!

Thanks for the log.

I found this line:

<3>[ 1613.575522] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

And looking the touch driver code:

/* IC bug Exception handling - Interrupt status reg is 0 when interrupt occur */

if (ts->ts_data.interrupt_status_reg == 0) {

TOUCH_ERR_MSG("Interrupt_status reg is 0. -> ignore\n");

goto err_synaptics_ignore;

}

So, it means that we have a bug there. As a workaround the only solution is to restart touchscreen (this is why the problem was resolved as soon as you used power button).
[Nexus 4 Original Android Development] a g bell:
Umm how to explain ok 4 cores at 384 then 2 stay 384 and 2 scale up to whatever for example say 1026 can l set all cores to go up at the same time everytime so all cores run at same frequency
[Nexus 4 Original Android Development] Targaeryan:
Its pretty good. Not as punchy as halfbreed but brings out the colors well. Have you tried bundi's settings?
[Nexus 4 Original Android Development] M@rs:
Can you pleas post bundis iphone colours in semaphore Format? Or how to convert from other formats, thanks.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] stratosk:
Why do you want this?

In every core kernel may schedule a process. If there is 1 process that have to run, kernel will schedule it to 1 core. Pushing freq to other CPUs will not speed up the processing.
[Nexus 4 Original Android Development] Targaeryan:
https://www.dropbox.com/s/iz6eor7gu8aa6cm/franco_semaphore.xls

---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------

Try this one. I think I sent a diff link.
[Nexus 4 Original Android Development] a g bell:
Ahh ok thankyou so it would be pointless because each process is scheduled to one core l learn something:)

But if l have all cores running a process at say 1026 and then another process is scheduled to a core that core is running 1026 already would that not be good?

Sorry if this makes no sense still learning:)
[Nexus 4 Original Android Development] yak84:
bundi_vivid- 0 87 119 1 6 0 1 0 1

bundi_iphone5-0 39 119 1 6 0 2 0 1

Enjoy.
[Nexus 4 Original Android Development] alen1901:
Hey stratosk, one question, is it possible to enable cpu oc in your kernel just with editing some file in system or compiling is needed. I remembered i saw on galaxy s2 long time ago, guy just added frequency to some CPU freqs list file and he got oc. Just wondering if thats possible here. Thanks.

Sent from Pure Nexus⁴
[Nexus 4 Original Android Development] chrisgtl:
Can anyone give me default semaphore settings for the latest 2.0.5?

Governor -

Up Threshold -

Scheduler -

SD Read Ahead -

Thanks.
[Nexus 4 Original Android Development] ihancioglu:
You are welcome. As I understand It is the bug in touch driver code, so nothing you can do, right?
[Nexus 4 Original Android Development] themike10452:
yes I have, I find this one better, it's a new preset by [MENTION=3973516]mohitgalaxy3[/MENTION] which I changed a little.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Original Android Development] stratosk:
Keeping all cores at high frequency waiting for a process to be scheduled is very power inefficient.

Hi,

No, it's not possible. Changes in the kernel are required for OC.

Default gov: ondemand. Up threshold 95.

scheduler noop, sd read ahead 128

Yes, it seems a stock issue. The comment in the code is from stock code.
[Nexus 4 Original Android Development] lilgiz:
Thanks for your reply. That makes sense especially considering the possibilities to expand. I guess the main reason I prefer swiping is that in it's current state I spend the majority of my time on either the cpu tab or the tweaks tab. Since I'm just dealing with 2 tabs, it's more efficient for me to just swipe between the tabs. Either way, which ever direction you go, I'll support your decisions. :thumbup:
[Nexus 4 Original Android Development] kridster:
Having the same problem. Unlocking the device with dt2w is working, as well as the hardware buttons. After that, touchscreen doesn't response at all and only a reboot fixed it.

Only dt2w enabled.
[Nexus 4 Original Android Development] rogers11:
Strange that DT2W works perfect on my device but not on yours.
[Nexus 4 Original Android Development] nemanja066:
Use stock ROM and will be all OK. I doesnt have any problem with kernel. :)
[Nexus 4 Original Android Development] dmourao:
Same here, no problems at all.
[Nexus 4 Original Android Development] themike10452:
Absolutely 0 problems with touch, blazing performance, satisfying battery life. Great job. No negative comments at all.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Original Android Development] leninke:
Latest omni, latest semaphore and everything is absolutely perfect here.
[Nexus 4 Original Android Development] max4wdc:
i have flicking sometime with this kernel but when i use AK kernel i don't have problem , anyone have this problem ?
[Nexus 4 Original Android Development] myfluxi:
Don't know if this is related but you can catch all errors with a little hack if store_ts_reset() is still there today (I left the N4 some time ago): https://github.com/myfluxi/android_kernel_google_msm/commit/cec9539e1dff8f3b7b821b29cc554ab33ca080f2

store_ts_reset(ts, "soft", 0);
[Nexus 4 Original Android Development] carlos67:
Quick question:

I don't use DT2W or Touch wake with semaphore v2.0.2. Is there any good reason to update to latest v2.0.5???

I mean all the latest revisions after 2.0.2 were to refine DT2W weren't they?

Thanks :)
[Nexus 4 Original Android Development] Wassupdog:
This kernel is designed for good battery life?

I'm now with another kernel and PA 4.0 Beta 4 and battery life are max 2:30hrs of screen On the Nexus 4.

Is that kernel has better battery life?

Thanks!
[Nexus 4 Original Android Development] stratosk:
Thanks for the info.

I already do something similar. The problem is that you can't wake the device with double tap but you need to use the power button.
[Nexus 4 Original Android Development] stratosk:
2.0.5 also includes latest Linux kernel update to 3.4.78.
[Nexus 4 Original Android Development] Wassupdog:
Would you please reply to my question? (in quote above).

Thanks!
[Nexus 4 Original Android Development] snak3ater:
Semaphore is a good balance of battery life and performance..

Ps: we don't know how you'll use your phone.. So it's impossible to tell if you will get more than the mentioned sot or not..i easily get more 4hrs+ sot with a total battery time of 1day and a few more hrs...
[Nexus 4 Original Android Development] Wassupdog:
Thanks.

Is there any app for this kernel so I can set gamma colors and sound control?
[Nexus 4 Original Android Development] snak3ater:
Semaphore manager.. It's a great app...
[Nexus 4 Original Android Development] hughfollett:
Download semaphore manager from the play store, it's free.. No sound control.. In the Op you'll find some more infos :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] domg73:
Same here.. since kitkat release I have lots of flickering on stock rom... I had to switch to a different kernel... But I still love semaphore.
[Nexus 4 Original Android Development] gialakias:
I have flickering too especially with SwiftKey, but it does not matter for me. No other problems with stock rom and semaphore . As I said in g+: Hats off to Mr Stratosk!
[Nexus 4 Original Android Development] BLADESMAN1889:
Hey guys.

I'm a long term user of Semaphore but I've been getting some problem with phone calls being killed upon answer - it happen both to incoming calls and outgoing - soon as the call is connected it just cuts off.

This is with latest SLIM Rom & various versions of Semaphore (2.0.2 was last I tried & the previous 2/3 versions before that)

Because of the need to answer the call I had to reflash the Rom - then after reflash I leave SLIMKAT all stock & phone is OK again.

Due to life being busy I've not had the time to follow the threads much so if I have missed something obvious I apologize.

I have not tried v2.0.5 yet but will download soon.......... Any ideas please guys ?

Sent from NEXUS⁴ via XDA Prem [SLIMKAT 4:4:2]​
[Nexus 4 Original Android Development] Arju:
I've never had that problem using Semaphore and slimkat. Did you alter with the kernel settings? Did you clean flash slimkat before you installed Semaphore? Did you come from a different kernel before flashing Semaphore the time the you were dropping your calls?
[Nexus 4 Original Android Development] deeppans:
Please correct me if I am wrong.

Semaphore 2.0x works flawlessly with PA & OmniRom, but not with CM11. Am I correct?
[Nexus 4 Original Android Development] snak3ater:
Yes..You are right..But you can find many Semaphore based CM11 compatible kernels in Android Dev section..if you like Semaphore.you can try those :)
[Nexus 4 Original Android Development] Wassupdog:
Thank you both!
[Nexus 4 Original Android Development] hughfollett:
View attachment 2552897View attachment 2552899View attachment 2552900

First run with aospa BETA 4 and semaphore 2.0.5. A lot of g+, fb, twitter, some WhatsApp and hangouts. Stock settings except for pa halfbreed and vibration to 90%. Airplane mod during the night. 2-3 min of 3G on g+ but the rest is on wifi.. 15-20 min of flappy bird..

Great job :thumbup:

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] ephumuris:
Wow that is good screen on time. No undervolt or anything in there then? Do you use dt2w?
[Nexus 4 Original Android Development] hughfollett:
No UV and no dt2w.. Changed only the settings for vibration and colours :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Bonvaz:
Dt2w reduce a lot battery life? Don't know if use it or not

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] RealSlimShadyMC:
Hardly any, its just a bit annoying since it unlocks sometimes

---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------

---------- Post added at 06:59 PM ---------- Previous post was at 06:59 PM ----------

Sorry about that, tapatalk bugged out
[Nexus 4 Original Android Development] ephumuris:
That's crazy I thought my 4 hours 15 minutes was good but that's underclocked to 1.3ghz and a big undervolt...

On a side note is there any colour settings anyway in an easy to apply format.
[Nexus 4 Original Android Development] hughfollett:
I forgot to add 20min of play music at max volume from the phone speaker. I just hope this is not a lucky cycle :) as for colors, search this thread for "semaphore spreadsheet" and you'll find all the profiles for semaphore manager.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] kelah:
A lil' init.d to disable red trigger, it will be disabled at reboot.

Unpack it and push "turn off led trigger" file to /system/etc/init.d.

EDIT: if it not launching then set permissions to rwxr-xr-x using root explorer or another rool file manager.
[Nexus 4 Original Android Development] BlueFlame4:
Yes. First exit exits superuser-mode (su) and second exits the shell (terminal).

Sent from my Gameboy Color