[00:21] <Acou_Bass> Has anyone noticed a worsening in battery life wwith ota-14? Fairly sure mines degraded :(
[01:15] <t-ask> Acou_Bass: I might look into it. Can you play videos without problems?
[01:57] <Acou_Bass> t-ask: Yeah videos work for me though they wont play in the scope (though thats never worked for me anyway )
[01:58] <t-ask> Acou_Bass: Did you download them with Youtube-dl, too?
[01:58] <Acou_Bass> no I just took a video with my camera to test it hehe
[02:00] <t-ask> Acou_Bass: I'm using Linux to download them and just put them on the phone. Since the OTA video playback is almost broken for me
[02:00] <Acou_Bass> hmm
[02:00] <t-ask> Tried mp4, mkv and webm without final success :(
[02:00] <Acou_Bass> weird
[02:01] <Acou_Bass> lemme see if I can grab some from my server and trst
[02:01] <t-ask> yes, very weired. With the OTA some videos only play audio with black sceeen
[02:01] <t-ask> all vides thumbnails are rendered fine in Gallery
[02:01] <t-ask> strange, really strange
[02:01] <t-ask> Gallery can obviously get a frame from the videos, but can't playback ...
[02:02] <t-ask> maybe I have to download them with a certain option or size eg.
[02:25] <Acou_Bass> t-ask: OK so mp4 worked for me but webm and mkv didnt
[02:25] <Acou_Bass> all 3 were done eith youtube-dl
[02:26] <t-ask> wihtout any special option, I guess.
[02:26] <Acou_Bass> the mp4 even played in the scope
[02:26] <t-ask> strange I have so many mp4 which don't work at all
[02:27] <t-ask> on the other hand, some of them work...
[02:27] <t-ask> even when downloaded them from the same playlist eg...
[02:27] <Acou_Bass> all thats in my youtube-dl config is prefer free formats
[02:29] <t-ask> Mmm
[02:30] <t-ask> Error is shown "Failure to connect with playback backend."
[02:31] <Acou_Bass> yeah I got that with a mkv however webm played sound with a blank video
[02:31] <Acou_Bass> and mp4 worked perfectly in both media player and scope
[02:31] <Acou_Bass> webm had no thumbnail yet mkv sid
[02:32] <Acou_Bass> did* odd
[02:36] <t-ask> I'm out of luck. MIght be another problem I have
[02:36] <t-ask> I downloaded the app "mediacodecs"
[02:36] <t-ask> starting it only lists Audio
[02:40] <t-ask> or file names are too long
[02:40] <Acou_Bass> hmm
[02:41] <t-ask> before the OTA I could play some of those videos. lets say 50%
[02:41] <t-ask> now it si 5-10% max :(
[02:42] <t-ask> this makes no sense to me
[02:45] <t-ask> anyways, I have to leave. I will ask tomorrow. Maybe nore devs are on eg.
[02:45] <t-ask> Acou_Bass: thanks for helping out :)
[02:47] <Acou_Bass> no worries :D
[02:47] <Acou_Bass> Ima mention mu battery issues too
[02:47] <Acou_Bass> ill test it for a couple days to make sure
[05:44] <JanC> I think high-bitrate videos might not work on a phone/tablet...?
[05:45] <JanC> maybe some high MPEG4 profiles not either
[08:00] <SebthreeBQM10HD> anyone around?
[08:39] <KrisJace> how to use SDL on Ubuntu Touch?
[08:39] <KrisJace> http://www.omgubuntu.co.uk/2014/02/mir-sdl-support
[08:40] <KrisJace> they say it works, but I tired 5 different games all crashed the phone
[08:40] <KrisJace> immediately upon starting
[08:40] <KrisJace> display went goes to shit and phone soon restarts
[08:40] <KrisJace> but it does work if ssh into the phone with x forwarding
[08:40] <KrisJace> not on mir though
[08:41] <KrisJace> I tried both X-Ubuntu-XMir-Enable=true and =false
[08:41] <KrisJace> the only difference is that with XMir enabled it only crashes the app, otherwise the entiore phone
[08:52] <duflu> KrisJace: We would like to fix that as soon as possible. Can you log a bug? https://bugs.launchpad.net/mir/+filebug
[08:53] <duflu> KrisJace: It's worth noting most of the development effort and real app testing for SDL has been on desktop (x86), and not the phone
[10:49] <vandenoever> are there currently ubuntu touch phones for sale? Aquaris M10 is out of stock
[13:22] <enthusi> where would I look if I was interessted in porting simple (own) things to the ubuntu-touch?
[14:14] <mterry> bfiller: btw snap launching in u8 should mostly work now.  So you can test apps in the real u8 env
[14:14] <mterry> You should download the snap from the silo, not the store though
[14:14] <mterry> Store u8 snap is lagging a bit, because of LP timeouts
[14:14] <bfiller> mterry, yeah noticed that last week after building the snap
[14:14] <mterry> bfiller: k
[14:15] <bfiller> mterry, most of our apps in the edge store use unity8 plug as well now
[14:16] <mterry> bfiller: calculator and clock don't (they're owned by ubuntucoredev, not canonical, but still)
[14:16] <bfiller> mterry, hmn, renato__ thought these were updated? ^^^
[14:17] <renato__> bfiller, let me re-check
[14:18] <renato__> mterry, which rev of clock app do you have?
[14:18] <mterry> renato__: 12
[14:19] <renato__> mterry, try to update the version on store is 19
[14:19] <mterry> renato__: hmm I did
[14:19] <mterry> let me try with more flags
[14:20] <mterry> renato__: ah.  You became a devmode snap
[14:20] <mterry> I'm guessing calculator did too...
[14:20] <renato__> mterry, yes, because of unity8 interface
[14:20] <mterry> ick got it
[14:21] <mterry> renato__: ok well great -- I'll play with these and update the unity8-snap-install script to pass --devmode
[14:22] <renato__> mterry, thanks,
[14:22] <renato__> mterry, ubuntu-docviewer-app is just wainting for approval to be publish on store
[14:28] <mterry> renato__: is webbrowser-app on the radar to be updated?  I still only see revision 1
[14:29] <renato__> mterry, oSoMoN is working on that. he can give us some status
[14:30] <oSoMoN> renato__, mterry: high on my list, will be done sometime this week
[14:31] <mterry> oSoMoN: cool, no rush on my side, just curious
[14:35] <mterry> renato__: do you know what the story is with the extra black window when launching a u8 snap?  tedg said it was a snap-side issue?
[14:36] <renato__> mterry, I know that in the past we need to launch the apps with --desktop_file_hint=unity8  because the real desktop file hint does not work
[14:36] <dobey> it happens becasue the snaps are u7 snaps, not u8 snaps
[14:36] <renato__> mterry, removing it should fix the problem I think
[14:37] <dobey> the --desktop-file-hint should probably be removed, but i doubt it is the problem
[14:37] <dobey> the empty black hole window is xmir
[14:37] <mterry> dobey: my understanding is that snaps can claim both and work natively in both.  But if you're saying that the snap is acting like a u7 snap in a u8 env, then I buy that
[14:39] <dobey> mterry: i still say it's a ual issue. the .desktop file says X-Ubuntu-Touch=true, and ual treats all "unity7" plugs as "x11" apps, when what the app runs on has nothing to do with unity7 itself
[14:40] <dobey> the "it can support both 'unity7' and 'unity8' interfaces" argument is a misnomer i think. because for snaps that declare both, do we show the same app twice, one that runs an xmir and one that doesn't?
[14:41] <tedg> I think we need to show it once, but we should use the "best" interface.
[14:41] <mterry> No, I think UAL just launches it differently
[14:41] <tedg> We need to clear the MIR_* variables when launching with XMir methinks. Perhaps some of the QT ones as well.
[14:42] <dobey> that is a recipe for disaster
[14:42] <tedg> I think it more comes down to "if the app declares both, it better do a good job of figuring things out"
[14:42] <tedg> I'd say that apps probably shouldn't declare both, because it's silly to carry all those extra libs, but we shouldn't disallow it.
[14:43] <dobey> i think we're ignoring the snapd-generated .desktop files, so we should prefer what the original .desktop file says, regardless of whether the interface is 'unity7' or 'unity8'
[14:44] <tedg> I think we have a firm way of confirming intent, magic undocumented keys in desktop files are not the way to go.
[14:46] <dobey> that might be true when snapd upstream actually has all the necessary changes, is deployed everywhere, and we don't have to have things manually approved in the store that require --devmode
[14:46] <dobey> i don't think that's true today
[14:47] <tedg> Sure, but I'm hoping it will be by say the end of Jan. So relaxing the rules won't help.
[14:47] <mterry> tedg: so is there guidance for app folks like renato__ to avoid the black window?  some shell script wedge to determine if it has real Mir or not?
[14:47] <tedg> In theory no one can declare unity8 right now anyway.
[14:47] <tedg> mterry: It should be if you have DISPLAY use X11, if not, use MIR_SOCKET.
[14:48] <tedg> mterry: In theory the Qt backend stuff should do that.
[14:48] <renato__> mterry, the app does not have control over that.
[14:48] <tedg> mterry: That's why I think we need to remove MIR_* because it might be checking for MIR_SOCKET first there.
[14:48] <mterry> got it
[14:49] <mterry> So the app *could* scrub its own environment.  But we can fix it once in UAL is what your saying
[14:49] <tedg> I think so, but right now that's just theory.
[14:49] <tedg> Let me try it.
[14:50] <mterry> "hold my beer"
[14:50]  * tedg wonders how mterry knew
[14:57] <aiyion> a/buffer 22
[14:57] <aiyion> sorry.
[19:55] <lehkeda> I have issue with booting ubuntu-phone , when my device load init of ubuntu-phone it reboots