Related
Hi guys,
Got my Desire HD last Friday and I'm really pleased with it, stunning device. The problem is, I'm using a case which protects the phone nicely and looks decent too but the power button is very tough to press in (let alone without a case TBH). I have Cyangens "Menu Unlock" enabled but I'm wondering if there is a tweak or APK to enable the capacitive buttons when the screen is off so I can turn it on easily (using Button Remapper). Maybe even a shake to enable app to wake the phone. Oh, cover below:
When I had the Galaxy S, I could just wake the screen with the main physical Home button.
When I had the Milestone, there was an APK to allow me to wake the screen with the buttons.
Any help or direction would really be appreciated. Would love to be able to unlock it that easily.
Cheers #auggie2k
Just a quick bump
auggie2k said:
Hi guys,
Got my Desire HD last Friday and I'm really pleased with it, stunning device. The problem is, I'm using a case which protects the phone nicely and looks decent too but the power button is very tough to press in (let alone without a case TBH). I have Cyangens "Menu Unlock" enabled but I'm wondering if there is a tweak or APK to enable the capacitive buttons when the screen is off so I can turn it on easily (using Button Remapper). Maybe even a shake to enable app to wake the phone. Oh, cover below:
When I had the Galaxy S, I could just wake the screen with the main physical Home button.
When I had the Milestone, there was an APK to allow me to wake the screen with the buttons.
Any help or direction would really be appreciated. Would love to be able to unlock it that easily.
Cheers #auggie2k
Click to expand...
Click to collapse
Buttons will be disabled when phone is asleep. The closest is to try "Tap Tap App" from the Market. Its free. Try and see how it could give you possibilities. Basically, it will allow you to set lock/wake permissions using the proximity sensor.
I use it as an alternative to pressing the power button all the time during shorter phone sleep/wake intervals
Much appreciated Jacob, cheers for the quick reply.
You can try WidgetLocker too, allow you to power up the phone using volume button.
auggie2k said:
Maybe even a shake to enable app to wake the phone.
Click to expand...
Click to collapse
now THAT is a cool idea
but, it would drain the battery...
panyan said:
now THAT is a cool idea
but, it would drain the battery...
Click to expand...
Click to collapse
Its possible without much battery drain I remember using Pocketshield with the HD2 where it unlocks when you flip the phone facedown and up or shake from side to side. Seems they're still hung up on Windows till now... I hope they come around to turn to Android soon
auggie2k said:
Much appreciated Jacob, cheers for the quick reply.
Click to expand...
Click to collapse
You're welcome mate! Test the proximity settings, I used to use "Easy Detection" but found it too sensitive, it unlocks with short finger waves which was cool but also gets screwed up with strong winds when outdoors... lol
Since, I've changed the setting to "safe mode (default)" and it responds well to 2 mild taps. Hope it works for you too!
bryant_16 said:
You can try WidgetLocker too, allow you to power up the phone using volume button.
Click to expand...
Click to collapse
only works if u're on stock kernel
try no lock, unlocks it with the volume buttons.
rossysaurus said:
try no lock, unlocks it with the volume buttons.
Click to expand...
Click to collapse
isnt this the same as widget locker, i.e. it works only on stock kernel
Just installed "Tap Tap App", works perfect for me as an alternative unlock/lock. Thanks a lot!
Jacob1369 said:
Buttons will be disabled when phone is asleep. The closest is to try "Tap Tap App" from the Market. Its free. Try and see how it could give you possibilities. Basically, it will allow you to set lock/wake permissions using the proximity sensor.
I use it as an alternative to pressing the power button all the time during shorter phone sleep/wake intervals
Click to expand...
Click to collapse
Jacob1369 said:
You're welcome mate! Test the proximity settings, I used to use "Easy Detection" but found it too sensitive, it unlocks with short finger waves which was cool but also gets screwed up with strong winds when outdoors... lol
Since, I've changed the setting to "safe mode (default)" and it responds well to 2 mild taps. Hope it works for you too!
Click to expand...
Click to collapse
Those settings work perfectly for me too, it makes the phone seem so much more "fancy" and has already spooked my poor iPhone owning friend, lots of WTF's Cheers for the suggestion.
auggie2k said:
Those settings work perfectly for me too, it makes the phone seem so much more "fancy" and has already spooked my poor iPhone owning friend, lots of WTF's Cheers for the suggestion.
Click to expand...
Click to collapse
lol... I was doing the exact same thing to my buddies with an iP4
I just bought the new nook with glowlight. Previously, my wife and I shared the basic kindle 4 without touch. My experience so far has been great. I prefer the nook interface to the kindle, and the glowlight has been a godsend - my wife hates any light while she is sleeping, and the glowlight at its lowest setting doesn't bother her and is perfect for reading in the dark.
The biggest adjustment for me coming from the non-touchscreen kindle, is having to deal with incidental page turns. While looking for the optimal position to read and hold the nook, I often find it most comfortable to have my hand on the actual screen. Sometimes I also like to follow along with my finger. Both of these actions will cause the nook to perform unintended page turns, or at the very least bring up the menu. Sometimes I have to spend a large portion of my reading time just finding my page again.
I realize that with time I can learn to be more careful and only hold the nook by the bezel. But, since the nook has those wonderful physical page turn buttons, I figured it has to be possible (assuming the nook is rooted), to disable the touchscreen while reading a book. Maybe a button could be added to the nook menu (the options that display when you hit the n button) that toggles between enabling/disabling the touchscreen. I’ve searched for a way to implement a feature similar to this but haven’t been able to find anything. Does anyone know if there is a way that I can accomplish this for my nook?
Is it possible to disable the Zforce touch screen? Yes
Is it possible to enable the Zforce touch screen? No
Apparently there is a bug in the driver.
To disable the touch screen:
Code:
# cat /sdcard/zero.txt>/sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Where zero.txt is a single byte file of the digit zero without any line termination.)
There is also the issue that if you do turn off the touch screen you would have to use a hard button to turn it back on.
Renate NST said:
Is it possible to disable the Zforce touch screen? Yes
Is it possible to enable the Zforce touch screen? No
Apparently there is a bug in the driver.
To disable the touch screen:
Code:
# cat /sdcard/zero.txt>/sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Where zero.txt is a single byte file of the digit zero without any line termination.)
There is also the issue that if you do turn off the touch screen you would have to use a hard button to turn it back on.
Click to expand...
Click to collapse
So I take it then that there is no existing method to do this. Does this mean that we can disable it but would never be able to re-enable it due to the bug?
Regarding the issue of using a hard button to turn it back on, I figure the n button could be used, but there is still the bug.
davidsimon said:
So I take it then that there is no existing method to do this. Does this mean that we can disable it but would never be able to re-enable it due to the bug?
Regarding the issue of using a hard button to turn it back on, I figure the n button could be used, but there is still the bug.
Click to expand...
Click to collapse
If i remember right its been a while... Cool reader allows you to customize the touch screen zones (there i 9 i think) to do different things... one of the options is to do nothing. You can also set cool reader to be the default app so when you click a book in the library it automatically opens in cool reader. By setting ever touch screen zone to do nothing its would technically disable the touch screen while reading. because none of the zones would turn the pages. but once you exit the app or hit the N button the screen would still work.
check it out if your rooted.
Well, that's another way to do things, have an app over the target app that captures the touches and does nothing.
You could also patch the stock Reader so that it doesn't respond to any screen touches.
That's actually quite easy.
It would have the advantage of not affecting anything else.
Personally, I find the hard keys too hard and I always use touches on the stock Reader to turn pages.
persichini said:
If i remember right its been a while... Cool reader allows you to customize the touch screen zones (there i 9 i think) to do different things... one of the options is to do nothing. You can also set cool reader to be the default app so when you click a book in the library it automatically opens in cool reader. By setting ever touch screen zone to do nothing its would technically disable the touch screen while reading. because none of the zones would turn the pages. but once you exit the app or hit the N button the screen would still work.
check it out if your rooted.
Click to expand...
Click to collapse
You actually don't need to do that in coolreader it has a disable touch screen option I have just set one of the buttons to disable and enable touch when I double press.
Dopedangel said:
You actually don't need to do that in coolreader it has a disable touch screen option I have just set one of the buttons to disable and enable touch when I double press.
Click to expand...
Click to collapse
Way cool, but I can't find the option. Where is the disable touch screen option?
Thanks!
Dopedangel said:
You actually don't need to do that in coolreader it has a disable touch screen option I have just set one of the buttons to disable and enable touch when I double press.
Click to expand...
Click to collapse
I'm interested in this, too. Send us the instructions!!
_ig_ said:
I'm interested in this, too. Send us the instructions!!
Click to expand...
Click to collapse
Open Options, and go to the fourth tab (this one with a pin icon). There u have 'Key actions'. You can assign to your buttons different actions - eg. Lock/unlock touch screen. Works great
Rafsen said:
Open Options, and go to the fourth tab (this one with a pin icon). There u have 'Key actions'. You can assign to your buttons different actions - eg. Lock/unlock touch screen. Works great
Click to expand...
Click to collapse
Awesome.
davidsimon said:
So I take it then that there is no existing method to do this. Does this mean that we can disable it but would never be able to re-enable it due to the bug?
Regarding the issue of using a hard button to turn it back on, I figure the n button could be used, but there is still the bug.
Click to expand...
Click to collapse
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
_ig_ said:
[...] Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Not sure about such battery life with wifi on. If I leave wifi on but the device otherwise off, I lose 3-5% battery per hour. With wifi off, it's good for a week or more, easily. I think the idea of disabling the IR sensors is great, but I'm not sure the battery savings will be enough to allow you to leave the screen active and wifi on.
had a look at the kernel code in zforce.c which I believe is the one in my multitouch hacked kernel (https://github.com/arkusuma/nook-touch-multitouch/blob/master/zforce.c)... basically
echo 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
works to switch it off, but
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
doesn't work, nor does
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/cmd
which should have a similar effect (ret = i2c_smbus_write_byte(tsc->client, cmd); where cmd = #define COMMAND_ACTIVATE 0x01)
all this said, when I get the nook to sleep by pressing the on/off button on the back I believe it goes into "deep_sleep" after a couple of secs; at this point, pressing the "n" button on the front restores the IR, so I suspect it's calling "static int zforce_resume(struct i2c_client *client)" which in turn checks whether the device was indeed on deep_sleep mode before re-initializing touch (IR) and the interrupt as per below code snippet. So, re-enabling IR should be OK but I don't want to monkey around with zforce.c... in terms of battery life, I am still checking stats before/after and I believe it goes from a 4% drop w/screen + IR + wi-fi on to about 1.5% drop if IR is disabled, but I need more time to quantify this gain in battery life.
if (deep_sleep == 0)
return 0;
zforce_touch_hw_init(1);
enable_irq(tsc->irq);
I want a way to do this too.
I already ruined a touch glow screen by simply handling it for a week without a case. No one had any idea at that time how ridiculously delicate the light-carrying film was and how it makes big starburst lights around every crack and blemish, and how effortlessly those cracks form.
So now I DO know I have to be fanatically paranoid about letting anything touch the screen that might put a crack or a scratch in it.
That means at the beach it simply must be inside a ziplock bag to keep sand off.
We need a way to disable the IR so things like a plastic bag don't activate it, and operate the device entirely from hardware buttons EVEN THOUGH yes I agree I don't like the bezel buttons for page turns either, NORMALLY.
Sent from my EVO using xda premium
I have a rooted nook simpletouch I got at Goodwill and wanted to chime in on how to disable touch for books:
Moon+ Reader allows you to disable screen touches too. Tap the center screen while in a book, press the cog that appears in the lower right, change everything in control options to "none" (the side clicky-buttons will still flip pages), then go to Miscellaneous and check "Disable vertical scrolling on touch" and uncheck "Allow fling horizontally to turn page."
I still have to touch the center of the screen to bring up options, but it's very intelligent and only responds to a quick tap -- not a long press of my thumb as I hold the nook awkwardly while reading in bed.
_ig_ said:
had a look at the kernel code in zforce.c which I believe is the one in my multitouch hacked kernel (https://github.com/arkusuma/nook-touch-multitouch/blob/master/zforce.c)... basically
echo 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
works to switch it off, but
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
doesn't work, nor does
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/cmd
which should have a similar effect (ret = i2c_smbus_write_byte(tsc->client, cmd); where cmd = #define COMMAND_ACTIVATE 0x01)
all this said, when I get the nook to sleep by pressing the on/off button on the back I believe it goes into "deep_sleep" after a couple of secs; at this point, pressing the "n" button on the front restores the IR, so I suspect it's calling "static int zforce_resume(struct i2c_client *client)" which in turn checks whether the device was indeed on deep_sleep mode before re-initializing touch (IR) and the interrupt as per below code snippet. So, re-enabling IR should be OK but I don't want to monkey around with zforce.c... in terms of battery life, I am still checking stats before/after and I believe it goes from a 4% drop w/screen + IR + wi-fi on to about 1.5% drop if IR is disabled, but I need more time to quantify this gain in battery life.
if (deep_sleep == 0)
return 0;
zforce_touch_hw_init(1);
enable_irq(tsc->irq);
Click to expand...
Click to collapse
_ig_ said:
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Has anyone worked on this at all? IG, if you have that apk to turn the IR off still, I would greatly appreciate it. I have been messing a lot with the NST and I would love to be able to conveniently turn off the IR. I don't mind having to turn the Nook off and on again with a long press to get the IR back on.
ALinkToTao said:
Has anyone worked on this at all? IG, if you have that apk to turn the IR off still, I would greatly appreciate it. I have been messing a lot with the NST and I would love to be able to conveniently turn off the IR. I don't mind having to turn the Nook off and on again with a long press to get the IR back on.
Click to expand...
Click to collapse
The reason why I want to do this is to save battery life while running a large print clock app which I found called NightClock which came from android 1.6 donut. I can leave the clock app open but turn off the IR sensors to save battery and let it run longer without a charge. I'd also like to do this using renate's simple reader app and using the side buttons to turn pages.
_ig_ said:
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Does anyone have his apk or anything similar that will disable the IR array? I'd really like to use this for various applications. I don't mind at all having to reboot by holding the power button down. This could be used for Nooks with bad IR arrays to re-use them as really low battery clocks or calendars, and would also be good for extreme battery savings while reading (using the side buttons only for page turning).
ALinkToTao said:
Does anyone have his apk or anything similar that will disable the IR array? I'd really like to use this for various applications. I don't mind at all having to reboot by holding the power button down. This could be used for Nooks with bad IR arrays to re-use them as really low battery clocks or calendars, and would also be good for extreme battery savings while reading (using the side buttons only for page turning).
Click to expand...
Click to collapse
it's been a while... 6 years... let me see if I can find it...
When the NST is not actively tracking your finger only one IR LED is being flashed occasionally.
I really don't think the current usage is that high, although I can check.
If you are having trouble with the IR touch screen the problem could be a) dirt, b) alignment of the plastic lenses.
You can try the Touch.apk (in the signature) to visualize where the problem is.
Is there a way to wake up and unlock the phone with a fingerprint scan? Aka without waking up the phone prior to scan to unlock...let's say all in one ?
Gesendet von meinem SM-G935F mit Tapatalk
Do not get the question, I press the home button and it unlocks it pretty much instantly with my fingerprint!
Do you mean without actually pressing the Home Button, well that would mean that the finger print sensor would have to be constantly scanning, think your battery would die pretty quickly
Yes i believe. "Without pressing the home button" is a feature in many phones like Xiaomi. It's a good feature but I think that with this button design it will be a problem. Fingerprint will always looking for a match even when it's being held in your hand.
Yes, without pressing the button should be an option. The button is already capacitive. So, this can be achieved just like the edge screens are sensitive too.
But then the phone is always looking for input, whether scanning for a finger print or looking for capacitive touch on the button. May be ok if the phone is in hand but for me that sort of defeats the purpose as this would be a better feature to unlock if the phone was on the desk.
I am by no means knocking the feature request or OP but personally cannot see much benefit from simply just pressing the button even if it only saves a few % of battery for me...
chippyuk said:
Do not get the question, I press the home button and it unlocks it pretty much instantly with my fingerprint!
Do you mean without actually pressing the Home Button, well that would mean that the finger print sensor would have to be constantly scanning, think your battery would die pretty quickly
Click to expand...
Click to collapse
I think the way that other phones work is that they scan for input only when the sensor is touched. So the iphone for example has a capacitive sensor on the finger print reader and knows when to start matching for fingerprints. This means that the phone isn't constantly scanning and doesn't use any more battery than the existing solution.
IMO Samsung probably should have implemented this feature.
le_lutin said:
I think the way that other phones work is that they scan for input only when the sensor is touched. So the iphone for example has a capacitive sensor on the finger print reader and knows when to start matching for fingerprints. This means that the phone isn't constantly scanning and doesn't use any more battery than the existing solution.
IMO Samsung probably should have implemented this feature.
Click to expand...
Click to collapse
Well on my iPhone 6s and all the previous ones I have had, I still have to press the home button for it to scan the finger if the screen is off, I cannot simply touch it to unlock. Once the phone is on then yes, the button is sensitive to touch, for example double touch to shrink the screen etc... Either way the phone has to constantly monitor for capacitive input even when it is off right, there must be some battery sacrifice for that. Of course it will use more battery than the existing solution as it will constantly be looking for capacitive touch input
Adding to this though, I would like the capacitive side of the home button to be available when the screen is on...
Probably not precisely what you're looking for, but search in settings for "Easy screen turn on" - under Personal -> Accessibilty -> "Dexterity and Interaction" on my device.
Enabling this will allow you to wake up the screen based upon a gesture, and then you can use fingerprint to unlock without actually pressing any hard buttons.
Ok thnx a lot guys
Gesendet von meinem SM-G935F mit Tapatalk
This is some lazy stuff man. Trying to avoid a having to press a button that you're already touching? To save what, a couple milliseconds?
munnarg said:
This is some lazy stuff man. Trying to avoid a having to press a button that you're already touching? To save what, a couple milliseconds?
Click to expand...
Click to collapse
I think the purpose is to preserve the life of the button itself because the home ans power buttons are the 2 that fails most often over the life of the device. Of course you wouldn't need to worry if you're someone who swaps phones often but some people use their devices for many years and would like to avoid issues with it if possible.
Exactly!
Gesendet von meinem SM-G935F mit Tapatalk
tiskewlio said:
I think the purpose is to preserve the life of the button itself because the home ans power buttons are the 2 that fails most often over the life of the device. Of course you wouldn't need to worry if you're someone who swaps phones often but some people use their devices for many years and would like to avoid issues with it if possible.
Click to expand...
Click to collapse
I did adore this on my iPhone 5s, I am not sure if I would want it on a Edge right now, I am kind of looking for the place to hold the phone anyway, so another capacitive place would not help
tiskewlio said:
I think the purpose is to preserve the life of the button itself because the home ans power buttons are the 2 that fails most often over the life of the device. Of course you wouldn't need to worry if you're someone who swaps phones often but some people use their devices for many years and would like to avoid issues with it if possible.
Click to expand...
Click to collapse
I recently had to break out an old GS3 phone to use when my primary one died. It was used for more than two years and the home button still works fine. Wearing out the home button isn't a concern of mine.
tiskewlio said:
I think the purpose is to preserve the life of the button itself because the home ans power buttons are the 2 that fails most often over the life of the device. Of course you wouldn't need to worry if you're someone who swaps phones often but some people use their devices for many years and would like to avoid issues with it if possible.
Click to expand...
Click to collapse
To be honest samsung home button very seldom spoil. You don't hear cases of it. From my own experience my s2 lasted over 3 years the phone itself died even though the home button was still perfect. My note 3 is 2.5 yrs now. Home button still perform like day 1. I am pretty sure samsung home button will outlast the phone life.
not available on either my old iphone or my new samsung
yeh i find the fact that you cant just use your fingerprint for unlocking really ****ty. maybe someone'll do an app.
oli_28 said:
I did adore this on my iPhone 5s, I am not sure if I would want it on a Edge right now, I am kind of looking for the place to hold the phone anyway, so another capacitive place would not help
Click to expand...
Click to collapse
How did you get this work on the iPhone? Is it a setting as I have always had to press the button to turn on the screen before it recognises the fingerprint.
chippyuk said:
How did you get this work on the iPhone? Is it a setting as I have always had to press the button to turn on the screen before it recognises the fingerprint.
Click to expand...
Click to collapse
OT: Jailbreak + 'VirtualHome', its actually a fully capacitive home button, I liked it very much..
oli_28 said:
OT: Jailbreak + 'VirtualHome', its actually a fully capacitive home button, I liked it very much..
Click to expand...
Click to collapse
Right, so not delivered functionality!
Did some digging as well and apparently it is not a capacitive button as it does not have capacitive points on it, it simply gives the impression of being similar to capacitive due to the circuit between it and the outer ring. If it was capacitive we would have seen swipe gestures added to it under Jailbreak tweaks...
No app yet for unlock the phone without press home button?
_u2pop_ said:
No app yet for unlock the phone without press home button?
Click to expand...
Click to collapse
Go to Settings / Accessibility / Dexterity and interaction / Easy screen turn on.
But I find it easier to press the home button and then leave my finger on it to unlock, rather than having to do two separate actions (wave then fingerprint).
I'm looking at the Axon 7 as a replacement for my ZMAX 2 but I HATE the power button (way too flimsy and easy to press) and lockscreen (laggy and unlocks by accident). Are the ones on the Axon better?
I would look up the Axon 7 notification bell before you dive in any further but hopefully they will add an option to disable that at some point. Power button is fine IMO. It's below the volume keys so it's different from other phones I've had but its pretty solid feeling. I dont see any lag with the lockscreen but the double tap to wake sucks, if you like using that. As for the unlocking by accident, I would say the sensors don't always behave like you think you will, sort of weird. But overall it doesn't cause too many problems.
I don't even use the power button most of the time. Simply putting my finger on the fingerprint sensor as soon as I pick it up makes it power up the screen and unlock to the desktop immediately. Also I put "Screen Off" app on one of my Pie Control triggers so I can just slide in from the bezel with my thumb and lift from that quadrant to turn it off.
rEVOLVE said:
I don't even use the power button most of the time. Simply putting my finger on the fingerprint sensor as soon as I pick it up makes it power up the screen and unlock to the desktop immediately. Also I put "Screen Off" app on one of my Pie Control triggers so I can just slide in from the bezel with my thumb and lift from that quadrant to turn it off.
Click to expand...
Click to collapse
Youre not on 2017G right? Pie controls don't work on the US models (2017U), just like the on screen buttons.
I use a Nova Launcher gesture to turn the screen off. Double tap to turn off. Phone already has double tap to wake, but as mentioned earlier, most use the fingerprint sensor to unlock. Quick and effective.
Nova launcher gestures ftw. I've set double tap screen to sleep and the capacitive home key set up to turn off screen. Barely use the power key although it's pretty good and sturdy.
Thanks guys-I'm between this and the OnePlus 3 (had the OnePlus One and loved it)!
Some basic info before i begin:
Phone: Moto X Style/Pure on android 5.1.1 (XT1572)
It is rooted, but no custom roms are installed.
So basically what happened was I dropped by phone, then all of a sudden the on screen (Home, Back and Multitasking) buttons started to become unresponsive and started ghosting. I have restarted so many times just to exit an app. After several restarts, my on screen (home, back and multitask) buttons have stopped working.
Firstly my basic and short term solution was to install a 3rd party on screen button app from the play store, this would put a second set of on screen buttons above the stock on screen buttons. But before this I noticed that the on screen buttons actually worked when rotated so that instead of being on the bottom of the screen they would be on top. The on screen buttons also work when i boot into recovery mode, my custom recovery is TWRP. I also wiped dalvik cache and reinstalled my apps through the recovery setup.
I dont know whats going on, I even made it so that when my on screen buttons moved to the top of the screen, i would click on apps from the bottom of the screen and it would work. It doesnt seem to be a hardware issue as i have confirmed it to be working through TWRP and tapping on apps from the bottom of the screen, confirming that my touch screen is working perfectly. The on screen buttons also work and it being detected when TalkBack is enabled.
Help me plez.
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
valest said:
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
Click to expand...
Click to collapse
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Houndz said:
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Click to expand...
Click to collapse
The touch screen issue of this device is hardware related, born with such flaw, you will have it even you didn't drop it.
No sure how it happened, but it helps if you can take it apart and clean the connector a bit and make sure you reconnect it firmly, if that doesn't work, you will have to replace the touch screen part or the whole screen and touch screen and rear frame and stuff, but do notice: it's likely to happen again.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049