Database Develop

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

Ok, this may have been answered before, but when I searched I found no concrete answers. Please forgive the noobness. I just got the NC on Saturday, tried it out as an e-reader, hated it compared to my Kindle and promptly rooted the dang thing. Now I have a really, really awesome tablet.
Anyway, I'm having an issue with the Kindle app that's bugging me. When I go into my archive and download books, I get an error that the book is corrupted and I need to remove it and try again. I do this and get the same error. It doesn't happen with every single book though so I started experimenting with some free books. With both of these books, I went to the Amazon web site from my computer and "purchased" them. Then I synced my Kindle app on the Nook and downloaded them.
The Adventures of Sherlock Holmes loads for me with no problems and works.
Tale of Two Cities does not work. It will download, but when I load it I get the the error message. I'd post the links to the books, but I can't since I'm a newbie user. Both are the free versions of said books.
The same thing happens with several other books I've got. Some will load and some will not, but I'm not sure why or what the commonality is between them. Has anyone else had these same issues and found a solution? Any help is appreciated in advance.

Read/write errors? Are these books saving to uSD? Are you using a class 6 uSD card or at least a Sandisk class 4?

Nevermind. I was able to fix it. I had to uninstall and re-install the app, but that fixed the problem. Now if I can only get my VLC streaming straightend out, I'll be in good shape. Appreciate the help though.

Great thread title. Got me to look at it.

A. Nonymous said:
Nevermind. I was able to fix it. I had to uninstall and re-install the app, but that fixed the problem. Now if I can only get my VLC streaming straightend out, I'll be in good shape. Appreciate the help though.
Click to expand...
Click to collapse
Glad that worked....I'm unable to download a certain book that I bought. All it says after a minute or two of "downloading" it says it is unable to download book. Opened a case with amazon, but they haven't figured anything out yet. This also happens on two of my windows pc's, so this isn't isolated to just android.

Adding G-Tablet to devices on the new Market site.

OK, I'm frustrated.
I have been trying to add my gtab to my devices on the new Market site, and have so far been unable to do so. Actually, that is not exactly true. I can get it to show up partially.
I have a Droid phone, and I see the phone when I go to my Market Account, Settings, My Devices. I enter the new nickname for my tablet.. [tablet, gtablet, Viewsonic G-Tablet, Malata ... all tried separately], I check the "show in menus" option. Press the Update button on the right. And nothing happens. The Maker, Model, Carrier columns for the tablet are empty, with only a hyphen. I cannot enter information directly into these columns, and whenever I try to download something, only the phone shows up. When I click on the little black triangle to expand the devices, I DO see the GTablet there. But it is grayed out with a question mark beside it. It says it is not compatible with this device. Every single app is not compatible with my tablet?
What am I missing?

Full Market fix
You need to change the build.prop file. Use steps 1-5 here:
http://forum.xda-developers.com/showthread.php?t=861044

Ya funny thing is, I think mine showed up (and someone will correct me I bet) as VS GTablet Advent Vegan 5.1.
Something like that but I thought oh they even know I am running the VEGAn ROM. Interesting indeed.

i'm runing vega5.1 and i had to do nothing... he just appeared..
but yesterday i had to do the market fix again and it disappeared.. LOL
weird

tysonkam said:
You need to change the build.prop file. Use steps 1-5 here:
http://forum.xda-developers.com/showthread.php?t=861044
Click to expand...
Click to collapse
my build.prop is correct and does not appear on market...
like i said before, it appeared then after fixing market again it does not

Same. I had to do the market fix again, and then my device disappeared. It was showing the TNT-Lite version beforehand, but now - nada.

tedlogan42 said:
Same. I had to do the market fix again, and then my device disappeared. It was showing the TNT-Lite version beforehand, but now - nada.
Click to expand...
Click to collapse
I had the EXACT same thing happen to me. It was there as a malata gtab running tnt lite, and I had to do market fix again. Now its like it was never there. Is there anyone we can talk to at google about this? Like a customer support type?
Sent from my GTablet-TnT-Lite using Tapatalk

Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.

Agree
Sprdtyf350 said:
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Click to expand...
Click to collapse
+1 I just use the market on the tablet.... My device(for now) is showing in web market.

My G-Tab running Vegan 5.1 is working in the new market with no changes or modifications except editing the nickname. I installed an app to it via the new market already. Since I have a Droid also, I kinda like the ability to install on either or both devices. YMMV, apparently...

