yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Chapi:
[MENTION=3750240]stratosk[/MENTION], i have today two times the 'unresponsive screen bug' with 2.0.2 and one more time yesterday with 2.0.1. If happens again, which kind of information can I get to help you to detect it??
[Nexus 4 Original Android Development] chavocarlos:
Hi, I have experienced the same issue, can you confirm me if you have LMT launcher enabled? I just disabled LMT and no more unresponsive screen.
[Nexus 4 Original Android Development] stratosk:
Unfortunately, logs will not show anything. The phone is up and running.

It's only the touchscreen that can't handle input events when the screen is on. I just need a way to reproduce this issue.

You may try the attached version though.
[Nexus 4 Original Android Development] ihancioglu:
Do you advised this test version to everybody or just for this issue? just enabled trace log?
[Nexus 4 Original Android Development] chavocarlos:
I am almost convinced that if you install LMT launcher you will get the error, I know that sounds weird, but try it :P.

http://xdaforums.com/showthread.php?t=1330150

Choose start service automatically and reboot your phone.

Regards.
[Nexus 4 Original Android Development] stratosk:
It has 2 more commits.

- A commit that tries to resolve unresponsive screen issue.

- a change to interactive that turns on input_boost by default.

I use it since yesterday. So, it's harmless to use it. :)
[Nexus 4 Original Android Development] chavocarlos:
I will try.
[Nexus 4 Original Android Development] stratosk:
Thanks maybe I could try.

But, I think it's "normal" to be a conflict with an app that handles touch events.

First, I would like to know if I can reproduce this issue on a clean stock ROM.
[Nexus 4 Original Android Development] chavocarlos:
Since I disabled LMT launcher, never gets another unresponsive screen. Hard decision, but d2tw like too much ;).
[Nexus 4 Original Android Development] ihancioglu:
I just enabled this option today to check how battery will affect this. What is your suggestion about hispeed_freq? Because If remain it default(1512), cpu will be on top most of the time. So I just decreased it 1315000.

I think there is another tunable for input_hispeed_freq on Franco to keep not on top all the time.

What do you think about io_is_busy on interactive gorvernor? It is OFF default.
[Nexus 4 Original Android Development] snak3ater:
It depends on the value of

go-highspeed-load...set its value to 99..interactive gov will do its job as normal.it wont stay on 1512mhz all the time.. there's a 'boost' tunable having a default value of 0.. if you set boost value to 1512mhz..then cpu would stay at 1512mhz as long as you keep touching the screen
[Nexus 4 Original Android Development] stratosk:
Yes, good choice. You may use hispeed frequency tunable to handle this.

I don't think there is a need for new tunable.

You may also experiment with io_is_busy. It should push the CPU during I/O (like in ondemand). They include it lately in interactive and it's disabled by default.
[Nexus 4 Original Android Development] ihancioglu:
Thanks for the answer but I am just a bit confused with go_hispeed_load

go_hispeed_load : Go to hi speed when CPU load at or above this value.

input_boost : Immediately scale to the hispeed_freq on touch input

As I just configured hispeed_freq to 1134000 and input_boost to 1 , freq will be go 1134 on every touch input without wait for go_hispeed_load.

So what will be the change If I change go_hispeed_load to 99 or 80 as I reach hispeed_freq on every touch input ?

Thanks,
[Nexus 4 Original Android Development] IgnorCZ:
Kudos [MENTION=3750240]stratosk[/MENTION] ...

Best implementation of dt2w for N4 !! I am using Purity rom and I want rapport that I had one freeze screen on v 2.0.0 and on the next versions I had 0 freeze :) ... but I had twice on v 2.0.2 unresponsive left edge of the screen .. for example I can't swipe from left part of screen in play store or in the other apps .... I don't know if it was problem with implementation of dt2w or some rom problem .. but I think that it has something with kernel :( .. it's tiny problem and reboot solve it .... thanks for your hard work !!!!

Now I am flashing new version :)
[Nexus 4 Original Android Development] Chapi:
I dont have LMT, I think there is not relation with this issue

Ok, I will install it and test it. Thx for the support
[Nexus 4 Original Android Development] ephumuris:
I've had the unresponsive screen issue twice today. Rebooting fixes it (volume down and power to reboot). Once the screen just wouldn't come on, the next one the screen came on but wouldn't detect touches.

Anything i can provide to help?

