55GB space missing on SDCard after deleting file - General Questions and Answers

I use Syncthing regularly to backup some things from the phone to my PC and it works rather nicely.
Syncthing - Wikipedia
en.wikipedia.org
However, it often chokes on big files, eg I wanted to copy some kiwix files (aka precompiled wiki) to my SDCard (the other way around which works also very well for small files).
Kiwix - Wikipedia
en.wikipedia.org
Welcome to Kiwix Server
library.kiwix.org
Well, that full wiki has some 99GB and it got stuck. So I stopped Syncthing and deleted the remnant incomplete file... took forever, I got impatient and rebooted my fon.
Ouch, no empty space was recovered - I am missing about 55GiB "emptiness". Remembering vaguely that exfat is windows, I thought to just check it quickly in Win10... except it didn't work (check via properties):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone explain this? What would be the proper way to enforce a check and free up my space?
PS: The card is a 512GB from Kingston with read/write above 70MB/s.

AFAIK modern SD-cards support CMD38 ( AKA TRIM ) command.
Check whether the SD-card in question supports CMD38 command and if, then apply it.
More info here:
Quickly Wipe an SD Card with ESP8266
In a previous story, I have written about connecting an SD Card to an ESP8266. During my adventures, I have discovered some interesting…
pawitp.medium.com

