| T42 | <meierrom> @adampigg: nice pic. Are batteries in separate box? | 01:26 |
|---|---|---|
| T42 | <然捷 %lastname%> (Photo, 1223x675) https://irc.thaodan.de/.imgstore/3aeEgOFBq3.png "精准币圈菠菜棋牌粉" "非小号/mytoken关注惊爆价"1、币圈电报群/微信群炸群推广 2、twitter、facebook关注 3.KYC身份材料出售 4、电报群/微信群/potato拉币圈活人 5、国内外交易所APP实名注册认证 6、电报群客服活聊天 7、批量注册国内外交易所实名账户，，出twitter、facebook、微信带粉账号 | 04:20 |
| T42 | <dontatmepls> these spam accounts need to stop | 06:13 |
| r0kk3rz | welcome to smellogram | 06:38 |
| deathmist | hey, if RTC alarms are working are they meant to power on the device (e.g. to actdead mode) when an alarm has been set in SFOS and the device is turned off or am I understanding them incorrectly? | 06:42 |
| T42 | <adampigg> @meierrom [@adampigg: nice pic. Are batteries in separate …], Atm...wont be final though | 06:44 |
| r0kk3rz | deathmist: yeah iirc | 06:44 |
| deathmist | I may know why they aren't working then: I can't set the rtc device as rw. when I do, the boot process stops before it even starts DSME :/ still get LED tho, could try debugging it if only I could telnet in for once | 06:46 |
| r0kk3rz | whats the go with this error? Error <creator>[11/19 06:49:21] : Command 'modprobe' is not available. | 06:50 |
| r0kk3rz | running mic | 06:50 |
| r0kk3rz | https://gitlab.com/sailfishos-porters-ci/sailfish-scorpion_windy_ci/-/jobs/354523340 | 06:51 |
| rinigus | r0kk3rz or mal: would you mind to rename nemo:devel:hw:sony:h8216 -> nemo:devel:hw:sony:tama and make new project nemo:testing:hw:sony:tama | 07:03 |
| T42 | <birdzhang> r0kk3rz: i asked yesterday, maybe we should ping coderus | 07:06 |
| mal | rinigus: not sure if rename is possible, I might need to create the new one | 07:07 |
| rinigus | mal: no problem, let's make new. | 07:08 |
| rinigus | I will let you know when the old one can be removed | 07:08 |
| mal | rinigus: https://build.merproject.org/project/show/nemo:devel:hw:sony:tama use osc copypac to copy the old packages | 07:09 |
| mal | I can do it if needed | 07:10 |
| r0kk3rz | @birdzhang its maybe a problem with the docker image? | 07:10 |
| r0kk3rz | tbh im surprised it even needs modprobe | 07:10 |
| rinigus | mal: will do. would have to learn copypac anyway. what about testing? I'd mainly need it for adding extra-images there | 07:11 |
| r0kk3rz | osc can be a pita to set up sometimes | 07:12 |
| mal | rinigus: https://build.merproject.org/project/show/nemo:testing:hw:sony:tama | 07:13 |
| rinigus | mal: thank you very much! | 07:13 |
| mal | r0kk3rz: that is why I have commands ready for osc copypac so I can clone a device easily | 07:13 |
| r0kk3rz | yeah its definitely useful | 07:14 |
| r0kk3rz | but ive also seen it explode with weird python errors too many times :) | 07:14 |
| T42 | <adampigg> use osc from your distro, not the sdk | 07:16 |
| mal | I always use it from host | 07:16 |
| rinigus | mal: would be great to become maintainer for nemo:devel:hw:sony:tama. if possible :) | 07:17 |
| mal | I thought I added you there | 07:17 |
| mal | rinigus: you should have permissions to both devel and testing | 07:19 |
| rinigus | mal: now I do, thanks. copypac worked with a small script | 07:20 |
| deathmist | mal: how should I deal with OBS for OP5/5T? maybe create a oneplus:msm8998-common project with most stuff, then :cheeseburger and :dumpling for droid-* packages perhaps with subprojects pointing to the :msm8998-common? hardware is nearly identical between the models | 07:20 |
| mal | rinigus: we should add copy script to faq | 07:21 |
| rinigus | mal: maybe. not mine, though - very quick hack :) | 07:21 |
| mal | deathmist: need to think | 07:22 |
| rinigus | ohh, surprise, _pattern package after copypac exploded and became broken. ... somebody was telling me _pattern is not really up for it. | 07:24 |
| rinigus | mal: how do I exclude _pattern from building? does it need to be re-patternised? | 07:25 |
| rinigus | tama project | 07:25 |
| mal | rinigus: remove it, then ask lbt to add patterns for those, and to remove it from the old project | 07:26 |
| mal | so we can remove the old project completely | 07:27 |
| rinigus | mal: will do | 07:28 |
| T42 | <adampigg> mal, bluetooth-rfkill-event is built from master, so that can be a common package....only need to pr broadcom-bluetooth | 07:30 |
| mal | @adampigg wure, I'll add those at the same time | 07:31 |
| mal | *sure | 07:31 |
| T42 | <adampigg> mal, for broadcom.... i should create broadcom-bluetooth-bluez5.spec, and add Provides: line? | 07:37 |
| T42 | <adampigg> mal, any easy way to use the new gcc? does it have many deps if i add it toa project? | 07:43 |
| r0kk3rz | @birdzhang so far so good with the 3.1.0.12 docker | 07:45 |
| T42 | <birdzhang> r0kk3rz: i see, will rollback to 3.1.0.12 docker image too | 07:46 |
| r0kk3rz | it only runs mic, so it should be ok | 07:47 |
| T42 | <birdzhang> yeah | 07:47 |
| T42 | <birdzhang> building now ;) | 07:51 |
| rinigus | any idea why initrd-logos is missing in testing 3.2.0.12 and available in devel? at obs. as a result, https://build.merproject.org/package/show/nemo:testing:hw:sony:tama/droid-hal-img-boot-sony-tama-pie is unresolvable | 08:17 |
| rinigus | lbt: please patternise nemo:testing:hw:sony:tama and nemo:devel:hw:sony:tama. also, please remove internal patterns for nemo:devel:hw:sony:h8216. we are going to delete this project | 08:19 |
| rinigus | for now, I copied nemo:devel:hw:common/initrd-logos-sailfish to tama testing. would be great to get that package in nemo:testing:hw:common | 08:33 |
| mal | @adampigg yes, add broadcom-bluetooth-bluez5.spec, you can probably add a Provides there also if we want to have those use the same thing in patterns | 08:41 |
| rinigus | I have been able to get oom killer on xz2 using the following sequence: https://github.com/sailfishos-sony-tama/main/issues/30 | 11:41 |
| rinigus | on onyx all is fine. | 11:41 |
| rinigus | I wonder whether its reproducible on other newer devices or just my xz2-specific headache | 11:42 |
| Mister_Magister | camera always used shitton of ram | 11:56 |
| abranson | that hdr scene mode's hilarious for testing oom. so many buffers. | 11:57 |
| rinigus | does it mean you see the same? | 11:59 |
| rinigus | actually, in dmesg I see something like https://dpaste.de/Dbem . from searching online, it seems to be android-feature. should we disable that beauty from our builds? | 12:10 |
| Mister_Magister | rinigus: lmk is standard part of linux kernel why would you even disable that | 12:11 |
| Mister_Magister | that would be madness. If you run out of ram your phone would not get out of it and just freeze | 12:12 |
| rinigus | Mister_Magister: that was a question, possible with the wrong assumption. assumption was that its a part of android builds, but not regular linux. from your reply, I deduce that this assumption is, probably, wrong | 12:13 |
| Mister_Magister | rinigus: if you enable sysrq on your desktop, hit alt+sysrq+f and you force trigger lmk. you will see same message in dmesg | 12:14 |
| Mister_Magister | well similar at least | 12:15 |
| Mister_Magister | https://paste.opensuse.org/59391536 linux can sound scary | 12:17 |
| rinigus | Mister_Magister: I am not going to try - as its gonna disturb too much right now. However, we have CONFIG_ANDROID_LOW_MEMORY_KILLER=y and corresponding driver seems to be in drivers/staging/android/lowmemorykiller.c | 12:18 |
| rinigus | not very desktopy to me | 12:18 |
| Mister_Magister | ye well android can have bit different memory killer that's fair point | 12:18 |
| Mister_Magister | but it's still needed | 12:18 |
| Mister_Magister | or you could use standard memory killer but what's the difference | 12:19 |
| Mister_Magister | you setup android one in init files i think | 12:19 |
| rinigus | Mister_Magister: I wonder whether my oom with camera is induced by trigger-happy lowmemorykiller. but let's see if others see the same killer at their devices. | 12:23 |
| Mister_Magister | rinigus: camera eats lots of ram it often kills my apps. you can monitor ram usage in background and see that it just ran out of memory | 12:28 |
| Mister_Magister | it's like… normal thing to do | 12:28 |
| abranson | yeah there's a special android lmk | 12:30 |
| rinigus | well, its a fast process and will not occur if you do it differently. its just I haven't seen it on onyx and couldn't reproduce it on it. at the same time, onyx has 1gb ram less. | 12:31 |
| Mister_Magister | abranson: but it should do roughly same job right | 12:31 |
| rinigus | ... and in onyx, its commented out | 12:34 |
| abranson | Mister_Magister: they score things differently iirc. the android one is quite specific to that process model | 13:04 |
| Mister_Magister | let's disable it what worse could happen | 13:06 |
| Mister_Magister | yeah android one probably chooses between java programs than native ones | 13:06 |
| abranson | i seem to remember it uses thousands for different classes of android process | 13:19 |
| Mister_Magister | interesting | 13:19 |
| rinigus | its briefly described in https://elinux.org/Android_Kernel_Features under oom handling | 13:22 |
| Mister_Magister | rinigus: you can try disabling it and switching to linux one if it changes anything | 13:22 |
| rinigus | abranson: android lmk is something additional, as far as I can see https://source.android.com/devices/tech/perf/lmkd | 13:22 |
| rinigus | Mister_Magister: yes, I will try | 13:23 |
| Mister_Magister | disabling different things is fun ^^ | 13:23 |
| abranson | rinigus: I think that daemon communicates with the kernel android lmk | 13:25 |
| abranson | manages the aggressiveness of the killing depending on how short memory is | 13:26 |
| rinigus | abranson: according to "In Android 9 and higher, userspace lmkd activates if an in-kernel lowmemorykiller driver is not detected", I'd expect they are exclusive | 13:26 |
| abranson | oh really? guess i can't remember then :) | 13:27 |
| T42 | <Lukapanio> simStatusChangedInd: radioService[0]->mRadioIndication == NULL | 13:46 |
| T42 | <Lukapanio> it seems to be mainproblem with modem | 13:49 |
| deathmist | @Lukapanio your modem or what? mine has that spammed plenty of times, but calls and SMS work, no cellular data tho so it's probably related to that(?) | 13:51 |
| deathmist | you're just likely missing configs if your modem doesn't work, do you even have UI yet? | 14:03 |
| deathmist | or "ofono" to be precise, not modem, that should mostly work OOB | 14:04 |
| T42 | <Lukapanio> yes i have gui | 16:07 |
| rinigus | fun fact: disabling android lowmemorykiller resulted in no oom induced by camera even in the presence of browser and osm scout server + pure maps. and there are no messages regarding low ram either. | 16:09 |
| rinigus | abranson Mister_Magister ^ will monitor whether it has some other side effects | 16:10 |
| abranson | rinigus: make sure you check dmesg to see if the linux oom killer's doing anything | 16:13 |
| abranson | if it's even there... | 16:13 |
| deathmist | @Lukapanio add ofono configs from https://git.io/JeKHH to your device (and possibly modify if needed), afterwards remember to put them in your droid-config repo too | 16:15 |
| rinigus | abranson: I did check, that seems to be clean | 16:16 |
| rinigus | I presume it is there... let me think how to test it | 16:17 |
| Mister_Magister | rinigus: try to kick looinx oom reaper | 16:31 |
| Mister_Magister | my moto g2 has # CONFIG_ANDROID_LOW_MEMORY_KILLER is not set | 16:34 |
| Mister_Magister | but that's older one let's try newest one | 16:34 |
| Mister_Magister | newest snapdragon 845 has CONFIG_ANDROID_LOW_MEMORY_KILLER=y | 16:35 |
| rinigus | Mister_Magister and abranson : with stress test I managed to reboot phone. not good, will have to see how to get oom killer working | 16:36 |
| Mister_Magister | that's what i suspected | 16:36 |
| abranson | maybe we have to use the android one? | 16:42 |
| Mister_Magister | for new devices possibly | 16:44 |
| rinigus | I presume that with android one configured, the classical one should be disabled mostly. well, for now, I can enable it back and postpone hunting for how to setup the classical one. | 16:45 |
| rinigus | and deal with it if it does become an issue in more common workloads | 16:45 |
| T42 | <Akatsu %lastname%> Do anyone have idea how wcnss initialization works? I have broken wifi so using logcat i made almost all what it was asking me for but i stopped on wcnss not being able to wcnss_write_cal_data. | 17:48 |
| rinigus | lbt: please patternise nemo:testing:hw:sony:tama and nemo:devel:hw:sony:tama. also, please remove internal patterns for nemo:devel:hw:sony:h8216. we are going to delete this project | 18:21 |
| T42 | <adampigg> rinigus: save the wait, dont paternize, use meta ;) | 18:23 |
| rinigus | adampigg: I don't mind meta, but then we have to do it properly. namely, generated KS should have already %packages replaced with meta. | 18:24 |
| rinigus | so far, I have found in one of droid-config scripts a call %gen_ks. | 18:24 |
| rinigus | any idea where is that one? | 18:25 |
| rinigus | ... defined | 18:25 |
| piggz | nope | 19:25 |
| piggz | mal: https://github.com/mer-hybris/broadcom-bluetooth/pull/2 | 19:25 |
| rinigus | piggz: me neither. | 19:32 |
| rinigus | maybe digging through build logs will help. I'll check | 19:33 |
| piggz | rinigus: i think its maybe done in droid-config.inc? | 19:33 |
| rinigus | piggz: grepping it didn't help. but that's where %gen_ks is | 19:34 |
| rinigus | piggz: I wonder, if its this bit - https://git.merproject.org/mer-core/ssu/blob/master/ssuks/ssukickstarter.cpp#L152 | 19:46 |
| piggz | rinigus: geez, its a compiled program??? | 19:47 |
| rinigus | piggz: yes, called ssuks | 19:48 |
| piggz | rinigus: im sure some sed magic will fix up the file :D | 19:48 |
| rinigus | piggz: yes, that's true. and that sed magick can be added to spec | 19:49 |
| piggz | yes | 19:49 |
| vknecht | good question, would have expected to find this rpm macro defined in one of https://git.merproject.org/mer-core?utf8=%E2%9C%93&filter=rpm but could find it from a quick look | 19:55 |
| vknecht | but there must be something somewhere : | 19:55 |
| vknecht | PlatformSDK [vince@dozer ~]$ strings /var/lib/rpm/Packages | grep gen_ks | 19:55 |
| vknecht | - [ks] Add hacky %gen_ks macro for easy kickstart packaging | 19:55 |
| vknecht | ah | 20:01 |
| vknecht | https://git.merproject.org/mer-core/ssu/commit/aa0adee682a8de48786c2230785735e34e32282c | 20:01 |
| TheKit | did latest Sailfish update break sailfishos-porters-ci? Error <creator>[11/19 20:23:26] : Command 'modprobe' is not available. | 20:25 |
| TheKit | 80 ERROR: Job failed: exit code 1 | 20:25 |
| deathmist | TheKit: it was discussed earlier today, seems 3.1.0.12 docker image works fine http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2019-11-19.log.html#t2019-11-19T06:50:49 | 20:28 |
| TheKit | thank you | 20:28 |
| deathmist | I have an interesting situation on my phone, got both /vendor/firmware/ and a mount /vendor/firmware_mnt/ with the ladder containing an image/ dir, but e.g. only the former having "tfa98xx.cnt" in it, what should I do? I still have some FW issues on 16.0 | 20:31 |
| vknecht | deathmist, about rtc & alarm wakeup, maybe you need something like that https://github.com/vknecht/android_kernel_alcatel_msm8916/commit/22eba3aaf141c1b3e868cdfe14074c3cc6133fb8 | 20:32 |
| vknecht | iirc that's what made powering up device from a sfos alarm work | 20:33 |
| piggz | deathmist: sounds similar to pro1 mounts | 20:33 |
| vknecht | *work for me | 20:39 |
| vknecht | and probably from los too ; don't be too eager, need like 3 or 4 minutes delay at least iirc | 20:44 |
| deathmist | vknecht: nvm I just re-tested and it seems to work (just boots normally tho, not to actdead but that is perfectly fine imo) :D that's cool. it just spams my logs like crazy tho in it's current state. primary cause for it seems to be https://git.io/JeKAP | 20:58 |
| deathmist | and a sample of the spam https://pastebin.com/21FvWevT | 20:58 |
| vknecht | actdead is only for battery charging when device is powered off isn't it ? I'd expect a full OS load on alarm wakeup, don't you ? dunno about log spam, should check it here | 21:02 |
| vknecht | good for you that it works without dts/kernel fiddling, tho ;-) | 21:03 |
| vknecht | rtc write seems like a whole different beast, iirc it crashed when enabled ; I'd have like not to have ~40 years uptime displayed, but let it slide | 21:07 |
| vknecht | *liked | 21:07 |
| mcencora | hi. now that we know that jolla does not care about the community, is anybody here working on Android 8/9 for Xperia X? | 22:19 |
| vknecht | mcencora, dunno about real Jolla intents, but there's effort about Loire platform toward aosp8 rebasing at https://build.merproject.org/project/show/home:vknecht:hw:qualcomm:f5121 | 22:34 |
| vknecht | and I'm about to switch to aosp9 base | 22:34 |
| vknecht | afaik, Jolla stance is http://www.merproject.org/logs/%23mer-meeting/%23mer-meeting.2019-11-14.log.html#t2019-11-14T10:47:10 | 22:35 |
| mcencora | vknecht: jolla stance was shared today on blog - they won't do aosp8 rebase for xperia x | 22:35 |
| vknecht | oh ? | 22:36 |
| vknecht | didnt' follow the blog lately | 22:36 |
| mcencora | vknecht: if I have paid Sailfish license, will I be able to install android app support with your port? | 22:36 |
| vknecht | well, best I can propose is Anbox support, can't say anything about paid-for-dalvik support | 22:38 |
| vknecht | (w | 22:38 |
| vknecht | (must say didn't even try Anbox on aosp8 base, lack of time) | 22:39 |
| mcencora | is there any difference w.r.t. to how jolla provides android app support vs anbox? | 22:40 |
| vknecht | there's probably tons of differences, esp. good knowing of system guts (eg. media/audio routing so it's available to android apps) | 22:43 |
| vknecht | maybe it's not so much, when you know andbox/lxd innards, but still... | 22:44 |
| mcencora | do you expect to get the bluetooth/usb and higher battery consumption to be fixed with your rebase on top of aosp9? | 22:46 |
| vknecht | hmm, just read the blog post and it sounds like a defeat | 22:48 |
| vknecht | well, about aosp9, I just recently published Loire AOSP 9 builds as baseline for a rebase ; and from what I've seen, it's more on the good side than bad | 22:50 |
| vknecht | https://forum.xda-developers.com/xperia-x/development/rom-aosp9-20191117-builds-t4004959 | 22:51 |
| mcencora | yeah, I am really pissed. It basically means that Jolla isn't going to fix Sailfish for Xperia X to finally make it non-beta quality | 22:51 |
| mcencora | but that seems to be the case for all Xperia's | 22:51 |
| vknecht | Im | 22:52 |
| mcencora | they prefer to offer more beta ports for another device, then to fix bugs/finish features for existings ports | 22:52 |
| vknecht | *I must say I'm a bit surprised, I'd have expected Jolla could up Alien Dalvik support for X (Loire) a0t least to XA2 (Nile) | 22:54 |
| vknecht | *at least par to XA2 (Nile) | 22:54 |
| mcencora | hmm, your aosp9 port looks interesting. i will most probably try it out | 22:55 |
| mcencora | one question, do I need to backup my home folder before flashing? | 22:56 |
| mcencora | i.e. will /home/nemo stay untouched? | 22:56 |
| mcencora | or I need to backup and restory it manually | 22:56 |
| vknecht | it's not started yet, will have to integrate all lessons learned from tama port | 22:57 |
| vknecht | keep an eye on https://github.com/sailfish-on-loire ;-) | 22:58 |
| mcencora | aaah, I thought these images are for sailfish with aosp9 base, but this is just plain aosp9 | 23:00 |
| mcencora | ok, I will | 23:01 |
| mcencora | you are my only hope vknecht | 23:01 |
| mcencora | if this port fails, I am going to try ubuntu touch, or switch back to android/lineage os | 23:01 |
| mcencora | so I keep fingers crossed for your work | 23:02 |
| vknecht | afaik there's no aosp9 image ; aosp8-based ones from my obs still suffer from high battery consuption and no BT | 23:02 |
| vknecht | *aosp9-based image | 23:03 |
| mcencora | do you know the status of upstream Xperia X support in linux kernel? | 23:05 |
| vknecht | so yeah, some patience is needed and we'll see ; next higher hope is mainstream support like https://github.com/kholk/kernel-upstream | 23:06 |
| vknecht | :-) | 23:06 |
| mcencora | :) | 23:06 |
| vknecht | mcencora, I think I'll start on Loire aosp9 base this week-end, maybe make a request to join sailfish-on-loire GH | 23:11 |
| vknecht | @eugenio_g7 ^ | 23:17 |
| mcencora | vknecht: hmm, I think admin must invite me | 23:22 |
| mcencora | I don't see a way to make request to join | 23:22 |
| T42 | <eugenio_g7> Cool stuff, I should finally sync the aosp9 tree :D | 23:39 |
| T42 | <eugenio_g7> mcencora: if you remember me tomorrow morning I'll add you to the organization :) | 23:39 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
