yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] saturax555:
i am on slimkat RC3. this kernel runs perfectly with it, really stable, fast and good battery life without modifiyng the parameters.

the dt2w is really incredible, so effective compare to the usual one. no more wake up in the pocket with this center hotspot, so great !

the touchwake feature is great too, but i cannot modify the delay. i would like to have only a few second, just in case the screen goes off when i read a text. but it remains always active.

the delay works when i switch off the dt2w feature. is it normal? are these 2 features not compatible?

anyway, my favorite kernel, such a great work, thanks a lot !
[Nexus 4 Original Android Development] lndulgence:
Hi Stratosk! I saw that you've posted the Semaphore 2.0.6 on page 676, is this an official release?

Thank you :)
[Nexus 4 Original Android Development] snak3ater:
Test version... but still it's as stable as any other official version. you can try it without any worries
[Nexus 4 Original Android Development] lndulgence:
Gotcha. Thanks!
[Nexus 4 Original Android Development] :
Hi [MENTION=3750240]stratosk[/MENTION].. I'm on version 2.0.5. This kernel is awesome, battery and performance wise. Just recently, I am using Touch Control because there's no "swipe-to-lock gesture" in this kernel. Well, maybe at least, not yet. But since last night, I encountered two instances of screen freeze where the "lock and unlock feature" on Touch Control works, but the screen freezes. If I touch the screen nothing happens but if I do the lock and unlock gesture, it works. It's weird, I had to restart to make the screen work properly.

Because of this I want to ditch Touch Control but I am a bit unwilling because I will miss the "swipe-to-lock mechanism". My question is.. Are you planning to add a "double-tap-to-unlock" function here? I think it will make the lock/unlock feature complete. :)
[Nexus 4 Original Android Development] snak3ater:
What rom are you using?

There are many options for you.."Either use double tap on statusbar to sleep" or add sleep shortcut into navring & use it...

You can also use sleep tile etc etc..There are so many options for that..But there are very few for waking up the device..

& this freezing problem..Well it's common issue while using Touch Control App..Only solution is to do a reboot or tap your screen with all the fingers you got..Screen would come back to life again..
[Nexus 4 Original Android Development] :
I'm on PA 4.0 Beta 5. And yes, it has a tile where I can tap to sleep the device. I think I'm gonna use it and see if it's convenient enough.

Tapping with 10 fingers? Like seriously? Hahaha!
[Nexus 4 Original Android Development] Gu$houn*:
Yep, it's kinda magic so don't tell anybody ... :D

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] snak3ater:
Yeah lol..it works..use all 10 fingers...
[Nexus 4 Original Android Development] ephumuris:
For screen off I have an app called screen off installed and in Nova, prime launcher I added this app to the double tap gesture. Obviously only works on home screen but I'm a bit OCD with going back to home screen anyway.
[Nexus 4 Original Android Development] stratosk:
Thanks for your nice words.

Touchwake and double tap to wake shouldn't be used concurrently.

I modified Semaphore Manager to forbid this.

Thanks!

I'm sorry, there will be no other implementations with screen gestures.
[Nexus 4 Original Android Development] :
Does you have the flash noise disabled, or sound set to silent?

I believe the null pointer dereference might actually be related to sound, as odd as that seems.
[Nexus 4 Original Android Development] snak3ater:
[MENTION=4128576]bedalus[/MENTION]: everything is stock..no changes in camera options...flash and sound both are enabled..I've used your kernel...no problem in it as well
[Nexus 4 Original Android Development] :
It's just a matter of time probably. The kernel logs show a panic, so there's definitely an issue on the kernel side.
[Nexus 4 Original Android Development] omer7:
I've tried this kernel with two different ROMs (rastakat & Cataclysm). On both ROMs I'm getting reboots while using camera (with flash ON).

Hope this issue gets resolved in the next update :)
[Nexus 4 Original Android Development] Coolgoly:
Imho Google has to fix it!
[Nexus 4 Original Android Development] omer7:
I m on google stock kernel now, will check it, whether it happens on stock kernel as well or not.

Will report back...
[Nexus 4 Original Android Development] stratosk:
New version Semaphore Manager 4.1.0 (available soon on Google Play)

- Add more languages (Dutch, Croatian, French, German, Italian, Indonesian, Norwegian, Polish, Serbian, Spanish, Swedish, Russian) (credits to all XDA members that work on this, thanks crowdin.net for hosting Semaphore Manager project for free)

