| Wizzup | uvos: for the rtcom call logging, shall I try to bring that up to my current understanding of how it should look like? | 00:17 |
|---|---|---|
| Wizzup | (for sphone) | 00:17 |
| diejuse | Wizzup Dbus working :D | 00:29 |
| diejuse | Fixed | 00:29 |
| Wizzup | great | 00:31 |
| Wizzup | what was the change? | 00:31 |
| diejuse | First I pseudo-mounted some key /proc files with proot. For example from /proc/uptime. That fixed the "/etc/init.d/dbus:50:[:-lt:unexpected operator" error | 00:33 |
| Wizzup | from some googlnig it looks like proot-distro would also create the uptime file | 00:34 |
| Wizzup | https://old.reddit.com/r/termux/comments/oalnsh/proc_inside_proot/h3jc29b/ | 00:35 |
| diejuse | Second, I checked the /etc/init.d/dbus file (I have knowledge of shell scripting) and made a modification that did the trick. In "start-top-daemon –start –quiet –pidfile $PIDFILE –chuid messagebus:messagebus –exec $DAEMON – –system $PARAMS" you must add "--chuid messagebus" or "--chuid $DAEMONUSER". | 00:35 |
| Wizzup | https://wiki.termux.com/wiki/PRoot this seems to suggest btw that it can do mount-bind's somehow | 00:36 |
| Wizzup | diejuse: I see @ modification | 00:36 |
| diejuse | With this change the "pid" and "system_bus_socket" files are created (finally!) in the /var/run/dbus directory. | 00:38 |
| Wizzup | great | 00:39 |
| diejuse | https://old.reddit.com/r/termux/comments/oalnsh/proc_inside_proot/h3jc29b/ -=> Yes, I applied Termux patches. | 00:40 |
| diejuse | It is the only solution (now) for non-rooted Android phones | 00:41 |
| diejuse | Now there are several things to solve and I ask you for help. | 00:41 |
| diejuse | First of all, portrait rotation (again). I have achieved it. It works fine in Maemo apps but it doesn't work when I open Debian apps (black screen). | 00:43 |
| Wizzup | hm, do maemo apps work in both rotations for you? | 00:44 |
| Wizzup | and how did you achieve it? | 00:44 |
| diejuse | At the end of launchMaemo.sh I have added "sleep 5; dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'portrait' " | 00:47 |
| diejuse | And works | 00:47 |
| Wizzup | okay, so the rotation isn't typically 'permanent' any apps that do not advertise support for portrait mode will get forced back to landscape mode, which might be what is giving you a black screen | 00:47 |
| diejuse | Everything works fine except when I open any Debian app. | 00:47 |
| Wizzup | I think there is a way to force it to stay in portrait, let me try to find it | 00:49 |
| Wizzup | iirc we had orientation lock applet | 00:49 |
| diejuse | Ok. I have installed orientation applet but I don't see changes. | 00:50 |
| Wizzup | you want to go into portrait mode and then activate the lock | 00:51 |
| diejuse | I did that but it doesn't work | 00:54 |
| Wizzup | ok | 00:57 |
| Wizzup | I don't have a solution directly | 00:58 |
| diejuse | OK. I'll investigate too. Another subject. Is there a way to get the virtual keyboard in a non-Maemo application? For example in the "mousepad" text editor. | 01:00 |
| Wizzup | there is a way to raise it regardless of the application | 01:01 |
| Wizzup | on various maemo devices we have a key that raises the keyboard | 01:01 |
| diejuse | perfect. How? | 01:02 |
| Wizzup | in /usr/share/hildon-desktop/shortcuts.ini you can set assign a key to raise the keyboard | 01:02 |
| Wizzup | like: | 01:02 |
| Wizzup | [Shortcuts] | 01:02 |
| Wizzup | RaiseVkb=XF86Search | 01:02 |
| diejuse | Do you know what code corresponds to any volume key? | 01:03 |
| Wizzup | XF86RaiseVolume I think is for vol up | 01:07 |
| Wizzup | and XF86LowerVolume | 01:07 |
| diejuse | I'll try it when I get the normal keyboard back. I have updated before from Beowulf to Chimaera and I have lost the virtual keyboard. It is normal? | 01:11 |
| Wizzup | do you mean that you did apt-get dist-upgrade? | 01:13 |
| diejuse | yes | 01:13 |
| Wizzup | it should not happen, but your setup is perhaps a bit more niche | 01:13 |
| diejuse | Maybe it will work if I reinstall hildon-input-method | 01:14 |
| Wizzup | dbus is key again here | 01:15 |
| diejuse | But it's already working. The rest of the things do work. | 01:17 |
| Wizzup | maybe manually start hildon-input-method and see | 01:18 |
| Wizzup | (if there are any errors) | 01:18 |
| diejuse | Wow, the keyboard appeared when I pressed volume+ (the code was XF86AudioRaiseVolume). Great! | 01:25 |
| Wizzup | note that this force-raise keyboard is not as featureful as the regular virtual keyboard, which is context aware | 01:26 |
| Wizzup | (lets you line edit) | 01:26 |
| Wizzup | uvos: ok, I made a voicecall-manager xsession script, rebooted my d4 and calls work on boot with voicecall-manager and sphone with that module | 01:27 |
| diejuse | Is there a way to edit the virtual keyboard keys? The enter key does not give me the line break (/n) and I cannot execute. | 01:36 |
| Wizzup | diejuse: hm, what are you seeing that is being sent? | 01:58 |
| diejuse | When I press the enter key, ithe keyboard exits tand sends what I have typed but does not do a line break. | 02:15 |
| diejuse | For example, in LXTerminal I put "ls" and want to send it but it just writes "ls" without sending it. | 02:16 |
| Wizzup | mhm | 02:21 |
| Wizzup | and you don't get the maemo keyboard in osso-xterm? | 02:21 |
| Wizzup | I just realised that maemo might detect that you have a keyboard attached and that it cannot be 'slide in' | 02:22 |
| Wizzup | in this case the virtual keyboard won't come up | 02:22 |
| Wizzup | (is this the case?) | 02:22 |
| diejuse | I don't have a physical keyboard with this smartphone. Furthermore, it did not happen with Beowulf. | 02:27 |
| diejuse | Anyway, in my last question I meant that I want to be able to do a line break at any time. That is, differentiate sending from a line break, regardless of the context. | 02:28 |
| diejuse | * differentiate between send and a line break, regardless of the context. | 02:29 |
| Wizzup | right, there is a way to edit the keys but I don't know on top of my head - it'll be similar to how it used to work in maemo | 02:30 |
| Wizzup | I need to get some rest first though :) | 02:30 |
| diejuse | It would be nice to be able to edit the keyboard and add some keys (arrow keys for example) | 02:31 |
| diejuse | Ok, it's true, it's late. | 02:31 |
| Wizzup | this reminds me | 02:31 |
| Wizzup | freemangordon: currently on the droid 4 keyboard I can't type any numbers in the phone number field in abook, I think this is because it doesn't understand that the drid 4 keyboard is different | 02:32 |
| Wizzup | freemangordon: maybe we should make a ticket for it if not already | 02:32 |
| diejuse | I think it is very important that a user can add their own keys. Especially smartphones without a keyboard. With a file in xml format for example. | 02:33 |
| diejuse | *withot physical keyboard | 02:33 |
| Wizzup | like I said, this is doable, but I do not know/remember how | 02:34 |
| Wizzup | https://github.com/maemo-leste/hildon-input-method-plugins/tree/master/scv_layouts | 02:35 |
| Wizzup | this might be it | 02:35 |
| Wizzup | well this is for the special keys I guess | 02:36 |
| Wizzup | https://github.com/maemo-leste/hildon-input-method-plugins/tree/master/hildon-im-virtual-keyboard-layouts | 02:36 |
| * Wizzup zzz | 02:38 | |
| diejuse | But there is a way to edit directly from Maemo or you have to edit and then compile? | 02:39 |
| Wizzup | right now I think not | 02:39 |
| diejuse | I'll look for it and tomorrow we'll talk more. Rest well. | 02:40 |
| freemangordon | Wizzup: abook, uses h-i-m afaik, this might be just a RE bug I introduced, will check | 07:37 |
| freemangordon | Wizzup: also, it might help if you define what 'd4 keyboard is different' means in that regard | 07:44 |
| freemangordon | like, there is no issue in the VM | 07:45 |
| Wizzup | freemangordon: I don't think it is a re bug, I think it is a hildon gtk2 'feature' that doesn't work on d4 | 11:24 |
| Wizzup | well so the maemo keyboard has numbers on the q,w...p keys | 11:24 |
| Wizzup | so when you are in the phone number field, and you press 'w' it will just type '2', regardless of wheter you press the blue arrow | 11:24 |
| Wizzup | on the droid 4 the numbers are just keys on their own | 11:25 |
| Wizzup | anyway that was just my guess, I might be wrong and maybe it is some re bug | 11:25 |
| freemangordon | Wizzup: ah, right, makes sense | 11:41 |
| diejuse | So any possibility of having an .xml that the user can edit to customize the virtual keyboard keys? | 12:28 |
| freemangordon | diejuse41: https://github.com/maemo-leste/hildon-input-method-plugins/tree/master/hildon-im-virtual-keyboard-layouts | 14:22 |
| freemangordon | gen_vkb is part of libimlayouts | 14:23 |
| diejuse41 | freemangordon Sorry I don't understand the technical details. What I want to know is if a user can edit the keyboard while ML is running without having to compile the source code. :) | 14:33 |
| Wizzup | rafael2k: hey | 14:46 |
| rafael2k | Wizzup: hi there! | 14:49 |
| Wizzup | rafael2k: anything I can help with for ppp iage? | 14:55 |
| Wizzup | image | 14:55 |
| rafael2k | Wizzup, I think the most important is with hildon-desktop | 15:02 |
| rafael2k | work on the primary display xrandr issue | 15:02 |
| rafael2k | the rest should be straight forward | 15:02 |
| rafael2k | I did not had time to work on it past 2 weeks, so on my side, the issue is stuck on the same point me and freemangordon discussed | 15:03 |
| Wizzup | I thought you had a workaround for now, right? | 15:07 |
| rafael2k | ha, not in form of code... | 15:12 |
| rafael2k | typing xrandr cmds in the cli does not really help | 15:12 |
| rafael2k | (not for something to be released to public) | 15:12 |
| Wizzup | I see | 15:23 |
| diejuse | Wizzup I already know why it doesn't work that the virtual keyboard appears after dist-upgrading from Beowulf to Chimaera. During the upgrade I got the error "dpkg: error processing package hildon-desktop:arm64" and I skipped the error with "rm /var/lib/dpkg/info/hildon-desktop:arm64*" and "apt -f install" . But of course, that way it doesn't | 15:28 |
| diejuse | install correctly. | 15:28 |
| Wizzup | right | 15:29 |
| diejuse | I don't know why I get "dpkg: error processing package hildon-desktop:arm64" | 15:29 |
| diejuse | I don't have a solution at the moment. | 15:29 |
| Wizzup | do you have more context? | 15:30 |
| rafael2k | the primary display hd picks is a disconnected one | 15:33 |
| rafael2k | but it is the one returned by x(randr) calls | 15:34 |
| Wizzup | so h-d should check whether it is connected or not? | 15:39 |
| Wizzup | or should we make the lcd the primary display | 15:39 |
| rafael2k | I think both would work | 16:00 |
| Wizzup | the latter would maybe just be a dts change? | 16:01 |
| freemangordon | Wizzup: unfortunately xrandr reports inconsistent data to h-d | 16:42 |
| freemangordon | like, it reports display as connected, but no crt (or somesuch, I don;t remember the details) | 16:43 |
| freemangordon | also, for neither of the displays it reports the type (Panel, etc) | 16:44 |
| freemangordon | I really don;t know enough for xrandr to decide whether it is ok to report missing display as primary | 16:44 |
| Wizzup | wonder how xrandr knows then | 16:54 |
| freemangordon | I am not sure it knows, as it reports primary for a disconnected display | 16:57 |
| freemangordon | it reports no crt for the connected display and reports disconnected for primary | 16:57 |
| freemangordon | a mess | 16:57 |
| freemangordon | maybe you can boot your PPP and create some shared debuggin session | 16:58 |
| freemangordon | we can cooperate trying to get some sane data from what xrand reports | 16:58 |
| freemangordon | me alone was not able to | 16:59 |
| Wizzup | ok, if rafael2k has a somewhat easy way to get me up and running | 17:13 |
| uvos | freemangordon: all of those sound like obvious bugs | 19:15 |
| uvos | rafael2k: you could modify https://github.com/IMbackK/drm_blankscreen/blob/master/main.c will print the properties of the crts by quering the kernel/drm directly | 19:17 |
| uvos | i suspect its wrong | 19:17 |
| uvos | ie kernel bug | 19:17 |
| uvos | *you dont have to modify it any iirc it dump prints the props | 19:17 |
| uvos | you have to execute this while xorg is not running or is in a different crt, it needs to become drm master | 19:18 |
| uvos | *different vt | 19:18 |
| freemangordon | uvos: my gut feeling tells me the same (bug in kernel), however, I have no hard data to provide | 19:20 |
| uvos | drm_blankscreen would tell him | 19:23 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!