Nvidia VEGAn-TAB-v1.0.0B5.1
My tablet showed up under the web-based market as: "Nvidia VEGAn-TAB-v1.0.0B5.1 ". I added a nickname and downloaded some applications. Since I wasn't connected to the internet at the time it was held in abeyance. Once I got a wifi connection, boom down they came. So I can now peruse the market at work or as I monitor these forums, find an application, purchase it (or not) while I am still thinking about it and have it update the tablet the next time it connects. Not bad functionality for someone like me whose work environment is wifi restricted.
I still have one issue I would like to see Google fix. I purchased a application under one gmail account but after reflashing from tnt-lite to Vegan Tab I put my other account on the device first. Now I can't update that application without some tricky effort. Not sure I want to go through that effort or pay the $5 again
While that was me being stupid, I proposed to Google that I could envision the case where I might want to purchase an application with my work credit card and put that on their tablet and also purchase an application with my personal credit card. Their current schema doesn't allow for that. I can see where with telephones it might be a little more personal but tablets may start becoming shared devices say within a family.

What they seem to have for that situation is the ability to use more than one CC with the account. In that case you could use your work CC for some and personal for others.
Not a help for your situation, but it does address the situation you proposed.

Sprdtyf350 said:
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Click to expand...
Click to collapse
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App

Frrrrrrunkis said:
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Google has prerequisites that must be met for a device to have official and supported Market. GPS and cellular radio are on that list if I'm not mistaken.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.1 w/ Clemsyn's Kernel using Tapatalk Pro

anjenaire said:
My tablet showed up under the web-based market as: "Nvidia VEGAn-TAB-v1.0.0B5.1 ". I added a nickname and downloaded some applications.
Click to expand...
Click to collapse
I'm getting the same showing up in my market access, but where we differ, is I have yet to have an application actually download to my tablet. I've gone through 5-6 different apps that did show the G-Tablet as a compatible device, and these were not installed on my tablet before going to the web market...
The big difference now is I am seeing lots more apps using the legacy Market app on the tablet.
I figured the first week or so would be pounding the web market, and things seem to be settling down, if just a small bit.

Frrrrrrunkis said:
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I think that they are not trying to give us a hard time as much as they are just trying to have some sort of way to keep things manageable. I mean, they set certain guidelines that devices need to follow to get market access so hopefully most of the apps will work. GPS, and cell type data connection are a couple requirements. Why? I don't know. Guess they had to start somewhere.
I think it is also done so developers can build apps that hopefully work for the types of devices that do qualify. Imagine how hard it would be to make apps that worked on every variation of Android out there. How often do we have issues with apps that don't work on one rom, but work on a different rom.
Maybe it was just to try and keep the market from being like the wild wild west...
Apple has it pretty easy. There are only a couple of hardware platforms they need to worry about. How about Android? There are probably a 1000 different hardware variants out there.
I really won't be surprised if they come up with a way to keep all non qualified devices off the market. Not that big of a deal really if they do though.

So far my tablet is showing on the new market and allows me to download apps to it. I'm running vegan tab 5.1 if that helps anyone...

Sprdtyf350 said:
I think that they are not trying to give us a hard time as much as they are just trying to have some sort of way to keep things manageable. I mean, they set certain guidelines that devices need to follow to get market access so hopefully most of the apps will work. GPS, and cell type data connection are a couple requirements. Why? I don't know. Guess they had to start somewhere.
I think it is also done so developers can build apps that hopefully work for the types of devices that do qualify. Imagine how hard it would be to make apps that worked on every variation of Android out there. How often do we have issues with apps that don't work on one rom, but work on a different rom.
Maybe it was just to try and keep the market from being like the wild wild west...
Apple has it pretty easy. There are only a couple of hardware platforms they need to worry about. How about Android? There are probably a 1000 different hardware variants out there.
I really won't be surprised if they come up with a way to keep all non qualified devices off the market. Not that big of a deal really if they do though.
Click to expand...
Click to collapse
You are probably right, i tend to lean towards everything being based on how these companies can make the most money. Like if what i said is true, maybe then google gets a bigger kick back from the carriers, or phone manufacterers. Its ATT 's fault really, lmao, since everything they do is based on getting more money from me as a subscriber. it seems loke they try to make evry feature, an extra charge, without lowering the standard monthly fees. (i know i am most likely wrong, it just seems this way to me). I am not askin for free stuff, it just seems like they keep the services i want out of my pockets' reach.
Sent from my GTablet-TnT-Lite using Tapatalk

Web market woes
I can confirm web market was working running TNT Lite... stopped working after redoing market fix. Web market working again... after flashing Vegan and wiping data.

