[00:35:06] *** Quits: Horwitz (~mich1@freenode-f65vg2.mg0r.l642.hujoc9.IP) (Ping timeout: 120 seconds) [00:49:06] *** Joins: Horwitz (~mich1@freenode-50hdke.jped.b38b.hujoc9.IP) [01:15:03] *** Quits: j_f-f (~quassel@freenode-3p0.0bl.0e6ebh.IP) (Connection closed) [01:18:44] *** Joins: j_f-f (~quassel@freenode-3p0.0bl.0e6ebh.IP) [10:23:00] [discord] i think my screen just died 😢 [10:23:47] [discord] it was working perfectly yesterday at night, and today i can't get it to turn on, no matter what i plug it to... The display controller seems to get hot and thats all [13:00:13] [discord] any plans on getting navit multicore friendly ? its only hitting one core of my pi [13:05:23] [discord] i tried zooming out and navit froze, its stuck using 1 core at 100% [13:31:22] [discord] there was already some work in this field, see here: https://github.com/navit-gps/navit/issues/760 [13:35:11] [discord] inceasing graphics memory did imporve the sitation slightly, but as soon as the zoom level gets too low it starts getting very slow to respond [13:36:53] [discord] it might be worsened by the fact that im running a demo navigation at the same time too [13:41:00] [discord] hmm i dont feel confortable enough to mess with mvglasow's fork and make it run for me :/ [14:15:59] [discord] @Bizzmark which pi did you have ? i find my 3b+ to be near unusable :/ [14:17:15] [discord] 4 4GB [14:17:50] [discord] hmm, zooming out more than a few times causes severe hang outs [14:20:07] [discord] Mine's okay. Slow-ish to respond, but doesn't really hang. Except when it crashes. I know it's not my Pi because all other apps are fine, even 1080p video, and OAP maps are perfectly responsive. [14:21:11] [discord] hmm im afraid i might end up havin to use something else [14:21:28] [discord] its really weird [14:23:03] [discord] BTW Guys, I really like that this chat feels alive with you all writing :) Thx [14:23:19] [discord] haha you are welcome ! im glad [14:23:29] [discord] Possible you could tweak some things [14:23:34] [discord] Sorry, but I've found the same jankiness with Navit, just maybe a bit less so because my Pi 4 is a little more powerful. That, plus the fact that my GPS module takes at least 30 minutes to get a lock and can't do so indoors, is why I use OAP as my primary. [14:23:42] [discord] Possible you could tweak some settings [14:23:56] [discord] i just hope i was giving better new tho, today is a downer... first my touchscreen dies with no warning, then this [14:24:18] [discord] i dont have such problems with my module [14:24:35] [discord] hmm what do you have in mind ? [14:25:20] [discord] when i see on what kind of potato you can run navit builds it really bugs me away as to why it would become so unresponsive as soon as i start zooming out, i may have done something wrong [14:25:46] [discord] i feel like it just gets overwhelmed by how much data it suddenly has to process [14:26:27] [discord] You can remove details from the layout so it will not be rendered [14:27:10] [discord] hmm how can i do that ? [14:27:31] [discord] wouldn't it hurt usuability too ? [14:29:11] [discord] Edit the layout or create a copy (and edit its name). You would need to remove map features or change when they are displayed [14:29:33] [discord] Not always, but it would change its look [14:30:31] [discord] thats fine, depending on how much it changes [14:30:49] [discord] im going to dig deeper into this [14:31:02] [discord] what are you usually running navit on ? [14:32:39] [discord] I did find mine runs a lot better with POI icons turned off. If this doesn't disable them being processed behind the scenes, maybe I could get even more performance. [14:33:55] [discord] As for GPS modules, a regular one does take that long to get a lock. If you have one that takes a SIM card for assisted GPS (triangulation, like a cell phone), that's more like a few seconds, but I can't justify having a second cell phone plan just for my GPS, and most are GSM only which is less common in the US. [14:34:37] [discord] my usb one takes like 20 sec at worse 🤔 no sim trickery [14:35:38] [discord] @jkoan i remembered that there was already a layout called simple so i went and tried this one first. Same issue using this one [14:36:11] [discord] its just freezes once i get to a scale of 5KM, idk how i can see zoom levels to be more accurate [14:36:58] [discord] External? Must have a decent antenna. I only have a small external antenna glued to the inside of my project box. Or maybe Ozzmaker actually sucks. [14:37:38] [discord] its a cheap round thingy i got from aliexpress, 10€ [14:38:20] [discord] link? [14:38:21] [discord] how did you go and turn off POI icons ? [14:38:44] [discord] In the menus, actually.. I looked for it in the XML but couldn't find the reference, so I just found it in the in-app menus somewhere [14:38:48] [discord] Settings probably [14:39:14] [discord] https://fr.aliexpress.com/item/32947709096.html?spm=a2g0o.productlist.0.0.4c75c703dW3msm&algo_pvid=2eb3a651-30dd-47d1-8e49-d00c42f95b7f&algo_exp_id=2eb3a651-30dd-47d1-8e49-d00c42f95b7f-3 [14:39:14] [discord] i think thats the one, or one very similar [14:40:09] [discord] ah yeah, thats a problem 😂 i have lost the settings menu ever since im using the up to date build version [14:41:06] [discord] now its even struggling to go full screen 😢 [14:41:10] [discord] tf is going on [14:42:40] [discord] idk, it does sound more broken for you than it should b [14:42:42] [discord] idk, it does sound more broken for you than it should be [14:43:45] [discord] yeah im really lost as to what on earth is going on here, a pi 3b+ is certainly not a strong device, but it should be enough [14:44:13] [discord] im going to try something... [14:52:35] [discord] @jkoan excuses the pings, but i found somehting intresting [14:52:52] [discord] the issue is non existant on the older apt version [14:53:44] [discord] so either something has changed in the new build that my pi *does NOT* like *at all*, or my custom osd (not too fancy...) is messing it up [14:54:40] [discord] changing zooms is still a bit on the slower side, but in a lot more reasonable way [14:54:55] [discord] any idea ? [15:05:09] [discord] after disabling all my osd items but zoom in/out buttons i do have a usuable up to date navit [15:05:37] [discord] no trying to figure ou if one of my osd items was fucking everything up or if it was the amount i had active [15:08:19] [discord] now trying to figure ou if one of my osd items was fucking everything up or if it was the amount i had active [15:09:57] [discord] also, would a smaller map (eg : only my country instead of all europe) improve performance ? [15:27:16] [discord] Sorry, not sure. jkoan can probably help more here. My guess is a smaller map would only affect startup time; I have all the US and some central/south America on my map, and it's not bad once it's started [15:28:10] [discord] Were you using something like the Ozzmaker icons & config? [15:28:25] [discord] yeah but OSM maps are not balanced : france is already bigger than the USA in terms of download size [15:29:13] [discord] yeah i followed the same tutorial as you did i think, im slowly adding back OSD items to test when navit starts freaking out [15:29:31] [discord] That doesn't seem quite right.. France is smaller than like 5 of our states. More roads, sure, but more than the whole US? lol [15:29:57] [discord] yeah, OSM is a european project (not sure, dont quote me) [15:30:06] [discord] western europe is close to 20GB [15:31:24] [discord] france only download [15:31:25] [discord] https://cdn.discordapp.com/attachments/500190750085087235/860543183603630141/unknown.png [15:31:37] [discord] USA only download (without alaska and hawaii) [15:31:38] [discord] https://cdn.discordapp.com/attachments/500190750085087235/860543239613710336/unknown.png [15:31:52] [discord] my bad, not bigger but close [15:33:46] [discord] That does explain some things I noticed missing in my town alone [15:34:22] [discord] yeah world coverage with OSM is far from perfect [15:34:36] [discord] its more advanced in europe probably because more people contribute to it [15:43:38] [discord] @jkoan see anything wrong with this OSD item ? [15:43:39] [discord] ```xml [15:43:40] [discord] [15:43:42] [discord] ``` [15:44:01] [discord] looks like this is what's slowing me down [15:44:47] [discord] lool poor jkoan will come back to his discord with a bilions notifications from me 😂 [15:56:24] [discord] Most of the time Linux and android. But I also have TomTom devices and wince devices. I have a whole lot of devices. One project which @ilovekiruna and I still need to do is the device farm for Android for automatic tests of navit. [15:57:24] [discord] It only takes long if you need to wait for it to download the "Almanach" which takes about 12min [15:58:07] [discord] Most GPS have the option to include or add a small battery which is used to keep the Almanach [16:00:23] [discord] Not right now [16:01:01] [discord] Actually it can yes [16:04:20] [discord] Depending on the graphics plugin it's possible that OSDs are andeled different. For example on SDL they are handled with overlays. Also it's possible to use navit with a X server directly on framebuffer which shaves off a few wlextra steps. But I don't know which plugin this was. Probably the egl [16:05:27] [discord] I think it was stated within Germany which explains why here sometimes single trees are mapped [16:06:08] [discord] You got an empty command, don't know if this is a problem [16:06:24] [discord] This is okay :D [16:14:43] [discord] right, i hope I find in or after august some time for this [16:14:53] [discord] right now the Rpi is used for other things [16:15:29] [discord] I probably got enough pi's on my side [16:15:55] [discord] The biggest problem could be proper management [16:17:22] [discord] you mean how to manage the different nodes? [16:18:16] [discord] I meant what kind of hardware, mostly cpu power [16:18:47] [discord] Ok i'll consider getting France only [16:18:49] [discord] most of the devices in the farm will be older android phones [16:19:50] [discord] Aight, so my pi3b+ should be plenty then [16:20:44] [discord] it was along with this : [16:20:45] [discord] ```xml [16:20:46] [discord] [discord] />``` [16:21:09] [discord] these two are supposed to be displaying routing status (routing, calculating etc) [16:22:02] [discord] i left this one active and my navit works fine, just i no longer have the button (the line i showed earlier) and thus can't see guidance status anymore [16:23:21] [discord] but i was able to reliably repeat the issue, this makes navit freak out. At close zoom it works fine, but zooming out becomes slower and slower untill past a certain zoom level it just completely stands still with one core pegged at 100% [16:23:38] [discord] i tried to wait to see if it would get unstuck but gave up after around 10min [16:32:46] [discord] without it, the first zoom levels take around 1.5/2sec to load, and further out levels are around 3. [16:32:48] [discord] With it, the close ones are like 4 sec rapidely increasing untill freezing [16:51:52] [discord] "close ones" as in closer to the ground? [16:53:50] [discord] yes [16:53:56] [discord] bigger zooms if you prefer [16:54:09] [discord] sorry there was a type/autocorrection. I meant power management [16:55:10] [discord] those are just on power supplies, dont understand what you mean. [16:55:23] [discord] i can give you screeshots, or even show you live if you prefer it might be easier [16:56:47] [discord] i mean i think having about 3-4 Raspberry pis with all the cables will be a mess, and probably i dont even have enough usb cables to wire up all thos devices [16:57:18] [discord] for this purpose I got an active USB-Hub [16:57:53] [discord] i will try to replicate it on my machine, this way i can even debug the code [16:58:29] [discord] but this also has a limit on hay many amps it can deliver which can/will be a problem with ~15 phones [16:58:52] [discord] thats my bad for using code thats not mine without proper testing tho, it was just out from a tutorial on the net [16:58:58] [discord] might be something badly formed here [16:59:10] [discord] ofc, but still better than running all directly from the rpi [16:59:49] [discord] I would also expect in standby those wont draw too extensive currents [17:00:42] [discord] probaly you are right, but its a cable mess any how [17:01:04] [discord] cable management nightmare are life guys [17:02:11] [discord] i already thought about taking all of the devices apart and just use the mainbords directly. Even without screen, wifi, battery, ... [17:03:00] [discord] I dont think those are needed, so could work, but then a serial connection would be grate to do maintenance it needed [17:19:19] [discord] i re used the documentation's example for naviagtion status. Works just fine [17:19:43] [discord] i guess the guy who did the code i used was making something more complicated that navit doesnt like [17:40:12] [discord] Could you please provide the full osd where the error happens? Or is it the one where command="" ? [17:43:04] [discord] ```xml [17:43:05] [discord] [discord] /> [17:43:19] [discord] [17:43:20] [discord] ``` [17:43:22] [discord] these two were working together for displaying navigation status [17:43:32] [discord] commenting the last one stopped the freezing from happening [17:43:59] [discord] i dont have the osd setup as it was when it was failing anymore so thats all i can provide [18:21:32] [discord] can we still access legacy gui menus ? for example i think there are some missing menus in the current build that i'd like to have (eg : go from car to car_avoid_tolls) but i cant figure how [18:24:33] [discord] same idea for a stop navigation button or a search place button [18:25:38] [discord] although for these two i can always as last resort make a spawn command that would mimic pressing CTRL+S and CTRL+D [21:18:59] [discord] hey its me again 😅 im trying to make a button appear only when guiding (actually, a button that changes based on navigation state would be better). I tried using osd_configuration for that. It worked.... sorta. For some reason, unlike navigation_next_turn types for example, buttons seem to be needing a redraw of the OSD to be displayed properly. [21:18:59] [discord] EG : two buttons with different icons, one with osd_configuration=1 and one with 2. We start the app in config1 (not navigating) and the button corresponding is here. If we change (now not navigating), button for 1 stays and button for 2 doesnt appear. If you pan the map around, or in general just trigger an osd redraw, button 1 will dissapear as expected and button 2 will appear [23:40:45] [discord] Mine - and several others - advertised a 10-15+ minute fix time depending on weather etc., and while mine does have a small battery, it only holds the bearings for up to 4 hours. I'd like to work a way to use my 4x 18650 batteries into that, but I doubt it's feasible unless I keep my UPS on and continuously powering the Pi (it supplies 3v even when shutdown) [23:41:26] [discord] I bet those USB units that you can put in a windshield do work faster, but I settled for something that fits inside my project box. If it's really a few seconds, though, maybe I'll reconsider.. and glue it to the top or something 🙂 [23:43:57] [discord] Get your screen working again? If it's defective, definitely get a refund