Develop Bugs

[Q] Couldn't capture screenshot. Storage may be in use.

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

[Q] Paranoid Android preference storage problem

Hello guys,
I've just flashed the Paranoid Android ROM by WOH (http://forum.xda-developers.com/showthread.php?t=1912187&page=111) and I really like it.
However, I'm having some kind of issue with the PA engine settings.
The problem goes like this:
1. When I set the global UI settings, I'm asked to reboot, but the settings are back to defaults after the reboot.
2. When I edit the preferences for a particular app, I'm only able to make it work by setting and applying the needed values followed by using the launch button, which finally makes the changes effective. These changes are, however, also reset after rebooting the phone.
I did some searching and found this hint (http://www.paranoid-rom.com/forum/guides-references/256-hint-pa-prefs-does-not-save-changes) which seems to deal with this problem, but haven't had any luck with it. In the terminal, when trying to run the commands, I get an error saying my file system is mounted read only. So I tried modifying the file perimissions in the ES file manager (which also didn't work on some occasions, but sometimes it did), then running the terminal commands successfully, but without any effect on the PA preferences bahaviour after rebooting.
I ended up editing those files manually and removing the backup file (which, I thought, was overwriting the preferences file, reverting the settings to defaults). The ES file manager also behaved very oddly when trying to manipulate those files, once I was not allowed to delete those files, than they disappeared on their own, same goes for renaming.
Finally, I think, the problem is being caused by the properties file being overwritten with the defaults on every boot. So far I've been unable to determine the cause of this behaviour, so I hope perhaps some of you have come across this problem and know the solution. Thanks in advance for that.

NFS: MW issue with data when switching Roms

I have been trying for the life of me to figure out the way, or if it's possible to keep progress from the game when updating or switching roms. As of now, Titanium Backup doesn't work, or does saving the data/game files and transferring them. Once you try to do either, it says that your unauthorized. Then you have to start fresh and re-download the 2 million gig game and files. I contacted firemonkey and they said rooted devices aren't supported. Don't remember seeing that on play, and it should be. Regardless, I paid for the game.....why am I not authorized to continue progress, and forced to start over from scratch when the newest version of pie is out? There has to be a way to keep progress....?:fingers-crossed:

I'm not sure how much this will help you but maybe it will be what you are looking for:
I recently had a problem where NFS:WM would crash on startup, and apparently the only thing to do (according to firemonkey) is just clear data and lose all progress. Having almost completed everything, I wasn't having any of that.
I'm not rooted but do have my bootloader unlocked so that I can fastboot TWRP to do backups, which also happens to give me root access when booted into TWRP. I made a backup and looked through it to try and and a problem. No luck there, but I did figure out that the game progress is stored in a single file. No config data or anything as far as I can tell, just the progress. So I cleared the data, ran the game through the first level, then copied that old progress file over the new one and I had it back up and going with all progress intact. It's basically a clean install, and since all of the config data is still part of the new install, it didn't cause me any problems.
I did download all of the game data again ultimately, however. But an earlier test of saving "/sdcard/Android/data/com.ea.games.nfs13_na/" and putting it back to avoid the download did work, although it could have been a fluke.
Anyway the file in question is "/data/data/com.ea.games.nfs13_na/files/var/nfstr_save.sb". Just save that one file, install the game from scratch otherwise, run it the first time, then copy that saved progress file over the new one. Assuming that there isn't anything else going on that I didn't find, that should solve your problem.

mtrs said:
I'm not sure how much this will help you but maybe it will be what you are looking for:
I recently had a problem where NFS:WM would crash on startup, and apparently the only thing to do (according to firemonkey) is just clear data and lose all progress. Having almost completed everything, I wasn't having any of that.
I'm not rooted but do have my bootloader unlocked so that I can fastboot TWRP to do backups, which also happens to give me root access when booted into TWRP. I made a backup and looked through it to try and and a problem. No luck there, but I did figure out that the game progress is stored in a single file. No config data or anything as far as I can tell, just the progress. So I cleared the data, ran the game through the first level, then copied that old progress file over the new one and I had it back up and going with all progress intact. It's basically a clean install, and since all of the config data is still part of the new install, it didn't cause me any problems.
I did download all of the game data again ultimately, however. But an earlier test of saving "/sdcard/Android/data/com.ea.games.nfs13_na/" and putting it back to avoid the download did work, although it could have been a fluke.
Anyway the file in question is "/data/data/com.ea.games.nfs13_na/files/var/nfstr_save.sb". Just save that one file, install the game from scratch otherwise, run it the first time, then copy that saved progress file over the new one. Assuming that there isn't anything else going on that I didn't find, that should solve your problem.
Click to expand...
Click to collapse
Awesome. I'll give this a try. :good:

I use MyBackup Pro. I backed up the data and apk from my Nexus and transfered it to me Evo LTE. I restored the apk and data. It does prompt me to reinstall the other game data, which is fine with me. I found if I tried to copy it from one device to the other it would cause the game to crash randomly
Sent from my Nexus 7 using Tapatalk 2

most likely because of the device id (which is the id you see when you type "adb devices" in a command prompt). it's supposed to stay constant in the lifetime of the device (except for factory reset)

Mobile Network wont work after root

Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!

mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?

aukhan said:
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
Click to expand...
Click to collapse
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway

mvattoy said:
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
Click to expand...
Click to collapse
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup

aukhan said:
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
Click to expand...
Click to collapse
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.

mvattoy said:
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
Click to expand...
Click to collapse
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.

aukhan said:
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
Click to expand...
Click to collapse
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?

mvattoy said:
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
Click to expand...
Click to collapse
first recommend you to flash stock and try see if you've got you IMIE .

mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
1st flash a stock rom and see whether u get imei and baseband back or not.. if it didnt get recovered then service centers can only help you as u didnt make a backup of efs..

There is a slim chance its not his efs,
I did pretty much the same as he to get root thru the toolkit, and had no network, I found I had no APN configured
Perhaps check this.
Settings... more settings .. mobile networks... acess point names.
Make sure you have something here.
if not you will need to search for the settings for whoever your provider is.
good luck
A|c

MTP broken in OB3?

Cheers!
I noticed a rather strange thing when trying to copy files to my 5T on my Mac with Android File Transfer. I was unable to create folders, and trying to write data resulted in errors (like again "can't create folder"). Some files present on the phone and visible in e.g. TotalCommander (or any other file manager) would not show up on my Mac. I then switched to my Win10 PC just to find out that creating folders was also giving me grief. /data lists most of the files, but some are missing. Also, there are a lot of devices (like HDDs) present (icon-wise). I thought the file structure might be knackered or there might be something going on with an app (I am rooted and use Magisk), so booted to TWRP to restore boot and system to find out if this would happen with a plain install as well. What can I say... TWRP also comes with MTP and this is working correctly. Booting into a clean OB3 again produces errors. This leads me to the conclusion that either something "broke" when upgrading e.g. OB2 to OB3, or OB3 (at least) is knackered when it comes to MTP.
Does anyone have similar/the same issues?