 @Io Note4 - Rocco, My opo is being weird too!
 (Photo, 1280x720) https://irc.ubports.com/0J4pl48J.png
 (Video, 24s) https://irc.ubports.com/VDJ6xj5O.mp4
 @PhoenixLandPirate, I love that startup screen though...
 @amolith, in my case when Dekko2 is released :)
[05:17] <ubptgbot> <Io Note4 - Rocco> @PhoenixLandPirate, Yesss, also for me
 Only two major issues now prevent me from start using my Pro 5 with xenial as daily driver: … 1) Camera app not launching at all (https://github.com/ubports/ubuntu-touch/issues/667) … 2) Calendar crashes every time I launch it (https://github.com/ubports/ubuntu-touch/issues/656) … Otherwise I am good to go. Of course a working G
[07:29] <ubptgbot> PS would be nice, but I am not depending on it.
 Some info for @h4ppycup which might be useful to others 😋
 Fwd from fourloop2002: FYI I have a Nexus 5 D821 which was not able to make or receive phone calls on either 15.04 or 16.04.  I reinstalled Android, tried LineageOS, and attempted multiple log monitoring. ofono scripts, etc, etc.  Eventually I changed my service provider and now I can make and receive phone calls.  So it
[08:37] <ubptgbot> appears that the frequency bands your service provider uses for each of the services phone calls, SMS, MMS and mobile data can break the phone.  Try different service provider(s) to see if this solves your issue.  Good luck!
 trouble with nextcloud account: bq E5 16.04 r95  when i try to enter my owncloud it always give me "Invalid host URL" i have https:// for my nextcloud. anybody here know what to do?
 It could be related to self-signed certificates (message is misleading in that case).
 @TomasOqvist, I confirm the issues for what concerns the camera app and the GPS which doesn't work at all on my Pro5.
 @Ingo_FP_Angel, its a letsencrypt ssl certificate on my server. do you know how to fix it?
 No, sorry. I would have assumed a Letsencrypt certificate would work.
 So are notifications for the Telegram app still broken on Xenial?
 yes
 just making sure I'm not alone :B
 https://github.com/ubports/ubuntu-touch/issues/602 supposedly fixed already but it still doesn't seem to register with ubuntu one for some reason, oh well
 Those problems are patchy. Seems related to registration, so it affects some accounts but not most 🤔
 odd.
[10:28] <duud> developers here? hammerhead doesn't use the deep-sleep states on 16.04, probably a wakelock issue. Can someone assist me pls how to check powerstates/wakelocks on ubuntu touch?
 duud, grabbing and releasing wakelocks should be announced in /var/log/syslog
 Otherwise it'll be in ~/.cache/upstart/unity8.log
 @duud, thats related to? https://github.com/ubports/ubuntu-touch/issues/674
 It's probably just from observation rather than a bug report
 #674 doesn't seem to affect arale at all
[11:42] <duud> UniSuperBox:Thx, 'cat /sys/kernel/debug/wakeup_sources' reveals the deep-sleep is prevented by grep msm_serial_hs_dma. This is a bleutooth device
 duud, do you have one connected?
[11:44] <duud> UniSuperBox: No, bluetooth is disabled on the phone
 Hmm. I'm not sure then.
[11:50] <duud> How are services managed on UT? In particular, how to stop all bluetooth related services like '/usr/sbin/bluetoothd'?
 `initctl list` with and without sudo will give you a full list of running services, then `stop service` will do what you desire
[11:54] <duud> Thx, the bt service is probably opening the bt-device without properly notifying it to release the wakelock
[12:11] <duud> killing '/usr/bin/hciattach' releases the wakelock, so there seems to be power management issues in the bluetooth stack. I'll check if hammerhead goes into deep-sleep after killing hciattach
[12:25] <duud> UniSuperBox: Is there something like a maintainer for hammerhead? I'm not sure how ubports is organized.
 The number of developers pretty much means "the developer" is "the project"
 Yes, opo camera app, zoom function works!
 16.04 that is
 Pro 5 camera worked perfectly up until xenial r91
 :(
 r329
 And flash 😃
 So next thing could be the phone gets permission to use the microphone so I can make a call?
 @duud, Bluetooth is 99% upstream in normal Ubuntu and with the Bluez package. There is not much special what is done for Ubuntu Touch itself
 @Flohack, there was a different (newer) build of bluez in the overlay ppa. if we're building xenial without that now, and it wasn't copied to ubports, perhaps there is a regression
 Yay new version of Ubuntu Touch R429 already released. Downloading now 😊
 also, there are definitely some differences, as i have a bluetooth device that would pair and work fine with bluez on even the vivid image on nexus 4, but would not pair with the same bluez build on my PC on 16.04, nor the backported version from 18.04 on 16.04, but does work fine with 18.04 installed.
 so there is definitely something going on with blueooth i think, that is not quite the same as stock ubuntu
 Yes the overlay might be, except that someone said, it was just the xenial version put into it. But we can check this
 @Flohack, it was not. there was a newer version in xenial overlay, than is in stock ubuntu 16.04, as well
 Hmm interesting
[13:52] <sander^home> Hi. Looks I cant turn off wireless network when I try to share a network connection.
[13:52] <sander^home> the wireless network is most likely blocking becouse its a non funtioning network now
[14:02] <duud> Flohack: msm_serial_hs_dma definitely holds a wakelock all the time preventing hammerhead from going deep sleep. I'm not sure how bt-power-management is supposed to work. Android usually has a bluesleep service running on hammerhead - this is not the case on 16.04
[14:09] <duud> btw. hammerhead is pretty usable on 16.04 beside video recording not working and more importantly the battery drain/ wakelock issue
 @duud, In 15.04 the wave lock works?
[14:10] <duud> sry no idea, I've installed ut for the first time a couple hours ago
 You should try vivid and compare to be have more a realistic input
 In vivid the battery drain is ok
 Not amazing just ok maybe you are having the same experience with xenial
 In comparison to android
[14:16] <duud> malditobastardo: I don't think this is necessary. It's pretty easy to see what's keeping the device from going into deep sleep, just by doing 'cat /sys/kernel/debug/wakeup_sources'. After killing '/usr/bin/hciattach' hammerhead goes properly into deep sleep on 16.04.
 @malditobastardo, i'm guessing there's a regression with bluetooth
 [Edit] You should try vivid and compare to have a more realistic input
 Understood. Thanks for the answers
 I will hold the jump to xenial then
 Battery drain is a huge deal
[14:31] <duud> malditobastardo: It's pretty possible that 15.04 is having the same issue
 @duud, Could you please open a detailed issue in the bug report?
[14:42] <duud> Yes ofc, not sure when. Where are issues tracked?
[14:43] <Beton> duud: https://github.com/ubports/ubuntu-touch/ i think
 @duud, https://github.com/ubports/ubuntu-touch/issues
[14:48] <duud> thx
[15:00] <duud> done
 this has been asked several times, but, as I am too stupid, how can I make SSH via USB working on startup?
 @IGNNE, ... SSH via USB?
 ssh_exchange_identification: read: Connection reset by peer
 That is all I get. There is something listening, but it immediately drops the connection
 @IGNNE, you need the phablet-shell script
 (Document) https://irc.ubports.com/XigRHzOl.null
 But I have no adb, I am just (again) trying to port my device. I get the Usb-Network-Interface, I can set the IP and route, I can ping the device but it won't connect to ssh
 https://docs.ubports.com/en/latest/userguide/advanceduse/ssh.html
 Well yes, but what is the error you're getting @IGNNE?
 (Plug for @ubports_porting
 [Edit] (Plug for @ubports_porting)
 oh well, initial porting is a different issue i guess
 @UniversalSuperBox, Yes, I forgot there is this other group. Sorry!
[18:21] <duud> Just go give you an impression about the difference in power consumption. The battery died after about 6-7h without using the phone, now it's on 85% after 6h. The battery is pretty old but as you can see the difference is huge.
 @duud, thats a lot
 duud, you are our hope for getting a fix for the battery life
[18:42] <duud> I'm not familiar with the bluetooth stack in ut, I also don't know how power management is supposed to work on the android side on hammerhead. So for now I simply kill /usr/bin/hciattach as I'm not using bluetooth anyway - but with this 16.04 is perfectly usable now. Maybe someone with more understanding will take a look at it.
 I will test on vivid in a few minutes
 @advocatux, turns out Pdfjsviewer *does* work in 16.04, but it seems to need a reboot to show up in the apps list and to be used with File Manager as an 'open as' option.
 @advocatux, [Edit] turns out Pdfjsviewer does work in 16.04, but it seems to need a reboot to show up in the apps list and to be used with File Manager as an 'open as' option.
[18:51] <duud> malditobastardo: also check the output of 'cat /sys/kernel/debug/wakeup_sources' it reports the total time each wakelock was hold, in particular the line containing msm_serial_hs_dma, this one was preventing my phone from going into deep sleep.
 @ronnietucker 👍
 Same on N5/vivid
 @duud, Thanks I will follow your instructions because we were speaking with @advocatux about using `sudo killall hciattach` to do it, etc
 https://github.com/ubports/ubuntu-touch/issues/676
 @malditobastardo, pkill, not killall
 @dohbee, Why?
 Xkill
 pkill -9 is always good
 pkill was the best bet
 kill process_number
 [Edit] pkill -9 was the best bet
 @amolith, because `killall` behavior on linux is not the same as other unixes. `sudo killall` on sunos/solaris for example would kill all running processes
 `pkill` is the correct way to kill all instances of a process name matching a pattern
[19:05] <duud> isn't it funny, we have a killall command on UNIXes ;)
 or i guess i should say `GNU killall` behavior is non-standard, rather
 @dohbee, Hmm. I've always used `killall`. Time to change another habit 😉 Lol thank you
 so yeah, pkill is "safer" everywhere, so good practice to use it even when killall does the same thing :)
 Going with the standard and "safe" route is always best.
 @duud, Good thank you
[19:11] <duud> this irc channel is forwarded to telegram via ubptgbot, right?
 @duud, Yes that's now it works I believe Duud
[20:12] <ubptgbot> Ivanuzzu was added by: Ivanuzzu
 @Ivanuzzu, Welcome Ivan. Amazing name :P
 Be sure to check out ubports.com/telegram-welcome to learn more about UT
 Hi
 (Sticker, 512x512) https://irc.ubports.com/NrdhxYBz.webp
 sorry :)
 I nave only one question, i would install this OS on my nexus 4, but it is possibile use android ap with anbox?
 @Ivanuzzu, Iirc anbox is not supported on n4
 not on Qualcomm devices yet, needs debugging
 (can I make a wish?)
 [Edit] sorry :), I accidentally clicked on a sticker. Not sure if I deleted it for everyone so please ignore it is still there.
 @NotKit, Sure :P
 Go ahead
 So, in a future can be possible? I love this OS, but needs app 😁
 @Ivanuzzu, it's the plan
 OK, thanks for information
 If I understood it right for Anbox all kernels need to be recompiled. Are there sources for every supported device?
 Yes
 Is anbox broken because of kernels being too old?
 Kernel is under the GPL, the user space drivers are not
 @VeryOriginalUsername, No
 Normally it installs the binder driver as a module. Since we already have a binder, it gets interfered with
 And also module loading is sticky and DKMS is an unlikely dream
 And messy. DKMS is messy.
 @UniversalSuperBox, technically we don't need separate binder driver, but patch the existing one to support namespaces
 at least this kinda works for 3.10 on SF
 @UniversalSuperBox, especially when you're not entirely debian based
 (Photo, 802x630) https://irc.ubports.com/zHDbple0.png why is that?
 @NotKit, Yep
 @RaphaelItsMe, Is your device unlocked?
 Already some news about if the UBports FileManager does support SFTP file exchange?
 @ignorare, it works now,  version 0.13 did not work on my ubuntu 18.04. version 0.12 did the job
 @UniversalSuperBox, it works now,  version 0.13 did not work on my ubuntu 18.04. version 0.12 did the job