Tuesday, 2019-12-31

sreehaxHey so i was trying to port SailfishOS to the Sony Xperia XZ following the HADK guide, however when i got to the step where i have to run breakfast it said command not found and indeed there was no breakfast command but i did do source build/envsetup.sh and other android build commands such as lunch were available04:53
sreehaxwhat could the issue be?04:54
masya_Trying to port for Xiaomi Mi A2 (jasmine_sprout, A/B-partitions). LOS-15.1. Stucking at vendor logo. At lsusb and dmesg - any mer devices. Journalctl - no entries.06:45
T42<Manish4586> @masya_ [Trying to port for Xiaomi Mi A2 (jasmine_sprou …], Give logs here06:46
T42<jash_gro> Someone working for mido ?06:47
T42<birdzhang> @jash_gro @adampigg06:52
masya_Remove from fixup-mountpoints b-slots and a-flags for A-slots. Flashing to a-slot. No effect.06:53
masya_Trees: device jasmine_sprout - https://github.com/LineageOS/android_device_xiaomi_jasmine_sprout06:57
masya_device wayne-common https://github.com/LineageOS/android_device_xiaomi_wayne-common06:57
T42<Manish4586> @masya_ [Trees: device jasmine_sprout - https://github. …], Use latest trees from github.com/xiaomi-sdm66006:58
T42<Manish4586> And check uvntd.rc06:58
masya_Kernel https://github.com/LineageOS/android_kernel_xiaomi_sdm66006:58
masya_https://github.com/xiaomi-sdm660/android_device_xiaomi_sdm660-common - which branch? Los-17.0?07:04
masya_But there are no hybris-17.0 branch07:05
T42<Manish4586> @masya_ [https://github.com/xiaomi-sdm660/android_devic …], Old07:09
T42<Manish4586> Which is los1607:09
masya_But https://github.com/xiaomi-sdm660/android_device_xiaomi_jasmine_sprout Old branch is for havoc, not los07:28
T42<Manish4586> @masya_ [But https://github.com/xiaomi-sdm660/android_d …], Convert07:29
T42<Daphne %lastname%> (Photo, 482x562) https://irc.thaodan.de/.imgstore/mNRutnKv1Z.png 👉联系message to :@Niokm09:35
T42<elros34> @masya_ do you build for hybris16? Are you sure this kernel was used to with your android base? it doesn't have 16 branch11:29
masya_No, I build for hybris-15.111:39
masya_Now I will try get trees and kernel from sdm660 for hybris-16.011:41
T42<elros34> wait, if it's a/b device, did you revert skip_initramfs support from your kernel?11:42
masya_No. In BoardConfig file?11:54
T42<elros34> in kernel: https://github.com/LineageOS/android_kernel_xiaomi_sdm660/commit/05f5cf60a4696fe63510581f530c8e8f74c9327b#diff-e37f0136aa3ffaf149b351f6a4c948e911:55
T42<Lukapanio> Anyone worked on karnak?13:30
T42<birdzhang> hybris 16.0 base, full dmesg https://paste.ubuntu.com/p/Xy8Y3R8Mxm/13:40
T42<birdzhang> gatekeeperd and vendor.ipacm services crash13:41
jwalckmal: I tried on the FP2 for two days now - working as fine as I'd say! This fairphone crashes heavy apps (browser, e-mail...) every now and then and reboots occationally, but it's been like this for a long time so I assume it's a hardware issue13:56
maljwalck: browser issues happen sometimes, some websites are terrible and the browser is a bit old14:11
maljwalck: I have also seen reboot but very rarely14:16
jwalckmal: mine is bordering on challenging to use (can run for a day or two fine, or reboot every 10 minutes). I may try revert this phone to lineage or FPOOS to verify that it is indeed a hardware issue but that's a task for another year:)14:19
maljwalck: ok, that doesn't sound normal, occacionally reboots are related to camera on my device14:20
malbut even then it happens very rarely14:20
maljwalck: if possible could you see what is in /proc/last_kmsg after such reboot?14:22
jwalckmal: I'll check that next time! I think today has been without reboots but if I use the browser more they're bound to come14:28
maljwalck: oh, if it's related to browser then it could be just out of memory killer misbehaving and killing some critical process14:29
malwhich it shouldn't do normally14:29
maljwalck: persistent journal logs could also help debugging the issue14:29
maljwalck: https://github.com/mer-hybris/hadk-faq/blob/master/README.rst#persistent-journalctl that way you can get journal log from previous boot also and it could tell if the reboot was due to some kernel issue or oom killer14:30
jwalckmal: it can come at any time, but as I said (memory) heavy applications are involved most of the times so memory killer is a good guess!14:55
jwalckthanks for the pointers for how to debug it, I'll add the persistent journalctl14:56
*** superpro1 is now known as superprower15:43
T42Moore %lastname% was added by: Moore %lastname%20:02
piggzfor info, remove and re-add the device, it adds more config21:42

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!