Network mount option

[lightc786]

Is there any way to do this with a network share rather than an hdd directly connected?

The reason I ask is because I'd like to keep my pixel charged to 50% and I do this by using a smart outlet and tasker to automate turning it off and on to keep the battery at 50%.

If the power delivery powered USB hub turns off, the ext4 drive will disconnect.

[master-hax]

i wish. my understanding is that it is only possible with a custom kernel. the stock pixel kernel doesn't include filesystem support for nfs or cifs or smb3 etc.

so one would need to recompile the kernel with nfs support

[master-hax]

you could also set it up using a FUSE based solution but it is very slow in my experience. you could also use adb or ftp or syncthing to push media to the pixel's attached drive instead.

[DevinDuricka]

Check out EasySSHFS. It's the only way I easily found to do it on Android 10 (11?)+
I've noticed it will also scan periodically throughout the day for new media, or you can broadcast a media scan

[lightc786]

Thanks I'll look into that. Is that a fuse based solution?

How slow are these network options exactly?

I'm using syncthing current to push files to the HDD attached to the pixel but my worry is that keeping it at 100% charge is not a good idea.

Even if one of these other network solutions is a little slow, it will allow me to keep the battery at 50% to hopefully avoid it from swelling down the road.

Also I was wondering whether there is any way to get the Pixelify module to act as if it is the physical pixel I am using to do my backups. If the module could use the same IMEI, I think it would be less likely anything would be flagged by Google down the road.

For now I will use the pixel to be safe but if there was a method to clone all the attributes from my physical device into a VM with Pixelify, it would reduce a lot of the headache involved with maintaining the battery, syncing items, mounting the HDD, re-writing exif and etc.

Thanks again!

[DevinDuricka]

I'm running Android 14 on it via LineageOS, and I think every solution Android 10+ requires fuse (don't quote me on that). In this case though, yes, it is a fuse based solution.

Umm, I haven't really noticed any slowness. It does run into issues though with large files, although it could be an encoding issue with the large file itself, still investigating. Otherwise, the real limit is the network connection (reading from LAN and upload) and the CPU + Google Photos app processing speed.

I've seen some people use a magisk module called acc to limit the battery charge. LineageOS also has it built in, so I haven't had to try it yet. I also just replaced the battery in one of the other Pixels I have, and it wasn't too terrible of a process (but I've had a little practice).

Agreed though, a VM would be a great solution.