Related
Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.
Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.
I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.
4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium
No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.
Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?
I fixed this deleting the "pictures" folder with RootExplorer.
jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .
My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!
Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.
Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0
/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk
I updated my Vzw GNex to the vzw 4.2.2 ota this afternoon. Everything works fine except when I try to download something from chrome I get a message saying "No SD card" when I click a download link. I can access the sd card just fine with rootexplorer and the stock browser downloads things just fine. I tried clearing cache and data for chrome and even uninstalled and reinstalled it. Anyone else having this issue? Is there a way to fix it?
MurdocZero said:
I updated my Vzw GNex to the vzw 4.2.2 ota this afternoon. Everything works fine except when I try to download something from chrome I get a message saying "No SD card" when I click a download link. I can access the sd card just fine with rootexplorer and the stock browser downloads things just fine. I tried clearing cache and data for chrome and even uninstalled and reinstalled it. Anyone else having this issue? Is there a way to fix it?
Click to expand...
Click to collapse
I am seeing the same issue on my GNex running AOKP mr-1 build 6. I have not found a fix yet.
Of note: I do NOT have this issue on my Xoom running 4.2.2 [baked_wingray_bb-8]
Try making a copy of your sdcard and factory resetting, then copy all the files over using MTP, not ADB.
I get that if i copy files over using ADB.
Mach3.2 said:
Try making a copy of your sdcard and factory resetting, then copy all the files over using MTP, not ADB.
I get that if i copy files over using ADB.
Click to expand...
Click to collapse
Mach - Thank you for your response. I have to ask though, is there any other way?
Per your recommendation I began to copy my sdcard but quickly realized that given the amount of data on my phone this would be painful using standard methods. Windows [7] was reporting no progress and seemed as if it was going to take forever to copy the contents and applications like RichCopy and TeraCopy do not see MTP devices
In the end, I simply used 'adb pull' to copy the contents. So, while it's good that I have a copy, I'm not sure how I plan to restore the copy after a factory reset without using 'adb push', which you said sometimes causes the issue. I always thought that using 'adb' was considered more reliable than the MTP interface.
Recommendations?
Thank you.
Hi, if you are running Xprivacy you should check if you have denied the 'Storage' permission for Google Chrome. That was the problem in my case.. :silly:
getting same problem on my moto g after rooting and flashing sm roms
Megabliss said:
Hi, if you are running Xprivacy you should check if you have denied the 'Storage' permission for Google Chrome. That was the problem in my case.. :silly:
Click to expand...
Click to collapse
hy its not the thread for moto g bt im getting same problem on my cell since i rooted it .. and by the way what u mean by xprivacy..??? xplain steps to allow it...
it seems like my system cant make changes to internal sd .. it cant take screenshots,gallerythumbnals all gone etc. -_-
I had similar troubles after changing roms on my N5, found this that fixed it just download terminal emulator and do the given commands, hope it helps people in the future: http://blog.wadegarrett.com/2014/08/10/easy-solution-for-sdcard-error-on-android-l
I have the same problem and the info in the link didn't work
CalebQ42 said:
I had similar troubles after changing roms on my N5, found this that fixed it just download terminal emulator and do the given commands, hope it helps people in the future
Click to expand...
Click to collapse
Thanks! It worked for my Xperia z ultra
lakhwani009 said:
hy its not the thread for moto g bt im getting same problem on my cell since i rooted it .. and by the way what u mean by xprivacy..??? xplain steps to allow it...
it seems like my system cant make changes to internal sd .. it cant take screenshots,gallerythumbnals all gone etc. -_-
Click to expand...
Click to collapse
Hi, sorry it took a long time to reply, I just saw it. Xprivacy is an Xposed mod to manage the permissions for each app. If you haven't installed it then it is not causing you any problems!
In regards to my aforementioned issue.
"Cannot download due to SD card missing" Error.
Simply open a terminal emulator and type in the following.
su
restorecon -FR /data/media/0
Reboot and it should work thereafter.
wrong thread, genius, sorry.
(that is the solution though )
CalebQ42 said:
I had similar troubles after changing roms on my N5, found this that fixed it just download terminal emulator and do the given commands, hope it helps people in the future: http://blog.wadegarrett.com/2014/08/10/easy-solution-for-sdcard-error-on-android-l
Click to expand...
Click to collapse
I had the problem with my Galaxy S3 running Lineage OS 14.1. This helped, Thanks!
I have just found another and simply solution in no rooted devices. Just open file manager and rename 'Download' folder to 'Download2' and then the system will automatically recreate 'Download' folder. Now, you are able to download.
mbahar92 said:
I have just found another and simply solution in no rooted devices. Just open file manager and rename 'Download' folder to 'Download2' and then the system will automatically recreate 'Download' folder. Now, you are able to download.
Click to expand...
Click to collapse
That worked for me. You saved my day!
I have rooted and have disabled most of the recommendations listed here: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503
I now find myself unable to create a folder (using ES or ASTRO) in any directory?
Very confused
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)? I checked out that thread, downloaded the "SDFix: KitKat Writable MicroSD", rebooted and still does not work. I am attempting the wanam xposed fix but whenever I attempt to use the xposed installer, it can't extract (due too inability to write to disk). Is there a way to install xposed via odin?
Thank you for the response. I am new to rooting and Android in general, but I am trying!
lordnorth4 said:
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)?
Click to expand...
Click to collapse
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Freakstyler said:
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Click to expand...
Click to collapse
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
same issue
lordnorth4 said:
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
Click to expand...
Click to collapse
I have the same exact issue. I can add folders through the Samsung My Files; the ES File explorer gives me 'Sorry, operation failed' also. I have reformatted, and re-rooted, but same issue.
Im no expert mind you, but i had this exact same issue, pretty sure its a kernel issue, specifically i think selinux and its two modes passive and enforce.........first i tried an app on the store thats suppose to change this mode upon reboot, before i realised newly installed apps were now also having issue with internal storage........anyways, long story short, i checked out the lone kernel in the dev thread, paraphrasing, selinux disabled, or some such, and bingo bango, everythings back the way it was
If you have recovery, might be worth backing up and flashing kernel, see if that works, report if it does for the benifit of others that might find themselves with internal storage issues
Edit
T700/T705 version
http://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-skyhigh-tw-kernel-t2806563
"SELinux PERMISSIVE" - turns out kernel is permissive by default, not disabled
T800/T805 version
http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
Hopefully thats usefull
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
UpInTheAir said:
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
Click to expand...
Click to collapse
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
banderos101 said:
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
Click to expand...
Click to collapse
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
UpInTheAir said:
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
Click to expand...
Click to collapse
Thanks by the way, for your kernel, and its rescue of my device .........and not least of all, the work you've done with our devices:highfive:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
Worked fine until i started rooting and flashing the recovery, pretty sure during that process something triggered this issue
UpInTheAir said:
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
Click to expand...
Click to collapse
Yup, first post in the Samsung threads and I messed up. Now I have to find a proper thread to get an answer....
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
banderos101 said:
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
Click to expand...
Click to collapse
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
UpInTheAir said:
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
Click to expand...
Click to collapse
Okay, i could have sworn that i was experiencing the same issue on the external, aswell as the internal, infact im certain, i remember trying the external fixes first, assuming i had the kitkat external storage issue, untill i noticed it was also happening to the internal storage.......this was the first and only thread i found concerning internal issues, maybe i had both issues, but then again, the kitkat fixes didnt fix the external issues, your kernel seemed to fix both, at least in my specific situation
Edit
Okay, i see maybe you were answering my question from a more knowledgeble perpective, it just seemed that whatever affected the internal, was also affecting the external, otherwise, wouldnt the sdfix and/or root file managers like es file explorer with a kitkat/sd workaround, worked, both of which i tried.......seems like whatever was affecting my internal was also affecting external..........one way to find out is if folks who find themselves with the internal issues could confirm if they also have external issues, and whether the external fixes work or not
Edit
Ive just come to realise the fact that i was having internal storage permission issues might have caused the external storage fixes not to function properly, and that maybe i did indeed have two seperate issues, and that whatever was affecting my internal storage was a different issue to the kitkat/external sd card issue, so maybe you are right in saying that this only fixes the internal storage issue, which in turn allowed the external storage fixes to work.........hopefully time will tell, and hopefully, some of that makes sense
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.
Hi, I've flashed my US Le 1 Pro first with Beta Hydri v4 but because I had the malware stock US rom it came with the phone. In the stock rom Hifi and that changing display didn't worked but i didn´t really care but everything else did , like gyroscope and compass (and very well) but since i've flashed to Beta Hydri v4 with full wipe, some axis are inverted, I think X in accelerometer is outputing negative values instead of positive.
I've trying flash other roms (like cuocu92 14s and the original stock I had from my backup) but didn´t worked. I'm so sad because I've just bought 2 days ago the bobovr z4 so i could use it for vr.... :'(
Can someone help me?
I noticed this problem when I tried to use Google Camera for (360° spherical panoramas) very frustrating.
At this moment one solution is use other phone to VR.
simondd said:
At this moment one solution is use other phone to VR.
Click to expand...
Click to collapse
It works with original rom but you have to wipe everything except your sdcard.
At least for me now working perfectly.
I am having the same issue. My phone is rooted. I am surprised there are no apps or anything that can invert the VR for us.
CM 12.1
dreamwalkerfx said:
I am having the same issue. My phone is rooted. I am surprised there are no apps or anything that can invert the VR for us.
CM 12.1
Click to expand...
Click to collapse
Thanks to @BetaHydri, he fixed this issue in the CM12.1 V4.2
Additional Infos about how to fix
Thanks very much for the quick reply!
I flashed to 4.2b using TWRP and then installed the gapps, I really did not want to format my device.
4.2b fixed my GPS issue thank God, but the VR is still inverted.
Went into TWRP file manager using recovery, and tried to move the new .conf file from the 4.2b zip to the /sensors/etc folder.
This didn't seem to help at all. There is still nothing in the /persist folder.
Any ideas would be appreciated.
Cheers
dreamwalkerfx said:
Thanks very much for the quick reply!
I flashed to 4.2b using TWRP and then installed the gapps, I really did not want to format my device.
4.2b fixed my GPS issue thank God, but the VR is still inverted.
Went into TWRP file manager using recovery, and tried to move the new .conf file from the 4.2b zip to the /sensors/etc folder.
This didn't seem to help at all. There is still nothing in the /persist folder.
Any ideas would be appreciated.
Cheers
Click to expand...
Click to collapse
First time I flashed the V4.2, I came from the Stock Rom, it didn't fix the Gyro problem, but as I remember you should delete/rename these files first (sensor_def_qcomdev.conf - sensors_settings - sns.reg) then in TWRP do a factory rest and wipe Dalvik + Cache.
Reflash the Rom again.
Thanks for the quick response.
Unfortunately with the lack of time I can't look at factory reset... it would take me forever to re-load all apps, docs, pictures, etc.
I am wondering if there's a manual way to do this through TWRP -- ie. copying the correct sensor files into their respective folders, clearing cache, and seeing if that works.. right now my /persist folder is empty
If anybody has a chance that has a working gyro, I'd love a copy of their sensors folders both in persist and system.
dreamwalkerfx said:
Thanks for the quick response.
Unfortunately with the lack of time I can't look at factory reset... it would take me forever to re-load all apps, docs, pictures, etc.
I am wondering if there's a manual way to do this through TWRP -- ie. copying the correct sensor files into their respective folders, clearing cache, and seeing if that works.. right now my /persist folder is empty
If anybody has a chance that has a working gyro, I'd love a copy of their sensors folders both in persist and system.
Click to expand...
Click to collapse
The factory reset doesn't wipe your internal storage, only the apps installed and settings will be restored to default.
Anyways, if tomorrow I get free time I will upload the files needed for you.
Does your GPs lock on OK?
May need to reflash, no idea what I did wrong but the GPS does not work. Bounces around the map every few minutes.
I can confirm, I reflashed today -exactly- as instructed on the instructions in the 4.2b thread, re-installed all apps, etc etc.. an hour process at least..
The gyroscope is still inverted,
After dalvik + cache cleanup in TWRP and after boot you should have in /persist/sensors folder three files:
1. error_log
2. sensors_settings
3. sns.reg (this has now all new settings in an encrypred format from the sensor_def_qcomdev.conf file)
And on /system/etc/sensors only that above mentioned clear text sensor_def_qcomdev.conf file.
Click to expand...
Click to collapse
and there is still -nothing- in the /persist folder...
I have the one file in /system/etc/sensors, but I don't have it in /persist.
I'm ready to throw this phone out the window
---------- Post added at 06:22 PM ---------- Previous post was at 05:36 PM ----------
My bad, there are the 3 files in the persist folder (had to activate root explorer in ES).
No idea why it's not working.
For the GPS, I have no idea because I don't use it at all. Go to CM 12.1 BetaHydri thread
I attached a Zip file contain all files with their respective directories as shown below.
Code:
system/etc/sensors/sensor_def_qcomdev.conf
etc/sensors/sensor_def_qcomdev.conf
persist/sensors/error_log
persist/sensors/sensors_settings
persist/sensors/sns.reg
Good luck.
nsmsdz, you are the man.
After replacing all the files/overwriting, and a reboot, it works fantastic.
May the Android Gods be with you always.
help
Hello.
I lama, I need help. He tried more ROM, still the same problem. I do not know if this one problem, I do not know how to delete and replace files. The phone ROOT files, but I can not see. Thank you very much for your help.
Sorry for the English, translated into translator.
Newbie can not embed the video, this is the only way
video:
youtu.be/YDJmj_dM8CY