thevancedgamer | mal: did you get to test it? | 06:54 |
---|---|---|
btchdRPR | hi 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 feasible | 09:40 |
Mister_Magister | btchdRPR: iirc you can run sfos on GSI | 11:25 |
btchdRPR | Mister_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_Magister | check logs | 11: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_Magister | well the paste doesn't want to load for me | 11:36 |
T42 | <edp_17> Just clicked on the link. it works. | 11:37 |
Mister_Magister | it took a minute to load | 11:38 |
Mister_Magister | it 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_Magister | thats what paste says | 11:39 |
T42 | <edp_17> It seems hanging in build.sh in build() in for SPEC in "$@" ; do | 11:39 |
Mister_Magister | ye so it builds rpm which in turns produces the log you pasted which says it hangs at verifying kernel config | 11:40 |
T42 | <edp_17> Okay, but if I manually run the "hybris/mer-kernel-check/mer_verify_kernel_config" command, it works. | 11:40 |
mal | thevancedgamer: fp4 with only wifi lost 11% in 19 hours, fp5 with wifi and sim lost 34% in 16.5 hours, so fp5 is not good | 11:41 |
Mister_Magister | did you give it the kernel config path as a parameter? | 11:41 |
Mister_Magister | ahh | 11:41 |
T42 | <edp_17> Yes. Like this: hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.confi | 11:41 |
Mister_Magister | it hangs without argument | 11:42 |
Mister_Magister | and in the log there's no argument | 11:42 |
Mister_Magister | here's your issue | 11:42 |
Mister_Magister | i think it doesn't find the kernel config path | 11:42 |
T42 | <edp_17> I haven't changed that script. | 11:42 |
Mister_Magister | I didn't say you did | 11:42 |
Mister_Magister | but you gotta figure out why it fails to get the path | 11:43 |
T42 | <edp_17> I meant, somehow it is broken if it works for everybody else. | 11:43 |
Mister_Magister | yeah happens | 11:43 |
Mister_Magister | just gotta figure out why it fails | 11:43 |
Mister_Magister | you can check the steps before this command is ran and try it yourself and see where it fails to get the path | 11: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_Magister | grep is your friend :) | 11:44 |
T42 | <edp_17> I've tried to run the lines one by one from build_packages.sh and build.sh | 11:45 |
Mister_Magister | it's in rpm/dhd/droid-hal-device.inc | 11:45 |
Mister_Magister | maybe check if there are some dhd submodule udpates | 11:45 |
T42 | <TheVancedGamer> mal: yeah, for some reason modem drains way more on FP5 | 11:46 |
T42 | <TheVancedGamer> maybe we need some more optimization | 11:46 |
T42 | <edp_17> @Mister_Magister : Thanks. | 11:49 |
Mister_Magister | did 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_Magister | that's quite exactly the ruining part :D | 11:50 |
T42 | <edp_17> Yeah. :D | 11:50 |
Mister_Magister | yeah 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 .inc | 11:50 |
Mister_Magister | also @edp_17 you cannot place comments like that cause \ includes next line and next line is comment so it includes nothing | 11:51 |
Mister_Magister | thats why it failed | 11:51 |
T42 | <edp_17> It worked for building 4.6. | 11:52 |
Mister_Magister | well 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 argument | 11:53 |
Mister_Magister | anyway, fixed now | 11:53 |
Mister_Magister | i'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_Magister | no worries | 11:54 |
T42 | <edp_17> New error, looks like python is missing: https://paste.ubuntu.com/p/kpBjYdCyTp/ | 12:00 |
Mister_Magister | it sure does look like it | 12:01 |
Mister_Magister | are you in mersdk… erm… sfossdk? | 12:01 |
T42 | <edp_17> yep, in sfossdk | 12:01 |
Mister_Magister | python does not exist here too | 12:02 |
Mister_Magister | so something ought to be outdated | 12:02 |
Mister_Magister | maybe confirm if you have up-to-date dhd submodule | 12:03 |
mal | @TheVancedGamer I'll do some checking of debug logs from ofono this weekend maybe | 12:05 |
T42 | <TheVancedGamer> mal: try suspend with just wlan on FP5 too | 12:06 |
Mister_Magister | mal: 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 wasted | 12:07 |
Mister_Magister | could you ask some people about it pretty please | 12:07 |
Mister_Magister | nobody 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 |
Keto | Mister_Magister: I guess there shouldn't be any reason not to update it, but I'll ask if someone has some opinions on that | 12:11 |
Mister_Magister | Keto: thanks! | 12:12 |
Mister_Magister | i assume mal has been very busy recently cause he doesn't talk much lately (nothing wrong with that) | 12:12 |
Keto | yeah, everyone is quite busy | 12:14 |
Mister_Magister | thanks, now i know :) | 12:15 |
mal | @TheVancedGamer yes, I plan to, charging the phone now for easier calculation of battery charge changes | 12:17 |
mal | Mister_Magister: considering pcre is EOL and pcre2 replaces it I see no reason to not update to pcre2 | 12:18 |
Mister_Magister | okidoki thanks | 12:18 |
Mister_Magister | i just wanted to make sure | 12:18 |
Keto | Mister_Magister: Thanks to your pestering, other unnecessary dependencies to pcre1 are getting fixed too https://github.com/sailfishos/libselinux/pull/3 :) | 13:13 |
Mister_Magister | hell ye | 13:14 |
Mister_Magister | for the glory of sailfish | 13:14 |
btchdRPR | upd 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 |
btchdRPR | time to build Sailfish. | 15:08 |
Mister_Magister | good luck | 15:08 |
Mister_Magister | its quite… unusual way to port so you'll probably encounter some issues | 15:08 |
btchdRPR | unusual but useful :) a lot of modern devices simply don't have aosp device trees ready | 15:08 |
Mister_Magister | I ported xiaomi pad 6 which had android 14 and lineage and it's quite a lot newer :) | 15:10 |
Mister_Magister | so it purely depends on device | 15:10 |
btchdRPR | 100%, i want to try to port a redmi k70 pro later which has 0 lineage support, official or not | 15:10 |
btchdRPR | this is just a warmup :) | 15:10 |
Mister_Magister | i had great experience with pad 6 | 15:11 |
Mister_Magister | except bootloader unlocking | 15:11 |
btchdRPR | i'm already past that on the k70P, with money lol | 15:11 |
btchdRPR | only way to do it on this device, sad | 15:11 |
Mister_Magister | yeah so i won't recommend xiaomeme or buy any xiaomeme device | 15:12 |
btchdRPR | in these days samsung is the mod-friendly vendor. crazy | 15:12 |
Mister_Magister | i wouldn't go as far | 15:13 |
Mister_Magister | these days there's no good vendor | 15:13 |
Mister_Magister | you can only find least evil | 15:13 |
btchdRPR | hmm... you may be right about that | 15:13 |
T42 | <morciatka> I feel like Samsung used to be much better than it is right now | 15:14 |
Mister_Magister | thats thanks to their weirdass cpu | 15:14 |
btchdRPR | okay let's not disrespect exynos, i love them | 15:14 |
Mister_Magister | you won't love porting them thats for sure | 15:14 |
btchdRPR | mainlining them is fun | 15:14 |
btchdRPR | this s20u is an exynos model | 15: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_Magister | you could try to install python | 15:29 |
Mister_Magister | but that could be masking the issue | 15:29 |
Mister_Magister | like sudo zypper in python | 15:29 |
Mister_Magister | in sfossdk | 15:29 |
T42 | <edp_17> I've installed python and still getting the same error message. I guess that is something else. | 15:40 |
mal | did you install python to target? | 15:43 |
rinigus | I 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 |
rinigus | that's on LOS21/sony nagara | 15:43 |
mal | hmm | 15:43 |
Mister_Magister | right its not in the sfossdk | 15:43 |
Mister_Magister | its in the target | 15:44 |
Mister_Magister | dummy me | 15:44 |
rinigus | will try to grep LOS sources and find it. but if its known issue, please share | 15:44 |
mal | rinigus: 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 python | 15:45 |
rinigus | mal: just a sec | 15:45 |
mal | Mister_Magister: or adding build requires to droid-hal spec | 15:46 |
Mister_Magister | oh… ye | 15:46 |
mal | easier that way :) | 15:46 |
Mister_Magister | surue :P | 15:46 |
rinigus | mal: 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_Magister | you mean droid-hal-init? | 15:48 |
Mister_Magister | wait rinigus i had that | 15:48 |
Mister_Magister | ISensorManager | 15:48 |
rinigus | yes, droid-hal-init. and ISensorManager :) | 15:48 |
Mister_Magister | I had that | 15:49 |
Mister_Magister | but i don't remember how i fixed it | 15:49 |
Mister_Magister | worth grepping logs | 15:49 |
rinigus | from our irc chat history and its grep, all I can find is "logcat message disappeared after disabling andoid's own sensor service". | 15:49 |
rinigus | which one is that? | 15:50 |
mal | rinigus: grep .rc files for sensor stuff and see if it gives any hints? | 15:50 |
Mister_Magister | I don't actually have it disabled | 15:51 |
Mister_Magister | so maybe something fixed it | 15:51 |
rinigus | mal: will do. on LOS, logcat "SystemServerTimingAsync: InitThreadPoolExec:StartISensorManagerService". with nativeloader included, if I understood correctly. will grep .rc's | 15:52 |
mal | that reminds me, I should try to finish aidl support in sensorfw | 15:53 |
Mister_Magister | ISensorManager was provided by the droidmedia iirc | 15:53 |
mal | rinigus: which los21 version, I mean rXX | 15:54 |
Mister_Magister | rinigus: i think it was not mounted paritions | 15:55 |
Mister_Magister | in my case i think odm | 15:55 |
rinigus | mal: I think I synced it in april. its unreleased LOS port based on sony stock | 15:55 |
mal | wouldn't be surprised if android again changed something in release and not wait for new major release | 15:55 |
rinigus | so, no idea about rXX | 15:56 |
mal | manifest should tell it probably | 15:56 |
Mister_Magister | Funny because grepping the logs i see myself having that issue on 3 different devices | 15:56 |
Mister_Magister | and i have no clue how i fixed it on either of them xd | 15:56 |
mal | rinigus: do you have mini* services running? | 15:57 |
mal | from droidmedia | 15:57 |
rinigus | mal: 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 it | 15:59 |
Mister_Magister | huh piggz'sg rep doesn't show my messages from pipa time | 15:59 |
Mister_Magister | i thought i had schizophreina | 15:59 |
rinigus | mal: 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_Magister | ahhh rinigus here the ISensorManager was requested by xiaomi-keyboard service, ISensorManager was in hwbinder not in binder and xiaomi-keyboard was in binder | 16:00 |
Mister_Magister | does it say in logs "'android.frameworks.sensorservice.ISensorManager/default' could not be found" | 16:01 |
rinigus | Mister_Magister: and ... how did you find it out? | 16:01 |
Mister_Magister | uhh logs | 16:01 |
rinigus | re keyboard | 16:01 |
Mister_Magister | it was saying ISensorManager/default' could not be found (requested by debug pid 3263) | 16:01 |
Mister_Magister | and the pid was xiaomi-keyboard | 16:01 |
Mister_Magister | and i yeeted that service cause it wouldn't work either way | 16:01 |
Mister_Magister | as a solution we spoofed it | 16:02 |
rinigus | OK, 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_Magister | nah thats different messsage | 16:02 |
rinigus | so, probably some vintf has it defined. will try to see if its in my port sources | 16:03 |
Mister_Magister | causei also had "ISensorManager/default' for ctl.interface_start from pid: 2159 (/system/bin/servicemanager" | 16:03 |
Mister_Magister | but thats different | 16:03 |
Mister_Magister | maybe try grepping for "requested by" | 16:03 |
Mister_Magister | basically any service that requires service_manager is not gonna work anyway cause its dummy one | 16:04 |
Mister_Magister | rinigus: can i have your device repo | 16:04 |
Mister_Magister | the android_device | 16:04 |
* Mister_Magister (damn i'm useful today) | 16:05 | |
mal | droidmedia only runs hidl sensormanager afaik | 16:06 |
rinigus | hmm, 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#L18 | 16:06 |
Mister_Magister | you got it | 16:06 |
Mister_Magister | thats your source of troubles | 16:06 |
Mister_Magister | thats why i asked for it | 16:06 |
rinigus | LOS device repos: https://github.com/sony-nagara | 16:06 |
Mister_Magister | xd | 16:06 |
mal | you only need vibra service if you have some terrible vibra kernel driver | 16:06 |
mal | like fp5 does | 16:07 |
Mister_Magister | rinigus: nah you found what i wanted to find xd | 16:07 |
mal | which reminds me that I should make a PR for binder vibra in sfos | 16:07 |
mal | I have it in use in fp5 but never made PR | 16:07 |
Mister_Magister | https://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 mistaken | 16:07 |
rinigus | mal: vibra doesn't work either. will have to look into it too | 16:07 |
Mister_Magister | and there's program that can help you find which binder has ISensorManager | 16:07 |
Mister_Magister | in my case it was hwbinder | 16:08 |
Mister_Magister | maybe point it to hwbinder xd | 16:08 |
Mister_Magister | thats 0iq move | 16:08 |
mal | but adding aidl sensor manager to droidmedia might be needed at some point | 16:08 |
Mister_Magister | its already there | 16:09 |
Mister_Magister | just dummy | 16:09 |
T42 | <TheVancedGamer> mal: seems like you've already suffered with the aidl vibrator on FP5 xD | 16:09 |
Mister_Magister | and i bet its registered in hwbinder | 16:09 |
Mister_Magister | mal: you remember that command to list the services in *binder | 16:10 |
mal | binder-list -d /dev/binder ? | 16:11 |
mal | from binder-tools package | 16:12 |
Mister_Magister | yeee | 16:12 |
Mister_Magister | rinigus: you can use that to see ISensorManager is in fact in hwbinder | 16:13 |
Mister_Magister | but it seems your vibraotr service asks it in vndbinder if i'm not mistaken | 16:13 |
* Mister_Magister i'm basically talking out of my ass | 16:13 | |
Mister_Magister | but thats my thinking | 16:13 |
rinigus | so, android.frameworks.sensorservice@1.0::ISensorManager/default is on hwbinder; android.hardware.vibrator.IVibrator/default on binder | 16:14 |
Mister_Magister | ye | 16:15 |
Mister_Magister | i had same thing | 16:15 |
rinigus | so, that's a mixup, if I follow Mister_Magister correctly | 16:15 |
Mister_Magister | i think so | 16:15 |
Mister_Magister | although i can't find your vibra service actually requesting ISensorManager | 16:16 |
Mister_Magister | https://github.com/VerdandiTeam/android_device_xiaomi_pipa/blob/lineage-22/peripheralmanager/xiaomi-keyboard.cpp#L84 like here | 16:16 |
rinigus | let's try to kill vibrator service and check out if it helps | 16:16 |
Mister_Magister | ez fix 100% | 16:16 |
Mister_Magister | having the "requested by debug pid" would be useful | 16:17 |
mal | wondering why fp5 didn't have that issue, need to check | 16:17 |
Mister_Magister | just sharing what i know that might be helpful | 16:18 |
Mister_Magister | rinigus: could you paste more of the logcat? i assume something is bootlooping that sends that message? | 16:19 |
rinigus | Mister_Magister: here you are: https://paste.opensuse.org/pastes/25b67926c602 | 16:23 |
rinigus | killing vibrator wasn't sufficient :( | 16:24 |
btchdRPR | gsi-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_Magister | rinigus: you absolutely have that message dummy | 16:25 |
Mister_Magister | could not be found (requested by debug pid 6628), | 16:25 |
Mister_Magister | what is pid 6628 | 16:25 |
rinigus | :) | 16:27 |
Mister_Magister | what is it | 16:27 |
rinigus | its slim_daemon | 16:28 |
Mister_Magister | here you go | 16:28 |
Mister_Magister | is that in vendor? | 16:28 |
Mister_Magister | disable that service (if its not needed) and voila | 16:29 |
rinigus | its pulled directly from stock proprietary files. :( . will have to check what is it | 16:29 |
Mister_Magister | its not gonna get useful data from dummy sensormanager anyway so its gonna be broken | 16:29 |
Mister_Magister | so for now you can disable it cause either way its "disabled" | 16:29 |
rinigus | will see. could be related to gps as well - that one works | 16:30 |
rinigus | thanks! | 16:30 |
Mister_Magister | in 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_Magister | no worries i gotta disappear now | 16:31 |
btchdRPR | gsi-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 |
btchdRPR | gsi-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 hahaha | 16:56 |
Mister_Magister | btchdRPR: 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 talking | 17:38 |
Mister_Magister | honestly everyone hates how i document everything i do because i got the habit here xd | 17:39 |
btchdRPR | Mister_Magister: true, but I plan to PR these changes anyway later on :) maybe when it boots and gets less hacky | 17:39 |
Mister_Magister | btchdRPR: but hit by bus scenario | 17:49 |
T42 | <morciatka> how can a developer get hit by a bus, developers never leave their caves :)) | 18:19 |
Mister_Magister | my lifestyle should not be reproduced at any cost | 18:23 |
btchdRPR | alright 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 |
btchdRPR | generating 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 |
btchdRPR | morciatka: don't be stupid, you have a port that i daily drive and i have some bad infra setup xDD | 18:32 |
T42 | <morciatka> tbh, I'm still surprised that you took the port and started using it | 18:32 |
T42 | <morciatka> since I originally intended the 7TP port just for me haha | 18:32 |
btchdRPR | hey, 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 5 | 18:34 |
Mister_Magister | btchdRPR: sfos is definition of non-generic | 18:58 |
Mister_Magister | @morciatka you should intend everything you do that way | 18:59 |
Mister_Magister | its very healthy | 18:59 |
btchdRPR | gsi-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 targets | 19:04 |
Mister_Magister | btchdRPR: 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 |
btchdRPR | some 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_Magister | while packages will have your desired name | 19:06 |
btchdRPR | Mister_Magister: thanks, will use that instead of symlinking | 19:07 |
Mister_Magister | https://github.com/VerdandiTeam/droid-hal-5z/blob/master/droid-hal-5z.spec#L4 also this | 19:07 |
Mister_Magister | ye HABUILD_DEVICE | 19:07 |
Mister_Magister | and change device in droid-hal .spec and set your desired rpm_device | 19:07 |
Mister_Magister | 5z ran like that (Z01R habuild, 5z rpm one) so feel free to look into repos for reference | 19:08 |
Mister_Magister | also 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.spec | 19:08 |
btchdRPR | aaand with a bit of fiddling around (which i need to add to hybris-gsi gsi.mk) -> droid-hal-z3s succesfully built :DDD | 19:13 |
T42 | <elros34> btchdRPR I am not sure by maybe halium based sfos would be more suitable for you? | 19:23 |
btchdRPR | elros34: Was not aware that existed | 19:24 |
T42 | <elros34> there are few ports, especially piggz one | 19:26 |
btchdRPR | thanks 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 go | 19:28 |
btchdRPR | this -> whatever i'm doing now LMAO | 19:28 |
Mister_Magister | i say press on and see where it takes you | 19:29 |
T42 | <elros34> search for 'halium' here: https://build.sailfishos.org/project | 19:29 |
btchdRPR | well, i have my first build done for this pseudoGSI, let's see how bad it'll burn on device | 19:35 |
btchdRPR | well, it's getting *somewhere* I guess. droid-hal-init runs, servicemanager works, but out of all the services logd crashes lol | 20:26 |
btchdRPR | https://katb.in/yecufebaner | 20:26 |
Mister_Magister | btchdRPR: some missing kernel config? | 20:28 |
btchdRPR | don't think so, check-config was happy | 20:28 |
Mister_Magister | btchdRPR: it might be missing stuff | 20:28 |
Mister_Magister | >SCHED_SP_BACKGROUND | 20:29 |
Mister_Magister | check config if its anywhere | 20:29 |
Mister_Magister | maybe it needs to be disabled | 20:29 |
btchdRPR | Mister_Magister: nope, not there | 20:29 |
btchdRPR | this is 4.19 btw | 20:29 |
Mister_Magister | i would grep kernel for it | 20:29 |
btchdRPR | nothing at all | 20:30 |
btchdRPR | i mean, android booted lol | 20:30 |
Mister_Magister | also check if every cgroup is enabled | 20:30 |
Mister_Magister | sure but you modified kernel no? | 20:31 |
Mister_Magister | but maybe i'm barking wrong tree | 20:31 |
Mister_Magister | Failed to read task profiles from /etc/task_profiles.json | 20:34 |
Mister_Magister | i think thats important | 20:34 |
Mister_Magister | as I find the SCHED_SP_BACKGROUND in task_profiles.json | 20:34 |
Mister_Magister | maybe symlink to system/etc? | 20:35 |
btchdRPR | Mister_Magister: i have just added the halium configs, nothing more. kernel's the same | 20:43 |
btchdRPR | Mister_Magister: hmm fails even with symlinks | 20:43 |
Mister_Magister | well have fun | 20:44 |
btchdRPR | grepping irc logs helps always :) | 20:45 |
btchdRPR | fixed it almost, now just have some unknown attributes | 20:45 |
T42 | <morciatka> btchdRPR: it helps... until the moment it didn't | 20:47 |
T42 | <morciatka> but it was fine, I figured stuff out on my own too | 20:47 |
T42 | <morciatka> and most of it was accidental | 20:47 |
T42 | <morciatka> some of it got mentioned here and most of it on my own devlog | 20:48 |
btchdRPR | hahaha it just didn't | 20:52 |
btchdRPR | https://katb.in/ivoheretuka <- new error, /dev/cgroup_info? | 20:52 |
btchdRPR | i don't even have that lol | 20:52 |
btchdRPR | added 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 logs | 20:54 |
Mister_Magister | but does /system/etc/task_profiles.json exist | 20:54 |
T42 | <elros34> task_profiles.json is know issue and its even explained in hadk-hot (reading it really saves time) | 20:55 |
btchdRPR | it does | 20:55 |
btchdRPR | elros34: 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.rc | 20:55 |
Mister_Magister | hadk-hot has still cert issues that are unfixed | 20:55 |
Mister_Magister | so its not like he can just view whats documented | 20:56 |
btchdRPR | Mister_Magister: I am viewing it right now :) | 20:56 |
Mister_Magister | sailfishos.wiki has literally expired cert though | 20:57 |
btchdRPR | yep | 20:57 |
Mister_Magister | firefox says no | 20:57 |
T42 | <morciatka> I can't even open the site anymore | 20:57 |
T42 | <elros34> yeah but nobody updates it, reading should be safe:) | 20:57 |
Mister_Magister | thats what i'm saying | 20:57 |
Mister_Magister | @elros34 but the site can't be opened | 20:58 |
T42 | <elros34> use better browser like sailfish one :) | 20:58 |
btchdRPR | i can open it without problems lol | 20:58 |
Mister_Magister | not on browser that cares about security | 20:58 |
btchdRPR | firefox 128.9.0esr :) | 20:59 |
Mister_Magister | quite outdated i'm on 137 | 20:59 |
btchdRPR | that's the perk of running debian. hadk-hot works | 20:59 |
Mister_Magister | well anyway | 20:59 |
btchdRPR | welp -> will come back to this tomorrow. quite tired for today. peculiar 'failed to set background scheduling policy: Success' lol | 21:00 |
btchdRPR | goodnight all! | 21:00 |
T42 | <morciatka> btchdRPR: have a nice one | 21:00 |
T42 | <elros34> you did apply hybris -patchs right? | 21:00 |
btchdRPR | elros34: yep | 21:00 |
T42 | <elros34> still maybe there is some patche related to that with some explanation | 21:02 |
*** deathmist1 is now known as deathmist | 21:50 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!