Database Info

"Screen Tap" vib instead of clicks? I have an idea.

I've been trying to figure out how this could be done for a few months now. My original idea was a .Net managed app wrapped up in a C++ service which would hook the proper WMessage and cause a short vibrate (reg entry to customize strength, duration, frequency, and wave shape perhaps). After looking into the Vibrating Dialpad registry hack and playing with Sound Schemes (see crediting links below), I'm thinking there may be a far more straight forward way using a simliar approach to Vibrating Dialpad. On the other hand, I'm not sure where *vibrate* gets interpreted so it may not be so simple. Anyone have feedback on this? I think even a basic "haptic" screen feedback would be very welcomed by many people and a cross-device solution seems feasable.
http://forum.xda-developers.com/showthread.php?t=300904
http://forum.xda-developers.com/showthread.php?t=340466&page=3

like this?
http://forum.xda-developers.com/showthread.php?t=425063

Yah, something like that I've been asking around for months and this is the first time I've heard of that app. I'll check it out. The "lag when typing fast" could be a problem, but we'll see. Thanks for the link.

Just like Vibrating Dialpad, the resulting vibration is far too long (at least 1 second) even when I configure it for 1ms. Perhaps this is a limitation of something more low-level on the Vouge?

I've tried a couple of these and the lag is always a problem, the vibration wants to be just a slight buzz and linked to the duration of the screen press. It needs to occur instantly too.
The LG touch screen phone seems to do it well.
But in response, I'd pay for a good app.

@Flipz/Devs, question about lockscreen

Where is the setting that sets the lockscreen timeout to 15 seconds? I still have a huge issue with pocket dialing and would love to adjust it down to 2 seconds (improve battery life as well). I know that it's not in the apk since the default android timeout is the same with the htclockscreen deleted.
Is this a kernel issue that can't be addressed until the source is released?
Thanks for your time.

tstack77 said:
Where is the setting that sets the lockscreen timeout to 15 seconds? I still have a huge issue with pocket dialing and would love to adjust it down to 2 seconds (improve battery life as well). I know that it's not in the apk since the default android timeout is the same with the htclockscreen deleted.
Is this a kernel issue that can't be addressed until the source is released?
Thanks for your time.
Click to expand...
Click to collapse
The timeout should be in the display section of settings.
It actually most likely is part of the apk. HTC modified the settings apk to add the scenes feature in there. Most likely they either modified that part too or, even more likely, they just read the settings for the lock screen in their lock screen apk. Either way, this is what would need to be modified to allow for adjusting of the timeout. Now, that said, there may be a plethor of other places that need to be modified to allow for this change to actually work. Right now this would be a lower priority.

There is already a 15sec lockout option. Go Menu>Sound & Display>Screen Timeout (will be at the bottom of the page).

chuckhriczko said:
The timeout should be in the display section of settings.
It actually most likely is part of the apk. HTC modified the settings apk to add the scenes feature in there. Most likely they either modified that part too or, even more likely, they just read the settings for the lock screen in their lock screen apk. Either way, this is what would need to be modified to allow for adjusting of the timeout. Now, that said, there may be a plethor of other places that need to be modified to allow for this change to actually work. Right now this would be a lower priority.
Click to expand...
Click to collapse
So you're saying that on a vanilla build of android there is a setting for the lockscreen timeout, and that the default android lockscreen is part of the settings.apk?
There is already a 15sec lockout option. Go Menu>Sound & Display>Screen Timeout (will be at the bottom of the page).
Click to expand...
Click to collapse
Not the screen timeout, the lockscreen timeout. In my pocket the menu button can be pressed, then pressed again within a 15 second window to wake the device and magically start dialing. I would like to cut that 15 seconds down to a realistic 2-3 seconds.

That's a good idea and I'm interested to hear if it's possible.

tstack77 said:
Not the screen timeout, the lockscreen timeout. In my pocket the menu button can be pressed, then pressed again within a 15 second window to wake the device and magically start dialing. I would like to cut that 15 seconds down to a realistic 2-3 seconds.
Click to expand...
Click to collapse
Why not just setup a unlock pattern?

