Sunday, 2026-05-10

Mister_Magisterhmm it sometimes still gets stuck in charging, i probably have to blacklist some more devices00:00
Mister_Magisterhmm mount --bind in droid-hal-early-init did not do it so maybe it's not hal00:03
Mister_MagisterI'll just bamboozle it and simply not build it as module, check mate00:11
Mister_Magisterhuh, aida64 instantly recognized phone is no longer charging and sfos not00:17
Mister_Magisteryaay charging limiting works00:47
Mister_Magisternow i jsut have to figure out loading of correct module00:47
T42<Mister_Magister> i blacklisted everything but battery and wireless and it still gets hang up despite sysfs paths changing correctly, ig it's just mce things00:56
Mister_Magisternah i had a typo, now i added 2 more devices to blacklist and it seems to be working fine01:12
Mister_Magisterwith just battery and wireless it detects usb charging but whateveeer01:12
T42<b100dian> mal: fp5 has libI420colorconvert?10:49
Mister_MagisterI shall write the usb service in D11:24
Mister_Magisteryes you heard that right11:24
rinigus@b100dian: I have updated the kernel and its modules. also dropped some kernel options as they don't apply for our kernel version (https://github.com/sony-nagara/android_kernel_sony_sm8450/commit/75525654e0b57f6e2f2e2db769b29ac8ba682168)11:37
rinigusthey were just ignored during the build11:38
rinigusI wonder who should be pinged for reviewing this: https://github.com/sailfishos/mce/pull/4311:39
rinigusb100dian: I think the complains regarding non-working charging limitation for nagara is due to non-merged MCE PR above. while all should work with USB charging, wireless is ignored without it11:41
Mister_Magisterrinigus: ping our best guy11:42
Mister_Magisterlastest commits are only from him and spiiroin no longer works [*]11:42
T42<b100dian> rinigus: nice! I ordered a wireless charger out of curiosity, but don't have it yet11:43
Mister_Magisterwireless chargers are sweet11:43
riniguslet's hope that the best guy(s) will pick it up already via message over here without ping. re spiiroin - I hope he is doing fine11:43
Mister_Magisteri'm using one on miami, used one on flo11:44
Mister_Magisterrinigus: well if i wasn't transparent already i meant mal11:44
rinigusit was11:44
rinigusjust not nice to get pinged all over the place :)11:44
Mister_Magister:D whoops11:45
Mister_Magisterbrother i'm in dependency hell trying to get d to build11:45
T42<b100dian> it's a race to the bottom, if you don't ping, others will11:45
Mister_Magistermmmmmmmmmm f it, c++ it is11:49
T42<b100dian> Mister_Magister: now you have two problems11:49
Mister_Magisterhm?11:49
T42<b100dian> It's usually about regex or xml the quote, but I would say C++ fits too11:50
malrinigus: need to do some testing with that to make sure it works on all devices12:01
Mister_Magistermal: so i made the service that writes none/peripheral depending on usb charging and sfos always says it's "charging only mode in use" no matter ifi  select any other default usb mode or select "always ask" also the usb seems to be stuck in mass storage mode, as if usb-moded wasn't doing anything at all12:18
rinigusmal: thanks12:18
Mister_Magisterandroid0 is changing correctly12:18
Mister_Magisterhmm hold on a second12:23
Mister_Magisterusb-moded can read usb status from udev no? it even states so in readme12:24
Mister_Magisterah it only reads charging mode12:25
Mister_Magisterit doesn't infere from it that usb is connected12:25
Mister_Magisterandroid_tracking = 1 and my problem is solved12:26
Mister_Magisternow we can play around with ncm12:27
Mister_Magistersweet ncm works, but DHCP doesn't xd12:33
Mister_Magisterit created usb1 interface with no ip assigned12:34
malit created second interface?12:34
Mister_Magisterye12:35
Mister_Magisterusb112:35
maldoes the usb0 seem ok?12:35
Mister_Magisterye12:35
Mister_Magisterhttps://paste.opensuse.org/pastes/f96af1e0a6d012:35
maland you have the connman config?12:35
Mister_Magisterhere's config12:35
Mister_Magisteryes12:35
maltry blacklisting usb112:35
Mister_Magisterwould be nice to have the ncm12:36
malyou mean the second one if the ncm?12:37
malmaybe you need to do something it prevent the rndis one12:37
malif init sets that up12:37
malyou could that the telnet disabling thingy12:37
mal*try that12:37
Mister_Magisterbut can I disable telnet in ramdisk?12:38
Mister_Magisteryou mean to make file init_disable_telnet right12:38
malyeah12:38
malramdisk only sets up ramdisk in error cases the, the rootfs init script does set it up in community builds unless init_disable_telnet is there12:38
mal*only sets up usb12:39
Mister_Magistermal: about integrating that service in to usb-moded, usb-moded already listens to udev events of charging being connected which is what my service does, then i could just do like charging_tracking or something for it to enable usb state based on charging detection, though it would have to write state to the driver too12:39
Mister_Magisterbut sounds entirely doable12:40
Mister_Magistertho i could be naive12:40
malyou can try12:40
Mister_Magisteri have all day today so maybe ill click it, but i think i'll dig into volte plugin hanging up12:41
Mister_Magistertho i might not do that because enabling otg is gonna be pain12:42
Mister_Magisterhmm no, no connection over ncm12:44
Mister_Magisteri removed the ncm line and rndis doesn't work like at all12:45
Mister_Magisterlol i changed function_rndis        = ncm.usb0 to usb1 and then changed interface = usb1 and now i have usb0 usb1 and usb212:47
Mister_Magisterthat smells like some configuration issue12:47
Mister_Magisternow I have usb312:48
malit creates new one with every reconnect of usb?12:49
Mister_Magisterhmm not sure12:49
Mister_Magisterlet me do some testing12:50
Mister_Magistermal: so when i connect usb, it creates usb1 and the state is `usb1: <BROADCAST,MULTICAST` etc, and usb0 becomes `usb0: <NO-CARRIER,BROADCAST,MULTICAST,UP>` then if i disconnect they swap12:54
Mister_Magisterusb1 becomes no-carrier12:54
Mister_Magisterif only connman would set up ip on usb112:55
malblacklist usb012:55
Mister_Magisteridk why it adds new device though12:56
malcopy NetworkInterfaceBlacklist from connman main.conf and append usb0 in your custom config12:56
Mister_Magisternow ip is on usb1 but it created usb212:56
malafter doing what?12:56
Mister_Magisterrestarting connman and reconnecting usb12:57
Mister_Magisternow i have both and it doesn't ping https://paste.opensuse.org/pastes/444705c94b1213:00
malshow the connman config modification13:00
maland usb-moded one also13:01
Mister_Magisterhttps://paste.opensuse.org/pastes/7367ecae6c6613:01
Mister_Magistertop portion is connman13:01
Mister_Magisteri was too lazy to create 2 pastes13:01
malI wonder about that ncm line13:04
malso is this now with rndis prevented at boot?13:05
Mister_Magisteri did create init_enter_debug yes13:05
malyou mean init_disable_telnet13:05
malalso that FallbackDeviceTypes should it have usb113:06
Mister_Magisteryes13:06
malbut does usb1 only appear on restart of connman or also in other cases?13:07
Mister_Magisterusb1 appears when i connect usb for the first time13:07
Mister_Magistermal: you son of… that was it13:09
Mister_Magisterit's working flawlessly now, even dhcp13:09
malhehe13:09
Mister_Magistertelnet is connection refused but ssh works so whatever13:09
maltelnet is not running because you have init_disable_telnet13:10
Mister_Magisteryeah that makes sense13:10
Mister_MagisterI'll pretend that OTG doesn't exist for now and jump onto volte plugin13:10
malprobably your external usb service should be able to handle that also13:11
Mister_Magisterthat's the plan but i don't want to figure out how to enable sending power when neither you nor android guy know how to do that, so instead i'll try to fix hanging up, which is the only hang up when it comes to daily driving it at this point13:12
Mister_Magisterpun intended13:12
malwell you need to provide content of the power_supply sysfs paths and iio13:14
Mister_Magisteryeah some other day i'm not in hurry to fix it as i use OTG very rarely13:16
Mister_Magisteri also need to debug ngfd due to the dreadful ui sounds volume13:18
Mister_Magistervolte plugin seems like fun thing to work on though13:19
Mister_Magisteroh the volte plugin is not installed lol forgot to add it to patterns13:21
Mister_Magistervolte registered instantly it's so beautiful13:22
maldo you see anything in logs about ngfd or pulseaudio or stuff13:24
Mister_Magisterbefore that, when calling the screen goes black as if proximity sensor was covered (it's not) and it's not ondemand thing because it's on by default now13:25
malcsd prox test works fine?13:26
rinigusb100dian: for eSIM, I need just to update 2 manifest files? https://github.com/sony-nagara/android_device_sony_sm8450-common/commit/7154844c723d5504a98592de046ebfffe2c79fe1 (changes on android side) and then track it further on the issue https://github.com/sailfishos-sony-nagara/main/issues/5613:26
rinigusno rush with reply ... I'll be afk for some time :)13:26
Mister_Magistermal: yeap13:26
Mister_Magistermal: ngfd doesn't output anything13:28
Mister_Magisterand getting pa logs is gonna be tricky13:28
Mister_Magisterngfd is reacting correctly because it vibrates13:29
Mister_Magisterand overall volume control works fine too13:31
Mister_Magistermal: hmm I added hw_volume=0 and the ui sounds are quieter now13:42
malok13:45
Mister_Magisteri still need to figure out why wrong module is being loaded hmm13:45
malwrong module?13:49
Mister_Magisteryeah so i modified qpnp_adaptive_charge and have it in /lib/modules but one from vendor is being loaded instead13:50
Mister_MagisterI think android loads it13:50
Mister_Magisteryeah i now got nothing sfos side to load it yet it's loaded13:52
Mister_Magisteri tried mount --binding the module but that didn't help13:55
Mister_Magisternow i have seriously no clue what loads the wrong module, i removed every mention of it13:58
malnot sure what the issue is, if you have that module in modules.load.d or something then it would load it from /lib/modules and then when android side tries later it would not do anything because the module is already loaded14:02
Mister_Magisterwell but wrong module IS being loaded though14:02
maleven if you use modules.load.d?14:03
malhow is that possible14:03
Mister_Magisterhttps://paste.opensuse.org/pastes/274807fea2dc14:03
Mister_Magistersee for yourself14:03
Mister_Magisteri don't know what's happening14:04
Mister_Magistervendor module doesn't have the change that adds charging_enabled, mine does14:04
maldo you have ramdisk modules? is that there?14:05
Mister_Magisterramdisk modules? not sure but i did flash the kernel14:05
Mister_Magisterand vendor_boot and dtbo14:06
malcheck out/ for vendor_ramdisk/lib/modules14:06
Mister_Magistereven if i remove it from modules-load.d it still is being loaded14:06
malso probably it's in vendor_ramdisk and being loaded from vendor_boot in init14:07
Mister_Magisterout/target/product/miami/vendor_ramdisk/lib/modules mhm14:07
malso maybe you need to flash also vendor_boot14:07
Mister_Magisterand it is there14:07
Mister_Magisterbut i already said i already flashed it14:07
malyeah so you forgot to flash vendor_boot after rebuild14:07
maloh14:07
Mister_Magisterno i didn't14:07
maland that module contains it?14:07
malhow did you rebuild kernel?14:08
malmake hybris-boot?14:08
malor make hybris-hal?14:08
Mister_Magisterhybris-boot14:08
malI suspect that didnt rebuild vendor_boot14:08
Mister_Magisterhmm14:08
maltry make hybris-hal14:08
Mister_Magisterlet's try hal then14:08
malyeah, vendorbootimage is not dependency of hybris-boot in here https://github.com/mer-hybris/hybris-boot/blob/master/Android.mk14:10
Mister_Magisteraww14:10
Mister_Magistermaybe it should be?14:10
malmaybe yeah14:10
Mister_Magistermaybe indeed14:10
malbut usually hybris-hal is used anyway14:11
Mister_Magisteri'm trying to save 1h of time14:11
malit only builds things that have changed14:11
malat least it does on my builds14:12
Mister_Magistersure but before it gets to the building…14:12
Mister_Magisteractual building is the fastest part14:12
Mister_Magisterwish we had wide angle camera but whatever i wanna sit down and debug hanging up14:13
Mister_Magisterwith hanging up fixed i'll be able to switch to this device for  calls14:14
Mister_Magistermal: I don't know if you remember but if you remember we did buncha changes to ofono-binder-plugin-ext-qti for oneplus 6 right? well i just tried it without those changes on the device i'm currently porting and it no longer registers14:42
Mister_Magisteroh well nevermind it just registered14:42
Mister_Magisterand also the charging_enabled issue is resolved now many thanks14:43
Mister_Magisteri wish it stopped turning my screen off14:48
Mister_Magisterhmmm14:51
Mister_MagisterI get a lot of "failed to parse incoming SMS data"14:51
Mister_MagisterI wonder how can i debug the ext_qti plugin14:51
T42<adampigg> @Mister_Magister whats your hangup issue?14:57
Mister_Magister@adampigg i cannot end volte call14:57
Mister_Magisterand even if someone picks up it still says "dialing"14:57
malI understood it's because the ofono-binder-plugin-ext-qti doesn't implement volte hangup call14:57
Mister_Magistereven if other end ends call, call never ends14:57
Mister_Magistermal: and we enabled that one function and it changed nothing14:58
T42<adampigg> ah ... the mtk plugin isnt that bad ... i did have some issue with ending calls, and did this, but i think a vendor update might have fixed it properly anyway https://github.com/piggz/ofono-binder-plugin-ext-mtk/compare/hangup-hack?expand=114:58
Mister_Magisterbut it's not just hangup, it doesn't change state indicate that call is in progress14:58
Mister_Magisterit's always dialing14:58
Mister_Magisterand i cannot unblock the damn screen14:58
Mister_MagisterI'm having a call and the plugin is spamming about "incoming sms data" there's no incoming sms data15:02
Mister_Magisterso the incoming sms data is indicator id 26 and it always fails to parse15:08
Mister_Magistercorrect me if i'm wrong but it looks like 26 is not in fact incoming sms data15:08
Mister_Magisterwhat if its the call state indicator that i'm missing?15:09
Mister_Magisteryeah and incoming sms did not trigger the indicator 26 at freaking all15:10
Mister_Magistermal: it seems this confusion is in QTI_RADIO_IND_1_2, can we somehow limit the indicator version to 1.1 or not doable?15:11
Mister_Magisterso i made the 26 execute qti_radio_ext_handle_call_state_indication and guess what? when hanging up the hang up method was actually called this time15:15
Mister_Magisterso my hunch was correct15:15
T42<b100dian> rinigus: yes, normal RIL slot enablement15:16
T42<b100dian> To test it under Lineage you have to install an app that manages the sim. I only tested this with gapps, but you could test directly with SimPro / lpac under sailfish15:17
Mister_Magisterthere was even status 29 which does not have handler lol15:18
malhmm, but 26 is the code for incoming sms indication in 1.215:25
malcall state changed indications are 1, 23 and 24 in 1.0, 1.1 and 1.215:26
rinigus@b100dian: I am planning to add it to overlay - no need to change much due to a manifest. at least that's my hope. does it become immediately visible somehow on SFOS? without lpac15:28
T42<b100dian> rinigus: that would work, yes15:28
T42<b100dian> But you won't have the option of using Lineae to register the esim if the lpac/SimPro combo does not work15:29
Mister_Magistermal: sure but it fails and if i send the data to call state changed it parses without issue15:31
Mister_Magisterso i'm telling you something is afoot15:31
Mister_Magisterand i'm 10000000% sure nobody is sending me sms15:31
Mister_Magisterand sms are arriving withuot triggering the 2615:32
Mister_Magisterand there's not even code 29 and yet that one arrives too15:32
Mister_Magistersomething's wrong with the codes15:33
Mister_Magisterespecially since call is always dialing15:34
Mister_Magistermal: i just removed the switch and forwarded all 1.2 codes into qti_radio_ext_handle_call_state_indication and guess what? call is now in progress, call ends correctly, i jsut can't hang up but that's beside the issue15:39
Mister_Magister29 is NOT the call state data15:40
Mister_Magister26 definitely is15:40
malwhat? 29 is part of 1.3 and means incomingCallAutoRejected15:41
Mister_Magisterit was outgoing call15:41
Mister_Magisterthere was no incoming call15:41
Mister_Magisterso on this phone it is not :)15:41
Mister_Magisteralso where did you get that info15:41
Mister_Magisterthe ext_qti plugin doesn't support 1.315:42
Mister_Magisterand i'm getting 29 on 1.215:42
malin internal volte plugin 26 is incoming sms15:42
Mister_Magisterit's in ext_qti plugin too15:42
Mister_Magisterbut on this phone it is not15:43
Mister_Magisterwhich i've proven in above messages15:43
malthat would be very odd15:43
Mister_Magisterwell it's reality15:43
Mister_Magister26 always fails to parse as incoming sms data and i'm absolutely sure there is no incoming sms so that's just bs15:43
malwhat happen if you stop it from using 1.215:43
Mister_Magisterthat's what i asked above15:43
Mister_Magister[17:11] <Mister_Magister> mal: it seems this confusion is in QTI_RADIO_IND_1_2, can we somehow limit the indicator version to 1.1 or not doable?15:43
malso why not test it15:43
Mister_Magisteridk how15:43
Mister_Magisterhttps://gitlab.com/ubports/development/core/hybris-support/ofono-binder-plugin-ext-qti/-/blob/main/src/qti_radio_ext.c?ref_type=heads#L570 inside here, 26 is qti_radio_ext_handle_call_state_indication and 29 also arrives15:44
malhttps://gitlab.com/ubports/development/core/hybris-support/ofono-binder-plugin-ext-qti/-/blob/main/src/qti_radio_ext.c?ref_type=heads#L88315:44
Mister_Magisterchanged it to 1.115:46
Mister_Magisteraaand the call doesn't change state and never ends15:48
Mister_Magisterbut it is sending 25 now15:48
Mister_Magisterit's sending 25 on 1.115:48
Mister_Magisterwell then let's try 1.015:49
Mister_Magistersomething is highly messed up15:50
Mister_Magistermal: hmm 26 is sms and 24 is call state, the phone is sending 26 but means 24… now i switched to 1.1 and it sends 25 while 1.1 only has 2315:50
Mister_Magisterdo you notice a pattern15:51
Mister_Magister29 then becomes 27 which is VOPS_CHANGED_INDICATION15:51
Mister_MagisterI think it's just 2 too high15:51
Mister_Magisteron 1.0 it did end the call (tho i couldn't hang up15:53
malwtf15:53
malwhat is the call indication in 1.0?15:54
Mister_Magister115:54
malso that is correct15:54
maldoes sms work in 1.0?15:54
Mister_Magisterwell it works-ish can't hang up and call is never in progress15:54
Mister_Magistersms worked fine even on 1.215:55
Mister_Magisterlet me try without our hangup change15:55
malwhat? but you just said sms indication was wrong in 1.215:55
Mister_Magisteri already told you no sms was incomding15:56
Mister_Magisterincoming*15:56
Mister_Magisterit was call status info15:56
Mister_Magisternobody was sending me sms when i was calling15:56
Mister_Magisterand when i asked for sms it arrived without triggering ext_qti  whatsoever15:56
malI can't follow anymore what the status is in 1.015:56
Mister_Magisteri think i'm explaining it very clearly15:57
Mister_Magisteryou just have to get past that 26 is NOT sms indication15:57
Mister_Magisterit's call status info15:57
malI'm talking about 1.0 now15:57
malforget 1.215:57
Mister_Magisteryes on 1.0 the call is never in progress, i cannot hang up, but the call ends15:57
malbut you said it sent indication 1 in 1.015:58
malfor call15:58
Mister_Magisteryes15:59
Mister_Magisteri'm just confused as you are about that one15:59
Mister_Magisterokay15:59
Mister_Magisterwithout our hangup change i CAN hang up15:59
Mister_Magistermal: on 1.0 sms still work16:01
Mister_Magisterin ofono all you get from sms is ofonod[40989]: incoming sms, 35 bytes16:01
Mister_Magisteryou don't get the imsradio016:01
Mister_Magisterhence my suggestion that it doesn't touch ext_qti at all16:02
Mister_Magisteri'll try real call soon16:02
Mister_Magistertho i'm really tempted to restore 1.2 and -2 it xddd16:03
Mister_Magistermal: okay on 1.0 and proper call the call is in progress i see the counter, I can talk no issue, i can hang up16:08
Mister_Magisterhanging up works too16:08
Mister_Magistermal: so all issues are resolved! 🎉16:09
Mister_Magisterexcept one16:09
Mister_MagisterI cannot turn on the screen16:09
Mister_Magistermal: apparently motorola likes to do bullshit like this16:14
Mister_Magisteri'll see if i can change to 1.0 without modifying code16:15
Mister_Magister…no16:16
malit doesn't support any config file for selecting interface version16:17
Mister_Magisteryeah16:17
Mister_Magisterdo you have any idea for the display bug? if i press the power button many times i can bug it to stay on16:18
Mister_Magisterit behaves like so: it goes dark, i press power button, it blinks and goes dark again16:18
malhave you tried witout ondemand prox?16:18
Mister_Magisteri shall16:19
Mister_Magistermal: without on-demand thingy it just never turns off the screen16:20
malhmm16:22
Mister_Magisterits like one last hurdle (beside usb otg)16:23
Mister_Magister(and dt2w16:23
Mister_Magistermal: question, you said something that waydroid won't work because of too new android base… does that apply to my port too?16:27
Mister_Magisteroh yeah mine is a15 and you said a14 is too new16:27
Mister_MagisterI will now build fresh image and see if all the fixes are there16:29
T42<Mister_Magister> @b100dian would you be as kind as to introduce me to wonderful world of camera2 api? xd16:46
T42<b100dian> Not that I know much, but what are you trying to solve? For sake it was unusable oversharpening defaults from camera1.16:48
Mister_Magisterwell i want to yeet sharpeining and denoising, it's bane of ALL devices16:49
Mister_Magister+ i wanna see if second back camera would show up16:49
Mister_Magistercan you disable sharpening and denoising on camera1 api? you can't right?16:49
T42<b100dian> I don't know how16:50
Mister_Magisteryeah16:51
Mister_Magisterhence camera2 api16:51
T42<b100dian> So, I am using a mix of mal's camera2 branch + my prs 111, 122 and 121 in https://github.com/sailfishos-on-sake/droidmedia/tree/master - That is for droidmedia, and I just updated it yesterday because I tested another quirk17:00
Mister_Magisterso all I need is just different droidmedia?17:00
T42<b100dian> For gst-droid you need this PR https://github.com/sailfishos/gst-droid/pull/7917:01
T42<b100dian> I am again using some combo here https://github.com/b100dian/gst-droid/tree/newquirks-zoom-mediabuffers with another PR17:02
T42<b100dian> So, if you use the pair of droidmeda / gst-droid then you should be able to add `on=off` here https://github.com/sailfishos-on-sake/droid-config-sake/blob/master/sparse/etc/gst-droid/gstdroidcamsrcquirks.conf#L417:03
T42<b100dian> I never got around to improving that config, "[edge-mode]on=off" sounds weird I know. You can off the noise reduction too17:04
Mister_Magisterthank you kindly i'll get to reading that soon17:05
T42<b100dian> fingerscrossed it works on your device too. And maybe you don't lose video recording, who knows17:07
T42<Mister_Magister> maybe I gain one more camera :P17:10
T42<Mister_Magister> i would hate to miss out on wide angle17:11
mal@b100dian did you push to wrong branch, ref https://github.com/sailfishos/droidmedia/pull/11117:37
T42<b100dian> mal: Yes :) I forgot that that PR was created from "master" branch. Fixing17:39
Mister_Magisteraww man encryption doesn't work :( oh well17:39
mal@b100dian as for camera2 maybe try this https://github.com/n2klb/droidmedia/commits/camera2-capture17:39
rinigusb100dian: manifest seem to help in terms of starting services in LOS (lshal). can't see anything in SFOS - or just forgoy where to look17:48
rinigussaw your PR for fake-qcrilmsgtunnel17:48
T42<b100dian> Oh wow. 2weeks ago. So this basically replaces your last year's branches?17:49
malyeah, my branch is pretty much obsolete now17:50
T42<b100dian> mal I've restored PR11117:50
mal@b100dian good reminder not to do PRs from master branch17:50
T42<b100dian> Yup, I'll just do this quick change, open a PR and here we are 2-3 years later17:51
Mister_Magistereugh i lost 120Hz but dtsi did not change so like why17:52
Mister_Magistermagically it's 120Hz now17:53
Mister_Magisterit fixed itself once i complained17:54
T42<b100dian> rinigus: sorry I missed your lines. I think this commit explains it https://github.com/sailfishos-sony-nagara/droid-config-sony-nagara/commit/baca0e26c38b8af10358e89e6c54b370fc84cbdd17:57
T42<b100dian> I have if'd out the 1 IV so people would not get updates with non-working multisim17:57
rinigusgreat - then I just have to adjust that - thanks!17:58
rinigusI bumped 1iv kernel on testing now as well17:58
T42<roundedrectangle> When trying to build the HAL package, I get an issue saying that CONFIG_NETFILTER_XT_MATCH_QTAGUID should be enabled in kernel defconfig. It seems like my kernel (3.10) has some features backported from newer ones, and after setting that flag it doesn't even appear in the final `out/target/product/$DEVICE/obj/KERNEL_OBJ/.config` file. How can I skip that check?17:58
T42<roundedrectangle> I use lineage 18.118:01
malcan be ignored18:02
T42<roundedrectangle> mal, it won't let me build the hal package18:02
malcomment it out from hybris/mer-kernel-check/mer_verify_kernel_config18:03
T42<roundedrectangle> thanks18:03
Mister_Magistermal: either I lost something on the way or… anyway youtube videos stop after a split second :/18:14
Mister_Magisterbut you mentioned they don't work on fp5 either18:15
Mister_Magisterso i will attribute that to f google18:15
malhave you tried GECKO_CAMERA_DROID_FORCE_MEDIA_BUFFER or GECKO_CAMERA_DROID_NO_MEDIA_BUFFER18:18
maldo you have latest droidmedia?18:18
Mister_MagisterI have not18:18
malactually only GECKO_CAMERA_DROID_FORCE_MEDIA_BUFFER makes sense on qcom18:19
Mister_Magisteri'm on this commit 4792c8c25e711e06c8b466ec17e5db60196764d118:20
Mister_Magisterwhere do I set the GECKO_CAMERA_DROID_FORCE_MEDIA_BUFFER18:20
malnemo env18:21
malhttps://github.com/sailfishos-sony-nagara/droid-config-sony-nagara/blob/main/sparse/var/lib/environment/nemo/90-nagara-browser-media.conf18:21
Mister_Magisterthat just crashes the browser18:23
malI should rebase my a15 branch18:24
Mister_Magister:)18:24
Mister_Magistermaybe if you rebase second back camera will pop up?18:26
Mister_Magisteri think i bugged the browser beyond comprehension18:27
Mister_Magisternow it doesn't crash18:27
Mister_Magisternow it crashes without that file18:31
Mister_Magisterso it crashes most of the time and the time it doesn't the decoding is messed up18:33
Mister_Magisterif i add video/avc = dont-use-droid-convert;use-codec-supplied-height;use-codec-supplied-width it crashes always18:35
malgst-droid config is for gallery old18:36
mal*only18:36
Mister_Magisterbut it affects browser somehow lol18:36
malMister_Magister: try latest android15 of droidmedia18:36
malit does not18:36
Mister_Magistermaybe coincidence then18:36
Mister_Magistermaking droidmedia18:37
Mister_Magistermal: it does exactly same thing, either crash or messed up decoding18:49
malso GECKO_CAMERA_DROID_FORCE_MEDIA_BUFFER does nothing?18:50
maldoes gallery app work without issues?18:50
Mister_Magisternot specifically no18:50
Mister_Magisteryes18:51
Mister_Magistertho that could be diff codec18:51
Mister_Magistermal: lol it's just one specific video that's broken18:57
maloh19:03
malwhat video?19:03
T42<Mister_Magister> https://www.youtube.com/watch?v=qVeq3QVi3aU19:03
Mister_Magisterit has like one static frame and is not really a video19:03
Mister_Magistereven yt-dlp complained19:03
malah19:03
nightishamanHi, I'm trying to build hybris-hal but for some reason the build script passes no kernel to mkbootimg19:10
nightishaman[ 92% 36726/39604] Making hybris-boot.img in out/target/product/panther/obj/ROOT/hybris-boot_intermediates/ using  true,,out/target/product/panther/obj/ROOT/hybris-boot_intermediates/boot-initramfs.gz)19:10
nightishamanFAILED: out/target/product/panther/obj/ROOT/hybris-boot_intermediates/hybris-boot.img19:10
nightishamanusage: mkbootimg [-h] [--kernel KERNEL] [--ramdisk RAMDISK] [--second SECOND]19:10
nightishaman                 [--dtb DTB]19:10
nightishaman                 [--recovery_dtbo RECOVERY_DTBO | --recovery_acpio RECOVERY_ACPIO]19:10
nightishaman                 [--cmdline CMDLINE] [--vendor_cmdline VENDOR_CMDLINE]19:10
nightishaman                 [--base BASE] [--kernel_offset KERNEL_OFFSET]19:10
nightishaman                 [--ramdisk_offset RAMDISK_OFFSET]19:10
nightishaman                 [--second_offset SECOND_OFFSET] [--dtb_offset DTB_OFFSET]19:10
nightishaman                 [--os_version OS_VERSION] [--os_patch_level OS_PATCH_LEVEL]19:10
nightishaman                 [--tags_offset TAGS_OFFSET] [--board BOARD]19:10
nightishaman                 [--pagesize {2048,4096,8192,16384}] [--id]19:10
nightishaman                 [--header_version HEADER_VERSION] [--dt DT] [-o OUTPUT]19:10
nightishaman                 [--vendor_boot VENDOR_BOOT] [--vendor_ramdisk VENDOR_RAMDISK]19:10
nightishaman                 [--vendor_bootconfig VENDOR_BOOTCONFIG]19:10
nightishaman                 [--gki_signing_algorithm GKI_SIGNING_ALGORITHM]19:10
nightishaman                 [--gki_signing_key GKI_SIGNING_KEY]19:10
nightishaman                 [--gki_signing_signature_args GKI_SIGNING_SIGNATURE_ARGS]19:10
nightishaman                 [--gki_signing_avbtool_path GKI_SIGNING_AVBTOOL_PATH]19:10
nightishamanmkbootimg: error: argument --kernel: expected one argument19:10
nightishaman[ 92% 36728/39604] Making hybris-recovery.img in out/target/product/panther/obj/ROOT/hybris-recovery_intermediates/ using  out/target/product/panther/obj/ROOT/hybris-recovery_intermediates/recovery-initramfs.gz19:10
nightishamanFAILED: out/target/product/panther/obj/ROOT/hybris-recovery_intermediates/hybris-recovery.img19:10
nightishamanusage: mkbootimg [-h] [--kernel KERNEL] [--ramdisk RAMDISK] [--second SECOND]19:10
nightishaman                 [--dtb DTB]19:10
nightishaman                 [--recovery_dtbo RECOVERY_DTBO | --recovery_acpio RECOVERY_ACPIO]19:10
Mister_Magisternightishaman: use paste service stop spamming19:10
nightishaman                 [--cmdline CMDLINE] [--vendor_cmdline VENDOR_CMDLINE]19:10
nightishaman                 [--base BASE] [--kernel_offset KERNEL_OFFSET]19:10
nightishaman                 [--ramdisk_offset RAMDISK_OFFSET]19:10
nightishaman                 [--second_offset SECOND_OFFSET] [--dtb_offset DTB_OFFSET]19:11
nightishaman                 [--os_version OS_VERSION] [--os_patch_level OS_PATCH_LEVEL]19:11
nightishaman                 [--tags_offset TAGS_OFFSET] [--board BOARD]19:11
nightishaman                 [--pagesize {2048,4096,8192,16384}] [--id]19:11
nightishaman                 [--header_version HEADER_VERSION] [--dt DT] [-o OUTPUT]19:11
nightishaman                 [--vendor_boot VENDOR_BOOT] [--vendor_ramdisk VENDOR_RAMDISK]19:11
nightishaman                 [--vendor_bootconfig VENDOR_BOOTCONFIG]19:11
nightishaman                 [--gki_signing_algorithm GKI_SIGNING_ALGORITHM]19:11
nightishaman                 [--gki_signing_key GKI_SIGNING_KEY]19:11
nightishaman                 [--gki_signing_signature_args GKI_SIGNING_SIGNATURE_ARGS]19:11
nightishaman                 [--gki_signing_avbtool_path GKI_SIGNING_AVBTOOL_PATH]19:11
nightishamanmkbootimg: error: argument --kernel: expected one argument19:11
nightishaman18:48:16 ninja failed with: exit status 119:11
malwhich android base?19:12
nightishamansorry, its my first time using irc, I thought it would be one message19:12
nightishamanhybris-22.219:13
malcheck that you have a16 branch of hybris-boot in hybris/hybris-boot19:14
nightishamanit is a16, according to the manifest, it is no branch currently since I modified fixup-mountpoints19:15
nightishamangit status reports no branch, due to the changes19:16
malok19:23
Mister_Magistermal: smallest of nitpicks, when phone is connected to charging, the screen doesn't wake up19:24
Mister_Magisterwhether it be wireless or usb19:24
Mister_Magistermal: i'll be releasing the port now and restoring backup on it to use it as daily device, as always, massive thanks to you for all your help, stupid old me couldn't have done it without you <319:27
Mister_Magisterkisses and love <319:27
nightishamanmal I'm having the feeling that the kernel is at the wrong location in the manifest I used. Do the kernels have to be static at kernel/VENDOR/DEVICENAME?19:32
malnightishaman: where id your kernel?19:32
malcheck device repo, it should mention the path there19:32
malnightishaman: that error seems to suggest your device for some reason has TARGET_NO_KERNEL defined or something else happens19:33
nightishamanmal at the default location for the manifest that I borrowed from lineageos19:33
nightishamanso it is aosp/19:33
malhmm?19:33
malwhich device?19:33
nightishamanpixel 719:34
malcan you show your local_manifest19:35
malit seems I probably found the issue19:37
nightishamanhttps://pastebin.com/72KWQ12D I just modified it to kernel/google/panther19:37
nightishamanand did repo resync19:37
malwhich one did you modify?19:38
nightishaman<project path="kernel/google/panther" name="kernel/common" remote="aosp-lineageos" revision="refs/tags/android14-6.1-2025-08_r11">19:39
nightishamanit was previously project path="aosp"19:39
malI wonder where you got that manifest19:40
nightishamanhttps://github.com/LineageOS/android_kernel_google_gs-6.1_manifest19:42
nightishamanit was the link attached on the lineageos website for kernel source19:42
malI don't see the device repos in the manifest19:45
Mister_Magisterwait19:47
Mister_MagisterWAIT19:47
Mister_Magistermal: what if the "connect usb once to fix suspend" issue is because ramdisk writes peripheral manually, so then it's stuck in peripheral and not none until you connect and disconnect usb?19:47
nightishamanmal https://github.com/LineageOS/android_device_google_pantah here19:48
malnightishaman: https://github.com/LineageOS/android_device_google_gs201/blob/lineage-22.2/BoardConfig-common.mk#L5919:48
Mister_Magistermy pipa (xiaomi pad 6) is currently in peripheral19:48
Mister_Magisterand it's not suspending19:48
maldoes it have telnet enabled?19:49
Mister_Magisterwhen i wrote none it suspended next second19:49
Mister_Magisterwithout even telnet enabled ramdisk sets up usb19:49
Mister_Magisterit only disables it after ramdisk19:49
malit should not19:49
Mister_Magisterit should19:49
Mister_Magisteri always get the "in real rootfs" device19:49
Mister_Magisterhttps://github.com/mer-hybris/hybris-boot/blob/master/init-script#L28819:50
Mister_Magisterit executes run_debug_session whether you like it or not19:51
malhmm19:52
Mister_Magisterthen i can just use my little daemon and it will fix suspend on pipa too19:53
Mister_Magisterit wasn't suspending for days now that i wrote none it went to sleep instantly19:54

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