Wednesday, 2019-12-04

T42<龚苑焦 %lastname%> (Photo, 988x565) https://irc.thaodan.de/.imgstore/ufy5AuAI0j.png 💥精准拉币圈区块链活粉💥非小号/mytoken关注惊爆价"1、币圈电报群/微信群炸群推广 2、twitter、facebook关注 3.KYC身份材料出售  4、电报群/微信群/potato拉币圈活人 5、国内外交易所APP实名注册认证 6、电报群客服活聊天  7、批量注册国内外交易所实名账户,出twitter、facebook、微信带粉04:05
Mister_Magistermal: piuuuung07:21
T42<RK2019account> @%lastname% [<reply to media>], AD09:28
rinigusDuring actdead, xz2 does not reboot when you press and hold power button. While it's detecting an event (in logs), reboot is not started. Anything to tune?11:17
malMister_Magister: pong?12:00
Mister_Magistermal: great! i have question!12:01
Mister_Magister[10:51] <Mister_Magister> mal: i updated my osprey but unfortunately dhi is segfaulting. I updated packages on obs, droid-hal is pretty old though. here is dmesg https://paste.opensuse.org/6a10416c and journal https://paste.opensuse.org/0aa2879612:01
Mister_Magisteri am kinda lost12:02
malwhich android base?12:04
Mister_Magister12.112:04
malhmm, plenty of core dumps from iptables and tc, I remember there was a fix for those12:05
Mister_Magistermal: yeah it seems like i'm missing one thing so i prefered to ask12:06
Mister_Magisteridk what i missing though. after one sailfish version it broke and since then i didn't bother to touch it12:06
Mister_Magister2.2.1 i believe12:06
maldo you have latest submodules, both dhd and configs?12:06
maldid you rebuild/repackage droid-hal rpms?12:07
Mister_Magisteri updated dcd submodule to latest12:07
Mister_Magisterno i didn't repackage droid-hal12:07
T42<elros34> 12.1 then probably to new libhybris12:07
Mister_Magisterhm?12:08
malneed to check logs12:08
T42<elros34> libhybris is broken for 11 and 12 bases: try a426857906dda89370a4b670f23d92a82e6f243b commit12:09
T42<elros34> also make sure you have up to date system/core12:09
Mister_Magisteri have old system/core12:09
malthere was some changes to core12:10
Mister_Magisteri didn't want to rebuild hal cause i deleted it but guess there is no other choice?12:10
malhttps://github.com/mer-hybris/android_system_core/commits/hybris-12.112:10
Mister_Magistermal: yeah i remember12:10
malalso dhd has had many changes12:10
Mister_Magisterso i should update hal then?12:11
malI would do that12:11
Mister_Magistereh so annoying12:12
malI build hybris-hal quite often12:13
Mister_Magisterwell hadk said you won't have to do it often12:14
Mister_Magisteri didn't update g2 hal since the needed system/core update12:14
malyes, not often but still sometimes there could be need12:14
malat least repackaging sometimes is useful12:14
mal@elros34 I need to figure out that libhybris issue, afaik it doesn't happen in if tracing/debug is enabled12:14
T42<elros34> mal: yes, iirc enable-trace was enough12:16
malI tried to look into the code earlier but couldn't see any obvious error, need to have another look12:19
malI have other fixes/cleanup to libhybris waiting locally12:19
T42<nitin_3> @mal that fix also worked for me..audio works without any hacks..removed the symlink12:32
mal@nitin_3 good12:35
rinigusmy actdead issue is shown in a log at https://dpaste.de/oGXw . question is how to convince mce or DSME to start reboot in these conditions (power button pressed, usb cable in). log also shows shutdown in actdead after removal of cable later16:23
malrinigus: what is the issue?16:33
rinigusWhen you have phone on usb in act dead mode, i would expect it to boot into full os when i press and hold power button. I believe that's what we had on onyx16:36
rinigusmal : /\16:36
malrinigus: afaik it should do it16:38
malrinigus: how long did you press the button?16:39
rinigusmal: for about 5 sec, until I've got vibration16:41
malneed to test on some device16:42
rinigusmal: corresponding location in log - https://dpaste.de/oGXw#L10316:42
rinigusmal: please do16:43
malrinigus: on fp2 after the vibration device reboots and goes to normal UI, afaik that is the way it works, maybe there is not direct transition from actdead to full boot but instead it does a reboot16:45
rinigusmal: yes, I was expecting reboot. but for some reason, it is completely ignored in my case.16:46
rinigus(full reboot, as in fp2)16:46
rinigusmal: I wonder whether actdead works for xperia 10. I think earlier versions were listing it as buggy16:48
rinigusmal: I guess it boils down to why DSME requst to shutdown is ignored after line #103 in my log16:49
deathmistrinigus: using a '.' instead in version seems to have worked and my device picked it up too from OBS download repo \o/17:45
rinigusdeathmist: great to hear!17:46
deathmistI assume including it in new images is as simple as adding the package to patterns and it'll be used from OBS with that kickstart?17:47
rinigusdeathmist: you don't have to add it anywhere, it will be pulled automatically17:53
rinigusif you use KS from OBS17:54
deathmistalright, neat :D  I used that already but it probably just picked the one from Jolla repos on last build as I couldn't install the custom one with "zypper in nemo-qml-plugin-systemsettings" on device before either17:55
rinigusmal: looks like it breaks for me at if/else logic in https://git.sailfishos.org/mer-core/dsme/blob/master/modules/state.c#L368 . I presume that in my case shutdown_requested=true, charger_state != CHARGER_DISCONNECTED, reboot_requested=false18:14
rinigusso, I end up in log message 'state: Actdead (charger: on, alarm: not set)'18:14
rinigusmal: looks like the dsme code does work as expected and one condition in if/else sequence is just missing. which makes me wonder how it works on fp2 with attached charger. so, I believe its dsme bug.18:31
rinigus... where are we expected to file bugs against mer-core/dsme these days?18:32
deathmisthey, any reason *.service files in /lib/systemd/user/ don't seem to be loaded in SFOS? moving the files to /etc/systemd/user/ made them work immediately20:43
piggzdeathmist: symlinks needed ... just systemctl enable....20:43
piggzalso, user ones should be in /usr/lib/systemd/user20:44
deathmistah, ok. I was looking for that dir ^^ the symlinks were already setup correctly20:45
spiiroinrinigus: looks like you started the long press when display is off... which is just supposed to turn display on - which does happen21:23
spiiroinrinigus: in addition to that you held the power key long enough to trigger dsme "emergency shutdown without ui". there is no shutdown from act-dead while charger is connected -> ignored, as it should21:24
spiiroinrinigus: i.e. wake up the display, then do the long power key press -> it ought to do reboot to user21:25
spiiroinit has been like this forever. except that: "long press from display off" kind of no longer exist (to normalize power key behavior in suspend in all devices) -> treated as short press -> wakes up display21:27
spiiroinIIRC it used to do nothing21:28
spiiroinrinigus: anyway bugs can be filed at https://bugs.merproject.org -> mer-core -> dsme (though if this were a bug it would be in mce, not dsme)21:35

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!