--- Log opened Tue Dec 27 00:00:40 2016
09:52 -!- Basilic [~Basilic@228-221-190-109.dsl.ovh.fr] has joined #navit
09:52 #navit: < Basilic> hello all
11:11 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
12:28 -!- Horwitz [~mich1@p200300800E6CC400022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds]
12:34 #navit: < kazer> hi there
12:34 #navit: < kazer>    
12:41 -!- Horwitz [~mich1@p200300800E4CDF00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
12:41 -!- mode/#navit [+o Horwitz] by ChanServ
13:33 -!- gernot_ [549684b1@gateway/web/freenode/ip.84.150.132.177] has joined #navit
13:33 #navit: < gernot_> hi
15:20 #navit: < kazer> hi gernot_
15:20 #navit: < gernot_> hi
15:22 #navit: < kazer> made some good progress on my carputer mark III last week, and was able to test it on the road over the week-end. Robertp did a great job finalizing the audio framework.
15:23 #navit: < gernot_> nice. Work it well?
15:24 #navit: < kazer> yeah, definitely. I am now using a raspi 2 instead of the nuc, it's really less bulky. Still have some work left, like the backup camera, but overall it worked really weel
15:24 #navit: < gernot_> In the new nabit-trunk i have sometime 2 "car" cursor
15:25 #navit: < gernot_> ever seen this?
15:25 #navit: < kazer> did you enable the demo vehicle maybe?
15:25 #navit: < kazer> you can enable multiple vehicles indeed, that's a feature :) it allows you to see your friends on the map for example
15:26 #navit: < gernot_> yes, raspi 2 is the best. I think better then pi3
15:27 #navit: < gernot_> yes, its in the configuration. But gps is active
15:27 #navit: < kazer> ah? why is 2 better than 3?
15:28 #navit: < gernot_> I think it has a better micro sd slot and  save some power  compared to 3
15:29 #navit: < gernot_> serial port is full working. On pi3 the well working baudrategenerator is used for BT
15:30 #navit: < gernot_> The Pi3 change the baudrate with the CPU clock
15:30 #navit: < gernot_> If you need BT or Wlan the PI3 is clear better...
15:33 #navit: < gernot_> ka: now its clear. I enabled demo, but leave gps also active. Thanks
15:33 #navit: < kazer> yeah, despite the power consumption. I actually need wlan in the car so i'll try the rpi3 too. I am currently using a ubec to power the pi 2 and it works better than a wall plug actually
15:33 #navit: < kazer> gernot_: np! we never implemented exclusion, because of the friends feature
15:35 #navit: < gernot_> I have a pi2 as server for 8 month. No problem
15:39 #navit: < gernot_> kazer: is your display bright enough?
15:42 #navit: < kazer> it's not great, but it was ok
15:42 #navit: < kazer> i will try to put a anti reflective layer on top of it though
15:43 #navit: < gernot_> I think about raspi, but like the bright display of the TT-XL
15:43 #navit: < gernot_> Its much better then TT-730 or the standatd raspi displays
15:44 #navit: < kazer> yeah this was my biggest concern. My previous build was using a lilliput screen, which was really bright and not glossy. The major annoyance with the rpi screen is that it's glossy
15:44 #navit: < gernot_> TT-XL is also glossy , real bright
15:45 #navit: < kazer> you don't have reflection problems with that screen?
15:46 #navit: < gernot_> No. there are more problems with much light in the  anti reflective layer TT-730
15:47 #navit: < gernot_> There is so much light that the display looks "white"
15:47 #navit: < kazer> mmm interesting
15:48 #navit: < gernot_> try it
15:49 #navit: < kazer> what do you mean try it? i don't have a tt-730 :)
15:50 #navit: < gernot_> use a notebook to compare the displays
15:51 #navit: < gernot_> you see the problem on any display
15:51 #navit: < kazer> ah ok. Oh, i just got the backlight brightness to work on the rpi touchscreen. sweet!
15:51 #navit: < kazer> now i can lower the brightness when switching to night mode
15:52 #navit: < gernot_> i use also osd buttons to switch the backlight
15:53 #navit: < gernot_> for me daylayout with dimmed  light looks better  then nightlayout
15:53 #navit: < kazer> ah thanks i'll have to try that
15:53 #navit: < kazer> are you using the default layout for day ?
15:54 #navit: < kazer> i am using this one that looks much better imo : https://github.com/pgrandin/navit-nuc-layout
15:54 #navit: < gernot_> yes, but with some changes  for powerless devices
15:56 #navit: < kazer> ok. is it available somewhere like on github?
15:58 #navit: < gernot_> no. but the initial files i changed are in opentom.
15:59 #navit: < gernot_> https://github.com/george-hopkins/opentom/tree/master/src/opentom_skel/share/navit
15:59 #navit: < gernot_> But this layout have a problem while scollinh the map
16:01 #navit: < gernot_> Every time the osd-cmdinterface run (1 per second) the display snap to the last location for short time.
16:02 #navit: < gernot_> so i removed the routing status text
16:15 #navit: < gernot_> kazer: https://github.com/gefin/opentom/tree/master/src/opentom_skel/share/navit
16:15 #navit: < kazer> thanks
16:15 #navit: < kazer> for the last location, have you tried the timeout setting?
16:16 #navit: < gernot_> I use a timeout, but this was a "screen redraw" problem
16:17 #navit: < kazer> do you mean that it jumps back to the last location, or that the refresh is slow?
16:18 #navit: < gernot_> any time the osd cmd interface run the screen is first redrawed like it was at begin of scrolling
16:18 #navit: < gernot_> after that the screen is drawd at the actual position
16:19 #navit: < kazer> would you be able to film that ?
16:20 #navit: < gernot_> I think the next days
16:20 #navit: < kazer> ok thanks. we can probably improve that, and actually seeing the problem would help
16:22 #navit: < gernot_> that would be good. I try to give the information.
16:24 #navit: < gernot_> there is an other interesting option to view the routing status in the "next turn" icon.
16:26 #navit: < gernot_> I see there is someone working on it, but it looks not ready yet
16:26 #navit: < kazer> do you have a link?
16:29 #navit: < gernot_> http://wiki.navit-project.org/index.php/OSD#navigation_status
16:30 #navit: < gernot_> It dont work like expected. (
16:31 #navit: < kazer> i am using something similar, so it should work. I'll have a look
16:31 #navit: < kazer> it does not work at all for you or it misbehaves?
16:32 #navit: < gernot_> e.g. no information "no route to target"
16:33 #navit: < gernot_> Also the integration in place og "next turn" dont work well with transparent icons
16:34 #navit: < gernot_> i would prefer a extended "next turn" function
16:35 #navit: < gernot_> i have to leave...
16:37 #navit: < kazer> ok let's resume later. Good night!
16:38 #navit: < gernot_> by
16:38 -!- gernot_ [549684b1@gateway/web/freenode/ip.84.150.132.177] has quit []
17:33 #navit: < kazer>  
18:32 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
19:10 -!- Horwitz [~mich1@p200300800E4CDF00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
19:23 -!- Horwitz [~mich1@p200300800E08B600022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
19:23 -!- mode/#navit [+o Horwitz] by ChanServ
19:43 -!- latouche_ [~Latouche@reverse-169.fdn.fr] has quit [Ping timeout: 260 seconds]
19:43 -!- latouche [~Latouche@reverse-169.fdn.fr] has joined #navit
--- Log closed Wed Dec 28 00:00:42 2016