B&N just announced a new eInk device called the Glowlight 3. You can see it on the B&N website. It's a 6 in. reader with what look like wide bezels. No waterproofing, but the display has a "Night Mode". I can't find out if the 3 runs Android or something else.
Does anyone else have any info on this? It's due to ship on November 8.
Follow-Up
Windsor1959 said:
B&N just announced a new eInk device called the Glowlight 3. You can see it on the B&N website. It's a 6 in. reader with what look like wide bezels. No waterproofing, but the display has a "Night Mode". I can't find out if the 3 runs Android or something else.
Does anyone else have any info on this? It's due to ship on November 8.
Click to expand...
Click to collapse
I emailed B&N, asking them about this device's OS. Here is their reply, for those who are interested:
Please be advised that the new NOOK Glowlight 3 has an operating system of Android 4.4.2 (KitKat). Also, please be informed that it does NOT run other Android applications or work with Google Play Store.
Edit: Those of you who have the Glowlight Plus know that apps can be installed on it. So I'm guessing that a way can be found to install apps on the Glowlight 3.
I asked the folks at the nearest B&N store to reserve one for me when it arrives. Once I get it, I'll see if I can install a launcher and some apps by adb. I'll let you know if it works.
I now have a Glowlight 3. It looks very much like an upgraded NST, maybe slightly larger due to the size of the bezels. However, it feels very light, and it's a pleasure to hold. The folks at the B&N store tell me that covers will be available in two weeks or so.
The 3 has a total of 8 gb of internal storage. However, after my 3 updated, I saw, in Storage, two partitions listed: one for Nook store content ( about 4.5 gb) and one for sideloaded books (about 0.95 gb). When I plugged the 3 into my Mac, I saw a Nook drive of about 1 gb. That was it. So, sideloading is limited.
By tapping on the Nook icon in Settings-About a number of times, a menu comes up that includes developer options. One can enable USB debugging there. However, when I started Terminal, connected my 3 to my laptop, and typed "adb devices", Terminal saw the device, but also came up with "unauthorized". After some attempts at turning usb debugging off and on again, and trying to deauthorize my computer and reauthorize it, I finally got authorization. Then, one can simply type "adb install .." followed by an apk, from Terminal, and install apps. Install a launcher first, so you can find app icons. I did not try rooting the 3. I just wanted to see if apps can be installed. The 3 is not designed to run apps, so if you go this route, stick with apps that focus on reading and do not make many demands on the hardware.
As a reader, the 3 does a good job. There are two buttons on either side of the display, so you can turn a page back or forward from either side. Text is clear, as you'd expect. There are several font options, and all the common customization choices. There is a slight hesitation from a button click to a page turn. Clicking the buttons makes a sound - for those who care. The display is recessed from the bezel, rather than flush. You can't put a microSD card into the 3.
Feel free to ask questions, if you wish. I'll post more as I learn more about the device.
Just got mine as well - SO love the fact that it's so easy to turn on developer mode and install apps - thanks for the confirmation. My needs are few: Calibre Companion, dropsync, web browser. I don't really need root either - I've been down the road of trying to push an ereader to its limits - I end up screwing around with the tech more than just reading. I'll also report back if I have any problems with any particular apps or if anyone wants me to try something out.
As far as reading, I can tell already that this is going to be a superior device than the Nook Glowlight Plus - that thing was slippery, weighted funny, the single non-physical button was frustrating as all get out. This really is the classic form factor of my all-time favorite Nook. I love the fact that I can turn the light on and off by long-pressing the N button again! And while I had long-since gotten used to not having physical page turn buttons, it is nice to have that option again - it might help with being able to navigate around other apps (rather Button Savior). The only small downside that I can see to there is no water-resistance - but that's not really important to me, esp. compared to the other upsides gained with this model.
I went down the root road with the Glowlight Plus, trying to get Play Store to work - and losing root at every system update. It wasn't worth the bother. A few apps, like you say, and I'm good to go.
It used to be that Calibre Companion didn't work for long if Play Store was not installed on a device, as CC would "phone home" to make sure we were legit owners. Has that changed? I didn't install CC on the Glowlight 3 for that reason.
Windsor1959 said:
It used to be that Calibre Companion didn't work for long if Play Store was not installed on a device, as CC would "phone home" to make sure we were legit owners. Has that changed? I didn't install CC on the Glowlight 3 for that reason.
Click to expand...
Click to collapse
I can't remember how I installed it (or what version) - I'm pretty sure it was a side-loaded APK, though, and it worked for me through the life of the Glowlight Plus without any problems. I do know that I purchased it, but I can't remember how the copy-protection worked.
I would be very grateful if anyone could post hw info. I'm mostly interested in cpu and screen, and RAM.
RyogoNA said:
I would be very grateful if anyone could post hw info. I'm mostly interested in cpu and screen, and RAM.
Click to expand...
Click to collapse
Wiki page: https://wiki.mobileread.com/wiki/Nook_GlowLight_3
Ram: 512? When I go to ReLaunch it shows Total: 460M / Free: 147M which I assume would be half a gig... (?)
Screen info (is this pretty much the same as the Glowlight Plus?):
Screen: 6" 300-dpi screen with built-in glare- scratch- and fingerprint-resistant lens provides a paper-like reading experience.
Resolution: 1072 x 1448 pixelsIs this helpful at all? cat /proc/cpuinfo:
Processor : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 1988.29
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10
Hardware : Freescale i.MX 6SoloLite NTX Board
Revision : 60200
spedinfargo said:
Ram: 512? When I go to ReLaunch it shows Total: 460M / Free: 147M which I assume would be half a gig... (?)
Click to expand...
Click to collapse
too bad, I was hoping they upgraded it to 1gb.
spedinfargo said:
Wiki page: https://wiki.mobileread.com/wiki/Nook_GlowLight_3
Screen: 6" 300-dpi screen with built-in glare- scratch- and fingerprint-resistant lens provides a paper-like reading experience.
Resolution: 1072 x 1448 pixels
Click to expand...
Click to collapse
cat /sys/class/graphics/fb0/xwi please, if possible.
spedinfargo said:
Hardware : Freescale i.MX 6SoloLite NTX Board
Click to expand...
Click to collapse
oh... I was hoping for i.MX7. Well, not too bad still.
RyogoNA said:
cat /sys/class/graphics/fb0/xwi please, if possible.
Click to expand...
Click to collapse
Here ya go:
320_R187_AF0C21_ED060KG2C2_TC
spedinfargo said:
Here ya go:
320_R187_AF0C21_ED060KG2C2_TC
Click to expand...
Click to collapse
Thank you. So, they've actually using new waveform oposed to Nook Glowlight Plus. I'm curious if they've implemented e-ink regal support.
anyone brave enough to pop theirs open and see if there is a UART possibility or not?
yegoshin said:
anyone brave enough to pop theirs open and see if there is a UART possibility or not?
Click to expand...
Click to collapse
Do you have any plan?)
yegoshin said:
anyone brave enough to pop theirs open and see if there is a UART possibility or not?
Click to expand...
Click to collapse
Of course!
It pops easily. Use a thin knifeblade to get it started then work a guitar pick around.
The TTY is easy and obvious, 3.3V, 115200 8N1.
Code:
[email protected]_6sl:/ #
Windsor1959 said:
It used to be that Calibre Companion didn't work for long if Play Store was not installed on a device, as CC would "phone home" to make sure we were legit owners. Has that changed? I didn't install CC on the Glowlight 3 for that reason.
Click to expand...
Click to collapse
The APK that I had for CC didn't work with the newer version of Calibre content server so I did a little digging. Turns out that they fully support sideloading of Calibre Companion now!
https://www.mobileread.com/forums/showthread.php?t=273880&highlight=nook
The requirement for Google Play (GP) was removed in February of this year, in CC version 4.3.4.4. If a device has GP then GP must work. If a device doesn't have GP then CC deals with it.
spedinfargo said:
The APK that I had for CC didn't work with the newer version of Calibre content server so I did a little digging. Turns out that they fully support sideloading of Calibre Companion now!
https://www.mobileread.com/forums/showthread.php?t=273880&highlight=nook
The requirement for Google Play (GP) was removed in February of this year, in CC version 4.3.4.4. If a device has GP then GP must work. If a device doesn't have GP then CC deals with it.
Click to expand...
Click to collapse
Thanks! I installed CC on my G-3 and it works fine. I appreciate the update.
Also, nice to see some more activity in the thread! Its starting to look like the old Glowlight Plus thread!
The six hard buttons are mapped in /system/usr/keylayout/imx-keypad.kl
LowerLeft 191 F9
UpperLeft 192 F10
UpperRight 193 F11
LowerRight 194 F12
Power 116 Power
Home 102 Home
You probably want to steal one for back.
Well, I'm setting my old Glow Plus alongside the Glow 3.
The displays seem about identical.
The thicker bezel on the G3 is a bit annoying the same way it was on the NST.
Oh! No! They are using the same IR sensor as in the NST, not the capacitive from the G+!
Get your Q Tips ready to clean cruft out of the corners of the bezel.
Under some conditions it also throws a distracting shadow.
The bezel on the G3 is also bigger, especially on the top and bottom.
Having physical buttons is somewhat handy.
They are still using about the same hardware in the G3 as in the G+.
MCIMX6L8DVN10AB (i.MX 6 series 32-bit MPU, ARM Cortex-A9 core, 1GHz)
KLM8G1GEME-B0141 (8 GB eMMC)
Nanya NT6TL128M32AQ-G1 (512 MB DRAM)
Realtek RTL8189FTV (2.4GHz WiFi)
TI TPS65185 (eInk power controller)
Ricoh RC51619 (eInk controller)
zForce NN1001 (IR touch sensor)
zForce NN2003 (IR touch sensor)
In a lot of ways it's not a lot of progress.
FYI, I've posted in Glowlight Plus topic links to TWRP recovery (and device tree), since HW in Glowlight 3 is mostly identical someone could try to build a recovery for Glowlight 3.
Does anyone know whether the Glowlight 3 runs Android 4.4 or a newer version?
Related
hi folks.
gonna be getting me one of these when they go on sale in a week or so here in the uk.
i want one to root because it looks like the perfect ereader to use with pdfs.
my question is once rooted and touchnooter is installed multi touch and no refresh are enabled and the very few apps i want installed are on the deivce can i then somehow remove the market app?
the plan is to simply install a few other ebook apps some pdf apps gmail skydrive and then never install another app ever. i want it as minimal as possible to help with the battery and the less that is on there the better
if anyone knows please let me know.
cheers
You could remove Market after using TN, or simply root without it. I've spent a lot of time looking at battery consumption on my NSTs, and have never noticed Market causing any drain worth worrying about.
With the recent release of Amazon's Kindle Paperwhite, you might want to wait to see how B&N responds. The NST is nice enough, but a capacitive screen would be nice.
bobstro said:
You could remove Market after using TN, or simply root without it. I've spent a lot of time looking at battery consumption on my NSTs, and have never noticed Market causing any drain worth worrying about.
With the recent release of Amazon's Kindle Paperwhite, you might want to wait to see how B&N responds. The NST is nice enough, but a capacitive screen would be nice.
Click to expand...
Click to collapse
thanks for the reply. yes i did see the tinynoot root solution after i originally posted this thread.
my question about that is if i used that method can i still install the multi touch and no refresh hack (i am guessing i can but confirmation would be nice). if i can then i will most likely go down that route. it isnt all about battery life but i know the market does check very often when wifi is enabled for updates and what not and i would rather not have to worry about that at all. bottom line i want to keep the reader as close to a reader as possible. pdf email web browser ebook reader and file manager is all that is needed. nothing more is required or wanted and therefore i want it is minimal as possible with no bells or whistles.
not really too fussed about any new future nook and will take the plunge as soon as i can here in the uk. if they bring out something extra special later then i will simply sell the old and buy the new but i will do that as and when i want/ have to. the reason the nook gets my vote over my kindle is the page turn buttons. i have a keyboard 3g at the moment and it is great but it doesnt handle pdfs very well. i bought the new kindle touch but i missed the physical buttons and so bought another keyboard but amazon have crippled the pdf functionality and although i could jailbreak it and install one of the pdf viewer hacks that improve the situation i cant be bothered with all the faffing around. however i was willing to do this but then i saw the multi touch no refresh hack on the nook and watched how it handled pdfs when the hacks were installed and that was me sold. i have a lot of pdfs that i would to view on an e ink screen and the nook is by far and away the best solution for the job.
"can i still install the multi touch and no refresh hack" (after rooting with tinynoot)
Not clear that you can, but if you look at the thread on the overclock kernel that's just been posted, the dev who posted that
also posted an APK that gives you much/most of hte benefit of the no refresh hack, in terms of screen speed.
I am not sure if that work also gives multitouch.
I have been looking around for an eink android tablet.
Is the NST the only option?
I understand that the screen refresh rate severely limits what you can do, but i was wondering if it is otherwise possible to run all apps?
As far as I could find, none of the other eink ereaders (Amazon Kindle, Kobo) can be rooted / made to run regular android apps.
andTab said:
I have been looking around for an eink android tablet.
Is the NST the only option?
I understand that the screen refresh rate severely limits what you can do, but i was wondering if it is otherwise possible to run all apps?
As far as I could find, none of the other eink ereaders (Amazon Kindle, Kobo) can be rooted / made to run regular android apps.
Click to expand...
Click to collapse
You can also choose a 13.3" epaper tablet from sony:
http://goodereader.com/blog/electronic-readers/sony-announces-13-3-inch-e-reader-to-launch-in-the-usa-this-may
I just can't precise if it even runs android.
I believe that neither Kindle or Kobo run android. They use a proprietary OS so, no rooting on them.
andTab said:
As far as I could find, none of the other eink ereaders (Amazon Kindle, Kobo) can be rooted / made to run regular android apps.
Click to expand...
Click to collapse
Check the Android on Kobo thread.
They can run Android 2.3.4
embryo10 said:
Check the Android on Kobo thread.
They can run Android 2.3.4
Click to expand...
Click to collapse
Though none of these eink readers runs a modern (4.x) version of android?
andTab said:
Though none of these eink readers runs a modern (4.x) version of android?
Click to expand...
Click to collapse
there is the boyue t62 and the boyue t61 the Icarus illumina is a rebrand of the boyue t61. they run android 4.2 I think I am considering getting one myself but android L coming out in a month and that's supposed to be for low power and android one is for low costs devices so I am starting to like the idea of an android one device with eink so I kind of want to wait.
There have been several readers released recently that run "open" andriod. There is the Onyx Boox T68 and the Icarus Illumina HD. You can find a comparision review of both readers here
@andTab, you are right about the refresh rate problem, but there is a way around it: NoRefresh enabler. It's a great alternative and it works nicely, too.
The only eink tablet?
Not at all. For example the Onyx Boox T68 comes with Android 4.0, a higher resolution display, more RAM, a faster processor
and is already open (no root required).
But the NST is by far one of the cheapest EINK devices running Android
smeezekitty said:
The only eink tablet?
Not at all. For example the Onyx Boox T68 comes with Android 4.0, a higher resolution display, more RAM, a faster processor
and is already open (no root required).
But the NST is by far one of the cheapest EINK devices running Android
Click to expand...
Click to collapse
Right. It's not even that bad for being the cheapest.
And cheap is always good.
otg support
do we know if any of the above android eink ereaders like onyx boox or boyuee T61 , T62 support usb host function - otg?? Nowhere is mentioned exactly and is very critical for my application to add a usb smartcard reader..
Take a look at Meet Earl project, it's not out jet, but looks very promising. I can't post links, look for youtube video - it will explain everything. Nook is the best tech thing I've bought. After Earl it will be second...
Boyue T62
I just rooted and set up a Boyue T62 for an avid reader. I used an exposed module to have the page up and page down buttons trigger Tasker tasks that input screen taps, making the buttons work in pretty much every reader app. It misfires on occasion, but the user says it happens so rare that it's not even an inconvenience.
The experience of reader apps as reported by her:
Built in "Books" app for non DRM books - Works flawlessly, but finding books stored in the card isn't as user friendly as it should be.
Cool Reader - works great after you tweak the options
Nook - Nearly flawless, but there is bug with the front light. If stuck on, use light icon in the tray to turn it off. Very minor inconvenience. Page turns are slower than an actual nook, but still well within reason.
Kindle - Sluggish, but once a book is loaded, works great.
Kobo - Unusably slow, but who uses Kobo anyway?
Various "Free ebooks" apps - most work great!
PDF - not tested yet.
Other apps useful on eInk
Flipboard - Usable
"Internet" - Great for pages that have a lot of text.
Built in Email - Flawless
IHeartRadio - Flawless, excellent for music to read to
Keyring - Set up and Tutorial look like crap, but it works flawlessly after that. She had this app on a hacked Nook before, and she has yet to find a barcode scanner that can't read an e-ink screen!
Google+ - Fails to install
Google Plus mobile site - works well
Dictionary.com app - Fails to install
Play Music - Fails to launch
Facebook Lite - works well
Facebook regular app - not tested
Google Keep - Works well, but color options, obviously, are quite limited. She just uses what we assume is the default yellow, which displays clearly.
Rounder - Looked AWESOME with the victorian corners she likes, but it interfered with the tasker set up I used for the page buttons.
If you're interested, e-mail me [email protected], and I'll give you the code and screen coordinates to use in tasker for the buttons, and the name of the exposed module I used to connect tasker to the buttons. I don't have the reader in front of me, I'll ask her for it for a second to get that for you. It's configed so the page turns are screen taps on click, volume on long press. The refresh button is standard refresh on press, standard back light toggle on long press, and brightness options on double press. Power key is standard power on press, power menu on long press, and screenshot on double press. Interestingly enough, screen shots are color when sent to a color device. I wasn't expecting that. The double press for the backlight options is a fantastic work around for the backlight bug in the Nook app.
When I see her, I'll see if her boyue supports USB host.
With my AFTV2 currently broken down about one day after I set it up - I mentally went through some of the steps I'm likely to repeat very soon and - also seeing that some people in here still are struggling with some aspects of it, that I already learned long ago how to cope with - I thought I share some of my reflections.
This is by the way not meant to be a usability review - or tips guide of Amazons own interface - which I find abysmal for the most part. Let them struggle on their own - and also, for some reason there already are in depth "reviews" of it on aftvnews (which I came to slowly accept and even somewhat like.. ) - which mostly highlight aspects of it deemed positive. Bravo and lull Amazon into false confidence I say...
So here we go.
1. Best launcher (rooted or not) still is Firestarter. Basically because of its deep integration to app settings - which allows you to stop apps, delete their data or uninstall them in the fastest way possible. You'll need it more often than you think and its great that its there.
Change icon PPI to 144 and for your own sake - change the background to something more uplifting and also enable the text background bubbles so you get a higher text contrast, regardless of the BG image you chose.
2. Fire OS v5 and its limitation to one adb connection only isnt the enormous setback I thought it would be. Firestarter literally changes its default automatically within the first 3 seconds of it not being able to access adb - and the one click>double click combo to launch it from anywhere is good enough. Also in OS 5 there are no screen transitions, so switching to Firestarter feels more "instant".
Not having Firestarter use adb frees up you using adb from different devices. Once you are connected via adb from a PC f.e. you can also open different shells, or transfer a file and simultaneously perform another action in the shell - so thats a non issue. Also I rewrote all the scripts I use to cleanly exit adb with adb disconnect - and ultimately that works fine.
Through the two days of setting the Fire TV up and testing use cases I got a "cant connect via adb" error (because there already was another process using it) only twice - which in return can be promptly fixed by toggling adb on and off - and again - Firestarter provides a shortcut to that menu as well - so its fast, and if you use adb disconnect as intended, you dont need it very often.
3. Drop adbFire or equivalent "Helper Tools" as fast as possible - because they prevent you from learning even the simplest command line instruction, that will speed up your life in the long term. Seriously - just do it.
Also, explore the file structure of Kodi and the Fire TV (as in "look at it", try to make sense of it - not as in "I wander what happens if I delete this..."), so you can actually learn how they work. This again brings me back to the do not use adbFire or other "prepackaged" (and poorly laid out and documented) tools.
4. If you transfer single files - and most of them you usually want to drop to /sdcard/ first, you use the adb push command, because it simply turns out to be the fastest way to move stuff - at least if your OS allows you to drop a file onto the command line window to autopopulate the filepath.
If you want to transfer files and folders not directly located in /sdcard/ - either use something more GUI orientated - like AAFM ( https://github.com/sole/aafm ) (Windows cant use it to its fullest extent in its current state (on Windows you can use Total Commander (Windows Version - this time it will cost you something ) - which also has an adb plugin available) and or - zip the folder you want to transfer locally, then push it to /sdcard/ and then use Total Commander to unzip it into its desired location on the Fire TV.
Transferring .zip files wirelessly ultimately almost always turns out to be faster than transferring the individual files themselves. That also goes for zipping files on the AFTV using Total Commander, and then backing them up to a PC.
5. Use Total Commander. No seriously, download it from the Amazon App Store today. I know how popular ES File Explorer became from being the only free filemanager left, that was popular back in the day - but its approach to be iconographic to a fault and hiding away features in sub menus hurts its usability on any device where you try to perform actions with a remote. TC is simply better suited for the usecase.
TC also can write to the sdcard1 partition in Android 5 - either using root, or using a scripted workaround - so you generally dont have the "its not writable" issue. Also adb shell with su can write to it as well - so also use that if you need to.
You can also install Total Commanders LAN plugin ( http://www.ghisler.com/androidplugins/ ) and thereby access network shares.
6. There even is a usecase for the Amazon Voice button - because from Kodi - you can use it to launch Total Commander with just three button presses (say: "Total Commander") - which is faster than it was before - and you can also exit back to Kodi with only a few presses of the back button. Other than for this, the voice button of course is entirely useless - as we generally arent especially interested in how bad the Amazon Store is stocked (at least over here in europe... ).
7. Dont use the RC3 of Kodi 16 (Jarvis) right now. With Kodi 14.2 and 15.2 you can pause a video, drop back to Amazons launcher, then into Firestarter - then launch another app, then leave it and return to Kodi - with the video (usually - if you have enough free memory) still being in the paused state. In RC3 for Kodi 16, the video auto stops as soon as you switch away from Kodi - which in the long run causes much frustration and the need for additional button presses. Just remember to manually stop a video if you dont plan on returning to it anytime soon so Kodis bookmark your current position feature triggers.
8. If you want to install a Kodi repo - its much faster to download it as a .zip file and then adb push it to /sdcard/ where Kodi can find and install it - than to "start typing" anything in Kodi itself.
At some point - create a shell script for your pc that allows adb to connect to your Fire TVs IP address by just typing adb.sh (for example) - so you dont have to type in your Fire TVs ip address each time you want to connect to it.
9. If you dont already have a NAS -get an old router with an USB port that runs dd-wrt and has NTFS support (= all newer firmwares with at least 16mb package size should have it integrated - if you use ddwrt, even some with a 8mb package size). You get a very low power NAS that also can mirror as an FTP server (faster file transfers), and can become a torrent box in case you use that stuff. The negative only is - that with 4.5-6MB/s transferspeeds tops (WLAN, but actually limited by the individual routers CPU - they are low powered, remember) compressed 1080p is the most you can wish for - out of a 10-30 USD device. Preferably run it as a stand alone and not as your main router (reboots can be performed without bringing down your whole network, processor load, ...).
edit:
10. Kodi runs a little faster on the AFTV2 than on the Fire TV Sticks - which turns out to cut out just the right amounts of seconds on Kodi plugins with an "lets aggregate everything" approach.
You failed to mention what is "broken down" lol
You did quite abit of modding there so what "broke" it.
Playing a GPU intensive 3D game and then watching a video.
No, really.
The part you describe as "modding" went perfectly well - and what I describe above is mostly normal Android use for anyone not depending on "prefab click button to do thingy" stuff. Thats actually what I want this community to explore more - because at some point it literally becomes pointless - watching another in depth video analysis of Amazon taking out a row of items from their spreadsheet inspired Smart TV interface..
Amazon should have done more chip testing before they let their devices out of their factories. Or they should have done more testing regarding the 5.0.5 update. Slowly rolling out firmware updates in case you missed something important - is no substitute for proper testing...
All banter aside - the rooting process doesnt modify the kernel of the device, and on mine the GPU seems to have run into problems. From "working perfectly fine" to "full brick" (slightly different colors of black screens flashing, then settling on a full black screen) after playing a game and then watching a video.
AFTV - quality you can trust in.
Also - somehow its curious - when you buy a laptop these days - where you have root rights from the start, most complaining centers around stuff the manufacturer has messed up in producing the device and the software. But if you - as a manufacturer - take away the actual rights (permissions) from people - the discussion suddenly shifts to "OMG what have you done to the device".
But people usually dont get suddenly less educated or less cautious, once you take certain rights away from them - so the only explanation I have come up with is, that actually taking away permissions and property rights from people for some reason surfaces more voices that now very publicly campaign for this being a much more desirable state in the first place.
On a related note - If I had bricked my device during the rooting process, or while the TWRP custom recovery was installed - or by modifying system files (which now that TWRP runs on the Fire TV is easier to fix then ever), my first action would have been to give a full report of what happened (which I have actually done in a separate thread, in this case as well), so potential flaws or stumbling blocks in the rooting method could have been sussed out.
Mine has had 0 issues.. then again i rooted mine and have twrp, xposed, adaway, v4a, play store, firestarter, busybox, kodi, plex leanback youtube, debloated (removed most Amazecrap) etc.
Does more than I expected and then some.. even better than Nexus Player imo
Good - then we only agree that it isnt the rooting process.
And with TWRP you now have the means to entirely wipe and factory reset the device - so even if you for some reason had messed up the entire system partition (system files) - you still have a fallback, in fact a much better one than on a stock Fire TV, to "start over".
But that sadly doesnt fix hardware issues. Believe me, I tried. And documented it along the way. Look for it in another thread.
edit: Also this isnt me taking a jab at the device itself. I dont agree with Amazons product policies (= politics), but I was perfectly happy with my AFTV 2 as well. For as long as it worked..
In fact my fall back was to go back to the Fire TV Stick I had still laying around and I had the same functionality back (including all this "modding" you see in the OP ) within around 15 seconds (I missed the power socket in the wall twice... ).
harlekinrains said:
Good - then we only agree that it isnt the rooting process.
And with TWRP you now have the means to entirely wipe and factory reset the device - so even if you for some reason had messed up the entire system partition (system files) - you still have a fallback, in fact a much better one than on a stock Fire TV, to "start over".
But that sadly doesnt fix hardware issues. Believe me, I tried. And documented it along the way. Look for it in another thread.
Click to expand...
Click to collapse
Yea.. no device is perfect lol.. but the fact it has a gpu processor (when it works) is great! probably one of the cheaper 4k capable boxes available..
For the price, its a great option with root/recovery for what it does do and to achieve what its capable of.. theres bound to be a few bad devices and surely pushed to the max it can die
Sure.
Love the device. Dont love Amazons policies and product politics. Will use any chance to heckle them, that comes my way.
Thats me in a nutshell.
If you like the product, but dont like the company, their Store UI, their Store, the way they managed their store (app removals) in the past, the content thats in their store, their "underground" store program (that puts price pressure on devs)... thats not only possible - but also valid.
I dont think of Amazon as "a package deal".
When I criticize certain aspects of their infrastructure, I dont say that others are bad.
And I also dont proclaim that there is a high failure rate with Fire TV 2s on the 5.0.5 firmware. For me its just a nuisance and another chance to throw some banter..
But look - there is also something good, that came from it - I wrote an entire post about usability and how to best interact with the Fire TV on 5.0.5.
Because people just demanding updates (and root) - isnt enough..
yea.. i can write a banter on any device lol..
chromecast is great but cant say i like it..
the stick is worse..
nexus player is decent but also limited and if you install a full rom its essentially no longer a nexus player etc.
Deleted
Just one little additional tidbit -
Amazon still prevents the Fire TV 2 from using SD Cards formated with exFat. They literally write it out of their firmwares. Their Fire tablets of course support it - because, well its fun to play with your customer, and prevent usecases you see unfit for your current business model.
If you by any chance have purchased a 64GB Micro SD - Windows doesnt allow you to format it in Fat 32 - but this can be circumvented, by following this tutorial:
https://www.raspberrypi.org/documentation/installation/sdxc_formatting.md
Of course the 4GB filesize limit still holds up.
edit: Also tested Kodi 15.2 by now - which shows the same pause state/app switching behavior as 14.2. I've edited the OP to reflect that.
harlekinrains said:
Just one little additional tidbit -
Amazon still prevents the Fire TV 2 from using SD Cards formated with exFat. They literally write it out of their firmwares. Their Fire tablets of course support it - because, well its fun to play with your customer, and prevent usecases you see unfit for your current business model.
If you by any chance have purchased a 64GB Micro SD - Windows doesnt allow you to format it in Fat 32 - but this can be circumvented, by following this tutorial:
https://www.raspberrypi.org/documentation/installation/sdxc_formatting.md
Of course the 4GB filesize limit still holds up.
edit: Also tested Kodi 15.2 by now - which shows the same pause state/app switching behavior as 14.2. I've edited the OP to reflect that.
Click to expand...
Click to collapse
kodi installs repos fine for me on 15.2.. of course i dont use the remote I use the fire tv app and then the keyboard so it doesnt take forever
It does on all versions.
Installing repos by downloading their .zip files first, then pushing them to /sdcard/ using -
adb push /path/to/zipfile.zip /sdcard/
is just faster - because you dont have to type something you see on one screen, letter by letter - into an app on another screen. You download the file, you open a command line window, type adb push , then drag/drop the downloaded file onto the command line window to get its filepath into it - then finish typing /sdcard/ and press enter. In Kodi you then just use the "install from zip file" option.
You dont switch devices, you dont switch keyboards, you dont have to look at two screens, you dont have to copy a url. But using a BT keyboard probably in the end isnt that much slower...
Its just good practice to not see the Fire TV (stick) as a device that has to be managed on its own. It is a always on, connected Android device. You can look at its contents, you can move files from and to it, you can give it instructions...
adb and adb shell
make it open enough.
Two more usability tips.
1. If you are rooted, sideload WiFi ADB ( https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb ) - its just a quicker way of disabling and reenabling ADB - when you cant connect (since 5.0.5 the Fire TV only allows one ADB connection at a time) from your PC.
I also tried to replace adbd (the adb daemon file on the FIre TV) - but so far have only found one from API level 21 (and Fire TV 5.0.5 needs 22 (as it is based on Android 5.1)) - that one didnt work at all. Even if replacing it with the exact API 22 version would work, this doesnt necessarily mean that the "one adb connection limit" is gone - but it is something I though would be worth giving a try.
2. If you have WiFi connection issues on a Fire TV 2 - especially with the Fire TV repeatedly failing to connect, It turns out that Amazons Wifi Implementation REALLY, REALLY wants you to have WMM enabled on your router. If you don't the connection tends to drop every day and the Fire TV then has problems to reconnect. With WMM enabled I now run three days without the slightest issue - and I also have changed WiFi networks within seconds, and not as previously - it taking about 10 minutes until thats successful. Before I came by this little quirk of the FIre TV , switching bands - even temporarily on 2.4 GHz would kickstart the Fire TV reconnecting to the same AP, just fyi.
Also when you are on the 5 GHz band, the Fire TV has a "drop off" if you are on any band higher than the first few (five or six), the Fire TV has problems even "seeing" the network. Also the last channel it still "sees" it has problems connecting to - so drop even one below that if you want it running on 5 GHz.
This quirk is more widely reported than the first one, but just as annoying.
Also just a big "really?!" into Amazons direction for messing up the Wifi implementation on the device this badly. I'm sure MediaTeks proprietary drivers play a part in this, as might the Fire TV 2 always running its own ad hoc WiFi network in the background - but still Amazon is selling that stuff.
I could test it with two different routers - on largely uncongested bands in both the 2.4 and 5 GHz space - and I have half a dozen other devices that never displayed any problems with the way I had my network set up in the past - but for the Fire TV 2 I had to reconfigure my routers just so it would stop dropping out - or start finding the respective network in the first place.
I've been thinking about how all these new apps are out now that would work great on my old NST if only it ran a more recent version of Android. I saw on the old l337 thread that the NST is confirmed to be able to run more adavanced versions, but that we'd have to pull the files from a phone or other, much more powerful device, rendering the resulting ROM pretty much unusable.
Until, that is, the Nook Glowlight Plus and 3 came along. The NG+ and NG3 run Android 4.4.2. 4.4 Android could mean being able to run apps like Overdrive and Libby, without workarounds. And that would be pretty sweet.
Now these are two different devices. I'm having a hard time finding data on the difference between the guts beyond the fact that the newer models have a higher DPI screen. I'd guess they have similar amount of processing speed to preserve battery life, though maybe more RAM.
I did a little googling, and I found this CM11 Mod but it looks like it it fizzled out after getting pretty close.
Do we think this can be done?
Was wondering about this the other day. There are an awful lot of NSTs floating around ebay for US$15 now. It would be fun to be able to breathe a little life into them, if only to use them for displays of calendars, to-do lists, or anything else you can do with more modern android apps
jptiger said:
There are an awful lot of NSTs floating around ebay for US$15 now.
Click to expand...
Click to collapse
The NST, NSTG and the first Glowlight used TI OMAP3621 processors.
The Glow2, 3, 4 use Freescale (now NXP) iMX6SL processors.
That's quite a difference.
I don't think that anything would be compatible.
jptiger said:
Was wondering about this the other day. There are an awful lot of NSTs floating around ebay for US$15 now. It would be fun to be able to breathe a little life into them, if only to use them for displays of calendars, to-do lists, or anything else you can do with more modern android apps
Click to expand...
Click to collapse
Oh, I'm going to promise not to look at ebay!!! Three devices are enough, even at that price. But it's very tempting. Too bad the NSTGs are rare as hens teeth and always high priced. Then there is a screen artifact issue. The one I finally got has three, but it's not too bad, I guess.
Other than watching movies or live TV (both of which, admittedly, are actually possible with the NST if you can stand it), it seems to me these devices are still wonderfully versatile. With a minimal installation of GApps you can have all the calendar displays you want, to-do-lists, etc. For some of these applications, there are still apps that work fine. For other uses (you dream it up) it's amazing what can be done with Tasker to create an app that looks like "the real thing". And while the learning curve for Tasker is a little steep, baby steps and lots of online help and examples are available.
The one clear drawback is almost anything that requires a login. The fact that Overdrive has not yet been hacked to address this issue is probably due to a lack of interest from a person with the proper expertise (not me). But really, selecting a library book on Opera Mobile from your local library? I'd sooner slit my wrists. Books can still be downloaded to a PC and then transferred to the NST via Adobe's software (or you can get around the whole DRM issue if you wish). And, you can get mobi format books from most libraries now and they will still magically appear in your Kindle app
That said, having flashed a Nook Tablet with CM 11 (KitKat), I can attest that there are still issues with that less-old Android version. For example, you can't view XDA properly in any browser. You have to go back to an earlier skin which has tiny print and is most annoying. In fact you can't get to some sites at all with any browser. And the OS returns SSL errors for some operations with other apps. So KitKat is no panacea. Even so, I like my Nook Tablet running CM 11. It's an 8 GB version and so has limited RAM and storage. Therefore I have scaled down my usual apps to some essentials and things it is really good at. In fact, it has fewer apps on it than my NST!
Every one of those NSTs on ebay is a treasure. But I'm not going to look!!!!
Renate NST said:
I don't think that anything would be compatible.
Click to expand...
Click to collapse
I meant as fas as kernel, various hardware libraries.
nmyshkin said:
Other than watching movies or live TV (both of which, admittedly, are actually possible with the NST if you can stand it), it seems to me these devices are still wonderfully versatile. With a minimal installation of GApps you can have all the calendar displays you want, to-do-lists, etc. For some of these applications, there are still apps that work fine. For other uses (you dream it up) it's amazing what can be done with Tasker to create an app that looks like "the real thing". And while the learning curve for Tasker is a little steep, baby steps and lots of online help and examples are available.
The one clear drawback is almost anything that requires a login. The fact that Overdrive has not yet been hacked to address this issue is probably due to a lack of interest from a person with the proper expertise (not me).
Click to expand...
Click to collapse
Thanks for the thorough response! I didn't realize you could do so much! I was envisioning having three mounted on walls in various places in my apartment, one with an interactive Google calendar, one with my to-do list from Any.do, and one with a local transit app that shows if there are delays on specific trains etc. (though I guess that one might wait until we're all using public transit again...) I've never used Tasker before, do you have any suggestions of resources or guides on getting it to replicate any functionality like this on an NST?
nmyshkin said:
Every one of those NSTs on ebay is a treasure. But I'm not going to look!!!!
Click to expand...
Click to collapse
Good luck! Save your money and vicariously help me do stuff with them?
jptiger said:
Thanks for the thorough response! I didn't realize you could do so much! I was envisioning having three mounted on walls in various places in my apartment, one with an interactive Google calendar, one with my to-do list from Any.do, and one with a local transit app that shows if there are delays on specific trains etc. (though I guess that one might wait until we're all using public transit again...) I've never used Tasker before, do you have any suggestions of resources or guides on getting it to replicate any functionality like this on an NST?
Click to expand...
Click to collapse
There is only one version of Tasker that will run on the NST/G (check your PM). It is designed to run in the background and execute tasks from shortcuts on the home screen or automatically start a series of tasks based on some trigger (time of day, opening a specific app, connection to WiFi, etc.). I originally used it to automatically start WiFi for apps that needed it. This is definitely a "baby step" idea. I don't use Tasker as a background service any longer. There is a companion app called AppFactory which takes your Tasker routines and converts them into stand-alone apps that anyone can run (with the caveat that either GApps must be installed or else two small Maps library files would need to be copied onto the device--actually this is a dependency for Tasker itself also). You can see many examples of "apps" I have created in this fashion in the last section of this forum. You design your own GUI to fit the NST/G screen. Tasks can vary from a simple activity call to website data scraping and massaging (definitely advanced) and more.
AppFactory will not run on the NST/G. It requires Android 2.2. I have a KitKat device which will run both the ancient version of Tasker and also AppFactory, so after I finish designing and testing the routines on the NST I move all the files over to the KitKat device and compile with AppFactory. The resulting app can be installed on the NST and behaves just like any other app (and does not require the presence of Tasker to run).
A lot of patience is required to get things right, especially if you want a full-screen GUI since Tasker seems to hate screen edges and when you edit a screen containing a near-full-screen image it tends to resize it a little smaller, throwing off other elements. Fixing this requires hand-editing the coordinates in the xml files which describe the scene elements. Also, because the file structure on the NST is not the same as on a KitKat device, references to images have to be edited by hand before (or after) moving files to the second device to compile. For example, "/media/" might need to be changed to "/storage/external_SD/Pictures/" or similar. Also, the touch screen on the NST is not always as responsive as we might like.
Finally, there is one one last fly in the ointment, so to speak. Tasker will not install on FW 1.2.2 for some reason unless it is resigned. When it is resigned, it ceases to interact properly with plugin apps (things like RotationLocker, or Minimalistic Text, as examples). The compiled apps will work properly, but testing on the NST is problematic if you are referencing plugins. On FW 1.2.1 everything works properly. Since I have three devices (gulp) I kept one on FW 1.2.1 to help me with this issue.
There is a Tasker Wiki with many examples, but just Googling will yield all kinds of things. There is a guy (Hollywood Frodo) who created all kinds of videos from the basic to the exotic and I found some of those very helpful. Finally, there is a Tasker Google group where--to judge by my personal experience--no question is too stupid!
While looking for something completely different, I stumbled across this and thought some people might find it interesting:
Turn an old eReader into an Information Screen (Nook STR) – Terence Eden’s Blog
shkspr.mobi
I wouldn't fixed NST to a wall and think that I have read here about app used here to do that job. Either someone is gonna fix TLS issue or maybe if we assume using NST as display it could be possible to use home Wi-Fi router or mobile phone as secure server or part of VPN that will negotiate TLS issue for NST. I always doubted slightly that NST can offer full internet browser experience but something in line of htttp web grab in reader mode might be good enough for some application. News (RSS), weather and I believe that maybe EPG TV guide are not impossible to accomplish. Only question about this remains will NST embedded HTML browser will be good for the job of showing the grab from web pages or is Opera in reader mode better for such job. Time to look up for a good web grabber...
SJT75 said:
I wouldn't fixed NST to a wall and think that I have read here about app used here to do that job. Either someone is gonna fix TLS issue or maybe if we assume using NST as display it could be possible to use home Wi-Fi router or mobile phone as secure server or part of VPN that will negotiate TLS issue for NST. I always doubted slightly that NST can offer full internet browser experience but something in line of htttp web grab in reader mode might be good enough for some application. News (RSS), weather and I believe that maybe EPG TV guide are not impossible to accomplish. Only question about this remains will NST embedded HTML browser will be good for the job of showing the grab from web pages or is Opera in reader mode better for such job. Time to look up for a good web grabber...
Click to expand...
Click to collapse
Curl can often bypass SSL checks and grab web content. It runs on the NST. I've used it in a few of my apps. Whether the data it gets can be used by the app the blogger mentions is something else.
@nmyshkin that is nice idea! And seems exactly in line of what I wrote. I do not know is curl accessible from Android layer. I pondered the same thought more in line of trying to use port of Lynx to Android I have seen someone did although who knows is that possible to do on this version of Android?
I've written a status app (that I never use).
It polls two different servers for JSON info and displays it using regular Android graphics stuff.
It uses Retrofit for polling.
And one more! (although this one uses a Sony PRS-T1)
Reusing my ebook reader – Fluffyelephant
Hmm, you got me thinking about this stuff.
There's the whole let the Nook poll some data service and display it on a web browser sort of thing.
I don't really need or want that.
I was thinking more of like as a status output device for a headless Raspberry Pi.
No, not as a terminal, more like status for a solar/home/whatever system.
The Nook doesn't poll anything, it just sits there waiting for text or graphics.
But here's the part I like, you don't use any WiFi.
You just plug your Nook into the Raspberry Pi.
Of course it has adb.
You can get adb for Raspberry Pi: sudo apt-get install android-tools-adb
Now you can set up port forwarding:
Code:
[email protected]:~ $ adb forward tcp:6666 tcp:6666
Then all you need is something on the RPi to connect to port 6666 and spit out stuff.
On the Nook you need an app to serve port 6666 and do display stuff.
I've already made a clock as proof of concept and it works fine.
You could just use text fields or compose a whole graphic frame on the RPi and send that over.
Heck, if you send whole frames you wouldn't even need to run the Android subsytem.
I could probably get that working on a Kobo.
A very sophisticated example follows.
It allows you to individually update separate fields.
These could be in tables with borders or labels or whatever.
Edit: Okay, a better screenshot.
You know, the thing I like about this is that the NST is the server.
It's a bit like running X11, but much more lightweight.
And if you want you can still run this over WiFi instead of ADB forwarding.
This electric sign app is really close to something I'm looking for. What I'd like to do is, instead of a screenshot of a URI, to take a screenshot of what I've got open in the device.
I'd like to use this with Google Calendar, and Opera Mini surprisingly seems to work with the HTML version. I think Opera Mini keeps the calendar updating with AJAX or something, so all I'd need an app like this to do would be to, when it's running, take a screenshot of what's on the screen right before sleeping and set that as wallpaper, then wake every X minutes, screencap what's there and go back to sleep with that as the new wallpaper. The end result should be an always-on, low power Google Calendar.
EDIT: For anyone looking later, I was wrong. Opera Mini does not keep updating Google Calendar, you have to refresh it manually, which makes this slightly more complicated...
jptiger said:
This electric sign app is really close to something I'm looking for. What I'd like to do is, instead of a screenshot of a URI, to take a screenshot of what I've got open in the device.
I'd like to use this with Google Calendar, and Opera Mini surprisingly seems to work with the HTML version. I think Opera Mini keeps the calendar updating with AJAX or something, so all I'd need an app like this to do would be to, when it's running, take a screenshot of what's on the screen right before sleeping and set that as wallpaper, then wake every X minutes, screencap what's there and go back to sleep with that as the new wallpaper. The end result should be an always-on, low power Google Calendar.
Click to expand...
Click to collapse
Somewhere on the site there is a discussion of a setup that copies the current screen into a screensaver folder so that, for example, a map remains visible when the device sleeps. Search for it.
Edit: https://forum.xda-developers.com/t/q-fridge-calendar.3057759/#post-59527882
Edit: https://forum.xda-developers.com/t/...uestion-o-noob-friendly.2941262/post-57216860
Eh, I'm not fond of browser-based anything,
For plain HTML stuff you could throw something together with Webkit instead.
For the adventurous you could use the Google Calendar API
Renate said:
Eh, I'm not fond of browser-based anything,
For plain HTML stuff you could throw something together with Webkit instead.
For the adventurous you could use the Google Calendar API
Click to expand...
Click to collapse
I tend to agree with you. As I already wrote above something akin to Pocket/ReadItLater and similar might be accomplished using simple web grab I presume and offline HTML browser. I have thought that it looks odd that beside "hidden" (and sadly for us practically unusable) browser NST have another HTML viewer. Reason for that might be it was intended to be used for B&N "browsing" through their shop that they periodically download to NST or maybe for presentation of e-book material of older type that was for all intents and purposes just web archived HTML page or perhaps for viewing magazines purchased through B&N.
In essence even epub use elements of CSS/HTML but that is another story. Maybe it could be possible to make some poor man Pocket like offline browser if we somehow find the way to cobble together parts of some RSS, bookmarks syncing, e-mail listing, forum/blog viewer and approach that me or nmyshkin proposed here. In my opinion hardest part if some web grab is possible would be to render it in usable form for this device. That mean turning of ads, flash/video, loading pictures only on demand (or better in on/off way) and show only text information. Now what "browser" is suitable for this is yet to determine. I know that very old Opera could turn off animation an pictures but as I remember it did that in such way that it didn't download them at all to save bandwidth. Maybe it could be somehow set to load web archives in such manner? Think about it as giving an command that some web page be "printed as epub". It might be to large task to accomplish. Pocket worked if I remember right in such way that selected page was sent to dedicated server which did the trimming part for user and allowing him/her to download that content on other device to be read later on. Here I think that if we could sync for example one of bookmark folders from a computer with NST and achieve web grab of those links in usable form we might have something. It is a matter for the debate isn't Opera mobile and style management already wrote on here in forum same or even better. Problem would be that page reformat/rendering would be tasked to NST itself and I am not sure if it is up to the task or am I capable to cobble such thing alone for that matter. Something flashed in my mind didn't Calibre had some news reader? If it does then I am inventing the wheel here. Still it would be nice to be able to have some even limited ability to open a link to a news story from RSS feed or a forum/blog we follow or e-mail listing etc.
For Calendar I hope that some kind of dedicated app combining Calendar, planner and to do list can be found to already exist for this device.
Did anyone inspected this option? https://greycoder.com/a-list-of-text-only-new-sites/ It might be interesting
SJT75 said:
Did anyone inspected this option? https://greycoder.com/a-list-of-text-only-new-sites/ It might be interesting
Click to expand...
Click to collapse
Thanks for these! The ersatz Google News is amazing in that even the external links are text-only! It makes my Google News app obsolete! Great with Opera Mini. Many, many things to look at there
nmyshkin said:
Thanks for these! The ersatz Google News is amazing in that even the external links are text-only! It makes my Google News app obsolete! Great with Opera Mini. Many, many things to look at there
Click to expand...
Click to collapse
I am glad that I have contributed with something useful. As have already guessed from mine posts in this thread I have contemplated heavily about what could be more useful for NST some text-only browser akin to old trusty Lynx or some rewrite/redefinition of working Opera. One thing lead to another and at first I thought to maybe open and disclosed source for firefox readability extension/addon ported for working version of Opera somehow is a way to go but as I always check all aspects of mine quirky ideas I stumbled upon this. It is poor man solution but as I remembered that you follow NPR and they have text mode only site felt obliged to mention it here.
In line with nmyshkin's idea of using curl if some information display akin to the one linked in the first post is needed does something like cron from Linux can be run on NST?
"Print as epub" exist as web form. Here is the result of that one. https://dotepub.com/ I tried to use online form there and results were mediocre but as I understand they also offer their API to developers etc. That I presume might draw attention from someone on xda.
In defense of the intended idea for using NST as info screen arguably touch technology it uses is best for those screens. Mine guess is that its deemed as such because it is most easily scalable from the currently available techniques. This also raise the question why B&N did not already made readers of much larger format like A4 paper size screen. Is the display cost really that high and prohibitive? On the other news rumors have spread that they have partnered with Lenovo not only for the new generation of tablets but also for new e-readers. Has anyone find some leek about possible specifications?
SJT75 said:
... rumors have spread ...
Click to expand...
Click to collapse
Say, what? After my buying a Poke3?
Edit: See https://www.barnesandnoble.com/w/no...ovo-barnes-noble/1139012795?ean=9780594080503
1200 x 800 for a 10" = 144 DPI, not drop dead impressive.
I agree. Cheap bastards! I can't say is that 149DPI good for LCD screen but is sub par for e-reader. They obviously targeted minimum resolution comparable to low resolution printing and hope to get away with it. Considered that I expressed criticism to level of development of current color e-ink technology being bellow resolution of NST by about 60% you can bet I find this to little question is does it comes to late for B&N. Still I am more interested about e-ink display device that rumor say is also planned but nothing is revealed so far.
Renate said:
Say, what? After my buying a Poke3?
Edit: See https://www.barnesandnoble.com/w/no...ovo-barnes-noble/1139012795?ean=9780594080503
1200 x 800 for a 10" = 144 DPI, not drop dead impressive
Click to expand...
Click to collapse
Nothing to report that is mine work now still in the spirit of this thread I want to post few links with things people did with e-ink screens that might be done with NST also.
1. Raspberry Pi powered news scrapper - something Renate might like as she as I understood work on something similar
https://www.reddit.com/r/raspberry_pi/comments/ksgomp
2. Weather display that I believe was made using software already mentioned somewhere on forum
https://www.reddit.com/r/homeassistant/comments/lcyos9
3. Something completely different! Device made as platform to enable development many things e-ink made. Link shows RSS implementation.
4. In the old days when e-readers were unobtainable on my location I was in desperation contemplating the idea to convert available photo frames to a e-reader. This is as you guess the other way around.
https://www.reddit.com/r/raspberry_pi/comments/liadda
5. Someone developed site for games for e-ink screen as I understood browser only
https://e-ink.club/index.php There is in my opinion plenty of room for some sort of games on e-ink and this is not comprehensive list but it is nice someone started a dedicated page/project for that.