Anyone know what creates this directory? It seems to be populated mainly with system stuff.
[email protected]_BLADE_A110:/ # ls -l /data/media/0/SatDigger
Code:
drwxrwxr-x media_rw media_rw 2017-04-22 05:46 android
drwxrwxr-x media_rw media_rw 2018-01-03 00:20 au.com.amaysim.android
drwxrwxr-x media_rw media_rw 2018-01-03 00:21 au.com.weatherzone.android.weatherzonefreeapp
drwxrwxr-x media_rw media_rw 2017-04-22 05:47 com.android.externalstorage
drwxrwxr-x media_rw media_rw 2017-04-22 05:47 com.android.inputdevices
drwxrwxr-x media_rw media_rw 2017-04-22 05:48 com.android.location.fused
drwxrwxr-x media_rw media_rw 2017-04-22 05:48 com.android.managedprovisioning
drwxrwxr-x media_rw media_rw 2017-04-22 05:48 com.android.providers.media
drwxrwxr-x media_rw media_rw 2017-04-22 05:48 com.android.providers.settings
drwxrwxr-x media_rw media_rw 2017-04-22 05:49 com.android.settings
drwxrwxr-x media_rw media_rw 2017-04-22 05:49 com.android.sharedstoragebackup
drwxrwxr-x media_rw media_rw 2017-04-22 05:52 com.android.shell
drwxrwxr-x media_rw media_rw 2017-04-22 05:41 com.android.systemui
drwxrwxr-x media_rw media_rw 2017-04-22 05:53 com.buak.Link2SD
drwxrwxr-x media_rw media_rw 2017-04-22 05:53 com.dan
drwxrwxr-x media_rw media_rw 2017-04-22 05:53 com.estrongs.android.pop.pro
drwxrwxr-x media_rw media_rw 2017-04-22 05:55 com.mediatek
drwxrwxr-x media_rw media_rw 2017-04-22 05:55 com.mediatek.apst.target
drwxrwxr-x media_rw media_rw 2017-04-22 05:55 com.mediatek.atci.service
drwxrwxr-x media_rw media_rw 2017-04-22 05:54 com.mediatek.batterywarning
drwxrwxr-x media_rw media_rw 2017-04-22 05:55 com.mediatek.dataprotection
drwxrwxr-x media_rw media_rw 2017-04-22 05:55 com.mediatek.engineermode
drwxrwxr-x media_rw media_rw 2017-04-22 05:56 com.mediatek.filemanager
drwxrwxr-x media_rw media_rw 2017-04-22 05:56 com.mediatek.lbs.em2.ui
drwxrwxr-x media_rw media_rw 2017-04-22 05:56 com.mediatek.omacp
drwxrwxr-x media_rw media_rw 2017-04-22 05:56 com.mediatek.thermalmanager
drwxrwxr-x media_rw media_rw 2017-11-08 05:35 com.modernappdev.btfiletf
drwxrwxr-x media_rw media_rw 2017-04-22 05:57 com.zte.engineer
drwxrwxr-x media_rw media_rw 2017-04-22 05:57 com.zte.zdmdaemon
drwxrwxr-x media_rw media_rw 2017-04-22 05:58 de.mehrmann.sdbooster
[email protected]_BLADE_A110:/ # du -h /data/media/0/SatDigger
Code:
1.7M /data/media/0/SatDigger/com.android.systemui
6.7M /data/media/0/SatDigger/android
20K /data/media/0/SatDigger/com.android.externalstorage
88K /data/media/0/SatDigger/com.android.inputdevices
20K /data/media/0/SatDigger/com.android.location.fused
188K /data/media/0/SatDigger/com.android.managedprovisioning
80K /data/media/0/SatDigger/com.android.providers.media
108K /data/media/0/SatDigger/com.android.providers.settings
12K /data/media/0/SatDigger/com.android.sharedstoragebackup
2.8M /data/media/0/SatDigger/com.android.settings
36K /data/media/0/SatDigger/com.android.shell
8.5M /data/media/0/SatDigger/com.buak.Link2SD
28K /data/media/0/SatDigger/com.dan
15M /data/media/0/SatDigger/com.estrongs.android.pop.pro
40K /data/media/0/SatDigger/com.mediatek.batterywarning
960K /data/media/0/SatDigger/com.mediatek
12K /data/media/0/SatDigger/com.mediatek.atci.service
28K /data/media/0/SatDigger/com.mediatek.apst.target
192K /data/media/0/SatDigger/com.mediatek.dataprotection
816K /data/media/0/SatDigger/com.mediatek.engineermode
232K /data/media/0/SatDigger/com.mediatek.filemanager
112K /data/media/0/SatDigger/com.mediatek.lbs.em2.ui
56K /data/media/0/SatDigger/com.mediatek.omacp
32K /data/media/0/SatDigger/com.mediatek.thermalmanager
1.1M /data/media/0/SatDigger/com.zte.engineer
28K /data/media/0/SatDigger/com.zte.zdmdaemon
1.5M /data/media/0/SatDigger/de.mehrmann.sdbooster
33M /data/media/0/SatDigger/com.modernappdev.btfiletf
14M /data/media/0/SatDigger/au.com.amaysim.android
25M /data/media/0/SatDigger/au.com.weatherzone.android.weatherzonefreeapp
113M /data/media/0/SatDigger
UPDATE: 12/05/2019 (prompted by private message)
I never did discover what this was for or where it came from. IIRC I zipped the folder and kept it for a while but eventually just deleted it without any consequence *shrugs*
Thanks to @Pantoflat this has been solved!
Pantoflat said:
i cant write comment or answer on that thread , so i PM u again .
i just discovered its from apk analizer app .
Click to expand...
Click to collapse
The app referred to is Apk Analyzer by Dinostudio8891:
Code:
C:\Users\xdarthanonx\Downloads> [URL="https://www.7-zip.org/"][B]7z[/B][/URL] x -otemp dinostudio.android.apkanalyse.apk
7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21
Scanning the drive for archives:
1 file, 2903319 bytes (2836 KiB)
Extracting archive: dinostudio.android.apkanalyse.apk
--
Path = dinostudio.android.apkanalyse.apk
Type = zip
Physical Size = 2903319
Everything is Ok
Files: 608
Size: 6010897
Compressed: 2903319
C:\Users\xdarthanonx\Downloads> [URL="https://docs.microsoft.com/en-us/sysinternals/downloads/strings"][B]strings[/B][/URL] -o -s temp | [B]find[/B] /i "satdigger"
[highlight]C:\Users\xdarthanonx\Downloads\temp\classes.dex: 3370258:/SatDigger/[/highlight]
Satdigger
Related
Hello,
while backing up an restoring I think i killed the permissions of my Galaxy Xcover 2.
Now my Mobile-Service (Internet, Call, SMS) isn´t working.
Why I think this:
I was in FactoryMode and after using following commands I could exit it:
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
So i want now to fix all Permissions of the /efs and /modemefs Folders and the Files.
Here´s what ls -l says about my /efs Folder:
Code:
[email protected]:/ $ ls -l /efs
drwxrwxr-x radio system 2014-08-14 16:53 FactoryApp
-rw------- radio radio 2 2014-08-14 15:25 GUARDFIL
drwx------ radio radio 2014-08-14 15:25 RFHAL
drwx------ u0_a70 u0_a70 2014-08-14 15:24 RFHAL.DEF
drwxrwxr-x radio system 2014-08-14 15:24 bluetooth
drwxrwxr-x radio system 2014-08-14 15:24 imei
-rw------- u0_a70 u0_a70 0 2014-08-13 23:01 pre_recovery.log
drwxrwxr-x radio system 2014-08-14 15:24 wifi
Here the /modemfs
Code:
[email protected]:/ $ su
[email protected]:/ # ls -l /modemfs
drwxr-xr-x radio radio 2014-08-14 15:27 CONF
-rw------- u0_a70 u0_a70 0 2014-08-13 23:21 GUARDFIL
drwxr-xr-x radio radio 1970-01-01 01:00 PERM
drwx------ u0_a70 u0_a70 2014-08-14 15:09 RFHAL
-rw------- u0_a70 u0_a70 2 2014-08-13 23:21 rfhal_copied
-rw-rw-rw- radio radio 184 2014-08-13 23:22 trace_auto.conf
Thanks
..
Hi,
For some reason none of my apps on my phone work because they can't write to /sdcard:
Code:
[email protected]:/ # cd /sdcard/
[email protected]:/sdcard # mkdir test
mkdir failed for test, Permission denied
Code:
[email protected]:/ # ls -l sdcard
lrwxrwxrwx root root 2015-01-02 17:53 sdcard -> /storage/sdcard0
/sdcard seems to be a symlink to /storage/sdcard0, which is not writable. However, when I go to /mnt/media_rw/sdcard0 I can write to the card:
Code:
[email protected]:/sdcard # cd /mnt/media_rw/sdcard0/
[email protected]:/mnt/media_rw/sdcard0 # mkdir test
[email protected]:/mnt/media_rw/sdcard0 #
Here are the permissions
Code:
[email protected]:/storage # ls -l
drwxrwx--x root sdcard_r 2015-01-02 21:32 sdcard0
drwxrwx--x root sdcard_r 2015-01-02 16:55 sdcard1
drwxrwx--- root root 2015-01-02 17:53 usbdisk0
Code:
root[email protected]:/mnt/media_rw # ls -l
drwxr-xr-x root root 2015-01-02 21:32 sdcard0
drwxr-xr-x root root 2015-01-02 16:55 sdcard1
drwx------ media_rw media_rw 2015-01-02 17:53 usbdisk0
[email protected]:/mnt/media_rw #
Is it normal that /storage/sdcard0 is not writable ?
Is there a way to maybe recreate the symlink to /mnt/media_rw/sdcard0 ?
Or are there any other ways I should solve this ?
Hi,
I had to wipe /data and am now struggling with restoring the data of the Threema app.
Similar to the other apps, I installed it, started it once and copied back the directories databases, files and shared_prefs under /data/data/ch.threema.app/. After adapting ownership using chown, it now looks like this (directories "." and ".." omitted):
Code:
[email protected]:/data/data/ch.threema.app # ls -la
drwxrwx--x 2 u0_a87 u0_a87 4096 2016-01-11 18:44 cache
drwxrwx--x 2 u0_a87 u0_a87 4096 2016-01-12 19:11 code_cache
drwx------ 2 u0_a87 u0_a87 4096 2016-01-11 18:44 databases
drwxrwx--x 3 u0_a87 u0_a87 4096 2016-01-12 18:02 files
lrwxrwxrwx 1 root root 34 2016-01-12 19:32 lib -> /data/app/ch.threema.app-1/lib/arm
drwxrwx--x 2 u0_a87 u0_a87 4096 2016-01-12 19:11 shared_prefs
subdirectories:
Code:
[email protected]:/data/data/ch.threema.app # ls -la databases/
-rw------- 1 u0_a87 u0_a87 943104 2016-01-11 18:45 threema.db
[email protected]:/data/data/ch.threema.app # ls -la files/
-rw------- 1 u0_a87 u0_a87 64 2016-01-12 18:02 .crs-private_key
drwx------ 2 u0_a87 u0_a87 4096 2016-01-11 18:44 icu
-rw------- 1 u0_a87 u0_a87 45 2016-01-11 18:48 key.dat
-rw------- 1 u0_a87 u0_a87 32 2016-01-12 19:18 msgqueue.ser
[email protected]:/data/data/ch.threema.app # ls -la shared_prefs/
-rw-rw---- 1 u0_a87 u0_a87 130 2016-01-11 18:44 _has_set_default_values.xml
-rw-rw---- 1 u0_a87 u0_a87 2681 2016-01-12 19:11 ch.threema.app_preferences.xml
When I start Threema, I am asked for my passphrase (which is accepted). As next step, I'm asked to create a new ID or restore from backup.
How can I restore my Threema account (optionally including the messages from a /data backup).
I am running CyanogenMod 13.0
Thanks in advance!
With all data copied back and after starting threema and entering my passphrase, I started the restore process from my ID backup that I created long time ago. This worked and I then also had access to all previous messages.
On a clean CM14.1 install - no issue.
On a clean CM14.1 install with OpenGApps pico - no issue.
On a clean CM14.1 install with OpenGApps Super with gapps-config - problem appears.
The apps are creating files on /data/media/0 aka /storage/emulated/0 with media_rw:media:rw:600.
Current (manually fixed) permissions:
Code:
oneplus2:/data/media/0 # ls -lah
total 86K
drwxrwx--- 19 media_rw media_rw 4.0K 2016-11-29 03:48 .
drwxrwx--- 4 media_rw media_rw 4.0K 1970-01-27 08:50 ..
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Alarms
drwxrwxr-x 4 media_rw media_rw 4.0K 2016-11-29 01:28 Android
drwxrwxr-x 4 media_rw media_rw 4.0K 2016-11-28 23:15 DCIM
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Downloads
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Movies
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Music
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Notifications
drwxrwxr-x 2 media_rw media_rw 4.0K 1970-01-27 11:17 Open-GApps
drwxrwxr-x 3 media_rw media_rw 4.0K 2016-11-29 02:42 Pictures
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Podcasts
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Ringtones
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-28 23:44 SMSBackupRestore
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 TWRP
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Telegram
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 WhatsApp
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 cmupdater
oneplus2:/data/media/0 #
Creating a folder and a file using an app called FX:
Code:
oneplus2:/data/media/0 # ls -lah
total 96K
drwxrwx--- 20 media_rw media_rw 4.0K 2016-11-29 03:49 .
drwxrwx--- 4 media_rw media_rw 4.0K 1970-01-27 08:50 ..
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Alarms
drwxrwxr-x 4 media_rw media_rw 4.0K 2016-11-29 01:28 Android
drwx------ 2 media_rw media_rw 4.0K 2016-11-29 03:16 CameraZOOM
drwxrwxr-x 4 media_rw media_rw 4.0K 2016-11-28 23:15 DCIM
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Downloads
-rw------- 1 media_rw media_rw 3 2016-11-29 03:49 File from FX.txt
drwx------ 2 media_rw media_rw 4.0K 2016-11-29 03:49 Folder from FX
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Movies
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Music
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Notifications
drwxrwxr-x 2 media_rw media_rw 4.0K 1970-01-27 11:17 Open-GApps
drwxrwxr-x 3 media_rw media_rw 4.0K 2016-11-29 02:42 Pictures
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Podcasts
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Ringtones
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-28 23:44 SMSBackupRestore
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 TWRP
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 Telegram
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 WhatsApp
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 02:42 cmupdater
Taking a picture...
Code:
oneplus2:/data/media/0 # ls -lah DCIM/Camera
total 778K
drwxrwxr-x 2 media_rw media_rw 4.0K 2016-11-29 03:50 .
drwxrwxr-x 4 media_rw media_rw 4.0K 2016-11-28 23:15 ..
-rw------- 1 media_rw media_rw 1.4M 2016-11-29 03:50 IMG_20161129_035027.jpg
oneplus2:/data/media/0 #
I tested on another device and this never happened. Have not been able to properly share documents for the past 3 days and I've never wiped and installed ROMs so many times ever before.
Should I clean flash to official OnePlus 2 OOS? If someone would be so kind enough to point me the way in troubleshooting this, it would be much appreciated.
A BLU Vivo AIR phone 16GB, (no extra sd card), becomes stuck every few days/weeks.. Checking the /data/.. folder noticed this cache directory filling up all the time:
Code:
[email protected]:/data/data/com.android.vending/cache # ls -l
-rw------- u0_a18 u0_a18 55273 2017-01-05 16:37 1468357373244.tmp
-rw------- u0_a18 u0_a18 60737 2017-01-05 17:09 1470286953684.tmp
-rw------- u0_a18 u0_a18 60737 2017-02-16 16:38 1478228129219.tmp
-r-------- u0_a18 u0_a18 35612 2017-02-16 16:39 com.android.opengl.shader
s_cache
-rw------- u0_a18 u0_a18 35771046 2017-01-10 12:38 gfbfv1-1407321045old
-rw------- u0_a18 u0_a18 25312644 2017-02-02 07:43 gfbfv1-1938407551old
-rw------- u0_a18 u0_a18 35720303 2017-02-10 08:20 gfbfv1-54134236old
-rw------- u0_a18 u0_a18 30249810 2017-02-06 11:52 gfbfv1-755265261old
-rw------- u0_a18 u0_a18 30249810 2017-02-11 12:31 gfbfv1-858435026old
-rw------- u0_a18 u0_a18 43200757 2017-01-29 10:40 gfbfv1-879983232old
-rw------- u0_a18 u0_a18 36155398 2017-01-28 08:57 gfbfv1-943855039old
-rw------- u0_a18 u0_a18 31497946 2017-02-02 07:39 gfbfv11084829459old
-rw------- u0_a18 u0_a18 21801412 2017-01-10 08:42 gfbfv11421810361old
-rw------- u0_a18 u0_a18 42667297 2017-02-14 18:37 gfbfv11487072824old
-rw------- u0_a18 u0_a18 33055061 2017-01-15 14:04 gfbfv1157473315old
-rw------- u0_a18 u0_a18 62752291 2017-02-06 17:41 gfbfv11708972366old
-rw------- u0_a18 u0_a18 43200757 2017-01-27 14:58 gfbfv1570258388old
-rw------- u0_a18 u0_a18 73255639 2017-02-12 10:43 gfbfv1572587892old
-rw------- u0_a18 u0_a18 73255639 2017-02-11 12:41 gfbfv1824247130old
-rw------- u0_a18 u0_a18 43200757 2017-02-01 06:20 gfbfv1927007937old
drwx------ u0_a18 u0_a18 2017-02-16 16:38 images
drwxrwx--x u0_a18 u0_a18 2017-01-05 16:36 lds
drwx------ u0_a18 u0_a18 2017-01-05 16:36 logs
drwx------ u0_a18 u0_a18 2017-02-16 16:38 main
-rw------- u0_a18 u0_a18 0 2017-01-05 16:36 restore.log
The w/a is to simply rm -f * all these files, then phone goes back to normal.
I didn't capture the contents (next time I will), but wondering if anyone knows what these are?
I suspected google play store, so cleared cache, and it didn't help, still after few days it got filled up again..
any tips welcomed! (this is Android 5.1, latest firmware from Aug 2016 as i recall).
read in another place that this vending belongs to playstore, and it's possible to remove this folder.. so stopped playstore, did mv /data/data/com.android.vending /data/data/com.android.vending-OLD, and rebooted.. now phone seems happier...