![]() I think Google is going in a particular direction: if you want lots of storage, buy a more expensive device that includes it internally. I don’t think this is the fault of the Syncthing android app. The only difference between the two devices is the use of the SD card. This means I wind up only starting Syncthing when I know something needs to be synced, and then I reboot the tablet once I see that it has synced. The binary keeps running and syncing, but the UI becomes unresponsive and Android asks me if I want to kill the app. My tablet is running Lollipop, and this seems to work (see below), but I understand further changes were made to the way SD cards work in Marshmallow and Nougat, so this could still be problematic in newer versions of Android.Įven with these changes, I experience the UI lockups noted by others above. Otherwise, Android itself limits access to the SD card. To get this to work at all, I must have the tablet rooted and have used the SD Fix app to restore pre-Kit-Kat functionality to the SD card. This is where I have the most problems, and I don’t think it’s the fault of Syncthing rather, I think it’s a limitation imposed by the design of Android. On the tablet (LG GPad 8.3), I have 16GB of internal memory and a 64GB micro SD. I sync the phone’s pictures and a few folders that have notes (recently replaced Evernote with Orgzly to do this). On the phone (a Moto G4), it works flawlessly, but that’s because I’m only using internal storage. I use Syncthing on two Android devices, a phone and a tablet. And also - in 99% of cases I can’t access the web UI from within the app once I set a password for it (remote access is fine though…) Now after “set it” i’d “forget it” and usually it works OK.ītw: I know i should be able to access WebUI within the app as well, but again, the wrapper itself will often hang before i get anywhere.Using the Web UI remotely like that is much easier, responsive and besides, there are many settings that are missing from the wrapper’s GUI (some versioning options and more). Access the Web UI via browser from some PC on the same LAN, and configure all the rest, folders devices, etc. Install, while it’s still “light” - configure android app’s settings (run conditions, etc.), set Web UI password.What I normally do (with my device and other that I help people to set up) is as follows: so I came to avoid using the “native UI” as much as possible. I often would give up just trying to get to the debug logs without the UI hanging on me. The wrapper’s UI is very unresponsive and super slow, often hangs (while ST itself is alive - files still fly around). However I do agree that it is a PITA to manage: I do use the android app on daily basis, and it does it’s core job (syncing stuff). Thanks Felix for your hard work on the Android side. Most of my Linux’s are servers (and VM’s at that) and don’t need to sync anything with my workstations. I wonder if that’s also an issue for some.Īdmittedly I only use ST much to Sync my windows home and work boxes (it rocks on Windows). I have noticed also, since then, far more stability from my apps and phone in general. I have since those days grown tired of modding my phone and constantly having to odin it back to health every weekend. Also had lots of instability and battery issues because of it. I wonder if rooting, custom roms or bootloaders (TWRP, ClockworkMod) could be causing these instability issues.īack in my day I did all the “ things” too and used custom roms and BL’s you name it. In fact I don’t know if I can recall the last time it crashed on me. No noticeable crashes or battery drain issues. ![]() I also use ST Android (but not heavily just for syncing pics and stuff also one Keepass file). I’m probably just being a “me too” but my $.02
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |