Friday, 2020-05-29

r0kk3rztiming issue on startup then ?00:01
T42<edp_17> I don't know. What I done was: created a script that gets the new mac and using this and the previous wifi_*_manafed_psk dir in  /home/.system/var/lib/connman/ and creates a new wifi_*_managed_psk directory then it updates the settings file in the new dir. If the wifi was on before the boot, it turns off, then back on after the magic.00:06
T42I created a service that runs the script before and after connman.service. And it does the job. πŸ˜„00:06
r0kk3rzthats a hack and a half00:06
r0kk3rzyou should fix the real issue00:07
T42<edp_17> Yeah I know, but I don't have enough knowledge. There are toooo much info in the logs (for me at least) and I am not sure what I should look for.00:09
T42<edp_17> r0kk3rz: Can you help with the vibra, please? @elros34 advised me to use the latest changes from mer-hybris/android_system_core, but I don't know how.00:13
mariogripmonich: Hey :) I'm from Ubports and got some question on ofono and the history about the 2 ril drivers, first whats the reason there was made 2 version? One was made by canonical and one by jolla but are there any overlap so they can be merged to one? I see from the history that rilmodem was made firt but then the ril one got created to be able to have multi sim, but both now have muli sim support but jollas one seems to be more00:29
mariogripadvanced at this stage. Is there any way we can merge these and upstream a common version?00:29
monichmariogrip: the short answer is that it's extremely unlikely that our ril stuff would ever get merged upstream00:33
mariogripmonich: can you give me the tldr of the fundamental differences between them and why a new one was created?00:35
monichmariogrip: when it started there was no ril support in ofono upstream at all. we started with a clone of canonical's stuff00:36
monichand then those clones diverged and then canonical became upstream00:37
monichours is using our own libgrilio to actually talk to ril00:37
monichthat supports different transports - sockets and binder00:38
monichbinder support pulls in libgbinder00:38
monichand so on00:38
mariogripI assume there is no overlap then? so a partial merge wouldn't even be possible?00:38
monichat this point there's very little overlap left, I think00:39
monichalthough I haven't really followed upstream development recently00:40
monichonce they announced that they are switching away from glib, I lost my interest :)00:41
mariogripright now we have 3 different forks of ofono for ubports, rilmodem one, jolla ril and upstream for pinephone00:41
monichyeah, that sucks00:42
monichat least I'm trying to keep our fork compatible with upstream dbus interfaces :)00:42
monichadding jolla specific dbus interfaces instead of extending the original ones00:43
mariogripthey partly switched to ell, and tbh ell is better fit for it as its much more lightweight00:44
mariogripbut not all parts, just the heavy ones iirc00:45
monichjust glib is more lightweight than glib + ell00:45
mariogripthis is true, but it's quite an cpu/memory improvments even with glib + ell00:46
T42<birdzhang> @edp_17
monichmariogrip: my feeling is that it's going to become as big as glib of even bigger if it ever becomes as functional as glib00:48
monichand we would end up with two glibs basically, each with its own set of bugs00:49
T42<edp_17> @birdzhang: Yeah, I got this but I am not sure what should do with it? Clone? Build? How? Which branch?00:49
mariogripmonich: I hope it stays a small portable lib, as it was inital designed for. but I agree we dont need another glib, but something smaller and faster then glib is ineeded imo00:51
monichI'll wait and see00:53
mariogripmonich: I guess I need to figure out how we at ubports can merge it all into one ofono01:00
mariogripbut thanks for you input :)01:00
r0kk3rz@edp_17: you will already have that cloned, you might just need to update01:26
T42<edp_17> Okay. Thanks.01:28
T42<edp_17> In /usr/bin/droid the is not executable. Is it correct?01:28
T42<gischpelino> is the oneplus3 community port of sfos still maintained? I have bt problems with (bluetooth-rfkill-event-hciattach updated from 1.0.6 to 1.0.8 and stopps working). Upgrade to breaks more, because not ready to install.09:05
r0kk3rzi dont think anyone is maintaining it at present09:23
riniguspiggz: I will try to finish small changes in one other project and then will continue with fp after that. plan to insert some debug messages to see where it breaks10:07
rinigusstill no logcat logs from xperia 10 available (or any other 'official' device). those would be handy, but should be possible to debug without10:08
riniguspiggz: your solution is still on top of biometryd, right? are those daemons that you wrote are using that as a backend?10:09
T42<edp_17> I'd like to run a script via a service before each reboot and shutdown. I though, could plug this script in before the shutdown.service but seemingly this is not the proper place. Can you let me know how to do it properly, please?10:12
piggzrinigus: no, its completely standalone10:16
piggzive taken some of the biometryd code for plugging into the hal functions, then reimplemented it10:17
piggzjust adding some more enums now from running strings on sailfish-fpd10:17
riniguspiggz: what shoud I test then? and what I should make to run10:20
piggzrinigus: by all means test biometryd, as thats a known working entity .... that will atleast give confidence to move onto my daemon.... or, you can run my daemon against its test application, i think the code will be easier to understand if there are problems10:22
piggzthe daemon needs to build against libhybris ... and requres the android library from biometryd10:22
riniguspiggz: understood!10:29
piggzrinigus: for info, i can now nearly enroll using my daemon from the settings devicelock page :)10:39
T42<gischpelino> r0kk3rz: thank you. :(   I cannot do it, but can send 50€ to motivate.10:51
r0kk3rzyou probably could do it, its not hard its just testing and debugging10:54
riniguspiggz: great! out of curiosity,. what was a reason for writing new daemon?11:05
T42<Amber %lastname%> Hello can anyone help me with this its showing me sdk manage command not found when i run the below commands13:30
T42<Amber %lastname%>
T42<Amber %lastname%> i am tring to install SDK13:30
T42<elros34> Your paste doesn't show prompt nor failure output but I guess you are not running it in platform sdk13:41
T42<Amber %lastname%> @elros34 [Your paste doesn't show prompt nor failure out …], yes bro i was running in terminal13:42
T42<Amber %lastname%> okay i have successfull installed SDK coz i can now see the help commands when i run sdk-manage β€”help13:46
T42<ankaos> @Amber %lastname% [okay i have successfull installed SDK coz i ca …], πŸ‘13:46
T42<ankaos> Los 15.1 problem13:50
T42<edp_17> Guys, I am trying to make bluetooth work. The bt driver is bcm4358 in kernel. My problem is there is no bcm*.hcd file in /system/bin/ or anywhere else. What I have is /system/vendor/firmware/bcm4358A0_V0033.0000.hcd13:57
T42<edp_17> Without the proper bcm*.hcd file I cannot use the brcm_patchram_plus.13:58
T42<edp_17> Hmmm. I might need to use hciattach instead.13:59
T42<edp_17> For hciattach, I would need a bcm*.hcd file in /system/etc/firmware/ but there isn't any.14:01
T42<edp_17> What am I missing here?14:01
T42<elros34> How do you want to figure out other params like tty port and baudrate? Ready your device/ repo, it has all information you need including firmware name14:07
T42<edp_17> I have checked dmesg and I think need to use /dev/ttySAC3, the port and baud rate I wanted to try what I used for the S2.14:09
T42<edp_17> Thanks! I just went into the device/treltexx/bluetooth and there is a bt_vendor.conf which has the UartPort = /dev/ttySAC3 and FwPatchFileName = BCM4358A1_V0054.0094.hcd14:11
T42<edp_17> I only have the BCM4358A1_V0054.0094.hcd in /system/vendor/firmware/ on the device. I'll use this as fw_patch.14:16
T42<edp_17> I am not sure how to find out the baud rate.14:19
T42<elros34> same place: somewhere in  device/ dir14:20
T42<edp_17> Thanks, that was in the trelte-common dir. πŸ‘14:21
T42<elros34> You should really read it all always when porting sfos to new device14:22
T42<edp_17> This info was new to me as previously I never needed to look into those files myself as you helped me with the exact values. However, I prefer to know where to see because this way I can do more by myself and only ask if something is failed. So, thank you!14:29
T42<elros34> IIRC I used random values from net :P14:30
T42<edp_17> Until they work, I don't mind. :P14:31
T42<edp_17> What I cannot see in those configs is the value for --scopcm. Is it possible that I do not need that?14:32
T42<elros34> I guess: SCO_I2SPCM_IF_ROLE  and SCO_USE_I2S_INTERFACE . You would have to read hciattach headers/comments to understand how to convert it to --scopcm14:34
T42<edp_17> Yeah, I have got SCO_USE_I2S_INTERFACE = TRUE and SCO_I2SPCM_IF_ROLE = 014:36
T42<edp_17> BT works (at least it can be paired with my XA2) when I run brcm_patchram_plus manually. 😊 Later I'll try to make it properly work but it is promising.14:59
T42<edp_17> I used the same --scopcm values that I used on the S2. It may not correct but that is for audio transmission and I don't worry about that right now.15:01
T42<Amber %lastname%> can anyone help me with the below please check the link i am getting some unrecognized option error15:49
T42<Amber %lastname%>
T42<naive17> Echo your env variables16:03
T42<naive17> Maybe they are empty16:03
T42<naive17> Try16:04
T42<naive17> echo $VENDOR-$DEVICE-$PORT_ARCH16:04
T42<naive17> If it outputs -- there's your error16:04
T42<edp_17> Amber : if you followed hadk you won't get these kind of errors. I recommend that.18:11
T42<ankaos> any help?18:14
riniguspiggz: I will try with your daemon as it seems to have less abstraction and (hopefully) should be easier to debug. I should use sailfish-fpd-community-test with it, right?19:27
piggzrinigus: yes, i just pushed a fix for the test app to use the correct interface19:46
T42<adampigg> rinigus: \o/20:34
riniguspiggz: congratulations!21:24
T42<adampigg> Rinigus: still stuff to implement,  like unlock!21:31
rinigus@adampigg: just managed to enroll with your test software :)21:32
rinigusbut it seems to have issues with clearing the store21:32
T42<adampigg> Oh, awesome. .what was wrong?21:33
rinigus@adampigg: something was wrong with handling c++ future/promises; and test is trying to clear first - that did not work there either.21:36
rinigusbut it wasn't really enrolling on other software either, so hard to say what was wrong specifically21:36
rinigusso, great progress thanks to you! I'll look tomorrow what's wrong with clearing the store...21:38
T42<edp_17> @elros34: Bluetooth is working. πŸ˜„22:34
T42<elros34> great!22:34
T42<edp_17> Now I am trying to fix the Default USB mode change problem.22:35
T42<edp_17> By the way do you know how to wake up the screen by a command?22:40
T42<elros34> mcetool for sure have such a power22:42
T42<edp_17> Thanks. And how can I monitor which button was pressed?22:43
T42<elros34> evdev_trace -t22:45
T42<edp_17> Oh yes, thanks.22:47
T42<edp_17> Do you know where the selected Default USB mode is stored and how to read what's stored?23:30
T42<edp_17> I have found it: /var/lib/usb-moded/usb-moded.ini23:40

Generated by 2.14.0 by Marius Gedminas - find it at!