gu1dry said:
Why not just setup a unlock pattern?
Click to expand...
Click to collapse
Have you actually tried using one for even just a day...what a giant PITA

tstack77 said:
Have you actually tried using one for even just a day...what a giant PITA
Click to expand...
Click to collapse
I've used the unlock pattern since I purchased the phone, which I got my phone 9 Oct 09...

gu1dry said:
I've used the unlock pattern since I purchased the phone, which I got my phone 9 Oct 09...
Click to expand...
Click to collapse
I commend you then, I didn't last an hour inputting the damn thing every few minutes just to read a text message...but of course I don't need my phone to be that secure so the annoyance > necessity
That said, the lockscreen should be able to accommodate the both of us, and I'm just looking for a solution that works for me.

tstack77 said:
I commend you then, I didn't last an hour inputting the damn thing every few minutes just to read a text message...but of course I don't need my phone to be that secure so the annoyance > necessity
That said, the lockscreen should be able to accommodate the both of us, and I'm just looking for a solution that works for me.
Click to expand...
Click to collapse
And I was simply suggestion a possible solution. Also I have my lockscreen timeout set to 1min.

My personal recommendation: follow the directions in the thread on deleting unwanted apps to root your Hero, remount the filesystem so you can delete HtcLockScreen.apk, then buy LockbotPro & install it instead. The current version is a little buggy in the way it handles reboots (after you reboot, the Android non-HTC lockscreen becomes re-enabled and "first in line"), but it's not too hard to fix when it happens, and it works wonderfully the rest of the time.
To fix it after rebooting, you basically swat away the default Android lockscreen (menu-menu), launch Lockbot, launch its settings menu, un-check "enable lockbot", return to home, relaunch Lockbot, launch its settings menu, re-check "enable lockbot", and you're done. Looking at the changelog, it appears that the bug I just described is a fairly recent new bug, and it looks like the author is releasing updates every couple of days trying to fix it.
Note that Lockbot will "kind of" work if you don't root & delete HTC's lockscreen... but it won't work well because HTC's lockscreen is pretty aggressive about defending its turf. It's a night & day difference. (Sorry if I sound like a broken record, but as they say... there's no zealot like the reformed sinner. If I'd known how easy it would be to fix the #1 thing I hated about my Hero, I'd have done it the afternoon the first "how to root the CDMA Hero" hit the net
I can definitely say that my overall happiness & satisfaction increased dramatically after I did it. It sounds petty, but HTC's dysfunctional/useless lock screen (backed up by Android1.5's annoying & tedious default) really did annoy me to the point where I was starting to dislike my Hero. Rooting & replacing them with Lockbot really made a difference.

Thanks for the recommendation, nice to see I'm not the only one annoyed with the default lockscreen issue.
I tried out LockBot all day yesterday but it still has one major flaw, any/every button will wake the device (not just 'menu' and 'power'). Each time I pulled the phone out of my pocket the screen was on, pretty sure it's the trackball constantly getting tapped in my pocket.
Had to delete it due to battery drain. Still looking for a solution

Need advice for solving persistent glitch

Hello everyone,
It has been a while since I ventured through this forum, but it seems that y'all may be my only hope.
I've been suffering through this glitch/stutter that, when scrolling, the phone registers my finger as taps everywhere my finger slides. All I simply need to do it remove my finger from the phone and I can continue scrolling like normal. It is super annoying and I cannot find out what causes it, it just seems random. It never happened on any of my Nexus phones in the past.
Now, here's a list of things I've tried in order to fix it:
- Safe mode
- Factory Reset (Restore from Google account)
- Factory Reset (New Device option)
- RMA'd through Google support and received a new pixel and the problem persists (even after going through the steps above on the new device)
Here is a short video of the glitch while it is happening.
https://goo.gl/photos/GysQXd82MexVkk836
(Hopefully that link works)
Note: the glitch will not stop until I take my finger off the phone, you can tell when it is happening when I scroll over the share button and it registers as a tap.
If you guys have any suggestions, I'm ready to try anything at this point. I don't want to go through Google support because I know they'll send me yet another Pixel (I've already talked to them again and that was their solution, I told them I'll try a few more things) and I feel like that is a waste. I'm almost 100% positive that this is a software glitch, not hardware.
Thanks!

Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.

