--------------
Method 1:
--------------
Now the Simple solution that you all must have tried by now is simply go to Settings>Applications>Manage applications>Market and select “Uninstall updates”.
This would uninstall the latest update but the problem is this does not stop the process of market being auto updated in some time.
Here is the solution to this:
#You need to have a rooted android phone.
This can be done with the help of Terminal Emulator. We will have to gain root access and then disable the updater application:
1)Run Terminal Emulator
2)Write the following commands in inverted commas.
“su” [press Enter]
The superuser screen will pop out select Allow
“pm disable com.android.vending.updater” [press Enter]
That’s it,
You will see this on screen and you are done.
“package com.android.vending.updater new status: disabled”
And if by chance things go wrong, or whenever you want to enable updating you can do so by using same commands and using “Enable” in place of “Disable”
--------------
Method 2:
--------------
Here is a simple guide on how to disable Android Market from automatically updating Itself:
1. First root your Android device.
2. Download and install BusyBox from Android Market.
3. On your Android device, tap on Settings > Applications > Manage Applications > Market and on uninstall updates. This will restore your device’s Android Market to stock factory version that it was shipped with.
4. Download, install and launch a terminal app. Android Terminal Emulator is one and you can get it from Android Market.
5. Type in the following command in the terminal emulator app: su (This will give your privileged root access)
6. Type in the following command in the terminal emulator app : touch /data/app/com.android.vending-1.apk
7. Type in the following command in the terminal emulator app: chattr +i /data/app/com.android.vending-1.apk
If done correctly, the above steps will disable auto updates for Android Market.
What this process basically does is put a bogus APK file in the way of where Android wants to put the new version. The chattr command makes the file “immutable”, so that even root can’t remove it. Just setting it read only with chmod isn’t enough.
--------------
Method 3:
--------------
NOTE: Phone must be rooted and have super user rights.
1. Go into your system/app folder and rename MarketUpdater.apk to MarketUpdater.apk.bak. (I would suggest a rename instead of deleting the apk)
2. If the market has already updated, after doing step 1, go to Settings > Applications > Manage applications.
3. Scroll down to Market, click on it and choose Uninstall updates.
Done. No more market update.
References :
http://www.myindiandroid.com/tips-and-tricks/how-to-stop-auto-update-of-android-market/
http://www.techsliver.com/how-to-disable-auto-update-for-android-market/
http://forum.xda-developers.com/archive/index.php/t-876991.html
03 March 2012
How To Disable Auto Update for Android Market
Labels:
IT Mobile
01 March 2012
Fixing The "Couldn't Install On USB Storage Or SD Card" Problem On Android
Today, for the first time ever, my Android had an unexpected failure installing updates for some of my Android apps. All update attempts would inevitably end in an almost instant failure with the message that read:
Installation errorCouldn't install on USB storage or SD card
The weird part was that some apps installed OK but some got stuck in a perma-fail mode and could no longer be updated. After mucking around for a bit, I dug into the logs and found the following relevant log line:
Failed to create secure container smdl2tmp1
Aha! Now what the heck is smdl2tmp1?
After digging around the Internet some more, I found that the problem is caused by a temporary file called smdl2tmp1.asec that is used during some installations (I think of apps that are movable to SD) but does not get deleted for some reason, most notably when you run out of space. Because of this, the system can't create it and treats it as an error, rather than figuring out that it's stale and simply deleting it.
The solution? Go and delete smdl2tmp1.asec yourself. From what I can tell, it could reside in 2 locations:
1. /sdcard/.android_secure - this is an invisible folder on your SD card, which you can access with any file manager, like ASTRO
2. /mnt/secure/asec/ - access to this folder requires root and a program like Root Explorer
Look for smdl2tmp1.asec in these folders and delete any ones you see. Deleting it seems to be a safe enough operation - it's just a temporary file after all. Once you've done that, all the update problems should go away:
I/logwrapper( 170): /system/bin/newfs_msdos terminated by exit(0)
I/PackageHelper(15175): Created secure container smdl2tmp1 at /mnt/asec/smdl2tmp1
I/DefContainer(15175): Created container for smdl2tmp1 at path : /mnt/asec/smdl2tmp1
I/DefContainer(15175): Copied /cache/32.apk to /mnt/asec/smdl2tmp1/pkg.apk
I/DefContainer(15175): Finalized container smdl2tmp1
I/DefContainer(15175): Unmounting smdl2tmp1 at path /mnt/asec/smdl2tmp1
Later on, I found this bug discussing the situation and slamming Google left and right for not fixing this problem and requiring users to look for random files on their phones, which I wholeheartedly agreed with.
Oh well, at least my phone is healthy again, and I hope yours is too, as you probably found this page while looking for a solution.
Labels:
IT Mobile
03 February 2012
喝酒脸红、喝酒脸白、喝酒出汗 — 什么样的人能喝酒?
喝酒脸红是乙醛引起的。乙醛具有让毛细血管扩张的功能,而脸部毛细血管的扩张才是脸红的原因。所以喝酒脸红的人意味着能迅速将乙醇转化成乙醛,也就是说有他们有高效的乙醇脱氢酶 (alcohol dehydrogenase)。 不过我们不能忘了还有一种酶,乙醛脱氢酶(aldehyde dehydrogenase)。喝酒脸红的人是只有前一个酶没有后一个酶,所以体内迅速累积乙醛而迟迟不能代谢,因此会长时间涨红了脸。不过大家都有经验,当1-2个小时后红色就会渐渐腿去,这是靠肝脏里的P450慢慢将乙醛转化成乙酸,然后进入TCA循环而被代谢。
那么喝酒比较厉害的人是怎么回事呢?这些人往往越喝脸越白,到一个点突然不行了,烂醉如泥。那是因为这样的人高活性的乙醇脱氢酶和乙醛脱氢酶均没有,主要靠肝脏里的 P450慢慢氧化(因为P450是特异性比较低的一群氧化酶)。那么,这样的人为什么会给人很能喝酒的感觉呢?那时因为他们靠体液来稀释酒精,个头越大感觉越能喝酒。在正常情况下,酒精浓度要超过0.1%他们才会昏迷,对大多数南方人来说是半斤白酒,而北方人由于体型大,可以喝到8两到一斤白酒。但不管什么人,如果他是脸越喝越白型的,最好不要超过半斤,不然有急性酒精中毒的可能性。
如果一个人即有高活性的乙醇脱氢酶又有高活性的乙醛脱氢酶会怎样呢?他/她就是传说中的酒篓子。如何判断他/她是不是酒篓子呢?看是不是大量出汗。因为如果两个酶都高活性,酒精迅速变成乙酸进入TCA循环而发热,所以大量发热而出汗。碰到这样的人你只能自认倒霉,就是十个八个正常人也斗不过他。好在这样的人不多,大概10万分之一左右吧。
喝酒脸红的人不容易伤肝脏,而喝酒脸白的人特别容易伤肝脏。红脸的人大家一般少劝酒,因此喝得少,酒后发困,睡上15-30分钟就又精神抖擞了。而白脸的则往往不知自己的地线,在高度兴奋中饮酒过量,直到烂醉。他们体内的酒精由于没有高活性的酶处理而发生积累,导致肝脏损伤。酒精性肝损伤一般只发生在这些人身上。红脸的人可以连续几餐即便喝吐了也喝酒,而白脸的人需要更多时间的休息,因为酒精的代谢需要一两天的时间。
References: http://lxysunday.blog.hexun.com/61028874_d.html
Labels:
Physical Healthcare
21 December 2011
Clear Recent Commands From the Run Dialog in Windows XP
Has it ever bothered you that there isn’t an obvious way to remove the previous items in the Run box in Windows? It’s often very useful, of course… but if you are just a little bit paranoid you might want to clean out that list on occasion.
Of course there are many cleaner applications that will do this for you, but we’ll explain how to do it manually.
Clear Recent Run Dialog Entries Through Regedit
Open up regedit.exe through the start menu run box, and then navigate down to the following key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU
You’ll see all your recent commands on the right, and you can delete any of the keys that contain your commands. You’ll have to logoff and then back on, but the list should be clean.
Note that this will also work for Windows Vista’s Run dialog, although most people have switched to using the search box instead.
Completely Clear Recent Run Dialog Entries The Easier Way
Reader Ayush pointed out a much more easy solution that this registry hack-happy geek overlooked.
Right-click on the taskbar and choose Properties, then choose Start Menu.
Select the “Classic Start menu” option, and choose the Customize button. (Don’t worry, we’ll cancel out of the dialogs so you can keep the XP menu style)
Now just click the Clear button to remove all of the recent documents and applications from the start menu.
Once you’ve done that, hit Cancel and then Cancel again to make sure you don’t switch to the Classic Start menu.
Note that this method will clear out everything… so if you just want to remove a single entry you need to use the registry hack method.
References: http://www.howtogeek.com/howto/windows/clear-recent-commands-from-the-run-dialog-in-windows-xp/
Labels:
IT Mobile
30 November 2011
Fix Temporary Profile in Windows 7 (Error message: "The User Profile Service failed the logon. User profile cannot be loaded”)
If you get a message you have been logged into a temporary profile in Windows 7 computer, then it’s not your correct profile. You may miss your icons on desktop, any customized settings in Windows 7 by this temp profile issue. This post explains how easily you can fix temporary profile in Windows 7 issue.
By restarting or re logging to Windows 7 computer will not help you in this case. This temp profile issue rises because of a registry key.
Fix Temporary Profile in Windows 7 Issue
1) Log in with temp profile.
2) Start registry editor by typing regedit in find box in Windows 7.
3) Navigate the following location in Windows 7.
4) You can see similar keys under profile list with .bak difference, as shown below.
5) Your correct profile key is marked as bak. Currently your Windows 7 computer logged in with fresh profile with same key. So, rename the new profile key ( which is not having.bak) and remove .bak from correct profile key. See below.
6) That’s it. Log off and log in with your user name and password. You must get your icons and profile settings back in Windows 7. This is very simple and easy method to fix temp profile in Windows 7 issue.
Method 1: Fix the User Account Profile
To do this, follow the steps below:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
- Click Start
- In Start Search (Windows Vista) or Search programs and files (Windows 7) area, type in regedit, and press Enter.
- If prompted by UAC, click Continue (Windows Vista) or Yes (Windows 7).
- In Registry Editor, go to:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
- In the left pane, look for the folder name starting with S-1-5 (SID key) followed by a long number. then click each folder and locate ProfileImagePath from the right pane, double click to verify that this is the user account profile that has the error.Expand this image
- If you have two folders starting with S-1-5 followed by same long nubmers and one of them ended with .bak. Change the .bak folder to normal one. To do this, follow the steps below:
- Right click the folder without .bak and choose Rename. Then add .ba at the end of the folder name.
- Right click the folder with .bak and choose Rename. Then remove .bak at the end of the folder name.
- Right click the folder with .ba and choose Rename. Then change the .ba to .bak at the end of the folder name.
- Right click the folder without .bak and choose Rename. Then add .ba at the end of the folder name.
- If you have only one folder starting with S-1-5 followed by a long numbers and ended with.bak. Right click the folder and choose Rename. Then remove .bak at the end of the folder name.
- If you have two folders starting with S-1-5 followed by same long nubmers and one of them ended with .bak. Change the .bak folder to normal one. To do this, follow the steps below:
- Choose the folder without .bak, in the right pane, double click RefCount and type 0 and then clickOK.
- Choose the folder without .bak, in the right pane, double click State and type 0 and then click OK.
- Close Registry Editor.
- Restart the computer.
- Log on again with your account.
Method 2: Log on to Windows and copy your data to a new account
reate a new account and copy the data from the old account to the new account.Method 3: Delete the error SID and create a new profile
To delete the error SID and create a new profile, follow the steps below:
- Delete the error SID.
To have us fix this problem for you, go to the "Fix it for me" section. If you would rather fix it yourself, go to the "Let me fix it myself" section.Fix it for me
To fix this problem automatically , click the Fix this problem link. Then click Run in the File Downloaddialog box, and follow the steps in this wizard.
Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.Let me fix it myself
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:How to back up and restore the registry in Windows
To resolve this problem yourself, follow these steps:- Delete the profile by using the Computer Properties dialog box. To do this, follow these steps:
- Click Start, right-click Computer, and then click Properties.
- Click Change settings.
- In the System Properties dialog box, click the Advanced tab.
- Under User Profiles, click Settings.
- In the User Profiles dialog box, select the profile that you want to delete, clickDelete, and then click OK.
- Click Start
- Locate and then expand the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
- Right-click the SID that you want to remove, and then click Delete.
- Delete the profile by using the Computer Properties dialog box. To do this, follow these steps:
- Log on to the computer and create a new profile.
References:
Labels:
IT Mobile
Subscribe to:
Posts (Atom)