--- Log opened Tue Jan 16 00:00:55 2018 00:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n 00:39 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed 00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 01:00 -!- Horwitz [~mich1@p200300800E029E00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 01:13 -!- Horwitz [~mich1@p200300800E035300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 01:13 -!- mode/#navit [+o Horwitz] by ChanServ 01:42 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 256 seconds] 01:44 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 02:02 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 255 seconds] 02:09 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 04:35 -!- jeremy_ [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has joined #navit 04:36 -!- jeremy_ is now known as Guest11761 04:39 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has quit [Ping timeout: 256 seconds] 06:11 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 06:11 -!- mode/#navit [+v xenos1984] by ChanServ 06:27 #navit: <+jkoan> Ilovekiruna normally you should make a new Branche from trunk line, and even better from navit trunk. This should work since you have the original navit repo under the name "navit" 06:27 #navit: <+jkoan> So it should be possible to do something like this : 06:28 #navit: <+jkoan> Git checkout navit/trunk 06:28 #navit: <+jkoan> Git update and so on 06:29 #navit: <+jkoan> Git checkout -b yournamedbranche or git branche yournamedbranche 06:31 #navit: <+jkoan> Probably your trunk is not clean so you get those problems. I don't know if this would be good but you can checkout navit trunk and force push it into your trunk. Then your repo has exactly the same commits than navit 07:41 #navit: <+ilovekiruna> jkoan: ok, will try that then 07:41 #navit: <+ilovekiruna> thx for the suggestion 07:50 #navit: <+jkoan> No problem 09:53 -!- noradtux [~noradtux@2a02:2028:521:5f01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 276 seconds] 09:57 -!- noradtux [~noradtux@2a02:2028:82c:d901:ec4:7aff:fe33:3dc1] has joined #navit 15:23 -!- teste_ [c9119ef6@gateway/web/freenode/ip.201.17.158.246] has joined #navit 15:24 -!- teste_ [c9119ef6@gateway/web/freenode/ip.201.17.158.246] has quit [Client Quit] 15:35 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:57 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:57 -!- mode/#navit [+v xenos1984] by ChanServ 16:43 #navit: <+jkoan> Hi @all 16:43 #navit: <+jkoan> O 16:44 #navit: <+jkoan> Ilovekiruna did it succeed? 17:44 #navit: <@KaZeR> hi there 17:45 #navit: <+jkoan> Hi Kazer 17:47 #navit: <@KaZeR> 'sup folks? 17:47 #navit: <+jkoan> Right now nothing 17:49 #navit: <+jkoan> And on your side? 17:54 #navit: <@KaZeR> not much. didn't have a lot of time for navit these last few days 17:54 #navit: <+jkoan> Me also :/ 18:00 -!- AVIC-MRZ02 [5f8e8f27@gateway/web/freenode/ip.95.142.143.39] has joined #navit 18:01 #navit: < AVIC-MRZ02> Hi there 18:01 #navit: <+jkoan> Hi AVIC-MRZ02 18:02 #navit: < AVIC-MRZ02> Hi jkoan 18:02 #navit: <@KaZeR> hi AVIC-MRZ02 18:02 #navit: < AVIC-MRZ02> Hi KaZeR 18:03 #navit: < AVIC-MRZ02> KaZeR: Did you find time to play with head-unit with WinCE 18:04 #navit: <@KaZeR> not since at least a week. i still haven't been able to run custom app on it 18:05 #navit: < AVIC-MRZ02> I'm hopeless about my head-unit (Pioneer). They work a lot on it to hide almost everything that I need :) 18:06 #navit: < AVIC-MRZ02> Cannot access registry, cannot access GPS receiver, cannot access start-up programs etc. 18:09 #navit: < AVIC-MRZ02> This week (and half of the next week) I'm very busy so it'll not be possible to continue to play with it. 18:10 #navit: < AVIC-MRZ02> I read a text about COM1 port connections of the head-unit. It is written there that, Pioneer uses COM1 for testing+debugging so it is accessible. 18:11 #navit: < AVIC-MRZ02> Means that, it is possible to connect another GPS receiver directly to these connections. 18:12 #navit: <@KaZeR> well for some of these stuff we can write some code to poll for the resources, like the com port 18:12 #navit: <+jkoan> Do you know which ports are available? 18:12 #navit: <@KaZeR> i think that the challenge with the registry will be that it's probably overwritten at boot 18:13 #navit: < AVIC-MRZ02> It is written that, it's original GPS antenna is connected to COM7 18:13 #navit: < AVIC-MRZ02> but in boot, it is locked by a DLL file 18:15 #navit: < AVIC-MRZ02> So COM7 is not accessible. But there is a connection on head-unit for COM1 18:18 #navit: < AVIC-MRZ02> KaZeR: May be it's overwritten in boot. But it's nonsense to try to hide everything like that. As a user, I already bought that unit, and if I want, it must be possible for me to change software on it. 18:23 #navit: <+jkoan> AVIC-MRZ02 I remember that there was a tool to detect the GPS port and frequency for wince, probably that could help. We will see. And if things will be overridden after a boot let's just rewrite it to the right value ;) 18:23 #navit: < AVIC-MRZ02> The other point is that, Audio-Video application on head-unit takes control after execution and don't let any app to run in front (z-order). When it's own navigation app is executed, lets it to run on top but any other application runs at the back of a splash screen (I think). 18:24 #navit: < AVIC-MRZ02> jkoan: I found a tool which finds the port of GPS receiver. This tool cannot find my head-unit's port. 18:26 #navit: <@KaZeR> AVIC-MRZ02: what do you mean locked by a dll ? 18:27 #navit: <@KaZeR> AVIC-MRZ02: oh i absolutely agree that you should be able to do what you want. but most manufacturers disagree with that.. 18:27 #navit: <@KaZeR> jkoan: exactly 18:27 #navit: <@KaZeR> AVIC-MRZ02: instead of replacing the navi.exe can you replace the av app ? 18:28 #navit: < AVIC-MRZ02> KaZeR: While I'm running file manager I did that, I'm running file manager instead of AV 18:29 #navit: <+jkoan> so while you have the file manager you could find the gs? 18:29 #navit: <+jkoan> *gps 18:30 #navit: < AVIC-MRZ02> After file manager, I executed navit.exe. If you remember, I managed to see the map but all other images were not there. 18:30 #navit: <+jkoan> yes, i know 18:31 #navit: <+jkoan> but what if you would start the gps port finding programm from file manager? probably then the dll could not block the port 18:32 #navit: < AVIC-MRZ02> jkoan: I did it. But in form it is written that DLL file is used in boot phase. 18:32 #navit: < AVIC-MRZ02> The name of the DLL file is :NPGPSENGINE.DLL 18:33 #navit: < AVIC-MRZ02> By the way, I couldn't find this dll file with file manager. May be it's hidden. 18:36 #navit: <@KaZeR> jkoan: don't you have a wince device somewhere too? 18:36 #navit: <+jkoan> yes, only need to search where, why? 18:36 #navit: <@KaZeR> AVIC-MRZ02: it would be interesting to find which program is loading that .dll 18:37 #navit: <@KaZeR> jkoan: to see if you can reproduce AVIC-MRZ02's issue with the images 18:37 #navit: <@KaZeR> i wonder if it's in the app packaging or a file path or a lib 18:38 #navit: < AVIC-MRZ02> How it will be possible to find which program is loading this .dll file? 18:39 #navit: <+jkoan> KaZeR: found it, what should i test? 18:39 #navit: < AVIC-MRZ02> And I think, head-unit must be Pioneer. Other manufacturers may have different DLLs. 18:41 #navit: <@KaZeR> AVIC-MRZ02: good question - we'll have to do some research. i haven't used windows based setup in years :) 18:41 #navit: <@KaZeR> jkoan: can you try https://4746-30791823-gh.circle-artifacts.com/0/root/project/wince/output/navit.cab ? 18:41 #navit: <+jkoan> KaZeR: normaly its good not to have any M$ shit 18:42 #navit: <@KaZeR> jkoan: makes life easier for you 18:42 #navit: <@KaZeR> jkoan: the .cab is from https://circleci.com/gh/navit-gps/navit/4746#artifacts/containers/0 18:42 #navit: <+jkoan> from the traffic branche? 18:43 #navit: <+jkoan> fail... our wince build is broken 18:43 #navit: <+jkoan> KaZeR: see https://circleci.com/gh/navit-gps/navit/4738#artifacts/containers/0 18:44 #navit: <@KaZeR> jkoan: i just pulled the latest one, as we don't really have any recent changes specifically for wince 18:44 #navit: <+jkoan> yes, but the uild is really broken :D 18:44 #navit: <+jkoan> *build 18:45 #navit: <@KaZeR> interesting. we need to fix that 18:45 #navit: <@KaZeR> but the .cab (and the associated resources) should still be valid 18:45 #navit: <+jkoan> i dont use cab, i can only use the exe, but yes, sould be 18:45 #navit: <+jkoan> *should 18:45 #navit: <@KaZeR> ok 18:46 #navit: <+jkoan> so if you touch the wince build could you also add zip with all files included (also images and config)? 18:47 #navit: <+jkoan> the exe reboots continuously let me chack the log 18:47 #navit: <+jkoan> *check 18:49 #navit: <+jkoan> full log: https://pastebin.com/RpZ8YCFL 18:50 #navit: <+jkoan> AVIC-MRZ02: this is similar to what you ad when we started, right? 18:50 #navit: <@KaZeR> jkoan: looks like an issue finding the config file. are you able to add command line parameters? 18:50 #navit: <@KaZeR> do you have a navit.xml? 18:51 #navit: <+jkoan> yes, in the same directory, but i can try to foce navit to run with it (navit.exe -c navit.xml 18:52 #navit: < AVIC-MRZ02> jkoan: In a series of build it was continuously re-booting but KaZeR solved that re-boot at that time. 18:53 #navit: <@KaZeR> jkoan: navit -d9 would help too (debug mode) 18:53 #navit: <+jkoan> KaZeR: i will try, just need to check the doc of Mortscript 18:55 #navit: <@KaZeR> ok thanks 18:56 #navit: < AVIC-MRZ02> jkoan: I don't want to interrupt but which version of Mortscript you are using? 18:57 #navit: <+jkoan> KaZeR: btw navittom/linux is more intelligent than wince: if i unmount the filesystem wince does nothing, but linux reboots, for wince i need to remove the cable 18:58 #navit: <+jkoan> KaZeR: need to check, it was included, so i dont know 18:59 #navit: <+jkoan> MortScript V4.1 19:00 #navit: < AVIC-MRZ02> jkoan: Thanks 19:00 #navit: <+jkoan> thx for what? 19:01 #navit: < AVIC-MRZ02> giving me the version info 19:01 #navit: <+jkoan> ah okay :D 19:01 #navit: <+jkoan> is "ah" international? 19:02 #navit: < AVIC-MRZ02> seems so. 19:03 #navit: <+jkoan> KaZeR: https://pastebin.com/zfyt4TQE 19:04 #navit: < AVIC-MRZ02> Cannot find navit.xml? This was my case :) 19:04 #navit: <+jkoan> yes, i know :D 19:05 #navit: <+jkoan> i will fix it by provideing the full path 19:06 #navit: <+jkoan> AVIC-MRZ02: interesting thing for you: MortScript can read an write the registry 19:07 #navit: <@KaZeR> jkoan: i think that it's because `pwd` isn't supported under wince 19:08 #navit: < AVIC-MRZ02> jkoan: Yes, I know, I tried it. It can modify the values but after re-boot everything returns back. 19:08 #navit: <+jkoan> KaZeR: but the logfile is at rhe right place 19:10 #navit: <+jkoan> AVIC-MRZ02 probably most of the system is only in the ram? 19:11 #navit: <@KaZeR> jkoan: interesting 19:12 #navit: < AVIC-MRZ02> jkoan: May be it's in RAM or may be it's re-writing registry values in boot. 19:15 #navit: < AVIC-MRZ02> jkoan: MS official site says that it needs RegFlushKey function to be executed to make modifications persistent. KaZeR located these functions in executable, I tested it but no way. 19:19 #navit: <+jkoan> KaZeR and AVIC-MRZ02: "Da Windows Mobile kein „aktuelles Verzeichnis“ kennt." just read this, it means "Because wince dies not know a current working directory" 19:26 #navit: <@KaZeR> yep 19:27 #navit: <+jkoan> then the only question is why its working on older versions 19:28 #navit: < AVIC-MRZ02> Which version of WinCE you're using right now? I think my head-unit is running on 5.0. 19:31 #navit: <+jkoan> i dont know right now, will chck soon 19:31 #navit: <+jkoan> *check 19:38 #navit: <+jkoan> WinCE Version: 6.0.3122 19:39 #navit: < AVIC-MRZ02> I'm not sure but my WinCE is 5.0 (most probably). 19:40 #navit: <+jkoan> you could try to install MortScript and test it :D 19:44 #navit: <+jkoan> KaZeR: could you provide the config file fixed version of the exe? 19:46 #navit: <+ilovekiruna> hi all 19:46 #navit: < AVIC-MRZ02> jkoan: OK. I found the command for version info (x = SystemVersion( [element] )). I'll check tomorrow. 19:46 #navit: <+jkoan> hi ilovekiruna 19:46 #navit: <+jkoan> AVIC-MRZ02: yes, right, but that would be a information i could also provide 19:46 #navit: <+ilovekiruna> hi jkoan 19:46 #navit: <+jkoan> ilovekiruna: whats up? 19:47 #navit: <+ilovekiruna> jkoan: so how about trunk now? 19:47 #navit: <+ilovekiruna> just kill my local copy? 19:47 #navit: <+ilovekiruna> or kill trunk branch and pull it new? 19:47 #navit: <+jkoan> the local copy is not the problem 19:47 #navit: <+ilovekiruna> but still, dont I always make my branches from the local copy? 19:48 #navit: <+jkoan> its also online. did you tryed the idea from the morning? 19:50 #navit: <+ilovekiruna> i think i slowly get it 19:50 #navit: <+ilovekiruna> will try 19:50 #navit: <+ilovekiruna> jkoan: by any chance are you good at writing .spec files? 19:50 #navit: <+jkoan> i have never done it 19:50 #navit: <+jkoan> but probably need to do it soon for the rpm build 19:51 #navit: <@KaZeR> jkoan: config file fixed version of the exe? 19:51 #navit: <+jkoan> the one you also did for AVIC-MRZ02. with fixed path 19:52 #navit: <+jkoan> https://pastebin.com/hEiVXkpB it looks like we also have the \ / issue, because the tryed path is right 19:53 #navit: <@KaZeR> mmm. i can probably find it somewhere, but it was really specific to AVIC-MRZ02's device 19:53 #navit: <+ilovekiruna> jkoan: I now try it for sth else, also clueless :) 19:54 #navit: <@KaZeR> ilovekiruna: you shouldn't need to kill your trunk branch, you should be able to update it from our main repo 19:54 #navit: <@KaZeR> ilovekiruna: you can get access to our main repo if you don't have it btw, could make your life easier 19:56 #navit: <+jkoan> KaZeR: he has a false commit in its trunk, so the easiest way is to override the trunk 19:57 #navit: <+ilovekiruna> i finally realized what sleske meant in the morning :( 19:57 #navit: <+ilovekiruna> my coe is commented out 19:57 #navit: <+jkoan> yep 19:57 #navit: <+ilovekiruna> need to do it again 20:02 #navit: <+ilovekiruna> before merging I want to check out the new warnings, there must be a reason why i commented it out 20:02 #navit: <+ilovekiruna> KaZeR: thanks for mentioning, I already have 20:07 #navit: <@KaZeR> ok cool. would have been surprised if it wasn't the case :) 20:18 #navit: <+jkoan> KaZeR: big present for you: https://jkoan.de/navit.log 20:19 #navit: <+jkoan> its so bit that pastebin dont want it :D 20:20 #navit: <+ilovekiruna> jkoan: from which drive is it? 20:21 #navit: <+jkoan> Navigon 10/71 Easy (WinCE 6.0.3122) 20:25 #navit: <+jkoan> KaZeR, AVIC-MRZ02, ilovekiruna: navit is starting :O https://static.jkoan.de/IMG_20180116_212248.jpg 20:25 #navit: <+ilovekiruna> cool 20:25 #navit: <+ilovekiruna> congrats 20:26 #navit: <@KaZeR> jkoan: nice! 20:27 #navit: <+jkoan> test done, it works 20:27 #navit: <@KaZeR> are the icons in the menu working? 20:27 #navit: <+jkoan> yes 20:27 #navit: <@KaZeR> ok that's good to know thanks 20:27 #navit: < AVIC-MRZ02> That's what I want to see on my head-unit :) 20:27 #navit: <@KaZeR> so back to the drawing board for AVIC-MRZ02's icons issue 20:27 #navit: <+jkoan> the icon issue on AVIC-MRZ02is due to xpm to icons change only the directory needs to renamed 20:30 #navit: <@KaZeR> not sure i got that. did you have to change something on your end to get this to work? 20:30 #navit: <@KaZeR> can you please elaborate or guide AVIC-MRZ02 through the change? 20:32 #navit: <+jkoan> the old versions of navit had a directory called xpm for the icons but we renamed that like you should remember. so on AVIC-MRZ02 we probably have the old xpm filder containing the icons, but the folder needs to be renamed to icons 20:34 #navit: <@KaZeR> mmm. AVIC-MRZ02's setup is quite recent. AVIC-MRZ02 can you please confirm if your folder is indeed 'icons' and not 'xpm' ? 20:34 #navit: <@KaZeR> jkoan: also i'd expect navit to complain about not being able to open the icon file in this case, but it's worth double checking 20:36 #navit: <+jkoan> the setup is really up to date but when he started we only head old binary's because the wince build was broken so i asume he has xpm 20:37 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has quit [Remote host closed the connection] 20:39 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has joined #navit 20:39 -!- mode/#navit [+v ilovekiruna] by ChanServ 20:39 #navit: < AVIC-MRZ02> OPS. I'm back. What must be the folder name of images? 20:40 #navit: < AVIC-MRZ02> In the version that I tried to execute with file manager, folder name was 'xpm'. 20:41 #navit: <@KaZeR> AVIC-MRZ02: dang! jkoan might be right :) 20:41 #navit: <+jkoan> :D 20:41 #navit: <+jkoan> good catch? :P 20:42 #navit: < AVIC-MRZ02> So, folder name must be 'icons'? 20:42 #navit: <@KaZeR> jkoan: fingers crossed 20:42 #navit: <@KaZeR> AVIC-MRZ02: yep 20:42 #navit: <+jkoan> icons instead of xpm yes 20:43 #navit: <+jkoan> AVIC-MRZ02: do you have the gps checker? 20:45 #navit: < AVIC-MRZ02> jkoan: Which app you're using for GPS? 20:45 #navit: <+jkoan> to deteckt the right com port 20:47 #navit: < AVIC-MRZ02> jkoan: I have one but I'm not sure about it, can you please share your executable for GPS check. 20:47 #navit: <+jkoan> i dont have one :D 20:48 #navit: <@KaZeR> AVIC-MRZ02: that suspens around icons is killing me!! :) 20:51 #navit: < AVIC-MRZ02> When I use the app that I have for GPS check, it says no GPS found in any port! 20:52 #navit: <+ilovekiruna> KaZeR,jkoan: can you please check my pull-request again? 20:52 #navit: <+jkoan> ilovekiruna: yes 20:52 #navit: <+ilovekiruna> I can merge it afterwards :) 20:52 #navit: <+jkoan> AVIC-MRZ02: wher did you found your gps check exe? 20:53 #navit: <+jkoan> ilovekiruna: did you looked if the warning is away? 20:53 #navit: < AVIC-MRZ02> jkoan: In one the forms 20:53 #navit: < AVIC-MRZ02> *one of the 20:55 #navit: < AVIC-MRZ02> jkoan: in AVIC411.com 20:55 #navit: < AVIC-MRZ02> jkoan: exactly in topic: http://avic411.com/index.php?/topic/31534-condis-hackmode-v22-autoinstall-working-also-with-f40bt-x940bt-etc-updated-27092012/page-1 20:55 #navit: <+ilovekiruna> jkoan: was wondering do we see the warnings on the ci? 20:56 #navit: <+ilovekiruna> was searching there, wanted to check 20:56 #navit: <+jkoan> ilovekiruna: i dident checked because i focus of the the wince problem today 21:07 -!- AVIC-MRZ02 [5f8e8f27@gateway/web/freenode/ip.95.142.143.39] has quit [Ping timeout: 260 seconds] 21:09 #navit: <@KaZeR> afk an hour or so 21:09 #navit: <+ilovekiruna> jkoan: there seems to be no warning in that file now :) 21:10 #navit: <+jkoan> KaZeR: now gps also seems to work 21:11 #navit: <+jkoan> will test tomorrow 21:19 #navit: <+ilovekiruna> any news on logo? 21:19 #navit: <+ilovekiruna> youte? 21:20 #navit: <+jkoan> Ilovekiruna youte was not online today 21:21 #navit: <+ilovekiruna> jkoan: u saw that i checked about the warning? 21:22 #navit: <+jkoan> Yes, I will check it tomorrow. And merge it afterwards 21:25 #navit: <+ilovekiruna> ok, if you want to shift it, however, we talk just about four lines 21:26 #navit: <+jkoan> Kazer after you are back, will you repair the wince build? 21:26 #navit: <+jkoan> Ilovekiruna every contribution is a big help 21:26 #navit: <+ilovekiruna> jkoan: dont worry 21:26 #navit: <+ilovekiruna> it was more a small challenge for myself 21:27 #navit: <+jkoan> The reason for fixing those warnings is because there is a ticket on the debian bug tracker (or somewhere there) this is where the idea came from 21:36 -!- AVIC-MRZ02 [b9e3b466@gateway/web/freenode/ip.185.227.180.102] has joined #navit 21:36 #navit: < AVIC-MRZ02> Hi There 21:36 #navit: < AVIC-MRZ02> KaZeR & jkoan are you here? 21:38 #navit: <+jkoan> Hi AVIC-MRZ02 yes I am here 21:39 #navit: <+jkoan> Is it working? 21:39 #navit: < AVIC-MRZ02> I was not planning to go to my car tonight but couldn't wait :) 21:40 #navit: < AVIC-MRZ02> Except GPS it's working 21:40 #navit: <+jkoan> I see a smile, so it's working? 21:40 #navit: <+jkoan> We will also figure out how to get GPS working 21:40 #navit: <+jkoan> What was your last try in the Navit config? 21:41 #navit: <+jkoan> BTW is your unit fast enough or does scrolling through the map is lagging? 21:42 #navit: < AVIC-MRZ02> I executed the app which finds GPS on COM ports. It's not finding any port. It checks from 0 to 9 21:43 #navit: < AVIC-MRZ02> I'm running navit from USB so it's not fast, if I copy it to unit I hope it will be faster 21:43 #navit: < AVIC-MRZ02> These are the images https://imgur.com/IQo12wR and https://imgur.com/qR0ByJF 21:44 #navit: <+jkoan> Really cool :) 21:45 #navit: <+jkoan> So last steps are gps and clean everything up 21:45 #navit: < AVIC-MRZ02> The other problem is that, when I copy exactly the same program to device and try to run instead of it's original navigation app. it gives this parsing problem 21:45 #navit: <+jkoan> Plus the bonus feature of audio feedback 21:46 #navit: <+jkoan> Did you tryed with the last version? 21:46 #navit: <+jkoan> But we will find a solution for that also :) 21:46 #navit: < AVIC-MRZ02> If I can find time I'll try it tomorrow. 21:47 #navit: <+jkoan> Okay, fingers are crossed as always 21:48 #navit: < AVIC-MRZ02> I read (from the form) the connection pin of com port 1, may be it's possible to detach it's GPS receiver from it's current pins and connect it to that pins 21:49 #navit: <+jkoan> Tomorrow I will also try to get my GPS ready (test if it really works) and optimize the osd 21:49 #navit: < AVIC-MRZ02> I asked about that idea to the ones in form but they said that an extra receiver is required. 21:50 #navit: <+jkoan> The better solution would be to do everything in Software so everybody who has the same unit can just install it easily 21:50 #navit: <+jkoan> We will see ;) 21:51 #navit: <+jkoan> Probably they also told that navit is not able to run on your device 8) 21:53 #navit: < AVIC-MRZ02> Exactly you're right, If problem can be solved in S/W side then there will be no need to touch device electronically. 21:55 -!- Mineque [~Mineque@public-gprs368754.centertel.pl] has joined #navit 21:55 #navit: < Mineque> hi 21:55 #navit: < AVIC-MRZ02> OK. I have to go now. See you soon. bye. 21:56 -!- AVIC-MRZ02 [b9e3b466@gateway/web/freenode/ip.185.227.180.102] has quit [Quit: Page closed] 21:57 #navit: <+jkoan> Hi Mineque 21:57 #navit: <+jkoan> You are the very first designer of navit right? 21:58 #navit: < Mineque> +/- few years ago 21:58 #navit: < Mineque> when OSD gui became usable 21:58 #navit: < Mineque> why? 21:58 #navit: < Mineque> and only OSD ui 22:00 #navit: <+jkoan> Because ilovekiruna and I will visit the Fosdem and want to print t-shirts. Probably you could design something for us? Youte already said he wanted to do something but he is very busy and we have limited time to order the shirts since the Fosdem is on begin of February 22:01 #navit: < Mineque> any ideas? voting? 22:01 #navit: < Mineque> or maybe more details about "something"? 22:01 #navit: < Mineque> ;) 22:02 #navit: <+jkoan> T-shirt with navit logo on it is the most I know. I think ilovekiruna has more details. 22:03 #navit: <+jkoan> And not related to the shirts but I think Kazer he'd the idea to update the Navit logo 22:03 #navit: < Mineque> deadline? 22:05 #navit: <+jkoan> For the shirts? 22:07 #navit: <@KaZeR> hi Mineque 22:07 #navit: < Mineque> jkoan: yeah 22:08 #navit: < Mineque> hi KaZeR logo ideas? 22:08 #navit: <+jkoan> For the t-shirts it would be in one week because print and transport need about a week and the Fosdem is on 03.02.18 22:10 #navit: <@KaZeR> Mineque: no not really. I have one idea : make it look good :) 22:10 #navit: <@KaZeR> jkoan: nice find on the xpm thing. This one was puzzling me off 22:12 #navit: < Mineque> KaZeR: so still the same old idea 22:13 #navit: <@KaZeR> yep 22:21 #navit: < Mineque> jkoan: some brainstorm about logo redesign wouldnt be bad 22:23 #navit: <+jkoan> Okay, but not today *zzz* need to wake up in less than 6h 22:28 #navit: <+jkoan> Good night guys 22:29 #navit: < Mineque> cya 22:47 -!- Mineque [~Mineque@public-gprs368754.centertel.pl] has quit [Quit: Leaving] 22:55 -!- Mineque [~Mineque@public-gprs368754.centertel.pl] has joined #navit 23:06 -!- Mineque [~Mineque@public-gprs368754.centertel.pl] has quit [Read error: Connection reset by peer] 23:36 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds] 23:43 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit --- Log closed Wed Jan 17 00:00:57 2018