Database Info

Low Battery + Camera Flash Tweak?

I was wondering if anyone knew of such a thing (a download to enable camera flash even at low battery) or would be kind enough to provide me with one, I would be so grateful. I've tried searching around to no avail. Thanks in advance.
*Actually, or if anyone knows where in the settings I can change this at because I've went through everything I see and I can't find an option for it.

I need it too....

Last time i checked, this was in
HKEY_LOCAL_MACHINE\\Drivers\BuiltIn\Battery\
Change the 0 value to "FlashlightpowerUnavailable" : 1
Cheers

There is a better solution:
[APP] Camera w/o low batt. flashlight restrictions - xda-developers

Hi there djet,
i tried to transfer both the files to the windows folder but i am getting this message: "be certain that there is enough free storage memory, that the destination is not write protected and that the file is not currently in use". Have you personally tried the method already?
many thanks

cezzarmicu said:
Hi there djet,
i tried to transfer both the files to the windows folder but i am getting this message: "be certain that there is enough free storage memory, that the destination is not write protected and that the file is not currently in use". Have you personally tried the method already?
many thanks
Click to expand...
Click to collapse
All you need to do is to copy Camera.exe to \Windows folder. You are definitely doing it wrong. Try Resco's Explorer for file management.
Have you personally tried the method already?
Click to expand...
Click to collapse
Personally? The patch and the package are mine. Of course it works.

