[clockworx]

Don't be an idiot and flash this to devices it wasn't intended for. This is for the WPDN, certain framework revisions ONLY.

In general, if you're grabbing a file for a different device and overwriting an existing file on your device, you are ASKING for trouble.


No more emulators!

Push this over to your phone, and you'll be able to get a working android ID without any sort of silly fooling around.

To repeat and clarify: You will get a fresh working Android ID, from Google, just like a phone.

From early testing it still appears SOME paid apps may be missing, but this is definitely a better solution than an ID from the 1.6 emulator as I continue to look into the issue. (I think this is actually less an Android ID issue than it is an issue with PDN being a configuration that some apps refuse to support, be it resolution, version 2.0 or whatever)

(I've also found that using your phone's ID on your PDN may "taint" what you can see in the market on your phone. Personally, I'll be moving away from sharing an ID with my phone)

Instructions
1) You'll need to remount system as R/W regardless. so let's start with that:
"adb remount"

2) If you want to start over clean, I'd recommend clearing market cache and killing your existing android ID.

adb shell sqlite3 /data/data/com.google.android.googleapps/databases/gls.db "update meta set intvalue='0' where name='androidId'";

To clear market cache: Settings->Manage Applications->press menu button->choose "Filter"->choose "All"->Scroll down to Market and select it->choose "Clear Cache"

3) Apply this hack

"adb push framework.jar /system/framework/"

4) Since we replaced a main framework, clear dalvik cache just to be safe, and reboot. Yes, the first reboot will take longer since we just cleared the cache.

"adb shell rm -r /data/dalv*"
"adb shell reboot"

5) Go ahead and log into Google Talk and use the Market to ensure all is working.

Feedback welcome!

File:
7/24 and 8/6: framework.jar

8/20: http://www.mediafire.com/download.php?8oowfn1c89uos8u

PDN Open Firmware Project: http://www.mediafire.com/download.php?1de9o4d8qc19x66

(props to blazingwolf for bravely being the first guinea pig [besides me], and noticing the Docs To Go full version is missing)

4/8/11 Mod Edit: Fixed formatting. Please report any broken links or other errors. Thanks --MrsB

 

[davidr]

clockwork..It sounds like the instructions assume you have already applied some sort of Google and market hacks.. What if you are starting from scratch.. just have basic hack (keys and alternate home).. same instructions?

 

[clockworx]

Yes, the files for this are unrelated to any previous hacks, so you're fine following the same instructions.(You will still need to install Google Experience at some point, however, otherwise you won't have Market at all. Alternate markets such as App Brain may work, not sure, haven't tested)

 

[davidr]

and if things go South.. same fix to get back...i.e. re-flash original fw?

 

[clockworx]

and if things go South.. same fix to get back...i.e. re-flash original fw?

Since it is only one file, you can pull off your original framework if you wish as a backup. "adb pull /system/framework/framework.jar framework.jar.pdn"
To restore then would be "adb push framework.jar.pdn /system/framework/framework.jar"

 

[davidr]

Thanks.. and is the best way to get GE, the modified 7-24fw? or is there just a file I can install with adb?
Sorry for the elementary questions.. I have read so much stuff I don't understand, that I am getting lost on the best way to do some things to maximize chance of success and minimize chance of problems...

 

[geebekazoo]

Clockworx, If one is installing GE for the first time and then installs this framework, when going out to Google for the first time which Android version ID will be given to the PDN? 2.0?

 

[clockworx]

Google actually doesn't get the version when generating the Android ID (at least, as far as I can tell).

 

[clockworx]

Thanks.. and is the best way to get GE the modified 7-24fw? or is there just a file I can install with adb?S
orry for the elementary questions.. I have read so much stuff I don't understand, that I am getting lost on the best way to do some things to maximize chance of success and minimize chance of problems...

My standalone installer is here: http://www.slatedroid.com/pandigita...ience-alpha-nearly-everything-but-market.html installs via ADB, you would just need to drop in a working YouTube.apk before installing (instructions on getting on are in that thread). I believe roebeet has a 7-24 FW with everything pre-installed, if you want to go that direction. Either should work, you'd just have to apply this hack afterwards.

 

[geebekazoo]

Google actually doesn't get the version when generating the Android ID (at least as far as I can tell).

It must get something from somewhere. After I logged in with the emulator I notice that there are some apps that the Marketplace will not offer because it's a 1.6 image.

 

[clockworx]

I believe that happens in the Market. The whole thing is kind of weird because it appears some kind of caching occurs, in that a previously working Android ID can become tainted by entering the Market on a poorly supported device (as I mentioned in the OP).

