[02:56] <JasonD> Hi duflu, I managed to try another hdmi screen with lower than 1920x1080 res and had the same output as before with the command you gave me
[03:01] <duflu> JasonD: Still reports 1080p?
[03:01] <JasonD> yup
[03:02] <duflu> OK, thanks. I've been meaning to try and understand the code better. Our Android guy(s) have not been looking at bugs it seems so haven't got involved
[03:02] <JasonD> np
[06:50] <SebthreeBQM10HD> hi
[09:14] <zzarr> hello! I just read an article about ransomeware. Are there any thoughts on how to protect people som such things?
[09:14] <popey> On Ubuntu?
[09:15] <zzarr> yea
[09:15] <popey> Same precautions as on other platforms. Using a spam protection tool, not opening attachments in mails you don't recognise etc
[09:16] <zzarr> I know it's not a problem yet, but if Ubuntu grows (which it's doing and have done)
[09:16] <zzarr> yea, I though about apps
[09:17] <zzarr> are apps tested as it is right now somehow?
[09:17] <popey> On the phone?
[09:18] <zzarr> I mean before the app comes out in store
[09:18] <zzarr> automated tests
[09:18] <popey> There's some checks done, but the apps aren't tested as in they're not executed
[09:19] <popey> The checks are to ensure the apps comply with our store policies
[09:19] <popey> But we don't do any interrogation of the apps themselves.
[09:20] <zzarr> okey
[09:22] <zzarr> I saw a competition some time ago where 7 teams with there own super computer let a software analyze (and in some cases patch) apps (Android apps)
[09:22] <zzarr> at least one was able to patch the stage fright bug
[09:23] <zzarr> I though it would be cool if something like that was applied to the Ubuntu store :D
[09:25] <divis1969> Hi, I've finally synced the phablet-5.1.1_r36 branch and I'm trying to build aosp_mako target. Unfortunately build fails with errors: system/core/include/cutils/jstring.h:32:35: error: unknown type name ‘char16_t’. I'm building on ununtu 16.04 and I've noticed that the build is using host cc as a compiler. How can I fix that error?
[10:53] <javier4> divis1969, you have to set your toolchain inside build/envsetup.sh
[11:04] <divis1969> javier4: it is not clear why I should do this. I've followed the standard procedure (source build/envsetup.sh; lunch) and supposed build will succeed.
[11:05] <divis1969> I've found that system/core/include/cutils/jstring.h contains:
[11:05] <divis1969> #if __STDC_VERSION__ < 201112L && __cplusplus < 201103L
[11:05] <divis1969>   typedef uint16_t char16_t;
[11:05] <divis1969> #endif
[11:05] <javier4> probably the version of gcc shipped with your installed operating system has some problem.
[11:05] <divis1969> So, this compiler is supposed to have char16_t defined but it is not
[11:06] <divis1969> I'm trying to figure out the values of those __STDC_VERSION__ and __cplusplus
[11:06] <divis1969> but no success yet
[11:07] <divis1969> I suppose that the toolchain is modified by ubuntu-touch, Android is using toolchains from prebuilts/
[11:08] <javier4> divis1969, you can set your toolchain from prebuilts editing phablet/build/core/combo/HOST_linux-x86.mk
[11:11] <divis1969> Is it ok to use the prebuilts? I supposed this change (to use host cc) was made intentionally
[11:43] <javier4> I think it depends on your host OS and release.
[12:36] <mardy> willcooke: hi! just got your mail about MIR'ing of account-plugins
[12:37] <mardy> willcooke: some plugins are already in main
[12:38] <seb128> willcooke, mardy, sorry looks like a small bug in the script with packages in main with some binaries in universe, feel free to ignore that one
[12:38] <mardy> seb128: ok, thanks
[12:39] <seb128> mardy, since you are around, is that u-c-c-o-a bug when the fb view is too small and don't let you enter your credential on your todolist? seems one that would be nice to fix for yakkety
[12:43] <mardy> seb128: according to the comments, it might be already fixed: bug 1621139
[12:44] <seb128> mardy, hum, k, need to retest, that bug you showed is on the phone though but I guess the desktop one is the same
[12:45] <seb128> mardy, logging to google accounts also has an issue, when you try to scroll the view it becomes white/empty, but that might be one for chrisccoulson
[13:04] <willcooke> thanks mardy seb128
[13:06] <mardy> seb128: that's bug 1613670, feel free to confirm
[13:07] <seb128> mardy, thanks
[13:08] <zzarr> when will Ubuntu be ready for the masses?
[14:11] <divis1969> javier4: it looks like commit bd593d692 in the build/ is intentionally set tool prefix to /usr/bin (branch 5.1.1). And this obviously does not work for ubuntu 16.04 (or probably for my host gcc). I'm wondering what was the reason for this change...
[14:35] <mardy> Mirv: do you know any tricks to install qt 5.5 in yakkety? I'm manually downloading and installing packages with dpkg, but hitting walls all the time
[14:35] <mardy> Mirv: is there a way to do taht with apt? maybe by adding some ppa?
[15:14] <matv1> I got to see a demo for the HP elite X3 phone with continuum the other day from a HP guy
[15:15] <matv1> not bad. but I never realized you cant actualy do windows desktop-apps at all on those devices
[15:15] <matv1> and that will never happen either
[15:16] <matv1> also I grabbed his display screen from him using my BQ M10 :)
[15:17] <matv1> which posed some question using this in office envirmonts
[15:17] <matv1> at which they are primarilt aiming
[15:18] <matv1> pretty fun getting to pitt the Ubuntu against it :)
[15:36] <Mirv> mardy: so you would like to downgrade to 5.5? you'd need older versions of the binaries of ubuntu-ui-toolkit, qtmir, qtubuntu, unity8, gsettings-qt, ciborium, webbrowser-app (or a recompilation of them against 5.5)
[16:16] <divis1969> it looks like rootstock-touch-install is using recovery mode to create the ubuntu filesystem on the device. Does ubuntu-touch use "standard" android recovery? I did not find any changes in bootable/recovery
[16:18] <ogra_> no, it uses a very specific one that can handle the ubuntu OTAs
[16:20] <ogra_> rootstock-touch-install just needs to mount the partitions for unpacking tarballs though, that should work with any recovery ... but for proper operation and updates you want a proper ubuntu recovery
[16:21] <divis1969> One more question: rootstock-touch-install seems create a system.img in the /data (which is userdata partition typically). I'm wondering is it possible to create the userdata.img instead (i.e. with no need to deal with the handset) which will have all needed files (from the ubuntu rootfs and the android image)
[16:26] <divis1969> ogra_: I did not find any ubuntu-specific changes in bootable/recovery. Do you know details how this recovery (built according to porting guide) differs from vanilla android one?
[16:31] <ogra_> your build should downalod an initrd binary
[16:31] <ogra_> and put it inside the recovery.img it produces
[16:44] <divis1969> well, I see from build log it is placed into boot.img, but recovery.img seems do not have it
[22:34] <hindlemail> hello - Using some very simple QML - to show a ActivityIndicator working on the emunlator but doesn't show on my "Aquaris M10"
[22:34] <hindlemail> the QML is :
[22:34] <hindlemail> import Ubuntu.Components 1.1
[22:34] <hindlemail> Page { ActivityIndicator {id: activity; running: true; } }
[22:36] <hindlemail> on the emulator as expected I see a spinning 'thing' but nothing at all is display on the M10 tablet.
[22:41] <hindlemail> when running on the M10 I get this error message "file:///opt/click.ubuntu.com/applayouttest.tom/0.1/AppLayoutTest/Main.qml:3:8: QML ActivityIndicator: file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.2/ActivityIndicatorStyle.qml:24 Invalid property assignment: "implicitHeight" is a read-only property" which doesn't appear on the emunlator
[22:42] <hindlemail> so I guess its this bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1618007