Since I have updated to the latest version the Logos app crashes before it can open. I use a Samsung Galaxy Tablet.
I'm not an android user so i will be of limited help.
What specific OS are you running? What specific device?
You <may> have resolution by deleting and reinstalling the app. I think that would mean the loss of any downloaded resources (it would on iOS).
I am having problems with Logos crashing before opening on my Android tablet as well. My wife's tablet (also Android, newer, both Samsung) works fine. I'm hoping it's not a compatibility problem with my older tablet. I've uninstalled/reinstalled and that didn't help.
My experience in the past has been that when I reinstall the software it automatically adds previously downloaded resources. Of course, this may take awhile if you have much downloaded. That was the case when L10 rolled out and there were problems with Android then.
Technically speaking, uninstalling does remove downloaded books, but they should automatically download again after re-installing. This is true in both iOS and Android.
Scott and Jeff,
If you are still having problems with Logos crashing before opening, please check in the Play Store for any available updates.
If you are still having this problem after getting up to date, please use these instructions to reset the workspace.
Thanks Joe. That is not an issue when someone has unmetered ultra-high speed internet. For those with metered or slower internet, it can be a very big deal.
My tablet is a Samsung Galaxy Tab A, Model SM-T550. It is a 16 GB, older than dirt tablet. It has 1.5 GB of RAM.
It is operating under Android version 7.1.1.
It has been sluggish of late, but the latest Logos update has put it out of its misery, as Logos crashes on startup.
Fortunately, I have other options (my wife's tablet, my phone (smaller screen, but more umph!,) and my laptop.)
We are investigating this crash and will reach out when we have more information. Thank you for your patience!
I have Pixel 7 Pro and have noticed often the app will freeze and tell me to wait, or restart. It is happening more often than it should. Not sure yet if it is a bug. Just an observation
