AsteroidOS IRC Logs

Privacy Policy

Search:

03:00:39Haelge<jrt[m]> "Someone using a SailfishOS 4..." <- SailfishOS 4.3.0.12 on Xperia 10 + Fresh Install of prebuilt AsteroidOS on bass:
03:00:39Haelgetl;dr: Starship does not work for me out of the box. I had an older starfish installed which was working fine (https://github.com/AsteroidOS/starship/issues/9#issuecomment-926962170)
03:00:40HaelgeFirst I installed Starship alongside Starfish (propably not the best Idea)
03:03:06HaelgeI established the connection between the phone and the watch but the app did not show an active connection. After restarting the service the "Connecting Page" flickers, but still no active connections shown.
03:04:34HaelgeSame behaviour after uninstalling starfish and after uninstalling both and reinstalling starship.
03:09:19HaelgeHowever after installing starfish alongside starship, i was able to restart services and found the active connection to my watch. (The "Connecting Page" was not flickering but shown for a plausible amount of time)
03:12:09HaelgePropably I simply started starfish with the starship desktop file? (Although the "about page" clearly states starship)
03:56:38HaelgeAfter removal of both apps, restart and clean install of starship I get the following Warn and Debug Logs right after Application start:
03:56:39Haelge[W] unknown:0 - Could not connect to asteroidsyncserviced. (5x)
03:56:39Haelge[D] initService:79 - Service file version ( 1.0 ) is not equal running service version (  ). Restarting service.
03:58:22HaelgeDoing the same procedure with the above mentioned version of starfish does not provide such log entries.
09:23:24marcdw[m]Man, I was so hoping to test the app. SailfishOS 4.2 on Pinephone. Been awhile since I booted. Figured I'd do a zypper ref & dup. All good.
09:23:24marcdw[m]On reboot I find I can't launch a single app. Nothing will launch at all. Not sure what that's about but won't be dealing with it anytime soon. Oh well.
15:32:15beroset[m]Today I'm working on creating a synchronization daemon that runs on Linux (Fedora and Raspberry Pi OS are my intended targets).
15:39:15eLtMosen[m]> <@marcdw:matrix.org> Man, I was so hoping to test the app. SailfishOS 4.2 on Pinephone. Been awhile since I booted. Figured I'd do a zypper ref & dup. All good.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/5da67a53e01c8fdbc85d58d20225974a1ee97f52)
15:41:56PureTryOut[m]<beroset[m]> "Today I'm working on creating..." <- Cool! What are you going to use the frontend? I was thinking of writing a Kirigami one at some point but haven't started yet
15:42:53kido[m]<beroset[m]> "Today I'm working on creating..." <- This should work https://github.com/AsteroidOS/asteroidsyncservice :)
15:43:03beroset[m]I'm not sure I understand the question. Since it's a daemon, it will have no gui.
15:43:26kido[m]It is what we use for both Ubuntu Touch and SailfishOS, there’s no reason why it wouldn’t work on desktop Linux too
15:43:46beroset[m]I looked at that, but want to make some significant changes in architecture.
15:44:04kido[m]What kind ?
15:44:19kido[m]And would they make sense on mobile Linux too ?
15:45:48PureTryOut[m]beroset[m]: Ah sorry I misunderstood
15:46:34PureTryOut[m]Then I'm not sure why you wouldn't just use https://github.com/AsteroidOS/asteroidsyncservice as kido said. That is already used on mobile devices as well
15:46:40beroset[m]Mostly, I want to have a more sharply defined interface. I want to isolate all of the Qt and bluetooth bits and keep them separated so that if, for example, we go with Qt6 at some point, it's easier.
15:48:43kido[m]I’m not suggesting that the current asteroidsyncserviced code base is good. I just think it’d be best if you were to improve it (maybe even rewrite it if the refactoring is too large) rather than duplicate it
15:49:19kido[m]If your goal is to build asteroidsyncserviced but nicer please do it but let’s make sure we don’t end up with two redundant projects :)
15:49:56beroset[m]I'm not averse to that at all. I just don't know anything about Ubuntu touch or Sailfish and so I would likely break things.
15:50:43kido[m]The « platform » code in the current codebase is fairly well separated so it should be relatively easy to refactor
15:51:17beroset[m]Ok, this kind of conversation is why I mentioned it here. :)
15:51:40kido[m]Sure, thanks for mentioning it :)
15:51:49beroset[m]I have only begun the design work, so nothing is lost.
15:52:15beroset[m]I also intend to use CMake instead of Qtmake
15:52:40PureTryOut[m]Yes please
15:52:57kido[m]Sure
15:53:07PureTryOut[m]I already converted most projects to CMake, this one needs to as well
15:54:13beroset[m]I would also propose to use `libasteroid`.
15:54:24beroset[m](Which I've already converted to cmake)
15:56:56beroset[m]It's going to be a large pull request in about one week if it goes as planned.
16:02:02marcdw[m]> <@m0sn:matrix.org> There has been two builds of sfos 4.2 for pinephone.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/064c107ce62f07b66d35ee831672e5a2c8b40e43)
16:03:19marcdw[m]s/Thanks. I joined the channel and posted there. 👍/Thanks. That's the version I'm using. I joined the channel and posted there. 👍/
17:14:53beroset[m]When building `asteroidsyncservice` following exactly the instructions here: https://github.com/AsteroidOS/asteroidsyncservice it doesn't find `version.pri` unless I remove the leading `../` from the `.pro` file reference to that file.
17:15:13beroset[m]Is that unique to my computer somehow or can someone else verify that behavior?
17:18:23beroset[m]In fact, I don't seem to be able to get it to build at all. <sigh> So step one is fixing the build.
18:27:15MagneFire[m]<beroset[m]> "Is that unique to my computer..." <- Yes, getting the same error. The `version.pri` one seems to be straightforward to solve though?
18:27:40MagneFire[m]I have it completely compiled on Arch, but it's failing to `ListAdapters` atm
18:27:51beroset[m]Yes, but then it doesn't build because `VERSION` isn't actually defined.
18:28:20beroset[m]I just hardcoded the literal string "1.0" to get it to compile for now.
18:28:51beroset[m]I don't want to waste time troubleshooting Qtmake issues when I plan instead to replace it with CMake anyway.
18:29:09MagneFire[m]beroset[m]: But it is though? Looking at the `version.pri` it seems to be set there
18:29:09beroset[m]And I know how to do that properly with CMake
18:29:15*MagneFire[m]posted a file: compile_fix.patch (2KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/KlRMeDoSHjGUfJClKomTBghn >
18:29:36MagneFire[m]^ Patch that fixes the pri and compilation for me, targeting the ubuntu platform
18:29:57beroset[m]I'll try that. Thanks!
18:30:54MagneFire[m]Build instruction for Arch:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/9265946ed166ef5ee8f21479988a176eb6babbc3)
18:31:03MagneFire[m] * Build instruction for Arch:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/941e16449616e9f41293bce6da885d3569f3e64c)
18:31:26MagneFire[m]The daemon will be under: `build/asteroidsyncserviced/asteroidsyncserviced`
18:31:58MagneFire[m]beroset[m]: So port CMake when? 😅
18:32:40beroset[m]Today.
18:34:13beroset[m]Your patch worked perfectly for me. Thanks!
18:41:17eLtMosen[m]Somehow i am glad now 2.0 missed the xmas window 😅
18:41:17eLtMosen[m]Updating VLC be like
18:41:25*eLtMosen[m]uploaded an image: (1320KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/RVbFJdMygipdemtSFEwkHQnZ/image.png >
18:50:12MagneFire[m]> <@m0sn:matrix.org> Somehow i am glad now 2.0 missed the xmas window 😅
18:50:12MagneFire[m]> Updating VLC be like
18:50:12MagneFire[m]Why are you glad about that? I really want a release out asap now. Taking too long there's very little we have to do I think (Only the settings slowness and adding watchfaces)
18:50:54beroset[m]I think he means that with many of us having time off work to work on toys, progress is coming rapidly.
18:51:03MagneFire[m]I remember wanting a release last year. Time flies ;)
18:52:00eLtMosen[m]MagneFire[m]: I was just refering to the silly xmas theming some projects do.
18:52:00eLtMosen[m]Just glad we are not tempted to do that 😁
18:53:05MagneFire[m]We can do a new years eve release or something 🤣
18:53:53MagneFire[m]s/eve//
18:53:58eLtMosen[m]We could pretend to be waiting for some asteroid to pass or get into observable distance. haha
18:54:21beroset[m]"an Asteroid is coming!"
18:55:29eLtMosen[m]Also, for people that wonder why no news for 3 years.
18:55:29eLtMosen[m]*Asteroids travel steady but sometimes leave observable distance*
19:00:50eLtMosen[m]https://www.jpl.nasa.gov/asteroid-watch
19:01:12*eLtMosen[m]uploaded an image: (2108KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/FOnlLRNgSlBaPiiCbUaXvoGr/image.png >
19:01:58MagneFire[m]I like it!
19:02:42MagneFire[m]Remove `WATCH` and it looks great! Or add some of the well supported watches on top of that, such that the asteroid becomes part of the background
19:06:38eLtMosen[m]Begs the question, is there any banners or other PR things for 2.0 already?
19:06:38eLtMosen[m]I did not follow who did the coool video for 1.0.
19:06:38eLtMosen[m]Is such a thing planned again for 2.0?
19:07:29MagneFire[m]No. No idea and no idea
19:07:46MagneFire[m]Was wondering who did the 1.0 video too. It looked soo smooth
19:08:46eLtMosen[m]I figure it was done in some framework. But honestly, hats off. That Video alone would be a weeks job for me...
20:06:33beroset[m]<eLtMosen[m]> "I figure it was done in some..." <- Better start now then. ;)
20:09:54beroset[m]Seriously, though, planning for PR things for 2.0 is a really good idea.