This object is in archive! 
Android 6.0.1 issues
Not a Problem
1. Locus has some problems dealing with read only extsdcard (check screenshot). First say extsdcard is read only but then offers a folder there.
2. Error 1152 when checking license. After clearing google play data locus is able to check licence
Files:
Screenshot_2016...
Good day Venereo,
"sdcard" on your screenshot is real physical SD card in device? I see no problem on your screenshot to be true. For me it looks like "sdcard" path is some writable memory where already exists Locus folder (internal memory probably) and second option is maybe SD card itself? Hard to say. Anyway when you select first option, that something do not work?
2. Error 1152 is some issue in Google Play application itself. Are you using valid official ROM with latest Google Play application?
Good day Venereo,
"sdcard" on your screenshot is real physical SD card in device? I see no problem on your screenshot to be true. For me it looks like "sdcard" path is some writable memory where already exists Locus folder (internal memory probably) and second option is maybe SD card itself? Hard to say. Anyway when you select first option, that something do not work?
2. Error 1152 is some issue in Google Play application itself. Are you using valid official ROM with latest Google Play application?
First item is internal sdcard, third is extsdcard, second is not valid (why locus detect it?) and fifth shouldn't be possible (it's in the read only extsdcard).
Using open_gapps-arm-6.0-nano-20160210 on cm13
First item is internal sdcard, third is extsdcard, second is not valid (why locus detect it?) and fifth shouldn't be possible (it's in the read only extsdcard).
Using open_gapps-arm-6.0-nano-20160210 on cm13
Oki, I still do not have answer on "when you select first option, that something do not work".
As I still see, what you see is just correct. Why is second option detected? Don't know. Android code returned this path on request "give me all possible locations".
And sorry, but I cannot help here with second problem for custom unoffical roms. I never saw this error code on official rom (maybe I never saw this error at all).
Oki, I still do not have answer on "when you select first option, that something do not work".
As I still see, what you see is just correct. Why is second option detected? Don't know. Android code returned this path on request "give me all possible locations".
And sorry, but I cannot help here with second problem for custom unoffical roms. I never saw this error code on official rom (maybe I never saw this error at all).
If it's OK for you it's ok for me, I've work it around. I understand it's difficult to track non official roms' problems but I've always used the nasty non-oficial rom + non oficial kernel + xposed + lp combination and always worked fine. Let's wait to see then, maybe it's just my issue
If it's OK for you it's ok for me, I've work it around. I understand it's difficult to track non official roms' problems but I've always used the nasty non-oficial rom + non oficial kernel + xposed + lp combination and always worked fine. Let's wait to see then, maybe it's just my issue
Oki, thanks. Usually in cases, there is any problem with licensing, we suggest to clear a cache of Google Play application + restart of device. I'm little worried that it won't help here, but you may give it a try. Otherwise, I'm worried it will be need to wait for next update of ROM or gapps library.
Oki, thanks. Usually in cases, there is any problem with licensing, we suggest to clear a cache of Google Play application + restart of device. I'm little worried that it won't help here, but you may give it a try. Otherwise, I'm worried it will be need to wait for next update of ROM or gapps library.
It's a nightly yes, but getting folders is pretty basic OS stuff, I don't think that's the problem. Since LL makes distinction between system sdcard and removable sdcard (needs formating to make a removable sdcard to work as system sdcard) I thought that was something related to that
It's a nightly yes, but getting folders is pretty basic OS stuff, I don't think that's the problem. Since LL makes distinction between system sdcard and removable sdcard (needs formating to make a removable sdcard to work as system sdcard) I thought that was something related to that
Which brings another issue: shouldn't locus be able to write to sdcard on MM?
Which brings another issue: shouldn't locus be able to write to sdcard on MM?
No app, except system apps is able to write directly to SD card. Since Android 5.0 is possible use quite complicated system which is usable for some basic tasks (and Locus use it for vector maps, SRTM files and backup), but for more complicated tasks (like direct access to SQLite database - maps) it is not usable. Unfortunately.
No app, except system apps is able to write directly to SD card. Since Android 5.0 is possible use quite complicated system which is usable for some basic tasks (and Locus use it for vector maps, SRTM files and backup), but for more complicated tasks (like direct access to SQLite database - maps) it is not usable. Unfortunately.
From my experience and understanding (take ES file Explorer working non-root for example) you offer the user a system dialog where the user choose which folder the app is allowed to write data to. Isn't as simple as that?
From my experience and understanding (take ES file Explorer working non-root for example) you offer the user a system dialog where the user choose which folder the app is allowed to write data to. Isn't as simple as that?
In case of plain files ... yes. In case of direct connection to file over existing libraries (like connection to SQLite DB) ... nope.
In case of plain files ... yes. In case of direct connection to file over existing libraries (like connection to SQLite DB) ... nope.
Replies have been locked on this page!