Database Users

Rooted Nook: Problems using Dropbox / Pocket (Read it Later) / Evernote?

Hello everybody,
last year I bought a Kindle 4 (non-touch) and I liked the eInk reading experience so far. The main reason for me: I am travelling a lot for business and I prefer packing light.
But at the same time I am an avid Android user (Galaxy Nexus at the moment) and love taking a break checking my newsfeeds with Google Reader throughtout the day, while sending longer articles to the App "Pocket" (formerly Read It Later).
This was the main thing missing on my kindle...as it just didn't work natively. The detour sending the articles reformated with e.g. Istapaper to my kindle-whipsernet mailadress is just uncomfortable.
I was searching through the forum and kept watching YouTube Videos about the rooted Nooks and other ebook readers with Android on it, because I wanted to find out if it works flawless with apps such as:
Dropbox (keeps loads of work related pdfs in there)
Pocket (formerly Read It Later)
Evernote
What is your experience with it?
The nook so far seems to be the best solution for my requirements.
And I actually like the glow feature and that the buttons now work with custom Roms. Or did I get that wrong?
Thank you very much in advance!
I hope I am not asking too much. If I was just too stupid to find information please give me a hint Thanks!
Leo

My personal experience
Evernote works, sometimes it Force Closes, I think Dropbox works perfectly, and Pocket currently is not supported; maybe you should try an older version, when it was still Read It Later.
I'm pretty satisfied with my Nook, I don't know if the new Kindle Paperwhite is based on Android, but if it is I'll consider getting one.

I can confirm that Read It Later (previous version of Pocket) works perfectly.
I got the apk out of one of the other threads, but I should be able to dig up what version it was later.

For Dropbox I'm using app called Dropsync which support two way synchronization - so far I'didn't have any problems with it. Works fast and easy.
Instead of Pocket u can use Instafetch (supports Instapaper.com).

alejandro.lopezavila said:
Evernote works, sometimes it Force Closes, I think Dropbox works perfectly, and Pocket currently is not supported; maybe you should try an older version, when it was still Read It Later.
I'm pretty satisfied with my Nook, I don't know if the new Kindle Paperwhite is based on Android, but if it is I'll consider getting one.
Click to expand...
Click to collapse
Thank you very much
I can live with force closes from time to time, as long as I would have access to notes that I can just leave open on a screen that doesn't consume any energy!
Ramides said:
I can confirm that Read It Later (previous version of Pocket) works perfectly.
I got the apk out of one of the other threads, but I should be able to dig up what version it was later.
Click to expand...
Click to collapse
That is fine enough
Thank you very much!
As I am not the biggest fan of the new blown-up pocket interface anyways
Rafsen said:
For Dropbox I'm using app called Dropsync which support two way synchronization - so far I'didn't have any problems with it. Works fast and easy.
Instead of Pocket u can use Instafetch (supports Instapaper.com).
Click to expand...
Click to collapse
Yes, I am a paid user for dropsync by myself. I love it!
Great to hear that it works flawless Thanks!
Thank you all for your comments!
(Sorry, was absent over the weekend and last days.)
Now I am trying to get a Nook in Germany :victory:

Yesterday I finally received my Nook Simple Touch Glowlight and love it so far.
The feature of sideloading custom android Launcher and being able to use apps is just phenomenal.
I rooted using NookManager and installed the gapps package. That so far works flawless!
But, however, I am still missing Pocket / Read it Later
Does anyone still have a working apk?
There are around 1000 articles saved in my pocket and I can't just switch to Instapaper.
Furthermore...does anyone have a apk of the stock Google Reader?
Thanks

Okay...there we go:
http://www.apktops.com/read-it-later-pro-1-3.html
Read it Later Pro v.1.3 :good::laugh:
Found it an old Lifehacker article, called "Turn your rooted Nook into the ultimate ereader with these 10 apps"
http://lifehacker.com/5926798/turn-your-rooted-nook-into-the-ultimate-ereader-with-these-10-apps
Anyways...worth a read
Getting all set up.
Dropbox, DropSync, Evernote, Gmail, Calendar, Read It Later, Opera Mobile, Maps, Google Drive, Google Reader, Amazon Kindle, AnkiDroid, Translate, Urban Dictionary, Dict.cc Plus
:victory:

Odp: Rooted Nook: Problems using Dropbox / Pocket (Read it Later) / Evernote?
You may want to check using your own RSS feed from pocket. Just add it to e.g. RssDemon, which works great on nook.
Wysłane z mojego GT-I5700 za pomocą Tapatalk 2

