[01:05] <dobey> please fix your connection
[02:13] <kirkins> hi all
[06:52] <gabriel_awe> Hi! Best phone to try out the UTouch?
[07:15] <krowv> gabriel_awe: Nexus 4.  Cheap, easy to find, easy to load Ubuntu on.
[07:22] <gabriel_awe> krowv: thanx
[07:31] <krowv> gabriel_awe: np.  good luck.
[14:20] <brunch875> guys the new alt-tab on the phone looks -fantastic-
[14:21] <brunch875> I tried the three fingers thing but it wouldn't work on the e4.5
[14:21] <brunch875> is there anything new I should try?
[14:22] <davmor2> brunch875: sidestage is still screen size dependant I believe
[14:23] <brunch875> yeah, I thought so
[14:23] <brunch875> I noticed how the name of the applications show up there like in unity7
[14:23] <brunch875> I take it there's going to be a context menu :)
[14:25] <r0kk3rz> Hi, does anyone know how the sensors work in ubuntu touch? is there some kind of service that reads them?
[14:25] <r0kk3rz> usensord doesnt seem to have much in it
[14:26] <MCMic> brunch875: What is the new alt-tab stuff?
[14:27] <brunch875> MCMic: http://www.omgubuntu.co.uk/2016/10/new-video-shows-changes-headed-unity-8
[14:28] <brunch875> I had it recently land on my device, I'm on rc-proposed
[14:29] <MCMic> brunch875: thanks
[14:30] <dobey> r0kk3rz: the qt sensors api is how apps get access to them
[14:30] <r0kk3rz> dobey: obviously, but qtsensors needs a backend
[14:31] <dobey> r0kk3rz: the drivers and such are all in the anroid container, which the ubuntu side talks to via libhybris
[14:31] <r0kk3rz> yep, and theres a bit in the middle that needs connecting
[14:31] <r0kk3rz> from the android sensor HAL to qt
[14:31] <r0kk3rz> in sailfish we have a daemon called sensorfwd that does this job
[14:32] <dobey> yes, we have a QPA which talks to libhybris
[14:34] <r0kk3rz> afaik thats mostly graphics stuff
[14:39] <r0kk3rz> im not seeing anything sensory in here https://launchpad.net/qtubuntu
[14:39] <r0kk3rz> is there somewhere else i should be looking?
[14:41] <pmcgowan> there is qtubuntu-sensors which talks to platform api
[14:41] <pmcgowan> usensord is a bit misnamed as its only vibration control
[14:42] <pmcgowan> r0kk3rz, ^
[14:43] <faenil> http://bazaar.launchpad.net/~phablet-team/qtubuntu-sensors/trunk/files/head:/plugins/
[14:43] <r0kk3rz> ill take a look through this one, thanks guys
[14:52] <r0kk3rz> where might the code for this live? <ubuntu/application/sensors/accelerometer.h>
[14:56] <pmcgowan> r0kk3rz, that is in the platform-api project
[14:56] <pmcgowan> https://code.launchpad.net/platform-api
[14:56] <r0kk3rz> cool thanks
[16:06] <TheKit> how Wi-Fi is set up on Aquaris Tablet in terms of hardware adaptation/MediaTek?
[16:39] <Nyxus> Does anyone know if the Meizu Pro 5 64GB/4GB Ram model is support?
[17:00] <learnbsd> Nyxus: i think so...didn't they ship that with ub touch on it?
[17:05] <Nyxus> learnbsd its was the the 32gb/3gb version
[17:05] <Nyxus> was just wondering if there was any problems
[17:10] <rbasak> Does anyone know something about a dead wifi system settings screen, a missing network indicator, and an empty "indicator-network" tab in the top edge menu?
[17:10] <rbasak> This reproduces on my Aquaris 4.5 even after reboot. I can't touch wifi settings any more.
[17:10] <rbasak> It's completely broken. Related might be that I was trying to use the hotspot facility the other day and that just stopped working too.
[17:11] <rbasak> During that time I was getting hard resets as well as Unity restarts.
[17:11] <rbasak> It seems very buggy since the last OTA.
[17:11] <rbasak>  /home has 1.3G free and / has 232M free.
[17:11] <rbasak> Any suggestions on what to look for?
[17:12] <learnbsd> rbasak: i have no wifi either so not just you.
[17:12] <rbasak> I'm happy to help debug. I have sshd running and working so can poke around. Just not sure where to look.
[17:12] <rbasak> learnbsd: thanks
[17:15] <pmcgowan> rbasak, there is a known issue with stale lock files
[17:15] <dobey> rbasak: maybe bug #1615474
[17:15] <ubot5`> bug 1615474 in indicator-network (Ubuntu) "Network Indicator / Connectivity-API is not accessible" [Critical,In progress] https://launchpad.net/bugs/1615474
[17:15] <pmcgowan> that one
[17:16] <rbasak> Thanks! That looks likely. I'll try the workaround.
[17:17] <rbasak> Yes, that fixed it. Thanks again!
[17:17] <rbasak> I guess I ended up with the stale lock when I hit the buggy hotspot behaviour that made my phone crash.
[17:17] <pmcgowan> yeah thats an awful bug
[17:18] <rbasak> pmcgowan: the bug isn't tagged regression-release or anything. Is there any place you gather known OTA regression type bugs that I can check when I hit issues next time, please?
[17:19] <rbasak> I do love the battery life on this phone BTW. "Last charged 91 hours ago"
[17:20] <pmcgowan> rbasak, the lock file issue is not really a regression, unless you mean the hotspot issue?
[17:22] <rbasak> Fair enough. I do feel that Unity is less stable this OTA though. It's crashed a whole bunch of times on me. And the browser app has too, sometimes making it impossible to restart without a reboot. It feels like a memory leak or corruption in Unity to me (though that's just speculation).
[17:23] <rbasak> I feel that's an OTA regression, but I don't really know where to look for a bug there.
[17:24] <pmcgowan> hmm let me check the reports, we just fixed a browser crash
[17:25] <rbasak> I feel that my issue is wider than a browser crash, because I've also seen Unity disappear at random times. Sometimes it restarts itself (so I see the moving dots and then it's as if I've just rebooted, but quicker).
[17:26] <rbasak> And the phone app display is sometimes broken, which I notice when I try to hang up an incoming call (as I never look at the phone app itself when receiving a call)
[17:26] <rbasak> So that's why I suspect a memory leak or unity issue.
[17:26] <pmcgowan> the oom could be shooting them but shouldnt
[17:27] <pmcgowan> rbasak, what is your device
[17:27] <rbasak> Aquaris 4.5.
[17:29] <rbasak> The hotspot thing I feel may be separate. IIRC, I only got hard reboots when trying to get the hotspot going. At that time I kept switching network (for various unrelated reasons) so I was probably pushing against a race. I presume that's what caused my stale lock.
[17:29] <rbasak> But the general unstability I feel has happened since the last OTA and possibly unrelated to the hotspot and the missing network indicator.
[17:30] <dobey> something is probably eating your ram
[17:30] <rbasak> That's what I suspected.
[17:30] <dobey> with only 1 GB total, there really isn't much to go around, so it's not unfathomable that the OOM killer might be getting hit a fair bit on a phone where you use many apps
[17:31] <rbasak> Hmm
[17:31] <rbasak> indicator-datetime
[17:31] <rbasak> 315892 RSS.
[17:31] <rbasak> Espected?
[17:31] <rbasak> unit8 is 110048
[17:31] <rbasak> unity8
[17:31] <dobey> do you have a whole bunch of alarms
[17:32] <dobey> and/or events?
[17:32] <rbasak> Probably many events, as it's syncing my calendar.
[17:32] <rbasak> Not many alarms. Perhaps 4.
[17:32] <dobey> unity8 may not be the unity8 process you are looking for
[17:32] <rbasak> I'm sorting by highest RSS :)
[17:33] <rbasak> It seems unreasonable for indicator-datetime to be using so much RAM to hold my events. If that's a problem, it should keep them on disk.
[17:33] <rbasak> Is there a bug for that?
[17:33] <dobey> right. i just mean there are multiple things that are "unity8" so depending on what's actually getting killed that process may or may not be it
[17:34] <dobey> i don't know
[17:34] <dobey> it might not be indicator-datetime itself, but the e-d-s libs. hard to say without hard data
[17:35] <dobey> indicator-datetime isn't using that much RAM on my workstation though
[17:35] <rbasak> There's bug 1342123
[17:35] <ubot5`> bug 1342123 in indicator-datetime (Ubuntu) "evolution-calendar-factory always running with high memory usage" [High,Confirmed] https://launchpad.net/bugs/1342123
[17:35] <rbasak> But my evolution-calendar-factory process isn't actually so bad compared to indicator-datetime itself.
[17:36] <rbasak> I wonder if I should reboot to see if it's a leak.
[17:36] <rbasak> (though then why would it be RSS?)
[17:36] <dobey> yeah, evolution-calendar-facotry on my workstation is using ~165 MB RSS
[17:36] <rbasak> Mine is 35816 only (!)
[17:36] <dobey> why would a leak not be RSS?
[17:38] <rbasak> I'd expect it to get swapped out as it would be unused.
[17:39] <dobey> well if it's a leak it's probably "used"
[17:39] <dobey> even if it's not
[17:39] <dobey> and i don't think there is a disk swap on the phone anyway
[17:39] <rbasak> In a normal leak, the program forgets about the memory. The kernel then eventually swaps it out.
[17:39] <rbasak> My phone has:
[17:39] <rbasak> Swap:       524284     210748     313536
[17:40] <rbasak> If indicator-datetime consistently uses high RSS, I'll file a bug. I'll keep an eye on it.
[17:41] <dobey> well i would expect a leak on the stack to show up as RSS (always has in my experience anyway)
[17:41] <rbasak> Ah. I was thinking heap.
[17:41] <rbasak> Stacks don't normally leak. How would they without crashing?
[17:42] <rbasak> Anyway, I should go. Thank you for the help :)
[17:42] <dobey> cheers
[18:56] <lpotter> r0kk3rz: sensors are read by android SensorManager->platform-api->qtubuntu->qtsensors
[19:11] <r0kk3rz> lpotter: the device im working on doesnt seem to need sensormanager, which is a bit weird
[19:13] <lpotter> if it's android, it does
[19:13] <r0kk3rz> at least, the service doesnt appear to be running under android os
[19:14] <lpotter> they may have forked and renamed it perhaps
[19:14] <lpotter> what device?
[19:16] <r0kk3rz> its a sony z3 compact tablet, but we're having the same problem on all sony devices of that era
[19:17] <r0kk3rz> like the z2/z3 phone
[19:17] <r0kk3rz> the android sensor HAL returns 0 sensors
[19:19] <lpotter> might be permissions issue?
[19:22] <r0kk3rz> yeah possibly, but ive been looking for any perms issues and come up empty so far
[19:24] <lpotter> could try finding the sensors devnodes and lsof to see who is using them.
[19:25] <lpotter> bit offtopic for this channel though
[19:27] <r0kk3rz> yeah thats not a bad idea