MobileRead Forums - View Single Post

kacir · 10-04-2017, 02:54 PM

I have used Kindle Paperwhite - the very first model as a Linux computer briefly.
When I got it, I was deeply dissatisfied with just about every aspect of the user interface, so I have installed every possible hack or tool to the device. One of those was Terminal. So I was able to use a text terminal and access the Linux the Kindle runs on.
Kindles run on Linux, not Android.
I was able to use many userland programs from Busybox that is installed by default in Kindle. It was a Dancing Bear (TM).
After my initial enthusiasm cooled down after a few days I only opened it when I wanted to brag that I have a genuine, working terminal on my e-ink reader. The only occasion when I used the feature was when I used the date command to set the date and time - I refused to let the device to connect to the Internet, so it couldn't use the Amazon server to synchronize the time, (and update to a newer version of firmware behind my back).

Besides Paperwhite I was a proud owner of several generations of PocketBook readers. PocketBooks run on Linux as well. At one moment in time, in a distant past, the PocketBook company released an SDK and even sponsored a competition for programmers in Russia. The results were spectacular. Several notable user interface enhancements, an FTP server (important if you want to tinker with the system files that are inaccessible when you connect the reader to PC over USB), a terminal program, an improved version of the flagship reading app FBReader and even linux terminal. Again, you could use the built-in Linux userland programs, mostly provided through Busybox. I even managed to install my beloved VIM text editor. Just like a Kindle PaperWhite, it was a Dancing Bear (TM). I have never used the terminal, ftp server or VIM text editor for anything work related. The only reasonable use was copying of some config files, so we could place a modified version to an user accessible place. PocketBook had a number of notable features. You could place your version of system config files and even ELF binaries to an user accessible partition and those files took precedence when you started the reader.

I also had rooted Nook Simple Touch. The only advantage was that I could use a better version of CoolReader or FBReader for reading. Unusable for any work. And, believe me, I have tried hard to find an use-case for my new toy. I already had a reader that had better parameters, so NST was only for playing and non-reading use. I sold it after several months.

Nowadays I have an Android powered front-lit e-ink reader. The only thing I *ever* use it for is reading. Again, I have tried hard to find some reasonable use for this "e-ink Android Tablet", but even for simple browsing it is simply too frustrating.

I ALSO have Yotaphone. With AMOLED screen on one side and an e-ink on the other. I have never used e-ink screen for anything but reading books and demonstration for my [envious] nerdy friends. Again, I have tried. Yet, when I want to do anything besides reading I find myself flipping the device to the AMOLED screen. And Yotaphone is not a clunky, under-powered device with limited memory and space for apps, like most e-ink readers, but a fast, modern, Android 5.0, smooth-as-butter high-end phone.

10-04-2017, 02:54 PM	#17
kacir Wizard Posts: 3,463 Karma: 10684861 Join Date: May 2006 Device: PocketBook 360, before it was Sony Reader, cassiopeia A-20	I have used Kindle Paperwhite - the very first model as a Linux computer briefly. When I got it, I was deeply dissatisfied with just about every aspect of the user interface, so I have installed every possible hack or tool to the device. One of those was Terminal. So I was able to use a text terminal and access the Linux the Kindle runs on. Kindles run on Linux, not Android. I was able to use many userland programs from Busybox that is installed by default in Kindle. It was a Dancing Bear (TM). After my initial enthusiasm cooled down after a few days I only opened it when I wanted to brag that I have a genuine, working terminal on my e-ink reader. The only occasion when I used the feature was when I used the date command to set the date and time - I refused to let the device to connect to the Internet, so it couldn't use the Amazon server to synchronize the time, (and update to a newer version of firmware behind my back). Besides Paperwhite I was a proud owner of several generations of PocketBook readers. PocketBooks run on Linux as well. At one moment in time, in a distant past, the PocketBook company released an SDK and even sponsored a competition for programmers in Russia. The results were spectacular. Several notable user interface enhancements, an FTP server (important if you want to tinker with the system files that are inaccessible when you connect the reader to PC over USB), a terminal program, an improved version of the flagship reading app FBReader and even linux terminal. Again, you could use the built-in Linux userland programs, mostly provided through Busybox. I even managed to install my beloved VIM text editor. Just like a Kindle PaperWhite, it was a Dancing Bear (TM). I have never used the terminal, ftp server or VIM text editor for anything work related. The only reasonable use was copying of some config files, so we could place a modified version to an user accessible place. PocketBook had a number of notable features. You could place your version of system config files and even ELF binaries to an user accessible partition and those files took precedence when you started the reader. I also had rooted Nook Simple Touch. The only advantage was that I could use a better version of CoolReader or FBReader for reading. Unusable for any work. And, believe me, I have tried hard to find an use-case for my new toy. I already had a reader that had better parameters, so NST was only for playing and non-reading use. I sold it after several months. Nowadays I have an Android powered front-lit e-ink reader. The only thing I ever use it for is reading. Again, I have tried hard to find some reasonable use for this "e-ink Android Tablet", but even for simple browsing it is simply too frustrating. I ALSO have Yotaphone. With AMOLED screen on one side and an e-ink on the other. I have never used e-ink screen for anything but reading books and demonstration for my [envious] nerdy friends. Again, I have tried. Yet, when I want to do anything besides reading I find myself flipping the device to the AMOLED screen. And Yotaphone is not a clunky, under-powered device with limited memory and space for apps, like most e-ink readers, but a fast, modern, Android 5.0, smooth-as-butter high-end phone.