[02:07] <ubptgbot> <F C> Artificial Intelligence of a virtual assistant for Ubuntu Touch written in C ++
[02:11] <ubptgbot> <UniversalSuperBox> @F C [Artificial Intelligence of a virtual assistant for Ubuntu Touch written in C ++], Sounds like a good idea, have you uploaded it on your personal GitHub or similar?
[02:16] <ubptgbot> <F C> Not at the moment, but I'm testing it on a Nexus 5
[02:18] <ubptgbot> <dohbee> you're referring to Mycroft?
[02:22] <ubptgbot> <F C> Not my assistant is based on the Google assistant
[02:37] <ubptgbot> <dohbee> why do you keep deleting your messages F ?
[03:09] <ubptgbot> <Fuseteam> @wayneTBT [Hi folks, can I open an ovpn file on UT?], no not currently, you can however manually edit settings via the vpn editor app in the open store
[04:01] <ubptgbot> Hermann Kirchdorfer was added by: Hermann Kirchdorfer
[05:22] <ubptgbot> <mofota> Hi everyone!
[05:23] <ubptgbot> <mofota> Thanks a lot UBports team for keeping up the great work!
[05:25] <ubptgbot> <mofota> & this awesome community
[06:32] <ubptgbot> <Christopher> yes thank you I've been using ubports on my nexus 5 for a long time
[06:32] <ubptgbot> <Christopher> it is great
[08:38] <ubptgbot> <TartanSpartan> Would Uadblock be compatible with the legacy browser's web engine, if the app were to be backported to Vivid?
[09:23] <ubptgbot> <Ingo_FP_Angel> uAdblock modifies the `/etc/hosts` file which means it afffects everything running on the phone that connects to the internet. … Or in short: yes it would also work in the legacy browser of vivid.
[09:31] <ubptgbot> <TartanSpartan> Could I apply the patch to the filemanually rather than have to backport the app?
[09:31] <ubptgbot> <TartanSpartan> [Edit] Could I apply the patch to the file manually rather than have to backport the app?
[09:33] <ubptgbot> <malditobastardo> Why are you using vivid?
[10:28] <ubptgbot> <TartanSpartan> I use Xenial on my Pro 5 (stable daily driver) and on my MX4 (devel device). But I have kept my M10 to Vivid for the time being. Why?
[10:30] <ubptgbot> <TartanSpartan> Well, saying this without wanting to ruffle any feathers, I don't think the Xenial experience is quite compelling enough for me to want to upgrade all of my devices to it. For example, if you compare the legacy browser to Morph, I think Morph introduced several regressions and frustrations. I say that in full knowledge that it confe
[10:30] <ubptgbot> rs more web security, and I accept the risk with legacy browser.
[10:31] <ubptgbot> <TartanSpartan> Also, the Libertine experience isn't quite as good on Xenial in several ways. Libertine works best on the go on a tablet rather than a phone, so it makes sense to keep it as functional as possible.
[10:32] <ubptgbot> <TartanSpartan> When those bugs have been patched, when Morph is up to par and when a couple of other apps match the Vivid experience, then I will be happy to upgrade.
[10:34] <ubptgbot> <TartanSpartan> I have a checklist in Talaan about the gaps that need to be closed. I should update it to see how close we're getting.
[10:36] <ubptgbot> <Javacookies> I definitely understand you, libertine/xmir is definitely more usable in vivid … and there are indeed notable issues in morph that isn't in oxide
[10:38] <ubptgbot> <YougoChats> libertine currently has two showstoppers for me: it opens every gui item in a new window, and it has a portrait/landscape problem.  … the new window thing can be tamed: https://forums.ubports.com/post/12957 … but so far i haven't seen improvement with the portrait/landscape input problem: https://github.com/ubports/libertine/issues/13
[10:40] <ubptgbot> <TartanSpartan> Right. Like VLC's menus are partially blocked from view. Among other things this means there is no way to set up SDL-powered video output, therefore VLC can't play videos on Xenial. I filed a bug report weeks ago but I don't think it has had any attention to date.
[10:54] <ubptgbot> <TuxThePenguin> How can I switch the onscreen keyboard to colemak? I have found 2 menus claiming to change the layout and one doesn't have alternative layouts
[11:14] <ubptgbot> <Fuseteam> i think you probably found the menus for the physical keyboard
[11:14] <ubptgbot> <TuxThePenguin> Ah that would make sense
[11:58] <ubptgbot> TheDragonn was added by: TheDragonn
[12:09] <ubptgbot> <TuxThePenguin> Wow teleports is nice
[12:09] <ubptgbot> <DC7IA> What is the best way to move to a new UBports device? My E4.5 is slowly dying.
[12:10] <ubptgbot> <TuxThePenguin> What is the current state of Ubuntu touch notifications?
[12:13] <ubptgbot> <Flohack> @TuxThePenguin [What is the current state of Ubuntu touch notifications?], They work xD
=== ecloud_wfh is now known as ecloud
[13:56] <ubptgbot> <mateosalta> @TartanSpartan [Could I apply the patch to the file manually rather than have to backport the ap …], yeah, just edit the hosts file
[13:58] <ubptgbot> <mateosalta> https://www.putorius.net/block-unwanted-advertisements-on.html
[13:59] <ubptgbot> <dohbee> @TuxThePenguin [How can I switch the onscreen keyboard to colemak? I have found 2 menus claiming …], there isn't such a layout for that. one would need to create a new layout for keyboard component, or add a feature to have multiple different layouts for each language somehow
[14:07] <ubptgbot> <DC7IA> @DC7IA [What is the best way to move to a new UBports device? My E4.5 is slowly dying.], (Could I just copy /home/phablet/* ?)
[14:08] <ubptgbot> <fredldotme> @DC7IA [(Could I just copy /home/phablet/* ?)], tar'ing /home/phablet would make sense
[14:09] <ubptgbot> <DC7IA> @fredldotme [tar'ing /home/phablet would make sense], How would I make sure nothing is writing there..?
[15:21] <ubptgbot> <TartanSpartan> @mateosalta [yeah, just edit the hosts file], Are there likely to be lots of differences between the file on a Xenial Pro 5 and a Vivid M10?
[15:22] <ubptgbot> <TartanSpartan> (besides the relevant Uadblock stuff of course)
[15:25] <ubptgbot> <dohbee> @TartanSpartan [Are there likely to be lots of differences between the file on a Xenial Pro 5 an …], no
[15:26] <ubptgbot> <dohbee> and well you just need to append stuff to the end of the file, not modify anything already there, i guess
[15:27] <ubptgbot> <dohbee> @TartanSpartan [Well, saying this without wanting to ruffle any feathers, I don't think the Xeni …], I guess you mean QtWebEngine vs Oxide here, as Morph itself I think doesn't really regress vs webbrowser-app
[15:27] <ubptgbot> <thedenomparkour> without nougat tree cant we build ubt?
[15:30] <ubptgbot> <dohbee> @thedenomparkour [without nougat tree cant we build ubt?], It's needed for Halium building right now yes. Oreo/Pie aren't usable yet. Please direct questions about Halium to https://t.me/halium as well. Thanks :)
[15:31] <ubptgbot> <thedenomparkour> already asked no response
[15:31] <ubptgbot> <dohbee> please be patient :)
[15:31] <ubptgbot> <thedenomparkour> ok
[16:15] <ubptgbot> <TartanSpartan> @dohbee [I guess you mean QtWebEngine vs Oxide here, as Morph itself I think doesn't real …], Yes I know, but the user experience is negatively affected either way.
[16:17] <ubptgbot> <TartanSpartan> Question: if mobile Firefox was ported to UT, that would be in no way reliant on QtWebEngine, correct?
[16:17] <ubptgbot> <mateosalta> tab preview, header scroll up, text selection
[16:18] <ubptgbot> <mateosalta> but the thing not crashing on video is worth all that missing 😄
[16:19] <ubptgbot> <mateosalta> there is a vivaldi build for arm, always wondered what it would take to run that
[16:50] <ubptgbot> <malditobastardo> it happened before jumping to xenial afaik
[16:54] <ubptgbot> <dohbee> newer Qt was also in ubports 1504 images as well; and that was also back in the time when all the unit tests for most everything was getting disabled in ubports builds
[16:54] <ubptgbot> <dohbee> so while oxide might have been affected, just blaming it outright doesn't make sense
[16:55] <ubptgbot> <dohbee> QtWebEngine is definitely not better than Oxide was when it was properly maintained and tested. which is why we have so many regressions there right now
[17:00] <ubptgbot> <dohbee> anyway, long road ahead and all that. we have plenty of things to fix/improve
[17:01] <ubptgbot> <malditobastardo> 🙂
[17:07] <ubptgbot> sausagii was added by: sausagii
[17:12] <ubptgbot> <sausagii> Hi there, … can anybody tell me about  the latest  devices  working with Ubuntu Touch?  … So far, I only read about the "promoted devices" on the website. Nexus 5 is pretty old isnn't it? Any tips or further information? … Thanks.
[17:14] <ubptgbot> erickporto86 was added by: erickporto86
[17:53] <ubptgbot> Am .... was added by: Am ....
[17:57] <ubptgbot> <TotalSonic> @sausagii [Hi there, … can anybody tell me about  the latest  devices  working with Ubuntu T …], PinePhone and Librem 5 should have UT support towards end of this year or beginning of 2020.  OnePlus One is a year more recent alternative to the Nexus 5 that works very well to UT.  If you can find a Meizu Pro 5 they are the most recent o
[17:57] <ubptgbot> f the supported phones and have the best integrated hardware experience in my opinion.
[17:58] <ubptgbot> <TotalSonic> @sausagii [Hi there, … can anybody tell me about  the latest  devices  working with Ubuntu T …], [Edit] PinePhone and Librem 5 should have UT support towards end of this year or beginning of 2020.  OnePlus One is a year more recent alternative to the Nexus 5 that works very well with UT.  If you can find a Meizu Pro 5 they are the most
[17:58] <ubptgbot>  recent of the supported phones and have the best integrated hardware experience in my opinion.
[18:01] <ubptgbot> <advocatux> @sausagii [Hi there, … can anybody tell me about  the latest  devices  working with Ubuntu T …], This is the current supported devices list https://devices.ubuntu-touch.io/
[18:03] <ubptgbot> <sausagii> Hi, thanks for the information. Seems that the Meizu Pro 5 is rather hard to find ... … From the list apparently the Nexus 5 works best. Is that true?
[18:12] <ubptgbot> <dohbee> why do people think age of device matters, if the OS works? only reasons age of device would really matters is if we required 64-bit SoCs, or if you must have radio chips that still get firmware fixes from mfgs (which honestly, is not terribly likely for most things anyway).
[18:16] <ubptgbot> <NotKit> @dohbee there are some possible reasons, like general availability or battery life
[18:17] <ubptgbot> <dohbee> those are also issues with newer devices too
[18:17] <ubptgbot> <NotKit> but most of it are psychological reasons
[18:17] <ubptgbot> <dohbee> yes, it was mostly a rhetorical question :P
[18:19] <ubptgbot> <dohbee> and well, fairphone 2 is also technically the newest currently supported device
[18:34] <ubptgbot> <mateosalta> @dohbee [QtWebEngine is definitely not better than Oxide was when it was properly maintai …], i wish we got to version 1.23 - i think they were implementing chromecast in it?
[18:35] <ubptgbot> <dohbee> @mateosalta [i wish we got to version 1.23 - i think they were implementing chromecast in it?], i don't recall that
[18:38] <ubptgbot> <TotalSonic> @dohbee [why do people think age of device matters, if the OS works? only reasons age of …], Why does age of the device matter to some people?  First - as mentioned it is a good indication of availability of units in good shape (e.g. battery life, cosmetics, buttons functioning correctly).  Next it is an indication of features - e.g. f
[18:38] <ubptgbot> aster CPU, more RAM, more storage, better display, better camera, USB-C connection instead of Micro, rapid charging.  In my experience direct experience in terms of desired usage the OnePlus One beat out the Nexus 5 (with the exception of the OPO's problems with camera zoom and flash), and the Meizu Pro 5 beats out both (with the exception of not g
[18:38] <ubptgbot> etting 4G - but for me HDSPA and 3G have proven to be very close to being as fast)  - which DOES correlate to device age.
[18:38] <ubptgbot> <TotalSonic> @dohbee [why do people think age of device matters, if the OS works? only reasons age of …], [Edit] Why does age of the device matter to some people?  First - as mentioned it is a good indication of availability of units in good shape (e.g. battery life, cosmetics, buttons functioning correctly).  Next it is an indication of features -
[18:38] <ubptgbot>  e.g. faster CPU, more RAM, more storage, better display, better camera, USB-C connection instead of Micro, rapid charging.  In my direct experience in terms of desired usage the OnePlus One beat out the Nexus 5 (with the exception of the OPO's problems with camera zoom and flash), and the Meizu Pro 5 beats out both (with the exception of not getti
[18:38] <ubptgbot> ng 4G - but for me HDSPA and 3G have proven to be very close to being as fast)  - which DOES correlate to device age.
[18:39] <ubptgbot> <dohbee> ask a rhetorical question, get rhetorical answers, i guess
[18:39] <ubptgbot> <TotalSonic> @dohbee [and well, fairphone 2 is also technically the newest currently supported device], noted!  It and the BQ stuff are the devices that I have no direct experience with - so forgot to mention it.
[18:40] <ubptgbot> <TotalSonic> @dohbee [ask a rhetorical question, get rhetorical answers, i guess], or - be careful of what you ask for.   :)  Perhaps <rhetorical> </rhetorical> tags would have helped.
[18:42] <ubptgbot> <TotalSonic> @sausagii [Hi, thanks for the information. Seems that the Meizu Pro 5 is rather hard to fin …], Nexus 5 is a solid device for UT.  OnePlus One has the advanages over it of more storage space, faster CPU, more RAM, larger display, and better video playback.  OPO's disadvantages are that the camera zoom and flash are currently not functi
[18:42] <ubptgbot> oning due to a difficult to fix bug.
[18:42] <ubptgbot> <TotalSonic> @sausagii [Hi, thanks for the information. Seems that the Meizu Pro 5 is rather hard to fin …], [Edit] Nexus 5 is a solid device for UT.  OnePlus One has the advantages over it of more storage space, faster CPU, more RAM, larger display, and better video playback.  OPO's disadvantages are that the camera zoom and flash are currently no
[18:42] <ubptgbot> t functioning due to a difficult to fix bug.
[18:44] <ubptgbot> <sausagii> It all depends on what you want to do with a device. There are always differences in hardware , therefore the initial question. Otherwise I am not against older hardware , on the contrary: old school stuff often offers more security when customizing it. … If on the Nexus 5 it works flawless/stable I'll probably go for that one.
[18:44] <ubptgbot> <dohbee> if you want a newer device, help work on ports :)
[18:45] <ubptgbot> <nocomp> Hi folks, did any of you succeed gettin discord working?
[18:46] <ubptgbot> <mateosalta> @dohbee [i don't recall that], hm, maybe not. there was some new feature i was looking for on the next two releases though.. maybe web push notifications?
[18:47] <ubptgbot> AzelGT was added by: AzelGT
[18:52] <ubptgbot> <dohbee> @mateosalta [hm, maybe not. there was some new feature i was looking for on the next two rele …], there was going to be media-hub integration iirc, but i don't recall anything beyond that. i don't think web notifications was in there. but doesn't really matter any more :)
[19:00] <ubptgbot> <TotalSonic> @TuxThePenguin [What is the current state of Ubuntu touch notifications?], you need to add your Ubuntu One account information (or create an account) in order to get notifications to work for Teleports.   Just go to System Settings -> Accounts -> Add Account
[19:57] <ubptgbot> Juliana Stewart was added by: Juliana Stewart
[20:06] <ubptgbot> <Fuseteam> @nocomp [Hi folks, did any of you succeed gettin discord working?], there was an open source project for a client, so far that lacks a maintainer
[20:07] <ubptgbot> <Fuseteam> @nocomp [Hi folks, did any of you succeed gettin discord working?], [Edit] there was an open source project for a client, so far that lacks a proper maintainer
[20:07] <ubptgbot> <Fuseteam> personally i have not been successfull to even get a build
[20:08] <ubptgbot> <mateosalta> @dohbee [there was going to be media-hub integration iirc, but i don't recall anything be …], ah, that was it fixed media hub
[20:08] <ubptgbot> <mateosalta> the others must have been dreams 😆
[20:10] <ubptgbot> <Fuseteam> ah so media hub wasn't fixed in oxide either
[20:13] <ubptgbot> <nocomp> Thxxxx
[20:15] <ubptgbot> <dohbee> @Fuseteam [ah so media hub wasn't fixed in oxide either], i think it was, just not in a version that was shipped on the phone yet
[20:32] <ubptgbot> <nocomp> Any recent to expect running up soon?
[20:38] <ubptgbot> <nocomp> Recent/ recent phone
[20:41] <ubptgbot> <TotalSonic> @nocomp [Any recent to expect running up soon?], yes, PinePhone https://www.pine64.org/pinephone/
[20:41] <ubptgbot> <TotalSonic> @nocomp [Any recent to expect running up soon?], and likely in 2020 - Librem 5 - https://puri.sm/products/librem-5/
[20:42] <ubptgbot> <nocomp> Pinephone s hardware is not very exciting, 1+1 is better no?
[20:43] <ubptgbot> <PhoenixLandPirate> Well it's inexpensive.
[20:44] <ubptgbot> <dohbee> then use a 1+1?
[20:44] <ubptgbot> <nocomp> Yep should be, cause it looks like sensors that nobody is using anymore
[20:44] <ubptgbot> <Lyokanthrope> Inexpensive and it supports display out which I'm massively excited about tbh
[20:44] <ubptgbot> <nocomp> I have my 1+1 bit i would prefer more recent phone
[20:45] <ubptgbot> <dohbee> there are other devices being ported via halium project too
[20:45] <ubptgbot> <dohbee> find a device there and help with the port
[20:45] <ubptgbot> <nocomp> If i yad the skills i would
[20:45] <ubptgbot> <nocomp> No doubts on that
[20:46] <ubptgbot> <sativista> There are two more with potential to be good devices! … https://www.fxtec.com/pro1/
[20:46] <ubptgbot> <sativista> and: … https://www.indiegogo.com/projects/cosmo-communicator/x/17213740#/
[20:46] <ubptgbot> <dohbee> if you can follow the instructions to get it flashed, then you can test and report issues; and you can of course also probably give money to the developers working on the ports. they need food/coffee/beer too
[20:47] <ubptgbot> <dohbee> let's not start listing off devices which we personally think it would be nice to have ports for
[20:47] <ubptgbot> <dohbee> the group would be a neverending stream of links to devices we can't currently support
[20:48] <ubptgbot> <nocomp> I agree
[20:48] <ubptgbot> <nocomp> It s going the right direction
[20:48] <ubptgbot> <nocomp> Huawei should step in
[20:48] <ubptgbot> <nocomp> They make great phones
[20:49] <ubptgbot> <TotalSonic> @nocomp [Pinephone s hardware is not very exciting, 1+1 is better no?], as an owner of both a OnePlus One and Meizu Pro 5 - I agree that PinePhone's specs aren't all that necessasirily exciting.  However - for those wanting a brand new phone that should offer ability to send to an external display, as well as offer a first step to a de
[20:49] <ubptgbot> vice using a non-Android firmware base - then PinePhone makes a nice option - and if successful could lead to a PinePhone 2 with more enticing feature specs.
[20:49] <ubptgbot> <nocomp> Would be awesome to have thz huawei camera on an up phone
[20:49] <ubptgbot> <nocomp> Agree @TotalSonic
[20:49] <ubptgbot> <TotalSonic> @nocomp [Would be awesome to have thz huawei camera on an up phone], any Huawei products would be very difficult to port due to their recent policies regarding unlocking their bootloaders
[20:50] <ubptgbot> <sativista> yeah! Sorry! … But just to let people know about this devices, because they are FOSS like, they will have unlock bootloaders and they will help developers who want to port OS to them! … But I won't post anymore!
[20:51] <ubptgbot> <TotalSonic> @dohbee [let's not start listing off devices which we personally think it would be nice t …], well - in the case of Planet Computing's products like the Cosmo Communicator - they have expressed interest and cooperation with getting UT ports going - and a port for UT is half done for their previous Gemini PDA
[20:51] <ubptgbot> <sativista> Yeah, they have!
[20:51] <ubptgbot> <dohbee> @TotalSonic [well - in the case of Planet Computing's products like the Cosmo Communicator - …], sure, but when every post is a preview of a web page, and just a link to some possible future device, it's very hard to follow along
[20:52] <ubptgbot> <nocomp> I ve sen somewhere this rpi based phone
[20:52] <ubptgbot> <nocomp> Can be fun
[20:52] <ubptgbot> <TotalSonic> true that - but I find Telegram doesn't make for easy "follow along" like the old usenet or regular forums do.
[20:53] <ubptgbot> <sativista> It's more feasible to port if the hardware people are involved, doesn't?
[20:54] <ubptgbot> <TotalSonic> @dohbee [sure, but when every post is a preview of a web page, and just a link to some po …], true that - but Telegram itself doesn't allow easy "follow along" like the old usenet or web based forums do.   Nice for free flowing chat though
[20:55] <ubptgbot> <dohbee> @TotalSonic [true that - but Telegram itself doesn't allow easy "follow along" like the old u …], unset/forums are a very different thing from real time chats. telegram is the latter, and it's easier to follow along when messages are brief and to the point, rather than overwhelmed with images/previews/etc… :)
[20:56] <ubptgbot> <TotalSonic> @dohbee [unset/forums are a very different thing from real time chats. telegram is the la …], well - the issue is it is hard to include a link without having a preview image pop up.
[20:56] <ubptgbot> <dohbee> @sativista [It's more feasible to port if the hardware people are involved, doesn't?], i think you're missing the point of my request to not go down the direction of "it would be nice to have this new phone supported" links
[20:57] <ubptgbot> <TotalSonic> @dohbee [i think you're missing the point of my request to not go down the direction of " …], I think the reason he mentioned them was that there had been some initial feelers put through for UT ports with the makers for both of them
[20:57] <ubptgbot> <dohbee> sure
[20:58] <ubptgbot> <sativista> @dohbee [i think you're missing the point of my request to not go down the direction of " …], Ok! I understood! … There is a way to put a link and not get a preview?
[20:58] <ubptgbot> <TotalSonic> Cosmo Communicator looks like it could be awesome - but I don't think there is anything in UT's code to accommodate the smaller back display screen - someone correct me if I am wrong on this.
[20:58] <ubptgbot> <dohbee> i don't know. but it is possible to state the names of the phones/makers without links :)
[20:58] <ubptgbot> <dohbee> @TotalSonic [Cosmo Communicator looks like it could be awesome - but I don't think there is a …], there is not
[20:59] <ubptgbot> <TotalSonic> @dohbee [there is not], thought so - so it would just be a blank screen then unless someone coded something specific for the device (which doesn't seem likely to happen to me)
[21:01] <ubptgbot> <dohbee> i mean, we should probably eventually support multiple internal screens on phones and such, and having them be for very different purposes; but we have enough problems with one screen for now :)
[21:05] <ubptgbot> <sativista> @dohbee [i don't know. but it is possible to state the names of the phones/makers without …], 👍👍👍