For the people with working web based market: did you change your android id? if you did, did you change it to a different devices id or did you use one from an emulator?

Amazon cloud not working on rooted Nook color

Amazon cloud service is not working on my rooted nook. I have it running on my cell but on the nook its saying no cellular or wi-fi availible? Un installed reloaded and im getting the same thing?
sent from my nook color

Working great on mine.
Phiremod 5.1 on internal.
Edit - works on 5.2 also...
Sent from my NookColor using Tapatalk

Wont let me connect. claims i don't have a connection. Nook Color 1.0.1 stock rooted stock kernal.

Same with me - error 70 - no connection (although Wifi is working well) - NookColor 1.0.1 stock rooted.

Same here. I installed the Amazon MP3 app from the Android Market first. Just for grins I uninstalled and reinstalled from the Amazon Market. Exception #70 for me every time.
But I can shop for MP3 from the app just fine, and all other wifi connection seems to be working. Autonootered v3, 1.1.

I don't have my NC with me right now as I'm at work and there's no point. I will look at this as soon as I get home to see if I'm having the same issues. I'm on stock rooted as well.

Same problem here. Running rooted stock nook color v1.1.

Error 70 with me as well.
Sad panda.
Works beautifully on my phone though.

Someone needs to call Amazon about this. I would, but I'm too lazy. When you call you get a real human who actually speaks English. I'm also not sure what reaction I'd get from admitting to Amazon that I own a Nook Color.

[email protected]
Sent from my Nexus One using XDA Premium App

Better to smile and dial for stuff like this rather than wait for someone to email you back 24-48 hours later.

WTF? Getting same error.
And, while I was trying to sign into the cloud, the damn thing rebooted. Hmm.... Something is fishy here. Maybe the stock NC ROM has something to block connectivity? I looked in the hosts file, and didn't find anything. Digging around some more.

The Chris said:
WTF? Getting same error.
And, while I was trying to sign into the cloud, the damn thing rebooted. Hmm.... Something is fishy here. Maybe the stock NC ROM has something to block connectivity? I looked in the hosts file, and didn't find anything. Digging around some more.
Click to expand...
Click to collapse
Much, much love if you can find the problem. I don't think it's a hosts issue as you can browse the MP3 store without any problems. I could be wrong though.

I emailed them and got some canned response about the NookColor not being able to use Amazon Market due to restrictions - even though the email was clear in that what was not working was their cloud drive. This may be a dumb question but does it have anything to do with the required Adobe Air? Neither my iPad nor touch will work with it either, but in those cases I assumed it was because of their inability to use Air?

solom01 said:
I emailed them and got some canned response about the NookColor not being able to use Amazon Market due to restrictions - even though the email was clear in that what was not working was their cloud drive. This may be a dumb question but does it have anything to do with the required Adobe Air? Neither my iPad nor touch will work with it either, but in those cases I assumed it was because of their inability to use Air?
Click to expand...
Click to collapse
That's why I suggested calling.

I think someone with a net sniffer needs to see what internet hosts a successful AZCloud connection makes, then see what (if anything) is coming out of the NC. I bet the stock NC ROM is blocking something and there is nothing wrong with the AZCloud app or Amazon's cloud. That would explain why a new ROM would connect and the stock ROM (but rooted) won't connect. I bet there is some transport that is disabled, or ports blocked on the NC side.

