Friday, 2021-02-05

*** jrayhawk_ is now known as jrayhawk04:55
mighty17 it seems to be coz of symlinks but didnt we already do it on device.... still no ui :(05:04
* mighty17 sent a long message: < >05:13
mighty17this seems to be correct05:13
mighty17btw should i try using los 13 as a base as that is quite stable than las 1405:15
xmnStumbled onto this interesting review on sailfish Security, perhaps you folks find it worth watching.
xmnguessing full disk encryption should solve or prevent these recovery tactics05:54
mighty17i did this to make sfos
mighty17the 1st command was make but it went out of the terminal06:47
T42<nologo> Fwd from TotalSonic: "Etar" in the F-droid store seems to be a decent one, I was able to get it to sync with my NextCloud CalDav via Dav5x - testing "Volla OS" on the Volla since I can't find a carrier that can both LTE and phone calls without VoLTE here in the USA.06:47
mighty17well its still the same, there is no ui all i can see is backlight on when i tap the screen07:10
mighty17my /init.log
mighty17journalctl --no-page
mighty17last_kmsg once i rebooted to twrp
mighty17sorry for sending so many messsges i really want sailfishos to work and im so close07:32
T42<edp_17> @elros34 [@edp_17 false alarm so far everything works go …], Good news! Have you built SFOS 4 for your old device? Did you update glibc or used it from version 3.4?07:45
mighty17edp_17 any idea what's the error?07:48
T42<edp_17> mighty17: No, unfortunately. What you can try is masking ofono service and reboot:07:54
T42<edp_17> telnet to the device, then07:54
T42<edp_17> ln -s /dev/null /etc/systemd/system/ofono.service07:54
T42<edp_17> then reboot07:54
mighty17<T42 "<edp_17> mighty17: No, unfortuna"> Well it works properly but ig it isn't able to load the ui07:55
mighty17<T42 "<edp_17> ln -s /dev/null /etc/sy"> Okay I will try that l07:55
mighty17* Okay I will try that07:55
mighty17<T42 "<edp_17> mighty17: No, unfortuna"> What does masking ofno service mean tho?07:56
T42<edp_17> Don't loading the ofono service, so no calls/no sms/no data. As there are errors from ofono in logs better if we eliminate that for now.07:59
T42<edp_17> In this, at from line 585 clearly shows that lipstick failed to start because of gralloc module. I am not sure what gralloc is or does.08:02
mighty17<T42 "<edp_17> Don't loading the ofono"> that can be fixed later its a tablet noone calls with it lmao08:44
mighty17<T42 "<edp_17> In this https://pastebi"> that might actually be the real reason!! anyone knows a fix?08:45
mighty17pkcon refresh08:46
mighty17pkcon install lipstick-jolla-home-qt508:46
mighty17will this work?08:46
T42<edp_17> mighty17: What would you like to do?08:47
mighty17i just googled that lipstick ui failed and got that as an answer
T42<edp_17> If you read that, he had a working sfos on his device before he got this problem.08:50
T42<edp_17> Have you masked ofono, and rebooted?08:51
mighty17not yet booting to twrp removes sfos so i hv to reflash it :/08:53
mighty17is it coz of the old glibc ?08:55
mighty17edp_17 yes i masked ofno and rebooted still same thing09:14
T42<edp_17> mighty17: I don't think it is because of glibc.09:37
T42<edp_17> Did you say re-flashed sfos?09:38
mighty17<T42 "<edp_17> Did you say re-flashed "> Yes09:38
T42<edp_17> After that did you run the script that does the symlinks? (What Elros suggested.)09:38
mighty17<T42 "<edp_17> After that did you run "> I already did that during building sfos09:39
T42<edp_17> So, you applied those in build and re-generated a new sfos image and flashed that on device.09:39
T42<edp_17> I se.09:39
T42<edp_17> see09:39
mighty17<T42 "<edp_17> So, you applied those i"> Yes!09:40
T42<edp_17> And what does the journalctl says now when ofono is masked?09:42
mighty17but ofno isnt the problem right?09:47
mighty17<T42 "<edp_17> mighty17: I don't think"> it dosent hurt to try with sfos3.2.1.20 does it?09:58
mighty17i am gonna try with it now10:12
T42<elros34> @mighty17 finally you showed that symlinks works. Check what modules you have loaded (lsmod) and /usr/libexec/droid-hybris/system/bin/logcat10:25
mighty17okay lemme boot the device10:26
T42<elros34> @edp_17 glibc did not change but I updated repo anyway so repo exists and have rebuilt busybox-static10:26
mighty17elros34 did u see it said something something lipstick ui failed??10:27
T42<elros34> yes, logcat might be usefull to figure out  why10:28
T42<elros34> did you use fbdev in droid-hal-device?10:28
mighty17no its hwcomposer10:29
mighty17as in i reflased sfos in between....10:30
T42<elros34> Anybody have issue with /etc/profile.d/ in sailfish It reads /proc/(pid of sd-pam instead systems)/environ which has root:root permission thus it fails and env variables are not set.10:31
T42<elros34> systemd*10:31
T42<edp_17> @elros34 [@edp_17 glibc did not change but I updated rep …], Thanks! I'll start building 4.0 for my treltexx. 😃10:37
T42<edp_17> mighty17: Change hwcomposer to fbdev in the file I told you and reboot then get the journalctl.10:39
mighty17changed it now 1 min wait before journal10:48
mighty17<T42 "<elros34> @mighty17 finally you "> @elros3410:48
mighty17this is the logcat10:50
mighty17the journal edp_17
T42<edp_17> migthy17: the "logcat" you pasted is not logcat. Just run: /system/bin/logcat10:55
T42<edp_17> migthy17: you said masked ofono but in the journal there is still ofonod (crashing)10:56
mighty17<T42 "<edp_17> migthy17: you said mask"> i will do it again :/10:57
T42<edp_17> What does this say: systemctl status -l ofono10:58
mighty17wait i just rebooted10:58
T42<elros34> never saw this logcat error11:00
T42<elros34> Does /system/bin/logcat fails same way? Do you use same android base as hybris?11:01
mighty17<T42 "<edp_17> What does this say: sys"> `Active: inactive (dead)`11:01
mighty17<T42 "<elros34> Does /system/bin/logca"> what do you mean by `as hybris`11:02
T42<elros34> repo * -b hybris-1411:02
mighty1714.1 for both11:03
mighty17 the new journal after disabling ofno11:04
T42<edp_17> @elros34 : When you updated the sdk in Platform did you get these errors, and if so, what option you chose:
mighty17<T42 "<elros34> Does /system/bin/logca"> elros34 logcat read failure: No such file or directory11:07
mighty17<T42 "<edp_17> @elros34 : When you upd"> huh i never got any of those errors u mean right?11:08
T42<edp_17> Nope, it is not for targets or toolings. (I am not sure this step is necessary though but always done that when upgraded my local repo to a newer sfos release.)11:09
T42<elros34> @edp_17 not exactly, I guess your adaptation0 repo doesnt refresh11:10
mighty17i never updated the sdk it was a fresh install11:10
mighty17<T42 "<elros34> @edp_17 not exactly, I"> ya i get this error something about adaptation011:10
mighty17but that seems unrelated11:11
T42<elros34> @mighty17 about journal use --no-tail -f because you don't read the logs you post and they are useles (not full)11:12
T42<edp_17> @elros34 : Yeah I think so. I got this before those errors:
T42<edp_17> @elros34 [@mighty17 about journal use --no-tail -f becau …], My bad, I just said "get journalctl" but should have said "get journalctl -f —no-tail" 😃11:13
mighty17im sorry for not readint it :(11:14
T42<elros34> is that whole log? where is dmesg11:15
T42<elros34> Try to get logcat as soon as droid-hal-init starts in dmesg11:15
mighty17<T42 "<elros34> is that whole log? whe"> Yes I also include the command at top11:18
T42<edp_17> @elros34 [@edp_17 not exactly, I guess your adaptation0 …], How can I get my adaptation0 repo refreshed?11:22
T42<elros34> Sorry, I don't know11:23
mighty17this is dmesg11:23
mighty17droid-hal-init starts at 12 seconds after boot11:24
T42<elros34> is that all dmesg? is only 14s. What you have in /system/lib/modules? Do you even have /system/bin/logcat?11:27
T42<edp_17> @elros34 [Sorry, I don't know], Ok, no problem. Another question: should I update the SDK before or after I updated the tooling and target?11:28
mighty17/system/bin/logcat gives logcat read failure: No such file or directory11:28
mighty17sh-3.2# ls /system/lib/modules11:28
mighty17bcmdhd.ko               pvrsrvkm_sgx540_120.ko11:28
T42<edp_17> mighty17: Have you connected to the device with telnet or ssh?11:30
T42<elros34> try: unlink /dev/log then ln -s /dev/alog /dev/log and /system/bin/logcat again. Do you have same modules in /lib/modues/$(uname -r)/?11:30
mighty17<T42 "<elros34> is that all dmesg? is ">
mighty17not much more in dmesg11:31
mighty17<T42 "<edp_17> mighty17: Have you conn"> telnet11:31
mighty17<T42 "<elros34> try: unlink /dev/log t"> it still says logcat read failure: No such file or directory do i need to reboot?11:31
mighty17sh-3.2# /lib/modues/$(uname -r)/11:32
mighty17sh: /lib/modues/3.0.101-g67333f2574c-dirty/: No such file or directory11:32
T42<elros34> so you are missing kernel modules. Are they in other /lib/modules/directory? What did you change so now yourv logs are empty? Previously you had failure of lipstickinlog11:34
T42<W %lastname%> Hello. My sailfish does not work aliendalvik, I need the library. Does anyone know where to get it?11:34
mighty17<T42 "<elros34> so you are missing ker"> i changed nothing maybe ofno but its the same zip11:35
mighty17<T42 "<elros34> so you are missing ker"> there is no /lib/modules11:35
T42<elros34> what?11:35
mighty17<T42 "<elros34> so you are missing ker"> oh dayum the spelling was wrong11:36
mighty17this is output of ls /lib/modues/$(uname -r)/11:36
T42<elros34> are they loaded?lsmod11:37
mighty17<T42 "<elros34> are they loaded?lsmod"> i dont think they are loaded11:38
T42<elros34> why? You didn't add /etc/mod* files I told you yesterday or they fail when you modprobe them?11:39
mighty17elros34 what files?11:40
mighty17the hadk-faq thing?11:40
mighty17i added them during the build itself 😄11:40
T42<elros34> this file but your module is different so you need to ammend it. I wonder why is that, even /init* try to load the old one11:41
T42<elros34> I hope you didn't  mix cm12 and cm14 repos for device/11:42
mighty17oooh i forgot to add it :(11:44
mighty17<T42 "<elros34> I hope you didn't  mix"> i didnt use this repo at all i did everything from scratch11:44
T42<elros34> I meant $ANDROID_ROOT/device/* and kernl11:47
mighty17no no i used cm14.1 repos for them :D11:47
mighty17now what am i supposed to do?11:49
T42<elros34> Load mosules as I said but I am still not convinced you used same bases. Why would have  pvrsrvkm_sgx540_120.ko from lineage/cm  and from your current kernel11:58
T42<elros34> modules*11:59
mighty17<T42 "<elros34> Load mosules as I said">
mighty17<T42 "<elros34> Load mosules as I said"> How do I load modules in the device? Do I need to rebuild?12:03
mighty17@elros34 should i use cm13 as a base?\12:13
T42Mohamed %lastname% was added by: Mohamed %lastname%12:23
T42<elros34> how /init.espresso.rc looks like?12:26
mighty17 this is it12:28
mighty17@elros34 u still didnt tell me how to load those modules in device12:29
T42<elros34> I did yesterday, and today: add them same as in old droid-config repo in /etc/modules-load.d/*.conf12:31
mighty17<T42 "<elros34> I did yesterday, and t"> in the device itself?12:32
T42<elros34> if you want to rebuild whole image to add one file with 2 lines then do it otherwise on device. There is few minutes delay in your old journal until lipstick fail. Make sure not unit use by-name path in /usr/lib/systemd/system/*.mount12:33
mighty17yes i want to do it in device :D for that i need to make a new file where? there is no /modules-load.d12:35
* mighty17 sent a long message: < >12:37
mighty17see there is nothing in tat directory12:37
T42<edp_17> @elros34 : When I am trying to remove target, I get this:
T42<edp_17> Never seen this before.12:42
T42<edp_17> It says, target doesn't exist however, that acctually DOES exist.12:42
T42<elros34> @edp_17 few days ago in logs you can find same issue. You have installed busybox grep and few more probably on 3.4.0.x platform sdk12:44
T42<edp_17> mighty17: Then create a file in there like droid-hal-espresso3g.conf and list your modules in there.12:44
T42<edp_17> Thanks @elros3412:45
T42<elros34> @mighty17 do you use correct kernel? Based on device repo cm12 use different than cm1412:45
mighty17<T42 "<elros34> @mighty17 do you use c"> yes but the kernel should be same right? cm14 stores kernel in /ti/omap4 whereas cm12 stores in /samsung/espresso10 but the kernel is
T42<elros34> I didn't compare them but they use different repo12:47
T42<elros34> not just directory12:48
mighty17no? what repo did u find they use? android_kernel_ti_omap4?12:48
T42<elros34> yeah12:49
mighty17<T42 "<edp_17> mighty17: Then create a"> what should i add in there are the modules are different for cm12 and this one12:49
mighty17<T42 "<elros34> yeah"> well this is weird :/12:49
T42<elros34> So do you correct one (android_kernel_ti_omap4) or not?12:50
mighty17no i used android_kernel_samsung_espresso1012:50
T42<edp_17> @elros34 [@edp_17 few days ago in logs you can find same …], What I only find was an advise to remove then recreate the sdk. Is it the solution?12:52
T42<elros34> yes12:52
T42<edp_17> Thanks.12:52
mighty17<mighty17 "no i used android_kernel_samsung"> i dont think it makes much diff12:53
T42<elros34> @edp_17 they easiest one12:53
T42<elros34> @mighty17 I don't know  much they diff but quick look at  commits shows they are different12:54
mighty17so rebuild?12:55
mighty17also i should now work with 4.x toolchains?12:55
T42<edp_17> @elros34 [@edp_17 they easiest one], Okay. In that case I just simply delete the sdks, toolings and targets foders in mer and re-create them.12:55
* mighty17 sent a long message: < >12:56
mighty17but its still same only backlight12:56
T42<elros34> I do not see point in debugging  it further with mix up 12/14 sources12:56
mighty17ohkay i will rebuild but should i move with cm13 as it is much more stable than cm14.1 on daily use?12:57
mighty17and with what toolchain do you recommend?12:59
T42<elros34> I don't know. It is good idead to use wll working android base but on the other side hybris-13 is not used by many. About sofos release use same 3.4.0.x12:59
mighty17cm14 does work but i think cm13 is very more stable :) plus hybris13 doesnt need that symlinks hacks and stuff13:00
mighty17so its a good idea?13:01
mighty17ermmm @elros34 android_kernel_ti_omap4 seems to be bugged13:34
* mighty17 sent a long message: < >13:35
mighty17i get this error13:35
mighty17anyways i will now redo with hybris 13.0\13:40
mighty17@elros34 this kernel is tested to run with postmarketos should i use it?
mighty17 is adaptation0 repo bugged?13:57
Mister_MagisterDoes anyone know what software is responsible for handling .desktop files/xdg configuration and showing the "choose app to open with" pop up?13:59
T42<elros34> lipstick use launcher/OpenFileDialog.qml and libcontentaction as backend14:06
T42<elros34> btw IIRC your youtube app breaks that behavior by using ~.local/share//applications fot https mime handler which is not supported14:07
T42<elros34> @mighty no use that kernel which is defined in cm/lineage.dpenendencies file in your device repo while you switch to correct branch14:08
mighty17well that repo gives errors :/14:08
T42<elros34> @Mister_Magister her is exact code:
ThaodanIf you have a device that has a dtbo partition that might help you:
Mister_Magister@elros34 my app doesn't break anything14:16
Mister_Magisterbut thanks @elros3414:16
T42<elros34> Mister_Magister : sure it does. It breaks every x-scheme-handler/https  handlers which are in /usr/share/app14:17
ThaodanMaybe that is content for #sailfishos14:17
Mister_Magisterno it does not, it inserts itself into handling https and pop up is open14:17
T42<edp_17> Hi all, When I run the mic ( I get an error message: Unable to find package: patterns-sailfish-device-configuration-treltexx16:33
T42<edp_17> What's missing?16:33
T42<adampigg> the pattern names changed around 3.4/4.0, there is a whole new naming convention16:36
T42<edp_17> Yeah, I have found that .rpm in local-repo, but when tried to install with sb2, I got a bunch of conflicts.. I am not sure whether I should accept them or not.16:37
maldid you migrate to meta-packages?16:49
T42<edp_17> mal: Nope. I wasn't aware of that. I'll do that. Thanks.16:51
malPSA: all porters should migrate patterns to meta-packages before 4.0.1 builds
mighty17mal: for 4.0 will there be patches for kernel <3.10?17:30
mighty17@elros34 is this the solution to my issue?
mighty17plus it seems that los14 was really buggy :/17:34
malnot sure yet, I haven't tried 4.0.1 with fp2 yet18:23
mighty17ohk also which sfos version natively supported 3.0 kernel?18:24
mighty17ig its 3.2.x?18:33
malI think 3.0 kernel needs a patched glibc, 3.4 kernel at least worked still in sfos 3.4.0, needs testing in sfos 4.0.118:34
mighty17yes elros has a 2.28 glibc patch which seems to have worked for them18:35
mighty17also any fixes for libgbinder issue that comes during rpm/dhd/helpers/ --mw (fix rn is git checkout and build later)18:44
malmighty17: what issue does libgbinder have?19:45
T42<edp_17> mal: I already have built all packages for sfos 4.0. Is it enough to migrate patterns to meta-packages now or I should re-generate packages after the migration?21:53
maljust rebuild the config packages and in case you hadn't updated the droid-hal-version submodule then also rebuild that22:16
T42<edp_17> Thanks mal. I've updated all submodules before I built packages, do will only rebuild configs and then try to do the mic.22:19

Generated by 2.17.1 by Marius Gedminas - find it at!