Wednesday, 2020-07-01

riniguspiggz: that would be handy!05:23
rinigusBut looking into the list of PRs sitting and waiting there, I wouldn't be that hopeful in timely manner of the merge. Unless you submit it as sledges (see merged PRs)05:26
spiiroinpiggz: the usual suspects: misidentified power supply devices / problems with change notifications06:38
spiiroinwhat mce version you have there? 1.106.0 has fixes / enablers for some cases06:39
piggzspiiroin: 1.105.306:40
spiiroinpiggz: for example what happened in pinephone on cable disconnect: charger device notified about connected->disconnect, but battery device did not notify about charging->discharging => state evaluation saw "battery is getting charged" -> heuristics misfire -> "there has to be a charger connected" -> similar "it thinks its plugged in all the time" situation06:52
piggzspiiroin: ill update mce then get back to you if there are still issues06:53
spiiroinworkaround: make mce poll all power supply devices when one of them reports change ->
spiiroinneeds to be enabled via config file06:54
spiiroin(the defaults for 1.106.0 = polls info periodically -> helps with things like not missing percentage changes, but not with "hard edges" such as what happens with cable disconnect)06:55
piggzspiiroin: usb plug in > developer mode in use, usb unplug > charging :D07:20
spiiroinpiggz: what would be expected in case of: connect -> + battery.state=charging ; disconnect -> + battery.state left in charging -> "some sort of charger that is not pc connected"07:22
piggzspiiroin: with mcetool, and cable disconnected, i see charger cable: disconnected, charger state: on07:40
piggzthere are 5 devices in /sys/class/power07:40
piggzspiiroin: when unplugged, /sys/class/power/*/online are all 007:58
spiiroinpiggz: the suspected problem comes from: tracking state via udev notifications produces different result vs reading that data directly09:13
piggzspiiroin: i wonder what causes it to think its charging when unplugged tho09:15
piggzi tried that config you sent, but that seems to be for something different, and didnt work anyway09:15
spiiroinpiggz: basically, if mce ends up in situation where every  but battery.state==charging -> disconnected but charging09:16
spiiroinwhat you could do is: enable verbose logging from battery-udev plugin -> follow change notifications mce sees & compare vs what you see by reading directly from sysfs09:18
spiiroinassumed to be the most relevant bits being online props for charger devices and status prop for the (hopefully only one) battery device09:20
piggzspiiroin: i have logs....looks like it could be an unknown charget type....09:21
piggzspiiroin: the gap at line 30 is where i unplug
spiiroinpiggz: ok, this was a novel gotcha. seems battery is treated as charger ...09:23
spiiroincan you paste uevent content from that cw-bat09:24
piggzspiiroin: wdym uvent content?09:25
piggzspiiroin: in /sys its type is "Battery"09:26
spiiroincat /sys/class/power_supply/cw-bat/uevent09:26
spiiroinit does not have status property. does /sys/class/power_supply/battery/uevent have one?09:27
piggzspiiroin: yes09:28
piggz[root@Phone nemo]# cat /sys/class/power_supply/battery/uevent09:28
spiiroinpiggz: ok, that is probably it: lack of status prop -> false "this must be charger" -> to avoid it, blacklist that device09:29
spiiroinprintf >> /etc/mce/99-hackhack.ini "[BatteryUDevDeviceBlacklist]\ncw-bat=true\n"09:30
spiiroinor so, and then restart mce09:30
piggzbtw, need to move away from term blacklist :)09:31
* spiiroin waits for somebody to find red-black trees ...09:32
piggzspiiroin: working :)09:32
piggzspiiroin: oddity, when i unplug, it says "charging complete" is tht normal? its at 92%09:33
spiiroinpiggz: hopefully with charger only? i.e. not when connecting/disconnecting from pc09:35
piggzspiiroin: no,its on my pc atm09:36
spiiroinurgh. some sort of false battery full perhaps09:37
spiirointhere were problems with some mtk devices and battery full reporting -> more heuristics that can misfire09:38
spiiroindo you still have that ini-file in place that was discussed earlier, the one for polling stuff?09:38
piggzspiiroin: no, i changed that one for the new hack09:38
spiiroinok, good. then the 1st thought is: battery=discharging gets acted on before charger=disconnected -> former might tickle battery full heurisitics (charger connected, battery from charging to discharging @ capacity > N == full)09:41
spiiroinso, it could be caused by order/timing of change notifications in kernel->udev->mvce, or mce->dbus->battery status tracker in lipstick09:43
spiirointo verify, you could run "mcetool --set-battery-level=42 -B" in one shell and leave it there, then attach/detach cable and see if it still happens09:47
spiiroinrequires that you have "devel flavor" mce though, battery simulator api is not made available normally09:47
T42Kovid1984 was added by: Kovid198413:31
*** MagneFire_ is now known as MagneFire13:32
piggzmal: remember u promised to look at dhd pr ;)16:57
malpiggz: oops17:28
piggzmal: yes, oops! :D17:36
malpiggz: maybe fix the typos in the commit message17:38
piggzmal: done17:41
mallooking good now17:53
T42<ItsMeShouko> Hello, I need some help. I am porting 3.3.0 to mi a2 and I got error while trying to run: rpm/dhd/helpers/ --mw19:21
T42<ItsMeShouko> Cloning into 'libnciplugin'...19:21
T42<ItsMeShouko> Already up to date.19:21
T42<ItsMeShouko> No provider of 'pkgconfig(nfcd-plugin) >= 1.0.27' found.19:21
T42<ItsMeShouko> Setting version: 1.0.619:21
T42<ItsMeShouko> error: Failed build dependencies:19:21
T42<ItsMeShouko>         pkgconfig(libncicore) is needed by libnciplugin-1.0.6-0.armv7hl19:21
T42<ItsMeShouko>         pkgconfig(nfcd-plugin) >= 1.0.27 is needed by libnciplugin-1.0.6-0.armv7hl19:21
T42<ItsMeShouko> Building target platforms: armv7hl-meego-linux19:21
T42<ItsMeShouko> Building for target armv7hl-meego-linux19:21
T42<ItsMeShouko> How can I fix this?19:21
T42<ItsMeShouko> Here are my repos:
maltry running "rpm/dhd/helpers/ --mw="20:07
T42<ItsMeShouko> It worked, thank you. However I got one error after running20:41
T42<ItsMeShouko> rpm/dhd/helpers/ --version20:41
malsb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R chmod 755 /boot20:46
malif that doesn't help then you need to provide the droid-hal-version-jasmine_sprout.log which is mentioned in the paste you showed20:47
T42<ItsMeShouko> Yes, it didn't work20:48
T42<ItsMeShouko> (Document)
malsb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -msdk-install zypper in droid-config-$DEVICE -ofono-configs-mer20:58
xmnHey Sailfish peeps. Question, would this be a good device to try a. run SF on?
T42<ItsMeShouko> Thanks mal, it worked. After solving some more issues like these I am getting package issues with --mic command, will post about it later22:09

Generated by 2.17.1 by Marius Gedminas - find it at!