Sunday, 2019-12-15

malyou only run that command once, also it has nothing to do with kernel00:00
malI mean you run the script only once00:00
T42<edp_17> I think after that script I ran this 'make -j$(nproc --all) hybris-hal'00:00
T42<edp_17> I didn't run the 'build_packages -c'00:00
deathmistdo that then, you can once again just install the RPMs from local repo after it's done if you don't want to make & install new image00:01
malyou misunderstood how things work, make hybris-hal is for android side build, the script affect the sailfish side adaptation repos00:01
T42<edp_17> I always re-bulit the whole thing.00:01
T42<elros34> so do you have all created symlinks in sparse/usr/libexec/droid-hybris/system/etc/init/?00:01
T42<edp_17> Yes, that is very much possible that I misunderstand how this work.00:01
malin $ANDROID_ROOT/hybris/droid-configs/parse/usr/libexec/droid-hybris/system/etc/init/00:01
T42<edp_17> I remember that when I ran that script I got a lots of 'already exist' messages, so seemingly everything was there.00:02
malyou only run make hybris-hal if you did anything to android side like did something to kernel, after that you alwasy have to run " -d"00:02
T42<edp_17> However I am happy to do a fresh start.00:02
malif you do something to $ANDROID_ROOT/hybris/droid-configs then you have to run " -c"00:03
T42<edp_17> @mal, I know that build_packages -d is enough but it was easier to run the whole thing and wait. Just tried to be on the safe side.00:03
malfresh start? why would do that, you just run the "rpm/dhd/helpers/ -c" now so the things that the script did will be included in next image00:04
T42<edp_17> This -c is a new thing, I have never done that. Probably that's why I had loads of issues.00:04
T42<edp_17> should I run this in platform or ubuntu chroot?00:04
malalso running without any parameters builds everything including what -c does00:05 is always run in platform_sdk00:05
malonly thing you do in ubuntu chroot is build the android side stuff using make hybris-hal (and later some other things also but not relevant now)00:05
T42<edp_17> Ok, so the previous 'build_packages -d' finished. Now I run it with -c.00:05
deathmist@edp_17 "-c" just packages all your droid-config repo changes to a few RPMs (in local repo) to be included in your final rootfs in new images, "-d" does same for droid-hal stuff like kernel etc00:06
malI really should finish the flow chart of the build process which tells what is needed when you do any changes00:06
malnow that we have the nice faq I could add it there00:07
T42<edp_17> You will probably laugh outloud but when I did my hammerhead port and needed to re-create the image, I re-compiled the kernel, re-built gstreamer, camera and everything. Always. :)00:07
malwhat you need to build depends on what you have changed00:07
deathmist@edp_17 once again you should be able to just grab the basic droid-config-$DEVICE RPM from local repo like you did before for droid-hal and install it on the device manually without needing a full new mic build & reflash on device :)00:08
T42<edp_17> I did it every time  independently what I changed. 😀00:08
malor even run the script on the device for testing (after changing the script to create the links to correct location)00:08
T42<edp_17> Ok, now the ...-c has also completed.00:08
malI will see about the flow chart to help people not build too many things00:10
T42<edp_17> I need to get used to this. And as you said, I was not sure how the things work when I wanted to include a new rpm, I re-run all commands.00:10
malyou should have asked here00:10
T42<edp_17> Now, I know a bit more. Thank you.00:10
T42<edp_17> I have tried to ask on IRC.00:11
T42<edp_17> Fortunately a guy from tmo has helped me so I was able to complete my hammerhead build. Then somebody told me that you are available on telegram, so I came here. And got help with my new port. 👍00:12
T42<edp_17> So, as I said the build_packages -c has completed. What's now?00:13
deathmist@edp_17 read my last message unless you want to build new mic image & reflash on device00:13
T42<edp_17> Yes, I scrolled up. Now I am building the image.00:14
T42<edp_17> Ok, instead of re-building the image do I need to install the rpms from droid-configs? All of them?00:17
deathmistjust the basic one, I checked that it contains your /usr/libexec init files00:18
T42<edp_17> Is it the basic one: droid-config-herolte-1-1.armv7hl.rpm ?00:20
deathmistbtw has anyone investigated why during mic builds the host Xorg keyboard map switches to en_US (seems like a setxkbmap command) or something? it's really annoying :/00:22
T42<edp_17> Copied, installed, rebooted. Still stuck on the Samsung logo until the screen is dimmed. (And after too.) I'll create a new journalctl.00:23
T42<edp_17> @mal, This time I didn't run this script:
T42<edp_17> Should I do it?00:27
T42<edp_17> Journalctl:
deathmistthe changes definitely have not taken any meaningful effect, show output of "ls -l $ANDROID_ROOT/hybris/droid-configs/sparse/usr/libexec/droid-hybris/system/etc/init/"00:29
T42<edp_17> No such file or directory.00:33
T42<edp_17> I remember that I deleted everything from that sparse directory when I refreshed the sub modules.00:33
T42<edp_17> I see now, so I ran that script that created which was necessary, then after the lots of problems I decided to start over and removed all changes from sparse including the libexec directory. That's why you see like I never ran that script.00:33
T42<edp_17> I said I am shooting in the dark. :)00:33
T42<edp_17> I guess not I need to run that script and build a new image.00:34
deathmistno need for new image still either, just run the script, make sure files are there with that ls command, run build_packages -c then install RPM & reboot the device00:34
T42<edp_17> This whole mess because of the mount parameters were wrong on my hos partition. 😭00:35
T42<edp_17> Ok, got that. Thanks.00:35
T42<edp_17> Script ran, libexec recreated in sparse/usr, build_packages -c completed, new base package installed, device rebooted. Still on logo.00:41
deathmistnew journal please :)  I'll take a look but I'm going to also get some sleep soon00:45
T42<edp_17> Yeah, I was looking how to change password to ssh because I need to reboot between sfos and recovery to get files in/out.00:46
T42<elros34> passwd nemo00:47
T42<elros34> but for getting journal you don't need recovery00:48
T42<edp_17> I'll try that.00:48
T42<edp_17> How can I transfer the journal to PC then?00:48
T42<elros34> just copy it from terminal window00:49
T42<edp_17> I am uploading the journal to pastebin now.00:49
deathmistI guess you could add "--no-pager" argument to journalctl so it displays everything at once00:49
T42<edp_17> Here it is:
T42<edp_17> I'll try that --no-pager. Quicker than rebooting to recovery.00:50
T42<edp_17> Thank you.00:50
deathmist@edp_17 are you sure you ran the ls command I sent previously? what does "ls -l /usr/libexec/droid-hybris/system/etc/init/" give you on the device? it may just be easier to build new image (if droid-config RPM actually has the init files) or modify the script and just run it on the device00:51
T42<elros34> do you really check log you post? I ask because nothing changed.00:51
T42<edp_17> Yes, I ran. Here is the output of the ls -l .. :
T42<edp_17> Yes, I check them but don't really know what to see there.00:54
T42<edp_17> See, this is why I re-ran all steps and re-built a new image. To avoid these issues.00:55
T42<edp_17> I meant issues when I am not sure if anything changed.00:55
deathmistwhat about that ls on device? if they're not there your RPM content did not change either00:56
T42<elros34> if you are not sure then just unpack that droid-config*rpm and check content00:56
T42<edp_17> I reboot into sfos, give me a seco.00:56
T42<edp_17> Only one line:00:57
T42<edp_17> -rw-r--r-- 1 root root 893 Dec  6 03:11 servicemanager.rc00:57
T42<edp_17> What about if I copy over the script to the device and run it there?00:57
deathmistcheck your droid-config-$DEVICE-*.armv7hl.rpm then, if you installed that one it doesn't have the changes either which makes no sense if you ran build_packages -c and the files are in the correct directory00:58
deathmistyou can also run the script on the device, just cut out "hybris/droid-configs/sparse" from the paths and it'll do it's thing01:00
T42<edp_17> I have checked the timestamp of those RPMs after I run the build_packages -c and all of them changed. Then I deleted the previous RPM file on the device and transferred the new one. Then installed.01:00
T42<edp_17> I ran the script on the device as root (removed the hybris/droid-config/sparse/ bit) but the ls -l.. command gives me the same output.01:11
T42<edp_17> I know why. Because I copied the script into /home/nemo/Downloads. It created the usr in there.01:12
T42<edp_17> Now I copied the script into / and ran there. The out put of the ls -l.. is the same as it was on host.01:13
T42谢晶婷 %lastname% was added by: 谢晶婷 %lastname%01:29
T42<edp_17> When I tried to start lipstick with 'systemctl --user restart lipstick', I got: 'Job for lipstick.service failed because a fatal signal was delivered to the control process. See "systemctl status lipstick.service" and "journalctl -xe" for details.'02:26
T42<edp_17> The 'journalctl -xe' gives me:
T42<edp_17> There is a problem with watchdog.02:29
SimdolSo, when you flash SailFish OS port over Lineage OS 16, can /data and /sdcard be preserved?02:43
SimdolCurious because A/B devices have possibility of dualbooting SailFish OS and linage, if that's true02:45
T42<elros34> sailfish in ports is unpacked to /data/.stowaways/sailfishos/ so all /data is preserved02:45
SimdolOh, that's neat.02:45
SimdolAnother question, from the research I know that ailen dalvik is not available for non-official devices. Is there a way to sideload Android apks on unofficial devices without using dalvik?02:47
SimdolOr can you hypothetically extract ailendalvik rpm by capturing from Jolla's server and flash it?02:48
T42<elros34> there is anbox which allows you to run android apps but it's forever wip state02:50
Simdoldoes it make sense to port anbox if that's the case?02:56
T42<edp_17> Good night everybody and thank you for the help!02:57
T42<elros34> Simdol: it's a mater of proper kernel config options, other packages are already built at obs and can be reused. I don't know the details, few people tired it03:03
Simdolhow does one write fixup-mountpoints for a/b device? there's two (a and b) for system partitions03:03
Simdolelros34: i see, thank you03:04
T42<elros34> just choose one slot and dont include _a/_b in fixup03:05
Simdolelros34: does it matter which slot i choose?03:05
T42<elros34> active one:)03:05
Simdoloh, that's tricky. so if i were to distribute the .zip image, does that also mean that the people flashing must switch over to active slot?03:06
T42<elros34> I am not sure what concern you, just choose slot a. Isn't that slot used by default?03:10
SimdolI don't think so, my understanding is that if you flash a rom from twrp, it switches active slot every time you flash03:13
T42<elros34> if you look at this channel logs, I think 2 days ago somebody mention about a/b  dualboot android and sfos03:19
Simdoldoes this look sensible to you?
Simdolnot sure if i should include ALIGN_TO_128k_1 and _203:23
T42<elros34> depends on how your fstab looks like.
Simdolokay, when i'm building i get this error: build/make/core/ error: FindEmulator: find: `tools/metalava/manual': No such file or directory03:34
Simdoldo i just clone metalava on build/tools?03:35
T42<elros34> did you notice my link? somebody already port sfos to enchilada03:35
Simdolelros34: i don't know how to navigate to that repository03:38
Simdolso i'm assuming sdm845 repository is for android source03:39
Simdolhow does one build this?03:40
T42<elros34> if you really want to build it instead installing ready to use image from author then grab local_manifests/enchilada.xml and repo sync, then follow hadk and faq03:44
Simdolelros34: i don't think there's an image built from the author that's available to public03:45
SimdolAnd the point of building myself was to familiarize myself with Android development, so that I can contribute to the author's repository. I don't have much knowledge on Android, but I do have quite a bit on GNU\Linux and programming, so I hope to help out.04:46
deathmist@edp_17 set CONFIG_WATCHDOG_NOWAYOUT=y in your defconfig, run "mka hybris-boot" and flash the new hybris-boot.img from out/target/product/$DEVICE/ on your boot partition. afterwards you should also give full .config from "find $ANDROID_ROOT/out/ -name .config"10:25
T42<edp_17> Hi @deathmist, thank you. I will do it.10:27
T42<edp_17> @deathmist, I set that flag, kernel re-compiled, flashed on device. .config is here:
T42<edp_17> Device is still on Samsung logo. Unfortunately I need to run now, so will come back later to check logs on the device. (I just wanted to quickly check whether I see the UI. 😀) Thank you!10:45
T42<elros34> dsme should take care of watchdog so just disable that android's watchdogd. It should be defined in /init*rc or somwhere in /system10:47
T42<edp_17> @Elros, thank you.10:48
T42<edp_17> I have found the 'service watchdogd /sbin/watchdogd 10 20' in 'init.samsungexynos8890.rc'11:15
T42<elros34> so comment it out in device and if it works then also  in $ANDROID_ROOT/device/, then make hybris-hal and rebuild droid-hal11:17
T42<elros34> you can also add "disabled" here
T42<edp_17> Can you suggest a user friendly editor for this? I tried vi but am very rubbish with that and don't want to mess up the file.11:32
T42<elros34> install nano if you like it or learn basics of vi: 'i' to enter edit mode, esc :wq to save and esc :q! if you mess something and don't want to save changes11:34
devnull-hi, got a alcatel idol-3 here with sialfish: [root@Sailfish nemo]# version11:35
devnull-Sailfish OS (Seitseminen)11:35
devnull- unfortunately the display is broken and I can't enter my pin, but I'm on the device via SSH. any idea how to fully reset the device ? I even can't flash with teamwin, because of unresponsive screenareas on the device.11:35
deathmistreset to factory defaults in just Sailfish or fully reinstall stock android or what? you should be able to use fastboot commands to flash/boot TWRP and use ADB if needed11:37
T42<edp_17> @Elros, ok I think I have messed up the file and saved. :( I restore the backup and retry. But later as need to run to a family event. Thank you.11:38
devnull-just a factor reset is enough11:40
devnull-but the recovery mode like on jolla phone is not working here with vol down and power up11:40
T42<elros34> @edp_17 just to make sure, unlikely watchdog has anything to your lack of gui11:43
devnull-in sailfish settings one can execute a factory reset, maybe some knows, how to do this from ssh ?12:00
vknechthmm, does factory reset work for community ports ? do we have official fimage equivalent ? never tried that actually12:12
vknechtdevnull-, hello, I think it should work from twrp, by removing /data/.stowaways/sailfishos and recreating this directory then extracting the tarball12:13
T42<elros34> there is something about factory reset in /sbin/preinit but I never tired it12:14
vknechteg. copy the tarball (extracted from the zip) to /data/sailfishos-rootfs.tar.bz2, then12:15
vknechttar --numeric-owner -xvjf /data/sailfishos-rootfs.tar.bz2 -C /data/.stowaways/sailfishos12:15
vknechtbut might need to use busybox instead of twrp's tar which is generally broken12:15
devnull-or is it enough to delete nemo home dir ?12:24
vknechtprobably not12:25
vknechthere's the busybox binary from idol3 build in case you need it :!heYAnQQQ!Y2jLTER-vRfXLP50kwdv1iyYOFC8uuBA2pPHSLJIhIY12:29
vknechtiirc, to use it instead of twrp's tar, copy it also to /data and use "busybox tar --numeric-owner [...]" command12:29
vknecht* /data/busybox tar [...]12:30
vknechtafter rebuilding libhybris for another revision, should we rebuild all middleware, only geoclue-providers-hybris & mce-plugin-libhybris, or also others ?12:45
vknechteg. gst-droid ?12:47
rinigusvknecht: but you don't have 'common' community port or do you? for lvm-based ports, I think it worked. for tama, when I tested, it looked to be working as expected13:25
vknechtrinigus, it was about idol3, not loire port13:25
rinigus(sorry, just realized you were replying)13:25
vknechtnp :)13:26
vknechtrinigus, can you provide some working tama journal log ? would like to compare, and possibly understand what goes wrong here13:41
rinigusvknech: sure.13:52
rinigusvknecht: . note that its sprinkled with selinux avc messages, as its gathered while selinux was permissive14:03
*** OhYash1 is now known as ohyash15:08
mautzoneHi everyone!15:35
mautzoneI'm havin problems building on OBS. I can not add the nemo:devel repo, when i click the edit repositories button nothing happens in my newly created subproject, in my other subproject it is working as expect. So, i can not build droid-hal, because nothing provides ubu-trusty.15:38
T42<elros34> have you tried edit it in meta tab? I think most peaople edit it there:
mautzoneelros34: Yes, i did this, but found an error in my droid-hal spec file, building started right now. Thanks!15:44
T42<elros34> btw: you should use a426857906dda89370a4b670f23d92a82e6f243b revison for libhybris for cm12 base15:45
mautzoneelros34: Why?15:49
T42<elros34> something is broken in libhybris when enable-trace is not enabled at least for cm11 and cm12 based. As result you will not get gui15:50
mautzoneelros34: Thanks!15:50
mautzoneI'm stuck again, nothing provides droid-hal-hammerhead-users for droid hal version.16:05
T42<elros34> have you tried uploading that missing package:P16:49
mautzoneNope, i never even heard that package name before :-D16:53
T42<elros34> it's quite new but should be built in your local repo16:54
mautzoneelros34: That des explain everything.16:55
T42<edp_17> Hi @mautzone, I'll send you that hammerhead-users package too. I have got that created but I didn't include earlier as it wasn't mentioned. 😊17:07
mautzoneedp_17: Thanks!17:13
deathmistmal: any clue about Sailfish OS doing something fishy in /data or /persist to always break WLAN on Android boot side on hybris-16.0 Pie based builds? this never was an issue for me on Oreo, check
deathmistit may be something SELinux related as booting droid image from recovery partition instead of boot (sets permissive selinux) makes WLAN work flawlessly again for me at least17:19
deathmistand this starts happening after booting Sailfish OS even once17:20
vknechtfiles getting relabeled ?17:20
vknechtmaybe try AUTORELABEL=0 in sfos' /etc/selinux/config ?17:22
mautzoneI can't build qt5-qpa-surfaceflinger-plugin on cm14.1 base. Getting this error: Anyone knows a solution?17:26
vknechtskip it17:26
deathmistvknecht: oooh maybe, I have no clue what that means but I suspect this may be it xD I'll definitely try tomorrow after full resetting everything to stock OOS first on my device17:27
T42<nitin_3> deathmist I haven't faced this issue17:30
deathmist@nitin_3 you've apparently enabled SELinux before which I've not done yet17:31
T42<nitin_3> I will test with it disabled17:33
T42<nitin_3> and get back to you17:33
deathmistvknecht: yikes, look at wlan_mac.bin xD
malmautzone: if you update rpm/dhd submodule then surfacefliger plugin is not built anymore17:38
*** OhYash1 is now known as ohyash19:09
mautzonemal: Thanks, after updating the submodules everything went fine, except for droid-hal-version, it complaints about ril-subscriptions.conf being in droid-configs and ofono. Should i delete my ril-subscriptions from sparse?19:55
monichmautzone: no, drop the one from ofono and use the one from sparse19:56
mautzonemonich: Should i uninstall ofono-configs-mer?19:57
monichmautzone: ignore it19:57
mautzoneThank you both!19:58
maldeathmist: do you have both of these lines
maloops meant mautzone19:58
deathmistok a bunch of files got unlabeled when running SELinux disabled Sailfish OS which broken WLAN on Android boots, tested and fixed by using "restorecon" on all affected files (context shown as "u:object_r:unlabeled:s0" in "ls -Z"), hopefully will fix it20:04
deathmistin particular I ran restorecon on /persist/wlan_mac.bin, mnt/vendor/persist/rfs/msm/mpss/server_check.txt & /vendor/rfs/msm/mpss/readwrite/server_check.txt which made the WLAN toggle in Android function normally again and finally stopped tftp-server spamming logcat like crazy20:09
deathmist^ s/mnt/\/mnt/20:11
mautzonemal: missed the obsoletes part in droid-configs/rpm/droid-config-hammerhead.spec. Rebuilding now.20:11
malmautzone: without that you have to manually uninstall the mer ofono config package to make build finish20:21
maland do it correct line sb2 ... zypper in droid-config-$DEVICE -ofono-configs-mer so both are handled in same command, having obsoletes makes life much easier20:22
deathmistmal: how do version OTAs work exactly btw? I know you can do the version --dup thing via cmdline, but what about GUI straight through Settings? will be nice to test once 3.2.1 released prob next week20:40
malno support for OTA via setting currently for community devices20:44
deathmistaw :/  it would bereally sweet to have implemented + the ability to just upgrade general adaptation packages simply from the pulley menu without having to enter some commands20:49
malI once made a separate app for udpates via UI but never released it because it wasn't perfect20:56
vknechtdeathmist, sfos-upgrade is an alternative to version --dup, tho still command line...
vknechtmanages a few things like the patch app, and disabling repo not recommended to have enabled when upgrading, as well as successice versio jump, and post upgrade cleanup21:27
vknechtdisabling the integrated gui in settings would be good, since it's no use21:29
mautzonemal: Thank you, the zypper command did it.21:42
mautzoneAfter rebuilding the kernel is it enough to just rebuild droid-hal-$DEVICE?22:25
T42<elros34> yes, droid-hal packages contains most of the stuff built in HABUILD22:31
mautzoneelros34: Thanks.22:34

Generated by 2.17.1 by Marius Gedminas - find it at!