Tuesday, 2024-03-26

« Monday, 2024-03-25 Index Wednesday, 2024-03-27 »
electro575hi all, is it possible to install sailfishos on sony xperia X ?08:37
electro575with precompile OS for this device ?08:37
T42_<sudo_si> https://irc.thaodan.de/.imgstore/f4937d5b/jorunal.txt09:11
T42_<sudo_si> https://irc.thaodan.de/.imgstore/1daf623f/dmesg.txt09:12
T42_<sudo_si> https://irc.thaodan.de/.imgstore/be17a9af/logcat.txt09:12
T42_<oleg3256> https://irc.thaodan.de/.imgstore/f4937d5b/jorunal.txt09:13
T42_<oleg3256> https://irc.thaodan.de/.imgstore/1daf623f/dmesg.txt09:13
T42_<oleg3256> https://irc.thaodan.de/.imgstore/be17a9af/logcat.txt09:13
T42_<sudo_si> any idea why mce keep `Failed with result 'timeout'`09:14
T42_<sudo_si> @elros34 (re @oleg3256: )09:14
T42_<elros34> @electro575 of course you can. This is officially supported device but it will be dropped soon. Not sure what do you mean by precompiled OS. Jolla gives you ready to use sfos image with instruction12:23
electro575dropped ? delete ?12:23
T42_<elros34> end of support12:24
electro575humm, okey12:24
electro575and for FP4 ?12:24
electro575elros34 : where can i find the link to sailfish for sony xperia X ?12:24
T42_<elros34> fp4 is not officially suppported device12:25
T42_<elros34> you can easily  find it in official jolla site12:25
electro575a list of supported devices ?12:25
T42_<elros34> same12:25
T42_<elros34> "sailfish x" program12:25
T42_<elros34> https://shop.jolla.com/12:27
electro575thk, sailfish x is the OS ?12:27
T42_<elros34> lets call it name for sailfish os for xperia devices.12:28
electro575i need buy it ? after how many time tested with free version ?12:28
electro575ok12:28
T42_<elros34> free trial is free forever12:29
electro575but v2.1.2 version of OS ?12:29
electro575for xperia X12:29
T42_<elros34> No jolla never gives acces for older versions, only latest. You would have to build image youself. Its a matter of getting ks (I think somebody uploaded them in tmo forum long time ago) file and running mic12:31
T42_<elros34> I don't see xperia x in list so maybe they already removed it, you need to try yourself12:32
electro575:-/12:33
T42_<elros34> login and try to get a trial12:35
electro575puremaps is off on market since 2021 ?12:35
electro575what's the market now ?12:35
T42_<elros34> not sure what do you mean by this but this is question for sailfishos channel not porters one12:37
electro575Yes, thk12:38
electro575elros34 : it's possible to have android compatibility app ?12:41
electro575with appsupport but, it cost a lot of ressources ?12:42
electro575just for 2 app12:42
T42_<elros34> on official devices yes, this is what you paid for. On unofficial there is waydroid12:46
electro575humm, ok12:47
electro575official is, jolla or sony ?12:47
T42_<elros34> offcial devices are all from jolla site so basically few sony models and IIRC for a one more release gemini, jolla tablet12:49
electro575i can, sony xperia X single SIM12:53
electro575but it's not an official device so !?12:53
T42_<elros34> @sudo_si disable properly audit via kernel cmdline, it spam whole dmesg12:54
T42_<elros34> this is also hybris-16, you should have disabled selinux according to mer-kernel-check12:56
T42_<elros34> ah its 17, I do not know what logs I have open13:17
electro575a market can be openrepo ?13:20
T42_<AntonlX> How to clear jolla-camera app data. It does not working after switching to inexisted camera.13:50
maltry "dconf reset -f /apps/jolla-camera/"13:51
T42_<AntonlX> This worked, thanks! (re @SailfishFreenodeIRCBridgeBot: <mal>try "dconf rese...)14:22
T42_<AntonlX> How I could hide broken lens in jolla-camera? My device have 4 cameras(one is depth sensor), but camera is showing 5. One breaks app, second is copy of main.15:01
T42_<elros34> maybe this patch will give you some ideas: https://coderus.openrepos.net/pm2/project/patch-five-cameras-tucana17:55
T42_<b100dian> mal: wasn't this also tracked internally? To only list cameras that have labels in jolla-camera18:01
*** rainemak_ is now known as rainemak18:06
malmight be, need to check18:24
T42_<sudo_si> journal not spammed (re @elros34: @sudo_si disable pro...)18:26
T42_<sudo_si> yes it's 17 and this port for exynos7880 it works fine on a5 but a7 wont boot (re @elros34: ah its 17, I do not ...)18:27
T42_<sudo_si> they are the same soc18:27
T42_<elros34> what happens when you run mce manually?18:40
T42_<elros34> some of your mount doesn't work: /opt/vendor/etc/init/init.samsungexynos7880.rc18:43
T42_<sudo_si> Job for mce.service failed because a timeout was exceeded.19:41
T42_<sudo_si> See "systemctl status mce.service" and "journalctl -xe" for details. (re @elros34: what happens when yo...)19:41
T42_<sudo_si> fixed but didn't help (re @elros34: some of your mount d...)19:41
T42_<elros34> manually means in terminal19:43
T42_<elros34> like: 'mce -v'19:44
T42_<sudo_si> not using systemd19:44
T42_<elros34> probably with -T argument too19:45
T42_<sudo_si> mce: T+0.000 W: mce.c: main(): MCE 1.114.1 (release) starting up19:46
T42_<sudo_si> mce: T+0.005 C: mce-dbus.c: dbus_acquire_services(): Cannot acquire service com.nokia.mce: (null): (null)19:46
T42_<sudo_si> mce: T+0.005 C: mce.c: main(): Failed to initialise D-Bus19:46
T42_<elros34> how do you start it? include command you use when you generate logs19:47
T42_<sudo_si> `mce -T`19:48
T42_<elros34> isn't it already running?19:48
T42_<sudo_si> no (re @elros34: isn't it already run...)19:48
T42_<elros34> systemctl stop mce, and then mce -vT and show whole command prompt19:48
T42_<sudo_si> sh-5.0# systemctl stop mce19:51
T42_<sudo_si> sh-5.0# mce -vT19:51
T42_<sudo_si> mce: T+0.000 W: mce.c: main(): MCE 1.114.1 (release) starting up19:51
T42_<sudo_si> mce: T+0.000 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/10mce.ini ...19:51
T42_<sudo_si> mce: T+0.000 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20als-defaults.ini ...19:52
T42_<sudo_si> mce: T+0.000 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20debug-led.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20evdev-types.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20hybris-features.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20hybris-led.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20mce-radio-states.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/30csdpatterns.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/60-doubletap-exynos7880.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/60-hybris-features.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/90evdev.ini ...19:52
T42_<sudo_si> mce: T+0.001 N: mce-fbdev.c: mce_fbdev_open(): open frame buffer device19:52
T42_<sudo_si> mce: T+0.001 N: mce-fbdev.c: mce_fbdev_init(): using ioctl for fb power control19:52
T42_<sudo_si> mce: T+0.005 C: mce-dbus.c: dbus_acquire_services(): Cannot acquire service com.nokia.mce: (null): (null)19:52
T42_<sudo_si> mce: T+0.006 C: mce.c: main(): Failed to initialise D-Bus19:52
T42_<elros34> what about systemctl mask mce and again. Use paste service for such long logs19:53
T42_<sudo_si> run it again manually19:54
T42_<sudo_si> run it again manually? (edited)19:54
T42_<elros34> mask and run again19:54
T42_<sudo_si> ok19:55
T42_<elros34> are really sure it's not already running? pgrep -af mce, or journalctl -f19:55
T42_<elros34> or restarting19:55
T42_<sudo_si> rebooted19:56
T42_<sudo_si> https://pastebin.com/Vybx1e3P20:01
T42_<sudo_si> journalctl https://pastebin.com/4VuyRWLQ20:04
T42_<elros34> so it stays like that forever?20:04
T42_<sudo_si> yes20:05
T42_<elros34> add more 'vvvvvv20:06
T42_<sudo_si> mce -vvvvvvT20:08
T42_<sudo_si> mce: T+0.000 D: mce-wakelock.c: mce_wakelock_init(): wakelock usage enabled20:08
T42_<sudo_si> mce: T+0.000 W: mce.c: main(): MCE 1.114.1 (release) starting up20:08
T42_<sudo_si> mce: T+0.000 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/10mce.ini ...20:08
T42_<sudo_si> mce: T+0.000 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20als-defaults.ini ...20:08
T42_<sudo_si> mce: T+0.000 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20debug-led.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20evdev-types.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20hybris-features.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20hybris-led.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/20mce-radio-states.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/30csdpatterns.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/60-doubletap-exynos7880.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/60-hybris-features.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-conf.c: mce_conf_read_ini_files(): processing /etc/mce/90evdev.ini ...20:08
T42_<sudo_si> mce: T+0.001 N: mce-fbdev.c: mce_fbdev_open(): open frame buffer device20:08
T42_<sudo_si> mce: T+0.001 D: mce-fbdev.c: mce_fbdev_open(): frame buffer device opened20:08
T42_<sudo_si> mce: T+0.001 N: mce-fbdev.c: mce_fbdev_init(): using ioctl for fb power control20:08
T42_<sudo_si> mce: T+0.002 D: mce-dbus.c: mce_dbus_init_privileged_uid(): privileged uid = 99720:08
T42_<sudo_si> mce: T+0.002 D: mce-dbus.c: mce_dbus_init_privileged_gid(): privileged gid = 99620:08
T42_<sudo_si> mce: T+0.002 D: mce-dbus.c: mce_dbus_init(): Establishing D-Bus connection20:08
T42_<sudo_si> mce: T+0.005 D: mce-dbus.c: mce_dbus_init(): Connecting D-Bus to the mainloop20:08
T42_<sudo_si> mce: T+0.005 D: mce-dbus.c: mce_dbus_init(): Acquiring D-Bus service20:08
T42_<sudo_si> mce: T+0.006 C: mce-dbus.c: dbus_acquire_services(): Cannot acquire service com.nokia.mce: (null): (null)20:08
T42_<sudo_si> mce: T+0.006 C: mce.c: main(): Failed to initialise D-Bus20:08
T42_<elros34> please use pasteservice. Also you should already know this error and what its wrong20:09
T42_<elros34> mce is already running20:09
T42_<sudo_si> https://pastebin.com/XhRjyRje20:13
T42_<elros34> maybe its not mce itself but sandbox in systemd service. What if you comment out all these Capability*,Private,Device* in mce.service?20:18
T42_<sudo_si> in actdead mode it bootup20:29
T42_<sudo_si> maybe this needed https://github.com/spiiroin/mce/commit/25c772f300387a9c0a426f87f03cbb63654194bb20:30
T42_<elros34> IIRC symptoms were different for this commit change20:31
T42_<elros34> maybe it would be good idea to increase logging in mce.service and watch for: "notifying systemd" https://github.com/sailfishos/mce/blob/6e94849a8bd969a4ff0fd54f131a6fa170db0d82/mce.c#L1136. I guess this is what is missing in your journal20:42
T42_<elros34> also I wouldn't be surprised if this is some race issue due to excessive logging: your not disabled audit + samsung kernel which logs everything you do not want to watch20:48
« Monday, 2024-03-25 Index Wednesday, 2024-03-27 »

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