Wednesday, 2019-05-01

osum4esthm i'm running build_packages again but a bunch of files are conflicting between libsensorfw-qt5 and libsensorfw-qt5-hal01:42
r0kk3rzwhich ones?01:45
osum4estibhybrissensorfw-qt5.so.1.0.0, libhybrisaccelerometeradaptor-qt5.so, libhybrisalsadaptor-qt5.so, and a bunch of others. i can pastebin the whole log file if you want01:48
r0kk3rzyou might need to revert sensorfw git back a version01:48
osum4esti tried the "Building sensorfw-qt5-hybris for Sailfish OS 3.0.0.8" in the faq but it didn't seem to help01:49
osum4estactually no, it did help. but then running build_packages.sh by itself looks like it updated the repo01:50
r0kk3rzwell i assume it did work, and now it doesnt01:50
r0kk3rzand this was updated recently01:51
r0kk3rzhttps://git.sailfishos.org/mer-core/sensorfw/tree/master01:51
osum4estyea i've run build_packages.sh fine before. the only thing i've changed since then is adding some stuff to sparse and it's been awhile since ive packaged everything01:52
r0kk3rzgenerally you dont have to rebuild everything01:53
r0kk3rzit can be a good idea when updating sailfish version01:54
r0kk3rzbut if you've just changed configs, then you only need to build configs01:54
osum4estah, got it. so if i change the spec folder i need to build_packages.sh -c, not -d01:56
osum4est*sparse folder01:56
osum4estsweet, that worked. no longer have to manually mess with the fstab. thanks, r0kk3rz02:17
r0kk3rzeverything in sparse is added to the overlayfs, so basically whatever you want in the rootfs you can put in there02:21
osum4estperfect. just got wlan working. on to cellular!02:23
r0kk3rzsounds like good progress02:32
osum4esthmm keep getting "ERROR! Can't connect to RILD: No such file or directory" from ofono. /vendor/bin/hw/rild is running03:00
osum4esti tried adding the lines to ril_subscription.conf but that didn't seem to help03:01
osum4estalso, list-modem outputs nothing03:01
r0kk3rzso /dev/socket/rild exists?03:02
r0kk3rzoh, maybe it needs binder fu03:02
osum4estit doesnt. guess thats part of the problme03:02
r0kk3rzhttps://github.com/mer-hybris/droid-config-sony-nile/blob/master/sparse/etc/ofono/ril_subscription.conf#L14-L1603:03
r0kk3rzhttps://github.com/mer-hybris/droid-config-sony-nile/blob/master/patterns/jolla-hw-adaptation-discovery.yaml#L1803:04
osum4estshould build_packages.sh -cd be enough after adding the binder?03:09
r0kk3rzim not sure how that plugin gets built03:09
r0kk3rzso you might have to manually build it03:10
osum4estbuild_packages.sh --mw=https://github.com/mer-hybris/ofono-ril-binder-plugin ?03:12
r0kk3rzthat should do it03:12
osum4estalso random question while that's building. don't we need to be on obs and store enabled for our device? i seem to be able to access it and download apps just fine03:15
r0kk3rzthe store usually needs to be enabled03:17
r0kk3rzwhich is just setting the arch in the store backend, but maybe thats been done already03:18
osum4estah. ghosalmartin must have done it when he was working on the port03:19
osum4esthm now rild doesn't want to run...03:38
r0kk3rzcheck logcat -b radio03:39
osum4estnothing03:39
osum4estthere was stuff there when rild was running but now it's blank03:39
osum4estif i manually start rild here's the logcat: https://pastebin.com/wU6X9JPG03:43
r0kk3rzstop ofono04:45
r0kk3rzand start rild again04:45
riniguskimmoli : I've been running 3.0.2 with libhybris .25 from last night. So far all is fine, will continue testing.04:46
rinigusmal: was the backtrace with .31 of any use? What would be the next steps that may help you with .31? I can restore device into .31 later today and look further04:49
r0kk3rzif it works, im not sure why you'd bother updating it04:51
kimmolirinigus: ok05:01
rinigusr0kk3rz: (if it was to me) don't have to update this time, but maybe in the next releases05:04
*** OhYash1 is now known as ohyash07:31
Nokiusr0kk3rz[m]: I was playing lst night a bit with the dontbeevel ci now I have monthly builds may will not work well for droid HW as the dhl needs polish now and then :-/07:33
r0kk3rzNokius: the what with the who now??07:51
T4<adampigg> dont be evil isthe code name for the pine phone08:15
r0kk3rzooooh08:25
T4<StillJustGerd> well now that is a nice codename12:02
TheOnlyBouncerr0kk3rz, hey, ever did a update on the Redmi Note 4 past 2.14 or something?14:04
TheOnlyBouncerI love the current rom, but new features are taunting me14:05
TheOnlyBouncerah 2.1.3.714:09
T4<adampigg> Rn4 is on 3.0.215:46
riniguskimmoli: there is a regression with bluetooth. cannot turn it on anymore. only response is in journal on pressing bt sign: "Sailfish lipstick[4073]: [W] unknown:0 - Can't get: technology is NULL"16:41
rinigusworked without issues on prev release with these backported drivers16:42
rinigus... I wonder if anything changed in bt stack for 3.0.2 that I have to take into account16:47
T4<elros34> grep changed, make sure droid-hcismd-up.sh does not fail16:55
malrinigus: are the drivers in kernel or are you using my backport repo?17:07
malrinigus: if latter did you remember to rebuild those in case you rebuilt hybris-hal17:07
rinigusmal: yes, I have your backport repo in use ("mlehtima/backports-bluetooth"). according to bash history, yes, I did run "make backports" after make hybris-hal. Although, after that I ran droidmedia and audioflingerglue builds as well17:21
rinigusmal: any way to check on device which modules are in use?17:21
malhmm, not sure17:24
rinigusmal: I guess I then should rerun the build and update kernel rpm on device to see whether I have any typos/mistakes17:27
malrinigus: did the modules load correctly?17:41
rinigusmal: I have bnep, bluetooth, skcipher, hci_smd which seem to be relevant listed in lsmod17:45
malok17:47
kimmolirinigus: have fun. /me is having my LSD dose17:51
rinigus:)18:05
rinigusmal: no luck. same with the recompiled kernel. on boot I have few messages from bt that seem to be absolutely fine (like "Bluetooth: Core ver 2.21" with "Backport generated by backports.git backports-20160324-0-g7dba139" above it).18:22
rinigusto be specific regarding what's going on: when I press BT button in pull-down menu on desktop, I get it to "On" status, but without any active background. If I will go to settings after that, BT page is just blank. If I click on BT button again, I get "In progress" notification on the top of the screen18:25
malrinigus: grab both dmesg and journal logs18:25
rinigusmal: will do18:28
rinigusmal: reading journal for info that I shouldn't paste and found an issue with grep invalid option. I think I saw it somewhere fixed for fp2. will read a bit more and then paste the logs18:45
rinigusmal: https://github.com/mlehtima/droid-config-fp2-sibon/commit/22023480f095d152412c74d3310388a94b04915118:46
rinigusmal & kimmoli: it works as soon as grep fix is applied. no idea why it worked before...18:50
malrinigus: ah, that issue19:04
malrinigus: sfos changed from using normal grep to the one included in busybox, those don't support same commandline options19:04
malrinigus: could you check if faq has some bluetooth fix stuff and add note of that there19:05
malrinigus: I forgot about that fix completely19:07
malprobably many others will find that same issue19:07
rinigusmal: sure, I'll look into FAQ20:15
rinigusmal: added a note under backported bt drivers20:23
malrinigus: I think also should go to qcom bluetooth section20:24
malrinigus: I think the original qcom instructions should use some other device as example instead of one that is broken20:28
rinigusmal: agreed. does fp2 have the same script for droid-hcismd-up.sh as used in the older bt stack? if it is, we just can point to your repo20:40
rinigus... its getting late over here, I'll better get out. will catch up tomorrow20:41
malrinigus: I didn't change the script, there are two variants of the script, not sure which one you use20:51
r0kk3rzTheOnlyBouncer: can take a stab at updating it if you want to be a guineapiggz?21:51
TheOnlyBouncerr0kk3rz, yeah of course!21:54
TheOnlyBounceri think you were the one also getting that device running right?21:54
TheOnlyBouncer(though i caught something like that last FOSDEM)21:54
r0kk3rz? i dont have that device21:56
TheOnlyBouncerah k, could be mistaken then21:56
TheOnlyBouncerits pretty lovely, bought it for 170 euro's21:56
r0kk3rzwhats the codename?21:57
TheOnlyBouncerlet me check21:57
r0kk3rzmido?21:58
TheOnlyBouncerr0kk3rz, https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_mido21:58
TheOnlyBouncerits pretty well supported already as well :) just a bummer it is stuck on a older version21:59
TheOnlyBouncerr0kk3rz, happy to donate one as well if you are interested and not have to many phones already :P21:59
r0kk3rzTheOnlyBouncer: https://gitlab.com/sailfishos-porters-ci/mido-ci/tags22:00
TheOnlyBounceronly things that are missing from support are fingerprint and the capacitive keys, but thats doable22:00
r0kk3rzdownload the build artifacts from that22:00
TheOnlyBouncerOh hey thats nice22:00
TheOnlyBounceris it available OTA?22:00
r0kk3rzwould be i think22:01
TheOnlyBouncerhmm let me connect and check :)22:01
TheOnlyBouncerhave not checked in a little bit22:01
r0kk3rzso long as that image was set up properly22:01
r0kk3rzthe thing in settings wont work, it requires a bit of manual poking22:02
TheOnlyBouncerah did not know about that22:02
TheOnlyBouncerany guide?22:02
TheOnlyBouncerah yeah keeps asking for a jolla account or something, some weird loop22:05
r0kk3rzyou can try this https://openrepos.net/content/olf/sfos-upgrade22:05
r0kk3rzyes you need a jolla account22:06
TheOnlyBounceryeah it seems to not login properly22:09
TheOnlyBouncerah nvm works now22:10
TheOnlyBouncerr0kk3rz, is there a deb version of the package?22:11
TheOnlyBounceror is the sfos-update running on the device22:11
r0kk3rzon device22:13
TheOnlyBouncerah makes more sense :)22:16
TheOnlyBouncerr0kk3rz, when running the script it wants to first downgrade to 1.0.2.5, would that be adviced?22:32
r0kk3rzmmm, that seems wrong22:32
TheOnlyBouncerr0kk3rz, https://hastebin.com/udodakidak.cs22:32
r0kk3rzso you're on 2.1 something?22:35
r0kk3rzyou might need to reflash, im not sure how we deal with stop releases on ported devices22:35
TheOnlyBouncerhmm reflashing should not be that difficult though22:36
r0kk3rzbut you can try `ssu release 3.0.2.8; version --dup; reboot`22:37
TheOnlyBouncerah that seems to work22:40
TheOnlyBouncerlol rtfm joey :P22:40
TheOnlyBouncerNICE!22:40
r0kk3rzyeah lets see if it boots afterwards22:40
TheOnlyBouncerhaha true22:40
r0kk3rzjolla defines 'stop releases' that you're supposed to do intermediate upgrades to if you're way behind22:41
r0kk3rzbut we dont maintain that for ports, so its a bit scorched earth22:42
TheOnlyBouncerah makes sense22:44
TheOnlyBouncerrebooting...22:51
TheOnlyBouncerr0kk3rz, update worked!22:53
TheOnlyBouncerwell that was anticlimactic22:53
TheOnlyBouncerworks pretty good!22:53
TheOnlyBouncervideo camera does not work (did not do that in older version as well), fingerprint sensor and capacitive buttons both are not working but rest seems fine!22:55
r0kk3rzreally? cool22:57
r0kk3rzthat was quite a big version jump22:58
TheOnlyBouncerdude the new status bar is killer22:58
TheOnlyBouncerthe only thing i was _really_ missing from android is in there22:58
r0kk3rzyeah, check the top menu too22:58
r0kk3rzandroid style swipe down from top22:58
TheOnlyBounceryeah its great!22:59
TheOnlyBouncerthats the one i was talking about22:59
TheOnlyBouncerr0kk3rz, any way turning in for the night, thanks for the help :)23:08

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