So I've been having this issue for about a week now. All the apps installed on my phones SD card once I reboot are not loading up. I know the data is still there because the first time that it happened I spent the better part of day freaking out thinking everything was gone gone. At some point I thought of checking of the data by plugging in into the computer. Turns out (1) all the apps miraculously return (2) I can't mount the SD card anymore (3) I can't unmount the SD card anymore either.
What is the deal? It's kind of annoying to lost everything every time you reboot. I'm not really in the mood to tether my phone each time for the unforeseeable future just to keep everything loaded. Has this happened to anyone before? What should I do?
Cwluc said:
So I've been having this issue for about a week now. All the apps installed on my phones SD card once I reboot are not loading up. I know the data is still there because the first time that it happened I spent the better part of day freaking out thinking everything was gone gone. At some point I thought of checking of the data by plugging in into the computer. Turns out (1) all the apps miraculously return (2) I can't mount the SD card anymore (3) I can't unmount the SD card anymore either.
What is the deal? It's kind of annoying to lost everything every time you reboot. I'm not really in the mood to tether my phone each time for the unforeseeable future just to keep everything loaded. Has this happened to anyone before? What should I do?
Click to expand...
Click to collapse
What do you mean, the icons? I'm going to assume that's what you're referring to, for this reply...
If that's what you meant, icons on the home screen take a few seconds to get themselves drawn, if apps are on SD.
You can switch to a different skin then switch back to your original skin, to get them to redraw. Or delete/reposition them one at a time. It's a workaround, but changing the skin temporarily is faster.
It's a sense bug, I'm pretty sure.
Doesn't happen if apps are installed on the phones internal storage, so until they fix it, move your apps onto internal storage, if you don't want to deal with this each time you reboot. They run faster if they're not on your SD anyway.
Unless you have waaaay more apps than you really need, of course.
Sorry should've been a little more specific. The shortcuts on my home screen are all no longer working and I'm well aware of how long it takes for sense to load them up on startup but even when I go to display all apps it only displays the apps on internal storage. In fact each and every app on the card (in the apps settings) has a funny icon that has a little "sd" on it now and just says computing and will not load.
And since writing this I can no longer get the phone to load any apps from the sd card by tethering it to the computer. It's still accessible - just downloaded today's song from amazon and played it - but apps on it are almost like they're gone.
This happens to me sometimes too. But usually when it happens to me I can go into Settings - Applications - Manage Applications and move the troublesome app to internal storage, and then it's fine. It never completely disappears.
It might do you some good to reformat your SD card. Move everything off of it first, then format it, then put everything back on.
Is it the stock 8GB SD card, or a different one?
homeslice976 said:
This happens to me sometimes too. But usually when it happens to me I can go into Settings - Applications - Manage Applications and move the troublesome app to internal storage, and then it's fine. It never completely disappears.
It might do you some good to reformat your SD card. Move everything off of it first, then format it, then put everything back on.
Click to expand...
Click to collapse
Sold, since I can no longer access the SD card and I've got nothing to listen to at work...
zuriken said:
Is it the stock 8GB SD card, or a different one?
Click to expand...
Click to collapse
Yup.
@homeslice976 copied, formatted (made sure it was FAT32), copied everything back and no dice. Same symptoms, Apps will not load.
@zuriken I don't know why you asked about the stock SD card or not, do you think it needs to be replaced? It's only been since February.
Cwluc said:
@homeslice976 copied, formatted (made sure it was FAT32), copied everything back and no dice. Same symptoms, Apps will not load.
@zuriken I don't know why you asked about the stock SD card or not, do you think it needs to be replaced? It's only been since February.
Click to expand...
Click to collapse
Did you do a full, not quick format? Scan for bad sectors/errors?
Scott_S said:
Did you do a full, not quick format? Scan for bad sectors/errors?
Click to expand...
Click to collapse
full format, chkdsk /f, still nothing though. This is honestly getting to the point where I'm tempted to switch to another phone. Why can't I access my stuff?
Another new bonus, every time I get some sort of alert it now plays random MP3s from the SD card. What is going on...
Cwluc said:
full format, chkdsk /f, still nothing though. This is honestly getting to the point where I'm tempted to switch to another phone. Why can't I access my stuff?
Another new bonus, every time I get some sort of alert it now plays random MP3s from the SD card. What is going on...
Click to expand...
Click to collapse
I'd try a brand new, good quality SD card before resorting to switching phones.
Have you flashed any custom roms or anything? I didn't see you mention either way.
Scott_S said:
I'd try a brand new, good quality SD card before resorting to switching phones.
Have you flashed any custom roms or anything? I didn't see you mention either way.
Click to expand...
Click to collapse
It's gonna be a little while until I can try a new SD card but I'll get back to you.
The only ROM I loaded was the one to originally root that removed the uploading cap from ATT.
I also solved where the random sounds were coming from apparently it doesn't want to play my selected theme and no matter what I do the only one that works is the original HTC default 2010 one or if I download any only the Celesta theme plays... I have a sinking feeling that copying all this funky data isn't going to resolve anything but I'll give it a go.
Cwluc said:
It's gonna be a little while until I can try a new SD card but I'll get back to you.
The only ROM I loaded was the one to originally root that removed the uploading cap from ATT.
I also solved where the random sounds were coming from apparently it doesn't want to play my selected theme and no matter what I do the only one that works is the original HTC default 2010 one or if I download any only the Celesta theme plays... I have a sinking feeling that copying all this funky data isn't going to resolve anything but I'll give it a go.
Click to expand...
Click to collapse
Good luck.
Since you haven't been messing with multiple roms and such, I don't know what else it could be, other than the SD card taking a dump.
I have some problems with my SD card on a THL T100s running a custom Kitkat 4.4.2 ROM.
I recently noticed that Android didn't see my SD anymore. I thought it was corrupted, so I put in on my pc and fixed file system and all. It didn't work. I tried with another SD, formatted it, but Android either didn't see the card at all, or say it was empty/corrupted. Then i booted into TWRP recovery mode to see if it was some software misconfiguration issue. TWRP saw the SD, so I rebooted and finally Android could read the card. Then something very strange started to happen. In a minute or so, my file explorer that previously could read and write on the SD, showed an empty folder instead, and no read or write operations could be performed anymore. Whenever I reboot, sometimes TWRP and/or Android can read/write on the SD card, sometimes not, and when it does it stops in a few minutes. Unmounting and remounting the SD from Settings->Memory result in a "Empty/Corrupted SD card" notification. I even hopelessly tried to wipe cache and dalvik cache (resulting in an annoying "Upgrading Android" at every boot)
I tried to logcat since boot, but honestly I spent all day long trying to figuring out what happens to no avail. I'm no expert and the logcats are huge: filtering only errors, or "sdcard1", "Volume", "Vold*" (which seemed to be related to the sdcard) didn't help me. I'm afraid it is a harware failure and that I can't do much about it.
Can anyone help me to search for the right things in logcats or has anyone else have an idea about what might happen? Any other suggestions?
I'll post a logcat if necessary but even filtering them out there are several hundreds if not thousands rows.
Thanks.
Hi
Welcome to XDA Assist.
Check this thread to know the basics of logcat .
http://forum.xda-developers.com/showthread.php?t=2274119
Though ,you are pretty much right . vold service manages SD card and volumes mounted such a SD card. And most probably your hardware is failing . Or the slot can't read the card properly.
A good way is to clean the contacts with isopropyl alcohol or some other cleaner. Dab some on tissue and clean it gently. You can also use a pencil eraser to clean contacts gently.
If you have any other issues ,you can sign up on forums and post in general Q/A
http://forum.xda-developers.com/android/help
Have a good day !
Just to add to this, Google has decided to limit sd card access in KitKat and Lollipop. You can also seek an app on Google Play called Sdfix which may be resolve the issue you are having. Also contact the developers of the custom ROMs you are using to see if they incorporated the known fix in their ROMs.
Thanks for the replies. I'll try to clean the contacts though they look pretty clean to me. I know about new Android restrictions, but I have root and the right permissions set. Previously it worked indeed.
I'm sure it probably is hardware related since a few days ago I had the phone repaired due to a broken micro USB port, and now sometimes even the camera can't connect. Perhaps the phone had been mounted incorrectly. I tried to dismantle it myself, but I can't see anything strange or out of place. A little pressure near the camera seemed to solve that problem. The micro SD slot isn't anywhere near the micro USB one, so this seemed strange to me. I hope the repairman didn't solder any circuitry it shouldn't.
If I don't solve with the cleaning I'll bring the phone back to him to see if he can handle that.
Thanks again
This is a strange one for me. Stumped. Been working on it all night, no improvement. New one for me, long-ish description (with detail), but a TL;DR too.
Last night I applied the 1.3 OTA for the K1. Being my K1 was rooted, I followed the process I have always followed by restoring the system images to stock, applying the OTA via recovery, then re-rooting. Process:
Shutdown tablet
Swap married/paired SD card with temp SD containing flashables (OTA, SuperSU)
Boot to bootloader, fastboot (re)flash tablet's current system images (recovery was already stock but flashed again for good measure, boot, system, blob -> staging)
Boot to custom recovery using fastboot boot -recovery image-
Flash OTA from temp SD, wipe caches, apply SuperSU
Shutdown, replace married SD, boot, enjoy life
This time I didn't immediately apply SuperSU, as I thought I'd flash 1.3 and let it go fully stock a bit to ensure no other updates were pending (nVidia seems to like incremental updates, so flashing to 1.1 won't give you an OTA to 1.3 directly, but to 1.2 first, then 1.3). I've also followed this process with the K1 for every update since 1.1 without a hitch, and although there haven't been many OTAs, it has still worked perfectly every time. Because of this and because I've done this a billion times on a million different devices with zero issues ever, I didn't take a backup before the update. Woe is me.
When I rebooted this time after flashing the OTA (no root), it booted up seemingly fine to the "Android is upgrading" modal, so I left the tablet alone for a bit to let it do its thing. When I came back, the tablet was HOT, was at a completely black screen save for the status bar (no wallpaper/launcher besides the clock/wifi icon which showed a connection, that's it). I tried to interact with it and couldn't (totally locked up, also a first), then it rebooted on its own. Subsequent times, during troubleshooting, I noticed that it's totally locked -- NOTHING responds, unless you can get to it before it reboots and hold power to kill it.
First thought was a bad flash. NBD, so went back and reflashed, double-checking everything and carefully following the same process. No dice. I did use a newer TWRP recovery from April of this year initially, which was a recommended version for the K1 specifically, rather than a really buggy but working one from last year. To test I did I try using the older TWRP on one of the next flashes thinking maybe the new one borked the partitions, or at least wasn't writing the partitions/symlinks properly (and the older one was the TWRP I had used for previous updates, with no issues). But, no change..
It took me a long time and many reflashes and cache formatting and digging before I realized if I pulled the married SD out, it booted just fine. Weird, and gets weirder. After leaving the married SD out and booting, and having the tablet working just as expected (except for missing the SD), Android shows a notification saying to reinsert the married SD. Once the married SD is reinserted, things seem OK for a few seconds before the whole system goes unresponsive again, heats up, and begins bootlooping. Before it sh'ts the bed, the message on the status notification asking to reinsert the married SD card doesn't change, but in the Storage settings, it shows it's "checking" the card, followed by a sudden hot death spiral into non-function. If you select the SD from Storage settings to take a look around its contents, the tablet basically locks up instantly. Inserting other SDs works fine (for the most part, still some other weirdness), it's just the married SD that totally kills the device without fail.
Obviously I'd like to avoid wiping and reinstalling the whole thing if it can be avoided, not just because my dumb ass didn't take a backup so I'd lose a ton of app/game data, but also because it's a just huge pain. A lot of the sites that offered "fixes" for these types of problems say to just wipe data, which is not a solution and is the nuclear option (like telling someone to to replace a car due to a flat tire).
Ideas? Is this as simple as recreating some symlinks that somehow disappeared and refuse to come back after all the flashes, and if so, how? I've been looking for hours and haven't found anyone with this particular issue or steps to correct.
[size=+2]TL;DR[/size]: Applied K1 1.3 OTA, married/paired SD card is no longer recognized, causes tablet to hard-lock and enter bootloop when inserted (other SDs do not cause this issue).
Other potentially pertinent bits:
Initial flash was dirty, second and subsequent flashes included a wipe of system first
Installed 1.2 images first, then tried going back to 1.1.1 and taking nVidia's OTAs to get back up to 1.3
1.1.1 does not recognize the married SD but doesn't kill the tablet, while 1.2 and 1.3 kill the tablet when the SD is inserted
When married SD is not inserted, using shell or ES Explorer or otherwise, not seeing a /storage/emulated/0, or /sdcard, or /data/media, or any other familiar storage related directories
When married SD is inserted, it dies too fast to look around much or try to do anything to check/fix the SD itself
/storage is totally empty except for a folder called "self", and inserting a working SD creates a directory under /storage labeled with the SD's serial number (not an emulated/0 directory or anything similar)
Not sure if this is expected behavior since the SD was married -- do those directories/symlinks live on the SD now since it's married, and won't show up in the device filesystem until everything's properly mounted?
Tried following these steps, which although written in the N5 forum, still seemed relevant.. no change
Tried the referenced SD permissions update with the card inserted and not, in case of the directories it touches only being visible/available with the card inserted, no change
Noticed even within TWRP, going to the "mount" menu seemed flaky, labored, and didn't show what I expected, but this could be because there isn't a "proper" or official custom recovery for the K1 yet and things are just buggy
ES File Manager still seems to think an /sdcard directory exists and tries to open to it, and just spins in an open directory.. as expected
Going to /data in ES File Manager shows me an empty directory with a message stating the SD card is missing
Using a working, freshly formatted SD in the tablet and trying to point Titanium to a directory on the SD gives me messages about the directory being unwritable, no matter where I go on the SD
Titanium's app permissions (including r/w storage) are proper, SD is not write protected (freshly formatted on the tablet)
Tried using SDFix, which also gave me an error re: "platform permission file is invalid"
There's probably more I'm missing, but can't remember it all -- I have tried everything, I feel like, and have been at it for 13 hours now (apologies if this is written spotty, fighting to keep my eyes open).
So is it totally hosed, or is this recoverable? Is there a way to fix the tablet to recognize the SD, or fix the SD itself if that's the issue (but I'd wonder how it got corrupted in the first place, since it has only been removed once fully powered down)? Is there at least a way to check the married SD for corruption or issues?
Thoughts?
EDIT: Formatting
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
GtrCraft said:
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
Click to expand...
Click to collapse
And why is that? When the OS is running, sure, you can't. It'd be equivalent to just deleting /data while the OS was running. It seems pretty unlikely that removing and reinserting it while it's powered off, though, would make it suddenly unable to read the SD or forget its pairing. Adopted storage is "married" to the device via a generated encryption key, which is stored on the device's internal storage. It's all handled in software, not like the SD fuses itself to the device Removing the SD (while off) would not (and does not) break this pairing method, unless the internal storage or SD decides to spontaneously erase itself while the device was off.
The process outlined is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
grivad said:
When the OS is running, sure. Maybe that is the case, but it seems pretty unlikely that removing and reinserting it while it's powered off would make it spontaneously unable to read the SD or forget its pairing.
This is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
Click to expand...
Click to collapse
Still, you better off formatting it
Sent from my XT1562 using XDA Labs
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
lafester said:
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Cool.
Regarding the YOU CAN'T REMOVE IT belief (which is categorically false), if this were a serious issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Also that I cannot write to a working SD with Titanium. These things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
grivad said:
Cool.
Regarding the DON'T REMOVE IT belief, if this were an issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Both of those things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
Click to expand...
Click to collapse
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
GtrCraft said:
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
Click to expand...
Click to collapse
It's not that I don't believe the solution, I don't believe the premise because it is provably false There is absolutely nothing unsafe about ejecting adopted storage, which is why the OS lets you do it, even while it's running and using the storage. Even less of a risk if the thing is off. The "solution" offered wasn't much of a solution, and in the OP it was stated that I wasn't looking for that answer (already know that's an option, which is why I mentioned in the OP).
I appreciate you trying to help, but simply saying "format it", again, is the nuclear option. Not what I'm looking for. Either information as to what's happening (if anyone else has dealt with this) with a justification as to why it's irrepairable, or things to try based on the information I gave. Spending a lot of time being thorough just to get a "format it" response, to be frank, isn't very helpful It's like telling someone to reinstall their entire OS because they can't figure out how to install a driver, or to raze their house because a painting fell off the wall.
The SD didn't spontaneously corrupt itself in the 5 mins it was out of the device. No gamma bursts or EM storms in my area that I know of, either Because the only thing that changed was installing the OTA, this really seems to be a software problem (albeit a bit bizarre, to me) so it should be fixable via software. The fact it's pegging the CPU when the SD is inserted makes me wonder if it's getting stuck in a loop, maybe due to partition changes (looking for a file or partition it can't find). If that's the case, again, that should be fixable via software, with instruction from someone knowledgeable on how the Android FS and mounts work.
Again thanks for trying to help. I know formatting is an option (the easiest one), but I'm looking for just that -- options.
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
lafester said:
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
Click to expand...
Click to collapse
True, the SD was out, however this is how I've both read to do it in multiple places, and how I've applied every OTA so far without issue (with the same adopted SD every time). As part of my troubleshooting, I did try flashing the OTA with the adopted SD inserted, though. It didn't make a difference.
I did try downgrading.. When I started the tablet was on 1.2, OTAd to 1.3. Every time I'd reflash I would do so to 1.2. I did try flashing down to 1.1.1 (the "recovery OS image") and OTAing back up, and like I mentioned that allowed me to use the device with the SD inserted, but it wouldn't recognize it as the adopted storage.. just kinda did nothing, as if the card wasn't inserted at all. This happened in 1.2 as well (OTAd from 1.1.1), and once it got up to 1.3 from 1.2 it all started all over again.
I'm creating an image of the SD right now (using dd) to try restoring it to another SD. I've read that doing this preserves the pairing information, so if it's a bad SD, this would hopefully fix it. I also wanted to try flashing directly to 1.3, but the images aren't available yet Only 1.2 and 1.1.1..
Honestly I would divorce the card before update then redo it after this whole method is janky anyway no reason to remap the data links like they do and all it would be required is if app devs were forced to comply with a data space method... The feature of installing to SD card should be available to non married storage.
Old thread, haven't been on in a while, but thought I'd post an update.
The problem ended up being a hardware issue. I contacted nVidia after absolutely nothing I tried resolved the issue (different SDs, different OS versions, different process to set up, etc.). I simply explained the problems I was having and my troubleshooting attempts, asked if it was a known issue or if they had any suggestions, and they immediately responded with RMA info, no questions asked. The replacement turnaround time was very fast (within a week IIRC), and the new K1 has had zero issues.
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.