--- Log opened Thu Jun 07 00:00:42 2012 01:53 -!- sera_ [~sera@gentoo/developer/sera] has joined #navit 01:57 -!- sera [~sera@gentoo/developer/sera] has quit [Ping timeout: 260 seconds] 04:03 -!- noradtux|away [~noradtux@2002:5ce0:3d61::1] has quit [Ping timeout: 260 seconds] 04:08 -!- noradtux|away [~noradtux@2002:5ce0:3ad5::1] has joined #navit 04:08 -!- noradtux|away is now known as noradtux 08:18 -!- test [4ebd6abb@gateway/web/freenode/ip.78.189.106.187] has joined #navit 08:19 -!- test [4ebd6abb@gateway/web/freenode/ip.78.189.106.187] has left #navit [] 08:41 -!- pini [~pini@bou-fi.pustule.org] has quit [Read error: Operation timed out] 08:47 -!- pini [~pini@bou-fi.pustule.org] has joined #navit 09:15 -!- sera_ is now known as sera 09:44 -!- fOB [~fob@ip-178-202-247-64.unitymediagroup.de] has joined #navit 09:59 -!- drlizau [~liz@billiau.net] has joined #navit 10:02 -!- zoff99 [~chatzilla@84.114.125.186] has joined #navit 10:24 -!- zoff99 [~chatzilla@84.114.125.186] has quit [Quit: ChatZilla 0.9.86-rdmsoft [XULRunner 1.9.1/20090707221522]] 11:42 -!- rifl [bc168f2a@gateway/web/freenode/ip.188.22.143.42] has joined #navit 11:42 < rifl> hello @everybody 11:45 < rifl> i designed a osd layout for android (http://wiki.navit-project.org/index.php/OSD_Layouts) - the last one. But i'm not really lucky with the performance from navit on android (samsung galaxy nexus) 11:46 < rifl> What is important for the performance? OSD Elements? Map Size? What can i do to improve it (for example displaying the whole route from innsbruck to vienna (about 500 km) takes me 20sec) 12:03 -!- efess [~Efess@ool-18bfe031.dyn.optonline.net] has quit [Ping timeout: 260 seconds] 12:07 -!- tryagain [529762b6@gateway/web/freenode/ip.82.151.98.182] has joined #navit 12:07 < tryagain> rifl Do you have much slower performance with your layout than with the default one? 12:09 < tryagain> And what do you mean by "displaying the whole route from innsbruck to vienna (about 500 km) takes me 20sec" Is it the time needed to calculate route or to display it when you zoom out to display the whotle already calculated route? 12:10 < tryagain> Btw we have still unclosed bug which says that routes more 80km are not calculated by navit ;) 12:10 < tryagain> http://trac.navit-project.org/ticket/456 12:11 < rifl> one moment 12:12 < rifl> hi tryagain, so, it takes my 20 sec to display the calculated route when i zoom out 12:12 < tryagain> I'd say it to be good timing - 20 sec to calculate whole routeof 500km in quite dense OSM area. 12:12 < tryagain> hm 12:12 < rifl> the routing takes not such a long time (i think about 5-10 sec) 12:12 < tryagain> did you made some changes to ? 12:13 < rifl> i think we chatted some weeks ago 12:13 < rifl> do you remember my layout? 12:13 < rifl> http://0606.at/index.php?option=com_content&view=article&id=115:samsung-galaxy-nexus-navit-layoutosd&catid=53:android&Itemid=57 12:14 < rifl> this changes i made. Maybe i try a simple layout, but do you think the performance of viewing the map depends on the layout? 12:17 < tryagain> it defenitely depends on layout. Default "android" layout for me is much faster than 12:17 < tryagain> ... default "car" one. 12:18 < rifl> hm okay 12:18 < rifl> maybe i try this 12:18 < rifl> i liked it because the default layout looks hm... "creapy" ^^ 12:18 < tryagain> Its done so to have better performance... 12:19 < rifl> hm. I posted the layout for public and nobody complained that it is slow, thought it is only my problem ^^ 12:20 < rifl> but i can try to deactivate the whole layout except zoom out and in, then i will see what's happening 12:20 < rifl> :-) 12:20 < rifl> do you know if there is a possibility to make routing points? 12:21 < rifl> z.B. create a route form innsbruck via munic to vienna? 12:21 < tryagain> There's "Plan with waypoints" option somewhere in settings. 12:22 < tryagain> It also can be switched in xml to have it enabled on startup. 12:22 < rifl> ah great, didn't knew that 12:22 < tryagain> Don't remember exact attribute name though. 12:23 < tryagain> Thats quite a new feature, added couple month ago. 12:23 < rifl> and for avoiding ferrys and so on i guess it's needed to creat a own profile 12:23 < tryagain> Yes, own vehicle profile. 12:29 < rifl> which layout do you use? 12:32 < rifl> there is another problem 12:32 < rifl> when i zoom out quite far 12:32 < rifl> and want to move the map 12:33 < rifl> it do not moves (because it's so slow?) and shows the meneu instead 12:33 < tryagain> well, I dont use navit very much. My usual travels don't require routing, so it's usually disabled. So default osd layout is enough for me. I switch to "Car" map layout when I want to see more lovely picture when I zoom out. 12:34 < tryagain> Yes, described effect is likely because of slow rendering. 12:35 < tryagain> You have to wait for rendering end before scrolling furter if you removed your finger from the screen. 12:37 < rifl> is there a possibility to improve the rendering? 12:38 < rifl> navit is simply not usable if there are displayed distances of more than 100km on the screen 12:38 < tryagain> I think its possible only by reducing number of objects displayed. 12:42 < tryagain> I've been trying to analyse perfomance on WinCE device (800MHz CPU) and it seems that we hit two bottlenecks on lower zoom levels at once: graphics performance and disk IO performance. 12:43 < tryagain> disk IO performance is probably combined with CPU resources needed to unzip tiles from the zipped binfile map 12:46 < rifl> hm. okay 12:46 < rifl> i thougt i already display not much things 12:47 < rifl> reducing the displayed elements is possible via the zoomlevel configuration? 12:47 < rifl> 12:47 < rifl> <-- the "order" attribute? 12:48 < curious> hello. was in dresden yesterday and i can say navit was complete failure 12:49 < curious> 1) it did crashed in city center even at zoom levels like 20 12:49 < curious> (device has 64M of ram) 12:49 < curious> 2)dunno why autobahns were not visible 12:50 < curious> 3)routing on distances over 90km - failure. epic. 12:50 < curious> i.e. it does not even try to route 12:50 < curious> may i know wtf happened? i used pretty recent build 12:52 < curious> either way compared with cheapest navigation program running on 400mhz cpu and 32M device it was just looking disasterous 12:57 < rifl> hm 12:57 < rifl> no i don't know 12:57 < rifl> routing over 500km is no problem with my device 12:58 < rifl> but i do not have the last build jet 12:58 < curious> yeah, i used previous builds and i did longer routes quite fine 12:58 < rifl> what is zoom level 20? 12:58 < rifl> rather close or rather far? 12:59 < curious> also been with them in prague and it did not crash _just displaying the map_(i.e. not even routing!) 12:59 < curious> close 12:59 < rifl> ah okay. No, that shouldn't be a problem 12:59 < curious> ~100-200m on the 'scale' 12:59 < curious> yeah, i know, that's why i came to ask wtf 12:59 < rifl> I'll try the newest build today 13:00 < rifl> maybe i can figure out something 13:00 < curious> now i have little time to dig this thing , i'll prolly return to it next week 13:01 < curious> gtg, and thx for attention :) 13:01 < rifl> no prob :-) 13:01 < rifl> till next time 13:17 < rifl> there is still the question how to get the center coordinates from the map :-( 13:22 < tryagain> just click it and see in the internal gui 13:23 < rifl> yes 13:23 < rifl> i know 13:23 < rifl> thats the problem 13:23 < rifl> i want to disable click on map 13:23 < rifl> (beauce on touch screen devices you often click the map even if you don't want ;-) ) 13:24 < rifl> therefore i want to disable it. If i do so, of course i'm only able to get the menue by clicking a buttton 13:25 < rifl> but if i click the button, i do not get the coordinates in the Menue :-( 13:25 < tryagain> post a ticket on trac, somebody will sometime implement it. Or attach your own patch, if you can program. 13:25 < rifl> so i wanted the earth symbol in the menue to show always the center coordinates form the screen 13:25 < rifl> but i do not know how to achive this 13:25 < tryagain> ^^^ post a ticket on trac ^^^ 13:26 < rifl> :D 13:26 < rifl> where i can do that? 13:26 < tryagain> http://trac.navit-project.org 13:27 < rifl> http://trac.navit-project.org/ticket/653 13:27 < rifl> just found it :-) 13:27 < rifl> thanks 13:27 < rifl> and. you are right. without osd elements it is much faster. 13:27 < rifl> The question is, which osd elements are slowing down the system and which doesn't 13:28 < tryagain> then I'm wrong, I was tinking the map items displayed are slowdown cause 13:29 < tryagain> You have about 10-20 osd elements to test. Try disabling them one-by-one, or, better, by groups. 13:30 < rifl> maybe they do that as well, but i disabled the whole osd 13:30 < rifl> and it works much more better 13:30 < rifl> my osd is quite complex (two osd layouts, one for landscape, one for portrait 13:31 < rifl> maybe this causes the slow reaction ;-) 13:31 < rifl> and then many auto update osd elements 13:31 < rifl> (routing status, gps status ...) 13:35 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection] 13:59 -!- efess [~Efess@ool-18bfe031.dyn.optonline.net] has joined #navit 14:20 < Celelibi> is the svn HEAD revision usable? 14:20 < Celelibi> is it supposed to be usable? 14:21 < tryagain> if you have different opinion, prove it ;) 14:24 < Celelibi> Is compiles, but do not add any vehicle. 14:24 < Celelibi> I can see the map and stuff, but cannot set my current position. 14:24 < Celelibi> Is compiles <-- It* 14:25 < Celelibi> Program received signal SIGSEGV, Segmentation fault. 14:25 < Celelibi> 0x000000000044fd63 in route_find_nearest_street (vehicleprofile=0x0, ms=0x74c880, pc=0x106be00) at /home/sgault/code/navit/navit/navit/route.c:2866 14:25 < Celelibi> 2866 (sd->flags & vehicleprofile->flags_forward_mask) == vehicleprofile->flags || 14:29 < tryagain> well we have to check for NULL vehicleprofile somewhere earlier. Why do you not have any vehicle? Do you have a GPS receiver? If not, you may use a demo:// one 14:29 < Celelibi> I don't have a GPS receiver yet. I have vehicle in navit.xml 14:30 < Celelibi> actually this part work well with the revision in debian package. 14:30 < Celelibi> But the svn revision do not add any vehicle. 14:31 < Celelibi> I run it with ./navit ~/path/to/navit.xml 14:31 < Celelibi> is it right? 14:56 -!- korrosa [c30285b6@gateway/web/freenode/ip.195.2.133.182] has joined #navit 14:57 < korrosa> rifl: Read your convo with tryagain with interest. 14:57 < korrosa> I made this layout for my netbook: http://wiki.navit-project.org/index.php/OSD_Layouts#Netbook_Layout_2 14:57 < korrosa> I then tried using it on my Android device and it was indeed quite slow. 14:58 < korrosa> I know just use a modified version of this: http://wiki.navit-project.org/index.php/OSD_Layouts#An_other_android_layout_800x480 14:59 < korrosa> The thing that slowed my netbook layout down was the constant call for icon updates, for example for routing status, 2D/3D status and sound status. 14:59 < korrosa> I also find, though, that if there are a lot of POI icons being displayed, that this also slows down rendering. 15:00 < korrosa> Navit's default Android layout has most of the POIs switched off, and you can switch it back on from the Android menu button. 15:00 < korrosa> (My device is a Galaxy SII) 15:05 < Celelibi> What are POI? 15:09 < kenguest> Points of Interest 15:09 < kenguest> occasionally translated as interesting points ;) 15:18 -!- zoff99 [~chatzilla@84.114.125.186] has joined #navit 15:18 < tryagain> Celelibi It depends. You must have navit plugins located in place that navit will find. Best way to try running a-just-compiled version of navit is start it from the build path. 15:19 < tryagain> Overise, it should be installed system-wide, with plugins placed where they were configured to be. 15:23 < tryagain> hm. But it would not have a GUI without plugins. So that's not the case. 15:24 < Celelibi> How do I know which navit.xml it's using? 15:24 < tryagain> Most probably, you have built navit without gps support. 15:25 < Celelibi> possibly. 15:25 < Celelibi> And I think I did. 15:25 < tryagain> If you specify it on command line, it should use that one 15:25 < Celelibi> May that be the cause of no vehicle beeing added? 15:26 < tryagain> Definitely. If you have no gps vehicle module and no other vehicle configured in navit.xml, you will not have a vehicle. 15:27 < tryagain> Try using demo vehicle. 15:27 < tryagain> source="demo://" 15:27 < tryagain> hm or data="demo://" ? :-/ 15:27 < tryagain> something like that 15:28 < tryagain> have 2 go now. Till later! 15:28 -!- tryagain [529762b6@gateway/web/freenode/ip.82.151.98.182] has quit [Quit: Page closed] 15:28 < Celelibi> Ok 15:32 < rifl> korrosa: i recogniced the same behaviour as you said. Removed the icon update and the performance is now much better. i'll try to remvove 15:33 < rifl> all unneeded parts of the layout. Routing information is fine, but not useful if the application slows down 15:33 < rifl> btw, i have nearly the same phone, Galaxy Nexus 15:36 < korrosa> Yeah. Another thing which used to slow down Navit even on my netbook was the speed camera OSD, but I think this has been fixed. 15:37 -!- playya [~playya@unaffiliated/playya] has joined #navit 15:39 < rifl> ah okay? 15:39 < rifl> havn't active the speed cam jet 15:40 < rifl> well, will have a look at it afterwards, the sun is shining ;-) 15:40 < rifl> till later :-) 16:00 < Celelibi> Hey, I tried vehicle Demo and it doesn't "say" anything. 16:00 < Celelibi> I have in the terminal lines like: speech_cmdline:speechd_say:text 'maintenant, tournez à droite ' 16:01 < Celelibi> and 'Fix the speech tag in navit.xml to let navit say:' 'Suivez la route sur 900 mètres' 16:05 < korrosa> Celelibi: http://wiki.navit-project.org/index.php/Configuring_Navit/Full_list_of_options and ctrl+f for "speech" 17:13 -!- korrosa [c30285b6@gateway/web/freenode/ip.195.2.133.182] has quit [Quit: Page closed] 17:24 -!- ScriptFanix [vincent@Hanaman.riquer.fr] has quit [Quit: Hard drive replacement] 17:51 -!- fOB [~fob@ip-178-202-247-64.unitymediagroup.de] has quit [Quit: Leaving] 18:15 < Celelibi> Is it possible to make the map follow the car "smoothly"? 18:16 < Celelibi> I mean, not by having "steps" every time the car goes out of the displayed area. 18:16 < Celelibi> Especially for the 3D view. 18:18 < Celelibi> Maybe it would take to much CPU? 18:18 < Celelibi> But if it's an option, I could enable it only of I run it on a powerful machine. 18:45 -!- nick___ [48b623f1@gateway/web/freenode/ip.72.182.35.241] has joined #navit 19:06 -!- korrosa [~netbook@host-2-96-83-65.as13285.net] has joined #navit 19:07 < korrosa> Celelibi: No, that's not possible. The map will follow the vehicle (or vehicle follow the map, if that's the way it should be viewed) every GPS-update. Typically, this is once per second (i.e. 1Hz). 19:07 < korrosa> There is no code in Navit to predict the future and interpolate, unlike the TomToms! 19:09 < korrosa> Ha, actually, that last bit is a lie: see the "lag" attribute in the Full List of Options wiki page. 19:13 < Celelibi> That's not what I mean. 19:14 < Celelibi> Currently the map is displayed and the blue triangle goes from the bottom to the top of the screen. When it reach the top, an new portion of the map is displayed and the cursor is now at the bottom of the screen. 19:14 < korrosa> Oh, yeah, that is definitely changeable. 19:14 < Celelibi> What I which is to have the blue triangle not to move on the screen. 19:14 < korrosa> Look for the "follow" attribute 19:15 < korrosa> Inside your tag, set follow="1" 19:15 < Celelibi> Yes I see. 19:16 < Celelibi> Let's try out. 19:19 < Celelibi> nice 19:20 < Celelibi> When the road is a bit messy it's not always easy to see which one is the right one. http://nsa30.casimages.com/img/2012/06/07/12060708332620719.png 19:21 -!- sleske [~sleske@p4FD45530.dip.t-dialin.net] has joined #navit 19:22 < Celelibi> The follow="1" attribute works fine except... For the first "screen". 19:22 < korrosa> Yep. I think the same thing - I made my own map layout which has the route on top of the roads: http://wiki.navit-project.org/index.php/Layout/mapnik 19:22 < Celelibi> The car has to reach the edge of the screen before the map follows the car. 19:22 < korrosa> Are you still using the demo car? 19:23 < korrosa> I think that behaviour is only for the demo car. It certainly follows me immediately. 19:23 < Celelibi> I use the demo car indeed. (I don't drive and chat at the same time. ;)) 19:24 < korrosa> Well, you never know!! 19:25 < sleske> korrosa: Hi! 19:25 < korrosa> Hi sleske! 19:26 < Celelibi> woah, navit is actually really customizable. 19:26 < korrosa> Welcome to Navit! 19:26 < Celelibi> I didn't thought I could customize the way the map is drawn. 19:29 < Celelibi> All this is really nice. 19:29 < Celelibi> Last blocking point is still the routing algorithm. 19:31 < Celelibi> For long roads (several hundreds of km) I can't avoid tolls. 19:33 < Celelibi> Is there an easy way to debug the blue areas leaking all over the map? 19:55 < nick___> Hi. I tried to install NavIt on an AT&T Fusion (HTC). Doesn't seem to ever find the compass or gps. Is this a known bug? 20:07 -!- nick___ [48b623f1@gateway/web/freenode/ip.72.182.35.241] has quit [Ping timeout: 245 seconds] 20:26 -!- korrosa [~netbook@host-2-96-83-65.as13285.net] has left #navit [] 20:41 -!- noradtux is now known as noradtux|away 20:46 -!- sleske [~sleske@p4FD45530.dip.t-dialin.net] has quit [Quit: leaving] 21:04 -!- drlizau [~liz@billiau.net] has joined #navit 21:18 -!- sera_ [~sera@gentoo/developer/sera] has joined #navit 21:19 -!- sera [~sera@gentoo/developer/sera] has quit [Ping timeout: 246 seconds] 21:37 -!- Dark_Ebola [~ebola@AToulouse-551-1-168-84.w109-222.abo.wanadoo.fr] has joined #navit 21:59 -!- Dark_Ebola [~ebola@AToulouse-551-1-168-84.w109-222.abo.wanadoo.fr] has quit [Quit: You're just jealous because the voices are talking to me] 22:07 < CIA-80> mdankov * r5137 /trunk/navit/navit/map/csv/quadtree.c: Fix:map_csv:Fix memleak. 22:10 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection] 22:24 < CIA-80> mdankov * r5138 /trunk/navit/navit/graphics.c: Fix:core:Two more leaks in graphics.c 22:28 -!- rifl [bc168f2a@gateway/web/freenode/ip.188.22.143.42] has quit [Quit: Page closed] 22:40 -!- zoff99 [~chatzilla@84.114.125.186] has quit [Quit: ChatZilla 0.9.86-rdmsoft [XULRunner 1.9.1/20090707221522]] --- Log closed Fri Jun 08 00:00:41 2012