2.0.2 kernel. Changes to stock rom are minimal, root, busybox, nova launcher and that's about it. No xposed or any other mods.
[Nexus 4 Original Android Development] snak3ater:
Yeah..with go hi speed load... You can control go high speed freq... but if you want cpu to jump up to certain freq on every input..then specify some freq to 'boost'..

---------- Post added at 06:53 AM ---------- Previous post was at 06:50 AM ----------

This left edge swipe issue is random and it's there in all kernels having dt2w/s2s/s2w
[Nexus 4 Original Android Development] Mercado_Negro:
Try version 2.0.3 posted by stratosk for testing.
[Nexus 4 Original Android Development] carlos67:
Could someone kindly link/point me to the fix for Trickster Mod showing 320 for gpu when idle but 128 when in use. I understand [MENTION=4152171]myfluxi[/MENTION] had a fix for this?

On the info tab the GPU shows 320 MHz when idle but when I start scrolling up/down it drops to 128 MHz. Surely it should be the other way round?

Thanks :)
[Nexus 4 Original Android Development] thracemerin:
The GPU sleeps at 320 MHz, it goes to 320 MHz before entering power save mode. If you aren't doing something graphics intensive and trickster shows it at 320 MHz it means it's in powersave (essentially hotplugged off). This is the correct stock behavior, there is nothing to fix, other devs have modified it to their liking.
[Nexus 4 Original Android Development] Italico:
Dear StratosK, after these changes to the interactive governor, what would be the best for battery life and performance? Is ondemand still the recommended one?

Thank You

Inviato dall'Ombelico del Mondo
[Nexus 4 Original Android Development] ephumuris:
Thanks seen that last night and installed. Let's hope it does the job because this is a feature that's made my power button obsolete. All phones need this.
[Nexus 4 Original Android Development] stratosk:
There are other loads that need to push the CPU freq. When the load is above a threshold (hispeed_load) the CPU will jump to hispeed freq.

I've never experiment with different interactive tunables.

Yes ondemand is still the recommended and the default in Semaphore.
[Nexus 4 Original Android Development] earlgrey_44:
DT2W

Now on 2.0.3. Have seen the following:

Reinstalled the kernel and Semaphore Manager since it seemed to be not working as expected. Most of my (already minor) problems disappeared.

On 2.0.1, no extra tapping was required. The phone woke first time, every time.

Reboots no longer affected the functionality.

On 2.0.2, everything was perfect except for these episodes:

I took a call (Using SAI) and had it cut off after about 30 seconds, where upon I found the phone was in airplane mode. I took this to mean that the screen was not deactivated when taking the call. This was the only incident like this that took place - other calls were normal.

When I picked up the phone in the morning for the first time on the second day, the phone was in a state where it would wake on any touch anywhere on the screen. After resetting double tap in the Manager, functionality returned, but the phone reverted to the "hypersensitive" mode a couple of hours later. No settings or software changes were made during or before these episodes.

So far on 2.0.3 for most of a day, no bad behavior of any kind. 100% functional. Every other similar implementation I've ever used on any kernel or app has had some irritation or bug(s) associated with it. This one is looking like the exception. Great coding job so far! Here's hoping todays perfect performance holds up.

I'm on SlimKat wth Xposed.
[Nexus 4 Original Android Development] DiDk070:
I have a problem with every custom kernel. I don't know why. I have it with this one too. The problem is that a part of the display is not responsive with CKs. I mean about 1mm to borders and its very hard to type. This kernel is very good, but this problem is very annoying. Can it be fixed, somehow?

Also I remembered for another problem - screen doesn't go off on calls.
[Nexus 4 Original Android Development] themike10452:
Is there any method to convert FAUX gamma presets into semaphore compatible format? please don't post the spread sheet cz I have it. I just have a personal preset that I want to convert.

Thanks.

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

I would like to inform you about two minor bugs in Semaphore Manager.

1- If you press OK with empty value on any tunables of any governor, Application is forcing close. Maybe that values should not empty but It should not force close as well :)

2- If you enable io_is_busy on Interactive then press "read system settings" to check enabled or not, It turns not checked.

Thanks,
[Nexus 4 Original Android Development] ephumuris:
No problems so far with the 2.0.3. Loving it.
[Nexus 4 Original Android Development] stratosk:
Excuse me. What is CK?

Screen goes off normally here. Can you please share your configuration?

Thanks for your feedback. I will try to resolve issues.
[Nexus 4 Original Android Development] snak3ater:
I think CK->Custom Kernel :D
[Nexus 4 Original Android Development] szacuken:
Strange... On 2.0.3 i have got lot of reboots after taking pictures by stock camera, instagram or other apps used camera. :<

EDIT:

and sometimes touchscreen stops working, I have to lock and unlock the phone to get everything back to normal.

In the previous version (2.0.0) did not have any of these problems
[Nexus 4 Original Android Development] Italico:
Thank You StratosK. BTW, with the 2.0.2 version the Touchwake disable during call, in SAI, seems to work better than before. Can't comment on DT2W, because I'm fine with Touchwake and button. But thanks!

Inviato dall'Ombelico del Mondo
[Nexus 4 Original Android Development] DiDk070:
Yes, CK is custom kernel. I write from phone and it's not very comfortable.
[Nexus 4 Original Android Development] ihancioglu:
Hi [MENTION=3750240]stratosk[/MENTION],

Touch screen stopped working a few minutes ago. But DT2W is still wakening the device fine. I am on latest test version(2.0.3).

I have attached dmesg log.

Thanks,
[Nexus 4 Original Android Development] DiDk070:
Also DT2W for me is only T2W. With one touch I can wake the phone... Why?
[Nexus 4 Original Android Development] jimyiak:
msm_hisc_host is only radio related?i tried hybrid radio 98/33 and still is the top on the battery stats..you think i should try another radio or it's kernel related??

neXus⁴ running kitkat 4.4.2
[Nexus 4 Original Android Development] yak84:
Yes, radio/kernel.
[Nexus 4 Original Android Development] IgnorCZ:
Read a little bit forum .. it's not so hard to find it ;) .. you have enabled t2w in semaphore manager ...... it must be disable !! Than it (dt2w) will be working without problem :)
[Nexus 4 Original Android Development] Fenvarien:
I had not a single problem with Semaphore 2.0.3, took many photos and videos, used it with wifi and mobile data and applied my usual UV.

Thanks for your hard work [MENTION=3750240]stratosk[/MENTION] :)
[Nexus 4 Original Android Development] IgnorCZ:
Hi [MENTION=3750240]stratosk[/MENTION]

I would like to post some feedback on 2.0.3 ... everything(dt2w) is running smooth and without problem!! No freezing screen,unresponsive edges :) ..... all is good when phone is using in normal way ....

but if I put a hand on the screen and leave the hand on it for example 30 s or 1 minute (to simulate: phone in the pocket is really close to body) ... dt2w is then not working and the screen becomes unresponsive :( ...... 10 fingers tip wake the screen ( I had a problems with it but finally I make it) .. everything is working again but there is unresponsive edges until next reboot ...... that's my feedback ...

.. dt2w is working perfectly, you did a stunning job ... it's only this situations with freeze screen .... I didn't have unresponsive screen if I used phone lets say "normal" way ... I had freeze only if I had phone in the pocket or did it with hand on the screen ..... I hope that I helped a little bit :) anyway thanks so much !!!!
[Nexus 4 Original Android Development] stratosk:
Hi,

Thanks for your feedback!

I didn't have unresponsive screen yet. But turning on the phone today and reading your post, I realized that I had the issue with the edges.

I enabled the "Show touches" options in developer options and I saw the issue. There was no touch input in the edges (left and right).

There is no change in double touch to wake functionality that can explain this behavior. So, I did this:

I disabled double tap to wake, turn off the screen and turn it on again.

The problem disappeared. Why? Most probably because if double tap to wake is disabled the touch screen device is powered off/on when turn off/on the device. So, actually when dt2w is disabled we reset the touch screen in every suspend/resume cycle.

So, I believe that there is a bug in touch screen firmware that causing this. I will try to test a version that resets the touch screen when a double tap is detected to workaround this issue.

Thanks again for reporting!
[Nexus 4 Original Android Development] leninke:
Hi Stratosk!

First thanks for your great work! I'm on latest Omnirom with your latest kernel and I get regularly soft reboot.is it kernel or rom related? Sry for my English.
[Nexus 4 Original Android Development] stratosk:
Hi,

A soft reboot means that the kernel is up and running. Usually there is a ROM issue or a conflict between ROM and kernel.

Please post a kmsg (not last_kmsg) and a logcat after the soft reboot.
[Nexus 4 Original Android Development] leninke:
Thanks for your reply.semaphore is my first custom kernel and omni is my first custom rom, so how can I do that?
[Nexus 4 Original Android Development] stratosk:
Please enable logger module in Semaphore Manager app. Then reboot your phone. This should enabled logcat functionality.

