Screen overscan in Poke3 (& others?)
My reader app uses a thin reading progress stripe on the bottom.
On my other devices it treads the fine balance between low-key and visible.
On the Poke3 that stripe is mostly eaten by the bezel.
Yes, if you hold the device at a 45° angle you can see under the bezel and see that the pixels are there.
I haven't measured exactly but it's somewhere in the realm of 20-30 "lost" pixels.
For my own use, I just modified the code to look at Build.MODEL to see if it's in the list of overscanned models.
That list is currently just {"Poke3"}
Instead of having the stripe 4dp, I use 8dp.
You could also use the shell command "wm overscan" (WindowManager) to reduce the screen size, but I don't like that idea.
Has anybody noticed this with other Onyx models?
|