I can't load the market application. As soon as I choose an option, for example if I go beyond the first set of options and choose "Applications" I get this message: "A server error has occurred. Retry, or cancel and return to previous screen." My data/IM seems to be working correctly other than the market, so it is not a connectivity issue. It doesn't load on WIFI, 3G, enhanced, or even edge, I've tried them all, so it doesn't seem to be an issue specific to my locale. Within a few attempts I get a force-close. What is going on here? Any ideas?
Anyone else getting this problem right now?
I ported the Market cache over to my SD card and it was working fine for weeks, does anyone think this might have anything to do with it? Maybe something is messed up on my card?
anyone got anything on this?
I just had same problem. Have you tried restarting the phone?
yes of course. lol. first thing i tried. i also upgraded from 1.41 to 1.42... THEN I solved my problem by actually thinking. Like I said I ported the market cache over to the SD card. I totally flushed the cache by deleting the folder I created there and then went back through the process of moving my cache over to the SD card. No more problems.
Solved.
Related
I hope this is the right area to post this, but basically i'm after help from some Android experts and this seemed the place to go.
Basically I appear to have in some way knackered the settings default Install Location for Apps.
I used the well known and pretty straight forward trick of using the adb program in the SDK to override the default install location so it's the SD, and then enabling me to move all my apps to the SD card. It worked perfectly and gained me loads of space, which I promptly filled up with other apps.
However a couple of days ago I had a load of updates to install so I went with the normal "Update All" option and let it go. However it downloaded all the apps but when it got to the install stage for all of them it seemed to fail, it just sat there with all 5 apps and said they were installing, but was like that for a good 5 mins. At this point I made my mistake and thought (stupidly) i'd just turn off the phone and start again.
The result of that however was that now no apps which are stored on the SD card will install. They'll download but the installation will fail instantly. If I move them to the Phone Memory they'll install, but I can't really do this consistently as if I move something over it takes the phone over the ~15mb limit and they won't download at all. Once I get apps on though they will move across to the SD card fine and work
I must have broken some setting somewhere, I'm thinking something has gotten stuck, a flag is raised which I need to lower or something.
I'd greatly appreciate help with this, as my only other alternative seems to be a hard reset.
My handset is an unrooted (obviously) HTC Desire running 2.2
thanks.
Anyone able to help in any way?
Yes, I've read the threads. I've done the search.
I have an HTC Aria running liberated FR008.
It's been working brilliantly for as long as I can remember but the error popped up "Couldn't install on USB storage or SD".
There is no "smdl2tmp1.asec" file on my phone, never was that I can tell. That is not related to the problem.
Yesterday, at great expense of time, I removed everything from the 16GB SD card, reformatted it, and put it all back (about 12GB worth of data). This did not fix the problem.
One thing that may be related, I recently was running into the issue of not having enough space, so I moved the dalvik cache to SD using "a2sd cachetosd" or whaver the command is. HTC Aria having limited space for apps is a known major problem that I was trying to fix. Is this related? I don't know. I did this before it began having this new error.
Someone has to know a legit fix for this issue. There is 1.65GB of free space on my SD card and 34.48MB on the internal storage. There should be more than enough space to do updates.
What's the scoop? can someone help?
Anyone have a hint on this? My search ninja skills on the net are not giving me any answers.
Continuing the theme of one hand clapping:
I found for a couple of apps that could not update due to this problem, they happened to be apps installed on the SD. I moved them back to the phone and they updated successfully. I have not attempted to move them back to the SD.
Perhaps this data point aids in diagnosing this issue. If this proves to be a consistent pattern, then I will just apply this work around as long as I have space on the phone to move apps over one at a time and update them that way. Even though the solution to this bug doesn't seem to be at hand, perhaps this is a work around.
Hi guys,
I've been having this problem for quite some time now. I first noticed this when I shifted from one custom ROM (SAGA LBC) to another (CyanogenMod 7.1). At first, my phone kept resetting after a reboot. At first, I thought it was an incompatible ROM. For a time, wiping cache and dalvik cache via the recovery interface did the trick. But then, it just got worse and worse. I eventually reverted back to LBC, thinking that it might be Cyanogen. But, as it turns out, my phone still kept resetting. Even as mundane a task as going to the settings menu freezes up my phone, requiring me to reset, sometimes even by pulling out the battery. I tried doing the wiping of the caches again, bit it never became effective.
Then I read somewhere that Andoid seems to be uber sensitive to file corruptions and defragmentation of the microSD card, so I defragged the SD, fixed the permissions, and deleted the LOST.DIR and tmp folders. Everything went smoothly at first, but then after a couple of days, my phone kept rebooting again. To verify that it was the microSD at fault, I removed it for the mean time. Since then, my phone hasn't frozen nor rebooted.
One other thing: whenever I check the microSD via Windows (right click --> Properties --> Tools), everything seems to be in order as Windows can't detect anything wrong. Right now, I've ran chkdsk :f /f /r on the drive, but Windows says that everything is fine. I haven't reinstalled the microSD yet, as I want to run a more thorough test before I do.
Have any of you encountered this? Could you guys give me suggestions on what to do, a better tool than chkdsk, etc? I can buy another card, but I don't want to do that just yet. My microSD is 32GB, and I don't want to just throw it away or something
Phone has been fine, working GREAT, thanks to the smart minds in this forum. Well, today my phone has been fine, until just a little while ago. It doesn't appear to have re-booted at all, but now things are really different. My theme isn't working, and isn't even showing up in my list anymore, as well as a lot of apps. I rebooted, and when I did, there was a wierd icon in my status bar. It looked to be the sim, or SD, with an exclamation point beside it.
I booted into recovery and tried wiping cache, dalvik, and fix permissions. It got rid of the icon, but my apps still aren't showing up. A lot of them. Also, before rebooting, it wouldn't let me send a text. What should I do?
Val Final Rom, AntonX rc2 kernel, AS14.1
Update:
Everything is looking fine now. Apps have returned. I'm not sure really what happened, but I freaked. This is why I only use 'chirps'. I get pissed and smash these things when they fail to do my bidding.
Update 2:
It happened again. I think I have it figured out to be a problem with my sim card. Gonna try a few things and report back.
Maybe internal storage device/memory problems? I would try making a backup and reflashing same/different rom to test if it still happens.
Last time that happened to me, my SD card went corrupt. It may be time for a new one
you may have broke your sd reader.
Sim cards don't cause internal phone problems, all that would happen is no service/"UNABLE TO READ SIM CARD". Your apps/data would be fine.
Did you drop it?(your phone)
That's what happened to my G1.
And since when are themes listed in applications??
Do you mean launcher?(home screen replacement)
cm7/miui have theme support.
Sorry, been awwaway. Crazty night off. Phonne is still workidng fine from last fix. I thinki I just put it donw too hard.
SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.
Click to expand...
Click to collapse
Solution answer
So this one is weird.
Everything was working fine untill I rebooted my phone earlier today.
For some reason, since this reboot, apps are unable to access my SD card storage. As far as I know, no update was applied with this reboot. I do not recall tinkering or changing anything related to this recently.
Symptoms
SD card is still visible in the storage tab of the settings (there is no available option to unmount or eject it) or in select cases when choosing a folder from an app, however the content does not show up past the root.
My music player (Oto music) sends an error message "Cannot play this file" while trying to play a song from the SD card
File explorer will not show the SD card directory at all
Resillio Sync has a synced folder on the SD card. It now says "Can't open the destination folder". If I try adding a new synced folder on the SD card and select the root of the SD card, I get the message "Android OS restricts access to this folder"
Google file is stuck in a loop trying to get permissions to access the card
SD card works just fine on another phone.
Other SD cards have the same problem with my phone, not just this one
SD card does not show up when using file transfer with a Windows PC
Rebooting the phone did nothing
Removing the card and putting it back in again did nothing
Formatting the card did nothing
I factory reset the phone. It worked, but the problem came back at the first reboot.
Current state of investigations I have reset the phone a second time and reboot it every time I install an app, uninstall or disable a system app or change some settings. So far the SD card is still accessible so I know what it's not:
it's not the fault of disabling system apps
it's not related to using a work profile (Insular)
still haven't found an app that causes it
Apps I have not tried re-installing on my second reset and that might be the curlprit:
Shizuku (I have my suspicions on this one, let me know if this one is known for causing similar bugs) Not Shizuku per se but a developper option needed for it (see solution answer)
I have no idea what could cause this, all I know is it's related to my phone in particular and it appeared out of nowhere.
I am using Android 13 on ColorOS.
Thanks to anyone who can help.
Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.
blackhawk said:
Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.
Click to expand...
Click to collapse
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?
Iune said:
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?
Click to expand...
Click to collapse
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.
blackhawk said:
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.
Click to expand...
Click to collapse
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.
SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.
Iune said:
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.
Click to expand...
Click to collapse
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.
blackhawk said:
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.
Click to expand...
Click to collapse
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help
Iune said:
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help
Click to expand...
Click to collapse
Yay! Well done. So many settings...
Traditionally a hard reboot is killing the power to the mobo... I believe, or maybe I just watched too many sci-fi movies You do it by holding the power button (or combination of buttons) down for 20-30 seconds.
On cams and older phones you simply remove the battery for a few seconds. It clears any volatile memory settings in the chipsets or semiconductors by cutting to power to everything.