--- Log opened Mon Apr 15 00:00:02 2019 00:46 -!- Horwitz [~mich1@p200300EC9BFE6E00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 00:59 -!- Horwitz [~mich1@p200300EC9BC34700022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:59 -!- mode/#navit [+o Horwitz] by ChanServ 04:02 -!- xenos1984 [~xenos1984@227-28-196-88.dyn.estpak.ee] has joined #navit 04:02 -!- mode/#navit [+v xenos1984] by ChanServ 05:51 #navit: <+Navit> @KaZeR wiki broken, no new account creation is possible. I don't have access to fox it. Could you please look into it? 06:37 #navit: <+Navit> Cleaned wiki again (now fully clean) 11:43 -!- ilovekiruna [~Patrick@iris-gw.iris.no] has joined #navit 11:43 -!- mode/#navit [+v ilovekiruna] by ChanServ 14:13 #navit: <+jkoan> hi @all 14:14 #navit: <+ilovekiruna> hi jkoan 14:14 #navit: <+ilovekiruna> what's up? 14:16 #navit: <+jkoan> not much, today i cleaned up the wiki and looked into trac 15:36 #navit: <+jkoan> And working on the Sdl2 graphic driver, circles already working 15:38 #navit: <+jkoan> ilovekiruna: what's up at your side? 15:46 #navit: <+ilovekiruna> am still mostly held up by my work 15:47 #navit: <+ilovekiruna> jkoan: do you have some scope that we could look at the device farm together? 15:47 #navit: <+ilovekiruna> or at least discuss it a bit? 15:51 #navit: <+jkoan> I already thought about it, but currently I haven't anything to present 15:55 -!- ilovekiruna [~Patrick@iris-gw.iris.no] has quit [Quit: Leaving.] 17:16 #navit: <+Navit> Hey jkoan 17:16 #navit: <+Navit> Hi mike 17:16 #navit: <+Navit> How are you 17:18 #navit: <+Navit> How did the exams go? 17:24 #navit: <+Navit> Everything good :) 18:25 #navit: <+Navit> SDL2 WIP 😄 18:25 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/567415329832042496/unknown.png 18:26 #navit: <+Navit> Exams are over? 18:27 #navit: <+Navit> Yep 18:27 #navit: <+Navit> Thats good 18:28 #navit: <+Navit> Can you help me now? :D 18:28 #navit: <+jkoan> whats the problem? 18:29 #navit: <+Navit> The gps 18:29 #navit: <+jkoan> ah i remember 18:29 #navit: <+Navit> It only has the map doesnt know where i am or moving or anything 18:29 #navit: <+jkoan> on tomtom? 18:30 #navit: <+Navit> Yes 18:31 #navit: <+jkoan> have you read this page? https://wiki.navit-project.org/index.php/TomTom 18:32 #navit: <+jkoan> and did you tryed to move the device out for at least 12mins? 18:33 #navit: <+Navit> Yes for like 2 hours 18:34 #navit: <+Navit> Where am i supposed to take it? 18:34 #navit: <+Navit> What vehicle is configured in navit xml? 18:36 #navit: <+Navit> I dont know 18:36 #navit: <+Navit> How to find out :D 18:37 #navit: <+Navit> Open navit.xml in a editor like notepad++ and search for vehicle 18:39 #navit: <+Navit> Gui_vehicle 18:39 -!- ilovekiruna [~Patrick@253.92-221-28.customer.lyse.net] has joined #navit 18:39 -!- mode/#navit [+v ilovekiruna] by ChanServ 18:40 #navit: <+Navit> No? 18:41 #navit: <+ilovekiruna> jkoan: I see two different approaches right now 18:42 #navit: <+ilovekiruna> either go with the openSTF and see how far it brings us 18:42 #navit: <+ilovekiruna> and maybe couple it with some orchestration with jenkins or similar 18:42 #navit: <+ilovekiruna> or look at the lava software package 18:44 #navit: <+ilovekiruna> http://lavasoftware.org/ 18:45 #navit: <+ilovekiruna> those are the things possible i see so far 18:48 #navit: <+jkoan> i also thought about something like magic Latern does by emulating a whole canon dslr camera: https://www.magiclantern.fm/forum/index.php?topic=20560 example: https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/478/artifact/qemu-eos/magiclantern-Nightly.2018Jul03.5D3113/mn.gif 18:49 #navit: <+jkoan> they use jenkins 18:52 #navit: <+jkoan> ah and qemu to emulate the camera 18:59 #navit: <+jkoan> if we manage if be obtain a full disk dump from all supported devices we only need to setup the hardware so it so similar enough to the real hardware so it boots, and then we should bne able to run it, i already tryed around 10-15mins with tomtom but had no success, since i need uboot bootloader to boot which i havent had by hand 19:05 -!- ilovekiruna [~Patrick@253.92-221-28.customer.lyse.net] has left #navit [] 19:05 -!- ilovekiruna [~Patrick@253.92-221-28.customer.lyse.net] has joined #navit 19:05 -!- mode/#navit [+v ilovekiruna] by ChanServ 19:06 #navit: <+ilovekiruna> what about the hardware part? 19:06 #navit: <+ilovekiruna> I would be concerned about touch, gps signal, etc. 19:07 #navit: <+jkoan> that would be the second path. first one could be emulated gps with emulated everything ;) 19:07 #navit: <+Navit> There are a lot of vehicles in the search 19:08 #navit: <+jkoan> one should have name and source and most important enabled=yes 19:11 #navit: <+ilovekiruna> jkoan: imho this would increase the level of complexity, one more thing that has the risk of not working 19:12 -!- ilovekiruna [~Patrick@253.92-221-28.customer.lyse.net] has quit [Read error: Connection reset by peer] 19:13 #navit: <+Navit> but real hardware needs additional hardware like a sd card switcher/emulator for tomtom and so on... 19:14 #navit: <+jkoan> yes mike, and the full line? 19:15 #navit: <+Navit> 19:16 #navit: <+jkoan> this should work... 19:16 #navit: <+jkoan> currently i dont have a idea why... 19:17 #navit: <+Navit> Is there an option in the menu that should tell my location? 19:19 #navit: <+jkoan> yes, on action there should appear a globe symbos with the coords under it 19:24 #navit: <+Navit> Yeah 19:24 #navit: <+Navit> That globs tells me some cords 19:25 #navit: <+Navit> 39°37'44"N 76°0'1"E 19:25 #navit: <+Navit> Then it should work 19:25 #navit: <+Navit> well 19:25 #navit: <+Navit> the issue is, that cord is in china. and im not 😄 19:26 #navit: <+Navit> Hmmmm 19:26 #navit: <+Navit> Probability because of the week overflow lately? 19:26 #navit: <+Navit> I will take the device on a long drive 19:27 #navit: <+Navit> Show it outside and tell it thats its not china XD 19:28 #navit: <+Navit> https://www.orolia.com/resources/blog/lisa-perdue/2018/gps-2019-week-rollover-what-you-need-know 19:28 #navit: <+Navit> Probably like this :/ 19:29 #navit: <+Navit> Haven't tested my tomtom since the overflow. It was like one week ago 19:30 #navit: <+Navit> I will give it another try 19:30 #navit: <+Navit> Okay 19:31 #navit: <+Navit> Btw 19:31 #navit: <+Navit> How to add games in it 😃 19:33 #navit: <+Navit> Never had looked into it and don't want to because the device only has 32mb of ram so not usable for much 19:55 #navit: <+Navit> @mike i did read a bit on the topic and the GPS week rollover should not affect the GPS position. It the device was powered on 12mins while being under clear sky and the issue still exists, that's really strange. Do you know if the position was right with the original firmware? 19:55 #navit: <+Navit> Yes it was fine 19:56 #navit: <+Navit> I remember last time when i copied the coords on google maps it gave me my exact location 20:09 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has joined #navit 20:09 -!- mode/#navit [+v ilovekiruna] by ChanServ 20:19 #navit: <+ilovekiruna> jkoan: if your concern is tomtom, I would guess lava would be the better choice 20:20 #navit: <+ilovekiruna> because this is exactly what linaro uses it for 20:20 #navit: <+ilovekiruna> but from my point of view, it lacks the possibility to manually test things on the devices 20:22 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has quit [Quit: Konversation terminated!] 20:24 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has joined #navit 20:24 -!- mode/#navit [+v ilovekiruna] by ChanServ 21:47 -!- xenos1984 [~xenos1984@227-28-196-88.dyn.estpak.ee] has quit [Quit: Leaving.] 22:13 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has quit [Quit: Konversation terminated!] --- Log closed Tue Apr 16 00:00:04 2019