Hey there, I'm having a weird issue with apps not being able to write to internal storage. I'm using stock rooted 4.4.2, things work after a hard reset but soon after es file explorer shows that my home directory changed to storage/emulated/legacy instead of /emulated/0 and things just dont work correctly. Eg. Instagram gives me an error, snapchat, Baconreader and imgur also fail to save images. I did use sd write fix, dunno if that could cause any issues.
Related
I am running the latest CM nightly. The system states that I am out of memory. When I go into Settings > Storage and refresh, it shows several GB available. I can't install any more apps. I deleted all of the apps I know longer use. I had about 600 pictures in my gallery. Since I sync with Dropbox and Google+, I deleted all of those as well. I changed my email retention from 7 days to 3. I cleared the app data of all apps.
Still getting this strange problem. I looked and there were a ton of strange log files in /data/system. They were RS_01.log, RS_02.log, etc, all the way to RS_90.log. Each log file was about 910 bytes. I deleted all of them in root explorer and rebooted. Same problem.
I can factory reset and reinstall CM, but want to see if there is a fix first. Found online people saying to dial *#9900# and deleting a log file, but dialing that number does not open a menu. Might be due to the fact that I have a later bootloader (M2), or that I am running CM.
Ideas?
Give lucky patcher a try. There's an option to odex system files which frees up int storage
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I can't install any apps. Android is throwing an error, not enough system space to install whenever I try to install anything. This has to be some sort of runaway log. I found references to dumpstate logs causing this problem, but they are all in /data/log. I don't have that directory on CM11. Not sure where to look.
I found solution..
Go into your time tool box and set apps to sd to auto. having it set on ext sd messed ours up too. Easy fix for us. Hope it helps.
hi all
so my transition to kitkat hasnt been without its hiccups and the latest one is probably quite big. So since 4.4 we're not allowed to write in the external SD as I have seen it put. my problem is shown by 2 different apps. one is the gallery (or quicpic that I use) when trying to delete a photo I took (and since I have my photos being saved on the SD) I get a message saying it failed! gallery seems to let me do it and delete the photo but when I check in quicpic or the files themselves the photos are still there. the other app is my sms backup and restore app where again I have my backup saving to the SD but when I try to select it it says I wont be able to use it and as is expected when I try to back it up it doesnt work.
why would they implement such a policy?! that goes completely backwards! is there a fix or a workaround?
really appreciate the help
You can fix it by rooting (+ e. g. NetApp SDFix) or wait for app developers to change their apps (in terms of storing data in private data folder, for instance '/storage/extSdCard/Android/data/com.google.earth') - or if possible change the storage path by yourself.
Sent from my black pearl using Tapatalk
nunein said:
You can fix it by rooting (+ e. g. NetApp SDFix) or wait for app developers to change their apps (in terms of storing data in private data folder, for instance '/storage/extSdCard/Android/data/com.google.earth') - or if possible change the storage path by yourself.
Sent from my black pearl using Tapatalk
Click to expand...
Click to collapse
how can developers change their apps since they wont be allowed to write on the SD? and what do you mean change the storage path by myself? as in to have stuff save on my phone? cuz thats what Im avoiding
As I wrote: every app has write access to its 'private' data folder of the SD card (if it creates such a folder). The folder name has to match the app name.
For instance '/storage/extSdCard/Android/data/com.example.app'
Disadvantages are that other apps do not have write access to these folders - and that data of an app will be deleted from its 'private' data folder if the app will be uninstalled.
The temporal solution is to root and use any KitKat fix to write in SD, there are single apps xposed modules flashable zips write some string in some system file.
fburgos said:
The temporal solution is to root and use any KitKat fix to write in SD, there are single apps xposed modules flashable zips write some string in some system file.
Click to expand...
Click to collapse
any pointers on where I could find such a thing?
See post no. 2: SDFIX (from NextApp), available here or at Play Store
Ok so I'm on an H810 and it's rooted. Software version H81010b. Now I have hardly done anything root wise aside from enabling the Hot Spot really. Now for some reason when I take pictures my camera thinks it's saving it to my SD CARD, but when I look, the picture is correct, just shows a strange icon, see attached. It used to work fine. At the same time Titanium backup used to work fine now it says that the directory I'm pointing it to is readonly. !? I have already enabled write access on my SDCARD long ago using the Netxapp fix and if I run it again it says that there's nothing to be done because write access is already set up. When I take a picture, the thumbnail shows up in the small window/circle, but when I touch it to load the image, it shows me a blank image actually. Now if I set the camera to take images on the INTERNAL sd card, then it's fine. I wasn't having any issues with this until a couple days ago... any ideas? Solutions? Thanks!!
OK, think I figured it out. I went into ES File Explorer and went to ROOT EXPLORER and then to MOUNT R/W and it showed the external sd card mounted as read only. If I set it to r/w then my camera and other apps work fine writing to the sd card. If I reboot my phone however, the problem comes back until I LAUNCH ES FILE EXPLORER but I don't have to do anything else, after I launch it everything else can write to the sdcard again. I am guessing this happened because I disabled boot notification/boot startup for es file explorer. My bad. Strange though that this has such a prolific effect on the device since this is a 3rd party app. HOWEVER, I do have root explorer enabled in it so maybe that has something to do with it?
When I try to open via file explorer (because apps just don't have acces to the memory like it wasn't connect at all) a video/music files from external memory with non-stock app (VLC for example), an error occur that tells that the file can't be open. When I choose stock video player everything works fine. Also all non-stock apps have granted all permissions, so why it does not work?
PS.: Hello everybody
Hello everyone, I flashed stock rom (Sense7-Marshmallow-4.11.401.1) into my Desire EYE. Everything is okey, but while moving or copying a file into Internal Storage it says "xXx can not move here". I downloaded ES and FX File Explorer, tried every way. FX File Explorer says " Access was denied". Although I have full access on External Storage, I have no access in Internal Storage. Even photos or videos can't save internal storage.
Is there any suggestion ??? I flashed 3 times, but it doesn't work. I think the problem is 'permission' file. I know the problem, but I don't know the sollution
Thanks for everything
fcansun said:
Hello everyone, I flashed stock rom (Sense7-Marshmallow-4.11.401.1) into my Desire EYE. Everything is okey, but while moving or copying a file into Internal Storage it says "xXx can not move here". I downloaded ES and FX File Explorer, tried every way. FX File Explorer says " Access was denied". Although I have full access on External Storage, I have no access in Internal Storage. Even photos or videos can't save internal storage.
Is there any suggestion ??? I flashed 3 times, but it doesn't work. I think the problem is 'permission' file. I know the problem, but I don't know the sollution
Thanks for everything
Click to expand...
Click to collapse
having same issue after flashing similar or maybe the same rom u did ,,, also the device is lagging like badly frame per second lag unusable ,,, trying diffrent solutions to use the eye any way if this failes i will try flashing ubuntu on it just to see if it would fix it
-tried relocking bootloader and unlocking (deleting everything again starting all over)
-had a working cyanogenmod recovery mode - lost it while trying to change it with flashing a twrp 3.2.1 -0 for desire eye that i found here on xda