Saturday, 2018-08-18

Qiangong2I'm at the script of the hadk, but it always fails with "Installed but unpackaged files found"01:40
Qiangong2Only thing that could be it is this: "Can't open ./out/target/product/jfltetmo/vendor/ueventd.rc: No such file or directory at rpm/dhd/helpers/makeudev line 35, <> line 294."01:42
Qiangong2Any ideas?01:42
*** Sailor11178 is now known as rydare05:33
tmp64I modified device tree files as stated here
tmp64Now I can see backlight turning on and off when I press the pwr button05:55
tmp64But the screen is completely black05:56
tmp64Without dtsi mods, it just stays on the fastboot screen06:33
tmp64There is alson an error "no compositor; going to logical off" in mce log06:34
tmp64 /sys/class/graphics/fb0/msm_fb_panel_status says "dead" while in Android it says "alive"06:40
echo_saliki am having this error:
echo_salikthe error part is sayng this: Caused by: java.lang.IllegalArgumentException: Failed to load any of the given libraries: [conscrypt_openjdk_jni-linux-x86_64, conscrypt_openjdk_jni-linux-x86_64-fedora, conscrypt_openjdk_jni]08:32
echo_salikwhole error log in the link above08:32
echo_salikr0kk3rz: now i have posted the whole log...08:33
kimmolishould that even build any .apk?09:21
echo_salikkimmoli: i dont kno09:33
echo_salikhey all... anyone has the idea regarding the error?10:07
echo_salikSorry if someone posted the solution... my internet is disconnecting again and again...10:08
echo_salikoh just came to know about chat logs...10:14
malecho_salik: I always build android 8 based android side directly in ubuntu 18.04 not in HABUILD_SDK10:16
malthe error seems some java environment related issue10:17
echo_salikoh... so should i install openjdk in habuild_sdk?10:18
echo_salikor should i build it in ubuntu directly10:19
malhabuild has java already, not sure which version10:20
echo_salikopenjdk version "1.8.0_171"10:22
echo_salikOpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-2~14.04-b11)10:22
echo_salikOpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)10:22
echo_salikmal: so what should my next step be? install JDK on my ubuntu main or try to update in habuild_sdk?10:24
malecho_salik: which host os do you run?10:25
echo_salikLinux 4.15.0-29-generic #31~16.04.1-Ubuntu SMP Wed Jul 18 08:54:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux10:26
echo_salikKDE Neon with Ubuntu 16.04 base10:26
malmaybe try build on host then, only the hybris-hal part of course10:26
tmp64So, I fixed kernel panics and mce stall. Now I have problems with display.10:27
echo_salikok... so i should just install openjdk-8-jdk?10:27
echo_saliki dont have java on my system...10:27
malbuild need some java so yes10:28
echo_salikok... thanks mal!10:29
tmp641) With no kernel modifications screen only has fastboot text and ASUS logo. 2) Removing "qcom,cont-splash-enabled;" from *.dtsi shows black screen and sometimes I see backlight change when I press the power button10:29
tmp64I also get a composer error in journalctl -u mce10:30
tmp64no compositor; going to logical off10:30
maltmp64: what do you mean with no kernel modifications?10:33
tmp64mal: Sorry, didn't notice your message10:45
tmp64Without removing "qcom,cont-splash-enabled;" from *.dtsi in arch/arm64/boot/dtb/qcom10:45
tmp64I found that here:
echo_salikhey mal, i get the same error10:47
malecho_salik: maybe try disabling the broken package from your device repo, it should be defined there somewhere11:25
echo_salikmal: by device repo you mean that file in devices/xiaomi/rolex?11:46
malecho_salik: yes, something like that11:57
echo_salikmal: build succeeded when i disabled TimeService.apk from vendor/xiaomi/rolex/Android.mk13:37
echo_salikthanks mal!13:38
tmp64_So, what do I do if all I see on the screen is "Fastboot Mode !!!" and ASUS and Android logos?15:06
elros1I would say read faq-hadk, there is important note about 14.1 and no display debugging15:30
r0kk3rztmp64: how far did you get? has sfos booted properly and dhi completed15:32
tmp64r0kk3rz: I think so15:33
tmp64elros1: Yeah, I've just found it15:33
r0kk3rzalways good to check logs for androidy services failing and such15:34
tmp64Logcat says "logcat read failure"15:36
elros1do you have needed symlinks?15:37
tmp64The ones from "Notes on LOS14.1 Porting"? I should15:38
tmp64Checked it, I do15:38
tmp64Wait a sec, I have logd disabled in /system/bin15:40
tmp64Nope, no effect15:42
elros1so check droid-hal-init15:43
tmp64Active: active (running)15:45
tmp64init-done.service is stuck15:46
tmp64 /usr/bin/setprop sys.boot_completed 1 is stuck15:46
elros1it's always better to post whole logs15:47
tmp64strace setprop test 0
tmp64strace test_hwcomposer stops on the same line15:50
elros1so check journactl15:50
elros1and dmesg15:51
elros1ls -al  /usr/libexec/droid-hybris/system/etc/init/15:57
tmp64My symlinks are wrong15:57
elros1I knew it15:58
tmp64Yeah, my fault :) I was like "i am smart" and created them in android's adb shell15:59
r0kk3rz!seen Nokius16:02
merbotr0kk3rz: Nokius was last seen in #sailfishos-porters 2 weeks, 3 days, 20 hours, 23 minutes, and 14 seconds ago: <Nokius> r0kk3rz[m]: let me test16:02
tmp64test_hwcomposer is working!16:02
tmp64Thank you, elros1 and r0kk3rz16:04
tmp64Lipstick failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: hwcomposer, minimal, wayland-egl, wayland.16:06
tmp64When I run lipstick in console16:06
r0kk3rzyeah i think you dont want to do that16:07
tmp64Just wanted to check it16:07
r0kk3rztheres probably a bunch of env vars you need to pass to it16:08
r0kk3rzif test_hwcomposer works then setting up the config and rebooting should be enough16:08
tmp64I had fbdev in "/var/lib/environment/compositor/droid-hal-device.conf"16:09
elros1why fbdev?16:09
tmp64Changed it to hwcomposer16:09
tmp64For testing16:09
tmp64It's alive! :D16:10
vknechtwhat would it take to make this GUI OTA checker ? using a combination of libssu and/or libzypp and/or PackageKit I guess ? any thought or source of inspiration ?16:13
r0kk3rzvknecht: tbh its mostly just a http request16:15
vknechtah, for just for checking, yes probably... I was thinking about "updater", so doing the whole operation16:16
r0kk3rzah yeah16:17
r0kk3rzthats mostly just a matter of getting the right release number16:18
r0kk3rzi think there was an updatery thing that NeoChapay did for nemo that could be useful here16:18
vknechtI guess the http request should check the "revision" field of the repomd.xml ? I'll dig in nemomobile, thanks :)16:22
r0kk3rzanyone know how this anbox stuff is supposed to work?16:50
r0kk3rzmal: ?16:50
vknechtr0kk3rz, you mean how to run it ?16:53
r0kk3rzi have patches, and i have installed the thing16:55
vknecht those are my notes16:55
r0kk3rzthe service doesnt want to run16:55
vknechtmaybe the lines to comment in service file16:56
Yardanicowait anbox already works? can it run actual android apps already? :D17:00
r0kk3rzvknecht: aha! thanks17:00
vknechtyou're welcome :)17:01
r0kk3rzYardanico: depends on what you mean by run :)17:01
Yardanicor0kk3rz, well, apps like WhatsApp (yes, a lot of people still use it)17:02
r0kk3rzyeah... its too experimental for like, actual use17:03
r0kk3rzwell it worked once...17:21
vknechtyeah, have to restart service about every time you want to run an app17:22
r0kk3rzi rebooted the device and it still wont chooch17:23
r0kk3rzmal: if i want to change the build.prop in anbox, how does do?17:41
r0kk3rzhmm, i wonder if we can replace this anbox session manager with something more defaulty18:02
r0kk3rzah i see, we're way behind on actual anbox development18:05
r0kk3rzi see a bunch of recentish commits about wayland support for instance18:05
vknechtsounds interesting :)18:07
malr0kk3rz: put it to overlay folder19:01
malto correct place under there19:01
malr0kk3rz: my local version is much less behind upstream anbox19:02
r0kk3rzi noticed :)19:03
malr0kk3rz: once I finish the gnss support for android 8 I can hopefully do some anbox work again19:04
r0kk3rzyeah it kinda works19:06
r0kk3rzfixing the multiwindow stuff would be good19:06
malr0kk3rz: yep, that would be nice, there are some issues why we can't use the upstream version directly, it doesn't like pure wayland19:08
malsomething about buffer allocation etc19:08
r0kk3rzoh ok19:12
ohyash_how would sailfish work on a 512MB Ram tablet?19:21
ohyash_even bigger question. how can one port sailfish to a generic chinese device with no source available and especially no device tree19:22
r0kk3rzwith great difficulty19:23
ohyash_more like great annoyance for the experts here because I'd come up with hell lot of weird problems then19:24
ohyash_Might have to reconsider this plan19:24
*** ohyash_ is now known as OhYash19:25
TheKitOhYash, biggest issue is kernel19:27
TheKitsystemd won't boot without cgroups or devtmpfs support, workarounding this is pain19:28
OhYashTheKit, I think I got the kernel, its AllWinner A23 sun8i.
TheKitdoes it boot to Android with all the components supported?19:31
OhYashIt came with android. That works well. I haven't even rooted it yet, let alone trying this kernel.19:32
OhYashMost of the things are here
elros1OhYash: I make sfos for A33 so certainly it's possible to port it to A23 which has better kernel support20:39
elros1unfounately it wasn't smooth, there were some errors in logs about buffers count20:40
OhYashelros1, sounds good. And what did you do about the device tree and the vendor dir? Not reqiured?20:58
elros1I used a33 sdk: it contains everything like kernel, android tree and gcc. I just needed to adapt it little to my device20:59
OhYashoh, the sdk20:59
OhYashjust have to test the sdk to check if that runs (as such, android) as TheKit mentioned. and then I have you to ping when I have problems :D21:01
OhYashOh, btw you must be having the changes over SDK on your github right?21:01
elros1as I said perfromancee was poor so I didn't publish it (except kernel) but I think I have all changes21:03
OhYashno prob21:04
OhYashwhats your A33 device config tho?21:04
elros1here is kernel:
elros1few changes was needed but for example in a31 to make it boot with gui I had to add 2 lines of code21:05
elros1It's for android obviously21:06
OhYashalways wondering how do people modify the huge ass configs. I can see errors when they come, just never know what to do to fix it.21:08
OhYashmy A23 runs on a 512MB Ram. I expect worse performance.21:09
elros1with allwinner you have sys_config.fex which is like device tree so you can extract it from device and then enable needed drivers in kernel21:09
OhYashah, thanks looking into fex21:10
OhYashfound it I guess
elros1yes, but its device specific so you need to extrac it from you tablet and replace21:13
OhYashoh, ok21:17
Keij0After the latest update rotation broke on my port22:35
Keij0messwerk shows data from rotation sensor but the OS doesn't rotate the display22:36
elros1do you have hw-settings.ini ?22:39
Keij0what is the path to it?22:40
elros1example is in faq-hadk22:41
elros1also put in /etc/sensorfw/sensord.conf.d/22:41
Keij0kay, I'll do it tomorrow, is that something that got introduced in this update? It was working before22:43
elros1yes, it was introduced lately22:44

Generated by 2.17.1 by Marius Gedminas - find it at!