KelvinAng95 / osmbonuspack

Automatically exported from code.google.com/p/osmbonuspack
0 stars 0 forks source link

Test on android mobile device #2

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using?

Please provide any additional information below.

I can calculate pedestrian route by using mapquest roadmanager on emulator now 
(figure1).But when I test my application on my mobile phone (HTC Desire S), 
route is passing only start and destination point (see problem1.jpg). what is 
your opinion,what the problem is. Did you test this application on any android 
mobile device? Thank you for your interest again.

Original issue reported on code.google.com by hzse...@gmail.com on 23 Jun 2012 at 11:19

Attachments:

GoogleCodeExporter commented 8 years ago
I've not tested on a real device for a while. I will test on Monday. 
In the meantime: 

- Are you sure you had your Internet connection working on the phone, when 
trying to get the route?

- Have you tried to connect your device to Eclipse, to look at the logcat 
traces?

Original comment by mathieu....@gmail.com on 23 Jun 2012 at 9:57

GoogleCodeExporter commented 8 years ago
I am sure I had internet connection on my mobile device. Yes, I tried to 
connect my device to Eclipse, but the result is same. Thank you for your 
interest again.

Original comment by hzse...@gmail.com on 24 Jun 2012 at 10:04

GoogleCodeExporter commented 8 years ago
when I use OSRM road manager, there is no problem. But when I use Mapquest road 
manager, it can not get route on mobile device. I want to use mapquest because 
OSRM does not support pedestrian route.Best regards

Original comment by hzse...@gmail.com on 24 Jun 2012 at 12:15

GoogleCodeExporter commented 8 years ago
I tested with MapQuest manager on an HTC: it was working fine... 
Could you connect your device to Eclipse and get the logcat logs? 

Original comment by mathieu....@gmail.com on 25 Jun 2012 at 2:11

GoogleCodeExporter commented 8 years ago
I get logcat logs. The related parts of the log are attached. The first one is 
emulator log file, the second one is HTC log file.

Original comment by hzse...@gmail.com on 26 Jun 2012 at 8:03

Attachments:

GoogleCodeExporter commented 8 years ago
I think the problem is related with Global References (GREF). I think GREF has 
increased to 201 on emulator but it has not increased on HTC device. But I 
don't know what the solution is. All part of the log files are attached. The 
first one is emulator log file, the second one is HTC log file.

Original comment by hzse...@gmail.com on 26 Jun 2012 at 9:06

Attachments:

GoogleCodeExporter commented 8 years ago
I download osmbonuspackdemo.apk from download page and tested it with my mobile 
device. I get we have a problem to get route error message too.

Original comment by hzse...@gmail.com on 26 Jun 2012 at 3:31

GoogleCodeExporter commented 8 years ago
Okay. 
In the HTC logs, the url request to MapQuest is traced: 
06-26 11:22:51.304: DEBUG/BONUSPACK(3446): 
MapQuestRoadManager.getRoute:http://open.mapquestapi.com/guidance/v0/route?from=
38.026796,32.511634&to=38.02256,32.51332&outFormat=xml&shapeFormat=cmp&narrative
Type=text&locale=en_AT&unit=k&fishbone=false&routeType=pedestrian

By Copy/pasting this url in a browser we can see the MapQuest answer, and 
understand the issue: "<message>Invalid value 'en_AT' for parameter 
'locale'</message>"

MapQuest doesn't support Austria country... In fact, they support few locales, 
and it's not documented at all. Real issue. 

In the short term, until finding a better solution, I will remove the setting 
of the "locale" option from getRoad, and let the caller handle it (or not) 
using addRequestOption("locale=..."). 

In the meantime, you can change your locale to English-US (or 
Deutsch-Deutschland). 

Original comment by mathieu....@gmail.com on 26 Jun 2012 at 8:42

GoogleCodeExporter commented 8 years ago
Yes, you are right. It is fixed. Thank you for your supports.

Original comment by hzse...@gmail.com on 27 Jun 2012 at 7:00

GoogleCodeExporter commented 8 years ago
Fixed in v1.4 (no locale set by default for MapQuestRoadManager)

Original comment by mathieu....@gmail.com on 28 Jun 2012 at 9:29