Couldn't get the ext. sd card to mount on pc. Weird thing is the ext. sd is available on yumaporn. Searched google and found out that you can use multi mount app @store but I would still prefer a native solution to a widget based mount (which can get unresponsive like, most of the times) on the Paranoid.
Any solutions?
I look forward to hearing an answer, on this, as well. Some forums for other ROMs have talked about tweaking build.prop and other files and getting it to work, but so far, none of those tweaks have worked for me yet.
My inability to get it working could easily be operator error, however.
Related
Hi
I am getting an error mounting sdcard2. Is there some setup needed for it to be mounted or is it automatic after insert?
thanks
odd...I'm having the same issue but in status, its showing No SD Card. I popped in two working microSD that was used on my rooted G1 and both show up fine when I plug it and turn on my old G1 phone....any suggestions or did i get a bad G Tablet
Assuming you are using TnT (Lite), it should be automatic. I have a 32GB microSD and it is seen on boot, and I can remove and reinsert with no issues.
We know that VOLD mounts the device, and that there's something in the framework that controls this. gojimi managed to replicate this in the VEGAn build, for example.
As to why your cards aren't working, the only things I can think of that either the GTab is finicky with certain cards, or that it's not formatted as FAT32. I'm going on the assumption that the former is more likely.
If you have access to ADB, you might want to look into the logcat logs to see if there are any errors when the device is inserted.
hmm wierd. i was using zpad and did not see an option to mount the card. i changed to tntlite now i can mount and see it.
All of a sudden apps on storage card fail to load.
After a few reboots they reappear at random, but disappear again on reset.
Did not have that problem with stock, but after flashing Infused 1.14 (and on) the issue appears even with the (rooted) stock rom.
Any ideas?
I am trying to determine if I need to return and replace the phone before I lose the option.
Thank you in advance.
Answering the question by myself, in case others encounter the same issue.
The external card had something corrupted, and when the system was mounting it, all mess ensued.
Backed up all the data and reformatted.
System appears ok for now
I just had this same problem or at least something very similar to it. Initially I thought it was the 32GB SD card being too big since I read Android had a 16GB external card limit. But those posts were from a year ago and when I searched deeper I read that 32GB cards were being use without size problems now. There was one issue that seemed to affect some people and that was that android could have problems formatting a card that big and that's how I installed it in my Infuse initially- I let the Infuse format it, then popped in in my Macbook Pro (in OSX) to copy over the contents from the previous 8G card. I believe I have hidden files set to show, so I should be copying over everything- though, could this method of upgrading the card be a problem too?
It worked for a couple days, but last night during a reboot I tried to access the app tray and didn't know the card was still being scanned. It froze and I couldn't get past the secondary media scan after many tries. I didn't realize that apps were being automatically installed to the card.
Anyway, I was gonna return the card, but after reading your post, I'm thinking again about corruption due to poor formatting as the problem, so I'll try it again when I get home. Thanks for your post. I really want to be able to use this larger card so I'm keeping my fingers crossed this will solve the problem.
BTW, how did you format the card? I have Win7 x64Pro on my MBP as well if I need to use windows, but did you use FAT, FAT32, ExFat? I'm still a 'droid noob ;P. Thanks again!
-- Infuse 4G Rooted with stock ROM
Hi after having to switch my phone off, when I turned it on again it appears that all the apps I moved to the SD card are no longer there. I have just spent some time downloading them from the market again.
Question is why has this happened and how do I stop it from happening again
Thanks in advance
Solution
Hi Nexus.
I think you'll find that the apps still exist, they're just fragmented on the SD
card. This has happened to me plenty of times.
I've found it's only apps that are installed on the SD card and it's never
happened with apps on the phone's internal ROM.
A good way to check is to go into: Settings- Applications- Manage applications-
then tap the SD card tab. That list shows all of your apps installed on the SD
card. I found that when apps here got fragmented/corrupt they didn't show their
original app icon. Instead they showed the stock android app icon. This is a good
way to tell if the missing apps in question are still there but are just fragmented.
The way to solve this, the way that's worked for me, is to plug the phone into a
pc and mount the SD card as a disk. Then on the PC access the SD card via
explorer and right click- properties- tools- then click de-fragment.
This may take up to 30 mins as it's not as fast as a HDD.
From using this technique my apps have always returned and I can use them
with no problems again.
I've also noticed that this issue only happens if I restart or turn the phone off. I
don't understand what is corrupting the apps as the SD card is mounted
correctly and is the one supplied as standard.
I hope I've helped, and I guess this will save you from re-downloading all of your
apps again.
I'm happy to hear anyone's thoughts/suggestions onto why this is actually
happening in the first place too.
Cheers, Dms
Hi thanks so much for the answer. This has been bugging me for ages and even though I have been searching I have not had any joy solving it until your reply.
As you said it only seems to happen to apps on the sd card, and I would like to know why they are not "persistent" There must be a developer who understands the Android system who can explain why this happens and what you can do to make apps you have on your sd card permanent.
As you said it only happens to me when I re start my phone.
Thanks again for the answer
Hi. It's no problem. Yes I havn't seen anything about this issue being mentioned either.
I'd like to know what's causing it. Whether it's a hardware fault or something in the software.
It's a real pain having to hook it up to my pc to sort it out. Especially when I'm away from a pc, I can't use half of my apps.
Sent from my HTC Desire S using XDA App
As the title says, something seems to be up with my SD card. I figured I'd nose around here before going out to pick up a card reader so I can mess with the darn thing on my computer.
Anyway, before anything else, I'm going to say that I've never had any issues with writing to my SD card since I picked up the Z3--neither on Kitkat nor on Lollipop. I don't even remember having to use the platform.xml fix.
Just today, however, I suddenly got an error when trying to copy some files to my external SD. I was more than a little surprised since, just a few days ago, I was moving files back and forth between the card and the internal memory without any problems. I tried backing something up in Titanium next, and got the infamous insufficient storage space error. I found it really weird but, since it wasn't anything new to me, I tried applying the fix, which didn't solve the issues. I also tried the Play Store app and FolderMount. FolderMount seemed to work so I uninstalled it (which you should be able to do, right?) and restarted my phone, to make sure whatever fixed things stuck. Aaand I ended up right back where I started.
Next, I thought of unmounting and remounting the card in Settings. What I saw there, though, was that the system wasn't detecting the card as mounted at all. I tried using the mount option but all I got was "Preparing SD card... " and nothing after that. Despite that, I could see and access/use everything on the SD card through ES and other apps. I pulled the card out and stuck it back in, and it finally started showing as mounted in Settings, but then everything else (ES and other apps) was showing that there was no SD card. Restarting the phone after that resulted in the original problem.
I've had a number of cards die on me in the past and, so far, I'm not getting any of the symptoms of that yet. If the card is indeed on its deathbed, I wouldn't be surprised either, as it is several years old. If I can, though, I would still rather forego the expense and trouble of getting a new card, so I'm hoping someone can point me in the direction of getting this sorted out.
Thank you!
Dying SD card, SanDisk UHS is so well known to start dying fast...I guess others that use similar components too...
I've been having some problems with the SD card also, and I suspect XZDualrecovery to do some weird stuff to the SD card..
I've been having problems with the SD card being 'damaged' according to the phone. However, if I take it out, and put it back in, it works like a charm again, until i reboot.
This error seems to coincide with XZDualrecovery, seeing that XZDR doesn't work anymore right before the 'damaged' messages.
When reinstalling XZDR, the error doesn't appear after reboot, and the thing is fine again for some time.
I really don't get why this happens though...
Hello everyone, I'm the sad owner of an Osprey terminal (XT1542), it was a gift from my family so I can have a more modern phone and so far it's been more a headache than a good thing.
My problem is that at first I believed it was some random bull**** from the Stock Marshmallow app, using Spotify and trying to download my playlist would end up with my internal storage full because Spotify (and any other app WITH the required permissions to "write" onto the SdCard) couldn't recognize the SD even after it displays it as totally readable, this creates a problem because the camera, the file explorer, even the ADB tool can't write onto the SDCard.
So, after using marshmallow with a 16GB class 10 Kingston SD card I did the following:
Tried every single possible solution to the issue with the vainilla Marshmallow 6.0, that includes formatting the SDcard OUTSIDE the android, different partition size, factory factory reset, nothing.
After failing on that, tried updating marshmallow, Failed, something about the "modem" isn't right on this phone.
So, I did what every XDA user would do, grabbed a brand new Nougat ROM and OGapps mini and installed it on the phone.
I didn't root the phone though....
Failed again, the same issue as before, so "It's the SD CARD YOU MORON" would be the answer here!
Nope. Brand New SDCard replaced with even a newer SDCard (same type) and again, the same issue as before.
As a note if I unmount the SDCard and mount it again via the config>storage option, it becomes "writable" again. For a while...
adb outputs when "push": failed to copy 'log_2017-04-13_OSPREY.txt' to '/storage/4FD8-E1EA/log_2017-04-13_OSPREY.txt': couldn't create file: Read-only file system
So, this leaves us with the simple fact that the issue is... Hardware? Software? Kernel? Maybe if I reset the phone to stock factory fully flashing every single bit of it it would work?
I really need your help in this one guys, thanks for your time.
Greets, let me know if you need any more info or maybe a log on the issue?
Did you REALLY need a poll for this? Seriously?
Did you look for information on this? There are at least a dozen threads on SD card issues on the Moto G 2015 just on XDA, much less the dozens of other threads everywhere else... Here is a quick summary, assuming you have tried clearing the cache partition, factory reset, etc:
50% of the time, it's the SD card itself that is bad, or there is a compatibility issue... Try a different brand, size, speed, etc. The most compatible cards seem to be Samsung EVO+ or EVO Plus series (they are different), PNY Elite series, Lexar 633x or 1000x series, and Sandisk Extreme or Ultra series but again this varies by individual handset. Kingston cards are hit and miss, some people have good luck, others not so much.
40% of the time it's a hardware defect or damage inside the device, nothing you can do but replace the microSD socket which requires micro soldering... Probably best to leave it to professionals.
10% of the time, it's a mixed bag... sometimes a couple layers of scotch tape on the back of the card will help (increases tension on the contact fingers slightly), sometimes it's counterfeit cards (don't kid yourself, this is a HUGE problem, use SD Insight to check), sometimes a U3 card helps, or who knows what else.
The point is, about half the time switching to completely different card fixes the issue, and since microSD card are cheap, especially at the 16GB-32GB card size, so it's a good place to start.
+1
replace card.
frenchiveruti said:
Hello everyone, I'm the sad owner of an Osprey terminal (XT1542), it was a gift from my family so I can have a more modern phone and so far it's been more a headache than a good thing.
My problem is that at first I believed it was some random bull**** from the Stock Marshmallow app, using Spotify and trying to download my playlist would end up with my internal storage full because Spotify (and any other app WITH the required permissions to "write" onto the SdCard) couldn't recognize the SD even after it displays it as totally readable, this creates a problem because the camera, the file explorer, even the ADB tool can't write onto the SDCard.
So, after using marshmallow with a 16GB class 10 Kingston SD card I did the following:
Tried every single possible solution to the issue with the vainilla Marshmallow 6.0, that includes formatting the SDcard OUTSIDE the android, different partition size, factory factory reset, nothing.
After failing on that, tried updating marshmallow, Failed, something about the "modem" isn't right on this phone.
So, I did what every XDA user would do, grabbed a brand new Nougat ROM and OGapps mini and installed it on the phone.
I didn't root the phone though....
Failed again, the same issue as before, so "It's the SD CARD YOU MORON" would be the answer here!
Nope. Brand New SDCard replaced with even a newer SDCard (same type) and again, the same issue as before.
As a note if I unmount the SDCard and mount it again via the config>storage option, it becomes "writable" again. For a while...
adb outputs when "push": failed to copy 'log_2017-04-13_OSPREY.txt' to '/storage/4FD8-E1EA/log_2017-04-13_OSPREY.txt': couldn't create file: Read-only file system
So, this leaves us with the simple fact that the issue is... Hardware? Software? Kernel? Maybe if I reset the phone to stock factory fully flashing every single bit of it it would work?
I really need your help in this one guys, thanks for your time.
Greets, let me know if you need any more info or maybe a log on the issue?
Click to expand...
Click to collapse
I'm in the same boat as you. Tried lots of different brand new SD cards from different vendors, every time the same bug appears. So the only working solution is STICK TO ANDROID 5.x. For some reason Motorola has screwed up the sdcard driver in the kernel, maybe because introducing new fancy features on 6.x and above. I highly suggest you to install CM 12 and keep it on your phone as long as possible. Unfortunately, there's nothing you can do with it, unless you are a pro kernel developer.
Maybe this will help you.
reactorcoremeltdown said:
I'm in the same boat as you. Tried lots of different brand new SD cards from different vendors, every time the same bug appears. So the only working solution is STICK TO ANDROID 5.x. For some reason Motorola has screwed up the sdcard driver in the kernel, maybe because introducing new fancy features on 6.x and above. I highly suggest you to install CM 12 and keep it on your phone as long as possible. Unfortunately, there's nothing you can do with it, unless you are a pro kernel developer.
Maybe this will help you.
Click to expand...
Click to collapse
I finally found someone with the same problem as me! (well, that's bad news for you and me bad at least I'm not the only one with this problem)
So, you tried everything like me and yet no way to make it work? I couldn't test a different "brand" of SDCard but I did try different ones and checked if they were fake ones and still I have the same annoying problem. Damn...
I think yeah I'll have to go down to an android 5 if there's no way to fix this.
I'm wondering if a custom kernel can solve this, but it's really difficult to know the "why" is this happening, and the logcat doesn't help that much to be honest, at least not from the side of knowing where or what to read that could be causing the issue.