| Umeaboy | Hi! | 01:40 |
|---|---|---|
| Umeaboy | How do I include the submodule directory droid-hal-version @ 1f5da44 in my droid-hal-version-zeroltexx repo? | 01:40 |
| Umeaboy | I can't find it when cloning the directory for jfltexx and I can see it's there. | 01:41 |
| Piggz_ | hmm, how to join mer-meeting withou a hash key | 07:58 |
| r0kk3rz | hash key? | 07:59 |
| r0kk3rz | oh right, your keyboard is broke | 07:59 |
| r0kk3rz | #### some free hashes to copy | 07:59 |
| Piggz_ | its ok, found gui to join adds hash symbol | 07:59 |
| Piggz_ | im on that bt keyboard case on my tablet | 08:00 |
| Piggz_ | its great otherwise | 08:00 |
| r0kk3rz | oh right | 08:00 |
| Piggz_ | real handy | 08:00 |
| luukert97 | Hello everyone! I'm a Sailfish OS user that is also interested in finding out how to port Sailfish OS. A question, how do you guys look to Treble by Google? Theoretically you can build one Sailfish image and run it on all Treble supported devices. This would open a huge market for aftermarket devices | 09:39 |
| luukert97 | Or do I understand it wrong? | 09:40 |
| r0kk3rz | with what we do i dont think we can do a 'one image to rule them all' type thing | 09:41 |
| r0kk3rz | for instance we dont use the android HAL for everything, and so those parts will still be device specific | 09:42 |
| r0kk3rz | but with any luck treble will minimise the amount of vendor specific hacks we need to integrate | 09:43 |
| luukert97 | Ah yeah okay so parts will be device specific. But wouldn't it give a huge kickstart to have a booting (but not fully functional) rom on supported devices? | 09:43 |
| r0kk3rz | sure, if we can get there | 09:43 |
| luukert97 | Sounds good | 09:45 |
| luukert97 | I'm asking this because I'm interested in porting Sailfish to my Google Pixel (first gen, my Nexus 5 was dying) and I wondered if it was very different from how to current porting guide works and/or if someone has made a attempt yet for Treble | 09:45 |
| luukert97 | I have coding experience (and with flashing roms and stuff) but haven't ported anything so far. | 09:45 |
| r0kk3rz | what lineageos is available for that? | 09:46 |
| luukert97 | I believe 14 and up till 15.1 (since it has treble). But also AOSP | 09:47 |
| r0kk3rz | you could try doing a 14 based port | 09:47 |
| luukert97 | 14.1, I misread it. Would that work you think? | 09:48 |
| r0kk3rz | yes i meant 14.1 | 09:48 |
| r0kk3rz | it should work | 09:48 |
| luukert97 | Ah okay nice. I'll try stuff out, hoping not to brick my Pixel :P | 09:49 |
| luukert97 | Thanks! | 09:50 |
| M4rtinK | I'd just add that having an "universal" Sailfish OS install image would IMHO be really good | 10:05 |
| M4rtinK | I'm involved in the Fedora release process and no way in hell would we get anything done if we had to make (not to say separately maintain) a custom image for every single PC/notebook/server type | 10:06 |
| M4rtinK | thankfully the PC-like BIOS/UEFI based x86 makes this possible and it's a huge win | 10:07 |
| M4rtinK | so fingers crossed a single image release can be achieved also for mobile Linux distros | 10:08 |
| r0kk3rz | yes obviously good thing is obviously good | 10:08 |
| luukert97 | Yeah, I was wondering if anyone has picked it up already. Since I've seen some Treble roms on XDA that run on all Treble devices | 10:12 |
| luukert97 | I've read the HADK and was really overwhelmed by all the stuff in there. Like I said I know programming and flashing roms, but this is way different than creating a Android app for example. | 10:14 |
| r0kk3rz | sure | 10:15 |
| r0kk3rz | porting operating systems is a whole other kettle of fish to creating apps | 10:15 |
| luukert97 | It certainly is. I thought since I've had quite some experiencing in developing all kinds of stuff (hardware prototypes, apps, backends etc) it wouldn't be that hard to learn | 10:17 |
| r0kk3rz | its not *that* hard, we can help you through most of it | 10:18 |
| r0kk3rz | these days we have quite a body of knowledge about how to do this | 10:18 |
| luukert97 | That would be great! :) Yeah I guess I first have to setup a Ubuntu environment with all the software since I'm using macOS now | 10:19 |
| r0kk3rz | yes that would be best | 10:20 |
| r0kk3rz | dualbooting is better than using VMs | 10:20 |
| luukert97 | Yeah I'll install Ubuntu on my desktop at home as dualboot. VM's are always a pain in the ass | 10:21 |
| r0kk3rz | the main issue is when your device wont boot, trying to futz with usb passthrough is just an extra complication you really dont want | 10:22 |
| luukert97 | Jup, it only makes things more complicated | 10:23 |
| luukert97 | I'm also wondering how the Android layer will work on Sailfish 3. Hopefully they use a new technique that also allows the porters to insert it into the community ports | 10:24 |
| r0kk3rz | perhaps we will find out once they actually invent it :) | 10:25 |
| luukert97 | While it would be awesome to use a phone without those apps, in reality people need banking and other essential apps | 10:25 |
| luukert97 | Gotta lunch, see you guys later | 10:27 |
| *** Nokius_ is now known as Nokius | 11:02 | |
| M4rtinK | r0kk3rz: actually, according to (IIRC) the previous meeting Jolla just got license of the Alien Dalvik source code from Miriad Group and will be maintaining/updating it themselves from now on | 11:07 |
| M4rtinK | including the the promised API level update in Sailfish OS 3 | 11:07 |
| r0kk3rz | i know | 11:08 |
| M4rtinK | so the rumors of switching the official Android emulation layer to Anbox or some other OSS solution proved unfounded AFAIK | 11:08 |
| M4rtinK | oh, ok :) | 11:08 |
| r0kk3rz | rumours? i dont know of any such rumours | 11:08 |
| M4rtinK | there have been some such guesses on TJC IIRC | 11:09 |
| Nokius | rumor / wish | 11:09 |
| Nokius | or I assume users like to see his switch | 11:09 |
| r0kk3rz | sure, some people wildly guess about all kinds of things | 11:09 |
| r0kk3rz | including myself :) | 11:09 |
| r0kk3rz | shifting to anbox would be a huge undertaking | 11:10 |
| r0kk3rz | nudging alien-dalvik to 5.1 compat might be simpler | 11:14 |
| M4rtinK | either way it's good that API level update is planned | 11:20 |
| M4rtinK | looking at the API version table: https://en.wikipedia.org/wiki/Android_version_history | 11:21 |
| M4rtinK | looks like 5.x is also already "unsupported" (whatever that means ?) and 6.x+ is "supported" | 11:22 |
| r0kk3rz | its not really about what goog supports | 11:22 |
| r0kk3rz | 5.1 is still the minimum version for a lot of apps | 11:22 |
| M4rtinK | looks like "support" is about security updates in this case, but I'm not sure how relevant is that for our case | 11:23 |
| M4rtinK | yeah, that looks like a good baseline for a while | 11:23 |
| r0kk3rz | i would consider that the 'minimum viable' update, if jolla can beat that then awesome | 11:24 |
| M4rtinK | IIRC one of the main issues was TLS 1.2 support | 11:25 |
| M4rtinK | IIRC the 4.4 series without google play blobs does not have that, which is becoming more of a problem by the day | 11:25 |
| r0kk3rz | eh, i would think the main issues for an app compat runtime is the ability to install apps | 11:26 |
| M4rtinK | as server side software starts requiring TLS 1.2 | 11:26 |
| r0kk3rz | jolla doesnt support google play | 11:27 |
| M4rtinK | I mean the need for TLS 1.2 will make app developers bump minimal API level to > 4.4 (> API 20) | 11:27 |
| M4rtinK | yep, so apps that don't use google play services will not run as they will start requiring a higher API level so they can get TLS 1.2 | 11:28 |
| M4rtinK | that's what I'm trying to say | 11:28 |
| r0kk3rz | i wasnt really concerned about the reason why, it was just a pattern i was noticing | 11:29 |
| M4rtinK | I'm sure there are other common reasons why app developers bump the API level, this can be just one of them | 11:30 |
| r0kk3rz | i dont think its unreasonable to drop support for devices from 2013 | 11:31 |
| T4 | <abhishek_0> 2.2 is out .. are the targets ready? | 20:08 |
| r0kk3rz | no? | 20:08 |
| T4 | <abhishek_0> Okay.. thanks | 20:09 |
| piggz_ | aww man, I have abunch of stuff to fix for my 2.2 roll out | 21:17 |
| piggz_ | been putting it off....seems i cant much longer! | 21:17 |
| r0kk3rz | i guess i should add another column to the hadk table of glory | 21:20 |
| mal | r0kk3rz: what column? fingerprint support? | 21:23 |
| piggz_ | marks > set > go ... porters working on fp sensor | 21:23 |
| r0kk3rz | mal: yup | 21:24 |
| mal | we need to check if that needs some build or are the packages generic | 21:24 |
| r0kk3rz | yeah we should talk to some jolla person about that | 21:25 |
| mal | r0kk3rz: changelog has package sailfish-fpd-slave-f5121 so it has a device specific part and we don't have sources | 21:27 |
| r0kk3rz | not yet at least | 21:27 |
| piggz_ | i wodner what that contains ... force install it and see if it works ;) | 21:34 |
| mal | piggz_: pretty sure it's built against the android fingerprint API | 21:35 |
| piggz_ | right .... i tried that once ... got as far as opening the device | 21:36 |
| piggz_ | :( | 21:36 |
| mal | piggz_: the same way as many of our other adaptation middleware | 21:36 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!