yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Midomad:
[MENTION=278972]stratos[/MENTION]

What do you think about bionic patch and optimized dalvik?

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] kalpik:
Those are on the ROM side, not the kernel side.
[Nexus 4 Original Android Development] Midomad:
And?

Thanks for the clarification

I just wanted to get his opinion!

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] stratosk:
I'm sorry, I've never tested them. :)
[Nexus 4 Original Android Development] C4SCA:
They simply work and are better than the stock dalvik. I advise u to use it if u dont use ART

sent from my diabetic Nexus 4 (KitKat's fault).
[Nexus 4 Original Android Development] alen1901:
You really cant see a difference with this dalvik in real life usage. Its not some massive improvement, and also, this optimisations are from moto x, so its really not made for higher end phones.

Sent from Pure Nexus⁴
[Nexus 4 Original Android Development] C4SCA:
Yes u do notice, for example recent button lag (wich occur sometines) is gone with the optimized dalvik.

The dual core 1.7ghz krait 300 from the moto x is in the same league as our quad 1.5ghz krait 200 when talking about processing power. Stop saying its a low end cpu.

Plus if u go to the thread the current version isnt from the moto x anymore, this dalvik is specific to qualcomm cpus (but may work/improve performance on other cpus).

sent from my diabetic Nexus 4 (KitKat's fault).
[Nexus 4 Original Android Development] gialakias:
Well the kernel and the features are fantastic, but I have a problem. Since I flashed it on stock rom the wakelock seen below has turned up. I didn't have it so much when I was stock rooted.
[Nexus 4 Original Android Development] spirosbond:
This may be a problem with the radio you are on. Flash the latest from here:

http://xdaforums.com/showthread.php?t=2087227
[Nexus 4 Original Android Development] gialakias:
Well the fact is that I am on the latest and I changed nothing but kernel from my previous state. Stock rooted 4.4.2 with custom recovery only with no other mods. This is happening much since the kernel flash.
[Nexus 4 Original Android Development] thracemerin:
PowerManagerService covers partial wakelocks from apps, it is not kernel related.
[Nexus 4 Original Android Development] gialakias:
No, I mean the above PowerManagerService wakelock. I don't know if it is kernel related, I have read your analysis from a May post if I can remember...
[Nexus 4 Original Android Development] thracemerin:
Oh, the msm_hsic one? that's radio related, you probably have bad signal.
[Nexus 4 Original Android Development] svnhvn:
As far as i know that happened since kitkat rolled. No kernel related i think, coz it happens on every kernel i flashed.

Mako = Purity + r201 + 98/33 -> using XDA Premium 4 mobile app
[Nexus 4 Original Android Development] varunbala:
i have been on semaphore for sometime and used to dismiss high msm_hsic as a nexus 4 problem...but yesterday i installed the latest mahdi and stuck to the stock rom kernel and over the past 24 hours the msm_hsic wakelock is significantly lower.
[Nexus 4 Original Android Development] Dan1234567890:
Are you using 3g as preffered nettwork? If so, you could lower this wakelock by turning to 2g. This wakelock occurs when phone is strugling with the 3g signal mainly.

If you need 3g, and you are lazy to switch it to 3g manually (as I am), you can do thw following; i installed xposed framework and this module http://xdaforums.com/showthread.php?t=2580234 (you can read in op that it significantly decreases this mentioned wakelock) and since I'm running this module, I have increase in battery life for cca 20-30%.

Much more than I managed to do with other tweaking since I rooted the phone, including flashing any custom kernel instead the stock one. :thumbup:
[Nexus 4 Original Android Development] carlos67:
Whereabouts is the vdd_table located in the folder tree? I want to check that the undervolt is being applied. I am using trickster mod but it doesn't show the voltage table. I want to navigate to the folder in root Explorer. I thought it would be in /sys/devices/system/cpu/cpu0/cpufreq/vdd_table but it is not there??

Anyone?

Thanks :)
[Nexus 4 Original Android Development] stratosk:
Please check second post of this thread.
[Nexus 4 Original Android Development] stratosk:
New test version 2.0.1

- Reworked double tap to wake functionality

I spent many hours investigating the issues.

Yesterday, I was in a dead end, and I thought that this is not going to work as it should.

Today, I had an idea and implemented it. I think this works now (I hope without issues). I will post details later.

Please test and report.
[Nexus 4 Original Android Development] TheQuarterMile:
Is there a chance you'd include faux sound control?
[Nexus 4 Original Android Development] Midomad:
Testing now...

Envoyé depuis mon Nexus 4 avec Tapatalk

---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------

You can use Joliekernel but i hope it will be implemented in semaphore.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Arju:
I was actually crossing my fingers for a new semaphore build and I'm amazed it came today. I'm now waiting for a new slimkat build and then I'll do a clean flash and test out this kernel and the reworked dt2w functionality. Dt2w is my favorite feature and I'm glad you're working on it! Thank you stratosk!
[Nexus 4 Original Android Development] andr0id_xda:
My pleasure to test it,thanks for your work!one question can i dirty flash over 2.0 version or i have to reflash rom,etc???
[Nexus 4 Original Android Development] stratosk:
You may just flash it over previous version.
[Nexus 4 Original Android Development] stratosk:
Not in my plans at the present.
[Nexus 4 Original Android Development] snak3ater:
Flash stock kernel first or dirty flash your rom and then flash semaphore 2.0.1
[Nexus 4 Original Android Development] TheQuarterMile:
What do you use to boost headphone output? And you considered including a otg patch?
[Nexus 4 Original Android Development] stratosk:
I don't use headphones. And I don't boost the sound. :)

