TCL Nxtpaper 11 Plus

[Quoth]

Originally Posted by Quoth

I use Gboard handwriting or a BT keyboard. On older Android a USB keyboard. Also External Keyboard Helper Pro for BT & USB , since Android 4.x, because Android used to only do USA external keyboards and was abysmal for áéíóú àèìòù äüö ç ẞ ł Ł þ etc. On Linux ` is dead and ü, å ā etc is using compose.
ChromeOS is terrible too.

Considering that Linux is so good and has the Compose key and a full compliment of AltGr, Android and ChromeOS have no excuse compared to Windows.

It's probably what ever variant of Android, or Google Security rather than a real TCL issue.

For years the External Keyboard Helper Pro was the only app I'd bought on the Playstore. Still available and still works. Works on my 4x TCL devices and Alcatel phone (also TCL).

[Quoth]

Originally Posted by 8833

I don't get what you were trying to say. Android doesn't have such issue, older and newer versions, so either TCL replaced something or misconfigured something, either way it doesn't work due to TCL firmware bug.

It can be weird. My Android eink Mars originally ran BorrowBox library app. Then it didn't. No updates except BorrowBox and ChromeBrowser.

It still worked on an Alcatel phone (made by TCL) running same version of Android. The Bolinda tech people eventually decided that a component of the Chrome Browser (which they used to render) was the "wrong" version, even though the Chrome Browser was updated and the same version as the phone. The App worked except the actual ebook pages were blank. There was no possibility of the older version that had worked for over a year as it was no longer compatible with the local library.

So the Android eink gathers dust as it was bought during Covid to access the local library. It does epubs less well than Kobo Libra2 or Sage. It does Kindle and PlayBooks aps, but I have a PW3. The PlayBooks works far better on the 4x NxtPaper devices, which support Pocketbook. The Pocketbook App doesn't work.

[8833]

Originally Posted by Quoth

It can be weird. My Android eink Mars originally ran BorrowBox library app. Then it didn't. No updates except BorrowBox and ChromeBrowser.

The annoying web pages wrapped in an apk... Javascript engine changes and boom, it's broken. You're right about this one as the web rendering engine can be changed, supplied by an app. You may be lucky to rescue the device then by enabling developer options in the Android setting, then selecting Android Web View instead of Chrome Web View under Web View Implementation. The access to Android settings might not be available in the default e-ink GUI, but a custom launcher can provide it.

[Quoth]

Originally Posted by 8833

You may be lucky to rescue the device then by enabling developer options in the Android setting, then selecting Android Web View instead of Chrome Web View under Web View Implementation.

Sadly that didn't work. Google or Bolinda broke something in compatibility with Chrome and that eink, even though it was exactly same Android OS as the still working phone. It would be understandable if it had never worked, but it worked for over a year. The "native" ereader app still works, which is similar to KoReader. KOReader (installed direct as APK download) works, but not as well as the supplied app.

I will certainly buy dedicated eink gadgets or ereaders as needed in the future, but not an eink Android one ever again. Well, maybe an Onyx Boox if it's less than €50 from local CEX and a still supported version of Android.

It has ability to turn off the Google Framework, which kills some but not all apps from the Playstore. All of the pre-installed apps unaffected.