--- Log opened Sat Mar 10 00:00:29 2018
00:09 -!- Horwitz [~mich1@p200300800E213300022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
00:22 -!- Horwitz [~mich1@p200300800E19BB00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:22 -!- mode/#navit [+o Horwitz] by ChanServ
00:23 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
01:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 264 seconds]
01:41 -!- j_f-f [~quassel@62.138.18.44] has joined #navit
02:22 -!- noradtux [~noradtux@134.101.203.188] has quit [Ping timeout: 252 seconds]
02:22 -!- noradtux [~noradtux@2a02:2028:607:3c01:10db:cab7:2c5a:3a3f] has joined #navit
03:35 -!- noradtux [~noradtux@2a02:2028:607:3c01:10db:cab7:2c5a:3a3f] has quit [Ping timeout: 252 seconds]
03:39 -!- noradtux [~noradtux@2a02:2028:81a:7101:10db:cab7:2c5a:3a3f] has joined #navit
04:57 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
04:57 -!- mode/#navit [+v xenos1984] by ChanServ
11:58 -!- ilovekiruna [~ilovekiru@p200300D10BE726AEF21FAFFFFE3C9502.dip0.t-ipconnect.de] has joined #navit
11:58 -!- mode/#navit [+v ilovekiruna] by ChanServ
12:22 #navit: <+ilovekiruna> hi all
12:23 #navit: <+jkoan> hi ilovekiruna
12:23 #navit: <+ilovekiruna> KaZeR, jkoan: Yesterday while driving, I had another idea for navit
12:23 #navit: <+ilovekiruna> how difficult would it be to switch to night mode when driving in a tunnel?
12:23 #navit: <+jkoan> not so much
12:23 #navit: <+ilovekiruna> :)
12:24 #navit: <+jkoan> i also head the idea to enable nightmode with a daylight sensor
12:24 #navit: <+ilovekiruna> also very nice idea :)
12:25 #navit: <+ilovekiruna> I also thought about that, but it has one downside
12:25 #navit: <+ilovekiruna> if you consider the map, u dont need an additional sensor
12:25 #navit: <+ilovekiruna> otherwise, it will be device-dependent
12:26 #navit: <+jkoan> yes, but i think we should support both :D
12:27 #navit: <+ilovekiruna> I dont mind both, ofc
12:28 #navit: <+ilovekiruna> and I would like if we could log to a file even on android, so difficult to recall problems after a long drive
12:28 #navit: <+jkoan> on android we would (always) have a daylight sensor
12:29 #navit: <+jkoan> yes, log is always important 
13:22 #navit: < Mineque> google maps works like that
13:22 #navit: < Mineque> with light sencors
14:04 #navit: <+jkoan> Mineque: i know, i noticed this behavior while driving to fosdem
14:06 #navit: < Mineque> what for log?
14:06 #navit: < Mineque> btw, tunnel will also work with light sensor. No need to check route type
14:07 #navit: <+jkoan> what do you mean, navit or google?
14:21 #navit: < Mineque> i mean that light sensor will detect lower light in tunnel
14:22 #navit: < Mineque> so if light sensor is present navit shoulnt check if in tunnel just follow sensor
16:51 -!- newby [ad4b8fda@gateway/web/freenode/ip.173.75.143.218] has joined #navit
16:53 #navit: < newby> Help Needed to install navit in raspberry pi
16:54 -!- newby [ad4b8fda@gateway/web/freenode/ip.173.75.143.218] has quit [Client Quit]
17:26 -!- ilovekiruna [~ilovekiru@p200300D10BE726AEF21FAFFFFE3C9502.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
17:26 -!- ilovekiruna [~ilovekiru@p200300D10BE726C8F21FAFFFFE3C9502.dip0.t-ipconnect.de] has joined #navit
17:26 -!- mode/#navit [+v ilovekiruna] by ChanServ
17:27 #navit: <@KaZeR> hi there
17:28 #navit: <@KaZeR> ilovekiruna: in my car since i have access to canbus i can actually switch the layout when my headlights are turned on or off (which is automatic)
18:03 #navit: <+jkoan> hi KaZeR
19:32 #navit: <@KaZeR> 'sup jkoan ?
19:33 #navit: <+jkoan> try to get a working linux kernel for tomtom 
19:33 #navit: <+jkoan> right now i dident got any working kernel in the last weeks...
19:36 #navit: <+jkoan> i would be so happy if i would have a uart debugging port :/ 
19:36 #navit: <+jkoan> i will give it a try to find it again ...
20:39 #navit: <@KaZeR> ha, i understand that frustration :)
20:47 -!- gernot_ [5dd4c5a3@gateway/web/freenode/ip.93.212.197.163] has joined #navit
20:47 #navit: < gernot_> hi
20:47 #navit: <+jkoan> hi gernot_
20:48 #navit: < gernot_>  jkoan: tried you the screen console configuration from opentom
20:48 #navit: <+jkoan> what?! i dont understand
20:50 #navit: < gernot_> If your opentom kernel e.g. freeze you can put the kernel messages onto the screen
20:50 #navit: < gernot_> there are a prdefined kernel config file which activate this aoutput
20:52 #navit: < gernot_> https://github.com/george-hopkins/opentom/blob/master/configs/kernel_config.console_minix
20:53 #navit: <+jkoan> i want to update the kernel from 2.6 to the last kernel and i dont get a working config. the kernel loads and after a time if freezes after the screen has a nearly random "image" on screen
20:55 #navit: < gernot_> i tried something with newer kernel, but had e big size problem. you have only 32 or 64 MB RAM. What is the zsize of your image? 
20:56 #navit: <@KaZeR> gernot_: did you save that config for the newer kernel?
20:58 #navit: < gernot_> no, i stopped with a non tested minimal kernel without specific TT things. The Image size was to big. I dont remember the exact site. 
20:59 #navit: <+jkoan> around 5MB i think
21:01 #navit: < gernot_> That is good if it include the modules. 
21:04 #navit: < gernot_> jkoan: checked you opentom.org at archive.org ?
21:05 #navit: <+jkoan> yes, i have, but i cant find the debug pin... only something like "neare the cpu"
21:06 #navit: < gernot_> hmmmm
21:09 #navit: < gernot_> just checked opentom....That all old devices...
21:10 #navit: <+jkoan> of cause they are "old" :D
21:16 #navit: < gernot_> I have no idea if you cant access the framebuffer
21:20 #navit: < gernot_> good night. I tell you if i have an idea.
21:20 #navit: <+jkoan> i know that the display is only handled over the frame buffer, so yes, it must be possible
21:20 #navit: <+jkoan> okay good night
21:21 #navit: < gernot_> yes, but it looks like the framebuffer memory or configuration is not initiated.
21:21 #navit: < gernot_> by
21:22 -!- gernot_ [5dd4c5a3@gateway/web/freenode/ip.93.212.197.163] has quit []
21:46 #navit: <+jkoan> KaZeR, gernot: I read this file again and noticed something the Barcelona has 20pins. My device don't really have the docking port itself but there is a curvy line of 20pins, probably this could be the Barcelona dock. Because the dock has the debug port in it. That would be nice
21:47 #navit: <+jkoan> https://events.ccc.de/congress/2005/fahrplan/attachments/569-Paper_HackingTomTomGo.pdf
21:57 #navit: <@KaZeR> jkoan: makes sense. your device only has the pads on the pcb, right?
21:57 #navit: <+jkoan> Yes, both
21:59 #navit: <+jkoan> I will try it again tomorrow
22:01 #navit: <+jkoan> And I need to remember, to check ttyS0 I will see if it is there :D today I tested with acm or something like this... Let's see tomorrow. Good night
22:44 #navit: <@KaZeR> ++
--- Log closed Sun Mar 11 00:00:30 2018