I'm sorry no otg either.
[Nexus 4 Original Android Development] carlos67:
Thanks and apologies for asking before checking the first page.
[Nexus 4 Original Android Development] stratosk:
No problem, my friend. :)
[Nexus 4 Original Android Development] capoooro:
Like always I try your last

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] jolinnard:
New code seems to work better, much better, but it's only my first impression. We'll see tomorrow. Thanks for your work!!
[Nexus 4 Original Android Development] carlos67:
I have switched off hotplugging (so all 4 cores active when screen on) and noticed a huge jump in smoothness and performance. It's perfect and the impact upon battery is less than I expected as the OP suggested a while ago in this thread.

I think [MENTION=3750240]stratosk[/MENTION] uses this setup and I can see why. I value performance & ui smoothness over battery life unlike most people on here.

Try it guys, you may be surprised. Yes, your battery life will take a small hit (smaller than you might think), but the uplift in smoothness and raw speed of opening apps/scrolling lists etc etc is more than worth it. ;)
[Nexus 4 Original Android Development] spirosbond:
Dt2w works perfect since now with 2.0.1!!

Great work man!

:good::victory:
[Nexus 4 Original Android Development] hellsgod:
There is a reason why the battery impact is not so much. Every hot plug decision your device makes cost you some energy. If you have all 4 cores online, there is no hot plug decision to make.

hells
[Nexus 4 Original Android Development] stratosk:
I used this in the past before the development of dynamic hotplug driver.

Yes, the battery cost is small and you will also have a little bit more hot device.

But it's an option
[Nexus 4 Original Android Development] Mercado_Negro:
[MENTION=3750240]stratosk[/MENTION]

I have a couple of questions about undervolting, if I may.

Why do you apply less undervolting for higher frequencies?

What's the difference between applying a lower undervolting for higher frequencies and higher undervolting for lower ones or viceversa?
[Nexus 4 Original Android Development] stratosk:
Usually, higher frequencies need more voltage to be stable.

This is the reason I split the freq scale into 2. Lower and higher freqs.
[Nexus 4 Original Android Development] snak3ater:
[MENTION=3750240]stratosk[/MENTION]: Can you please explain what new changes were made in dt2w?

Because i never had any issue with dt2w in Semaphore 2.0.0
[Nexus 4 Original Android Development] :
Well, ever since Franco started working on Hammerhead I've been thinking about switching to a different kernel with an active developer and since I used Semaphore for my older SGS and liked it, I think I'll use it once more, this time for my N4. Can anyone who used both FK/Semaphore compare the two? Will I have worse/better battery? Will my performance take a hit? etc. Thanks in advance.
[Nexus 4 Original Android Development] kalpik:
In my opinion, Semaphore has both better battery life, and better performance.
[Nexus 4 Original Android Development] svnhvn:
Naah, in my opinion they both in same level. I'm thinking to temporarily switch from FK too..

