Database Develop

[Q] Comixology App

Hi guys! Been trying to purchase comics using the Comixology app... problem is... it keeps popup up an error stating "Sorry, the transaction failed. The Paypal billing service may not be available at this time. Could you please send us a not to let us know?"
I send the comixology guys a note and they already gave me the same advise 3x... that I reboot, force stop, etc. the app... tried and failed. I even went to the point of re-downloading the entire app.
I have no problem downloading "free" comics... but can't purchase them on my gtab... I tried the app on my wife's android phone (I used my comixology account on her phone) and I did not encounter the problem that keeps displaying on my gtab. Anyhow, maybe someone had some experience on this problem? A solution? Through gtab?

I didn't even know there was an Android version out there! (see what happens when you go offline for a day).
Did you get this from the market?

I've used Comixology for a little over a week now. Very nice app. I downloaded the app from the market.

logcat:
Code:
E/ComicDetail(11064): Payment failed: errorid=-1 msg=Application not authorized
I just installed it. I am a big comic reader, so I would like to get this working, as well. Delving deeper, now....
EDIT: What UI are you running, just curious. Stock? TnT Lite? VEGAn? Other?
EDIT2: My guess right now is that PayPal is supposed to pop-up, and I'm assuming that it's using the canned web browser. Does that sound right? If so, it could be the TnT proprietary browser causing issues. I might be able to prove that with using a different mod, such as the VEGAn.
EDIT3: Also curious -- do you have the PayPal app on the phone? I can't seem to find it in the Market on my GTab. I'm basically stopping at this point anyway, as I wouldn't want to store my PayPal password on my GTab anyway, as it's just not secure imo. Adding my Facebook or Pandora ID is one thing, but anything financial is where I draw the line.
Maybe I can purchase on my PC, then this app with sync? That would work (at least for me).

Roebeet,
Sorry I can't help. I've been only reading free comics up-to-now.

Their desktop PC store doesn't accept PayPal? What's up with that?
Holding off, for now. Seems like they need to still work some things out.

roebeet said:
logcat:
Code:
E/ComicDetail(11064): Payment failed: errorid=-1 msg=Application not authorized
I just installed it. I am a big comic reader, so I would like to get this working, as well. Delving deeper, now....
EDIT: What UI are you running, just curious. Stock? TnT Lite? VEGAn? Other?
EDIT2: My guess right now is that PayPal is supposed to pop-up, and I'm assuming that it's using the canned web browser. Does that sound right? If so, it could be the TnT proprietary browser causing issues. I might be able to prove that with using a different mod, such as the VEGAn.
EDIT3: Also curious -- do you have the PayPal app on the phone? I can't seem to find it in the Market on my GTab. I'm basically stopping at this point anyway, as I wouldn't want to store my PayPal password on my GTab anyway, as it's just not secure imo. Adding my Facebook or Pandora ID is one thing, but anything financial is where I draw the line.
Maybe I can purchase on my PC, then this app with sync? That would work (at least for me).
Click to expand...
Click to collapse
Answer 1: I'm using VEGAn... with Launcher Pro.
Answer 2: Yes... there should be a screen that will allow you to log-in to your Paypal account... saw this on my wife's android phone. Her phone was not rooted by the way... and using all the default software.
Answer 3: Yes I have the Paypal app... but decided to remove it. Regardless, its not working on both cases.
I believe the problem is with the ROM? No problem downloading and viewing free comics... not sure what will happen if I downloaded using my wife's phone (my account) then load up my app again via my gtab. It should display all my purchased comics (If one will believe the marketing hehe).

FYI, I also got an email back from comiXology:
"BTW, you can buy comics on https://comics.comixology.com and then download them to the app. You'll need to restart the app and your purchases will appear in My Comics."
I figured this was the case - the only issue I see if that PayPal is not a payment option. This whole setup seems a bit messy, so I think I'll wait until it's a little more stable. Anything that asks for my credit card info needs to be stable and secure, not "beta".

