Has anyone been having trouble keeping fdroid apps working? For some reason when I reboot my phone the setting for the "shared folder" keeps getting turned off. If I try to launch an fdroid app under that condition it seems to crash the process that deals with fdroid, necessitating another reboot in order to get apps installed through fdroid to work again. Of coarse when the phone does end up booting I need to remember to turn on the shared storage... When I do get an fdroid app to launch it only takes up 3/4 of the screen and you are unable or only sometimes able to interact with UI elements along the bottom of the app window
This post was modified 3 weeks ago 2 times by goodstuff9
@jpitz NOT, NOT, NOT an expert here, but here is how I think about it and dealt with it.
At times the android container (andromeda) just crashes and locks up - just like an android phone locking up. When that happens, android apps either just don't start, or they run in that crazy looking half screen mode. So, just as you need to reboot an android phone when it locks up, that's what I've found I've had do with the FLX1s: I go into Settings >> Android, and turn it off, wait a bit to make sure it has ended, and then turn restart it, give it a few moments to boot up, and then all android apps are okay.
I saw the same thing with the shared folder always getting disabled. Well, I noticed when I have android set to start at boot, I'd have general android problems more times than I cared to deal with. So, I set it NOT to start at boot, and just told myself part of the phone booting process is to always go into settings after the phone has finished booting and then start android AND reenable shared folder. Things have worked a lot better that way.
Don't know how much this affects things: I'm pretty anal about going into Console >> memory and quitting applications that don't need to be running and consuming precious RAM.