Starring: Mako

Also starring: Purity, r201, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] stratosk:
Let me first explain the exact double tap to wake mechanism.

As you know without this functionality when kernel suspends, it turns off

many hardware subsystems to save power. Touchscreen is also powered off and

it's impossible to handle any touch events.

Double tap to wake implementation does not power off touchscreen during suspend.

Touchscreen driver uses interrupts to signal the kernel when there is a touch in

the screen. Double tap to wake registers this specific interrupt that it's

capable to wake up the kernel.

All double tap to wake implementations use the same mechanism to handle the

interrupt and simulate a power key press to completely wake up the device.

Though, all implementations have one issue. If the kernel is suspended (and

there are no wake locks active) the driver fails to recognize the double tap in

many cases.

After a lot of investigation I found the root of the issue. Android kernel

uses opportunistic suspend mechanism and tends to auto suspend IF there is no

wake locks active. This means that even if there is an interrupt from

touchscreen, kernel will try to suspend as soon as possible. So, many

touchscreens events are lost and the driver couldn't process them correctly to

recognize double tap.

The solution is pretty simple. When the screen is off, and there is and

interrupt from touchscreen, we use a wake lock to keep the kernel awake

until the whole processing of double tap functionality is over. This

seems to resolve the issues, and now a double tap always wakes up the device

properly.

Moreover, I reworked the code in order to be more efficient and more accurate.
[Nexus 4 Original Android Development] ihancioglu:
I am testing the new test version. It looks very promising , every double tap event is ended with wake up the device.

Congratulations, this changes makes this function is very close to perfect. Hopefully battery drain will not increase too much after these changes.

Thanks [MENTION=3750240]stratosk[/MENTION], I was sure you will implement this feature perfectly.
[Nexus 4 Original Android Development] capoooro:
After a day I don't see any appreciable difference in battery life. Good work... Like always

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] snak3ater:
Thanks [MENTION=3750240]stratosk[/MENTION]...latest version is running great.. no issues so far..

Ps:Want to ask if there's any plan of adding a feature for device sleep..something like sweep2sleep..dt2w is a really big feature that made its way into semaphore...now only if its small brother sweep2sleep gets added too.. it would be great :)
[Nexus 4 Original Android Development] hulicow:
[MENTION=3750240]stratosk[/MENTION] I am runnung also the test version also and it looks like it is more responsive that the previous one. Anyway, are you going to implement also when the device is sleep when you double tap it it would wake the device.. It is like double tap to wake.. Like on LG G2, when the device is sleep when you double tap the screen it will awake, when the device is awake when you double tap it it will sleep. You already implement one of those, I hope that double tap to wake would be possible also.. Thanks sir for great work.
[Nexus 4 Original Android Development] Fenvarien:
You could use Purity ROM, it features an option that sends your device to sleep if you double tap the status bar.

[MENTION=3750240]stratosk[/MENTION] Great and innovative work with the DT2W feature, it works now perfectly reliable here! :)
[Nexus 4 Original Android Development] OldGaf:
I had not noticed that.... thanks!

Purity... double tap to sleep

Sema... double tap to wake

Love it :)
[Nexus 4 Original Android Development] snak3ater:
I am using rastakat which has got this double tap feature..It works okay but sweep2sleep was something else :fingers-crossed:

Can't use touch control as well..As it freezes the screen..Currently using dt2w (Semaphore) and double tap to sleep (rastakat) :)
[Nexus 4 Original Android Development] bankgg:
I've been using the test version for the whole day and my screen was frozen once about a minute when I was trying to unlock the screen (with d2tw on), apart from that, it's just worked fine.
[Nexus 4 Original Android Development] IgnorCZ:
Hi you can have sweep2sleep on Purity too .... if you in "Quick launch shortcuts" set "screen off" than you can swipe from home button upp and your display goes off ;) I am using this for ages ....