Jaxidian said:
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Click to expand...
Click to collapse
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.

Skillfulshoe said:
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Click to expand...
Click to collapse
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!

Jaxidian said:
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Click to expand...
Click to collapse
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
I'm not sure if this is caused by a bad touchscreen sensor because I've had the problem on two separate Pixel phones so far. Or maybe I just got super unlucky with two faulty phones.
I don't think my fingers are too dry. If all else fails, I'll try moisturizing them I guess. I've never had this problem on all my other phones though, but I guess you never know.
Thanks for the help.

Skillfulshoe said:
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
Click to expand...
Click to collapse
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.

I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.

Jaxidian said:
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
Click to expand...
Click to collapse
Yeah I totally understand what you're saying. I just have gotten frustrated with this. I know it isn't a big deal honestly.

gadgetgaz said:
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Click to expand...
Click to collapse
Yeah that could be what causes it. Maybe it is just the way we are scrolling and how Google has calibrated the screen touch sensors.

Possible Fix
So I went into accessibility settings and changed the duration you need to hold your finger down to do a long press to medium (from the default as short). It seems that may have fixed it. I haven't experienced the glitch since I've done that change.
Here's to hoping that did indeed fix the issue.
Thanks everyone.

Anyone else experiencing dropped tap inputs?

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.

A few observations on the google pixel 4a

I've had the Pixel 4a since tuesday and I like it. I've a few observations I thought I'd put here in case anyone else agrees; there's a fix/workaround etc:
1) The speaker isn't too loud and it's only in the last 20% or so of the volume bar that you can hear the difference. They should change the linearity such that there's more control over the sound difference of the last 20% of the range, if that makes sense. Not a big deal.
2) It's annoying that I can't swipe back (ie swipe left from the right edge of the screen) to get rid of the keyboard. Instead a large percentage (10?) of the bottom of the screen is black except for the arrow which closes the keyboard. Waste of space.
3) On a similar note, there's a white line near the bottom of the screen. I guess it's to show that you can swipe up, but I'm not sure. Why would anyone who wasn't sure if they could swipe up see a white line and go "ah - I bet I could swipe up here"? But that's my best guess. And this is on most screens. It's the worst, and the most noticeable, on chrome. You have a full screen site, curving nicely at the top of the screen, and at the bottom the screen starts to curve but then there's the black rectangle, which exists purely to highlight the mystery-white-line-which-might-mean-you-can-swipe-up-here, cuts in, ending the curve and wasting around 5% of the height of the screen. This line doesn't appear in 3 button mode. But isn't the point of gestures that you don't need to waste space on buttons. So...don't waste the space showing me you can swipe up then. There's no swipe down hint, or swiping left/right hint. I don't get it at all. It knows I know you can swipe up, because I've swiped up.
4) Nova launcher problem. It just doesn't stick. Every once in a while it stops being the default launcher and you have to run it again. This has happened on other phones and eventually they fix it. I guess I have to try nova launcher again every month or so. The stock launcher isn't too bad, but:
5) Stock launcher is quite unconfigurable. The 5 icons at the bottom of the screen are sort of like the nova launcher dock (which i always turn off) and are there on every screen.
6) There's a notification history, which is a great idea. If you swiped away a message but then forgot if it was an email, or which whatsapp contact it was, you can see quickly what the most recent message was. You access it via a button under the notification shade which you can press to get at it. But...get this: That button only exists if you currently have unread notifications. If you swiped the last one away, the history button vanishes. You now have to go into settings to read it (why settings? my photos aren't in settings). Why? Who thought that was a good idea? That's when you're most likely to want the history! Doh!
7) Aggressive app killer. This will never change - no matter what google says about ai and machine learning, there's something too complicated about "ok, there's a music player running, playing music, and there are headphones attached, and the headphones are playing music...but...oh, the screen is turned off, which apps can I kill to save battery...well, there's this music player nobody's looking at, that'll do" to ever fix. Really? You're not checking if an app gets reloaded immediately after it gets killed every time it's killed and learning "hmm... it's as if.....he was listening to music and didn't want the app killed?" I guess it's true what they say - most machine learning is just a regex, and this isn't something which can be solved with a regex, so... I've disabled the battery optimisation for this app; time will tell whether that does the trick.
8) Can't disable the sound it makes when taking a screenshot.
9) Google photos can't keep up with quickly deleting a number of photos. To be fair, this happens on the website too. It's odd - you'd think it would be easy. You're not actually doing anything other than marking the fact that a photo is deleted. You're just moving it to the bin; it still exists locally. It's an offline-operation. Why doesn't it just defer until later, or do asynchronously - whatever it's doing. On both web and phone it's so laggy and disorienting that it's easy to end up deleting the wrong photo, the only workaround being to delete literally one picture every 5 seconds. Annoying if you're been taking pics of kids and took a bunch so as to ensure you have at least one without a blur or closed eyes etc.
Well, sounds quite ranty I guess. It's a great phone though - highly recommended. I really bought it for the camera and the fact it's quite a small phone. I recommend the spigen tough armor (sic) case; nice and grippy and feels like it's going to keep it pretty safe.

