=== everbrew_ is now known as everbrew
=== balloons_ is now known as balloons
=== deshack_ is now known as deshack
=== vika is now known as vik
=== Azelphur_ is now known as Azelphur
=== nhaines_ is now known as nhaines
[07:13] <uhhimhere> how do i check if I have a usb OTG capable device?
=== l3on_ is now known as l3on
[09:19] <cpyarger> has anyone ported utopic or vivid for the maguro, toro?
[09:41] <uhhimhere> hi guys how do i turn off the splash screen on my android phone so that I can see all the bootup messages?
[12:46] <Ozymandias42> hi. is anyone here with experience with the HP Stream 7 ?
=== Guest4192 is now known as Zic
[13:24] <timocov> Hello everybody. Where I can see builds?
[13:25] <ogra_> with the --show-image option to ubuntu-device-flash you can see the images for a specific device and channel
=== saidinesh is now known as saidinesh5
=== jgdxx is now known as jgdx
=== sturmflut_ is now known as sturmflut
[13:55] <taiebot> Hi all i am going to report that 3g does not work anymore on mako vivid r87 but does anyone confirm? There is also in the apn section in system settings carrier. if you enter and exit constantly the APN section you add one entry any time you re-enter http://i.imgur.com/i0F7TZR.png
[13:59] <sturmflut> taiebot: Looks like a case for a bug report, yes. I can't confirm since the SIM in my mako is not 3G enabled
[14:26] <sturmflut> Hm. I managed to get WhatsApp Web working as an Ubuntu Touch Web App, but does anybody know if it is "legal" to do so? WhatsApp is known to block users who are using third-party apps.
[14:27] <Stskeepz> generic advice is not to name whatever you've made *whatsapp*.. that seems to go south quite quickly for many
[14:27] <sturmflut> Stskeepz: Jep
[14:27] <taiebot1> sturmflut that would not be a third party app as it is developped by whats app..
[14:28] <cwayne> yeah but whatsapp doesn't appear to be a particularly rational company, wouldnt be surprised if they blocked it
[14:29] <sturmflut> cwayne: In this case it would be quite hard to even find out if you used the app or not. It is just a browser shell with a faked user agent string. From outside it looks like I am opening https://web.whatsapp.com/ with Google Chrome.
[14:30] <sturmflut> cwayne: But you're perfectly right
[14:30] <cwayne> right, that may be okay then.. just always paranoid with them :)
[14:31] <cwayne> which pisses me off btw, they're kinda like the anti-ubuntu/oss
[14:31] <sturmflut> Jep. Personally I hate them, but people are going to want WhatsApp when the phones ship. Which is in seven days.
[14:33] <cwayne> yes and yes
[14:33] <cwayne> :)
[14:33] <sturmflut> Maybe it's better to not publish the WebApp and wait until WhatsApp Web supports other browsers than Google Chrome. Then people can just use the built-in browser.
[14:35] <taiebot1> sturmflut that does not make any sense because they would not support oxide. so why waiting?
[14:36] <sturmflut> taiebot1: I don't know their plans. Maybe they'll distinguish by user agent, then Oxide will never be supported. Or they just accept all browsers and detect the available capabilities. Both ways are possible.
[14:42] <sturmflut> taiebot1: Wrapping WhatsApp Web in Oxide has its limitations anyway. You can chat and send existing files, but the camera and the microphone don't work and you don't get any push notifications. It also crashed a couple of times already.
[14:43] <taiebot1> sturmflut: realised also that you will need an existing account with another phone also.
[14:43] <sturmflut> taiebot1: Jep, you have to authenticate the Web version against an existing app installation on an existing phone. Using a QR code.
[14:51] <sturmflut> I think the major problem is that we don't have a single alternative messenger app. No Threema, no Telegram, no Jabber, nothing. There was a project to port Telegram but it hasn't been updated for a year.
[14:52] <sturmflut> Does the Facebook WebApp support chats?
[14:54] <cwayne> sturmflut there's webogram
[14:54] <cwayne> which is telegram
[14:54] <sturmflut> cwayne: Right, my fault
[14:55] <sturmflut> And DTelegram, which seems to be the same
[14:57] <cwayne> but yeah, your point remains valid
[15:10] <taiebot1> sturmflut http://andregarzia.com/posts/en/whatsappdoesntunderstandtheweb/
[15:13] <taiebot1> So it also needs another phone connected to the internet to work .. =-O
[15:17] <sturmflut> taiebot1: Haha yes, my phone was online all the time, I didn't even notice that the webapp does no longer work if I take the phone offline
[15:19] <taiebot1> sturmflut i do not think its worth a webapp will make a lot of people think it can connect to whats app while it cannot
[15:19] <sturmflut> taiebot1: Yep
[15:20] <cwayne> god i hate whatsapp
[15:21] <cwayne> i really dont get why its so popular
[15:25] <sturmflut> cwayne: It was one of the first apps of this kind, it was free for the first year, the registration process was extremely simple (there was none) and it just worked
[15:26] <cwayne> first of its kind? isn't it just xmpp (slightly altered)
[15:27] <sturmflut> cwayne: Jep, like Facebook Chat.
[15:30] <sturmflut> cwayne: It is just a question of marketing and design. If XMPP was as easy to set up as WhatsApp is, and was openly marketed as an SMS/MS replacement, maybe WhatsApp would have never been developed.
[15:31] <cwayne> right
[15:31] <cwayne> and the world would be a better place :P
[15:46] <vik> does anyone knows where to edit persistent adb settings for ubuntu touch ? and where to put adb_keys ? thanks
[15:46] <vik> (touchscreen broken...)
[15:49] <sturmflut> vik: Hmmmm, good question.
[15:50] <vik> I've fiddled yesterday with this and found some files lije persist.radio.adb_log_on in /data/android-data/property
[15:50] <vik> (added needed files, does not work)
[15:51] <vik> i've fiddled with default.prop
[15:51] <vik> and build.prop in system
[15:51] <vik> does not work either
[15:51] <vik> i've made a find . -name "*.build" and etc
[15:51] <vik> erm *.prop
[15:52] <vik> but I'm running out of idead
[15:52] <vik> I tried to run a usb mouse in OTG with a custom Y adapter for powering everything
[15:52] <vik> but seems that nexus4 rom does not have otg enabled
[15:52] <vik> or that mouse does not work on welcome screen
[15:55] <vik> basically the only thing I want to do is activate ssh and connect to my wifi network
[15:55] <vik> but for this I think adb shell is mandatory
[16:21] <studio_> hi
[16:22] <studio_> someone here or only bots?
[16:25] <studio_> nobody here?
[16:32] <studio_> what kernel is ubuntu-touch using?
[16:35] <studio_> hmmm ....
[17:03] <studio_> hello?
=== chihchun is now known as chihchun_afk
[17:31] <studio_> come on, why i get no answer here?
[17:40] <skweek> studio_, whats up
[17:42] <skweek> my kernal version?
[17:42] <studio_> yes
[17:42] <skweek> 3.16.0.30?
[17:43] <studio_> i dont't know, therefore i asked
[17:44] <studio_> i am looking for a new kernel for the bq Aquaris E4.5
[17:44] <skweek> i'd like to try touch on this device
[17:45] <studio_> i don't understand, are you still using ubuntu-touch?
[17:46] <skweek> i'm not, I have ubuntu installed on a tablet pc that disconnects from the keyboard to turn into a slate touch screen
[17:48] <studio_> sorry for my english, you are still running Ubuntu-Touch on a tablet?
[17:49] <skweek> I never have but I would love to try and see if it were better and more suited for this device lenovo miix 2 11.6 http://goo.gl/qM0b7L
[17:53] <studio_> @skweek this is not an embedded device ... i need help for a bq Aquaris E4.5
[17:55] <skweek> hmm
[17:56] <skweek> sorry
[17:57] <studio_> @skweek why do you not install the "normal" ubuntu?
[18:00] <skweek> I have, the touch screen support is fairly limited
=== CarlosNeyPastor_ is now known as CarlosNeyPastor
[21:55] <zmaj_> can't wait for the bq phone launch next week :D
[23:33] <adrian47> Hello, this line: "mount --move /android-system ${rootmnt}/android/system" from touch script did not work for me, what can i do?
[23:34] <adrian47> android.img is properly mounted at /android-system but moving didn't work