- Code improvements and bug fixes

- "touchwake disable" option in SAI is disabled if touchwake (in Tweaks) option is also disabled. This will probably avoid accidentally enabling touchwake after calls

- Touchwake and double tap to wake options are mutualy exclusive

- Fix pick up phone functionality

- Better handling of swipe
[Nexus 4 Original Android Development] omer7:
So far didnt face this issue on stock kernel (cataclysm rom with stock (cataclysm) kernel). Took many pics (with flash on), no reboot.

Will try to check it one more time n report back if it reboots...
[Nexus 4 Original Android Development] miksontije:
downloaded,works fine.serbian translate is great. tnx friend
[Nexus 4 Original Android Development] ZioGTS:
I found a few mistakes in italian translation and made my corrections in crowdin.

Just my small contribution to [MENTION=3750240]stratosk[/MENTION] marvellous creations! :fingers-crossed:
[Nexus 4 Original Android Development] twowheeler:
Really cool to see these translations. If I spot a fault, can I just fix that with crowding? Vibrator should be trillen for the dutch translation. Looks kind weird now :P .

Rest of the update is perfect. It maybe better to show swiping as pages. This looks sexier, but pages maybe make it easier to see what you're actually swiping to.

Verstuurd vanaf mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] artifex21:
Posto sam na brzinu preveo,mozda se zavukla negde neka greska ali sve u svemu bi trebalo fino da izgleda.

Sorry for foreign language...
[Nexus 4 Original Android Development] stratosk:
Yes, please use crowdin to fix translations.

The basic navigation method is the navigation drawer.

I added swipe support as an extra method to navigate between fragments.
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

Is there a way to enable/disable DT2W without wake the device?

I would like disable DT2W while phone in pocket, I can do it with tasker but screen on and off on every execution is very annoying.

Thanks,
[Nexus 4 Original Android Development] Arju:
No there is not. If you're gonna use tasker you would need to know how long the phone is going to sit in your pocket or some new feature has to be implemented using the proximity sensor to detect that the phone goes in and out of the pocket. That would cause a bigger drain than just letting dt2w be enabled all the time. So the best is to let it stay on by day and turn it off using tasker by night. Unless anyone has any better idea(?)
[Nexus 4 Original Android Development] stratosk:
Hi,

As Arju007 said, no.

But, I will try to do something
[Nexus 4 Original Android Development] Sw2rT1:
Hi stratosk!

Could you add new option in your Sema Manager, to use force English language?
[Nexus 4 Original Android Development] twowheeler:
dutch translations fixed (the vibration part at least).
[Nexus 4 Original Android Development] nemanja066:
Use Xposed App and App Settings Module (recommended on Stock ROM). You can set the language independent of the phone language. Not only that, but many other useful options.:highfive:
[Nexus 4 Original Android Development] themike10452:
What is he's on ART ;)

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) + T.A.R.D.I.S powered by HellsDoctor R18 Linux 3.4.79 kernel.
[Nexus 4 Original Android Development] Fenvarien:
[MENTION=3750240]stratosk[/MENTION] Just a little feedback for Semaphore test kernel 2.0.6.

I used this version now for many days and took quite a lot of pictures. The device was rockstable during this period with good battery life and performance, just like 2.0.5.

Initially I used stock voltages, later on I applied some moderate undervolting and never experienced unexpected reboots.

The only case I was able to forcefully produce a crash was when I took many photos with flash in a very fast sequence. Then I heard an unusual 'clicking' noise and the N4 rebooted. But that's the known stock rom/kernel issue we most probably can't fix on our own...

Let's hope Google comes up with a fix for this bug, which is present since Android 4.3. ( http://xdaforums.com/showthread.php?t=2568962)

IMHO you can add the commit you used for this test version to the next final Semaphore release, it's not healing the issue completely but it somewhat improves the situation and has no negative impact :good: :)
[Nexus 4 Original Android Development] stratosk:
Thanks for your feedback, my friend.

Yes, I will include that commit. Maybe it doesn't resolve the issue but an extra check doesn't harm.
[Nexus 4 Original Android Development] faddyie:
Where is 2.0.6 download link... Did not find in op
[Nexus 4 Original Android Development] a g bell:
It was a beta version stratosk posted in the thread for testing if you look several pages back you might find it
[Nexus 4 Original Android Development] Fenvarien:
You can find the 2.0.6 test build here: http://xdaforums.com/showthread.php?p=50216441
[Nexus 4 Original Android Development] :
Hi friends, I need a little help.

