SailfishOS on Motorola Droid 4 XT894 (alpha port) - Page 11 - maemo.org

merpl | # 101 | 2017-08-04, 12:45 | Report

My vote would be for TheKit's solution since most of my use of alt and ctrl is for irssi - alt/ctrl+n/p

I'd also make < and > map to SYM(alt)+, and . keeping the ; and : as labeled on the keyboard.

Definitely also need \ ~ | somewhere.

I was also thinking maybe OK could be a right-shift, you know to shift the stuff on the left half of the keyboard more easily.

With the ALT mapped, we don't really need a seperate key mapped for '\', - for e.g. we could make it alt+L to put it near the normal US placement.

just my $0.02.

This is the greatest thing since the N900 folks. TheKit is one of my heroes. <3

The Following User Says Thank You to merpl For This Useful Post:
juiceme

wicket | # 102 | 2017-08-04, 16:18 | Report

Originally Posted by TheKit View Post

Quick question. In the next build I want to remap some keys in kernel, to avoid editing xkb files. Do you think it's a good idea to make Caps Lock => Shift and Shift => Ctrl, or this will cause unneeded confusion?

SYM is going to be Left Alt (needed to allow layout switching combinations, for example). What would be the good use for OK? Currently I have it as \ and | key on my device, which is useful in terminal.

This thread may be of interest. It provides details on how the keys are mapped in mainline Linux.

P.S. I got myself a Droid 4, but not for Sailfish nor Android

The Following 5 Users Say Thank You to wicket For This Useful Post:
juiceme, Macros, moodroid, mp107, t-b

tmlind | # 103 | 2017-09-12, 14:47 | Report

Originally Posted by wicket View Post

This thread may be of interest. It provides details on how the keys are mapped in mainline Linux.

Yeah let's keep kernel changes to minimum and map the custom keys in user space as we need to do that anyways.

The user space app to use here in the long run is probably funkeymonkey:

https://github.com/bzar/funkeymonkey

Originally Posted by wicket View Post

P.S. I got myself a Droid 4, but not for Sailfish nor Android

Yeah it should be possible to use any distro no problem.

For booting distros, please also take a look at the utagboot I pushed last night. It should allow booting sailfish from any partition, the microSD card should work too:

https://github.com/tmlind/utagboot

Cheers,

Tony

The Following 6 Users Say Thank You to tmlind For This Useful Post:
juiceme, maegon9y00, moodroid, mp107, t-b, wicket

merpl | # 104 | 2017-09-14, 04:22 | Report

I noticed RetroArch emulator failed to start. On latest xt894 release from TheKit

After a websearch i found this seems to be related to egl problems.

Code:

[nemo@Sailfish /]$ test_egl
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found

[nemo@Sailfish /]$  EGL_PLATFORM=hwcomposer test_egl
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found
Segmentation fault

