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