Hi, I have the phone of my signature, a Samsung Galaxy Core 2 G355HN.
Everything works fine except the camera, but just sometimes. This is what happens. I'm chatting via WhatsApp and I try to share a picture of something. I tap on the camera icon, focus an object and press the middle button "take picture". When I press it, there's an error that says "Unkown error occurred", and I'm sent back to the chat screen. I try it again, press on the camera icon, focus an object, and the same error. Then I open the stock android camera app, and the same happens. It seems to be an error when trying to take the actual picture, like if suddenly the camera couldn't write data or had no permission to do so.
The only way to solve this is to reboot the phone, and then everything works fantastic. I've not found any method or something like that to activate this bug or error. It seems to happen randomly.
What can be causing this issue?
I've thought about some potential sources of the issue:
1. I have the phone rooted. May be the camera app suddenly and mysteriously loses permission to write data on the microSD card. May be SuperSU doesn't grant it access.
2. I have installed Xposed framework and the GravityBox [KK] module. May be that is causing this error.
3. A problem with the microSD (It's a Samsung EVO 64GB, and it works like a charm, but who knows...)
4. My stock carrier's ROM is faulty, though I don't think that's the case cause everything else works great.
5. I also have installed ES File Explorer, and one day happened one weird thing. Like a week ago I was trying to solve this problem by closing and restarting system apps (I mean WhatsApp, Camera app, and whatever I've found could be related in taking pictures), cleaning cache, dalvik cache, etc. Still, I opened the camera app, and when hit the button, the problem still appeared. I remember I opened ES File Explorer and went to the photo folder, then go to the camera app and the problem was solved. This is the only time I've solved the issue without restarting. Nevertheless, this bug has happened like 2 times since then, and I've tried to do that very same process, and the bug didn't got fixed.
Remember that this only happens sometimes randomly, and if I reboot the phone, the problem gets solved (until it occurs again).
Problem solved:
http://forum.xda-developers.com/gal...ing-photos-t3109320/post62979839#post62979839
Try to go to SuperSU setting and swipe down till u find the trust system user and check it. Tell me if this work
Sent from my GT-I8262 using XDA Free mobile app
All right. I have that one unchecked right know, and of course I can take photos without a problem. But when the error appears, instead of rebooting, I'm gonna check that option and activate it.
One question: should that question be activated by default?
I've been using this smartphone for 6 months and I've never activated it.
I've edited my main message:
5. I also have installed ES File Explorer, and one day happened one weird thing. Like a week ago I was trying to solve this problem by closing and restarting system apps (I mean WhatsApp, Camera app, and whatever I've found could be related in taking pictures), cleaning cache, dalvik cache, etc. Still, I opened the camera app, and when hit the button, the problem still appeared. I remember I opened ES File Explorer and went to the photo folder, then go to the camera app and the problem was solved. This is the only time I've solved the issue without restarting. Nevertheless, this bug has happened like 2 times since then, and I've tried to do that very same process, and the bug didn't got fixed.
Click to expand...
Click to collapse
Card error
Your GC2 doesn't support 64GB Card, like mine. That's the problem !
StratOS_HTC said:
Your GC2 doesn't support 64GB Card, like mine. That's the problem !
Click to expand...
Click to collapse
What?
The Core 2 does support 64GB, that's 100% guaranteed. I've had no problem with my card.
Anyway, if it did not support 64GB cards, it'd have no sense that this issue happens only suddenly like once or twice a week. But as I told you, this device supports 64GB of microSD, that's what Samsung claims in the official GC2 specs.
rambomhtri said:
What?
The Core 2 does support 64GB, that's 100% guaranteed. I've had no problem with my card.
Anyway, if it did not support 64GB cards, it'd have no sense that this issue happens only suddenly like once or twice a week. But as I told you, this device supports 64GB of microSD, that's what Samsung claims in the official GC2 specs.
Click to expand...
Click to collapse
This statement Samsung never stated. Couse it's wrong and it doesn't support fully !
Have written to Samsung support and they have stated that they intend to fix it in future development, they stated that this is kernel related.
I have tested mine G355HN on stock OS with class 10 SDHC 64 GB on exFAT partition. The resoults were identical couple of times. I were unable to copy/access some files on SDCard.When I put a card on comp's SDCard reader there werte errors on exFAT.I also got new identical card on ebay for free ( I bought it there ) and the things with new card happened again, so now I'm on 32 GB and those things never happened again for now.
Regards
http://www.gsmarena.com/samsung_galaxy_core_ii-6331.php
MEMORY Card slot microSD, up to 64 GB
http://www.samsung.com/in/consumer/mobile-devices/smartphones/others/SM-G355HZKDINU
External Memory Support
MicroSD (Up to 64GB)
http://gadgets.ndtv.com/samsung-galaxy-core-2-1738
Expandable storage type microSD
Expandable storage up to (GB) 64
http://www.mgsm.pl/pl/katalog/samsung/galaxycore2/
microSD, microSDHC, microSDXC (do 64 GB)
There's not a single webpage that claims this phone only supports 32GB. And Samsung's official page claims up to 64GB. So... yeah, this phone supports 64GB microSD cards, unless they are all lying about specs, even Samsung. Anyway, imagine that It wouldn't support 64GB cards:
Then why when I put the microSD card, the phone recognizes all those 64GB and there's no error message or unsupported message?
Why I can read and write data from the microSD card without any single problem, except this one, of course, that remember, only happens twice a week maximum. The rest of the time, it takes photos without any single problem.
h.d.z said:
Try to go to SuperSU setting and swipe down till u find the trust system user and check it. Tell me if this work
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
And that's the solution! :victory:
It has happened now, the "Unkown error occurred" bug. I went to SuperSU, checked the trust system setting, and go back to WhatsApp to take a photo, and it worked.
Thanks!
OK, I've tried to do this trick again, and it has not worked. What the hell?
I've had to reboot the phone, cause otherwise the error was not gonna get fixed.
Weird. What I did when the error occurred was go to SuperSU, untick trust system, went back to the camera, still the same error, went back to SuperSU, tick trust system, and the error still persisted.
OK, I think I've finally found out what's happening.
As I have a 64GB microSD card in this phone, I obviously set the download folder and camera folder in the Samsung EVO microSD card, that even was recommended by the default camera app.
This issue has been happening always, I thought I had fixed it when did the SuperSU option tweak, but I was wrong. It fixed it the first time, but it was pure causality. The issue is related with using the microSD as the camera picture folder. Since I've set it to the internal memory, the camera error has never happened again. So... something's wrong with the microSD support or the camera app. Besides this, the microSD works perfectly in every other aspect, this mobile recognizes without a single problem the 64GB and all the rest of the stuff is 100% working.
May be, as StratOS stated, there's something wrong with the kernel, or with the camera app. But he was wrong when he said that this mobile does not support 64GB, cause it does.
Related
So does anybody has had this error on their phone? Sometimes when I want to take a pic it shows a light blue/cyan screen error, and the picture doesn't get taken. The error says:
Failed to save photo to SD card (error code=2)
The following are fixes for this error:
- make sure your SD card is inserted
- remove the SD card and re-insert, then launch Camera ZOOM FX again
- reboot and try again
If this problem continues, please mail [email protected]
Somebody knows what is going on?
Thanks.
I'm using the same app, but haven't had any problems since switching to a Class 4 SD card (due to the known issue w/Class 10 cards on this device). Can't seem to use video with it though, every time I try to switch to video it force closes.
armyengineer51 said:
I'm using the same app, but haven't had any problems since switching to a Class 4 SD card (due to the known issue w/Class 10 cards on this device). Can't seem to use video with it though, every time I try to switch to video it force closes.
Click to expand...
Click to collapse
The weird thing is that if I do a factory reset, then it works fine, but as soon as I begin to install some apps and play around, then it happens again.
Somebody else has another input?
I was having the same issue I also did a Factory Reset then pulled the battery over night and have not had the issue since not sure if it was just a glitch or what.
I just downloaded Camera Zoom FX and got the same thin I took out my sd card and tried the app again, same response. I bought a 16mb class 6 sd card at the suggestion from here on what would work. The camera is a disappointment with the stock app, hope I can get FX working.
Sent from my MB865 using XDA App
So far no problems with Camera Zoom FX.
OS versions 2.3.5 or 2.3.6.
SDcard is a Sandisk 16G class 6
Any news nahuelarg86 on your situation
I had the same problem with this app. The standard camera app would appear to save the pictures but when you would go into MyGallery, no picture would be there although you wouldn't get an error message like CameraFX. I found this information somewhere else, but if I went and looked at the dcim directory on the sdcard there would be corrupt files in the Camera subdirectory. Deleting these files would then allow pictures to be saved. I was using a class 10 sd card, but switching to class 4 didn't fix the issue. I did the OTA update to 2.3.6 hoping this would correct the issue. This made things worse regarding the camera apps. Every picture file for news pics appeared to be corrupt. I then did a factory reset to 2.3.6 and I haven't had a problem with the camera apps since.
Well, I did a factory reset and I didn't have the problem again. But, I began to download some apps and play around and then I got it again... I deleted all the apps that I installed last time in hope that it would help, and it did. For me it's a pain in the a$$ to do factory resets because of the setting up, re installing of thing, etc.
I still don't know where the problem might be. Seems like it's related to space or the resources an app uses, but I know of the problems of SD cards and everything is stored in the phone's memory. So I have no idea...
I know this thread is old, but it was the first hit on google, so maybe someone else will need the solution: Most of the times the save feature on external sd card is corrupted because of rom change. Backup your data of your external sd on your PC. Then go in android under settings < "space" (Speicher auf deutsch) and format the external sd card. Afterwards you should be able again to save your pictures on your external sd card, because the card is now perfectly formatted to your rom....
I am getting an error, old as android itself, with my new s7 Exynos. "The device has either stopped responding or has been disconnected". This happens when I try to copy my 25 gb music library on external sd card. I tried all usual stuff like:
- Use different cables
- Reinstall samsung drivers via Kies
- Transfer using MTP or PTP
- Use USB Debugging on and Stay awake option on
- Tried pushing folder via ADB push command, but it says "Read-only file system" when I typed location as /sdcard1 (which I think is an extSdcard right? It did copy a .txt file if I typed just /sdcard but that is internal storage)
- Tried with Samsungs own SmartSwitch but the bloody thing doesn't even have an option to copy files to device (only backup and restore), and Kies is not supported for S7.
On side note, the same sd card worked perfectly with my S3 and gave no errors. When I inserted sd card into S7, I formatted it inside the device. What other troubleshooting stuff should I do? I can't believe that this crap is still an issue. Why can't we have our USB Mass Storage back?
-----------------------------
Big edit:
Ok my phone doesn't seem to like this sdcard. I inserted microsd card to my s3 and copied 17 gb of files, to check if there is a problem with MTP connection or sdcard, but it copied all 17 gb of files without any errors or problems. I checked on phone if it reads correctly, and all music plays fine instantly without any lag or freez. But when I inserted this micro sdcard back into my s7, there was a massive lag/freezes. When I click "MyFiles" or "SolidExplorer", or any other file manager, there is a big lag/freeze, and file manager never opens (it is always stuck). Also, when I go into settings and when I press "unmount" under storage, nothing happens. When I press home, it doesnt go to home screen, and says that touchwizz is not responding (if I change default applications to Nova launcher, it does go to the homescreen though). When I try to open Shealth app, it doesnt open it. Also when I put my phone to sleep, I have to wait like 10 seconds for screen to turn off sometimes. When I pop out sdcard though, all the problems go away INSTANTLY. Everything is smooth again and responsive, file manager opens, shealth opens, everything works like it should. If I insert sd card back in, same problems happen.
And as a cherry on the cake, I put sdcard back into my s3, and everything still works fine. All files are readable, music playes, etc.
When I was searching online, this is the closest thing I have found that explains my problems, but there was no solution: http://forums.androidcentral.com/samsung-galaxy-note-4/542854-sd-card-freezes-note-4-a.html
Anyone ever experienced anything similar?
EDIT: Luckly, it was not my phone fault. It was my sd card. Even though it worked fine on s3 and my friends s5, it didn't work in s7 for some reason. I purchased samsung evo+ and it works flawlessly.
try format as exfat ?
Can't, it is 32gb card and it is not allowing me. Also, sometimes when I insert it, the whole phone freezes complitely. Once I even had to use volume down + power button for 10 seconds reset method since it froze complitely. Card is in fat32.
edit: I also tried copying files from USB flash drive (adata 64gb exFat) to sdcard directly on my phone, via OTG cable. It also stopped the process midway and phone wouldn't enter into any file storage (it froze). I had to remove sdcard again and insert it back in to remove that freezing.
edit2: I copied 17gb folder full of subfolders to internal storage, and it transferred without any problems and pretty fast (about 20 minutes). That means MTP connection and drivers are fine. When I tried copying the same 17gb folder to external sd card, "device stopped responding or has been disconnected" error again.
It seems like this is a lot bigger problem, as this is not really an issue about "device stopped responding" anymore. I edited first post. Still looking for solution.
Search the forums, this is a known issue with some phones. You can try other cards, sometimes that will help. Or get your phone replaced as it's a hardware defect. My first S7 was like that. This one reads sdcard without issues (but has radio issues).
Sent from my SM-G930W8 using Tapatalk
phoenix_rizzen said:
Search the forums, this is a known issue with some phones. You can try other cards, sometimes that will help. Or get your phone replaced as it's a hardware defect. My first S7 was like that. This one reads sdcard without issues (but has radio issues).
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
Luckly, it was not my phone fault. It was my sd card. Even though it worked fine on s3 and my friends s5, it didn't work in s7 for some reason. I purchased samsung evo+ and it works flawlessly. So happy I don't have to hassle with warranty!
I've had a constant problem for the past few days with the camera. In every app that uses the camera I get an error message saying something like
"Please close other apps, the camera cannot be accessed right now."
This is temporarily redeemed with clearing my cache but after using the phone for a while the problem returns. Restarting the device doesn't seem to help very much but occasionally the camera will work after a restart. I'm on the software version 6.0.1 V20a-SEA-XX and I have a H959. I have not tried a hard reset on my device yet and wish to avoid that if an easier fix is available.
When the Mrs's phone was updated by LG following repair, she had a similar issue. It turned out to be an issue with the camera trying to save to the SD card, but the SD card not playing nice with the new firmware.
To see if you have the same issue, go into the camera and change the save location to internal storage before you attempt to take any shots. If you can take a shot after this change, you know its an issue with the SD card.
Lets hope its something so simple. :angel:
Masteryates said:
When the Mrs's phone was updated by LG following repair, she had a similar issue. It turned out to be an issue with the camera trying to save to the SD card, but the SD card not playing nice with the new firmware.
To see if you have the same issue, go into the camera and change the save location to internal storage before you attempt to take any shots. If you can take a shot after this change, you know its an issue with the SD card.
Lets hope its something so simple. :angel:
Click to expand...
Click to collapse
Got the camera to work for once and changed it to save to the phone. Worked for a while but I believe it reverted to saving to the SD card. Taking out the SD card and putting it back in was a simple fix along with saying "No" to a prompt about asking it I want to save to the SD card. Many thanks! I was starting to believe I'd never take photos again with this phone.
lol_cool88 said:
Got the camera to work for once and changed it to save to the phone. Worked for a while but I believe it reverted to saving to the SD card. Taking out the SD card and putting it back in was a simple fix along with saying "No" to a prompt about asking it I want to save to the SD card. Many thanks! I was starting to believe I'd never take photos again with this phone.
Click to expand...
Click to collapse
No problems Lol_cool. :highfive:
I would suggest you copy everything off that SD card and then format it using the phone before moving everything back onto it. Other apps may also cause the same types off issues if your SD card is now not entirely compatible with the phone.
Masteryates said:
No problems Lol_cool. :highfive:
I would suggest you copy everything off that SD card and then format it using the phone before moving everything back onto it. Other apps may also cause the same types off issues if your SD card is now not entirely compatible with the phone.
Click to expand...
Click to collapse
I have the same problem. I don't even use sd card and it always happen again and again. Even the flash can't be turned on in the quick toggle menu. I have hard resetted my phone several times and constantly appears again.
Ficoradic said:
I have the same problem. I don't even use sd card and it always happen again and again. Even the flash can't be turned on in the quick toggle menu. I have hard resetted my phone several times and constantly appears again.
Click to expand...
Click to collapse
I think LG will tell you to do a factory reset Ficoradic.
If that doesn't work, you'll have to do a RMA or pay for the repair if your out of warranty. :crying:
I'm having the exact same issue. I already replaced the rear camera module as I thought it was broken. It seemed to work for a while, but now i'm having the cannot connect to camera issue almost constantly.
What seems to help is to 'clear all' applications from the recent apps window, and use camera restarter (https://play.google.com/store/apps/details?id=com.exlyo.camerarestarter) a few times and launch the camera app again. (need root)
I'm using a rooted 5.1.1 v15C-EUR-XX, have root, xposed, powernap, amplify, greenify and some other root tools installed and am thinking that that might be the issue.
The restarter thing didn't work anymore today, so I put some pressure on the part of the laser focus thing while opening the camera app, and it worked until I took my finger off, then it went black. I tried again, and again it was a success. The connector for the camera is right under that laser thing so it might just be due to bad connection of the camera connector, or the laser thing that has a bad connection inside.
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.
Hi All,
I got a new S8 Plus this past Friday. Nice phone, but after spending a few days with it, it seems to have some issues.
The SD card seems to mount and unmount randomly. I have a few apps that are on my SD card and every now and then I just get the gray android generic "App Not Available" icon in place of the correct app icon. Then eventually it may show up again, or it may take a reboot to show up again.
The other thing (more annoying to me) is that the phone randomly reboots without error. No heat, no other issues that I can find, just a complete reboot. Again, there is no app that seems to do it, no excessive (or any noticiable heat at all for that matter). Just a reboot. I know it does it overnight as well because I can check the system up time, and I can also tell because I have iris scanning set up and after a reboot you have to plug in your pin number no matter what.
FYI - I called Samsung and they had me clear my cache and reboot to safe mode. Other than that, they did nothing else, said to watch it. And did not indicate anyone else was experiencing this.
Just wanted to know if anyone else is experiencing this.
Thank you!
A lot of folks are experiencing this, myself included. Try moving any apps you have put on your SD card to back to internal storage, that stopped the random reboots for me. I've removed my SD card for now, hoping a software fix is possible. If this "SD Card Monitor" app is correct my card mounts/unmounts 100+ times per day, even when sitting untouched on my desk!
Also, check out these threads:
https://us.community.samsung.com/t5/Galaxy-S-Phones/Galaxy-S8-SD-Card-Problems/td-p/91194
https://us.community.samsung.com/t5/Galaxy-S-Phones/Galaxy-s8-keeps-restarting-by-itself/td-p/92825
https://forum.xda-developers.com/galaxy-s8/help/s8-locking-restarting-t3591795
https://forum.xda-developers.com/galaxy-s8/help/sd-card-issues-t3597223
https://forum.xda-developers.com/galaxy-s8+/help/s8-owners-experiencing-random-reboots-t3603146
I have an old Sandisk 200Gb installed in my T-Mobile variant 8+ and have not experienced any sdcard issues or reboot issues. I DO NOT have any apps installed to the sdcard either.
Verizon S8+ here. I have a year old Sandisk 128gb Sdcard in mine and I have no reboot or dismount issues.