=== salem_ is now known as _salem === founderio1 is now known as founderio === Coolguy42 is now known as ATDT911 === chihchun_afk is now known as chihchun === _salem is now known as salem_ === chihchun is now known as chihchun_afk === salem_ is now known as _salem [10:09] repowerd on the desktop causes laptop screen to turn off automatically since yesterday. It even sometimes causes a suspend as well. After a few hours of worrying, removing repowerd seems to have fixed the issue. [10:19] Hi [10:19] I need support [10:19] I'm fighting with bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592412 [10:19] Launchpad bug 1592412 in Canonical System Image "Remove waking screen by double tap on MX4" [Undecided,New] [10:20] and I found some temporary fix (I think). In my /sys/devices/*/*/* there is a file called gesture_test [10:20] and there is option 'disable_all=0'. I want to change that, I'm using adb shell, but I can't overwrite file [10:21] Permission denied [10:21] could anyone help? [10:26] I need to make my filesystem writable? === zhxt is now known as zhxt_work === LarreaMikel1 is now known as LarreaMikel === vrruiz_ is now known as rvr [11:49] ktatar156, if you need to do that, then instructions are here: https://developer.ubuntu.com/en/phone/devices/installing-ubuntu-for-devices/ [12:03] ok, I made writable [12:03] but I need to edit file in /sys/* folder [12:03] is there any way to do that? [12:04] file "gesture_test" and there is option 'disable_all=0'. I want to change that, [12:04] not that I know, sorry === LarreaMikel1 is now known as LarreaMikel === JanC is now known as Guest20161 === JanC_ is now known as JanC === _salem is now known as salem_ [13:20] I need to edit one thing in file /sys/devices/bus.1/11009000.I2C2/i2c-2/2-0020/input/input1/gesture_test [13:20] how can I do that? [13:22] ktatar156: i think you need to fix the udev file for the device [13:23] hmm... how to do that? [13:23] wrong path, I need to edit /sys/bus/i2c/drivers/mtk-tpd/2-0020/input/input1/gesture_test [13:37] dobey: how to do that? [13:37] grep -R *mtk-tpd* / [13:37] not here, sorry :) [13:38] i don't think you can [13:47] there isn't any way to change that boolean value in file gesture_test ? [14:28] ktatar156, I dont thin that file controls the config, probably just shows it [14:28] did you check for an idc file? [14:29] I don't know what it is. I've found [14:29] $ ls /system/usr/idc/ [14:29] autopilot-finger.idc hid-keyboard.idc qwerty2.idc qwerty.idc [14:29] ok same then [14:30] but I need somehow to set one value in file /sys/devices/platform/mt-i2c.2/i2c-2/2-0020/input/input1/gesture_test [14:30] but I think that is just showing you what is set, not setting it, need a kernel guy to advise [14:31] I know that it shows value that has been set. But now I need to know how to change that value [14:32] to remove these stupid DT2W [14:32] https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592412 [14:32] Launchpad bug 1592412 in Canonical System Image "Remove waking screen by double tap on MX4" [Undecided,New] [14:37] ktatar156: I thought we disabled that in the touch driver [14:38] oh wow.. [14:38] I think it's a long story... I've installed latest FlymeOS 5.1.x (with DT2W support). And next I've installed again UT. But I think that there are some bits left from Android 5.x responsible for DT2W [14:38] ok [14:39] but installing UT means installing the UT kernel.. [14:39] and that one would come with the firmware for the touch panel [14:39] isnt there a wishlist item to have double tap to wake.. [14:41] but how works flashing kernel? [14:42] Simply it works like copying and overwritting all files/folders, [14:42] but if in destination there are more files not included in source [14:42] path, installation will leave them untouched (don't remove them), [14:42] right? [14:42] Is there any possibility to fix that (remove these additional Android [14:42] 5.x bits)? I mean to get something similar to 'rsync --delete' (it [14:42] sync and delete files in destination which are not present in the [14:42] source). [14:49] anpok: If you want, I can upload my FlymeOS 5.x rom with DT2W working with MX4 Ubuntu Edition. You can flash it and next go back to UT and you'll see that DT2W is working [14:49] for me, the problem is I need somehow to edit /sys/class/input/input1/gesture_test file (change boolean value) [14:50] well, you need to set the thing that makes that show 0 to show 1 [14:50] you don't necessarily need to set *that* to 1 [14:52] ktatar156, what is the contents of gesture_test [14:52] i can compare to mine with no dt2w [14:53] exacly [14:53] https://paste.gnome.org/prtn3zs3l [14:54] Before, I've checked in FlymeOS. When I turn on gestures mode (in GUI Settings), changed from disable_all=1 to disable_all=0 [14:55] but in UT there isn't such option to control that. So I'm looking for manually set that value to true [14:55] ok it is different no surprise [14:55] gesture_control=0 tap(0),swipe(0),O(0),V(0),unicode(0) [14:56] need to find out where that is set [14:56] * ogra_ guesses there is some firmware partition ... [14:57] the rest of the values are the same here [14:58] we rely on the factory to prepare the partitioning properly on ubuntu ... we only format our own partitions when flashing .. so if whatever you used to flash flyme overwrote a partition we do not touch, will not be reverted by ubuntu-device-flash [14:59] (this is also true for IMEI and friends btw ... but likely also for any firmware carrying partitions) [14:59] pmcgowan: Please look at https://paste.gnome.org/pxa1vgx57 [15:00] strange that there are for gesture_{control,hex,data} but not gesture_test [15:01] and in really I don't know what exacly is that what I've generated ;) [15:02] Maybe there is a need to somehow add that ATTR{gesture_test}=="..." ? [15:02] I get syspath not found when I issue that command [15:02] ogra_: is there any way to revert changes? [15:02] it is very unlikely that you can influence it beyond flashing the right firmware blob to the right place, i guess the node is readonly by default [15:04] pmcgowan: try udevadm info -a -p /sys/class/input/input1 [15:04] naw it looks the same [15:04] http://pastebin.ubuntu.com/22320247/ [15:05] so not sure we can get at it a ogra_ says [15:06] so I don't understand why all other files from */input1/ folder are set by ATTR{file_name} (or it looks like them are set in that way), but not gesture_test [15:07] so to sum up - there is no possibility to change/show in 'gesture_test' line 'disable_all==1', right? [15:09] there is, by flashing the right file to the right partition ... [15:10] there is likely nobody who can tell you which file or which partition though [15:10] ktatar156, but as I said my gesture_test also has disable=0 so not sure thats the magic [15:10] since that is done in the factory for the ubuntu preinstalled devices [15:11] ok, so I'm going back to FlymeOS and waiting for new UT avaible to buy.... :( [15:12] how did you re-flash btw ? [15:12] from FlymeOS to UT? [15:13] either way [15:13] using the MTK toool ? [15:13] no, fastboot TWRP and flash my custom update.zip [15:13] ah [15:13] and going to UT by normal ubuntu flash way [15:14] ohh.. I've touched again my phone and it look that swipe to wake also works...:( [15:14] if we look again at https://paste.gnome.org/prtn3zs3l [15:14] tap and swipe has '1'. [15:15] so DT2W and S2W works:/ [15:16] Last chance [15:16] https://paste.gnome.org/pxa1vgx57 [15:16] there is ATTR{gesture_control}="" [15:16] Is there any way to change that to ATTR{gesture_control}="0" [15:17] ? === dandrader is now known as dandrader|afk [15:37] ktatar156: my experience with touch screen drivers is that you do not have runtime control.. but I may be wrong. looking back at the code [15:37] mediatek structure is so confusing [15:39] maybe writing some udev rule will help? [15:39] Sth like: ACTION=="add" KERNEL=="input1" SUBSYSTEM=="input" DRIVER=="" ATTRS{name}=="mtk-tpd" ATTR{gesture_control}="0" [15:40] Will that change gesture_control from "" to "0"? === dandrader|afk is now known as dandrader [15:46] ktatar156: try it.. === davidcalle is now known as davidcalle|afk === dandrader is now known as dandrader|afk [16:53] ...what the!! [16:53] mute is gone and "silent mode" is back [16:55] this is a terrible regression ☹ [16:55] mute allowed me to watch facebook videos in the library [17:00] brunch8752: you've got that the wrong way round. mute showing and silent mode not, was the regression :) [17:01] brunch8752: also, headphones? :) === dandrader|afk is now known as dandrader [17:49] dobey: I don't really always have my headphones around [17:50] I've never been a big fan of silent mode... you can always just lower the call volume to nothing [17:51] silent mode is great [17:54] but eh, boats and floats [17:55] I guess you're right... [17:56] I suppose what we really need is multiple volume controls [17:56] android started with one and eventually realized the need of more [17:58] we have them [17:59] brunch8752: i'm not sure if it's installed on the phone, but as a workaround for your case, "pactl set-sink-mute" might work for you [18:00] ooo thanks dobs [18:00] We do have multiple volume controls? [18:01] well, there are "roles" used on the phone. multimedia role is different from alert (ringtone) and call rols, iirc [18:01] ah yeah, indeed [18:01] the volume control is contextual [18:01] but I meant from a multiple sliders point of vie [18:02] yeah, the UX is a bit awkward still [18:02] it would be really handy for me to have two sliders [18:02] well, youtube itself has a slider [18:02] in the video player [18:03] well yeah but it still starts playing before you can lower it [18:03] but yeah, managing multiple volume levels can get awkward quick [18:03] I'll just fall back to what I did before [18:03] which is have multimedia sound off by default [18:03] and raising it when needed to then lower it before stopping [18:04] well i guess you'd do the same thing if there were multiple sliders, too :) === zulucloud1 is now known as zulucloud [18:06] that's correct! [18:07] on the other hand, forgetting to set it down wouldn't be an issue anymore [18:14] dobey, brunch8752 the updated design calls for multiple volume slides, 2 I think, but I think we need more [18:14] ringtone and media, bt we also need alerts imo [18:14] pmcgowan: more? ...like microphone slider like on the desktop [18:14] ? [18:14] need per-app volume i think [18:15] yeah, that would be great [18:15] thats also a thing yeah [18:15] ie, what we need is the same as we have under unity7 [18:16] most definitely ☺ [18:16] controls for device inputs/outputs, on for alerts/notification sounds, and then per-app volume === labsin_ is now known as labsin [18:57] when the app that shows the scopes "hangs" (doesn't react to input), is there a way to restart it? [18:58] other apps can be killed by swiping up or down in the task switcher, but that one not... [19:01] JanC: "restart unity8-dash" in terminal [19:01] well, it's hard to start a terminal if I can't use the app scope :) [19:02] launcher? [19:02] you can swipe from left edge to open the launcher still [19:02] if it would have been there... [19:03] hold power button and choose "restart" ? :) [19:03] yeah, that worked [19:03] but was anoying (happened yesterday) [19:03] *annoying* [19:04] would be nice if you could kill/restart it in the task switcher [19:04] yse, bugs are indeed annoying [19:04] well, it kind of is the task switcher [19:05] I mean the one that you get when swiping from the right [19:05] yes [19:05] so do i [19:05] that still worked [19:05] I could switch between running apps & and close apps [19:05] yes, the process wasn't hanged [19:06] i guess [19:06] or maybe that is actually a different process [19:07] so only the thread(s) that show(s) the scopes interface or something? [19:07] or maybe it was waiting for something from the backend [19:07] well, "hanged" is difficult to interpret [19:07] didn't react to any user input [19:07] right, but that could mean many different things [19:08] hard to debug if you are somewhere "on the road" with only a phone :) [19:08] hard to debug anyway [19:11] JanC, is that on proposed channel? [19:11] saw that on an mx4 when testing something else [19:11] nope [19:11] hmm [19:29] Hi, is there any news about Meizu MX6 with Ubuntu? Is it still in plans? Or any other phone that will be avaiable to buy soon? === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader [21:03] Hi, is there any news about Meizu MX6 with Ubuntu? Is it still in plans? Or any other phone that will be avaiable to buy soon? [21:31] ktatar156: no news