[05:41] <silvarion> Hello, just testing if this channel works before going to bed
[05:41] <silvarion> Tomorrow I'll be back to chat a little bit about porting ubuntu-touch to the Sony Xperia Z
[05:42] <silvarion> Blessings for everyone!
[07:00] <zzarr> hello! will ota-13 be built on another version of Ubuntu? (other then 15.04)
[07:13] <yakaar> Bonjour à tous, j'ai un gros soucis, un ami a fais malencontreusement tombé mon portable aquaris E4.5, l'écran est brisé, mais le téléphone est encore allumé, mais en  veille. Le tactile n'est plus fonctionnel, que faire ??
[07:20] <zzarr> yakaar, English please
[07:25] <yakaar> Sorry, I forgot, my mobile has its screen broken and no function is working, I want to change my screen how to find another??
[07:30] <duflu> yakaar: First ask the point of sale if it's covered under warranty. Usually the answer is no, but ask there first. Second go to any regular phone shop/repairer and they should be able to get a replacement screen for you eventually. I can see they can be sourced unofficially on eBay etc.
[07:42] <zzarr> duflu, do you know the answer to my question?
[07:43] <duflu> zzarr: Good question. I don't know
[07:43] <duflu> zzarr: Our plan is to move phones to 16.04 as a base. But that might take longer
[07:43] <zzarr> okey
[07:44] <duflu> I believe the 'stable' channel is still vivid (15.04) as a core, but overlayed with the latest Ubuntu Touch
[07:45] <zzarr> what qt version?
[07:46] <zzarr> I wonder, if I wanted to use Qt 5.7 (or 5.8 when it comes), would be possible to use in a snap package
[07:53] <kaisoz> hi
[07:56] <kvmmm> So I'm reading, Ubuntu for Ubuntu-phone is the exact same OS as full Ubuntu, just with some GUI configurations to make it work nicely on a phone?
[07:56] <kvmmm> So I can run any Ubuntu software on the phone?
[07:59] <zzarr> kvmmm, it's experimental yet but yes
[08:00] <kvmmm> ok, cool. So what about something like... KVM and Whonix?
[08:02] <zzarr> it's called libertine, it uses XMir
[08:03] <sil2100> Ubuntu touch has some differences from regular Ubuntu, but the base system is built from the same parts
[08:05] <zzarr> I have tried Firefox and GIMP on my phone and it works
[10:56] <Mirv> zzarr: stable is Qt 5.4, staging channels are Qt 5.6 (well, soon anyway). 5.6 is the upstream LTS version so the next stable will be based on that.
[10:56] <Mirv> (staging = 16.04)
[10:57] <Mirv> 16.04 will be needed for the snap support (15.04 has the older click format), but I'm uncertain what kind of snaps can be used. certainly it would be possible to bundle newer Qt in a snap, but the system would use what's testsed to be stable, that is Qt 5.6
[11:03] <zzarr> thanks Mirv
[11:04] <zzarr> Mirv, if I successfully built an application in Qt 5.5.1, would I be able to run it on my phone?
[11:04] <zzarr> (OTA-12)
[11:08] <Mirv> zzarr: maybe, most applications use the Qt public ABI that is at least forward compatible, often also backwards compatible
[11:08] <Mirv> there weren't too many new functions in 5.5
[11:09] <zzarr> I know
[11:09] <zzarr> okey
[11:09] <zzarr> thanks
[11:11] <zzarr> I installed the 5.5.1 overlay in an schroot
[11:15] <zzarr> how ever the kit remains on 5.4, how can I "tell it" to use 5.5.1?
[11:31] <REAPer61616> Hi!
[11:32] <REAPer61616> Can someone tell me if is there ubuntu touch based on android 6.0.1?
[11:33] <REAPer61616> means availible source
[12:11] <robinhero> hi guys! Please +1 these bug reports if you are also affected:
[12:11] <robinhero> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573193
[12:11] <robinhero> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1609719
[13:17] <kaisoz> hi mimecar
[13:17] <mimecar> good evening kaisoz
[13:59] <jgdx> mterry, hey, any progress on the uss datetime issue?
[14:00] <mterry> jgdx: no, as I said, it's on the bottom of my priority list right now -- doing MIRs to get u8 stack into yakkety right now
[14:00] <jgdx> mterry, ack
[14:23] <Mirv> hmm, if I have an obsolete "ubtd.mzanetti_shareplugin_0.3" in my Share dialog, where would I remove traces of it? it's no longer installed, as it got upgraded to 0.4 which shows in the dialog too with a better name and an icon
[14:24] <Mirv> I tried grepping .[a-z]* but didn't find anything useful sounding to clean
[14:24] <tedg> mariogrip: hey, mhall119 mentioned that you might have a nexdock as well. What device are you connecting to it?
[14:26] <Mirv> oh, the fix is called "reboot"
[14:30] <mariogrip> tedg: Yes, we will support any Ubuntu touch and Android devices, we are also looking into Ios but it seems like its too locked down for us
[14:30] <tedg> mariogrip: Sure, I was curious which Ubuntu touch devices you were using.
[14:31] <mariogrip> tedg: sorry, that was to another person, (copy paste fail)
[14:31] <tedg> mariogrip: The N4 works, but it's.... old hardware...
[14:31] <mariogrip> tedg, nexus 5 :)
[14:32] <mariogrip> maybe an miracast dongle, so i can try Oneplus one and Fairphone 2
[14:33] <tedg> mariogrip: Ah, interesting, I don't know using miracast would be great.
[14:33] <tedg> mariogrip: Didn't know that the N5 had external display
[14:34] <mariogrip> yeah, but the nexus 5 has slimport so that should work just fine
[14:34] <tedg> mariogrip: Do you know if the OPO 3 has slimport?
[14:34] <tedg> That's what I *really* want to work :-)
[14:34] <mariogrip> and that i fixed bluetooth it should be perfect
[14:34] <mariogrip> opo 3, nope
[14:34]  * tedg drools over 6GB of RAM
[14:35] <mariogrip> buuut, i got something in mind so we can use the usb port to transfer hdmi
[14:35] <tedg> I thought there was some standard there for USB-C, no?
[14:36] <mariogrip> yes it is usb-c but it's still usb 2.0
[14:36] <mariogrip> so, it's just the port that is different
[14:38] <tedg> Ah, yeah.
[14:40] <dobey> yeah it's kind of messed up that made it 2.0 on usb-c
[14:40] <dobey> that is totally not standard
[17:36] <taiebot> awe: I have a network related question. Hope it will be clear enough. I just want to make sure that UT has nothing to do with this.  I am currently changing phone provider and i am in the process of transferring my phone number. I have given my PAC code to my new provider (Three) and I am currently having issues with this. I can call with my number on three (Correctly transferred) but all the call received are still tra
[17:42] <awe> taiebot, your last message was cut off
[17:42] <awe> what phone are you using?
[17:42] <taiebot> awe: Nexus 4
[17:43] <awe> and do you have another phone you could try, to ensure it's not UT?
[17:43] <awe> so you can make outgoing calls, but what's happening with incoming?
[17:43] <awe> that's the part that was cutoff
[17:43] <taiebot> awe: they all get cut off.
[17:44] <taiebot> awe: repasting the end of the message
[17:44] <taiebot> awe: . I had a quick chat with a representative of three which explained to me that there could be some problems with some config files and they would try to fix it within 24h. In case they do not manage to solve this and its due to the phone what do you recommend me to do?  Would you like a debug of some sorts? Hopefully it is at their end. Thank you for your answer.
[17:45] <taiebot> awe: it is certainly at their end
[17:45] <awe> what do you mean "cut off"?
[17:45] <awe> you call from another phone, and it never starts ringing?
[17:46] <awe> and doesn't go to VM either?
[17:46] <taiebot> but all the call received are still transferred to my old provider (not correctly transferred ) and therefore are dropped because i am using the sim from three on my phone.
[17:46] <awe> yea, that sounds like nothing to do with UT
[17:46] <awe> again, do you have another phone you can test the SIM in to confirm?
[17:47] <awe> if you can confirm it works in another phone, then it's time to file a bug, collect logs, ...
[17:47] <awe> but right now, I don't hear enough evidence from you to warrant starting all that
[17:48] <awe> it really sounds like # porting didn't fully take effect
[17:48] <taiebot> awe: cool thank you, yes i can try on another phone. My concern if it's a sim configuration it could get right into the other phone and when i put it back to UT it 's all ok
[17:54] <awe> taiebot, the only thing UT touches on a SIM is a file used for message-waiting indication.  If the SIM is from three, it should just work
[17:59] <taiebot> awe: Ok just wanted to make sure i am not sure this has been done very often on an ubuntu touch and just wanted to make sure i did not had a weird bug
[18:08] <dobey> taiebot: it worked fine for me when i had to get a new SIM from my provider. was same provider, but still had to assign a diff number and then port the number over, but when i first enabled an ubuntu phone i had to do that
[18:14] <taiebot> dobey: Ok thanks makes me less worried
[18:15] <cariveri> hi. since last update the ubuntu-phones apps like Telegram dont notify anymore. is this known? can I do anything about it?
[18:16] <dobey> cariveri: are you logged in to U1 in System Settings -> Accounts?
[18:21] <cariveri> dobey: yes.
[18:26] <dobey> cariveri: if you go to updates panel does it ask you to log in again?
[18:27] <cariveri> no
[18:30] <dobey> hmm, ok. don't know why you wouldn't be getting push notifications then. maybe check logs in ~/.cache/ to see if something's going on. not sure exactly where ubuntu-push-client logs are in there, but should be in there somewhere
[19:55] <gihel> anyone has the same problem with sms notifications ? it doesn't ring after a while, the phone vibrate but I don't get any sound
[19:56] <gihel> I thought it was related to radio apps that interfered with something, but even withour using radio apps this bug occurs
[19:56] <gihel> without*
[19:57] <gihel> after rebooting the phone, it's ok for a  while
[20:03] <dobey> gihel: i'd suggest filing a bug about that
[20:45] <TheKit> does anyone know if Android should still run with libhybris's bionic TLS slot shift patch applied?
[21:13] <gihel> ok dobey, will do some more tests and I will file a bug this week end, thank you