As an example, when I was testing this, Blazingwolf noticed Dataviz's paid apps weren't showing up.
In order of events:
1) I checked on my HTC Hero to ensure they showed up there. They did.
2) I checked on my PDN to see if they showed up there. They did not.
3) I set my PDN's android ID to the phone's android ID to see if it was an ID related issue, or a device related issue. The first time I used Market on the PDN Dataviz's paid apps showed up. On subsequent attmepts, they did not.
4) Now, on my phone, I can no longer see Dataviz's paid apps as well. Hopefully this will sort itself out.

 

[bodex]

It doesn't seem to be working for me, yet. Before following these instructions I was getting errors/force close whenever something tried to sync.

Now, after following your not-ugly directions here, I'm no longer getting any errors. I click on Google Talk and a screen just flashes open/close before I see anything (is that normal?).

I open up Market just fine and can see everything, but upon trying to install, the app just hangs at "Starting download..."

edit. another note, you mentioned dataviz apps not showing up in market, and I did get this error when I rebooted after your instructions : "Sorry! Process com.dataviz.docstogo is not responding." I do have Documents To Go installed so that must be it... doesn't seem like that would cause a problem with anything else though, just wanted to mention it

edit2. Just looked at the sync settings and under manage accounts my gmail account has Sync Error listed under it. The sync icon at the far right is red. Usually red is bad. I must have broke it.

edit3. and clicking on my gmail account it looks like I get an okay check for gmail sync, but a bad ! for com.android.contacts.

 

[clockworx]

Can you use the instructions from the ugly market hack to check for a google ID value in gls.db?

 

[oneglory]

hey clockworx - hows about you and me combine our batch scripts?

 

[bodex]

Can you use the instructions from the ugly market hack to check for a google ID value in gls.db?

I used: adb shell sqlite3 /data/data/com.google.android.googleapps/databases/gls.db "select * from meta";
If I did that right, it gave me: androidId||0

 

[clockworx]

hey clockworx - hows about you and me combine our batch scripts?

Actually, I was going to suggest you and enjoys1 combine....mine are usually just the basics, and then I've passed on a suggestion or two to him (and maybe you too? don't remember.....) I'd be happy to keep you guys updated as I have stuff coming though, so you're ready for it.

 

[clockworx]

I used: adb shell sqlite3 /data/data/com.google.android.googleapps/databases/gls.db "select * from meta";If I did that right it gave me: androidId||0

If you run logcat and save it to a file ("adb logcat > log.txt"....it will just sit there, so give it a few seconds and then do CTL-C to break), you should see some debug messages if you search for CLOCKWORX.

See if anything comes up...Are you running 7/24? I don't think it should matter, but just asking anyways...

 

[bodex]

If you run logcat and save it to a file ("adb logcat > log.txt"....it will just sit there so give it a few seconds and then do CTL-C to break), you should see some debug messages if you search for CLOCKWORX.

See if anything comes up...Are you running 7/24? I don't think it should matter, but just asking anyways...

Yes, running on 7/24.
With your name on it, Logcat only shows this line "I/CLOCKWORX( 5634): Returning 1."
I'm not sure if you need more info from the log before/after that?

 

[clockworx]

Yes running on 7/24.
With your name on it, Logcat only shows this line "I/CLOCKWORX( 5634): Returning 1."
I'm not sure if you need more info from the log before/after that?

If working properly, it should kick off another CLOCKWORX message around that same area (slightly earlier, I think) with a longer string.

It sounds like for some reason Google is unwilling to kick off another request to get your Android ID. I know a full factory reset will work, since I tested that, but I doubt you want to do that.

Would it be possible for you to move /data/system/accounts.db (I think I got that filename right) to a seperate file and see if Google will re-initiate when doing a proper account setup? (I also did test with setting up my account, checking that my Android ID is zero, and then applying the fix, and it worked. That should be the same situation you're in, so I'm not sure why it wouldn't be kicking off the request to get an Android ID)

 

[bodex]

If working properly it should kick off another CLOCKWORX message around that same area (slightly earlier, I think) with a longer string.

It sounds like for some reason Google is unwilling to kick off another request to get your Android ID. I know a full factory reset will work, since I tested that, but I doubt you want to do that. Would it be possible for you to move /data/system/accounts.db (I think I got that filename right) to a seperate file and see if Google will re-initiate when doing a proper account setup?...

So just move the accounts.db file to another location and then try to sync in settings again?