Thanks roebeet. Hmm, maybe this will open up some things... maybe for the devs... I used my wife's android phone... I was able to purchase the comics that I wanted and I force stopped the app in my gtab and launched it again. I was now able to download the purchased comic on my gtab... unfortunately, I still can't purchase anything on the comixology app on my gtab and will have to jump to my wife's cell just to buy it then download it unto my gtab. I believe it to be an issue with the ROM... anyone able to purchase anything on another ROM?

normz007 said:
anyone able to purchase anything on another ROM?
Click to expand...
Click to collapse
I have actually purchased quite a few things on my gtablet. I bought something from TigerDirect with a credit card, I bought a stand from ebay using paypal, and I have bought about 6 apps from the market specifically for my gtablet since the apps are better with the bigger screen. When I purchased with Paypal I was using Xscope as the browser.

I mean... has anyone able to purchase comics on this app... coz so far haven't been able too... at least on gtab running VEGAn.

Oh sorry

comhack said:
Oh sorry
Click to expand...
Click to collapse
No problem The Comixology dev team already emailed me regarding the bug... and I informed them that it might be because I'm using a rooted device... hopefully, they can fix the problem that would allow paypal purchase (even on rooted devices). ^^

downloaded comics keep needing to be re-downloaded
I've been using the Comixology app for a few weeks and overall I have been very happy with it. However, today I began to experience a weird issue with comics I have purchased (on their website) which are then ready to download when I open the Android app. I click the Download Now button and it shows the download progress (10%, 15%, etc...) until it is completely downloaded and the botton changes to Read Now. I click on it to open the comic and it comes up fine. I close the app and go back into it and then it shows the comic needs to be downloaded again (it says Download rather than Read). It has happened several times today. It is getting frustrating. Has anyone else seen this behavior?
Update: By default, the Comixology app is set to use 500MB of storage. The comics stopped disappearing once I increased the storage limit.

