[00:26] <RobbyF> _polto_, can't create users yet
[00:36] <_polto_> RobbyF, I was able to create a user, it have it's own home, accessible via ssh, but I do not know how to login with this new user...
[00:36] <RobbyF> it's not built to that extent yet.
[00:37] <_polto_> RobbyF, how can I reset phablet user so ? to use it with my personal data ?
[00:37] <RobbyF> you can remove some of the pre-installed data, is that what you mean?
[00:37] <_polto_> I would like to test SMS, ... address book , ...
[00:37] <_polto_> yes
[00:37] <_polto_> remove pre-installed data.
[00:37] <RobbyF> https://wiki.ubuntu.com/Touch/ReleaseNotes
[00:37] <RobbyF> scroll down to Sample content section
[00:38] <_polto_> thanks
[00:38] <_polto_> got it
[01:37] <wilee-nilee> So is the raring development in the touch auto installable with the phablet tols?
[03:28] <onewanman_> hello
[03:28] <onewanman_> how is the OS progressing
[06:45] <dholbach> good morning
[06:56] <Akiva-Mobile> I was just learning about c++ so I could develope for ubuntu-phone in the future. I then found out that a lot of people hate it, especially linus torvalds :http://thread.gmane.org/gmane.comp.version-control.git/57643/focus=57918.  Before investing a lot of time in learning more C++, I was thinking that maybe it would be better to learn C, seeing as I already know a oo language [python].
[06:57] <Akiva-Mobile> my question is whether that is fine if I plan to work with QT?
[06:57] <Akiva-Mobile> I am a pretty new programmer, but I figure if it works well with c++, it should also work well with c.
[06:58] <Akiva-Mobile> If I plan to write applications with QT gui's, the ubuntu touch, etc, can I get by with just knowing c?
[07:01] <bef0rd> qt is c++
[07:01] <bef0rd> better learn qt and Qml
[07:08] <Akiva-Mobile> bef0rd: I do not get it; does ubuntu touch applications run on qt? I thought that was just the GUI, where as everything else was c++?
[07:15] <bef0rd> learn what qt is
[07:15] <bef0rd> and yes, ubuntu touch apps are qt/qml
[07:22] <Akiva-Mobile> bef0rd: You could just tell me. It says "Application framework", which means... what? You can use it to make a calculator, or you can use it just to make the framework for a calculator, where as the rest of it has to be done in literal c++?
[07:25] <chriadam> Akiva-Mobile: Qt is a set of C++ libraries, basically.  When you write Qt code, you're writing C++ - but instead of using standard types, you're using types provided by the Qt libraries.  QML is different: it's a separate language, whose implementation was written in C++, but client code doesn't have to be C++ (you can use just QML syntax + JavaScript)
[07:26] <chriadam> QML has deep integration with normal Qt C++ types, so you can mix and match Qt C++ and Qt/QML code, in various ways.
[07:26] <Akiva-Mobile> chriadam: QML just strikes me as a html renderer basically. Is that partly correct?
[07:27] <chriadam> no
[07:27] <chriadam> it doesn't use a DOM or a HTML rendering engine
[07:27] <Akiva-Mobile> okay. why did it choose to use html code?
[07:27] <chriadam> it didn't
[07:28] <Akiva-Mobile> sorry
[07:28] <Akiva-Mobile> javascript
[07:28] <Akiva-Mobile> im a goof
[07:28] <Akiva-Mobile> thats what I meant; a javascript renderer
[07:28] <Akiva-Mobile> QML just strikes me as a JAVASCRIPT renderer basically. Is that partly correct?
[07:28] <chriadam> it chose JavaScript for expressions basically because it's a well known language, with C-like syntax so it's familiar to most people.  also, QML has similarities to JSON, and JS and JSON are familiar friends.
[07:29] <chriadam> JavaScript and rendering are completely unrelated concepts
[07:29] <bef0rd> there's no need to guess, search for QML documentation
[07:29] <Akiva-Mobile> Thanks for letting me know~
[07:30] <chriadam> QML uses an optimised, OpenGL scene-graph renderer, written in C++.
[07:41] <Akiva-Mobile> chriadam|away: Why is it not more logical to use C++ for expressions, seeing it is working with a c++ based language qt?
[07:42] <chriadam|away> I'm about to head home, unfortunately.  but, briefly: because expressions are (or can be) dynamic.  You can't resolve dynamic things at build time.
[07:42] <Akiva-Mobile> Thanks!
[08:04] <Akiva-Mobile> Why can't dynamic things be resolved at build time?
[08:06] <Akiva-Mobile> Dynamic things as I understand it, is just an equation broken up into smaller equations (supposedly for multitasking)
[08:07] <Akiva-Mobile> is that like to say, that when c++ compiles, it will solve the  various equations, and save to memory only the results?
[08:11] <shadeslayer> ogra_: so, I got the bootlooping to stop, but since the screen is always off idk whats happening
[10:10] <ogra_> shadeslayer, try to enable the serial gadget in your kernel, that should give you serial output on USB after the kernel is up
[10:11] <shadeslayer> yeah I tried that, but there was no /proc/bus/usb/devices
[10:12] <ogra_> on your PC ?
[10:12] <shadeslayer> yes
[10:12] <ogra_> you want /dev/tty....
[10:12] <ogra_> check dmesg while booting the n10 with an exisring USB connection
[10:13] <shadeslayer> oh, I was following https://www.kernel.org/doc/Documentation/usb/gadget_serial.txt
[10:13] <Rami__> hell
[10:14] <ogra_> shadeslayer, you ant it builtin  and it should just come up automatically
[10:14] <shadeslayer> I see
[10:15] <ogra_> and there is no need for any drivers on the PC side ... just watch dmesg when booting, you shoould see the tty device appear
[10:22] <shadeslayer> ogra_: and you were right about the the toolchain
[10:22] <shadeslayer> all of my compile issues went away when I used the ubuntu toolchain
[10:23] <shadeslayer> so much easier to just export CROSS_COMPILE=arm-linux-gnueabihf-  and run make :)
[10:35] <nerochiaro> tmoenicke: hi, have a question about the OSK. right now it seems that when you tap and hold on a button, you don't get repeated events. but it would be really useful to have instead
[10:38] <shadeslayer> ogra_: uh, nothing shows up in dmesg
[10:42] <xnox> Look how hot this is: http://paste.ubuntu.com/5710034/ c++ demangled dpkg symbols file =)
[10:43] <ogra_> shadeslayer, hmm, weird
[10:43] <shadeslayer> indeedly
[10:43] <shadeslayer> note that I /think/ the device booted the kernel because it feels warm when you touch it
[10:43] <ogra_> lol
[10:44] <shadeslayer> :P
[10:44] <shadeslayer> there's no output on the screen, so I can't tell
[10:44] <ogra_> well, you need to make it output somehow ... either through g_serial or through a framebuffer console
[10:45] <ogra_> thats always the first essential step
[10:46] <Quintasan> shadeslayer: you got n10?
[10:46] <shadeslayer> yes
[10:47] <Quintasan> Tch. Gibe one plax
[10:47] <ogra_> xnox, and do these symboals actually have something in their back or is it just stubs
[10:47] <ogra_> ?
[10:48] <shadeslayer> Quintasan: whut
[10:48] <Quintasan> give me one
[10:48] <Quintasan> :P
[10:48] <shadeslayer> haha
[10:50] <shadeslayer> hm, this config has some weird command line options
[10:51] <shadeslayer> CONFIG_CMDLINE="vmalloc=512M debug_core.break_on_panic=0 debug_core.break_on_exception=0 no_console_suspend s3c2410-wdt.tmr_atboot=1 s3c2410-wdt.tmr_margin=30"
[10:51] <ogra_> yeah, ignore them, usually the bootloader sets it anyway (and overrides it)
[10:51] <shadeslayer> if I completely remove all those options, I don't get a bootloop, but don't get a fb as well
[10:51] <ogra_> just make sure the bootloader config is right
[10:51] <shadeslayer> ogra_: actually CONFIG_CMDLINE_EXTEND=y
[10:52] <ogra_> ah
[10:52] <tmoenicke> nerochiaro: when you keep a button pressed, usually a popup comes up offering extended keys like umlauts
[10:52] <tmoenicke> nerochiaro: which we will have soon
[10:52] <shadeslayer> thing is, if I completely remove those options, then I don't get anything ( no bootloop as well )
[10:52] <ogra_> try console=ttyGS0
[10:53] <ogra_> that should force it to use the g_serial console
[10:53] <nerochiaro> tmoenicke: but that doesn't apply to keys like backspace
[10:53] <shadeslayer> okay
[10:53] <nerochiaro> tmoenicke: which need repeats to quickly delete text
[10:53] <shadeslayer> ogra_: so all it should pass to the kernel is root=/dev/block/platform/dw_mmc.0/by-name/userdata console=ttyGS0
[10:54] <tmoenicke> nerochiaro: yep for that case, true
[10:54] <tmoenicke> nerochiaro: the maliit-keyboard has that
[10:54] <ogra_> shadeslayer, no idea if that device path exists ...  but yeah for the console ...
[10:54] <ogra_> if you boot into an initrd prompt root= doesnt really matter anyway
[10:54] <shadeslayer> heh okay
[10:54] <nerochiaro> tmoenicke: any way we can get that fixed ?
[10:54] <ogra_> just make sure to have the right break= optiojn set too
[10:55] <shadeslayer> break=top ?
[10:55] <ogra_> yeah
[10:55] <tmoenicke> nerochiaro: yep the new keyboard does that
[10:55] <ogra_> and well, make sure its actually an ubuntu initrd :)
[10:55] <shadeslayer> haha ofcourse
[10:56] <xnox> ogra_: what do you mean "in their back"?
[10:56] <ogra_> xnox, well, are there actually sensors to get data from ?
[10:57] <xnox> ogra_: maybe =)
[10:57] <ogra_> (is it linkled into some android lib, libhybris ... libfoo ?)
[10:57] <ogra_> ah
[10:57] <xnox> yeah, it's libhybris dependant implementation library.
[10:57] <ogra_> ah, good
[10:57] <xnox> ogra_: the "original" symbols are C++ ugliness which can be arch dependant: http://paste.ubuntu.com/5710076/
[10:57] <ogra_> though i think hybris doesnt have any sensors connections yet ... might be stubs there
[10:58] <ogra_> yeah
[10:58] <xnox> ogra_: I didn't know up until today that dpkg-gensymbols supports (c++) tag to filter the symbols via c++filt
[10:58] <ogra_> symbols are a pain in C++
[10:59] <xnox> well with c++ tag they are ok, but I am worried that mangled symbol might change/dropped while demangled name stays the same.
[11:03] <delaya73> hello
[11:03] <delaya73> help
[11:04] <delaya73> p990 adb not work, usb connect error: usb device not configured, error -22
[11:05] <delaya73> error on the side of the phone
[11:07] <delaya73> lsusb not list device
[11:07] <delaya73> new bootloader
[11:09] <ogra_> delaya73, i guess you are better off asking in the xda forums
[11:10] <delaya73> ok
[11:12] <ogra_> (in the linked thread from the wikipage)
[11:12] <shadeslayer> mmmm ... nope, still doesn't show up in dmesg
[11:28] <krabador> ogra_, why raring haven't the new core apps inside quantal?
[11:28] <ogra_> krabador, i think they arent built for raring yet ... the raring image is still experimental
[11:29] <ogra_> which reminds me ...
[11:29] <ogra_> sergiusens, all raring bits (except changelog and the still empty manifest) are on cdimange now, shoould be ready for testing changes to phablet-flash
[11:30] <ogra_> i just linked the android parts
[11:50] <sergiusens> ogra_: nice, I'll make the necessay changes
[11:51] <sergiusens> can you tag todays quantal build as well?
[11:53] <ogra_> you mean move it to the quantal dir ? didnt we wnat tests first ?
[11:53] <ogra_> (its just a cp -a for me but i thought we wanted to wait for a set of manual tests)
[12:14] <RobbyF> whats the phablet-flash command for raring orga?
[12:17] <ogra_> there is none
[12:17] <ogra_> phablet-flash will automatically switch once everything is ready
[12:17] <RobbyF> oh ok. thought there was from above comments,
[12:17]  * RobbyF needs morning coffee
[12:17] <ogra_> no, i meant just for testing :)
[12:18] <ogra_> (you could surely hack up phablet-flash locally to use raring though
[12:18] <ogra_> )
[12:19]  * h01ger dist-upgraded to raring and now the display stays black (nexus4) - i can still ssh in though
[12:20] <ogra_> dist upgrading might cause libhybris and platform-api issues ...
[12:20] <ogra_> since half of them lives on the android side
[12:20] <h01ger> ic
[12:20] <ogra_> (yet unpackaged)
[12:21] <h01ger> the android side is the kernel and?
[12:21] <ogra_> we're waiting for the results of the possible container flip
[12:21] <h01ger> +, i'm glad this is unsurprising
[12:21] <ogra_> once android lives in the container it will be easier to update these bits by packages
[12:22] <ogra_> android consists of kernel, binary drivers the full HAL layer and platform-api and libhybris
[12:22] <ogra_> everything you need to make the HW work ...
[12:22] <ogra_> everything above that level is ubuntu
[12:23] <h01ger> ah. and "platform-api and libhybris" is running on android, but not part of normal android, but rather done to be able to run ubuntu on top?
[12:24] <ogra_> right, they are the communication layers to talk to the HW
[12:24] <ogra_> one half lives in android, the other in the ubuntu rootfs
[12:24]  * h01ger nods
[12:24] <ogra_> and indeed they need to be in sync
[12:25] <ogra_> which can cause dist-upgrade to break if you dont also use a new ansdroid layer
[12:25] <h01ger> makes sense now :-) so i will reflash from scratch once again - though not before next weekend..
[12:25] <h01ger> ogra_, thanks for the explaination. much appreciated.
[12:25] <ogra_> :)
[12:31] <mhall119> ogra_: do you know which core apps are in the latest images?
[12:31] <mhall119> is it still clock, calendar and calculator?
[12:31] <ogra_> nope, i dont ... sergiusens might
[12:32] <sergiusens> mhall119: yes, it's those
[12:32] <mhall119> thanks
[12:32] <sergiusens> mhall119: I wasn't told about any new additions
[12:32] <mhall119> ok, just wanted to make sure, I'm working on a blog post
[12:32] <sergiusens> mhall119: but it's easy to add them as long as they are in that same ppa
[12:32] <h01ger> app wise, i mostly miss vibration feedback in on-screen keyboard... but i guess thats planned and i just need to be patient?
[12:39] <mhall119> sergiusens: yeah, I just wanted to highlight the ones we've started including
[12:40] <ogra_> h01ger, once we have proper sensor handling in the api vibration should work too
[12:41] <h01ger> ah, nice. (and good to know what the cause is..)
[13:12] <mterry> didrocks, hello!  What's the skinny on daily-release and config deployment?  I'm happy to help wrangle some of the stragglers today
[13:14] <steve_fi> heya, I get these weird corrupted fonts and wondered if someone can give me a hint to where I might start looking to solving it
[13:14] <steve_fi> http://ubuntuone.com/23E3affaQMvDRxGmfrRTTi
[13:15] <ogra_> steve_fi, mali ?
[13:15] <steve_fi> its when using my asus transformer
[13:15] <steve_fi> tegra
[13:15] <ogra_> ah
[13:15] <ogra_> i only know it from mali400 ... downgrading to the last driver solves it there
[13:15] <shadeslayer> that looks like a TF101
[13:15] <steve_fi> it is
[13:15] <shadeslayer> such a crappy device that is :(
[13:16] <steve_fi> yeah I agree, I bought the dock and the keyboard lasted about 2 months on it, bought a second which lasted 1 month
[13:16] <shadeslayer> heh
[13:16] <lilstevie> oh fun
[13:16] <Quintasan> oh lilstevie
[13:16] <shadeslayer> hahaha
[13:16] <shadeslayer> lilstevie is here
[13:16] <shadeslayer> :D
[13:16] <lilstevie> used to get that on the tegra x11 drivers on the tf101 all the time too
[13:16]  * lilstevie hates tegra
[13:17] <steve_fi> ah, so I know where to start looking :D
[13:17] <Quintasan> steve_fi: You won't get nvidia drivers working on newer kernels I believe
[13:17] <shadeslayer> ^^
[13:17] <Quintasan> Since it lacks some interfaces AFAIR
[13:18] <steve_fi> alright
[13:18] <ogra_> at least you can still call your friends :P
[13:18] <Quintasan> lilstevie might know the exact problem
[13:18] <ogra_> (according to the screenshot)
[13:19] <shadeslayer> ogra_: it's weird btw, I flashed a kernel a couple of hours ago that made the android robot in funny colors
[13:19] <shadeslayer> things were cyan
[13:19] <shadeslayer> and I had modified my init script to increase brightness and the brightness did increase before the screen shutdown
[13:19] <lilstevie> Quintasan, yeah, but with ubuntu touch they are using android driver blobs
[13:19] <lilstevie> and using the old ones
[13:19] <lilstevie> shadeslayer, woo welcome to the weird 2.6.39.4 fbcon screwups
[13:19] <Quintasan> still, the nvidia driver won't work with new kernel, will it?
[13:20] <shadeslayer> lilstevie: eh, this was on the Nexus 10
[13:20] <shadeslayer> it's super weird, I can't get a fbcon on this thing atl all
[13:20] <lilstevie> Quintasan, the latest android one? no, that said I don't think the latest one works on tegra2
[13:20] <lilstevie> shadeslayer, oh
[13:20] <shadeslayer> though I got it to stop bootlooping
[13:20] <lilstevie> heh
[13:20] <ogra_> lilstevie, thats n10 and he is trying to get a normal X11 up
[13:20] <Quintasan> lilstevie: my point exactly
[13:20] <ogra_> (or rather first an fbcon)
[13:20] <shadeslayer> ^^
[13:21] <lilstevie> ogra_, yeah I got that now :p
[13:21] <shadeslayer> lilstevie: exact same concept as the one you had with the TF101 ;)
[13:21] <lilstevie> I really hate arm fbcons
[13:21] <lilstevie> half the time they work
[13:21] <shadeslayer> can't even get g_serial up
[13:22] <lilstevie> fbcon hangs the SoC on my xperia t
[13:23] <shadeslayer> might explain what happens here
[13:25] <shadeslayer> lilstevie: how did you figure that out btw?
[13:26] <lilstevie> shadeslayer, uart debugging showed that as soon as the bootloader jumped to the kernel everything just stopped
[13:26] <shadeslayer> ah
[13:27] <shadeslayer> the xperia t has uart debugging, cool :)
[13:27] <lilstevie> requiring a forced reset
[13:27] <lilstevie> heh yeah
[13:27] <lilstevie> fairly easy to get to also
[13:27]  * shadeslayer hasn't found a way to do uart on the n10
[13:35] <didrocks> hey mterry, sorry was in a hangout :)
[13:36] <shadeslayer> lilstevie: did you enable FRAMEBUFFER_CONSOLE on the TF101 and it just worked? :P
[13:36] <didrocks> mterry: so, some progress, but still some work to do :)
[13:36] <didrocks> mterry: we had sil2100 fixing some of the "dep-wait forever because of powerpc" things
[13:36] <didrocks> mterry: I would say that 1. is look at what happened to unity raring
[13:37] <didrocks> mterry: 2. there is still some help needed on other components if you want :)
[13:37] <shadeslayer> \o/
[13:37] <ogra_> shadeslayer, you might need some mali specific settings  in the framebuffer options
[13:37] <shadeslayer> I have the funny cyan thing again
[13:37] <lilstevie> shadeslayer, pretty much
[13:37] <didrocks> mterry: 3. we'll need to put every stacks in manual uploads mode I guess for final freeze
[13:37] <mterry> didrocks, I noticed that some head stacks were failing because I forgot to list all the install deps of the autopilot test packages.  Will make a merge for that
[13:38] <didrocks> mterry: oh, sync with sil2100
[13:38] <didrocks> mterry: he's looking at it today, I asked for it
[13:38] <mterry> didrocks, OK
[13:38]  * didrocks hugs mterry for looking at that, the only one! :-)
[13:38] <didrocks> mterry: I asked me in particular to look at the list closely
[13:38] <mterry> :)
[13:38] <didrocks> not sure if you noticed but mysql is installed
[13:38] <mterry> didrocks, you asked who in particular?
[13:38] <didrocks> maybe we want to fix the dep/recommends to avoid that :)
[13:39] <didrocks> mterry: oh, I asked today sil2100 for it. I thought your subteam would look at what they bootstrap :-)
[13:39] <mterry> didrocks, I have a subteam?
[13:40] <didrocks> mterry: our* subteam :)
[13:40] <mterry> didrocks, phew
[13:40] <mterry> :)
[13:40] <didrocks> mterry: ahah, I see you relief, you will skip meeting at 8PM :p
[13:42] <shadeslayer> omg omg omg
[13:42] <shadeslayer> ogra_: my init can control brightness
[13:42] <shadeslayer> but that's about all I can get it to do at the moment :D
[13:43] <shadeslayer> I put this in my init http://paste.kde.org/725000/
[13:43] <shadeslayer> and the brightness first lowers and then increases \o/
[13:43] <sil2100> mterry: now I do!
[13:46] <ogra_> shadeslayer, well, check the console options  in your kernel, there is likely some meli specific option you can set
[13:46] <ogra_> *mali
[13:46] <shadeslayer> hmm
[13:46] <shadeslayer> will try and get a serial console up first
[13:47] <shadeslayer> since I know it's loading the kernel and booting into the initrd
[13:50] <Guest38227> hello
[14:03] <shadeslayer> hmm
[14:03] <shadeslayer> ogra_: there's a pin : /sys/class/android_usb/android0/enable
[14:03] <shadeslayer> that's from recovery
[14:04] <ogra_> shadeslayer, for fbcon ?
[14:04] <shadeslayer> for usb access
[14:04] <shadeslayer> the recovery init writes 1 into that file to get adb working
[14:05] <shadeslayer> but obviously, that path is not available to us I think
[14:09] <shadeslayer> so I know stuff is happening in the init, I just dont know why it fails over :/
[14:11] <shadeslayer> ogra_: https://www.dropbox.com/s/55b1wljzlailxb4/IMAG0566.jpg
[14:11] <shadeslayer> that's the weird colored android I see
[14:36] <mterry> didrocks, are we keeping quantal support (for the moment) when porting jenkins configs from phablet to head?
[14:36] <mterry> fginther ^
[14:38] <fginther> didrocks, this is regarding the upstream ci/autolanding jobs
[14:41] <sergiusens> the plan for dropping quantal is -> raring tested, raring image has no regressions compared to the quantal build, quantal publishing dropped, cdimage defaults to raring
[14:43] <mterry> fginther, sergiusens: all the work so far in the daily-release part is raring only
[14:43] <mterry> Which is not to say we can't re-enable quantal
[14:43] <sergiusens> mterry: if you keep that phablet-land job, it will do the necessary thing
[14:43] <mterry> Just that it's a fair bit of unplanned work
[14:43] <sergiusens> mterry: I guess we will have to flip the switch faster
[14:43] <fginther> mterry, we're talking about upstream autolanding jobs, does the daily release care about that?
[14:43] <sergiusens> ogra_: pmcgowan rsalveti ^^
[14:44] <mterry> fginther, does the auto-upload bit not use the same platform config settings?
[14:44] <ogra_> sergiusens, i think that misses a "quantal tested" as well
[14:44] <rsalveti> sergiusens: hopefully we'd be able to take the decision later today/tomorrow
[14:45] <ogra_> if i tag it to the quantal dir i want to be sure its stable enough for demoing
[14:45] <rsalveti> depending on the test results
[14:45] <pmcgowan> right lets execute the plan
[14:45] <rsalveti> yeah
[14:45] <fginther> mterry, no, the "configurations" section is for upstream only
[14:46] <fginther> mterry, the only option that the daily release jobs look at under a project is 'daily_release' :-)
[14:47] <mterry> fginther, OK.  Well if we want to re-enable quantal, that's fine.  But can that be done separately from this qtvideo-node branch?  Seems like something we should do globally at the top of each stack
[14:48] <fginther> mterry, yes. that's actually a good point
[14:48] <fginther> mterry, i'll update my comment
[14:50] <mterry> fginther, I can make a branch for that.  You said you didn't want to enable all 3 platforms (i386 amd64 armhf)
[14:50] <mterry> fginther, why not?  Seems like we could have a problem on one of them but not the others
[14:50] <fginther> mterry, I make the MP, I want to review the other projects briefly
[14:50] <mterry> fginther, OK
[14:51] <fginther> mterry, we just try to save some resources by not building all permutations
[14:52] <AmEv> Anyone there?
[14:52] <ogra_> where ?
[14:53] <AmEv> Just wanting to add a device to the WIP list.
[14:54] <ogra_> do it :)
[14:54] <AmEv> http://www.thriveforums.org/forum/pio_masaki-development/18090-wip-ubuntu-touch-thrive-development.html
[14:55] <ogra_> (if you are the porter, just add it yourself, its just a wikipage)
[14:56] <AmEv> Toshiba Thrive, codename Antares. Not the porter myself, but...
[14:56] <AmEv> I'll see what I can do.
[14:56] <ogra_> well, the wiki needs a contact person
[14:58] <AmEv> Don't know muck Wiki code, but I'll see what I can do.
[15:01] <A1taiR> Hello2All
[15:01] <A1taiR> I'm wondering: could you install Gimp on Ubuntu touch?
[15:02] <ogra_> you cuold ... but you coldnt use it on the display
[15:02] <ogra_> (you can install ssh and use it via "ssh -X" remotely)
[15:03] <ogra_> there is no Xorg support in ubuntu touch ... so it cant run on the display server
[15:03] <A1taiR> oh, I see
[15:03] <A1taiR> Is there any way to draw on ubuntu touch?
[15:04] <ogra_> write an app :)
[15:04] <A1taiR> :)
[15:04] <A1taiR> Will be there Xorg support ever?
[15:05] <A1taiR> Maybe, announced
[15:05] <ogra_> at some point once Mir is ready and enters the desktop
[15:05] <ogra_> currently ubuntu touch uses surfaceflinger ... that will soon be replaced with Mir which will only support Qt in the beginning ...
[15:06] <ogra_> for the move to the desktop there then will be XMir ... that will give you Xorg support
[15:06] <A1taiR> I see
[15:07] <A1taiR> Will it be compatible with Xorg applications?
[15:07] <ogra_> yes
[15:07] <A1taiR> Thanks!
[15:07] <ogra_> but thats 14.04 material i think
[15:07] <ogra_> so still far out
[15:07] <A1taiR> ok
[15:08] <ogra_> (the guys in #ubuntu-mir might have more details)
[15:13] <shadeslayer> rsalveti: around?
[15:14] <mhall119> kenvandine: do we have API docs for Friends and OnlineAccounts?
[15:14] <AmEv> That's weird... I'm trying to add it, but Wiki's crashing when I try to log in....
[15:15] <mhall119> AmEv: that's not relaly weird, the wiki is like that most of the time :)
[15:15] <AmEv> Haha....
[15:16] <AmEv> I have a U1 account, so I'm trying to use it.
[15:16] <AmEv> Anyone willing to help me out?
[15:16]  * mhall119 loves U1
[15:16] <mhall119> AmEv: if I can, sure
[15:17] <AmEv> Well, I'm trying to add another tablet to the WIP list.
[15:18] <AmEv> Toshuba Thrive (AT100/105) Codename Antares.
[15:18] <mhall119> ok, are you logged in?  It should have your username next to the "More Actions:" drop-down
[15:18] <kenvandine> mhall119, not yet.. there are docstrings in the code
[15:18] <AmEv> http://www.thriveforums.org/forum/pio_masaki-development/18090-wip-ubuntu-touch-thrive-development.html
[15:19] <kenvandine> but i never figured out how to generate the docs
[15:19] <kenvandine> i think i did generate them in qml-friends, but never built in a package
[15:19] <AmEv> Dev is pio_masaki.
[15:19] <mhall119> kenvandine: qdoc
[15:19] <kenvandine> i borrowed the script from ubuntu-ui-toolkit
[15:20] <AmEv> *Toshiba, not toshuba... haha
[15:20] <kenvandine> mhall119, so basically i need to add the -doc package for qml-friends and probably tidy up the docstrings
[15:20] <kenvandine> same for accounts-qml-module
[15:21] <AmEv> Trying login once more....
[15:22] <AmEv> OK, I'm logged into SSO, but when I'mtrying to Wikiize, it hangs....... argh....
[15:22] <nik90> bzoltan1: ping
[15:23] <bzoltan1> nik90: pong
[15:23] <AmEv> Ther we go!
[15:24] <nik90> bzoltan1: I wanted to ask you some question regarding TimeZone Data for the ubuntu-clock-app core apps
[15:24] <bzoltan1> nik90:  shoot
[15:24] <nik90> bzoltan1: Is there a common platform API I can use to get a list of all the timezones using qml? I basically need to provide that info to the user.
[15:25] <nik90> bzoltan1: so basically the user chooses a city for instance new york and in return I need to display the time there
[15:25] <AmEv> sigh... I was in, but changing pages logged me out....
[15:25] <mhall119> kenvandine: when you have that, let me know so we can publish it to developer.u.c
[15:25] <kenvandine> will do
[15:26] <kenvandine> mhall119, can you pull that from packages in a PPA?
[15:26] <AmEv> Wait...
[15:26] <kenvandine> i don't think i'll be able to land that in raring
[15:26] <nik90> bzoltan1: I have tried looking at tzdata where it lists all the timezones in the world but was hoping there was api already available for us to use
[15:26] <mhall119> kenvandine: I think it takes some hacking on the script, I'll check with dpm
[15:28] <AmEv> Haha... Refreshing the page helps!
[15:36] <didrocks> 16:46:28      fginther | mterry, the only option that the daily release jobs look at under a project is 'daily_release' :-)
[15:36] <didrocks> fginther: mterry -> target_branch as well
[15:36] <didrocks> as we introduced it :)
[15:36]  * fginther slaps head
[15:37] <mhall119> ogra_: rsalveti: when will we switch the daily images to Raring?
[15:37] <AmEv> It's in... How'd I do?
[15:38] <bzoltan1> nik90:  I suggest to parse this -> http://qt-project.org/wiki/Qt-5-QTimeZone
[15:39] <nik90> bzoltan1: will have a look at it
[15:39] <nik90> bzoltan1: might I also ask if you have any information about obtaining the longitude and latitude (location of user) using API?
[15:40] <nik90> bzoltan1: I need the long, lat to determine the sunrise and sunset time using an online API
[15:40] <ogra_> mhall119, once there were enough tests to make sure that a) qunatal is good enough for demoing so we can freeze the last build and b) raring has no major regressions
[15:46] <AmEv> Well, I'm hoping to have this on my Thrive soon!
[15:54] <nik90> bzoltan1: on reading through QTimeZone, it seems that this is a concept being worked on and can only be expected in qt 5.1.
[16:20] <Meizirkki> hi
[16:22] <Meizirkki> If, when there is an ubuntu (the real one) booting on nexus devices, isn't is possible to use kexec to boot android
[16:22] <Meizirkki> sort of dual boot
[16:22]  * Meizirkki wishes to use android when ubuntu isn't fully fuctional
[16:23] <Meizirkki> typos, grah
[16:23] <Tassadar_> depends on the device, really
[16:24] <Tassadar_> kexec usually tends to not work with android things
[16:24] <Tassadar_> (the not modified, real kexec, there are patches which workaround some of the problems)
[16:25] <Meizirkki> hmm
[16:25] <Meizirkki> maybe the other way round? Boot android first, then kexec ubuntu if requested
[16:25] <Tassadar_> that's not the point, ubuntu will use android's kernel anyway because drivers
[16:25] <Meizirkki> I had an Nokia N810 few years back, and when an android image came around it was possible to boot Maemo from power button menu
[16:26] <Meizirkki> But aren't people working on a "real" ubuntu image as well?
[16:26] <Tassadar_> well yeah, but you need the drivers
[16:27] <Tassadar_> and drivers are probably the problem - they just aren't written with kexec in mind, so usually it freezes halfway through, with pretty much no way to debug that
[16:27] <Meizirkki> i see
[16:27] <Tassadar_> it is possible to use something called kexec-hardboot, which adds real device reboot to kexec, so that drivers and devices are properly re-initialized
[16:28] <Tassadar_> I have that working on nexus 7
[16:28] <shadeslayer> nik90: bzoltan1there's http://api.kde.org/4.10-api/kdelibs-apidocs/kdecore/html/classKTimeZone.html
[16:29] <shadeslayer> you could potentially a) make your app depend on libkdecore or b) copy headers
[16:29] <shadeslayer> s/headers/code/
[16:29] <Meizirkki> Tassadar_: okay
[16:33] <Oranger> mhall119: Hi ! I'm free actually so if you want you can explain me the project, thanks you in advance
[16:44] <rsalveti> shadeslayer: pong
[16:44] <shadeslayer> sigh
[16:44] <shadeslayer> rsalveti: I have good news and bad news
[16:44] <shadeslayer> rsalveti: I got the kernel to boot and I could control the backlight from the initrd
[16:44] <rsalveti> mhall119: ogra_: the call for testing will be out later today, so we can decide if we're able to switch to raring already
[16:44] <rsalveti> if so, we'll probably switch tomorrow or later this week
[16:44] <rsalveti> shadeslayer: right
[16:44] <shadeslayer> but I still can't get a serial console up
[16:45] <shadeslayer> ( using serial gadget )
[16:45] <shadeslayer> nor can I get fbcon up
[16:46] <rsalveti> ogra_: do you remember easily how to set up serial gadget to provide a terminal?
[16:46] <ogra_> shadeslayer, did you dig for mali options in the console settings of your kernel config ?
[16:46] <shadeslayer> ogra_: yes, I don't see anything obvious
[16:46] <ogra_> rsalveti, just compile it in and set console=ttyGS0 ...
[16:47] <shadeslayer> yeah, ^^ already tried like you told me a couple of hours ago :)
[16:47] <ogra_> right
[16:47] <ogra_> no magic involved ...
[16:47] <ogra_> though probably your exynos doesnt like it builting (it doesnt matter on tegra) ... so you could try a module and load it from initrd
[16:48] <ogra_> *builtin
[16:48] <shadeslayer> hmmm
[16:48] <shadeslayer> I'll try that
[16:49] <mhall119> rsalveti: perfect, let me know when you put the call out and I'll help promote it
[16:50] <shadeslayer> ogra_: fwiw : http://i.imgur.com/OYJXu7i.png && http://i.imgur.com/pRSymW5.png
[16:50] <ogra_> whats that ?
[16:51] <shadeslayer> mali GPU options that I can see
[16:51] <ogra_> ?
[16:51] <ogra_> oh
[16:51] <ogra_> is that the Xorg kernel config ?
[16:51] <rsalveti> mhall119: sure, sergiusens is taking care of that
[16:51]  * ogra_ has never seen that 
[16:51] <ogra_> hard to find any options there
[16:51] <shadeslayer> that's from make xconfig :)
[16:51] <ogra_> yeah
[16:51] <shadeslayer> uses Qt
[16:52] <ogra_> never used that in my life
[16:52] <shadeslayer> :D
[16:52] <ogra_> very bad to see the options this way
[16:52] <shadeslayer> I used menuconfig earlier
[16:52] <shadeslayer> but found xconfig to be easier to use
[16:52] <shadeslayer> oh?
[16:53] <ogra_> so what is "exynos video driver support" ?
[16:53] <ogra_> did you try that ?
[16:53] <shadeslayer> I have no idea, I've been searching, haven't found anything
[16:53] <shadeslayer> I did not
[16:53] <shadeslayer> I don't want to just randomnly enable modules :P
[16:54] <ogra_> also Ion memory manager ... isnt that nvidia related ?
[16:54] <ogra_> or does that refer to a different Ion
[16:54] <shadeslayer> dunno, enabled by default, didn't bother unticking it
[16:54] <ogra_> really, you should play with the options a bit,... be brave :)
[16:55] <shadeslayer> haha
[16:55] <ogra_> alos look at console support
[16:55] <ogra_> might also miss options there
[16:55] <ogra_> (under character devices iirc)
[16:56] <shadeslayer> *facepalm*
[16:56] <shadeslayer> CONFIG_X86_PLATFORM_DEVICES  -> y
[16:56] <ogra_> fun
[16:57] <Tassadar_> what does that even mean Oo
[16:58]  * Tassadar_ googles
[17:08] <shadeslayer> ogra_: the module is just called g_serial right?
[17:09] <shadeslayer> so I modprobe g_serial on the device
[17:09] <ogra_> right
[17:09] <ogra_> from an initramfs-toolks hook or so
[17:09] <shadeslayer> oh
[17:09] <ogra_> and indeed make sure to have it in the initrd
[17:09] <shadeslayer> I was going to put it in /init :P
[17:44] <RobbyF> OT: Psy's new video hits 62 Million.
[17:55] <JanC_test> RobbyF, is it as bad as the previous one?  :p
[18:14] <RobbyF> JanC_test, yes
[18:55] <boiko> mhall119: ping
[18:55] <mhall119> boiko: pong
[18:56] <mhall119> boiko: if this is about my package-fixes branch, I pushed the fix to Vcs-Bzr
[18:56] <boiko> mhall119: ah yes, it was :)
[18:56] <mhall119> :)
[18:56] <mhall119> dalius pointed out to me that I was the blocker
[18:57] <boiko> mhall119: ok, thanks for fixing it, I'll approve it as soon as CI finishes running
[18:57] <mhall119> thanks boiko
[19:00] <t1mp> aquarius: I added a question for you to this bug report https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1166982
[19:00] <t1mp> maybe it is a question for design
[19:02] <Oranger> mhall119: Are you back ?
[19:05] <mhall119> Oranger: I am, yes
[19:05] <mhall119> popey: you around?
[19:05] <popey> ya
[19:05] <Oranger> mhall119: cool :)
[19:06] <popey> wassup?
[19:06] <mhall119> popey: Oranger is going to be joining the Document Viewer project
[19:06] <popey> excellent!
[19:06] <popey> Welcome to the mad house
[19:06] <Oranger> Hi popey !
[19:06] <popey> er, development community
[19:06] <mhall119> Oranger: first thing, before submitting any code, we need you to sign the contributor agreement: https://forms.canonical.com/contributor/
[19:07] <Oranger> Ok I do it now
[19:07] <mhall119> thanks
[19:07] <mhall119> then, we have a spec and blueprint for this project
[19:07] <mhall119> the spec is https://wiki.ubuntu.com/Touch/CoreApps/DocViewer
[19:08] <mhall119> and the blueprint with work items to be done is here: https://wiki.ubuntu.com/Touch/CoreApps/DocViewer
[19:08] <Oranger> Yes, I ahave already read it :)
[19:08] <popey> brb, need to reboot to test new kernel
[19:14] <Oranger> mhall119: Do I have to put your name on "Canonical Project Manager"
[19:19] <Oranger> mhall119: Ok, I did it with your name
[19:20] <mhall119> Oranger: that should be fine
[19:20] <mhall119> I'll check with the person who processes those form submissions in the morning
[19:21] <Oranger> So tomorrow ?
[19:25] <mhall119> you can start contributing any time
[19:25] <mhall119> I was just letting you know I would handle the rest
[19:26] <mhall119> so we had one other developer who was interested in contributing ot this project, but there hasn't been any code written yet except the template branch that all of the Core Apps have been using
[19:26] <mhall119> which is at lp:ubuntu-docviewer-app
[19:27] <Oranger> Ok, i'm actually trying to clone the branch in my computer. Is there something in particular I need to know before touching the code?
[19:28] <mhall119> only some QML and Javascript
[19:28] <janimo> rsalveti, sergiusens is there anything needing  extra to be done when porting to a device using ICS blobs, that is not suported by CM/JellyBean?
[19:28] <mhall119> Oranger: we're trying to stick with pure QML whenever possible, and if we need to write some C++ do that in a QML plugin in aseparate branch
[19:28] <rsalveti> janimo: hm, might not work out of the box, as there might be api issues with the binary drivers from ics
[19:29] <rsalveti> I know the cm codebase we're using supports ICS based blobs
[19:29] <rsalveti> but you might still face issues with that
[19:29] <janimo> rsalveti, ah, I thought this had been done before and there are workarounds
[19:29] <rsalveti> like lack of symbol or such
[19:29] <mhall119> Oranger: what is your Launchpad username?
[19:29] <rsalveti> janimo: yeah, cm usually brings back the old symbols/apis to support older bins
[19:29] <Oranger> My (new) username is "chocanto"
[19:30] <janimo> rsalveti, any particular thing I need to do extra so the compat mode is activated, or is it taken care of by a regular build?
[19:30] <rsalveti> janimo: that's why it might work, but it might also give you issues
[19:30] <janimo> rsalveti, ok thanks
[19:30] <mhall119> Oranger: thanks, I've added you to the development team
[19:30] <mhall119> Oranger: the basic process for developing and submitting code is documented here: https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[19:30] <rsalveti> janimo: it should just work, the main problem is with the blobs
[19:31] <janimo> rsalveti, right, but the blobs may be involved in graphics so affecting the UI bringup right?
[19:32] <Oranger> mhall119: Ok, thanks.  Is there a feature you want to be added first ?
[19:32] <mhall119> Oranger: the first thing I would like to see is the ability to display plain text files
[19:32] <rsalveti> janimo: yup, but I saw already some devices working with ics based blobs, so it should work (at least the graphics part)
[19:32] <rsalveti> unless your blob is doing something really weird
[19:32] <janimo> rsalveti, thanks that is good to know
[19:33] <mhall119> Oranger: ideally it would accept the file path as a command-line argument, we already know that will require some C++ code, and we're hoping to get that done by a more general purpose app-launcher
[19:33] <Oranger> mhall119: Sound logical to me ^^
[19:34] <Oranger> mhall119: The ubuntu-touch-core devs are not planning to find a way to use QML to get command-line arguments ?
[19:34] <rsalveti> janimo: http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_frameworks_av.git;a=commitdiff;h=43926620689579fd45420955ebfc548ccf57a628;hp=864a653ee757c7236f1a221942850e9a554b2827
[19:34] <rsalveti> janimo: one example of backporting an older api
[19:35] <mhall119> Oranger: the Ubuntu SDK developers are already discussing the replacement of qmlscene with something else for running these QML-only apps
[19:35] <mhall119> command-line argument parsing could be built into that
[19:35] <mhall119> we can put together a small launcher for this project until they have that though, if necessary
[19:36] <Oranger> mhall119: Ok nice
[22:48] <sergiusens> jhodapp: mind looking at https://bugs.launchpad.net/touch-preview-images/+bug/1169352
[23:57] <rickspencer3> mhall119, jono_ http://theravingrick.blogspot.com/2013/04/introducing-inkcanvas.html
[23:58] <jono_> rickspencer3, nice!
[23:58] <mhall119> ah ha, grumpy cat with a mustache
[23:59] <rickspencer3> mhall119, I'm happy to find collaborators for InkCanvas
[23:59] <rickspencer3> if anyone needs that functionality, feel free to send them my way
[23:59] <mhall119> will do
[23:59] <rickspencer3> it seems like it could open up some more interactive apps
[23:59] <mhall119> yeah, a finger-painting app for kids would be cool