[00:20] <sergiusens> fginther, yes, image based upgrade systems still depend on setting up an ubuntu_commands in /cache/recovery, rebooting into recovery and doing whatever is in ubuntu_commands from there
[00:22] <sergiusens> fginther, it's something like this if it interests you https://wiki.ubuntu.com/ImageBasedUpgrades/Upgrader
[00:46] <dermag> holla ,i need some help
[00:47] <dermag> i have xperia pro mk16i ,does ubuntu can work ok on this device ?
[00:50] <dermag> anybody help ,please
[00:52] <dermag> ?
[03:42] <ca18det> is the ppa down for phablet tools?
[03:43] <stgraber> launchpad is down
[03:43] <stgraber> datacenter power problem
[03:43] <ca18det> oh on!!
[03:43] <ca18det> no
[06:03] <gaurav_> Can anyone help me install the stable version of Ubuntu touch on my Nexus 4
[06:04] <gaurav1912> Is anyone there?
[06:05] <gaurav1912> I want to install the stable build of ubuntu on my nexus 4
[07:43] <bray90820> Why am i getting a status 7 error when i try to install ubuntu on my Tmobile g2/htc vision
[13:01] <kumikumi_> thinking of installing ubuntu on my galaxy nexus. which one is the one that I (should?) currently want?
[13:01] <kumikumi_> why does the official "ubuntu-system" image come with a read-only filesystem?
[13:05] <kumikumi_> on the part of the Release notes where it comes to "Accessing the device over SSH" it says that it won't work if I have flashed with "ubuntu-system" variant as that's a read-only filesystem
[13:05] <kumikumi_> on the other hand it says somewhere else that "cdimage-touch" -images are deprecated
[13:09] <ogra_> redonly images are a requirement for the over the air updates to work
[13:09] <ogra_> the cdimage images are deprecated, the ubuntu-system image is the default now
[13:10] <kumikumi_> what's an over the air update? is it the same as typing apt-get update && apt-get upgrade ?
[13:10] <ogra_> no
[13:11] <kumikumi_> apt-get dist-upgrade ?
[13:11] <ogra_> it puts a binary diff in place with the updates
[13:11] <ogra_> about 10x faster than apt
[13:11] <ogra_> and a lot smaller too
[13:12] <ogra_> to do that, the root filesystem on the phone needs to be identical to what the server uses to generate the diff
[13:12] <ogra_> which simply requires it to be readonly
[13:12] <kumikumi_> so ubuntu touch is using a package/update management system other than apt?
[13:12] <kumikumi_> interesting
[13:12] <ogra_> it uses full image updates instead of package updates
[13:13] <ogra_> apps come in the cnew click package format and install in a writable area the user can access
[13:13] <kumikumi_> what if one user installs different packages than the other?
[13:13] <ogra_> he will have to make the image writable and will lose the ability to do OTA upgrades
[13:13] <kumikumi_> alright.
[13:14] <kumikumi_> and will he still have an option to use package upgrades?
[13:14] <ogra_> (and apt will likely break at some point since the space on the system partition is limited)
[13:15] <kumikumi_> sounds a bit worrying?
[13:15] <kumikumi_> alright but thanks for the help, now I know what image to use
[13:18] <ogra_> well, your mom wont use apt on her phone ...  and she will appreciate that it gets automatic updates ;)
[13:18] <kumikumi_> no doubt about it
[13:19] <ogra_> apt is really only for people that want to develop  the image
[13:19] <kumikumi_> but my mom won't be the first to adopt this
[13:20] <ogra_> well, the first to adopt it are hopefully app devs ... who dont care about the system but about their click packages :)
[13:21] <kumikumi_> I may look into that part, but currently I'm still more curious about the system
[13:22] <kumikumi_> I remain fascinated about the thought that it could become as powerful as a PC
[13:22] <ogra_> well, first it needs to become a solid phone system before it can become anything else
[13:22] <ogra_> desktop functionality will not happen before the october  release
[13:25] <kumikumi_> I hope you are working with debian to get upstream all this smartphone/tablet support sweetness :)
[13:26] <ogra_> i doubt they want much of it ... we use an android kernel, use a minimal android inside an lxc container to make the modem stack work (there is no other way) ....
[13:26] <ogra_> s/android kernel/android kernel source/
[13:26] <ogra_> so everything is kind of tied into this setup more or less
[13:27] <kumikumi_> I imagine that could be very useful who wants to support current android devices
[13:27] <ogra_> right
[13:27] <kumikumi_> unless there's some license restrictions or something
[13:27] <ogra_> porting ubuntu touch to a new phone isnt a beginner task ... but not that hard if you have a working android port (and the source for it)
[13:28] <ogra_> the modem and graphic drivers are fully proprietary
[13:28] <ogra_> same for most of the sensors
[13:29] <ogra_> and there is sadly no way around this if you want to use this HW .... thats pretty much a blocker for debian inclusion
[13:30] <ogra_> indeed we try to get general changes where we modify packages  into debian, but i doubt you will be able to ever see a full setup in there without pulling a lot of ubuntu in
[13:35] <kumikumi_> I still remain worried about not being able to use apt at some point
[13:36] <kumikumi_> Imagine not being able to use apt on your desktop or laptop computer (and only being able to do upgrades by upgrading the entire root filesystem), and the reason for that is that your mom wouldn't use apt anyway
[13:36] <kumikumi_> (except that there already exists a graphical upgrade manager that my grandpa knows how to use)
[13:36] <kumikumi_> for the desktop, that is.
[13:40] <kumikumi_> but I'm not the one to make decisions and I do realize you have certain priorities.. I just hope you don't break your system too much on the way
[14:12] <l4serb0y> hey all
[14:13] <l4serb0y> just tried to connect a Google Nexus 4 to my screen here, is that not supported yet?
[14:13] <ogra_> no
[14:13] <l4serb0y> doh!  >.<
[14:14] <ogra_> we first need a stable and feature complete  phone OS before adding fancy features
[14:14] <l4serb0y> anyone know when it will
[14:14] <l4serb0y> ok
[14:14] <ogra_> it is planned for the october release
[14:14] <l4serb0y> it's november now  :)
[14:15] <ogra_> til april we work on stablization and feature completeness ... we also left the tablets behind last release ....
[14:15] <ogra_> from april to october the focus will be on convergence then
[14:15] <l4serb0y> i'm really looking forward to it
[14:15] <ogra_> we all do :)
[14:16] <ogra_> but we have to do one step after the other
[14:16] <l4serb0y> is the plan to make it available for "all" phones on the market
[14:16] <l4serb0y> or just a select few?
[14:16] <ogra_> we only support the nexus line .... but it isnt hard to port it to other phones
[14:16] <ogra_> there are around 50 ports (more or less activer)
[14:16] <ogra_> !devices
[14:17] <ogra_> these are done by community people
[14:17] <ogra_> beyond nexus there will be preinstalled ubuntu phones at some point ... (but i suppose these will be more locked down than what we offer for the nexus)
[14:18] <Guest55123> hello together
[14:18] <l4serb0y> the most exciting part for me is that you can dock it and make it a desktop
[14:18] <l4serb0y> :)
[14:18] <Guest55123> does anybody know if the Nexus 5 will be supported in te future?
[14:19] <ogra_> well, to do that in a pleasant way you will want better hardware than the currently available one
[14:19] <ogra_> Guest55123, it is being discussed ... i suppose we'll hear an official word at or after vUDS
[14:20] <Guest55123> I really hope so
[14:21] <kumikumi_> after running phablet-flash ubuntu-system --no-backup my device boots into a CWM-based recovery with a fancy ubuntu background. does this mean everything worked?
[14:21] <ogra_> kumikumi_, yes, it should then transfer files etc
[14:22] <kumikumi_> so I should just wait? (there's an option to "reboot system now" but I got back to android after selecting that one)
[14:22] <ogra_> ignore the phone, watch the terminal ;)
[14:22] <kumikumi_> alrighty :)
[14:23] <kumikumi_> but it just says INFO:phablet-flash:Waiting for recovery image to boot
[14:32] <kumikumi_> still supposedly "waiting for recovery image to boot"
[14:55] <kumikumi_> There is an error message that I didn't notice earlier. On Ubuntu CWM-based recovery it says "E: Can't open /cache/recovery/ubuntu_command"
[14:55] <kumikumi_> followed by "Checking for autodeploy.zip" and "autodeploy.zip not found"
[14:56] <kumikumi_> is this possible a known issue?
[15:06] <timppa> what's with the latest ota update?
[15:07] <timppa> phone does not boot anymore :(
[15:07] <timppa> trusty image...
[15:07] <timppa> adb shell goes to busybox
[15:08] <msvb-lab> Anyone testing or developing the tablet distros by chance?
[15:09] <msvb-lab> The tablet distros seem pretty sloppy, so I'd like to understand why.
[15:09] <msvb-lab>  I assume that all efforts are going towards a viable phone format.
[15:09] <msvb-lab> So tablet funcationality is lost in the ether?
[15:16] <Gtm> Hi there guys
[15:16] <Gtm> Is there any means to install phablet-flash without the PPA ?
[15:17] <sergiusens> msvb-lab, I have it on manta
[15:17] <msvb-lab> Gtm: Technically you could browse to the PPA area and just download the files.
[15:17] <Gtm> Im behind a firewall that blocks me from accessing keyserver.ubuntu so I cant add PPAs
[15:17] <sergiusens> Gtm, bzr branch lp:phablet-tools
[15:17] <msvb-lab> Is that what you mean? ...and then a simple dpkg -i or so on the .deb.
[15:18] <sergiusens> Gtm, oh, then just download the debs manually from the ppa; or add the keys manually
[15:18] <msvb-lab> sergiusens: But I don't think he wants to build, rather just install the binaries.
[15:18] <Gtm> Adding manually doesnt work for me
[15:18] <Gtm> Ive tried in past
[15:18] <Gtm> and it just gives me errors
[15:18] <Gtm> The deb should work I guess
[15:18] <sergiusens> Gtm, if you don't add the keys, apt-get will still work
[15:18] <sergiusens> it will just print an error
[15:18] <Gtm> I didnt think Deb file would be available there
[15:18] <msvb-lab> sergiusens: Me too, I have Ubuntu Touch on manta (10 inch 2012 nexus tablet.)
[15:19] <Gtm> But it wont update the repository without the key
[15:19] <msvb-lab> sergiusens: How did you decide on the install channel to use?
[15:19] <sergiusens> msvb-lab, manta and grouper are being fixed this cycle
[15:19] <msvb-lab> I used the development channel (customized not proposed.)
[15:19] <sergiusens> msvb-lab, phablet-flash ubuntu-system --channel trusty-proposed
[15:19] <sergiusens> that's what I use
[15:19] <msvb-lab> Customized so that the sample photos and music are in there.
[15:20] <msvb-lab> sergiusens: I didn't even know trusty-proposed was available. Its undocumented.
[15:20] <timppa> sergiusens: Have you updated into todays build via ota?
[15:20] <sergiusens> msvb-lab, so sidestage is rather broken if that is what you are seeing
[15:20] <sergiusens> and manta isn't on mir yet
[15:21] <sergiusens> timppa, no, not today's, was there a build last night? I was supposed to trigger it and there was an outage
[15:21] <msvb-lab> sergiusens: Do you recomment I ditch saucy (development-customized) and burn the trusty-proposed then?
[15:21] <sergiusens> ogra_, did you eventually trigger the build?
[15:21] <msvb-lab> Or are there just as many (but different) broken things on trusty?
[15:21] <Gtm> 4.2.2+git20130218-3ubuntu3~raring	
[15:21] <sergiusens> msvb-lab, I haven't tried the customized builds at all; so not sure what you are missing
[15:22] <timppa> sergiusens: I just did and Nex4 does not boot anymore :(
[15:22] <sergiusens> msvb-lab, I do know that there are issues with manta though; I'm also just using my maguro as a day to day device; the tablet (that one) is just too big
[15:22] <sergiusens> timppa, roll back?
[15:22] <timppa> sergiusens: how?
[15:23] <sergiusens> timppa, reboot into recovery then phablet-flash ubuntu-system --channel (the one you use) --revision -1
[15:23] <msvb-lab> Okay, forget it. I'll try it out and see what happens. Hopefully no brick. Sergiusens flashed on manta architecture, so since that's the one I have I assume there will be no brick.
[15:23] <sergiusens> timchen119, that will install the previous build and since there's no --bootstrap, it shouldn't wipe your data
[15:23] <sergiusens> msvb-lab, it's impossible to really brick devices with fastboot
[15:23] <timppa> sergiusens: thanks! I'll try that
[15:24] <sergiusens> msvb-lab, just don't flash the bootloader (which requires you to jump through hoops to do so)
[15:24] <sergiusens> timppa, I'm assuming you want the previous build, you can switch channels as well and shouldn't lose any data if you want to be less bleeding edge
[15:24] <msvb-lab> Sergiusens: Flashing the bootloader would probably overwrite fastboot, it seems to be a rather flexible bootloader made for devs.
[15:25] <msvb-lab> timppa: I think you never lose data due to phablet-flash(1) auto backup feature.
[15:25] <msvb-lab> ...so if you disable that with --no-backup or whatever then you will lose data.
[15:25] <sergiusens> msvb-lab, yup; as long as you have a working bootloader; it's unbrickable
[15:25] <msvb-lab> Otherwise your data is backed up upon flashes and restored after the new OS is in.
[15:26] <sergiusens> msvb-lab, auto-backup is gone; it's done like OTA now; but with artifacts downloaded to your host instead
[15:26] <sergiusens> msvb-lab, it still means you don't lose data at all
[15:26] <ozberk> hi guys I need your opinion
[15:27] <ozberk> does ubuntu touch really worth to try because I want to use is on my android phone
[15:27] <ozberk> galaxy nexus
[15:27] <ozberk> for example how many applications can work with os so far ?
[15:29] <timppa> sergiusens: how can i enter recovery?
[15:29] <msvb-lab> osberk: If it's your only android device and you use it happily it might not be a good idea.
[15:29] <msvb-lab> The apps I've seen are not very refined or stable.
[15:29] <sergiusens> timppa, I always forget the exact combination, but power button + vol up + vol down takes you to the bootloader
[15:29] <msvb-lab> ...and there's lots missing, for example the ability to read PDF.
[15:29] <sergiusens> timppa, then use the vol buttons to search for recovery
[15:30] <ozberk> ok
[15:30] <ozberk> thanks for suggestion
[15:30] <ozberk> I'll be wait for updates
[15:30]  * sergiusens has been using maguro as his main phone since late May
[15:30] <msvb-lab> osberk: There's no harm in installing touch and then going back to Android a couple days later.
[15:30] <msvb-lab> ...but the pain in that is reconfiguring all that you use Android for.
[15:31] <msvb-lab> Email, calendars, oops lost photos, language, and so on.
[15:31] <msvb-lab> Takes a while to get back to square one.
[15:31] <sergiusens> couple of things you might miss: whatsapp; skype; hangouts; video playback in webbrowser; gps navigation
[15:31] <msvb-lab> ...that's why I've only installed on lab devices to test with (don't go out of the lab.)
[15:31] <sergiusens> msvb-lab, you can always use one of those android backup tools around
[15:32] <msvb-lab> Touch is pretty shabby right now, but there's no reason to give up on it of course.
[15:32] <msvb-lab> sergiusens: Back up is a pain in general.
[15:32] <msvb-lab> ...except for Backula connected devices like desktops.
[15:32] <msvb-lab> Bacula I mean. Perfect for POSIX platforms.
[15:33] <sergiusens> msvb-lab, wouldn't adb pull /data somelocalloation do the trick on a rooted android?
[15:33] <msvb-lab> sergiusens: Since I don't trust Android I've never looked into their structured storage, how they store config data, if all apps do it too, and so on.
[15:34] <msvb-lab> sergiusens: But if you're right about one are to rule them all /data, then that's cool.
[15:34] <sergiusens> msvb-lab, well the only writable location (aside from /cache) is /data
[15:34] <msvb-lab> ...of course adb(1) is your friend.
[15:35] <sergiusens> msvb-lab, the other location is /sdcard; but most devices have a virtual one that point's back to something in /data
[15:35] <msvb-lab> sergiusens: It's worth experimenting with, but tell me for example what happens if you want a partial restore later of only some of the backed up data, or the API level changes?
[15:35] <msvb-lab> ...just playing devil's advocate with that, it's likely that your solution is fine.
[15:36] <msvb-lab> I would reboot and run adb(1) right from the start though, to avoid stale config or other things not written to disk yet.
[15:36] <sergiusens> msvb-lab, oh, I never promised that; I was just doing a one time thing for flashing touch ;-)
[15:37] <msvb-lab> sergiusens: So who is helping to fix manta and grouper 'this cycle' as you say?
[15:38] <msvb-lab> ...and does that mean that when trusty is released, that these formats will finally work?
[15:38] <msvb-lab> Manta and grouper I mean.
[15:38] <msvb-lab> Is there a roadmap?
[15:39] <msvb-lab> ...and if they will be fixed this cycle, why is there almost nothing 'Touch' related in the Summit tracks?
[15:39] <msvb-lab> Looking at the forthcoming Ubuntu Summit topics makes it seem that touch is being abandoned.
[15:39] <msvb-lab> ...rather than being intensively worked on 'this cycle.'
[15:41] <sergiusens> msvb-lab, oh, I think that technical debt might not be something to discuss on a vUDS perhaps?
[15:41] <sergiusens> msvb-lab, unless people want to know how to help
[15:41] <sergiusens> ogra_, hey, what if we create a blueprint to track technical debt on manta so people can chime in with fixes?
[15:42] <sergiusens> I guess the bug list is already a good indicator though
[15:44] <kumikumi_> I'm trying to install ubuntu-touch and just installed a stock android 4.2.2. image. What exactly is supposed to happen when I type "adb reboot fastboot" ? My phone reboots to android
[15:46] <timppa> msvb-lab: I did loose everything, as the phone cloud not backup...
[15:46] <timppa> :(
[15:48] <sergiusens> timppa, ?? what version of phablet-flash are you using?
[15:49] <timppa> latest one
[15:50] <timppa> I've updated everything before this
[15:50] <timppa> phone cloud not boot anything but Busybox
[15:50] <sergiusens> timppa, there is not attempt to backup in the latest tools; it's something that just happens
[15:55] <timppa> That's a risk when you use bleeding edge software :)
[16:07]  * sergiusens will bbl
[16:09] <timppa> yes, latest image does not work even when flashed clean
[17:20] <daker> hi
[17:21] <daker> is normal that's this take so long(~30min) INFO:phablet-flash:Waiting for recovery image to boot ?
[17:22] <daker> ouch failed :(
[17:55] <popey> daker: is it image 16?
[18:13] <kumikumi_> daker: I'm having exactly the same problem
[18:14] <kumikumi_> daker: did the recovery actually boot up?
[18:14] <kumikumi_> daker: for me it's stuck at waiting for recovery image to boot, but I can see the recovery image has actually booted up on the phone
[18:46] <timppa> kumikumi_: image 16 does not work, flash with --revision -1, image 15 does work
[18:58] <kumikumi_> what's image 16?
[18:59] <kumikumi_> timppa: like this? phablet-flash --revision -1 ubuntu-system
[19:00] <timppa> kumikumi_: phablet-flash ubuntu-system -d mako --no-backup --channel trusty-proposed --revision -1
[19:01] <timppa> -d <device>
[19:02] <kumikumi_> I have a galaxy nexus (maguro) btw.
[19:02] <timppa> ok
[19:02] <timppa> -d maguro the3n
[19:03] <AskUbuntu> How to install ubuntu touch on sprint Galaxy nexus (toroplus) | http://askubuntu.com/q/374621
[19:05] <timppa> kumikumi_: toimiiko?
[19:06] <kumikumi_> timppa: pääsen jopa kohta kokeilemaan kun piti asentaa android eka
[19:07] <timppa> kumikumi_: ok
[19:08] <timppa> kumikumi_: onko sulla aikasemmin ollu ubuntu touch asennettuna luuriin?
[19:09] <kumikumi_> timppa: joskus asensin sillon kun tuli eka preview
[19:09] <kumikumi_> nyt näyttää edistyvän jopa, kiitos erittäin paljon :)
[19:10] <timppa> kumikumi_: ok, jos haluat hiukan stabiilimman ympäristön niin käytä --channel saucy
[19:10] <timppa> kumikumi_: toi on edelleen aika hidas tossa raudassa, nexus 4:lla ihan eri luokassa
[19:11] <timppa> kumikumi_: toivottavasti Canonical lähtee kehitäämään ubuntua Nexus 5:lle myös
[19:12] <kumikumi_> niin, aika erikoista olis jos kehittäisivät vanhoille nexus-laitteille mutta eivät uudelle
[19:13] <timppa> kumikumi_: pitkälti kai se riippuu myös siitä että saako bootloaderin unlockattua samalla tavalla kun näissä vanhoissa
[19:13] <kumikumi_> no eiköhän se ole tarkoituksella mahdollisimman helpoksi tehty
[19:14] <timppa> kumikumi_: joo. Tilauksessa ois nex5 :) pitää koittaa ite porttaillla sitä jos ei muuten
[19:14] <timppa> kumikumi_: aikanaan porttasin previewin Samsung noteen kun ei muutakaan ollu
[19:15] <kumikumi_> mulla olis tommonen samsung galaxy tab 2 7.0 jossa ei myöskään oikein hyvin toiminut, ei ole vissiin tehty semmosta "flipattua" versiota siitä vielä
[19:16] <timppa> kumikumi_: just, en oo nyt seurannu oikeen muita porttauksia
[19:21] <marinella> Hello guys, how can i add song in my ubuntu touch?
[19:26] <Morgofth> Algem me ajuda será possivel instalar o ubuntu no telefone alcatatel one toutch
[19:28] <successus> salud
[19:31] <marinella> rbye and thank for help
[19:36] <daker> kumikumi_: failed 3 times but it works now
[20:25] <someguy_> is ubuntu for android an app?
[20:27] <someguy_> is ubuntu for android an app?
[20:29] <AskUbuntu> Ubuntu touch on innotab3? | http://askubuntu.com/q/374651
[20:43] <successus> salud, hasta otro rato o/
[21:55] <AskUbuntu> Nexus 7 Possibly Bricked | http://askubuntu.com/q/374679
[22:33] <ivostoy> I have ifc6410 snapdragon board and tried to install ubuntu-touch on it
[22:34] <ivostoy> Didn't get recognized of course
[22:34] <ivostoy> I saw one post in mailing archives about somebody trying to port to it
[22:35] <ivostoy> Just checking if anybody is working on the same task
[23:21] <AskUbuntu> QtCreator doesn't let me create Ubuntu Touch apps! | http://askubuntu.com/q/374710
[23:29] <fishscene> AskUbuntu: We will need a lot more detail to even begin helping you.
[23:31] <fishscene> NVM. computer was being stupid and didn't load the 2nd half of your link. -_-