glitching

joined 1 week ago
[–] glitching@lemmy.ml 3 points 11 hours ago

possible. I tried it at one point with the -Z option, which should disable compression but no change, same result.

[–] glitching@lemmy.ml 6 points 11 hours ago

works. still would like to know what the issue is with adb.

28
submitted 12 hours ago* (last edited 12 hours ago) by glitching@lemmy.ml to c/android@lemmy.world
 

trying to transfer a large (13 GB) folder via USB to my phone with adb push. if I try singular, smaller files they go through, pushing the whole folder hangs adb and then gets OOM killed.

adb pull from phone #1 worked without issues, pushing it to phone #2 starts eating up all RAM (16 GB) and then gets killed. so I created a 16 GB swap file, swapon, push - same thing, eats up all RAM, then all swap, then OOM manager kills konsole. no files are created on the phone.

transferring via MTP isn't viable, it's like 700 bytes/sec.

tried everything suggested here.

edit: tried adb over wifi, different terminal, same deal.

[–] glitching@lemmy.ml 3 points 2 days ago

tl;dr - attacker needs to be connected to your wifi to exploit it. wish they'd lead with that.

[–] glitching@lemmy.ml 106 points 2 days ago* (last edited 2 days ago) (4 children)

not a plex user but someone buried the lede here... to me, this is the neon sign that screams GTFO:

we noticed that you've accessed libraries in the past

what business of yours is it to notice my private comings and goings?! what other actionable intel do y'all keep in your logs?! bye!

[–] glitching@lemmy.ml 2 points 4 days ago

I ran something similar a while ago; it automated the steps you're describing so it downloaded every new video from the channels I'm subscribed to along with metadata. I gave that up as it's hella inefficient. what I have now is just a media sink by way of macast and I can send videos for playback to my media PC. so if you don't need those videos for archiving purposes, try it out.

[–] glitching@lemmy.ml 9 points 6 days ago (1 children)

don't go with server variants of the OS. they are intended for boxes that work without display and keyboard, which you have. instead, install any normal distro you're familiar with. it's infinitely easier to fix something with the full GUI at your disposal.

this is just your first install, you will iterate, and through that process you'll get better and leaner, in terms of underlying OS. think of it as training wheels on a bike, you'll pull them off eventually.

wired connection only, leave wireless turned off, and assign it a static IP address.

don't do containerS, do one container first. figure out where you're gonna store the compose files, where it will store data, how you will back that data up, etc. then add another. does it fit into your setup? do you need to modify something? rinse. repeat.

casaOS, aside from it's murky background (some chinese startup or sumsuch, forgot?) doesn't provide that path forward nor allows you to learn something, too much hand holding.

good luck.