Any working Reddit apps? Diode, RIF? Not working - Nook Touch Themes and Apps

Hey all, love using my nst in 2020 after a few months of using it. Running stock rooted
One thing I've been trying to get working on here is a functioning reddit app.
I've tried Diode and RedditIsFun. For some reason Diode doesnt even launch correctly even when I try to launch the main activity from adb shell. RIF launches but it doesnt fetch any posts or sub info. I've tried a few Diode versions, all of them yield the same result. RIF version 1.3.2. I'm also using nmyshkin's new cacerts.bks from thread. Still nothing from RIF.
Has anyone had any success with this? Thanks

KyleSaki714 said:
Hey all, love using my nst in 2020 after a few months of using it. Running stock rooted
One thing I've been trying to get working on here is a functioning reddit app.
I've tried Diode and RedditIsFun. For some reason Diode doesnt even launch correctly even when I try to launch the main activity from adb shell. RIF launches but it doesnt fetch any posts or sub info. I've tried a few Diode versions, all of them yield the same result. RIF version 1.3.2. I'm also using nmyshkin's new cacerts.bks from thread. Still nothing from RIF.
Has anyone had any success with this? Thanks
Click to expand...
Click to collapse
A logcat might reveal something. Or not. If it's a certificate issue it should show up. Remember, that cacerts file is still very old. It would not include Cloudflare, for example, which is increasingly used. I've had logcat actually specify a certificate before, but I think that was just dumb luck.
Edit: this is from a Reddit post regarding old versions: "You should be aware versions older than this are unlikely to even work anymore. There have been numerous changes to the reddit API since then, and you definitely won't be able to log into it because OAuth is now required and the old version did not support it."

You can try https://old.reddit.com/.compact from opera mobile. I find it decent.

I have posted before link to a page with few assorted links for older devices etc. among them was https://teddit.net/ which might me what you are looking for. Not an app but as long Opera on NST is able to hold on its ground should work I guess.

Related

Official Google Nav for 1.6 and above in Market

http://www.engadget.com/2009/11/23/google-maps-navigation-officially-comes-to-android-1-6/
When trying to download onto my phone from the Market, I get an error message 'Package file was not signed correctly.'
I'm running Cyanogen 4.2.5 on my Rogers Magic 32A.
Doesn't work for me in denmark
I think this is only US.
It's been released for the Market on all devices, but I think it has something to do with our devices using test-keys and not release-keys...
Thoughts?
Same problem in Belgium with 32A using CyanogenMod 4.2.5 with Kernel 2.6.29bfs.
Very sad
working fantastic on my MT3G running Dwang 1.13. Didn't get an 'update available' notification, but installing it from the market worked flawlessly. I gotta say, navigation with google layers is freakin' awesome
cursordroid said:
When trying to download onto my phone from the Market, I get an error message 'Package file was not signed correctly.'
I'm running Cyanogen 4.2.5 on my Rogers Magic 32A.
Click to expand...
Click to collapse
I have the same phone and ROM version and it updated just fine from the Market. However, I did push the software to my phone, following the instructions here. Not sure if that's why it works without issue.
So i guess its confirmed that this is still US only. BAH
"Some features of Android 2.0 are not available on Android 1.6, for example, the ability to use the "navigate to" voice command as shown in our demo video. However, you can still create a shortcut that will allow you to launch Navigation and start getting directions to a specific place from your current location with just a single touch from your home screen."
Source: http://googlemobile.blogspot.com/2009/11/happy-thanksgiving-travels-google-maps.html
ugh...
If it is US only, why did they not restrict it to the US on the market ? Or maybe that's technically not possible with the current market configuration ?
Neejay said:
"Some features of Android 2.0 are not available on Android 1.6, for example, the ability to use the "navigate to" voice command as shown in our demo video. However, you can still create a shortcut that will allow you to launch Navigation and start getting directions to a specific place from your current location with just a single touch from your home screen."
Source: http://googlemobile.blogspot.com/2009/11/happy-thanksgiving-travels-google-maps.html
ugh...
Click to expand...
Click to collapse
Or you can search the Market for 'Nav Launcher' and it will enable these features through an external application. Works fine for me.
Same issue on a Mytouch 3G (32B,) in the US and also running Cyanogen 4.2.5.
This is a fresh install of cyanogen as well (literally nothing more than the 1.6 base image and then the cyanogen update.)
I'm also getting the "package not signed" error. Not sure what the problem is. Running CyanogenMod Android 1.6, but I honestly don't remember what version of Cyanogen it is.
This official update no different than the 1.6 hacked Maps w/Navigation that was pulled from the Droid dump.
Even if you can get it installed, you still need to use either Directions shortcuts or the Nav Launcher to get it working outside the US.
I keep getting errors cannont remove / no such file or directory
on cyan 4.2.5 seams like nothing different from 2.0 droid nav
I sure do wish that people stop giving apps 1 start because it doesn't work on cyanogenmod..... these are precisely the people that bring down heat on developers with their crying. God forbid they have to do a search on the net... and, dare I say, read 3 lines of text.
People need to realize we are not flashing official software here, and so we have no right to b*tch if something that's made for official software doesn't work on our hacked ones. There is not one dev here that I can remember who doesn't clearly say that if you break your phone it's your responsibility, not his, or the manufacturers. That's why we have this community here, if you're having problems most members here will help you out however they can because that's what this place is about tweaking our equipment as much as possible and fixing it when we mess up. I would say most people here enjoy helping others out with tech related stuff, I know I do in whatever way possible, but I have no sympathy for those that can't be a$$ed to read a few lines and just want to flash their phones with total disregard of what could happen.
How do you think google feels everytime they see a one star rating on one of their apps, or any other app, that works perfectly fine on official images when the person comments "DIS SUXXORS, IT B NOT WORKING ON C.M 4.2.5"? It's a miracle they didn't crack down on cyanogen much sooner than they did. PLEASE, PLEASE PRETTY PLEASE if you have issues with something you downloaded from XDA or any other site on the net that deals with this kind of stuff, don't go complaining to your mobile carrier, or whoever developed your mobile's official software; come here and ask for help... besides 99% of the time I'm fairly sure that we'll do a much better job of helping than anybody you can contact from your mobile carrier, or official developers. Also, if you brick you're phone be responsible for you're mistake; don't try to be sly and send it in because it's not working to your dev because again this only attracts unnecessary attention to this site. I'm fairly sure that cease & desist that xda received from MS a few years back was due to precisely this.
I've customized windows mobile, palm, symbian, android phones, plus ps1, ps2, ps3, psp, wii, and so far I've never brick anything, or at least not to the point I can't bring it back, so does this mean I'm super lucky? or super smart? Not really, it's quite simple really my secret is this: READ, Read like your equipment depended on it because quite frankly IT DOES.
Sorry for the rant guys, it's not directed at any one of you, but maybe just maybe one of these "people" will find it and correct themselves. I'd actually wish the mods would post something on the main page, but then again who am I kidding the problem originally arises from them not reading in the first place.
I agree.
Also not working on my phone (32a Magic). Currently looking for a work around.
I have searched for:
Google
Google Maps
Google Maps Navigation
Navigation
Etc, Etc, Etc...
and can NOT find this version in the market???
I updated to the latest "Google Maps" from the market, but it does not have the NAV Features.
AHA!
Redownloaded and now get the "Package Not Signed" error as well.
CyanogenMod-4.2.5

