| mal | Mister_Magister: did you ever test the gstqmlgl change? | 14:54 |
|---|---|---|
| Mister_Magister | didn't have time | 14:55 |
| Mister_Magister | but i'll be getting to it soon cause i implemented what i wanted in another project | 15:02 |
| T42 | <nc1x72> Is there a daemon for usb-moded in SFOS? | 18:05 |
| T42 | <nc1x72> | 18:05 |
| T42 | <nc1x72> In UT, there is umtprd and usb-tethering which usually give enough info on what is wrong. | 18:05 |
| T42 | <nc1x72> | 18:05 |
| T42 | <nc1x72> Trying to fix usb on Spacewar | 18:05 |
| T42 | <nc1x72> I mean they give the information when you try to run them manually for instance | 18:06 |
| mal | since you said that the extcon and android_usb states didn't change when you connected usb then I wonder if the extcon patch in fp5 kernel is something that you should not have? | 18:09 |
| mal | could you recheck the /sys/class/android_usb/android0/state and /sys/class/extcon/extcon*/state content when connecting and disconnecting usb cable | 18:10 |
| mal | if none of those change then I suggest you try reverting the extcon change in kernel and see if that helps | 18:11 |
| mal | @nc1x72 could you check if these instructions are clear enough for the codename handling https://github.com/mer-hybris/hadk.sailfishos.org/pull/3 to prevent issues like that for porters | 19:00 |
| T42 | <nc1x72> I have reverted the changes. Compiling now the kernel for testing. | 19:09 |
| T42 | <nc1x72> | 19:09 |
| T42 | <nc1x72> Regarding your PR, it’s clear enough for me. However, there’s a caveat. When you Android side build (i.e droid-hal and droidmedia) still fail because this export gets passed to LineageOS build. | 19:09 |
| T42 | <nc1x72> I have to manually export “Spacewar” prior to running “make droid-hal droidmedia” | 19:09 |
| T42 | <nc1x72> Another way was to run “breakfast Spacewar” instead of “breakfast $DEVICE”. | 19:09 |
| T42 | <nc1x72> Edit: | 19:11 |
| T42 | <nc1x72> | 19:11 |
| T42 | <nc1x72> When you run “export DEVICE=spacewar” (with lowercase s) Android side build (i.e droid-hal and droidmedia) still fail because this export gets passed to LineageOS build which expects Uppercase. | 19:11 |
| T42 | <nc1x72> I had to manually export “Spacewar” prior to running “make droid-hal droidmedia” | 19:11 |
| T42 | <nc1x72> Another way was to run “breakfast Spacewar” instead of “breakfast $DEVICE”. | 19:11 |
| T42 | <elros34> AFAIK you need HABUILD_DEVICE<upper case device codename> in .hadk.env | 19:13 |
| T42 | <nc1x72> Yeah I didn’t export it that way indeed | 19:15 |
| mal | @elros34 yes, forgot about that, thanks | 19:20 |
| mal | @elros34 is it better now? | 19:24 |
| mal | I'll add a note to the android side build instructions also | 19:27 |
| mal | done | 19:29 |
| T42 | <b100dian> I am trying to hunt down why the nagara xqcq54 ssu-kickstarts package uses, for the testing repo, an url that has "testing:" in it but finishes with sailfishos_latest_aarch64 🤔 | 21:07 |
| T42 | <b100dian> There's a small adaptation made by rinigus like here, https://github.com/sailfishos-sony-nagara/community-adaptation/commit/798e2009cf308d3fb3f878d666014bbc5941c556 | 21:09 |
| T42 | <b100dian> But that gives correct URLs for adaptation-community.ini in droid-config-xqcq54 | 21:11 |
| T42 | <b100dian> Something fishy, maybe unrelated: DEVICE=xqcq54 HABUILD_DEVICE=pdx224, howevert | 21:13 |
| T42 | <b100dian> the build log from here mentiones pdx223 twice https://build.sailfishos.org/build/nemo:testing:hw:sony:nagara:5.0/sailfishos_5.0_aarch64/aarch64/droid-config-xqcq54/_log | 21:13 |
| T42 | <b100dian> `cumulate droid-hal-pdx223-devel-0.0.6-202512191831` :hmm: | 21:14 |
| T42 | <nc1x72> Digging to Spacewar usb issue, It does seem like device doesn't use extcon. I booted to sfos recovery. android0/state said CONFIGURED whereas extcon*/state remained with =0 on everything. Where to go from here? Also reverting the commits related to extcon didn't help. | 21:15 |
| mal | so does android0/state also change correctly if you disconnect usb? | 21:20 |
| mal | if so then just change this to 1 and extcon to 0 https://github.com/mlehtima/droid-config-fp5/blob/master/sparse/etc/usb-moded/usb-moded-fp5.ini#L11 | 21:21 |
| T42 | <nc1x72> I wouldn’t know unfortunately. Because I tested in sfos recovery | 21:21 |
| mal | in your device specific config | 21:21 |
| T42 | <nc1x72> Testing now | 21:21 |
| T42 | <nc1x72> I’m also facing a weird issue, encryption doesn’t seem to work. After a reboot, I enter the password to decrypt, it gets stuck for too long and I’m forced to reboot (sometimes I have to reboot many times to get to home screen). Is it possible to temporarily disable this encryption? | 21:24 |
| mal | yes, https://github.com/mlehtima/droid-config-fp5/blob/master/patterns/patterns-sailfish-device-adaptation-fp5.inc#L78 | 21:28 |
| mal | commenting out that line in patterns removes encryption | 21:28 |
| mal | of course you need to build a new image | 21:28 |
| mal | and droid-config package before that | 21:29 |
| T42 | <nc1x72> Need to rebuild just droid-config then mic? | 21:34 |
| mal | yes if you want to remove encryption | 21:35 |
| mal | maybe you could also do the usb-moded change at the same time | 21:35 |
| T42 | <nc1x72> Good idea. I'm gonna cleanup and rebuild everything these changes | 21:36 |
| T42 | <nc1x72> One last question tho, don't these lines need change as well (regarding usb) ? https://github.com/SailfishOSSpacewar/droid-config-Spacewar/blob/master/sparse/etc/usb-moded/usb-moded-spacewar.ini#L2-L5 | 21:42 |
| mal | gadget_udc_device possibly, other probably are ok | 21:44 |
| mal | I did ask you to check that udc device earlier | 21:45 |
| mal | nephros: I noticed you had built dav1d on obs, I have existing packaging already https://github.com/mlehtima/dav1d I also have in aom | 22:51 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!