3.24.11 not fitting on display

[Backporch]

Wondering if I'm special of something? No one else has reported that the most recent push is too wide for the display. 3.24.11 v2 adapter (not plus) on Lenovo P11 Plus tablet running Android 11.

Other than TouchDRO I am not of the Droid world and have stopped allowing OS updates unless demonstrably necessary. A while back I allowed an OS update and a "new feature" in that Samsung OS rendered both of my TouchDRO systems unusable with no near term fix. I ended up shelving the two new Samsung A7 tabs and purchasing a couple Lenovos. ( https://www.hobby-machinist.com/threads/help-bitten-by-samsung-bug.103959/ ) Yuriy has since implemented a work around and Samsung tabs are back on the OK list. (FYI: there are two very briefly used Samsung A7 tabs in tough shells sitting on a shelf should anyone be interested).

Maybe this is an OS setting I should know about - but I don't.

Cheers, Louis

 

[Schtimpy]

I had a similar issue with the edge finder dialogue cut off. This appeared after I had to do a factory reset on my tablet and start again from scratch. The cut off was caused by the "Display Zoom" setting (in display settings) to be set too high. I dropped it back at Yuriy's suggestion and everything was back to normal. Might be worth a try.

 

[Backporch]

The only seemingly relevant setting I could find was "display size" under display settings which didn't change anything in TouchDRO even after tablet restart.

The issue appeared on both my systems coincident with the push of this update which seems somewhat suspect.

 

[ycroosh]

The only seemingly relevant setting I could find was "display size" under display settings which didn't change anything in TouchDRO even after tablet restart.

The issue appeared on both my systems coincident with the push of this update which seems somewhat suspect.

Display size changes the resolution, so TouchDRO can't get accurate DPI for the screen. It's better to use font size and leave display size unchanged.
I will try to tweak this, but don't know yet how to detect the setting.

 

[Backporch]

Hi Yuriy, Glad you're on the case.

Nothing in any tablet settings had changed in months (years?). Things have looked normal over many, many beta pushes - until this one. Does this make sense to you?

Is there anything you'd like me to do/try? I don't know how many beta folks are still on 'droid v11? Maybe i should (with some trepidation - see above) update at least one of them to v12 if that would be informative.

Thanks, Louis

 

[PNW_Guy]

Other than TouchDRO I am not of the Droid world and have stopped allowing OS updates unless demonstrably necessary. A while back I allowed an OS update and a "new feature" in that Samsung OS rendered both of my TouchDRO systems unusable with no near term fix. I ended up shelving the two new Samsung A7 tabs and purchasing a couple Lenovos. ( https://www.hobby-machinist.com/threads/help-bitten-by-samsung-bug.103959/ ) Yuriy has since implemented a work around and Samsung tabs are back on the OK list. (FYI: there are two very briefly used Samsung A7 tabs in tough shells sitting on a shelf should anyone be interested).

Be aware that most companies that use Android will put of a layer of their own software on top of Android. And if there's a cellular carrier involved, they'll add to the party as well.
When Google pushes an update, Samsung and other will sit on it for 6 months and may (or may not) push it to your device.

I use Android for my phone, but buy the a Pixel phone from Google so it doesn't have any extras on it. This is why Verizon refused to carry the first iPhone; they couldn't touch it. AT&T got it first, IIRC.

I find my Android experience to be significantly better if there's only one company involved.

This is also why I use a Amazon Fire tablet for Touch DRO.

 

[ycroosh]

Be aware that most companies that use Android will put of a layer of their own software on top of Android. And if there's a cellular carrier involved, they'll add to the party as well.
When Google pushes an update, Samsung and other will sit on it for 6 months and may (or may not) push it to your device.

I use Android for my phone, but buy the a Pixel phone from Google so it doesn't have any extras on it. This is why Verizon refused to carry the first iPhone; they couldn't touch it. AT&T got it first, IIRC.

I find my Android experience to be significantly better if there's only one company involved.

This is also why I use a Amazon Fire tablet for Touch DRO.

I would say that Google Pixel and Amazon Fire tablet are about as far apart on the clean Android spectrum as you can get. One has the reference base OS, and the other has the mother of all OEM overlays smothered over every aspect of Android.

Hi Yuriy, Glad you're on the case.

Nothing in any tablet settings had changed in months (years?). Things have looked normal over many, many beta pushes - until this one. Does this make sense to you?

Is there anything you'd like me to do/try? I don't know how many beta folks are still on 'droid v11? Maybe i should (with some trepidation - see above) update at least one of them to v12 if that would be informative.

Thanks, Louis

Yes. I ripped out most of the old-school UI code that lingered from Android 4.x days and switched to the "modern" theming. Many of the old APIs are now deprecated, and things started coming unglued on the latest OS releases.
Google forces all apps to target OS version no older than 1 year.

For what it's worth, I treat any OS updates as necessary unless proven otherwise. I work with info security a lot in my day job, and at this point the moment a device stops getting updates I stop using it (my old test tablets are connected to a separate firewalled WiFi network with a separate internet connection). Updates can be a PITA, but compared to a data breach (even in a home network), it's a small minor inconvenience.

 

[PNW_Guy]

I would say that Google Pixel and Amazon Fire tablet are about as far apart on the clean Android spectrum as you can get. One has the reference base OS, and the other has the mother of all OEM overlays smothered over every aspect of Android.

Looks like I didn't finish my thoughts...

I use a Pixel because it's clean, and I use a Kindle Fire because Touch DRO is released for it as a "native" app. Since I know you thoroughly test before releasing updates, I trust that it'll run correctly on a Fire. But all I use a my Fire for is Touch DRO.

 

[ycroosh]

Looks like I didn't finish my thoughts...

I use a Pixel because it's clean, and I use a Kindle Fire because Touch DRO is released for it as a "native" app. Since I know you thoroughly test before releasing updates, I trust that it'll run correctly on a Fire. But all I use a my Fire for is Touch DRO.

Ah, I see.
So, one important nuance: I treat Fire as a "LTS platform" (long time support) - it gets updates once or twice per year, and usually a bit later. This way there is Beta for "bleeding edge" releases, Android prod for normal cycle, and Fire for more conservative releases.

Regards
Yuriy