Thanks djet...worked this time (using resco's explorer).
i tried using the native file explorer yesterday which didn't work
EDIT++++
i tried the camera app and it didn't work. says that app may be right protected... i returned the original camera app and i got it to work. do i still have to do something on the replacement camera app before placing it to the windows folder?
thanks

cezzarmicu said:
Thanks djet...worked this time (using resco's explorer).
i tried using the native file explorer yesterday which didn't work
EDIT++++
i tried the camera app and it didn't work. says that app may be right protected... i returned the original camera app and i got it to work. do i still have to do something on the replacement camera app before placing it to the windows folder?
thanks
Click to expand...
Click to collapse
What ROM are you using and what exactly is the message?

I am using the old ROM (1.48.707.2) WWE. I'm from the Philippines btw.
I'm sorry I forgot the exact message but it did say something like either the phone having not enough memory space (but I still have 78MBfree space) or installing a right-protected (certificate) file?

cezzarmicu said:
I am using the old ROM (1.48.707.2) WWE. I'm from the Philippines btw.
I'm sorry I forgot the exact message but it did say something like either the phone having not enough memory space (but I still have 78MBfree space) or installing a right-protected (certificate) file?
Click to expand...
Click to collapse
The patch is intended for 1.66+ Camera. Certificate checks must be disabled as the patched exe isn't properly signed.

i see. now i am going to have to be forced to upgrade my rom thanks

SD Card Speed Fix!! IMPLEMENT INTO CM7 PLEASE

http://forum.xda-developers.com/showthread.php?t=921530
THIS WORKS on the Aria. BIG DIFFERENCE!

akira02rex said:
http://forum.xda-developers.com/showthread.php?t=921530
THIS WORKS on the Aria. BIG DIFFERENCE!
Click to expand...
Click to collapse
I just tried this, and it appears that the tweak to the file makes a difference in speed tests.
I'm trying to get my hands around how to actually test it in real-world situations.
So for CM7 - this would definitely be a nice addition to this already excellent ROM...

akira02rex said:
http://forum.xda-developers.com/showthread.php?t=921530
THIS WORKS on the Aria. BIG DIFFERENCE!
Click to expand...
Click to collapse
This should have been posted in the CM7 thread. Why start a new one?
Here is a flashable zip that will add the fix to an init.d script and will survive reboot. It checks to see if the value is 4, and if so changes it to 128. You have to apply it after each new rom flash.

This can be tested with adb pull.
Pull it with the setting at 4. pull pack the cm rom to a local folder. you will get speed stats. after the first pull, set the param to 128. pull again.
syntax from adb: adb shell echo 128 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
from terminal - just skip the adb.
one note, I tried this on my Aria - it broke adb transfers. Then I tried it again and it worked.
Before I add this to CM, I want to make sure it's reliable.

The gallery loads even faster.
Sent from my Liberty using XDA App

attn1 said:
This can be tested with adb pull.
Pull it with the setting at 4. pull pack the cm rom to a local folder. you will get speed stats. after the first pull, set the param to 128. pull again.
syntax from adb: adb shell echo 128 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
from terminal - just skip the adb.
one note, I tried this on my Aria - it broke adb transfers. Then I tried it again and it worked.
Before I add this to CM, I want to make sure it's reliable.
Click to expand...
Click to collapse
Im at 128 with the update.zip I posted above, and I can adb pull and push to my hearts content. I am on nightly 18 BTW.

bkmo said:
Im at 128 with the update.zip I posted above, and I can adb pull and push to my hearts content. I am on nightly 18 BTW.
Click to expand...
Click to collapse
the correct way is to add it to init.rc - that's when I had a failure. but the failure is not consistent.

bkmo said:
This should have been posted in the CM7 thread. Why start a new one?
Here is a flashable zip that will add the fix to an init.d script and will survive reboot. It checks to see if the value is 4, and if so changes it to 128. You have to apply it after each new rom flash.
Click to expand...
Click to collapse
On cm, if you want to preserve an init script, you can do anyone of the following:
Save it in /sd-ext/userinit.d/
Save it as /sd-ext/userinit.sh
Save it as /data/local/userinit.sh
Use cm's backuptool, it runs on rom installation. Just save its path (without the leading "/system/") into /system/etc/custom_backup_list.txt
Code:
etc/init.d/04sdcardspeedfix

Apparent improvement
Just flashed the above posted zip on CM7 Nightly 18 - seems to be a dramatic improvement, at least in stats, on my cheapie class 6 card:
before update: Write 5 / Read 6
after update: Write 4 / Read 12
I did not conduct this test at all scientifically - just ran one speed test before and one after the update, so take it for what it's worth I guess...just figured I'd share.

attn1 said:
the correct way is to add it to init.rc - that's when I had a failure. but the failure is not consistent.
Click to expand...
Click to collapse
I have it running as an init.d script and cannot make it fail. I do see this tweak posted in a lot of different forums.

Looks like this thread is now dead. This has been commited to cm7.

bkmo said:
Looks like this thread is now dead. This has been commited to cm7.
Click to expand...
Click to collapse
I dont quite understand. This last change set it back to 4? We still gotta manually change it? Or that's just the MIN value?

Darius_bd said:
I dont quite understand. This last change set it back to 4? We still gotta manually change it? Or that's just the MIN value?
Click to expand...
Click to collapse
The last commit is making a correction for the nand flash after the sd commit changed all memory readahead to128.

.
Gotcha, thanks for the clear up

bkmo said:
The last commit is making a correction for the nand flash after the sd commit changed all memory readahead to128.
Click to expand...
Click to collapse
Correct! The changes will be built in tonight's nightly.

Have anyone who can build boot.img already flashed the new kernel files? Is Wi-Fi broken? Or just me?
Sent from my Liberty using XDA App
EDIT: sorry... my bad, it's my typo of modules folder

[Guide] SQLite3: Dramatically Improve Entire Phone

So I've used the sqlite vacuum/re-index feature of V6 SuperCharger blindly without knowing what it does getting a placebo effect sort of thing, and I started doing some research on it and realized that this feature has started getting stripped out of a lot of stock roms and what not on android devices and that basically it makes it wayyyy easier for the system to index and sort out system/app files a lot of it was over the top for me but I figured there could be no negative effects to this at all.
So long story short I downloaded SQLite Installer from the market
Restarted and everything on my phone has been quick and painless it's been up for 6 hours now since the restart and have yet to have any lag/problems.
here's my set up:
Tweaked 2.0
0504 PBJ Kernel
OC'd to 1.2ghz (SIO i/o and Interactive governor)
don't know if it is placebo affect once again and I'd love to get some more veteran knowledge on this but I LOVE MY PHONE NOW
As I am a new member here I cannot post links but go to my thread at rootzwiki[dot]com/topic/25072-sqlite3-phone-is-snappier-than-ever/ and read the instructions there and download the easily flashable .zip file with the included detailing script.
happy flashing
p2kmafia

I just flashed so ill report if results are the same for me
Sent from my SCH-I510 using XDA

good lookin. there were positive results in my rootzwiki thread.

RFS or EXT4?
and is this the app: https://play.google.com/store/apps/details?id=ptSoft.util.sqlite3forroot

It would be fairly easy to run before and after database benchmarks in an app such as AnTuTu Benchmark. That would show if there are any real gains to be had.
Looking at the script, it essentially just re-writes all of the databases on the phone (via a VACUUM/REINDEX combo). Logic would state that if you have badly fragmented databases, which would manifest as things like degredation of performance over time, then this should make your phone a bit snappier.
[edit: I ran before and after tests (average of 3 tests). There was no appreciable difference between the tests. Now, the test results may not reflect real world results for two reasons: 1. I have no idea how the database I/O test in AnTuTu actually tests (what database, etc) and 2. I received errors when the script was attempting to vacuum databases ("error: unable to open file"), though the re-indexing worked fine.
End result? The test essentially means nothing and all we can go off of is anecdotal evidence. However, whether it's a placebo effect or not, this process simply can't harmfully impact your phone. As such, results should be anything from no change in response to some response increase.
Yeah, I know. A whole lot of typing that essentially says nothing. Sorry!]

jco23 said:
RFS or EXT4?
and is this the app: play.google[DOT]com/store/apps/details?id=ptSoft.util.sqlite3forroot
Click to expand...
Click to collapse
yes that's the app but check out my rootzwiki thread the flashable zip file adds the detailing script to your sd card that you'll need if you feel your device slowing down.
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip

p2kmafia said:
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip
Click to expand...
Click to collapse
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.

I don't know what to tell you. I just re-ran the detailing script and I don't receive those errors, but if you know it is installed correctly/is vacuuming it shouldn't be a problem. I wish I knew more about this software to help out. I just discovered it helps a lot haha.

Cilraaz said:
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.
Click to expand...
Click to collapse
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium

Endless2232 said:
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Script manager as root. Command line as root. The entire script and individual manual vacuums. Same result on all. Maybe I'll boot into CWM and run a fix permissions to see if that does anything.

Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium

Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?

p2kmafia said:
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?
Click to expand...
Click to collapse
No, you're fine.

So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium

Crap7126 said:
So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.

p2kmafia said:
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.
Click to expand...
Click to collapse
Failed for me.
Sent from my SCH-I510 using xda premium

deafptl4ever said:
Failed for me.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
what failed for you? i'd love to help out but need a little more information

Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Click to expand...
Click to collapse
If this was in regard to my issue, it's of no consequence. The sqlite3 executable was running fine, as evidenced by the fact that there were no errors in executing sqlite3 (the REINDEX command ran without problem). The permission issue would be with the database files themselves, though root should have no permission issues on r/w partitions like data and dbdata, or wherever sqlite3 is trying to write the temporary database during the VACUUM process. The VACUUM process actually reads data out of the database file, stores it in a temporary file, and then overwrites the original file with data from the temporary file. This eliminates "blank" data and fragmentation within the database files, which is why you see a slight performance increase and smaller database footprint.
Does anyone know where that temporary db file is stored by sqlite3?

Cilraaz said:
Does anyone know where that temporary db file is stored by sqlite3?
Click to expand...
Click to collapse
Unfortunately my expertise stops at how it works/why it works I just found out that it helps my phone and that's it

This def made my phone much snappier. My only question is, when i run the script i get a constant error, "error mountind database". Not really sure whato do (if anything) since it has made the phone quicker regardless.
Sent from my SCH-I510 using XDA

[Q] Keyboard Dropping/Missing Keystrokes?

Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.

ged92781 said:
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
Click to expand...
Click to collapse
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom

ultraprimeomega said:
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
Click to expand...
Click to collapse
I wonder what the issue is that's causing it to show up on custom ROMs. Though, I've had it on the stock ROMs as well.

Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622

yogi2010 said:
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
Click to expand...
Click to collapse
Thank you!!!!!!!! I went ahead and dug into that thread. I do have that kernel already on my phone. I looked at the thread linked in that thread that gives a patch to adjust the timer delay and column delay in the kernel. HOWEVER, I'm not knowledgeable enough to apply that patch to my phone as it's given. Elsewhere in that thread, someone gave the commands to edit the settings manually through a terminal which I did through Android Commander on my PC and it worked wonders! Being the suspicious type, I guessed that the settings might not keep after a reboot. Unfortunately, that is the case and I had to reapply the settings after my phone finished restarting. So, I'll have to play with this a bit more to get it to keep, but thank you for showing me this!

You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.

yogi2010 said:
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
Click to expand...
Click to collapse
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?

ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
+1
I've noticed this problem and thought it was just me :$

I've had this happen as well as my screen thinking I was pressing it in one location when I wasn't even touching the phone. :s Had me at my wits end.
Sent from my SGH-T839 using xda premium

To those interested in the commands I used to fix the keyboard, see below. If you reboot your phone, these settings will go away and you will need to input these commands again. For a permanent fix, someone will need to add them to a kernel that can be flashed. To use these commands, your phone must be rooted. I've successfully used Android Commander to enter these commands from my PC while my phone is connected via USB.
The current timer delay may be read with:
cat /sys/devices/platform/s3c-keypad/timer_delay
The default is 5 if I remember correctly.
A new timer delay may be set with:
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
The default 300 µs column delay value may be read with:
cat /sys/devices/platform/s3c-keypad/column_delay
A new delay may be set with:
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
In either command, you may experiment with different values by changing the 1 or the 30 in either command to what you want. I believe the lowest is 1 and the max is 256 for the timer delay. If you damage your phone running these commands, that's on you. I'm just telling you what I did and feel worked for me. YMMV. Also, if you don't want to connect your rooted phone to your PC and want to use Terminal Emulator from the Play store, that will work too. You need to enter 'su' prior to running the above commands and grant the terminal super user permissions for the commands to take.

ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.

RicAndroid said:
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
Click to expand...
Click to collapse
Thank you!

ged92781 said:
Thank you!
Click to expand...
Click to collapse
You are very welcome! All done, BTW. Posting my updates now.

Permanent Fix(Manual way)
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)

SammaelAkuma said:
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
Click to expand...
Click to collapse
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?

RicAndroid said:
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
Click to expand...
Click to collapse
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.

SammaelAkuma said:
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
Click to expand...
Click to collapse
I'm using your commands, dude. I'm very into details....so thanks!

RicAndroid said:
I'm using your commands, dude. I'm very into details....so thanks!
Click to expand...
Click to collapse
Lol. No problem. And good luck with the custom rom cooking.

Internal Memory running low - MacLaw 4.4

I have installed MaclawStudio Kit Kat ROM (version of March 17th, 2014) in my Galaxy S2 Lite (a.k.a Galaxy S Advance).
Everything was running fine, but now with some months of usage I was fighting with low internal memory available, even though I have only a few apps installed.
I used Storage Analyser app to check where the pain point was an found out a big number of folders with the naming mmdsp-SIA_... in the data folder.
They contained the following files:
mem_sdram_data.data
mem_sdram_code.data
mem_esram_code.data
mem_tcm.data
metadata.txt
I could not find much information about this, but as the name folder contained a timestamp I imagine this is some kind of Short Dump memory information.
I deleted this folders, made free more or less 400 MB and so far the phone is ok.

Thats what happen when you use ****law cm :laugh::laugh::laugh:
PS: sorry for OT

Same problem here
Hi,
I'm having the same exact problem with my S Advance but i have no custom ROM, though i have routed my phone to uninstall operator apps so that i could make it run lighter.
I have more than a hundred of them and don't know if i can delete them without problems.
Do you still have those kind of directories ?
Have you found what they are for ?
And still no problems deleting them ?
Thanks

Force said:
Thats what happen when you use ****law cm :laugh::laugh::laugh:
PS: sorry for OT
Click to expand...
Click to collapse
I'm open to suggestions.

dellagustin said:
I'm open to suggestions.
Click to expand...
Click to collapse
Sorry for that rude post . Try SD Maid, it can free some space.

PauloSilva.1969 said:
Do you still have those kind of directories ?
Have you found what they are for ?
And still no problems deleting them ?
Click to expand...
Click to collapse
Hello, sorry for the late response.
The folders appear again now and then. When I'm low on space I always check the data folder and if they are there I'll delete them.
No harm so far.