| deathmist_ | Umeaboy: 17.1 is cutting edge in hybris currently, 18.1 based adaptations aren't possible yet. also have you even tried to build without the patches? they're mandatory for 16.0+ | 00:06 |
|---|---|---|
| Umeaboy | deathmist_, That's why I asked if they're mandatory. | 00:07 |
| mal | Umeaboy: it is, check the PR in faq repo | 00:09 |
| mal | I mean for hybris-17.1 things | 00:09 |
| deathmist_ | oh, I never %define android_version_major 10 to https://github.com/sailfishos-oneplus5/droid-config-cheeseburger/blob/hybris-17.1/rpm/droid-config-dumpling.spec as no one mentioned it anywhere back then, welp that was probably why it was always broken for me then | 00:12 |
| Umeaboy | mal: hybris-16.0 and hybris-17.1 have the same structure? | 00:12 |
| deathmist_ | I'll take a crack at it later I suppose; the space requirements for hybris-17.1 are insane though | 00:12 |
| Umeaboy | OK. I have to change my spec then, deathmist_ | 00:12 |
| deathmist_ | Umeaboy: https://github.com/mer-hybris/hadk-faq/pull/8/files as per mal's earlier message | 00:13 |
| rinigus | piggz: version release component is kept in one of the files in build. Didn't know about such jolla store limitation | 03:35 |
| mighty17 | <T42 "<elros34> @mighty17 you are miss"> Oh right derp xD, now to figure out how to get wifi working, usb internet doesn't work as well :( | 04:31 |
| rinigus | piggz: I will add an option to disable release mangling for a project. Sounds like it will make sense for store projects | 04:43 |
| T42 | <Zainal %lastname%> Any info porting sailfish 4 for oneplus X ? Thanks | 05:34 |
| mighty17 | Use the hadk guide for porting :D | 06:03 |
| piggz_ | rinigus: does tbuilder do the mb2 prepare step? | 08:45 |
| rinigus | piggz_: it should be done by mb2 automatically if you don't use shadow builds. if I remember it right | 10:07 |
| rinigus | but I can check the sources tonight | 10:08 |
| T42 | <adampigg> Rinigus,.might try and build xulrunner as a stress test! | 10:21 |
| rinigus | @adampigg: but have you seen that prep step was not applied? | 10:25 |
| T42 | <adampigg> No, just wondering | 10:54 |
| rinigus | @adampigg: let me know how it goes | 11:04 |
| rinigus | just checked - if not shadow build then `-p` is added to `mb2` command. so, should be fine | 11:08 |
| rinigus | @adampigg ^ | 11:08 |
| *** Nico[m] is now known as Nico-old-defunct | 12:15 | |
| mighty17 | hello, i need some help for sfos my device has broadcom bluetooth and acc to hadk-faq i need to do something like this commit https://github.com/mer-hybris/droid-config-f5121/commit/afa01bdf4bdb8a0d16bbd34996ec7cac34bbbc55 but mine is bcm4330 and the commit has bcm4345c0 with `bcm4345c0.conf` but bcm4330 doesnt have a `bcm4330.conf` file so what am i supposed to do | 13:05 |
| calebccff | I wonder why the FaQ isn't just a github wiki, those allow anyone to edit... Rather than the PR process which is poorly suited to documentation | 13:06 |
| poetaster | that's a good question. I had elaborate help that clarified what was only anecdotal in the FAQ | 13:07 |
| mighty17 | calebccff: are u caleb? the op6 caleb? | 13:08 |
| calebccff | mighty17: Yeah that's me :> | 13:08 |
| mighty17 | you are everywhere xD | 13:08 |
| calebccff | SFOS is where I started aha | 13:09 |
| mighty17 | oh thats cool! | 13:09 |
| mighty17 | well the hadk-faq just says `add configs: https://github.com/mer-hybris/droid-config-f5121/commit/afa01bdf4bdb8a0d16bbd34996ec7cac34bbbc55` i mean thats very vague and i have no clue on what to do for that :/ | 13:15 |
| mighty17 | @edp_17 it seems our devices share same module bcm4330 mind sharing how did you do it xD | 13:18 |
| poetaster | I'v joined #sailfishos and -porter on libera.chat and posted to the forum. | 14:17 |
| poetaster | for those who haven't heard yet. https://www.kline.sh/ | 14:18 |
| T42 | hungarianboi was added by: hungarianboi | 14:48 |
| mighty17 | <poetaster "I'v joined #sailfishos and -port"> Well I'm on matrix do I need to change? | 14:59 |
| poetaster | @mighty17, I'm just being proactive. but I'm not going to stick to freenode long. | 15:03 |
| mighty17 | Yeah that is a serious issue about freenode, thanks for raising awareness | 15:07 |
| mighty17 | I found it here didn't know about that | 15:07 |
| poetaster | I know that none of us has time for this but I started a thread: https://forum.sailfishos.org/t/freenode-hostile-takeover/6388/4 | 15:08 |
| T42 | <adampigg> maybe get mal to move onto telegram :D | 15:10 |
| mal | @adampigg :) | 15:13 |
| T42 | <adampigg> https://blog.bofh.it/debian/id_461 | 15:14 |
| mal | @adampigg still relevant https://xkcd.com/1782/ | 15:16 |
| T42 | <adampigg> yup :) | 15:17 |
| rinigus | ohhh, it is damn tempting to ping those T 4 2 | 15:19 |
| mal | some channels have been moving to oftc | 15:21 |
| rinigus | if/when we move, please make sure that there is matrix bridge | 15:23 |
| mal | rinigus: oftc has a matrix bridge at least, not sure abotu libera | 15:24 |
| rinigus | let me check | 15:24 |
| rinigus | no good hits yet; didn't find in their web either. probably too new, but I guess that will come as well | 15:27 |
| poetaster | @adampigg you might be onto something. it's war at libera riht now. the freenode bots are spamming. | 15:27 |
| poetaster | adam, I'm already running bridges between irc/xmpp/matrix and mattermost so. ... telegram? | 15:28 |
| poetaster | https://libera.chat | 15:29 |
| poetaster | Ok. so maybe I'll : set up a matrix server with an irc bridge for us. | 15:30 |
| poetaster | load average: 0.02 0.02 0.02 | 15:31 |
| T42 | <adampigg> its probably not wise to just jump into something immediately, best to get a decent community consensus over the following week or so ? | 15:33 |
| Mister_Magister | @adampigg sfos meeting would do i think | 15:35 |
| T42 | <adampigg> yup | 15:36 |
| poetaster | @adampigg ... a hostile power has my personal data... I don't know about waiting for consensus | 15:37 |
| poetaster | Ok, then I'll go dark till the powers that be decide to do nothing. | 15:37 |
| poetaster | they (freenode which is no longer freenode) are being vERY hostile | 15:38 |
| poetaster | ah, wait, maybe a great firewall has risen. | 15:39 |
| mal | there is the sailfish community meeting tomorrow so maybe that is a good place to talk | 15:42 |
| T42 | <adampigg> mal: can we get you on slack? :D | 15:42 |
| T42 | <adampigg> or, ms teams?? | 15:42 |
| poetaster | 9 AM tomorrow? I have homeschooling. sigh. | 15:44 |
| poetaster | it's too late for tomorrows meeting (well, at least 3 days before meeting is in bold). | 15:49 |
| mal | well there is the free discussion part of it | 15:49 |
| poetaster | ah, that's true. damn. I'm just sick and tired of plunking my child in front of a screen. | 15:53 |
| poetaster | sigh. thank god he's playing outside. | 15:53 |
| *** Keij0_ is now known as Keij0 | 15:58 | |
| poetaster | nico (kuroNeko) put it on the agenda | 16:11 |
| Nico-old-defunct | I need to register a new nick for the meeting... | 16:14 |
| poetaster | oh, damn. I just changed my pw and mail. | 16:20 |
| poetaster | too late anyway. sigh. | 16:20 |
| poetaster | bib | 16:20 |
| pketo | sure the topic can be discussed in tomorrows meeting even though it didn't meet the 3 days deadline | 16:35 |
| Nico-old-defunct | There may not be an official answer tomorrow, but since there are no other topics anyway, I'm pretty sure it would have been discussed in any case | 16:37 |
| pketo | it's not a hard deadline, "Please _try_ and have your topics ready at least 3 days before the meeting" | 16:37 |
| pketo | yep | 16:37 |
| rinigus | piggz_: I have added an option to tbuilder allowing you to keep release as is in spec. see README and example config.yaml under "project" subfolder of tbuilder | 19:06 |
| piggz | rinigus: i also thought of another nice-to-have... | 19:23 |
| piggz | the option of appending the build target in the name/version? | 19:23 |
| rinigus | piggz: not sure. usually we have separate repos for different targets. that allows users to switch between SFOS versions and get them linked with the correct repo. | 19:25 |
| rinigus | if you have target in the name, amazfish-sfos-4.0.1 will disappear when you switch to 4.1 | 19:25 |
| piggz | rinigus: which is what i need ... both amazfish and advanced-camera break between 4.0 and 4.1 :) | 19:26 |
| piggz | i need to host multiple versions, but dont have a way to do that atm | 19:26 |
| rinigus | separate repositories? | 19:27 |
| piggz | becuase 4.1 isnt obs, and all the ea users are piping up | 19:27 |
| piggz | rinigus: yeah, just a temprary priblem | 19:27 |
| rinigus | piggz: not sure how temporary it is | 19:27 |
| piggz | rinigus: is that implying something? | 19:28 |
| piggz | ie, 4.1 may not be on obs? | 19:28 |
| piggz | actually, it will be a double pain, as aarch64 doesnt work anyway | 19:29 |
| rinigus | no, just observation that it is with every release these days. | 19:29 |
| piggz | and already somone released an advanced-cam 64bit version ahead of me ... tho, without the 4.1 patches | 19:29 |
| rinigus | would be nice to have separate some place where packages for different sfos versions can be pushed. openrepos, ideally | 19:29 |
| rinigus | for port, I can put repos into the cloud and just config to get them from there. for apps, not so nice | 19:30 |
| piggz | i could hack it on openrepos iwth seperate user accounts :D | 19:30 |
| piggz | but that would become unmanagemable very quickly! | 19:31 |
| rinigus | exactly. | 19:32 |
| mal | rinigus: about your tama actdead issue, the log suggests charger state is unknown or off and triggers reboot | 19:38 |
| rinigus | piggz: ideally, we need something where we can push whole repos. and which users can easily find and configure | 19:39 |
| rinigus | mal: thanks for looking into it! | 19:39 |
| piggz | rinigus: umm, like obs? :D | 19:39 |
| rinigus | :) | 19:39 |
| mal | rinigus: that line "DSME[2720]: state: Actdead (charger: off(?), alarm: not set)" | 19:39 |
| rinigus | mal: before forcing reboot with actdead, I usually unplug the charger. let me try without unplugging and see if the same line will be there | 19:41 |
| mal | rinigus: also the usb audio issue, remember to make the udev rule for ignoring built-in audio card if you enable module-udev-detect in pulseaudio | 19:41 |
| mal | rinigus: I though the log meant it automatically rebooted? | 19:42 |
| rinigus | mal: it did at least once. but that was when I plugged to PC port. (although, not sure it was relevant). frequently it is stuck with lid black screen | 19:43 |
| mal | rinigus: do you have this https://github.com/mer-hybris/droid-config-sony-seine/pull/18/files | 19:43 |
| rinigus | mal: yes, I do | 19:43 |
| piggz | rinigus: did you have the hadk somewhere in text format? | 19:45 |
| rinigus | piggz: https://github.com/sailfishos-sony-tama/main/blob/hybris-10/hadk-sony-xz2.md | 19:49 |
| rinigus | that's for aosp10 based and using tbuilder | 19:50 |
| rinigus | mal: this time it was hanging on lid screen. log at https://dpaste.org/Ah0a | 20:00 |
| rinigus | DSME later found the charger - DSME[2648]: state: Actdead (charger: on, alarm: not set) | 20:00 |
| rinigus | again, had to force reboot | 20:01 |
| mal | rinigus: is that the whole log? | 20:14 |
| piggz | mal: starting a fresh port, how to you minimise a full lineage 17.1 repo? | 20:41 |
| mal | piggz: what do you mean? the hybris-17.1 is somewhat minimized already | 20:44 |
| piggz | mal: oh, i was talking about the los android.git .. i couldnt see a hybris-17.1 | 20:45 |
| piggz | mal: my bad ... it was in the stale list! | 20:46 |
| piggz | mal: python version error? | 20:49 |
| piggz | File "/parentroot/parentroot/data/piggz/mer/android/droid.gs290/.repo/repo/main.py", line 79 | 20:49 |
| piggz | file=sys.stderr) | 20:49 |
| piggz | ^ | 20:49 |
| piggz | SyntaxError: invalid syntax | 20:49 |
| piggz | this should help https://forum.developer.parrot.com/t/olympe-repo-wont-link/12608 | 20:50 |
| piggz | mal: does the ubuntu trusty rootfs have python 3.6, which is required for repo? | 20:54 |
| T42 | <ruspartisan> Last time I checked, chroot had very old Ubuntu (14.04 afair) that was too old for python required for repo | 20:55 |
| piggz | yeah, im adding a ppa | 20:56 |
| mal | piggz: I think it has if you install it manually | 21:20 |
| mal | piggz: was it 3.5 or 3.6 in there | 21:20 |
| piggz | mal: it has 3.5, but 3.6 is required | 21:20 |
| piggz | googling shows approprate ppa | 21:20 |
| mal | piggz: hmm, I thought the 3.5 is the hard minimum requirement for repo, 3.6 is the soft requirement | 21:26 |
| T42 | <b100dian> mal: got minimer working! The composer stack corruption was because system overlaying of droid-hybris/system (mixing libs) | 21:27 |
| mal | @b100dian ok, good | 21:28 |
| piggz | mal: | 21:28 |
| piggz | ABUILD_SDK [GS290] piggz@linux-f1uu:/mer/android/droid.gs290$ repo init -u git://github.com/mer-hybris/android.git -b hybris-17.1 | 21:28 |
| piggz | repo: warning: your Python 3 version is no longer supported; Please upgrade to Python 3.6+. | 21:28 |
| mal | piggz: yes, but it doesn't exit at that point afaik https://gerrit.googlesource.com/git-repo/+/refs/heads/main/main.py#87 | 21:29 |
| mal | piggz: older than 3.5 will cause exit | 21:29 |
| piggz | mal: https://paste.mozilla.org/ETP7B5Kj | 21:30 |
| deathmist_ | piggz: I've started building droid HAL on my host since that issue appeared, I know it can be fixed but doing it on host is also slightly faster for me | 21:30 |
| mal | I have built all newer android bases directly in ubuntu 20.04 (and 18.04 before that) for a long time | 21:31 |
| piggz | deathmist_: yeah, i imagine it may be faster ... my host is opensuse tho, nothing like a ubuntou setup | 21:31 |
| mal | piggz: so the requirements seem wrong then | 21:31 |
| mal | piggz: run repo on host, everything in HABUILD | 21:32 |
| mal | *everything else | 21:32 |
| piggz | yeah, that would work too | 21:32 |
| piggz | but, i now have python3.6 in habuild anyway | 21:32 |
| Umeaboy | I have tried to pull my device vendor blobs, but fail to do so. I did extract the vendor.img and mounted the image as rw to a random folder and the extract-files.sh couldn't find the majority of the files even though I used the right zip described in the device.mk file for Lineage. Need help. | 22:26 |
| Umeaboy | Please. | 22:26 |
| Umeaboy | I extracted the vendor.img.lz4 and ran lz4 -d vendor.img.lz4 vendor.img and then I ran simg2img vendor.img vendor_unpacked.img and that went fine. I then mounted the vendor_unpacked.img to a random folder that I created and that went fine. I even remounted the folder as rw. | 22:28 |
| Umeaboy | There must be some step I'm missing. | 22:28 |
| Umeaboy | Here's the result: https://ghostbin.co/paste/5kjey7 | 22:28 |
| T42 | <b100dian> I think extracting vendor files is for creating your own image. I am using the one on device for example, not customized | 22:42 |
| Umeaboy | I think I made a boo boo. | 22:42 |
| Umeaboy | I have to follow this page: https://wiki.lineageos.org/extracting_blobs_from_zips.html | 22:42 |
| mal | Umeaboy: what device is that? | 22:44 |
| Umeaboy | mal: The beyond2lte. I realized that I did the wrong thing when I tried to pull the blobs. | 22:45 |
| mal | what vendor? | 22:45 |
| Umeaboy | Samsung. | 22:45 |
| Umeaboy | And now it found the blobs. :( | 22:47 |
| Umeaboy | :) | 22:47 |
| Umeaboy | So no harm, no foul. :) | 22:47 |
| T42 | <b100dian> " droid-hal-init: Could not find 'android.hardware.graphics.composer@2.1::IComposer/default' for ctl.interface_start" | 22:52 |
| T42 | <b100dian> I don't have the 2.1 rc file on my device, only the 2.3 file | 22:52 |
| T42 | <b100dian> Do you know where is 2.1 referenced from? | 22:53 |
| Umeaboy | b100dian: A previous update zip perhaps? | 22:56 |
| T42 | <b100dian> a couple of seconds above it says `droid-hal-init: Parsing file /vendor/etc/init/android.hardware.graphics.composer@2.3-service.rc.` | 23:10 |
| T42 | <b100dian> Umeaboy: what update.zip? | 23:10 |
| Umeaboy | b100dian: Which Lineage base and what vendor? | 23:11 |
| T42 | <b100dian> 17.1, xiaomi | 23:12 |
| Umeaboy | b100dian: Which modelname? | 23:16 |
| T42 | <b100dian> tucana | 23:16 |
| Umeaboy | b100dian: What the build date on your current running Lineage system? | 23:19 |
| Umeaboy | 20200907 ? | 23:19 |
| Umeaboy | Settings -> About phone | 23:20 |
| T42 | <b100dian> Hmm I just build it yesterday I think, The vendor has ro.vendor.build.date=Sun Oct 25 22:15:30 CST 2020 | 23:21 |
| T42 | <b100dian> *built | 23:21 |
| Umeaboy | OK. | 23:23 |
| Umeaboy | Check if you can find it here: https://github.com/TryHardDood/mi-vendor-updater/releases/download/tucana_id_global-stable/fw-vendor_tucana_miui_TUCANAIDGlobal_V12.0.2.0.QFDIDXM_3f5daf06f7_10.0.zip | 23:25 |
| Umeaboy | Look here otherwise: https://xiaomifirmwareupdater.com/vendor/ | 23:27 |
| Umeaboy | Any of the previous zips. | 23:27 |
| T42 | <b100dian> Oh, you mean I _should_ have a 2.1 service | 23:29 |
| T42 | <b100dian> I'll be looking, thanks | 23:29 |
| T42 | <b100dian> I'll try to define it first to point to the 2.3 one:) | 23:30 |
| T42 | <b100dian> but the question is how to determine which file was parsed that init jumped to the conclusion that it should start it in the version 2.1 | 23:30 |
| Umeaboy | Ask the person that made the device repo. | 23:31 |
| Umeaboy | :) | 23:31 |
| Umeaboy | And the vendor repo of course. | 23:31 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!