[Q] Anyone got Audible working?

Hi All-
Trying to get the Audible app working from the android market. It downloads and installs seemingly correctly. I can even browse the audible catalog using it.
What isn't working correctly for me is entering my account information to authorize the device & start playing items from my audible library. I seem to end up in an endless loop of asking for my credentials, saying they're good, followed by asking for them again. (I have another thread open where I am experiencing the exact same problem with the android market -- I can't seem to buy paid apps but free apps download and install fine & dandy)
Hopefully this issue with audible & my android market issue are caused by the same problem & both will start working once solved. In the mean time, can anyone confirm they have audible working on their device??
Thanks,
Mark
Have Exactly Same Issue
I called Audible and spoke with tech service - they even reset my password but to no avail. Audible is basically clueless (owned by Amazon so maybe it's a conspiracy
docfreed said:
I called Audible and spoke with tech service - they even reset my password but to no avail. Audible is basically clueless (owned by Amazon so maybe it's a conspiracy
Click to expand...
Click to collapse
I really dont think audible tech support can be faulted for not being able to help you get their app working on a rooted ereader.
Audible and Rooted Nook Color
I have this same issue with the Audible app. I had an email thread with someone from the app team and here is what I got from them.
"The problem is that we are not getting a consistant device id for use in authentication. I'm guessing from the device that you're using that you're making your own framework builds; if so, if you can force the DeviceID field to always give the same value, then your activation problems should stop.
I've deactivated all the activations on your account. Just to be explicit, we check TelephonyManager.getDeviceId(), and if your phone type is TelephonyManager.PHONE_TYPE_NONE we'll check android.provider.Settings.Secure.ANDROID_ID. If for whatever reason you can't get these working correctly, then you can use the .audiblePrefs file from a device where this does work; we cache the device id there in case TelephonyManager.getDeviceId() returns null but your phone type isn't PHONE_TYPE_NONE."
So it looks like someone will need to figure out how to ensure that the Device id remains the same during all the transactions with Audible.
Sean
Thanks for finding that, Sean.
I have an android phone I can look at rooting to get to the mentioned prefs file. Perhaps that would be a way to generate a stop-gap while one of the devs looks into the device id issue.
Mark
Doesn't Market Use the Device ID
It seems that I remember that the Android Market also uses the phone device ID - in fact that is why certain cheap Android tablets cannot have the Market installed. Since we can get Market on a rooted Nook Color with no issue, I don't understand how the device ID would keep changing in case of Audible.
Keeping an eye on this thread. I would love to have my Audible app working
Sent from my nook color using XDA App
Same problem here; also following it like K8108; thanks for any help you guys can come up with!
I havent tried to install audible yet but wanted to listen to my huge library of books on my old mytouch before they had an app and found a solution. You can buy SoundTaxi and rip the downloaded Audible books from your PC to whatever format you want and put on memory card on the Nook and listen. its not as bad as you think.
The odd thing of it is that under 0.2 and side-loading the app seemed to work for me. Moving to the latest autonooter however is causing the authentication problem that everyone is having.
Audible support was very kind, but basically said we do not support tablets only phones. My NC was trying to connect to audible.co.uk thus causing the conflict. As a Californian this isn't going to work for me obviously. The app seems to be able to download but not play the .aa files. Is there anyway to check the server without sending an in-app email, as that is the only way I know how to check?
Subscribed to the thread with hope that someone smarter than me can figure this out.
Update: Forgot to state that using adb of Audible does not work. Does this have anything to do with the new .jar file from Barnes and Noble, or something in the Autonooter itself. 0.2 was working very nice, but that was also under 1.0.0.
So doesn't anyone have any android device with working Audible on it... that can examine .audiblePrefs
RpDn said:
So doesn't anyone have any android device with working Audible on it... that can examine .audiblePrefs
Click to expand...
Click to collapse
I have audible working on my android rooted HD2 - and have put several builds on there, but don't know a lot of techie stuff. If you will explain to me where to look, I could have a try.
It's been suggested to copy a working .audiblePrefs file over, but I don't have another android device to set up. I might borrow one, though, for a temporary setup, to get a working .audiblePrefs file (or an Id anyway), if I knew it was the way to get around this glitch. Was hoping someone with a NC and another android device would have tried it by now.
I have a Samsung Fascinate with Audible. I copied .audiblePrefs from my SF to my NC, rebooted my NC, and I am still in the loop of entering my username and password.
I am don't know much about the technical side of this, but I am very good at following directions. If there is anything you want me to try, just let me know. I am very anxious to try this.
I don't mind posting my .audiblePrefs file, but I don't know if there is personal information in there that I should be careful about posting.
I think you should keep your prefs file to yourself... it may be specific enough to include subscriber Id. Also, you may have exceeded your activation limit if you've tried too many times before copying your prefs... an email to Audible can reset the limit.
I find it interesting that the activation loop includes a quick flash of "Activation successful" on the screen. Audible sent me a reply in response to question... that they reset my activations... didn't solve prob, of course. Also interesting that I -can- play recent 'free' excerpts dnld'd from them via Audible app on the NC.
Just need a modder to look into this Id storage/reading. I'm a comptech but just a newbie on Android/NC.
I call all the time to have Audible reset my activations. That is no big deal for me. I am rooting phones all the time or switching computers and I never deactivate devices the way you are supposed to. I do wish Audible would wise up and give their users a way to reset activations online. But at least they never hassle me about resetting them when I call them.
Any new updates on getting Audible to work? Just did the autonooter and have hit the same problem.
Thanks,
Tim
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
k8108 said:
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
Click to expand...
Click to collapse
I went from a stock 1.1.0 and then applied autonooter for the first time. Audible does not allow the authentication to occur just as the original poster noted.
k8108 said:
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
Click to expand...
Click to collapse
I did same thing (except I requested only my Android activations be reset, so as not to affect my PC or WinMo phone)...and have been using Audible on my NC successfully for a week.

R.I.P. Yalp Store

So the last (?) PlayStore access app for Android 2.1 bites the dust, apparently. The Search function died sometime last month and now log-in is impossible. The most recent version, 0.46, was done at the beginning of 2019. Word has it that the developer has abandoned the project.
Is there an alternative?
---------- Post added at 10:58 PM ---------- Previous post was at 10:40 PM ----------
nmyshkin said:
So the last (?) PlayStore access app for Android 2.1 bites the dust, apparently. The Search function died sometime last month and now log-in is impossible. The most recent version, 0.46, was done at the beginning of 2019. Word has it that the developer has abandoned the project.
Click to expand...
Click to collapse
I just installed Yalp Store fork from F-Droid.
Even ist says it's. Not compatible with my device, the app works perfect with yalp store built-in credentials.
XtraWater said:
Is there an alternative?
---------- Post added at 10:58 PM ---------- Previous post was at 10:40 PM ----------
I just installed Yalp Store fork from F-Droid.
Even ist says it's. Not compatible with my device, the app works perfect with yalp store built-in credentials.
Click to expand...
Click to collapse
Assuming this is what you are referring to: https://f-droid.org/en/packages/com.github.kiliakin.yalpstore/
I cannot at this time confirm your experience. I have been unable to successfully log in with this new forked version.
nmyshkin said:
Assuming this is what you are referring to: https://f-droid.org/en/packages/com.github.kiliakin.yalpstore/
I cannot at this time confirm your experience. I have been unable to successfully log in with this new forked version.
Click to expand...
Click to collapse
Choose another device.
XtraWater said:
Choose another device.
Click to expand...
Click to collapse
Mmm...you might have saved me some time by telling me which one worked for you. I eventually found that choosing HTC Desire would allow a log-in, but this raises other issues. Originally the Yalp Store would filter out apps that were not for Eclair (or at least list them as "incompatible"). This does not happen if you are spoofing another device that is running who knows what version of Android.
Also, Search is broken. It reverts to a search of the device (Library and Shops) rather than the PlayStore. Not helpful.
Finally, although you can use the "category" option to look at apps (with no idea which might actually be compatible...), you cannot download anything. At least I couldn't. I got an error each time I tried.
So....a lot of work for the new developer to make this functional for the NST. For a lark I installed the last version of the original Yalp Store on my Tablet running 8.1 and was surprised to see that it actually worked without any funny business. So whatever happened to it seems to have affected legacy devices, but not more current OSes.
nmyshkin said:
Mmm...you might have saved me some time by telling me which one worked for you. I eventually found that choosing HTC Desire would allow a log-in, but this raises other issues. Originally the Yalp Store would filter out apps that were not for Eclair (or at least list them as "incompatible"). This does not happen if you are spoofing another device that is running who knows what version of Android.
Also, Search is broken. It reverts to a search of the device (Library and Shops) rather than the PlayStore. Not helpful.
Finally, although you can use the "category" option to look at apps (with no idea which might actually be compatible...), you cannot download anything. At least I couldn't. I got an error each time I tried.
So....a lot of work for the new developer to make this functional for the NST. For a lark I installed the last version of the original Yalp Store on my Tablet running 8.1 and was surprised to see that it actually worked without any funny business. So whatever happened to it seems to have affected legacy devices, but not more current OSes.
Click to expand...
Click to collapse
I used galaxy 7 edge. However, can't login anymore today at all.
Including Aurora store not able to log in.
I guess this is a war against Huawei that might eventually lead to the death of aosp at least for gapps people. Imagine gapps flashing on top of clean aosp becoming useless as none of these apps would not be able to log in etc
darfri said:
Including Aurora store not able to log in.
I guess this is a war against Huawei that might eventually lead to the death of aosp at least for gapps people. Imagine gapps flashing on top of clean aosp becoming useless as none of these apps would not be able to log in etc
Click to expand...
Click to collapse
I don't want to speak out of turn because I could not do the sort of programming required for these efforts. However, I do run the 8 gb version of the Nook Tablet using the microG project components. It works very well including maps, and uses so few resources you can even use the actual Playstore app instead of one of the other apps which seem to be either abandoned or in need of repair. Unfortunately, KitKat is the lower limit for microG, but it sure makes a difference, especially on a device struggling with memory issues.
At least F-droid have in descriptions of application requirements that state minimal version of Android it can be run from on my tablet it is so. I hope that is also the case with f-droid run from NST. If I had to choose device name for spoofing purposes on that YALP application my bet would be some of the phones running Eclair. Last were some Motorola phones from 2015 as far as I recall. Since on my NST social and even shop stopped working properly I am more and more leaning to go through the road taken by many and ditch original software and start tweaking and tinkering with the device. Eclair is so old that I do not know is there many application left to work with but in case this thread escaped attention I will leave link here. https://forum.xda-developers.com/showthread.php?t=698851
SJT75 said:
At least F-droid have in descriptions of application requirements that state minimal version of Android it can be run from on my tablet it is so. I hope that is also the case with f-droid run from NST. If I had to choose device name for spoofing purposes on that YALP application my bet would be some of the phones running Eclair. Last were some Motorola phones from 2015 as far as I recall. Since on my NST social and even shop stopped working properly I am more and more leaning to go through the road taken by many and ditch original software and start tweaking and tinkering with the device. Eclair is so old that I do not know is there many application left to work with but in case this thread escaped attention I will leave link here. https://forum.xda-developers.com/showthread.php?t=698851
Click to expand...
Click to collapse
"Run" and "work" are not always the same thing. The original Yalp Store stopped working in the mid 0.4x series. It could not log in, even with your Google account, probably due to SSL issues. The fork of the Yalp Store can log in but search is broken and download does not work. Search defaults to a device search rather than a search of the PlayStore and attempts to download an app from the Categories results in a crash. I've sent results to the developer but there does not seem to be a lot of change going on there (the app does work on the NST CM 11 ROM). It's pretty moot as there is not a lot in the Market any longer that will work on the NST. It's "easier" in the long run to do your homework and then search for the app you think will work using Apkpure or similar.
If Social and Shop have stopped working on your device you probably have not updated to 1.2.2.
nmyshkin said:
"Run" and "work" are not always the same thing. The original Yalp Store stopped working in the mid 0.4x series. It could not log in, even with your Google account, probably due to SSL issues. The fork of the Yalp Store can log in but search is broken and download does not work. Search defaults to a device search rather than a search of the PlayStore and attempts to download an app from the Categories results in a crash. I've sent results to the developer but there does not seem to be a lot of change going on there (the app does work on the NST CM 11 ROM). It's pretty moot as there is not a lot in the Market any longer that will work on the NST. It's "easier" in the long run to do your homework and then search for the app you think will work using Apkpure or similar.
If Social and Shop have stopped working on your device you probably have not updated to 1.2.2.
Click to expand...
Click to collapse
True about that. Should and will are two different verbs meaning. Interesting info about that app is still working but under different ROM. Just for the sake of making things clear all custom made things here on the forum are still based on Eclair and there were not any Android upgrades through custom ROM to preserve compatibility with B&N software?
About your Nook page say that I have version 1.2.2 of software. Remember that I have NST in untouched never modified condition that has active over the air active update as designed by B&N. So it might be that something gone wrong during update and I need to do it again manually from SD card or through computer. Shop behaves odd. It allows me to search for a book but does not allow me to download. Social do not connect at all.
I am just sifting through different apps looking for those that might be possible to use on NST. I have seen in F-droid repository two YALP stores. One from the original author that is not updated for over a year and second one labeled fork which is not updated for over nine months period. To add to confusion OP mentioned version 0.46 which is not the latest version original author placed in repository (his latest version is 0.45). Still forked version with that number exist sort of labeled 0.46-legacy IIRC. So what is exactly version up used that stopped working? Even an info about non-working app is good sometime to avoid loosing time on very much likely fruitless effort.
SJT75 said:
I am just sifting through different apps looking for those that might be possible to use on NST. I have seen in F-droid repository two YALP stores. One from the original author that is not updated for over a year and second one labeled fork which is not updated for over nine months period. To add to confusion OP mentioned version 0.46 which is not the latest version original author placed in repository (his latest version is 0.45). Still forked version with that number exist sort of labeled 0.46-legacy IIRC. So what is exactly version up used that stopped working? Even an info about non-working app is good sometime to avoid loosing time on very much likely fruitless effort.
Click to expand...
Click to collapse
Yeah, it's a mess over there. You have to go to the github to access older versions of the original Yalp Store. So you can see there that the developer of the "fork" just picked up with version 0.45 and carried on. The "legacy" refers to a simpler UI such as can run on Android 2.1, for example, as even the original developer started branching out, eventually releasing two versions of the app each time. Actually it was after the app tried to become a little more fancy that it began to have trouble on the NST (surprise). It's been quite awhile since I ran the app on the NST but I suppose somewhere in my original post about the Yalp Store the version is mentioned (probably started with 0.39, if memory serves, and then moved along as login failed when Google changed things; at one time I think I got as far as 0.43)
One issue with the "fork" (besides the fact that "fork" is in the screen display name...) on the NST is that Search is broken. It defaults to a device search rather than a PlayStore search. Not sure if this was ever a problem with the original. I'll have to download a few versions and see. Also, even if you wade through the categories and select an app that way, it crashes when you try to download.
All that said, those are definitely NST issues since the most recent version of the "fork" runs fine on the CM 11 sdcard-ROM for the NST (including Search and download)
nmyshkin said:
Yeah, it's a mess over there. You have to go to the github to access older versions of the original Yalp Store. So you can see there that the developer of the "fork" just picked up with version 0.45 and carried on. The "legacy" refers to a simpler UI such as can run on Android 2.1, for example, as even the original developer started branching out, eventually releasing two versions of the app each time. Actually it was after the app tried to become a little more fancy that it began to have trouble on the NST (surprise). It's been quite awhile since I ran the app on the NST but I suppose somewhere in my original post about the Yalp Store the version is mentioned (probably started with 0.39, if memory serves, and then moved along as login failed when Google changed things; at one time I think I got as far as 0.43)
One issue with the "fork" (besides the fact that "fork" is in the screen display name...) on the NST is that Search is broken. It defaults to a device search rather than a PlayStore search. Not sure if this was ever a problem with the original. I'll have to download a few versions and see. Also, even if you wade through the categories and select an app that way, it crashes when you try to download.
All that said, those are definitely NST issues since the most recent version of the "fork" runs fine on the CM 11 sdcard-ROM for the NST (including Search and download)
Click to expand...
Click to collapse
Thanks for reply with all quality info there! Does github work on NST or have done cloning/compiling elsewhere and sideload app to NST? Interesting issue with search on NST. It looks to me like B&N manage to pull another fast one on us like they did with "nonexistent" browser. I believe that somehow they screwed search through basically invoking any search attempt to link to their search library/shop application instead. Probably author in early versions used his search function but later decided to exploit some inbuilt Android/Google option that B&N screwed with. That might be the reason why on running the app through CM11 ROM from flashcard everything works as author intended/expected to work had NST be ordinary Android device. Now question remains...is that search function still there on NST but "hidden" and can it be somehow re-enabled or some heavier work lies on that road?
SJT75 said:
Thanks for reply with all quality info there! Does github work on NST or have done cloning/compiling elsewhere and sideload app to NST? Interesting issue with search on NST. It looks to me like B&N manage to pull another fast one on us like they did with "nonexistent" browser. I believe that somehow they screwed search through basically invoking any search attempt to link to their search library/shop application instead. Probably author in early versions used his search function but later decided to exploit some inbuilt Android/Google option that B&N screwed with. That might be the reason why on running the app through CM11 ROM from flashcard everything works as author intended/expected to work had NST be ordinary Android device. Now question remains...is that search function still there on NST but "hidden" and can it be somehow re-enabled or some heavier work lies on that road?
Click to expand...
Click to collapse
So here's a run-down of what still "works" on the stock NST:
Only one version of the original Yalp Store passes every test but one. Version 0.35 succeeds in log-in (with your own Google account--no version successfully logs in with a generic Yalp Store account), Categories successfully brings up lists of apps and you can download/install from these lists. Search shows in light grey within the field "applications" and an initial search string brings up a number of more specific items, but no matter which you select it always returns "no apps".
As to the "fork", you can log in with a Google account, but Categories is blank, and Search shows in light grey within the field "Search NOOK(R)" and will dutifully check the Library, Shops, Social, etc. Totally useless.
So it seems the most nearly working is 0.35 of the original app series. Presumably the API for getting search information from the PlayStore is no longer correct. However, it may be possible for someone clever (more clever than I) to reverse engineer or cross engineer versions. Since we know the "fork" versions work on a non-NST ROM, it seems the API or whatever for Search is currently valid in them. Why they default to device search remains a mystery.
I should add that I did not try device spoofing in any of my tests. Too many variables for my brain. It may be that changing the apparent device ID would bring up apps in Categories which is otherwise blank. But using Categories to select apps is painful. A working Search is essential or the app is pretty useless.
nmyshkin said:
So here's a run-down of what still "works" on the stock NST:
Only one version of the original Yalp Store passes every test but one. Version 0.35 succeeds in log-in (with your own Google account--no version successfully logs in with a generic Yalp Store account), Categories successfully brings up lists of apps and you can download/install from these lists. Search shows in light grey within the field "applications" and an initial search string brings up a number of more specific items, but no matter which you select it always returns "no apps".
As to the "fork", you can log in with a Google account, but Categories is blank, and Search shows in light grey within the field "Search NOOK(R)" and will dutifully check the Library, Shops, Social, etc. Totally useless.
So it seems the most nearly working is 0.35 of the original app series. Presumably the API for getting search information from the PlayStore is no longer correct. However, it may be possible for someone clever (more clever than I) to reverse engineer or cross engineer versions. Since we know the "fork" versions work on a non-NST ROM, it seems the API or whatever for Search is currently valid in them. Why they default to device search remains a mystery.
I should add that I did not try device spoofing in any of my tests. Too many variables for my brain. It may be that changing the apparent device ID would bring up apps in Categories which is otherwise blank. But using Categories to select apps is painful. A working Search is essential or the app is pretty useless.
Click to expand...
Click to collapse
Hmmm...well nice to know what is working. Interesting that YALP spoofing does not work but you can login using your credentials. I was under impression that nothing in the line of Gapps works now on NST due to changes implemented by big G..gle. Since other methods like G-droid, Aurora store etc.are out of option due to their android version incompatibility it seems that sideloading through SD card and PC is only option left viable. That present another problem of search for a right app on web through PC but it seems like a topic for another thread. I believe that we also opened here another rabbit hole of messed up search on NST which is if I remember well been observed in several situation/application. On my side I think that two things I found. First apparently working search in B&N Shop does not have to mean anything as it seems that it simply goes through internally downloaded DB of their Shop. My request for download never delivers anything and it seems that internet connection to B&N servers is down. Interestingly later I received e-mail from B&N claiming that my books are ready for delivery. I will investigate this and report back about outcome but it seems that there is someone on the other end of my request sending listening and filing the intent but from some reason unbeknownst to me they do not send the requested file. Maybe they opted for another method of delivery in case of such outdated devices due to possible security problem/flaw? We will see.
While researching about Opera browser something came to my attention and I have to ask about it and this look as good place as any. I remember that people here managed to use Amazon app to download applications to NST that I have no information is it still working. However I stumbled upon an info about something called Opera store. Since Opera is still working on NST if the ancient version allows using Opera Store that might be interesting option? Has someone checked that out?
SJT75 said:
While researching about Opera browser something came to my attention and I have to ask about it and this look as good place as any. I remember that people here managed to use Amazon app to download applications to NST that I have no information is it still working. However I stumbled upon an info about something called Opera store. Since Opera is still working on NST if the ancient version allows using Opera Store that might be interesting option? Has someone checked that out?
Click to expand...
Click to collapse
I had always thought the Opera Store was for Opera extensions and addons, but you made me take a look.
Supposedly the URL is apps.opera.com, but this redirects to something called the "Bemobi Mobile Store" (using the Opera logo). The site loads fine in Opera Mini on the NST, probably Opera Mobile as well, although I did not try.
I looked at a few apps just to see what would happen. There didn't seem to be any check on the Android version. In each case I tried, tapping on the "Download" button took me to the Android Market agreement (i.e., the PlayStore entry) so whatever is going on there, it doesn't seem to be an actual "store" as much as a listing of apps with referral to the PlayStore (where, of course, the NST cannot go). There may be exceptions. Obviously I didn't try everything.
In the long run, there is very little point in some kind of Market access for the NST. If you want to try something you need to track it down. There are all kinds of sites like Apkpure, etc., that can be sources for old versions of apps. The other day I came across a huge listing of Android 2.1 apps (by an XDA member, as it happens) and most of them had dead PlayStore links. But with a version number and a little searching I had little trouble finding the few that sounded interesting.
I had hope that Opera tried to make their version of store like Amazon did or at least manage to make their online browser based version of Aurora which considering what they do with Opera Mobile wouldn't be that hard to achieve. Nevermind sideloading for the win it is!

You Version Bible app dead?

I know this app has been discussed long ago but I can't find the reference, so I need to start another thread
I've installed this in the past because it really is so much easier than trying to search through the entire epub for something. But I was not able to download the version I wanted (was greyed out or something), couldn't find any old references, and so eventually deleted it. The version I am using is labeled 1288193153_Bible_2.4.1.apk
Now when I install it I get lots of server communication error messages and never any content. I also cannot see offline options. Always the server communication errors. Refresh does not help.
Does anyone know if this is dead for the NST/G now or am I just having a bad day?
Well, can you see the URL it's trying to reach? Does it still exist?
You can apktool it then grep for http.

[SOLVED][NST/G] R.I.P. Amazon Kindle app (NOT!)

8-31-21: My report on the death of this app for the NST is a little premature. See post #5, etc., for a "fix". It worked for the poster and it worked for me. It might work for you.
Don't shoot the messenger...
Sometime in late 2020 or early 2021 it became impossible to negotiate an initial login with the Kindle app (yes, even with the OTP they email you). I've checked the security certificates and they are fine. I've tried installing the app on newer devices, going all the way to Oreo. Same behavior. A logcat on the NST shows a failed SSL negotiation so it looks like the server just won't talk to the old app any longer--at least for an initial authorization. That's the very bad news.
There is a tiny bit of good news for those who already have the Kindle app installed and authorized. At least on my three devices it continues to function completely. You can still check out Overdrive Kindle books and send them to your device and the same book on different devices appears to sync. You can also sideload .mobi books and read those. The clock is, however, probably ticking.
I mention this as a warning for anyone who has a legacy Kindle installation and is thinking of doing major work on their device. If you uninstall or wipe out the Kindle app, it's gone for good. It may be possible to use something like Titanium Backup to restore the app. I was able to find all this out after a reset and then restore my NookManager backup and the app worked fine.
Edit: I have done a little experimenting and the app authorization token appears to include a lot about the device and system. So it's not possible to use Titanium Backup. I tried this on a FW 1.2.1 installation with a working copy of Kindle. Then I updated and rooted FW 1.2.2, installed the Kindle app and then restored a Titanium backup from the same device (but with FW 1.2.1). It failed to initialize, asking to register again. I've had success only in restoring a NookManager backup from the same device with the same FW, etc., and in cloning a device from a NookManager backup. This is not something I would necessarily recommend, but you might have your reasons. However, when I tried to correct the MAC address, this threw off the Kindle app token and it reverted to asking for registration again. So there's very little wiggle room for preserving a working installation if you have to do any significant changing.
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
If the SSL layer is somewhere in Android oh boy that might be harder cookie to bake from my point of view.
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
I
Click to expand...
Click to collapse
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
Click to expand...
Click to collapse
My understanding of the issues is very limited. I once happened into a discussion where it was stated that apps which need to communicate with external servers contain their own SSL certificate which has an expiration date. If so, apps like that just die a "natural" death.
It's actually amazing that there are some apps requiring logins that still work on the NST. Two that come to mind are ancient versions of Pandora and TuneIn Radio. I use both and they still perform flawlessly. For now.
Until today I didn't know what Pandora is but I am familiar with TuneIn radio app. Good to know that some of those apps is still working. Well it just had to be complicated with SSL/TLS hidden somewhere in Android layer. I totally understand why people like Android user friendly UI and apps availability. Still gamble with Java seems that didn't paid of regarding promised platform crossing ability.
So either porting to a new Android version which probably will not be very new (low RAM) or making custom Linux which is anything but user friendly?
Edit: Scratch that question about Linux and the app OP mentioned! I just realize that there is no Linux Kindle app. It could be used through Wine and such witchcraft but that is stupid way of doing things on this device. Better option is to use it on PC and then pass it on to NST using Calibre IMHO. SSL/TLS although remains as weak spot for the time being. Oh well... If that issue with certificates get somehow fixed maybe Kindle cloud reader from browser could reclaim at least part of functions of dedicated Kindle app.
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
wrexroad said:
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
Click to expand...
Click to collapse
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
nmyshkin said:
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
Click to expand...
Click to collapse
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
wrexroad said:
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
Click to expand...
Click to collapse
Excellent. As I expected based on legacy installs continuing to work, once the credentials are on the device, you're good to go whether you use single or two factor login after.
I had a password issue with Amazon awhile back and I'll bet that's where the problem originated. When I changed my password, authentication must have gone to two-factor. I need to check that, but I'm pretty sure that's it. What great news! Back to seamless library book checkout and download, all on the device!
BTW, the version of the app you mention is the only one that works (again!) on the NST.
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
wrexroad said:
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
Click to expand...
Click to collapse
Mmm... I'm glad you posted this before I started testing. I have two NSTs with working Kindle apps right now and I don't want to trash those while tracking down the "solution". I need to think about how I'm going to approach this.
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
wrexroad said:
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
OK, that's what I had hoped for and expected since my two working installs were made before my auth. got changed to two-factor. With really old apps you never quite know how server negotiation is going to evolve.
I hope to give it a try later today.
wrexroad said:
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
When I went to my Amazon account it seemed like 2SV was not enabled, by which I mean that clicking on "edit" for the settings generated an email which contained a link that took me to a page with a button that said "Get Started".
I didn't pursue this. I didn't see anything about turning it off--or should I have gone farther along?
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
wrexroad said:
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
Click to expand...
Click to collapse
Yeah, this is not working for me. I looked at the 2SV stuff again this morning and thought, "well, I'll just set it up and then disable it". Except I don't own a mobile phone (no, truly, just an emergency ancient (non-text message) device I keep in my glove compartment), and the QR thingy woud do me no good with the NST. So I'm cooked.
Despite apparently not having 2SV set up, now I can't even generate an OTP email when I try to login with the Kindle app. But my two working installations continue to function. Puzzlement.
Edit: I had a friend with a mobile phone help me out. So I finally got to where I could "disable" 2SV. But it made no difference. Still can't log in or even generate an OTP email by trying to log in. I'm glad this worked for you and I'd like to think it might work for others, but alas my account appears to be "special".
Edit-Edit: Yeehaw! It took a lot of fumbling for me with the unwieldy password I had to recreate in the near past, but by clearing the dalvik cache and making sure that 2SV was actually listed as "disabled" at Amazon, I was finally able to log in a new installation!!! Now I don't have to run a "clone" of another device on this particular NST. Thank you, @wrexroad, for taking the time to look into this and communicate your findings. One big step back from the brink for the Kindle app
That's awesome, I'm glad you got it running! In the future, if you need to get a password via text, you can use a temporary number here: https://sms24.me/en/countries/us/
Hey folks,
I just stumbled into this NST world and want to share my experience with the Kindle app. I'm on FW 1.2.2, and used NookManager to root. I replaced the certs file as recommended in another thread. Once I was ready to login, I enabled 2fa on my Amazon account in a browser. The instructions there clarified that I would need to use PASSWORD+OTP when registering my device. Previously I had tried only the OTP, or only my normal passwrord, but those failed. Appending the OTP to my password, I was able to login.
Hope that helps anyone else who has reached this point.

Categories

Resources