In ondemand governor used in this kernel, is there an equivalent to input_boost_freq and touch_boost_duration? If yes, would you be kind enough to tell me? I couldn't find them in the Semaphore Manager, or maybe they are named/labelled differently.

Thanks a lot.
[Nexus 4 Original Android Development] ihancioglu:
Hi,

touch_load is the same with input_boost_freq on Ondemand. 75 default is equal to 1.1Ghz. If you decrease the value, Freq will be lower than default.

touch_load_duration is the define how long will be stay on that freq.(touch_boost_duration)

Hope this helps
[Nexus 4 Original Android Development] snak3ater:
You can calculate touch load value as :

Touch load *max freq/100

Default touch load value is 75..so.

75*1512/100 =1134mhz boost freq

Decrease the touch load and boost freq will also decrease
[Nexus 4 Original Android Development] :
Very very helpful answers guys, now I'm tweaking and my device is running like a Ferrari. Thanks a lot. God bless you all.
[Nexus 4 Original Android Development] jtwebfusion:
On 2.0.6, the undervolting show CPU table won't display in the Semaphore Manager. Is this a bug, or a "feature" of the beta kernel?
[Nexus 4 Original Android Development] Fenvarien:
It's working here with Semaphore 2.0.6 without any problems.

disce aut discede
[Nexus 4 Original Android Development] Arju:
Works here too.
[Nexus 4 Original Android Development] jtwebfusion:
Thanks. I'll try reinstalling it.
[Nexus 4 Original Android Development] capoooro:
Also here 2.0.6. Stable and undervolted. Try to reset manager to default, then uninstall manager and reinstall

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Tipkaros:
Pick up phone without touching the screen doesn't work for me. The first time I tried it (after updating Manager to 4.1) I got a su request for com.semaphore.sai. I gave it permission yet it still isn't working. I'm on 2.0.5
[Nexus 4 Original Android Development] Midomad:
Try to disable/enable SAI.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Tipkaros:
I did that and a few other things that came to mind and it didn't help. In the end I updated Purity and now pick up phone works but the screen doesn't turn off. If I, however, move the phone away from my face when the call is already ongoing and put it back, the screen does turn off.
[Nexus 4 Original Android Development] Gu$houn*:
Latest purity with Jolie 2.0.5 /=semaphore 2.0.5/ and no problems here, running purity with semaphore/jolie for a few months and no problem with this at all.

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] omer7:
[MENTION=3750240]stratosk[/MENTION], cn u plz tell me is it safe to use a modified thermald.conf with ur kernel? Coz when i was on stock kernel (in JB 4.3) i used to use a modified thermald.conf file, which had modified throttling values. And i removed GPU throttling from that file and it worked fine.

So can i use the same file with ur kernel? Coz ur kernel (as per my knowledge) uses the same thermald.conf file, which is in stock. And i guess ur kernel does throttling in the same way as stock kernel, right?

Thanks.
[Nexus 4 Original Android Development] a g bell:
Care to share that file ?
[Nexus 4 Original Android Development] snak3ater:
Yup... It's same as stock.. So if that file worked okay with stock kernel, then it should work with semaphore as well :)
[Nexus 4 Original Android Development] omer7:
Yeah thanks bro. Hope it works fine.

I need modified values especially in hot weather, when battery temperature rises quickly. Don't want GPU throttling, so I've modified that file. ;);)

Sure bro. But please use this file at your own risk :). Coz I'm not at all expert at how these kernels/ROMs work, just I modified throttling values a bit.

Here's a link to file

https://www.dropbox.com/s/zxmcnu94ht073i6/thermald.conf

And here's google stock kernel (thermald.conf) values and my modified values:

Google Stock Throttling Values:

Modified Throttling Values:
[Nexus 4 Original Android Development] theBeholderN4:
Thanks! Tried it out just now.
[Nexus 4 Original Android Development] cmajetic:
very good kernel. 2.0.5 is really smooth and the double tap to wake is working great here. thank you very much :)

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] malcho:
Running few days with this kernel and as always I'm truly impressed.

