Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - beonun

Pages: [1] 2 3
1

Hmm...
Anyway, I have tested a few sqlitedb mapfiles  in various ways  and restarted the device twice.
But it.s the same.

The Google offline mapfile(sqlitedb) is normally initialized in 'Device Storage', but it's not  in 'SD memory card'.
And .tar mapfile  is normally read in SD memory card.
That's it!



2
Thanks menion!

Have you also tested it in Android 4.4(Kitkat) above ?
I guess that the initialization error of the sqlite map in the external SD is related with Android 4.4


https://developer.android.com/about/versions/android-4.4.html
---------------
External storage access

You can now read and write app-specific files on secondary external storage media, such as when a device provides both emulated storage and an SD card. The new method getExternalFilesDirs() works the same as the existing getExternalFilesDir() method except it returns an array of File objects. Before reading or writing to any of the paths returned by this method, pass the File object to the new getStorageState() method to verify the storage is currently available.

Other methods for accessing your app-specific cache directory and OBB directory also now have corresponding versions that provide access to secondary storage devices: getExternalCacheDirs() and getObbDirs(), respectively.

The first entry in the returned File array is considered the device's primary external storage, which is the same as the File returned by existing methods such as getExternalFilesDir().

Note: Beginning with Android 4.4, the platform no longer requires that your app acquire the WRITE_EXTERNAL_STORAGE or READ_EXTERNAL_STORAGE when you need to access only your app-specific regions of the external storage using the methods above. However, the permissions are required if you want to access the shareable regions of the external storage, provided by getExternalStoragePublicDirectory().

-------------------------

3
About the sqliteDB map  importing error  in external memory(SD) - Android 4.4.2

Have you heard the sqlite map importing error in external SD memory ?
I've just known it when I moved the Google offline map to SD memory in Galaxy Note 3.



Chek it over, pls.

