[02:32] Hey can you remember the bridge name to access this group from umatriks ? [02:40] [Edit] Hey can you remember me the bridge name to access this group from umatriks ? [05:46] @UniversalSuperBox, Why it seems I don't own such a recovery window on my Pro5? I flashed the recovery_turbo.img file but if I reboot to recovery I only see the Ubuntu logo in the middle of the screen. Is this a different recovery img? [05:50] I suppose that is only for FP2. Old Canonical devices are not the UBports flagships :). [05:51] that's a nexus 5 tho [05:52] Oh, ok. I thought FP2 based on the comment posted by Flohack later on. [06:39] @zubozrout, Oh I see...thus it's a pity not having that recovery for all the devices [06:46] Chrisewcs was added by: Chrisewcs [06:49] Well, the original recovery works fine, so I guess it is ok. And I like it visually more. [06:54] @mattbel10, Because the recovery is not opensource, as the whole device tree. We need to stick with what was there from Canonical [06:56] @Flohack, Thank you Florian for the clarification :) [07:00] However I would infer that a recovery boot without recovery options is not kind of an actual recovery, so poorly useful [07:01] Hmm, not sure if the option was ever there, can't find it, but is there a way to prevent waking the screen if I detach the power charger from the device? [08:02] Aleksander Nikitin was added by: Aleksander Nikitin [08:13] When the UBports installer says "Please connect the device with a USB cable", does it mean "Wait, I'm downloading what is needed, keep the device connected" or really it does not detect that the device is connected? [08:15] It means `sh*t I can't see your device, one of us f*cked something up` [08:16] On my n5 I couldnt flash right after I unlocked bootlodaer, I had to reflash android and enable usb debugging once again [08:16] @UniversalSuperBox, Is it possible to make a script that automatically updates the Openstore after ota update? [08:16] @VeryOriginalUsername, got it, thank you [08:18] @VeryOriginalUsername, The stange thing is that it detected the device when I connected it, and the device has been rebooted in a strange mode... [08:18] Just reflash android if you can and try agai [08:18] [Edit] Just reflash android if you can and try again [08:19] Ok, thank you [08:19] @unknown, Like doing it into autostart and remove it afterwards [08:20] As a side note, I think the UBPorts installer uses too much CPU to get the job done [08:31] @garrogarri, it's electron ;) [08:56] @neothethird, Its the animation [08:56] with the dots. When you minimize it its better [08:56] Welcome Aleksander !!! Check this put for more about UBports https://ubports.com/page/telegram-welcome [09:00] Hello everybody, I have the opportunity to buy a Meizu Pro 5 Ubuntu Edition [09:01] Can someone tell me, what the status of that device regarding ubports support, especially 16.04 is? Thank you very much! [09:12] A question: The OPO camera zoom and flash are still not working also with xenial? [09:13] @Chrisewcs, Hi Christian, welcome! Take a look to https://ubports.com/page/telegram-welcome to get you started 👍 [10:17] @garrogarri, Try going into recovery manual if that happens [10:20] @mateosalta, Should I press pwr+vol up+vol down altogether, right? [10:21] I'm on a Fairphone [10:48] Either up or down I think [10:49] Its diffrent for each, some one provides a menu, others each is either fast boot or recovery [11:16] Recovery on FP2 is Power plus Vlo-Up. [11:16] Vol-Up... [11:17] What should I do once I'm in recovery? [11:22] Just dropped by and missed the start of the conversation. You're trying to install UT on an FP2 but the installer doesn't find the device (says you should connect via USB but it's already connected)? [11:24] IIRC help with installing UT is typically done in the welcome group https://t.me/WelcomePlus [11:42] @Ingo_FP_Angel, I'm trying to upgrade to 16.04 [11:42] I have UBPorts already [11:42] [Edit] I have UT already [11:46] @garrogarri, So you can try with the cli tool [11:47] Fwd from mariogrip: or `sudo system-image-cli --switch 16.04/rc` from the phone [11:47] @mymike00, Ok, I'm trying [11:49] I've never used it so I can't help you if you have problems... [12:51] (Photo, 540x960) https://irc.ubports.com/zCpQhuWQ.png [12:53] How to make 3 icons in row [13:21] Hi! Morning. Can I install/test UT on my Redmi Note 3 (Kenzo)? [13:53] Uhhh wifi suddenly 🅱 roke on my nexus5 [13:53] Version 2 of ota4-rc [13:59] @Gilmars, The currently supported devices are listed at https://devices.ubuntu-touch.io/ [14:01] @VeryOriginalUsername, `nmcli d` returns wifi0 unavailable [14:04] @VeryOriginalUsername, same here but on FP2, i've opened an issue here https://github.com/ubports/ubuntu-touch/issues/703 [14:05] but i don't know how to reproduce or how to debug it [14:05] Switches are there, yet there's no actual wlan [14:05] oh [14:05] ok [14:07] The strange thing is that it worked fine right after update and it stopped now, I really hope my hw is not damaged [14:07] Phone's been sitting on airplane mode for like 2 days though [14:10] Does UT support internet over bluetooth? [14:15] @VeryOriginalUsername, Fixed: disable display -> wireless display and reboot [14:22] @unknown, I was thinking something graphical [14:24] @VeryOriginalUsername, Rc2? [14:26] v2 is what update menu told me [14:26] @John, For hammerhead and bacon only for now [14:26] I guess it's more like ota4-rc1.1 [14:27] @UniversalSuperBox, What about something automatical in the background like doing a script into autostart and remove it afterwards [14:28] @unknown, That's not great UX if we're doing it from the internet, but it could work if we included the new click with the update [14:28] People get kinda upset about "automatically updating stuff" [14:29] A graphical installer which runs on first boot could at least say "hey, click here to update things or your phone won't work" [14:30] @UniversalSuperBox, I like this one 👍 [14:32] @advocatux, What's new in it, iam using hammerhead [14:32] @John, No idea, sorry [14:34] My camera stuck when I switch between camera to video mode in 15.04 rc1 [14:34] Nexus 5, known issue. [14:35] Any other device having same issue? [14:35] See https://github.com/ubports/ubuntu-touch/milestone/7 for known new bugs in 16.04 [14:35] @John, No [15:00] t0no6 was added by: t0no6 [15:01] @t0no6, Hi Toño G, welcome! 🤘Check out https://ubports.com/page/telegram-welcome … There's a Spanish group too :) [15:08] could someone please send me `/usr/share/backgrounds/warty-final-ubuntu.png` from ubuntu touch? [15:09] don't have access to the device atm, but need it for developement [15:09] @vanyasem, you can pull it using adb [15:13] (Document) https://irc.ubports.com/pZVADPli.png [15:18] thank you ^^ [15:40] @UniversalSuperBox, Just fixing the click bug will solve the problem for preinstalled apps [15:41] Well that's good [15:41] Do you have a reference to "the click bug" since I haven't read the codebase to understand what it's doing wrong [15:43] @UniversalSuperBox, I don't know if it's been reported. The issue is it's preferring apps in opt when the hooks get run. It needs some logic adjustment there. I can probably take a quick look later [15:45] Castorfilth was added by: Gilmars [16:03] Ellypsis was added by: Ellypsis [16:05] Hi all. I'm looking for the cellular interface to add a rule to ufw to only authorize MMS [16:06] I suppose it's one of the rmnet? [17:08] I just solved my problem using /var/log/ufw.log, it was rmnet0. Now, I can block data but authorize MMS. [18:26] Hey @mariogrip, I think I got it. https://github.com/ubports/mir/tree/xenial_-_jbb-upstream-test [18:26] It's an alias, I think [18:27] @UniversalSuperBox, alias of xenial, but it seems like it :D [18:27] This was dumb, I should have done something that I'd actually commit to [18:28] :P [18:35] but that would give mir build to test? [18:35] It should [18:36] Alright, that didn't work [18:36] The refs don't seem to update on GitHub [18:36] what if you push it manually? [18:37] Yeah, but that's not the point [18:37] still less work than keeping separate branches [18:38] `git push --all` [18:38] Seems ridiculous but it's working [18:41] This isn't a very good solution unfortunately [19:20] Ellypsis was added by: Ellypsis [19:24] Hi! Me again. I have a small problem when I use "adb shell". When I type, the wrapping not wokring, it always override the first line. To have it works, I have to resize my terminal window (urxvt) to a specific width. It's not really nice when you use a tilling manager (xmonad). Did I forgot something in bashrc? [19:24] adb only works with 80 character wide terminals [19:25] oh ok. So it's just that... Will try to have ssh working so [19:25] thanks @UniversalSuperBox [19:32] @Ellypsis, sudo apt install xterm; resize [19:32] makes the terminal wrapping sane [19:36] Where's the best place to get support flashing an mx4? [19:36] @WelcomePlus is the coolest of install chats [19:37] didn't know resize command, working fine with urxvt. Thanks! [19:38] My mx4 is in fastboot, but ubports installer is still telling me to reboot [19:39] I'm guessing you're using the snap? Either way, there's lots of people in @WelcomePlus who know the workarounds [19:39] ah o [19:39] [Edit] ah ok [19:55] Happy 300 Liberapay! [20:02] on 16.04, we can't mount system rw? [20:03] i try "mount / -o remount,rw" but still can't edit a file in /system/usr/keylayout [20:03] No, the systemimage is mounted ro originally [20:03] So it can't be remounted [20:03] `touch /userdata/.writable_device_image`, I think [20:03] And reboot [20:05] will give a try [20:05] I have no more power button on a new nexus 5, so i need to remap button [20:05] Sounds weird [20:05] But smack it on a table, that side down [20:06] Stuck power button is common [20:06] the button was unweld [20:06] ah [20:06] it's not a problem as it's one only for test and bug report ;) [20:06] my dealy driver is on 15.04 [20:07] daily* [20:08] can't edit a system file with 'touch /userdata/.writable_device_image' [20:08] Maybe it's hyphens [20:09] I can never remember [20:18] `$ kill hciattach … bash: kill: hciattach: arguments must be process or job IDs` how can I kill that process? [20:18] [Edit] ```$ kill hciattach … bash: kill: hciattach: arguments must be process or job IDs``` how can I kill that process? [20:21] @mymike00, sudo pkill -9 hciattach [20:23] @malditobastardo, Ah, thanks. … What does that 9 stand for? [20:28] without -9 send signal TERM; with -9 send signal KILL [20:28] TERM is not as forcefull as KILL [20:29] Exactly [20:33] TERMinate is like "hey kill that guy" and KILL is like "he's already dead" [20:54] You don't bring a TERM to a KILL fight (? [23:53] I'm on OTA-3 stable on the Nexus 5. Do I just switch to RC to get the OTA-4 RC?