Fantastic work my friend
[Nexus 4 Original Android Development] Nicolae-Daniel:
Does GPU frequency affect battery life? Using 2.0.5 and my frequency is 400 by default.
[Nexus 4 Original Android Development] Gu$houn*:
IMHO I think it depends on your usage, I don't play games at all so I'm running on 320 without any trouble ...

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] clockworkstop:
[MENTION=3750240]stratosk[/MENTION] perhaps long pressing the powerbutton to turn off dt2w would be a simple solution for people wanting dt2w to be off when their phone is in their pocket?

Sent speedily from my scurrying Nexus 4
[Nexus 4 Original Android Development] Arju:
Don't think that would work as long pressing the power button would turn off your phone. To make such feature work, you would have to implement it in the rom, not the kernel. Does your phone even turn on in your pocket? Is it battery that concerns you? Turning it off when entering the pocket defeats the purpose of the feature as when you turn the feature off you'll have to turn it on somehow, which means extra steps. If it concerns you that much, you could always just turn dt2w completely off.
[Nexus 4 Original Android Development] thracemerin:
The power button shutting the phone down completely is actually a hardware feature, you can't turn that off in the kernel or the ROM, it's designed like that because you can't battery pull on this device.
[Nexus 4 Original Android Development] Arju:
Guess I learnt something new. Thank you! :) so basically there is no way to implement such feature as what the post above my last post is asking for. Unless dt2w gets implemented in a different way. I love dt2w and is not bothered about the drain. It not even that noticeable. (Assuming that's why clockworkstop wants it to turn off in the pocket.)
[Nexus 4 Original Android Development] snak3ater:
I think AK kernel had this feature.. Pressing power button would disable s2w..
[Nexus 4 Original Android Development] thracemerin:
Well, it's possible to do, it depends on the definition of long press I suppose, if you used a time between the short press (screen off/lock) and the hardware long press (shutdown) it would work, but you might run into trouble with people not knowing how long is long enough without shutting their phone down accidentally.
[Nexus 4 Original Android Development] mor_1228:
Trust me or not but latest semaphore gave problems with D2W enabled like after flashing latest kernel it booted with no problem but my device got stuck at lockscreen many times during normal usage with no tweaks default settings of kernel and screen remain unresponsive 6-7 times in 3 hours and everytime i had to reboot. it didnt occur eveytime i double tap but 6-7 times
[Nexus 4 Original Android Development] lndulgence:
I encountered the same thing, though i'm not using D2W. I'm using TouchControl, and enabled swipe2lock and swipe2wake, and the weird part is both features works, i can lock and wake the screen no problem, but screen is unresponsive.. Hmmm. So, is it a kernel problem? I wonder..
[Nexus 4 Original Android Development] mor_1228:
same with me i can wake device but after that screen does not respond
[Nexus 4 Original Android Development] schmitzekater:
Touch the screen with all 10 fingers and it's responsive again.

That's not a bug it's a feature. ;)

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] Chapi:
Six fingers are enough for me :D
[Nexus 4 Original Android Development] lndulgence:
No way??! Hahaha and now i cant wait for it to happen again so that i can give it a try! :) What feature though? What benefits can we get from that?
[Nexus 4 Original Android Development] mor_1228:
dumb are you or this feature ?:p
[Nexus 4 Original Android Development] snak3ater:
This is really strange.. Ever since dt2w showed up in semaphore.. I never had any freezes with any of the versions.. I wonder why :D

What exactly are some of you doing with the screen :p
[Nexus 4 Original Android Development] nemanja066:
Same here. What are they doing, God know. :)
[Nexus 4 Original Android Development] Holer Togni:
For me the “unresponsive screen after dt2w” bug is completely gone since 2.0.5. The only thing that keeps happening every few days is that dt2w stops working and I need to press the power button once to wake up the device. After that it's good again. But that's no biggie at all. This is the most reliable dt2w implementation I've tried and has really changed how I use my N4. I've gotten so used to it that I sometimes try to dt2w other devices like my gf's iPhone :)
[Nexus 4 Original Android Development] Italico:
Hi everyone. Had a FC on camera app yesterday on 2.0.6, flashed 2.0.5 and everything seems better
[Nexus 4 Original Android Development] Urticant2:
What is the battery % per hour on idle mode with Double Tap enabled
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

DT2W is working fine but screen is unresponsive, phone is stuck at Lock screen..

