Thursday, 2025-05-08

thevancedgamermal: did you get to test it?06:54
btchdRPRhi there, i have a bit of a question - could I in theory compile LineageOS for a generic target with hybris patches, use my device's stock Android11 vendor, and somehow boot Sailfish? afair that's how UT folks do it, and the device i'm trying to bring up has no real working LineageOS ROM. just wondering if that's even feasible09:40
Mister_MagisterbtchdRPR: iirc you can run sfos on GSI11:25
btchdRPRMister_Magister: thanks. i am currently trying to see where i can go with it, device is a Galaxy S20 Ultra, currently trying to get it to boot any GSI lol. will maybe put up a forum thread with my findings.11:27
T42<edp_17> mal: Any idea about why "rpm/dhd/helpers/build_packages.sh -d" hangs?11:34
T42<edp_17> I am trying to build sfos 5. hadk_env is correct, I run command in sdk and it just doesn't end.11:35
Mister_Magistercheck logs11:35
T42<edp_17> There is nothing: https://paste.ubuntu.com/p/PxSyqxJ7GT/11:35
T42<edp_17> It just shows that I interrupted with ctrl+c after a long waiting.11:36
T42<edp_17> I get the "Building rpm/droid-hal-ocean.spec" message and that's it.11:36
Mister_Magisterwell the paste doesn't want to load for me11:36
T42<edp_17> Just clicked on the link. it works.11:37
Mister_Magisterit took a minute to load11:38
Mister_Magisterit hangs at Verifying kernel config?11:38
T42<edp_17> Here is a fresh one: https://paste.ubuntu.com/p/PkzC5fGqW2/11:38
T42<edp_17> No.11:38
Mister_Magisterthats what paste says11:39
T42<edp_17> It seems hanging in build.sh in build() in for SPEC in "$@" ; do11:39
Mister_Magisterye so it builds rpm which in turns produces the log you pasted which says it hangs at verifying kernel config11:40
T42<edp_17> Okay, but if I manually run the "hybris/mer-kernel-check/mer_verify_kernel_config" command, it works.11:40
malthevancedgamer: fp4 with only wifi lost 11% in 19 hours, fp5 with wifi and sim lost 34% in 16.5 hours, so fp5 is not good11:41
Mister_Magisterdid you give it the kernel config path as a parameter?11:41
Mister_Magisterahh11:41
T42<edp_17> Yes. Like this: hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.confi11:41
Mister_Magisterit hangs without argument11:42
Mister_Magisterand in the log there's no argument11:42
Mister_Magisterhere's your issue11:42
Mister_Magisteri think it doesn't find the kernel config path11:42
T42<edp_17> I haven't changed that script.11:42
Mister_MagisterI didn't say you did11:42
Mister_Magisterbut you gotta figure out why it fails to get the path11:43
T42<edp_17> I meant, somehow it is broken if it works for everybody else.11:43
Mister_Magisteryeah happens11:43
Mister_Magisterjust gotta figure out why it fails11:43
Mister_Magisteryou can check the steps before this command is ran and try it yourself and see where it fails to get the path11:44
T42<edp_17> I have no idea where this is verifying the kernel config. I didn't find that in code.11:44
Mister_Magistergrep is your friend :)11:44
T42<edp_17> I've tried to run the lines one by one from build_packages.sh and build.sh11:45
Mister_Magisterit's in rpm/dhd/droid-hal-device.inc11:45
Mister_Magistermaybe check if there are some dhd submodule udpates11:45
T42<TheVancedGamer> mal: yeah, for some reason modem drains way more on FP511:46
T42<TheVancedGamer> maybe we need some more optimization11:46
T42<edp_17> @Mister_Magister : Thanks.11:49
Mister_Magisterdid that help?11:49
T42<edp_17> Not yet, but I've found a change that I did in that file. This: https://paste.ubuntu.com/p/dhCgwCSYNc/11:50
Mister_Magisterthat's quite exactly the ruining part :D11:50
T42<edp_17> Yeah. :D11:50
Mister_Magisteryeah the script just runs command to build the rpm, log is from the actual building and the script to build is in .spec file and in .inc11:50
Mister_Magisteralso @edp_17 you cannot place comments like that cause \ includes next line and next line is comment so it includes nothing11:51
Mister_Magisterthats why it failed11:51
T42<edp_17> It worked for building 4.6.11:52
Mister_Magisterwell i'm sure as hell it won't work on any version of bash so… could be accident that it worked lol or maybe the command didn't hang without argument11:53
Mister_Magisteranyway, fixed now11:53
Mister_Magisteri'm just noting to avoid this in the future :)11:53
T42<edp_17> Yep. It's fixed.  I'll remember this. Thanks.11:54
Mister_Magisterno worries11:54
T42<edp_17> New error, looks like python is missing: https://paste.ubuntu.com/p/kpBjYdCyTp/12:00
Mister_Magisterit sure does look like it12:01
Mister_Magisterare you in mersdk… erm… sfossdk?12:01
T42<edp_17> yep, in sfossdk12:01
Mister_Magisterpython does not exist here too12:02
Mister_Magisterso something ought to be outdated12:02
Mister_Magistermaybe confirm if you have up-to-date dhd submodule12:03
mal@TheVancedGamer I'll do some checking of debug logs from ofono this weekend maybe12:05
T42<TheVancedGamer> mal: try suspend with just wlan on FP5 too12:06
Mister_Magistermal: lemme ask again, if i move timed to pcre2 will jolla accept the pr (assuming it goes through CR)? Or it should strictly not be moved to pcre2 in that case my work would be wasted12:07
Mister_Magistercould you ask some people about it pretty please12:07
Mister_Magisternobody builds pcre1 anymore and sfos has pcre2 so i can't see why not (and i need it updated to run nemo xd)12:08
KetoMister_Magister: I guess there shouldn't be any reason not to update it, but I'll ask if someone has some opinions on that12:11
Mister_MagisterKeto: thanks!12:12
Mister_Magisteri assume mal has been very busy recently cause he doesn't talk much lately (nothing wrong with that)12:12
Ketoyeah, everyone is quite busy12:14
Mister_Magisterthanks, now i know :)12:15
mal@TheVancedGamer yes, I plan to, charging the phone now for easier calculation of battery charge changes12:17
malMister_Magister: considering pcre is EOL and pcre2 replaces it I see no reason to not update to pcre212:18
Mister_Magisterokidoki thanks12:18
Mister_Magisteri just wanted to make sure12:18
KetoMister_Magister: Thanks to your pestering, other unnecessary dependencies to pcre1 are getting fixed too https://github.com/sailfishos/libselinux/pull/3 :)13:13
Mister_Magisterhell ye13:14
Mister_Magisterfor the glory of sailfish13:14
btchdRPRupd on my gsi: got it to boot, stock vendor had some hacks specifically for android13. ok, fine, will use hybris-20. everything (seems) to work, sans fingerprint reader. can live with it.15:07
btchdRPRtime to build Sailfish.15:08
Mister_Magistergood luck15:08
Mister_Magisterits quite… unusual way to port so you'll probably encounter some issues15:08
btchdRPRunusual but useful :) a lot of modern devices simply don't have aosp device trees ready15:08
Mister_MagisterI ported xiaomi pad 6 which had android 14 and lineage and it's quite a lot newer :)15:10
Mister_Magisterso it purely depends on device15:10
btchdRPR100%, i want to try to port a redmi k70 pro later which has 0 lineage support, official or not15:10
btchdRPRthis is just a warmup :)15:10
Mister_Magisteri had great experience with pad 615:11
Mister_Magisterexcept bootloader unlocking15:11
btchdRPRi'm already past that on the k70P, with money lol15:11
btchdRPRonly way to do it on this device, sad15:11
Mister_Magisteryeah so i won't recommend xiaomeme or buy any xiaomeme device15:12
btchdRPRin these days samsung is the mod-friendly vendor. crazy15:12
Mister_Magisteri wouldn't go as far15:13
Mister_Magisterthese days there's no good vendor15:13
Mister_Magisteryou can only find least evil15:13
btchdRPRhmm... you may be right about that15:13
T42<morciatka> I feel like Samsung used to be much better than it is right now15:14
Mister_Magisterthats thanks to their weirdass cpu15:14
btchdRPRokay let's not disrespect exynos, i love them15:14
Mister_Magister you won't love porting them thats for sure15:14
btchdRPRmainlining them is fun15:14
btchdRPRthis s20u is an exynos model15:14
T42<edp_17> @Mister_Magister : I've cloned the latest dhd and still getting the same issue. :(15:27
T42<edp_17> I'll try from scratch again.15:28
Mister_Magisteryou could try to install python15:29
Mister_Magisterbut that could be masking the issue15:29
Mister_Magisterlike sudo zypper in python15:29
Mister_Magisterin sfossdk15:29
T42<edp_17> I've installed python and still getting the same error message. I guess that is something else.15:40
maldid you install python to target?15:43
rinigusI am getting spammed with "Could not find 'aidl/android.frameworks.sensorservice.ISensorManager/default'" in journal & logcat. based on csd, sensors seem to work. how can I disable it?15:43
rinigusthat's on LOS21/sony nagara15:43
malhmm15:43
Mister_Magisterright its not in the sfossdk15:43
Mister_Magisterits in the target15:44
Mister_Magisterdummy me15:44
riniguswill try to grep LOS sources and find it. but if its known issue, please share15:44
malrinigus: which process causes the log entry, it should have pid in logcat?15:45
Mister_Magister@edp_17 you gotta do the sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in python15:45
rinigusmal: just a sec15:45
malMister_Magister: or adding build requires to droid-hal spec15:46
Mister_Magisteroh… ye15:46
maleasier that way :)15:46
Mister_Magistersurue :P15:46
rinigusmal: its droid-init-hal. I'll look up in my LOS logcats which process starts that service. probably its defined in some place and init-hal is trying to get it up...15:47
Mister_Magisteryou mean droid-hal-init?15:48
Mister_Magisterwait rinigus i had that15:48
Mister_MagisterISensorManager15:48
rinigusyes, droid-hal-init. and ISensorManager :)15:48
Mister_MagisterI had that15:49
Mister_Magisterbut i don't remember how i fixed it15:49
Mister_Magisterworth grepping logs15:49
rinigusfrom our irc chat history and its grep, all I can find is "logcat message disappeared after disabling andoid's own sensor service".15:49
riniguswhich one is that?15:50
malrinigus: grep .rc files for sensor stuff and see if it gives any hints?15:50
Mister_MagisterI don't actually have it disabled15:51
Mister_Magisterso maybe something fixed it15:51
rinigusmal: will do. on LOS, logcat "SystemServerTimingAsync: InitThreadPoolExec:StartISensorManagerService". with nativeloader included, if I understood correctly. will grep .rc's15:52
malthat reminds me, I should try to finish aidl support in sensorfw15:53
Mister_MagisterISensorManager was provided by the droidmedia iirc15:53
malrinigus: which los21 version, I mean rXX15:54
Mister_Magisterrinigus: i think it was not mounted paritions15:55
Mister_Magisterin my case i think odm15:55
rinigusmal: I think I synced it in april. its unreleased LOS port based on sony stock15:55
malwouldn't be surprised if android again changed something in release and not wait for new major release15:55
rinigusso, no idea about rXX15:56
malmanifest should tell it probably15:56
Mister_MagisterFunny because grepping the logs i see myself having that issue on 3 different devices15:56
Mister_Magisterand i have no clue how i fixed it on either of them xd15:56
malrinigus: do you have mini* services running?15:57
malfrom droidmedia15:57
rinigusmal: re LOS version. nope, doesn't look like it. its current sync, so rather floating condition. which doesn't help, but kind of needed for it15:59
Mister_Magisterhuh piggz'sg rep doesn't show my messages from pipa time15:59
Mister_Magisteri thought i had schizophreina15:59
rinigusmal: re mini* - yes, they do. media and sf. no audio, but that I will ping about later. will check logcat for something odd with services and rc files.16:00
Mister_Magisterahhh rinigus here the ISensorManager was requested by xiaomi-keyboard service, ISensorManager was in hwbinder not in binder and xiaomi-keyboard was in binder16:00
Mister_Magisterdoes it say in logs "'android.frameworks.sensorservice.ISensorManager/default' could not be found"16:01
rinigusMister_Magister: and ... how did you find it out?16:01
Mister_Magisteruhh logs16:01
rinigusre keyboard16:01
Mister_Magisterit was saying ISensorManager/default' could not be found (requested by debug pid 3263)16:01
Mister_Magisterand the pid was xiaomi-keyboard16:01
Mister_Magisterand i yeeted that service cause it wouldn't work either way16:01
Mister_Magisteras a solution we spoofed it16:02
rinigusOK, in my case full line is: May 08 18:41:04 Xperia1IV droid-hal-init: Control message: Could not find 'aidl/android.frameworks.sensorservice.ISensorManager/default' for ctl.interface_start from pid: 2738 (/system/bin/servicemanager)16:02
Mister_Magisternah thats different messsage16:02
rinigusso, probably some vintf has it defined. will try to see if its in my port sources16:03
Mister_Magistercausei also had "ISensorManager/default' for ctl.interface_start from pid: 2159 (/system/bin/servicemanager"16:03
Mister_Magisterbut thats different16:03
Mister_Magistermaybe try grepping for "requested by"16:03
Mister_Magisterbasically any service that requires service_manager is not gonna work anyway cause its dummy one16:04
Mister_Magisterrinigus: can i have your device repo16:04
Mister_Magisterthe android_device16:04
* Mister_Magister (damn i'm useful today)16:05
maldroidmedia only runs hidl sensormanager afaik16:06
rinigushmm, looks like aidl/vibra service asks for it. assuming that this is used: https://github.com/sony-nagara/android_device_sony_sm8450-common/blob/staging/lineage-21/aidl/vibrator/service.cpp#L1816:06
Mister_Magisteryou got it16:06
Mister_Magisterthats your source of troubles16:06
Mister_Magisterthats why i asked for it16:06
rinigusLOS device repos: https://github.com/sony-nagara16:06
Mister_Magisterxd16:06
malyou only need vibra service if you have some terrible vibra kernel driver16:06
mallike fp5 does16:07
Mister_Magisterrinigus: nah you found what i wanted to find xd16:07
malwhich reminds me that I should make a PR for binder vibra in sfos16:07
malI have it in use in fp5 but never made PR16:07
Mister_Magisterhttps://github.com/sony-nagara/android_device_sony_sm8450-common/blob/staging/lineage-21/aidl/vibrator/service.cpp#L42 it searches in vndbinder if i'm not mistaken16:07
rinigusmal: vibra doesn't work either. will have to look into it too16:07
Mister_Magisterand there's program that can help you find which binder has ISensorManager16:07
Mister_Magisterin my case it was hwbinder16:08
Mister_Magistermaybe point it to hwbinder xd16:08
Mister_Magisterthats 0iq move16:08
malbut adding aidl sensor manager to droidmedia might be needed at some point16:08
Mister_Magisterits already there16:09
Mister_Magisterjust dummy16:09
T42<TheVancedGamer> mal: seems like you've already suffered with the aidl vibrator on FP5 xD16:09
Mister_Magisterand i bet its registered in hwbinder16:09
Mister_Magistermal: you remember that command to list the services in *binder16:10
malbinder-list -d /dev/binder ?16:11
malfrom binder-tools package16:12
Mister_Magisteryeee16:12
Mister_Magisterrinigus: you can use that to see ISensorManager is in fact in hwbinder16:13
Mister_Magisterbut it seems your vibraotr service asks it in vndbinder if i'm not mistaken16:13
* Mister_Magister i'm basically talking out of my ass16:13
Mister_Magisterbut thats my thinking16:13
rinigusso, android.frameworks.sensorservice@1.0::ISensorManager/default is on hwbinder; android.hardware.vibrator.IVibrator/default on binder16:14
Mister_Magisterye16:15
Mister_Magisteri had same thing16:15
rinigusso, that's a mixup, if I follow Mister_Magister correctly16:15
Mister_Magisteri think so16:15
Mister_Magisteralthough i can't find your vibra service actually requesting ISensorManager16:16
Mister_Magisterhttps://github.com/VerdandiTeam/android_device_xiaomi_pipa/blob/lineage-22/peripheralmanager/xiaomi-keyboard.cpp#L84 like here16:16
riniguslet's try to kill vibrator service and check out if it helps16:16
Mister_Magisterez fix 100%16:16
Mister_Magisterhaving the "requested by debug pid" would be useful16:17
malwondering why fp5 didn't have that issue, need to check16:17
Mister_Magisterjust sharing what i know that might be helpful16:18
Mister_Magisterrinigus: could you paste more of the logcat? i assume something is bootlooping that sends that message?16:19
rinigusMister_Magister: here you are: https://paste.opensuse.org/pastes/25b67926c60216:23
riniguskilling vibrator wasn't sufficient :(16:24
btchdRPRgsi-adventures-part-3: first build, first issues -> notably, the device fstab. bad solution, but i pointed the makefile to a hardcoded path, if the build system detects it's building for generic_arm64 target.16:24
Mister_Magisterrinigus: you absolutely have that message dummy16:25
Mister_Magistercould not be found (requested by debug pid 6628),16:25
Mister_Magisterwhat is pid 662816:25
rinigus:)16:27
Mister_Magisterwhat is it16:27
rinigusits slim_daemon16:28
Mister_Magisterhere you go16:28
Mister_Magisteris that in vendor?16:28
Mister_Magisterdisable that service (if its not needed) and voila16:29
rinigusits pulled directly from stock proprietary files. :( . will have to check what is it16:29
Mister_Magisterits not gonna get useful data from dummy sensormanager anyway so its gonna be broken16:29
Mister_Magisterso for now you can disable it cause either way its "disabled"16:29
riniguswill see. could be related to gps as well - that one works16:30
rinigusthanks!16:30
Mister_Magisterin my case it was that xiaomi-keyboard service and it needed it to turn on keyboard based on orientation… it was weird so we replaced it with just executing end result aka always keybaord)16:31
Mister_Magisterno worries i gotta disappear now16:31
btchdRPRgsi-adventures-part-4: same, but with power-profiles. sad hardcode. TODO: maybe think of a better way to get battery capacity somehow?16:35
T42<edp_17> mal, @Mister_Magister : installing python in target has helped. droid-hal has built. Thanks for help.16:39
btchdRPRgsi-adventures-last-post-here-until-i-make-a-forum-thread: compiled! :D a bit more hardcodes than i'd like, but hell yeah i have a hal layer! i'm so scared of booting it hahaha16:56
Mister_MagisterbtchdRPR: spamming here is quite encouraged as long as you provide explanation to how you fixed things and what was the problem, so that it stays in logs and someone grepping the logs might find answer just as I found my own talking17:38
Mister_Magisterhonestly everyone hates how i document everything i do because i got the habit here xd17:39
btchdRPRMister_Magister: true, but I plan to PR these changes anyway later on :) maybe when it boots and gets less hacky17:39
Mister_MagisterbtchdRPR: but hit by bus scenario17:49
T42<morciatka> how can a developer get hit by a bus, developers never leave their caves :))18:19
Mister_Magistermy lifestyle should not be reproduced at any cost18:23
btchdRPRalright then, a small update -> i have just made the most non-generic gsi, added some infra to hybris-boot for generating boot images as well as less-hardcoded fstabs, it's finally cleaner, and i have telnet :)18:30
btchdRPRgenerating boot images -> as in, getting the offsets right, because those are specified in the device tree, which we do not have (duh...)18:30
T42<morciatka> btchdRPR: you already did more work than I ever did for my 7TP port. Keep up the great work.18:31
btchdRPRmorciatka: don't be stupid, you have a port that i daily drive and i have some bad infra setup xDD18:32
T42<morciatka> tbh, I'm still surprised that you took the port and started using it18:32
T42<morciatka> since I originally intended the 7TP port just for me haha18:32
btchdRPRhey, it works great ;)18:32
T42<morciatka> I still have to try to fix a few hurdles and then it's finally high time to get it to SFOS 518:34
Mister_MagisterbtchdRPR: sfos is definition of non-generic18:58
Mister_Magister@morciatka you should intend everything you do that way18:59
Mister_Magisterits very healthy18:59
btchdRPRgsi-adventures: first build failures, had to symlink out/target/product/generic_arm64 to z3s (device codename). fine. then it was missing some init services -> turns out that some dependency matching for hybris kind of breaks when running just hybris-hal droidmedia targets, now building entire systemimage and vendorimage targets19:04
Mister_MagisterbtchdRPR: you can change HABUILD_DEVICE and HABUILD_VENDOR (iirc those were the envs) to have different device name if you need to set it to "generic"19:06
btchdRPRsome initial skeleton for the work that i did can be found here https://github.com/BotchedRPR/hybris-gsi https://github.com/BotchedRPR/hybris-boot/commit/674144fee5b7c6b9fb992f26bde28117b6f094fe but keep in mind that it's extremely dirty and will probably eat your lunch.19:06
Mister_Magisterwhile packages will have your desired name19:06
btchdRPRMister_Magister: thanks, will use that instead of symlinking19:07
Mister_Magisterhttps://github.com/VerdandiTeam/droid-hal-5z/blob/master/droid-hal-5z.spec#L4 also this19:07
Mister_Magisterye HABUILD_DEVICE19:07
Mister_Magisterand change device in droid-hal .spec and set your desired rpm_device19:07
Mister_Magister5z ran like that (Z01R habuild, 5z rpm one) so feel free to look into repos for reference19:08
Mister_Magisteralso need that in droid-configs https://github.com/VerdandiTeam/droid-config-5z/blob/master/rpm/droid-config-5z.spec and hal-version https://github.com/VerdandiTeam/droid-hal-version-5z/blob/master/rpm/droid-hal-version-5z.spec19:08
btchdRPRaaand with a bit of fiddling around (which i need to add to hybris-gsi gsi.mk) -> droid-hal-z3s succesfully built :DDD19:13
T42<elros34> btchdRPR I am not sure by maybe halium based sfos would be more suitable for you?19:23
btchdRPRelros34: Was not aware that existed19:24
T42<elros34> there are few ports, especially piggz one19:26
btchdRPRthanks for bringing it up. well, i'll see where i go from here lol, already started this so what'd hurt in seeing where it'll go19:28
btchdRPRthis -> whatever i'm doing now LMAO19:28
Mister_Magisteri say press on and see where it takes you19:29
T42<elros34> search for 'halium' here: https://build.sailfishos.org/project19:29
btchdRPRwell, i have my first build done for this pseudoGSI, let's see how bad it'll burn on device19:35
btchdRPRwell, it's getting *somewhere* I guess. droid-hal-init runs, servicemanager works, but out of all the services logd crashes lol20:26
btchdRPRhttps://katb.in/yecufebaner20:26
Mister_MagisterbtchdRPR: some missing kernel config?20:28
btchdRPRdon't think so, check-config was happy20:28
Mister_MagisterbtchdRPR: it might be missing stuff20:28
Mister_Magister>SCHED_SP_BACKGROUND20:29
Mister_Magistercheck config if its anywhere20:29
Mister_Magistermaybe it needs to be disabled20:29
btchdRPRMister_Magister: nope, not there20:29
btchdRPRthis is 4.19 btw20:29
Mister_Magisteri would grep kernel for it20:29
btchdRPRnothing at all20:30
btchdRPRi mean, android booted lol20:30
Mister_Magisteralso check if every cgroup is enabled20:30
Mister_Magistersure but you modified kernel no?20:31
Mister_Magisterbut maybe i'm barking wrong tree20:31
Mister_MagisterFailed to read task profiles from /etc/task_profiles.json20:34
Mister_Magisteri think thats important20:34
Mister_Magisteras I find the SCHED_SP_BACKGROUND in task_profiles.json20:34
Mister_Magistermaybe symlink to system/etc?20:35
btchdRPRMister_Magister: i have just added the halium configs, nothing more. kernel's the same20:43
btchdRPRMister_Magister: hmm fails even with symlinks20:43
Mister_Magisterwell have fun20:44
btchdRPRgrepping irc logs helps always :)20:45
btchdRPRfixed it almost, now just have some unknown attributes20:45
T42<morciatka> btchdRPR: it helps... until the moment it didn't20:47
T42<morciatka> but it was fine, I figured stuff out on my own too20:47
T42<morciatka> and most of it was accidental20:47
T42<morciatka> some of it got mentioned here and most of it on my own devlog20:48
btchdRPRhahaha it just didn't20:52
btchdRPRhttps://katb.in/ivoheretuka <- new error, /dev/cgroup_info?20:52
btchdRPRi don't even have that lol20:52
btchdRPRadded in symlinks: /etc/task_profiles -> /system/etc/task_profiles and /etc/task_profiles.json -> /system/etc/task_profiles.json, just like mal suggested in the logs20:54
Mister_Magisterbut does /system/etc/task_profiles.json exist20:54
T42<elros34> task_profiles.json is know issue and its even explained in hadk-hot (reading it really saves time)20:55
btchdRPRit does20:55
btchdRPRelros34: sure, i've added the symlinks in just like in hadk-hot. now i'm getting a new (better?) problem with /dev/cgroup_info/cgroup.rc20:55
Mister_Magisterhadk-hot has still cert issues that are unfixed20:55
Mister_Magisterso its not like he can just view whats documented20:56
btchdRPRMister_Magister: I am viewing it right now :)20:56
Mister_Magistersailfishos.wiki has literally expired cert though20:57
btchdRPRyep20:57
Mister_Magisterfirefox says no20:57
T42<morciatka> I can't even open the site anymore20:57
T42<elros34> yeah but nobody updates it, reading should be safe:)20:57
Mister_Magisterthats what i'm saying20:57
Mister_Magister@elros34 but the site can't be opened20:58
T42<elros34> use better browser like sailfish one :)20:58
btchdRPRi can open it without problems lol20:58
Mister_Magisternot on browser that cares about security20:58
btchdRPRfirefox 128.9.0esr :)20:59
Mister_Magisterquite outdated i'm on 13720:59
btchdRPRthat's the perk of running debian. hadk-hot works20:59
Mister_Magisterwell anyway20:59
btchdRPRwelp -> will come back to this tomorrow. quite tired for today. peculiar 'failed to set background scheduling policy: Success' lol21:00
btchdRPRgoodnight all!21:00
T42<morciatka> btchdRPR: have a nice one21:00
T42<elros34> you did apply hybris -patchs right?21:00
btchdRPRelros34: yep21:00
T42<elros34> still maybe there is some patche related to that with some explanation21:02
*** deathmist1 is now known as deathmist21:50

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