Hi everybody,
I open this thread because I'm desperate. The Galaxy S7 is my 4th Android device and I had a problem of corrupted photos at least with the 3 last devices. I bought the S7 partly with the hope of say goodbye to this fuc**** problem.
But here we are, I have the S7 since a month now and it gave me already tons of corrupted photos. On my previous Xpiera devices I use various AOSP ROM and now I use King ROM on my S7 and the problem frequency still exactly the same. (I was expecting a solution by using stock based ROM.)
Speaking of the problem, here is the descption of it:
- About 1 out of 20 times (to be nice) I got corrupted photos with a varible sized grey rectangle. (See 2nd picture enclosed)
- That's new with the S7: sometimes there is no grey rectangle but a big problem of colors. (See 1st picture enclosed - I just add blue rectangles over faces)
I hope you have ideas about my problem. :fingers-crossed:
I don't understand why this problem still persists over different devices. I also already tried few microSD card.
Don't hesitate to share any idea or ask me for details if you don't understand my average English.
Thanks in advance! :good:
Pretty weird... did you try shoot with selfiestick? I guess you`ve high EM field emitted by your hands.
P.S. I`m not kidding at all!
Have you tried a different ROM? formatted your phone and /data in TWRP?
kornelius1982 said:
Pretty weird... did you try shoot with selfiestick? I guess you`ve high EM field emitted by your hands.
P.S. I`m not kidding at all!
Click to expand...
Click to collapse
Hi and thanks for this (surprising) idea. I guess EM meanselectromagnetic.
I didn't have a selfiestick but I just tried to take photos with a big magnet next to my phone and all photos were ok. So EM doesn't seem to produce corrupted photos.
It's a ramdom bug, sometimes all is ok for almost few weeks and then (for example yesterday) I got 4 corrupted photos in the 15 photos I took.
There is some threads on internet where people complain about grey rectangles in there photos but nobody seems to found a solution.
I have to say that I'm a bit frustrated to pay over 500€ for a flagship smartphone and still have this kind of issues...
ha3kser said:
Have you tried a different ROM? formatted your phone and /data in TWRP?
Click to expand...
Click to collapse
I've also tied SuperMan ROM but I don't stay on it enougth time to test that.
I always format my phone(s) before flashing. I never make dirtyflash.
Did you switch to King ROM because stock gave you the same problems? If not, you might want to give stockTouchwiz a try
Neorpowa said:
Did you switch to King ROM because stock gave you the same problems? If not, you might want to give stockTouchwiz a try
Click to expand...
Click to collapse
No I switched to Stock based Custom ROM because I just can't support Stock ROM.
It's not conceivable that I use the stock Samsung ROM daily, I prefer sell my phone than have to use this kind of heavy and no-functional ROM. I would prefer a AOSP based ROM but Samsung high end devices doesn't offer that.
Nevermind! :silly:
I sould try a stock ROM for a couple of days but no more. Maybe next weekend.
Thibou said:
No I switched to Stock based Custom ROM because I just can't support Stock ROM.
It's not conceivable that I use the stock Samsung ROM daily, I prefer sell my phone than have to use this kind of heavy and no-functional ROM. I would prefer a AOSP based ROM but Samsung high end devices doesn't offer that.
Nevermind! :silly:
I sould try a stock ROM for a couple of days but no more. Maybe next weekend.
Click to expand...
Click to collapse
Allright, hopefully (in your case) it doesn't change anything and thus you won't have to switch to stoxk
Sent from my Galaxy S7 Edge using XDA Labs
Are you using the same SD card in each device? It is possible that the card is causing the issues with the files.
crizyal said:
Are you using the same SD card in each device? It is possible that the card is causing the issues with the files.
Click to expand...
Click to collapse
This is exactly what I thought.
Try to save the photos in phone memory, not in the external SD card and see if this still give you corrupted photos. If not, then the SD card is most likely corrupt (should not be repaired with just a format. Buy a new one instead)
Had exactly the same problem of corrupted images. Even worse, my phone just crashed on the gallery app, requiring reboot with power+volume down.
Remove the sd card. The sd card is causing it, either get a good new one, or use the internal memory of the phone.
Havn't had a corrupted image/video or crash since i removed it, and in general its faster too.
I used at least 3 different sd cards in my phones.
First I used a 16GB card with no precise specifications and I don't remember if I had this problem of corrupted pictures with this card.
Then I bought a 32GB Samsung card with (in theory) a reading speed of 70MB/s and a writing speed of 20MB/s. I used this card in my 2nd and 3rd phone and I get corrupted pictures with it.
Currently I use a Lexar 64GB card with real speeds of 43MB/s in reading and 36MB/s in writing. I used this card in my 3rd and 4th (the S7) phone and obviously I get corrupted pictures with it.
Did you think that the Lexar's speeds are too low?
It's strange because I can shoot over 100 pictures in burst mode or 4k video without any problem.
Concerning internal storage, I bought the S7 in part because I want to save my datas in external storage. I want to be able to get my datas even if I crash my phone.
So I will not adopt internal saving as a solution.
You're not using an aftermarket flip case with a magnetic latch on it are you?
cheetah2k said:
You're not using an aftermarket flip case with a magnetic latch on it are you?
Click to expand...
Click to collapse
No I use a silicon case without magnet.
I just noticed that my Lexar 64GB card gives a reading speed of 41MB/s and a writing speed of 24MB/s when I use "A1 SD Bench" app. So my card seems slower in my phone than in my laptop benchmarck.
I don't think 24MB/s is realy too low but it is 10MB/s less than laptop benchmarck.
Thibou said:
...
So I will not adopt internal saving as a solution.
Click to expand...
Click to collapse
Of cause not, but to narrow the problem you have to know if it has something to do with ROM, camera, SD card, etc.
At least you can try! Maybe after checking the files aer ok, you can move them to SD card. That would be another test if SD card works in the device. Maybe the connection is partly broken?
Bright.Light said:
Of cause not, but to narrow the problem you have to know if it has something to do with ROM, camera, SD card, etc.
At least you can try! Maybe after checking the files aer ok, you can move them to SD card. That would be another test if SD card works in the device. Maybe the connection is partly broken?
Click to expand...
Click to collapse
Oh yes sorry I didn't understood your idea this way.
I just change the saving location setting, we will see what happen in next days. :good:
Related
Hi everyone,
I just wanted to let you know about what I have found out.
A couple days ago my I9505 started to overheat a lot, although it was not used and in my pocket. At first I thought it was the battery, so I switched it off and took the battery pack out, but it turns out it wasn't hot... but the phone was! Especially the upper part (around the camera, and even on the screen side). I waited and restarted the phone. After a while it did it again and my phone rebooted by itself after a few hours, which was a complete surprise: I have been running the last stable version of SlimBean, which is awesome and really stable for the past couple of months (the reason why although I have tried some KK based rom I ended up going back to 4.3).
Anyway, I though maybe something was wrong with my settings and I decided I would test a few KitKat ROMs, and so I did:
- SlimKat
- OmniRom
- CarbonRom
- AOKP
- CM11
- and a few more...
With all of them, I experienced the same issue. And I had them all for a few hours, because I know at the beginning the phone always retrieves data and apps from google servers, so I figured it was bound to heat, but not that much! And the random reboots happened in all of them.
This morning, I was ready to flash back to a stock ROM to have the phone serviced (I have knox tripped but I don't care, I don't think they would mess around with me about it here in Europe, at least from what I've heard, and anyway, I'd just tell them that Kies did it ), when I realised that Hey! the day before it started, I was unable to copy/paste all the data from my 32GB microSD card to my computer using the USB cable. I would systematically get an error saying that the device has been disconnected from the computer. I had even wondered if my USB cable was damaged, but seeing that the phone charged alright, I did not pay too much attention to it.
I started to investigate the card and retested some ROMs I had tested previously. This time I would not connect, but I did try with and without the card, and BINGO! every time I put the card in, it would overheat.
I then tested my card with an adapter in my computer, and there seemed to be something wrong with it, because even then the copy operation would hang! So I formatted the card (after I had backed up everything I could), and put it into the phone, where I formatted it again with the phone. Now the card has been (albeit empty) for a few hours in the phone, and no overheating or random reboot in sight (running the latest stable SlimKat).
So if your phone starts to overheat, especially the upper part, check what happens when you remove the SD card.
Hope I'll have helped someone with this. If you don't hear more about me in this thread, it means everything's alright. I'll start re-loading things on the same microSD card. I'll see if it is still faulty or if the phone heats up. If it does, I'll try with another microSD and see if it does the same.
Cheers!
Fa
Do tell me if the micro sd card is the problem. I have this overheating issue since a year and haven't been able to sove it. Yet. But i remember trying to rovercome this issue by the micro sd csrd method, it hadn't worked..
Anyways, this issue with s4 is too common, i know 10-15 people with the same issue, so i think its a hardware fault..
Sent from my GT-I9500 using xda premium
Thanks for this, very useful advice. Just recently I was having some issues with my phone not writing to my SD card and the card inexplicably filling up with data. It turned out to be corrupted data in the Android folder, so I backed up my stuff, formatted the card etc and that fixed it (as well as freeing up about 6gb of space on the card)
After reading your post it occurred to me that corrupted data may have been causing overheating in your phone, due to the card constantly being read over and over.
I didn't experience any overheating myself but it could well be the same cause. Either way, definitely worth checking if you're having overheating issues.
Very interesting. I for one reformat my SDcard every 2 to 3 months. Just a simple maintenance that i like to do. This is something good to keep in mind and thank you for sharing mate.
armaan.ag said:
Do tell me if the micro sd card is the problem. I have this overheating issue since a year and haven't been able to sove it. Yet. But i remember trying to rovercome this issue by the micro sd csrd method, it hadn't worked..
Anyways, this issue with s4 is too common, i know 10-15 people with the same issue, so i think its a hardware fault..
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
So! Some more info on this (just in case someone's interested), but first FYI Armaan.ag, the card seemed to be the issue.
I had another microSD card of the same capacity, so I copied every single file that was on the faulty card to my computer, and I noticed there were two mp3 files that were in fact not really mp3 files, but rather some junk that the phone must have created at some point.
I deleted these two files and copied all the rest to the new card, and it works just fine. So at least it's not a hardware issue on the phone: it reads the card content fine and does not overheat (well, IMHO a phone should not overheat when it encounters a corrupted file, but that's another issue)
As for the first (faulty) card, I have formatted it (full format) and checked it for errors. Windows tells me it is fine. I'm now copying all files back to it, I'll test it when it's ready. If it still crashes my phone, then I'll try on my wife's phone (I9300) and see what it does before I return it for exchange (the card is not even 3 months old).
Cheers!
Fa
fabecoool said:
(well, IMHO a phone should not overheat when it encounters a corrupted file, but that's another issue)
Click to expand...
Click to collapse
When the OS is indexing files on the sd card the CPU will be working, if there is corrupted data on the card, it can interfere with the data indexing and cause the OS to read the card over and over. This will keep the CPU active for longer than it needs to be, and when the CPU is active for extended periods of time it can cause overheating.
Alternatively, the overheating could have been caused by a physical fault with the sd card reader or the sd card itself. Either way let us know how you get on.
fabecoool said:
Hi everyone,
I just wanted to let you know about what I have found out.
A couple days ago my I9505 started to overheat a lot, although it was not used and in my pocket. At first I thought it was the battery, so I switched it off and took the battery pack out, but it turns out it wasn't hot... but the phone was! Especially the upper part (around the camera, and even on the screen side). I waited and restarted the phone. After a while it did it again and my phone rebooted by itself after a few hours, which was a complete surprise: I have been running the last stable version of SlimBean, which is awesome and really stable for the past couple of months (the reason why although I have tried some KK based rom I ended up going back to 4.3).
Anyway, I though maybe something was wrong with my settings and I decided I would test a few KitKat ROMs, and so I did:
- SlimKat
- OmniRom
- CarbonRom
- AOKP
- CM11
- and a few more...
With all of them, I experienced the same issue. And I had them all for a few hours, because I know at the beginning the phone always retrieves data and apps from google servers, so I figured it was bound to heat, but not that much! And the random reboots happened in all of them.
This morning, I was ready to flash back to a stock ROM to have the phone serviced (I have knox tripped but I don't care, I don't think they would mess around with me about it here in Europe, at least from what I've heard, and anyway, I'd just tell them that Kies did it ), when I realised that Hey! the day before it started, I was unable to copy/paste all the data from my 32GB microSD card to my computer using the USB cable. I would systematically get an error saying that the device has been disconnected from the computer. I had even wondered if my USB cable was damaged, but seeing that the phone charged alright, I did not pay too much attention to it.
I started to investigate the card and retested some ROMs I had tested previously. This time I would not connect, but I did try with and without the card, and BINGO! every time I put the card in, it would overheat.
I then tested my card with an adapter in my computer, and there seemed to be something wrong with it, because even then the copy operation would hang! So I formatted the card (after I had backed up everything I could), and put it into the phone, where I formatted it again with the phone. Now the card has been (albeit empty) for a few hours in the phone, and no overheating or random reboot in sight (running the latest stable SlimKat).
So if your phone starts to overheat, especially the upper part, check what happens when you remove the SD card.
Hope I'll have helped someone with this. If you don't hear more about me in this thread, it means everything's alright. I'll start re-loading things on the same microSD card. I'll see if it is still faulty or if the phone heats up. If it does, I'll try with another microSD and see if it does the same.
Cheers!
Fa
Click to expand...
Click to collapse
Thanks for this!
Getting an S4 this week so will keep the page bookmarked should I have any of the issues mentioned here. Thanks.
Google plus heated my s4, check settings and unchecked other folders.
Maybe upload on WiFi only. And when charging?
Sent from my GT-I9505 using XDA Free mobile app
Mines doing the same thing.
Everything fine now
Just thought I'd let you know after re-formatting the card:
Complete format with windows, then erase card on the SGS4, which then complained that my card must be formatted, so I formatted it with the phone.
I've been going with the original "faulty" card for more than a week now, and I have had no overheating issue. All the files (except the corrupted files) that were on the card when the problem occurred are back on it. And no issue.
Hope this helps!
Cheers!
Fa
fabecoool said:
Just thought I'd let you know after re-formatting the card:
Complete format with windows, then erase card on the SGS4, which then complained that my card must be formatted, so I formatted it with the phone.
I've been going with the original "faulty" card for more than a week now, and I have had no overheating issue. All the files (except the corrupted files) that were on the card when the problem occurred are back on it. And no issue.
Hope this helps!
Cheers!
Fa
Click to expand...
Click to collapse
1.this is a 7.9mm phone
2.the back cover is thin as a sheet of paper
3.the sdSlot has been installed behind the processor (for speed reasons) and it's made of metal components so there s heat transmission
just replace your cover with the stock one of the 9505 black edition and tell me ..anyway i wanna try this solution tnx in advance
charlie878 said:
1.this is a 7.9mm phone
2.the back cover is thin as a sheet of paper
3.the sdSlot has been installed behind the processor (for speed reasons) and it's made of metal components so there s heat transmission
just replace your cover with the stock one of the 9505 black edition and tell me ..anyway i wanna try this solution tnx in advance
Click to expand...
Click to collapse
You're not wrong at all, but the fact here is that there was a real problem: it was really hot AND there was a huge drain on the battery, which changing the back cover wouldn't have solved.
Besides, I no longer need to do anything, since after formatting the card, it's back to normal, i.e. no overheating. But you're right that heat reaches the surface of the back cover when e.g. downloading or watching streamed videos for some time.
Cheers!
Fa
The i9500 overheats too, so I'll cehck if the SD Card is the problem next time it happens. Thanks!
Man I've been having problems since day one. I've had it for a couple of days now and I'm so frustrated that I'm thinking of going back to my LGV10 and returning it back. At first I was super excited to open up the package but then......
1st problem...
Wasn't able to install the SD card and sim card. I kept on trying to install it but it would jump out of its slot and fall off. With the weight of the phone I had to also not just try to insert the cards but try to not drop the phone while juggling to balance it.
2nd problem.....
SD card doesn't read...
I have a 200gb SD I had on my V10 so I thought I could just pop it in and enjoy me some movies on this big screen and enjoy some music but Nope, it doesn't seem to want to read it and making me reformat it. I don't think so.
I installed a new one. Had to format it and thought I could transfer files to it and..
3rd problem.....
No OTG..... I didn't know that I tried to manually install some files and no luck.
Oh yeah I dropped it already also but good thing it was on the carpet.
I really really like the phone so I there's anything anyone can help me with I would be much appreciated .
Thanks and sorry I had to vent..
This phone could be great, but it really needs some dev love. If it could be unlocked and rooted I really think a custom rom could make this phone really shine. Maybe in the near future. For now I went ahead and ordered the Zenfone 3 Ultra. Going to spend the next week comparing the two. If I can get over the lack of LTE and the Zenfone has better user experience I will probably return the Lenovo.
MR.MEMORYLANE said:
Man I've been having problems since day one. I've had it for a couple of days now and I'm so frustrated that I'm thinking of going back to my LGV10 and returning it back. At first I was super excited to open up the package but then......
1st problem...
Wasn't able to install the SD card and sim card. I kept on trying to install it but it would jump out of its slot and fall off. With the weight of the phone I had to also not just try to insert the cards but try to not drop the phone while juggling to balance it.
2nd problem.....
SD card doesn't read...
I have a 200gb SD I had on my V10 so I thought I could just pop it in and enjoy me some movies on this big screen and enjoy some music but Nope, it doesn't seem to want to read it and making me reformat it. I don't think so.
I installed a new one. Had to format it and thought I could transfer files to it and..
3rd problem.....
No OTG..... I didn't know that I tried to manually install some files and no luck.
Oh yeah I dropped it already also but good thing it was on the carpet.
I really really like the phone so I there's anything anyone can help me with I would be much appreciated .
Thanks and sorry I had to vent..
Click to expand...
Click to collapse
I had a 7" display phablet. It had simcard instructions printed on the back shipping plastic. I kept the plastic on because it was a very handy reminder and was hidden by the case anyway. The way I did the simcard in Slot 1 and the sdcard in Slot 2 was to keep the phone flat on its face on a table. Open the slots one at a time... Install the cards... The table made it so easy!!! My simcard had to go into a plastic adapter to make it the right size and it was a real juggling act before I tried this - it also aids in not losing the teenie cards. They land right on the table. Now, it's possible that you have to put the phone on its back on the table... It just depends on the orientation of the card in the tray and the tray in the slot!!! Don't let that be the reason why you return the phone! Try it!!!
Another thing, I am not a techie but a few people here have mentioned that our old sdcard format doesn't work in this phone. They have (usually) purchased a new card (which I'm going to do once I get lucky enough to get this phone in my hands!) and reformatted it to work in this phone and then transferred the data from the old card onto the new one... I am not a techie so I am still going to research this different format... I still have some questions about whether my pc card reader reads that format or do I need to get a reader? Are a lot of newly released phones changing the sdcard format? Why would they request the new format? But I am not letting that stop me... I really want this phone. In my area the Chinese phones don't give good MMS text performance or I would be doing an ASUS Zenphone 3 Ultra!!!
Sent from my SM-N900T using Tapatalk
Yeah I figured out the card inserts & I also installed a brand new SD card. I format it to how it was suppose to be and I installed one song. Took me forever just for that one song. I just hope to figure it out before it's to late to return. Just want to be happy with it if you know what I mean lol.. Thank you
Picked up a high-speed MicroSD card and formatted it in my moto z. My device gets hot and full charge battery only lasts about three hours. When I remove the MicroSD card everything goes back to normal.
Using custom kernel and prerooted stock rom.
Anybody having any issues like mine or can shed some light on how to fix the issue? Thanks!
happened to me in moto x force and moto z
with 128gb lexar (works flawlessly on samsung tab a)
changed to sandisk uhs-i and no problems
might be moto is picky when it comes to sd cards
Yep this is a lexar card. Was on sale for $100. I guess I'll have to return it. Thanks for letting me know.
I went back to stock encrypted and it seemed to fix the issue.
don't count on it
Just FYI...
I've a 128 GB 1000x Lexar on my Moto Z with stock kernel and no issues with it... :fingers-crossed:
So another update, turns out Android sucks at indexing and it was constantly scanning my 5800 FLAC files all the time. 100% battery would go to 10% in just under three hours, it had nothing to do with it being a lexar card!
Solution? I put a .nomedia file in my music folder and enabled my music player to ignore that and it scans my whole library with ease. I went to work at 8:30 am today and just got home (6:18 pm) and my battery is still at 85%.
Turbojugend said:
So another update, turns out Android sucks at indexing and it was constantly scanning my 5800 FLAC files all the time. 100% battery would go to 10% in just under three hours, it had nothing to do with it being a lexar card!
Solution? I put a .nomedia file in my music folder and enabled my music player to ignore that and it scans my whole library with ease. I went to work at 8:30 am today and just got home (6:18 pm) and my battery is still at 85%.
Click to expand...
Click to collapse
Really a weird issue...
I've my MP3 and videos on my SD card and I've noted no issue with them...
I've tried multiple high speed UHS-I cards, and formatted as internal, but all of them were either flagged by the phone as "too slow and might affect performance" or gave me heat and battery life issues.
And it would take five minutes after a reboot to show all app icons, or apps would lose login passwords, games lost saves and other annoying issues.
Formatting it as external storage, and just setting the camera to record directly to it works fine though.
Someone from Xiaomi actually said they're not adding or supporting MicroSD as internal due to them always having issues apparently. And it seems to be true.
Shadowdancer123 said:
...
Formatting it as external storage, and just setting the camera to record directly to it works fine though.
....
Click to expand...
Click to collapse
This is in fact my actual situation... no issues with Lexar 128GB 1000x.
enetec said:
Really a weird issue...
I've my MP3 and videos on my SD card and I've noted no issue with them...
Click to expand...
Click to collapse
Maybe because I am using FLAC and have 5900 of them on it hahaha.
Turbojugend said:
Maybe because I am using FLAC and have 5900 of them on it hahaha.
Click to expand...
Click to collapse
Probably! :laugh:
Btw, another reason to not use it formatted as internal storage, is the immense power requirements MicroSD can spend at max write speed.
According to Wikipedia, as much as 100mA, which really explains why the phone heats up when it's formatted that way. And that doesn't include the consumption of the sd card controller.
https://en.m.wikipedia.org/wiki/Secure_Digital
Shadowdancer123 said:
Btw, another reason to not use it formatted as internal storage, is the immense power requirements MicroSD can spend at max write speed.
According to Wikipedia, as much as 100mA, which really explains why the phone heats up when it's formatted that way. And that doesn't include the consumption of the sd card controller.
https://en.m.wikipedia.org/wiki/Secure_Digital
Click to expand...
Click to collapse
It didn't matter how I had it formatted before it was still getting super hot. Now that I haven't been using it, the issue must have been Android trying to index all the files as it's been running fine all week now that I have that .nomedia file in my music folder.
Does anyone know of a 128 card that can handle is phone?? Im gonn try the Samsung Pro+ 128
masterjay21 said:
Does anyone know of a 128 card that can handle is phone?? Im gonn try the Samsung Pro+ 128
Click to expand...
Click to collapse
Using Lexar 1000x with no issues at all here...
enetec said:
Using Lexar 1000x with no issues at all here...
Click to expand...
Click to collapse
And at last... I had issues too!
On sdcard I store TWRP backups (no issues...), Titanium backups (no issues...), Maps (no issues...) and.... Pics & videos... and here I begin to see some weird behaviour...
First I saw Gallery had difficulties on showing pics thumbnials if I go fast between them... then it begins to show some "damaged" pics... at last I saw Camera app begins to crash just after taking a pic... (set to save on sdcard...)
So, I removed sdcard, connected to a PC and copied all files... The copy requested A LOT of time since of read difficulties, BUT all files was ok at last. :highfive:
Then I formatted sdcard and extensively tested with h2testw with no issues and constant speed.
So I formatted again and copied all files back in.
Then I've found a way to have it working fine with Moto Z... (I think... :fingers-crossed
Problem is that Moto Z is set to use a too small cache size for modern sdcards (128 KB) and this probably generate sync issues (and when this happens I saw CPU go wild and phone become warm... in a very similar way with Windows when it is having issues with USB keys... )
So I installed "SD-booster" app from Play Store (yes, it requires root...) and used it to resize cache to a more suitable value of 2048 KB and I haven't had any issue since then... more, my gallery has never been so fast scrolling and taking a LOT of pics in seconds or slow motion video isn't an issue at all now...
masterjay21 said:
Does anyone know of a 128 card that can handle is phone?? Im gonn try the Samsung Pro+ 128
Click to expand...
Click to collapse
I'm using a Samsung Evo 128go and I have no issue
So, I currently only use my 128gb Samsung UHS1 card for external storage only because of the issues other have experienced using it as internal. Not sure if it's on anyone's radar but Sandisk just announced a new micro sd card made specifically to be able to handle the read/write requirements.
http://www.droid-life.com/2017/01/05/sandisks-new-256gb-a1-microsd-card-wants-apps/
Moving the intent of a few posts on LineageOS thread to here.
rb1979 said:
Hi everyone,
Some of you reported that SD Card stopped working. This happened to me too today after about 20 hours after the latest update. The case with me is it doesn't fix itself even after a restart. I'm kind of stuck, whatever I want to do with the SD Card it wants me format it. I always had it as internal storage with apps and other things there. I have the the backup from the before the update. Will that fix if I restore it? Just want to mention that I update every week and never missed one. I had very minor issues up until now. Week in and week out everything has been fine and I started using the rom with the first release, all clean, full format and then weekly over the air updates every single week.
If anybody know any solution please let me know, if nothing works or I don't hear anything I'll probably try the backup restoration. BTW, to be specific about SD card no working I always get two notifications, one is "Unsupported SanDisk SD card" and the other is "SanDisk SD card missing"
Thank you
Click to expand...
Click to collapse
KrisM22 said:
Use a card brand other than sandisk and size 32GB or less.
Click to expand...
Click to collapse
rb1979 said:
Thank you for you help, I really appreciate it. The problem I see, right or wrong, is that I had this card for a year with no issues, first under stock rom, then under CM, and now under LineageOS up until the latest update with no issues at all. So it's just hard for me to take the card as the problem. Especially after seeing other people reporting it too lately. Do you have more information than just that? Meaning LineageOS and won't ever get along with sandisk or size larger than 32GB because of some external hardware limitation or something like that. Or this is just general knowledge what works best with LineageOS? In the first case I can think about case I can go and invest into a new card but in the second case I can just wait it out until codebase improves. It would good to know more so I can make better decisions.
Thanks for your help again.
Click to expand...
Click to collapse
KrisM22 said:
In my experience, most folks presenting SDcard problems have sandisk. I personally have had problems with sandisk that has led me to avoid them. I prefer samsung. There are many others. edit currently using a pny U3 32GB, but it's an old one and only does 56/29MBs R/W.
Click to expand...
Click to collapse
adityak1303 said:
+1 @KrisM22. I agree that almost all the users that state that there's a problem with their SD card were using a SanDisk SD card including myself. @rb1979, if you really think that your card isn't faulty, then try using it in some other phone. If you face the same errors then your card is faulty. If it works fine on the other phone, only then can it be considered as a problem with the ROM.
Click to expand...
Click to collapse
rb1979 said:
Thanks both of you, I'll do some testing around and get back to you with my findings.
Click to expand...
Click to collapse
KrisM22 said:
I just ordered one of these because I want to test the 64GB thing as it keeps coming up.
Samsung 64GB 100MB/s (U3) MicroSDXC EVO Select Memory Card with Adapter (MB-ME64GA/AM) - $23 + some silly $3 thing to get free shipping over $25. There are faster ones out there but I'm a cheapskate and don't use it enough to justify it.
Click to expand...
Click to collapse
That's most of it - then it goes verbose and wobbly.
I welcome any and all comments about SDcards!
There is no OT here but remember the XDA rules and try to be nice to folks. You can learn without trying to control others' behaviour.
No need to pretend you are TD. (allusion to Alice in Wonderland - Top Doormouse)
Thanks for creating this thread. There are surprisingly few other recent threads that discuss this topic on XDA apart from the one I've previously linked to (https://forum.xda-developers.com/android/help/micro-sd-write-access-format-exfat-t3358275). Also, I'm bringing over the well informed SD related comments that you left behind.
---------------------------
I've got to push back on the apriori assumption that these are specifically Sandisk brand card issues without knowing the specific details of the issues and seeing actual logs, and also without knowing the history of the individual cards in question (details of every device it was connected to and how it was connected, what OS and what file management methods were used, and how full the card typically is, and how frequently it might be disconnected in the middle of a file operations, among other things).
We must be mindful of the fact that the majority of SD cards in circulation are Sandisk cards which means that the majority of reported problems will be on Sandisk cards but this does not mean that the Sandisk cards are experiencing proportionately more issues than other brands. I don't doubt individual experiences, but it they may not speak to a larger picture. For example: Having supported large systems (>300 devices) running Linux directly from SD cards I did not see more problems with Sandisk cards than others. We've not seen enough evidence here to declare that this this is a Sandisk problem.
rb1979 said:
...I had this card for a year with no issues, first under stock rom, then under CM, and now under LineageOS up until the latest update with no issues at all.So it's just hard for me to take the card as the problem
Click to expand...
Click to collapse
The fact that a card has been used for a long time under different circumstances does not support a logical argument that the problem is in the ROM, in fact that supports the logical argument that the problem is with the card.
adityak1303 said:
....if you really think that your card isn't faulty, then try using it in some other phone. If you face the same errors then your card is faulty. If it works fine on the other phone, only then can it be considered as a problem with the ROM.
Click to expand...
Click to collapse
Good advise since, if the cards is having problems it should bring the problems to the other devices. Testing a different card in the first device on which the problem was noticed is also a good test.
--------------------------
Here is some supplemental information specific to Sandisk SD cards' built in data protection on cards experiencing failure. https://forum.xda-developers.com/android/help/micro-sd-write-access-format-exfat-t3358275. To summarize what is there: An SD card may begin to fail unknown to us, and then when the built in data protection is invoked it "breaks" the card with a dirty bit at beginning of drive so it cannot be written to or formatted but still allows us to copy data. The symoptoms when that data protection is invoked are similar to those bing reported by people who can no longer mount the card in Android devices (Android devices require read and write access to mount the card, unlike when the card is access via card reader on computer).
Just an update. I tried to format the card as portable storage (after this failure as internal and being burned I have hard time trusting it now) but it fails. I didn't do any testing with other phones just went straight for format. I might just buy another card. I think the phone specs say it's 32 GB max, is it still the case with different OS or not (meaning it was due to software not hardware) if I could get something higher than 32 (the current broken one is 32) I would go for it.
Thanks
rb1979 said:
Just an update. I tried to format the card as portable storage (after this failure as internal and being burned I have hard time trusting it now) but it fails. I didn't do any testing with other phones just went straight for format. I might just buy another card. I think the phone specs say it's 32 GB max, is it still the case with different OS or not (meaning it was due to software not hardware) if I could get something higher than 32 (the current broken one is 32) I would go for it.
Thanks
Click to expand...
Click to collapse
I believe after you use it as internal, and then try to use it as external, you first have to write an MBR on it and a partition formatted FAT32. i use a bootable stand-alone GPARTED to do that.
http://gparted.org/
Moto says it's limit is 32GB. Folks have, I believe, used much bigger cards on it. Don't know what is the limiting factor - be it software (ROM) , hardware, or licensing (exfat for Microsoft). I have ordered a 64GB Sammy which I should get in 1/2 week so I can test. Course I wouldn't be doing exactly what you would be doing so the test would only show that the G3 could read/write to it. I will only use it as external storage. I don't really "need" 64GB but it will allow me to be a bit more sloppy vis a vis nandroid backups.
It could be that after you format yours, that it will suddenly work just fine. Then again I just had a thumb drive go belly-up from I/O errors - once in a great while, it happens.
KrisM22 said:
... Moto says it's limit is 32GB. Folks have, I believe, used much bigger cards on it. Don't know what is the limiting factor .
Click to expand...
Click to collapse
I've got a 128gb in my Moto G (3rd - XT1540 2GB), and I have used the card for a long time. It works just fine for me, and the space is obviously fantastic to have. Every now and then (every few months or so, I'd say - maybe 3 times in the 18 months I've had it), it does become corrupted, though, and I get those same error messages. A backup, wipe/re-format, and restore, and I put it right back in my phone and it works just fine again. Seems like that's happened in other devices, though, too.
The card is a SanDisk Ultra SL128 (Class 10/UHS-1, man'd Jan 2016). I've only ever used it for external storage, never adopted, and I've only ever formatted the card as FAT32, using my PC. I'm running stock Android 6.0 24.24.1 at the moment, with TWRP.
beachfl said:
I've got a 128gb in my Moto G (3rd - XT1540 2GB), and I have used the card for a long time. It works just fine for me, and the space is obviously fantastic to have. Every now and then (every few months or so, I'd say - maybe 3 times in the 18 months I've had it), it does become corrupted, though, and I get those same error messages. A backup, wipe/re-format, and restore, and I put it right back in my phone and it works just fine again. Seems like that's happened in other devices, though, too.
The card is a SanDisk Ultra SL128 (Class 10/UHS-1, man'd Jan 2016). I've only ever used it for external storage, never adopted, and I've only ever formatted the card as FAT32, using my PC. I'm running stock Android 6.0 24.24.1 at the moment, with TWRP.
Click to expand...
Click to collapse
Thanks - Becoming corrupted every 6 months seems excessive, but with heavy use...? So what do you use it for? Also it sounds like you are using something other than the phone to format it...?
At least you are ready for it and just re-format it!
beachfl said:
I've got a 128gb in my Moto G (3rd - XT1540 2GB), and I have used the card for a long time. It works just fine for me, and the space is obviously fantastic to have. Every now and then (every few months or so, I'd say - maybe 3 times in the 18 months I've had it), it does become corrupted, though, and I get those same error messages. A backup, wipe/re-format, and restore, and I put it right back in my phone and it works just fine again. Seems like that's happened in other devices, though, too.
The card is a SanDisk Ultra SL128 (Class 10/UHS-1, man'd Jan 2016). I've only ever used it for external storage, never adopted, and I've only ever formatted the card as FAT32, using my PC. I'm running stock Android 6.0 24.24.1 at the moment, with TWRP.
Click to expand...
Click to collapse
That may not be drive corruption but rather a corrupted file or files. If it is localize drive corruption it may still be there without having any impact until some data is written to that part of the drive. Unlike platter based hard drives, when these drives actually start to fail they may invoke a built in data protection (dirty bit) which resembles being locked in read only mode preventing the drive from being formatted which is obviously not your case. Have you ever done a sector scan of the drive, eg chkdsk <driveletter> /f /r or done a full format (as opposed to quick format)? Either of those things may flush out localized damage and the scan might fix it but they would take a long time.
KrisM22 said:
Thanks - Becoming corrupted every 6 months seems excessive, but with heavy use...? So what do you use it for? Also it sounds like you are using something other than the phone to format it...?
At least you are ready for it and just re-format it!
Click to expand...
Click to collapse
Yeah I guess it is kinda a small PITA lol. Could just be from me starting and cancelling or moving too many things at once, I don't know.
I've never actually come close to needing all that space to TBH. I could probably do just fine with a 64, but it's nice to know I could record or store hours of HD video, for example, if I need it. I got nearly 30 gigs of music on it. I keep tv and movies on there, too, in case I get caught bored somewhere. Full Nandroid and Titanium backups are on there, as well.
I use a microSD adapter and a small (76 kb) utility for Windows called FAT32Format (Ridgecorp).
---------- Post added at 22:00 ---------- Previous post was at 21:45 ----------
IronTechmonkey said:
That may not be drive corruption but rather a corrupted file or files. If it is localize drive corruption it may still be there without having any impact until some data is written to that part of the drive. Unlike platter based hard drives, when these drives actually start to fail they may invoke a built in data protection (dirty bit) which resembles being locked in read only mode preventing the drive from being formatted which is obviously not your case. Have you ever done a sector scan of the drive, eg chkdsk <driveletter> /f /r or done a full format (as opposed to quick format)? Either of those things may flush out localized damage and the scan might fix it but they would take a long time.
Click to expand...
Click to collapse
I've had that problem before, too, but not on the 128 I have in my phone now. That is very frustrating. One of my 32 gb cards suddenly went into "read-only" mode as you describe, and nothing I can do will get it useable again. All the files are still readable from it (except the part of one huge video file that is on the bad sector that seems to have caused the problem).
So right, my 128 card doesn't have that problem, and seems to be corrupted files, as you say, not the drive itself. I do actually do what you talk about - when I do find I have to re-do the 128 sd card in my phone, I run a Windows chkdsk /r before I re-format it, and a chkdsk /f afterward, as a check. The chkdsk /r does take quite a while, yeah .. a few hours.
Cheers
beachfl said:
Yeah I guess it is kinda a small PITA lol. Could just be from me starting and cancelling or moving too many things at once, I don't know.
I've never actually come close to needing all that space to TBH. I could probably do just fine with a 64, but it's nice to know I could record or store hours of HD video, for example, if I need it. I got nearly 30 gigs of music on it. I keep tv and movies on there, too, in case I get caught bored somewhere. Full Nandroid and Titanium backups are on there, as well.
I use a microSD adapter and a small (76 kb) utility for Windows called FAT32Format (Ridgecorp).
---------- Post added at 22:00 ---------- Previous post was at 21:45 ----------
I've had that problem before, too, but not on the 128 I have in my phone now. That is very frustrating. One of my 32 gb cards suddenly went into "read-only" mode as you describe, and nothing I can do will get it useable again. All the files are still readable from it (except the part of one huge video file that is on the bad sector that seems to have caused the problem).
So right, my 128 card doesn't have that problem, and seems to be corrupted files, as you say, not the drive itself. I do actually do what you talk about - when I do find I have to re-do the 128 sd card in my phone, I run a Windows chkdsk /r before I re-format it, and a chkdsk /f afterward, as a check. The chkdsk /r does take quite a while, yeah .. a few hours.
Cheers
Click to expand...
Click to collapse
Great that you're running chkdsk on it. May be caused if you cancel or something happens in the middle of a move. Only other thing I could suggest is to do your format on the phone itself, after you've done everything else on the PC. Don't know if that would make a difference. Shouldn't but I've run across vy experienced folks saying to do that. But... Yeah you've got me hankering to put a 128GB on it...
edit: for read only cards before you trash them I would run them by gparted just to see if re-creating the MBR and partition would change its mind. I have successfully done that with thumb drives but not with cards/adapter/reader.
KrisM22 said:
Great that you're running chkdsk on it..
edit: for read only cards before you trash them I would run them by gparted just to see if re-creating the MBR and partition would change its mind. I have successfully done that with thumb drives but not with cards/adapter/reader.
Click to expand...
Click to collapse
Yeah, thanks for reminding me about fixing the errors, IronTechmonkey. It's kinda an important step I forgot to mention.
I not sure I have the bad card still. I didn't think about GParted, should have. I tried Paragon, among other things, but to no avail.
What speeds are folks getting from a U3 SDE card? I bought what I thought was a 100/60MB/s card and it does about what my old PNY card did - R=40-50, W=34-40MB/s. Is the phone the limiting factor or did I get a bum card?
KrisM22 said:
What speeds are folks getting from a U3 SDE card? I bought what I thought was a 100/60MB/s card and it does about what my old PNY card did - R=40-50, W=34-40MB/s. Is the phone the limiting factor or did I get a bum card?
Click to expand...
Click to collapse
AFAIK the the phone hardware/OS is unlikely to meet the advertised speeds of the cards. Likewise and perhaps more so for USB 2.0 ports and anything using MTP.
I dont know how this compares but for what it is worth: With a Sandisk Utra SDHC (Class 10 - Video, Ultra High Speed Class 1 - whatever that jargon means) touting 80 MB/s read speeds and 40 MB/s* write speeds; the read speeds did consistently approach the rating (getting hot enough to scorch the logo) and the wite speed occasional did. Another factor is the size of files being copied, larger quantities of smaller files taking more time per MB, unless using some dedicated test utility I've never actually done a test of SD r/w speeds on the device. What are you using to measure those?
* In re write speed ratings: Digging into the small print of the specifications may reveal that the manufacturer uses different size cards each for the reed and write speed ratings, effectively padding the write speeds by citing test results from smaller capacity cards.
IronTechmonkey said:
AFAIK the the phone hardware/OS is unlikely to meet the advertised speeds of the cards. Likewise and perhaps more so for USB 2.0 ports and anything using MTP.
I dont know how this compares but for what it is worth: With a Sandisk Utra SDHC (Class 10 - Video, Ultra High Speed Class 1 - whatever that jargon means) touting 80 MB/s read speeds and 40 MB/s* write speeds; the read speeds did consistently approach the rating (getting hot enough to scorch the logo) and the wite speed occasional did. Another factor is the size of files being copied, larger quantities of smaller files taking more time per MB, unless using some dedicated test utility I've never actually done a test of SD r/w speeds on the device. What are you using to measure those?
* In re write speed ratings: Digging into the small print of the specifications may reveal that the manufacture uses different size cards each for the reed and write speed ratings, effectively padding the write speeds by citing test results from smaller capacity cards.
Click to expand...
Click to collapse
Thanks.
Interesting - so you were testing it on windows (?) I did test them on linux and got W=74 on the PNY and 77MBs on the Samsung. That's through a USB3 cardreader.
On the phone I used A1 SD Bench, SD card test, and disk speed test.
Off to try windows...
I was just going to boot up a WinPE and test it there. What prog did you use to test it?
Yes, both of these cards test at about R=81 , W=66.
KrisM22 said:
Thanks.
Interesting - so you were testing it on windows (?) I did test them on linux and got W=74 on the PNY and 77MBs on the Samsung. That's through a USB3 cardreader.
On the phone I used A1 SD Bench, SD card test, and disk speed test.
Off to try windows...
I was just going to boot up a WinPE and test it there. What prog did you use to test it?
Click to expand...
Click to collapse
Yes, Windows 7, which reports file data transfer speeds in the copy process window so I did not use a utility. I've done this enough times in geneal, and a few times specifically with large files and a stopwatch, so I know the speed in the file copy window is relatively accurate (for single large files). The speeds you get on linux seem reasonable. I'll test A1 SD Bench on Osprey when I have a chance. Thanks.
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
KrisM22 said:
Yes, both of these cards test at about R=81 , W=66.
Click to expand...
Click to collapse
Also seemingly reasonable.
My card seem to be working just fine on my Lineage OS. I rebooted by device and now it says it's corrupted. Is there any way out? Will I be able to get my data back?
jay.bhadra1995 said:
My card seem to be working just fine on my Lineage OS. I rebooted by device and now it says it's corrupted. Is there any way out? Will I be able to get my data back?
Click to expand...
Click to collapse
My suggestion would be to copy whatever you can off it and re-format it asap. If you can't read it via phone, try PC.
EDIT: I am assuming you are using it as external. If you are using it as internal, I believe you have lost everything. I know of nothing that can read it. GPARTED can only re-add an MBR and a partition and make it usable again, but all data is lost.
KrisM22 said:
My suggestion would be to copy whatever you can off it and re-format it asap. If you can't read it via phone, try PC.
EDIT: I am assuming you are using it as external. If you are using it as internal, I believe you have lost everything. I know of nothing that can read it. GPARTED can only re-add an MBR and a partition and make it usable again, but all data is lost.
Click to expand...
Click to collapse
Yeah. I copied everything and made a backup. Luckily I use it only as a storage device and not an internal drive for apps. But how do I re-format it? I tried using the format option that my phone gives me but to no avail.
jay.bhadra1995 said:
Yeah. I copied everything and made a backup. Luckily I use it only as a storage device and not an internal drive for apps. But how do I re-format it? I tried using the format option that my phone gives me but to no avail.
Click to expand...
Click to collapse
Do you have a little card reader so you can plug it into your PC?
KrisM22 said:
Do you have a little card reader so you can plug it into your PC?
Click to expand...
Click to collapse
No. Sadly I don't. Is there no other way round to format it?
I have just bought a u12 plus and sometimes the camera loads fine other times it takes up to 30 seconds to load, other times it fails to open at all. I'd rather not have to send it back after spending the day setting it up but I use the camera a fair bit. Something simple to fix or RTB? Spotify also won't behave either freezing or not loading. I moved my memory card from my old u11 to this phone, any connection? Thank you in advance for any help...
Not good form to reply to my own post but... Card works in a reader on laptop so contents copied, card reinserted into phone, formatted but still playing up in the phone. Is there a way to determine if its a problem with the phone reading the card or just the card itself? Cheers...
Try factory reset ,it solves some problems for me after otas.
Thanks for the reply (Awesome username btw !). I really was hoping to avoid this after taking most of the day to get it how I wanted it tbh. I've ordered a new card to see if this does the trick as it appears to work fine without one inserted & I tried re-formatting in both the phone & the laptop but it failed on both attempts leading me to point towards the card. I hope not to have to but will use the Hard Reset as a last resort after testing the card when it arrives. Thanks for looking in and taking the time to try & help, appreciate it...
Memory card was the issue in case anyone else experiences this...
smudgelab said:
Memory card was the issue in case anyone else experiences this...
Click to expand...
Click to collapse
I'm glad you sorted it out