when trying to install locus pro on my xperia m4 aqua dual it complains about not supported device.
This object is in archive!
Locus crashes on xperia M4 Aqua
Solved
On startup it crashes.
adb log:
- E/SQLiteLog(26384): (1032) statement aborts at 8: [CREATE TABLE info (minzoom INTEGER,maxzoom INTEGER,center_x DOUBLE,center_y DOUBLE,zooms TEXT,provider INTEGER);]
- E/AndroidRuntime(26384): FATAL EXCEPTION: Thread-562
- E/AndroidRuntime(26384): Process: menion.android.locus, PID: 26384
- E/AndroidRuntime(26384): android.database.sqlite.SQLiteReadOnlyDatabaseException: attempt to write a readonly database (code 1032)
- E/AndroidRuntime(26384): at android.database.sqlite.SQLiteConnection.nativeExecuteForChangedRowCount(Native Method)
- E/AndroidRuntime(26384): at android.database.sqlite.SQLiteConnection.executeForChangedRowCount(SQLiteConnection.java:748)
- E/AndroidRuntime(26384): at android.database.sqlite.SQLiteSession.executeForChangedRowCount(SQLiteSession.java:754)
- E/AndroidRuntime(26384): at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:64)
- E/AndroidRuntime(26384): at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1676)
- E/AndroidRuntime(26384): at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1605)
D
The same problem 
Hello guys!Yesterday I installed the new firmware (26.1.A.2.99). The Locus v2.20.1 runs perfectly on it. I can create and import points, save tracks. The Locus can write into the internal memory. The factory firmware also tried, but I could not save anything.
It would be nice to try out the latest version to see if it works. (sorry for my english)
Hello guys!Yesterday I installed the new firmware (26.1.A.2.99). The Locus v2.20.1 runs perfectly on it. I can create and import points, save tracks. The Locus can write into the internal memory. The factory firmware also tried, but I could not save anything.
It would be nice to try out the latest version to see if it works. (sorry for my english)
Good day Andreas, sorry for a troubles.
I'm surprised that you even see Locus Free on a Google Play. Yesterday I've disabled Locus for this device for Locus Map Free and Locus Map Pro.
We already received few same reports from different users. Unfortunately, we still have absolutely no idea! what happen here and why. Locus is not ale to write to required databases even they are placed on SD card. On 100% it is an issue in Android in M4 Aqua device, so maybe an update of system that may comes in future, may solved it.
For now sorry, no existing solution as I know.
EDIT: btw, this is first device ever, I have disabled support for, since Locus existence.
Good day Andreas, sorry for a troubles.
I'm surprised that you even see Locus Free on a Google Play. Yesterday I've disabled Locus for this device for Locus Map Free and Locus Map Pro.
We already received few same reports from different users. Unfortunately, we still have absolutely no idea! what happen here and why. Locus is not ale to write to required databases even they are placed on SD card. On 100% it is an issue in Android in M4 Aqua device, so maybe an update of system that may comes in future, may solved it.
For now sorry, no existing solution as I know.
EDIT: btw, this is first device ever, I have disabled support for, since Locus existence.
Found an interesting post on that - not sure if this could be related:
http://stackoverflow.com/questions/26937152/workaround-for-nexus-9-sqlite-file-write-operations-on-external-dirs
an ls -li on the Locus dir - at least it seems that inodes are > 32 bit.
ls -li /storage/emulated/legacy/Locus/
367106556384 drwxrwx--- root sdcard_r 2015-07-09 20:24 backup
367106558624 drwxrwx--- root sdcard_r 2015-07-09 20:24 cache
367106276224 -rw-rw---- root sdcard_r 11400 2015-07-09 20:25 config.cfg
367106554464 drwxrwx--- root sdcard_r 2015-07-09 20:24 data
367106557344 drwxrwx--- root sdcard_r 2015-07-09 20:24 export
367106557504 drwxrwx--- root sdcard_r 2015-07-09 20:24 icons
367106555904 drwxrwx--- root sdcard_r 2015-07-09 20:24 logs
367106559104 drwxrwx--- root sdcard_r 2015-07-09 20:24 mapItems
367106552544 drwxrwx--- root sdcard_r 2015-07-09 20:24 maps
367106558304 drwxrwx--- root sdcard_r 2015-07-09 20:24 mapsOnline
367106558784 drwxrwx--- root sdcard_r 2015-07-09 20:24 mapsVector
small addition: the xperia is
getprop ro.product.cpu.abi
arm64-v8a
Found an interesting post on that - not sure if this could be related:
http://stackoverflow.com/questions/26937152/workaround-for-nexus-9-sqlite-file-write-operations-on-external-dirs
an ls -li on the Locus dir - at least it seems that inodes are > 32 bit.
ls -li /storage/emulated/legacy/Locus/
367106556384 drwxrwx--- root sdcard_r 2015-07-09 20:24 backup
367106558624 drwxrwx--- root sdcard_r 2015-07-09 20:24 cache
367106276224 -rw-rw---- root sdcard_r 11400 2015-07-09 20:25 config.cfg
367106554464 drwxrwx--- root sdcard_r 2015-07-09 20:24 data
367106557344 drwxrwx--- root sdcard_r 2015-07-09 20:24 export
367106557504 drwxrwx--- root sdcard_r 2015-07-09 20:24 icons
367106555904 drwxrwx--- root sdcard_r 2015-07-09 20:24 logs
367106559104 drwxrwx--- root sdcard_r 2015-07-09 20:24 mapItems
367106552544 drwxrwx--- root sdcard_r 2015-07-09 20:24 maps
367106558304 drwxrwx--- root sdcard_r 2015-07-09 20:24 mapsOnline
367106558784 drwxrwx--- root sdcard_r 2015-07-09 20:24 mapsVector
small addition: the xperia is
getprop ro.product.cpu.abi
arm64-v8a
so it seem that providing the arm64 libs inside locus could solve the issue.
so it seem that providing the arm64 libs inside locus could solve the issue.
I think that is a very good lead given by Andreas. Kudos for that! So switching to 64bits is starting to play tricks, possibly. Why not on other devices? And thinking about this, then the M4 might be the first of a new range of devices that start showing the same issues. I just read through the link Andreas provided and it seems to provide a solution. So maybe it is worthwhile to still dig into this and prevent issues from Locus-with-SQLite running on 64 Android versions that are not patched yet.
I think that is a very good lead given by Andreas. Kudos for that! So switching to 64bits is starting to play tricks, possibly. Why not on other devices? And thinking about this, then the M4 might be the first of a new range of devices that start showing the same issues. I just read through the link Andreas provided and it seems to provide a solution. So maybe it is worthwhile to still dig into this and prevent issues from Locus-with-SQLite running on 64 Android versions that are not patched yet.
Hello guys,
sorry, ARM 64 libraries are already included!! in Locus. This is not just about ARM64, but it is about ARM64-v8. Which should be backward compatible with already included 64 bit version, but they aren't due to issue in Locus. But most important, for work with point/track database aren't used any special library from Locus, but it used sqlite.so library that is already part of Android!!!
Btw. mentioned topic is already reported here http://help.locusmap.eu/topic/error-saving-data .
But from what we already tested on other users, exactly same issue happen even when they place Locus into internal memory or into special Locus directory in "/external/0/Android/data/menion.android.locus"/files . So sorry, these are known information for me that has no usage.
Hello guys,
sorry, ARM 64 libraries are already included!! in Locus. This is not just about ARM64, but it is about ARM64-v8. Which should be backward compatible with already included 64 bit version, but they aren't due to issue in Locus. But most important, for work with point/track database aren't used any special library from Locus, but it used sqlite.so library that is already part of Android!!!
Btw. mentioned topic is already reported here http://help.locusmap.eu/topic/error-saving-data .
But from what we already tested on other users, exactly same issue happen even when they place Locus into internal memory or into special Locus directory in "/external/0/Android/data/menion.android.locus"/files . So sorry, these are known information for me that has no usage.
Ok, so I have to switch to another app.
I guess it will happen on any file with 64 bit inodes
Ok, so I have to switch to another app.
I guess it will happen on any file with 64 bit inodes
OK Menion, clear. So would you then say that this issue needs to be fixed in Android? As the article on stackoverflow suggests. It would mean that all 64bit devices with the broken version of Android will not be capable of running Locus. If so, that would be a big red warning for me, being a profound Locus user, to be very careful with buying a new, 64bit..., phone. I would then need to check before, whether it comes with a certain minimum version of Android 5. Can you point this out?
OK Menion, clear. So would you then say that this issue needs to be fixed in Android? As the article on stackoverflow suggests. It would mean that all 64bit devices with the broken version of Android will not be capable of running Locus. If so, that would be a big red warning for me, being a profound Locus user, to be very careful with buying a new, 64bit..., phone. I would then need to check before, whether it comes with a certain minimum version of Android 5. Can you point this out?
Hello guys!Yesterday I installed the new firmware (26.1.A.2.99). The Locus v2.20.1 runs perfectly on it. I can create and import points, save tracks. The Locus can write into the internal memory. The factory firmware also tried, but I could not save anything.
It would be nice to try out the latest version to see if it works. (sorry for my english)
Hello guys!Yesterday I installed the new firmware (26.1.A.2.99). The Locus v2.20.1 runs perfectly on it. I can create and import points, save tracks. The Locus can write into the internal memory. The factory firmware also tried, but I could not save anything.
It would be nice to try out the latest version to see if it works. (sorry for my english)
Ah, thanks for the heads up! That is good news. My friends M4 is now gone for repair (broken accelerometer), but when back then updating is surely the first thing to do & try.
Ah, thanks for the heads up! That is good news. My friends M4 is now gone for repair (broken accelerometer), but when back then updating is surely the first thing to do & try.
i can confirm Locus Free 3.10.3 is runnig perfectely with the new firmware (26.1.A.2.99).
Please unblock the pro version in the play store or post a downlink here.
thank you very much!
i can confirm Locus Free 3.10.3 is runnig perfectely with the new firmware (26.1.A.2.99).
Please unblock the pro version in the play store or post a downlink here.
thank you very much!
Please post a download link for the pro version of " Locus Free 3.10.3".
Thank you.
Please post a download link for the pro version of " Locus Free 3.10.3".
Thank you.
Thanks for confirmation that version works fine. I'll publish new version of Locus on Google Play in the end of this week.
EDIT: new version will be delayed most probably to 6. - 7. of August
Thanks for confirmation that version works fine. I'll publish new version of Locus on Google Play in the end of this week.
EDIT: new version will be delayed most probably to 6. - 7. of August
I've got the same problem but I've got firmware 26.1.A.1.100
I've got the same problem but I've got firmware 26.1.A.1.100
Replies have been locked on this page!