Energyrom / MaxManilla / Sense 2.5
I first noticed I had an issue with Voice recorder. I get an error regarding the inability to save the file to the SD card because I dont have one, or I dont have enough space. This has been happening for the last 3 or 4 rom versions.
Nobody else had reported this.. (That I can find) So it's just me.
I noticed finally that when I go to the settings tab in sense, and choose "SD card and Phone Storage" The SD card section shows 0.00 mb.
I think I understand now.. Something in Sense thinks I have no SD card.
My music works fine from SD using the music tab, Windows memory sees the SD, applications and all that work fine. The only 2 issues I seem to have is that sense settings show 0.00mb and voice recorder fails.
Any ideas?
I dont know if it's Sense, as much as it's some HTC software.. Hence the reason Audio Recorder sees no SD card.
I switched cards as a test with my brother-in-law running the same rom on his VZW TP2, and his sense saw my card fine. Mine phone did NOT see his. So it's not the card.
I had this problem on an HTC HD2 (TMO USA). I went through every step you did and tried formatting an SD card anyhow just to see if the process would trigger something to recognize the card, no go.
Finally I backed everything up and did a factory reset. That solved the problem and now my SD card is recognized.
Got it! - Almost..
OK.. Figured it out.
The SD is fine.. Only Sense does not see it.
The cause is when I use HTC Network Folder, or Resco Explorer and Make the "Network" Folder visible to applications.
I now have 3 choices when I install apps, or when I save files.
Main memory
Network
Storage Card.
Sense is clearly looking at the second item for SD card stats.
Enabling the network folder makes the Storage Card the 3rd item.
So.. I figured it out.. but anyone have an idea to tell sense where to look??
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.
I have ran
Slimbean
Liquid smooth
Carbon
Root box
All of them I have issues with the ringtones reverting back to default after I change them. Anyone else having issues or know of what I can try to fix it?
So no one else is having issues like this?
I might have found the problem... I think I might have found the issue. I store my ring tonnes on SD card. I moved them to the internal storage..... let s see if that fixes the issue.
I have my ringtones on the SD card and they work fine.
So far so good. For me.. I never had this issue until recently...
Spoke to soon... Just had it reset.....
Castanoff said:
I might have found the problem... I think I might have found the issue. I store my ring tonnes on SD card. I moved them to the internal storage..... let s see if that fixes the issue.
Click to expand...
Click to collapse
I've had this problem once and a while due to storing the ringtone on the SD card (at least that was my assumption as to the cause). Pretty sure what's happening is that it's taking the phone longer to verify the SD card (or whatever it does during bootup) and extends past the time during which the ringtone is loaded. Since the SD card hasn't finished loading, the ringtone can't be found.
I wonder if faster sd cards would solve the problem (don't have any others to try or I would check this out) . . .
This time I found the culprit.. I had a audiomanager app that kept getting installed via titanium backup. After removing the app it has stayed.
A little concerned so far. Won't recognize my ringtones. Won't run UC Browser. Some problems with SD cards.
Gonna give it a couple more days, but I've had phones that inspired more confidence.
And I do realize some challenges may come from running Marshmallow, not really being HTC's fault at all.
What do you mean by not recognizing your ringtones? And UC browser has a problem with Marshmallow, so it's not the phone. Can you elaborate 'some problems with SD cards'?
I mean I put notification and ringtone .ogg files on the phone and it will list them in some apps but not in others. But when I select one of my notification sounds even in the apps that show them on the list, the selected sound shown in the app is Firefly. The ringtone initially works if I can select it, even in the apps that display Firefly, but after a reboot they seem to stop working until reselected.
The phone's internet speed is very good, but very laggy/stutters when scrolling in browsers. Tried Chrome and Dolphin, both slower than my G2.
Still working out the SD issues. Phone says my SD card is slow. I do not have spec for this particular card, so I don't know if that's true. It's about a year old, so it's surely slower than the newest cards you can buy today.
The first card I tried got that slow warning but the class 10 Sandisk didn't and is working like a champ.
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.