Issue with Android odroidm1-121-20230328

[tokawit]

I just installed latest Android image (selfinstall-odroidm1-121-20230328) and I noticed two issue;

- The virtual keyboard does not shows up, it should come up clicking on input text box.
- There is no way to set a screen lock, app crash every time (logcat here: https://pastebin.com/raw/Kdm920ZG).

Thanks for the help.

[Luke.go]

1. you can change the option to show virtual keyboard.
Settings -> System ->Languages &input -> Physical keyboard -> check Use on-screen keyboard

2. It is hard to support about screen lock features. Now you can use Swipe option.

[tokawit]

Thanks for your reply.

1. If I enable that option and then connect a physical keyboard, the virtual keyboard continues to appear on the screen.
IMHO this is a bug, the virtual keyboard should appear by default without having to change anything in the settings, and if I connect a physical keyboard the virtual one should not appear on the screen.
AFAIK this is how it works on any android version.

2. Is this issue something to do related to the Google Play Services as it is not a certified device?

[Luke.go]

Sorry For late reply.

1. I tested it on the latest release. But it just work without physical keyboard like you said. when I connected vu8m display to the ODROID-M1 and selected the search bar or other text typing view, virtual keyboard is appeared.
when connected usb mouse to the ODROID-M1, It just work like you said, virtual keyboard is appeared.
Just when connect usb keyboard to the ODROID-M1, the virtual keyboard is not appeared.
So I'm not sure there is bug. I tested on the 20230328 version.
Please check your connected devices. or please share your environment. I will test with it.

2. It is not related to Google Play service. And, actually we find the way to use screen lock. but it need to update petitboot. and it is not yet updated.
because, it has powerful security methods. when you activate screen lock feature, you can't access user data partition when you are not unlock the screen.
AND if you swap the installed media (like eMMC or SD card) to the other ODROID-M1, YOUR USER DATA WILL NEVER BE ACCESSED. So if you want to use the media, you should format user data.
This powerful security method can cause user's unnecessary experience. actually it is good to security side. but if you confuse attaching devices,, you can imagine what happens.

So I want to know why you need this feature. Because of the above issues, we want to approach this issue cautiously. Actually it will be disabled on the default settings, but you can make it be enabled.

[tokawit]

1. That's strange, see my video please, it's a fresh install of latest rom selfinstall-odroidm1-121-20230328 (eng, not userdebug version) connected via HDMI to a monitor, I just have USB mouse connected, nothing else, and the virtual keyboard does not appear.

Video: https://www.dropbox.com/s/g00n1shdf0k1sg7/M1.mkv

2. Not a problem, I wanted to set the lock screen to avoid having my son access the TV when he shouldn't.

[Luke.go]

Please share your logcat message when you connected your mouse to the odroid-m1.
let me check about your shared logcat message.

2. Please wait until petitboot is uploaded.

[tokawit]

Here is the logcat: https://pastebin.com/raw/8JfFC2sk
It's a Logitech M220 mouse.

I tried with another Logitech mouse (M185) and the virtual keyboard appear
Looks like the system see the M220 more like a "keyboard" than a mouse.

[tokawit]

I found another bug; The "Screen recorder" tile does not works as it should, the output file is just a full green screen.

[Luke.go]

I found another bug; The "Screen recorder" tile does not works as it should, the output file is just a full green screen.

Oh.. please share another logcat please.
I tested it, and... it also work on my ODROID-M1.
https://drive.google.com/file/d/1lGwrTY ... share_link

[tokawit]

Logcat here: https://pastebin.com/raw/c1u6wt7y

Another user reported the same issue some time ago: viewtopic.php?f=213&t=45551

[Luke.go]

Sorry for late reply.

This problem was related to Memory size. It was not happened on the odroid-m1 with 4GB memory but happened on the odroid with 8GB.

Now, we fixed this problem and it will be applied next release.

And, to more fast apply please try with attached file.

First connect your odroid-m1 to the host pc with OTG cable.

And try this commands.

Code: Select all

$unzip patch.zip
$ adb remount
$ adb push vendor/lib/libomxvpu_enc.so /vendor/lib/
$ adb push vendor/lib64/libomxvpu_enc.so /vendor/lib64/
$ adb reboot

you can now record the screen!

[tokawit]

I can confirm the patch fixed the issue! Thanks!!

I don't know if this could be an issue with "libfs_mgr" but this is the output of adb remount

Code: Select all

$ adb remount
Using overlayfs for /system
Using overlayfs for /vendor
Using overlayfs for /odm
Using overlayfs for /product
Using overlayfs for /system_ext
[libfs_mgr]__mount(target=/system,flag=MS_PRIVATE)=-1: Invalid argument
[libfs_mgr]__mount(source=/system/bin/su,target=/dev/TemporaryDir-iNnZxC,flag=MS_MOVE)=-1: Invalid argument
Now reboot your device for settings to take effect
remount succeeded

[Luke.go]

Nice to solve this problem!

that's not problem. so don't care.