Title says it all - can you listen to Amazon MP3's if using the Kindle app for Android?

No, you can install Audible if you want though.

There's a thread dealing with Audible on XDA-Developers. Basically, no one has been able to get it to work - something having to do with the Phone ID on our NC

I use Audible on a regular basis. It works for me. I haven't done anything special to get it working.

If you had any difficulty setting it up. I keep getting into a loop when I try to enter my login info and others have described the same issue. Also, what version number of Audible for Android are you using?

I have 1.0.3. No issues setting it up. It worked after I enabled Market manually. Remember, I didn't use autonooter.

Or, it's possible that changing the phone.apk and telephony provider somehow screws up the telephone ID - I'll have to do a a little detective work.

Thanks for the quick answer

Or, it's possible that changing the phone.apk and telephony provider somehow screws up the telephone ID - I'll have to do a a little detective work.

Thanks for the quick answer

I didn't change those filenames for the battery thing.

I'm cautious about changing filenames when all is working well. I know it's tempting to read what others are doing and follow along. I try to do it only if it'll unlock some needed functionality.

That changing the names is the issue. Well, nothing for it but to wipe and reroot. Aargh!!

Someone posted this on XDA (Anyone got Audible working?):

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.

1.00 or 1.01? It seems obvious to me that Autonooter does something to the Nook that maybe Nooter doesn't do. BUT, I don't know if Nooter 0.2 can be used on an updated Nook Color - have you any idea?

I'm still on 1.0.0. The instructions don't mention anything about Nooter .2 being for 1.0.0 or 1.0.1. It's my assumption that it doesn't matter because it's a bare bones fix.

Edit:

Be sure to install/enable all needed functionality manually.

http://nookdevs.com/NookColor_USB_ADB
http://nookdevs.com/NookColor_Enable_App_install_from_on-device_installers
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
http://nookdevs.com/NookColor_Install_missing_google_geolocate_library
http://www.nookdevs.com/NookColor:Manual_market_enable

deleted

I'm still on 1.0.0. The instructions don't mention anything about Nooter .2 being for 1.0.0 or 1.0.1. It's my assumption that it doesn't matter because it's a bare bones fix.

Edit:

Be sure to install/enable all needed functionality manually.

http://nookdevs.com/NookColor_USB_ADB
http://nookdevs.com/NookColor_Enable_App_install_from_on-device_installers
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
http://nookdevs.com/NookColor_Install_missing_google_geolocate_library
http://www.nookdevs.com/NookColor:Manual_market_enable
Thanks for the info - I'm going to go back to 1.00 and investigate

While you're investigating you may want to disable automatic updates before you're stopped in your tracks.

I use Audible on a regular basis. It works for me. I haven't done anything special to get it working.

So far I haven't needed to use Audible. Their books are too expensive. I've been quite content with audiobooks form the library and public domain.

I agree they're expensive. When I say use on a regular basis, I'm referring to accessing the app, not necessarily purchasing content on a regular basis.

The selection of ebooks and audiobooks is slim at my library. Not to mention that most of the audiobooks are WMAs.

While you're investigating you may want to disable automatic updates before you're stopped in your tracks.
Yes, good point - what method did you use (I think it's important so as to allow Audible to run) - I want to follow exactly your method

Yes, good point - what method did you use (I think it's important so as to allow Audible to run) - I want to follow exactly your method

http://www.mobileread.com/forums/showpost.php?p=1300675&postcount=19

The selection of ebooks and audiobooks is slim at my library. Not to mention that most of the audiobooks are WMAs.

I'm lucky, because I belong to libraries with large selections.

I have no intention to listen to audiobooks on my NC. I'll continue to use my MP3 player because it's small and supports the three major audiobook formats - Audible, MP3, WMA.

Yes, good point - what method did you use (I think it's important so as to allow Audible to run) - I want to follow exactly your method

How is your investigation going?

Bump.

I spoke with the Audible folks but they claim the issue is with a rooted Nook Color, and more specifically as follows:

Apparently, when using autonooter, it winds up identifying the NC as a Droid Eris phone, and the Audible app isn't compatible with the Eris!

I think that Nooter 0.2 might not do this, or the issue may lie in how the Google apps are installed.

Whatever the case, the real issue is that Android is still very much a phone OS and until Google gets its act together and comes out with a Android tablet OS there will still be issues.
This was also commented on at ZDNet.com recently and if Google delays, Apple may eat their lunch regarding tablet OS's - any way just my humble $0.02.

For now, I'll just keep my Audible stuff on my IPOD touch but it's a real PITA to have to carry two devices.

I spoke with the Audible folks but they claim the issue is with a rooted Nook Color, and more specifically as follows:

Apparently, when using autonooter, it winds up identifying the NC as a Droid Eris phone, and the Audible app isn't compatible with the Eris!

I think that Nooter 0.2 might not do this, or the issue may lie in how the Google apps are installed.

Whatever the case, the real issue is that Android is still very much a phone OS and until Google gets its act together and comes out with a Android tablet OS there will still be issues.
This was also commented on at ZDNet.com recently and if Google delays, Apple may eat their lunch regarding tablet OS's - any way just my humble $0.02.

For now, I'll just keep my Audible stuff on my IPOD touch but it's a real PITA to have to carry two devices.

Hey, glad you responded. That's why I bumped the thread. :D

Interesting take on the device fingerprint. This is an autonooter thing. When I enabled Market manually, there's an option at the end of the process to change the device fingerprint from a generic one, to a Verizon Eris one. The reason given was to have access to certain apps in the Market that otherwise would be blocked. I preferred keeping the generic fingerprint because I wasn't comfortable having the device present itself as a specific phone. I sensed there would be complications.

You can change your fingerprint to a generic one:

adb pull /system/build.prop

edit the following line:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys

so it reads:
ro.build.fingerprint=generic/zoom2/zoom2/zoom2:2.1/ERD79/269:user/test-keys

adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push build.prop /system/
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
adb reboot