Android Market

[WINKSTER]

So deleting smdl2tmp1.asec worked for me. I could not install rio before and it installed first try after this. To make things clear for people this file nor any of the files inside android _secure show up using an on phone file explorer such as astro or root file explorer. You have to do it by mounting to pc and deleting from computer. I copied the file to a folder on my desktop just incase. Now I still want to know what causes this file to appear and or be corrupted and what is its purpose. Is it something to do with apps2sd applications or rooting or use of custom roms.

Htc evo
Azrael x 4.0
Stock kernel
Adw launcher ex

 

[splmonster]

With all due respect splmonster, I have read the whole thread, in fact been monitoring it the whole time and the fix you posted on the first page of this thread is NOT the fix that we are using now.

Your suggested fix from your post was as follows:

This is the official fix.. Has come from XDA and many other forums.

Step 1 - Move all apps to internal memory from card
Step 2 - Delete android_secure file on the SD
Step 3 - Move all apps back to SD as you please, and everything will update fine.

I'm sure that works for many people but not for those of us that have a lot of apps on the SD card for two reasons 1)Very tedious to move all the apps off and then back on to the card and, more importantly 2) I can't move all of my apps from the card to my phone -- there is not enough room. Indeed the reason the apps are on the card in the first place is because i don't have enough space on the phone! I noted this in a response to your suggestion my first post in this thread. Also, I note that if you delete the android_secure file while you still have apps on the sd card, when the android_secure file is recreated it will not recognize any apps that were left on the card -- with the XDA method the apps MUST be moved off the card and then back on again for the new android_secure file to recognize them and for the phone to then access them.

The "new" fix solves that as, instead of deleting the whole android_secure folder as you and XDA suggest, its only necessary to delete the one bad file that is in the android_secure folder. This is much simpler since you don't have to move your apps off of the sd card and then back on for it to work.

BTW, I don't take credit for this, the first poster of this method was, as near as I can tell, "The Engineer" in another thread, but it was a very bare-bones statement without intructions. I do take credit for trying to explain it in a way hopefully anybody can perform, even someone that has never hooked his phone up to the computer before.

I also hope everyone passes this fix on to the number of multiple threads that are all complaining about either not being able to update apps or not being able to install certain apps like AB-Rio. I had asked the mods to merge all of these threads together and give them a sticky so there could be one place to discuss and solve the problem but to no avail. By that same token, splmonster, you may very well have posted this fix in another thread but not here and that is part of the problem, too many threads on this same issue to keep track of.

So, if you can and don't mind moving apps off the card you can delete the whole android_secure file but, if not, you only have to delete the one bad file without touching the apps.

The next question is, will this bad file reappear at some point? I think it is highly possible since I, and others, were not having problems updating apps at first and, then, something happened where it couldn't be done anymore. I'm guessing some app or some action in moving apps around created the problem and caused this bad file to be generated somehow so its possible i assume for it to happen again.

Not all have that file.. Only reason is I have done this on over 20 devices and none had that file. Including my own. Just sayin

 

[midmofan]

So deleting smdl2tmp1.asec worked for me.... Now I still want to know what causes this file to appear and or be corrupted and what is its purpose. Is it something to do with apps2sd applications or rooting or use of custom roms.

The problem started for me BEFORE I rooted my phone and, from reading the threads, it appears that there are a lot of non-rooted phones that are an issue. I THINK the problem didn't start until after I started ussiing app2sd but im not certain and have no idea if that caused any of the problem.

I also not that, at first, the problem was only with a couple of apps on the sd card but then it spread so nothing on the card, or anything that HAD been on the card at one point (even if moved it back to the phone) would update. Before the smdl2tmp1 deletion, the only way i could update an app that had ever been on the card was to have the app on my phone and then unmount the card, then update, then remount the card again. Apps that had never been put on the card would update fine with our without the card mounted.

I'm guessing that, since I did not have this problem at first it could reappear. People should experiment with app2sd, and other things to see if using that to move files back and forth might recreate the bad file.