Thursday, 2019-02-14

T4Felix (MISSING @USERNAME! was added by: Felix (MISSING @USERNAME!
*** me is now known as Guest4649700:42
heroic_1yamui and initrd-helpers and hw-ramdisk don't seem to be in the repos though00:54
r0kk3rzthose are in the sailfishos github
Mister_Magisterafter 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 12710:48
r0kk3rzdid you update hybris-sensorfw ?11:02
Mister_Magisternow yes11:04
Mister_Magisterits up to date11:04
Mister_Magisterfek there is newer one11:05
Mister_Magisterand i updated devel stupid me11:05
heroic_1mic is failing me: "Error <creator>[02/14 10:55:14] : Unable to find pattern: Jolla Configuration f8331"11:10
Mister_Magisterheroic_1: hadk11:10
heroic_1what's odd is that my kickstart has 3 lines that look like this: "%packages @Jolla Configuration f8331 %end"11:11
heroic_1isn't "packages" supposed to be non-pretty? i.e. "droid-config-f8331" instead of the full name?11:11
Mister_Magisteranswer is in hadk lel11:12
Mister_Magisterno it shouldnt11:12
heroic_1"Substitute the line @Jolla Configuration @DEVICE@ with @jolla-hw-adaptation-@DEVICE@11:13
heroic_1in your .ks" thx :) I11:13
Mister_Magisterheroic_1: that's not solution11:15
Mister_Magisterthat's only step for debugging11:15
Mister_Magisteryou need to rever it back later11:15
Mister_Magistercontinue on reading11:15
heroic_1well 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 f833111:17
heroic_1jeez my grammar is failing me today11:17
Mister_Magister could be i never had sony11:19
Mister_Magistermerobs workers are busy11:23
Mister_Magisterwe need more workers11:23
* Mister_Magister tries to not place racist joke11:24
heroic_1is 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 unnecessarily11:32
Mister_Magisteri doubt they refresh repos for every of 800 packages11:33
heroic_1every time a package is built with "buildmw", it refreshes the repos11:34
Mister_Magisterah yes11:34
heroic_1same when I start mic, it always first refreshes repos, even if they were refreshed just minutes ago11:34
Mister_Magisterand they should be refreshed11:35
Mister_Magistersomething could change11:35
heroic_1ofc, but I mean, cmon, for every package?11:36
heroic_1do you clear the packages of package-v(n-1) when package-v(n) is released?11:36
heroic_1I 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_Magisterinstall faster internet11:40
Mister_Magistersolution :v11:40
heroic_1100mbit cable here11:40
heroic_1and a beast machine11:41
Mister_Magisterheroic_1: xeon?11:41
heroic_1generally the solution to such problems is not to instruct people to get better hardware or internet, it's to fix the tooling11:41
Mister_Magisterye ye you didn't get my joke sorry11:42
heroic_1alright sry11:42
Mister_Magisterbut ye we live with refresh11:42
Mister_Magisterheroic_1: now you know which package you are missing11:42
Mister_Magisterso hadk -> audioflingerglue11:43
Mister_Magisteri like the name tho11:43
Mister_Magisterthere is charater with that name11:43
heroic_1You'll love other sony devices then. I made a lil overview:
Mister_Magisterheroic_1: nah i love my motos <311:46
Mister_Magisterheroic_1: nothing better than some ghost or titan11:48
Mister_Magisterbut ye japanese names are nice11:49
heroic_1"external/audioflingerglue/ $PORT_ARCH $(gettargetarch)" fails because I have no "gettargetarch" command12:23
Mister_Magisterisn't there a mistake12:25
heroic_1I assume the target arch is "aarch64" since the device is 64bit12:25
Mister_Magistershouldnt it be getarch12:25
Mister_Magisterkek nvm12:25
Mister_Magisterheroic_1: you assume wrongly12:25
Mister_Magisteror maybe not12:26
Mister_Magisteryou should update something but i forgot what12:26
heroic_1I only started porting sunday, already something out of date?12:26
heroic_1can't find anything related to audioflingerglue in the hadk-faq12:27
Mister_Magisterthere is audioflingerglue in hadk12:28
heroic_1But can you explain to me what part of audioflingerlgue I need? I see it has an file but also "rpm/audioflingerglue.spec"12:28
Mister_Magistergettargetarch is in habuild and you are probabbly in sdk12:29
Mister_Magisterjust follow 13.3 and you will be good to go12:30
heroic_1I am inside the chroot launched by "sfossdk", yes12:30
heroic_1so do I need to switch to the ubuntu chroot?12:30
heroic_1the ubuntu chroot doesn't have gettargetarch either12:31
heroic_1nvm, sourcing build/ fixes it12:33
heroic_1target arch is "arm", in case you're interested12:33
Mister_Magisteras i thought12:41
Mister_Magisterjust follow the instructions12:41
Mister_Magisternever do anything on your own unless you know what you are doing lel (or someone gave you instructions)12:42
heroic_1thanks :)12:52
* Mister_Magister feels nostalgic12:52
Mister_Magisteri wasn't active there in some time12:52
* Mister_Magister feels happy that he can help mal12:53
heroic_1Mister_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_Magisteri know what you mean13:23
Mister_Magisterand ye13:23
Mister_Magisterit's used when building packages with mb213:23
Mister_Magisterit's installed in your target13:23
Mister_Magisteryou were installing target do you remember?13:24
heroic_1I think I get it, yes. One SDK for the host and one SDK for the target. "sdk-assistant" lists all those13:39
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 :
Its_Mike_Tried just about everything but still nothing :(14:28
Mister_Magisteryou know guy is legit when he gives you log as the second thing he says14:28
Mister_Magistergirls listen guys who give you logs are good guys14:28
Its_Mike_lol :))14:29
Mister_MagisterFailed to connect to camera service14:29
Mister_Magisterhow was it called…14:29
Its_Mike_What do you mean !?14:29
Mister_Magisterps -aux |grep mini14:30
Mister_Magistergive me output of that14:30
Its_Mike_OK ...14:30
Its_Mike_ Here you are :))14:31
Mister_Magisteri would grep logs for Failed to connect to camera service14:33
Mister_Magisterlook at topic14: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.414:38
Mister_Magisterit comes from camera service not running prably14:38
Its_Mike_And that relates to kernel?14:39
Mister_Magisterwho knows14:40
Its_Mike_:)) any chance to fix it?14:41
Mister_Magisterwho knows14:45
Mister_Magistergrep logs14:45
Its_Mike_OK then...14:46
Mister_Magisterspiiroin: my moto g2 won't lock screen after 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 sensor14:46
malIts_Mike_: pastebin whole dmesg15:15
Mister_Magisteroh hi mal15:20
Its_Mike_mal : OK !15:26
malMister_Magister: hi, did you solve the lock screen issue already?15:35
Mister_Magisternoo i'm waiting for jusa15:36
Mister_Magisterthought it might be low power mode but no15:36
Mister_Magistermaybe my custom mce from jusa15:36
malIts_Mike_: I said dmesg, not logcat15:36
Mister_Magisterthis phone has some modifications to mce15:36
Mister_Magisteryee older mce15:37
Mister_Magister1.96 and 1.98 is in 3.0.115:38
Mister_Magisteror not15:38
Mister_Magisterit's 1.98 installed15:38
Its_Mike_mal : So sorry mal :))15:39
malMister_Magister: ah, so it installed the wrong version then, maybe rebase the changes you have in mce or just force install the old mce15:39
Mister_Magisterwhoa i have both of them installed15:39
Its_Mike_Journalctl ( in case if you needed ) : and dmesg :
Mister_Magisteri will try to uninstall old version15:39
Mister_Magisterhmm dunno how to tho15:40
Mister_Magistersomething is just not right but i can't simply remove mce15:43
malMister_Magister: wouldn't the old one be the correct version, chech where those come from, pkcon search name mce should show repo names15:43
malI assume it just used the newer version from jolla repo and not use the custom version15:44
Mister_Magistermal: i downgraded mce and it fixed issue15:46
Mister_Magistermal: which mce do you have?15:46
malMister_Magister: that is the default in
malMister_Magister: so maybe you could rebase the branch with custom mce changes on top of that version and then it should be fine15:50
malIts_Mike_: does that port have other issues?15:59
Its_Mike_Yeah ...15:59
mallike what?15:59
Its_Mike_Bluetooth not working, no RIL16:00
Its_Mike_I'm porting kernel 3.10 , everything were stable on kernel 3.4 for that port16:01
maldifferent android base?16:01
Its_Mike_nope, hybris12.1 for both of them16:01
malwhere did you get the new kernel?16:02
malis that intended for 12.1 base?16:03
Its_Mike_Hmmm, I'm not sure!16:04
malwhy 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
malnot 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 kernel16:12
Its_Mike_Oh :( that's bad...16:12
malit's also possible that it just doesn't find the firmware or something16:14
malor cannot load those16:14
Its_Mike_Hmm, my android base is still on 3.4 kernel16:15
Its_Mike_Does it makes any problem?16:15
malI still don't know for what the kernel you use was made originally16:16
malwas it some testing kernel, some different android base or what16:16
Its_Mike_It's used in a large range of custom roms for my device, from android 6.x to 9.x16:18
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't16:22
heroic_1so it looks like my rootfs is packed correctly, but it fails with the "root.img" file:
heroic_1this is my kickstart file
Mister_Magistermal: no 1.98 is in
Mister_Magisternot 1.1917:09
Mister_Magisterand i have now 1.9617:09
Mister_Magisteryou sure you got valid data?17:09
Mister_Magistermal: even jolla phone has 1.98 update your super old mce lol17:11
heroic_1I don't see where root.img would even get generated17:12
heroic_1should I be using "mic create loop" instead of "mic create fs" like the Sailfish X guide says?17:15
malMister_Magister: typo17:36
Mister_Magistermal: kek17:36
Mister_Magisternah it just won't work on 1.9817:36
Mister_Magisterand there was no changes that should cause that17:36
malMister_Magister: but you said you have some custom mce?17:38
heroic_1the pack command for root.img is adapted from nile:
heroic_1I can't find it in other configs, e.g. in latte or espresso17:41
heroic_1I "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 work18:07
malheroic_1: nile devices use different build method compared to community ports18:26
T4<adampigg> @eugenio_g7 :)18:26
heroic_1could 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 forever19:15
piggzabranson: not sure i should thank you for selling piggz-o-vision on tjc! :D19:17
piggzmal: dfconf appears to read a setting containing a QSize back ok, but in qml, im having trouble reading it, any thoughts?19:19
malpiggz: ?19:25
piggzmal: 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 odd19:26
piggzprinting it results in nothing19:26
piggzusing console.log19:27
malpiggz: sorry, I can't help today, I'm almost falling asleep19:28
piggzmal: np ... i'll try storing it in an intermediary var19:29
piggzor a property size19:30
heroic_1hey, 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_1eugenio_g7: thanks, I was a bit confused. then it looks alright to me20:53
heroic_1but I think something is wrong with my "root" lvm partition:
T4<adampigg> @eugenio_g7 any progress joy tonight?22:38
T4<eugenio_g7> nope22:44
T4<eugenio_g7> on your front?22:44

Generated by 2.17.1 by Marius Gedminas - find it at!