4
Information / About adding custom online map not using WGS84 Datumn
« on: December 22, 2012, 08:01:25 »
Quote from: "torayoko"
Hi menion. Could you offer some korea maps?
1. DAUM map (http://local.daum.net)
2. NAVER map (http://map.naver.com)

The biggest problem is that, these maps doesn't use wgs84 coordinate. it uses TM, KATEC coordinate.
but it seems like there is a solution.
http://code.google.com/r/swkim01-osmand/source/browse/
This is OsmAnd Korea map sources. so you can consult this one.

Tile url : DataExtractionOSM/src/net/osmand/map/TileSourceManager.java
Coordinate transformation : DataExtactionOSM/src/net/osmand/osm/GeoPoint.java, GeoTrans.java, MapUtils.java(wgs84), DaumMapUtils.java(ă…‡DAUM map-TM), NaverMapUtils.java(NAVER map-KATEC)

Of course, I got developer's consent to use this sources to put in LOCUS. I hope you consider this...

menion !
Have u considered about the above ?

I also want to add the above online map(Daum, Naver)
I really want to read your comment about this.

Have a happy X-mas!

5
Wishlist / Re: Adding 'Waypoint next' to the top panel
« on: July 18, 2012, 12:46:49 »
When I say " I still could not understand why the next waypoint is not the closest waypoint from the current over the track", I mean the track and waypoints are normally imported. And waypoints are displayed  red dots on my track.
But the field of 'name of waypoint'  display a specific waypoint and is not changed though I move over other waypoint.
Morever, the point is not real next waypoint.

At present, Locus has the fixed route points(red dot points) after the track is imported.
Can I add the red dot points after importing ?
Sometimes I want to add a waypoint as a route point on my way to the destination.

I think it is desirable that the route points can be added after the track is imported.
To do that, the route points(red dot points) are not decided as the track is imported.
They have to be dicided when the user select 'Guide on'  a specific track.
Waypoints on  and around the track are listed up as the route points(red dot points)
Waypoints within 50m around the track can be the route points.
What do you think about this?

I wish Locus will be better!
Always thanks!

6
Wishlist / Re: Adding 'Waypoint next' to the top panel
« on: July 16, 2012, 12:12:08 »
Special thanks! Menion!
I've tested this on 2.5.2.

But I still could not understand why the next waypoint is not the closest waypoint from the current over the track.
I want to know which waypoint is the next on Locus. How do you figure out the next waypoint on the track ?

In my thought, when I set 'Guide on' a track, waypoints over the track are are listed up as 'active route points'  
So, they are sort down to the distance from the current place. They can be 'the next waypoint' automatically, one by one.

And I find out the waypoints of gpx file are always not imported as a route point. Some are only imported as waypoints.
So, when I set the track 'Guide on', top panel is not activated.
What is the differences between them ?

7
Wishlist / Re: Adding 'Waypoint next' to the top panel
« on: July 04, 2012, 10:32:01 »
I have noticed that my intention is not properly expressed when I installed 2.5.1
I only want to use 'Guide on' on Track Navigation with Locus.

Usually I record the track with track record funcion when I climb the mountain.
I create a waypoint at the place where I need to review later, naming 'Bridge1, Gate1, Alley Start, ...
So the track I've made has many trackpoints and a few wayponts.


I want to use the recorded track when I climb the same course.
When I select 'Guide on', I want to see the name of the waypoint and the distance to the waypoint that I created  on top panel.
The thing I want to see is not a meaningless point name(point 267, 345, ....)
Point 1, 2, ... are only track points. They are not waypoints.
I want to see the waypoint name (Bridge1, Gate1, Alley Start, ....) and the distance to that point.

8
Wishlist / Re: Adding 'Waypoint next' to the top panel
« on: July 02, 2012, 23:19:49 »
That's right !

You can add other fields (like 'Waypoint at Destination, Bearing, Heading, Sunrise, Sunset, ...) to the top panel.
And in my opinion, 'Waypoint at Next' is better than ''Name of next waypoint'

I really appreciate your quick reply^^

9
Wishlist / Adding 'Waypoint next' to the top panel
« on: July 01, 2012, 05:20:12 »
Dear Menion

Do you remember the below ? ^^
--------------------------------------------------
Could you add  'waypoint next' to top panel ?
I have tested 'improved guiding top panel'
I can view 'Distance to next waypoint', but I can not know clearly which waypoint is the next.
Sometimes I have confused which waypoint is the next and whether Locus is operated properly or not.
If the 'Waypoint next' is added, and I select ' Waypoint next' on left top, 'Distance to next' on right top , I could see easily what I want to see.
-----------------------------------------------
Always Thanks !

10
Under review / Re: Adding 'Waypoint next' to guiding top panel
« on: December 03, 2011, 01:28:13 »
Dear Menion

Do you have any reason not to feed back about this ?
I think this is very useful and is actually included in Garmin Oregon series.
http://garmin.blogs.com/softwareupdates ... ation.html
I use this function on climbing and mountain biking.

I want to know your opinion about this.
I would be sorry if you did not see this post.

Disappointed wih u.

11
Under review / Adding 'Waypoint next' to guiding top panel
« on: November 29, 2011, 00:34:05 »
Quote from: "menion"
oki, so I created this .. fine?

[attachment=0:3hvf6fjd]device-2011-10-09-125059.png[/attachment:3hvf6fjd]

Dear Menion

Could you add  'waypoint next' to top panel ?
I have tested 'improved guiding top panel'
I can view 'Distance to next waypoint', but I can not know clearly which waypoint is the next.
Sometimes I have confused which waypoint is the next and whether Locus is operated properly or not.
If the 'Waypoint next' is added, and I select ' Waypoint next' on left top, 'Distance to next' on right top , I could see easily what I want to see.

Always Thanks!

12
Locus Classic (LM Free, LM Pro) / Re: [APP] - version 1.14.x
« on: November 08, 2011, 23:18:28 »
Quote from: "beonun"
Thanks Menion!

I am so glad that waypoints of the track are imported as rte points in the version 1.14.1
So I can see top panel 'distance to next point'.... when I select 'Guide on' the track.
But waypoints of the track were not imported as points in 'Points' section. I can not see any points.

And if I want to add rte points to the track after importing the gpx, what can I do ?
As I know, on track navigation in Gamin device, eg. Oregon 550,
"For a waypoint to appear as on the track, it must be within 100 meters of a track segment. Specifically, it will be connected to the closest track segment"

So when I create a waypoint just on the track or, within 100 meters of the track, I can see the waypoint as a rte point.

Thanks again for your troubles !!!

13
Troubles & Questions / Re: Distance to a point on track navigation
« on: November 08, 2011, 23:16:34 »
Thanks Menion!

I am so glad that waypoints of the track are imported as rte points in the version 1.14.1
So I can see top panel 'distance to next point'.... when I select 'Guide on' the track.
But waypoints of the track were not imported as points in 'Points' section. I can not see any points.

And if I want to add rte points to the track after importing the gpx, what can I do ?
As I know, on track navigation in Gamin device, eg. Oregon 550,
"For a waypoint to appear as on the track, it must be within 100 meters of a track segment. Specifically, it will be connected to the closest track segment"

So when I create a waypoint just on the track or, within 100 meters of the track, I can see the waypoint as a rte point.

Thanks again for your troubles !!!

14
Troubles & Questions / Re: Locus and the attached gpx file on Gmail
« on: November 04, 2011, 05:24:55 »
Special thanks !  Menion!

My phone is Galacy S2 and Gingerbread 2.3.5
Anyway,  I have reviewed AndroidMenifest.xml of Locus 1.14.0.1 and OruxMaps 4.5.7 to solve this.
I understand this depends on Gmail's attached file support policy.

In this situation,
if the below code is insertd in AndroidMenifest.xml of Locus, I could excute Locus at Gmail's gpx file download by helping Astro file manager.
 
<data android:scheme="content" android:mimeType="application/octet-stream" />

I think this may not be desirable on Locus, but considerable in this situation, anyway.
The best is Gmail's file support policy change, for sure.
I want you to  review about this.


Thanks again for your quick reply.

15
Troubles & Questions / Re: Locus and the attached gpx file on Gmail
« on: November 03, 2011, 15:52:40 »
Thanks Menion !

Somebody answered me :

<intent-filter>
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
                <data android:scheme="file" />                              
                <data android:mimeType="*/*" />
                <data android:pathPattern=".*\.gpx" />
                <data android:host="*" />
</intent-filter>
He says :
If the above code is added in Locus' AndroidManifest.xml,  you could open the gpx file on Locus.

Would you test this ?
If it is possible, would you bring me Locus apk beta to test this ?

I always appreciate for your reply.

Pages: [1] 2 3