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