[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.

[Q] 2 Brand New NC and one won't autonooter

I had 2 Nook Colors I bought Friday. Today I have successfully set up one with 1.1.0 and autonooter'd using 3.0. Followed instructions and everything works as assumed.
On the second nook (wife's), I can load Autonooter, but when I get to the YouTube part, it has a network issue. I then try and go to GMail and it says the account is not set up to sync, but where it wants me to set this up is not a settings option in Nook Color Tools or anywhere I know.
I've had to reset this device twice back to factory settings. Can someone give me an idea on what I can try to do this differently?
I tried a third time by setting up the Google Account at the account setup screen during setup, but still have the problem. Seems that there is some GSM settings popping up on this device.
Wife is not happy that my NC can be rooted and her's cannot. I'm to the point of returning hers and getting a new one.

So, her device works fine as-is before trying to root it? Wireless is fine, connections are okay, browser works, etc?
I'd say double-check that you're actually on 1.1.0 if you're using the noot for 1.1.0, or maybe wait for the real Auto Nooter to see if that works better.. Should be out in a day or two hopefully.

Yeah, her device works fine stock. I have flashed it back to stock 1.0, stock 1.0.1, etc. each time doing a sideload update to 1.1.0. I then used the Autonooter for 1.1.0 and I keep getting some issue with setting up her gmail account on the phone.
If I try and set it up during the Android Setup, it loops and simply makes me set it up again. Otherwise, if I skip...I get asked to set up gmail account when trying the YouTube My Channel portion of the setup. I get the network error there.
What I have noticed is that when setting up the account on the Android Start-up section, it gives me a notification of sync/connections, but the account does not setup to sync. This is the problem - I can't find where to make the account sync or complete setup with the Autonooter I guess.
Like I said, my Nook works fine and was the first one I did. I followed the same procedures on her's and it is the same issue each time.
Disclaimer: She doesn't use the Gmail account much, but I logged into on PC. Not sure if that is a factor.
Thanks for your feedback!

lxadoz104 said:
Wife is not happy that my NC can be rooted and her's cannot. I'm to the point of returning hers and getting a new one.
Click to expand...
Click to collapse
Best advice I can give (though it seems one device may have something goin on for sure) is that you earn some brownie points and give her yours and get yourself a new one! Amazing the future favors returned by an action like this, hehe.

Great idea. Where can I adjust the account settings for her account in place of mine? (Google account)...Thanks.

lxadoz104 said:
Great idea. Where can I adjust the account settings for her account in place of mine? (Google account)...Thanks.
Click to expand...
Click to collapse
Both my wife and I use same account for the Market (really don't like paying twice for apps...we do the same for purchased books from kindle / B&N)...you can add / remove google mail accounts from inside google mail settings. Just click ADD ACCOUNT, and disable yours (or at least disable sync).
**Disclaimer** Sharing apps across multiple devices in the same household is smart, and not a slight to developers at all. We purchase apps and books, and both use them...that's called economical

Oh also.be sure to check out these cases for your new toys! We both have them, and they're perfect!!
http://forum.xda-developers.com/showthread.php?t=934081

Have you tried just doing it from 1.0.1? Is there a specific reason you want to be on 1.1.0?

lxadoz104 said:
.I get asked to set up gmail account when trying the YouTube My Channel portion of the setup. I get the network error there.
Disclaimer: She doesn't use the Gmail account much, but I logged into on PC. Not sure if that is a factor.
Click to expand...
Click to collapse
Is her G-Mail account linked to YouTube? This is a pre-requisite. Good Luck!

The easy (but time consuming) fix for this is to downgrade to 1.0.0 or 1.0.1 (make sure the downgrade was successful via settings-device info-about or whatever it is.) Then use one of the older auto-nooters to noot that version. From here, if you still would like to have a rooted 1.1 ROM, install rom manager from the Market and use it to flash the 1.1 pre-rooted ROM from the dev section. This would be the best way in my opinion.

Suggestions for an eReader

I just got a NST which I plan on rooting. I am looking for an eReader which will allow me to sync epub books accross my NST, phone, tablet and PC. Any suggestions?

I've used Moon+ and FBReader with FBSync and I'm about to start testing Aldiko with sync soon. I liked the simplicity of FBReader but it didn't seem to play nicely with the text formatting (no italicized text) and I had to manually run FBSync to save the position. Moon+ displayed the content better and when the sync worked it was perfect. It would automatically sync the latest position no matter what device I was reading on...when it worked. Of the two books I have tried I made it through the first without a problem but the second is not syncing properly and I can't seem to get it to behave itself.
So far for me nothing seems to be 100% perfect.

Well, I seem to recall Mantano has some sort of sync feature, thought I haven't made use of it, content as I am with calibre. I'd recommend checking that one out, since Mantano itself is an excellent app.

PC Calibre+Dropbox - library is in dropbox folder (folder A)
NOOK build in reader+Dropsynch - folder A is synch with /media/books
PHONE(ANDR.) some epub reader+Dropsynch - folder A is synch with /sdcard/books (or where you need)
TABLET(ANDR.) some epub reader+Dropsynch - folder A is synch with /sdcard/books (or where you need)

I just rooted over the weekend and have tried a few programs in the hopes of being able to sync the Nook Simple Touch with my Nook Tablet and phone. Therefore I've only tried programs which contain synchronization of current place/page. Here is what I've found so far:
Moon+ Reader: Has built in synchronization which worked well with the other devices but I cannot get it to work at all with the Nook Simple Touch. I've noted comments from others saying either it isn't working at all or works intermittently.
Aldiko Reader: Worked initially but then the program stopped loading. I've subsequently read that older versions will work. The sync program is a separate program which did load. I haven't done a sync yet as the main program stopped working. As opposed to the other two programs mentioned here, it does not use the Nook's built in buttons.
Mantano Reader: Best integrated with the NST of the programs I've tried. Uses built in buttons and if you use the Nook's program to list books you are given a choice of loading with built in reader versus Mantano. It uses a cloud based system to synchronize so I have not tried it yet. There is a free trial and a few different tiers for the paid version--$2 per month looked like the one which I bet most users will wind up using.
One problem with these add on readers--page turning is slower than with the built-in reader with it taking longer for the pages to refresh. I'm going to have to try this some more to decide whether the potential of synchronizing pages is worth the decrease in performance. At this point, if I am going to go with synchronization Mantano looks like the best choice (but I do want to try installing an older version of Aldiko to see how its speed is). I might also unroot the NST and use Moon+ to synchronize my phone and tablet and go back to trying to remember my place when changing between NST and other devices.

I might as well add information on a couple of other readers which I've had to reject for my purposes but which others might find useful:
FBReader: Program available to sync but not working on my phone (Galaxy Nexus). I've heard it is working with ICS on some other phones
Cool Reader: I do not believe it has any ability to synchronize but might be worth checking out as there is a version with more control over refreshing pages made for the Nook. I have not tried it but it sounds like it does refresh as quickly as the built in reader. It also works with the Nook's buttons. Information here: http://blog.the-ebook-reader.com/20...artial-refresh-and-page-button-support-video/
It looks like there are several options but no one program which does what I want If only Cool Reader would add synchronization or if Moon+ would develop a version optimized for the Nook.

I've been playing around with this a little more. I sort of got fbsync to work. There were two issues. First, I found that there is an su.zip file which works better with the Galaxy Nexus than the file I had used. Once I flashed that I was able to get fbsync to load. I also tried changing the file format on my phone to match that of the Nook Simple Touch and Tablet--moving books to SD/My Files/Books.
It does work but on a couple of tests not perfectly. I suspect that being a third party add on program affects how it works. Being free, this is something worth trying but don't rely 100% on it. On one test it did move the current page backwards to where I left off on one device as opposed to the last actual page.
Mantano does give a ten day free trial for synching and Mantano has the advantage of using the built in buttons of the Nook ST. I think I'm going to give it a try and if it works better than synching on FBReader go with the $2/month plan. Mantano has one minor problem. Listing books by author goes in order of first name, while FBRreader does order by last name. I might use Calibre to change the order of the names to last name then first name so they will be in the correct order on Mantano and reload my library.

I've been using aldiko for months now. No crashes or problems. I would definitely recommend it!
Sent from my NookColor using xda app-developers app

Mantano
Hi, I have recently rooted my NSTG. Same need of sync exposed in previous posts across the NSTG, my TF-201 tablet and my i9100 phone. Got Mantano Premium. Good app, good integration with any of my devices. Sync relatively well (sometimes it miss but for just for one page. I recommed it.
Khonshu

dxcore35 said:
PC Calibre+Dropbox - library is in dropbox folder (folder A)
NOOK build in reader+Dropsynch - folder A is synch with /media/books
PHONE(ANDR.) some epub reader+Dropsynch - folder A is synch with /sdcard/books (or where you need)
TABLET(ANDR.) some epub reader+Dropsynch - folder A is synch with /sdcard/books (or where you need)
Click to expand...
Click to collapse
Instead of dropbox I am using gdrive: in PC Insync and SyncFolder in nook. Working perfectly

CoolReader rocks refresh but does not synch atm
rcchusid said:
Cool Reader: I do not believe it has any ability to synchronize but might be worth checking out as there is a version with more control over refreshing pages made for the Nook. I have not tried it but it sounds like it does refresh as quickly as the built in reader. It also works with the Nook's buttons.
It looks like there are several options but no one program which does what I want If only Cool Reader would add synchronization or if Moon+ would develop a version optimized for the Nook.
Click to expand...
Click to collapse
I've been using CoolReader, as the refresh is handled brilliantly, and you can even set how many pages between full-screen refreshes.
Unfortunately I have not figured out synch yet, and the dev has talked about adding synch but I can't find any reference to progress.
How does Mantano do on refresh? Is it settable like CoolReader?

[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.