Related
I'm going to avoid rooting, at least for the time being, I never rooted my D1 either. Anyways, I know January 1st, the thing's being upgraded with Adobe Flash and the Nook app store. (Flash hopefully means it's being upgraded to 2.2 as well, the lady in the store said both Flash and apps on January 1st).
I'm wondering who if anyone, is working on apps for publishing through the Nook store.
NC will not see its marketplace or any significant upgrade on January 1, believe me. The company is currently saying 'first quarter' for the marketplace and no timeframe whatsoever on flash/2.2
Two days ago when I went to B&N to pick up my nook the guy at the front showing off the nook told me it would be "upgraded to android 2.2 Gingerbread in the not to distant future." Not knowing what to make of that I just nodded my head in agreement maybe this guy knows something we don't... anyways love my stock nook.
Roofus44 said:
Two days ago when I went to B&N to pick up my nook the guy at the front showing off the nook told me it would be "upgraded to android 2.2 Gingerbread in the not to distant future." Not knowing what to make of that I just nodded my head in agreement maybe this guy knows something we don't... anyways love my stock nook.
Click to expand...
Click to collapse
2.2 Gingerbread, LOL. Hey, at least they can help you find a book so they aren't completely useless! (Not all are this ignorant of course, some are very informed.)
Obviously, being someone who was waiting for the 2.1 update for Droid 1, which was given a release date like three or four times, I know that release dates aren't exactly set in stone. Believe me.
But she did state January 1st with some manner of certainty, like it was a date stated somewhere internally. Whether or not it actually happens by then or not is obviously yet to be seen.
It's possible the lady was outright wrong too, we'll see I suppose. I do know she was a Droid owner too.
I accidentally set the default action to open home screen instead of the softkeys app... Is there anyway to change this setting? (I tried reinstalling)
ender89 said:
I accidentally set the default action to open home screen instead of the softkeys app... Is there anyway to change this setting? (I tried reinstalling)
Click to expand...
Click to collapse
install another launcher like zeam\adw\launcher pro, it will prompt you again, set it to softkeys then uninstall the extra launcher (or keep it if you wanna have 'two' launcher setups)
Since you have a non-rooted nook could you try to get to the USB debug screen as described in this thread:
http://forum.xda-developers.com/showthread.php?t=862531
If you enable USB debugging there you can push applications via adb. (And you don't have to do anything you couldn't have done by accident )
ixampl said:
Since you have a non-rooted nook could you try to get to the USB debug screen as described in this thread:
http://forum.xda-developers.com/showthread.php?t=862531
If you enable USB debugging there you can push applications via adb. (And you don't have to do anything you couldn't have done by accident )
Click to expand...
Click to collapse
I dont, and tried eariler and couldnt see it
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.
Has anyone been able to run the Nook Android Application on a rooted Nook Color?
When I try to run it, it just exists immediately.
Why would you want to run the android app, when you already have the nook.
Sent from my HTC Vision using XDA App
Nookie Froyo can and from what I've been told works fine, therefore the app works on the screen and such, but for some reason no it doesn't work properly in the B&N ROM.
I have the same experience, that is, immediate exit.
Why run it on the NookColor??
Because the Market app is just better.
Page turning is more like a page turn, the interface is better......
Tried killing native processes and it still won’t work..
No, ideas. I guess I’ll wait for Froyo.
moemoney12 said:
Why would you want to run the android app, when you already have the nook.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I knew someone was going to ask that.
Easy - once you add about 2700 books, the library app on the nookColor shows 0 books. You can still search, but you can no longer browse. (That's using up 2.5GB of space - so just about half).
I have 0 faith that B&N will fix this, so I was thinking perhaps that the android app would not have this limitation.
Whoa....have you reported this bug?
If that's the case i have no doubt it WILL be fixed. Has anyone duplicated this issue with that many books?
cabbieBot said:
Whoa....have you reported this bug?
If that's the case i have no doubt it WILL be fixed. Has anyone duplicated this issue with that many books?
Click to expand...
Click to collapse
I really hope you are right, but I wonder where you get your optimism.
E-mail technical support @ Barnes and Noble is non-existent. So far, the suggestions have ranged form hard resetting the device, to telling me how I can unarchive my books. So I gave up on that.
I called in a few times, and managed to get to the next level up of support, but can't seem to get them to file a bug report in their system. Previous companies I worked for, we would gladly file a bug report and give the customer the #. Not here.
As you can imagine, 2700 books might be considered an edge case - but not for long - especially given that the Nook reads PDFs, etc. 2700 is not all that much.
There's a post here: http://bookclubs.barnesandnoble.com...ks-in-Library/m-p/770718/highlight/true#M3277 which shows another user concurring. I have seen others with the same issue as well...
Two things.
First, another valid reason to utilize the android app is the ability to use multiple accounts. I personally use three accounts on B&N, and it is super annoying that I have to wipe my account just to read my other books.
Second, if this is a real bug present in the stock Barnes and Noble library, they will fix it. The original NOOK has had five updates to fix bugs and add features, and Barnes and Noble will continue this with the NOOKcolor. The main reason they chose the android OS as opposed to creating their own ( a la kindle or sony) was the easiness of OTA updates.
Two things.
First, another valid reason to utilize the android app is the ability to use multiple accounts. I personally use three accounts on B&N, and it is super annoying that I have to wipe my account just to read my other books.
Second, if this is a real bug present in the stock Barnes and Noble library, they will fix it. The original NOOK has had five updates to fix bugs and add features, and Barnes and Noble will continue this with the NOOKcolor. The main reason they chose the android OS as opposed to creating their own ( a la kindle or sony) was the easiness of OTA updates.
Also, the reason I am looking for it, is the ability to read holding the nook landscape, it is more confortable to me that way.
I prefer the Phone version of the UI in the Nook App and would like my CM7 NC to look the same as some of the button in the tablet version are hard to hit for some reason (especially 'go to shop', 'settings', etc).
I installed the APK that my phone downloaded but the app knows it's a tablet and converts to that. Anyone know how to make it look more like the phone version?
AutoNootered 1.0.1
havent gotten around to doing the 1.1 upgrade yet. Anyway, when i was unrooted i would add books (.epub) via Calibre (i had to do the mobi convert to get covers to show). So the books would then be added to the Books section in the library.
But since ive rooted, the books dont go into the book section, the go into "my files" in the library, and the covers dont show. And when i do read them this way, they cant be quick launched from the "keep reading" button on the bottom of the screen.
any idea on whats causing this? ive searched, but maybe im not using the right terms. i dont know.
also, now that i am rooted, is there any way to add a shortcut to the book from the home screen?
edit: i would add the books via Calibre with the nook connected via USB and then i would transfer to main memory.
double edit: using Zeam, the "keep reading" button on the bottom doesnt seem to work, i guess that rules that out. but i would still like the books to show in the my books section as the covers dont seem to work in my files. and i would still like to place a shortcut to it on the homescreen.
Anything?
Sent from inside the Gibson using my NOOKcolor.
Anyone have any ideas?
WOOHOO!!! problem solved. i launched the stock launcher and everything synced up correct.
i rebooted just to make sure, and while the "keep reading" button doesnt work, the books do show up on the Library, with the covers.
I am also new to my nook and the first thing I did was root it. I dropped some PDF files in the 'Books' folder but can't find them. I am not sure if our problems are the same but did you have the stock launcher going when you sync or did you just switch to it after you placed the files?
When the HD comes out, could somebody rip the Amazon Instant Video app apk and post it on xda?
The reason: Old app only works on Gingerbread. The new one should work on ICS and JB because the new Kindle Fire's OS is based on ICS.
Was just about to post a thread over here, we has one going on the old KF forums. ES File Explorer is on the Amazon market and should be able to read the /system/app directory without root. Really hoping this apk works on other ICS/JB devices.
An update bin file was posted and I grabbed the apk file from that. So far no luck, it FCs on my Touchpad with CM9. I tried installing as a regular app making sure Voodoo had me unrooted. I also tried as a system apk and rebooted, still FCs. It refuses to install on GB so I imagine its using API Level 15.
Hopefully it just needs another apk installed, Ill play around with it and see if I can get it working.
EDIT: I installed aLogcat to see if I could narrow down what is causing the FC. Its looking for the class "amazon.unifiedsettings.UnifiedSettingsHelper" which doesn't exist. Later in the log the FC is caused by a fatal exception with the class "amazon/unifiedsettings/UnidifedSettingsHelper" not being found. Is this a lib file or a system apk it wants?
EDIT2: I gave up on it for now. I tried some lib files, tried installing as many apks as I could (didn't try replacing system apks). It still FCs with the same error log and I can't find any files that reference unified settings. I also downloaded the Kindle Fire 2 update file (the updated original fire) and its using the same APK. LCD Density for the HD is 240 and 160 for the regular Fire 2. I use 160 on my Touchpad so that shouldn't be the issue.
How does one get apks out of Amazon's .bins?
com.amazon.dcp.apk
MyAccount-unsigned.apk
AccountAndSyncSettings.apk
These are the three extra apks (in addition to video apk itself) I needed to get it running on my Nook Tablet back in the day. I noticed back then that it seemed to work a little different for everyone. Some folks didn't need any of those while others of us experienced all manner of crashing without some of them. Sadly, one also forced my NT to appear as a KF in the Amazon app store, which made some of my purchased apps incompatible. Caveat emptor.
Would love to see those posted though if someone gets around to it. Would also love to see Amazon get their rear in gear and release a prime streaming app for android that didn't require all the fuss.
The bin files open for me in WinRAR, I think they are just zip files. AccountAndSyncSettings.apk is gone from the new Kindle Fires, the other two files are still there. I remember using those 3 files before allowed you to add an Amazon account and then open the app and you would already be logged in. With the new 2 files, it FCs in settings when I try to add an Amazon account. I didn't try using the old GB apks, it may be worth a try as they allowed an Amazon account to be added even on ICS.
I'll upload them, there is only 2 now, because you may have a different outcome than me on a different device.
No luck on a simple side load to an Acer A700 or an Acer A100 both stock and unrooted running ICS. I am reluctant to try the other apk's because I also had my a100 appear as a kindle fire and had to restore it to get use of my apps that were not kindle compatible.
I was messing around on my Touchpad with CWM so I always have the option to restore a nandroid if I were to screw something up. But I played around with it a lot this morning and didn't do any damage, everything was FCing.
No luck on Nexus 7. Tried after installing all three apk.
Sent from my Nexus 7 using Tapatalk 2
I too am looking to stream amazon on my cm9_tp but did not see anyone mention the fact it works perfectly on WebOs.
rfauconn said:
I too am looking to stream amazon on my cm9_tp but did not see anyone mention the fact it works perfectly on WebOs.
Click to expand...
Click to collapse
I will work through a flash capable browser with a desktop user agent in Android as well, but its not optimized very well for mobile devices. The app is much nicer when it works. At this point we may be better off trying to get the GB version working in ICS since it will at least open and let you browse.
In addition to a better UI in the app, I've also experienced intermittent, albeit minor, audio sync issues with mobile flash that I never had in the app. I hate that.
can someone with a kindle fire hd open up the app and then post the log? Wouldn't we be able to see where the unifiedsettingshelper file was with the log of it opening successfully?
Any update on this?
Sent from my Transformer Prime TF201 using Tapatalk 2
We need a Fire HD user or somebody with more knowledge of how things work to figure out where we can get "amazon.unifiedsettings.UnifiedSettingsHelper" from. This is the missing service it crashes on. I can't find any lib files or apks from the ROM that fix this issue. Also even if we get past this crash error another one may appear. At this point I'm thinking we may be better off trying to get the old GB app working since it seems to have fewer issues. It allows you to open and browse to videos on ICS, also allows you to add your Amazon account to the device, but crashes when you go to play a video. Its having a database issue according to the crash log posted over in the GB thread:
http://forum.xda-developers.com/showpost.php?p=31633773&postcount=193
spunker88 said:
We need a Fire HD user or somebody with more knowledge of how things work to figure out where we can get "amazon.unifiedsettings.UnifiedSettingsHelper" from. This is the missing service it crashes on. I can't find any lib files or apks from the ROM that fix this issue. Also even if we get past this crash error another one may appear. At this point I'm thinking we may be better off trying to get the old GB app working since it seems to have fewer issues. It allows you to open and browse to videos on ICS, also allows you to add your Amazon account to the device, but crashes when you go to play a video. Its having a database issue according to the crash log posted over in the GB thread:
http://forum.xda-developers.com/showpost.php?p=31633773&postcount=193
Click to expand...
Click to collapse
could amazon.unifiedsettings.UnifiedSettingsHelper be part of one of the odex files in system/app ?
It will be fantastic once this can be resolved. I hate that they are allowing this on iOS but not on other android devices.
Yes, it is absurd that iPad has access and general android devices are SOL. We purchased our content...and can't watch it reliably (app access). I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Gonzorito said:
Yes, it is absurd that iPad has access and general android devices are SOL. We purchased our content...and can't watch it reliably (app access). I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Click to expand...
Click to collapse
I tried giving Amazon some feedback on supporting other Android devices - they didn't seem to care much. I guess they want to sell more Fires, but if they're selling them at a loss wouldn't they make more profit by supporting their app on other devices?
Our how about, I purchased my kindle to read, purchased a tablet before the fire was a gleam in their eye.
I purchase video content and have limited access to it, so i won't purchase future content with amazon as a result.
No I won't buy a fire and I am encouraged to buy my future content through Google play on top of that!
Loss, loss, and more loss for Amazon. Doesn't make sense.
Sorry for side tracking the thread, I will end the QQ
Gonzorito said:
I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Click to expand...
Click to collapse
Yup. Of course they aren't going to listen to any one complaint, but Amazon is a pretty responsive company on the whole. Squeak enough and they'll grease the wheels. There's no indication they want to make this fire-only, given how many other devices its on, it's just a question of priority. You can bet the apple people whined more than the android people, so if you want them to get it in gear get on their contact page and make the request. I've done it repeatedly, but we need more people to get noticed.