--- Log opened Thu Oct 26 00:00:51 2017 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 02:50 -!- noradtux [~noradtux@2a04:4540:8c05:c501:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 255 seconds] 02:54 -!- noradtux [~noradtux@port-1775.pppoe.wtnet.de] has joined #navit 05:12 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 07:34 #navit: < jkoan> Found a possible way to fix the Fdroid problem: https://api.github.com/repos/navit-gps/navit/releases 07:35 #navit: < jkoan> Probably also https://api.github.com/repos/navit-gps/navit/releases/latest 07:49 #navit: < jkoan> This could be the regex: .*"tag_name". *"(.*)",$ 10:55 #navit: < jkoan> Hi Kazer hi youte 10:55 #navit: < jkoan> Hi ilovekiruna 10:59 #navit: < jkoan> What about doing the change on fdroid and then publish a pre release for 0.5.1? I know we have around 100 Tickets remaining, but even though we can release a pre release or are released candidate 10:59 #navit: < jkoan> This could also help to test fdroid 11:02 #navit: < jkoan> Also youte: do you want to write a new description for Fdroid (in my opinion we should drop the reference to zanavi because in my mind we can not recommend it 11:02 #navit: < jkoan> ) 14:39 #navit: < jkoan> youte: we need to create something like this for navit https://static.jkoan.de/cloud/index.php/s/TFdfPqT9XiVr8Tg 14:39 #navit: < jkoan> The Wikipedia app on fdroid is the perfect showcase 14:55 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:25 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 16:37 #navit: <@KaZeR> hi there 16:37 #navit: <@KaZeR> jkoan: works for me. 0.5.1 is overdue anyway, we can move the tickets to 0.5.2 16:38 #navit: < jkoan> nice 16:38 #navit: < jkoan> hi KaZeR 16:38 #navit: < jkoan> currently working on regex for f-droid.... 16:38 #navit: < jkoan> and metadata like that one on the screenshot 16:39 #navit: < ilovekiruna> Hi jkoan, hi KaZeR 16:39 #navit: < jkoan> hi ilovekiruna 16:46 #navit: < jkoan> KaZeR: how good are you in regex? 16:50 #navit: <@KaZeR> decent 16:52 #navit: < jkoan> from "2015-12-31T07:42:41Z" this i need only the numbers, but in one capture group 16:53 #navit: <@KaZeR> this one's tricky. does it has to be in one pass? 16:54 #navit: < jkoan> its in python and is not re programmable (f-droid) they take the first group 16:55 #navit: <@KaZeR> do you have a url pointing to the doc? 16:57 #navit: < jkoan> https://f-droid.org/uk/docs/Build_Metadata_Reference/#Update-Check-Mode 16:58 #navit: < jkoan> in code its: m = re.search(codeex, page) 16:58 #navit: < jkoan> vercode = m.group(1).strip() 16:58 #navit: <@KaZeR> how about we just provide an api endpoint specifically for them to check? 16:58 #navit: < jkoan> where codeex is the expression and page the content of the github api 16:58 #navit: < jkoan> api endpoint wood be nice 16:59 #navit: <@KaZeR> we would update the endpoint via circleci, and export the tag in the format that's convenient for them. Doing so we would have full control 16:59 #navit: <@KaZeR> are you familiar with aws lambda? 16:59 #navit: < jkoan> could you write one and push it today? 17:00 #navit: < jkoan> i am not familiar with all from aws 17:00 #navit: <@KaZeR> yeah sure. we can hardcode a tag for today to get the ball rolling 17:00 #navit: <@KaZeR> i'll give you the endpoint url. what should the query look like and what should the result look like? 17:01 #navit: < jkoan> two lines: 17:01 #navit: < jkoan> version_code:[code] 17:01 #navit: < jkoan> version_name:[name] 17:02 #navit: < jkoan> where name is v0.5.1 and code the id code from github api the published_at converted to YYMMDDHHMM 17:03 #navit: <@KaZeR> can you give me an example of code? 17:04 #navit: <@KaZeR> also name shouldn't be v0.5.1 as it isn't released yet. Can we use 'live' or 'git' for the name ? 17:04 #navit: <@KaZeR> gentoo calls that -9999 for example 17:04 #navit: < jkoan> what language do you prefer? then i write it 17:05 #navit: < jkoan> okay, i have an idea 17:05 #navit: < ilovekiruna> KaZeR: I am not sure if the gentoo style is so good here 17:05 #navit: < ilovekiruna> as i think froid or the market have nothing comparable to masking 17:06 #navit: <@KaZeR> ilovekiruna: true :) it's definitely a workaround for the version scheme having to match -[\d\.]+ : 17:06 #navit: <@KaZeR> just wanted to point out that usually you should make a distinction between a release and 'live' code 17:06 #navit: < ilovekiruna> I agreee 17:07 #navit: < ilovekiruna> maybe i missed it, but what about using the short commit hash 17:07 #navit: < ilovekiruna> then the data is metadate in froid, and we dont mess always with numbers 17:08 #navit: < ilovekiruna> those are clearly hashes and not plain numbers 17:09 -!- MarcR [~MarcR@p5DD9111B.dip0.t-ipconnect.de] has joined #navit 17:12 #navit: < MarcR> Hi everyone! 17:13 #navit: < jkoan> hi MarcR 17:13 #navit: < ilovekiruna> hi MarcR 17:15 #navit: < MarcR> Has anyone an idea how i can get more peformance to navit on my pi ? maybe there is a better rendering method ? 17:15 #navit: < ilovekiruna> KaZeR: I think for the next tests, i rather leave the device farm 17:15 #navit: < ilovekiruna> return when i have everything running and do appium tests locally, if i ever get it to work 17:27 #navit: < youte> ok jkoan 17:35 #navit: < jkoan> KaZeR: how about this? https://pastebin.com/aEKYDdi2 17:36 #navit: < jkoan> then i add this to artifacts at circleci 17:40 #navit: < jkoan> and config diff would be: https://pastebin.com/8zggHJ27 17:44 #navit: < jkoan> is it okay to test it? (on circleci) 17:48 #navit: <@KaZeR> ilovekiruna: i believe that there's a restriction about the tag, like it has to be incremental or something 17:49 #navit: <@KaZeR> MarcR: what rendering method are you currently using? 17:50 #navit: <@KaZeR> jkoan: but how would you query the artifact then? 17:51 #navit: <@KaZeR> ilovekiruna: yeah i guess that testing locally would make your life easier at the beginning 17:55 #navit: < MarcR> KaZeR: in navit.xml gui type is internal 17:56 #navit: <@KaZeR> ok, what about 'graphics'? 17:57 #navit: < MarcR> What do you mean ? 17:58 #navit: < MarcR> pi graphics ram is set to 512mb 17:59 #navit: <@KaZeR> i meant the `graphics` tag in navit.xml :) 18:00 #navit: <@KaZeR> https://wiki.navit-project.org/index.php/Configuration/Display_Options#Graphics_Driver 18:00 #navit: <@KaZeR> you're probably using gtk_drawing_area which is the default 18:00 #navit: < MarcR> Ah 18:00 #navit: < MarcR> sorry :) 18:00 #navit: <@KaZeR> on the pi, if you want to run navit fullscreen, qt5 can be used with the egl backend. this means that you get full acceleration without even needing X 18:00 #navit: <@KaZeR> np i wasn't clear :) 18:01 #navit: < jkoan> KaZeR: that was new to me, i only tryed sdl without X on pi 18:02 #navit: <@KaZeR> jkoan: qt5+eglfs is blazing fast. Animations are super smooth 18:02 #navit: < MarcR> it is gtk_drawing_area 18:02 #navit: < jkoan> ah okay :D 18:02 #navit: <@KaZeR> jkoan: i'll record a demo video 18:02 #navit: < jkoan> you dont need t i trust you ^^ 18:02 #navit: < MarcR> smooth and fast, sounds good to me ;) 18:03 #navit: <@KaZeR> MarcR: so my advice would be to switch to qt5+eglfs. first you'd need to install qt5 then recompile navit. you can't use a package for this, it has to be from sources currently 18:03 #navit: < MarcR> so i can switch to qt5 and give it a try ? 18:03 #navit: <@KaZeR> yeah, happy to help you do so 18:03 #navit: <@KaZeR> soon we'll provide prebuilt images for that, which will make everybody's life easier. it's almost done 18:03 #navit: < MarcR> uh ok 18:04 #navit: < MarcR> my problem is, that my last try to compile navit on my pi, was a failure 18:04 #navit: <@KaZeR> i'm sure we can fix that :) 18:04 #navit: < MarcR> only get it back via package 18:06 #navit: < MarcR> so I will delete working but, a but laggy navit now - and begin the step by step navit install from wiki again 18:06 #navit: < MarcR> all for the club ;-) 18:11 #navit: < MarcR> damn - can't find the step by step install tutorial again in the wiki ... 18:12 #navit: < MarcR> got it 18:12 #navit: < MarcR> had to clean my glaases more often ;-) 18:14 #navit: <@KaZeR> jkoan: how about https://epu5hjnir7.execute-api.us-west-2.amazonaws.com/prod/fdroid ? 18:14 #navit: < jkoan> would be possible 18:14 #navit: <@KaZeR> MarcR: that helps :) 18:14 #navit: <@KaZeR> jkoan: it's just a quick and dirty example but we could push tag updates from circleci and have f-droid query that endpoint, should work 18:15 #navit: < jkoan> my idea would be: https://circleci.com/api/v1/project/navit-gps/navit/latest/artifacts/root/f-droid?branch=master&filter=successful (not working right now 18:15 #navit: <@KaZeR> api v1 ? 18:15 #navit: <@KaZeR> this doens't work in v2 anymore i believe 18:15 #navit: < jkoan> dont know if its working also on v2 18:15 #navit: < jkoan> i am testing right now 18:16 #navit: <@KaZeR> because of the workflow feature, you can're really rely on build numbers anymore. each step of a workflow will have its own build number (vs each build before) 18:16 #navit: < jkoan> yes, but here its only latest 18:20 #navit: < ilovekiruna> KaZeR: what i find really tricky is how to predict how long the download should take 18:21 #navit: < ilovekiruna> on the aws farm, beside the general issues i told u yesterday 18:21 #navit: < MarcR> ah ok - looks like I need the total qt5 package to get forward with compiling 18:21 #navit: < MarcR> CMake Warning at CMakeLists.txt:172 (find_package): 18:21 #navit: < MarcR> By not providing "FindQt5Quick.cmake" in CMAKE_MODULE_PATH this project has 18:21 #navit: < MarcR> asked CMake to find a package configuration file provided by "Qt5Quick", 18:21 #navit: < MarcR> but CMake did not find one. 18:22 #navit: < jkoan> MarcR: did you installed the lib -dev packages 18:22 #navit: <@KaZeR> ilovekiruna: indeed, because it depends on the load on our servers and also the bandwidth available in the farm 18:23 #navit: < ilovekiruna> KaZeR: any idea how to predict? or detect when the download is done? 18:23 #navit: <@KaZeR> ilovekiruna: we could detect by looking at the active menu item. If we are downloading, then the menu is still displayed. 18:23 #navit: < ilovekiruna> good idea :) 18:24 #navit: <@KaZeR> We could also programatically look at the maps that are available (on linux dbus would work, dunno about android) 18:24 #navit: < ilovekiruna> maybe i also try that in some time 18:24 #navit: <@KaZeR> cool! 18:24 #navit: < MarcR> jkoan: i followed the install tutorial step by step 18:24 #navit: < MarcR> ah 18:25 #navit: < MarcR> there is still some missing devs 18:25 #navit: < MarcR> standby 18:25 #navit: <@KaZeR> MarcR: the pain you're going through right now will help us improve our docs, thanks for being the guinea pig :) 18:26 #navit: < MarcR> everything tastes better with bacon 18:26 #navit: < MarcR> ;-) 18:28 #navit: < jkoan> KaZeR: feature freeze on sunday? ;) then we publich 0.5.1-rc1? ;) 18:28 #navit: < jkoan> *publish 18:28 #navit: < MarcR> so 18:28 #navit: < MarcR> there is a problem with the raspbian tutor 18:29 #navit: < MarcR> mkdir navit-build 18:29 #navit: < MarcR> and then in navit-build 18:29 #navit: < MarcR> starts cmake 18:30 #navit: < MarcR> pi@RaspiCarPC:~/navit-build $ cmake ~navit -DFREETYPE_INCLUDE_DIRS=/usr/include/freetype2/ 18:30 #navit: < MarcR> CMake Error: The source directory "/home/pi/navit-build" does not appear to contain CMakeLists.txt. 18:30 #navit: < MarcR> Specify --help for usage, or press the help button on the CMake GUI. 18:30 #navit: < MarcR> I know, where the cmakelists.txt is, but that isn't helping the wiki 18:30 #navit: <@KaZeR> looks like a / is missing. should be ~/navit probably 18:31 #navit: < MarcR> yeap 18:31 #navit: < MarcR> so i found a mistake in the wiki ;-) 18:32 #navit: <@KaZeR> wiki fixed, thank you :) 18:32 #navit: < MarcR> your' welcome 18:32 #navit: < jkoan> feel free to find more ;) there will be a lot :X 18:33 #navit: < MarcR> I'm not done with my install, so we will see 18:33 #navit: < MarcR> -- WARNING: you are using the obsolete 'PKGCONFIG' macro, use FindPkgConfig 18:33 #navit: < MarcR> -- PKGCONFIG() indicates that gtk+-2.0 is not installed (install the package which contains gtk+-2.0.pc if you want to support this feature) 18:34 #navit: <@KaZeR> we don't need gtk if we want to use qt5 18:34 #navit: < MarcR> but i want to compile my navit ;) 18:35 #navit: < MarcR> CMake Warning at CMakeLists.txt:172 (find_package): 18:35 #navit: < MarcR> By not providing "FindQt5Quick.cmake" in CMAKE_MODULE_PATH this project has 18:35 #navit: < MarcR> asked CMake to find a package configuration file provided by "Qt5Quick", 18:35 #navit: < MarcR> but CMake did not find one. 18:38 #navit: <@KaZeR> MarcR: cmake messages are not necessarily errors. What this does is look at what's available for your system and then build navit according to what you have 18:39 #navit: <@KaZeR> for qt5quick i believe that it's libqt5quick5 let me check 18:40 #navit: < MarcR> yeah looks like i dont have any qt5 stuff on my pi 18:40 #navit: < MarcR> but it is updated, and dist-upgraded 18:40 #navit: < ilovekiruna> KaZeR: working now on my phone 18:41 #navit: < ilovekiruna> so cool to c how things work magically ;-) 18:43 #navit: < MarcR> ilovekiruna - i had an sony erricson years ago, which had an open os - was so cool, to play scumvm games on it :) 18:43 #navit: < ilovekiruna> which OS was on it? 18:43 #navit: < MarcR> puh man, it is 10 years ago 18:43 #navit: < MarcR> it was one of the first hand helds 18:43 #navit: < MarcR> from sony 18:44 #navit: < MarcR> with touch 18:45 #navit: <@KaZeR> ilovekiruna: awesome :) 18:45 #navit: < MarcR> it was the P990i 18:45 #navit: <@KaZeR> oh i had a p990i too :) 18:45 #navit: < MarcR> it was cool 18:46 #navit: <@KaZeR> it was really good at that time. excepted the messaging app, it was crappy 18:46 #navit: < MarcR> yes 18:46 #navit: <@KaZeR> crap i can't find my qt5 deps list for debian anymore 18:46 #navit: <@KaZeR> no big deal 18:48 #navit: < MarcR> i actually have qmake 3.0 on my pi 18:48 #navit: < MarcR> hmm 18:49 #navit: < MarcR> ah qtcreator is missing - and 470mb of stuff getting installed now 18:49 #navit: < MarcR> standby ;-) 18:51 #navit: < MarcR> hmmm... looks like my 16gb sd card is not enough for my carpi :-P 18:51 #navit: <@KaZeR> ha! apt-get install cmake libpng12-dev librsvg2-bin libfreetype6-dev libdbus-glib-1-dev g++ libgtk2.0-dev libqt5svg5-dev qtdeclarative5-qtquick2-plugin qtdeclarative5-window-plugin qtmultimedia5-dev is what we used to use in the CI 18:52 #navit: <@KaZeR> you probably don't need qtcreator : it's only used to edit the interface 18:52 #navit: <@KaZeR> you probably want libqt5svg5-dev qtdeclarative5-qtquick2-plugin qtdeclarative5-window-plugin qtmultimedia5-dev 18:52 #navit: < MarcR> ah ok 18:53 #navit: < MarcR> qtcreator is getting installed right now... 18:53 #navit: <@KaZeR> also, with the build we've been working on the system image is about 250Mb! 18:57 #navit: < MarcR> packet qtdeclarative5-qtquick2-plugin is not available on my pi ..... 18:58 #navit: < MarcR> will do update and upgrade again 18:59 #navit: <@KaZeR> might be something quite close. this package was for ubuntu 14.04 i believe 19:00 #navit: < MarcR> i think there are missing repos 19:12 #navit: <@KaZeR> crap. well that's a good opportunity to finish the pre-built image then 19:13 #navit: <@KaZeR> do you have a desktop installed on your pi? 19:15 #navit: < MarcR> yeap 19:16 #navit: < MarcR> i can install teamviewer - so you could have a look if you want ;) 19:17 #navit: < MarcR> hm no teamviewer on raspian .. ok 19:18 #navit: < jkoan> look on rdp if you use windows and want remote desktop 19:19 #navit: < MarcR> I have an extra monitor connected to my pi, via a hdmi to vga adapter ;-) 19:20 #navit: < MarcR> hm 19:20 #navit: < MarcR> still get the compile error 19:20 #navit: < MarcR> :'-( 19:21 #navit: <@KaZeR> CMake to find a package configuration file provided by "Qt5Quick" ? 19:21 #navit: < MarcR> Could not find a package configuration file provided by "Qt5Quick" with any 19:21 #navit: < MarcR> of the following names: 19:21 #navit: < MarcR> Qt5QuickConfig.cmake 19:21 #navit: < MarcR> qt5quick-config.cmake 19:21 #navit: < MarcR> i would take that as a no 19:22 #navit: <@KaZeR> apt-cache search qt5quick ? 19:23 #navit: < MarcR> libqt5quick5 - Qt 5 Quick library 19:23 #navit: < MarcR> libqt5quickcontrols2-5 - Qt 5 Quick Controls 2 library 19:23 #navit: < MarcR> libqt5quickparticles5 - Qt 5 Quick particles module 19:23 #navit: < MarcR> libqt5quicktemplates2-5 - Qt 5 Quick Templates 2 library 19:23 #navit: < MarcR> libqt5quicktest5 - Qt 5 Quick Test library 19:23 #navit: < MarcR> libqt5quickwidgets5 - Qt 5 Quick Widgets library 19:23 #navit: <@KaZeR> is libqt5quick5 installed ? 19:24 #navit: < MarcR> its set as installed manually 19:24 #navit: < MarcR> so - yes 19:26 #navit: < ilovekiruna> KaZeR: seems like i can detect it in my small setup :) 19:26 #navit: < ilovekiruna> what is next? 19:26 #navit: <@KaZeR> ilovekiruna: nice! 19:26 #navit: <@KaZeR> one thing i noticed yesterday is that testing a dbug apk via the farm, menu icons were missing. It makes navit almost unusable. Would be nice if we could ensure that they are here 19:27 #navit: <@KaZeR> next we should set a position and compute a route to ensure that it doesn't crash 19:27 #navit: < ilovekiruna> so far i have never tried to detect icons, sounds more tricky, strings are easy 19:27 #navit: <@KaZeR> MarcR: raspbian jessie, right? 19:27 #navit: < MarcR> correct 19:28 #navit: <@KaZeR> ilovekiruna: is it possible to read the application logs? if navit cannot load an icon it should complain there 19:28 #navit: <@KaZeR> and then as a rule of thumb we could just check for any error message in the logs and have the test fail if anything is found there 19:28 #navit: <@KaZeR> MarcR: ok give me a moment i'm pulling a pi from its drawer 19:28 #navit: < MarcR> ^^ ok 19:29 #navit: < MarcR> sorry that i make you more work. but you want me to help so ;-) 19:29 #navit: <@KaZeR> MarcR: oh no you're fine. this should be much easier than that 19:30 #navit: < ilovekiruna> KaZeR: does navit issue any error if icons are not loaded? 19:30 #navit: < MarcR> if anything would be right, there would be only - copy and paste the commands to the shell. but there is an error. don't know where 19:31 #navit: <@KaZeR> ilovekiruna: it should yeah 19:31 #navit: <@KaZeR> MarcR: indeed :) 19:31 #navit: < MarcR> ilovekiruna - you can enable logs via the navit.xml - done it before. then it should be in there 19:31 #navit: <@KaZeR> error logs should be always enabled :) 19:31 #navit: < ilovekiruna> MarcR: question would be if i could access that from my setup 19:32 #navit: < MarcR> then there was an detailed option, i enabled , but don't have an up and running navit at the moment ;-) 19:32 #navit: < ilovekiruna> MarcR: I try to test navit on android via appium 19:32 #navit: < MarcR> Ah ok 19:32 #navit: < ilovekiruna> so i run everything from a python script 19:32 #navit: < ilovekiruna> and not sure, if i could access from there the file system 19:33 #navit: <@KaZeR> ilovekiruna: how about adb logs ? 19:35 #navit: <@KaZeR> ilovekiruna: were you aware of this ? http://docs.aws.amazon.com/devicefarm/latest/developerguide/direct-device-access.html (i wasn't) 19:37 #navit: < ilovekiruna> KaZeR: look here: https://aws.amazon.com/device-farm/pricing/ 19:37 #navit: < ilovekiruna> ;-) 19:37 #navit: < MarcR> ha! @pricing 19:38 #navit: < MarcR> we could rent device minutes ;-) 19:39 #navit: <@KaZeR> fuck! they changed it no? it wasn't a one time offer before, was it? 19:40 #navit: < ilovekiruna> KaZeR: waht do u mean? 19:40 #navit: <@KaZeR> my recollection was that we would get free minutes every months. not a lot but we shouldn't need a lot 19:41 #navit: <@KaZeR> that page says it's a one time, 1000 minutes 19:41 #navit: < ilovekiruna> :-o 19:41 #navit: < ilovekiruna> now i get u 19:41 #navit: < ilovekiruna> that is pretty annoying 19:41 #navit: < ilovekiruna> just once 1000 minutes? 19:41 #navit: <@KaZeR> that's what this page says 19:42 #navit: <@KaZeR> ah! no! 19:42 #navit: < MarcR> oh - an aaaah moment ;) 19:42 #navit: <@KaZeR> Free one-time trial of 250 Device Minutes 19:42 #navit: <@KaZeR> FUCK 19:42 #navit: <@KaZeR> https://aws.amazon.com/free/?sc_ichannel=ha&sc_icampaign=free-tier&sc_icontent=2234 19:44 #navit: < ilovekiruna> https://aws.amazon.com/device-farm/?ft=n 19:45 #navit: < ilovekiruna> here is says again first 1000 minutes are free 19:45 #navit: < ilovekiruna> * For a limited time, get a one-time trial of 1000 free device minutes instead of the standard 250 device minutes. 19:45 #navit: < ilovekiruna> so we just have 1000 minutes in total :( 19:46 #navit: <@KaZeR> yes, but my recollection of our research was that after that we would get a free monthly credit 19:46 #navit: <@KaZeR> exactly 19:46 #navit: <@KaZeR> it might still be worth it. I'm willing to sponsor some time. We could also crowdfund via opencollective 19:47 #navit: < ilovekiruna> u know even 17 cts per minute, not sure if we would thing it is worth 19:47 #navit: <@KaZeR> to cover our infrastructure costs 19:47 #navit: <@KaZeR> you have concerns? 19:47 #navit: < ilovekiruna> i mean think about it, one of our simple tests excluding downloads already runs for 5 minutes 19:47 #navit: < ilovekiruna> from what we experienced so far 19:48 #navit: < ilovekiruna> lets say the whole test takes 20 minutes 19:48 #navit: < ilovekiruna> means every single test is roughly 3$ 19:49 #navit: < ilovekiruna> more precise 3.40$ 19:49 #navit: <@KaZeR> well it looks like we don't pay for the actual wall time 19:50 #navit: < ilovekiruna> could be, actually maybe we should once run a test and c how much it deducts 19:50 #navit: <@KaZeR> we've noticed that. also yesterday i notice that when running an interactive session it *seems* to bill only when you are interacting with the device 19:50 #navit: <@KaZeR> yep 19:50 #navit: < ilovekiruna> but ofc am a little concerned that it can quickly be quite some money unless we find a sponsor ofc 19:51 #navit: <@KaZeR> yeah. we'll need to have proper gating. We also don't want to test for each build, only for prod release to googleplay 19:51 #navit: < ilovekiruna> which would be still good, but ofc less of the ci type we first imagined 19:52 #navit: <@KaZeR> kind of yeah. as long as it helps reducing crashes, it's a win though 19:54 #navit: <@KaZeR> so right now we have 835 minutes remaining. Want to kick off a test? 19:54 #navit: < ilovekiruna> can just repeat the last, then have to be off a bit 19:54 #navit: <@KaZeR> yep that would work 19:55 #navit: < ilovekiruna> preparing for tomorrows trip :) 19:55 #navit: < MarcR> weekend trip 19:56 #navit: < ilovekiruna> nope 19:56 #navit: <@KaZeR> where are you going? 19:56 #navit: < ilovekiruna> one days of holidays 19:56 #navit: < ilovekiruna> to a cold country in the north 19:56 #navit: < ilovekiruna> where i worked before 19:56 #navit: < ilovekiruna> Sweden :) 19:56 #navit: <@KaZeR> ha, going to kiruna? :) 19:56 #navit: < ilovekiruna> not exactly, 400 kms away 19:56 #navit: <@KaZeR> kk 19:56 #navit: < MarcR> ah ok 19:57 #navit: < jkoan> KaZeR: for the fdroid file, what would you do? 19:57 #navit: < ilovekiruna> KaZeR: have you uploaded a new version of navit to the farm? 19:57 #navit: <@KaZeR> ilovekiruna: i did yesterday. that apk has the taiwan map menu entry 19:58 #navit: <@KaZeR> jkoan: what do you think of the api url i shared? 19:58 #navit: <@KaZeR> we just need to add a PUT endpoint to update the tags from the ci, and we're done 19:58 #navit: < ilovekiruna> KaZeR: ok. started it now. please check then and report 19:58 #navit: <@KaZeR> ilovekiruna: thanks, will do 19:59 #navit: < jkoan> KaZeR: how we get data into it? 19:59 #navit: <@KaZeR> jkoan: an api call using PUT instead of GET 20:00 #navit: < jkoan> with a token? 20:00 #navit: <@KaZeR> exactly 20:00 #navit: <@KaZeR> MarcR: dpkg -l|grep qt5quick ? 20:01 #navit: < MarcR> ii libqt5quick5:armhf 5.7.1-2+rpi1 armhf Qt 5 Quick library 20:01 #navit: < MarcR> ii libqt5quicktest5:armhf 5.7.1-2+rpi1 armhf Qt 5 Quick Test library 20:01 #navit: < MarcR> ii libqt5quickwidgets5:armhf 5.7.1-2+rpi1 armhf Qt 5 Quick Widgets library 20:01 #navit: <@KaZeR> jkoan: we probably don't need a git repo for that. we can store the current tag in aws 20:01 #navit: <@KaZeR> MarcR: interesting. here i have 5.3.2-4+rpi1+b1 which is too old for what we want 20:02 #navit: < MarcR> hmmm 20:02 #navit: <@KaZeR> (but i didn't install jessie, just used the sdcard that was already in the pi) 20:02 #navit: < jkoan> KaZeR: the repo is not for the version file 20:03 #navit: <@KaZeR> ah ok 20:04 #navit: < MarcR> so the self compiling navit - is not compatible with jessie ? 20:04 #navit: < jkoan> this is to get the things from the screenshot in order 20:05 #navit: <@KaZeR> ilovekiruna: if you hover over a time in the UI, it'll tell you how much we've really been charged : https://imgur.com/a/HCklr 20:05 #navit: < jkoan> what we also need are pictures 20:05 #navit: <@KaZeR> jkoan: gotcha 20:05 #navit: <@KaZeR> MarcR: they are from the previous raspbian release yeah. but we'll fix that 20:06 #navit: <@KaZeR> ilovekiruna: your test lasted 6:29 but we were metered for 3:39 20:06 #navit: < MarcR> so i need to reinstall navit via package ? 20:07 #navit: <@KaZeR> MarcR: depends of what your goal for today is. I'll resume the work on the prebuilt image for qt5. it's night and day with the performance that you would get using raspbian 20:07 #navit: < ilovekiruna> KaZeR: so it is roughly half of the shown time, right? 20:08 #navit: < ilovekiruna> still quite a bit i would say 20:08 #navit: < ilovekiruna> especially considering in those tests barely anything than opening navit was done 20:08 #navit: < MarcR> no need to rush, from my side. 20:09 #navit: < MarcR> so i can wait a bit more, until you give the prebuilt the go 20:10 #navit: < jkoan> Kazer if you could setup the file, I can implement it into the Fdroid update process and we can try it with the rc1 on Sunday? 20:13 #navit: <@KaZeR> ilovekiruna: i think that the actual time will depend on what we do. time will tell :) 20:14 #navit: < ilovekiruna> KaZeR: ofc depends on the use case, just thinking if for example downloading a map wouldnt be critical, as it is pretty non-deterministic 20:14 #navit: <@KaZeR> jkoan: how about we split the load? i'll provide an endpoint that will store the name and code when called via PUT, and reply with them when called via get, and you implement the ci part ? 20:15 #navit: < ilovekiruna> good thing is that appium can be also installed elsewhere 20:15 #navit: < ilovekiruna> KaZeR: anything done on FOSDEM? 20:15 #navit: <@KaZeR> ilovekiruna: regarding the map i wonder how much we're billed for that. we should test 20:15 #navit: <@KaZeR> and yeah with or without device farm, appium will help us improve 20:16 #navit: <@KaZeR> ilovekiruna: not yet. My suggestion was to start throwing some notes somewhere and see how it goes? 20:17 #navit: < ilovekiruna> i would i think first start making a bit a structure for myself, what to show, but some notes are already helpful 20:17 #navit: <@KaZeR> sure! 20:18 #navit: < ilovekiruna> KaZeR: wondering, some cheap phones from ebay, couldnt on that small scale we build sth by ourselfes? 20:18 #navit: < ilovekiruna> just run navit on those with a webhook on github? 20:19 #navit: <@KaZeR> ilovekiruna: yeah i've thought about that. The major difficulty was to find a test suit that would fit us. But your work on appium looks promising 20:19 #navit: <@KaZeR> i have a old nexus 5 tablet and an old phone that could be used for that 20:19 #navit: <@KaZeR> finding cheap android devices usually isn't a problem 20:20 #navit: < ilovekiruna> I have an old sony tipo 20:20 #navit: < MarcR> I have an old sony tablet too 20:20 #navit: < MarcR> but it lags like hell 20:21 #navit: <@KaZeR> cool :) 20:21 #navit: < jkoan> KaZeR: could an not process the github web hook? 20:21 #navit: <@KaZeR> if we could drive them using raspberry pi we could build our own farm 20:21 #navit: <@KaZeR> jkoan: what do you meant? 20:22 #navit: < ilovekiruna> KaZeR: maybe u remember, I thought about that right when starting with device farm ;-) 20:22 #navit: < jkoan> Register aws as we hook and Prozess the release information there 20:22 #navit: <@KaZeR> ilovekiruna: yeah, but at that time our understanding was that we would get some minutes each months, which made building our own farm not the best idea :) 20:23 #navit: < ilovekiruna> KaZeR: sure. i remember and still we have not had any loss yet 20:23 #navit: < jkoan> KaZeR: this one : https://developer.github.com/v3/activity/events/types/#releaseevent 20:23 #navit: < ilovekiruna> so am happy 20:23 #navit: <@KaZeR> jkoan: you mean update the api data via a github hook? 20:23 #navit: < jkoan> Jep 20:23 #navit: <@KaZeR> ilovekiruna: any loss? 20:23 #navit: <@KaZeR> jkoan: oh yeah totally 20:24 #navit: < ilovekiruna> KaZeR: i mean nothing was wasted, we are still progressing :) 20:26 #navit: <@KaZeR> ohyeah definitely 20:28 #navit: < jkoan> KaZeR: okay do you say if the link is ready? 20:30 #navit: < ilovekiruna> KaZeR: i see with adb we could then also make a video recording like on the device farm 20:30 #navit: <@KaZeR> i'm going to need a sample request to check the parameters 20:31 #navit: <@KaZeR> ilovekiruna: yeah pretty sure that device farm is using adb in the background 20:31 #navit: <@KaZeR> videos are great! 20:31 #navit: < jkoan> KaZeR: from github or fdroid? 20:31 #navit: <@KaZeR> from github yeah 20:32 #navit: <@KaZeR> from fdroid we're not expecting parameters, are we? 20:34 #navit: < jkoan> The Fdroid parameter are on the doc 20:34 #navit: < jkoan> *github parameter 20:36 #navit: <@KaZeR> jkoan: this would publish only on release. we don't want to publish on builds? 20:38 #navit: < jkoan> I think we should only trigger fdroid builds on releases and release more often ;) 20:38 #navit: <@KaZeR> that's a good option too 20:38 #navit: < MarcR> and raspian ;-) 20:39 #navit: <@KaZeR> well the issue with raspbian is that we don't have control over when they update the packages :) 20:39 #navit: <@KaZeR> fdroid has a programatic way of doing it 20:39 #navit: < MarcR> I just hear a "mimimi" here ;-) 20:39 #navit: <@KaZeR> haha 20:39 #navit: < MarcR> no, its ok. got you ;) 20:40 #navit: < MarcR> so maybe it would be better, if i use an "older" destri ? 20:41 #navit: <@KaZeR> issue is that an older distro like the one i have could have an outdated qt5 package 20:41 #navit: < MarcR> hm yeah 20:41 #navit: < MarcR> and I'm working an an up to date car pc 20:41 #navit: <@KaZeR> right now, you could revert to gtk navit to get used to it while we finish the qt5 prebuilt image 20:42 #navit: <@KaZeR> i don't think it'll be fully ready today, but it shouldn't take long either 20:42 #navit: < MarcR> hey, no need to finish a qt5 today 20:43 #navit: < MarcR> then i will install it via package again, and use gtk to configure the xml to my needs, then i will back it up, and will install a qt5 version, until its ready. no prob 20:43 -!- wondiws [~Jasper@5ED7DF59.cm-7-8d.dynamic.ziggo.nl] has joined #navit 20:43 #navit: < wondiws> hi there 20:44 #navit: < jkoan> Hi wondiws 20:44 #navit: < MarcR> hi wondiws 20:44 #navit: < wondiws> jkoan, I startup navit, but I only get an empty beige window 20:44 #navit: < wondiws> on Debian, I should add 20:48 #navit: < jkoan> wondiws: you need to add a map ;) 20:49 #navit: < wondiws> jkoan, is there some sort of system (that is also included in Debian)? 20:49 #navit: < jkoan> Check out how to configure navit https://wiki.navit-project.org/index.php/Configuration 20:50 #navit: < jkoan> Navit is compatible with OpenStreetMap maps which must be downloaded 20:50 #navit: < jkoan> Check http://maps.navit-project.org for the map download 20:51 #navit: < jkoan> If you need help feel free to ask here :) but it could take some time for us to answer because we don't have so much manpower ;) 20:54 #navit: <@KaZeR> hi wondiws 20:55 #navit: < wondiws> hi KaZeR 20:55 #navit: <@KaZeR> i would check if your version of navit isn't too old. Debian might be packaging an old version that is not compatible with our newer maps 20:55 #navit: <@KaZeR> and welcome btw :) 20:56 #navit: < ilovekiruna> KaZeR: saw this now. https://github.com/cisco-open-source/qtwebdriver I wonder if with that i could also cover sailfish 20:58 #navit: < wondiws> I download the benelux map of 1.7GB, added it to the config file, it loads it, because it doesn't give me the error anymore when I made a typo in the filename, but nothing happens :( 20:59 #navit: < wondiws> my version is 0.5.0 21:02 #navit: < MarcR> wondiws: did you check all dependencies ? - that was my mistake yesterday 21:02 #navit: < wondiws> MarcR, but than it would not install, nor run 21:03 #navit: < MarcR> it installs on my pi, and runs, but i only got a yellow blank screen. even with an 3.5g map file 21:03 #navit: < wondiws> MarcR, exactly 21:04 #navit: < jkoan> wondiws: Navit is highly modular so it will probably always run ;) 21:04 #navit: < MarcR> then I checked the dependencies again, and install navit via package again, and in runs with map 21:04 #navit: < jkoan> Even without grafics Navit is able to run (useful to generate gpx routes) 21:06 #navit: < wondiws> MarcR, I don't get it 21:06 #navit: < jkoan> wondiws: if you are familiar with building from source this would be a good alternative to get all the latest features. MarcR could probably guide you :) 21:07 #navit: < wondiws> I built my own linux distribution when I started using linux ten years ago, but now I prefer to conform to debian packages whenever possible 21:07 #navit: < MarcR> no no, i just followed the step by step guide, until i got an cmake error, then installed navit via apt-get install again, and it works. so not such a good guide type of guy ;) 21:07 #navit: < MarcR> wondiws: same here 21:08 #navit: < wondiws> MarcR, so if I reinstall, it will work? :S 21:08 #navit: < MarcR> maybe 21:08 #navit: < jkoan> KaZeR: probably again you client, please check your private messages ;) 21:08 #navit: < MarcR> i followed this guide 21:08 #navit: < MarcR> https://wiki.navit-project.org/index.php/Raspberry_Pi 21:08 #navit: < MarcR> until the cmake part 21:08 #navit: < wondiws> so the debian package is probably not properly authored 21:08 #navit: < MarcR> then i install navit via package again, and it worked 21:09 #navit: < MarcR> raspian - is based an debian so 21:09 #navit: < wondiws> MarcR, yes, it has pretty much the same packages 21:09 #navit: < MarcR> yep 21:09 #navit: < MarcR> so you could give it a try 21:09 #navit: < MarcR> like me 21:10 #navit: < wondiws> I do have a RPi 21:10 #navit: < wondiws> but I will try and built navit now 21:10 #navit: < MarcR> ^^ 21:12 #navit: < jkoan> wondiws: we hope to get the new version out soon, but for now building from source is the best way to get the best experience 21:12 #navit: < wondiws> jkoan, I'm just experimenting at the moment 21:12 #navit: < MarcR> when cmake works ;-) 21:13 #navit: < jkoan> MarcR: I didn't followed up the end of the cmake discussion, which at was the last problem? 21:14 #navit: < wondiws> completed, but no graphic system available when I try ./navit 21:14 #navit: < MarcR> we figured out, the raspbian jessie is to up to date for the self build at the moment - qt5 don't compile - but its noted now 21:16 #navit: < jkoan> wondiws: what does the summary said, every gui and graphics disabled?! 21:16 #navit: < wondiws> yeah 21:16 #navit: < jkoan> MarcR: really interesting, if I find time I will look into it 21:17 #navit: < jkoan> wondiws: even "null"? 21:17 #navit: < wondiws> I think so 21:18 #navit: < jkoan> If you run cmake at the end you see a summary, do you know where I mean? 21:19 #navit: < wondiws> jkoan, yes, but I think indeed null was disabled, I'm gonna install qt5 first before I try again, but it has thousand-and-one packages, so I don't know which one cmake uses to check 21:19 #navit: < jkoan> https://wiki.navit-project.org/index.php/Raspberry_Pi 21:20 #navit: < jkoan> Look here ;) 21:20 #navit: < jkoan> There is a nice list what you need for which gui and graphics system 21:21 #navit: < jkoan> You must decide one graphics and one gui system ( i really like Sdl for example) 21:23 #navit: < MarcR> holy crap - text to speech is working too, just like that, the console is giving out the tts commands in german atm 21:23 #navit: < wondiws> jkoan, apperantly null is disabled by default 21:23 #navit: < MarcR> saaaweet :) 21:24 #navit: < jkoan> MarcR: are you German? :D 21:24 #navit: < jkoan> wondiws: okay, and the others? 21:25 #navit: < MarcR> yes 21:25 #navit: < MarcR> oh it says "Fix the Tag" so i guess I need to fix it first ;) 21:26 #navit: < jkoan> MarcR: Guten Abend aus Deutschland 21:26 #navit: < MarcR> ernsthaft? :D 21:27 #navit: < wondiws> jkoan, oh, null was enabled, just not for "vehicle" 21:27 #navit: < jkoan> MarcR: yes you need to replace this on the config with your tts command or select another tts engine 21:27 #navit: < jkoan> wondiws: ah OK :D 21:27 #navit: < jkoan> MarcR: ja, ich komme aus Deutschland 21:28 #navit: < MarcR> jkoan: Ich auch :-P 21:28 #navit: < MarcR> NRW 21:29 #navit: < jkoan> Niedersachsen, aber wir sollten bei Englisch bleiben damit alle mit Reden können ;) 21:30 #navit: < MarcR> Stimmt, das ist nur fair. ;) 21:30 #navit: < MarcR> Ok, TTS will come later, need to get another beer first ;) 21:31 #navit: < jkoan> Germans and beer, so much stereotype :D 21:31 #navit: < MarcR> hehe 21:32 #navit: < wondiws> it won't compile, now it find parts of qt 21:32 #navit: < MarcR> wondiws: welcome in the club 21:33 #navit: < jkoan> wondiws: could you do a pastebin of the output? 21:33 #navit: < MarcR> wondiws: my navit works, after i installed it via package then - apt-get install navit. after I checked the dependencies from the step by step guide 21:34 #navit: < jkoan> MarcR: possible a interesting thing for you (because of Germany). Did you know tmc? 21:35 #navit: < MarcR> heard of it, but don't get you atm 21:37 #navit: < jkoan> It's traffic message channel. Traffic messages which comes over the fm radio. I am working to get support to get such traffic related things into navit. It will be a very long way, but we/I working on it 21:37 #navit: < MarcR> aaaah 21:37 #navit: < MarcR> yes yes, have it in my actual radio turned on atm. 21:38 #navit: < MarcR> that would be a monster feature, if navit would get tmc data, and reroute you along traffic jams then. 21:38 #navit: < wondiws> MarcR, I commented out Qt ;) 21:38 #navit: < wondiws> I see a map now 21:39 #navit: < MarcR> your welcome ;) 21:39 #navit: < jkoan> wondiws: nice 21:39 #navit: < wondiws> but I don't live near Munich :P 21:39 #navit: < MarcR> hehe 21:39 #navit: < MarcR> thats only the center start 21:39 #navit: < MarcR> if you you have a gps working , it will get your location 21:40 #navit: < MarcR> and next time navit start, it remembers your last location 21:40 #navit: < jkoan> Munich is the default center because the founder is based around there, but you can change it in the config 21:41 #navit: < wondiws> doesn't it have OSD? 21:42 #navit: < MarcR> just click anywhere on the map left mouse , then you should get the main menu 21:42 #navit: < jkoan> MarcR: I am already in the place to receive rds-tmc messages, but now the big part starts with decoding, and all those. And later we need to integrate it into routing. As I said, long way to go 21:43 #navit: < MarcR> jkoan: sounds like a cool feature :) 21:43 #navit: < ilovekiruna> auch von hier Guten Abend :) 21:43 #navit: < jkoan> wondiws: we also have osd, you must configure it also in the config 21:43 #navit: < wondiws> jkoan, I see it yes, it is included :) 21:44 #navit: < jkoan> ilovekiruna: invasion of germans :D ;) 21:44 #navit: < MarcR> :-D 21:44 #navit: < ilovekiruna> felt like 21:44 #navit: < wondiws> jkoan, so, now I have to set up my Beitian BN-880 21:45 #navit: < jkoan> wondiws: do you need help? 21:45 #navit: < wondiws> jkoan, yes please 21:46 #navit: <@KaZeR> ilovekiruna: saw the webdriver link. nice! putting a note in my backlog about it 21:46 #navit: < jkoan> wondiws: how it is connected to the PC? 21:46 #navit: < wondiws> jkoan, /dev/ttyUSB0 21:47 #navit: < jkoan> You also know the baud? 21:47 #navit: < wondiws> jkoan, 9600 21:47 #navit: <@KaZeR> wondiws: i would suggest poking the debian maintainers for an update on the package. 21:48 #navit: < jkoan> Then it's easy ;) you have everything you need to know 21:48 #navit: < wondiws> KaZeR, maybe I just didn't configure it right 21:48 #navit: < jkoan> KaZeR: for poking the maintainer we need to release something, see pm 21:48 #navit: <@KaZeR> wondiws: i'm quite sure that the version there is quite old :) 21:49 #navit: < jkoan> wondiws: this is what you are searching for https://wiki.navit-project.org/index.php/Configuration/Vehicle_Options 21:50 #navit: <@KaZeR> wondiws: you can use the 'file' vehicle or you can proxy the gps via gpsd 21:50 #navit: <@KaZeR> wondiws: navit's default config is to use gpsd, but it's easy to change 21:50 #navit: < jkoan> KaZeR: do you continue to guide wondiws and MarcR? ^^ 21:51 #navit: < MarcR> I'm fine atm, waiting for the qt5 support for the self build respian jessie build 21:52 #navit: < jkoan> Ah OK MarcR :D 21:52 #navit: < MarcR> looks like there is an issue with my gps neo 6m now. don't know why 21:53 #navit: <@KaZeR> jkoan: didn't want to steal your thunder, just wanted to help :) 21:53 #navit: < jkoan> I also have the GPS neo 6m, what's your problem? 21:54 #navit: < wondiws> jkoan, it doesn't give me errors, but I don't see my neighbourhood 21:55 #navit: < jkoan> Hm okay, do you have the 3d fix? For me first start could take up to 15mins 21:55 #navit: < MarcR> jkoan: it worked super fine, until i deleted my last navit version, and tried to compile it from the build. 21:56 #navit: < MarcR> so its KaZeR fault ;-) 21:57 #navit: < jkoan> Try to check the baud, this was often my problem 21:57 #navit: < MarcR> on it 21:57 #navit: < jkoan> KaZeR: everything's good, I only wanna go to sleep ^^ 21:58 #navit: <@KaZeR> MarcR: :D 21:58 #navit: <@KaZeR> jkoan: i relieve you of your duties! :) 21:58 #navit: <@KaZeR> MarcR: are you using gpsd? 21:59 #navit: < jkoan> Kazer :D 22:00 #navit: < MarcR> KaZeR: I do 22:00 #navit: < jkoan> Good night everybody, see you all tomorrow :) 22:00 #navit: < MarcR> gps device is working but don't get a lock atm . no blinking red led anymore 22:00 #navit: < jkoan> BTW I like that the chat is so active right now, continue this tomorrow 22:00 #navit: < MarcR> jkoan: have a good sleep 22:01 #navit: < jkoan> MarcR: thx 22:01 #navit: <@KaZeR> MarcR: what does gpspipe -r says ? 22:03 #navit: < MarcR> {"class":"VERSION","release":"3.16","rev":"3.16-4","proto_major":3,"proto_minor":11} 22:03 #navit: < MarcR> {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/serial0","driver":"u-blox","subtype":"URANUS4_4.3.0.5_2017-01-10-FFF0","activated":"2017-10-26T22:02:23.992Z","flags":1,"native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00,"mincycle":0.25}]} 22:03 #navit: < MarcR> {"class":"WATCH","enable":true,"json":false,"nmea":true,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false} 22:03 #navit: < MarcR> $GPTXT,01,01,01,ANTENNA OK*35 22:03 #navit: < MarcR> and so on 22:04 #navit: < MarcR> I think i deleted a package which i don't had to - I don't know :'-( 22:05 #navit: <@KaZeR> is your device really on /dev/serial0 ? that's uncommon 22:07 #navit: < MarcR> minicom also gives out the same output like gpspipe 22:08 #navit: < MarcR> all tutorials that i found said that the neo 6m via the gpio pins at the pi, an raspbian jessie will work as serial0 22:08 #navit: < MarcR> and it work, until today :-P 22:14 #navit: <@KaZeR> oh ok 22:14 #navit: <@KaZeR> usually it's something like /dev/ttyAMA0 for the serial port using the pi GPIO 22:15 #navit: <@KaZeR> you have a pi2 or a pi3? 22:15 #navit: < MarcR> pi3 22:16 #navit: <@KaZeR> ok (this is for the qt5 image) 22:16 #navit: < MarcR> maybe i have made a mistake with gps - checking it atm 22:17 #navit: <@KaZeR> for your gps problem, i'd stop gpsd, unplug the gps, replug it and start gpsd with 'gpsd -N -d9 /dev/serial0' to reinitialize the device and get the gpsd logs 22:17 #navit: <@KaZeR> you're 100% sure about the serial port, right? 22:18 #navit: < wondiws> where is the NAVIT_SHAREDIR? 22:18 #navit: <@KaZeR> it'll depend upon how you installed navit. you compiled from sources, right? 22:19 #navit: < MarcR> KaZeR: replug ? hm so i have to re plug the cords to the gpio 22:19 #navit: < wondiws> yes 22:19 #navit: < wondiws> I think i got it 22:19 #navit: <@KaZeR> wondiws: did you run 'make install' or are you running from sources? 22:20 #navit: < wondiws> KaZeR, running from source direcotry 22:20 #navit: < MarcR> oh - neo is firing up again ! 22:21 #navit: <@KaZeR> ok. then it should be the `navit` subfolder in the directory where you ran cmake 22:21 #navit: <@KaZeR> MarcR: nice! 22:21 #navit: < MarcR> red led blinking so gps lock 22:24 #navit: < wondiws> ah, got it, I had to write an *.xml file 22:24 #navit: <@KaZeR> wondiws we actually have a branch in the repo that will take care of the download and the map activation for you.. should be finished soon 22:28 #navit: < wondiws> wow, the map even shows benches 22:29 #navit: < wondiws> and our shed 22:29 #navit: < MarcR> the openstreetmap version is cool 22:30 #navit: < MarcR> it even shows the house numbers 22:30 #navit: < MarcR> no other navi does that 22:33 #navit: <@KaZeR> wondiws: you can even shot electric pylones if you want :D 22:33 #navit: <@KaZeR> technically we could also draw the stop lines on the roads and things like that 22:33 #navit: <@KaZeR> not shot obviously, show :) 22:34 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 22:35 #navit: < wondiws> KaZeR, I know understand the ballooning filesize 22:36 #navit: < wondiws> how is my position displayed? 22:36 #navit: < wondiws> I don't get an error that it can't open /dev/ttyUSB0 22:36 #navit: < wondiws> which I did get previously when it didn't have the rights 22:36 #navit: < wondiws> so now apperantly it does open it 22:37 #navit: < MarcR> there should be a green circle on the map 22:37 #navit: < MarcR> that is your gps position 22:38 #navit: < wondiws> MarcR, it doesn't work ofcourse :P 22:38 #navit: < MarcR> there is an option to show your gps satellite locks at the osd 22:39 #navit: <@KaZeR> also, if you click in the action menu, the submenu will show two sets of coordinates : under the globe it's where you are looking at, under the vehicle it's the position from your gps 22:39 #navit: <@KaZeR> wondiws: nothing in the console? (navit isn't really good today at reporting errors in the UI) 22:40 #navit: < wondiws> KaZeR, no problems in the console 22:40 #navit: <@KaZeR> ok. how about the action menu ? 22:41 #navit: < MarcR> looks like i don't fix my gps problem 100% - but i have to sleep now, see you later guys. 22:41 #navit: <@KaZeR> bye MarcR we can resume tomorrow 22:41 #navit: < MarcR> it's fun to work with you 22:41 #navit: <@KaZeR> :D 22:41 #navit: < MarcR> would be great - all of you have a good sleep ! 22:42 -!- MarcR [~MarcR@p5DD9111B.dip0.t-ipconnect.de] has quit [] 22:42 #navit: <@KaZeR> wondiws: https://wiki.navit-project.org/index.php/File:InternalGUI-Actions.png here there's no valid gps as you can see 22:43 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 240 seconds] 22:46 #navit: < wondiws> now we need 3d models of buildings in the maps ;) 22:47 #navit: < wondiws> KaZeR, what does a valid GPS look like in the Actions menu? 22:47 #navit: <@KaZeR> yeah :) want to help? :) 22:47 #navit: <@KaZeR> wondiws: looks like coordinates, just like the coordinates under the globe 22:48 #navit: <@KaZeR> what are the permissions on your gps device? 22:48 #navit: <@KaZeR> wondiws: first time users feedback is super important for us to help us improve! 22:48 #navit: < wondiws> KaZeR, I tried with root first 22:51 #navit: <@KaZeR> still using root? 22:52 #navit: <@KaZeR> grep "vehicle " navit.xml ? 22:53 #navit: < wondiws> bbl 22:53 -!- wondiws [~Jasper@5ED7DF59.cm-7-8d.dynamic.ziggo.nl] has quit [Quit: Leaving] 23:02 -!- wondiws [~Jasper@5ED7DF59.cm-7-8d.dynamic.ziggo.nl] has joined #navit 23:33 -!- Horwitz [~mich1@p200300800E648501022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 23:46 -!- Horwitz [~mich1@p200300800E475901022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 23:46 -!- mode/#navit [+o Horwitz] by ChanServ --- Log closed Fri Oct 27 00:00:53 2017