Oh thanks!
I didn't know that there is an RSS feed!
But I can't imagine that there is a synchronisation?
Because RSS doesn't allow any feedback from the client if I am not mistaken.
(I am not home right now...so I can't test it )

spaboleo said:
Oh thanks!
I didn't know that there is an RSS feed!
But I can't imagine that there is a synchronisation?
Because RSS doesn't allow any feedback from the client if I am not mistaken.
(I am not home right now...so I can't test it )
Click to expand...
Click to collapse
I works just as standard RSS, if there is something new to download detected, it is downloaded. But only once app perform time based checks (every hour for example). So it is not a push service, like in mails ( right the time one comes it is downloaded, i presume)

Ah...hmm...yeah then I could just read them directly in my RSS reader I guess
The temporary storage of articles that I want to read later is what comes in handy
Well the Read it Later APK from above still works, even though the scrolling is a bit odd on the nook. I have to perform quite long strokes on the screen to get it to move forward.
Anyways...better than nothing :good:
Too bad that Google will discontinue the service for Google Reader...it was such a convenient webapp

Evernote has stopped working for me - the screen always just blinks for a second when I'm trying to open the app. I tried deleting the cache, deleting the dalvik cache, reinstalling the app and rebooting - nothing helped. I wonder, if this is related to the latest update 5.0.2? Has anybody elso got similar isues? Thanks!

schlozi23 said:
Evernote has stopped working for me - the screen always just blinks for a second when I'm trying to open the app. I tried deleting the cache, deleting the dalvik cache, reinstalling the app and rebooting - nothing helped. I wonder, if this is related to the latest update 5.0.2? Has anybody elso got similar isues? Thanks!
Click to expand...
Click to collapse
I had the same issue, i didn't find any solution for the newest version, had to install Evernote 4.5.6.2 which works fine.
Available from Android Drawer Repositary.

FBReader 1.8.2 is crashing quite often

Hi All,
Have you ever had such a problem with FBreader? (see attached pic)
It happens every few times you launch the app.
It's quite annoying, because you have to hit the cancel button and restart the app few times to get it working.
Initially I though it might be related to a lack of memory or something, but after freeing more that 100MB of ram it still crashing.
Thanks,
m6

moosix said:
Hi All,
Have you ever had such a problem with FBreader? (see attached pic)
It happens every few times you launch the app.
It's quite annoying, because you have to hit the cancel button and restart the app few times to get it working.
Initially I though it might be related to a lack of memory or something, but after freeing more that 100MB of ram it still crashing.
Thanks,
m6
Click to expand...
Click to collapse
Damn, I posted it in wrong category
Can someone move it to i.e. "Nook Touch General" ?
Thx

Moved.

I'm rooting now with the primary objective being FBreader. I'll let you know how it goes.
Have you found a solution or an older version that is stable? Which android version did you use? My understanding is that the Nook Touch is based on Android 2.0 so I'm trying that one first. There are three versions of each build available: http://fbreader.org/FBReaderJ
moosix said:
Hi All,
Have you ever had such a problem with FBreader? (see attached pic)
It happens every few times you launch the app.
It's quite annoying, because you have to hit the cancel button and restart the app few times to get it working.
Initially I though it might be related to a lack of memory or something, but after freeing more that 100MB of ram it still crashing.
Thanks,
m6
Click to expand...
Click to collapse

Sim2 said:
I'm rooting now with the primary objective being FBreader. I'll let you know how it goes.
Have you found a solution or an older version that is stable? Which android version did you use? My understanding is that the Nook Touch is based on Android 2.0 so I'm trying that one first. There are three versions of each build available: http://fbreader.org/FBReaderJ
Click to expand...
Click to collapse
From what I've read about NST, it's running Android 2.1 (but some apps that require 2.2 also works).
At the moment I'm playing with FBReader 2.0 beta 8 for Android 2.* devices, so far it works pretty good. The only thing that doesn't work is search. Wherever I try to search for a book app does a quick restarts of the device!!! (maybe it requires some system application that I've disabled when using a "Disable all B&N apps" option in NookManager).
Apart from FBReader I can recommend some other ereaders:
Prestigio ereader 3.1 - it's a nice clone of FBReader but only if you don't mind a rather poor visibility in the bookshelf view
EBookDroid very good PDF DJVU reader
txt reader It only reads txt files

btw. GO Book is also nice ereader. There's only one problem with it. It always opens a book in a fullscreen mode, which prevents you from using the statusbar "go back/menu" buttons.
To overcome this nasty feature use Smart Statusbar

Thanks for the reply, I settled on the same version of FBReader with good results. It crashes under one rare circumstances (that I can't actually remember atm..) but not while I'm reading.
I also got Colordict 3 working so I'm happy about that. had to install the Google App store to get it as it's not in the Amazon store.
I use FB on all of my other devices so I'm sticking with it. Great reader, IMO. And since I'll rarely if ever leave the app, I'm quite satisfied now. FBreader in-book search works for me. Are you talking about the B&N book search?
The only FB annoyance I've noticed is that I've been unable to get FBreader to access the on-board book location which seems to be /media/My Files/books. I can only get FB to access the /sdcard. Not delved to deeply into this yet as Its not a big deal.
Would be nice if there were complete ROMS with only E-reader and related software installed. This doesn't seem to be the case for the NST. I had to jump through a few hoops to get this rooted & install apps and I've rooted quite a few android devices before.
moosix said:
From what I've read about NST, it's running Android 2.1 (but some apps that require 2.2 also works).
At the moment I'm playing with FBReader 2.0 beta 8 for Android 2.* devices, so far it works pretty good. The only thing that doesn't work is search. Wherever I try to search for a book app does a quick restarts of the device!!! (maybe it requires some system application that I've disabled when using a "Disable all B&N apps" option in NookManager).
Apart from FBReader I can recommend some other ereaders:
Prestigio ereader 3.1 - it's a nice clone of FBReader but only if you don't mind a rather poor visibility in the bookshelf view
EBookDroid very good PDF DJVU reader
txt reader It only reads txt files
Click to expand...
Click to collapse
---------- Post added at 08:22 AM ---------- Previous post was at 08:17 AM ----------
moosix said:
btw. GO Book is also nice ereader. There's only one problem with it. It always opens a book in a fullscreen mode, which prevents you from using the statusbar "go back/menu" buttons.
To overcome this nasty feature use Smart Statusbar
Click to expand...
Click to collapse
I actually prefer full screen. I re-mapped the right side buttons to android 'back' and 'menu' so I can navigate android and other apps more easily. Pressing menu in FBReader also brings up the status bar.
BTW, I rooted with NookManager, and then installed a google apps package to get the (somewhat broken) G app store.

Google Books: no basket/cart so can't buy books.

Using gbooks_10_16.apk I can search and get a book list, but nothing happens when I click a book. The basket/cart and pay apparatus is missing. Does anyone know how I can fix this?
I've also tried gb152.apk, but this doesn't seem to work at all.
I rooted with Nook Manager and then ran NTGAppsAttack (both v.050). NTGAppsAttack went fine until I clicked on Market only to find there were no apps at all anywhere. I left the Nook near my wifi, with wireless on, for hours and finally What's App appeared. I'd have preferred something simpler, but installed it anyway and then, having doubts, uninstalled via the Apps Drawer. I then upgraded the Market and installed SearchMarket, which just brings up the search keyboard. However, it finds apps, thpough only free ones, and downloads them. The Market still shows only What's App, though something else appeared briefly. There was no Books app in the Apps Drawer, so I downloaded the above versions.

caromcm said:
Using gbooks_10_16.apk I can search and get a book list, but nothing happens when I click a book. The basket/cart and pay apparatus is missing. Does anyone know how I can fix this?
I've also tried gb152.apk, but this doesn't seem to work at all.
I rooted with Nook Manager and then ran NTGAppsAttack (both v.050). NTGAppsAttack went fine until I clicked on Market only to find there were no apps at all anywhere. I left the Nook near my wifi, with wireless on, for hours and finally What's App appeared. I'd have preferred something simpler, but installed it anyway and then, having doubts, uninstalled via the Apps Drawer. I then upgraded the Market and installed SearchMarket, which just brings up the search keyboard. However, it finds apps, thpough only free ones, and downloads them. The Market still shows only What's App, though something else appeared briefly. There was no Books app in the Apps Drawer, so I downloaded the above versions.
Click to expand...
Click to collapse
So just to be sure, you are using the NST?
You will see very few/no apps via the Market app. Sometimes the category list will dredge up an app or two (free), but you need SearchMarket to find anything. I think you are right about only free apps. It may be that the old apps cannot negotiate the security transactions for paid apps.
And on that topic, the non-function of the store in Gbooks is your least problem. Have you noticed that it doesn't upsync?! I and others have done a pretty thorough investigation of the various versions that will run on the NST.. The version you mention has a functioning reader but can't upsync. I think up to 1.3.5 the reader still works (going from memory here...) but no upsync. The oldest version that will currently sync is maybe 1.5.2, but only if you can get the book to actually display, which is more miss than hit.
I played with Gbooks for a long time, even though I've never used it. I don't think it's doable without a serious rewrite of the source.

If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.

cjpicci said:
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
Click to expand...
Click to collapse
Does your version upsync? If so can you post a copy of the apk?

nmyshkin said:
So just to be sure, you are using the NST?
You will see very few/no apps via the Market app. Sometimes the category list will dredge up an app or two (free), but you need SearchMarket to find anything. I think you are right about only free apps. It may be that the old apps cannot negotiate the security transactions for paid apps.
And on that topic, the non-function of the store in Gbooks is your least problem. Have you noticed that it doesn't upsync?! I and others have done a pretty thorough investigation of the various versions that will run on the NST.. The version you mention has a functioning reader but can't upsync. I think up to 1.3.5 the reader still works (going from memory here...) but no upsync. The oldest version that will currently sync is maybe 1.5.2, but only if you can get the book to actually display, which is more miss than hit.
I played with Gbooks for a long time, even though I've never used it. I don't think it's doable without a serious rewrite of the source.
Click to expand...
Click to collapse
Yes, I'm using the NST. I haven't looked at syncing because as I understand it this is just a question of convenience when reading on multiple devices, which is not my aim. I just want to get books onto the Nook. Many thanks.

cjpicci said:
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
Click to expand...
Click to collapse
Many thanks. This is very interesting, but I'll have to wrap a wet towel round my head before going back to the thread you suggest! Too late at night now.

nmyshkin said:
Does your version upsync? If so can you post a copy of the apk?
Click to expand...
Click to collapse
It seems to upsync last read pages, roughly anyway since the formatting varies for different devices. Since this old version doesn't support anything like notes or highlights, I'm not sure what else it could sync.
What's the best/most practical way to share files on xda? While I've been lurking for quite some time, I only created an account fairly recently.

cjpicci said:
It seems to upsync last read pages, roughly anyway since the formatting varies for different devices. Since this old version doesn't support anything like notes or highlights, I'm not sure what else it could sync.
What's the best/most practical way to share files on xda? While I've been lurking for quite some time, I only created an account fairly recently.
Click to expand...
Click to collapse
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.

nmyshkin said:
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
Click to expand...
Click to collapse
I've solved my problem now. I've been trying to download books from Google, first to my NookST and then to my laptop. But I'm running 32-bit Linux on my laptop and Google, like Adobe, seems determined to exclude Linux from the world of ebooks. So I downloaded to my Android phone and was quite surprised when the book also appeared on my Nook. I was offered the option of syncing, but decided not to be too ambitious in case it caused problems with the rather old Nook software.
It may have helped that I did all the NTGAppsAttack process on my Nook (I didn't want to go to the laptop because of the Linux problem). After I typed in my phone number I first tried to confirm on the phone and, when that didn't work, typed in the confirm number on my Nook. So perhaps the 2 devices finally got quite firmly linked.
I'll have a go at attaching the Google Books version I'm using, gbooks_10_16.apk.
I got it from another post on this forum. The reader works well but doesn't have a search facility.

nmyshkin said:
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
Click to expand...
Click to collapse
Here's the md5 for the attached file generated by Android File Verifier:
bde6462cde86e0521d0b78270e11adb4
I think I probably got this apk when it was posted a long time ago, but I can't remember for sure. I just let Lookout scan it again and it came up "safe", for whatever that's worth.

cjpicci said:
Here's the md5 for the attached file generated by Android File Verifier:
bde6462cde86e0521d0b78270e11adb4
I think I probably got this apk when it was posted a long time ago, but I can't remember for sure. I just let Lookout scan it again and it came up "safe", for whatever that's worth.
Click to expand...
Click to collapse
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.

nmyshkin said:
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
Click to expand...
Click to collapse
Glad it's working for you too! I can't remember for sure, but I think this version might've been recommended by someone else before. I'll have to look through my old bookmarks...

nmyshkin said:
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
Click to expand...
Click to collapse
Thanks for all the info, guys. Second time you've steered me in the right direction, nmyshkin. NB Attaching the apk file was difficult because the process was incredibly slow (and not even a whirligig). Lots of notices about scripts that had stalled. I'm running Linux Mint 17 (Cinnamon) 32-bit; browser is Firefox.

Opera Mobile and TLS 1.2

It's time to show a little more love for arguably the best browser for the NST/G
I've been reading up on the whole TLS 1.2 thing and bemoaning the gradual eroding of the NST/G internet capabilities as various apps wink out of usefulness due to the recent change. I felt the same way about Opera Mobile 12.10, especially when I had finally figured out an app for Google News, only to find that many of the external links could not be opened, presumably due to this new security protocol.
Imagine my surprise today when I revisited the configuration screen for Opera Mobile and saw that even on this nearly prehistoric app there is an option for TLS 1.2!! Once I had selected that I could suddenly navigate to all kinds of sites that were previously snubbing me! Woo-hoo!
The procedure, in pictures, below. Love live Opera Mobile (at least until TLS 1.3).
Edit: I should mention that this has nothing to do with the recent NST/G update to 1.2.2. B&N only added TLS 1.2 handshaking for their own purchasing system, not anything else. I have one device running 1.2.1 and one updated to 1.2.2. They are identical in their need for and response to this change in settings for Opera Mobile.
Edit, Edit: I've been looking at this issue again recently and found sites that actually test the browser and recommend changes in settings. It turns out that ONLY the TLS 1.2 should be enabled, not older protocols. One site also recommended disabling the SSL v.3, but my tests with two devices trying to access the same sites indicated that was a bad idea.
My most unexpected discovery was a post on an Opera board somewhere that suggested simply clearing cache (from the Menu: Settings>Privacy>Clear Cache) will often allow access to sites that initially give a security connection error. This actually seems to work in many cases. I have no idea why, but it prompted me to try unticking ALL cache settings except for "Empty on Exit" (last screenshot below). Don't forget to "Save" at the end of that section before exiting.

This is great, thank you!
Has anyone gotten this tweak to allow you to sign into Overdrive (online library) websites? New York Public Library's Overdrive page, nypl.overdrive.com still won't let me sign in, even with both TLS 1.1 and 1.2. For the record I think I'm still actually on firmware 1.1.0

jptiger said:
This is great, thank you!
Has anyone gotten this tweak to allow you to sign into Overdrive (online library) websites? New York Public Library's Overdrive page, nypl.overdrive.com still won't let me sign in, even with both TLS 1.1 and 1.2. For the record I think I'm still actually on firmware 1.1.0
Click to expand...
Click to collapse
That was the second thing I tried. No joy. Unfortunately there is zero information in a logcat of my unsuccessful session, almost as though the system was ignoring the browser activity entirely, so nothing to work with there.
Out on a limb here, but it could be a case of no contact with systems older than the oldest one to still support an Overdrive app (2.3, I think?). When I encounter a site that still won't connect with Opera Mobile, despite the addition of TLS 1.2, I think that's similar. Such an old browser (and OS) is seen as a security issue. Now exactly how the determination is made, that I don't know. It seems unlikely that it's something as simple as the User Agent string, as I have two NSTs, one running 1.2.2 and the older one with 1.2.1. I'm pretty sure I have not done anything with the UA string on the 1.2.2 device (it's a beast to type in) but I know I altered the other one to match the original stock browser on the device. I'll have to run down both values to see if there's something about the OS in there.
If the sites have a way of querying the system to recognize whether it is "safe" or not, then there's not much to be done. There was that one older version of UC Mini Browser which was able to negotiate a login at one time, but even if you could get into the library's Overdrive section, the closest you would come to a book is downloading the acsm file and then what? AFAIK there is no way to deal with it on the device itself. It would have to be processed on a PC and then transferred to the NST.
Login would allow you to checkout Kindle books and even confirm the download at the Amazon site (painful as that is), but I don't see how to make the epub thing work solely on the device any longer short of a new OS. That's way beyond my pay grade. I'm curious about it but recognize that it's not something I'm going to pick up at this stage of my life. Too bad the few projects directed at that weren't more modest in their goals. A change to just Gingerbread would have made a huge difference, although even with that, the handwriting is surely on the wall.

but even if you could get into the library's Overdrive section, the closest you would come to a book is downloading the acsm file and then what?
Click to expand...
Click to collapse
Open the file with Aldiko! I actually used to do this all the time, it was the main way I used to interact with Overdrive for years. Worked great... until I wasn't able to log into Overdrive sites and access my holds any more.
You might need a specific old version of Aldiko, I'd bet I found it on these forums somewhere. I'm writing this on my phone on a subway, otherwise I'd link here. Moot point atm anyway.

jptiger said:
Open the file with Aldiko! I actually used to do this all the time, it was the main way I used to interact with Overdrive for years. Worked great... until I wasn't able to log into Overdrive sites and access my holds any more.
You might need a specific old version of Aldiko, I'd bet I found it on these forums somewhere. I'm writing this on my phone on a subway, otherwise I'd link here. Moot point atm anyway.
Click to expand...
Click to collapse
There may yet be a magic version of Aldiko that can do this, but I think the operative word in your response might be "used" to interact with Overdrive.
I don't know why but I decided to look at this issue again and stumbled on @straygecko's post re: Overdrive and Aldiko here: https://forum.xda-developers.com/showpost.php?p=35917607&postcount=2
I scrounged around for a "2.0" version of Aldiko and came up with 2.00.081 (maybe close enough?). Anyway, it does install and the first few steps of the procedure @straygecko outlines actually work great, even the sign in with Adobe--which I found shocking. I was able to painfully add my local library's Overdrive URL to the "My Catalogs" section and actually "browse" to the URL, if you can call it that. If we think Opera Mobile is antique, think more along the lines of the stock NST browser. Mostly floating text appears here and there, lots of broken images, and Search does not seem to work. Oh, and scrolling up the page? LOL! If you can get lower on the page to something like "available now", the screen will not update. It may not be absolutely necessary but while I was chortling and grimacing I also tried the "sign in" option. In little tiny letters across the top of the screen comes the "oops! something went wrong" message, all too familiar.
I hope, I really do hope that there is another version of Aldiko 2.0 that would work. But the post by @straygecko was from 2012 and while at my age that seems not so long ago, in the world of Android, it might as well be 500 BCE.
For your entertainment, I attach the version of Aldiko I was able to scare up. YMMV.

Odd. I think you might be trying to make Aldiko do a different part than I was referring to. Here was my usual workflow after installing Aldiko and logging into my Adobe ID on it:
1 open opera mobile
2 navigate to my library's overdrive page
3 sign in (not currently working)
4 browse and check out an epub ebook
5 download the ascm file
6 when prompted about what to do with it open it aldiko
7 Aldiko then downloads the epub using your Adobe ID and shows it in your library until it expires
If those are the steps you're following, where do you hit the unreadable text? After the book downloads?

jptiger said:
Odd. I think you might be trying to make Aldiko do a different part than I was referring to. Here was my usual workflow after installing Aldiko and logging into my Adobe ID on it:
1 open opera mobile
2 navigate to my library's overdrive page
3 sign in (not currently working)
4 browse and check out an epub ebook
5 download the ascm file
6 when prompted about what to do with it open it aldiko
7 Aldiko then downloads the epub using your Adobe ID and shows it in your library until it expires
If those are the steps you're following, where do you hit the unreadable text? After the book downloads?
Click to expand...
Click to collapse
You're right, those were not my steps. On my local library Overdrive site it is not possible to check out an eBook without eventually signing in. Catch-22.

nmyshkin said:
It's time to show a little more love for arguably the best browser for the NST/G
I've been reading up on the whole TLS 1.2 thing and bemoaning the gradual eroding of the NST/G internet capabilities as various apps wink out of usefulness due to the recent change. I felt the same way about Opera Mobile 12.10, especially when I had finally figured out an app for Google News, only to find that many of the external links could not be opened, presumably due to this new security protocol.
Imagine my surprise today when I revisited the configuration screen for Opera Mobile and saw that even on this nearly prehistoric app there is an option for TLS 1.2!! Once I had selected that I could suddenly navigate to all kinds of sites that were previously snubbing me! Woo-hoo!
The procedure, in pictures, below. Love live Opera Mobile (at least until TLS 1.3).
Edit: I should mention that this has nothing to do with the recent NST/G update to 1.2.2. B&N only added TLS 1.2 handshaking for their own purchasing system, not anything else. I have one device running 1.2.1 and one updated to 1.2.2. They are identical in their need for and response to this change in settings for Opera Mobile.
Click to expand...
Click to collapse
Wow. I have tried every other browser. This is definitely the only one that works. Thanks so much for the info.

lz199366 said:
Could you share your Opera Mobile.apk? I can't get opera 12.1.0 install on my NST(firmware1.1.2).
Besides, which app did you use to take screenshot in Black&White color ? I tried screenshot ER before. It is good but producing shots in colors only.
Click to expand...
Click to collapse
Opera Mobile: https://ftp.opera.com/pub/opera/android/mobile/1210/
For screenshots, I made two apps. The original produces slightly gray b&w images. The second gives better quality color images. Here: https://forum.xda-developers.com/nook-touch/themes-apps/app-screenshot-t3648855. When I post images I always convert to greyscale anyway since that's what will be seen on the device.
That older firmware may be a problem. B&N did actually have reasons to update firmware now and then. If the Opera Mobile will not run you might try Opera Classic. Some people said it worked for them.

Some additional discoveries
Just a bump to bring this post back up again. I've done some additional tests with different settings lately and have improved the connection success rate quite a bit. Changes reflected now in the original post.

Since you're bumping the thread maybe you can help me with a problem? I think I've tried this APK on my last three Nooks (Glowlight Plus, NG3, and now Glowlight Plus 7.8) and every time I launch Opera Classic from my launcher I get a short splash screen that says "Opera Mobile" and then it immediately dies. Nothing shows in my "running process" screen either (so it's not just hidden in the background).
Any idea where to start looking as far as logs, etc. go? I've never really had much use for a browser on a Nook before, but with the 7.8" display my interest is somewhat piqued again...

spedinfargo said:
Since you're bumping the thread maybe you can help me with a problem? I think I've tried this APK on my last three Nooks (Glowlight Plus, NG3, and now Glowlight Plus 7.8) and every time I launch Opera Classic from my launcher I get a short splash screen that says "Opera Mobile" and then it immediately dies. Nothing shows in my "running process" screen either (so it's not just hidden in the background).
Any idea where to start looking as far as logs, etc. go? I've never really had much use for a browser on a Nook before, but with the 7.8" display my interest is somewhat piqued again...
Click to expand...
Click to collapse
Mmm.....first, this is Opera Mobile 12.1, not Opera Classic, although I don't think that is the issue. Not sure about the Glowlight Plus, but I think the others run at least KitKat? My first suspicion was that Opera Mobile (or Opera Classic) might be too old for those devices, but I just tried installing it on my SIM-less KitKat "phone" and it did just fine.
So maybe screen density? It's hard to know. Like @Renate NST says, a logcat might reveal the cause of the crash--or not. Meanwhile I should think that with a KitKat device there must be a number of more modern browsers that would work OK. I recommend Via Browser. Slick and simple, small footprint. Requires Android 2.3 and up (too bad the NST just missed it...). I run it on my Oreo 8.1 tablet and love it.

nmyshkin said:
Mmm.....first, this is Opera Mobile 12.1, not Opera Classic, although I don't think that is the issue. Not sure about the Glowlight Plus, but I think the others run at least KitKat? My first suspicion was that Opera Mobile (or Opera Classic) might be too old for those devices, but I just tried installing it on my SIM-less KitKat "phone" and it did just fine.
So maybe screen density? It's hard to know. Like @Renate NST says, a logcat might reveal the cause of the crash--or not. Meanwhile I should think that with a KitKat device there must be a number of more modern browsers that would work OK. I recommend Via Browser. Slick and simple, small footprint. Requires Android 2.3 and up (too bad the NST just missed it...). I run it on my Oreo 8.1 tablet and love it.
Click to expand...
Click to collapse
Ah yes, I forgot that the original NGP was where the jump to KitKat occurred which opened up more options for apps. I'm going to give Via a try - thanks for the quick response!

First problem:
Our (at least my) /system/lib/libgui.so does not have
status_t GraphicBuffer::lock(GGLSurface* sur, uint32_t usage)
The Opera libOS15.so requires it
Eclair had this function, I don't think KitKat has it.
I think this Opera "Opera_Mobile_12_1_Generic_Opera_Armv5v7.apk" was designed for Eclair and uses stuff no longer in KitKat.
You need to find a different APK.

@myshkin Once again, you've answered one of my questions before I asked it! I am going to use an NST to interact with my online scheduler for a sweet e-ink, easy on the eyes, scheduling unit.

First I want to thank for well written guide how to set things up to make any browser (in this case obviously Opera) working on NST. I read several threads about browsers and wondered how those could be solved. It seems to me that some of those problems could be solved using web grabber or offline browser or some of those plugins that redirects to cached version of the web page on Wayback machine (Brave browser is gone incorporate that option so I have been told). Naturally that might work for reading cached content on NST inside your browser if it supports page rendering and so. Still for pages that need user/reader interaction that won't solve anything. Would application like Gapps browser resolve at least some of the issues you experience? It should run on Eclair but I am not sure will it run on NST. That need to be tested.

SJT75 said:
First I want to thank for well written guide how to set things up to make any browser (in this case obviously Opera) working on NST. I read several threads about browsers and wondered how those could be solved. It seems to me that some of those problems could be solved using web grabber or offline browser or some of those plugins that redirects to cached version of the web page on Wayback machine (Brave browser is gone incorporate that option so I have been told). Naturally that might work for reading cached content on NST inside your browser if it supports page rendering and so. Still for pages that need user/reader interaction that won't solve anything. Would application like Gapps browser resolve at least some of the issues you experience? It should run on Eclair but I am not sure will it run on NST. That need to be tested.
Click to expand...
Click to collapse
I had never heard of Gapps browser but I can tell you now that it does not work properly on the NST. It never gets past a partial, immobile screen of Google News. None of the other options do anything at all.
While I still prefer Opera Mobile for general browsing and value its ability to open local HTML files (something I have exploited in a number of my news apps), Opera Mini 7.6.4 also functions on the NST and can skirt around some of the SSL issues because the pages are initially picked up by Opera's up-to-date servers, rendered, and then passed on to the user. However, sites with complex constructions and modern WebView requirements will not display properly, if at all. Opera Mini also has a "picker" that will allow you to open media files (like videos) in an external player. This is something Opera Mobile will not do. It just refuses to deal with them at all.
On the whole, the browser issue is the proverbial straw for the camel's back when it comes to older Android OS. I have seen this working with KitKat ROMs where already many sites cannot be accessed because of the outdated WebView. Lollipop, which is the first OS version with a WebView that can be updated, is a little better. But custom ROMs (or ROMs like on the NST) that are not properly updated for SSL are never going to be able to hold on forever in this regard.

Thanks for thorough reply. I fear that it is not only updates of the software that is hampering factor but very nature of e-ink devices that hold us back. Even Kindles from Amazon have the issues in that regard and it is certainly not from lack of funding that firm can provide to solve the problem. That is why I mentioned web grabber approach. As last resort someone might try to print some web page as PDF for later reading but that would not solve problems like logging in some web services etc. I even considered text based browsers as alternative. My friend who is proficient in programming, web administration and computer related stuff said me the same thing as you did that Opera is by far best browser for mobile device.

[SOLVED?] The mysteries of the "now reading" button

I must have a unique way of using my devices because I've never seen this issue reported on the forum.
Firstly, I just want to say that lastreadingpoint.db seems to be something of a garbage bin. I'm working with one of my older devices right now (formerly my principal reader) and the db is filled with books that were deleted long ago. Now, perhaps, cleanup of this file is supposed to happen when books are removed via UMS since that's the only provision B&N made for removing side-loaded content, but I doubt it. Since I just use a file manager, I may be frustrating some grand design that would keep the db file tidy. NOT.
But I digress. My real beef is the unpredictability of the button. When I select a new book from the library and move along a few pages to the first chapter, I often return to the home page to deal with some other things and then set the device aside until I'm ready to start my new book. But when I do return and tap that button, I generally get the last book I just finished (at the last page....). If I have deleted that book already then I'll get some other book, maybe an anthology I frequent, wherever I left off.
Inspection of lastreadingpoint.db shows no indication that I ever selected a new book.
I have struggled with this for a long time and realize that without knowing exactly when and under what circumstances the db would actually be updated, this is really difficult to run down. I just tried another experiment and put the device to sleep manually after starting a new book (book still displayed). Then I woke it up and returned to the home screen (i.e., my launcher, not the B&N Home). The "now reading" button worked correctly! And repeatedly.
BUT...A look at lastreadingpoint.db still did not show that the new book had been opened! This helps explain why my overtures with sqlite were not having much effect.
It's a mystery, wrapped in an enigma, enclosed in a B&N box.
I just want the #$%&*% button to do what you would expect it to do without a lot of nonsense. It's easier to get it to consistently open a current Kindle book then to open an epub in the stock reader.
Why?
Edit: The next day: I accessed the book one more time this morning without any problem and copied out the database again. This time it finally showed an entry for the book with the correct access time.
Edit: 9-12-22 Nothing seems to work consistently except for one change. I have installed on my devices a little app called "NookReader". It's buried deep in the old posts of the forum and its purpose is to allow epubs to be opened via a file manager (which I never do). In effect it creates a "listener" which the stock system lacks.
Well, it seems the stock system doesn't like eavesdropping. When I uninstalled the app from the device I had been experimenting with the effect was immediate and I was able to move from selection to selection, each time returning to the most recent book correctly using the "now reading" button. Another device required an uninstall as well as a reboot in order to start behaving properly.
Moral: if you're not using it, get rid of it!

nmyshkin said:
I have struggled with this for a long time and realize that without knowing exactly when and under what circumstances the db would actually be updated, this is really difficult to run down. I just tried another experiment and put the device to sleep manually after starting a new book (book still displayed). Then I woke it up and returned to the home screen (i.e., my launcher, not the B&N Home). The "now reading" button worked correctly! And repeatedly.
BUT...A look at lastreadingpoint.db still did not show that the new book had been opened! This helps explain why my overtures with sqlite were not having much effect.
It's a mystery, wrapped in an enigma, enclosed in a B&N box.
Click to expand...
Click to collapse
@nmyshkin ... even i've struggled with something like this ... inconsistencies of the last reading point actions ...
nmyshkin said:
Edit: 9-12-22 Nothing seems to work consistently except for one change. I have installed on my devices a little app called "NookReader". It's buried deep in the old posts of the forum and its purpose is to allow epubs to be opened via a file manager (which I never do). In effect it creates a "listener" which the stock system lacks.
Click to expand...
Click to collapse
are you referring to the app that goes by 'dev.nookreader.apk' ? ... for now i've just renamed it to 'dev.nookreader.apk.bkp' so its as good as removed ...
some database problems i think i can report, one that i've annoyingly encountered, in this I've sometimes found the order of the books in the default library aren't displayed as they should have ... Iam referring to the 'Most Recent' sorting option where the last opened/accessed book should ideally show up at the top most ... BUT SADLY IT DOESN'T !!! ...
Most annoying is when i search a book open and read it and expect it to show up on the top or at least in the first few pages of the library ... but they don't ... search is the only option to reopen such a book ...
Aren't the books that are opened using the 'Search' option of the library not supposed to show high up the library ?
I WOULD REALLY LIKE TO GET THIS ANNOYANCE RID OF ... i would love to find all the last accessed books in the topmost sorting order as its supposed to work ...
I don't even know what database records the last accessed book information ... any and all help appreciated to identify and fix this annoyance.
PS : Are "New"' books(Lend Me) installed from the B&N store supposed to show up at the topmost ?

Update : strangely the searched book shows up in the B&N Home under 'READING Now' section but its not showing in the Library as the topmost book in it ... another inconsistent DB recording ???

aiamuzz said:
Update : strangely the searched book shows up in the B&N Home under 'READING Now' section but its not showing in the Library as the topmost book in it ... another inconsistent DB recording ???
Click to expand...
Click to collapse
OK, well, I can't say that I know a lot more now than when I started this thread.
What I can say is that the device seems to work with a copy of the database in RAM or else keeps variables in RAM that are not written to the database until much, much later (like during or after a nap).
I began to think about how I use the device vs. how B&N intended it to be used so I made a few tests going from the B&N Home to the Library, to a book. Then, there is really only one way to get out of the book and that is through the QuickNav buttons. I thought that maybe the trigger to the database update was somewhere in there, but I saw the same inconsistent results and delayed updating of the file as with my own sequence.
This is why I eventually abandoned the database as a source of info for my SetCover app and started relying (at least partly) on my own data. All I can say for "sure" at this point is that a good nap on the open book seems to aid in the correct information making its way into the database. Not very technical, I know.
If you are getting really spurious behavior from your lastreadingpoint.db or you find that it is full of deadwood, you can clean out the entire thing as here. Of course you will lose absolutely everything in the database if you do that, so it's a "last gasp" scenario.
For me, things seem to have calmed down if I just leave an epub open in the stock reader for awhile. And after all, what's the rush to get back to the home screen? (in general). That's not how the reader was probably meant to be used.

aiamuzz said:
Update : strangely the searched book shows up in the B&N Home under 'READING Now' section but its not showing in the Library as the topmost book in it ... another inconsistent DB recording ???
Click to expand...
Click to collapse
Can you run this test ?
1. Open stock library.
2. Search for some book that is buried in the last pages of the Library.
3. Open that book from the search results.
4. Flip a few pages to emulate that you've read that book.
Ideally that book should be the Last Read (Reading Now) ... WHICH INDEED DOES WORK SO !!!
Having been a recent book that one has read ...
The Library app should also show that book on the very first page as its the most recent one ... BUT IT DOES NOT SHOW SO IN THE LIBRARY !!!
I would really like the searched and opened books to move to the front pages of the Library App and stay there and get moved down as and when other books are opened ... at worst it should be easily locatable in the first few pages of the Library App ... the 'recent' book sorting option in the Library and the place where this info is stored may have to be trouble shot ...

aiamuzz said:
Can you run this test ?
1. Open stock library.
2. Search for some book that is buried in the last pages of the Library.
3. Open that book from the search results.
4. Flip a few pages to emulate that you've read that book.
Ideally that book should be the Last Read (Reading Now) ... WHICH INDEED DOES WORK SO !!!
Click to expand...
Click to collapse
Well, there you are. I've never used the "search" function on the NST for anything! But I did, just to humor you, and I see that it actually turns up a "hit".
I use the Library almost exclusively in shelf format. What I personally would like is for the @%W$#% Library to remember that. Of course, it will not, because then I would not see all the nifty new books I just purchased (NOT) from B&N as they are delivered.
Any "adjustments" to the Library behavior are beyond my pay grade and you won't get you-know-who interested in that either, as she has her own Library app. I've looked at a lot of Library alternatives. There were many promising looking ones in the early days but all seem to have been abandoned at some incomplete point by their developers (except for the one mentioned above).
I just live with it. I don't have hundreds of books on my device. When I finish a book I actually delete it (gasp!) [except for something like the Bible].
But it would be nice to understand the rules or thinking behind the "reading now" business. However, since the database doesn't seem to accept input (although you can read from it), it doesn't matter much I guess.