[00:15] <ED_> EDToday unable to download and install available updates for Ubuntu Touch after OS23 install yesterday.... Anyone else experiencing this problem? Just checking prior to submitting new bug report.... Thanks in advance, ED
[07:08] <simosx> I got a message from a user of our LoCo that with the recent phone update r23, the phone bootloops. Is there a page that describes how to resolve, preferably without losing data? A short description should suffice, I'll guide them.
[07:30] <lotuspsychje> simosx: wich device and channel?
[07:54] <simosx> lotuspsychje, bq E4.5, channel: the default one (bq).
[07:54] <lotuspsychje> simosx: do you have an ubuntu pc available?
[07:55] <simosx> simosx, yes there is (I am doing remote help to a member of the community, so I am relaying).
[07:56] <miltosk> μπηκα... καλημερα
[07:56] <lotuspsychje> simosx: backup all data to the ubuntu pc
[07:56] <simosx> miltosk, hi Miltos. Here is the process to fix the bootloop issue. Can you backup your personal data to your Ubuntu computer?
[07:57] <miltosk> ok
[07:57] <miltosk> παντα κραταω buckup
[07:58] <simosx> miltosk, (it's only in English here). You already have a backup, so you are in a position to go to the next step?
[07:58] <lotuspsychje> simosx: normally after you can reset the phone with volume UP + DOWN
[07:59] <miltosk> im already in fastboot
[07:59] <miltosk> i ve factory reseted the device
[07:59] <simosx> lotuspsychje, so, the phone is switched off, then you press (and keep pressed) the Vol- + Vol+ keys for long enough so that it performs the reset?
[07:59] <miltosk> even removed ubuntu-device flash
[07:59] <lotuspsychje> simosx: yes, then you can enter reset
[08:00] <Sleep_Walker> I had again some incomming call incident - someone called, I saw only the circular screen (the one after waking up the phone) and I could do _nothing_, I couldn't even make it stop ringing which was even more unpleasant as I were in public transportation at that time... I holded power button for several seconds to make it silent :(
[08:01] <simosx> miltosk, you would need to get out of fastboot mode, and switch off the device. Then, start it up by pressing  Vol-  +  Vol+ (keep pressing for 10 seconds).
[08:01] <miltosk> ok... hold
[08:03] <miltosk> device swiched off
[08:03] <lotuspsychje> hmm what about only VOL DOWN hold?
[08:04] <simosx> Sleep_Walker, that might be related to the situation where the phone does not wake up properly as if some process got stuck, and it takes a bit of time for the UI process to be responsive again.
[08:05] <simosx> lotuspsychje, Vol-  +  Power  takes you to factory mode, https://sturmflut.github.io/ubuntu/bq/2015/05/04/hacking-the-bq-part-2-factory-mode/
[08:05] <lotuspsychje> ah right
[08:06] <miltosk> after pressing both up + down device has entered fastboot mode
[08:06] <lotuspsychje> miltosk: ok now you should be able to factory reset
[08:06] <Sleep_Walker> yes, it is possible that UI was not responsive and overall phone feel in cpu or I/O stress
[08:06] <miltosk> how?
[08:07] <miltosk> its a black screen that shows only fastboot mode on the bottom...
[08:07] <miltosk> whats next?
[08:07] <lotuspsychje> miltosk: thats not the screen you need
[08:08] <miltosk> thats what happened when i presses both up + down after device was swiched off
[08:09] <simosx> lotuspsychje, perhaps the instructions at https://sturmflut.github.io/ubuntu/bq/2015/05/04/hacking-the-bq-part-1-bootloader-fastboot-recovery/   (Vol+  +  Power, then select recovery).
[08:09] <miltosk> i tryed before factory reset from recovery mode
[08:09] <lotuspsychje> miltosk: http://img856.imageshack.us/img856/5773/img20130225195221.jpg
[08:09] <miltosk> nothing happened
[08:09] <miltosk> did that...
[08:09] <miltosk> didnt work
[08:10] <miltosk> bootllop again
[08:10] <simosx> miltosk, oh, I had the impression you had a bq phone. No?
[08:10] <lotuspsychje> miltosk: hmm, then you might need a total new install
[08:10] <miltosk> yes!!!
[08:10] <miltosk> from the start
[08:10] <lotuspsychje> miltosk: check wiki install from wiki
[08:10] <lotuspsychje> with phablet tools
[08:10] <miltosk> did that already
[08:11] <miltosk> 2 days  ago
[08:11] <lotuspsychje> and install the BQ image channel
[08:11] <miltosk> failes
[08:11] <miltosk> fails
[08:11] <miltosk> bootloops
[08:11] <lotuspsychje> miltosk: you sure you did it right?
[08:11] <lotuspsychje> wich channel did you try?
[08:12] <miltosk> channel ubuntu-touch/stable/bq-aquaris.en
[08:12] <lotuspsychje> miltosk: did you add --bootstrap after?
[08:13] <miltosk> yes
[08:13] <lotuspsychje> and after perfect install, does nothing?
[08:13] <miltosk> ubuntu-device-flash touch --channel ubuntu-touch/stable/bq-aquaris.en --bootstrap
[08:13] <lotuspsychje> yeah thats good
[08:13] <lotuspsychje> so after that it installs correctly right?
[08:13] <miltosk> and resulted in bootloop
[08:14] <lotuspsychje> miltosk: did you wait long enough?
[08:14] <lotuspsychje> miltosk: you did not press something suring the install?
[08:14] <miltosk> disappointed after 3rd bootloop
[08:14] <lotuspsychje> miltosk: did you leave the install do its work?
[08:15] <lotuspsychje> miltosk: or did you pressed something during setup?
[08:15] <miltosk> nope
[08:15] <lotuspsychje> hmmz
[08:15] <miltosk> waited long enough
[08:15] <lotuspsychje> so after it reboots, what kind of screen do you see?
[08:15] <miltosk> now running process again
[08:15] <Sleep_Walker> "long enough" ? :)
[08:16] <miltosk> miltosk@FX8350:~$ ubuntu-device-flash touch --channel ubuntu-touch/stable/bq-aquaris.en --bootstrap 2015/06/20 11:15:13 Expecting the device to be in the bootloader... waiting 2015/06/20 11:15:13 Device is |krillin| 2015/06/20 11:15:14 Flashing version 23 from ubuntu-touch/stable/bq-aquaris.en channel and server https://system-image.ubuntu.com to device krillin
[08:16] <miltosk> so far....
[08:17] <lotuspsychje> ok wait until it reboots itself now
[08:17] <miltosk> white screen.... power by ubuntu and loops again
[08:17] <miltosk> thats the result after waiting
[08:18] <lotuspsychje> hmmm
[08:18] <lotuspsychje> that might be that OTA4 problem from canonical perhaps?
[08:18] <miltosk> i thought so
[08:19] <lotuspsychje> miltosk: did you write the channel command, to see all available channels for your device?
[08:19] <lotuspsychje> miltosk: maybe they released new working channel?
[08:19] <miltosk> when i upgrated the device i did in device terminal
[08:20] <lotuspsychje> miltosk: ubuntu-device-flash query --list-channels --device=DEVICE
[08:20] <lotuspsychje> try maybe
[08:20] <miltosk> i tryed the process many times changing channels with bootstrap
[08:20] <lotuspsychje> to see if something else shows
[08:20] <miltosk> rc
[08:20] <miltosk> rc-proposed
[08:20] <miltosk> ect
[08:21] <lotuspsychje> miltosk: and everything result in bootloop?
[08:21] <miltosk> no
[08:21] <miltosk> the same
[08:21] <miltosk> miltosk@FX8350:~$ ubuntu-device-flash touch --channel ubuntu-touch/stable/bq-aquaris.en --bootstrap 2015/06/20 11:15:13 Expecting the device to be in the bootloader... waiting 2015/06/20 11:15:13 Device is |krillin| 2015/06/20 11:15:14 Flashing version 23 from ubuntu-touch/stable/bq-aquaris.en channel and server https://system-image.ubuntu.com to device krillin 61.50 MB / 61.50 MB [[08:21] <miltosk> failed to enter recovery
[08:22] <lotuspsychje> miltosk: did you try this one: ubuntu-touch/rc/bq-aquaris.en
[08:22] <miltosk> i ll give it a shot now...
[08:23] <lotuspsychje> ill browse some errors online meanwhile
[08:24] <simosx> Here is the discussion on the mailing list about the OTA-4/bootloop issue, https://lists.launchpad.net/ubuntu-phone/msg13304.html
[08:25] <lotuspsychje> miltosk: i think i found it
[08:25] <lotuspsychje> miltosk, simosx :http://askubuntu.com/questions/602035/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5-and-aquaris-e5
[08:26] <lotuspsychje> miltosk: check the lines after --bootstrap
[08:26] <miltosk> already did that....
[08:27] <miltosk> i told you that none of the sullotions proposed so far doesnt work :-(
[08:27] <lotuspsychje> hmmz
[08:27] <miltosk> ubuntu-device-flash touch --channel ubuntu-touch/rc/bq-aquaris.en --bootstrap 2015/06/20 11:23:49 Expecting the device to be in the bootloader... waiting 2015/06/20 11:24:14 Device is |krillin| 2015/06/20 11:24:14 Flashing version 24 from ubuntu-touch/rc/bq-aquaris.en channel and server https://system-image.ubuntu.com to device krillin Failed to enter Recovery
[08:29] <miltosk> miltosk@FX8350:~$ ubuntu-device-flash touch --channel ubuntu-touch/stable/bq-aquaris.en --bootstrap --recovery-image path/to/downloaded/recovery.img 2015/06/20 11:28:15 Expecting the device to be in the bootloader... waiting 2015/06/20 11:28:40 Device is |krillin| 2015/06/20 11:28:41 Flashing version 23 from ubuntu-touch/stable/bq-aquaris.en channel and server https://system-image.ubuntu.com to device krillin can't flash reco
[08:29] <lotuspsychje> miltosk: no path to recovery must be written manual i think
[08:29] <lotuspsychje> not sure wich
[08:30] <simosx> miltosk, lotuspsychje: how to flash manually the recovery, https://lists.launchpad.net/ubuntu-phone/msg13317.html
[08:34] <miltosk> The requested URL /ubuntu-touch/stable/pool/device-168ccf6a391da4f83feb0325783f02b313e3892675bfea9e4a036bd63fd24f93.tar.xz was not found on this server.
[08:34] <lotuspsychje> miltosk, simosx can this help: http://sturmflut.github.io/ubuntu/touch/2015/05/06/hacking-ubuntu-touch-part-2-devices-and-images/
[08:35] <lotuspsychje> ogra_: alive?
[08:36] <miltosk> και αυτο το δοκιμασα....
[08:36] <miltosk> χθες
[08:36] <miltosk> μια απο τα ιδια.... bootloop
[08:37] <simosx> lotuspsychje, that URL (from sturmflut) shows how to extract the recovery image and then apply it manually, and it is referenced in the discussion on the mailing list.
[08:38] <miltosk> only wiping completely the phone and installing again might solve the problem but i dont know how is done
[08:38] <simosx> Since the URL to the recovery image (in the mailing list post) has changed, then it might be an updated image or something.
[08:39] <simosx> miltosk, I had a similar issue, I compiled from source the linux kernel for the bq E4.5, and then flashed it on the phone. Apparently, it did not work, so I used the same process to get the "boot.img" and flash manually. Problem fixed.
[08:40] <miltosk> ubuntu-device-flash query --device=krillin --channel=ubuntu-touch/rc/bq-aquaris.en --show-image Device: krillin Description: ubuntu=20150611.3,device=20150529-8e13c5f,custom=20150528-722-29-15-vivid,version=24 Version: 24 Channel: ubuntu-touch/rc/bq-aquaris.en Files:  0 https://system-image.ubuntu.com/pool/ubuntu-8f4b0295d39ba4998bc391ae3b202887767f24f2164a6f82642a9c7aa6baeae3.tar.xz 312300804 1891cae983555f969f4fb1538653527e
[08:40] <simosx> miltosk, Since you have tried so many things, it is highly likely that the correct process may be failing due to some previous bad steps.
[08:40] <miltosk> probably
[08:41] <miltosk> any idea how to do the process from the very beginning?
[08:41] <simosx> The command above, mentions 'version 24'. I thought that OTA-4 was version 23 (r23).
[08:42] <miltosk> right...
[08:42] <miltosk> but i also tryed any available channel
[08:44] <miltosk> any idea how to completely fresh start from the beggining?
[08:44] <lotuspsychje> i dont get why you cant enter the factory reset
[08:45] <lotuspsychje> normally it should only wipe user data and fallback to original
[08:45] <miltosk> i can enter factory reset....
[08:45] <miltosk> after that it rolls on bootloop again
[08:45] <lotuspsychje> miltosk: did the bootloop started after an update?
[08:46] <simosx> I am mystified about the r23/r24 situation. you might have on your phone some partitions in r23 and others in r24.
[08:46] <miltosk> after the update when i restarted the device
[08:46]  * simosx is checking the phone.
[08:47] <lotuspsychje> miltosk, simosx http://askubuntu.com/questions/598797/ubuntu-touch-of-aquaris-e4-5-ubuntu-edition-freezes-when-booting-up
[08:48] <miltosk> trying now
[08:49] <lotuspsychje> miltosk: not sure what to do with that .img or where to put it
[08:49] <miltosk> me neither...
[08:49] <miltosk> i ll try the command instead
[08:51] <miltosk> the above is probably another version of ubuntu-device-flash
[08:51] <miltosk> so i guess....
[08:51] <simosx> lotuspsychje, that recovery image is from long time ago (Feb 2015). Might or might not work (but can try anyway).
[08:52] <miltosk> ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/stable/bq-aquaris.en --recovery-image recovery.img 2015/06/20 11:51:49 Expecting the device to be in the bootloader... waiting 2015/06/20 11:51:49 Device is |krillin| 2015/06/20 11:51:49 Flashing version 23 from ubuntu-touch/stable/bq-aquaris.en channel and server https://system-image.ubuntu.com to device krillin can't flash recovery image
[08:52] <simosx> An issue to avoid is this, there is a boot.img and a recovery.img. These need to go to the appropriate partitions. If you flash one to the place of the other, bad things happen.
[08:55] <miltosk> nothing works
[08:55] <lotuspsychje> http://askubuntu.com/questions/622911/cant-flash-recovery-image
[08:56] <lotuspsychje> this would make sense the android partition, before the image can be installed
[08:57] <miltosk> ou have access to a Windows computer with administration rights???
[08:57] <lotuspsychje> lol
[08:57] <lotuspsychje> never done this mate sorry
[08:58] <lotuspsychje> i have nexus7 myself, much easier proces
[08:58] <miltosk> ok...
[08:59] <lotuspsychje> miltosk: you might idle here until ogra_ and sturmflut are online, theu surely know howto
[09:00] <lotuspsychje> devs will wake up pretty soon i think :p
[09:00] <miltosk> if anyone finds sthing please enlighten me....
[09:00] <miltosk> anyone can leave me a pm on google+
[09:01] <miltosk> i m out... thank you all for yout time....
[09:01] <lotuspsychje> ubuntu-device-flash touch --channel ubuntu-touch/stable/bq-aquaris.en --bootstrap --recovery-image path/to/downloaded/recovery.img
[09:02] <lotuspsychje> path/to might be where you download that recovery.img
[09:02] <lotuspsychje> /home/miltosk/recovery.img
[09:03] <lotuspsychje> simosx: http://newtips4u.com/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5/
[09:07] <simosx> lotuspsychje, that URL (newtips4u.com) is not the source of the information. They are probably machine-generated, and the source is askubuntu.com (https://askubuntu.com/questions/602035/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5-and-aquaris-e5).
[09:08] <lotuspsychje> perhaps, but that path to folder must be your own dir/to/img
[09:08] <lotuspsychje> thats why its not working
[09:09] <lotuspsychje> simosx: so he must download that img to his pc, and point the command to own dir
[09:09] <simosx> lotuspsychje, okay, I'll relay this to miltosk.
[09:16] <simosx> lotuspsychje, I also asked him to 'apt-cache policy ubuntu-device-flash' in order to verify the version as well.
[09:17] <lotuspsychje> ok
[09:17] <ice9> I'm trying to port Ubuntu Touch to a new device, where can I find the device blobs needed?
[09:17] <lotuspsychje> !devices | ice9
[09:18] <ice9> lotuspsychje: my device is not listed that's why I'm porting to it!
[09:19] <lotuspsychje> ice9: try the XDA forums for existing projects or check the porting guide wiki
[09:21] <ice9> lotuspsychje: I'm following the porting guide already, I just have a specific question, where can I find device blobs?
[09:21] <lotuspsychje> not sure
[09:21] <simosx> ice9, which device, if I may ask ;-)
[09:21] <ice9> simosx: Samsung Galaxy Note 8 N5100
[09:21] <simosx> nice
[09:22] <simosx> ice9, I think the device blobs exist already on your phone, so you are asking how to identify them?
[09:23] <ice9> simosx: yes please
[09:23] <ice9> how do I extract them to make the port
[09:24] <simosx> ice9, I do not know the answer to that ;-(. You may want to check here a bit later if you can get someone who has done such porting already, or try to find some blog post of anyone who performed this task on their own device.
[09:26] <ice9> thanks simosx
[09:26] <simosx> I am following this one, http://forum.xda-developers.com/moto-g/development/ubuntu-touch-utopic-ubuntu-touch-falcon-t2820359
[09:27] <simosx> ice9, at xda-developers, there are several threads in various places which describe the process, and you may find the details you need.
[10:34] <brunch875> I liked the old settings icon better :|
[13:23] <nik90> cwayne: it seems I am unable to write a review for the Ubuntu News Scope. There seems to be no review box to add a review despite having it installed. Do you see the same issue?
[13:24] <nik90> cwayne: I am able to review other scopes that I have installed.
[13:42] <cwayne> nik90: i've seen that for other stuff, no idea what causes it
[13:42] <cwayne> but uninstalling+reinstalling fixed it for me
[13:43] <nik90> cwayne: ah ok..will do that then. Can you add keywords support to it so that I can use it from the news scope?
[13:52] <popey> cwayne: nik90 i suspect this is because it wasn't installed via the store
[13:52] <popey> I have seen that for apps included in the overlay click
[13:53] <nik90> popey: I haven't installed any app/scope via sideloading in my BQ device and I experience this bug in both my N4 and BQ.
[13:53] <nik90> popey: my BQ is pristine install without any hacks/sideloading etc..just for experiencing it as a standard user.
[13:58] <popey> ditto :)
[13:58] <DanChapman> popey, nik90, https://bitbucket.org/snippets/dekkoproject/dEejr if you want to try out notifications
[13:58] <popey> ooh
[13:59] <nik90> awesome
[14:00] <DanChapman> nik90: thanks for the review :)
[14:00] <nik90> DanChapman: np, surprised that I didn't review it earlier.
[14:01] <nik90> DanChapman, popey: Btw what would it take for Dekko to be installed by default (like any other core app)?
[14:01] <nik90> It seems to be as mature as the telegram app
[14:08] <DanChapman> nik90: I have no idea tbh. Would be cool though :-D
[14:09] <nik90> DanChapman: Does Dekko have good automated test coverage? That's one criteria that the QA team look for before accepting any default app.
[14:13] <DanChapman> nik90: unit test converage is ok'ish but no functional tests yet.
[14:15] <popey> nik90: would need to run that past richard and joeo
[14:32] <studio_> hi
[14:34] <studio_> do someone here know the different between the e4.5 ubuntu edition with the id 2a47:0c02 and the id 2a47:2008 ?
[14:37] <popey> no idea what 2a47:2008 is
[14:37] <studio_> also bq e4.5 ubuntu edition
[14:38] <studio_> for exp. in german: http://www.mintblog.de/2015/04/bq-ubuntu-phone-als-usb-massenspeicher-unter-linux-mint-einbinden/
[14:40] <studio_> i thought the 2a47:2008 is the bq e5?
[14:41] <popey> dunno, i don't have an e5
[14:44] <studio_> is it possible, that bq gives for different devices the same usb-id? or is the usb-id depending from the motherboard?
[14:47] <popey> all manufacturers are guilty of messing about with USB ids
[14:48] <studio_> so usb-ids are not "normed" like an ean-code?
[14:48] <popey> they're not
[14:48] <studio_> ok
[14:50] <popey> studio_: I just asked someone with an e5, and they got 2008
[14:51] <studio_> i know, therfore i was wondering, that there are e4.5 with the id 2008 on the market
[14:55] <studio_> there are also some e5fhd with the id 0c02 on the market. confusing ...
[15:14] <studio__> btw. i have also seen in the internet that the bq aquaris "e4" got the id 2008 and is also using an MTK6582"M". will that device also be supported in the near future with/by ubuntu touch?
[15:21] <cwayne_> nik90, good idea, i'll add that
[15:48] <K1773R> why always this mind madness?
[15:48] <tathhu> why not
[15:53] <popey> K1773R: wat?
[16:01] <svij> popey: against which project should I file a bug for my "notification-indicator isn't green on new notifications" and "no led notifications" on arale?
[16:19] <ogra_> popey, fyi, the usb id varies depending on the config of the android gadget driver (adb,mtp vs adb,rndis vs mtp only)
[16:20] <ogra_> svij, bug 1461682
[16:21] <svij> ogra_: oh thx
[16:22] <svij> "indicator-messages"… I searched for "indicator-notifications"
[16:23] <popey> ahh, thanks ogra_
[16:24] <popey> svij: https://wiki.ubuntu.com/Avengers is a good place to find where to file bugs
[16:24] <svij> popey: oh great
[16:24] <ogra_> svij, i'm not sure the indicator on the arale is actually supposed to be colored ... for krillin the indicator color is adjusted for the led (and the other way round) the arale led can not display colors afaik
[16:24] <svij> ogra_: oh
[16:25] <svij> that would make sense why it's "white" not green.
[16:25] <ogra_> so it might make sense if it is just a filled vs outlined envelope icon
[16:25] <ogra_> not sure though
[16:25] <svij> even though the difference between "grey" (no notification) and "white" isn't that big
[16:25]  * ogra_ <- luckily not a designer :) 
[16:25] <popey> yeah, it has no colour attributes
[16:25] <svij> so it's intended?
[16:26] <popey> hardware limitation
[16:26] <svij> I mean, in the indicators
[16:26] <svij> not the hardware button itself
[16:26] <popey> sorry, what's the question?
[16:26] <svij> the indicator for the messages is white not green when I've got a notification
[16:27] <svij> and grey when there is none
[16:27] <popey> green here
[16:27] <svij> hm…
[16:27] <studio_> popey, that is funny, bq is iso 20000 certified :)
[16:27] <popey> studio_: 17:19 < ogra_> popey, fyi, the usb id varies depending on the config of the android gadget driver (adb,mtp vs adb,rndis vs mtp only)
[16:28] <studio_> ouch?
[16:28] <popey> svij: http://people.canonical.com/~alan/screenshots/device-2015-06-20-172839.png
[16:29] <studio_> lsusb is allways wrong?
[16:29] <svij> gimme a sec and I'll show you my screenshot
[16:29] <popey> svij: channel: ubuntu-touch/rc-proposed/meizu.en
[16:29] <popey> build 31
[16:29] <ogra_> studio_, no, but the part after the colon is not fixed ... it can vary based on the setup of the deriver
[16:29] <popey> so just that I'm ahead of you that's all
[16:29] <ogra_> *driver
[16:31] <studio_> ogra_, can you please give me an example for that?
[16:31] <nhaines> studio_: sure.  For example, the BQ aquaris E4.5.
[16:31] <ogra_> studio_, http://paste.ubuntu.com/11746237/
[16:31] <popey> see also lots of 3g mifi devices
[16:32] <ogra_> oh, wow
[16:32] <ogra_> the arale rules are completely wrong
[16:33] <svij> popey: notification in white (https://svij.org/graphics/screenshot20150620_093515348.png) vs no-notification in grey (https://svij.org/graphics/screenshot20150620_093527479.png)
[16:33] <ogra_> /lib/udev/rules.d/70-android-tools-adb.rules has the right ones
[16:33] <svij> so this might be already fixed…
[16:33] <popey> svij: yeah, but you're on an older image?
[16:34] <studio_> mtp device is 2008 and adb device is 0c02 ?
[16:34] <popey> svij: http://paste.ubuntu.com/11746243/
[16:34] <svij> that stable one… r1
[16:35] <svij> and I can't get adb work on arale… :-/
[16:35] <ogra_> studio_, no, if the device is configured for mtp+adb it is 0c02 ... if it is mtp only it is 2008 ... the latter is with developer mode switched off, the former with developer mode switched on (mtp is always on, we hardocde it)
[16:37] <studio_> mtp only means no dev mode?
[16:37] <ogra_> yes
[16:38] <studio_> ok
[16:38] <studio_> will try that later ...
[16:38] <studio_> thanks
[16:40] <studio_> so for bq phones, the usb-id has noting to do with the device itself, right?
[16:42] <nhaines> Wrong?
[16:44] <studio_> nhaines, why you ask "wrong?" ? isn't the bq usb-id just an mtp-device and/or mtp+adb-device, but say nothing about the mainboard and its features?
[16:45] <nhaines> It's not a UUID.
[16:46] <studio_> one UUID for different devices?
[16:47] <OerHeks> UUID <> usb ID , UUID is storage id.
[16:48] <studio_> and what is 2a47:7f10 for exp?
[16:55] <svij> hm… isn't there an "Alt" key on the terminal app?
[17:02] <studio_> ogra_, cool on android without dev mode it is 2008, and with dev mode it is 0c02. so ubuntu inherited that or is that still android stuff?
[17:09] <studio_> orga_ ?
[17:16] <studio_> btw. meizu is using the same device- ids :2008 and :0c02? *confused*
[17:22] <studio_> could someone please explain me what device :2008 and :0c02 means, do i have it to compare for the ubuntu devices like a "port"?
[17:26] <studio_> ping
[17:27] <tathhu> pong
[17:27] <studio_> ping
[17:28] <tathhu> BANG
[17:28] <mariogrip> How to set apparmor in complain mode on Ubuntu touch
[17:33] <studio_> 2a45:2008 / 2a45:0c02 is the same as 2a47:2008 / 2a47:0c02 ? so 0c02 is just an mtp/adb-device? and if yes, what is 2a47:7f10, also an mtp/adb-device?
[17:43] <studio_> 2a45 is meizu and  2a47 is bq (mundo reader). i am a bit confused about that usb-ids ... :(
[17:43] <tathhu> does it matter :o
[17:45] <studio_> depending ...
[17:50] <studio_> back to ubuntu/linux stuff. how to disable ssh via certification? is there a "sshd_config" to disable that?
[18:00] <studio_> thanks for trying to help for today. have to leave. bye all
[18:04] <muka> cellular data stopped working. ubuntu 15.10(r230) development -branch.
[18:04] <ogra_> muka, could well be ... devel i snot for day to day use
[18:04] <ogra_> *is not
[18:05] <muka> I know, just want to report.
[18:05] <ogra_> well, file a bug then
[18:19] <faenil> what is the recommended way to handle cross platform apps which run on ubuntu touch? In particular I'm talking about conditions in .pro files
[18:20] <faenil> There is no ubuntu touch specific OS condition/makespec, afaik
[18:20] <faenil> the alternative is having CONFIG += ubuntu-touch in every .pro file, but that's...messy
[19:10] <cimbro> hola
[19:48] <jjohansen> mariogrip: install apparmor-utils and use aa-complain
[19:49] <jjohansen> mariogrip:  for touch profiles you will need to use the -d option
[19:49] <jjohansen> I think it is aa-complain -d /var/lib/apparmor/profiles
[22:10] <Guest99372> v
[23:35] <mariogrip> jjohansen: Thanks.