AsteroidOS IRC Logs

Privacy Policy

Search:

00:24:29DocGalaxyBlock[m<dodoradio[m]> "carp will charge off the debug..." <- It shows chargi g but mine got off after some time... (would need to test that again)
00:28:26DocGalaxyBlock[m* It shows chargi g but mine got off after some time... (I would need to verify that again)
00:53:23*dodoradio[m]uploaded an image: (29KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/RyHuuinETqzVbegRXwKpjECx/IMG_20220527_235208.jpg >
00:54:25dodoradio[m]ah it crashed
00:54:56dodoradio[m]not sure if it's because the battery was dead or because something is actually wrong
01:00:58dodoradio[m]MagneFire: you mentioned you had to disable GPS, was this in the kernel?
01:03:30dodoradio[m] * not sure if it's because the battery was dead or because something is actually wrong
01:03:30dodoradio[m]edit
01:03:50dodoradio[m] * not sure if it's because the battery was dead or because something is actually wrong
01:03:50dodoradio[m]edit: it's because the system wipes itself after an oem unlock and I forgot about that
01:21:51dodoradio[m]wow UI really gets messed up on carp as a result of the tyre
01:57:35dodoradio[m]we really need to work out what to do about the tyre
01:58:23dodoradio[m]I'm thinking, maybe we could make the anchors.centerIn the actual display center, while moving up the bottom edge to comply with the tyre
10:44:45MagneFire[m]<dodoradio[m]> "MagneFire: you mentioned you had..." <- Yes, only the kernel. But keep in mind that a smelt dump is used too. So some userspace blobs (firmware) might also be missing for it
10:46:27MagneFire[m]<dodoradio[m]> "I'm thinking, maybe we could..." <- Wouldn't this break the QML, since the center isn't the actual center? :P
10:46:27MagneFire[m]I'm tempting to agree with you that the right thing to do is to make all apps behave the same as the homescreen.
10:46:27MagneFire[m]But the bottom edge is in that case at a virtual point, below the flat tire
10:48:12MagneFire[m]I think this was even the thing I was trying to achieve when porting smelt.
10:48:30hofmeister[m]Hello everyone. Since Wear OS has been around for the Gear S3, is anyone here porting this?
10:48:35dodoradio[m]> <@magnefire:matrix.org> Wouldn't this break the QML, since the center isn't the actual center? :P
10:48:35dodoradio[m]> I'm tempting to agree with you that the right thing to do is to make all apps behave the same as the homescreen.
10:48:35dodoradio[m]> But the bottom edge is in that case at a virtual point, below the flat tire
10:48:35dodoradio[m]hmm. I'll need to see how qml actually calculates the edges and center?
10:50:08MagneFire[m]dodoradio[m]: Perhaps, let's hope that there's some proper way to do this though.
10:50:08MagneFire[m]Making code changes in qtdeclarative is imo not the way to do this
10:50:43MagneFire[m]hofmeister[m]: I'm not aware of anyone porting AsteroidOS to the Gear S3. Though I must admit that I've grown some interest when I heard the news
10:55:59hofmeister[m]I flashed it at the morning. Now im looking at the Porting Guide and try my best.... is there a layer after meta-mooneye-hybris? parasetam0l has used Android 9 Version. At the moment I have no idea what that means for patching stress
10:58:42jrt[m]Tizen is already gnu/linux. It feels a bit wrong to base a port on wearos community builds instead of the tizen image
11:02:08MagneFire[m]jrt[m]: While true, I think a different approach could work too.
11:02:08MagneFire[m]Having a good starting point/a port at all is a win in my book.
11:03:03hofmeister[m]and Tizen has a bad reputation like "27 000 Errors in the Tizen Operating System"
11:03:25MagneFire[m]<hofmeister[m]> "I flashed it at the morning. Now..." <- Android 9 is a bit troublesome for AsteroidOS ports. We don't actually have a functioning port for that.
11:03:25MagneFire[m]All existing ports use a mixed rootfs with Android 8 and Android 9 blobs
11:03:27dodoradio[m]<MagneFire[m]> "Yes, only the kernel. But keep..." <- Hmm, I just notice some lines of pixels dancing around the top of the display when scrolling. I suspect this might be another reason to use a carp dump here
11:04:18MagneFire[m]hofmeister[m]: Theoretically, the kernel would have a framebuffer that's compatible already with the Tizen based OS.
11:04:18MagneFire[m]Tizen also uses systemd, so it's not really that different from AsteroidOS in that regard
11:04:44MagneFire[m]dodoradio[m]: Is this the carp or sportscarp?
11:05:21dodoradio[m]MagneFire[m]: Sportscarp
11:05:57MagneFire[m]Ah
11:06:03dodoradio[m]I'l gonna dump mine this evening after I'm finished staring at the transparent minnow
11:06:26MagneFire[m]What's the current build of Android on sportscarp?
11:19:11DocGalaxyBlock[m<dodoradio[m]> "Hmm, I just notice some lines of..." <- Do you need a mmc img?
11:22:27MagneFire[m]DocGalaxyBlock[m: Are you also experiencing these lines on your carp?
11:29:03DocGalaxyBlock[mI did not booted/flashed asteroid after dumping a facesetted mmc img
11:29:03DocGalaxyBlock[mBut I do not rember to notice that behavior yet
11:32:26dodoradio[m]Also, the transflective display does seem to work (I was expecting it to get stuck on lowest backlight, but it does manage to turn off). Heartrate seems broken also
11:40:29DocGalaxyBlock[m<dodoradio[m]> "Also, the transflective display..." <- My heartrate worked but only after the 2nd/3rd time booting asteroid
12:26:53dodoradio[m]<DocGalaxyBlock[m> "My heartrate worked but only..." <- That's really weird
12:31:14kido[m]<DocGalaxyBlock[m> "My heartrate worked but only..." <- I’d recommend you consult a cardiologist
13:49:19dodoradio[m]<DocGalaxyBlock[m> "Do you need a mmc img?" <- I probably want one specifically from sportcarp because of the display and GPS
13:50:48dodoradio[m]The way the pixels glitch (very difficult to film) makes me think the issue might be the smelt display driver - carp and smelt have the same display res but carp has a bigger tyre, so it might be overdrawing or doing something else weird
14:45:47dodoradio[m]MagneFire: when you boot up narwhal, is the system time 1h behind the correct time?
15:16:35*xatt[m]uploaded an image: (1488KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/wCnkIXacBxaMwtGrmDsuWTBc/watch.png >
15:16:36xatt[m]How do you get that
15:18:04xatt[m]is this possible to make into a watchface?
15:22:31MagneFire[m]<dodoradio[m]> "MagneFire: when you boot up..." <- Can you send the ipk for the sync daemon? Mine still works independently ;)
15:23:08dodoradio[m]MagneFire[m]: ok, I'll send it over
15:23:14dodoradio[m]but by default, is there 1h offset?
15:24:25MagneFire[m]dodoradio[m]: 2h in my case
15:24:31dodoradio[m]<xatt[m]> "watch.png" <- oh wow, that's really cool! it would actually be quite an easy watchface to make, you'd need to get a font and then concatenate a bunch of strings to show the time and stuff
15:24:42dodoradio[m]MagneFire[m]: so it is a timezone issue 🔫
15:25:10xatt[m]dodoradio[m]: Well if you want to do it, would be very cool!
15:25:10dodoradio[m]> <@magnefire:matrix.org> 2h in my case
15:25:10dodoradio[m] * so it is a timezone issue
15:25:10xatt[m]I'm not an experienced coder
15:25:23MagneFire[m]dodoradio[m]: I suspect that this has something to do with WearOS honestly. AsteroidOS doesn't know anything about timezones.
15:25:23MagneFire[m]It sets the local time
15:26:14dodoradio[m]> <@magnefire:matrix.org> I suspect that this has something to do with WearOS honestly. AsteroidOS doesn't know anything about timezones.
15:26:14dodoradio[m]> It sets the local time
15:26:14dodoradio[m]I know that (it's actually really weird to me. A timekeeping device that doesn't respect timezones? wtf?)
15:26:57dodoradio[m]maybe the solution here is to actually implement timezones, but it could be a case of patching something to ignore the timezone compensation
15:27:09Katze[m]Olla
15:27:19xatt[m]Hallo katze
15:27:39MagneFire[m]dodoradio[m]: My annoyance #1 on narwhal.
15:27:39MagneFire[m]Also, I think that we should at some point move to using systemd for time keeping. But in that case we need to think about timezones.
15:27:39MagneFire[m]Add something to bluetooth and use a default one in the manual setup
15:28:02MagneFire[m]Also: https://github.com/AsteroidOS/asteroid-launcher/issues/35
15:30:12*dodoradio[m]posted a file: (3KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/dzmWNEHHvZfDQYagOqZaYzzn/hands-timesync_%2Bgit0%2Bf8791b1dbf-r1_armv7vehf-neon.ipk >
15:31:10dodoradio[m]> <@magnefire:matrix.org> My annoyance #1 on narwhal.
15:31:10dodoradio[m]> Also, I think that we should at some point move to using systemd for time keeping. But in that case we need to think about timezones.
15:31:10dodoradio[m]> Add something to bluetooth and use a default one in the manual setup
15:31:10dodoradio[m]getting away from the timed-mce stack, what an idea 🤷
15:32:06MagneFire[m]dodoradio[m]: Also the reason why I like the idea of exploring QtApplicationManager: https://github.com/AsteroidOS/asteroid/issues/211#issuecomment-1125463231
15:34:46dodoradio[m]how much does MCE actually do? Ever since I've seen it controlling stuff in pulseaudio, I have grown to fear it more and more
15:35:54MagneFire[m]It can do a lot. But it's main purpose is controlling the display. Inevitable it also sends messages over dbus to the launcher to start/stop rendering.
15:36:41MagneFire[m]I've no idea why it needs to monitor/control pulseaudio
15:37:45dodoradio[m]MagneFire[m]: for calls and stuff, I suspect. It's got a bunch of code for turning the display on and off with the proximity sensor (for ear detection) and also for pocket detection, so I suspect it also tries to manage calls
15:38:34dodoradio[m]I imagine that this functionality is needed, but the fact it's compiled into the main MCE is probably architecturally bad.
15:38:41dodoradio[m]s/probably//
15:39:16MagneFire[m]dodoradio[m]: It really isn't though. That's the concept of modules in mce. You had succes in disabling that. It caused for some other issue though
15:40:18Katze[m]should I get a LG G Watch R second hand for under 30 euros?
15:40:27xatt[m]Katze[m]: yes
15:41:19dodoradio[m]Katze[m]: keep in mind it's a large watch with a 'chunky' design, and also check that the battery is good before buying. ofc this also depends on pricing in your region
15:41:55dodoradio[m]MagneFire[m]: that's not a module, the proximity sensor stuff, that's in the main code
15:43:54MagneFire[m]dodoradio[m]: Oh! For real?! Indeed not nice!
15:43:58dodoradio[m]the way the main state machine works, the fact it's all in the 'display' code, it's all quite frustrating. Just the fact that the display code is in charge of so much hardware is frustrating, it should really be separated
15:44:42MagneFire[m]In any case, I installed your ipk. It synced up nicely. The hands are now correct, but the time of the smartwatch is not correct.
15:44:49MagneFire[m]^ after a reboot
15:45:05MagneFire[m]I think this issue has nothing to do with your daemon though
15:45:24dodoradio[m]MagneFire[m]: well we now know it's a timezone issue, and at this point I am happy hand off the torch to someone who can go far away and deal with that
15:48:57MagneFire[m]Actually, it looks like the kernel module doesn't even set the time from the hands
15:49:32MagneFire[m]These are the only kernel messages wrt the sop716 module:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/487c060f5db378d9947cfb348b927241c3ecf4b9)
15:49:40dodoradio[m]MagneFire[m]: it's got a command in there to do it, I suspected it does, because I didn't see much more reason for it to exist?
15:50:36MagneFire[m]It will set the time only when `update-syslock-on-boot` is set in the device tree
15:51:05MagneFire[m]Then you'd get a kernel module log message starting with `setting system clock to `...
15:51:23MagneFire[m](This function: https://android.googlesource.com/kernel/msm/+/refs/heads/android-msm-narwhal-3.18-oreo-wear-dr/drivers/misc/sop716.c#1334)
15:51:46MagneFire[m]But it's never called because of this switch case: https://android.googlesource.com/kernel/msm/+/refs/heads/android-msm-narwhal-3.18-oreo-wear-dr/drivers/misc/sop716.c#2152
15:51:57MagneFire[m]s/switch/if/, s/case/statement/
15:52:27MagneFire[m]No, we can ofc enable that, but it's more a workaround to the actual issue. Like you said, the timezones
15:53:38MagneFire[m]Hmm, it appears to be there though: https://android.googlesource.com/kernel/msm/+/refs/heads/android-msm-narwhal-3.18-oreo-wear-dr/arch/arm/boot/dts/apq8009-narwhal/apq8009-narwhal-movement.dtsi#29
15:55:13MagneFire[m]May 28 13:43:02 narwhal kernel: soprod716_movement 4-0048: setting system clock to 2022-05-28 13:42:59 UTC (1653745379)
15:57:31MagneFire[m]adbs
16:00:41MagneFire[m]Writing to `/sys/devices/sop716/tz_minutes` does at least something
16:00:59dodoradio[m]> <@magnefire:matrix.org> ```
16:00:59dodoradio[m]> May 28 13:43:02 narwhal kernel: soprod716_movement 4-0048: setting system clock to 2022-05-28 13:42:59 UTC (1653745379)
16:00:59dodoradio[m]> ```
16:00:59dodoradio[m]so you mean it is enabled? I was expecting this, because I couldn't come up with another reason for why it would be exclusive to narwhall
16:02:24MagneFire[m]dodoradio[m]: Yes, it's enabled
16:02:50dodoradio[m]hmm, it would be interesting to try a kernel built without it
16:02:53MagneFire[m]It looks like WearOS sets the timezone `/sys/devices/sop716/tz_minutes` was set to `120` in my case
16:03:11MagneFire[m]Writing `echo 0 > sys/devices/sop716/tz_minutes` seems to fix the issue
16:03:14dodoradio[m]MagneFire[m]: ohh, there's a timezone thing. I didn't realise
16:03:28dodoradio[m]yeah, my daemon should probably do that for the time being
16:04:30MagneFire[m]dodoradio[m]: I see what you did there XD
16:04:40MagneFire[m]But yeah, that seems to work great
16:04:55dodoradio[m]that's a problem solved
16:04:58dodoradio[m]ghost busted!
16:05:44MagneFire[m]Would it then make sense to have this daemon available by default for all `narwhal` users?
16:11:12dodoradio[m]<MagneFire[m]> "Would it then make sense to have..." <- Yeah, of course. We should probably upstream it until lecris and I figure out hw-controls
16:22:31dodoradio[m]I'll send over the bitbake recipe after I get home and add the timezone resetter. Are we fine with pulling it from my repo, or do we want to keep all under asteroid's organisation?
16:24:58MagneFire[m]dodoradio[m]: Thanks!
16:24:59MagneFire[m]I think preferably we would want this under the AsteroidOS organization.
16:24:59MagneFire[m]kido What's your opinion on this?
17:57:38xatt[m]I think i just roasted my gen 4
17:58:03xatt[m]The gnd disconnected while plugging it in
18:22:01beroset[m]<xatt[m]> "The gnd disconnected while..." <- That's unlikely to cause a permanent problem. I wouldn't give up on it just yet.
18:23:54xatt[m]I tried to do a couple resolders
18:24:15xatt[m]But no connection being established
18:41:15kido[m]> <@magnefire:matrix.org> Thanks!
18:41:15kido[m]> I think preferably we would want this under the AsteroidOS organization.
18:41:15kido[m]> kido What's your opinion on this?
18:41:15kido[m]Agreed
18:56:44DocGalaxyBlock[m<Katze[m]> "should I get a LG G Watch R..." <- Got mine for 25€ incl shipping from ebay ka, battery lasts ~working day but has some bad pixels
18:56:44DocGalaxyBlock[mI bought mine only to get some flashing experience before try to Flash my carp