[02:29] <ahoneybun> mhall119: I've been very bad about app dev since everytime I install the SDK on Kubuntu my machine randomly breaks
[02:30] <ahoneybun> yea but I even I can't live on 2G
[02:30] <ahoneybun> *even I
[02:32] <ahoneybun> mhall119: I was also wondering about advanced boot options like in android
[02:32] <ahoneybun> like reboot bootloader and recovery
[03:42] <ahoneybun> mm hotspot is not working right
[03:42] <ahoneybun> I'm getting auth problem on the device trying to connect
[03:42] <ahoneybun> device: mako
[03:42] <ahoneybun> latest stable OTA6
[06:07] <masa_> i want to try install ubuntu touch on my old droid phone. which phone do you recommend?
[06:21] <dholbach> good morning
[06:33] <mokmeister> masa: look and see if your device is on this list, if so you might be able to get ubuntu-touch on your old droid phone - https://wiki.ubuntu.com/Touch/Devices
[06:33] <mokmeister> dholbach: good morning
[06:34] <dholbach> hi mokmeister
[08:54] <JamesTait> Good morning all; happy Guacamole Day! 😃
[10:05] <Prosthet1cS> Has anyone tried running a plasma mobile image on either a meizu or bq aqauris?
[10:06] <Prosthet1cS> http://kubuntu.plasma-mobile.org/
[11:03] <ogra_> oSoMoN, dbarth, do you gys have plans to ever add a fullscreen button to the browser menu ?
[11:05] <oSoMoN> ogra_, no plans, but feel free to file a bug to request the feature, it shouldn’t be hard to implement (there is already a keyboard shortcut that does that on devices with a keyboard)
[11:05] <ogra_> i just notice that i wouldnt have packaged many of my games if they would have been able to properly initiate fullscreen :)
[11:06] <oSoMoN> hehe
[11:06] <ogra_> (usually a bug in the game ... but being able to forcse fullscreen from teh browser  would solve that)
[11:06] <oSoMoN> yeah
[11:14]  * tathhu is now running ubuntu on laptop, tablet & rpi2 :o
[11:15] <ogra_> you definitely need a phone !
[11:15] <ogra_> and a drone too !!
[11:16] <tathhu> phone, maybe soonTM (again)
[11:16] <tathhu> drone... brb!
[11:20] <ogra_> heh
[11:31] <jgdx> davmor2, hey, did you make a bug for hotspot being shown on mako?
[11:35] <davmor2> jgdx: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487157 lists the 2 bugs
[11:35] <davmor2> jgdx: not sure is the second is right or not any more, I can certainly file one though
[11:35] <jgdx> davmor2, perfect
[11:36] <bkchr> Hi, has anyone an idea why my adb-emergency-shell is dying? http://pastebin.com/Nw9b3NZ0 Maybe because another adbd is already running?
[11:54] <K1773R> can i get GPS coordinates from CLI?
[12:03] <tathhu> Can I get someone to buy me an ubuntu phone? :P
[12:03] <k1l_> if you found one tell him i need one too :)
[12:04] <tathhu> :D
[12:04] <tathhu> Stupid me :)
[12:08] <pete-woods> pitti: it's that time again (https://github.com/martinpitt/python-dbusmock/pull/11)
[12:08] <pete-woods> if you could merge that into the stable overlay PPA again, it would be extremely helpful
[12:30] <bkchr> Anyone has an idea why my upstart doesn't create any log files in log/upstart?
[12:37] <greyback> bkchr: /var/log/upstart and ~/cache/upstart are where upstart logs usually
[12:38] <greyback> ~/.cache/upstart
[12:43] <bkchr> greyback: ahh okay, under ~/.cache/upstart there is something but nothing under /var/log/upstart, hmmm. http://pastebin.com/DkVJYktp any ideas why everything is crashing?
[12:43] <greyback> bkchr: define "everything" - it looks like ubuntu-location-service is in a crash loop though
[12:44] <greyback> you've got a bunch of system services failing
[12:45] <greyback> bkchr: what image has you installed?
[12:45] <greyback> have
[12:46] <greyback> even your syslog service died. Which would explain the lack of logs
[12:47] <bkchr> greyback: Hmm what image should I use? I'm new and I think I took the wrong -.-
[12:47] <greyback> bkchr: what device are you using?
[12:48] <bkchr> greyback: Oneplus one, porting a kernel^^ Used the following image "ubuntu-.." image: http://system-image.ubuntu.com/ubuntu-touch/devel/ubuntu/generic/index.json
[12:50] <greyback> bkchr: I'm not a porting expert. But I would recommend working on the "rc-proposed" (or "rc-stable") image instead of "devel"
[12:50] <greyback> rc-* = vivid
[12:50] <greyback> devel = wily, which isn't getting much attention
[12:50] <greyback> we're focusing on delivering the phone based on the stable vivid foundation
[12:52] <bkchr> greyback: So I should use one of these? http://system-image.ubuntu.com/ubuntu-touch/rc/ubuntu/generic/index.json or should I use a rc-proposed?
[12:54] <greyback> bkchr: either is ok, rc-proposed changes daily, whereas stable moves very slowly (i'm not sure how often "rc" changes, not much looking at its history)
[12:57] <jibel> rc changes as often as stable
[12:57] <pitti> pete-woods: heh, looking
[12:58] <bkchr> okay thx, I will try the rc-proposed ;)
[12:58] <jibel> bkchr for reference https://wiki.ubuntu.com/Touch/Channels
[13:00] <greyback> jibel: good to know, ta
[13:03] <pete-woods> pitti: thanks :)
[13:07] <bkchr> jibel: ahh. Maybe someone should edit this page, because ony devel-proposed states that it is wily
[13:23] <pitti> pete-woods: done: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?field.name_filter=dbusmock&field.status_filter=published&field.series_filter=
[13:30] <pete-woods> pitti: awesome! much appreciated! :)
[13:34] <bkchr> greyback: Could you maybe help me another time? My android-tools-adbd.log shows "install_listener('tcp:5037','*smartsocket*')" but I never see the device at my pc, any ideas?
[13:37] <zaolin> Does anyone know why the audio playback interrupts on each device action ? For example locking the screen.
[13:46] <seb128> mterry, hey
[13:46] <seb128> mterry, we can revert that libusermetrics landing if you prefer
[14:03] <mterry> seb128, no it's fine
[14:03] <mterry> seb128, unity8 should handle "" better if it's not the invalid-flag I thought it was
[14:04] <seb128> mterry, thanks for working on that!
[14:04] <mterry> seb128, I didn't mean to sound ornery  ;)
[14:04] <seb128> you didn't
[14:04] <didrocks> that's volounteering
[14:05] <seb128> but you were right on principle, buggy updates should probably be reverted
[14:05] <mterry> :)  speaking of volunteering, I need to do sponsoring today
[14:06] <jdstrand> beuno: hey, it might be time to bzr pull the review tools. there are two small updates for touch. this is not time-critical
[14:07] <beuno> jdstrand, ack ack, cc/ pindonga
[14:07] <pindonga> will do
[14:12] <jdstrand> thanks
[14:17] <mpt> charles, hi, perhaps you could pop in to #ubuntu-desktop to help us understand some indicator-power stuff
[14:17] <mpt> particularly the terminology involved in <https://code.launchpad.net/~mdeslaur/indicator-power/fix-priorities/+merge/260903>
[14:21] <greyback> bkchr: sorry man, that layer I don't know anything about. ogra_ might be able to point you in right direction
[14:27] <bkchr> greyback: okay.
[14:29] <TonyBoston> is there any new way to sync with owncloud?
[14:29] <bkchr> ogra_:  Hi, could you help with the adb daemon? I see in the kernel log that adb is started "adb_open", but my device isn't showing up at my PC. lsusb doesn't show anything. Added adb to /data/android-data/property/persist.sys.usb.config. Created the android-tools.override in /etc/init....
[14:30] <ogra_> if you already dont see it in lsusb there is a deeper prob than adb
[14:31] <ogra_> you should definitely see a connect event in dmesg when you plug it in and there should also be some entry in lsusb
[14:31] <ogra_> else i'd say the USB interface on  the phone side isnt up
[14:32] <bkchr> how can I check if the usb interface is up?
[14:32] <ogra_> well, via lsusb and dmesg as i said
[14:32] <ogra_> for the phone side ... that depends on your device and how it handles that
[14:32] <bkchr> dmesg on my pc doesn't show any connect/disconnect. Yesterday I tried the same kernel, but with an older image
[14:33] <bkchr> and my adb was working :/
[14:34] <ogra_> well, i havent touched adb on phones in about a year now (and dont work on the phone anymore ) ... but i doubt anythin in the rootfs has changed in that regard
[14:36] <bkchr> hmm okay, but I think you're right that the problem isn't an adb problem, more an usb problem.
[14:40] <bkchr> ogra_: I see "gadget: android_usb ready" in my kernel log. Maybe you have some hints, for what I could search?
[15:32] <lotuspsychje> http://linux.softpedia.com/blog/white-version-of-meizu-mx4-ubuntu-edition-no-longer-in-stock-491910.shtml
[15:32] <lotuspsychje> you guys bought too much
[15:34] <mariogrip> Yey, got my oneplus two today :D
[15:35] <lotuspsychje> nice mariogrip !
[15:35] <lotuspsychje> mariogrip: will the one+one image work on it?
[15:38] <mariogrip> lotuspsychje: unfortunately it will not work. but I hope the porting will go faster than on the one.
[15:38] <lotuspsychje> cool, good luck mariogrip
[15:39] <mariogrip> Thanks :D
[16:39] <old_benz> mariogrip: can't wait for the OPO...
[16:45] <mariogrip> old_benz: :D
[16:55] <taiebot> Hey ya all. Are we ever going to have scopes like Nearby on nexus 4 i have been waiting for a long time but they never appeared. :'(
[17:05] <taiebot> Also has there been any progress regarding app startup there was a thread on the mailing list talking about some work by Benjamin Zeller
[17:14] <old_benz> hey guys, I've checked out Ubuntu Touch following the "port to new dvices" guide
[17:15] <old_benz> I'm just very stupid, but where are the kernel sources?
[17:17] <old_benz> It says on the developer page: You can find your kernel config at kernel/[manufacturer]/[codename]/arch/arm/configs/ cyanogenmod_[codename]_defconfig.
[17:17] <old_benz> I don't have a kernel folder though, in my ~/phablet folder
[17:26] <Shihab> Hai
[17:35] <old_benz> I found this: git clone git://phablet.ubuntu.com/CyanogenMod/android_kernel_asus_grouper.git
[17:35] <old_benz> that's for the 2012 Nexus 7
[17:35] <old_benz> but I don't see a similar repo for Nexus 7 2013 - flo
[17:45] <old_benz> any help guys?
[17:49] <ogra_> old_benz, the kernels for the suppported nexus devices are somewhere on kernel.ubuntu.com
[17:49] <ogra_> (and packaged as debs in the ubuntu archive)
[17:50] <old_benz> so they are not build alongside Ubuntu Touch?
[17:50] <ogra_> what would "build alongside ubuntu touch" mean now ?
[17:51] <ogra_> the images are built from deb packages
[17:51] <old_benz> I see
[17:52] <old_benz> I only found this: http://kernel.ubuntu.com/git/ppisati/ubuntu-nexus7.git/
[17:52] <ogra_> you want to search for the codename ... i.e. flo
[17:52] <old_benz> don't find anything with that search
[17:53] <ogra_> that branch is most likely from a few years ago when we tried desktop on the tablet
[17:53] <old_benz> that's what I figure
[17:53] <ogra_> ask in #ubuntu-kernel then ...
[17:53] <ogra_> note that all of the above only applies to the nexus images
[17:54] <ogra_> non-nexus devices usually build their kernel from the android tree directly
[18:00] <old_benz> ogra_: thanks, asking there
[18:00] <ogra_> :)
[19:50] <ahoneybun> mariogrip: You've been quite lately
[19:54] <dhbiker> ogra_, did something major change today in rc proposed ?
[19:55] <dhbiker> battery life is quite better for me now on arale
[21:09] <old_benz> rtg: do you know where I might be able to find the sources of the custom CWM recovery that Ubuntu Touch uses?
[21:09] <old_benz> sorry, all: do you know where I might be able to find the sources of the custom CWM recovery that Ubuntu Touch uses?
[21:11] <old_benz> also, is it possible to install Ubuntu Touch without the custom recovery?  The kernel sources that "flo" is using are patched up to support this device.  The root of my problem is that the CWM recovery isn't able to mount any partitions
[21:55] <mariogrip> ahoneybun: Yeah, I have been way to busy lately. but now i
[21:56] <mariogrip> 'm back with a shiny new oneplus 2
[21:58] <ktatar156> Hello
[21:59] <ktatar156> I've got a problem with flashing
[21:59] <ktatar156> paste.ubuntu.com/12430800
[22:00] <ktatar156> Last message from terminal was ~25 minutes
[22:00] <ktatar156> should I stop that by CTRL+C and do it again? Can that break device?
[22:05] <mariogrip> ktatar156: The script only pushes the tarballs to device, and the devices recovery will install the updates on the system. so it is save to stop and do it again.  (dont reboot the device if there is a spinning Ubuntu logo, that means that it's progressing the tarballs and edits the system)
[22:06] <mariogrip> safe*
[22:06] <mariogrip> so, the script is safe to stop at any time.
[22:07] <mcphail> ktatar156: I've had similar problems with a silently dropped adb connection
[22:07] <mcphail> ktatar156: the channel flashing is certainly buggy
[22:07] <mariogrip> Yeah, a dropped adb connection will halt the script
[22:08] <mariogrip> halt/crash
[22:08] <mcphail> ktatar156: I've had better results flashing from recovery, but I don't know if that was just good luck
[22:09] <ktatar156> Thanks. So I must just try and try?:)
[22:10] <mcphail> ktatar156: yep :)
[22:10] <mariogrip> mcphail: Should be the same, the script will just "fastboot boot recovery.img" any way.
[22:10] <mcphail> mariogrip: I've never had a dropped connection when flashing from recovery, though
[22:11] <mariogrip> I dunno, but it *should* be the same, since it boots the same image
[22:11] <mcphail> mariogrip: yes, probably just luck
[22:11] <mariogrip> :)
[22:12] <mcphail> mariogrip: I did wonder whether there was a bug which makes the system drop adb connections, though
[22:12] <ogra_> the USB on the meizu is very picky in general
[22:12] <ogra_> thats a HW issue
[22:13] <mcphail> ogra_: i have the bq
[22:13] <ogra_> if you have a device with USB 1.1 port, try that ...
[22:13] <ogra_> or an 1.1 hub you can put in the line
[22:13] <ogra_> that usually tames it
[22:13] <ogra_> mcphail, yeah, i was more commenting on the problem above
[22:15] <ktatar156> So, to get best result, I should use ubuntu-device-flash touch --wipe --channel=ubuntu-touch/stable/meizu.en --bootstrap --recovery-image=recovery.img in fastboot mode, yes? Or other command?
[22:16] <ogra_> if you use --botstrap you dont need --wipe
[22:16] <mcphail> ktatar156: that will completely wipe the device
[22:16] <ogra_> *bootstrap
[22:16] <ktatar156> I want to delete as much as I can and reinstall all
[22:17] <ogra_> then --bootstrap is correct
[22:17] <ktatar156> without --wipe?
[22:18] <mcphail> ktatar156: you don't need --wipe to wipe the device if flashing from fastboot with --bootstrap
[22:18] <mcphail> (--bootstrap was enough for a full wipe for me, anyway)
[22:20] <ktatar156> ok, thanks
[22:20] <ktatar156> But still I'm not lucky man, can't flash it... maybe because of using Ubuntu in virtual box...,
[22:22] <mcphail> ktatar156: You're quite brave to be flashing a device from a virtual machine
[22:25] <ktatar156> Just can't make my arch working with that ubuntu-device-flash...
[22:28] <ktatar156> maybe phablet-tools? But how to use them - what command to flash with stable channell Meizu?
[23:10] <ahoneybun> nice mariogrip