I've been trying to install the Rugby World Cup app from the market, but every time it gets to "installing", I get a message saying the SD card has been removed.
I don't know what's actually been removed, as all my music is still accessible and I can browse the SD card in OI File Manager, but then, some apps aren't working, and I have to reboot to get it back.
Any ideas what might be causing this? I've tried updating existing apps, and that works fine...
Thanks!
I have a Nexus S i9020t (soju) with 4.1.1 (JRO03E) (stock and no root) on T-Mobile.
I did a "Reset" in 1.5-R75-v6, removed the app, reboot, and installed 1.5-R79-v5. It only let me add the pre-paid card back. I get an error when I try to add AMEX or VISA card. I also got an error trying to remove the pre-paid card.
I did another reset in this version and went back to 1.5-R75-v6. Then I added all my cards and installed 1.5-R79-v5 on top of 1.5-R75-v6.
I have not tried to use it yet, but was wondering if anyone else had issues with the new market version?
Used it today. It gave me the "Check with the cashier" message, but it went through with my AMEX card.
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.
Hi there !
Has anyone experienced this issue?
https://forum.xda-developers.com/mate-20-pro/help/write-to-sd-card-emui-10-t4017037
When I first got my P30, I restored a backup I had on my Galaxy S7 and everything seemed to work fine.
I had set up some 3rd party apps to have access and store things to the Nano Memory card.
For example Pocket to save its downloaded articles to the external card, Flud to store downloads on the memory card, etc.
I was also storing some Nova Launcher backups to the memory card.
The memory card is an original and quite expensive Huawei 128GB NM card.
Two days ago all of a sudden MixPlorer could not copy files from internal storage to the NM card.
Nova Launcher could not access the card either.
Every single 3rd part app could not have access.
Only Huawei apps (and I think Google apps, too) can have access. Huawei Files manager has no issue moving / copying files from internal to the memory card, the Camera app can save photos to the memory card just fine and I think Google News can save articles to the memory card.
Also, plugging P30 via USB to my Windows PC and using Huawei HiSuite has no issues. This way the NM card is accessible.
Yesterday morning I formatted the NM card (via the phone) and then I also did a factory reset to the phone and set it up again from scratch !
I also removed the card to clean it and then inserted it again to the phone sim/nm tray.
These steps did not fix the issue !
Now this might have been a coincidence but in the afternoon I realized that Google backup was stuck to "waiting to backup" so I used ADB commands to fix this known bug. I followed these instructions: https://forum.xda-developers.com/mi-8/how-to/guide-google-backup-waiting-to-backup-t3895101
After that - it might be a coincidence, though - I could write to the NM card ! It seemed that the issue was resolved. Somehow 3rd party apps could have write access permission to the NM card !
I was happy, but today when I woke up the problem had resurfaced !
I tried installing every single Root Explorer there is in the Play Store, but none worked. I also tried with like other 5 File Explorers to see if they could re-enable access to write to the NM card, but nothing worked.
I have enabled Developers options & then enabled "Force allow apps on external storage" but this does not solve the problem, either.
Any ideas what could be happening here ?
Could this be a bug with EMUI 10 and the write permissions to the external storage ?
I'm thinking that if this was a corrupted NM card issue, then neither Huawei Files manager, or Camera app, etc would be able to write on the card, right ?
Any help would be appreciated !
SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.
Click to expand...
Click to collapse
Solution answer
So this one is weird.
Everything was working fine untill I rebooted my phone earlier today.
For some reason, since this reboot, apps are unable to access my SD card storage. As far as I know, no update was applied with this reboot. I do not recall tinkering or changing anything related to this recently.
Symptoms
SD card is still visible in the storage tab of the settings (there is no available option to unmount or eject it) or in select cases when choosing a folder from an app, however the content does not show up past the root.
My music player (Oto music) sends an error message "Cannot play this file" while trying to play a song from the SD card
File explorer will not show the SD card directory at all
Resillio Sync has a synced folder on the SD card. It now says "Can't open the destination folder". If I try adding a new synced folder on the SD card and select the root of the SD card, I get the message "Android OS restricts access to this folder"
Google file is stuck in a loop trying to get permissions to access the card
SD card works just fine on another phone.
Other SD cards have the same problem with my phone, not just this one
SD card does not show up when using file transfer with a Windows PC
Rebooting the phone did nothing
Removing the card and putting it back in again did nothing
Formatting the card did nothing
I factory reset the phone. It worked, but the problem came back at the first reboot.
Current state of investigations I have reset the phone a second time and reboot it every time I install an app, uninstall or disable a system app or change some settings. So far the SD card is still accessible so I know what it's not:
it's not the fault of disabling system apps
it's not related to using a work profile (Insular)
still haven't found an app that causes it
Apps I have not tried re-installing on my second reset and that might be the curlprit:
Shizuku (I have my suspicions on this one, let me know if this one is known for causing similar bugs) Not Shizuku per se but a developper option needed for it (see solution answer)
I have no idea what could cause this, all I know is it's related to my phone in particular and it appeared out of nowhere.
I am using Android 13 on ColorOS.
Thanks to anyone who can help.
Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.
blackhawk said:
Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.
Click to expand...
Click to collapse
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?
Iune said:
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?
Click to expand...
Click to collapse
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.
blackhawk said:
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.
Click to expand...
Click to collapse
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.
SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.
Iune said:
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.
Click to expand...
Click to collapse
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.
blackhawk said:
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.
Click to expand...
Click to collapse
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help
Iune said:
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help
Click to expand...
Click to collapse
Yay! Well done. So many settings...
Traditionally a hard reboot is killing the power to the mobo... I believe, or maybe I just watched too many sci-fi movies You do it by holding the power button (or combination of buttons) down for 20-30 seconds.
On cams and older phones you simply remove the battery for a few seconds. It clears any volatile memory settings in the chipsets or semiconductors by cutting to power to everything.