Jakob Krantz

Ok, it's my voltage compressions int mV => byte which is bad, nothing wrong with history code I think. And a bug in get sampel i. Now fixed

Never had this issue, but we can add it if it's needed. Got a proposed way to do it?

> @jakkra did you change the IP address before building the container? Note that the environment will be copied once the container is built. You can retrigger it by opening...

AStyle 3.1 I got from apt-get

> It seems like this is started, but I can't seem to find a branch/pull request for this. I can help set it up, I was going to do this...

@Rayvert64 I guess so, I don't have any specific idea how to do it. IMO it's not really needed as I think using nRF toolchain is easy and reliable. But...

> @jakkra you did some stuff for the app. Are we done here and can we close it? Still need the accelerator compensation. But we can modify this ticket to...

Done in https://github.com/jakkra/ZSWatch/pull/355 We now have `zsw_alarm_add` and `zsw_alarm_add_timer` that handles the requirements in this issue.

@Kampi Low, but whenever someone needs it, we can implement it. Should be a simple one. Also possible right now for an app to workaround it just call the [zsw_power_manager_reset_idle_timout](https://github.com/jakkra/ZSWatch/blob/main/app/src/managers/zsw_power_manager.c#L115...

Will check it out