Wednesday, 2020-05-06

T42<edp_17> I need a little support. I have boot loop, however I have all partition mounted:
T42<edp_17> I have tried: 'ln -s /dev/null /etc/systemd/system/ofono.service' but didn't help00:11
T42<edp_17> and I have BOARD_KERNEL_CMDLINE := console=ttySAC2,115200 consoleblank=0 selinux=0 in boardcommonconfig.mk00:13
T42<edp_17> The device is Galaxy S2 (i9100) and the base is CM-14.1.00:14
T42<edp_17> Can the reason of this behaviour be that I used Cyanogenmod kernel but LOS android image?00:26
r0kk3rzwhy arent you using the kernel associated with your image?00:33
T42<edp_17> A long story in short. I already had a LOS14.1 image and when I started to work on the new port with 14.1 base, I realized that used cm kernel only after that I made the hybris-hal and the image.00:41
r0kk3rzLOS used to be cm, so as long as its the kernel for the image thats fine00:41
T42<edp_17> Ok, thanks.00:42
T42<edp_17> I have found a cm-14.1 android image and will try this one.00:46
r0kk3rzi assume the image you had booted and worked01:03
T42<edp_17> Yes, it did. I had been used it on my device for years.01:04
r0kk3rzso you want to build sailfish with the closest matching source to that01:04
r0kk3rzthat is all01:04
T42<edp_17> Yeah, I guess need to use the los kernel for that image.01:05
T42<edp_17> I have tried with the downloaded cm-14.1 image, and the result was the same. Tomorrow I will re-try.01:06
T42<birdzhang> cm and los are same01:06
r0kk3rzyou're probably barking up the wrong tree01:06
T42<edp_17> I know the los is the successor of cm, but I was not sure whether I can mix the kernel (hybris-hal) and the android image that is under SFOS.01:08
T42<edp_17> That's all.01:08
T42<edp_17> The problem is probably somewhere else.01:09
T42<edp_17> By the way. Can I try building image or it is still not 'officially' out in the repos?01:11
r0kk3rzyou can01:12
T42<edp_17> Thanks.01:12
r0kk3rzfor early stage stuff it wont really matter01:13
r0kk3rzand like i said, you use the kernel that the base image uses01:13
r0kk3rzit doesnt matter whether its los or cm or whatever, so long as its what the base image uses01:14
T42<edp_17> Thanks. I think push aside the 14.1 attempt for a while and go back to my 12.1 port and try to upgrade that image to
r0kk3rzso you had a working port? why change the base01:16
* Oksana , in the end, upgraded to devel - Videos from Gallery play fine, Camera takes photographs fine (not black, focus works, no problems whatsoever), SIM card slots are fine, patch for Notes timestamps applies fine (it didn't work in testing?)...02:01
OksanaVolume control buttons are fine. Desktop/lipstick/mainScreen/whatever prefers to stay in portrait all the time, while terminal auto-rotates to landscape or portrait easily depending on orientation - in short, weird, but merely a cosmetic glitch.02:02
* Oksana has moved over Notes from old Sailfish to new Sailfish - now should figure out how to move over history of phone calls and SMS and MMS02:03
UmeaboyPlease merge my PR on hybris-boot. I just added the mountpoints for maple.03:41
UmeaboyMy bad! Forgot I had already added a PR to get the mountpoints added.03:50
spiiroinDylanVanAssche: sort of like that but not at all like that ;-)04:11
UmeaboyBuilding hybris for maple as we speak. :)04:57
DylanVanAsschespiiroin (IRC): It's trash code, but it does the job πŸ™‚ Now we can discuss a bit how we want it: configuration, splitting up code, ... What do you think?06:16
T42<edp_17> @r0kk3rz: Yes, I have got a working port with cm12.1 base. Yesterday I tried to make another one with cm14.1 because hoped the camera recording issue would work.06:59
T42<edp_17> Ehh, not the 'camera recording issue' but the 'camera recording'. πŸ˜„07:00
T42<edp_17> I would like to build a new image for the latest SFOS. Do I need to upgrade the Platform SDK to or leave it as it is currently
T42<edp_17> This is for my working S2 port with cm12.1 base.08:14
T42<birdzhang> rinigus:
T42<birdzhang> json-glib is on jolla repo09:03
T42<edp_17> When I am trying to update the tooling to the latest with command 'sdk-assistant update SailfishOS-3.2.1', I am getting: 'mount: /srv/mer/toolings/SailfishOS-3.2.1/etc/resolv.conf: special device /run/connman/resolv.conf does not exist.' What am I doing wrong?09:24
deathmist@edp_17 I've always just straight up removed and re-added latest tooling, but that could maybe also be something to look into09:37
T42<edp_17> Thanks. I think last time somehow I managed to update tooling and target (for another environment) but it didn't work when I started building. Finally I ended up with delete and recreate them, but thought it would work this time.09:47
T42<edp_17> A silly question, if I keep the current 3.2 tooling and create a new one for 3.3, how will the process know which one to use?09:50
T42<edp_17> Ops, now I know why the update didn't work. For the same reason why the download failed: 'Could not resolve host:'10:02
T42<edp_17> It was just my PC. Looks like time to time I need to reboot.10:09
rinigusbirdzhang: I am going through all my projects to make them sfos 3.3 compatible and trying to keep support for older SFOS versions. haven't made it to flatpak yet, will take some days, I think10:50
T42<birdzhang> it’s okay, just info you11:34
T42<RealDanct12> i'd like to bring 3.3 to my lavender, though i still have to create an tjc account11:35
rinigusbirdzhang: thanks - wrote down into todo :)11:35
UmeaboyHmmmmmmm. Did I miss to do something to make this work?
UmeaboyThe creations look fine for me.11:54
UmeaboyBesides line 33.11:54
T42<elros34> what about line 14?11:56
T42<elros34> Has anyone which use libhybris- tried latest in 3.3.0? It seems now it's even worse (even --enabled-trace doesn't help) unless I mess something up11:58
T42<edp_17> @Umeaboy: I am not sure it does make any difference but I only use the '$VENDOR-$DEVICE-$PORT_ARCH' rather than 'SailfishOS-$VENDOR-$DEVICE-$PORT_ARCH' when creating target. Try to re-create with removing the 'SailfishOS-' tag.12:13
T42<edp_17> Or just try to build the image and you'll see if anything is missing. 😁12:14
T42<elros34> obviously it make a difference:  $VENDOR-$DEVICE-$PORT_ARCH is default target name used in all instructions and scripts12:15
T42<edp_17> Thanks.12:16
UmeaboyThat did the trick. Thanks. Removing SailfishOS from the sdk-assistant create line.....12:18
UmeaboyIs the error Repository 'adaptation0' is invalid. going to be solved in the near future?12:21
UmeaboyI also need to solve this: fatal: No url found for submodule path 'kernel/sony/msm-4.9/kernel/drivers/staging/wlan-qc/fw-api' in .gitmodules12:28
UmeaboyIt also says: fatal: run_command returned non-zero status while recursing in the nested submodules of kernel/sony/msm-4.9/kernel12:28
UmeaboyAnd Fatal: Cannot save state of Git submodules: git-stash failed for some.12:28
maldid you follow the instructions? meaning the part about ./ --mb ?12:30
Umeaboymal: Isn't this the right way to do it?12:31
UmeaboyEverything has been working quite OK until now.12:32
Umeaboyhybris-hal and droidmedia built.12:32
malwhat are you doing after that to get the error?12:34
UmeaboyYes, I did create the spec file.12:36
malso what command gives the error?12:36
malyou never told that12:36
Umeaboyrpm/dhd/helpers/ --droid-hal12:37
malso does the $ANDROID_ROOT/fw-api have content? did you correct pull submodules when you cloned the droid-hal repo12:41
UmeaboyHere's a picture of the fw-api directory content:
Umeaboymal: Any workaround?13:08
malnot sure what you did wrong13:09
vknechtiirc, also had problems with wlan-qc stuff until at least git add'ed them13:10
UmeaboyUhu, so this is not MY error this time. Wooohoooo!13:15
spiiroinDylanVanAssche: I cooked up something ->
spiiroinone thing to check: are the ac/usb charger devices always present? or are they dynamically added/removed depending on what is connected13:40
spiiroin(adding should be ok, but removal is not handled atm at all)13:41
DylanVanAsschespiiroin (IRC): They are always present in sysfs. They have some 'connected' state to see which one is plugged inused and which not13:42
Mister_Magistermal: how to fix dhv on 3.3 without rebuilding dhd?13:43
malhow is it broken?13:44
T42<edp_17> Guys, on sfos when I am trying to install a kodi from openrepos, I get: 'Nothing provides needed by kodi-16.1-1.armv7hl'. I didn't get this error on the
DylanVanAsschespiiroin (IRC): So much better than my demo C code 😁 which was so efficiently horrible :D13:48
DylanVanAsscheI will test it out later today13:48
T42<birdzhang> mal: logs
T42<edp_17> The libgcrypt package is installed.13:49
T42<edp_17> 'No update candidate for 'libgcrypt-1.8.5+git1-1.4.1.jolla.armv7hl'. The highest available version is already installed.'13:49
T42<birdzhang> I thought you knew13:49
mal@birdzhang yeah, no idea why that fails13:51
malI was just confused why droid-hal was mentioned13:52
T42<elros34> @birdzhang you can find workaround here:
T42<birdzhang> @elros34 yeah, i used that way fix dhv on obs.  Mister_Magister asked how to fix without rebuilding dhd13:55
T42<elros34> ah ok. It sane to rebuild dhd because of changes in user/groups handling13:56
malalthough some fixes are still missing from system/core13:57
Mister_Magisterwelp, no update for my users then13:57
malMister_Magister: why can't you rebuild dhd?13:57
Mister_Magisterit's too much to bother and i don't have whole hadk locally13:57
malit doesn't really take long to rebuild13:58
Mister_Magisterthe issue is with using custom droid-hal-device instead of hybris one13:59
malwhat is the difference?13:59
Mister_Magisterand later on i will have to rebuild again to switch to master again eh14:03
Mister_Magisterand syncing whole repo is not quicc14:03
malI keep copy of all hybris-* source trees locally14:05
T42<elros34> reverting this can also potentially help:
Mister_Magistermal: ye i know i don't have that much space14:09
malI think the real reason could be installation order, filesystem is installed after droid-hal kernel14:14
T42<elros34> same issue is in fresh 3.3.0 target14:15
DylanVanAsschespiiroin (IRC): Charging gauge works now πŸŽ‰ Only when you unplug the cable, it says 'charging' instead of 'charger removed'14:16
spiiroinDylanVanAssche: nice, eh ;-) might be some interplay from charger node emitting notification and battery not14:18
DylanVanAsschespiiroin (IRC): Really nice work!14:18
spiiroindoing a forced update when udev reports anything might solve that, but ... ugly14:18
T42<adampigg> its all ugly :D14:19
DylanVanAsscheIt should support udev notifications out of the box like other hardware, but yeah, that's life14:19
spiiroinI'll add it just to see if it makes any difference14:20
spiiroinadded a commit14:28
spiiroinprobably would make sense to delay such operation if it is needed. to avoid unnecessary repeating & improve changes of getting relevant info14:29
DylanVanAsscheBuilding now :)14:30
DylanVanAsschespiiroin (IRC): That works! Unplugging is now properly shown in the UI. Another thing I noticed: developer mode or any other USB mode works when plugged in, but when you plug it into a normal charger, it thinks that it's plugged into an USB port instead of a charger :D14:42
mal@elros34 I have a cleaner way to fix the /boot issue14:48
T42<elros34> great, I don't fully understand why this fail14:49
malI do14:50
malwell I think I understand14:50
T42<adampigg> if you could also understand why harbour-storeman cannot be install with a kickstart, that would be great :D14:55
T42<elros34> @adampigg I remember I had to rebuild it by myself, that one from openrepos coudn't be installed14:56
mal@elros34 this seems to work but need to do some more testing
T42<adampigg> @elros34 oh, is it some weird package problem? i added a hack to install it to the end of out kickstart14:56
T42<elros34> Some dependency, which prevents it's from installing, can't remember it now14:58
T42<elros34> mal: not sure this will help for local sdk target14:58
T42<elros34> @adampigg IIRC storeman rpm was build with short-circuit option15:01
mal@elros34 why not?15:01
mal@adampigg why this ?15:02
T42<elros34> I can't see how this could, filesystem is already installed in target but I will test your solution later15:03
ThatComputerKidI have sailfish os on my galaxy tab. So far so good except for the touchscreen appears to be rotated at a different angle than the screen itself, is there any documentation on how to rotate the touch screen?15:05
spiiroinDylanVanAssche: do you have separate "xxx-ac" and "xxx-usb" power supply devices (as I thought there would be)? Was discussing with abranson earlier and he had only "usb" one.15:07
spiiroinif there is only one charger device, it probably should indicate whether pc or charger is connected15:08
spiiroinwhich is how all qc devices work, but maybe props/whatnot are different with pinephone15:09
mal@elros34 is the problem also on local build?15:09
T42<elros34> mal: yes, on fresh target15:10
T42<elros34> ThatComputerKid: try to add ':rotate=90' to evdevtouch plugin in /var/lib/environment/compositor/droid-hal-device.conf15:12
spiiroinDylanVanAssche: i.e. now it probably ends up using "mtk style" detection logic (separate ac/usb/wireless/... device nodes) and having "usb" in name -> triggers "is pc"15:13
ThatComputerKidT42 When I created the files in TWRP and rebooted they deleted themselves. Any idea what's going on there?15:30
T42<adampigg> mal: because I dont know why i reverted it originally ... it was summer last year, and con only think it was a mistake!15:30
T42<adampigg> mal: so, this makes the branch closer to master15:32
T42<elros34> ThatComputerKid: you don't create any file, it's is already there: /data/.stowaways/sailfishos/ is / root path for sailfish in twrp15:33
meowdudeis hybris-11 worth it for sfos 315:42
meowdudejust in terms of hardware support, I know the different bases aren't very epic15:42
DylanVanAsschespiiroin (IRC): I have those indeed...
DylanVanAsschespiiroin (IRC): Do I need to configure it somehow to activate this commit?16:10
ThatComputerKidT42 Thank you that helped. I am into the sailfish os now but cannot connect to wifi for some reason. I go into the WLAN settings but there are no wifi networks16:27
T42<elros34> Did you build wlan as a module?16:33
ThatComputerKidI am using a build from someone else, how can I check. please excuse my noobieness16:35
T42<elros34> Ah so you just install image? I would suggest to ask porter how he made wifi work. Usually it's enough to build wlan as module and then 'modprobe wlan' in systemd service16:38
ThatComputerKidThe problem is that I am actually 3 builds behind but the next 3 build won't install on my tablet. a modprobe wlan brings up the message couldn't find module so I guess it isn't there.16:43
ThatComputerKid Is there a way to build it in now? post install?16:44
T42<elros34> Why you you can't install latest build?16:47
ThatComputerKidI get a " Failed to extract filesystem  " Error16:47
T42<elros34> Which twrp version did you try?16:48
ThatComputerKidtwrp 3.3.0-216:50
ThatComputerKidDo I need to update it?16:50
T42<elros34> you could downgrade it16:51
T42<elros34> try something around 3.016:51
ThatComputerKidActually I just found that Sailfish os can apperantyl see my mac address...17:10
ThatComputerKidI can't figure ou t how to reflash TWRP17:23
T42<elros34> has anyone experienced more browser crashes in 3.3.0? Could be related to gst-droid19:07
piggzmal: any idea why this fails in testing but works in devel: ?
deathmistpiggz: worked for me, maybe try upgrading it to version 1.0.30?20:05
rinigusbirdzhang: flatpak is recompiled using sfos-provided json-glib and libseccomp. hopefully, this will resolve the conflicts20:10
piggzdeathmist: hmm, nfcd still wont build :/21:03
piggzdeathmist: ah, failures are random, it worked after a re-trigger!21:16
T42<birdzhang> rinigus: thank you23:07
T42<birdzhang> @elros34 i have, both on xa2 and my port devices23:08

Generated by 2.17.1 by Marius Gedminas - find it at!