Related
Having a strange issue with ADW.Launcher. From time to time, I will get a white dialog box in the upper right hand corner, almost like it is announcing a notification of some sort, but it's just an empty write box. I think it's triggered by me moving an icon around, but letting it "slip" and not moving it enough, but I'm not really sure. In any case, once that one dialog box appears, nothing short of a reboot will get rid of it. Moreover, I notice that the tablet will freeze up for a few moments at a time as well.
This is on a stock tablet with the Enhancement Pack. Thanks in advance for any help!
festivus said:
Having a strange issue with ADW.Launcher. From time to time, I will get a white dialog box in the upper right hand corner, almost like it is announcing a notification of some sort, but it's just an empty write box. I think it's triggered by me moving an icon around, but letting it "slip" and not moving it enough, but I'm not really sure. In any case, once that one dialog box appears, nothing short of a reboot will get rid of it. Moreover, I notice that the tablet will freeze up for a few moments at a time as well.
This is on a stock tablet with the Enhancement Pack. Thanks in advance for any help!
Click to expand...
Click to collapse
I'm having it too with stock+enh pack 2. It looked as you said like a dialog box, so I tried to press anything that would usually make one - turning the wifi off seems to fix it. Don't ask me why. For now I think I'll switch back to LauncherPro until this is worked out.
This happened to me as well. I currently have adw.launcher EX 1.2.2 running on Tntlite 5.0.0
There is a launcher action called "open notifications" that is the default action associated with one of the launcher gestures -- either up swipe or down swipe (sorry, i don't have the gtab in front of me at the moment). I just made sure i changed that configuration to use a different action.
I have found that when the empty open notification window is there, weird things happen. Setup seems to not work consistently for example.
Also, I swear that I have seen this issue on previous versions of ROMs and not just tntlite 5.0.0.
I don't have a reasonable fix for this other than "don't open notifications". I did try the latest ADW Notifier but that didn't work.
poymeister said:
This happened to me as well. I currently have adw.launcher EX 1.2.2 running on Tntlite 5.0.0
There is a launcher action called "open notifications" that is the default action associated with one of the launcher gestures -- either up swipe or down swipe (sorry, i don't have the gtab in front of me at the moment). I just made sure i changed that configuration to use a different action.
I have found that when the empty open notification window is there, weird things happen. Setup seems to not work consistently for example.
Also, I swear that I have seen this issue on previous versions of ROMs and not just tntlite 5.0.0.
I don't have a reasonable fix for this other than "don't open notifications". I did try the latest ADW Notifier but that didn't work.
Click to expand...
Click to collapse
I've seen this too. That's a great explanation of what it is.
Turning off that gesture makes perfect sense.
A new version of ADW Launcher was released in late October 2012--both free and EX version.
Many things changed from the previous version.
Quite a few people say "it is better," but I have some issues. First, a phenomenon never seen with the previous version...often, after 'doing things,' when the phone returns to the home screen, there are no icons for brief to not-so-brief time. Very disconcerting. They do eventually populate, but it is shocking when it happens and does not leave the impression of a well-produced app.
Second, with previous versions, I =LIVED= with using the dots placed left and right of the bottom dock to move (navigate) from screen to screen. Those have disappeared, even from the fee version. On my phone, using swipes to move the screen usually launches the app your finger first touches to do the swipe--very annoying. Emails to the dev asking if the navigation dots will return have not been answered.
(NOTE: I am not talking about the INDICATOR dots at top that show what screen you are currently on.)
I present this for people who may be considering ADW to know. The previous versions I highly recommend; the latest, I do not unless issues are resolved.
Anyone know an alternative way to show opened apps? When i used Nova i could set one like "pinch out" or something.. On ADW i can't fine the way to do that.. Ι avoid using home button every time..
A new update for ADW EX was just released 11-06-12, 1.3.3.7 on my phone.
It did not put back in the dots that will navigate to different screens.
Also, the phenomenon of icons being completely missing (blank screen) after settings changes remains as well.
Disappointment continues.
Its crap. I use menu button unlock in my phone and when I do it pops up the settings screen. No way to disable it. I sent an email to the dev and got no response. going back to the old one.
Sent from my HTC Inspire 4g using xda premium
toxicpaulution said:
Its crap. I use menu button unlock in my phone and when I do it pops up the settings screen. No way to disable it. I sent an email to the dev and got no response. going back to the old one.
Click to expand...
Click to collapse
He has not answered any of my two emails to him either.
Does anyone have the old ADW apk? I have a TitaniumBackup, but file in it is not the apk. ???
Attached is a screenshot to prove I have the EX version. If you only have non-EX, I will even use that--I hate this new version so much.
The ghost icons effect happens to me each time I change any ADW setting, for me it is no problem because I think it is due to the need of restarting app to make changes happen. I prefer the old scheme when you press the menu button, but I think it is just a matter of habit. Anyway, bugless for me as the previous one, and quite smooth, more than Go Launcher for example, at a friend's Galaxy 3 it makes the phone itself way faster than with Go Launcher.
Goalba said:
The ghost icons effect happens to me each time I change any ADW setting, for me it is no problem because I think it is due to the need of restarting app to make changes happen. I prefer the old scheme when you press the menu button, but I think it is just a matter of habit. Anyway, bugless for me as the previous one, and quite smooth, more than Go Launcher for example, at a friend's Galaxy 3 it makes the phone itself way faster than with Go Launcher.
Click to expand...
Click to collapse
I just don't see anything that is better than before, and several (important to me) things that are much worse...the "ghost" icons--I call them disappeared icons as they are gone for a LONG time on my phone, and the removal of the navigation dots for screen moves, which was my total navigation mode.
When I swipe to move screens, half the time I activate an app where my finger first touches the screen. Argghhh! I need the dots back. Author won't even answer.
OK, I think I have had a mind out of body situation here...
I deleted the new ADW EX and installed the old one (1.3.3.56). Am in the process of adding my shortcuts to the various 7 screens and setting the options and dock.
BUT...
the main reason I switched back was to get back my "navigation dots" left and right of the dock that I used to navigate from screen to screen. I cannot find how to turn the on in the options.
I have looked and looked. Can someone have mercy on me and tell me how those are commanded to be there, please?
(I KNOW they used to be available because I used them ALL THE TIME to move to different screens.)
This little app acts as a replacement or companion to the default systembar on tablets. It can hide and restore systembar on most Android 3.x and 4.x devices.
Also like similar apps it requires root.
Unlike "GMD Hidebar" or "Hide Bar" which are recommended for simply using the device in "Kiosk mode" this app is meant to be more like an replacement for the systembar. It provides two configurable softbuttons which can be configured in position, size, color and transparency or can be completely disabled.
Several actions can be assigned to the buttons. Each button holds up to three actions, one for short, one for long click and one for swipe above the button. Possible actions:
Nothing: Um, yeah.. this does... nothing. Not sure why I implemented this.
Go back: Acts as the known "back" button to navigate back within apps.
Go to homescreen: Shortcut to directly go to homescreen... just like at the original systembar
Show recent apps: Will show a little panel to quickly switch between recently used apps. Unfortunately the well known "swipe to kill" function of the original can't be implemented because the necessary permission is only granted to apps with systems signature.
Restore systembar: An action to quickly restore systembar. With the latest version this can also be done by notification.
Show notifications: The second most important feature of the systembar. It shows a panel displaying the notifications. It is a complete reimplementation so some features are not available for now. The basic function works well on most devices.
Open apps menu: Older apps usually display their menu-button within the systembar. This action now can open the menu for those apps.
Pie Menu: Opens a configurable Pie Menu next to the touch area. This menu can be configured individually for each event.
This free version is fully functional and should be absolutely sufficient for most users. For lazy ones like me, who don't want to manually hide'n'restore systembar each time, there is a "plus"version available which automatically hides systembar for selected apps.
Oh, and yes, the free version shows a little advertisment for the plus version once in a while... if you want to get rid of it: just click this advert three times and it won't appear again. If you didn't buy the plus version after visiting it's store entry three times you probably won't ever.
please feel free to post critics, bug-reports, requests and suggestions
changelog:
1.0:
Initial release
1.1:
Improvement: wallpaper restoring much faster
Added settings for position and design of toucharea.
1.2:
Implemented panel for recently used apps
Added option for hiding systembar on boot
1.3:
Bugfixes
1.4:
Implemeted notification to quickly hide systembar
Added second touch area to use more actions
Touch areas now can be hidden completely
Fixed recentspanel not being hidden on buttonclick
Fixed toucharea not appearing under rare circumstances
1.5:
Implemented Notificationspanel
Added new action to access applications menu
Touch areas now always being composed correctly
Fixed apps malfunction on some devices (pfff.. the damn wrong environment issue most root-app-developers stumble upon)
1.5.1
Bugfixes
German translation
Visual feedback on buttonpress
1.5.2
Added information about battery, wifi and bluetooth in notificationpanels header
Support for big notifications in JellyBean
Changed unit for size of toucharea to dip (density independent pixel)
Fixed lost ability to accept calls on some phones
Added about- and contact-info
1.5.3b
No new features for now...
Service running more reliable. Should always restart after crash, manual or oom-kill
Removed full!screen from recent-apps-list (people swipe'n'killed full!screen from that list and wondered why it wouldn't work anymore )
1.6b1
few bugfixes.
New action: Pie Menu... this opens a Pie menu next to the touch area which can be freely configured for any event.
New event: Swipe... a third action can be assigned to the button which will be invoked when swiping over the button.
New extended options: activate them within the apps Options menu to freely change color and feedback of touch areas or to change long click timeout.
1.6
just bugfixes
Works good, I just need the notification area back and it's perfect!!
Works great for me.
Suggestions:
Multi colors
allow back button to exit the recent apps. Could not find any way to exit the recent apps when selected.
Sweet, this works for ICS too? Gonna try it out now.
synergeticink said:
Works great for me.
Suggestions:
Multi colors
allow back button to exit the recent apps. Could not find any way to exit the recent apps when selected.
Click to expand...
Click to collapse
Thanks for your feedback.
The recent apps panel should be closed when tapping on back button or anywhere alse outside the panel.
Well there is indeed a issue when "short click action" is set to something else than "Go back". Then tapping on button does not hide the panel. Did you mean this? I'll fix that.
I just got a message the wallpaper-workaround does not work at all on one device.
Since the wallpaper-issue was one of my main topics I am eager to solve this.
At least me and some testers never ran into this problem: if anyone else experiences this, please drop me a line. I need to collect some information to delimit that issue.
update:
the latest version now introduces the missing Notifications Panel.
At least for me the missing access to notifications was the only reason to ever restore the original systembar. So now it nearly always stays hidden.
A little drawback: new notifications so far are only being reported by sound. My own tablet doesn't have a LED and Vibro, so I personally am not missing this.
Hope you like it!
Great little app and I would be happy to shell a couple of bucks for it, one suggestion if I may though: it seems to be the case that all those who develop this kind of on-screen button apps forget to put a feedback for when the button is being pressed (momentary change of color preferably).
Since your app seems to be of the most complete offerings I think it would be great if you were to implement it in a given future. Android devices are often no strangers to lag so a feedback of any kind (that the button was actually pressed) I think it would improve the usability by quite a lot and hopefully it is easy to be implemented too...
Again thanks for this great app, here's looking forward for future updates
Stevethegreat said:
..., it seems to be the case that all those who develop this kind of on-screen button apps forget to put a feedback for when the button is being pressed (momentary change of color preferably).
Click to expand...
Click to collapse
Seems that those developers hardly ever imagine to operate an Android device with somthing else than their big Wurstfinger-thumbs
When I use the app I don't see the buttons since they are completely covered by my fingers. But you are right, when using eg. one of those attach-to-TV-Android-sticks which are operated by mouse and keyboard, and having systems touch sounds disabled, there is no feedback at all.. It's pretty easy to implement such optical feedback, soon to be done.
thanks for your suggestion.
Tsorn said:
Seems that those developers hardly ever imagine to operate an Android device with somthing else than their big Wurstfinger-thumbs
When I use the app I don't see the buttons since they are completely covered by my fingers. But you are right, when using eg. one of those attach-to-TV-Android-sticks which are operated by mouse and keyboard, and having systems touch sounds disabled, there is no feedback at all.. It's pretty easy to implement such optical feedback, soon to be done.
thanks for your suggestion.
Click to expand...
Click to collapse
Thanks
Not much else to suggest -I guess- sort from allowing more actions (through the press of the buttons) but that can be done later... oh and a way to have the buttons accessible regardless of being fullscreen or not (for those who'd love to have "hot corners" at all times)... oh and a minor bug report now that we're at it: upon reboot the app gets superuser permission but does not procede to enable the service (even though I have "enable at boot" selected).
Again thanks for this great app, loving it so far
This works really well on the Nexus 7. I was using GMD gesture control and i had remapped my volume buttons so they could be used as back and home but this is much handier. I can now have my buttons back.
Many thanks
I bought the paid version.
I have been looking an app like this for a while, tried others but this is perfect for what i want.
Top job!!
The latest version includes visual feedback for button-press. I chose a not to flashy color, hope you like it. I am thinking of implementing the before suggested user-colorable buttons but this may take some time...
Stevethegreat said:
Thanks
... oh and a minor bug report now that we're at it: upon reboot the app gets superuser permission but does not procede to enable the service (even though I have "enable at boot" selected).
Click to expand...
Click to collapse
mhh, I could only confirm this behaviour when setting SuperSu to prompt for granting su-access to the app. Which su-Manager are you using?
Did you set your su-Manager to automatically grant access to full!screen? This is necessary because the timeout waiting for su-access is set to 10 seconds... Since full!screen uses that accessibility-service it gets loaded at very early stage... far before other apps get loaded. Depending on how long it takes to fully load the system the timeout might occur even before the su-Manager gets a chance to Display it's confirmation-dialog.
Tsorn said:
The latest version includes visual feedback for button-press. I chose a not to flashy color, hope you like it. I am thinking of implementing the before suggested user-colorable buttons but this may take some time...
mhh, I could only confirm this behaviour when setting SuperSu to prompt for granting su-access to the app. Which su-Manager are you using?
Did you set your su-Manager to automatically grant access to full!screen? This is necessary because the timeout waiting for su-access is set to 10 seconds... Since full!screen uses that accessibility-service it gets loaded at very early stage... far before other apps get loaded. Depending on how long it takes to fully load the system the timeout might occur even before the su-Manager gets a chance to Display it's confirmation-dialog.
Click to expand...
Click to collapse
I was usuing "superuser" so maybe that was why; once I've installed superSu the issue went away and now it boots with my system I've I asked it to
As for the visual feedback it works great but it goes away a bit too soon (Google's own feedback lasts quite a bit longer when one presses -say- the home button) and also it's less than visible when one uses low opacity. I like how the color is discrete though, great choice :good:
All in all I'll recommend this to friends what a great app
BugReport:
While using the app, SnapChat wont work. It FCs. When turning off fullscreen, it works.
Edit: To be to the point; One can take a picture with snapchat and put a comment on it, but when you press "send" it FCs.
dmbardal said:
BugReport:
While using the app, SnapChat wont work. It FCs. When turning off fullscreen, it works.
Edit: To be to the point; One can take a picture with snapchat and put a comment on it, but when you press "send" it FCs.
Click to expand...
Click to collapse
installed this SnapChat on my tablet and could send and receive pictures without problems. I am just to blind to find a place to enter a comment to the picture!?
Anyway, I doubt I could do anything about another app complaining about missing systembar or something...
Is it a phone you installed the app to? ... there are some problems known with phone devices like not receiving calls anymore.. may be it's some related problem. :-/
Tsorn said:
installed this SnapChat on my tablet and could send and receive pictures without problems. I am just to blind to find a place to enter a comment to the picture!?
Anyway, I doubt I could do anything about another app complaining about missing systembar or something...
Is it a phone you installed the app to? ... there are some problems known with phone devices like not receiving calls anymore.. may be it's some related problem. :-/
Click to expand...
Click to collapse
You just click the screen for adding a comment.
Anyhow, yes. Its a phone. Its my Xperia V.
I got quite a few apps tho, so it might just aswell be any other app aswell.
But I found it to good to be a coincidence when I disabled fullscreen and then it worked.
The FC still happends when I dont comment btw.
But it might be SC complaining ofcourse. But its no problem, I just added an invisible button to get the systembar back before I take pictures with SC.
Your app is the only one working properly btw. the lower left and right buttons that you've added are perfect. I can make them small and invisible wich makes it perfect. GREAT job!
Keep up the good work.
I'd like the option to have the notification bar on, but the onscreen buttons off, with just the corner buttons etc., if that makes sense. I like having the notification bar on, I think it's useful. Apologies if there is a way to do this already, I couldn't seem to find it.
It would be good if it rearranged the app icons too to fill the extra space better.
Or alternatively, I would like notification on, original onscreen buttons on but transparent with screen visible behind them, that would be a good option too, I think.
Thanks for the app though.
TheGSL said:
I'd like the option to have the notification bar on, but the onscreen buttons off, with just the corner buttons etc., if that makes sense. I like having the notification bar on, I think it's useful. Apologies if there is a way to do this already, I couldn't seem to find it.
It would be good if it rearranged the app icons too to fill the extra space better.
Or alternatively, I would like notification on, original onscreen buttons on but transparent with screen visible behind them, that would be a good option too, I think.
Thanks for the app though.
Click to expand...
Click to collapse
Unfortunately that not possible at all... at least not without patching original systemUI. Buttons bar and notifications bar are created by the same process. Disabling this process obviously means disabling both bars. I might implement an internal UI similar to the original systemUI some day. But thats at the end of a long list of wishes and suggestions I got so far, because it would take much, much work.
Re: [App][3.x][4.x] full!screen - App to hide/replace Systembar
Hi, this program is almost perfect for me, but I have a question: given that it's oriented towards tablets, ¿do you foresee any problem using it in a phone?. I've installed the free version in my Xperia T and it seems to work alright, but I want to be sure.
--
Enviado desde mi móvil.
AT&T LG G3, love the phone. I'm down for the lollipop update, but I can't seem to remedy one new Lollipop problem.
At various times, i haven't figured out exactly what causes it, but when i drag down my notification bar, during just normal use of my phone, I can see various notifications from applications, but NO DETAILS, only a line saying "Unlock to see sensitive". Of course my phone is unlocked as I AM USING IT!! I tried going into settings/sound/notifications/turning SHOW ALL NOTIFICATIONS on, and then you can go into apps individually to set notification preferences, but nowhere does it say anything about setting sensitivity for individual apps. This seems to be a bug. I've dug through all the possible settings.
One example that has happened to me many times is i'll be on the phone talking, i hear a notification tone, put on speaker phone and drag down my notifications to see what it is, and i only see the app icon, with "Unlock to see sensitive". Then if i press the notification it brings up the application no problem, but that is a pain and i didnt want to open the app, just see the notification. This is sure frustrating.
Any help greatly appreciated.
???????
I am also having random occurrences where all of my drop-downs say unlock to see sensitive. Locking and then unlocking the phone fixes it I have no idea what causes it
I am having the same issue haven't figured out the cause or a fix
I just started having the same issue. I went to Display >>> Lock Screen and noticed that my setting had been set to Swipe to Unlock, even though I've always had it set to None. I switched it back to None and now I can see the notifications again.
This randomly happens to me too. Checking the power button automatically locks screen option is a bandaid solution for me
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.