[00:00] I think its wpa_supplicant that scans. [00:00] dobey: exactly (still, if you haven't scanned for 1h, please don't show the same APs, just refresh when I open the indicator..) [00:01] anyway, i suppose i should go do something else now [00:01] awe_: when you have time to have a look at the WiFi discussion above, please let me know if it's all under control or you want me to file bug and post logs etc...I didn't hear back from you about the ESSID issue anymore :) [00:01] dobey: yeah, and I should really go to bed :) [00:01] :) [00:01] it seems like the test is not flaky anymore, 800 runs without failure so far... [00:02] (last words...) [00:03] night o/ [00:06] faenil, please no more bugs... [00:06] ;D [00:06] yea, so just read the bt [00:07] thats an old one [00:07] :) [00:07] the dialog problem unfortunately is not going to be fixed unless the product team says so [00:07] as it requires investigation, ux design, ... [00:07] as promised [00:07] I made sure it's on the list [00:08] regarding some of the other issues [00:08] I'm working on it as we speak [00:08] unfortunately I'm not free to self-assign myself to any task I'd like to [00:08] so I'd been recently working on bluez for snappy [00:08] then I went on vacation [00:09] I'm back, and NM is my favorite project atm [00:09] why would iwlist wlan0 scan not show AP's sometimes? [00:09] use iw [00:09] iwlist is old [00:09] it also depends on the drivers [00:09] the best tools to look at available APs [00:09] are wpa_cli ( run as root ) [00:09] and nmcli [00:10] one of the issues with the version of NM that we use, is that NM keeps a separate accounting of APs [00:10] dont that all go through wpa_supplicant? [00:10] ( ie. it maintains it's own available list ) [00:10] yes [00:10] so wpa_s [00:10] responds to NM's requests to scan [00:11] and if/when NM decides to connect to an AP [00:11] it tells wpa_s to do so [00:11] but the issue was in the past, there were issues with a lot wifi drivers [00:11] especially around hidden APs [00:12] hudden AP should be banned [00:12] hidden [00:12] believe me, alot of things should be banned [00:13] anyways, we believe there's a condition where NM thinks that wpa_supplicant has roamed, and if is timed poorly, NM can hang [00:13] and it will stop scanning [00:15] faenil, so... I don't mean I'm not interested in the other specifics, but at the moment I'm trying to size up the effort to upgrade NM to a newer release, which includes a major re-write of the WiFi scanning logic [02:15] has tethering been fixed for mako? [02:33] might need some help in the near future [02:34] posted a couple hours ago [03:30] so ok [03:30] i am using M8 as my device [03:30] trying to port over Ubuntu Touch [03:30] Ubuntu says it uses cm-10.2 aka 4.4.2 android for the wrapper or whatever [03:31] I am using th ehtc one m8, which I believe came out during jellybean [03:31] there are a few errors i am concerned about [03:31] dtb tool, linux/include/msm_ion.h and a few others [03:31] i have ported many roms for quite a few devices for android [03:34] https://zerobin.net/?7cf46e1affcf21e3#ZJvaSDVcLdZ760moMJEjicPmG7A+jWcLMY/Nx/O+JGc= [03:34] out/host/linux-x86/bin/dtbTool', needed by `/home/punkunity/android/phablet/phablet/out/target/product/m8/dt.img'. Stop. [03:34] to summarize [03:41] https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/ [03:41] using this guide [03:42] and am now trying to just make a \n image for a suported, woking device [03:42] what jdk/jre version should i be using [03:42] sytem wifde? [03:43] so trying to build for mako aka nexus 4 [03:43] and it fails pretty quick [03:43] an di thought this was supported, ready to build device? [03:43] what am i doing wrong? [03:57] punkunity: I'm not sure, mako has an build-image, so there may be some guides for mako. === duflu_ is now known as duflu === Avasz_ is now known as Avasz === Avasz is now known as Guest59123 === Guest59123 is now known as Avasz === ecloud_wfh is now known as ecloud [07:10] ogra_: ping === orsonmmz|away is now known as orsonmmz [08:08] bah, no luck [08:08] when trying to do ubuntu-device-flash touch, I get "device cannot be detected over adb" [08:09] Tm_T: did you unloack your device [08:09] lotuspsychje: it doesn't fully boot [08:10] I can use fastboot to reboot the device for example, but can't get any other control it seems [08:10] Tm_T: sounds like adb cant see the device, did you install those android tools [08:10] lotuspsychje: yes [08:10] $ adb devices [08:10] List of devices attached [08:10] 75HACL6UHG82 device [08:11] ah it shows good [08:11] then you need to enter to the bootloader or something [08:11] adb reboot something..cant recall :p [08:11] hmmm, will try fastboot mode, but I suspect it isn't any better as there's no adb access then whatsoever [08:12] lotuspsychje: thing is, none of the adb commands get through [08:12] hmmz [08:13] Tm_T: you enabled usb debugging too right? [08:14] lotuspsychje: where, how? [08:14] I've flashed this device successfully before (: [08:14] kk [08:14] Tm_T: what you get when you: adb reboot bootloader ? [08:15] lotuspsychje: I get fastboot mode [08:16] and then there's no adb available [08:16] Tm_T: how about sudo fastboot oem unlock [08:16] https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/ [08:17] lotuspsychje: I'm unsure how that would help, this is Meizu ubuntu device, but I can try (: [08:18] FAILED (remote: unknown command) [08:18] Tm_T: isnt there like a button combo that resets your device to original? [08:19] or did something corrupt your image [08:20] OTA update to RC did break this, yes (: [08:20] there's "recovery mode" in meizu ubuntu edition that doesn't seem to do anything [08:20] hmmz [08:20] I'll try one more thing [08:20] Tm_T: is it the mx 4? [08:21] yes [08:21] http://askubuntu.com/questions/672185/reinstalling-ubuntu-touch-on-the-meizu-mx4-ubuntu-edition [08:21] I'll try --bootstrap if that would make things different [08:22] lotuspsychje: ye I try avoid doing those windows-based things [08:22] as I have no such thing available (: [08:22] and have zero interest having [08:23] oh, there's support for other platforms too? [08:23] seems like it [08:23] interesting, will try that too then, thanks [08:23] np [08:23] flu doesn't help maintaining patience (: [08:24] yeah got one too [08:24] --bootstrap does seem to do something === orsonmmz is now known as orsonmmz|away === orsonmmz|away is now known as orsonmmz === davidcalle_afk is now known as davidcalle [08:27] not alot of usefull guides for the mx out there grr [08:31] lotuspsychje: I noticed that [08:40] flashing failed, recovery mode is broken? === orsonmmz is now known as orsonmmz|away === orsonmmz|away is now known as orsonmmz [09:02] Tm_T: have you installed an adb-enabled recovery image? [09:03] mcphail: I have what I have from canonical/meizu + flashed rc image once [09:04] Tm_T: the default recovery doesn't have adb enabled [09:04] hmm, default recovery does what? [09:06] Tm_T: the default recovery really just lets you boot the phone, I think. If you have the adb-anabled recovery you can use that along with the --bootstrap command to perform a full wipe and reinstall [09:06] mcphail: default recovery lets boot the phone to some specific state where user can do something? [09:07] currently it doesn't allow me to do anything [09:08] yes - if you're locked out you'll need to flash from fastboot using the --bootstrap command (which will fully wipe the phone). See https://wiki.edubuntu.org/QATeam/ChannelsToFlash [09:09] Tm_T: that is what I had to do after a little adventure using the -devel channels on the bq, but I've seen other people on here having to do the same thing with the meizu [09:10] mcphail: so I flash recovery.img first? [09:10] Tm_T: I don't think you actually have to flash it, if you specifiy it n the command line as per that webpage. i _did_ flash it though [09:11] mcphail: interesting, I'll give it a go [09:11] Tm_T: the important thing is to make sure you're booted into fastboot (rather than recovery) before you start the process [09:12] but I still don't understand what's the purpose of default recovery mode is and how it is supposed to work [09:12] mcphail: ye, bootloader that is [09:13] Tm_T: sturmflut has made an excellent series of blog posts about the low-level stuff on the bq phone, which is worth a read if you're wondering about what all these things actually do on Ubuntu devices [09:14] Tm_T: I think adb has been removed from the consumer recovery images for security concerns [09:14] Tm_T: see mailing list [09:14] mcphail: I think there's some variation between BQ and Meizu [09:14] davmor2: thanks [09:14] Tm_T: yep. I don't think the meizu has been as well explored as the bq [09:15] davmor2: I get the same error still, no access to recovery mode [09:16] $ ubuntu-device-flash touch --channel=ubuntu-touch/stable/meizu.en --bootstrap --recovery-image Downloads/recovery.img [09:17] Tm_T: Unplug the device, press power and hold till it turns off, then press power then quickly volume down to enter into fastboot mode then try again [09:17] davmor2: I'm doing it like that, yes [09:17] Are you unplugging it [09:18] it begins the process fine, then it boots to recovery mode and waits timeout to spit error [09:18] davmor2: yes [09:18] because without unplugging it doesn't get fastboot connection [09:18] Flashing version 10 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale [09:18] Failed to enter Recovery [09:19] Tm_T: when it reboots to recovery, have you then tried the "boot device" entry on the menu? [09:19] what menu, there's no menu [09:19] there's nothing except ubuntu logo [09:19] big or small? [09:20] thumbnail size [09:20] have you left it to work for a few minutes? [09:21] yes [09:21] even hours before, I've never seen anything useful in Meizu recovery mode [09:22] you don't get a menu in the recovery? === chihchun_afk is now known as chihchun [09:22] Tm_T: Okay try the following. Drop the device into fastboot, in the terminal type fastboot flash recovery recovery.img and then try the ubuntu-device-flash command again [09:22] davmor2: thanks, will try that (: [09:23] mcphail: it's a issue with mx4 it enters recovery but slow so times out the adb session [09:23] aah [09:24] On the bq I have to press the "volume up" button to go from the Ubuntu logo to the menu in recovery [09:27] davmor2: recovery flash seemed to go in just fine, trying ubuntu-device-flash now [09:27] Tm_T: if it sticks at the Ubuntu logo again, try pressing "Vol up" to see if that works on the meizu [09:28] mcphail: nope, never had [09:28] davmor2: no luck [09:28] :( [09:28] adb still doesn't see the device, flash tool still spits out the same error [09:29] Tm_T: can you connect with adb now when the device is in recovery mode? Just a simple "adb shell"? [09:31] mcphail: no [09:31] I managed to adb say the device is there but offline [09:31] hmm. Sounds like you're getting close to having this working [09:32] ooooh now we're getting somewhere [09:32] when it failed again, I fiddled with it and "adb devices" listed the device in recovery [09:33] then "ubuntu-device-flash touch --channel=ubuntu-touch/stable/meizu.en --device arale" [09:33] sounds promising [09:33] .... and now we're "2016/02/25 11:33:07 Rebooting into recovery to flash [09:34] so with good timing one can get that working it seems [09:34] worth documenting [09:34] Tm_T: I usually get a "failed to enter recovery" error at that point, but it can be ignored [09:34] * lotuspsychje brings out the fireworks [09:35] it's booting up... [09:35] ... [09:35] * mcphail crosses fingers [09:35] hehe [09:37] it's up, and I don't see any data lost [09:37] !!!! [09:37] !yay | Tm_T [09:37] Tm_T: Glad you made it! :-) [09:37] thanks mcphail lotuspsychje and davmor2 [09:37] so what did the trick now? [09:38] flashing the recovery mode + timing [09:38] right [09:38] apparently that adb in recovery mode is online only for a short time [09:38] so you have to retry flashing with correct timing [09:38] Tm_T: maybe you can file a bug and solve it right away for future reference? [09:38] lotuspsychje: ye, that too [09:39] lotuspsychje: sounds like the known problem davmor2 mentioned above [09:39] mcphail: yeah [09:40] timing is out of our hands unfortunately plays up more on usb3 and certain usb leads over other and the list of parameters goes on but you get the hint [09:40] davmor2: ye, I understand === chihchun is now known as chihchun_afk === vrruiz_ is now known as rvr === Chipaca` is now known as Chipaca === xiinotulp is now known as plutoniix === JMulholland_ is now known as JMulholland [11:00] hey all [11:01] I've found this pic on trello in Unity8 landing for OTA-10: http://picpaste.com/pics/indicator-FMruC8JY.1456397893.png [11:01] What is this blue color and the new toggles. Is this a new theme for OTA-10? [11:02] ka, elisa === KathyReid_ is now known as KathyReid [11:28] robin-hero: voodoo [11:28] davmor2, ? [11:29] robin-hero: the blue and new toggles, you asked what it is, it is voodoo :P [11:30] davmor 2, Thanks, but I'd really appreciate if somebody explain the real situation :P [11:30] too bad it is not #009bf9 would match ubuntustudio :p [11:32] robin-hero: :D man you just want the moon on a stick don't you :D [11:32] could someone please tell me where can i find what the OTA-10 adressed? :) [11:33] sakrecoer_: ota10 isn't released yet [11:33] well, i got a 40mb package yesterday that said OTA-10 (o.O) [11:33] sakrecoer_, that was OTA-9.1 [11:33] or rather, it said "ubuntu 10".. [11:34] a hotfix release [11:34] davmor2: you clearly need a crystal ball [11:34] ok :) [11:34] sakrecoer_: no it said image 10 if you open system settings and click on about is will say OTA-9.1 [11:34] maybe, i did it now, don't know how to check again [11:34] davmor2, why is this that hard to answer my question? :D [11:35] i'm pretty impressed i must say [11:35] sakrecoer_: the image number is sequential so we can't change that 9.1 is a tag we can modify so we know the image you are actually on [11:36] robin-hero: because I know nothing about it [11:38] ah yeah! found it! https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-9.1 hehe. i actualy need to write one for ubuntustudio beta1 so i will learn from you [11:39] one=release note article [11:40] robin-hero, yes it's the new theme for OTA10 [11:41] jibel, \o/ and can I see some other screenshots somewhere? [11:42] robin-hero, I don't have any, but you can install the silo :) [11:42] or wait until it lands in rc-proposed [11:43] jibel, OK :) [11:46] The lack of documentation hurts. Half of the links in the porting wiki are broken === _salem is now known as salem_ [12:32] hola, anyone know of any individual working on a port to Nexus 6? Can't find anything easily on the tubes. [12:34] elijah: you can vote with a donation at https://devices.ubports.com/#/ [12:34] mcphail: ahh, that is the site I saw the other day, thank you! [12:38] So, I have a Nexus 6 that crashes once a day, even in safe mode which is the catalyst reason I want to move to Ubuntu Touch (my daily driver is 14.04). Now, it may crash the same in UT too but that is yet to be seen. I can sacrifice this device and try to get a Nexus 5 so I can run UT on it. Do you think my Nexus 6 that is in good condition other than the [12:38] fact it crashes once a day would be accepted as a debug/test device? [12:38] charles, https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783 [12:38] Launchpad bug 1549783 in indicator-datetime (Ubuntu) "Indicator shows "Tomorrow" for an alarm happening today when checked after midnight" [Undecided,Confirmed] [12:41] elijah: I think it would be one of those things you'd never know until you started working with the device. If there is a major hardware problem, it is going to be incredibly frustraing working with the device. However, I suspect mariogrip would be very pleased to get hold of a device to try hacking it [12:43] mcphail: Yah, just saw the page to donate devices, emailing @mariogrip now [12:44] elijah: he's usually active on this channel as well, although I suspect he might be at MWC showing off his devices ;) [12:48] mcphail: Fun [12:51] mcphail: Interestingly, @mariogrip is the one who gave me some hope with the switch because he posted something showing Project Fi working on a Nexus 5 with Ubuntu Touch. I thought it was interesting that he was also leading the UBPorts project! [12:51] elijah: I get the feeling he is some kind of godlike genius [12:51] mcphail: I also would like to eventually help developing for the platform/OS [12:52] mcphail: Maybe a little bit of that but probably just someone who has surpassed 10,000 hours ;) [12:52] :) [12:53] mcphail: Oh, I stand corrected, it wasn't @mariogrip with the project Fi, it was Ian Santopietro -> https://plus.google.com/+IanSantopietro/posts/5HjpzEKtLG5 [12:54] abeato: I've pushed new version of code fixing formatting issue. Could you please have a look again? [12:54] Either way, I welcome the pain that will come with switching [12:54] peat-psuwit, sure [13:50] Hello, I am looking for someone who can give a try to my .click app/game before I uploaded to the store. [13:50] This is an update of an existing app. I want to see if it works because I have no ubuntu device. [13:51] preferably, I'd like to know if it's still work with device with ota 8. let me know if you can try it. [13:51] slvn_: there is an ubuntu-touch emulator out there you can install [13:52] lotuspsychje, this is for final testing, I would prefer a real device. I have already use to the build bot marvin, to make sure it starts. but just want a double check. [14:49] mzanetti, hey, are you going to use QSystemInfo 5.5 now in the shell, or are you waiting for something in the uitk? [14:49] jgdx, "something in uitk"? Not sure what you mean. I'm going to use QSysteminfo 5.5, yes [14:50] mzanetti, yeah, ken said the uitk was exposing abilities in the uitk. But okay [14:50] <_Sponge> Looks like the bq phones are getting a_lot of cover-flak from ebay. [14:50] jgdx, not really sure what that would be... except duplicating the API? [14:50] <_Sponge> popey, Not sure if this is legit. But hey-ho . http://ebay.eu/1S3AGWa [14:50] which doesn't seem to make too much sense to me [14:52] mzanetti, while on the subject, do you have a branch for u8 moving to QSystemInfo? [14:52] jgdx, not pushed somewhere yet... gimme a sec [14:52] mzanetti, thx [14:53] jgdx, lp:~mzanetti/unity8/move-to-qinputinfo [15:10] kenvandine: ping [15:11] kenvandine: The "Wi-Fi Displays" page of System Settings is broken on Nexus 4: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1549605 [15:11] Launchpad bug 1549605 in ubuntu-system-settings (Ubuntu) "Wi-Fi Displays page fails to load on Nexus 4" [Undecided,New] [15:11] I'm on rc-proposed [15:11] I think the package is missing some files [15:12] mhall119, huh? Wi-Fi Displays hasn't landed.... [15:12] or it wasn't supposed to have landed :) [15:13] kenvandine: well....it has [15:13] in system settings anyway [15:14] mhall119, do you maybe have silo 0 installed? [15:15] i don't have wifi displays on my arale [15:15] and the branch hasn't been merged [15:15] I do have silo 0 installed, but I haven't apt-get upgraded in quite a while [15:15] mhall119: rc-proposed or rc-proposed-pd [15:16] mhall119, it's been in silo 0 for weeks [15:16] channel: ubuntu-touch/rc-proposed/bq-aquaris.en [15:17] purge silo 0 [15:17] kenvandine: ok, maybe I did get it that way [15:17] had to have :) [15:17] but I *like* silo 0, it has all the fun stuff :) [15:17] whew... /me breathes again [15:17] haha [15:17] yeah, I think I got aethercastcrl from there [15:17] so my mako has silo 0, and that page loads [15:18] hmm, maybe I just need to apt-get upgrade then [15:18] regardless, that code is no where near ready to land :) [15:18] that's what makes it "fun stuff" [15:18] mhall119, it's taped together just enough for demo purposes :) [15:19] what version of ubuntu-system-settings do you have? [15:19] the overlay PPA has a newer version than silo0 it seems [15:21] kenvandine: I can confirm no widi here in settings on todays rc-proposed [15:21] Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/stable-phone-overlay'. [15:21] The team named '~ci-train-ppa-service' has no PPA named 'ubuntu/stable-phone-overlay' [15:21] hmm [15:21] citrain seems to be unhappy [15:22] kenvandine: I assume it is in the Network section like hotspot or is it in a section [15:22] davmor2: it's in Wifi section [15:23] davmor2, yeah, it never landed :) [15:23] kenvandine: we are right and mhall119 is wrong stick with that I'll back you up :D [15:24] :) [15:24] mhall119: did you install the pocket-desktop version on your mako? [15:24] i am curious why the page isn't loading for mhall119 though [15:24] it definately should [15:24] davmor2: not this one, no [15:25] silo 0 is extremely experimental, i don't think it's included in ubuntu-pd [15:25] kenvandine: it's because it doesn't have the Displays component, which I assume should be in /usr/share/ubuntu/settings/system/qml-plugins/wifi/aethercast/ but that whole directory doesn't exist [15:26] kenvandine: ha I bet I know what it is, mhall119 will of upgraded at some point that's probably broken connections when the new image got installed [15:26] that sounds likely,yeah [15:27] could be [15:27] it loads here [15:27] and i know it's been working for morphis [15:37] mhall119, warning... don't try to upgrade with silo 0 installed [15:37] mhall119, i just did, it removed the shell :/ [15:37] i think it downgrades mir [15:37] * kenvandine wasn't paying attention and now has the google screen [15:38] heh [15:38] time to flash [15:38] I got very good at rebooting to recovery and flashing when I last played with silo0 [15:38] i think i see why, it downgraded mir [15:40] At one point I even modified the citrain tool to make me confirm the package install/upgrade/remove list instead of doing it automatically [15:40] so I could check if Unity was being removed === dandrader_ is now known as dandrader|afk === orsonmmz is now known as orsonmmz|away === dandrader|afk is now known as dandrader [16:53] Hi, Is Uubuntu Touch java based like Android? [16:57] no [17:00] On which smartphones does it run properly? [17:00] bq aquaris E5 for example [17:01] I mean which doesn't comes straight from factory. And a bit stronger and faster that that bq [17:01] there are a few retail phones available [17:01] the nexus4 is the development phone [17:03] Thanks. It's a shame that it doesn't have an sd card slot and it's battery life is pour. [17:04] battery life on nexus4 is basically fine here [17:04] well, with ubuntu anyway [17:04] Sounds good [17:05] you can't assume that the battery life complaints from people running android 4.2 on the nexus4 are going to be valid if you are running ubuntu [17:05] just the same as that battery life aren't necessarily equal between windows and ubuntu on a laptop [17:05] dobey, True [17:06] Do you use Ubuntu on Nexus? [17:07] yes [17:07] Everything is fine? [17:08] i have a nexus4 for development; it doesn't have a SIM in it though, so perhaps a bit better battery life than with a SIM, but battery life is plenty fine on it [17:08] Oh, By the way did you have you already tried the Plasma version? [17:08] well, my nexus4 is broken all the time, because i use it for development :) [17:09] i haven't, no. i don't think it maintains the same security model/policies that ubuntu does [17:12] It has the same apps like on Ubuntu? It it has, is the GUI optimized for mobile phone, if it doesn't have has it an Ubuntu "app store"? [17:14] Linnak: you'd be better asking the plasma people that one really. [17:14] I'm asking Ubuntu Touch and not plasma [17:18] oh, i misunderstood [17:19] Linnak: ubuntu-touch uss click packages (and will switch to snappy in the future iirc). you can use apt-get if you make your systempartition rw but that will stop getting OTA updates. [17:20] Can I see somewere what kind of and how many packages are there already? [17:21] yes, someone made a mirror for the store. but i dont know the link right now [17:21] Linnak: https://uappexplorer.com/ [17:21] davmor2, tHANK YOU [17:25] hi, can you help me? cp: cannot create regular file ‘/usr/share/locale-langpack/sk/LC_MESSAGES/ubuntu-system-settings.mo’: Read-only file system [17:25] phablet@ubuntu-phablet:~$ [17:26] P_E_T_O: if you want to modify anything under /usr/, you have to make the root mountpoint rw rather than ro. This is not generally recommended, and can affect future updates [17:27] mcphail: then how can i test my translated locale? [17:27] P_E_T_O: you can remount rw and accept the risks ;) - your phone can always be reflashed if it breaks... [17:28] mcphail: sudo mount -o remount,rw '/usr' -- will work? [17:28] P_E_T_O: "sudo mount -o remount,rw /" is the command, iirc [17:38] mcphail: thanks it works :) and for the translation i need just .mo file? can you help me? === dandrader is now known as dandrader|afk [18:00] mariogrip: have you had a chance to document those kernel issue yet? I'd really like to get that info to the Fairphone guys to look at head of our next call === alan_g is now known as alan_g|EOD === dandrader|afk is now known as dandrader [18:26] Hi, guys! I have some questions on UT topic.. As I understood BQ M10 UT tablet is not able to run x86 apps, for example TeXstudio. Am I right? [18:30] ba2095: I assume so. It is an ARM device, so will only run ARM apps [18:34] As I got it.. Made me sad, not able to be a real day-to-day machine than, will wait for something like Core-M based tablets w UT. And another one, didn shure if it's system or app related. On my krillin when I'm listening to music via Music app using [18:34] ba2095: while you could run the traditional .deb packages you dont want them to run since they are not made for convergence [18:35] ba2095: nearly all packages in the ubuntu repos are build for arm too. [18:35] but that is again .deb packages vs click packages on UT. [18:36] urbaneaers headphones w mic, no reaction on button pressed(next/prev track or stop/play even). Ok w ipod [18:40] Hi peoples ;) [18:40] should I adress this as bug/feature-request to UT sysimage or to Music app? [18:41] ba2095, there are already existing bugs for that, let me see if i can find them [18:41] hi! [18:41] k1l: huh? [18:41] ba2095, and only recently has the music-app/platform added support for this to be even possible. Now they need to just link up the button presses [18:41] dobey: ? [18:42] k1l: the "convergence" feature of the m10 is exactly running traditional .deb packages, in a chroot [18:42] dobey: ah its the regular .deb isntall on "dockmode"? [18:42] ba2095: you should be able to run texstudio on the M10; it's open source and has armhf packages [18:42] dobey: good to know [18:42] k1l: that is what libreoffice/gimp are yes. it's running them with XMir in a chroot [18:43] k1l: so they are confined a bit still [18:43] ba2095: then you can use all usual ubuntu packages when the tablet is docked. [18:43] well, you can use anything that is built for arm, pretty much [18:43] only tricky bit are PPAs then, because they dont get build for arm as standard [18:44] ba2095, found at least bug 1309731 and bug 1473134, i believe there were others as well [18:44] bug 1309731 in Canonical System Image "headphone button does not play/pause music." [High,Confirmed] https://launchpad.net/bugs/1309731 [18:44] you could theoretically use qemu to emulate x86 and run some things, but it would be low [18:44] bug 1473134 in indicator-sound (Ubuntu) "handle headphone button" [Medium,Confirmed] https://launchpad.net/bugs/1473134 [18:44] k1l: i don't know that PPAs will be "supported" anyway [18:45] Great! And the last one.. Using terminal app i was able to use python/perl scripts on my phone, but cant run gcc compiled binaries, cos container restrictions. Edited container configs for terminal app by hand, but maybe will be better to have kind of "~/Projects" folder w execution rights for binaries? [18:45] what do you mean you can't execute binaries? [18:47] because of bug #1534807 ? [18:47]