Android simulator Market Installation

Reprinted: the most painful http://blog.23corner.com/2010/06/16/%E7%AA% AE %E4%BA%BA-android-%E9%96%8B%E7%99%BC%E8%80%85%E6%B8%AC%E8%A9%A6-donut-%E7%89%88%E6%9C%AC-market-%E5%95%8F%E9%A1%8C%E7%9A%84%E6%96%B9%E6%B3%95/Android developers do not find the program in the Market, but this problem can not be re-appeared in the development of their own phone, in addition, Programmer is very slow (?) I couldn't send the problematic mobile phone back to the mailbox, so I had to endure the pains of those eager users. of course there are many solutions to this problem on the Internet. after a time, the body will remember those mines, it seems that there is no need to lend money to your phone in the future. in other words, if you want to do something nice, you must first sharpen the tool. If you have a cheap and easy-to-use method, you can renew your own program. small offers a very simple and cheap way to allow developers to reverse the attack until the network bandwidth stops. 1. the most common problems are Donut version (1.6) and QVGA. Therefore, install the 1.6 SDK on the computer first, and build a QVGA avd.2. then go to the HTC Developer website to capture the 1.6 System Image of Android Dev Phone 1 (the current metric name is signed-dream_devphone_userdebug-img-14721.zip) 3. the image in the next Shard is split into system. img placed in avd For Windows users, go to C: \ Documents ents and Settings \ <user> \. android \ To find your avd category. For Mac users, go ~ /. Android/avd found. 4. finally, when the Emulator is activated, you can quickly access the Market.1.5 of Donut in a similar way. After 2.0? I will try again .. :-The Installation Method on MySQL 2.1 is 1.5. For versions earlier than MySQL 1.6, you can refer to the previous article. This article provides the 2.1 method. In fact, as long as there is a change to the GMS, the usage is not the same, but the principle is the same. note the following points when running Android Market on Emulator: 1. first of all, we need to have a corresponding version of Google Android Mobile Service, usually the network can be found (GoogleBits-sdk7) 2. the default partition size of Emulator seems to be 66 MB, but the later version is system. img has exceeded this size. After opening, use df to check whether free space is 0. therefore, when initiating emulator, the-partition-size 96 must be added to generate the free space plug-in case. 3. emulator will not trigger Google check I N service, you cannot log on to Google without using it, so you have to activate emulator first, through adb pull/system/build. prop will set the recovery case for ro. config. nocheckin = yes is removed, and then put it back in the following step. after completing the preceding steps, you can start the next step. 1. switch to the category of avd, and set <sdk_dir>/platforms/android-7/images/system. the img was too late, but I was not impressed that the information could not be written, and I had to Download an SDK again to save it, therefore, the service should be enabled separately. 2. modify Emulator. Do not forget to add the-partition-size 96 parameter. 3. at this time, you can activate ddms to check whether the operation is complete (the log stops and is not spit out), and then configure the adb remount to make the system parti Tion can be used to import data. 4. change the previous build. prop plug back: adb push build. prop/system/5. open the Googlebits package, and add the following contents of the system into the Emulator adb push etc/permissions/com. google. android. datamessaging. xml/system/etc/permissions/adb push etc/permissions/com. google. android. gtalkservice. xml/system/etc/permissions/adb push framework/com. google. android. gtalkservice. jar/system/framework/adb push app/EnhancedGoogleSearchProvide R.apk/system/appadb push app/GoogleCheckin.apk/system/appadb push app/GoogleApps.apk/system/appadb push app/gtalkservice.apk/system/appadb push app/SetupWizard.apk/system/appadb push app/ vending.apk/system/appadb push app/TalkProvider.apk/system/app6. set SdkSetup.apk (adb shell rm/system/app/SdkSetup.apk) remove, so after re-opening, the SetupWizard7. disable Emulator.8. exclude cache. img with userdata-qemu.img (If your avd is via S C: \ Documents ents and Settings \ <user> \. android \ find the avd category you created; if it is created using the command line, find the path when creating avd <avd_dir>) 9. activate Emulator again! After the event, SetupWizard appears. After logging on to Google marketplace, you can use the Android Market! 2010-06-17 Updated: 2.2 seems to be more simple. First, you can find the Froyo ROM from the MoDaCo Forum. Next, refer to the aforementioned steps, in step 5, the plug-in apk is converted into GoogleServicesFramework.apk and Vending.apk! It seems that dependency does not have such a limit ..