Originally Posted by emt
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.
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:
so it reads:
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