Kajetan Krykwiński
Kajetan Krykwiński
Link between portals: [1] https://intel.ingress.com/?pll=51.146801,16.891397 and [2] https://intel.ingress.com/?pll=51.110173,17.025442 goes "below" portal [3] https://intel.ingress.com/?ll=51.136045,16.928558&z=17 on IITC, but above on stock Intel:   This is even more interesting, as on that...
Hello, ``` battery.charge: 66 battery.charge.low: 10 battery.charge.warning: 50 battery.runtime: 65535 battery.runtime.low: 150 battery.type: PbAc battery.voltage: 52.0 battery.voltage.nominal: 48.0 device.mfr: American Power Conversion device.model: Smart-UPS X 750 device.serial: device.type: ups driver.name:...
Hello, I live in a multi-storey building with a lot of wmbus devices. Those are: - `apator162` water meters - `amiplus` power meters - `Apator E-ITN 30.51` HCAs (not supported...
Full implementation of protocol for Apator E-ITN 30.51, as discussed in #598 So far tested on 4 devices I have access to, and a dozen ones I don't have access...
With today's head c113f0e665e2b9e62b4510b989e397bab714b85c i get: ``` (apator162) telegram contains a register (0a) with unknown size. Please open an issue at https://github.com/weetmuts/wmbusmeters/ and report this telegram: 5A441486128805000507B60AFFFFF5450106F41BB0767A50004085EE8C318C97BB9E01929519E82D56DE6FDB31DBF5AC13628F3B380F3D4E71F3A6D97E8CC7F8DB18340EEFD2991FC5BDEE1A80781A37493A7CDC7D8E81308AC7E9 ``` Some more...
In 05a99a7c5f4c0723568382f629bb8b44a89dd7bb I blindly believe font file to be valid if just header magic matches. `bfnt_load_from_card` should be updated to: * verify if loaded size > header size * parse...
To discuss / implement: * boot-d678.c shall be probably renamed * better way to handle new RGBA buffer size? * implementation of XCM compositor support so layer with "legacy" resolution...
Found with `file_man.mo`: Digic 7 and 8 have a different `fio_file` struct, with additional fields. Modules are universal, compiled without per-cam ifdefs and thus wrong structure definition is used, ending...
Both R and RP (untested on M50) have random crashes related to EvfCap task. Recently @coon42 got nice trace [1] that sent us into `stateobj_lv_spy()` from `state-object.c`. Disabling state objects...
On D6 and up `additional_version` doesn't work properly. We point this at `\n` in char buffer that contains firmware version in RAM. However Canon code leaves there `1.0.0` on boot...