Running nookie froyo on an older oc kernel (2.6.29-omap1 [email protected]#44) and was able to download the app from amazon's app store and run it perfectly.
Not sure I'll use it, uploading to the cloud's a PITA IMO. There's no drag and drop support and their idiotic uploader app takes my neatly organized library (by artist) and presents it to me sorted by album making it a painstaking process to upload select artists to the cloud. I suppose it's their way of encouraging us to purchase extra space beyond 5gb.

muzzy996 said:
I suppose it's their way of encouraging us to purchase extra space beyond 5gb.
Click to expand...
Click to collapse
Buy any album and get 20gb space for a year. You can buy albums priced as low as $0.69 cents.

A. Nonymous said:
I don't have my NC with me right now as I'm at work and there's no point. I will look at this as soon as I get home to see if I'm having the same issues. I'm on stock rooted as well.
Click to expand...
Click to collapse
I can't speak for the all of us, however i have been up all night with anticipation for your answer.

It seems this issue is exclusive to those running elcair, one semi work around i discovered is to login to the service via the browser, you cannot stream due flash however you can dowload your library.

[Q] Help for an App Developer

Hello XDA'rs,
I work for the developer Loud Crow Interactive Inc. and we build book apps for kids.
We've recently launched into the Android Market and are having trouble with our app being installed on rooted nook colors. The issues appear to be on the licensing side.
Does anyone have any thoughts on what this could be? Also, what does a rooted nook register as (device) on the Android Market place,
Thanks in advance,
Tom

What's the error, logcat ?, what's the app?
dude u gotta give some info if need a solution.
There could be a million things that could cause problems like that.

x2002dude said:
Hello XDA'rs,
I work for the developer Loud Crow Interactive Inc. and we build book apps for kids.
We've recently launched into the Android Market and are having trouble with our app being installed on rooted nook colors. The issues appear to be on the licensing side.
Does anyone have any thoughts on what this could be? Also, what does a rooted nook register as (device) on the Android Market place,
Thanks in advance,
Tom
Click to expand...
Click to collapse
We are all waiting for an answer. I have an outstanding request in with Google that I have had to update several times as they seem to be dancing around the question. When and if I hear I will post a response.

The App is "The Going to Bed Book" or "PopOut! The Tale of Peter Rabbit" - Our users are getting a "Invalid License" error. We're going to root one of our nooks soon to do some testing, but until then we were thinking we might be able to get something from the forums. Both users who reported the issue were running CM7, which I also run on my HTC IS, and runs our apps fine. Thus we're thinking it could have something to do with the device ID running against the licenses?
As we set up restrictions by device, We were curious what a rooted NC running CM7 would show as in terms of a device on the Android Market place?
Thanks for the help guys, and thanks for the patience. I'm not the actual Android developer on the team. He's out of the office for the week,
Cheers,
Tom

I think he means he is having trouble getting the application to install from the market in general. I looked up the applications and the NC was not a supported device.
I don't want to pay the money to download it to my phone and sideload it (I'm at work anyways). I don't know much about applications and how devices are determined to be compatible other than maybe their permissions. However, these applications (there are two on the market), don't require anything other than SD access.

As we set up restrictions by device....
Click to expand...
Click to collapse
That might be part of some of this. I was not aware developers were setting restrictions by device. Is this new?

model name -NookColor
product name -encore
And there is really no way to find out the problem, without looking at the logcat.

patruns said:
That might be part of some of this. I was not aware developers were setting restrictions by device. Is this new?
Click to expand...
Click to collapse
No, this feature is available to every developer since a long time. but there are 600 or so devices so not a lot of people bother with it.

rigy73 said:
model name -NookColor
product name -encore
And there is really no way to find out the problem, without looking at the logcat.
Click to expand...
Click to collapse
Actually, questions to the market run against your account and the email info and log the following device details:
> IIILanguage: en
> IssueType: market_website
> Language: en
> android_app_name: Facebook
> android_os: gingerbread
> android_os_other:
> device_manufacturer: other
> device_manufacturer_other: Barnes & Noble
> hidden_country: US
> website_issue_select: grayed_device

device_manufacturer= bn
If u want to know more take a look at build.prop, people have uploaded it in netflix thread, which reminds me that a lot of users usually change their device and fake it to run different apps.

rigy73 said:
device_manufacturer= bn
If u want to know more take a look at build.prop, people have uploaded it in netflix thread, which reminds me that a lot of users usually change their device and fake it to run different apps.
Click to expand...
Click to collapse
Those were direct quotes from what Google's filters picked up when I sent an email while logged in to the market.

Thanks guys, this will be a good start. If and when we resolve the issue I'll be sure to post an update with the details. I really wish Android Market supported promo codes; we'd love to be able to throw out some free copies for you guys to have a look at and test for these one off issues.
Thanks Again!

I assume if you sideload the .apk it will install fine?

Just want to contribute that I have the Going to Bed Book installed and running fine on my Nook. I am still running CM7 7.1RC, and have my build.prop spoofed for Netflix (no longer required, but I never changed it back and haven't flashed a new CM7 in a while). The only change I made in build.prop was setting the manufacturer to HTC.
The book runs great and is my son's new favorite app.

You may have an issue using get.DeviceID()... have one of your users use my IMEI generator and see if it fixes their problem. They can also spoof Manufacture, Device and Model with the newest version.
IMEI Generator Thread.

I have it on my CM7 (7.0.3 to lazy to update, running off sd no changes to build.prop) Nook and it works fine. My daughter loves it.
Some of the pages are kind of hard to register a turn, and it always starts upsidedown then flips itself over. But both of those things are the same on my incredible 2 as well.
Sent from my ADR6350 using XDA App