Mobileread
What version of Android is the Glowlight Plus (2019) software using?
#1  aquilegia 12-29-2020, 07:57 AM
I know Nooks use some kind of interface over Android - what version of Android are they running currently? I'm sort of idly curious since I have been considering getting a Nook Glowlight Plus (for the big screen & buttons) and hacking it so I can do other stuff with it/get to the the regular Android stuff.
Reply 

#2  Ryzir 12-30-2020, 12:11 AM
4.4.2 (KitKat)

Be aware that the default software has no back button and most Android apps need one. Button saviour app can add on-screen back, home, and menu buttons or you can root and re-map one of the hardware buttons to be a back button.

I have my Glowlight 3 (also Android 4.4.2) rooted to re-map the buttons and to set sleep screen to be the cover of the book I'm currently reading. I use Zeam Launcher, Calibre Companion, Alreader, ColorDict, and Solid Explorer apps.

It is the best reading experience I've had out of all the devices I've owned.
Reply 

#3  Pajamaman 12-30-2020, 02:44 PM
The xda forum details how to root it. I think buttonsaviour will be a must install to get a back button. I have the 6" and the screen is excellent. But I use an Onyx now. But you can get a Nook real cheap and root it and put nookmanager on there. Works good. Way better than the default software.

https://forum.xda-developers.com/t/how-to-root-and-set-up-a-new-nook-glowlight-3.3802331/
Reply 

#4  aquilegia 12-31-2020, 08:26 AM
Ooh thanks for all the tips! I've definitely heard that the default software is terrible.

I was debating getting a Glowlight Plus for the bigger screen and then saw a refurbished Kobo Forma for $145 on ebay and grabbed it immediately because it was such a fantastic price (and it works great, definitely pleasant in some ways that my ancient kindle was lacking) but I think the Glowlight Plus might be a better fit for me.

Does anyone know if Hoopla works decently on the Glowlight's version of Android? Or is it too old/slow for that?
Reply 

#5  Pajamaman 12-31-2020, 11:13 AM
https://www.mobileread.com/forums/sh...d.php?t=291744
Reply 

#6  Burktross 12-31-2020, 04:26 PM
Quote Ryzir
4.4.2 (KitKat)
I have my Glowlight 3 (also Android 4.4.2) rooted to re-map the buttons and to set sleep screen to be the cover of the book I'm currently reading. I use Zeam Launcher, Calibre Companion, Alreader, ColorDict, and Solid Explorer apps.

It is the best reading experience I've had out of all the devices I've owned.
How does the reading experience on a rooted Glowlight 3 differ from the vanilla experience, aside from greater freedom / stability on the backend? I've been thinking about rooting my new Glowlight 3, but I don't want to risk bricking it for nothing.
Reply 

#7  Ryzir 01-01-2021, 07:11 PM
To side load apps you do not need root. Just ADB initially and if you put a launcher and file explorer you then can side load apps via usb drag and drop (then install from file explorer on reader) instead of ADB. I have my reader rooted to re-map the hardware buttons (one being a back button) and to enable me to display the book I'm currently reading as the sleep screen.

I have Calibre Companion which I use instead of the default library software which gives me wireless transfer of books, far more customizable navigating options of my books (By tags, series, author, etc.), CC can set the cover of the book I'm currently reading as the sleep screen (with root).

For reading software I use Alreader which has a lot more customization options than the BN reader. I can side load fonts, customize touch screen zones, show how many pages left in chapter, chapter name, clock, battery level, reading position bar with chapter marks, ability to open images in external image viewer with ability to pinch zoom (I use solid explorer for this).

I like the ColorDict dictionary better than the BN dictionary but I don't really use the dictionary that much. It also integrates with Alreader really well.

I've re-mapped the hardware buttons (with root) so that the "n" button is page forward which makes a huge difference for me since I like to hold the reader with one hand on the bottom with my thumb to press the "n" button.

The downside is that it takes quite a bit of time to get it all set up correctly but once it's all set up it all works really, really well.
alreader.jpg dictionary.jpg 
Reply 

#8  Burktross 01-01-2021, 08:30 PM
Quote Ryzir
<snip>
That does look and sound very compelling. I suppose that if I don't want to remap hardware buttons, I wouldn't even need to root then. Do the hardware buttons function with Alreader out of the box?
Reply 

#9  Ryzir 01-02-2021, 12:04 AM
Quote Burktross
That does look and sound very compelling. I suppose that if I don't want to remap hardware buttons, I wouldn't even need to root then. Do the hardware buttons function with Alreader out of the box?
No unfortunately, you have to re-map for the page turn buttons to work in Alreader. Once you have root it's easy to re-map, basically just changing some text in a file.
Reply 

#10  Burktross 01-02-2021, 12:46 AM
Quote Ryzir
No unfortunately, you have to re-map for the page turn buttons to work in Alreader. Once you have root it's easy to re-map, basically just changing some text in a file.
Ah alright, that makes sense. If this guide I found on XDA is anything to go by, rooting doesn't look too hard anyhow. One last question; how do you interface with the Nook brightness/warmth settings in the non-proprietary apps? Does the top status bar still appear on tapping the screen?
Reply 

  Next »  Last »  (1/2)
Today's Posts | Search this Thread | Login | Register