[04:10] <wawan> y.
[07:11] <Colin_> hello ? Um.. What does the message which printed on fastboot " get_partition_name() fail" when flashing system.img means ?
[07:15] <duflu> Colin_: Don't know. All I can tell is that it's an Android error message and not coming from any Ubuntu code. It's obviously caused by Ubuntu code mind you
[07:15] <duflu> Colin_: Which device?
[07:15] <Colin_> Meizu mx2
[07:15] <Colin_> Meizu Mx4
[07:15] <Colin_> sry
[07:17] <duflu> Colin_: The MX4 requires you to provide a recovery .img file on the command line of ubuntu-device-flash. Did you do that?
[07:17] <duflu> If not it will fail
[07:17] <Colin_> I tried , but I can't flash recovery partition >.<
[07:18] <Colin_> "partition 'recovery' not support flash"
[07:18] <duflu> Colin_: Yes, you will need to download this and pass it as the recovery image option: http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
[07:19] <duflu> Flashing will fail otherwise. This extra step is only required on the Meizu and BQ phones.
[07:19] <duflu> Colin_: https://wiki.ubuntu.com/QATeam/ChannelsToFlash
[07:20] <Colin_> thx for your help :D
[07:21] <duflu> No problem. I remember being stuck on the same problem
[11:05] <Colin_> hello?A qusetion: Does ubuntu touch can install on the phone by fastboot? I means command "fastboot flash system system.img" ? I tried to flash a "system.img" but it said "DOWNLOAD ERROR". I made that "system.img" with those steps (https://wiki.ubuntu.com/Touch/Deploying#Deploying_your_own_full_images).
[12:57] <Colin_> um... Meizu customer service said "Mx4 ubuntu's recovery partition not support flash isn't abnormal"... Is that true?
[13:04] <ogra_> it supports flashing via ubuntu-device-flash
[13:05] <ogra_> (and only that)
[13:23] <Colin_> uh.... Neither fastboot & ubuntu-device-flash can flash recovery.img O.O why ? But I can flash both boot.img & system.img.
[13:27] <ogra_> Colin_, and you followed the instructions for recovery.img files with ubuntu-device-flash ?
[13:28] <Colin_> "--recovery-image recovery.img" ?
[13:28] <ogra_> and --bootstrap
[13:28] <ogra_> and also have the device in bootloader mode
[13:28] <Colin_> yes
[13:29] <Colin_> yeah...I did it in  bootloader mode....
[13:30] <ogra_> well, that should work i think
[13:30] <Colin_> Q.Q
[13:31] <Colin_> so Any other method to install ubuntu touch? Such as create a system.img and flash in?
[13:32] <ogra_> no, system..img sits as img file inside a partition, it isnt used like in android
[13:32] <anpok_> Colin_: it fails during flash?
[13:32] <Colin_> It can't start flash >.<
[13:32] <anpok_> as in usb connection lost..
[13:33] <Colin_> no... I can flash android...
[13:34] <ogra_> you are aware that the partitioning between android and ubuntu is completely different ?
[13:34] <ogra_> if you use some flash script for flashing android it might chnage the partitioning
[13:34] <Colin_> ogra: thx for your answer XD  I used to followed this article try to create a system.img (https://wiki.ubuntu.com/Touch/Deploying#Deploying_your_own_full_images)
[13:34] <ogra_> you woulld have to use the meizu factory tool to get tthe ubuntu partition setup back
[13:34] <Colin_> O.O
[13:35] <ogra_> ubuntu-device-flash only uses the existing partitions, it doesnt do any raw writes
[13:35] <ogra_> (and it expects the partition scheme to be correct already)
[13:36] <Colin_> >.<
[13:36] <ogra_> (that way ubuntu can never break something like firmware or IMEI partitions of the device)
[13:37] <Colin_> thx for your answer XD
[13:38] <ogra_> but still, if your partitioning hasnt changed, ubuntu-device-flash should still work ... probably ondra has an idea here
[13:38]  * ogra_ hasnt flashed any phone in ages)
[13:39] <Colin_> um... A question: What does partition changed mean?
[13:39] <ondra> Colin_ what device?
[13:39] <Colin_> meizu mx4
[13:41] <mardy> renatu: hi! there's a little problem with your landing of account-plugins
[13:41] <mardy> renatu: we always do triple landings
[13:41] <Colin_> oh... I find something interesing.. When I flash Flyme Android (Globe version). The ubuntu's recovery still here. But after I flash Yun OS. The ubuntu's recovery was replaced by meizu's recovery O.O.
[13:42] <renatu> mardy, yes this silo is stuck: https://requests.ci-train.ubuntu.com/#/ticket/1755
[13:44] <ondra> Colin_ if you flashed any android to the device, it's very likely you have changes partition table and when you want to flash back Ubuntu you will need to choose firmware upgrade in flasher
[13:45] <mardy> renatu: are you able to fix it?
[13:45] <Colin_> Thank you so much. :D
[13:45] <renatu> mardy, looks like it is blocked due the qt-base landing
[13:45] <dobey> mardy, renatu: what's the problem now?
[13:45] <mardy> renatu: AFAIU, it's because this landed in yakkety but not in xenial and vivid: https://launchpad.net/ubuntu/+source/account-plugins/0.13+16.10.20160804-0ubuntu1
[13:45] <mardy> dobey: ^
[13:45] <renatu> we need to wait for it
[13:46] <mardy> renatu: ok, it looks like we are talking of two different issues
[13:46] <dobey> how did something land in yakkety but not overlay?
[15:32] <ganeshi4u> ondra: the following repos aosp/platform/ prebuilts/maven_repo/android and aosp/platform/ prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8 could not be found and shows error while syncing from phablet-5.1.1_r36 branch. I have cross checked the manifest with the one in your personal branch and the above repos are not present. Are these repos necessary or
[15:32] <ganeshi4u> should I just ignore them?
[15:41] <ondra> ganeshi4u yeah they are not needed
[15:41] <ondra> but I will add them
[15:45] <ondra> ganeshi4u OK updating those repos, they are not really needed though, not sure what is maven used for, but other one is cross compiler for x86_64bit which is platform we do not support at the moment anyway
[15:54] <ganeshi4u> ondra thanks, those repos are causing the sync to fail due to fetch errors. AFAIK maven is used to speed up the compilation of java files
[15:54] <ondra> ganeshi4u try now
[15:55] <ondra> ganeshi4u it should be updated now
[16:00] <ganeshi4u> ondra: right now I'm in middle of the sync. I'm afraid it'll get corrupted if I stop the sync, I'll report back when i start it once again later
[16:25] <ondra> ganeshi4u cool thanks
[17:04] <kaisoz> hi there!
[17:08] <kaisoz> hi there!
[17:10] <kaisoz> I recently got a bq aquaris e5 and installed ubuntu touch on it
[17:10] <kaisoz> I'm really loving it!
[17:10] <kaisoz> I would like to contribute to the project
[17:14] <kaisoz> I've been reading about the project and I see that basically it's Ubuntu with Android inside a container along with some core apps (Calendar, File Manager...) and some services (oFono, ...)
[17:14] <kaisoz> am I right?
[17:14] <ogra_> nope
[17:14] <kaisoz> :D
[17:15] <kaisoz> well, so I miss some info then
[17:15] <ogra_> the android container is only a bunch of drivers and a few services around them to make the HW work
[17:15] <ogra_> the ubuntu that is running is a full ubuntu
[17:16] <kaisoz> ahh ok, yeah, I understood that too, maybe my explanation was a bit vague
[17:16] <ogra_> but yeah, essentially you are right
[17:16] <kaisoz> ubuntu is reusing the Android drivers
[17:17] <ogra_> it has to
[17:17] <ogra_> (for most of the HW there are no alternatives ... and te drivers are linked against the bionic lib instead of libc ... which makes the container a requirement)
[17:18] <kaisoz> yeah sure, that's a clever idea
[17:18] <kaisoz> that's why libhybris is there right?
[17:18] <ogra_> (you could do it without container, but that would leave you with a giant mess of two mixed systems )
[17:19] <kaisoz> that would be a hell to mantain...
[17:19] <ogra_> yeah, hybris makes the ubuntu side talk to the bits in the container
[17:19] <kaisoz> great, so I got it
[17:19] <ogra_> well, it seems ot work for sailfish ... but they also dont have the requirement that you can turn the os into a normal desktop
[17:19] <kaisoz> I've been checking the components to see where I could help
[17:20] <ogra_> so we tried to keep the ubuntu side as clean as possible
[17:21] <kaisoz> sure, I also think is the best approach
[17:21] <kaisoz> I've seen the canonical system image
[17:21] <kaisoz> project
[17:22] <kaisoz> what's that for?
[17:22] <kaisoz> cause I've seen that there are projects for the core apps
[17:22] <kaisoz> projects for ofono and related
[17:22] <kaisoz> it looks like a general project or something like that
[17:22] <dobey> it's for tracking things
[17:24] <kaisoz> so people fill bugs there
[17:24] <kaisoz> and once there are triaged, they are linked to the proper project?
[17:25] <dobey> well, bugs on launchpad can "affect" multiple projects
[17:25] <dobey> the c-d-s-i project is basically how we track features and bugs in launchpad, that we want to target for certain OTAs and such
[17:26] <dobey> one can file a bug against it, sure, or the package or project which the issue is actually in
[17:26] <kaisoz> ahhh oka
[17:26] <kaisoz> so you group there the bugs/features to be completed for the next mileston
[17:26] <kaisoz> kind of a roadmap
[17:36] <kaisoz> so, are the projects listed in https://wiki.ubuntu.com/Touch/Components the only ones Ubuntu-touch related?
[17:36] <kaisoz> is this list updated?
[17:37] <dobey> that is by no means an exhaustive list
[17:38] <dobey> and not entirely correct for everything there
[17:39] <kaisoz> yeah, I tough so... I guess there's no up-to-date list anywhere right? I'll have to search around Launchpad to know them all
[17:40] <dobey> i don't think necessarily that "knowing" all the individual packages/projects that make up the entire phone image is a worthwhile expenditure of time
[17:41] <dobey> if you have a problem and don't know which component the problem is in, you can just ask, or if there is something specific you want to help work on. we can help point you in the right direction in here
[17:42] <kaisoz> I was about just curious, but yeah, you're right, thank you :)
[17:43] <dobey> sure, but most of us who work on the phone stuff on a daily basis probably couldn't even recite the entire list of projects/packages, and some of them even vary across phone images
[17:44] <kaisoz> heheh I imagine that
[17:44] <dobey> because some different scopes/apps are shipped on different devices and in different regions, for example
[17:45] <dobey> and configuration for some devices is sometimes different than others
[17:45] <dobey> tablets versus phones versus laptops, for example
[17:45] <kaisoz> I'll play deeply with the phone, channels and so
[17:47] <kaisoz> about the contribution cycle, how it goes here? Sorry for so many questions... I've contributed with a few patches to the kernel (drivers subsystem) and there the steps are quite straightforward, you pick a task, work, submit the patch and then wait for feedback. Do you work in the same way? Are there tasks that are only for the Canonical guys?
[17:48] <kaisoz> I mean, do I select a project, look for bugs to solve and submit patches? Do I have to contact a maintainer before?
[17:48] <dobey> ubuntu is ubuntu, there aren't necessarily any differences in contributing fixes for the phone or other packages in ubuntu, generally
[17:48] <kaisoz> again, sorry for some many questions
[17:49] <dobey> well, things that only canonical people can work on/fix, you can't see anyway if you're not canonical :)
[17:49] <kaisoz> that's logical, anyway better ask xD
[17:51] <dobey> depending on the project/package, there are some minor differences in how things should ideally be submitted, but basically, just picking something that you want to work on, and either submitting a patch or working with whomever is already working on the task, is how to do it
[17:54] <kaisoz> that's great, many thanks for the info :)
[17:56] <kaisoz> I'll start playing deeply with the phone
[17:56] <kaisoz> Let's see where I can help
[17:57] <kaisoz> :)
[19:18] <Bijou> Hello, Is it possible installing Ubuntu phone under Meizu mx4 Android international version, or it's only possible under Meizu mx4 Ubuntu edition version?
[19:37] <dobey> Bijou: a version with android on it has to be repartitioned, and needs an unlocked bootloader (which is not a guarantee afaik)
   I've found this link http://forum.xda-developers.com/meizu-mx/general/tutorial-easy-unlock-bootloader-flash-t3239052  (UNLOCK Bootloader and flash TWRP 2.8.6.0 for MX4)
