| freemangordon | yeah, but I think gtk3 im will benefit more people | 00:02 |
|---|---|---|
| freemangordon | also, it should be more or less way easier and faster than vrfb | 00:03 |
| freemangordon | I doubt it will take more more than a week or so | 00:03 |
| freemangordon | anyway, time to zzz | 00:05 |
| freemangordon | night! | 00:05 |
| freemangordon | ok, vkb works in empathy :) | 09:25 |
| freemangordon | a little buggy still, but well... | 09:25 |
| Wizzup | freemangordon: :) | 09:41 |
| freemangordon | Wizzup: does not work in either FF or chromium | 10:15 |
| freemangordon | I wonder why | 10:16 |
| uvos__ | freemangordon: ff and chromium are not really any toolkit | 10:19 |
| uvos__ | they use the webengine to render everything inc the ui | 10:20 |
| freemangordon | yes, but thay should have some integration with input methids | 10:20 |
| uvos__ | ff uses gtk to integrate with linux | 10:20 |
| uvos__ | but this is skin deep often | 10:20 |
| uvos__ | sure | 10:20 |
| uvos__ | there is also the option of useing atispi | 10:20 |
| uvos__ | i have some code that works with this | 10:21 |
| uvos__ | also the x11 option will allways be needed | 10:21 |
| uvos__ | since there are applications with random or no tooklits | 10:21 |
| freemangordon | sure | 10:21 |
| freemangordon | hmm, why it stopped working? | 10:22 |
| uvos__ | what stopped working/ | 10:22 |
| uvos__ | ? | 10:22 |
| freemangordon | vkb in empathy | 10:23 |
| uvos__ | it did? | 10:23 |
| freemangordon | yes | 10:23 |
| uvos__ | what toolkit dose that sue? | 10:23 |
| freemangordon | gtk3 | 10:23 |
| uvos__ | so the x11 backend dosent work? | 10:23 |
| freemangordon | I ported im module to gtk3 | 10:23 |
| uvos__ | oh ok | 10:23 |
| uvos__ | no idea i never used any of this | 10:23 |
| freemangordon | well, I just use empathy as test tool | 10:24 |
| freemangordon | for gtk3 application | 10:24 |
| freemangordon | oh, it seems h-i-m crashed :D | 10:26 |
| uvos__ | wrt replacement | 10:33 |
| uvos__ | for him | 10:33 |
| uvos__ | examining how phosh and the plamo keyboards work might be usefull | 10:33 |
| uvos__ | iirc plamo is derived from the meego keyboard | 10:33 |
| freemangordon | then it is tied to qt | 10:34 |
| uvos__ | well him is tied to gtk2 | 10:34 |
| freemangordon | no, I mean that it works only in qt | 10:34 |
| uvos__ | and has other defficancies too | 10:34 |
| Wizzup | him works in x11 too, no? | 10:34 |
| Wizzup | :) | 10:34 |
| uvos__ | not sure how that is different to him really | 10:34 |
| freemangordon | we will have to write plugins for gtk | 10:35 |
| uvos__ | not sure how that is different to him really | 10:35 |
| uvos__ | xD | 10:35 |
| freemangordon | we already have plugins for gtk :P | 10:35 |
| uvos__ | 2 | 10:35 |
| uvos__ | but not qt | 10:35 |
| uvos__ | so its neigher here nore there | 10:35 |
| freemangordon | we have code for qt4 | 10:35 |
| uvos__ | also plamo may have done so allready | 10:35 |
| uvos__ | at least for gtk3 | 10:35 |
| freemangordon | yeah | 10:36 |
| freemangordon | backport to gtk2 shoudl be trivial | 10:36 |
| freemangordon | uvos__: ok, but what is the situation with browsers? | 10:36 |
| freemangordon | as for toolkits is more or less the same | 10:37 |
| uvos__ | where? | 10:38 |
| freemangordon | hmm, my ubuntu has vkb that is able to type cyrillic if FF | 10:39 |
| freemangordon | *in FF | 10:39 |
| Wizzup | wouldn't at spi help with browser input? | 10:39 |
| Wizzup | imho the main him shortcoming is no arrow keys / support for that mode (direct input) and portrait being a bit cramped | 10:40 |
| Wizzup | otherwise it's not bad | 10:40 |
| uvos__ | freemangordon: onboard | 10:41 |
| freemangordon | yes | 10:41 |
| uvos__ | yes onboard works on qt and gtk | 10:41 |
| freemangordon | Wizzup: adding arrows is easy | 10:41 |
| uvos__ | directt input however | 10:41 |
| uvos__ | goes against the way him works fundamentaly | 10:41 |
| freemangordon | not really | 10:42 |
| freemangordon | see special symbols vkb for example | 10:42 |
| uvos__ | well the vkbs are on a plugin interface | 10:42 |
| uvos__ | that expects strings | 10:42 |
| uvos__ | sure there are special exceptions also for enter etc | 10:42 |
| uvos__ | but really in the main | 10:42 |
| uvos__ | it expects to transfer finished strings | 10:42 |
| freemangordon | we can always add one more atom for direct input | 10:43 |
| uvos__ | imo this requires rearchitecting the plugin interface to the extent that you might as well replace him | 10:43 |
| Wizzup | burn down and rewrite is not my fav way of doing things, but we can do it in some cases | 10:44 |
| Wizzup | for maemo leste we're rarely doing the burn down approach | 10:44 |
| Wizzup | :) | 10:44 |
| uvos__ | replace dosent nessecarly mean rewrite | 10:44 |
| uvos__ | since we could try and use something that exitst | 10:45 |
| uvos__ | the main obstical here is | 10:45 |
| uvos__ | hildon-desktop | 10:45 |
| uvos__ | hidon-desktop dosent support the atom usualy used by the vkbs to dock themselves to the bottom of the display | 10:45 |
| uvos__ | and dosent support multi window at all | 10:45 |
| uvos__ | but this is also the same problem with him | 10:46 |
| uvos__ | if you add direct input | 10:46 |
| uvos__ | and if you solve this defficancy in h-d | 10:46 |
| uvos__ | then onboard would for instance simply work | 10:46 |
| uvos__ | (but maybe be not ideal on a phone screen) | 10:46 |
| uvos__ | then you can see if the phosh keyboard would not simply work too | 10:47 |
| freemangordon | ok, seems chromium somhow obeys gtk3 IM, as when that new plugin is added, hwkb typing is ignored | 10:47 |
| uvos__ | (imo it should) | 10:47 |
| freemangordon | so, it is a matter of fixing it and it should work | 10:47 |
| Wizzup | I have a hard time imagining it on landscape | 10:47 |
| Wizzup | freemangordon: nice | 10:47 |
| _uvos_ | something ate my commens | 10:54 |
| _uvos_ | btw at-spi | 10:54 |
| _uvos_ | id like to mention again that with at-spi you could in the main make the x11 backend behave like the gtk2 one | 10:54 |
| freemangordon | hmm, focus_in etc is called | 10:54 |
| _uvos_ | ie field click opens vkb etec | 10:54 |
| freemangordon | so it is really some bug | 10:54 |
| _uvos_ | and that works in _every_ toolkit | 10:54 |
| freemangordon | great | 10:55 |
| freemangordon | I have no experience with that though | 10:55 |
| _uvos_ | there is some proof of concept code | 10:55 |
| _uvos_ | in the him repos as a branch | 10:55 |
| _uvos_ | freemangordon: its pretty undocumented | 10:56 |
| _uvos_ | at-spi is also a huge security risk | 10:56 |
| Wizzup | (and all DEs use it( | 10:56 |
| Wizzup | ) | 10:56 |
| _uvos_ | that in wayland allows you to read a lot of stull that makes "X11 insecure" | 10:56 |
| _uvos_ | https://github.com/IMbackK/hildon-input-method/commit/6f7adcf49553a74cbeb7fe5fff9153e060ac8ac2 | 10:58 |
| _uvos_ | here is proof of concept code | 10:58 |
| freemangordon | ok, our chromium is buggy in regards to gtk IM | 11:22 |
| freemangordon | hmm, actually upstream is buggy too | 11:23 |
| freemangordon | it never calls gtk_im_context_set_client_window() unless a key is pressed | 11:23 |
| rafael2k | I would also consider Palemoon as browser alternative, which still maintains gtk2 builds, alongside with gtk3 builds. | 12:14 |
| rafael2k | http://linux.palemoon.org/ | 12:15 |
| rafael2k | and have read-made Debian 10 builds | 12:16 |
| rafael2k | : ) | 12:16 |
| _uvos_ | hows touch support | 12:22 |
| _uvos_ | the other mentioned browsers have very good support for touch gestures | 12:22 |
| rafael2k | xorg updated - wow! | 12:22 |
| rafael2k | _uvos_: not very good gesture support I guess... but it is considerably faster than ff or chromium | 12:29 |
| rafael2k | I'm using it, but with mouse and keyboard | 12:29 |
| _uvos_ | not sure about faster | 12:29 |
| _uvos_ | on d4 ff is pretty mutch the faster browser by a large margine | 12:29 |
| _uvos_ | (scrolling speed wise) | 12:29 |
| rafael2k | try palemoon | 12:30 |
| rafael2k | it is faster, at least in the PP | 12:30 |
| rafael2k | I'm using the gtk2 build, btw | 12:30 |
| _uvos_ | freemangordon: btw current cellulard/pinentry dosen reccognize when a puk is required (dont ask me how i know xD) | 12:32 |
| _uvos_ | rafael2k: seams way slower than ff | 12:35 |
| _uvos_ | wierd, maybe beacuse d4 has a faster gpu than pp but a mutch slower cpu | 12:36 |
| rafael2k | interesting | 12:37 |
| rafael2k | anyone, both work fine here tbh | 12:39 |
| rafael2k | *anyway | 12:39 |
| rafael2k | a simple "top" measurement for opening "google.com", ff eats 24% of the system memory, while palemoon gtk2 9% (2GB total) | 12:44 |
| _uvos_ | top sucks at this because it fails to account for shared memory | 12:47 |
| _uvos_ | also ff holds buffers based on total memory size (yes this is really dumb) | 12:48 |
| rafael2k | right, indeed... not a trustworthy method | 12:48 |
| rafael2k | did not know about this in ff | 12:48 |
| rafael2k | :/ | 12:48 |
| _uvos_ | anyhow d4 total memory usage with ff loaded at google is 345 mb | 12:50 |
| _uvos_ | as a point of referance | 12:50 |
| _uvos_ | 32bit helps some here too ofc | 12:50 |
| rafael2k | 366.4 MiB here | 12:52 |
| _uvos_ | for ff or system? | 12:53 |
| rafael2k | ff | 12:53 |
| rafael2k | 176.6 MiB palemoon | 12:53 |
| _uvos_ | my value was total system | 12:53 |
| _uvos_ | anyhow its fine | 12:53 |
| _uvos_ | both ;) | 12:53 |
| rafael2k | indeed | 12:54 |
| rafael2k | I'm using this to measure: https://github.com/pixelb/ps_mem | 12:54 |
| _uvos_ | rafael2k: yeah thats a good tool | 12:54 |
| rafael2k | it really yelps : ) | 12:55 |
| rafael2k | btw, "sphone: route-pulseaudio: failure: Set sink to Earpiece No such entity" | 13:00 |
| rafael2k | sphone: route-pulseaudio: failure: Set sink to Speaker No such entity | 13:01 |
| rafael2k | sphone: route-pulseaudio: Seting route on alsa_output.1.stereo-fallback | 13:01 |
| rafael2k | So no Speaker nor Earpiece entities in Maemo PP UCM config | 13:02 |
| rafael2k | Also, who packaged the ring tune, packaged in the wrong location (my package was right...): sphone: playback-gstreamer: /usr/share/sounds/Nokia_tune.aac is not a valid file | 13:03 |
| rafael2k | maemo-ringtones-mr0 <-- is the package wrong | 13:05 |
| uvos__ | alsa_output.1.stereo-fallback sounds like its the wrong audio device or? | 13:06 |
| uvos__ | alsa_output.1.stereo-fallback sounds like its the wrong audio device or? | 13:06 |
| uvos__ | can you switch in pavucontrol-qt during a call | 13:06 |
| uvos__ | whats your default sink during a call? | 13:06 |
| uvos__ | (pactl info) | 13:06 |
| rafael2k | yes | 13:06 |
| uvos__ | maybe also add pactl list to the bug | 13:07 |
| rafael2k | btw, maemo-ringtones-mr0 changed /usr/share/sounds/Nokia_tune.aac to /usr/share/sounds/NokiaTune.aac dunno why... :( | 13:07 |
| rafael2k | ok | 13:07 |
| rafael2k | "Internal speaker" makes the audio out through the speaker | 13:10 |
| rafael2k | (in pavucontrol) | 13:10 |
| rafael2k | about the ringtone, any advice where to fix it? in the package or in the sound profile? | 13:12 |
| rafael2k | ps: this was my package, as a reference: https://www.abradig.org.br/maemo-crazyness/maemo-ringtone_0.1-2_all.deb (which made my phone ring) | 13:13 |
| rafael2k | btw, I'm debbuging libcamera in this issue: https://github.com/kbingham/libcamera/issues/28#issuecomment-1257167174 | 13:22 |
| rafael2k | still trying to have a clear picture with qcam... | 13:26 |
| uvos__ | rafael2k: yeah so the problem with the button in sphon ei ssimply | 13:30 |
| uvos__ | Default Sink: alsa_output.1.stereo-fallback is wrong | 13:30 |
| uvos__ | should be alsa_input.0.Voice_Call__hw_PinePhone_0__sink | 13:31 |
| uvos__ | so this is a pa setup issue, not related to sphone itself. | 13:31 |
| rafael2k | is it with my specific setup or with PP in general? | 13:37 |
| rafael2k | (I mean, Maemo in PP setup) | 13:39 |
| uvos__ | well unless you changed something wrt that maemo on pp | 13:39 |
| rafael2k | I did not afair | 13:46 |
| freemangordon | chromium on d4 runs circles around FF | 13:50 |
| freemangordon | to my surprise | 13:50 |
| rafael2k | a couple of (still looking shitty) pics taken with qcam in maemo in PP: https://www.abradig.org.br/maemo-crazyness/test.jpg https://www.abradig.org.br/maemo-crazyness/test1.jpg | 13:56 |
| freemangordon | nice :) | 13:57 |
| rafael2k | one of libcamera devs (Kieran Bingham) is trying to help | 13:59 |
| rafael2k | lets see if we get these problems squared out... then we'll have all the lower level plumbing done (including gstreamer sources!) | 14:00 |
| uvos__ | nice at pp images | 15:48 |
| uvos__ | i should try and get the front camera on d4 working some time | 15:49 |
| freemangordon | uvos__: re PUK - how to repro without blocking my SIM? | 18:10 |
| buZz | oh man, these typos get me everytime, what :D | 18:35 |
| buZz | > sphone: sphone-conf: Could not get config key ExternalExec/CallAwnserd | 18:35 |
| buZz | Awnserd? :D no wonder you cant find it, sphone-conf | 18:35 |
| buZz | (btw, i'm having corona, hence my afk-ness) | 18:36 |
| Wizzup | take care | 18:37 |
| uvos | buZz: i hope you get better soon :) | 18:41 |
| uvos | yeah idk what these sphone devs where thinking | 18:42 |
| buZz | spellchecker too expensive ;) | 18:51 |
| buZz | uvos: sent a PR for correcting these :) | 19:18 |
| uvos | freemangordon: hmm i cant repo the dimm problem | 19:41 |
| uvos | freemangordon: so i wait until mce dimms | 19:41 |
| uvos | then i "dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_display_state_on" | 19:42 |
| freemangordon | yes | 19:42 |
| freemangordon | but, while it is dimming | 19:42 |
| uvos | yeah | 19:43 |
| freemangordon | did you repro? | 19:43 |
| uvos | no | 19:43 |
| uvos | so while its dimmed but not off | 19:43 |
| uvos | i send that call | 19:43 |
| uvos | this is the log i get | 19:43 |
| uvos | mce: Received display on request | 19:43 |
| uvos | mce: MCE_DISPLAY_ON in /build/mce-1.10.0+2m7/src/modules/display.c display_on_req_dbus_cb 446 | 19:43 |
| uvos | mce: inactivity: device inactivity timeout 30 | 19:43 |
| freemangordon | lemme try to repro here | 19:43 |
| uvos | it also dosent missbheave in any way | 19:43 |
| freemangordon | well, maybe because you are using different plugins | 19:44 |
| uvos | ill mv my user ini | 19:44 |
| uvos | sec | 19:44 |
| freemangordon | or maybe recent fixes fixed it | 19:44 |
| uvos | ugh | 19:45 |
| uvos | x hanged | 19:45 |
| uvos | well i never saw the issue | 19:45 |
| uvos | so idk about recent fixes | 19:46 |
| uvos | something about your setup vs mine is more likely | 19:46 |
| freemangordon | my setup is vanilla | 19:46 |
| uvos | sure | 19:46 |
| freemangordon | yes, the issue is still there | 19:48 |
| freemangordon | remember, you have to disconnect teh charger | 19:49 |
| uvos | still rebooting | 19:49 |
| freemangordon | did you upgrade x to latest? | 19:49 |
| uvos | yeah | 19:49 |
| uvos | it still hits https://github.com/maemo-leste/bugtracker/issues/614 tis | 19:50 |
| uvos | *this | 19:50 |
| uvos | sdl on drm also hits this | 19:50 |
| uvos | so i doubt its xorgs fault | 19:50 |
| freemangordon | never happaned here | 19:51 |
| freemangordon | *happened | 19:51 |
| freemangordon | ok, have to charge the batter a bit | 19:52 |
| freemangordon | uvosL also, I think having 3 times --verbose on mce cmdline helps with recreating the ussue | 19:53 |
| uvos | there is no verbose byond 2 times | 19:53 |
| uvos | but ok | 19:53 |
| freemangordon | well, I was running with 3 times | 19:54 |
| freemangordon | maybe one was ignored, dunno | 19:54 |
| uvos | yes it just decreases an int with no further effectr | 19:54 |
| uvos | anyhow so now with default modules i cant repo either | 19:54 |
| uvos | but no charger/usb let me get one | 19:54 |
| freemangordon | it is not *that* easy | 19:54 |
| uvos | (not that i know how it would make a difference) | 19:54 |
| freemangordon | timing? | 19:55 |
| uvos | idk how it would affect the timeing even | 19:55 |
| uvos | mce dosent really care | 19:55 |
| freemangordon | hmm, what the? now " display stays lit while on charger" actually works | 19:55 |
| uvos | anyhow let me try | 19:55 |
| uvos | thats wierd since the code in mce is gohne | 19:55 |
| uvos | and nothing reads the corrisponding datapipe | 19:56 |
| uvos | so it must be redundantly implmented | 19:56 |
| uvos | (not a suprise theres quite some stuf rdeundantly implmented) | 19:56 |
| freemangordon | yes, the issue is still there | 19:57 |
| uvos | ok so plug in charger | 19:57 |
| uvos | remove it? wait for dim? | 19:57 |
| freemangordon | disable "lock screen automatically" | 19:57 |
| freemangordon | maybe charger is unrelated | 19:57 |
| freemangordon | hard to tell | 19:57 |
| uvos | hmm | 19:58 |
| uvos | cant trigger it | 19:58 |
| uvos | still | 19:58 |
| freemangordon | set timeout to 10 seconds | 19:58 |
| uvos | yeah i have that | 19:58 |
| uvos | display stays lit when charging is on on your end? | 19:59 |
| freemangordon | no, it is onchecked | 19:59 |
| freemangordon | so: | 20:00 |
| uvos | i just triggered it | 20:00 |
| uvos | by unchecking that | 20:00 |
| uvos | no dbus required | 20:00 |
| freemangordon | ok | 20:00 |
| freemangordon | maybe | 20:00 |
| uvos | so its something about exiting that mode | 20:00 |
| freemangordon | I think dbus helps, but could be coincidence | 20:01 |
| uvos | i cant make it happen again | 20:01 |
| uvos | hmm | 20:01 |
| freemangordon | yes, it it not easily reproducible | 20:02 |
| freemangordon | that's why I think it is related to timing | 20:02 |
| freemangordon | maybe changing gconf setting is related | 20:02 |
| uvos | maybe but what would be changing gconf | 20:03 |
| freemangordon | we, from the settings | 20:03 |
| uvos | no | 20:03 |
| freemangordon | dunno, just speculating | 20:03 |
| uvos | those dont use gconf anymore | 20:03 |
| freemangordon | ugh | 20:03 |
| freemangordon | but what? | 20:04 |
| uvos | theoreticly only mce should use its gconf keys | 20:04 |
| uvos | ie its gsettings compliant | 20:04 |
| uvos | they use the dbus interface to tell mce what to do | 20:04 |
| freemangordon | how mce gets notified about the change? dbus? | 20:04 |
| freemangordon | ttyl | 20:07 |
| uvos | ttyl | 20:07 |
| Guest224 | I think that sept 25th stable release has security problem. It has at internet connection settings: Connect automatically Wi-fi...shoul it be Always ask...so that device doesn't go any open wi-fi:s automatically. | 21:06 |
| Guest224 | user can switch it automatically, if he/she wants later...but if user doesn't want..damage is done, if its default automatically. | 21:07 |
| Guest224 | ah..bad english...user can switch it to "connect automatically", if he/seh wants later...but if user doesn't want...dameage is done in first start up, if settings default is "connect automatically" | 21:11 |
| uvos | connect automatically dosent mean it connects to any open wifi | 21:18 |
| Guest224 | ok..does it have to choose one time and then it goes it automatically? | 21:19 |
| uvos | yes it connects to networks only if you connected to them before | 21:20 |
| Guest224 | thanks...good to know. | 21:20 |
| Guest224 | I also tested Pinephone docking bar with HDMI-output, but nothing happens...but should it even work yet with stable? | 21:21 |
| Guest224 | and I would test docking bar ethernet-port...any hints to good way to test? | 21:23 |
| Guest224 | 3G data-connection still need dev-image? | 21:25 |
| uvos | yes | 21:25 |
| uvos | hdmi out works | 21:25 |
| uvos | but you have to set it up by hand | 21:25 |
| uvos | via xrandr | 21:25 |
| uvos | and hildon-desktop has bugs if the display changes size | 21:26 |
| freemangordon | uvos: OTOH, I think mce should control kbd brightness better than it does now | 21:26 |
| freemangordon | right now no matter what happens, kbd backlight is barely visible | 21:27 |
| uvos | freemangordon: its user configurable | 21:27 |
| freemangordon | leaving kbd useless in dark conditions | 21:27 |
| uvos | imo its bright enough | 21:27 |
| freemangordon | it is not | 21:27 |
| uvos | but maybe d4s have variation | 21:27 |
| uvos | anyhow i dehardcoded it | 21:27 |
| freemangordon | here it is like it is off all the time | 21:27 |
| uvos | its honstly quite bright here | 21:28 |
| uvos | so thats wierd | 21:28 |
| freemangordon | sec | 21:28 |
| uvos | btw i found why display on while chargeing still wokrs | 21:28 |
| freemangordon | here it is almost absolutely dark here and brightness is 80 | 21:28 |
| uvos | indeed its redundantly implemented in fremantle | 21:28 |
| freemangordon | well, not that bad it seems :) | 21:28 |
| uvos | something tells mce to stay on | 21:29 |
| freemangordon | battery applet? | 21:29 |
| uvos | via inactivity_mode_set_dbus_cb | 21:29 |
| uvos | i have no idea whay | 21:29 |
| uvos | t | 21:29 |
| uvos | maybe | 21:29 |
| uvos | anyhow i think the issue is | 21:29 |
| freemangordon | you can dbus-monitor | 21:29 |
| uvos | that timers dont get reset if the dbus call disables the inactivity block | 21:30 |
| uvos | while dim | 21:30 |
| uvos | but i cant make it happen again | 21:30 |
| uvos | so hard to tell | 21:30 |
| uvos | the brightness of the display and the keyboard are not directly related | 21:31 |
| uvos | those are different tables | 21:31 |
| freemangordon | sure | 21:31 |
| uvos | btw | 21:31 |
| freemangordon | the point is that 80 for dark room is not enough | 21:31 |
| freemangordon | where is the table? | 21:31 |
| uvos | well i think it is, but that a user prefeance thing | 21:32 |
| uvos | mce.ini | 21:32 |
| uvos | so unplugging the usb creates activity | 21:33 |
| freemangordon | I cannot find it there | 21:33 |
| uvos | in mce | 21:33 |
| freemangordon | https://github.com/maemo-leste/mce/blob/master/config/mce.ini | 21:33 |
| uvos | so i gues it depends on if the dbus call comes before or after mce realises the usb gohne | 21:33 |
| freemangordon | yeah, might be related | 21:34 |
| uvos | maybe i should just remove this and have mce implement it again | 21:34 |
| uvos | it seams wierd for mce to have all info needed | 21:34 |
| uvos | but need some external tool to act on it.. | 21:34 |
| freemangordon | ok, where in mce.ini is that setting? | 21:35 |
| uvos | oh nowhere sorry | 21:35 |
| uvos | i forgot that i dehardcoded the brightness table for the display | 21:35 |
| uvos | but not the one for the keyboard | 21:35 |
| uvos | its in button-backlight.h | 21:35 |
| uvos | needs the same treatment as the ex table in display.h then | 21:36 |
| freemangordon | well, it seems there are 2 values only | 21:36 |
| uvos | yes the keyboard is off | 21:36 |
| uvos | beyond 1750000 lux | 21:36 |
| uvos | backlight wise | 21:37 |
| freemangordon | that's not ok | 21:37 |
| uvos | ? | 21:37 |
| freemangordon | as I said, kbd is useless for me in dim conditions | 21:37 |
| uvos | why would it be on in the sun | 21:37 |
| freemangordon | no need | 21:37 |
| uvos | 1750000 lux is pretty bright | 21:37 |
| freemangordon | then the table should be between 25 and 1750000 | 21:38 |
| freemangordon | ignoring higher readings | 21:38 |
| uvos | no | 21:38 |
| uvos | beacuse its user preferance | 21:38 |
| freemangordon | why? | 21:38 |
| uvos | someone might whant the keyboard light to be allways on | 21:38 |
| freemangordon | ok, but default should be sane | 21:38 |
| uvos | like on android | 21:38 |
| uvos | its sane | 21:38 |
| uvos | imo | 21:38 |
| freemangordon | currently it is not | 21:38 |
| freemangordon | no, trust me on that one | 21:38 |
| uvos | so 1750 lux should be Overcast day;[4] typical TV studio lighting | 21:39 |
| freemangordon | I can film you a video if you widh | 21:39 |
| uvos | table is in mlux | 21:39 |
| uvos | if something else is happening maybe your sensor is defective/ needs other callibration | 21:39 |
| uvos | (calibration is in 70-droid.ini | 21:39 |
| uvos | ) | 21:39 |
| freemangordon | what do you mean? | 21:39 |
| freemangordon | the max brightness that can be set is 128,no? | 21:39 |
| uvos | sure | 21:40 |
| uvos | but thats quite bright | 21:40 |
| freemangordon | not here | 21:40 |
| uvos | (set it via sysfs) | 21:40 |
| freemangordon | yes, that's what I did | 21:40 |
| uvos | i dont know what to tell you | 21:40 |
| uvos | i think its very bright, if you dont thats fine, ill dehardcode the table and you can set it to whatever you want | 21:41 |
| freemangordon | also, it seems it never hits 128 here | 21:41 |
| freemangordon | lemme check | 21:41 |
| freemangordon | it does | 21:42 |
| freemangordon | so, 80 is barely visible | 21:43 |
| freemangordon | esp if you set display brightness to max | 21:43 |
| uvos | 80 is farily dim but 25lux is very dark and the als cant realy mesure anything lower than that | 21:44 |
| uvos | and i dont want it bright in a totaly dark room | 21:44 |
| freemangordon | ok, but 250000 is too high threshold imo | 21:45 |
| uvos | sure but at 200 ish lux it can be off anyhow | 21:45 |
| freemangordon | so if you have indirect light (not sun) and display to max, kbd is not visible | 21:45 |
| uvos | imo | 21:45 |
| freemangordon | no, because you have reflections | 21:45 |
| uvos | i dont see how you can have a high lux reflection | 21:46 |
| freemangordon | from the buttons | 21:46 |
| uvos | but not have lots of external lux on the keyboard | 21:46 |
| freemangordon | of the keyboard | 21:46 |
| uvos | they are matte | 21:46 |
| uvos | i really dont follow | 21:47 |
| freemangordon | not if they are used :) | 21:47 |
| uvos | anyhow ill dehardcode the table | 21:47 |
| uvos | and shure we can add a entry for 100lux | 21:47 |
| freemangordon | tomorrow I'll capture a video to show you what I mean | 21:47 |
| uvos | "Very dark overcast day" | 21:47 |
| sicelo | incidentally, the buttons being too bright is the reason i disabled their lighting (and yes, i understand they only support On and Off) | 21:48 |
| freemangordon | a couple of times it was impossible for me to write anything in a bar because I simply cannot see the letters | 21:49 |
| freemangordon | sicelo: not really, this is how it is set now | 21:49 |
| freemangordon | maybe really there are HW variants | 21:49 |
| sicelo | i meant the touch buttons | 21:49 |
| freemangordon | ah | 21:49 |
| uvos | there ARE hw variants btw | 21:49 |
| uvos | d4 hwA has a different keyboard | 21:49 |
| uvos | (slightly) | 21:49 |
| freemangordon | yeah, they are bright, but to me they are fine | 21:49 |
| uvos | idk if it affects brightness | 21:49 |
| uvos | those are way to bright for me | 21:50 |
| uvos | i disabled those too | 21:50 |
| freemangordon | touch buttons? | 21:50 |
| uvos | like sicleo | 21:50 |
| uvos | yeah | 21:50 |
| freemangordon | not here | 21:50 |
| freemangordon | look normal to me | 21:50 |
| uvos | i think your eyes are simple different :P | 21:50 |
| freemangordon | but, I keep display to max | 21:50 |
| freemangordon | no, display is too bright here | 21:50 |
| uvos | anyhow those buttons are 1 bit | 21:50 |
| freemangordon | so, maybe display brightness shall affect kbd brightness as well | 21:51 |
| uvos | mabye | 21:51 |
| uvos | but lets dehardcode the table first | 21:51 |
| freemangordon | ok | 21:51 |
| uvos | its stupid anyhow | 21:51 |
| uvos | since a different device will need different values | 21:51 |
| freemangordon | in the meanwhile I will compile mce here :) | 21:51 |
| uvos | it just so happens to work ok across d4 an and n900 | 21:52 |
| Wizzup | Guest224: re: eth, you can just manually bring it up | 21:53 |
| Wizzup | we don't have a plugin for wired eth | 21:53 |
| Guest224 | ok | 21:53 |
| uvos | Wizzup: btw | 22:02 |
| uvos | the icd dialog still hangs even now (where gprs usualy works) | 22:02 |
| uvos | if gprs dosent work at that time | 22:02 |
| uvos | (ie by not entering the pin for instance) | 22:02 |
| uvos | or being out of range of a tower | 22:03 |
| freemangordon | oh, which remindsm me that I shall fix that stupid limit for wpa pass length we have somewhere | 22:03 |
| freemangordon | *reminds | 22:03 |
| uvos | freemangordon: https://github.com/maemo-leste/mce/commit/4442a4bfaa274abcaab7c8bb5b4ceadcbb5da930 | 22:10 |
| uvos | i think this fixes the issue | 22:10 |
| uvos | but its hard to be sure with the issue being so finiky to repduce | 22:10 |
| freemangordon | mhm | 22:10 |
| uvos | freemangordon: https://github.com/maemo-leste/mce/commit/b1954307d70f7013d6da8104c2b629e491e58af1 | 22:37 |
| uvos | buZz: thanks for the sphone pr | 22:39 |
| buZz | yw :) | 22:39 |
| buZz | i feel more might be coming in a while | 22:39 |
| uvos | https://github.com/maemo-leste/libhildon/pull/9 | 22:53 |
| uvos | Wizzup: what happened to lel? | 22:53 |
| uvos | buZz: how do you check the ofono sms qeue? | 23:06 |
| uvos | ./list-messages i gues | 23:09 |
| uvos | pending sweet | 23:09 |
| uvos | i cant send sms anymore | 23:09 |
| uvos | :( | 23:09 |
| uvos | freemangordon: could you give me the ofono envvars for debuging at some point | 23:10 |
| buZz | uvos: not list-messages | 23:10 |
| buZz | sudo ls /var/lib/ofono/thatlongnumber/tx_queue -l | wc -l | 23:11 |
| buZz | :D | 23:11 |
| uvos | /var/lib/ofono/ is filled with long numbers for me | 23:12 |
| uvos | anyhow list-messages shows my sms as forever pending | 23:12 |
| uvos | so thats why it nolonger works | 23:12 |
| uvos | probubly some new or now more severe ofono bug | 23:13 |
| uvos | dosent matter if i restart or reboot | 23:13 |
| buZz | https://paste.debian.net/plain/1255097 | 23:13 |
| uvos | no sms ever makes it | 23:13 |
| buZz | uvos: only one of such dirs here | 23:13 |
| buZz | afaik the number is the imsi, but not sure | 23:14 |
| uvos | i have like 20 dirs in thre | 23:14 |
| uvos | so if its imsi something is very wrong :P | 23:14 |
| buZz | maybe you copied install around a lot? :P | 23:14 |
| buZz | we already established your install is weird before, i think :D | 23:15 |
| uvos | pff wierd :P | 23:16 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
