Related
Search returned nothing. Thanks.
Picked this up from another thread.
It is ThinkFree from an Android netbook - Archos:
Works just fine. Takes a little bit to convert the pdf - but, it doesn't need internet communication to do so like many of the other apps.
Wish we could get a 1.6 version of PDF viewer!
I got it from this thread:
Archos 5 Internet Tablet Apps & Media
Download the app folder and install "tfmobile-archos_Archos5-release.apk"
There's one that comes with the newest CyamgenMod
YoungJ030 said:
There's one that comes with the newest CyamgenMod
Click to expand...
Click to collapse
There isn't a pdf viewer in the new cyanogen roms. And the old viewer does not work with the new roms either.
Consider one of these
http://www.cyrket.com/package/com.cerience.reader.app
http://www.cyrket.com/package/com.westtek.jetcetpdf
http://www.cyrket.com/package/com.dataviz.docstogo
I don't know about the ones posted above... But, I have downloaded and tried out a couple of pdf apps that required the app to communicate/transfer data to the internet to convert the pdf to read on Android.
I can tell you for sure that ThinkFree works on 1.6 and requires no internet connection to convert data/read pdf's.
frankencat said:
Search returned nothing. Thanks.
Click to expand...
Click to collapse
Android PDF viewer(beta/demo) has worked ok for me, on CM 4.1.999.
Its free on the market and does not use the internet to view.
I wanted to use the Kindle app on my Touch (heresy, I know), and it works well.... except for a single issue.
I can't search a book. Using the search utility on the Kindle app brings up nothing. No problems searching in Aldiko or the B&N native reader. Just wondering if I'm missing something blatantly obvious or if it's hosed to begin with.
I can confirm the issue, searching in a book doesn't return any results. :-(
cceerrtt:
I was sooooooooooooo hoping it was just me. Without the ability to search for passages, I can't use it.
No worries. Quite a few other readers.
Thanks again for the reply.
Here's a question for everyone, too: is it possible to run the native Kindle Fire application on the Nook?
There are a lot of free titles available on Kindle that are not available on Nook. Heresy is appreciated when it is practical
I am also having the search problem. I tried updating the Kindle app through Google Market, but it won't update. The latest version in the market is 3.3.2. When I uninstall the Kindle app and reinstall through the market, it seems to install version 3.2.0.35. Has anyone been able to install 3.3.2?
So apparently the latest version 3.3+ you need to have android 2.2 or higher. Since the nook is only 2.1 the latest version you can install is 3.2
I have not tried searching but it seems that scrolling through larger titles (newspapers etc) with articles does not work. It is hard to say exactly how it should work but turning pages using a right to left swipe works perfectly fine. Scrolling through a vertical list of articles using a up to down swipe does not work at all. This makes newpapers really difficult to read on the nook since you have to many skip through each article.
Dictionaries seem to work the same as anywhere else which for foreign language reading is fantastic
Is there any way to get the hardware pageturn buttons to work in kindle.apk?
Tom Fagerland said:
Is there any way to get the hardware pageturn buttons to work in kindle.apk?
Click to expand...
Click to collapse
Similar questions came up recently in two other threads. Paraphrased answers from these threads: You could either modify the key mappings statically in /system/usr/keylayout/TWL4030_Keypad.kl and reboot. Or, for dynamic app-dependent button mappings, you could attempt porting Buttonmap over from the PRS-T1.
There are any number of things that annoy me about the stock B&N reader.
I've been writing my own reader app from the ground up.
It's missing a lot of features, but it's still become my standard reader.
I have a lot of technical references in PDF.
At least my reader will allow me to see them in landscape mode fit to width.
The app has adjustable overscan to get rid of the paper margins.
For EPUBs, there are 17 font sizes, 30 margin sizes, 21 line spacings.
EPUBs or PDFs can be viewed in either orientation.
The app is eInk smart but runs on standard cell phones too.
I assume that you plan on making this app available to the community at some point. When you are ready for other users to test, I would be glad to volunteer.
Yes, as soon as I get rid of the worst bugs, I'll let this loose.
It doesn't have text search or word lookup or annotations or bookmarks.
From MY perspective, bookmarks would be priority #1, followed by dictionary look up. I have never used annotations or word search, though I am sure others have.
Just my $0.02. Other's opinions will vary.
From MY perspective, dictionary look up would be priority #1, and never bookmarks, as I am Russian speaking person. I have never used annotations or word search.
Just my $0.02. Good luck in your efforts.
I'm still working on this.
One of the things I found most lacking was good navigation on large PDFs.
It can get a bit hairy dealing with the table of contents on some PDFs.
Sometimes a page number is more specific than a TOC entry and sometimes it's the other way around.
Will you be supporting mobi files as well ?
It seems it's hard to find a nice reader that support both epub and mobi ...
No, it will not read MOBI.
MOBI is a really stupid format based on database files for Palm OS.
EPUB is a halfway reasonable format.
HTML based reflowable text and a table of contents.
What more do you need?
Of course, all the manufacturers (like Kindle) are pushing for whiz-bang HTML5 formats.
Renate NST said:
No, it will not read MOBI.
MOBI is a really stupid format based on database files for Palm OS.
Click to expand...
Click to collapse
1) I really liked Palm
just kidding, nostalgia kicked in
2) I already have some books in MOBI format, that's why I'm asking.
Yes, I know I can convert them to EPUB ...
Thanks!
Finally ready for a super pre-alpha preview.
Very short user manual:
Hit the right screen edge or PAGEDOWN for forward a whole page
Hit the left screen edge or PAGEUP for backward a whole page
Hit the top screen edge for the navigation menu
Hit the bottom screen edge for table of contents view
Hit the middle of the screen when viewing PDFs to go down a chunk of one page
(These 4 edges are actually the edges of the page view.
When the TOC is showing, the left edge will be somewhere in the middle of the screen.)
There are separate config dialogs for EPUB and PDF.
In TOC view, the +/- are indicators and not controls.
The app tries to keep everything as compact as possible.
TOC scrolls with a drag, selects with a push on a chapter title, dismisses with a bottom push in the page side.
You can call up navigate, page forwards and backwards while the TOC is showing.
A single empty square and the title indicates that the PDF has no TOC.
The eInk special handling only works with 1.2.1 software.
If you are using nofresh/fast refresh/whatever, then no guarantee nor interest in what it will do.
It may be self-delusion, but it seems to me that the text is clearer than the stock reader?
You can just install this as a regular app.
You can set it as default for EPUB or PDF separately.
Unless you're me, you shouldn't get rid of the stock reader just yet. :cyclops:
Hmm, I'm not sure if it will handle Last Reading Point correctly if you are using the stock library.
Oh! It will list all the fonts on your system, but it won't handle the fonts that the underlying library files don't like.
Renate NST said:
Unless you're me, you shouldn't get rid of the stock reader just yet. :cyclops:
.
Click to expand...
Click to collapse
First problem: On my nook it didn't show up in adw so I can't run it
richardcoop said:
On my nook it didn't show up in adw...
Click to expand...
Click to collapse
Well, it wouldn't, would it?
The stock reader doesn't show up there either.
For an application to show up in a launcher its AndroidManifest.xml would have to have:
Code:
<category android:name="android.intent.category.LAUNCHER" />
File viewers normally don't have that, they are invoked by other intents.
Use your "Last Read" icon, a library application or a file manager to open an EPUB or a PDF.
Renate NST said:
Finally ready for a super pre-alpha preview.
I
It may be self-delusion, but it seems to me that the text is clearer than the stock reader?
You can just install this as a regular app.
You can set it as default for EPUB or PDF separately.
Hmm, I'm not sure if it will handle Last Reading Point correctly if you are using the stock library.
.
Click to expand...
Click to collapse
Think the text is clearer!
Doesn't remember the Last Reading Point for me but not using the stock library.
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Also, looses my place when the screen saver kicks in.
Thanks for the good work Renate. I think the display is better than other epub/pdf readers and maybe stock reader too. As most of my reading is done with my Glow version in bed, a "Night Mode" switch for white font on black background would be great if possible?
Thanks again.
richardcoop said:
Also, loses my place when the screen saver kicks in.
Click to expand...
Click to collapse
Yes, the integration between a reader app and a library app is close.
Tracking of last point is usually done in the library app.
I was planning on adding a single LRP directly in the reader for files that aren't tracked in the library.
Is it possible to run this on an Android 2.3.4 installation or its code assumes a Nook?
The reason I ask, is because I have a Kobo Glo with android installed, and I would like to check it there, if it is e-Ink optimized.
The problem with supporting eInk is that the interface classes in Java are all different.
Even in the Nook 1.1, 1.1.5. 1.3 are incompatible with 1.2.1
(Notice that the latest 1.3 on the white Nook uses an older scheme than the 1.2.1)
They all use android.hardware.EpdController in /system/framework/framework.jar
I have no idea what the Kobo is using.
I can guarantee that the application posted above will do no special eInk handling as it checks the system build fingerprint for compatibility.
If you are using Nook 1.1.5 or 1.3 it will also not do any special eInk handling.
The application should work on any device if you copy over these two library files:
/system/lib/libpdfhost.so
/system/lib/libbndeviceinfo.so
I have this app running on my (old) Kyocera Rise (cell phone).
It should run (without any special eInk handling) on your Kobo.
Anything further would require research and programming.
Renate NST said:
Hmm, I'm not sure if it will handle Last Reading Point correctly if you are using the stock library.
Click to expand...
Click to collapse
It does not handle Last Reading Point correctly when using the stock library.
Great work! I used this for all of 10 minutes and the potential is evident. With some more of your excellent development work you will have a real winner on your hands.
Question, as this obviously will not read books with B&N DRM, is there some way to make this reader the default when using your library app and allow the stock reader to be the default when using the stock library? Perhaps a setting in your library app to use either the "device default" (stock or other) reader or Temblast Reader specifically when a book is selected.
With regard to the text being clearer than the stock reader, I don't notice a difference. However, I am using the Tweaked Modded ROM, which states:
"Forced all rendering to be done on the GPU." I noticed the text was darker using this ROM when I first installed it. Perhaps your reader essentially does the same thing? This might account for the those who notice the text being clearer when using your reader.
David0226 said:
"Forced all rendering to be done on the GPU."
Click to expand...
Click to collapse
Interesting, that's not what I explicitly did, but maybe it's effectively what I did.
Font display doesn't seem as good as stock reader upon closer inspection.
For PDF reader I still use two particular versions of Repligo and ezPDF-Reader both: fast, full of options and pinch in-out for zoom on txt/image based files and more, opening all pdfs.
The epub reader is suffering on some files with wrapping longer lines so I get remainder lines with two or three words, unless fonts are much smaller even with little margins so back to AlReader and FBReader I'm afraid.
Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
scotte9999 said:
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
Click to expand...
Click to collapse
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
So we move on.
Click to expand...
Click to collapse
Indeed. I spent some time yesterday exploring web-based widgets, thinking we could just point the browser at a URL, but most widgets use HTTPS and Javascript, neither of which are the strong suit of the NST, even with Opera Classic instead of the native browser.
Did this work?
disTrck33 said:
Did this work?
Click to expand...
Click to collapse
Depends on what "this" is.
I eventually wrote my own weather widget app for the NST/G: https://forum.xda-developers.com/nook-touch/themes-apps/app-nst-weather-widget-t3946270
This works.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
Click to expand...
Click to collapse
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
SJT75 said:
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
Click to expand...
Click to collapse
Didn't remember the US restriction, but all of the potential apps I looked at back then looked terrible on the NST or required network location. That is why (shameless promotion...) I eventually worked up my own Weather widget/app just for the NST. It lacks many bells and whistles but will work for any locale that OWM has stations. And, if I say so myself, looks pretty good on the NST.
nmyshkin said:
Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Click to expand...
Click to collapse
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
mycodefab said:
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
Click to expand...
Click to collapse
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
nmyshkin said:
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
Click to expand...
Click to collapse
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
mycodefab said:
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
Click to expand...
Click to collapse
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
nmyshkin said:
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
Click to expand...
Click to collapse
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
mycodefab said:
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
Click to expand...
Click to collapse
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
nmyshkin said:
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
Click to expand...
Click to collapse
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
mycodefab said:
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
Click to expand...
Click to collapse
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
nmyshkin said:
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, thanks. In case you have DarkSky API key (the app know it as Forecase.IO, it was an old name of the DarkSky API) please use it with the version 1.7.4, the app version support the weather source. Once purchased by Apple, DarkSky (Forecast.IO) no longer give out free keys. But any old keys continue to work atm, as far as I know.
Building a new version with updated support for weather sources will take some time. As usual, most problems in the case are not related with app itself, but with other libraries. For example, a library that provided map does not support Android 2.1 anymore, so probably I will need to completely remove map from the app. Google libraries related with analytics and ads - also does not support old android versions anymore. I will work on it this weekend.
nmyshkin said:
Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
Click to expand...
Click to collapse
You need GPS.
nmyshkin said:
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
The version support 2 weather sources - OWM (open weather map) and Norwegian MET.NO.
Limitations:
1. Removed weather map and adding locations via map. I cant find any android weather libraries that support Android 2.1 devices.
2. Removed ads for same reason.
3. Weather icons limited to the small set of icons inside the app + 1 custom icon set.
As for custom icon set, its mostly same as for latest versions of WeatherACE, just a bit different directory for images. Directory is "Android/data/mycodefab.aleph.weather/files/custom/icons/". It use same format as for the latest versions. So, for example, for "clear sky in day" condition it will use "d_100.png" file, "clear sky in night" will look for "n_100.png" file, "overcast" will use "d_104.png", etc.
In case the version of the appt will start, but not show the weather after weather info update, please get to Menu->Settings->Advanced->Weather Sources. Here you could see Active weather sources on the top. Tap on it. Uncheck OpenWeatherMap and Norwegian MET, tap OK. Enter Active weather sources again. Set check OpenWeatherMap and Norwegian MET, tap OK. It will recheck availability of sources for existing locations and will update the weather info.
mycodefab said:
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
Click to expand...
Click to collapse
I tried the app on both devices (with and without Network Location). Unfortunately it does not want to run
There is immediate funny business as the package shows in the file manager as a generic "package" icon rather than the app icon. Also, the package name (and generic package icon) are displayed in the launcher rather than the app icon and name.
I've attached a section of a logcat for trying to open the app. I don't know whether it has information that is helpful.
It may or may not have any bearing on what you have done, but as you're already going way beyond any expectations, I would suggest that leaving the app alone except for fixing the weather sources would be more than enough. I can understand your desire to have things "right". I have that same problem , and I do appreciate it, but maybe without so many changes there would be a better chance of the app still working, which is what it did even now, except for the access to weather sources. Of course, it's probably not that simple.
Thanks for your efforts.
Two apps that I use on my NST (glowlight) are AlReader and RelaunchX, for which there are still relatively recent apk's to be found. I haven't seen them mentioned here a lot, so here's the link to the latest Alreader that still works on Android 2.1 (hard to find if you don't speak Russian):
http://4pda.ru/pages/go/?u=http://a...340035&usg=ALkJrhhH03h-JtOUNtSq7Dy0YRE5zt-deQ
And here's ReLaunchX, a fork of ReLaunch:
https://f-droid.org/en/packages/com.gacode.relaunchx/
I just fixed my Nook after it stopped working with the 1.2.2 update that I hadn't installed yet, so I'm updating it with some recent apps that still work on it.
Sent from my BLA-L09 using Tapatalk
STEELBAS said:
Two apps that I use on my NST (glowlight) are AlReader and RelaunchX, for which there are still relatively recent apk's to be found. I haven't seen them mentioned here a lot, so here's the link to the latest Alreader that still works on Android 2.1 (hard to find if you don't speak Russian):
http://4pda.ru/pages/go/?u=http://a...340035&usg=ALkJrhhH03h-JtOUNtSq7Dy0YRE5zt-deQ
And here's ReLaunchX, a fork of ReLaunch:
https://f-droid.org/en/packages/com.gacode.relaunchx/
I just fixed my Nook after it stopped working with the 1.2.2 update that I hadn't installed yet, so I'm updating it with some recent apps that still work on it.
Sent from my BLA-L09 using Tapatalk
Click to expand...
Click to collapse
There is also an English version of the Alreader website with app downloads: http://www.alreader.com/?lang=en
nmyshkin said:
There is also an English version of the Alreader website with app downloads: http://www.alreader.com/?lang=en
Click to expand...
Click to collapse
That's true, but despite what it says there, the version up for download there is not actually compatible with Android 2.1. I had to use Google translate on their support forum to find the above version.
Sent from my BLA-L09 using Tapatalk
STEELBAS said:
That's true, but despite what it says there, the version up for download there is not actually compatible with Android 2.1. I had to use Google translate on their support forum to find the above version.
Click to expand...
Click to collapse
Yes, you are correct. I've been trying out v. 1.7.7, which is that same as in your link.
I like it a lot except for two minor issues: the TTS does not work (a very minor issue) on the NST, although if you install the app on another device with native audio support it does work properly, and (more significantly for me), there is no way to address the Library directly. Unlike the author of FBReader, this author has made all of the various activities private so there is no way of accessing them from outside the app. I've been looking at the Android Manifest in the decompiled app, trying to decide if this can be "fixed". I've seen references to dealing with this issue before but now when I want then I can't locate them
nmyshkin said:
Yes, you are correct. I've been trying out v. 1.7.7, which is that same as in your link.
I like it a lot except for two minor issues: the TTS does not work (a very minor issue) on the NST, although if you install the app on another device with native audio support it does work properly, and (more significantly for me), there is no way to address the Library directly. Unlike the author of FBReader, this author has made all of the various activities private so there is no way of accessing them from outside the app. I've been looking at the Android Manifest in the decompiled app, trying to decide if this can be "fixed". I've seen references to dealing with this issue before but now when I want then I can't locate them
Click to expand...
Click to collapse
Ah, yes... Well, I would never use the NST for TTS, so that's no problem for me. As for the library... I take it you mean in the underlying code? Out of interest: what would you use it for? I basically use ReLaunchX to locate the book I want (in my own directory-based library) and open it with Alreader.
The one thing I wish Alreader would provide, myself, is a cover image of the current book to use as a screensaver on the Nook. But that's a minor issue.
STEELBAS said:
Ah, yes... Well, I would never use the NST for TTS, so that's no problem for me. As for the library... I take it you mean in the underlying code? Out of interest: what would you use it for? I basically use ReLaunchX to locate the book I want (in my own directory-based library) and open it with Alreader.
Click to expand...
Click to collapse
I have to confess that I hate Relaunch. I use a more traditional Android structure, including ES File Explorer, but that's not a nice way to browse for books. On two devices I have the B&N system and on one for experimentation I have removed all that and am trying out different readers. I miss the Library.
The one thing I wish Alreader would provide, myself, is a cover image of the current book to use as a screensaver on the Nook. But that's a minor issue.
Click to expand...
Click to collapse
Ah, but it does! Take a look in /media/screensavers and you will discover that it has created a new folder and there is a cover image there for the book you are currently reading. All you need to do is select that folder from the NST Settings app.
nmyshkin said:
I have to confess that I hate Relaunch. I use a more traditional Android structure, including ES File Explorer, but that's not a nice way to browse for books. On two devices I have the B&N system and on one for experimentation I have removed all that and am trying out different readers. I miss the Library.
Ah, but it does! Take a look in /media/screensavers and you will discover that it has created a new folder and there is a cover image there for the book you are currently reading. All you need to do is select that folder from the NST Settings app.
Click to expand...
Click to collapse
Aaaaah. Here I was looking all over for that folder, but for the place where you'd expect it. Well. Great, then.
I never really used the B&N Library app in the first place, I always immediately rooted my Nook and browsed for books in the directory structure, so that helps... Also my meta-data is always a mess so using a real library app wouldn't really work well for me, anyway.
STEELBAS said:
Two apps that I use on my NST (glowlight) are AlReader and RelaunchX.
Click to expand...
Click to collapse
You probably have more experience with AlReader than I do so I thought I'd pose a question which I have not been able to answer.
Is there a way to center the page number in the status bar? I don't have any of the other stuff showing in the status bar but I do want to see the page number, even in full screen. What I don't like is to see it floating at some small indentation from the left margin. You can center the title/author in the Header (which I do not have visible in full screen), but why not the page number? I think the answer is perhaps that the developer wanted to cram in all the other possibilities in the status bar and so each has a certain space allotted to it. I hope not.
I've pored through the settings xml file for AlReader but I can't make sense of much of it. Too many obscure abbreviations. I can't even find the line for centering the title/author in the Header.
Any ideas?
Edit: I made a tiny bit of headway, identifying variables in the xml file that control some aspects of the header and footer. However, as sometimes happens with these files, when you make a change and save the file, the values have reverted back if you return for another look. I'm assuming that the master data must be held in a database so I'll look at that tomorrow.
Edit-Edit: Nope, nope and nope. The databases are all about books. So the values are hidden in the app itself (library files or jars perhaps, who knows?). I spent way too much time squinting at the smali files from the decompiled app but it's just all so much mush to me. Not even a hint that resembles English as to how items are positioned. It's a pity that one of the choices in the Header was not "page". If that were true I'd switch the Header with the Status bar and the problem would be solved. The "page number/chapter" I find useless. Oh well....nothing is perfect.
External library app
I have a ton of bookmarks for NST/G stuff that I was reorganizing this morning and in the process came across this app: https://forum.xda-developers.com/nook-touch/themes-apps/library-app-t2823169
I haven't put it through the wringer yet, so to speak, but it looks reasonably good and books open in whatever the default reader is. If it's reliably functional it may serve as a general library app for whatever reader one chooses. Perhaps worth a look.
I'm trying to install v1.77 on NSTG 1.2.2 but I got error: Parse Error
try the
mrhamed said:
I'm trying to install v1.77 on NSTG 1.2.2 but I got error: Parse Error
Click to expand...
Click to collapse
Try the attached. It works for me.