Maybe these things will be fixed in future updates. I reverted back to 10 and flashed Dirty Unicorns, just a better overall user experience compared to stock at the moment.

I would like to add something: do you also the "bubbles" always appear on the left of the screen even if you have moved them to the right before closing them?

_a! said:
...Well, sounds quite ranty I guess. It's a great phone though - highly recommended. I really bought it for the camera and the fact it's quite a small phone. I recommend the spigen tough armor (sic) case; nice and grippy and feels like it's going to keep it pretty safe.
Click to expand...
Click to collapse
Most observations in original post pertain to Android 11 (AOSP) and have little to do with the device itself. My experience on a couple items:
- Nova has yet to crash since updating to Android 11 (stable on A10 too). That said, you likely interact with the launcher in different ways not to mention app portfolio interactions. Should submit a bug report to developer via contact link in Nova settings.
- Not experiencing the same nonlinearity in volume adjustment. Max volume is fine for my tastes but probably would work well as the sole audio source at an Italian wedding

DB126 said:
Most observations in original post pertain to Android 11 (AOSP) and have little to do with the device itself. My experience on a couple items:
- Nova has yet to crash since updating to Android 11 (stable on A10 too). That said, you likely interact with the launcher in different ways not to mention app portfolio interactions. Should submit a bug report to developer via contact link in Nova settings.
- Not experiencing the same nonlinearity in volume adjustment. Max volume is fine for my tastes but probably would work well as the sole audio source at an Italian wedding
Click to expand...
Click to collapse
The device runs Android 11, so that's all I can talk about, not what might happen if it ran a different operating system.
I never said nova launcher crashed; just that it stopped being a default launcher by itself a few times.

The white line at the bottom of the screen is annoying! I liked having the option in Oxygen OS to hide it, hopefully that becomes an option on future updates.
Overall I'm really enjoying the phone after coming from the Nord.

_a! said:
The device runs Android 11, so that's all I can talk about, not what might happen if it ran a different operating system.
Click to expand...
Click to collapse
Not what I said; no reference to an alternate OS
_a! said:
I never said nova launcher crashed; just that it stopped being a default launcher by itself a few times.
Click to expand...
Click to collapse
Almost always the result of excessive memory pressure (also has nothing to do with the device assuming memory is adequate...which it is on the 4a)

For your issue 4 I guess there's bug in Nova launcher. I had similar issue with Nova, but after switching to Lawnchair it sticks permanently.
Default gesture navigation is surely ****ty. I prefer using old 3-buttons navigation.