Android Market

[Guest skymera]

Hmm,

Well I've successfully installed 2 apps from the Desktop Market on my Blade running JJ9. This was when it first went live.

I'll try again and report.

Edit: Seems to not work now. How disappointing.

Edit2: It just took a few minutes! Captial FM and Beluge installed from market.android.com!

Edited February 4, 2011 by skymera

[Guest urban_i]

anyone know if there is a way to uninstall app's as well?

[Guest ztedd]

Actually I'm not that happy with Google being able to remove or install apps without me being asked.

Have a look at this:

http://jon.oberheide.org/blog/2010/06/25/r...google-android/

http://jon.oberheide.org/blog/2010/06/28/a...ice-connection/

If you don't want Google to be able to do this, then you could try the following:

(option 1) use Droidwall to forbid the "Market", the "Download Manager" and the "Google Service Framework" to connect to the internet. This should stop this remote functionality. Can anyone confirm this?

However, Droidwall doesn`t work all the time. Some seconds during boot, internet isn't protected, also I experienced some problems with Droidwall, it seems to be not working sometimes.

(option 2) As apparently the Market (Vending) app is doing the remote delete / install, you can hinder the Market from running when you don't want it to. To do this, you could copy the /data/dalvik-cache/system@[email protected]@classes.dex to a backup location and then create a 0 bit file with the same name but owner and group changed to root (user 0). So Market won't be able to start till you will move the right dalvik file back.

This can be automated with scripts: "Start Market" Script and "Kill Market" Script.

commands:

For "Killing Market":

su

ps | grep com.android.vending | awk '{print $2}' | xargs kill

mv /data/dalvik-cache/system@[email protected]@classes.dex /data/backup/system@[email protected]@classes.dex

touch /data/dalvik-cache/system@[email protected]@classes.dex

chown 0.0 /data/dalvik-cache/system@[email protected]@classes.dex

chmod 600 /data/dalvik-cache/system@[email protected]@classes.dex

Then you can use Autostarts to deactivate all the Autostart Events Market uses (there are plenty!), to hinder Market from automatically starting, because it will produce Errors / Force Closes each time Market trys to start (as the dalvik cache is missing). However in the first time perhaps exactly this will be very interesting for you - to realize how often Market wants to start ;) (Google Mail and others are even worse).

For "Starting Market":

su

rm /data/dalvik-cache/system@[email protected]@classes.dex

cp -p /data/backup/system@[email protected]@classes.dex /data/dalvik-cache/system@[email protected]@classes.dex

am start -a android.intent.action.MAIN -n

com.android.vending/com.android.vending.TabbedAppBrowser

(option 3) You could deactivate the remote removing and/or installing feature completely by recompiling your market app.

Follow these steps:

1. Download and extract the APK Manager Script to C:\temp\apk_manager or some other directory with no spaces or special characters included.

Link: http://forum.xda-developers.com/printthrea...95701&pp=50

(there is a version for windows and one for linux, describing it for windows now)

Note: Requirements fpr APK Manager: Java, Adb (for ADB you need ZTE usb drivers and fastboot.zip)

2. use adb to copy the /system/app/Vending.apk to your PC, directory: C:\temp\apk_manager\place-apk-here-for-modding

command: adb pull /system/app/Vending.apk C:\temp\apk_manager\place-apk-here-for-modding

3. start C:\temp\apk_manager\Script.bat

4. type 22 and hit enter, choose Vending.apk

5. Type 9 (Decompile apk) and hit enter, wait for the process to finish

6. minimize APK Manager Script, go to C:\temp\apk_manager\projects\Vending.apk, open AndroidManifest.xml with text editor.

7. delete the following lines (perhaps they are a little bit different, but similar):

  <receiver android:name=".InstallAssetReceiver" android:permission="com.android.vending.INTENT_VENDING_ONLY">

			<intent-filter>

				<action android:name="android.intent.action.REMOTE_INTENT" />

				<category android:name="INSTALL_ASSET" />

			</intent-filter>

		</receiver>

		<receiver android:name=".RemoveAssetReceiver" android:permission="com.android.vending.INTENT_VENDING_ONLY">

			<intent-filter>

				<action android:name="android.intent.action.REMOTE_INTENT" />

				<category android:name="REMOVE_ASSET" />

			</intent-filter>

		</receiver>

8. save AndroidManifest.xml

9. Maximize APK Manager Script, type 11 (Compile apk) and hit enter, wait to finish, then type 12 (Sign apk) and hit enter, wait to finish. When asked if it is a system app, hit yes.

10. Go to C:\temp\apk_manager\place-apk-here-for-modding and delete old Vending.apk then rename signedVending.apk to Vending.apk

11. Use Root Uninstaller (Uninstaller for Root) to uninstall the Market (Vending)

12. open windows console (cmd), type: adb push C:\temp\apk_manager\place-apk-here-for-modding\Vending.apk /system/app/Vending.apk

13. use Rootexplorer or ES File Explorer to browse to /system/app and then install your new Vending.apk

14. Finished.

Can anyone confirm which methods worked for him?

Edited June 3, 2011 by Paul

[Guest Phoenix Silver]

auto kill market app with advanced task killer ;)

[Guest That-Guy]

This is a bad move on Google's part, there should be an option to enable/disable this at least ;)

[Guest targetbsp]

As mentioned above, Appbrain did all this ages ago - even the automatically downloading to the phone until google intentionally broke it before apparently ripping off the idea for themselves. :S

Still - it's a heck of a lot better than the old market. Once they get around to adding some decent search filters I spose I'll be ditching Appbrain!

I take it back! Appbrains Fast Web Installer is back. :P http://blog.appbrain.com/2011/02/fast-web-...er-is-back.html

[Guest The Soup Thief]

Hiya

Since the Android Market website opened up (https://market.android.com/) everytime I've tried to access it, whether from home, work or college I've gotten a warning accessing the site, stating that it's not secure and may represent a security risk - that its scripts don't tally or somesuch

In the address bar the https has a red strike through it, suggesting that it ain't secure

What's all that about then? it's been that way since the day it opened

What's the case? Anyone else seeing this?