T4 | Felix (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) was added by: Felix (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) | 00:40 |
---|---|---|
*** me is now known as Guest46497 | 00:42 | |
heroic_1 | yamui and initrd-helpers and hw-ramdisk don't seem to be in the repos though | 00:54 |
r0kk3rz | those are in the sailfishos github https://github.com/sailfishos/ | 00:56 |
Mister_Magister | o/ | 10:48 |
Mister_Magister | after updating to 3.0.1 sensorfwd won't start. it throws error: [F] unknown:0 - ASSERT: "socketHandler_->listen(SOCKET_NAME)" in file sensormanager.cpp, line 127 | 10:48 |
r0kk3rz | did you update hybris-sensorfw ? | 11:02 |
Mister_Magister | now yes | 11:04 |
Mister_Magister | its up to date | 11:04 |
Mister_Magister | hybris-libsensorfw-qt5-0.9.6-1.2.1.jolla.armv7hl | 11:04 |
Mister_Magister | fek there is newer one | 11:05 |
Mister_Magister | and i updated devel stupid me | 11:05 |
r0kk3rz | derp | 11:07 |
heroic_1 | mic is failing me: "Error <creator>[02/14 10:55:14] : Unable to find pattern: Jolla Configuration f8331" | 11:10 |
Mister_Magister | heroic_1: hadk | 11:10 |
heroic_1 | what's odd is that my kickstart has 3 lines that look like this: "%packages @Jolla Configuration f8331 %end" | 11:11 |
heroic_1 | isn't "packages" supposed to be non-pretty? i.e. "droid-config-f8331" instead of the full name? | 11:11 |
Mister_Magister | answer is in hadk lel | 11:12 |
Mister_Magister | no it shouldnt | 11:12 |
heroic_1 | "Substitute the line @Jolla Configuration @DEVICE@ with @jolla-hw-adaptation-@DEVICE@ | 11:13 |
heroic_1 | in your .ks" thx :) I | 11:13 |
Mister_Magister | heroic_1: that's not solution | 11:15 |
Mister_Magister | that's only step for debugging | 11:15 |
Mister_Magister | you need to rever it back later | 11:15 |
Mister_Magister | continue on reading | 11:15 |
heroic_1 | well the hadk guide isn't prepare for families yet. on kagura, you have "f8331" mixed with "kagura". the sed line in "8.3 Creating and Configuring the Kickstart File" is uses "$DEVICE"(=kagura) instead of f8331 | 11:17 |
heroic_1 | jeez my grammar is failing me today | 11:17 |
Mister_Magister | could be i never had sony | 11:19 |
Mister_Magister | merobs workers are busy | 11:23 |
Mister_Magister | we need more workers | 11:23 |
* Mister_Magister tries to not place racist joke | 11:24 | |
heroic_1 | is there a way to prevent mb2 and mic from trying to refresh the mer repos for every single package? it takes about 1-2 minutes every single time, and it seems it puts a lot of strain on the servers unnecessarily | 11:32 |
Mister_Magister | i doubt they refresh repos for every of 800 packages | 11:33 |
heroic_1 | every time a package is built with "buildmw", it refreshes the repos | 11:34 |
Mister_Magister | ah yes | 11:34 |
heroic_1 | same when I start mic, it always first refreshes repos, even if they were refreshed just minutes ago | 11:34 |
Mister_Magister | and they should be refreshed | 11:35 |
Mister_Magister | something could change | 11:35 |
heroic_1 | ofc, but I mean, cmon, for every package? | 11:36 |
heroic_1 | do you clear the packages of package-v(n-1) when package-v(n) is released? | 11:36 |
Mister_Magister | ye | 11:37 |
heroic_1 | I now spend about 3 minutes waiting for repo refresh on every invocation of mic. Is that something you people just put up with? 3 minutes just to tell me "nothing provides audioflingerglue needed by pattern:jolla-hw-adaptation-kagura-1-1.noarch" | 11:40 |
Mister_Magister | install faster internet | 11:40 |
Mister_Magister | solution :v | 11:40 |
heroic_1 | 100mbit cable here | 11:40 |
heroic_1 | and a beast machine | 11:41 |
Mister_Magister | heh | 11:41 |
Mister_Magister | heroic_1: xeon? | 11:41 |
heroic_1 | generally the solution to such problems is not to instruct people to get better hardware or internet, it's to fix the tooling | 11:41 |
Mister_Magister | ye ye you didn't get my joke sorry | 11:42 |
heroic_1 | alright sry | 11:42 |
Mister_Magister | but ye we live with refresh | 11:42 |
Mister_Magister | heroic_1: now you know which package you are missing | 11:42 |
Mister_Magister | so hadk -> audioflingerglue | 11:43 |
heroic_1 | yup | 11:43 |
Mister_Magister | i like the name tho | 11:43 |
Mister_Magister | kagura | 11:43 |
Mister_Magister | there is charater with that name | 11:43 |
heroic_1 | You'll love other sony devices then. I made a lil overview: https://sx.ix5.org/info/sony-devices/ | 11:44 |
Mister_Magister | heroic_1: nah i love my motos <3 | 11:46 |
Mister_Magister | heroic_1: nothing better than some ghost or titan | 11:48 |
Mister_Magister | but ye japanese names are nice | 11:49 |
heroic_1 | "external/audioflingerglue/detect_build_targets.sh $PORT_ARCH $(gettargetarch)" fails because I have no "gettargetarch" command | 12:23 |
Mister_Magister | isn't there a mistake | 12:25 |
heroic_1 | I assume the target arch is "aarch64" since the device is 64bit | 12:25 |
Mister_Magister | shouldnt it be getarch | 12:25 |
Mister_Magister | ah | 12:25 |
Mister_Magister | gettargetarch | 12:25 |
Mister_Magister | kek nvm | 12:25 |
Mister_Magister | heroic_1: you assume wrongly | 12:25 |
Mister_Magister | or maybe not | 12:26 |
Mister_Magister | you should update something but i forgot what | 12:26 |
heroic_1 | I only started porting sunday, already something out of date? | 12:26 |
Mister_Magister | hmm | 12:26 |
heroic_1 | can't find anything related to audioflingerglue in the hadk-faq | 12:27 |
Mister_Magister | there is audioflingerglue in hadk | 12:28 |
heroic_1 | But can you explain to me what part of audioflingerlgue I need? I see it has an Android.mk file but also "rpm/audioflingerglue.spec" | 12:28 |
Mister_Magister | 13.3 | 12:28 |
Mister_Magister | whole | 12:28 |
Mister_Magister | audioflingerglue | 12:28 |
Mister_Magister | gettargetarch is in habuild and you are probabbly in sdk | 12:29 |
Mister_Magister | just follow 13.3 and you will be good to go | 12:30 |
heroic_1 | I am inside the chroot launched by "sfossdk", yes | 12:30 |
heroic_1 | so do I need to switch to the ubuntu chroot? | 12:30 |
heroic_1 | the ubuntu chroot doesn't have gettargetarch either | 12:31 |
heroic_1 | nvm, sourcing build/envsetup.sh fixes it | 12:33 |
heroic_1 | target arch is "arm", in case you're interested | 12:33 |
Mister_Magister | heh | 12:41 |
Mister_Magister | as i thought | 12:41 |
Mister_Magister | just follow the instructions | 12:41 |
Mister_Magister | never do anything on your own unless you know what you are doing lel (or someone gave you instructions) | 12:42 |
heroic_1 | thanks :) | 12:52 |
* Mister_Magister feels nostalgic | 12:52 | |
Mister_Magister | i wasn't active there in some time | 12:52 |
* Mister_Magister feels happy that he can help mal | 12:53 | |
heroic_1 | Mister_Magister: do the "sfossdk" chroot and mic somehow share a package base? When it says "installing droid-hal-kagura", does that package get installed into the chroot or into some kind of rootfs for the finished sailfish image? | 13:22 |
Mister_Magister | i know what you mean | 13:23 |
Mister_Magister | and ye | 13:23 |
Mister_Magister | it's used when building packages with mb2 | 13:23 |
Mister_Magister | it's installed in your target | 13:23 |
Mister_Magister | you were installing target do you remember? | 13:24 |
heroic_1 | I think I get it, yes. One SDK for the host and one SDK for the target. "sdk-assistant" lists all those | 13:39 |
Mister_Magister | yee | 13:40 |
Its_Mike_ | Hey sailors :) | 14:26 |
Its_Mike_ | I have some problem with droidmedia, camera is crashing, no video playback, no flashlight... | 14:27 |
Its_Mike_ | Here's the log : https://paste.ubuntu.com/p/cC5PCStf5F/ | 14:27 |
Its_Mike_ | Tried just about everything but still nothing :( | 14:28 |
Mister_Magister | you know guy is legit when he gives you log as the second thing he says | 14:28 |
Mister_Magister | girls listen guys who give you logs are good guys | 14:28 |
Its_Mike_ | lol :)) | 14:29 |
Mister_Magister | Failed to connect to camera service | 14:29 |
Mister_Magister | how was it called… | 14:29 |
Its_Mike_ | What do you mean !? | 14:29 |
Mister_Magister | ps -aux |grep mini | 14:30 |
Mister_Magister | give me output of that | 14:30 |
Its_Mike_ | OK ... | 14:30 |
Mister_Magister | chill | 14:30 |
Its_Mike_ | https://paste.ubuntu.com/p/zBXBq4Sm9D/ Here you are :)) | 14:31 |
Mister_Magister | i would grep logs for Failed to connect to camera service | 14:33 |
Its_Mike_ | Hmm..? | 14:34 |
Mister_Magister | look at topic | 14:35 |
Its_Mike_ | btw, any idea about where the problem cames from? I mean is it related to droidmedia or the device kernel, because everything were fine with camera and other things on kernel 3.4 | 14:38 |
Mister_Magister | it comes from camera service not running prably | 14:38 |
Its_Mike_ | And that relates to kernel? | 14:39 |
Mister_Magister | probably | 14:40 |
Mister_Magister | maybe | 14:40 |
Mister_Magister | who knows | 14:40 |
Its_Mike_ | :)) any chance to fix it? | 14:41 |
Mister_Magister | who knows | 14:45 |
Mister_Magister | grep logs | 14:45 |
Its_Mike_ | OK then... | 14:46 |
Mister_Magister | spiiroin: my moto g2 won't lock screen after 3.0.1.11 update. When it tries to lock screen or when i lock screen it just wakes up back. it only locks screen when i cover proximity sensor | 14:46 |
mal | Its_Mike_: pastebin whole dmesg | 15:15 |
Mister_Magister | oh hi mal | 15:20 |
Its_Mike_ | mal : OK ! | 15:26 |
Its_Mike_ | https://paste.ubuntu.com/p/ybX3ksWwJz/ | 15:31 |
mal | Mister_Magister: hi, did you solve the lock screen issue already? | 15:35 |
Mister_Magister | noo i'm waiting for jusa | 15:36 |
Mister_Magister | thought it might be low power mode but no | 15:36 |
Mister_Magister | maybe my custom mce from jusa | 15:36 |
mal | Its_Mike_: I said dmesg, not logcat | 15:36 |
Mister_Magister | this phone has some modifications to mce | 15:36 |
mal | ok | 15:36 |
Mister_Magister | yee older mce | 15:37 |
Mister_Magister | 1.96 and 1.98 is in 3.0.1 | 15:38 |
Mister_Magister | or not | 15:38 |
Mister_Magister | it's 1.98 installed | 15:38 |
Mister_Magister | hm | 15:38 |
Its_Mike_ | mal : So sorry mal :)) | 15:39 |
mal | Mister_Magister: ah, so it installed the wrong version then, maybe rebase the changes you have in mce or just force install the old mce | 15:39 |
Mister_Magister | whoa i have both of them installed | 15:39 |
Its_Mike_ | Journalctl ( in case if you needed ) : https://paste.ubuntu.com/p/qj5NkhtXsv/ and dmesg : https://paste.ubuntu.com/p/hyMQ4ZfcbH/ | 15:39 |
Mister_Magister | i will try to uninstall old version | 15:39 |
Mister_Magister | hmm dunno how to tho | 15:40 |
Mister_Magister | something is just not right but i can't simply remove mce | 15:43 |
mal | Mister_Magister: wouldn't the old one be the correct version, chech where those come from, pkcon search name mce should show repo names | 15:43 |
mal | I assume it just used the newer version from jolla repo and not use the custom version | 15:44 |
Mister_Magister | mal: i downgraded mce and it fixed issue | 15:46 |
Mister_Magister | mal: which mce do you have? | 15:46 |
mal | Mister_Magister: 1.19.2.2 | 15:49 |
mal | Mister_Magister: that is the default in 3.0.1.11 | 15:49 |
mal | Mister_Magister: so maybe you could rebase the branch with custom mce changes on top of that version and then it should be fine | 15:50 |
mal | Its_Mike_: does that port have other issues? | 15:59 |
Its_Mike_ | Yeah ... | 15:59 |
mal | like what? | 15:59 |
Its_Mike_ | Bluetooth not working, no RIL | 16:00 |
Its_Mike_ | I'm porting kernel 3.10 , everything were stable on kernel 3.4 for that port | 16:01 |
mal | different android base? | 16:01 |
Its_Mike_ | nope, hybris12.1 for both of them | 16:01 |
mal | where did you get the new kernel? | 16:02 |
Its_Mike_ | https://github.com/alireza1219/android_kernel_xiaomi_cancro | 16:03 |
mal | is that intended for 12.1 base? | 16:03 |
Its_Mike_ | Hmmm, I'm not sure! | 16:04 |
mal | why did you want to move to 3.10 kernel? | 16:05 |
Its_Mike_ | for anbox :)) | 16:05 |
Its_Mike_ | So no luck to fix it? | 16:07 |
mal | not sure, there are kernel traces from camera in log, difficult to say what is causing those, no idea what kind things are needed if you change the kernel | 16:12 |
Its_Mike_ | Oh :( that's bad... | 16:12 |
mal | it's also possible that it just doesn't find the firmware or something | 16:14 |
mal | or cannot load those | 16:14 |
Its_Mike_ | Hmm, my android base is still on 3.4 kernel | 16:15 |
Its_Mike_ | Does it makes any problem? | 16:15 |
mal | I still don't know for what the kernel you use was made originally | 16:16 |
mal | was it some testing kernel, some different android base or what | 16:16 |
Its_Mike_ | It's used in a large range of custom roms for my device, from android 6.x to 9.x | 16:18 |
mal | ok | 16:19 |
Its_Mike_ | So ? | 16:19 |
T4 | <elros34> was it used for your android base or you just pick up random kernel and hope it will work? | 16:21 |
Its_Mike_ | Nope ... it wasn't | 16:22 |
heroic_1 | so it looks like my rootfs is packed correctly, but it fails with the "root.img" file: https://del.dog/uzicuxetid.sql | 16:57 |
heroic_1 | this is my kickstart file https://del.dog/eyedametod.sh | 16:57 |
Mister_Magister | mal: no 1.98 is in 3.0.1.11 | 17:09 |
Mister_Magister | not 1.19 | 17:09 |
Mister_Magister | and i have now 1.96 | 17:09 |
Mister_Magister | you sure you got valid data? | 17:09 |
Mister_Magister | mal: even jolla phone has 1.98 update your super old mce lol | 17:11 |
heroic_1 | I don't see where root.img would even get generated | 17:12 |
heroic_1 | should I be using "mic create loop" instead of "mic create fs" like the Sailfish X guide says? | 17:15 |
mal | Mister_Magister: typo | 17:36 |
Mister_Magister | mal: kek | 17:36 |
Mister_Magister | nah it just won't work on 1.98 | 17:36 |
Mister_Magister | and there was no changes that should cause that | 17:36 |
mal | Mister_Magister: but you said you have some custom mce? | 17:38 |
heroic_1 | the pack command for root.img is adapted from nile: https://github.com/mer-hybris/droid-config-sony-nile/blob/master/kickstart/pack/h4113/hybris#L25 | 17:40 |
heroic_1 | I can't find it in other configs, e.g. in latte or espresso | 17:41 |
heroic_1 | I "fixed" it for now by using "mic create loop", which creates a "tar.bz2" image with "root.img" inside, and just adding a step in the kickstart to untar it. Hacky, but it should work for now until I figure out how mic internals work | 18:07 |
mal | heroic_1: nile devices use different build method compared to community ports | 18:26 |
T4 | <adampigg> @eugenio_g7 https://github.com/sailfish-on-latte/droid-config-latte/pull/16 :) | 18:26 |
heroic_1 | could it be that the jolla servers are completely overloaded? or the obs thingy? refreshing repos and downloading packages(e.g. gcc for the sdk tooling) takes forever | 19:15 |
piggz | abranson: not sure i should thank you for selling piggz-o-vision on tjc! :D | 19:17 |
piggz | mal: dfconf appears to read a setting containing a QSize back ok, but in qml, im having trouble reading it, any thoughts? | 19:19 |
mal | piggz: ? | 19:25 |
piggz | mal: using a ConfigurationValue containing a qsize, it is saved ok, as tested using dconf at the console, but using the value in QML it appears empty...quite odd | 19:26 |
piggz | printing it results in nothing | 19:26 |
piggz | using console.log | 19:27 |
mal | piggz: sorry, I can't help today, I'm almost falling asleep | 19:28 |
piggz | mal: np ... i'll try storing it in an intermediary var | 19:29 |
piggz | or a property size | 19:30 |
heroic_1 | hey, can anyone tell me how system.img is supposed to look like? I think the nile stuff is a bit odd, I have only home.img.gz and root.img.gz, shouldn't the system image be a filesystem itself? | 20:18 |
T4 | <eugenio_g7> heroic_1, system.img is "fimage", which contains the factory reset images. The actual LVM partitions are flashed in userdata (at least on loire, but I think nile is the same) | 20:43 |
heroic_1 | eugenio_g7: thanks, I was a bit confused. then it looks alright to me | 20:53 |
heroic_1 | but I think something is wrong with my "root" lvm partition: https://del.dog/fuqinurupi.sql | 20:54 |
T4 | <adampigg> @eugenio_g7 any progress joy tonight? | 22:38 |
T4 | <eugenio_g7> nope | 22:44 |
T4 | <eugenio_g7> on your front? | 22:44 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!