.. BTW .. everything works like it should ;) thanks so much [MENTION=3750240]stratosk[/MENTION]
[Nexus 4 Original Android Development] snak3ater:
All of my targets are already occupied...Google,Screenshot and Torch..

I would prefer "statusbar:double tap to sleep" over quick launch shortcuts :)

I've been spoiled by s2w/s2s..Even now i sometimes do a swipe instead of double tap in Semaphore :p

It'l take some time but i'll get used to it :good:
[Nexus 4 Original Android Development] Luigi_2:
With default settings, both kernels have good performance, i'd say they're on par. But franco's usually gets me about 2h30m screen-on time compared to 3h and a bit more with semaphore. Of course with mix usage, and uptime > 100 hours.
[Nexus 4 Original Android Development] stratosk:
Just added a new feature. I will focus to test it and release a new version. And then some rest :)

I was investigating this a whole week. I think I will not benefit from double tap to wake, because I used much more times the power button last week :)

Anyway, I think sweep2sleep or double tap to sleep is a little bit unnecessary. We will see...
[Nexus 4 Original Android Development] schmitzekater:
You could use LMT for that. Trigger key '26'. This simulates the power button.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] M@rs:
What Feature have you added? If allowed to ask :)

i like the Kernel, its my first custom Kernel and i dont see a advantage of other kernels for my daylie use. So i am really interrestet in upcoming Features.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] stratosk:
Sorry for misunderstanding. I mean I spent a lot of time to make double tap to wake work without issues (in test version 2.0.1).

I want to stabilize it and release the new version.
[Nexus 4 Original Android Development] Mercado_Negro:
That's just probably because you're not used to double tap to wake yet. Same as me, I always forget to double tap but I'm too used to just press the power button. We're creatures of habit :)
[Nexus 4 Original Android Development] stratosk:
I meant that I used the power button many many times to flash test kernels last week. :)
[Nexus 4 Original Android Development] spirosbond:
And we can all agree now that this post was a bit tricky :p :cyclops: :laugh:

Cheers
[Nexus 4 Original Android Development] fortunz:
I use purity and put a power down shortcut on the quick menu (swipe up from the home button, what used to trigger google now). It feels pretty smooth. I don't touch my power button much anymore.
[Nexus 4 Original Android Development] anbinhv:
What is the lastest test verson?
[Nexus 4 Original Android Development] Mercado_Negro:
http://xdaforums.com/showpost.php?p=49585831&postcount=6259
[Nexus 4 Original Android Development] anbinhv:
Thank you Mercado!
[Nexus 4 Original Android Development] manjee:
Hi Stratos,

DT2W is working great but I encountered an issue: the phone became unresponsive to the point I was unable to unlock it (pattern lock). The screen was recording inputs but was so inaccurate I couldn't even switch between lock screen and camera.

I failed to capture a log but thought you might be Interested anyway.

Thank you for making our phone even greater than it already is !
[Nexus 4 Original Android Development] fuzzyAI:
After a day of using, I find it's much better than v2.0.0. No more wake up from a single touch.

This morning, I encounter this problem. My lock screen's using passcode and number 2 happen to be in middle screen. I double tap and the screen did not wake up. I press power button, the screen light up but I cant enter number 2. I can still enter other number, delete number. But number 2 is dead.

Turn off the screen and back on with power button did not help and I have to reboot.

Unrelated to above issue, I also find that I can swipe in the middle of the screen to wake up (swipe left to right, botton up, right to left , topdown also work). Is this a normal behavior ?
[Nexus 4 Original Android Development] aimcr7:
No such issue here, and swiping doesn't wake up the device, tried several times.

Dt2w is working great here, battery life is great too which means it doesn't drain my battery too much.
[Nexus 4 Original Android Development] "D":
[MENTION=3750240]stratosk[/MENTION]

this is the result with test kernel 2.0.1 :)

good work! i'm happy.

thanks and best regards from germany.
[Nexus 4 Original Android Development] stratosk:
I changed something (it will be available in next version) that maybe helps for this issue (I also had it once).

I've never faced a similar issue. This is definitely not a normal behavior.
[Nexus 4 Original Android Development] earlgrey_44:
DT2W

