Thursday, 2018-06-21

MeowDudeCBtime to see what the default state of /sys/****/control is...01:49
MeowDudeCBit's auto as well01:49
MeowDudeCBwritev(4, [{"\6", 1}, {"use-Rlog/RLOG-RIL(s)\0", 21}, {"Failed to get socket port [7777]"..., 45}], 3) = 6701:59
MeowDudeCBthis seems to be the big lebowski, the thingy in the rild that is borked01:59
MeowDudeCBwritev(4, [{"\6", 1}, {"RILC\0", 5}, {"Failed to get socket rild\0", 26}], 3) = 3202:00
MeowDudeCBmonich: does any of this ring any bells?02:00
MeowDudeCBI am stracing /system/bin/rild02:00
MeowDudeCBhopefully my init changes are helping the modem, I think I am getting a better understanding of this stuf02:22
MeowDudeCBhell yeah! the speaker AND headphone jack both work now thanks to that h2w fix in hadk!02:25
MeowDudeCBbeidl: /sys/fs/kdbus/0-system/bus: No such file or directory -- this is the issue with, it can't find the old hybris10.1 dbus directory, do you (or anyone reading this) know what it is called in cm11/hybris11?03:21
MeowDudeCBokay how does THIS make any sense: mkdir: cannot create directory `kdbus': No such file or directory03:27
KsenZ Error 50308:21
*** doniks_ is now known as doniks09:26
*** zhxt is now known as zhxt_away11:15
branek_Just started porting for OnePlus 5T, based on lineage-15.1... And until device delivered to me, decided to try to go by HADK doc...11:42
branek_Just created local manifest,
malbranek_: does that only have 15.1?11:42
mal15.1 porting needs some undocumented tinkering11:42
branek_well, I want to give a try... :)11:43
branek_should I use oneplus kernel, or kernel from 15.1?11:43
T4<abhishek_0> mal i flashed the hybris-boot.img to test if anbox works or not.. my wifi stopped working11:46
malusually 15.1 kernel is better, I assume it's tested11:46
mal@abhishek_0 if you had build wlan as module you need to either manually copy the modules to the device or just repackage droid-hal rpms and install those11:47
T4<abhishek_0> oh .. alright11:48
branek_@mal thanks. And what about manifest file, is it ok for start?11:49
malyes, but you'll need to download libhybris sources before building hybris-hal, from a certain branch11:52
branek_@mal Understood. I guess, right path is to start from mer-hybris/droid-hal-device, and to configure it for oneplus 5T? On my own repo which, added to manifest xml?12:07
r0kk3rzdo the hal build first, follow the order in the hadk12:08
branek_@r0kk3rz Sorry, but I am confused now... I'm following hadk, and with current manifest ( should I proceed with build like in chapter 5.4 of hadk?12:14
branek_@r0kk3rz great... starting sync now...12:19
_svenmal: can you tell me in which file is screen rotation locking stuff?13:15
mal_sven: /etc/dconf/db/vendor.d/silica-configs.txt  maybe and in there something like default_allowed_orientations=15 changing that value based on something might help14:01
malI think the value is a mask value14:02
T4<abhishek_0> anbox keeps on crashing14:11
T4<abhishek_0> it just loads up to the splash screen and then FC14:13
maldid you check if you have /var/lib/anbox/overlay/system/lib64/libGLESv* files14:15
T4<abhishek_0> mal on a 32 bit install ?14:17
malis your device 64-bit? or completely 32-bit?14:18
T4<abhishek_0> completely 3214:18
T4<abhishek_0> [root@Sailfish nemo]# ls /var/lib/anbox/overlay/system/lib    … egl  hw  libqservice.so14:18
malso you have no /var/lib/anbox/overlay/system/lib64/ ?14:18
T4<abhishek_0> no14:18
T4<abhishek_0> any fix ?14:20
malhow about getting some logs14:22
malfor example /var/lib/anbox/data/system.log and dmesg14:23
r0kk3rzabhishek: please ask better questions14:27
T4<abhishek_0> mal dmesg
r0kk3rz'please fix my problem for me' is just lazy :P14:27
malvery much so14:28
maland extremely annoying14:28
T4<abhishek_0> and there is nothing in /var/lib/anbox/data/system.log14:28
maldid you even start the container service?14:28
T4<abhishek_0> yes i did, it didnt start dmesg
maldammit, why the hell do you paste dmesg, systemd service log to journalctl14:36
malthink a little would you14:37
T4<abhishek_0> here is the journalctl  and systemctl status is just below that14:46
malremove anbox-bridge stuff from the anbox container manager systemd service file14:48
T4<abhishek_0> removed14:52
T4<abhishek_0> and it caused a reboot14:52
T4<abhishek_0> let le grab journlactl14:53
malreboot could indicated some mistake in patching the kernel14:54
T4<abhishek_0>  i hope i did everthing right .. there were two conlicts in overlayfs patch14:55
T4<abhishek_0> which i solved manually14:56
T4<abhishek_0> anyway here namei.c … fs.h
T4<abhishek_0> i kept both15:13
malI'm not going to go through the whole patch, you need to show what exact parts had conflicts and what those were15:22
T4<abhishek_0> sorry , conflicts are marked with ===== ..15:23
T4<abhishek_0> control + F  ,,,,,, :PP15:24
T4<abhishek_0> okay ... i see .. i have a newer kernel .. and the reason vknecht and mal was able to get anbox working because they didnt had this commit
T4<abhishek_0> i should have used a older kernel15:33
malor just adapt the patch to fit15:39
vknecht@abhishek_0: I'd say you're lucky to have 3.10.108, it's probably better to adapt15:47
r0kk3rzmal: were you patching sonykernel for anbox?15:49
T4<abhishek_0> vknecht i am not cool enought for that i guess *sighs*15:50
T4<abhishek_0> *enough15:51
vknecht@abhishek_0: if I get it correctly, you'd have to use the "permission2" version, and it means keeping HEAD/above section15:53
malr0kk3rz: yes, I have x kernel patched15:53
r0kk3rz[m]mal: sweet, i should merge that then :)15:54
malr0kk3rz[m]: I never made any PR or anything15:55
malit just for my personal use15:55
r0kk3rz[m]yeah ive got my own fork anyway15:57
T4<abhishek_0> vknecht i wish it was that easy .. whole patch is based around "permission"17:20
T4<abhishek_0> like this happens
*** doniks_ is now known as doniks17:34
r0kk3rzmal: that was easy :D -
malr0kk3rz: well you could have fixed the commit messages, that's just ugly17:49
T4<abhishek_0> or what if i just reverted that "permission2" commit altogether .. and then apply patch17:56
r0kk3rzi just clicked some buttons on github :P18:03
T4<abhishek_0> lucky18:03
r0kk3rzwell its nice when all the sony devices use the same kernel18:06
opendataanyone tried the 4.9 sony kernel with sfos yet?18:07
r0kk3rzi dont think so18:07
r0kk3rzthe xa2 would use the 4.4 i should think18:08
opendataxa2 has 4.918:08
r0kk3rzyeah but jolla isnt using that for the xa2 adaptation18:10
opendatathey might but18:11
r0kk3rznot yet at least :P18:12
opendata, nah18:14
T4<abhishek_0> sledges if you are watching, then please create nemo:testing:hw:wingtech:wt88047 username abhishek965018:14
taaemr0kk3rz: how do you know what Jolla is using for the xa2?18:16
r0kk3rzthey've been recently pushing the adaptation public18:16
opendatalook at date18:17
opendataunless they started 14 days ago18:17
r0kk3rzthe adaptation will be public so im sure someone will try it18:18
taaemr0kk3rz: intersting do you have a link?18:18 :P18:19
opendatawell im getting an xa2 in 10 days, so ill try ir18:19
r0kk3rzoh cool, good luck opendata!18:19
taaemHmm I'm seeing all those android_* repose there which only hava a aosp_8.1 branch that should be Xperia XA2 right?18:20
taaemopendata: good luck!18:20
r0kk3rztaaem: yes thats it18:20
taaembut the actual adaptation repo is empty :/18:21
r0kk3rzso far18:21
taaemso this ( proves that they'll support the dual sim variant :P18:23
malh4113 is the dual-sim variant, h3113 is the single-sim18:25
r0kk3rzthey already said which devices they're targetting18:26
r0kk3rzin a meeting minutes somewhere18:26
taaemyeah but in some telegram groups was still some unclarity which version they would support18:33
taaembut this seems like they *only* target the dual sim variant? Or is it just the device they got first so they just do that first?18:34
r0kk3rzhipstergrammers not paying attention, whodathunk18:48
beidlMeowDude: breakfast fails just as much. regarding the kdbus issue: WOW, seems as if something in userspace (systemd?) falls back to the kdbus codepath, which is definitely not in the maguro kernel. try setting the DBUS_SYSTEM_BUS_ADDRESS environment variable to the appropriate dbus socket.19:10
beidlshould be either somewhere in /run or /tmp19:10
lazyguymcAnyone here?20:27
malthe proper way is to just ask the actual question you have, or describe the problem20:29
lazyguymcOk just checking20:29
lazyguymcCan I port on Windows Subsystem for Linux?20:29
malwhat do you mean by that?20:30
r0kk3rzyou can try, but i wouldnt20:30
lazyguymc Are there any errors here or did I forget to install something sofar?20:32
krnlynglazyguymc, it is not able to enter the sdk20:34
krnlynglazyguymc, i am not sure how "mount" is handled on windows, but it seems there is a problem with at least that20:35
malpretty sure it would be easier to use virtual box or something, not sure how fast that would be for building things20:35
lazyguymcso dualboot or vmware?20:38
lazyguymceh. guess its time to download kubuntu20:39
T4<abhishek_0> or arch maybe20:44
r0kk3rzkubuntu is fine20:48
lazyguymchow much ram should i give the vm?20:53
lazyguymcif i have to give it more than 4gb of ram, ill have to dual boot20:53
T4<abhishek_0> lazyguymc 4 gb is enough20:54
T4<abhishek_0> mal overlayfs conflict .. to keep or not to keep ?20:54
malyou need check if that is needed by something20:55
MeowDudeCBbeidl: where do I define DBUS_SYSTEM_BUS_ADDRESS? I tried defining it directly in /sbin/, but no dice.22:59
MeowDudeCBit's in /run/dbus/system_bus_socket22:59
MeowDudeCBofono-hack.service: Failed at step EXEC spawning /sbin/ Permission denied22:59
MeowDudeCBboop failed to set permisions22:59
MeowDudeCBHAHA! no errors23:00
MeowDudeCBso ofono-hack is online and ofono has no errors, now I am going to restart the phone and see if anything pretty happens23:04
MeowDudeCB[grilio] ERROR! Can't connect to RILD: Connection refused23:05
MeowDudeCBthe socket is where it's meant to be23:09
mallogcat -b radio might tell something23:16
MeowDudeCBmal: DBUS_SYSTEM_BUS_ADDRESS is still not being used, where do I define environment variables like these?23:19
MeowDudeCBbecause I am getting a systembus error in ofono23:19
malare you in using telnet or ssh?23:20
malnot sure, it's also very late so I'll try to get some sleep23:22
MeowDudeCBthat sucks. good night mal23:22
MeowDudeCBJun 22 08:45:48 Sailfish ofonod[5363]: Unable to hop onto D-Bus: Address does not contain a colon23:28
malwhat address did you give it?23:34
MeowDudeCB /run/dbus23:37
MeowDudeCBbut it isn't using it23:38
MeowDudeCBit's still trying to use the incorrect kdbus address in logs23:38
MeowDudeCBnow that I think about it, it's prbably because it refuses to use the address I gave it23:38
malyou gave only /run/dbus/ and not /run/dbus/system_bus_socket ?23:43
malnot sure what it should be23:43
MeowDudeCBJun 22 09:14:54 Sailfish systemd[1]: [/lib/systemd/system/ofono.service:7] Unknown lvalue 'DBUS_SYSTEM_BUS_ADDRESS' in section 'Service'23:45
MeowDudeCBmal ^^^ ha it doesn't even know what to do with it, I'll try defining it with "EXTERNAL" as reflected in journcalctl -u ofono23:46
MeowDudeCBnope same resault23:47
malhow are you trying to define that23:47
MeowDudeCBI'll try defining it-- I am defining it by doing EXTERNAL="$path" in the file23:47
malyou have something really wrong if you even have to think about dbus23:47
MeowDudeCBwell it can't connect to the right dbus address23:48
MeowDudeCBso something is wrong with it23:48
malbut you shouldn't have to think about that at all so the real issue is somewhere else23:48
malgive a link to your kernel configs and I'll have a look tomorrow23:49
MeowDudeCBall I need to do is get it to point to the right dbus address, but I don't know how to tell the computer "hey, look over HERE!"23:49
malalso get relevant logs, dmesg and journalctl, make sure those are complete, anyway I'll only check those tomorrow, it's almost 3 am23:52

Generated by 2.17.1 by Marius Gedminas - find it at!