| T42 | Beryl %lastname% was added by: Beryl %lastname% | 05:04 |
|---|---|---|
| rinigus | piggz: no, Mesa should be already in the platform. So extension shouldn't be needed. Please check with coderus, maybe there is a trick to make it run on x86 sfos | 05:49 |
| rinigus | spiiroin: I have the pickup sensor working. works reasonably, as far as I can see. | 06:36 |
| rinigus | it is wired as tapadaptor, at https://git.sailfishos.org/rinigus/sensorfw/tree/pickup-dev/adaptors/hybrispickupadaptor | 06:36 |
| rinigus | main issue with the sensor is that it is one shot | 06:36 |
| rinigus | so, I get it once to fire and then it has to be stopped/started again | 06:36 |
| rinigus | spiiroin: not sure how to proceed from here. would it be ok for mce to restart the sensor on every display off? | 06:37 |
| rinigus | spiiroin: also, is it ok to use tapsensor for it? | 06:37 |
| rinigus | btw, sensor fires whether device was asleep or active, as requested | 06:38 |
| r0kk3rz | sounds like a bug in your code somewhere | 06:43 |
| rinigus | r0kk3rz: was it for me regarding sensor? no, it's one shot sensor by definition: https://source.android.com/devices/sensors/sensor-types#pick_up_gesture | 06:46 |
| rinigus | sensor reporting mode: one shot | 06:47 |
| rinigus | https://source.android.com/devices/sensors/report-modes#one-shot | 06:47 |
| r0kk3rz | oh ok, so it has to be reset by design | 06:53 |
| r0kk3rz | id try resetting it straight away, and see how it functions | 06:55 |
| rinigus | r0kk3rz: that's an option, indeed. so, after each pickup restart the sensor in sensorfw, if I understood you correctly | 06:58 |
| r0kk3rz | yeah | 06:58 |
| r0kk3rz | might act weird, but its the simplest solution | 06:58 |
| spiiroin | rinigus: for mce edge actions such as "on display blank" is not really sufficient... but if you can get the sensor working, I can help with mce "monkey work" regarding settings, state machinery and such | 07:05 |
| *** birdzhang1 is now known as birdzhang | 07:11 | |
| rinigus | spiiroin: as such, it works already. question is whether to stop/start on mce side or on sensorfwd, as suggested by r0kk3rz. | 07:17 |
| rinigus | in some respect, the sensor is expected to be activated only when wakeup is needed. this points towards mce | 07:18 |
| rinigus | but as sensorfw HybrisAdaptor is qobject derived, I imagine that restarting sensor via qobject timer should be trivial on sensorfwd side as well. timer is probably needed to avoid some race conditions on restarting sensor as soon as it fired. | 07:20 |
| rinigus | spiiroin: ^ | 07:20 |
| spiiroin | rinigus: in thery single-shot is enough. in practice ... things like on-demand ps can make it necessary to re-arm the sensor | 07:28 |
| spiiroin | from sensorfwd client pov, I'm not sure if single shot is something one would want to have. or if one wants just one wakeup, sensor can be stopped after getting that tap | 07:29 |
| spiiroin | so I'd be inclined to handle that single-shot detail as internal thing within senserfwd | 07:30 |
| spiiroin | mal: opinions on ^ ? | 07:30 |
| rinigus | spiiroin: from looking but into mce sources, I could see that the tap sensorfw is there already. I wonder if it could be used for triggering "display on" already or config has no such option? | 07:45 |
| rinigus | spiiroin: as for doing repeated firing inside sensorfw, I'll be able to look into it tonight | 07:46 |
| rinigus | Unless you with mal prefer different way | 07:47 |
| *** birdzhang1 is now known as birdzhang | 08:31 | |
| T42 | <Verevka86> Hello. does not create /dev/socket/netmgr_connect_socket. mobile Internet doesn't work. dummy_net added. what could be the reason? | 09:15 |
| spiiroin | rinigus: shortly, tap event needs to go via the same route and be subject to the same policies as power key, double taps, fp wakeups, etc and have config structure similar to all other sensors mce uses | 09:22 |
| spiiroin | there is some tap-sensor code in mce, but atm in is for-debug-only i.e. not connected to anything -> helps to some extent | 09:23 |
| rinigus | spiiroin: I will read the source and follow the double tap routes. I'll ask/report back when I get there | 09:27 |
| piggz | rinigus: codeus says angelfish works on hybris based x86-64 (jolla tablet).... | 09:27 |
| piggz | i will try on pinephone as a non hybris arm device | 09:27 |
| rinigus | piggz: note that it will use on this device the included mesa. for L5, I remember, it took some time to get mesa updated in flatpak platforms. so, pure maps was able to start working there relatively recently... | 09:32 |
| rinigus | don't know what's the status for pinephone. | 09:32 |
| piggz | rinigus: L5 ? | 09:35 |
| rinigus | piggz: purism L5. they also use flatpak for pure maps | 09:36 |
| piggz | is that mesa too? | 09:36 |
| rinigus | yes, its native and uses gnome by default | 09:37 |
| rinigus | so, for qt apps, flatpak is a good option | 09:37 |
| piggz | rinigus: i added a few env variables that were in coderus command line, but it still crashed..... there is a lot of hybris/arm stuff in this command line https://paste.mozilla.org/LSs3Kngk | 09:50 |
| rinigus | piggz: which device? X86? | 09:54 |
| piggz | rinigus: xiaomi latte, x86 | 09:55 |
| rinigus | filesystem=/opt/flatpak/maliit/org.kde.Platform/arm/5.12:ro is surely not needed, it's from older days before official extension for maliit | 09:55 |
| piggz | no hybris | 09:55 |
| piggz | is my flatpak isntall old? | 09:56 |
| rinigus | piggz: try something simpler, just qml. Osm scout server should do. That's available on flathub and check if it shows gui. That way we will see if it's webengine or qml | 09:57 |
| piggz | dolphin works.... | 09:58 |
| piggz | thats widget based tho | 09:58 |
| piggz | kaidan loads up, is that qml? | 09:58 |
| piggz | elisa also loads | 09:59 |
| rinigus | piggz: no idea, but you could check the source to see if it's qml | 10:07 |
| T42 | <Verevka86> Fwd from Verevka86: Hello. does not create /dev/socket/netmgr_connect_socket. mobile Internet doesn't work. dummy_net added. what could be the reason? | 10:07 |
| T42 | <Verevka86> Can they help here? | 10:08 |
| rinigus | If qml works, but not webengine, then you will have to start disabling all kinds of accelerations by it's envs | 10:09 |
| T42 | <ankaos> https://paste.ubuntu.com/p/Jbcmvsfjf5/ ı new build sailfish os | 10:25 |
| T42 | orangechemist was added by: orangechemist | 11:31 |
| T42 | <Verevka86> Help me 😊 not work mobile internet | 12:52 |
| T42 | <Verevka86> Ofono debug- https://hastebin.com/imuqaripex.sql | 12:52 |
| T42 | <ankaos> @Verevka86 [Help me 😊 not work mobile internet | 12:54 |
| T42 | <ankaos> Ofono debu …], not work ril and wifi | 12:54 |
| T42 | <ankaos> camera, wifi, bluetooth, sim kart and wifi not work :D | 12:57 |
| T42 | <Verevka86> Everything works for me except mobile Internet 😊 | 12:58 |
| T42 | <ankaos> ofono.service mask. because device is bootloop. | 12:59 |
| T42 | <ankaos> droid-hal-init https://paste.ubuntu.com/p/djfRvzQK55/ | 13:01 |
| T42 | <ankaos> bluetooth https://paste.ubuntu.com/p/TwqCDgBDtD/ | 13:04 |
| T42 | <ankaos> How can I activate wlan. | 14:08 |
| T42 | <elros34> https://github.com/mer-hybris/hadk-faq#build-wlan-driver-as-module | 14:13 |
| T42 | <ankaos> @elros34 [https://github.com/mer-hybris/hadk-faq#build-w …], :( dont work | 14:16 |
| T42 | <elros34> that explain everything | 14:18 |
| T42 | <ankaos> Elros please look. https://paste.ubuntu.com/p/QbTgNh2wGz/ | 14:40 |
| T42 | <elros34> what issue? Always provide full logs: journalctl --no-page not so long time after reboot. Partial logs are useless | 14:42 |
| T42 | <ankaos> Shall I compile this for ofono? https://github.com/mer-hybris/ofono-ril-binder-plugin | 18:03 |
| piggz | rinigus: was not counting on having to port biometryd to a newer version of boost! | 18:04 |
| rinigus | piggz: :) | 18:05 |
| T42 | <ankaos> https://github.com/mer-hybris/ofono-ril-binder-plugin if I compile this, will the ofono open? | 19:41 |
| mal | which android base? | 20:22 |
| T42 | <ankaos> @mal [which android base?], los-14.1 | 20:25 |
| mal | that is used for device using hybris-15.0 or newer (android 8+) | 20:38 |
| mal | so what are you trying to fix | 20:38 |
| T42 | <ankaos> I do not have any major problems other than wlan and ril right now. | 21:18 |
| T42 | <ankaos> I even think of compiling for los-16.0. | 21:18 |
| T42 | <ankaos> Do I have the possibility to get wired from the computer? @elros | 21:22 |
| T42 | <elros34> I dont understand what you mean | 21:23 |
| T42 | <ankaos> @elros34 [I dont understand what you mean], How can I get the internet from the computer? | 21:24 |
| T42 | <ankaos> wlan not work. ril not work | 21:25 |
| T42 | <elros34> ah there is instruction for internet from your pc in HADK pdf | 21:26 |
| T42 | <elros34> wlan should be easy if you follow hadk-faq | 21:26 |
| T42 | <ankaos> 13.6 WLAN` | 21:27 |
| T42 | <elros34> 9.3.3 in hadk for usb networking | 21:29 |
| T42 | <ankaos> How can I find out what wlan is? wlan0 wlan1 etc. | 21:35 |
| T42 | <elros34> use ifconfig | 21:36 |
| T42 | <ankaos> okey | 21:39 |
| T42 | <ankaos> @elros34 [9.3.3 in hadk for usb networking], used this line. | 21:44 |
| T42 | <ankaos> what will i do next | 21:45 |
| T42 | <ankaos> @elros34 [9.3.3 in hadk for usb networking], not connected | 22:05 |
| T42 | <elros34> dunno, maybe you have firewall enabled? | 22:07 |
| T42 | <elros34> @edp_17 I think I know why symbols wasn't exported from dhd_linux.c. Driver is write in a way to use deferred module initialization from userspace. I think this is somehow similar to touch /dev/wcnss_wlan used in other wlan drivers which trigger initialization. I guess something in /Init*rc read /proc/deferred_initcalls which triggers | 22:48 |
| T42 | wlan. | 22:48 |
| T42 | <ankaos> ı cant add jolla account. | 23:03 |
| T42 | <ankaos> because device dont see wlan :(. | 23:03 |
| T42 | <ankaos> but open usb connecting | 23:04 |
| r0kk3rz | theres a test connman does to check for connectivity | 23:11 |
| r0kk3rz | but iirc the browser ignores that, so try something | 23:12 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!