I have attached kmsg.

Thanks,
[Nexus 4 Original Android Development] stratosk:
Hi, my friend. Thanks for the log.

I saw that you did a touchscreen reset. I guess this did not change anything(?)

I start to believe that the issue is in the kernel input subsystem and not in touchscreen device...
[Nexus 4 Original Android Development] ihancioglu:
Yes, I tried touchscreen reset, but does not help. Also I tried a wake with power button , but screen remain unresponsive..

I got this problem second time with DT2W, both of them start after an incoming phone call (maybe it's coincidence) as soon as hang up the phone , notification drawer stuck half open, you cannot touch it on the screen.

After screen off/on notification drawer closes but screen remain unresponsive.. Interesting bug :)

Thanks,
[Nexus 4 Original Android Development] Coolgoly:
Sometimes I have the screen unresponsive after a DT2W. Just putting five fingers on it to unlock.
[Nexus 4 Original Android Development] rogers11:
Maybe flashing too many custom kernels without flashing boot.img in between.

Also no freezes here.
[Nexus 4 Original Android Development] snak3ater:
I always flash boot.img of my stock rom..Wipe cache/dalvik,reboot..After that flash Semaphore,wipe cache/dalvik,reboot :p
[Nexus 4 Original Android Development] :
It's not a good idea to perpetuate that myth.

If you flashed correct boot.img for your ROM, then just flash the new kernel

The only cleaning you may need to do is before you even flash the new boot.img, go to /etc/init.d/ and remove any files that you didn't put there yourself
[Nexus 4 Original Android Development] blttalas:
2.0.6?????
[Nexus 4 Original Android Development] RealSlimShadyMC:
It was a test build
[Nexus 4 Original Android Development] ShinnAsuka:
Is there a way to preserve Semaphore Kernel Manager settings between flashes? For example, I want to flash the latest nightly of OmniROM through their opendelta system and I have the Semaphore kernel in the "FlashAfterUpdate" folder. Will the settings of SKM be preserved after such a flash or will I have to set them again? I don't see a preserve settings feature in the manager which is why I ask. Thanks in advance, great kernel by the way!
[Nexus 4 Original Android Development] Gu$houn*:
It's normal app so if you will backup it and then restore, it will be the same.

P.
[Nexus 4 Original Android Development] ShinnAsuka:
Yes I understand that, but when I flash the latest nightly, it doesn't erase /data so all user-level apps will still be there. I'm just wondering if the SKM will keep the settings from the previous kernel. This function exists in Trickster MOD albeit its through a dialogue box on whether or not you want to preserve the settings. Thanks.
[Nexus 4 Original Android Development] Gu$houn*:
Ok, if you want to do a dirty flash, then one of the options could be to freeze skm before flash, do all the flashes including semaphore kernel, then unfreeze the skm. If you want to manage some stock kernel with skm, I think it's better to use trickster.

P.
[Nexus 4 Original Android Development] Slymobi:
if you use omnirom open delta it will keep semaphores settings but it will overwrite semaphore kernel. if you have semaphore kernel in the flash after folder then yes it should be restored.

however !!! as using semaphore kernel you might not meet the open Deltas requirements as you are using a changed setup so it may fail all together !!

nandroid then test it or just backup semaphore manager via another method and restore after.

A good all round tool is ESfile as it can backup app and data and much much more.
[Nexus 4 Original Android Development] ShinnAsuka:
Looks like the settings were preserved after testing it. Now just need to wait for a newer kernel to come out to see if the settings truly hold.

EDIT: Does anyone have a reference as to the various color profiles that we can use? The spreadsheet found here: https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=5 doesn't seem to have a single profile where Semaphore Kernel was used. As I understand it, the gamma/color control on this kernel is derived from Faux, but the values don't seem to match up to the kernel's presets... Thanks
[Nexus 4 Original Android Development] thiagox:
Hello all, someone has had the situation of trying to wake up your phone with DT2W after leaving the unit some time in the pocket and he did not wake up? This has been happening to me, especially when I'm driving or at the gym for example. It seems to have something to do sweat... Apparently it triggers all touch points of the screen at the same time and just stops responding, until I wake it with the power button.

I'm a new user of Semaphore Kernel, so do not know if this has been reported here... if so, anyone got a solution?

Thanks guys!

Sorry for my English.:silly: