Here is a beta version of dt2w for 757.
A known bug is the screen unlocks when u double tap the screen the two times.
Maybe @blueether could help with it.
The funny thing is the bug disappears when I logcat.
It seems the bug only happens to me lol. Never mind
Here is the kernel:
Link deleted due to permission reason.
Sorry about that.
I will send a pull request and open source.
Enjoy!
I was going to do that today, I guess I'll have to find something else to do today
Did you include recovery/ RIC disable?
blueether said:
I was going to do that today, I guess I'll have to find something else to do today
Did you include recovery/ RIC disable?
Click to expand...
Click to collapse
Yes. It includes dual rec and RIC disable.
But there is something wrong with the driver.
The screen only unlocks when u do double tap two times. (double tap once, then double tap)
jackie099 said:
Yes. It includes dual rec and RIC disable.
But there is something wrong with the driver.
The screen only unlocks when u do double tap two times. (double tap once, then double tap)
Click to expand...
Click to collapse
when the phone is on charge (so adb) it will work flawlessly as I think the screen gets put into the next power state, this is the main problem with the dt2w.
Do you have an extra screen protector on? I think that that may be part of the problem
blueether said:
when the phone is on charge (so adb) it will work flawlessly as I think the screen gets put into the next power state, this is the main problem with the dt2w.
Do you have an extra screen protector on? I think that that may be part of the problem
Click to expand...
Click to collapse
No, I do not have extra screen protectors on.
Dt2w works perfectly on CM based rom. But not on Sony stock rom.
I have people test on their phones, they have same problem.
Maybe Sony stock rom have special power management?
jackie099 said:
No, I do not have extra screen protectors on.
Dt2w works perfectly on CM based rom. But not on Sony stock rom.
I have people test on their phones, they have same problem.
Maybe Sony stock rom have special power management?
Click to expand...
Click to collapse
What happens if you drop the "int dt2wcount = 2;" to 1?
blueether said:
What happens if you drop the "int dt2wcount = 2;" to 1?
Click to expand...
Click to collapse
I tried, but nothing changes.
jackie099 said:
I tried, but nothing changes.
Click to expand...
Click to collapse
MXM_PWR_SLEEP_MODE = 0x0001, to 0x0002?
When I bumped that up I never had a unlock fail
but I dont know what that would do to the power consumption
Bugger I have a SoD issue again
blueether said:
MXM_PWR_SLEEP_MODE = 0x0001, to 0x0002?
When I bumped that up I never had a unlock fail
but I dont know what that would do to the power consumption
Bugger I have a SoD issue again
Click to expand...
Click to collapse
Just changed the file and recompile.
Still no luck.
Just flashed and working fine at the moment. Only double tap once. And beautiful splash screen. Love it dude. Thank you. I'll report issues when they arise.
Sent from my C6806 using XDA Premium HD app
blueether said:
MXM_PWR_SLEEP_MODE = 0x0001, to 0x0002?
When I bumped that up I never had a unlock fail
but I dont know what that would do to the power consumption
Bugger I have a SoD issue again
Click to expand...
Click to collapse
I just found out dt2w works in TWRP recovery. I only need to double tap once.
It should be a system issue then.
can I flash over doomkernel? sounds promising! battery friendly? love it = )
Sent from my C6833 using XDA Premium 4 mobile app
truemagic said:
can I flash over doomkernel? sounds promising! battery friendly? love it = )
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, just flash it as you did the DooMKernel
jackie099 said:
Here is a beta version of dt2w for 757.
A known bug is the screen unlocks when u double tap the screen the two times.
Maybe @blueether could help with it.
The funny thing is the bug disappears when I logcat.
Here is the kernel:https://mega.co.nz/#!AhFE2AjT!0M9oKuoMpXfH_cTpgHMxG7Hus8EmYH-sOhVP6BDTJqw
Enjoy!
Click to expand...
Click to collapse
Thanks for work. Tell and how to activate DTW operation. I have a frimware ★ monxDIFIED ★ ZUltra™ 4.4.2 dt2w doesn't work.
Feodorus 4PDA said:
Thanks for work. Tell and how to activate DTW operation. I have a frimware ★ monxDIFIED ★ ZUltra™ 4.4.2 dt2w doesn't work.
Click to expand...
Click to collapse
It is enabled after flashing the kernel.
Feodorus 4PDA said:
Thanks for work. Tell and how to activate DTW operation. I have a frimware ★ monxDIFIED ★ ZUltra™ 4.4.2 dt2w doesn't work.
Click to expand...
Click to collapse
If it's the same code I use then:
De-activate
Code:
su -c "echo 0 > /sys/android_dt2w/dt2w_active"
Activate
Code:
su -c "echo 1 > /sys/android_dt2w/dt2w_active"
blueether said:
If it's the same code I use then:
De-activate
Code:
su -c "echo 0 > /sys/android_dt2w/dt2w_active"
Activate
Code:
su -c "echo 1 > /sys/android_dt2w/dt2w_active"
Click to expand...
Click to collapse
Thanks. Helped. Now everything works.
so we need to de activate and activate again on monx? and this is only for unlocked bootloader?
Can u make it for the z1 too?
Gesendet von meinem C6903 mit Tapatalk
Reported from monxDIFIED ROM + doomkernel (previous kernel), I too need double tap TWICE to wakeup my phone...
How to overcome it? Hmmm
Related
To make doubletap2wake feature work in CyanogenExtended kernels you should once downoad and flash .zip (compatible with your device & ROM of course) to add KeyHandler support in system (external module which enable screen when kernel sended a message (KEY_DOUBLE_TAP 251) to it that you make doubletap).
For Cyanogenmod 12.x:
D618: KeyHandler already is in ROMs, you don't need to do flash anything.
D620 (also compatible with any cm12-based ROMs): https://yadi.sk/d/btiBkgZXgvLNm
For Cyanogenmod 11 (only for clear ROM, not for it's based ROMs!!!):
D618: https://yadi.sk/d/OgON5Uz2guw33
D620: https://yadi.sk/d/XF8jJB1vgvLsA
For MIUI V5:
D620: https://yadi.sk/d/yaNS_hiUgvMFs
Another CM11-based ROMs (AOKP-4.4, CRYSTAL PA) isn't supported yet - if you want to help me with it just send me your framework-res.apk from /system/framework/ and write from which ROM is it.
I flashed it on MIUI but don't work
simo14 said:
I flashed it on MIUI but don't work
Click to expand...
Click to collapse
flash activation script from first post in miui thread =)
or input in terminal emulator:
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
System_F said:
flash activation script from first post in miui thread =)
or input in terminal emulator:
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
Click to expand...
Click to collapse
I downloaded all the files but still don't work
simo14 said:
I downloaded all the files but still don't work
Click to expand...
Click to collapse
hmm, open terminal emulator and input:
su
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
man..i have no words..you are the best!!!
thank you very much for your hard work.
it`s working on cm11
System_F said:
hmm, open terminal emulator and input:
su
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
Click to expand...
Click to collapse
Thanks now it finally work
CM11 from invaderjohn, 2tap2wake not working :\
I've installed zip and enabled it from setting (kernel adiutor too), but it's not working :\
Andrewbons said:
CM11 from invaderjohn, 2tap2wake not working :\
I've installed zip and enabled it from setting (kernel adiutor too), but it's not working :\
Click to expand...
Click to collapse
Maybe you mean CM12 from @invaderjohn? Don't you forget to install custom kernel?
Nikita Pro Android said:
Maybe you mean CM12 from @invaderjohn? Don't you forget to install custom kernel?
Click to expand...
Click to collapse
Sorry, i don't even remember that post XD maybe i was drunk or something Everything works fine, good work
System_F said:
hmm, open terminal emulator and input:
su
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
Click to expand...
Click to collapse
May this even work for CM12-ROM, too?
So far I'm not able to bring that feature to life. Installed Kernel and Patch twice, did the settings - still it won't work.
Any suggestions?
westenthor said:
May this even work for CM12-ROM, too?
So far I'm not able to bring that feature to life. Installed Kernel and Patch twice, did the settings - still it won't work.
Any suggestions?
Click to expand...
Click to collapse
Device? Did you try to disable/enable option in settings? And feature don't work when you're charging phone, don't forget.
Nikita Pro Android said:
Device? Did you try to disable/enable option in settings? And feature don't work when you're charging phone, don't forget.
Click to expand...
Click to collapse
D620 LG G2 mini.
Yep, I know.
Feature seems to work if I toggle on "Lift to Awake"- Function in Display-Settings, but with that the display wakes up every ten seconds.
westenthor said:
D620 LG G2 mini.
Yep, I know.
Feature seems to work if I toggle on "Lift to Awake"- Function in Display-Settings, but with that the display wakes up every ten seconds.
Click to expand...
Click to collapse
This is not doubletap2wake, just "rubbish" function. Try to download kernel and keyhandler patch and install them again.
Nikita Pro Android said:
This is not doubletap2wake, just "rubbish" function. Try to download kernel and keyhandler patch and install them again.
Click to expand...
Click to collapse
You mean like "Did you try turning it off and on again"?
Ok, I'll try...
Btw. Thanks for answering so fast!:good:
EDIT: Downloaded kernel and patch. Installed as recommended. Still no response.
Same for me here. I've downloaded nikita's kernel, and patch. Installed first kernel, then patch. Tried reactivating DoubleTap2Wake, and it wont work.đ
Also, I've typed command in TerminalEmulator that System_F mentioned with su rights, and nothing happens.
Shommey said:
Same for me here. I've downloaded nikita's kernel, and patch. Installed first kernel, then patch. Tried reactivating DoubleTap2Wake, and it wont work.đ
Also, I've typed command in TerminalEmulator that System_F mentioned with su rights, and nothing happens.
Click to expand...
Click to collapse
For cm11/12/12.1 - don't forget to activate it in Settings/Dispaly
Phone is d620r, rom is cm12, I activated it, but still won't work... Don't know why..
Shommey said:
Phone is d620r, rom is cm12, I activated it, but still won't work... Don't know why..
Click to expand...
Click to collapse
Do you have installed CM12 Kernel?
http://forum.xda-developers.com/g2-mini/development/d618-cyanogenextended-t3072141
Radac Stunghthumz said:
Do you have installed CM12 Kernel?
http://forum.xda-developers.com/g2-mini/development/d618-cyanogenextended-t3072141
Click to expand...
Click to collapse
Yes, as I said, I first installed kernel, then patch... I didn't work like that, so I added command in Terminal Emulator, like system_F said, tried turning off and on DoubleTap2Wake in Display settings, but nothing happens.
OS: cm12
Phone: d620r
One thing I find strange, in settings -> About phone, phone doesen't display kernel info, but Kernel Auditor does. Screenshots provided.
EDIT: It appears I didn't have latest unofficial cm12 version. I have installed it, now works perfect.
Code:
/** Disclaimer
* The usual stuff, I am not responsible for any damages from this mod,
* either to you phone, your job, your house, your kitten, blah blah…
*/
Introduction, How it works, etc.
This is a KnockCode feature addition for hellsCore kernel on our beloved Nexus 4.
I created this mod by modifying Stratoks's dt2wake in hellsCore kernel that you can input a pattern on the screen, which is separated in a grid of 4 rectangles (For further explanation search for LG KNOCKcode on Google). I record that pattern in Touchscreen driver, and then write it into a sysfs file.
In the second step, the hellsCode config Xposed module reads the code from that file, and compares it to the code saved in its preferences. If the code was correct, it finishes the Keyguard to unlock your device.
If the code is wrong, the screen still goes on, but this time shows the Keyguard. That means you can also use it as QuadrupleTap2Wake
At the moment, this mod heavily relies on Xposed, but I hope that I can integrate this mod directly into some custom roms, I will write a guide for rom creators later.
Since B80, my mod is merged into the official hellsCore kernel.
Sources:
Look below.
Click to expand...
Click to collapse
Installation instructions
* You need Xposed for this to work properly
* Install hellsCore kernel from here (since B80)
* Install hellsCodeConfig.apk, activate in Xposed installer, reboot.
* Set up your code in hellsCode Config app.
* You need to have doubletap2wake enabled in your favorite Kernel manager, and also enable the mod with
echo 1 > "/sys/devices/virtual/input/lge_touch/hells_code_enabled"
To disable temporarily, do echo 0 > "/sys/devices/virtual/input/lge_touch/hells_code_enabled", to remove permanently uninstall the hellsCode Config app.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* hellsgod for creating the best kernel in the world
* Stratosk for providing me the base with his dt2wake mod
XDA:DevDB Information
hellsCode, Device Specific App for the Google Nexus 4
Contributors
Maxr1998, hellsgod
Source Code: https://github.com/hellsgod/hells-Core-N4/commit/10eb65957bbcf65004d432a02fe7345a149c36db
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2015-06-27
Created 2015-06-15
Last Updated 2016-08-24
Download
Changelog
Code:
1.1 - 2015.06.27
[fix] -- relock keyguard
Older changelogs:
Code:
1.0 - 2015.06.15
[new] -- initial release
Click to expand...
Click to collapse
FAQ
Why isn't there a version for CM?
-- There actually is one, just take a look at the official hellsCore kernel, which includes the mod since B80.
The device sometimes unlocks when woken up with the power button, why does this happen?
-- That was a bug, fixed with config 1.1
Click to expand...
Click to collapse
Good job man, will try this asap!
is it echo 1 > "/sys/devices/virtual/input/lge_touch/hells_code_enabled"
or
echo 1 > /sys/devices/virtual/input/lge_touch/hells_code_enabled ???
eurochild said:
Good job man, will try this asap!
is it echo 1 > "/sys/devices/virtual/input/lge_touch/hells_code_enabled"
or
echo 1 > /sys/devices/virtual/input/lge_touch/hells_code_enabled ???
Click to expand...
Click to collapse
Whatever. With "" it has nicer formatting, and is most times better when you have spaces in folder names.
Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B78
Feedback
Really thanks! I really like knock code. This mod works great, but with three problems :
1. Lock screen is shown for a milisec, then unlocks. Not really a big problem.
2. After unlocking, status bar is sometimes pulled down.
3. Power button is useless now. Every time I use power button, it bypasses lockscreen. Every time.
I hope this mod advances with updates! Thanks!
ddaggebi said:
Feedback
Really thanks! I really like knock code. This mod works great, but with three problems :
1. Lock screen is shown for a milisec, then unlocks. Not really a big problem.
2. After unlocking, status bar is sometimes pulled down.
3. Power button is useless now. Every time I use power button, it bypasses lockscreen. Every time.
I hope this mod advances with updates! Thanks!
Click to expand...
Click to collapse
1. I still have to research which hooks suit better.
2. Really? That's strange, and has nothing to do with the mod..
3. That's a bug, read OP
Btw, if you touch screen once, and then press power button, it doesn't unlock. Will fix later today IF I have the time.
I unfortunately ignored school a bit the last few days, and have to catch up :/
Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B78
ddaggebi said:
Feedback
Really thanks! I really like knock code. This mod works great, but with three problems :
1. Lock screen is shown for a milisec, then unlocks. Not really a big problem.
2. After unlocking, status bar is sometimes pulled down.
3. Power button is useless now. Every time I use power button, it bypasses lockscreen. Every time.
I hope this mod advances with updates! Thanks!
Click to expand...
Click to collapse
For me is working quite fine, only problem i face is that the mod is not respecting unlocking sequence configured on hellscode config, if you tap on anywere 4 times phone unlocks.
Enviado desde mi Nexus 4 mediante Tapatalk
Thanks for the quick reply. I will love this if the power button bug is fixed!
About the statusbar, I think it is related with my rom's feature(quick pulldown). Do you use stock rom?
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
damopi95 said:
For me is working quite fine, only problem i face is that the mod is not respecting unlocking sequence configured on hellscode config, if you tap on anywere 4 times phone unlocks.
Enviado desde mi Nexus 4 mediante Tapatalk
Click to expand...
Click to collapse
Can you tell me what rom you use? Stock?
ddaggebi said:
Thanks for the quick reply. I will love this if the power button bug is fixed!
About the statusbar, I think it is related with my rom's feature(quick pulldown). Do you use stock rom?
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Can you tell me what rom you use? Stock?
Click to expand...
Click to collapse
Euphoria-OS 13 June build
Enviado desde mi Nexus 4 mediante Tapatalk
ddaggebi said:
Thanks for the quick reply. I will love this if the power button bug is fixed!
About the statusbar, I think it is related with my rom's feature(quick pulldown). Do you use stock rom?
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Can you tell me what rom you use? Stock?
Click to expand...
Click to collapse
Sorry i quoted the wrong post, Euphoria-OS 13 June build
Enviado desde mi Nexus 4 mediante Tapatalk
damopi95 said:
For me is working quite fine, only problem i face is that the mod is not respecting unlocking sequence configured on hellscode config, if you tap on anywere 4 times phone unlocks.
Enviado desde mi Nexus 4 mediante Tapatalk
Click to expand...
Click to collapse
Sure it unlocks? Or does only screen toggle on?
ddaggebi said:
Thanks for the quick reply. I will love this if the power button bug is fixed!
About the statusbar, I think it is related with my rom's feature(quick pulldown). Do you use stock rom?
damopi95 said:
Euphoria-OS 13 June build
Click to expand...
Click to collapse
I use Euphoria as well.
Click to expand...
Click to collapse
Maxr1998 said:
Sure it unlocks? Or does only screen toggle on?
ddaggebi said:
Thanks for the quick reply. I will love this if the power button bug is fixed!
About the statusbar, I think it is related with my rom's feature(quick pulldown). Do you use stock rom?
I use Euphoria as well.
Click to expand...
Click to collapse
Unlock
Enviado desde mi Nexus 7 mediante Tapatalk
Click to expand...
Click to collapse
damopi95 said:
For me is working quite fine, only problem i face is that the mod is not respecting unlocking sequence configured on hellscode config, if you tap on anywere 4 times phone unlocks.
Enviado desde mi Nexus 4 mediante Tapatalk
Click to expand...
Click to collapse
damopi95 said:
Euphoria-OS 13 June build
Enviado desde mi Nexus 4 mediante Tapatalk
Click to expand...
Click to collapse
work fine here, if i tap a wrong sequence the screen turn on but it doesn't unlock the screen
Nice work. I was waiting for this for a long time. I'll try the mod as soon as power button bug will be fixed.
Is there any chance you fix the micro lag that makes lockscreen shows for a millisecond?
Thanks
Ciao600 said:
Nice work. I was waiting for this for a long time. I'll try the mod as soon as power button bug will be fixed.
Is there any chance you fix the micro lag that makes lockscreen shows for a millisecond?
Thanks
Click to expand...
Click to collapse
Possibly.
But I don't have too much time this week. Maybe tomorrow or friday, but not today.
Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B78
How does this mod influence battery life?
Ciao600 said:
How does this mod influence battery life?
Click to expand...
Click to collapse
Exactly as much as original dt2w. Means not that much, maybe 1-2% overnight extra.
Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B78
no CM hells kernel?? how do i try it on resurrection remix??
abhishek24dogra said:
no CM hells kernel?? how do i try it on resurrection remix??
Click to expand...
Click to collapse
Not by now, sorry. But as @hellsgod will merge it into his sources, I'm sure he will also provide a CM build then..
Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B78
its same as all others out but i have synced it today with cm sources
built from source
try it
New TEST BUILD only flash if you want to test and report
cm-13.0-20160610-UNOFFICIAL-gemini
again this is broken sorry
and yes you will get blank screen instead of "Android is Upgrading"
please wait 10 mins.
if it goes into blank launcher bug
try below from recovery -
echo "debug.sf.disable_hwc=1" >> /system/build.prop"
(without last ")
You can do that from the recovery.
please report back
Device Tree - https://github.com/Mi5Devs/android_device_xiaomi_gemini
Thanks to Bruno,Louis,xiaobai.
Hi so you guys are the devs of the EU CM13, can I call it that??
No luck with this build, screen not reacting to presses.
This bug was also present on the Temasek's UNOFFICIAL CM13.0 build by Yairpatch
NisseGurra said:
No luck with this build, screen not reacting to presses.
This bug was also present on the Temasek's UNOFFICIAL CM13.0 build by Yairpatch
Click to expand...
Click to collapse
he fixed it???
droid.riz said:
he fixed it???
Click to expand...
Click to collapse
No, i gave him some logcats but he did not reply if it was helpful.
device screen is getting normal while pressing volume buttons
droid.riz said:
device screen is getting normal while pressing volume buttons
Click to expand...
Click to collapse
Yes, but its out of focus if no buttons is pressed.
There is a recovery fix for this on yairpatch site..
So what is this build?
It's in the wrong place.
Does it work, is it broken? Change log?
Mi5 is a mess for posts.
NZnewbie said:
There is a recovery fix for this on yairpatch site..
Click to expand...
Click to collapse
does it work?
white43 said:
So what is this build?
It's in the wrong place.
Does it work, is it broken? Change log?
Mi5 is a mess for posts.
Click to expand...
Click to collapse
broken
Wrong thread.
This is the temesak rom screen fix. It worked for me.
Guys this fix is for the graphic bug (where you can't use your launcher
echo "debug.sf.disable_hwc=1" >> /system/build.prop"
(without last ")
You can do that from the recovery.
white43 said:
Works fine for me. I'm using as a daily driver.
Click to expand...
Click to collapse
You are using my build???????????
droid.riz said:
You are using my build???????????
Click to expand...
Click to collapse
No, sorry, wrong one.
New TEST BUILD only flash if you want to test and report
cm-13.0-20160610-UNOFFICIAL-gemini
BROKEN sorry guys
and yes you will get blank screen instead of "Android is Upgrading"
please wait 10 mins.
if it goes into blank launcher bug
try echo "debug.sf.disable_hwc=1" >> /system/build.prop"
(without last ")
You can do that from the recovery.
please report back
droid.riz said:
New TEST BUILD only flash if you want to test and report
cm-13.0-20160610-UNOFFICIAL-gemini
BROKEN sorry guys
and yes you will get blank screen instead of "Android is Upgrading"
please wait 10 mins.
if it goes into blank launcher bug
try echo "debug.sf.disable_hwc=1" >> /system/build.prop"
(without last ")
You can do that from the recovery.
please report back
Click to expand...
Click to collapse
Just asking why not add this Line in build? It will broker something for people that not have bug after boot?
Sent from my SM-T560 using XDA-Developers mobile app
fuxmen said:
Just asking why not add this Line in build? It will broker something for people that not have bug after boot?
Sent from my SM-T560 using XDA-Developers mobile app
Click to expand...
Click to collapse
This will disable hardware composing, as the qcom-display is not aligned to mi5 yet.
adwinp said:
This will disable hardware composing, as the qcom-display is not aligned to mi5 yet.
Click to expand...
Click to collapse
So if im getting it right it is related to sources.. That we don't have them yet. Thanks for clarification I'm here for a while and still learning
Sent from my SM-T560 using XDA-Developers mobile app
droid.riz said:
New TEST BUILD only flash if you want to test and report
cm-13.0-20160610-UNOFFICIAL-gemini
BROKEN sorry guys
and yes you will get blank screen instead of "Android is Upgrading"
please wait 10 mins.
if it goes into blank launcher bug
try echo "debug.sf.disable_hwc=1" >> /system/build.prop"
(without last ")
You can do that from the recovery.
please report back
Click to expand...
Click to collapse
Could you post the latest CM13 build again, i like to try few tricks to solve the screen bug.
My rmn4x has not working dt2w, i tried many roms but nothing change, i really need help :highfive:
Help ?
Hello? Anyone?
Hiou said:
Hello? Anyone?
Click to expand...
Click to collapse
do you enable dt2w on settings? If it doesn't work you can try download kernel adiutor on play Store. Open it and go to wake and enable it on boot. See if it works.
Zasnizas said:
do you enable dt2w on settings? If it doesn't work you can try download kernel adiutor on play Store. Open it and go to wake and enable it on boot. See if it works.
Click to expand...
Click to collapse
Tks let me try
Zasnizas said:
do you enable dt2w on settings? If it doesn't work you can try download kernel adiutor on play Store. Open it and go to wake and enable it on boot. See if it works.
Click to expand...
Click to collapse
Hiou said:
My rmn4x has not working dt2w, i tried many roms but nothing change, i really need help :highfive:
Click to expand...
Click to collapse
If settings and kernel adiutor isn't showing d2w then probably it isn't supported by your display.
MyNameIsRage said:
If settings and kernel adiutor isn't showing d2w then probably it isn't supported by your display.
Click to expand...
Click to collapse
So i need to change my screen ?
MyNameIsRage said:
If settings and kernel adiutor isn't showing d2w then probably it isn't supported by your display.
Click to expand...
Click to collapse
Ss here, so my display not support and i need to replace it with new one ?
MyNameIsRage said:
If settings and kernel adiutor isn't showing d2w then probably it isn't supported by your display.
Click to expand...
Click to collapse
Setting system still show dt2w, kernel adiutor didnt
Hiou said:
Setting system still show dt2w, kernel adiutor didnt
Click to expand...
Click to collapse
maybe your stock kernel don't support DT2W . You can try custom kernel that support dt2w ie Franco kernel . But before that make a backup first before doing anything.
Hiou said:
Setting system still show dt2w, kernel adiutor didnt
Click to expand...
Click to collapse
How old is your phone?
MyNameIsRage said:
If settings and kernel adiutor isn't showing d2w then probably it isn't supported by your display.
Click to expand...
Click to collapse
MyNameIsRage said:
How old is your phone?
Click to expand...
Click to collapse
My uncle gave it to me, is been 2 months
Zasnizas said:
maybe your stock kernel don't support DT2W . You can try custom kernel that support dt2w ie Franco kernel . But before that make a backup first before doing anything.
Click to expand...
Click to collapse
Tks u but i already try FK, but no Wake Gestures tab in Kernel Adiutor
Hiou said:
Tks u but i already try FK, but no Wake Gestures tab in Kernel Adiutor
Click to expand...
Click to collapse
that weird did you have working dt2w when you are on stock room?
Zasnizas said:
that weird did you have working dt2w when you are on stock room?
Click to expand...
Click to collapse
I got 2 mido, 4x both, black one works perfectly and when i boot in to recovery redwolf, it takes double tap to wake from black screen, blue one is the problem here and redwolf takes ONLY single tap to wake, and i cannot use dt2w on official miui either, whats wrong with my device
Hiou said:
I got 2 mido, 4x both, black one works perfectly and when i boot in to recovery redwolf, it takes double tap to wake from black screen, blue one is the problem here and redwolf takes ONLY single tap to wake, and i cannot use dt2w on official miui either, whats wrong with my device
Click to expand...
Click to collapse
maybe the device is the older one. one which was being produced before xiaomi opted for some other type of screen
Hiou said:
I got 2 mido, 4x both, black one works perfectly and when i boot in to recovery redwolf, it takes double tap to wake from black screen, blue one is the problem here and redwolf takes ONLY single tap to wake, and i cannot use dt2w on official miui either, whats wrong with my device
Click to expand...
Click to collapse
maybe you got defective one, only one way to know it you must go to the service center and ask them to check it.
Thank you guys all #MyNameIsRage and #Zasnizas
I think i will go to the Mi Center to check it
Below are Stock kernels with DT2W added. The kernels have been extracted from 47.2.A.11.228 firmware.
The kernels are SElinux enforcing (same as stock). They are in no way custom, all i have done is add the dtb from Iovf's .107 kernel to allow double tap 2 wake.
Some people have reported the DT2W feature requires a solid tap, and sometimes may not wake the screen instantly.
This is out of my hands, and capabilities, to do anything about.
Installation:
On stock .228 firmware:
Flash the kernel for your device in TWRP
Flash whatever Magisk.zip you prefer, and reboot. Once rebooted, install the magisk module below (DT2W_Magisk Module) and reboot.
(If you want permissive selinux, also install the Permissive module in Magisk at the same time).
eXistenZ users:
The kernels are also compatible. Same install steps apply (flash kernel, flash magisk, reboot)
If.you want to keep SElinux set to enforcing, use the DT2W_Magisk Module.
If you are using something to set SElinux to permissive for fonts (or whatever reason), you dont need the DT2W Magisk Module, only the Permissive module.
Also attached are the TWRP flashable stock .228 kernels.
Thanks to @iovf for the original kernels I pinched parts from.
Thanks to @shoey63 for the DT2W Magisk Module.
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Did you flash magisk after kernel?
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Which kernel? Single or dual?
kojak1989 said:
Did you flash magisk after kernel?
Click to expand...
Click to collapse
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Beetle84 said:
Which kernel? Single or dual?
Click to expand...
Click to collapse
Single
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
Did tou do it with clean install ? If yes then you must do it with 18.1 and let eXistenZ boot once and for me iovf kernel make freezes.
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
I use v20 on the XZP with no drama, can you try the dual sim kernel and let me know? There is no harm in using a dual kernel on a single sim phone. Thanks.
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
Myself5 said:
I roughly remember looking into this decades ago and the conclusion was that either the XZP/XZ1 kernel is super ****ed (beyond repair) or they have some sort of hardware issue causing the situations. When you used DT2W and combined it with using the power button in a specific order the touchscreen wouldn't work anymore until you turn the screen off/on again using the power button.
Click to expand...
Click to collapse
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Generic123. said:
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Click to expand...
Click to collapse
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Generic123. said:
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Click to expand...
Click to collapse
Will do
Beetle84 said:
Will do
Click to expand...
Click to collapse
Many thanks my dude.
I'm bit courious, as there has been only one person has mentioned what rom and firmware they are using, but for those that are using the the existenz rom have you tried going into the rom display settings and flipping on the dt2w switch to see if it helps..
see pic..
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
theflanker said:
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
Click to expand...
Click to collapse
No idea mate, single and dual are confirmed working. Try flashing the stock kernel, magisk and reboot
Then try the dt2w kernel, magisk and reboot.
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
See above.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Myself5 said:
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
See above.
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Click to expand...
Click to collapse
Thanks for the clarification. Would it be possible for us to determine what our touchscreen manufacturers are? In your case, tap to wake is pretty glitchy. But, in @Beetle84's case, he appears to have little/no issues. It would be nice to see if different touchscreen manufacturers are at play here.