Recently I flashed a new ROM and then added Google Now to my phone by following the instructions here (http://forum.xda-developers.com/showpost.php?p=29756226). After doing so, I found that my camera no longer saved photos and that I could not take screenshots. For screenshots, I would receive the error "Couldn't capture screenshot. Storage may be..."
I found a lot of entries about this and/or similar problems on the forum. Many of them had complex permission resetting (or device wiping) instructions. I found that by erasing the memory card from within the android settings menu and then re-mounting it, my permission problems (and the saving problems) went away. It's a really simple solution and probably won't work for all folks, but I hope I can save someone else frustration and hassle.
Related
I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.
I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.
replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.
I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.
SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers
SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.
I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.
Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs
@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks
Hi all,
A brief history of my device: Hardware failed so I create a backup image, send the busted phone for warranty, and restore the image on my new hardware. I think some permissions weren't quite set right when I restored from the image, I noticed problems like:
1) My camera complained I had no storage space (it didn't have permission to write to the sd card). If I remember correctly, I had to manually fix some permissions to fix this.
2) (The current problem I am writing about): In the Google Maps application, when I tried to save a region for offline use, it said something like 'Storage Error' in red (I don't remember exactly what the message was because I updated the app, see below).
In an attempt to fix this, I updated the Maps application to the newest version. The new version has a different 'offline maps' implementation. This new implementation claims to be downloading/caching the map, but if I exit the app and re-open it, the map is not actually stored anywhere.
Question: Does anyone know how to fix this?
At the very least...can anyone tell me where google maps stores its offline maps so I can try to manually fix permissions?
Thanks!
-Julian
Shameless bump because I'm out of the country and offline maps would be nice!
Any help appreciated!
Generally apps store their data in 1 or 2 of the following places:
/sys/data
/data/data
/sdcard/Android
If you're rooted with a custom recovery, the recovery app should have a fix permissions. I know twrp and cwm do.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks
try to apply kitkat sdcard fix
click
I have the Xperia Z3 running on Lollipop.
Same issue, all apps such as whatsapp, fb, etc can access the SD card except for line.
The error message when trying to send a photo to someone in Line is "Can't use SD card. Please confirm SD card settings"
Reinstalled the app several times, unmounted and remounted the SD card, even moved the app to the SD card with the app itself still working fine. But still cannot send or receive photos or download stickers.
Also applied the suggested that sd card fix even though it wasn't really needed since all other apps can access the SD card just fine..anways it didn't help.
Any other ideas?
Oh yeah, even tried installing a Line version which was 6 months old - didn't help either.
mcdimm said:
Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks
Click to expand...
Click to collapse
I have the exact same issue after a full wipe and re-flashed custom ROM. The naver LINE app have the same issue as mentioned above. All other apps functions normal. Anyone found a solution to this yet?
HTC One M7
Vipeone sense-based ROM 9.0.0.
Hi. I've encountered a similar problem recently. The interesting thing is that my telephone does not have SD card at all. So my first thought was that the problem is in permissions or cache.
I checked the permissions - app had full access.
Then I cleared programm cache on my phone. both inner memory cache and telephone memory cache (at least that's what they are called in my native language)
After that I tried to upload the image, yet it gave another error. something like: "cannot perform the action now, try again later"
I was quite short on the inner memory on my phone (around 70 MBs free), and thought it can be the problem. I deleted the biggest app and was able to upload the screenshots again.
Probably worth mentioning: I did not reinstall the Line app.
My device:
Telephone called ImSmart C471. China at it's best. Assembled in Ukraine though, company called Impression.
Android 4.4.2
In the latest build, Line apk cant send photo from internal/sdcard..it said line cant use sdcard..?
i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.
where's the settings?
andrew_susanto said:
i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.
Click to expand...
Click to collapse
I can't find any setting for permission to storage from the application manager, is there any? did I overlooked?
Try updating the app in play store. I had the same issue but solved with the updated version.
I had the smale problem. I deleted some pictures and videos and then restarted the phone. Works like magic
Repost from Sprint forum area, since this main area is much more active...
I have some weirdness going on with my LS990, still running the original ZV4 with Xposed and TWRP. I've never had any problems, until now, with anything on this phone, it's been fantastic and that's why I leave it on Kit Kat.
Starting yesterday, whenever I try to open the stock File Manager, I get the following error dialog:
------------
Note
Cannot read files. File Manager will be closed. Please check Media Storage enable settings and try again.
OK <--button
------------
Sometimes the dialog is in the foreground and I can close it with OK, but File Manager never opens. Sometimes the dialog appears behind my launcher icons and everything is unresponsive until I kill the running process using my nav bar shortcut from G3 Tweaksbox.
Also, I was trying to take a screenshot to include with this post, but it gives an error (Cannot take screenshot. Try again.) when trying to save it, plus the notification just stays on "Saving Screenshot" and is unable to be swiped away. [UPDATE: Noticed the screenshots do get saved in the proper Pictures/Screenshots folder, but the notification remains "stuck"]
I have also noticed my gallery is now empty, yet I can still access all of my pics from third-party file managers. Plus, when I open the camera and take a picture, it doesn't show in the little Gallery bubble at the bottom of the screen - in fact, the bubble doesn't even work, but yet the picture is saved properly.
Has anyone seen behavior like this before? The only thing I have changed on the phone is flashing the new TWRP 3.0.0.0 yesterday, using the image feature in my previously installed TWRP 2.8.7.0. I've updated TWRP plenty of times and there has never been an issue, but one difference I did notice this time was it asked if I wanted to keep System read-only or the default swipe to make read-write, which is what I did since I have Xposed and it modifies the System anyways.
Hopefully someone out there has an idea how to fix this, I really don't want to start all over, at least not until Sprint releases MM for the G3. The strange thing is, everything else is working just fine. My phone is fully functional except for the quirks mentioned above, root is still there and Xposed is functioning properly. I did do a Safe Mode boot to see if I could eliminate any root apps, but the issues were still there even after a safe boot.
Try sd card write fix on the market just for kicks u mighta lost permissions to the ext sd try switching save point to internal and see if they save
Unfortunately, I'm not using a microSD card, everything is saved to the internal memory. I thought it might be something with permissions, was thinking about trying the "fix permissions" option in TWRP but I'm not sure if that would make things worse. I've already tried a cache and Dalvik wipe, but that didn't fix anything. Even in Safe Mode, nothing changes.
I've searched online and haven't seen anyone else with this issue, it's very strange. I wish Sprint would hurry up and drop the MM update so I would have the perfect excuse to flash back to stock.
Hello everybody,
maybe one of you can give me a hint where this problems might come from and how to fix:
I have installed LimeageOS 18.1 on my Fairphone 3+ successfully (incl. OpenGApps & Magisk) and in the beginning I was able to install some apps (e.g. WhatsApp) from my old phone (using "adb install <appName>.apk" as well as transfering the data structure(s) from the old phone to the new Fairphone (incl. fixing permissions, etc.).
The next time I wanted to continue this and install further apps from my old phone, this is blocked by the Fairphone (Signature failure). I was able to solve this by disabling the app checking when installing is done from/by adb. But the installed apps crash every time I try to start these. When I install these by the PlayStore these work. Previously I definitely was able to install apps without deactivating the security check in the system settings and these were working!
Furthermore, I had successfully installed and used WhatsApp as described previously. But: some day, BEFORE I started to install further apps using adb, WhatsApp started refusing to show the status pictures/videos as well as refuses to download pictures send to me (message: file not found on sd-card). But I still can upload pictures.
Between initial setup and installation of some apps, I've done nothing special except inserting an SD card and formatting as extension of the internal memory. At least I don't remember more...
Has anybody an idea what might have happened and how I could make things working without a full re-installation?
Any hint is welcome!
Regards,
Markus