Monday, 2019-12-16

T42布淑淮 %lastname% was added by: 布淑淮 %lastname%00:39
r0kk3rzmal: we should fix sfos-upgrade on OBS so we can add it to common repo01:37
r0kk3rzthats a bit better
T42<edp_17> @mal Do I need to add too the usb-moded-configs Obsoletes from the example or the ofono-configs-mer is enough? Thanks.06:51
T42<edp_17> @Elros, As you said, disabling the watchdog didn't solve the my missing gui issue. At leas I have one problem less in my build.06:55
deathmist@edp_17 do you know what those obsoletes do? they stop the default configs for ofono & usb-moded etc from conflicting with YOUR self provided ones in droid-configs sparse (if you have them), do NOT add obsoletes unless build is failing or something07:08
deathmistthe config files are provided in those -configs packages and obsoleting them obviously just doesn't install them to stop the conflict, either way give fresh journal after boot07:10
T42<edp_17> Thank you, I suspected that. I have got the same issue with my own ril-subscription file and I decided drop my one from sparse. Now I put it back and applied the obseletes bit into my .spec. And I was wondering about the other one. Thank you for explaining.07:14
T42<edp_17> Fresh journal:
T42<edp_17> when I tried to start lipstick with 'systemctl --user restart lipstick', I got 'Failed to get D-Bus connection: No such file or directory'07:28
Mister_Magisteris dhi working?07:28
T42<edp_17> How should I know?07:30
Mister_Magistersystemctl status droid-hal-init07:30
T42<edp_17> What I spotted is 'start-user-session@USER.service - not found'07:30
Mister_Magisterthat's okay07:31
Mister_Magisterwhat about07:31
T42<edp_17> dhi is active07:31
deathmist@edp_17 you can look at the log and simply search for "droid-hal-init", something funky is definitely going on as it's basically not executing any of the init*.rc files07:32
T42<edp_17> Thank you.07:33
Mister_Magisterdeathmist: ah right i was missing something ye init files are not being executed but it starts fine07:33
Mister_Magister@edp_17 how old is your source/build07:34
Mister_Magisterdeathmist:  /init.rc: 11: error while expanding import ya think?07:35
T42<edp_17> CM14.1 base, SFOS version Build is made yesterday.07:35
Mister_Magisterbut i mean sources07:36
Mister_Magisterthere is like only /init starting07:36
T42<edp_17> Yeah, I have found that. It says, insecure /init.samsungexynos8890.rc.07:36
deathmistlmao what "insecure init file"07:36
T42<edp_17> This is where from I removed the watchdog bit.07:37
Mister_Magisteris this samsung?07:37
T42<edp_17> Yep, S707:37
deathmistMister_Magister: quite sure that expand error is just the /init.extraenv.${ro.product.cpu.abi}.rc one which at least on my device is entirely irrelevant as I don't have one for arm64/aarch6407:38
Mister_Magisteryeah i was just wondering it probably is just warning07:39
Mister_Magisterbut that insecure is lmao07:39
T42<edp_17> Don't worry about the insecure file. As I said, I wanted to remove the watchdog from it and I messed up the original file therefore I transferred one from my pc but probably didn't set the correct permission.07:40
Mister_Magistertry to fix it then07:40
Mister_Magisteri'm pretty sure that's the error07:41
T42<edp_17> I reflash the image and that will solve it. But that will re-introduce the watchdog thing again.07:41
Mister_Magisterwhat watchdog thing?07:41
T42<edp_17> Yes, this time might be that is the issue, but I didn't have gui previously either. On my pc I removed the watchdogd, so I think the best to create an new image and flash that on the device. Then, I can see whether the gui started.07:42
T42<edp_17> Thank you guys. I'll go and create a new image for testing this out.07:43
T42<edp_17> I am not sure about that watchdog, in the previous journal it was moaning about it, so we decided to remove. But as Elros said, removing it probably will not solve the gui issue.07:44
T42<edp_17> But we tried.07:44
r0kk3rzthe issue with the watchdog, is that you didnt enable the kernel config like the config checker told you to07:45
Mister_Magisterr0kk3rz: XDDDDDD07:46
T42<edp_17> I have added this into the defconfig: 'CONFIG_WATCHDOG_NOWAYOUT=y'07:46
deathmistthis is his .config from earlier looks fine to me but I usually fix all warnings that I can too cuz I'm like that :)07:47
T42<edp_17> And yes, you are right, first my kernel didn't have it.07:48
deathmistah, make sure you package droid-hal with build_packages -d @edp_1707:48
T42<edp_17> But once we discovered this missing CONFIG_WATCHDOG_NOWAYOUT=y I added, recompiled the kernel and flashed it on the device. Then I tried to remove the rows from the init file.07:49
T42<edp_17> I run the 'rpm/dhd/helpers/' I think that also includes the -d.07:50
T42<edp_17> This new image will contain the kernel with the nowayout=y and the modified init.samsungexynos8890.rc where from I commented out the watchdog related stuff.07:52
T42<edp_17> Thank you for the help guys!07:52
deathmistrunning build_packages without any flags will rebuild literally everything including SFOS userspace stuff with no changes etc, it is usually not needed and I pretty much always just give it flags "-dcvi" for local builds07:57
T42<edp_17> I know it is rebuilding everything. Now this is what I wanted. I need to get used to it to use the flags. :)07:59
Mister_Magisteri just -d and drop it onto obs lmao08:00
T42<edp_17> I don't have obs yet. 😀08:00
T42<edp_17> But hope will have one.08:01
r0kk3rzget yourself an account08:11
Mister_Magisterit's FOSS08:12
Mister_Magisteror FOS if you prefer08:12
T42<edp_17> Ok, thanks.08:15
T42ItsMeShouko was added by: ItsMeShouko09:12
T42<ItsMeShouko> Hello, I am new to porting, I need some help09:13
T42<ItsMeShouko> ubu-chroot command is not properly set up I think so I cannot enter ubuntu chroot09:13
deathmist@ItsMeShouko welcome! please give approperiate logs like in this case full command-line you ran + the output and if it's over 3 lines or so put it up in or a similar service09:16
T42<ItsMeShouko> @deathmist [@ItsMeShouko welcome! please give approperiate …],
deathmistit seems you have an issue in ~/.hadk.env at least, check out that file for for and fill it in if info is missing as per HADK09:22
deathmistafter try and exit + re-enter the platform SDK chroot to see if the issue is still present09:24
r0kk3rzor source the file09:44
T42<ItsMeShouko> okay I fixed the file10:27
T42<ItsMeShouko> for repo init which mer-hybris branch do I need? My phone is Xiaomi MI A2 (came with android 8 but supports android 9 via OTA and is planned to receive android 10)10:27
T42<ItsMeShouko> should I use hybirs-16.0 branch for repo init?10:27
r0kk3rzyou need to select an appropriate base image10:29
r0kk3rzwhich is usually lineageos10:29
r0kk3rzideally the one that works the best10:30
T42<kisekinopureya> @ItsMeShouko use havoc pie device tree for a210:32
T42<kisekinopureya> And hybris 16 branch10:33
T42<谢晶婷 %lastname%> (Photo, 978x544) 👍接码批量出售 可注册各大平台👍精准拉币圈活粉,非小号 mytoken关注惊爆价 1、币圈电报群/微信群炸群推广 2、twitter、facebook关注 3.KYC身份材料出售  4、电报群/微信群/potato增粉拉人 5、国内外交易所APP实名注册认证 6、电报群客服活聊天  7、批量注册国内外交易所实名账户,出tw10:40
T42Sqonurgbxl was added by: Sqonurgbxl14:33
deathmistvknecht: this damn server_check.txt file with literally containing "hello" in /persist & /vendor keeps on gettting unlabeled even after running restorecon manually regardless of setting AUTORELABEL=0 in /etc/selinux/config with SELinux disabled on fresh image, nothing seems to work18:33
deathmistat least I know exactly where the issue is and can manually fix it if needed, but I think the only way to fix this would be revert to 3.1 where SELinux stuff wasn't implemented basically at all instead of having it dormant in systemd etc which seems to just cause issues :/  when are we getting proper full SELinux support for ports?18:34
vknechtmaybe have to add a custom policy for this file18:36
rinigusdeathmist: depends on a port. xperia tama has selinux support now19:09
deathmistrinigus: just a regular hybris-16.0 port (OnePlus 5 / cheeseburger)19:10
rinigusdeathmist: as far as I understood, it needs dbus/selinux related patch from aosp9 branch. then you need to integrate this patch policy into the used one. on xperia ports, we can do that by compiling aosp9 base as well. for other ports, selinux policy files will have to be adjusted differently19:15
vknechthere maybe it's just matter of having sfos recognizing the file as being the same selinux context as in los, maybe it's missing in some <whatever>_context, or maybe it should be added in /etc/selinux/<whatever>/context/files (just thinking alound, referering to )19:37
vknechtthis is a new field of headaches, reminds me CentOS 4 :-)19:38
piggzmal: is it possible to prevend dsme shutting down on low battery?20:16
mal@adampigg not sure, why do you want to do that=20:29
piggzmal: pinephone is plugged in on usb, tho charging doesnt seem to be working.  It is powered on USB-c, but it still wants to shut down shortly after bootup20:49
piggzmal: stopping dsme seems to have helped for now20:55
KabouikDoes the Pro¹ unlocks SFOS when opening the keyboard Mister_Magister?21:27
T42<elros34> don't know about pro but such a action is configurable in mce21:34
T42<adampigg> we may need such config, i cant remember off the top of my head, and mine is turned off atm22:37
spiiroinpiggz: the battery empty shutdown limit is configurable (in dsme, not mce) -> /etc/dsme/battery_levels.conf22:44
piggzspiiroin: can it be set negative ... my battery is at 0 :D22:45
spiiroinformat is apparently not that well documented (it matches already removed code ...), but I can dig details tomorrow if needed22:46
spiiroinzero is allowed, but mce might be reporting -1 if battery/charger probing fails ...22:46
piggzim leaving it on a slow charge over night to ry and revive it22:46
spiiroinpiggz: another thing you could try: move/rename/remove dsme batterytracker plugin -> dsme should still run, but whole battery tracking logic is disabled22:47
piggzok, thx22:48

Generated by 2.17.1 by Marius Gedminas - find it at!