--- Log opened Sun Mar 30 00:00:01 2014 00:36 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 00:36 -!- mode/#navit [+o KaZeR] by ChanServ 00:41 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 01:15 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 01:15 -!- mode/#navit [+o KaZeR] by ChanServ 01:17 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/wince_arm/svn/navit-svn-5761.failed 01:17 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 01:34 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 02:45 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 02:45 -!- mode/#navit [+o KaZeR] by ChanServ 02:49 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 03:26 -!- drlizau [~liz@billiau.net] has joined #navit 03:45 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 03:45 -!- mode/#navit [+o KaZeR] by ChanServ 03:51 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 264 seconds] 04:46 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 04:46 -!- mode/#navit [+o KaZeR] by ChanServ 04:51 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 05:25 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has joined #navit 05:46 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 05:46 -!- mode/#navit [+o KaZeR] by ChanServ 05:52 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 265 seconds] 06:47 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 06:47 -!- mode/#navit [+o KaZeR] by ChanServ 06:52 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 265 seconds] 07:07 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has joined #navit 07:47 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 07:47 -!- mode/#navit [+o KaZeR] by ChanServ 07:53 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 264 seconds] 08:02 -!- Usul1 [~matthias@erina.opennet-initiative.de] has joined #navit 08:09 -!- Usul1 [~matthias@erina.opennet-initiative.de] has quit [Quit: Leaving.] 08:16 #navit: < _rd_> Is there a reason why we have no armv7 builds? 08:17 #navit: < _rd_> Current Android hardware seems to be armv7....or is it just not worth the effort to make it faster? 08:31 #navit: < xenos1984> maybe just nobody has set up an armv7 build / toolchain yet 08:32 #navit: < xenos1984> i wonder which arm type the raspberry pi has... 08:48 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 08:48 -!- mode/#navit [+o KaZeR] by ChanServ 08:54 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 264 seconds] 09:14 #navit: < _rd_> I think raspberry pi is armv6: https://en.wikipedia.org/wiki/Raspberry_Pi 09:14 #navit: < _rd_> The Android build feels terribly slow compared to running on the n900.... 09:15 #navit: < _rd_> ...I have to admit though that the n900 did not have Full HD resolution. 09:16 #navit: < _rd_> Terribly slow means in particular when scrolling maps. 09:16 #navit: < _rd_> Since it is the first thing users do, Android users will be scared away. 09:16 #navit: < _rd_> Did anybody seen that before or has even somebody investigated that before? 09:32 -!- tryagain [~tryagain@178.216.76.18] has joined #navit 09:49 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 09:49 -!- mode/#navit [+o KaZeR] by ChanServ 09:54 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 10:01 #navit: < tryagain> Is there anybody who can test if navit's "Marco Polo Großer Reiseplaner" map plugin is working fine? 10:02 #navit: < tryagain> I plan to do a core change which will affect mg map driver but can't test is as i have no map data. 10:04 #navit: * xenos1984 has never used android or mg maps 10:04 #navit: < xenos1984> indeed, the raspberry pi is armv6 10:05 #navit: < xenos1984> and its quite powerful, also longer routes (like 300km) are calculated quickly even in "car pedantic" mode when lots of smaller roads are involved 10:09 #navit: < tryagain> xenos1984 there is a report of bad search peroformance on WinCE (also some arm favour) http://trac.navit-project.org/ticket/1109. Can you verify if it reproduces it on pi? 10:10 #navit: < xenos1984> tryagain: i have not checked with a russian map, but with an estonian one it works quite quickly also in larger cities such as tallinn 10:11 #navit: < xenos1984> i can try some other maps, too 10:14 #navit: < tryagain> would be great. Search in Cyrillic domain is more processor intensive, so it may make a difference. 10:16 #navit: < xenos1984> yes, i would also guess so 10:18 #navit: < xenos1984> interesting - looks like there is no predefined map of russia on the navit map servers 10:19 #navit: < xenos1984> maybe there is no common agreement which parts of the world belong to russia and which don't ;) 10:21 -!- drlizau [~liz@billiau.net] has quit [Quit: Leaving] 10:24 #navit: < tryagain> if you draw a rectangle around whole Russia, you'll get much more than currently is disputed ;) 10:25 #navit: < xenos1984> indeed ;) it's downloading now, but it says the download will take 9 hours for 1,6GB... 10:26 #navit: < xenos1984> download rate around 50k, is that normal? 10:27 #navit: < tryagain> you may try with different servers. Or just download the area described in the ticket. 10:29 #navit: < tryagain> http://maps9.navit-project.org/api/map/?bbox=59.5,53.9,63.7,56.1×tamp=140328 10:30 #navit: < tryagain> the town in question is spelled as Челябинск 10:30 #navit: < tryagain> street to test with is Победы 10:31 #navit: < xenos1984> ok, i'll try that 10:32 #navit: < xenos1984> maps9 is a lot faster than maps5 10:34 #navit: < xenos1984> takes about 1-2 seconds 10:35 #navit: * tryagain can't comment on this 10:36 #navit: < xenos1984> street search, that is - in cyrillic letters it's a tiny bit slower than in latin letters, but it does not takes nearly as long as in the tickets 10:37 #navit: < xenos1984> is it possible that this also depends on the map size? the map i used now has 90MB, but with a 1,6GB map of all of russia it could take longer 10:39 #navit: * xenos1984 is downloaing the large map from maps9 now to test that one, too - takes 10 min now to download 10:41 #navit: < tryagain> i do not expect big difference with lager map, but verifying it is a good idea of course. 10:49 #navit: < xenos1984> maybe 2 seconds now 10:49 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 10:49 -!- mode/#navit [+o KaZeR] by ChanServ 10:55 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 265 seconds] 11:34 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 11:35 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has joined #navit 11:50 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 11:50 -!- mode/#navit [+o KaZeR] by ChanServ 11:55 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 264 seconds] 12:48 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 12:50 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 12:50 -!- mode/#navit [+o KaZeR] by ChanServ 12:56 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 13:51 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 13:51 -!- mode/#navit [+o KaZeR] by ChanServ 13:56 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 14:52 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 14:52 -!- mode/#navit [+o KaZeR] by ChanServ 14:57 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 15:52 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 15:52 -!- mode/#navit [+o KaZeR] by ChanServ 15:58 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 264 seconds] 16:05 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 16:05 -!- mode/#navit [+o KaZeR] by ChanServ 16:06 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 16:08 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 16:08 -!- mode/#navit [+o KaZeR] by ChanServ 17:07 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 265 seconds] 18:03 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has joined #navit 18:36 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds] 19:11 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has joined #navit 20:25 #navit: < _rd_> xenos1984: there is no issue on Android for calculating routes, there is an issue when it comes to map presentation on the screen. 20:26 #navit: < _rd_> When moving the map or changing zoom level, for quite some time nothing (!) happens, and then eventually the map gets updated. 20:28 #navit: < _rd_> That update is ways too slow though....if the map would move and the "new" areas (not seen bevore moving) would appear after a while, that would probably be ok. But just freezing the screen is really poor user experience....and everybody will notice that right away. 20:28 #navit: < _rd_> Note that is on a high-end smartphone like the S4. 20:32 -!- drlizau [~liz@billiau.net] has joined #navit 20:33 #navit: < _rd_> I will dig somewhat into osmand, they seem to have a decent UI on Android, but I am not sure how much configurability they offer. 20:42 #navit: < tryagain> _rd_ is it related so some specific map region, zoom level, or navit version? Or appears at any attempt to zoom/move the map? 20:49 #navit: < _rd_> tryagain: for me it appears on any navit version I tested (installed 5761 today). 20:49 #navit: < _rd_> My impression is the more is on the map the slower everything becomes. 20:50 #navit: < _rd_> E.g. in a city and zoomed out it becomes much worse than in a forest with a zommed in a lot. 20:52 #navit: < _rd_> Certainly it also depends somewhat on the map settings....maps which show fewer pois/paths are faster than maps which show more information. 20:53 #navit: < _rd_> I used essentially the same map settings as on the n900, and the n900 is a lot faster....and the n900 is 3-4 years older than the S4. 20:53 #navit: < xenos1984> could it be a graphics driver issue? i guess there is an own navit graphics driver for android 20:53 #navit: < tryagain> yes, graphics for android is own 20:54 #navit: < _rd_> Hmm....I see in my navit.xml: that's not graphics, that's gui 20:55 #navit: < _rd_> ok 20:58 #navit: < _rd_> Is there any chance to get the android graphics driver profiled? There may be heavy bottlenecks in there given that navit runs on the Raspberry Pi type devices. 21:01 #navit: < tryagain> hm... Quickly looking at the code, it seems that we pass to java layer each graphics primitive one by one, instead of passing the whole bunch at once. Changing that may give some performance benefit. 21:01 #navit: < tryagain> though changing the way it works is not as easy as i would like :) 21:17 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection] 21:20 -!- _rd_ [~rd@p57B4931D.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 21:21 #navit: < xenos1984> i guess this also applies to other graphics drivers, but there drawing of a single primitive may be faster than on android 21:23 #navit: < xenos1984> but for example, if i run navit on the raspberry pi, display the output through an x11 tunnel via ssh and have high rendering effort (route graph overlay, many pois etc) it also gets a bit slower 21:23 #navit: < xenos1984> but on the attached display it works nicely 21:24 #navit: < tryagain> on android, drawing a primitive is done through java function call from our c code. That java call probably costs too much for us. 21:25 #navit: < tryagain> if we would pass more than one primitive per java call, it could perform better 21:25 #navit: < xenos1984> yes, i guess so (similar to drawing a primitive through an x11 tunnel) 21:26 #navit: < xenos1984> i guess it would be better to either bundle graphics primitives, or have something like a software framebuffer for drawing, which can then be passed as a whole when the drawing is done 21:26 #navit: < tryagain> and problem arises only when i use "car" layout on android. With default "android" layout performance seems to be good. 21:27 #navit: < xenos1984> hm... is the android layout more slim / less pois? 21:27 #navit: < tryagain> yes, android layout quickly strips detail level as you zoom out 21:27 #navit: < xenos1984> ah, i see 21:30 #navit: < tryagain> For me, car layout in Berlin takes 5 seconds to render a "fast after move" screen (without details around previusly rendered area) and another 5 seconds to display final screen. 21:31 #navit: < xenos1984> hm... quite a lot 21:31 #navit: < xenos1984> good night 21:34 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has quit [Remote host closed the connection] 22:06 -!- tryagain [~tryagain@178.216.76.18] has quit [Remote host closed the connection] --- Log closed Mon Mar 31 00:00:01 2014