[19:54] <mariogrip> morphis: can I use ffplay to display mirscreencast_to_stream? if yes how?
[19:55] <mariogrip> vlc shows nothing
[19:55] <morphis> mariogrip: didn't tried ffplay yet
[19:55] <morphis> mariogrip: but vlc -vvvv rtp://@:5000 --network-caching=250 must work
[19:55] <morphis> if not something from the sending side or network conf is wrong
[19:57] <mariogrip> morphis: http://paste.ubuntu.com/22839515/
[19:58] <mariogrip> it just displays random small purple lines
[19:59] <dobey> Bijou: ok. you must be very careful when using the tools and repartitioning a device though, as it is very easy to brick the phone and lose the IMEI and such
[20:19] <Bijou> Thanks <dobey>
[20:19] <dobey> np
[20:58] <PaulfraOSAA> Is it possible to run a QtWidget based application on ubuntu touch?
[21:00] <PaulfraOSAA> I've followed the tuts and made some QML stuff, but since I've just been happily surprised that I can now run QtCreator on my M10 I thought it migt be possible to run it using the QtMir QPA
[21:01] <pmcgowan> PaulfraOSAA, I think it should work but that module is not installed by default
[21:01] <pmcgowan> so your click app could bring it in
[21:03] <dobey> pmcgowan: eh?
[21:03] <dobey> PaulfraOSAA: yes you can run qt apps under unity8, so long as you stick to the qt modules provided by the sdk
[21:03] <dobey> pmcgowan: of course the qtmir qpa is installed. that's how qt/qml works in the first place :)
[21:04] <pmcgowan> dobey, the qtwidgets are not installed
[21:05] <pmcgowan> libqt5quickwidgets5 for example
[21:05] <brunch875> dobey: does this mean roughly any qt app will work?
[21:05] <pmcgowan> but it is in the overlay
[21:06] <dobey>   ubuntu-touch: daily-preinstalled
[21:06] <dobey> that says it is installed
[21:07] <dobey> brunch875: well, anything that either only uses the APIs provided as dependencies of the SDK, or which provide any additional needed modules themselves, and don't try to do things which are outside the realm of their confinement, yeah
[21:07] <PaulfraOSAA> So OTA won't be able to do QtWidget stuff. *sigh*
[21:07] <dobey> huh?
[21:08] <pmcgowan> you need to provide the modules you need f they are not installed
[21:08] <PaulfraOSAA> Ohh, sounds interesting, I'll have to see if the documentation has become better then :)
[21:09] <brunch875> sounds interesting indeed
[21:09] <dobey> PaulfraOSAA: well, full c++ apps aren't really "supported" by the sdk (we don't have c++ APIs for all the ui toolkit bits yet), so not sure if what you want out of documentation is going to be there yet
[21:10] <dobey> but sure, there was at least one app in the store that was pure c++/qt without qml (the gl demo thing)
[21:11] <dobey> you don't have to worry about the QPA either. the right one should be used if you run the app under mir vs running under xorg
[21:12] <PaulfraOSAA> dobey: Is there any work on enabling full c++ QtWidgets apps?
[21:12] <PaulfraOSAA> I'd be interested in how I could pull in the QtWidget module since my OTA update probably won't have it
[21:13] <dobey> the widgets module should already be installed by default
[21:13] <dobey> i don't recall what "widgets" are in what modules, but i think the uitk uses some widgets stuff
[21:14] <dobey> PaulfraOSAA: my suggestion is "just try it"
[21:15] <PaulfraOSAA> dobey: The uikit uses the QmlControls, that is not the same as QtWidgets, which is the "old" standard c++ way of doing stuff
[21:15] <PaulfraOSAA> dobey: Just haven't figured out how to get along with the click packages yet
[21:17] <PaulfraOSAA> That is the documentation I'd really like to see improvements on. Maybe I just haven't found it yet