=== JanC_ is now known as JanC === _salem is now known as salem_ === JanC_ is now known as JanC === salem_ is now known as _salem === LiQiong_Lee1 is now known as LiQiong_Lee === ecloud_wfh is now known as ecloud === chihchun_afk is now known as chihchun === marcusto_ is now known as marcustomlinson_ === marcustomlinson_ is now known as marcustomlinson === chihchun is now known as chihchun_afk === curtness is now known as strahtw === _salem is now known as salem_ === salem_ is now known as _salem === curtness is now known as strahtw === _salem is now known as salem_ === boiko_ is now known as boiko [13:16] will the sdk ever have its own popup menu implementation? [16:18] hi [16:24] welcome, Ab3L === JanC is now known as Guest36981 === JanC_ is now known as JanC [18:03] hi, how can i try ubuntu touch on an x86 tablet? [18:06] did it came with Windows? [18:07] most x86 tablets are a bit weird, so the basic answer is probably "not easily" [18:08] if it has proper UEFI, you can probably install desktop Ubuntu, but not all hardware will work [18:08] and no easy way for Ubuntu Touch [18:09] well you can run unity8, which is not necessarily the same as the phone/tablet images at the moment. [18:10] even with weird EFI, if it can do legacy boot you can install standard ubuntu on it i think. [18:10] UEFI on Intel Atoms can't legacy boot generaly [18:10] *generally [18:11] i think all my atoms can, but they are convertibles, not pure tablets [18:16] dobey, no it's not weird, it's pretty much just as weird as any given windows/linux laptop :D [18:17] and it's an intel core [18:17] in other words, i have no trouble running the desktop version of ubuntu, but i want to see what's the fuss about ubuntu touch [18:18] do you mean "the same thing that's the current supported phone/tablet images" or do you mean "unity8" by "ubuntu touch" there? [18:21] most times its crappy 32bit uefi :/ [18:22] well, if it can run ubuntu desktop there is no reason why the unity8 session wouldnt run as well ... [18:22] but that will only give you an impression, not the very exact thing you get with touch onn a phone [18:22] (pretty close though) [18:23] yes, that's why i asked what the goal is exactly :) [18:47] dobey, i mean the thing that canonical advertises on the ubuntu site under "tablets" [18:48] i want to see what the hell is happening on actual ubuntu touch products like that BQ tablet :) [18:50] and sorry for late replies [18:52] pauliunas: then the quick answer is no. longer answer is sort of but not exactly, and not especially easily [18:54] you can try the bits of where things are heading a little more easily, but still may not be quite what you expect [18:54] why don't they just make it public? that way they would get actual developers for this platform... [18:55] it is public [18:55] because right now it can only be tested on some phones [18:55] ok, so if it's public, why can't i install it on my tablet? [18:55] there is no image built for your tablet [18:56] arm/android phones/tablets do not work in the same way as traditional PCs in terms of booting and device access [18:56] the phone/tablet images are based around the needs of those types of phones and tablets, not generic x86 platforms [19:01] yes i know [19:01] but since there are no widely available ubuntu touch tablets, wouldn't it make sense to just release a generic x86 image that developers could use? [19:17] pauliunas: there is no such thing as a generic image in terms of phone/tablet images; the x86 ISOs are the only thing close to "generic" and you can run most of the core stuff just fine from there with installing the snap [19:18] pretty much everything is packaged in the archive or overlay PPA, or as snaps; in terms of developing the future of ubuntu on devices [19:23] dobey, i didn't mean a generic image for android tablets, as that wouldn't be possible.. i meant a generic image in the same format as ubuntu desktop [19:24] i think it can safely be called "generic image" as it runs on every [19:24] pretty much every x86 computer* [19:27] pauliunas: https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc [19:28] also, 16.10 and zesty have unity8 available to test by default [19:28] dobey, this looks interesting :) thanks for sharing [19:29] but how close is it to the retail experience? [19:29] (just out of curiosity, it's not really important) [19:29] not very [19:29] so there's currently no way to see what's the deal? [19:29] there are a lot of stumbling blocks in getting things moved to snaps, and making various bits work better on x86 [19:30] but there are changes landing pretty much daily [19:31] i've been waiting for over a year.. :/ i guess i should just give up :D [19:31] not sure why you didn't just get a wifi nexus 7 2013, if what you want to play with is the tablet image [19:32] actually, i wanted it to become my daily driver... xD [19:33] as in, on my phone, desktop, tablet... full convergence just like they marketed it [19:33] well, thanks for help, i gotta go now [19:33] well, it's coming [19:33] meh [20:14] anyone with some knowledge on enabling usb tethering It looks like nm detect the phone as a wired connection but there is never a connection which gets establised [20:15] i am currently looking at this https://danielpocock.com/android-betrays-tethering-data not sure it is related [20:25] taiebot: it worked just fine for me when i used it ~1 year ago with my nexus 5 [20:25] that's about all i know though :) [20:27] dobey it seems to work but maybe network manager cannot connect to it. Indicator just speens forever [20:35] taiebot: don't recall that problem [20:35] ok i think i have found my answer https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1427697 [20:35] Ubuntu bug 1427697 in dbus-property-service (Ubuntu) "Malformed /etc/NetworkManager/system-connections/tethering on mako" [High,Confirmed] [22:08] yeah managed!!! === salem_ is now known as _salem