Then just wait for the soft reboot. In a terminal emulator (or adb shell):

su

dmesg > /sdcard/kmsg.txt

logcat > /sdcard/logcat.txt (wait few seconds and then ctrl-c)

Please send the 2 files located in sdcard. There are also apps that makes the above procedure easier.
[Nexus 4 Original Android Development] ephumuris:
The holding of the touch screen causing freezes seems to make sense. Outside of work no freezes, I wear jeans. At work today had multiple freezes and I have very thin pockets in my work trousers and have the screen facing my leg to protect the screen.

Hopefully a fix can be found. I'm only getting two hours on screen on time Max at the minute so testing back on stock kernel with no undervolt or tweaks for now. Will definitely come back to this after my tests though.
[Nexus 4 Original Android Development] franklinlucas:
Hello stratosk, thanks for the awesome work. I'd like to ask for a feature: fast charge. It's really useful for me, sorry if it has been asked before, I didn't have time to read the previous pages. Thanks again!
[Nexus 4 Original Android Development] stratosk:
Thanks!

I'm sorry, no fast charge at the present.

At least until I deeply investigate why kernel developers don't implement it on stock.
[Nexus 4 Original Android Development] stratosk:
New test version 2.0.4

- Reset touchscreen device when device wakes up due to double tap

I hope this version will resolve the unresponsive touch screen issue.

Please test and report.

Thanks everybody for testing!
[Nexus 4 Original Android Development] Arju:
It feels like Christmas every time you launch a new version! Thank you!
[Nexus 4 Original Android Development] Gu$houn*:
I have weird issue since 2.0.2, sometimes /on 2.0.3 once, on 2.0.2 twice/ after longer deep sleep I have unresponsive edges on top and bottom /bottom one causes nothing but top one doesn't allow me to pull the notification bar down in apps, the swipe gesture in Nova works just fine./

Someone with this issue? [MENTION=3750240]stratosk[/MENTION] what could I pull from my phone to you about this issue?

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] rogers11:
Look one post above
[Nexus 4 Original Android Development] Arju:
Download and install test version 2.0.4. I don't have this issue att all.
[Nexus 4 Original Android Development] IgnorCZ:
[MENTION=3750240]stratosk[/MENTION]

.. you did it :) .... it's almost done :) ... when I simulate phone in the pocket with hand on the screen (1 minute or so) .. dt2w stops working .. I'm forced turn the screen on with power button but than screen is not frozen anymore .... everything is working flawlessly .. no unresponsive edges and after turnig off the screen dt2w is working again .....

.. it's almost perfect !! Thanks so much !
[Nexus 4 Original Android Development] Gu$houn*:
Yes, I knew there is new test version when I was writing my post, I meant it that way that I wanted help with development ... and many people wrote they had unresponsive side edges but not top & bottom ... anyway, nevermind, I'll flash new version.

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] dmourao:
Well... As weird as it may seem or not, I haven't had any response problems or touch screen not working. Phone has been on my pocket for a couple of hours today and it didn't stop working nor gave me and problems (I'm at 202).
[Nexus 4 Original Android Development] Arju:
Sorry if my post didn't help you but if you see the changelog Stratosk wrote for v2.0.4, it addresses the unresponsive screen and edges. So that's why I was pointing you towards that version.

[MENTION=3750240]stratosk[/MENTION] I love the latest version, it works as it's tend to work. The screen responds much better and dt2w is working great.
[Nexus 4 Original Android Development] Gu$houn*:
No problem, buddy, I cough it.;)

And the latest version works really flawlessly, thanks for your hard work [MENTION=3750240]stratosk[/MENTION]. :good:

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] MajinJoko:
Dear stratosk,

thanks for the fantastic work. And my compliments for your dt2w, it's really good.

