r0kk3rz | Thaodan: looks like we can just scp it from gitlab if you have an appropriate user | 01:20 |
---|---|---|
T42 | Geekmar was added by: Geekmar | 03:38 |
Thaodan | r0kk3rz: if you want I can create one later | 04:48 |
*** moralrec1rdings is now known as moralrecordings | 05:31 | |
r0kk3rz | Thaodan: yeah i dont have much space on my server | 05:38 |
rinigus | Morning! r0kk3rz , looks like that build went through. I was planning to have a pipeline with 6 builds in parallel (all variants of tama, one per job). Do you know whether looks are for the still of artifacts or is it some runtime limitation? | 05:56 |
rinigus | Right now, I have uploaded build as a release file at https://github.com/sailfishos-sony-tama/main/releases . As it's aosp and below 2gb per file, it should be ok | 05:59 |
rinigus | As with the servers, it's frequently the bandwidth of meet connection that's a problem | 06:00 |
rinigus | Thaodan /\ | 06:00 |
Thaodan | mine in a datacenter in Germany | 06:01 |
Thaodan | it should be fine | 06:01 |
rinigus | Question is in the bill usually. You probably have some number in the contract | 06:04 |
r0kk3rz | rinigus: if its archiving ok then maybe they changed the rules since i was trying the x compact build | 06:07 |
rinigus | r0kk3rz : will have to see the generated zip. | 06:08 |
r0kk3rz | rinigus: something is definitely wrong there | 06:09 |
r0kk3rz | surely 39.5MB is not big enough | 06:09 |
r0kk3rz | a normal build is like 300 ish isnt it? | 06:09 |
Thaodan | rinigus: You mean traffic? | 06:22 |
rinigus | r0kk3rz: its usually more than 1GB. will have to look | 06:57 |
rinigus | Thaodan: yes | 06:58 |
T42 | <faenil> rinigus: thanks for the kernel configs, just as I was looking into it, yesterday 😁 | 07:19 |
rinigus | faenil: sorry, should have warned. I am right now setting it up the builds for all the variants. | 07:22 |
rinigus | configs are ready, as much as I can do without devices. | 07:22 |
rinigus | faenil: hopefully, the fun part will start when the builds are done and you could start testing. I suspect that touch device will give us a bit of a problem, as it may be different among devices | 07:23 |
r0kk3rz | you should be using udev for that anyway | 07:24 |
T42 | <faenil> rinigus: it's okay, it was helpful :) I am still going through the instructions to do the first build , plan to finish today...had some minor problems here and there | 07:24 |
rinigus | faenil: right now I have system/vendor for xz2 (dual) and xz2c(single) compiled, not uploaded to obs. as my src code contains gpt utils fixes, I'll better do all aosp compilations | 07:24 |
T42 | <faenil> What do you mean by all aosp compilations? | 07:25 |
T42 | <faenil> On obs you mean | 07:25 |
rinigus | faenil: system and vendor images for all 6 variants. | 07:26 |
T42 | <faenil> Oki | 07:26 |
rinigus | no, that's done locally. packages are uploaded to obs | 07:26 |
T42 | <faenil> Ok | 07:26 |
T42 | <faenil> A build system that doesn't build? :D | 07:27 |
rinigus | faenil: it does build the rest | 07:27 |
rinigus | fortunately, we are not going to rebuild those bits much. I hope | 07:28 |
T42 | <faenil> :D ok | 07:28 |
rinigus | r0kk3rz and Thaodan : houston we have a problem. artifacts too large. so, how can we upload it to somewhere else? | 07:31 |
Thaodan | rinigus: yes, please send me an e-mail with your public key and then I'll send you logindata later | 07:42 |
rinigus | Thaodan: thank you! I'll generate special one for gitlab | 07:43 |
deathmist | morning, how can I include https://github.com/sailfishos-oneplus5/nemo-qml-plugin-systemsettings in my builds by default? it stops my internal partitions being treated as external and after building it & adding the package to patterns, the build still uses the official version :/ | 07:46 |
rinigus | local or obs? at obs, see tama project. | 07:47 |
deathmist | just local, I haven't figured out OBS stuff on the device side even tho the project should be fine (needs to be updated for 16.0 first tho) | 07:48 |
deathmist | in fact I should probably do that today and attempt getting OTAs working (maybe test from 3.1 to 3.2, kernel subversion updates and how it affects built modules on device etc) | 07:51 |
rinigus | deathmist: didn't try that on local. but I presume you can build it as any mw | 07:52 |
r0kk3rz | rinigus: if you send me the private key, i can put it into a shared secret thing between all the CI jobs | 07:54 |
rinigus | Thaodan: would that be OK? ^ | 07:56 |
Thaodan | so that every job can use the server? | 07:57 |
Thaodan | that would be ok | 07:58 |
r0kk3rz | yes | 07:58 |
rinigus | I presume so | 07:58 |
Thaodan | just create a folder for each device | 07:58 |
rinigus | r0kk3rz: your email, please. (don't know how to start PM via matrix on irc). send email via pm | 08:00 |
Thaodan | i assume their a three type's of builds just like on obs? | 08:01 |
rinigus | Thaodan: I know testing and devel. which one is the third one. | 08:06 |
Thaodan | release? | 08:07 |
rinigus | never happens :) | 08:07 |
rinigus | I think ports always release from testing | 08:07 |
Thaodan | i think Sony's could be in release if the aosp support is good. | 08:10 |
Thaodan | but requires more manpower for more structured development | 08:11 |
rinigus | Thaodan: let's start with 2 and then see where do we get with it | 08:11 |
r0kk3rz | most devices never make it out of devel | 08:12 |
deathmist | oh right I got stuck at paccopy before when I needed to basically clone devel to testing because of some username / permission issues, will have to take another look at that after I update all the packages at least | 08:17 |
deathmist | about naming of the project(s), http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2019-11-19.log.html#t2019-11-19T07:20:55 still stands | 08:25 |
deathmist | mal: r0kk3rz: ^ any opinions about that? everything currently lives at https://build.merproject.org/project/show/nemo:devel:hw:oneplus:cheeseburger | 08:27 |
mal | Thaodan: about the [[]] vs [] in those script, the first line in those scripts defines we use bash so it there some issue using [[]] in that case | 08:57 |
Thaodan | Not issues but it's not really needed imho.I tend to use the posix syntax most of the time except when I need something like arrays or perl style regex marching | 09:00 |
Thaodan | *matching | 09:01 |
Thaodan | Also there are features that are pretty useless like the function keyword | 09:03 |
mal | Thaodan: ok, just thinking of that wildcard matching which would need [[]] or case | 09:26 |
Thaodan | yes | 09:41 |
Thaodan | i tend to use case then | 09:41 |
T42 | 龚莆婷 %lastname% was added by: 龚莆婷 %lastname% | 09:52 |
Thaodan | can we invite shieldy into the telegram side like in the main group? | 10:06 |
T42 | <birdzhang> too many spam bots | 10:09 |
T42 | sheildy_bot was added by: birdzhang | 10:09 |
Thaodan | there are also bots who spam ssh servers there are far worse in terms of numbers | 10:15 |
piggz | mal: aby idea how ive broken my target? magic_load failed: File 5.14 supports only version 10 magic files. `/usr/share/misc/magic.mgc' is version 14 | 11:54 |
piggz | when buildng rpms | 11:54 |
mal | piggz: did you update both sdk and target? | 12:31 |
abranson | and tooling! | 12:44 |
Mister_Magister | mal: u got time later today? | 12:45 |
mal | for what? | 12:48 |
mal | abranson: I have never really understood how tooling is updated | 12:48 |
mal | abranson: the sdk-assistant update does usually nothing for that, not sure how that can be used together with changing version | 12:49 |
abranson | mal: sdk-manage can do all of them | 12:49 |
Mister_Magister | mal: debugging hybris16 | 12:49 |
mal | abranson: I'm usually just lazy and remove the whole tooling and target and install again | 12:49 |
abranson | piggz: a good hint there ^ :) | 12:49 |
Mister_Magister | mal: i think i finally solved all issues with asus stupid retarded bootloader so i wanna get my asus on hybris16 to gui, i got i think all services needed but gui it not starting and user session is freezed (you cannot ssh to nemo or su to nemo) | 12:57 |
Mister_Magister | mal: so i was wondering if you have time to help me today | 12:59 |
mal | we'll see in the evening, I will be doing new fp2 release later today but that is just writing release notes etc | 13:03 |
Mister_Magister | mal: okay! i will write to you if i solve bootloader issue | 13:04 |
piggz | mal: abranson: ok | 13:19 |
deathmist | I still didn't get a response earlier today, so how should we deal with making my OBS projects for OP5/5T like https://build.merproject.org/project/show/nemo:devel:hw:oneplus:cheeseburger ? I've got a rough idea http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2019-11-19.log.html#t2019-11-19T07:20:55 | 14:16 |
deathmist | mal: r0kk3rz: ^ | 14:17 |
T42 | <nitin_3> @deathmist did you check?..were ssid showing twice in the list of wifi networks for you also? | 16:50 |
deathmist | @nitin_3 yep I did, and no I only see each SSID once | 17:01 |
deathmist | kimmoli: spiiroin: any clue why the gesture-daemon methods would seemingly trigger twice for everything? log only says "MCE signal power_button_trigger says event7" once yet the action is executed twice, here's my EV_MSC "hack" https://git.io/JeXv4 | 18:32 |
Mister_Magister | mal: u there? | 18:32 |
deathmist | my fork of gesture-daemon https://git.io/JerMg and custom MCE config for gesture handling https://git.io/JeXv0 (if those matter) | 18:33 |
mal | Mister_Magister: I was just about to go for a short walk, maybe describe the issue you have and provide logs and I'll check those after I get back in about half an hour or so | 18:38 |
Mister_Magister | mal: go for a walk i magically got gui. will try to get logs and stuff | 18:38 |
Mister_Magister | basically sfos boots but only telnet works su root or nemo freezes | 18:38 |
Mister_Magister | aand i don't have gui anymore after it rebooted itself | 18:38 |
mal | hmm | 18:38 |
mal | Mister_Magister: make sure you enable persistent journal logging so you can see why it rebooted | 18:41 |
Mister_Magister | mal: logcat is spammed | 18:41 |
Mister_Magister | https://paste.opensuse.org/87465943 | 18:41 |
mal | well that looks bad | 18:42 |
Mister_Magister | mhm | 18:42 |
mal | grab dmesg or journal so we can see how the droid-hal-init works and if any services fail | 18:42 |
Mister_Magister | oki | 18:43 |
Mister_Magister | it's quite stable now | 18:43 |
kimmoli | deathmist: couldnt find anything wrong with a quick look | 18:47 |
mal | deathmist: show what evdev_trace -t shows | 18:47 |
kimmoli | if this hits only once? https://github.com/sailfishos-oneplus5/gesture-daemon/blob/master/src/gesture-actions.cpp#L42 | 18:51 |
kimmoli | sure you don't have two instances running? | 18:51 |
Mister_Magister | mal: surfaceflinger fails with failed to create composer client but if i kill hwc i get bootanimation | 18:52 |
Mister_Magister | so test_hwc2 works now fine aswell | 18:54 |
Mister_Magister | mal: in dmesg all i can see is IPC_RTR: msm_ipc_router_bind: pm-service Do not have permissions | 18:55 |
mal | just show the whole log | 18:55 |
mal | Mister_Magister: are you sure you didn't have the usual issue of eventd*.rc not appearing in out/ | 18:56 |
Mister_Magister | mal: i put eventd there | 18:56 |
mal | ok | 18:56 |
Mister_Magister | as a confirmation all 3 servicemanagers are working | 18:57 |
Mister_Magister | hwc is working too… keymaster too… | 18:57 |
Mister_Magister | mal: i can't… it's fully spammed 11 secs after boot | 19:00 |
Mister_Magister | can't get dmesg ealier | 19:00 |
spiiroin | deathmist: I can't spot any obvious faults either | 19:06 |
T42 | <faenil> rinigus: --version build fails with unsatisfied BuildRequires, all the droid-config-*. | 19:09 |
T42 | <faenil> Any reason why the droid-configs build has --do-not-install? | 19:09 |
T42 | <faenil> Also all the droid-hal-* are missing | 19:09 |
T42 | <faenil> I wonder if the instructions are missing some install commands, or I am missing something :) | 19:15 |
mal | Mister_Magister: that is why I asked for persitent journal log, the kernel messages and droid-hal-init stuff goes there also | 19:20 |
Mister_Magister | mal: i got bit further with android devs already :) | 19:20 |
rinigus | faenil: I had akari in few instructions specified, corrected with the last commit in hadk | 19:24 |
rinigus | faenil: that droid-config will have to be fixed. | 19:25 |
deathmist | ok uuuh now the gestures just started working properly by themselves automagically? I didn't even change anything since it didn't work just moments ago ._. will do more testing... "evdev_trace -t" just gave me the MSC_GESTURE and SYN_REPORT events as expected from the changed source | 19:25 |
rinigus | I am right now building hal for xz2c single sim, should be ready soon | 19:25 |
rinigus | android is ready for it, not uploaded yet | 19:25 |
rinigus | 10-15 mins | 19:25 |
rinigus | faenil: are you trying to build it locally or get from obs? | 19:26 |
Mister_Magister | mal: okay i know how to fix it now but got problem | 19:30 |
Mister_Magister | https://github.com/mer-hybris/android_system_core/blob/hybris-15.1/init/README.md#options capabalities is not workign | 19:30 |
T42 | <faenil> rinigus: all locally. I noticed the akari commands yesterday and had a PR ready but then I saw you already committed today :D | 19:34 |
T42 | <faenil> The android build is done already | 19:34 |
rinigus | faenil: then that's good. its great if you get through as well - the more checks the better | 19:35 |
T42 | <faenil> Yeah I don't like fast food ;) | 19:35 |
rinigus | the first droid-configs are built with install. | 19:36 |
T42 | <faenil> Just noticed that the boot img failed to build, there's a conflict between busybox-symlinks-cpio and the cpio BuildRequire'd by the boot img spec | 19:36 |
T42 | <faenil> I'll have a look later, dinner time o/ | 19:36 |
T42 | <faenil> Yeah noticed that :/ | 19:36 |
rinigus | see https://github.com/sailfishos-sony-tama/main/blob/master/hadk-sony-xz2.md#build-packages | 19:36 |
rinigus | enjoy! | 19:37 |
T42 | <faenil> Yeah I ran those commands again just to be sure... | 19:37 |
Mister_Magister | rinigus: do you have something to drink? we got something to celebrate | 19:37 |
T42 | <faenil> And then as I building boot img again I noticed the cpio conflict | 19:37 |
T42 | <faenil> Bbl | 19:37 |
rinigus | Mister_Magister: not tonight, unfortunately. but I am listening... | 19:38 |
Mister_Magister | sec lemme write tweet | 19:38 |
Mister_Magister | rinigus: mal: https://twitter.com/Mister1Magister/status/1199412334353145856 | 19:39 |
rinigus | Mister_Magister: congratulations! | 19:42 |
T42 | <faenil> Congrats! | 19:42 |
Mister_Magister | rinigus: thanks! i went through hell to get it | 19:42 |
Mister_Magister | wifi is working ootb xd | 19:44 |
Mister_Magister | now time to write notch support | 19:45 |
rinigus | I can see that. even started chewing on one side of the screen and now you will miss the time on status bar | 19:45 |
T42 | <nitin_3> wow..congrats...it also has sdm845 right? | 19:45 |
Mister_Magister | rinigus: yeah i will write support | 19:45 |
Mister_Magister | @nitin_3 hell yeah it is | 19:45 |
Mister_Magister | i wanted to be first but i ain't first anymore | 19:45 |
Mister_Magister | only because asus | 19:45 |
T42 | <nitin_3> why..what happend | 19:46 |
Mister_Magister | @nitin_3 adding android and spl version to bootimg with buildv property was causing my bootloader to freeze and since i didn't have working bootctl i ran out of tries and bricked my device so i had to remove back glass in order to short pins to get it to edl and then flash bootimage to get bootloader working again and after it all i learned that lineage devs added buildv property to kernel cmdline ONLY to fix Error value on | 19:49 |
Mister_Magister | bootloader screen and that buildv property was causing bootloader to freeze! | 19:49 |
Mister_Magister | WHY ASUS DO YOU READ PROPERTY FROM KERNEL CMDLINE JUST WHY AND WHY YOU FREEZE | 19:49 |
Mister_Magister | ah i forgot to add i have to add android and spl version just because asus devs were too lazy to remove this requirement (as google removed it) | 19:50 |
Mister_Magister | so annoying | 19:50 |
Mister_Magister | writting about it is short but actually fixing it… | 19:51 |
T42 | <nitin_3> do you think it is intentional? | 19:57 |
T42 | <nitin_3> ^was | 19:57 |
Mister_Magister | nah other guys on other vendors had same lame lazy vendors | 19:58 |
Mister_Magister | but asus bootloader is snowflake | 19:58 |
mal | Mister_Magister: nice that you got UI working now, do logs look better now? | 20:18 |
Mister_Magister | yeah but i will explain it to you how i fixed it | 20:18 |
Mister_Magister | mal: i need to add capabilities NET_BIND_SERVICE to pm-service but it didn't work so i just disabled checking for permissions in kernel. so i just need to fix capabilities NET_BIND_SERVICE and it will work fine | 20:19 |
rinigus | faenil: I corrected the command in hadk for config build, in root fs section | 20:27 |
rinigus | faenil: mountpoints are the same for akari and apollo - https://github.com/mer-hybris/hybris-boot/pull/179 | 20:29 |
T42 | <faenil> rinigus: yeah I already defaulted to using the same mountpoints :) haven't even unlocked my device yet, so haven't checked on aosp | 20:35 |
rinigus | faenil: just uploaded hal and system/vendor for apollo single sim. as soon as system/vendor rpms are prepared by obs, droid-hal-version-h8314 should be resolvable (in devel https://build.merproject.org/project/monitor/nemo:devel:hw:sony:tama) | 20:36 |
rinigus | faenil: do you have single or dual sim? | 20:37 |
T42 | <faenil> Cool. I need to get it done locally though :P or I won't enjoy/learn | 20:37 |
T42 | <faenil> Single | 20:37 |
T42 | <faenil> I don't think the configs spec was the problem, it was building all packages already :/ | 20:38 |
T42 | <faenil> I think the cpio conflict is the problem atm, I'll fix that first | 20:38 |
rinigus | faenil: that special feeling when you baked it yourself... | 20:38 |
T42 | <faenil> :D more about learning, but yeah | 20:39 |
rinigus | faenil: it maybe was building too many. try with that command | 20:39 |
T42 | <faenil> No no, it built all of them. | 20:40 |
T42 | <faenil> I tried with the new cmd, no difference | 20:40 |
T42 | <faenil> I think it's just that it doesn't find the boot-img package (which is not building due to cpio) and the missing droid-config is just a false positive due to the missing boot img pkg | 20:41 |
rinigus | faenil: not sure I understand where the issue is. pastebin some logs ? | 20:42 |
rinigus | but config was built before boot-image. did you remember to run sb2 command before boot image? | 20:42 |
T42 | <faenil> The failure is not in config, it's in boot-img and version | 20:43 |
T42 | <faenil> I'm writing from the phone, it's faster if I just fix it and then write here :) | 20:44 |
rinigus | faenil: sure! good luck | 20:46 |
T42 | <faenil> Cheers | 20:48 |
mal | Mister_Magister: quite strange issue | 20:48 |
Mister_Magister | this whole device is strange | 20:49 |
T42 | <faenil> Rinigus: boot-img build fixed by manually installing cpio in the sb2 target and manually resolving the installation conflict (I chose to remove busybox-symlinks-cpio, replacing it with cpio) | 20:50 |
rinigus | nice! | 20:51 |
T42 | <faenil> Back to version now, still complaining about missing providers for all the droid-hal-* and droid-config-* | 20:52 |
vknecht | in case different tama models have different partitions layout, overriding flash-partition to use MER_HA_DEVICE could be useful, like here for loire https://github.com/vknecht/droid-config-sony-loire/commit/f8ac0dfc5deafd2dad8ff24c4a2edd91b0a2c4d1 | 21:04 |
vknecht | also restore /dev/touchscreen, to support different /dev/input/eventX depending on model: https://github.com/vknecht/droid-config-sony-loire/commit/e76ddd126ccf807ff4bc3c534b736dcb573b62d7 | 21:05 |
T42 | <faenil> rinigus: mmm I see droid-configs.inc provides droid-config-%{rpm_device} but also conflicts with bluez5. Both are build deps of the -version pkg though | 21:07 |
T42 | <faenil> is that expected? | 21:07 |
rinigus | vknecht: let's see. I hope we don't need it | 21:07 |
rinigus | faenil: strange, you should have those in local repo | 21:07 |
T42 | <faenil> I am just reading the .spec | 21:07 |
rinigus | vknecht: touchscreen I may need. xz2c maybe different | 21:09 |
T42 | <faenil> rinigus: built —configs for the 3rd time...after that —version built successfully... I am confused. —configs succeeded in the past already | 21:11 |
T42 | <faenil> unless the script is not reporting a silent failure | 21:11 |
vknecht | restoring /dev/touchscreen was kind of easiest/laziest, maybe cleaner to have per-device sparse/var/lib/environment/compositor/droid-hal-device-....conf | 21:12 |
rinigus | faenil: good that it did. | 21:12 |
T42 | <faenil> yeah, I guess I'll just assume I did something wrong twice | 21:12 |
rinigus | vknecht: I was told that xz2c has different batches with different touchscreens | 21:13 |
rinigus | don't know if its different event dev | 21:13 |
T42 | <faenil> and now again, can't find jolla-configuration-h8314 ... argh :) | 21:14 |
vknecht | at least for X vs. Xcompact, it was a different one ; also,maybe tama isn't only "clearpad" driver, at least both suzu and kugo are (fwik) | 21:15 |
rinigus | faenil: that jolla-configuration- is built using do-not-install variant of config. do you have it as a package in local repo? | 21:17 |
T42 | <faenil> tried building the rootfs twice, once failed with jolla-conf-$device not found, then with droid-config-$device-bluez5 not found (needed by jolla-conf-$device). | 21:18 |
T42 | <faenil> oh well | 21:18 |
T42 | <faenil> rinigus: second time it was missing bluez5 droid config | 21:18 |
rinigus | faenil: I am off to sleep. you could also cheat by pulling KS from http://repo.merproject.org/obs/nemo:/devel:/hw:/sony:/tama/sailfish_latest_armv7hl/armv7hl/droid-config-h8314-ssu-kickstarts-0.2.0+master.20191124153518.1.g61a77f1-1.2.1.jolla.armv7hl.rpm | 21:19 |
T42 | <faenil> so it seems like during the second run it could find jolla-conf (how? it couldn't find it on the first run...) but it failed to install it | 21:19 |
T42 | <faenil> rinigus: no worries, I'll play with it and get it fixed :) have a good night! | 21:19 |
T42 | <faenil> rinigus: if you're still around, just one thing, what is supposed to build droid-config-$device-bluez5? I can't find any provider for it in .specs | 21:23 |
T42 | <faenil> found, nvm | 21:26 |
TheKit | can I ask for planet-cosmocom on OBS? | 21:45 |
r0kk3rz | TheKit: thats the codename? | 22:17 |
r0kk3rz | or planet:cosmocom ? | 22:17 |
TheKit | planet:cosmocom | 22:17 |
r0kk3rz | ok | 22:18 |
r0kk3rz | https://build.sailfishos.org/project/show/nemo:devel:hw:planet:cosmocom | 22:23 |
TheKit | r0kk3rz, thank you | 22:29 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!