Android devices. Built in e-reader vs. e-reader app. Your preferences?

[Quoth]

Originally Posted by pazos

The java vm used in android has nothing to do with the standalone Oracle/Sun machine. It just happen that both are compatible with bytecode for java7. The old one was Dalvik and the new one is ART.

Because they COULDN'T put desktop JVM without getting sued. The entire point of it is instead of limited subset Java allowed by Sun on Mobile (symbian era) they cloned so as to have full fat Java on mobile. So of course it's compatible. There are emails querying if they'd get sued anyway. They did and it's still ongoing. So the Java vm used in android has EVERYTHING to do with the Oracle/Sun machine. Deliberately, so they can have a full Java implementation.

They also wanted to get the existing Symbian developers which is why they chose Java at all.

No ereader needs the Android VM for Java. They don't need to run Java.

[Pajamaman]

I use alreader, or the stock oreader that comes with onyx ereaders because its so good. So both. I use koreader on a kindle too, so I don't even use the standard reader on a non-Android reader.

[pazos]

Originally Posted by FrustratedReader

Because they COULDN'T put desktop JVM without getting sued. The entire point of it is instead of limited subset Java allowed by Sun on Mobile (symbian era) they cloned so as to have full fat Java on mobile. So of course it's compatible. There are emails querying if they'd get sued anyway. They did and it's still ongoing. So the Java vm used in android has EVERYTHING to do with the Oracle/Sun machine. Deliberately, so they can have a full Java implementation.

Incorrect. JVM is stack based because it is compatible with more architectures and fits the slogan: build once, run everywhere. Dalvik VM is register based because google don't need DVM everywhere and this allow them to run faster as they can skip certain cpu instructions used to manipulate the stack.

Implying that google implementation of the java vm is just a copy or a clone of the java one is wrong. They're both different implementations. The implentation that's part of android core relies on an underlying linux kernel and a bunch of c++ glue code while the oracle one can run on most hw arch without carying about the underlying OS.

BTW, I was wrong in my last comment. DVM don't run java bytecode. It is compatible at the source level but the java classes are not just compiled to java bytecode, but translated to dalvik opcodes too.

Originally Posted by FrustratedReader

No ereader needs the Android VM for Java. They don't need to run Java.

I agree with you. Sadly isn't a matter of what's needed but what is already available. The two options most manufacturers choose are based on AOSP + SDK framework and Linux + Qt framework. Releasing an application inside an embedded device is not an option if you use qt without a license for that specific device. (See https://www.qt.io/qt-for-device-creation/). So most vendors go with the android route since it provides more frameworks and permissive licenses too.

Some people still thinks that java, in the context of android, adds an overhead and is slower that native code. Unless you work with multimedia, AR or cpu intensive tasks (like compression/decompression) that's not true.

[pazos]

Originally Posted by FrustratedReader

No, it's pointless for eink and pointless for something you can't install apps on.

I had a PRS-T1 and it didn't do anything Androidy. I think the T2 is basically a T1 that works better. Considering that Sony had FOUR years of experience doing ereaders without Android rather than being new in 2008 it made no sense. Also they had there own decent TV GUI before the Ghastly Android TV.
They produced PS1, PS2, PS3, PS4. The PS2 even had a Sony Linux Distro.
Minidisk
PSP (various models)
PCs & laptops

The only way it would have been slightly logical was if the Phone Division was taking over the ereaders.

I've written a program for Android and one in Java to run on Linux or Windows desktop identically.
I've written C programs for Linux (Debian) and also for OpenWRT with no GUI. I helped port Debian on to a 320 x 240 LCD panel portable gadget with touch screen, email, MP3, player, Firefox etc and Trolltech QT based GUI in late 2006 early 2007.
So from my own experience I can see no point to Android for an ereader of any screen type and less for eink. Especially when you've already been doing better ereaders than the first Kindle. No point to Android unless you are including the Android home screen and stock apps and no point if you can't install apps. You don't absolutely need the Playstore to install apps on Android, but unless you are Samsung, Huawei or Microsoft it's a bit mad.

Sorry I missed that comment.

You could argue that Nook, Tolino or Sony have a worse software stack that Kobos or Kindles, but you cannot say that the only reason for that is they're based on AOSP.

The fact that you did sw development outside the Android world just shows that is possible to avoid android completely. In the same vein it is possible to avoid Qt on desktop and use other frameworks like wxwidgets or gtk.

[Tortuosit]

Moon+. I carry it from device to device (Settings,covers). No alternative to it in book management and flexibility.
I read on standard android smartphones only, OLED preferably. Currently a Mate 20 X.