Search:
| 02:35:51 | DrDouchebag[m] | Newbie here but interested in switching from Samsung since I got graphene os on my phone. Which is the best watch for asteroid right now? |
| 03:12:48 | totalsonic1[m] | <DrDouchebag[m]> "Newbie here but interested in..." <- I'd recommend TicWatch C2+ (skipjack), LG G Watch R (lenok), LG G Watch Urbane (bass) and Huawei Watch gen1 (sturgeon) - all work well with AOS. The TicWatch is the most recent and has the best hardware specs, the LG watches have working compass app, the Huawei has the more elegant build to it. |
| 04:17:08 | beroset[m] | <dodoradio[m]> "so I was just messing with..." <- I think you're right that needs changing. |
| 04:18:12 | beroset[m] | Also, my prototype version of the timezone setting addition to asteroid-settings is here: https://github.com/AsteroidOS/asteroid-settings/pull/63 |
| 04:19:22 | beroset[m] | It does what it's supposed to do, but isn't pretty yet, and as I mentioned earlier, D-Bus is not allowing the ceres user to set the timezone. I haven't figure out what mechanism is preventing that, nor how to address it. |
| 08:44:48 | eLtMosen[m] | Pardon my ignorance in this 😅😇 Is the problem solved where setting a timezone breaks the time sync with the AOSSync Android app? I have no details on the root cause, but its noted as a warning in the usfull commands section where manual setting of a timezone is explained? |
| 08:55:33 | dodoradio[m] | <eLtMosen[m]> "Pardon my ignorance in this..." <- I think the issue is that the asteroidossync app will transmit the local time and a timezone setting on the watch will result in the watch having an offset from real time |
| 08:58:17 | eLtMosen[m] | And another curious time thing i noticed. I flashed tetra yesterday, and it had correct date and time only off by one hour directly on first boot. Where i never set any date/time manually. Is that due to sw_clock too? Or am i hallucinating?!? |
| 09:00:47 | dodoradio[m] | eLtMosen[m]: That sounds fine, timezone is usually correctly set by android just after flashing. Problems with offset start later, but those are what swclock fixes |
| 09:02:53 | eLtMosen[m] | Thats so cool tbh. All i experience as of yet was that time/date was set to that ominous feb 24th(?) at 17:42. But did not flash watches since sw_clock was introduced |
| 09:02:56 | dodoradio[m] | there exists https://www.bluetooth.com/specifications/specs/current-time-service-1-1/ to which we could potentially move to - it includes characteristics for timezone offsets but still works with local time by default, like our current system |
| 09:04:10 | dodoradio[m] | Alternatively we could add an additional characteristic to our time profile which sets a similar timezone offset, while still transmitting the local time |
| 09:04:43 | eLtMosen[m] | Worldclock Watchface incoming :P |
| 09:06:07 | dodoradio[m] | dodoradio[m]: beroset MagneFire kido opinions? |
| 09:11:10 | kekskopf[m] | Hi everybody, I would like to know what is the status of starfish, the asteroidos client for sailfish os. As far as I know there is no package released in Openrepos. Is there a working version of that? |
| 10:01:49 | kido[m] | <dodoradio[m]> "beroset MagneFire kido opinions..." <- yup, if there's a standard protocol then we should use it ;) |
| 10:02:04 | kido[m] | standard protocol that addresses our needs* |
| 10:18:48 | eLtMosen[m] | <kekskopf[m]> "Hi everybody, I would like to..." <- Hey! Starship development has not seen any progress since you last asked. There was a partly working build attached to the git comments but you sure have seen that already since a year passed since that. And frankly, nobody has asked about it in the past year 🙈 Afaiu, there could be a possibility to integrate AsteroidOS watches into adam piggs Amazfish. Since afaiu that relys on |
| 10:18:48 | eLtMosen[m] | Gadgetbridge support. And GB support for AsteroidOS watches has been merged a month ago and should be available in next GB release. |
| 10:18:48 | eLtMosen[m] | https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3013 |
| 10:30:26 | kekskopf[m] | wow, Gadgetbridge support is a great improvement. Does piggz usually pull updates in Gadgetbridge to amazfish? Maybe I should nagg him... |
| 11:12:16 | eLtMosen[m] | I think we could do a little research upfront to not offload all the work to him 😅 |
| 11:12:16 | eLtMosen[m] | From a quick glance at the repo it does not look like its as easy as him pulling things from GB. But with AsteroidOS in Gadgetbridge, it looks to me like we would have a good basis at least to make integration into amazfit possible. He actually asked back if it would not be easier to integrate AOS watches into Amazfit instead of having a standalone client. When i nagged him regarding a question to starship. This where his short instructions |
| 11:12:16 | eLtMosen[m] | and i have not followed up. I think its our move now :P |
| 11:12:17 | *eLtMosen[m] | uploaded an image: (22KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/fTKQpLkXKCJIxlhSUIRMXvva/image.png > |
| 12:55:10 | kekskopf[m] | this abstractDevice Interface has to be implemented where? in amazfish? And what programming language would that be? |
| 13:04:42 | LunaJernberg[m] | Swedish 100% done again |
| 13:07:32 | kekskopf[m] | ok, looks like the first four files from |
| 13:07:32 | kekskopf[m] | harbour-amazfish/daemon/src/devices/ |
| 13:07:32 | kekskopf[m] | need to be specified for a device to include it |
| 15:09:08 | beroset[m] | <dodoradio[m]> "beroset MagneFire kido opinions..." <- I just read through the specification and I think it would not be very difficult to support this. Does Android or iOS support this? |
| 15:26:03 | beroset[m] | I just answered half of that question -- yes, iOS implements Current Time Service over Bluetooth. |
| 15:29:31 | dodoradio[m] | beroset[m]: If ios supports a standard protocol, android probably supports it |
| 15:31:31 | dodoradio[m] | * I can't find anything quickly for that |
| 15:32:41 | beroset[m] | Here's what I did: I paired my iOS phone to a Linux laptop using bluetoothctl and observed the supported UUIDs. |
| 15:35:12 | dodoradio[m] | beroset[m]: Hmm, I'll try that |
| 15:50:23 | dodoradio[m] | <beroset[m]> "Here's what I did: I paired my..." <- hmm, I don't see anything when running `bluetoothctl` -> `menu gatt` - |
| 15:50:24 | dodoradio[m] | * `menu gatt` -> `list-, * -attributes [phone mac]` |
| 15:52:17 | beroset[m] | You have to pair from the phone to the computer for the latter to act as a peripheral device. |
| 15:52:59 | dodoradio[m] | beroset[m]: hmm, I'll try again |
| 15:53:31 | beroset[m] | When you pair them, the phone will list its services but they go by quickly. After the devices are paired and connected, you can just type info from the main menu. |
| 15:57:43 | dodoradio[m] | beroset[m]: ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/469186fb93cc1c865de1a8a7660937a8c4c12f03>) |
| 15:58:20 | beroset[m] | Too bad. It doesn't appear to be listed there. |
| 15:58:32 | dodoradio[m] | beroset[m]: eh, we can implement it easily enough |
| 15:58:46 | dodoradio[m] | the fact that ios supports it is already good enough reason to add support for it |
| 15:58:59 | beroset[m] | I agree. Looking into that now... |
| 16:01:39 | dodoradio[m] | <LunaJernberg[m]> "Swedish 100% done again" <- oh, you're back - did you get kicked by the power tripping irc bot? |
| 16:01:54 | dodoradio[m] | s/you're/welcome/ |
| 17:01:57 | dodoradio[m] | I think I've fixed the suspend issue on koi |
| 17:10:49 | dodoradio[m] | After digging through mce code a bit I've come to the conclusion that MCE relies on the kernel autosuspend. And I've discovered that CONFIG_AUTOSLEEP was disabled in defconfig... 🤔 |
| 17:13:30 | dodoradio[m] | and it looks to be working correctly. I'm currrently at 71% charge, I'm going to wear it until the end of the day and see how much battery drains and check for any stupid errors |
| 17:14:50 | dodoradio[m] | s/CONFIG_AUTOSLEEP/CONFIG_PM_AUTOSLEEP/ |
| 17:20:35 | dodoradio[m] | Issue identified: it looks like it can get stuck in suspend somehow... |
| 17:24:20 | beroset[m] | <dodoradio[m]> "Oh, that doesn't mention repo..." <- Done! https://github.com/AsteroidOS/asteroidos.org/pull/221 |
| 17:26:10 | eLtMosen[m] | <dodoradio[m]> "Issue identified: it looks..." <- Is it completely stuck in suspend? If it only takes a long time to wake from it, thats a known issue i also observe on at least bass and lenok. Dory too sometimes. |
| 17:26:24 | eLtMosen[m] | At least on those it takes seveeral "tries" to wake sometimes. |
| 17:32:52 | dodoradio[m] | It looks like it's got something to do with the charger |
| 17:33:07 | dodoradio[m] | When taking it off charge, it can 'get stuck' in suspend and not power back up |
| 17:45:54 | dodoradio[m] | Hmm, can't reproduce it. Let's hope it was a one-time error |
| 20:12:11 | dodoradio[m] | <dodoradio[m]> "After digging through mce code a..." <- so, a quick summary of how this works in MCE in case someone needs to know in future: |
| 20:12:11 | dodoradio[m] | As far as I understand, when the power button is pressed, MCE does not explicitly request a suspend (an example of an explicit suspend request would be closing the lid on a laptop, or `systemctl suspend`). Instead, MCE keeps a wakelock when the display needs to be on. When the display turns off, assuming there are no other wakelocks being held, MCE releases the last wakelock and the kernel's autosleep should put the system into suspend. On |
| 20:12:11 | dodoradio[m] | koi, the autosleep was disabled - this meant that there was no way for it to enter suspend without it explicitly being requested. |
| 20:12:54 | dodoradio[m] | * being requested, even when all the wakelocks are released. |
| 22:42:48 | MagneFire[m] | <dodoradio[m]> "beroset MagneFire kido opinions..." <- I like it! There even exists some example implementation for Android: https://github.com/RideBeeline/android-bluetooth-current-time-service/tree/master/currenttimeservice%2Fsrc%2Fmain%2Fjava%2Fco%2Fbeeline%2Fandroid%2Fbluetooth%2Fcurrenttimeservice |