I've been testing (2.0.1) too and find the following:

When in deep sleep, the phone may require a double, double tap to wake but has never failed to do so thus far.

The setting does not survive a reboot. I open Semaphore controller, untic the DT2W setting, tic it again, close the app, and functionality returns.

I have poked the screen with my finger while on a phone call twice, and the screen appears deactivated. A common bug in the implementation of these "screen always on" controls in the past has been that the proximity sensor will turn off the backlight when taking a call, but the screen remains activated, so your cheek is busy pressing buttons and doing things while you are talking on the phone. It seems this is not so here.

Pretty great implementation Stratosk, congrats!
[Nexus 4 Original Android Development] chavocarlos:
I have the same bugs in 2.0.0 and 2.0.1 :P ... frequently the screen don't respond, or unlocks it, but the screen stops responding, only works weird swypes in navigation and status bar. The power button and power options works well despite this bug.
[Nexus 4 Original Android Development] snak3ater:
One thing i noticed is that phone does not wake up anymore while inside pocket. that's the only reason i stayed away from dt2w and been using s2w.

In other dt2w implementations, my phone always did things all by itself while inside pocket..camera taking pics and stuff like that.. So far no such thing in latest Semaphore...
[Nexus 4 Original Android Development] lalo20:
I dont like d2w because it drains the battery, I prefer touchwake and it works perfect, but sometimes inadvertently wakes the phone,

is possible that instead of using a tap to wake, could be two taps to awake?, as it works in d2w
[Nexus 4 Original Android Development] diogo.sena:
great job with dt2w,

two big annoyances of others implementations are in call, and in pocket accidental unlock, (i was using tasker to solve both )

at least in call, your implementation seems to solve 100%

is possible to implement reading of proximity sensor before wake the screen in kernel? (to do some kind of in pocket detection)
[Nexus 4 Original Android Development] stratosk:
Thanks for your feedback!

Please remember to double tap on the center of the screen. It's the only way to trigger the wake.

The functionality is disabled by default. You have to enable it after reboot. Semaphore Manager will do this for you once the "on boot" service will activate all your selections (few seconds after you unlock your phone after boot).

About your third observation, I hope 1 more commit will solve this (in next version).

That's why I will not drop touchwake. But I will not implement the double tap.

Because I believe that touchwake functionality has a little bit different meaning. For example: your read something and the screen goes off because of inactivity. You just touch the screen. IMHO, there is no reason for a double tap.

Thanks!

Unfortunately, there is no in kernel proximity sensor driver to control it. Moreover activating one more sensor means more battery drain.
[Nexus 4 Original Android Development] carlos67:
I'm using this too and it works like a champ.

---------- Post added at 07:36 PM ---------- Previous post was at 07:24 PM ----------

Regarding sweep-2-wake. I don't use it now because I was finding (on v2.0.0) that sometimes (maybe 1-in-5) times the screen would freeze on wake-up and be unresponsive. Only way to get it to respond again was to turn off screen with power button and then back on with s2w and then it would start working again. That's why I disabled it and now just use the volume button wake.

If it could be made to work without the screen freeze issue I would use it again because it's a great feature.
[Nexus 4 Original Android Development] hughfollett:
You could try it in the latest test version. [MENTION=3750240]stratosk[/MENTION] doesn't always keeping the touchscreen active harm it?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] :
I merged the double-tap-to-wake code into my own little project and it seems to work well. I appreciate the code stratosk, it's nice when things work properly
[Nexus 4 Original Android Development] stratosk:
I don't think so. It's an electronic part that produce almost no heat.

LG is using this feature to new models.
[Nexus 4 Original Android Development] ZioGTS:
Which ROM have you installed?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] lalo20:
i agree. Just trying to give a idea. When i have touchwake enabled, I set it with 10 seconds of delay. But sometimes when the screen is going off itself, I have to awake and lock with the power button to put in my pocket, the double tap avoid that the phone awake in my pocket itself. The same hapen in calls (I know SAI). also if I want off the screen with a gesture like dt2sleep in statusbar, if I put the phone in my pocket, touchwake awakes the phone.

sorry for my english Im learning :p