tlaukkanen / mobile-trail-explorer

Automatically exported from code.google.com/p/mobile-trail-explorer
2 stars 0 forks source link

Exportfolder unselectable #175

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. go to options
2. click on exportfolder
3. nothing happens

What is the expected output? What do you see instead?
Nothing, the Phone crashes if I try to start the recording

What version of the product are you using? On what operating system?
1.14 on Siemens SP65 mobile phone, with navibe blutooth dongle.

Please provide any additional information below.

My GPS wasn't found so I enabled the Bluetooth fix. Now the GPS is found
and positions is displayed. When I try to start the track recording the
screen becomes black and the app seem to crash.
I only had to confirm bluetooth acess, normaly filesystem acess, to or? I
tried to log the behaviour but unfortunely there won't be any logs created.
My account on osm.org is !i!

Original issue reported on code.google.com by g...@mailinator.com on 26 Apr 2009 at 10:19

GoogleCodeExporter commented 9 years ago
I have a similar problem with my Motorola A1200 (Ming) - which I use in 
combination
with the Motorola GPS receiver T805. When I navigate to 'Setting' -> 'Export 
Folder'
I can't select anything.

I tried the stable (1.14) and the beta (1.15) version aswell as the mobile 
touchpad
version of MTE by Patrick Oosterveld.

The relevant permission settings for the application are:
- 'User data read': 'Access denied' (that's the only option available)
- 'User data write': 'Always ask' (second option would also be 'Access denied')

I can trace the track without any problems. When I click on 'Start/Stop' again 
(to
stop the tracking) I come to the 'Trail Actions'-Dialog. When I activate 
'Export to
KML' and/or 'Export to GPX', after I gave MTE my 'permission to write to files 
or
directory', I get this:

KML: Save Failed
java.lang.Exception:
writeToFile: Open Connector:
java.lang.illegalArgumentException: Illegal file connection name!

and/or

GPX: Save Failed
java.lang.Exception:
writeToFile: Open Connector:
java.lang.illegalArgumentException: Illegal file connection name!

When I activate the option 'Save GPX Stream also as Default' (in 'Settings' ->
'Recording') the problem starts when I hit the 'Start/Stop'-Button the first 
time (to
start the tracking) - I get one error message after the other (the only 
difference is
the value of ********):

Error in recorder task:
java.lang.NullPointerException:0
controller ist h@1ee07f43
current position ist eu@********

So I have to kill the application. When I start it again, I come to the 'Stream
Recovery'-dialog, but it makes no sense because I just can't save the GPX-track.

However, it seems to be possible to save the trail. When I check the 'Save 
Trail' box
(and nothing else) in the 'Trail Actions'-dialog, I get this:

RMS: Save succeeded

I really hope this problem can be solved. I love this application and I'd 
really like
to use it... Please tell me if I can help with any additional information.

Original comment by ghost68w...@gmail.com on 15 May 2010 at 12:59

GoogleCodeExporter commented 9 years ago
OK, I managed to get rid of the restrictive permission settings with a program 
for
the Motorola A1200 called 'Java Hacker' by Dedracks (published in the
motorolafans-forum).

But still, the problem keeps the same: When I go to 'Settings' -> 'Export 
Folder' I
can't select anything. I don't really think so but maybe this bug is related to 
Issue
116? AFAIK the path of the SD Card is /mmc/mmca1/

I also still get this error when I try to export KML (the same with GPX):

KML: Save Failed
java.lang.Exception:
writeToFile: Open Connector:
java.lang.illegalArgumentException: Illegal file connection name!

So all I can say is that it doesn't seem to have anything to do with the
read/write-permissions. Instead I suppose it has something to do with the 
default
path (see Issue 116) - at least on the Motorola A1200.

Original comment by ghost68w...@gmail.com on 16 May 2010 at 11:17

GoogleCodeExporter commented 9 years ago
original problem is a duplication of issue 116. Comment 1 describes another 
problem which has a relation to issue 116. That might worth a separate issue.

Original comment by javapis...@gmail.com on 23 May 2011 at 1:20