Monday, 2019-08-19

lp35Hi all! I'm the author of I would like to discuss a bit about opportunities for a new device for the community with android support.11:25
* Mister_Magister there is no such thing as best smartphone11:26
* Mister_Magister there is always a bigger fish11:26
lp35yes of course, but I mean a device that is suitable for a large community such as Jolla's one.11:27
Mister_Magister"Unfortunately I now that driving this project alone is not possible today because this requires too much spare time"11:27
* Mister_Magister cries in me11:27
Mister_Magister5 projects like those at the same time are totally doable11:27
Mister_Magisterfor single person11:27
lp35What about the bus factor?11:28
Mister_Magisterthere are git and obs repos11:29
Mister_Magisterand i didn't died yet so11:29
lp35ok, so I guess you already ported some devices ?11:30
lp35which ones?11:31
Mister_Magisterdoes it matter. i just wanted to complain11:32
lp35k. What about something more constructive? You've got someone motivated here.11:33
r0kk3rzok, what do you want to do?11:34
Mister_Magisterlp35: just wanted to say that "requires too much spare time" and i'm doing 5x this so my free time is porting *cires in me*11:34
r0kk3rzthe 'with android support' sounds tough11:35
Mister_Magisterr0kk3rz: anbox was working, why11:35
lp35I want to poll the community for their need, and a device that could be "balanced" between different usages11:35
Mister_Magisteruntill mal left xd11:35
r0kk3rzi know workinf for you means not crashing11:36
Mister_Magisterlp35: doubt that will work11:36
r0kk3rzbut tbh it does crash a lot, so...11:36
lp35yes, anbox sound really promising, but I guess a big layer will miss between Sailfish & anbox, isn't it?11:36
Mister_Magisterr0kk3rz: it crashed on start for me11:36
Mister_Magisterlet's bring back sfdroid11:36
Mister_Magistersfdroid was working at least :P not great, tons of problems, but working :P11:37
lp35ok, I wasn't aware about sfdroid. It's not supported anymore?11:37
Mister_Magisterofcourse not11:38
Mister_Magisterjust proof of concept11:38
Mister_Magisterinb4 bring bacc apkenv xd11:38
lp35ok so the goal is to move from POC to daily usable bits.11:39
r0kk3rzfor android?11:39
Mister_Magisternot with sfdroid or anobx11:39
Mister_Magisterthat is whole big project on its own11:39
lp35my guess it's the strongest dependency with jolla dev team11:39
Mister_Magisterto get somewhat stable android support on ports11:40
lp35so that's why it couldn't be the project of 1 person :)11:40
Mister_Magisteri mean the android support on ports isn't there since yesterday it's since beginning i believe and no solution yet11:40
Mister_Magisterif only qualcomm allowed kvm11:41
lp35yes but efforts & poc has been made. What are the technical reason for stopping?11:41
Mister_Magisternot stopping11:41
r0kk3rztechnical reason? none11:42
r0kk3rzjust peoples interest11:42
Mister_Magisterit was there and it will be there11:42
r0kk3rzthis stuff just doesnt magically happen if its technically possible11:42
Mister_Magister^ +111:42
lp35r0kk3rz, what do u mean exactly? spending time on dev?11:43
r0kk3rzyes, someone needs to actually work on it11:43
r0kk3rzmal was, but he gets busy with other things11:44
Mister_Magisterr0kk3rz: reason is different11:44
Mister_Magisterconflict of interest11:44
lp35ok so was talking 'bout the bus factor, it's not really far from the reality :D11:44
Mister_Magisternot lack of time11:44
r0kk3rzthe reason why doesnt really matter, just he stopped for his own reasons :P11:44
Mister_Magisterr0kk3rz: but we konw reason xd11:45
lp35conflict of interest? what are they?11:45
Mister_Magisterlp35: mal became jolla employee11:45
r0kk3rzlp35: well if you want to pay someone to make this for us and run it as a real project then go for it11:45
Mister_Magisterthat should explain11:45
r0kk3rzotherwise its just people doing things for interest and fun11:45
r0kk3rzwhich change often11:46
* Mister_Magister sad Mister_Magister noises11:46
lp35ok so shall we think that jolla will do everything in their power to prevent anyone of adding android support on community port?11:47
r0kk3rzcertainly not11:47
lp35ok. Do you think it's doable to start the dev again?11:48
malnobody is trying to prevent that, it's obvious that employees cannot help with that either11:48
lp35do you know anyone motivated?11:48
lp35mal: thanks for the precision11:49
Mister_Magister"do you know anyone motivated?" see now you got to the point11:49
malmany people seem to want anbox but nobody is willing to spend time doing it11:49
lp35I do. But not alone.11:49
Mister_Magisterlp35: i wish life was this easy11:50
r0kk3rzwell, its a cross section of desire, skill, and time11:50
lp35Mister_Magister, it's incredible how pessimistic you are about life! Go get some time off the kb!11:51
r0kk3rzif you have these things, then start doing, if you need help then you can ask here11:51
Mister_Magisterlp35: if i wanted to do my ports with "i don't wanna do it alone" there would be no ports from me11:51
lp35my motivation come from teamwork :D11:51
r0kk3rzthen go play fortnite11:51
Mister_Magisterdestroyed xd11:52
r0kk3rzor like, soccer or something :)11:52
r0kk3rzyou wont be alone, we can help you understand stuff if you want to try with anbox11:52
Mister_Magistersee thats what i was talking about :P11:53
Mister_Magisteri for example don't care about android at all11:54
Mister_Magistereven more after debugging keymaster11:54
Mister_Magisterfucken keymaster11:54
lp35ok so for you developing code/open source project is just a matter of 1 person. I don't know how is the reality of open source project around sailfish, but you clearly don't spread the desire to help -_-11:54
malalso related to anbox, question is that do we want to use the custom way or try to make upstream anbox work in sailfish11:54
lp35mal: I think it's a political issue of Jolla11:55
Mister_Magisterlp35: preventing busfactor is pushing source to github11:56
Mister_Magisterside/opensource projects in small community don't work they way you think they do11:56
Mister_Magisteri think every port you see is work of single person asking others for help11:57
r0kk3rzlp35: what stops you from just starting work on it?11:57
Mister_Magister^ +1011:57
r0kk3rzif its a thing you want, then you need to make the thing :)11:57
Mister_Magisterthat's how life works11:57
r0kk3rzif you want a quick tour, or help getting started, then we can help you with that11:58
Mister_Magisterwith attitude "it takes too much time so i don't wanna spend my personal time but instead i want other people to spend their personal time to do thing i want" it won't work11:58
lp35r0kk3rz, k deal. But I have a longterm vision of this. I don't want spending my time developing something that will not get any support from any dev. Want to be sure to bet on the right horse.11:58
r0kk3rzso you want to be a manager?11:58
lp35why not.11:59
r0kk3rzlong term goals is fine, but they start short term11:59
r0kk3rzit sounds like you want to find someone and convince them to work for you for free11:59
r0kk3rzif so, good luck with that11:59
lp35ok, wasn't my goal12:00
Mister_Magisterlp35: well everything you said says otherwise :P12:01
r0kk3rzpeople with time and skill tend to have their own pet projects12:01
r0kk3rzso, if you have time and skill, then get stuck in12:01
lp35ok got it.12:01
r0kk3rzthe list of 'wouldnt it be nice if someone did this' is quite long12:02
lp35So I think the starting point of previous work is there?
r0kk3rzthere are some instructions for running anbox on a ported sailfish device12:03
r0kk3rzyou have a ported device?12:03
lp35not yet12:04
lp35not possible with a officialy supported device?12:04
lp35like JollaC?12:05
Mister_Magisteryou need to recompile kernel12:05
Mister_Magisternot saying it's not possible12:05
lp35I have the basics on kernel compilation. I have done this many time, but for x86 platforms. I'm a daily developer using buildroot, and already integrated some custom drivers in it12:07
r0kk3rzyeah, but this is not that simple for sailfish devices12:08
lp35what are the caveats?12:10
lp35drivers? blob? kernel version restrictions?12:10
Mister_Magister"kernel version restrictions?" here12:11
lp35is this restriction due to device vendor or sailfish os HAL?12:23
lp35(or both?)12:23
r0kk3rzwell, you need the exact code and build environment and pack the boot.img12:24
r0kk3rzstuff we do all the time when porting devices12:24
lp35r0kk3rz, what do you mean by exact code? Same code as vendor used to pack its android img?12:28
lp35and they doesn't provide this I guess... ^^12:29
lp35*they don't12:29
r0kk3rzjolla does, but getting the blobs and environment stuff may not be so easy12:30
r0kk3rzi think there is a guide on tjc about kernel compiling for jolla phone12:30
lp35ok so what would be the easiest way to kickstart? Try to do on my jollaC or try with a community ported device?12:36
r0kk3rzimo a community ported device12:37
r0kk3rzsome devices have all the required things done for anbox already, so you just flash the image12:37
lp35any suggestion?12:44
maljust mentioning that the sfdroid github has very old version of anbox, more recent versions are available in some other places12:49
masha11mal: Hello! Can I show you my logs? My device (griffin with cm 14.1) does not show GUI. How do I start debugging?12:58
Mister_Magisterlet me quote hadk-faq12:59
Mister_MagisterSo you booted your Sailfish OS? Congrats! No GUI? Oh dear :)12:59
masha11dmesg:, journalctl:, lipstick:, test_hwcomposer:
malmasha11: logcat missing13:12
Mister_Magistermal: in test_hwc13:13
lp35mal, of course I will cerry-pick/rebase on top of the latest version ;)13:15
masha11mal: logcat- ,lipstick-
lp35r0kk3rz, any device/doc resources for such community port?13:21
lp35r0kk3rz, I was refering to "some devices have all the required things done for anbox already, so you just flash the image" any suggestion in mind?13:32
r0kk3rzumm lets see, fp2, mido, scorpion13:34
r0kk3rzprobably a bunch of Mister_Magister's motos13:34
Mister_Magisternah i didn't port anbox13:35
r0kk3rzbut even if it didnt, you could probably ask the porter to enable the required flags and add the code commits13:35
r0kk3rzor of course do it yourself13:36
Mister_Magister>my motos are 3.4 or 3.1013:36
r0kk3rz3.10 can work13:36
r0kk3rzi think13:36
Mister_Magister3.4 too13:37
Mister_Magisterif you try hard enough13:37
Mister_Magisteri had problems with anbox on osprry13:37
albertus1mal: do you happen to have any new idea or suggestion for me to try with my issue of MIC failing with "repo problem: pattern:jolla-configuration-h3113-1-1.noarch requires droid-config-h3113-bluez5, but this requirement cannot be provided" [...], where editing the .ks file with only the one package didn't produce an error?13:41
Mister_Magisteralbertus1: show dcd13:42
albertus1what's that?13:44
albertus1I hope these are what you're looking for, because I don't know `dcd` and don't know what particular config (and from where) I should pull otherwise: (Jolla-@RELEASE@-h3113-@ARCH@.ks), (hybris/droid-configs/patterns/jolla-hw-adaptation-pioneer.yaml), (hybris/droid-configs/13:50
Mister_Magisterdroid-configs repo13:51
albertus1sorry, I think I need a bit more verbose instructions. I'm new to this practice and followed this guide without understanding or looking into every detail
r0kk3rzthen you probably missed a build step13:58
r0kk3rzrebuild the configs and mw13:59
albertus1i.e., chapter 7 of HADK pdf?14:01
albertus1(or rather the corresponding "do instead" portion from the build guide)14:04
albertus1again, running into "cannot remove mesa to build libhybris", which seemed to be related to an old submodule in the git repository: (as pointed out by @elros34 on Aug 11: )14:13
albertus1I will build that manually again and then skip it14:13
r0kk3rzthe last two lines of the 'do instead' in chapter 7 is probably enough to start with14:13
r0kk3rzand make sure it all builds properly of course14:14
albertus1or should I try to update the git submodule manually?14:17
r0kk3rzid leave the code as is14:17
r0kk3rzuntil you're sure you're doing the build process correctly14:18
albertus1but it always produces that error after building libhybris14:18
r0kk3rzmaybe bump it then, i would hope these repos would be maintained though14:19
malchannel logs have instruction how to remove mesa manually, or more correctly how to install libhybris manually14:21
albertus1this is the repo that wasn't updated after the commit in droid-hal-device, mentioned above:
albertus1otherwise, I couldn't be getting that particular error anyway, because it was removed and had a "new way" for "mesa >= 19"14:29
malalbertus1: try running "sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in libhybris" which then should ask you to remove mesa14:35
malbut indeed the submodule in the droid-hal repo should be updated at some point14:36
malalbertus1: if you want you can update the submodule and make a pull request to the repo14:50
albertus1maybe tonight when I'm home, my mobile connection is quite slow here14:56
vknechtalbertus1, it could be that you have to comment out these two lines which obsolete encsfa stuff:
malthat's a good idea15:22
lp35Mister_Magister, motoG4 is the most recent device that has been ported?16:33
lp35looking for buying one of those to start porting anbox.16:33
vknechtlp35, vince/redmi note 5+ is probably a good bet, since its maintainer (birdzhang) also maintains the most advanced (afaik) anbox fork
vknecht*anbox fork for sfos16:47
vknechtalthough it should work on any device with required defconfig mods, overlay fs support and a few other patches16:49
vknechtand here's his OBS repo to install:
Mister_Magisterlp35: most recent is pro117:01
Mister_Magisterit's not even out xd17:01
lp35pro1 is nice but screen is too big ^^17:03
lp35and too expensive17:03
r0kk3rzanything with a recentish version of android should be fine17:14
vknechtwould be nice if tapping the 4 corners also disabled the tips ;-)18:23
Unbegriffhello, i am attempting to build an image for my zl1 device. Reading the pdf I notice it strongly suggest to flash the stock rom to the device. I got rid of it long ago for LOS and i never loocked back. Is there a way i could start from a LOS base? what dificulties would i encounter compared to the suggested method.18:37
r0kk3rzflashing LOS is fine18:39
r0kk3rzits mostly about making sure you have a well working device18:39
Unbegriffnice, it means i have green light to try. Thanks my dude.18:40
albertus1when building audioflingerglue (make -j$(nproc --all) $(external/droidmedia/ $PORT_ARCH $(gettargetarch)) $(external/audioflingerglue/ $PORT_ARCH $(gettargetarch))). is it correct that I receive lots of messages indicating "VNDK Abi broken"? it still says "build completed successfully" in the end... but it's quite a lot of these ABI warnings18:44
malthose should not be a problem18:50
malas long as build was successful18:50
albertus1okay. I'm not exactly a systems programmer, so I can't tell, but it just sounds a bit scary. let's see if the rebuilding from config and mw gets me to a more successful `mic` eventually18:53
electro575hi all19:02
albertus1is it a sign of anomaly that `rpm/dhd/helpers/ --configs` does not "fail with a non-critical Exception AttributeError: "'NoneType... error." like HADK pdf chapter 8.4 says?19:37
albertus1and bumped into the same problem again: Warning[08/19 19:41:07] : repo problem: pattern:jolla-configuration-h3113-1-1.noarch requires droid-config-h3113-bluez5, but this requirement cannot be provided, not installable providers: droid-config-h3113-bluez5-1-1.armv7hl[adaptation-community-h3113-]19:41
albertus1so no use in re-doing everything from building config and mw19:42
vknechtalbertus1, did you comment the Obsolete lines mentioned previously ?19:48
albertus1I'm not sure what you mean by obsolete lines19:50
vknechtthese two lines in :
albertus1no, I must have missed that discussion19:51
albertus1ah, thanks19:52
albertus1I read it on the public log that you were addressing me while I was away, sorry19:52
vknechtafter commenting them, resume with --configs19:52
vknechtno problem19:52
albertus1indeed I had to skip building the qt-qpa-surfaceflinger because it failed19:53
albertus1do I have to re-build the ks file after that?19:57
albertus1or is enough?19:57
vknechtgenerally, better get newer ks when changing droid-config19:58
vknecht(still generally) and always process pattern before a new local build19:59
vknechtthose don't cost much19:59
albertus1to be honest, I asked too late, went with the "old" .ks file and now it already looks different20:00
albertus1the stdout, I mean20:00
vknechtit's probably ok20:00
albertus1seems it didn't run into the error any more, so maybe you're on to something here :)20:00
vknechtif it ends without error, you're good :-)20:00
albertus1getting excited again to be close to having a flashable image20:00
albertus1will still have to go through backflashing my xperia xa2 from android 9.0 to 8.1 or something, via windows, but first things first20:03
albertus1Error <repo>[08/19 20:03:17] : Could not run transaction.20:04
albertus1whatever that means20:04
albertus1it doesn't say what transaction20:04
vknechtafaik the backflashing from 9 to 8 is not needed anymore20:06
vknechtfor the transaction issue, this doesn't look familiar to me, but maybe try getting new KS and regenerate patterns20:07
albertus1to no avail, unfortunately20:13
vknechthmm, dbus changes make me think about recent secure lock-down changes in sfos, but dunno how that relates to a local build ; maybe some submodule upgrade or downgrade is needed20:16
malthose look very strange20:18
vknechtmaybe need some mic cache clearing ?20:24
albertus1I'll happily try out any command sequence you tell me...20:36
vknechtI can't say, just testing OTA'ing to on my dear idol3 daily driver, and didn't see anything like that ; when I try it for loire, maybe I'll get that too but saying more atm would be pure speculation20:40
vknechtand I guess Mal is on it ;-)20:40
vknechtmy precious booted this OTA \o/20:44
* vknecht hopes it will work to wake him tomorrow in the morning20:45
malvknecht: very odd, I just built an image using platform sdk (well just updated to it) and it worked fine20:58
vknechtso, maybe some submodule revision thing ? for idol3 I updated both dhd and dhc to master/HEAD21:00
vknechtor maybe his pfsdk is not as up-to-date21:05
vknechtI'll try it with loire soon™21:08
vknechtgood night :-)21:08
malvknecht: very strange, I do see the same folder provided by both packages that cause the conflict but it still builds fine21:09
malso what is different in our installations21:09
albertus1if only I knew.... going to bed now, too21:46

Generated by 2.17.1 by Marius Gedminas - find it at!