| T42 | <birdzhang> Can you use gitlab ci build 3.2.0.12? Error <creator>[11/16 06:02:36] : Command 'modprobe' is not available. | 02:49 |
|---|---|---|
| T42 | <birdzhang> ^^ https://gitlab.com/sailfishos-porters-ci/vince-ci/-/jobs/352637909 | 02:49 |
| T42 | <birdzhang> local build is okay | 02:49 |
| mal | @adampigg I removed some useless packages, which have same versions in 3.2.0 already, from the main dontbeevil OBS project | 06:51 |
| *** birdzhang1 is now known as birdzhang | 08:01 | |
| deathmist | morning, should I switch to memless haptics on 16.0? droid vibrator worked fine on 15.1, but after rebase it only works properly on some boots, and on others it doesn't work at all in pulley menus or home screen (but e.g. keyboard taps still vibrate), very strange behavior | 08:21 |
| r0kk3rz | use native plugin | 08:22 |
| deathmist | r0kk3rz: I think I'm actually using it, probably got the names mixed up https://git.io/JeoDk | 08:23 |
| r0kk3rz | yeah i dont think we really use the hybris one anymore | 08:24 |
| r0kk3rz | sounds like you need a cuatom config though | 08:24 |
| rinigus | morning! as obs is setup and can be used to make working images, I am ready to discuss naming and organization for repos for xz2 and tama platform | 08:28 |
| rinigus | currently, hadk conventions and same naming as for xperia 10 are used. as a result, kickstart files are generated correctly. | 08:28 |
| rinigus | in addition to h8216 project, there is a sub-project containing system and vendor. that is separate allowing to have repos according to android base | 08:28 |
| rinigus | as a recap, tama platform is for xz2, xz2c, xz3. I presume all of them have 1 and 2 sim variants. total - 6 device codes | 08:28 |
| rinigus | from looking into packages in h8216, there aren't many which would not depend on libhybris/droid-hal. so, I am not sure I can organize it somehow differently without using separate projects for each of the devices | 08:28 |
| rinigus | we can have tama project and move there boot image helpers and have tama:extras with system and vendor images. | 08:28 |
| rinigus | I can also make main packages in tama and have each device mirror it (somehow?), but build separately. | 08:29 |
| rinigus | mal ^ | 08:29 |
| r0kk3rz | typically the ones we build at all dependent on hybris | 08:34 |
| mal | deathmist: looks like your droidmedia is a bit behind, you should rebuild it, at least based on OBS https://build.merproject.org/project/show/nemo:devel:hw:oneplus:cheeseburger | 08:48 |
| deathmist | mal: ah yeah, they aren't even updated to 16.0 yet since I want it to at least function properly with cellular data etc so it's usable :p I just do local builds with latest upstream versions myself | 08:49 |
| mal | ok | 08:49 |
| mal | what was the problem with cellular data? | 08:49 |
| deathmist | mal: http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2019-11-10.log.html#t2019-11-10T09:24:21 | 08:50 |
| mal | deathmist: that link to your logs in there has expired | 08:51 |
| deathmist | alright, I'll grab a fresh journal at least after toggling cellular data again in a sec | 08:52 |
| mal | deathmist: also get logcat and logcat -b radio | 08:54 |
| deathmist | the libexec logcat or one from /system? | 08:55 |
| mal | libexec | 08:55 |
| deathmist | mal: uh, I get absolutely nothing with "locat -b radio" even with /system/bin/logcat :/ here's journal https://pastebin.com/jr4YgnTe and full libexec logcat https://pastebin.com/iJ8Z233Z | 09:01 |
| T42 | <adampigg> Mal, thx...also, take a look at the 2 bt packages on latte, i thibk they could be common candidates | 09:15 |
| mal | @adampigg any reason you haven't done a pull request of that broadcom-bluetooth change to mer-hybris? although we might need to consider having two spec files, that is used on tablet | 09:20 |
| T42 | <adampigg> Mal, forgetfulness :) | 09:20 |
| mal | so just make a PR with a new spec with name broadcom-bluetooth-bluez5.spec and it should be fine | 09:21 |
| mal | that won't break tablet | 09:21 |
| mal | after that we can add it to common probably | 09:22 |
| mal | although those are rarely needed on other device probably | 09:22 |
| mal | most new devices use bluebinder | 09:23 |
| rinigus | in context of https://wiki.merproject.org/wiki/Adaptations/libhybris, what's a difference between haptics and vibra? | 10:38 |
| mal | rinigus: I think maybe like vkbd vibra vs notification stuff etc, those come via different middleware | 11:10 |
| entil | hiyall! anyone know if there's work on fairphone3? | 11:19 |
| entil | my fp2 is severely breaking down, the modem's gone missing again, and I think I'm done with that hardware and it's time to consider something else | 11:20 |
| entil | ethically I'd love sticking to fairphone but if it doesn't exist it can't be helped | 11:20 |
| rinigus | mal: thanks. Looks like the both are working for me | 11:23 |
| mal | rinigus: usually both of those are working if one is | 11:24 |
| mal | just for reference those are ngfd-plugin-native-vibrator and qt5-feedback-haptics-native-vibrator | 11:25 |
| rinigus | mal: thanks, good to know. | 11:28 |
| rinigus | Any thoughts regarding sony tama repos? | 11:29 |
| mal | rinigus: well there are options how to handle those, how similar are those? those could either be all in tama repo as those still use same android base and probably would be so similar libhybris and things would work on all | 11:34 |
| mal | or have a common repo for some stuff | 11:35 |
| rinigus | mal: I don't know how similar are android bases. I expect they are, but there are still separate options you choose for `launch` | 11:35 |
| rinigus | surely some common stuff can be put together. | 11:36 |
| rinigus | also probably the same versions of packages will be used for all. so, maybe I should branch packages at obs | 11:36 |
| mal | rinigus: of course you need separate droid-* packages for those but those packages can all be in same repo if needed | 11:37 |
| rinigus | but apart from that, it looks like separate builds still. I wonder how xperia 10 or xa2 is organized in jolla's internal obs. I presume this is something similar | 11:37 |
| rinigus | mal: droid-hal indeed. not droidmedia, at least without changing the names | 11:38 |
| mal | rinigus: droidmedia only cares about the API stuff | 11:39 |
| mal | which is most likely the same as those use same hybris branch | 11:40 |
| deathmist | mal: is libhybris/porters in merproject wiki still even used? I could add OP5/5T there as I finally also added them to the adaptations index today too :p | 11:40 |
| mal | deathmist: not all people add things there, you can add if you want, it's always nice to have info there | 11:40 |
| rinigus | mal: from development speed pov, it still makes sense to have droid-hal- packages separate. as it will trigger rebuilds only for the ones that are dependent. if I change only one package | 11:41 |
| rinigus | re droidmedia: good to know, then I can move that to tama | 11:42 |
| rinigus | I presume that audioflingerglue is the same | 11:42 |
| rinigus | mal: so, in my understanding: all that is independent from droid-hal- can go to unified repo - :sony:tama, this includes droidmedia and audioflingerglue and packages depending on them, if any | 11:45 |
| rinigus | the rest will go into device specific ones. android system and vendor would be under :sony:tama:extra-images in testing | 11:45 |
| mal | maybe it's easier to have separate project for each set of devices which can use the same droid-hal packages | 11:47 |
| rinigus | mal: what would be set then? All 6? | 11:48 |
| mal | rinigus: well actually you could have all in same project and just use one (via project config) for building libhybris and stuff | 11:49 |
| mal | because the base is so similar that way libhybris would work for all even if you just build it against one | 11:50 |
| rinigus | mal: let me think about it... | 11:52 |
| mal | that's how it's done for nile and ganges | 11:57 |
| deathmist | mal: so I was looking thru my journal for HWC version to fill in, I assume it's 2.1? https://pastebin.com/bSMHyEH6 also about RIL, version should be latest mentioned on the comment in ril.h (15 in my case) here https://pastebin.com/eCwjQ9V4 or should I find it on the running device somehow? | 12:05 |
| mal | deathmist: that is usually available in logcat -b radio which for some reason didn't work for you | 12:11 |
| mal | I mean RIL version | 12:11 |
| mal | hwc version is seen in journal log | 12:12 |
| mal | deathmist: hmm, I need to remember how to parse that hwc version | 12:12 |
| mal | probably 2.1 is fine | 12:13 |
| deathmist | weirdly enough in my reference libexec logcat on 15.1 there also is 0 mention of "radio" in the entire file | 12:14 |
| mal | deathmist: normal logcat (without parameters) doesn't have radio related things "/usr/libexec/droid-hybris/system/bin/logcat -b radio" should have | 12:16 |
| rinigus | mal: sounds like a great plan! assumption is that libhybris will work and all differences are in config/version packages and system/vendor images. | 12:29 |
| rinigus | mal: as for libhybris preference (which hal to use), I guess it will go into config as in https://build.merproject.org/project/prjconf/nemo:devel:hw:sony:h8216 | 12:30 |
| rinigus | mal: question regarding this organization - how do you tell obs to build all included SPEC files? | 12:30 |
| mal | yes, just add Prefer: droid-hal-something-devel | 12:30 |
| rinigus | as if I have multiple specs in https://github.com/sailfishos-sony-tama/droid-config-sony-tama-pie/tree/master/rpm | 12:31 |
| mal | rinigus: you add separate packages for each | 12:31 |
| mal | I think it doesn't know how to handle multiple specs otherwise except to have package names after each spec | 12:32 |
| rinigus | mal: OK, but how do I tell which SPEC it will use in each package? as when should it choose droid-config-h8216.spec and when something else from the same source tree. | 12:32 |
| mal | rinigus: it chooses spec based on package name | 12:33 |
| rinigus | mal: nice! will try. | 12:33 |
| mal | rinigus: so if you add a package with name droid-config-h8216 it swill use a spec with that name, in case there is no such spec then it search for any spec, if there are more spec files then it might fail, you can test multiple spec build by renaming some package with multiple specs to something that doesn't match any of those | 12:34 |
| rinigus | mal: as it works for ganges and nile, should work here as well | 12:35 |
| mal | afaik it should only know how to build one spec for each package so just add the separate packages | 12:35 |
| mal | which all then use the same git repo | 12:35 |
| rinigus | mal: now what about generated kickstart file in http://repo.merproject.org/obs/nemo:/devel:/hw:/sony:/h8216/sailfish_latest_armv7hl/armv7hl/droid-config-h8216-ssu-kickstarts-0.1.1-1.10.1.jolla.armv7hl.rpm . I suspect that url will be generated with the device name (as h8216) and not tama in it. | 12:35 |
| mal | rinigus: check how it's done for ganges, it has stuff like board mappings | 12:37 |
| mal | sparse/usr/share/ssu/board-mappings.d | 12:38 |
| mal | i.e. variants | 12:38 |
| mal | rinigus: which means we probably should rename the OBS project | 12:40 |
| rinigus | mal: yes, I am sure we will need to rename, probably to tama. from those mappings I cannot figure out what will be url in kickstart | 12:41 |
| mal | rinigus: probably related to adaptation-repos in 05-sony-ganges.ini which is then used by ssu things | 12:42 |
| rinigus | mal: I guess I will have to experiment and see what url will be composed | 12:43 |
| rinigus | mal: or do you have somewhere nearby ganges ks? | 12:43 |
| mal | there is hopefully it will work, if not then we need to fix the ssu things | 12:44 |
| rinigus | .. but I can also experiment with it | 12:44 |
| mal | just check how the kickstarts look if you add such configs | 12:44 |
| rinigus | mal: ok, will do. So, I will check how kickstart will change and then, if all is fine, we will rename project accordingly | 12:45 |
| rinigus | mal: unfortunately, it looks to be ignored. commit https://github.com/sailfishos-sony-tama/droid-config-sony-tama-pie/commit/e0d69362f6c8fce5b4cd2b26bd8ec409fd35ab69 | 13:05 |
| rinigus | ks - http://repo.merproject.org/obs/nemo:/devel:/hw:/sony:/h8216/sailfish_latest_armv7hl/armv7hl/droid-config-h8216-ssu-kickstarts-0.1.1+master.20191117125332.1.ge0d6936-1.11.1.jolla.armv7hl.rpm | 13:05 |
| mal | rinigus: https://github.com/mer-hybris/droid-config-sony-ganges-pie/blob/master/droid-config-common.inc#L5 | 13:15 |
| rinigus | mal: missed that, sorry! | 13:15 |
| rinigus | mal: still seems to be ignored for ssu ks generation | 13:30 |
| mal | rinigus: there is the new repo in there though | 13:31 |
| mal | but not completely correct though | 13:31 |
| mal | rinigus: maybe community adaptation messes that up | 13:32 |
| mal | in your spec | 13:32 |
| * vknecht sharpens his Loire Pie builds | 13:34 | |
| rinigus | mal: not sure what you mean regarding incorrect url, looks to be ok - also when tested via browser | 13:40 |
| rinigus | as for community adaptation, maybe. no idea | 13:40 |
| rinigus | will test without it | 13:41 |
| vknecht | iiuc setting community_adaptation = 1 sets some sort of default when there's no ssu board mappings, so it's sort of exclusive | 13:42 |
| vknecht | Mal, curious to know what POV snapshot PR gave with another device, had you have a chance to check and did it work better ? | 13:49 |
| rinigus | mal, vknecht : that worked. not what we want, but at least some change - https://dpaste.de/wEWk | 13:51 |
| rinigus | I guess I should base it on https://github.com/mer-hybris/community-adaptation | 13:58 |
| mal | rinigus: I meant that your config has sony-tama:/extra-images but the url .ks has h8216:/extra-images | 14:11 |
| mal | rinigus: I think we might need to do some changes somewhere, not sure if there is even point having the extra-images project | 14:12 |
| mal | rinigus: we need community-adaptations anyway it seems | 14:13 |
| rinigus | mal: I agree. except extra images project is good to have to avoid many copies of the same images for multiple sfos releases. right now its one image per android base | 14:14 |
| rinigus | mal: one way would be to fork community-adaptations and make changes in its urls | 14:14 |
| mal | rinigus: that will need some thinking because for example how would that work in testing, the url would have to have some custom target name | 14:17 |
| mal | vknecht: I need to test that again on some devices | 14:19 |
| rinigus | mal: devel/testing is done via spec name trick in community-adaptations and declaring project either -devel or -testing in name. for extra images, we will have the same url for devel and testing. no need to keep 2 copies | 14:19 |
| mal | rinigus: I mean that community-adaptation forces the target name to be versioned in testing | 14:19 |
| rinigus | mal: if we talk about extra-images, this doesn't matter, as far as I can see. we just include it as 'external' repo. or do I miss something? | 14:21 |
| mal | rinigus: where did the url get that target name? | 14:22 |
| rinigus | mal: I need more specific question, sorry. which url and what's target in it? | 14:24 |
| mal | repo --name=adaptation-community-h8216-extra-images-@RELEASE@ --baseurl=http://repo.merproject.org/obs/nemo:/devel:/hw:/sony:/h8216:/extra-images/aosp_9.0.0_r46/ | 14:24 |
| mal | where did that aosp_9.0.0._r46 come to that, where did you define it | 14:24 |
| mal | that is the name of the OBS target | 14:25 |
| mal | you must have defined it in some config | 14:25 |
| rinigus | mal: sure. its defined in https://build.merproject.org/project/meta/nemo:devel:hw:sony:h8216:extra-images | 14:26 |
| rinigus | as for url, I define it using a hack in https://github.com/sailfishos-sony-tama/droid-config-sony-tama-pie/blob/master/kickstart/part/h8216 | 14:27 |
| deathmist | alright just tested calling and seems to work nicely on hybris-16.0 :) just no cellular data for some reason, SMS already works too | 15:08 |
| deathmist | what I did notice tho is that my BT headset still doesn't function during calls (ringtone from phone speaker & different tone from headphones, no mic unless switched to phone speakers, no call audio from headphones) when media audio works normally. done the following already https://git.io/Jeo5i am I missing something? | 15:12 |
| mal | deathmist: what BT configs do you have enabled in kernel? | 15:25 |
| mal | in defconfig | 15:25 |
| deathmist | mal: at least these ones I've moved down with the other hybris changes https://git.io/Jeo5N | 15:26 |
| mal | ok, those should be enough | 15:30 |
| mal | deathmist: remove droid-config-cheeseburger-bluez5 | 15:33 |
| mal | deathmist: sorry, don't remove | 15:33 |
| mal | misread some configs | 15:33 |
| mal | deathmist: do you see anything in journalctl when you try to use BT headset during calls? | 15:36 |
| deathmist | mal: there is "Refusing unexpected connect" from bluetoothd and "audio_route_sink(): unknown audio sink device = 'bthfpforcall'" from mce at least, I first placed a call normally and then received one after already connecting the BT headset https://pastebin.com/MTB7czby | 15:45 |
| mal | deathmist: check what "pactl list" tells as nemo user | 16:07 |
| T42 | <Lukapanio> @Lukapanio [https://paste.ubuntu.com/p/HTMpKwfCtf/], here is logcat | 16:07 |
| deathmist | mal: https://pastebin.com/raw/RDcV5uGU | 16:09 |
| mal | @Lukapanio which android base? | 16:09 |
| T42 | <Lukapanio> @mal 15 | 16:13 |
| T42 | <Lukapanio> https://paste.ubuntu.com/p/WRVXGsNtGs/ | 16:13 |
| T42 | <Lukapanio> journal | 16:13 |
| deathmist | @Lukapanio you've clearly missed entirely on reading second part of https://github.com/mer-hybris/hadk-faq#hybris-15-1 I don't see overrides for hwservicemanager and vndservicemanager being used... | 16:24 |
| mal | deathmist: that was my guess also and why I asked which base it was :) | 16:29 |
| *** electro is now known as Guest76717 | 16:29 | |
| T42 | <nitin_3> @mal I am getting access call barring error from one service provider | 16:40 |
| T42 | <nitin_3> when on sfos ,someone else also tried with same service provider and their out going calls are also getting barred | 16:40 |
| T42 | <Lukapanio> @deathmist thanks done tha on device | 16:40 |
| T42 | <Lukapanio> got boot animation of los | 16:40 |
| deathmist | @Lukapanio isn't that worse? SFOS has no bootanim or did you run surfaceflinger manually? I don't understand | 16:41 |
| mal | deathmist: your ril config looks odd, you have both socket and transport in there | 16:45 |
| mal | deathmist: compare to this https://github.com/mer-hybris/droid-config-sony-ganges-pie/blob/master/sparse/etc/ofono/ril_subscription.conf | 16:45 |
| deathmist | mal: oh yeah I was meant to clean that file up a bit after rebase, those are indeed useless but also don't help with cellular data in anyway (just tested after removing them and rebooting, same errors still) | 16:49 |
| deathmist | and by "those" I meant socket lines | 16:50 |
| mal | deathmist: how did you select the other custom changes you have there? | 16:50 |
| T42 | <Lukapanio> I HwcPassthrough: HwcHal::createClient: Client already exists. Waiting for it to be destroyed. | 16:50 |
| T42 | <Lukapanio> hmmmmm how to know what client, and how to destroy it | 16:51 |
| T42 | <Lukapanio> https://github.com/Sailfish-On-Vince/issues/issues/15 | 16:55 |
| deathmist | mal: I looked thru the reference ril_subscription config upstream and picked options after I made syre they didn't cause any regressions back on my 15.1 port, just carried the file over to 16.0 as well. tried Xperia 10 and XZ2 (which worked fine for a start in 15.1) configs too, but still no cellular data with all same errors | 16:56 |
| mal | deathmist: did you have the same android side services disabled in 15.1 or did you disable something more in 16.0 (other than the standard ones like in ganges) | 17:06 |
| mal | the changes you had in config repo looked quite scary | 17:06 |
| deathmist | lmao, yes I did disable more stuff, maybe that's worth yet another look, I'll start re-enabling stuff until SFOS won't boot or stuff starts working and take notes :p | 17:14 |
| deathmist | mal: btw the "patched" vendor files I have there mainly just changed paths to /dev/cpuset so that worked, but after further research there is already another cpuset cgroup mounted: /sys/fs/cgroup/cpuset so maybe I'll do udev magic and make a symlink to /dev/cpuset etc for droid stuff compatability. I've already disabled mount units for those too to | 17:17 |
| deathmist | eliminate them causing issues | 17:17 |
| mal | deathmist: those vendor things in libexec look very odd | 17:21 |
| deathmist | they're mostly useless, already disabled their respective bind mount units so they can't affect anything | 17:22 |
| mal | deathmist: you mean those vendor.dataqti and rmt_storage is very imprtant (it's for mobile data or modem in general) | 17:23 |
| mal | and so on | 17:23 |
| mal | I'm quite sure those are required | 17:24 |
| mal | also android 9 has override option for services in which case there no need to edit the original files anyway, the whole thing is just very wrong | 17:25 |
| mal | many of those look like something that shouldn't be removed | 17:25 |
| deathmist | mal: my libexec vendor init files? the things I removed just spam logs and die continuously or (most of them) the actual binaries the services reference don't exist. either way I removed them from libexec now on the device at least as well as their mount units, re-enabled qti stuff in init files, no cellular data stil after rebootl. I'll keep going | 17:29 |
| deathmist | tho | 17:29 |
| mal | without actually seeing logs I can't really be sure | 17:32 |
| mal | if a service dies there is usually some reason for that, it's not common for that to happen | 17:33 |
| deathmist | mal: when I use https://git.io/JeBvs instead, still no luck. constantly failing services with that file include time_daemon (safe to disable), vendor.dataqti (looking thru init files it's some logging service, seems to be equivalent to my previous 'qti' service on 15.1 which I didn't need for cellular data) and keystore | 17:38 |
| deathmist | I'll send journal in a bit | 17:40 |
| deathmist | mal: journal after ~2 min of waiting https://dpaste.de/KVhh/raw also "vendor.dataqti" is marked as "disabled" in my /vendor/etc/init/hw/init.qcom.rc and it's binary is indeed just "qti" | 17:51 |
| T42 | <Lukapanio> @Lukapanio [https://github.com/Sailfish-On-Vince/issues/is …], hmmm @birdzhang how have you fixed? | 17:52 |
| T42 | <Lukapanio> that 2 commits dosnt help | 17:52 |
| deathmist | @Lukapanio which issue? I can try to help, but telegram replies cut off so the URL is broken in IRC | 17:56 |
| T42 | <Lukapanio> https://github.com/Sailfish-On-Vince/issues/issues/15 | 17:56 |
| rinigus | is there any reason to not include jolla-settings-accounts-extensions-3rd-party-all? is it included on official devices by default? | 17:57 |
| deathmist | @Lukapanio I assume you're in an early porting stage, common cause is /system & /vendor not being mounted, so maybe give output of "mount" | 18:00 |
| T42 | <Lukapanio> https://bpaste.net/show/LB37E | 18:01 |
| deathmist | rinigus: idk what you mean, pretty sure that's been default in patterns for a while even on community devices https://git.io/JeoNW | 18:02 |
| rinigus | deathmist: then I managed to miss it somehow in my config. | 18:02 |
| T42 | <Lukapanio> @deathmist | 18:02 |
| T42 | <Lukapanio> https://bpaste.net/show/LB37E | 18:02 |
| deathmist | @Lukapanio I already noticed, but seems both are mounted. what is the device? | 18:03 |
| T42 | <Lukapanio> p | 18:03 |
| T42 | <Lukapanio> moto g5 | 18:03 |
| T42 | <Lukapanio> cedric | 18:03 |
| T42 | <Lukapanio> test_lights | 18:04 |
| T42 | <Lukapanio> is ok | 18:04 |
| T42 | <Lukapanio> test_sensors is ok | 18:04 |
| deathmist | @Lukapanio after adding init files from FAQ, did you rebuild droid-configs and make new image or somehow place them on the device rootfs? if the ladder, how? I had issues manually placing files to where they should be from TWRP (it was init files specifically too), so maybe make a new image with the changes and see if anything is different | 18:08 |
| T42 | <Lukapanio> changed inrootfs | 18:09 |
| deathmist | then I suggest you doing the changes to your droid-config repo, run build_packages -c and build_packages -i after | 18:11 |
| deathmist | @Lukapanio you've made your droid-hal spec incorrectly, you never terminate straggler_files with a "%{nil}", also doesn't SD430 have 64-bit support? | 18:16 |
| T42 | <Lukapanio> it have | 18:16 |
| deathmist | well why don't you have "%define droid_target_aarch64 1" in your spec file then too? | 18:17 |
| T42 | <Lukapanio> yep | 18:17 |
| deathmist | so you don't keep your github sources in sync with your local ones? I can't really help you much if I don't know what your repos actually look like when you're asking a question | 18:18 |
| T42 | <Lukapanio> ok will upstream to new branch | 18:22 |
| T42 | <Lukapanio> https://bpaste.net/show/OBRFM | 18:22 |
| T42 | <Lukapanio> %define droid_target_aarch64 1 | 18:22 |
| T42 | <Lukapanio> i have it | 18:22 |
| T42 | 彭汝掎 %lastname% was added by: 彭汝掎 %lastname% | 18:36 |
| deathmist | mal: what do you think about https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_cheeseburger-dumpling ? :) I'll prob move over some steps from my GitHub guides later, but would it be ok to merge the two 5/5T models together? the hardware is pretty much identical and only difference is droid-* packages which I can deal | 19:47 |
| deathmist | with myself | 19:47 |
| vknecht | deathmist, nice pic :-) | 19:51 |
| vknecht | problem with wlan hotspot/connection sharing ? | 19:56 |
| deathmist | thanks :) yeah well cellular data is broken so I can't share hotspot, it probably works fine but I can't test it :p | 19:57 |
| vknecht | ah | 19:58 |
| vknecht | wasn't fan of upping base version, but I guess no much other choice now... hope it'll play well | 20:09 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!