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
Related
Next JB problem: When I installed stock JB, I did a wiped data/cache, but when I booted up, I could see that all the folders were still there in Root Explorer as well as Airdroid. But, Android can't see them. What I mean is, if I open up Gallery, it claims I have no pictures stored on the device, despite actually having hundreds of pictures in several folders. Quickpic sees them just fine, but Gallery doesn't. I'd rather use Gallery because it can find pics from Picasa, which saves a ton of space on the phone.
How do I get my phone to see the folders that are still there?
I updated to Bigxie's ROM, but that didn't resolve it (not that I necessarily expected it to).
sorry, can't really help, as it worked for me without problem from the beginning.
maybe it just takes some time until media scan was operated? or are you using any filters like the .nomedia-manager?
No .nomedia files. If I plug in a USB port to connect it to my PC, it only shows a few empty folders, nowhere near all that are there. There's a Pictures folder, but it's empty, even though my Pictures folder actually has a bunch of files and folder s in it. It's like it's looking at some other partition or something.
That happens to me... i fix it by restoring my previos rom backup, and then doind a dirty flash of the JB Rom (only Dalvik and Cache wipe)
Same here .. no media file in gallery so I flash my old rom...
Sent from my Galaxy Nexus using XDA Premium App
Raisone said:
That happens to me... i fix it by restoring my previos rom backup, and then doind a dirty flash of the JB Rom (only Dalvik and Cache wipe)
Click to expand...
Click to collapse
That sounds like a good solution, except whatever it is that's preventing me from finding my media files is also preventing me from accessing my Nandroid backup.
E:Unknown volume for path [/emmc/clockworkmod/backup/2012-06-28.00.32.22]
Cat't mount backup path
result was NULL. message is: assert failed:
restore_rom("/emmc/clockworkmod/backup/2012-06-28.00.32.22". "boot", "system", "data", "cache", "sd-ext")
I:using /data/media, no /sdcard found.
Might have to do with the sdcard being linked to another folder in storage
KJW979 said:
Didn't see mentioned in here but over at rootzwiki is being mentioned that the reason some can't wipe and return to a previous rom might have to do with JB adding a new folder named storage. If go into root explorer or similar right below folder Sd there is a storage folder if opened brings up another folder named sd, seems to be a duplicate sd folder. I can't remember ever seeing it on any previous rom's. Also nobody sure consequences if deleted. Personally not much knowledge, just passing along.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll have to remember that for next time. I gave up and did a factory wipe from Galaxy Nexus Tools, and am in the process of restoring my Nandroid, then I'll do a 'dirty' JB upgrade from there and hope it doesn't do the same thing twice. If it does, I'll just stick to ICS.
NeoMagus said:
Might have to do with the sdcard being linked to another folder in storage
Click to expand...
Click to collapse
Just saw that, thank you for your post. It's weird, though, is it mirroring the SD card? I've got my SD card almost full, and if it duplicated it I would have gone way over.
I decided not to take any more chances now that I'm back to ICS. I'll wait for the official release. I don't think Google Now and the smoothness make up for the loss of themes and customization.
Sent from a connected, sensor-laden supercomputer that fits in my pocket
Did anyone find a way to fix this without a reflash?
Archpope said:
Next JB problem: When I installed stock JB, I did a wiped data/cache, but when I booted up, I could see that all the folders were still there in Root Explorer as well as Airdroid. But, Android can't see them. What I mean is, if I open up Gallery, it claims I have no pictures stored on the device, despite actually having hundreds of pictures in several folders. Quickpic sees them just fine, but Gallery doesn't. I'd rather use Gallery because it can find pics from Picasa, which saves a ton of space on the phone.
How do I get my phone to see the folders that are still there?
I updated to Bigxie's ROM, but that didn't resolve it (not that I necessarily expected it to).
Click to expand...
Click to collapse
Where did you find a Galaxy Nexus with a SD card slot?
Wondering if anyone can help...
on JB, stock google apps and system apps won't recognize my SD Card at all, while outside apps have no problem recognizing it...?
for example, stock Gallery app won't bring up my pictures, however Quick Pic has no problem. Root Explorer has no problem, Titanium Backup has no problem...but trying to access music or custom notifications for gmail/sms won't show up in the system apps (gmail, mms, etc).
another thing is when I plug my phone into my computer, none of my old files are there (but like I said they show up just fine with Root Explorer or any other file explorer).
I've tried every JB Rom available for Toro, yes I've tried SuperWipe, I've done it all.
Any ideas, fellas? Any help would be greatly appreciated. Thanks
philsfan said:
Wondering if anyone can help...
on JB, stock google apps and system apps won't recognize my SD Card at all, while outside apps have no problem recognizing it...?
for example, stock Gallery app won't bring up my pictures, however Quick Pic has no problem. Root Explorer has no problem, Titanium Backup has no problem...but trying to access music or custom notifications for gmail/sms won't show up in the system apps (gmail, mms, etc).
another thing is when I plug my phone into my computer, none of my old files are there (but like I said they show up just fine with Root Explorer or any other file explorer).
I've tried every JB Rom available for Toro, yes I've tried SuperWipe, I've done it all.
Any ideas, fellas? Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
have you logged in to your account??? Cause I know sometimes if you are not logged in then your stock photo gallery will not show your photos....as far as not seeing them in your pc I don't know you might be shif out of luck cause if they are not there they not be there at all
Sent from my Galaxy Nexus using Tapatalk 2
Same issue here....looking for a solution...
The files are definately there...I can open them from the device but not via USB and not using Gallery. Its as though its a permission issue but I ran a fix permissions using ROM Manager but no joy....
having the same issue too. hope to get solution soon.
aidanbree said:
Same issue here....looking for a solution...
The files are definately there...I can open them from the device but not via USB and not using Gallery. Its as though its a permission issue but I ran a fix permissions using ROM Manager but no joy....
Click to expand...
Click to collapse
logged in.
files are definitely still there bc, as i said in OP, I can view them with Root Explorer and other file managers. Only with stock apps and system apps it seems to not see them.
i think it's a media server issue but i'm not educated enough on how to fix it
aidanbree said:
Same issue here....looking for a solution...
The files are definately there...I can open them from the device but not via USB and not using Gallery. Its as though its a permission issue but I ran a fix permissions using ROM Manager but no joy....
Click to expand...
Click to collapse
Try this.
Hi efrant
Thanks for the suggestion. Gave it a go (tried it twice) but unfortunately it hasn't made any difference.
I'm having the same problem... I did notice that not everything under /data/media had media_rw as the owner/group but fixing it didn't fix the media server issue.
It's definitely a media server issue though as from what I've read it's responsible for listing the files when connected via MTP/USB so I haven't found a fix for it.
I've always thought MTP was flaky. I use ADB to transfer any files back and forth.
Downloading any SDCard rescan app doesn't seem to work... but what I have noticed that if you go to Settings -> Apps -> Running and look under Media, you should see that the service is stuck in the restarting state...
I/ActivityManager( 336): Process android.process.media (pid 2148) has died.
W/ActivityManager( 336): Canceling start item Intent { cmp=com.android.providers.media/.MediaScannerService (has extras) } in
service ComponentInfo{com.android.providers.media/com.android.providers.media.MediaScannerService}
W/ActivityManager( 336): Canceling start item Intent { cmp=com.android.providers.media/.MediaScannerService (has extras) } in
service ComponentInfo{com.android.providers.media/com.android.providers.media.MediaScannerService}
W/ActivityManager( 336): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 1440256ms
W/ActivityManager( 336): Scheduling restart of crashed service com.android.providers.media/.MtpService in 5000ms
I/ActivityManager( 336): Start proc android.process.media for service com.android.providers.media/.MtpService: pid=2249 uid=10013 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
Click to expand...
Click to collapse
Sejanus,
Mine is restarting too.
I have noticed that if I use a file manager to duplicate an old file (e.g. photo) then I can access it...It looks like some sort of weird permission issue although I have tried all sorts of things to sort the permissions.
I'm using the GNex Toolkit V7.0 to pull everything from my virtual SD card /sdcard and then I'm going to delete everything, reboot, then push everything back to it, reboot, then see if that fixes it.
efrant said:
Try this.
Click to expand...
Click to collapse
I just tried, and it didn't work. Double checked, there was no file with a different user/group.
It seems that now my Media is not restart anymore, however I still can't see my files, neither through Google Music / Galery (although some show up), nor using USB to computer (only a few folders show up).
Therefore, nothing yet.
Any clues guys ?
Probably a solution! (at least it did work for me)
Guys, for those having issues with Media process, where Pictures & Musics don't show up, here's the solution that worked for me:
I got it from http://forum.xda-developers.com/showpost.php?p=21746289&postcount=2 (thanks Chrono_Tata).
Based on what Chrono_Tata wrote, I decided to create a ".nomedia" file in my main personal directory, where contains pictures, musics, personal files and so on.
(For those not familiar with Linux, the ". (dot)" in the beginning of the filename is very important! It means that it's a hidden file. You can create it through ES File Explorer)
For testing purposes, I copied some musics / pics to directories out of that my structure.
Then, stopped and cleaned data for: Gallery, Google Music and Media . Afterwards, restarted phone.
Bingo. It did work, and I could see the pics/musics outside my main directory (although it takes a while to re-scan everything, so wait! Gallery and Music will show nothing until scan is complete).
Well, after I realized it did work, I continued in the following way:
1) Delete the previous ".nomedia" file that I created
2) Create a new one under some sub-directory.
3) Repeat process for re-scan
I did it until I found which directory had an issue (btw, my pictures directory).
I think it might be related to thumbs.db file created by Win, but I'm not sure. Anyway, I still have to check carefully my structure to find the issue.
Hope it helps.
Regards,
Adriano.
Nice one!
For some reason the same worked with me. I seemed to have some 0k files that were perhaps causing issues. I used your process to clear things out.
Thanks Adriano!
aidanbree said:
Nice one!
For some reason the same worked with me. I seemed to have some 0k files that were perhaps causing issues. I used your process to clear things out.
Thanks Adriano!
Click to expand...
Click to collapse
Basically resolved this by
1) Creating a new directory in /sdcard/DCIM and moved all photos from /sdcard/DCIM/Camera to this directory
2) Placed .nomedia files in almost every directory in /sdcard except the obvious ones (/sdcard/DCIM/Camera being one of them)
3) Copied a months worth of photos from /sdcard/DCIM/Camera_bkup to /sdcard/DCIM/Camera, rebooted the phone, checked the gallery to see if all the photos now appeared
4) Repeated until /sdcard/DCIM/Camera_bkup was empty... in the process I removed a bunch of older pictures that were legacy from a non-Android cellphone that I copied over from my first phone
This was after I fixed the media_rw/media_rw permissions that I found as when I used the GNex Toolkit to dump my SDCard and then tried to restore it, all the files had root/root user/group permission set.
There was also an issue with timestamps of some photos where they were actually placed in the future by a few days, which was annoying because as I slid back from a picture I had just taken to the gallery it would show me some other picture then the one I had just taken. This got resolved as the wrong timestamped photos entered the past.
I was on an MCR JB build... I hope I don't have to go through all these hoops when CM10 comes out.
efrant said:
I've always thought MTP was flaky. I use ADB to transfer any files back and forth.
Click to expand...
Click to collapse
It definitely is. I'll have files missing from the MTP listing, but when I go in and look on my phone, the files are clearly there. MTP is janky at best.
This has been driving me nuts, since when the I/O update came out I flashed and had the same issue, just reverted to AOKP from nandroid.
I have partially fixed the issue by going into Recovery and fixing permissions, now I can see and select ringtones and most my camera pictures. Still many files are not showing on gallery, but I guess its progress .
Edit: Forgot to mention that I tried 4.1.1 and still had the issue, I just reverted to a nandroid b/u of ICS.
i think this issue is caused because the storage is named "sdcard0" the normal should be "sdcard" i tried to change the storage name but "sdcard0" is reed only, so i can't change the name with root explorer maybe someone can try to rename it and see if this issue will be fixed.
any thing let us know because this issue is being annoying.
raidy said:
i think this issue is caused because the storage is named "sdcard0" the normal should be "sdcard" i tried to change the storage name but "sdcard0" is reed only, so i can't change the name with root explorer maybe someone can try to rename it and see if this issue will be fixed.
any thing let us know because this issue is being annoying.
Click to expand...
Click to collapse
Having the same issues... wasting the WHOLE day troubleshooting this issue w/o any luck so far... I think I will end up going back to ICS and be happy with it until a solution is apparent. So annoying...! Jelly Bean is sooo fast!
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!
SystemUI keeps crashing when it tries to restart, making my phone completely unusable. I'm not able to flash another ROM at the moment so what I'd like to try is deleting the app data for SystemUI (wiping cache and dalvik didn't work). I have Team Win Recovery so I'm able to access the filesystem to delete files.
Can anyone suggest which file(s) I should look for?
restore a backup
beekay201 said:
restore a backup
Click to expand...
Click to collapse
I want to keep my most recent files. I took some photos today and they didn't get a chance to instant upload. I can wait a few days until I get to a computer I can use ADB on to push a ROM.
Sounds like you don't need a working device.
a maguro wrote this.
Use adb to remove /data/data/com.android.systemui/ folder
Hey guys! Big news!
I've fixed the problem, well.. sort of.
I will edit the post If I had something else to test.
1. Uninstalled Android System Webview and installed the one that is present in the Play Store (I can't select it for Webview Implementation though)
2. Launched YouTube app and showed a green screen no matter what the quality is.
3. Tried Chrome and the video works well without any freezes.
Has anybody encountered the camera app not saving pictures? The camera app opens up and takes pictures fine but when you open the image from the gallery app, it's just a solid dark green color. I searched the OP3 threads but I have found nothing conclusive. Storage is also wonky since sometimes I can't access files I have placed in the internal storage (rom folder for flashing disappears but takes up space). I have encountered this problem in 6.0.1 to 7.1.1. I have tried adb format userdata and wiping storage and flashing the correct TWRP and firmware images. If any of you has encountered this problem and has solved it, please do comment and help me. Thanks!
vinax89 said:
Has anybody encountered the camera app not saving pictures? The camera app opens up and takes pictures fine but when you open the image from the gallery app, it's just a solid dark green color. I searched the OP3 threads but I have found nothing conclusive. Storage is also wonky since sometimes I can't access files I have placed in the internal storage (rom folder for flashing disappears but takes up space). I have encountered this problem in 6.0.1 to 7.1.1. I have tried adb format userdata and wiping storage and flashing the correct TWRP and firmware images. If any of you has encountered this problem and has solved it, please do comment and help me. Thanks!
Click to expand...
Click to collapse
seems to me like its a hardware fault here, its your nand storage which looks like its about to give up on you, better claim warranty while its still valid.
vinax89 said:
Has anybody encountered the camera app not saving pictures? The camera app opens up and takes pictures fine but when you open the image from the gallery app, it's just a solid dark green color. I searched the OP3 threads but I have found nothing conclusive. Storage is also wonky since sometimes I can't access files I have placed in the internal storage (rom folder for flashing disappears but takes up space). I have encountered this problem in 6.0.1 to 7.1.1. I have tried adb format userdata and wiping storage and flashing the correct TWRP and firmware images. If any of you has encountered this problem and has solved it, please do comment and help me. Thanks!
Click to expand...
Click to collapse
Did you make any edits to your buildprop?
Hw4ng3r said:
Did you make any edits to your buildprop?
Click to expand...
Click to collapse
Nope, buildprop is stock/unchanged. I have a guess that this is a storage permission problem.
vinax89 said:
Nope, buildprop is stock/unchanged. I have a guess that this is a storage permission problem.
Click to expand...
Click to collapse
i was having the same problem here. it hapened to me when i went to 7.0 on freedom os. it has nothing to do with the storage that guy was talking about.
i just reinstalled the os and wiped and it was gonne like that
It happened to me after disabling an app, unfortunately don't know exactly which one. I suggest factory reset.
I'm having the exact same issue.
I've re-flashed OOS 4.0.2 twice, re-formatting the system via stock recovery in between. tried with and without root, also removed data for the camera app.
Strangely it works just fine with an app like Open Camera (although the quality is miserable) - have you tried that?
edit: I also assume a permission issue but struggling to find out how that seems to work in Nougat...
Cheers
Stock build.prop
can anyone upload the stock build.prop file for oxygen os 4.0.2 one plus 3
shubhambankar96 said:
can anyone upload the stock build.prop file for oxygen os 4.0.2 one plus 3
Click to expand...
Click to collapse
Is this what you want? Delete ".txt" from the name of the attached file.
Try changing build.prop permissions to rw-r-r. That worked for me with a similar problem.
It only happens if u have edited Ur build prop or something did it. make sure the build prop is stock and dpi change is also issue (via build prop not from settings )