[nemo@Sailfish /]$  EGL_PLATFORM=fbdev test_egl
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found
ERROR: failed to open framebuffer: (Bad address)
test_egl: eglplatform_fbdev.cpp:35: void fbdevws_init_module(ws_egl_interface*): Assertion `0' failed.
Aborted

[nemo@Sailfish /]$ EGL_PLATFORM=null test_egl
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found
^C  [just sits there]

[nemo@Sailfish /]$ EGL_PLATFORM=wayland test_egl
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found
Segmentation fault

Looking for the egl drivers I found these:

Code:

[nemo@Sailfish /]$ ls -l /usr/lib/libhybris
total 368
-rwxr-xr-x 1 root root 104899 Apr  5 23:55 eglplatform_fbdev.so
-rwxr-xr-x 1 root root  25224 Apr  5 23:55 eglplatform_hwcomposer.so
-rwxr-xr-x 1 root root  19194 Apr  5 23:55 eglplatform_null.so
-rwxr-xr-x 1 root root 209501 Apr  5 23:55 eglplatform_wayland.so

Searching for PVROGL

Code:

find / -name libPVROGL.so

returns nothing.

I tested on three devices. All same result.

Now i just found something interesting:

Code:

[nemo@Sailfish /]$ EGL_PLATFORM=wayland test_egl_configs
Starting test (EGL_PLATFORM=wayland)
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found
Segmentation fault

[nemo@Sailfish /]$ EGL_PLATFORM=hwcomposer test_egl_configs
Starting test (EGL_PLATFORM=hwcomposer)
linkerlinker.c:1109| ERROR: Library 'libPVROGL.so' not found
linkerlinker.c:1109| ERROR: Library 'libPVROCL.so' not found
EGL Version 1.4
Extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer EGL_ANDROID_recordable EGL_HYBRIS_native_buffer2 EGL_HYBRIS_WL_acquire_native_buffer EGL_WL_bind_wayland_display 
Available configurations: 25
===== Configuration #0 =====
  EGL_RED_SIZE: 8
  EGL_GREEN_SIZE: 8
  EGL_BLUE_SIZE: 8
...
much more stuff

I have the sgx540 driver loaded of course.

Code:

[root@Sailfish lib]# lsmod
Module                  Size  Used by
compat                  1502  0
tty_hci                 3952  0
pvrsrvkm_sgx540_120   293781  130
wl12xx                167937  0
mac80211              378066  1 wl12xx
cfg80211              144942  2 mac80211,wl12xx
wl12xx_sdio             2806  0

Possibly relevant discussions:
http://www.merproject.org/logs/%23sa...12-25.log.html

Can someone confirm this on their device? What do we do to get it working?

EDIT: The PVROGL and PVROCL aren't important and don't cause the errors, afaict. These mobile GPUs only need to support OpenGL-ES. AFAIK

Last edited by merpl; 2017-09-14 at 06:25.

The Following User Says Thank You to merpl For This Useful Post:
juiceme

ThePhxRises | # 105 | 2017-09-19, 04:20 | Report

I was never able to upload those ofono logs, and have since removed sfos from my Droid 4, though I can definitely confirm that CDMA networks do not work at all. If it's any help the log loops the same 3 or 4 lines over and over, but I can't recall them right now. My apologies, but if I can get my Droid 4's battery replaced so it doesn't die in .02 milliseconds, I'll look into getting those logs.

The Following User Says Thank You to ThePhxRises For This Useful Post:
juiceme

ThePhxRises | # 106 | 2017-09-24, 03:53 | Report

I decided to reinstall SFOS and ran the logger for a few minutes. The logs are attached.

Additionally, it may just be the humidity, but there almost seems to be some touch screen calibration issues.

EDIT: After using it for a while, I noticed the battery indicator still only moves in intervals of 10, and doesn't seem to work about 1/3 of the times I boot, constantly showing 100%.

Attached Files

ofono_2017-09-23_202346.tar.gz (24.2 KB, 104 views)

Last edited by ThePhxRises; 2017-09-25 at 02:03.

The Following User Says Thank You to ThePhxRises For This Useful Post:
juiceme

merpl | # 107 | 2017-09-25, 11:38 | Report

Experimenting with Camera and video recording:

it defaults to store pictures in
/home/Nemo/Pictures/Camera
and for video
/home/Nemo/Videos/Camera

This is bad because root partition is almost full.

I try to go to Settings->Apps->Camera and change Storage setting, to point it to the sdcard.

This lists Device memory and many entries saying 'Memory card is unmounted'.

SFOS File Browser also doesn't register a mounted sdcard, however it can be accessed under the /media path.

My workaround currently to make space for pictures is to symlink directories on my sdcard to the /home/Nemo Pictures and Videos directories.

my sdcard is mounted on
/dev/mmcblk0p1 on /media/sdcard/3933-3934

using updated sdcard utils script https://git.merproject.org/mer-core/sd-utils

Some discussion on xt894 sd mounting here: http://www.merproject.org/logs/%23sa...09-18.log.html

The Following 2 Users Say Thank You to merpl For This Useful Post:
juiceme, moodroid

Flash-A-Holic | # 108 | 2017-10-31, 10:50 | Report

Originally Posted by ThePhxRises View Post

After using it for a while, I noticed the battery indicator still only moves in intervals of 10, and doesn't seem to work about 1/3 of the times I boot, constantly showing 100%.

I can confirm that battery state is usually showing 100%. Sometimes reboot will fix it but sometimes not.

I have been using Droid 4 with Sailfish OS as a daily driver for a while and it works OK. There are some issues but I'm hoping that those can be fixed in future.

If the keyboard layout is still in pipeline I hope that TheKit could add Scandic support like it is done in FinQwerty Android app (https://play.google.com/store/apps/d...qwerty.finnish).

Anyway, thanks for hardwork so far

.

The Following 4 Users Say Thank You to Flash-A-Holic For This Useful Post:
eekkelund, imaginaryenemy, juiceme, ThePhxRises

tmlind | # 109 | 2017-12-04, 01:33 | Report

Originally Posted by tmlind View Post

For booting distros, please also take a look at the utagboot I pushed last night. It should allow booting sailfish from any partition, the microSD card should work too:

https://github.com/tmlind/utagboot

And now we have a flashable 4MB kexecboot image at :

https://github.com/tmlind/droid4-kexecboot

Note that kexec booting v3.0.8 kernels needs the initramfs modified to use the kernel command line instead of the SafeStrap configuration on mmcblk1p25 if somebody wants to work on that.

The Following 4 Users Say Thank You to tmlind For This Useful Post:
jakibaki, juiceme, t-b, wicket

merpl | # 110 | 2017-12-13, 18:06 | Report

Nice work tmlind, ty. Might try that if I end up filling the remaining 200MB.

For what its worth, I realized I was being silly with the SD card issues. You can label the SD card partition and the mountpoint will be your label name. So now symlinks from /home/nemo are reliable (for Camera / Videos for e.g.).

Other than that, Sailfish on XT894 has been wonderful! I do need to hook it up to the charger overnight, or it seems to become unresponsive (crashed?) requiring a long power button hold to turn off and reboot.

The Following User Says Thank You to merpl For This Useful Post:
juiceme