Unfortunately I use a lot the fastcharge, therefore I am forced to use another kernel :(

But.. why not implementing this feature? Do you think it could be harmful for our devices?

Thank you again!
[Nexus 4 Original Android Development] snak3ater:
This thing has already been discused many times here..Use Jolie kernel from 'Android Dev section'..

It's pure semaphore..Only difference is inclusion of multiboot,faux sound,speaker & fast charge patches in it..
[Nexus 4 Original Android Development] Crostantin:
the Sema 2.0.4 is fantastic...the dt2w works very good...

I use LMT pie control and the issues seem disappear !!!

At now no other problems...
[Nexus 4 Original Android Development] Rohit02:
Installed the latest kernel and I got a hot reboot with Mahdi's latest ROM. Cant reproduce it and I am out in a function. Just wanted to report..
[Nexus 4 Original Android Development] leninke:
Hi Stratosk, i got a soft reboot again.I can't upload the logcat file to here, so i uploaded to my box. logcat thanks for your help
[Nexus 4 Original Android Development] snak3ater:
[MENTION=3750240]stratosk[/MENTION] . . . everything working great so far in latest test version...now it's time to change the kernel version in thread's title :D
[Nexus 4 Original Android Development] jimyiak:
with latest purity..default settings,uderclocked to 1,35gHz,undervolt 50-62mV,disabled dtw+touchwake,enabled only touch accuracy,i have about 4.45-5 sot maximun..110 hours up..everything stable though like a rock!!thank for this great kernel!!!!!
[Nexus 4 Original Android Development] rogers11:
Same here, no problems with DT2W on 2.0.4 (but I also had no problems with 2.0.2/2.0.3). - Using Nexus 4 -
[Nexus 4 Original Android Development] earlgrey_44:
Version 2.0.3 eventually displayed screen sensitivity issues once a day for two days for me, and my first try at 2.0.4 caused several problems, at which time I concluded that my testing wasn’t telling me anything useful anymore. After updating my ROM every week for some time, switching out a kernel here and there, I thought my ROM/kernel installation must have accumulated some problems. This can be true even if everything runs beautifully (except DT2W), which it was.

I wiped the phone, reinstalled my SlimKat and Sema 2.0.4, and replaced nandroid data to see if I could get away with that.

My first 2.0.4 install had shown trouble right away, screen freeze, single touch wake, and more. After the wipe, big difference - it has run flawlessly all morning. I can’t provoke any of my previously reported problems or any other bad behavior. Congrats again, Stratosk. Is it too much to say that you have done what nobody else has – made a trouble free “screen always on” control?

My remaining concern is battery draw. Two overnight trials with earlier versions of Semaphore DT2W showed averages of 1.75 to 2.1 percent of total battery drain per hour while the phone was asleep - no special wake locks occurring.

This strikes me as a noticeably faster clip than with no “screen active” feature being used, but I don't what it's going to be like now, or if I have any reason to care if I can still get 4 hours+ of combined screen on and phone talk time on a routine usage day. I’ll want to watch this to see if it’s worth being concerned about.
[Nexus 4 Original Android Development] stratosk:
Let's wait a little bit more.

Thought the first reports seems positive about double tap to wake (I hope to, because I run out of ideas :) )
[Nexus 4 Original Android Development] stratosk:
Thanks for logs.

Did you flash Semaphore of your stock kernel?

If no, please dirty flash your ROM and then Semaphore.

I can see some incompatibilities in logcat. For example the PowerHAL library. It's not the same as in stock ROM. And this cause the message:

"touch_boost: failed..."

Of course maybe this is not the cause of the reboot, but it shows that something is wrong...
[Nexus 4 Original Android Development] jimyiak:
You think that if i switch to art,i ll have better battery life?

neXus⁴ running kitkat 4.4.2
[Nexus 4 Original Android Development] leninke:
I'm on omni nightly.I flashed several times nightlys with semaphore, but reboots stay.I don't know what's going wrong.I try flash maybe.thanks for help, your kernel is awesome.
[Nexus 4 Original Android Development] snak3ater:
Does not matter..Battery life is same in both
[Nexus 4 Original Android Development] H-Body:
Hey guys, is this the most recent one for mako kernel: https://github.com/android/kernel_msm/tree/android-msm-mako-3.4-kitkat-mr1 ?

I know, its a bit off-topic, but this is always a thread with helpful and polite people, so i thought it would be a good thread to ask :)
[Nexus 4 Original Android Development] thracemerin:
Yes
[Nexus 4 Original Android Development] schmitzekater:
I can confirm that. I had issues with every other kernel version before, with LMT not working complete unresponsive screen.

Latest version is fine with DT2W so far.

Thanks [MENTION=3750240]stratosk[/MENTION] you're the best!

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] themike10452:
Running 2.0.4 for a couple of days and I'm loving it. Had screen edge unresponsiveness problem on 2.0.2 and now gone with 2.0.4. Nice work [MENTION=3750240]stratosk[/MENTION] :good:

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.4 Linux 3.4.77 kernel.