jwoegerbauer said:
modern SD-cards support CMD38 ( AKA TRIM ) command
Click to expand...
Click to collapse
Thanks! I would have expected a 512GB card is modern enough but no luck so far:
fstrim: /media/xxx/[email protected]: the discard operation is not supported
So I searched and found two apps:
https://forum.xda-developers.com/t/...ol-of-your-device-nand-chip-trimming.3038240/
https://forum.xda-developers.com/t/...tility-for-android-no-root-necessary.4258765/
Feature set was limited (basically just on and off, cannot select mounts/devices). Tried to set trim at reboot, no luck. Next step was busybox:
~ $ sudo busybox fstrim -v /storage/8549-8438
fstrim: ioctl 0xc0185879 failed: Function not implemented
Yeah, unless there is another idea... I think I just reformat it today (and won't reboot my fon next time so quickly if it occurs again).
PS: When moving all my files from sdcard to pc, something did get triggered and a lost-folder popped up. Unfortunately it was only half of it, instead of 55GB now "only" 34 were missing

Related

G1/Dream Google Bits

Ok, so I'm definitely no expert, and I've done a bit of searching seeing that people are trying to find ways to backup their proprietary google bits when it comes to the Cease and Desist order laid down upon Cyanogen. I was messing around in Terminal Emulator today and found a way to list all of the proprietary bits. I was wondering why it gives me this message, when I try to copy one of these files to the SD card?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once I understand why it "omits" the directory, and fails to copy the file, I will continue working on getting these bits to backup, so we can keep our google apps. Me personally, I use Google Maps like it's going out of style, so losing it is not an option for me, but I love CyanogenMod Roms. Thanks for any help. I can post the rest of the code if need be.
RicFusion said:
Ok, so I'm definitely no expert, and I've done a bit of searching seeing that people are trying to find ways to backup their proprietary google bits when it comes to the Cease and Desist order laid down upon Cyanogen. I was messing around in Terminal Emulator today and found a way to list all of the proprietary bits. I was wondering why it gives me this message, when I try to copy one of these files to the SD card?
Once I understand why it "omits" the directory, and fails to copy the file, I will continue working on getting these bits to backup, so we can keep our google apps. Me personally, I use Google Maps like it's going out of style, so losing it is not an option for me, but I love CyanogenMod Roms. Thanks for any help. I can post the rest of the code if need be.
Click to expand...
Click to collapse
Nevermind. I messed around with it a bit more and found out how to do it. I can now copy the proprietary google apps, to the sd card. Here is the command I used in order to make it work.
$ su
cd /data/data
ls
(It will list all of the software on your device)
cp -r "insert app name here"
cd /sdcard
ls
Click to expand...
Click to collapse
If you look now, whatever named app you copied, will now be on your sd card!
So, is anyone up for helping me write a script, and or app that will allow this to run?

HtcLoggers.apk and other eavesdroppers

By now, some you have seen reports about the latest bit of under-the-covers eavesdropping, this time by HtcLoggers.apk. In case you haven't, this post on Android Police details the whole thing pretty well.
One thing that really caught my attention was the graphic showing all the different ways various bits of Android snoop on you:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Those of us not running HTC software don't have to worry about most of these. The one that remains for all of us, at least according to the research so far, is Google Checkin, part of GoogleServicesFramework.apk. You can see in the graphic what kind of information Checkin collects and where it puts it. I've seen /data/system/dropbox before, occasionally I clear it out because it collects a huge number of files. I hadn't really paid much attention to /data/system/usagestats.
Using Root Explorer, I see that the permissions on both these directories is rwx------. As an experiment, to see if I can block whatever Checkin is collecting, I deleted their contents and then removed all permissions on these directories (and rebooted for good measure). I did this about an hour ago. So far, the directories have remained empty.
My G2 (running ILWT CM7 build 216) appears to be functioning normally, including the Market. If anything malfunctions, I'll report here.
Update. More directories to block: /data/anr, /data/tombstones, /data/dontpanic. File to block: /data/system/userbehavior.db (I first used SQLite Editor to empty the file).
Do not attempt this procedure on /data/system/throttle -- this caused my phone to enter a boot loop, which I had to repair by booting into recovery and then reverting my permissions change through ADB.
Quick follow-up... Looks like removing all permissions on the two directories has no effect on the phone's behavior. I've seen no breakage and the directories remain empty. So if you want to thwart some data collection, this looks like a decent approach.
So now that some time has passed, what is veridict? Were there any averse affects on the phone? Does everything still work?
Still seeing no problems. I did the same thing to my Nook Color, and it's also behaving normally.
This is very interesting, I'll try changing the permissions too.
Updated original post: added a few more directories to block based on additional information reported by the Carrier IQ Logging Test App.
I also gave this a try...
And so far so good! Thanks!

[Q] Cant access transformer files on PC

Hi All,
I am struggling to access my transformer files using my PC.
I have used the SDK tools and can get the device ID, so i know that bit works
USB Debugging is on
USB cable is new
I am using ICS Nightlies v24, the latest Gapps and TestyMeh v1.0 kernal
i can access the files in androids file explorer
my issue is odd, i connect my transformer to my pc and i hear the connection tone, it then shows up in my windows explorer (see picture 1). I click on it and it opens (Picture 2). then when i click on any of the files it goes to a blank window, and at the bottom it says "0 files" (Picture 3). if i try to drop a file it says it is going to root of storage and nothing happens (picture 4)
any idea why i cant see them?
1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2
3
4
Thanks
Mike
I have same issue (but not that severe). I nailed it down to the .nomedia flags. Recently, the TF is connected to the PC as a media-device, so I think that .nomedia flag will play its role.
If you have the flag in the root --> whole drive is hidden.
If you have the flag in the root of a folder --> whole folder may appears empty. I just remove the flags to see the contents. But then the multimedia apps make pick up all the junks and add them to their library.
Currently I switch to a wireless connection (using some apps like Samba) to get around.
hyperxguy said:
I have same issue (but not that severe). I nailed it down to the .nomedia flags. Recently, the TF is connected to the PC as a media-device, so I think that .nomedia flag will play its role.
If you have the flag in the root --> whole drive is hidden.
If you have the flag in the root of a folder --> whole folder may appears empty. I just remove the flags to see the contents. But then the multimedia apps make pick up all the junks and add them to their library.
Currently I switch to a wireless connection (using some apps like Samba) to get around.
Click to expand...
Click to collapse
Samba seems to allow me to access the internal and external SD card, but it isn't the .nomedia issue. I guess this will work for now, but i would still like to get it sorted..........
thanks anyway, anyone else got an ideas?
Mike
bump

[Q] SD card cannot be detected when browsing as root.

Good day, fellow XDA citizens.
Here's my problem. My phone's external storage cannot be detected by apps when they are browsing as root. See screens:
This is what it looks like when the apps are browsing as root: (i.e. granted su permissions)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it looks like when the apps are not browsing as root: (and the way things are supposed to be)
Note that these issues are not limited only to this Script Manager app, but others as well, including Android Tuner, TiB, and the likes (most apps that access the external storage)
I've noticed that fuse in external storage becomes "RO rootfs" when browsing as root, and fuse remains intact for internal storage whether or not it was given su permissions.
I've tried googling around for answers, a few articles and discussions mention fuse but I can't make a certain sense out of them, most likely because I am a scrub on linux usage.
What things can I do to try fix this issue? Any help will be much appreciated.
regards, Ocenyx
SD card not detected
I have Samsung Wave2 GT-s8530. whenever I am installing badadroid on my set whatever the ROM is my external SD card was not detected. it showed 0 MB only. Details of my phone and installation as follows:
Installed at Downloader v5.67
Fat32 is the format of SD card.
Anyone please?
By the way, this phone is running 4.4.2 version of Android. This issue was not present in 4.2.2 before.
To anyone else having this issue,
It seems to be a well-known symptom of Kitkat for MT6582 devices. I'm not certain if this problem exists on any other chip.
While we wait for any official fix for SuperSU app regarding this issue (if any), the only fix I have ever known to have worked is by using KingRoot. I'm aware that many advanced android people always discourage users from installing chinese stuff but it addresses the issue at least. It's much much better than living through this inconvenience.
Regards

Is it possible to allow app(s) to write to external storage without root ?

I have a brand new Mate 9 and am happy with it. I even did not root it as I otherwise won't get updates anymore and most things I needed to root for don't require root anymore under Nougat.
Except for one thing (?).
Apps cannot write to the external storage, except the buitin file manager and of course the USB connected MTP from a computer.
Using Airdroid, it prompts when I attempt to write to extSDCard and then I clicked on some prompts in the builtin file manager and after that Airdroid is allowed to write to extSDCard, so that works.
I would like to do the same with other apps, particularly SSHDroid (SSH server) as this is somewhat easier for syncing with rsync for a Mac or Linux computer which does work for internat storage but not for extSDCard.
Is there a possibility to allow it, at least on a per app basis ?
Or with an adb command to write settings as many apps (like Autotools) do for special rights ?
The switch below in 'Developer settings' does not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess an app should be able to properly request and get permissions to write to SDcard (or perform any other action). And it's up to developer to "teach" it.
I use Solid Explorer and it works with external memory perfectly fine after being granted permission to.
Just FYI, FolderSync got an update today which allows it to write properly to the external sdcard, and you can use it to sync over sftp (and I believe it also uses rsync internally).
As I know, the camera app can save pictures to SD card. I also wonder how to have a 3rd-party app write to SD card.
The app has to be specifically coded for the storage API. (API 23+? I don't remember the exact version.) Any app that does this will pop up a dialog box on first access that lets you choose what sd card folders to allow write to. Any app that doesn't support this will fail.
ResonanceZero said:
Just FYI, FolderSync got an update today which allows it to write properly to the external sdcard, and you can use it to sync over sftp (and I believe it also uses rsync internally).
Click to expand...
Click to collapse
But it still messes up the timestamps as another Android problem is that timestamps on both internal and external storage are always set to the copy time and not the original time.
Found the answer myself, after some searching around, but it still doesn't work.
adb shell pm grant berserker.android.apps.sshdroid android.permission.WRITE_EXTERNAL_STORAGE
But writing still fails after force quit the app and restarting it.
Why does this not work ?

Categories

Resources