This object is in archive! 
Locus free 3.4.0 crashes on Woxter QX105 Tablet
Solved
I've installed locus free 3.4.0 on my tablet (Model Woxter QX105, 1 GB RAM DDR3, CPU: Quad Core Cortex A7, GPU: Mali-450 MP4, Android version: 4.4.2) and, even though the installation seems to be OK, it always crashes on startup. I've reinstalled the app but nothing changes.
Good day Paco,
sorry for a troubles. Unfortunately to fix such serious issue, I need a log made by this method http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log .
Also you say "Locus crash". Describe me please more precisely, what you see as last on screen before crash, thank you!
Good day Paco,
sorry for a troubles. Unfortunately to fix such serious issue, I need a log made by this method http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log .
Also you say "Locus crash". Describe me please more precisely, what you see as last on screen before crash, thank you!
Hi Paco, thanks for the screenshots. On last screenshot is exactly what I needed, thanks!
Seems that you tablet has some serious problem and is missing one function that is required by Locus on many places. I found out that more people already reported this issue and all on Woxter QX105 or QX115 tablets.
I did a small change in code that should help with this issue. In such cases, I really hope that such change helps here and mainly that it do not cause more troubles on different devices :).
So please let me know later after test 3.5.2 version (during this week). Hope it helps, because otherwise I have absolutely no idea how to solve it now.
Hi Paco, thanks for the screenshots. On last screenshot is exactly what I needed, thanks!
Seems that you tablet has some serious problem and is missing one function that is required by Locus on many places. I found out that more people already reported this issue and all on Woxter QX105 or QX115 tablets.
I did a small change in code that should help with this issue. In such cases, I really hope that such change helps here and mainly that it do not cause more troubles on different devices :).
So please let me know later after test 3.5.2 version (during this week). Hope it helps, because otherwise I have absolutely no idea how to solve it now.
Replies have been locked on this page!