OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio


Welcome Guest ( Log In | Register )

Personal Photo
Personal Statement
mithrandir doesn't have a personal statement currently.
Personal Info
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
No Information
Joined: 7-January 18
Profile Views: 667*
Last Seen: Today, 12:31 PM
Local Time: Feb 20 2019, 05:57 PM
78 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Private
* Profile views updated each hour



My Content
13 Feb 2019
I have just tried to connect a Bluetooth headset and failed. Has anybody successfully tried?

Pairing has been successful and when turned on bluetoothctl says the headset is connected, but by no way I could get pulseaudio to playback on the device.
30 Jan 2019
Does anybody know the pinout and type of the camera connector? Just thinking about connecting a NFC reader/writer to it instead of the outer camera... Anyways, the metal cover might prevent this. Still, this might be interesting for other upgrades.
15 Jan 2019
After performing the latest updates repowerd fails to start form me. Thus i.e. standby on close does not work any more.

root@gemini:/home/gemini# journalctl --unit=repowerd|cat
-- Logs begin at Tue 2019-01-15 18:12:52 CET, end at Tue 2019-01-15 18:32:29 CET. --
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: main: Starting repowerd 2017.03
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: SysfsBacklight: Using backlight /sys/class/leds/lcd-backlight
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: Unable to load selected module, using dummy.
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: Loading module: 'libubuntu_application_api_test.so.3.0.0'
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: TestSensor INFO: Setup for DYNAMIC event injection over named pipe /tmp/sensor-fifo-1473
Jan 15 18:12:54 gemini.mittelerde.ldr repowerd[1473]: TestSensor WARNING: Requested sensor light not yet created, blocking thread until create event received

However, I cannot find any information on libubuntu_application_api_touch_mirclient.so. It looks like recently this got used by (at least it worked before) libubuntu_application_api.so.

root@gemini:/usr/lib/aarch64-linux-gnu# egrep -r touch_mirclient
Binary file libubuntu_application_api.so.3.0.0 matches

One of these updates seems to have caused the problem:

Start-Date: 2019-01-14 01:24:11
Commandline: apt upgrade
Requested-By: gemini (100000)
Upgrade: libsystemd0:arm64 (232-25+deb9u6, 232-25+deb9u7), udev:arm64 (232-25+deb9u6, 232-25+deb9u7), libudev1:arm64 (232-25+deb9u6, 232-25+deb9u7), systemd-sysv:arm64 (232-25+deb9u6, 232-25+deb9u7), libpam-systemd:arm64 (232-25+deb9u6, 232-25+deb9u7), systemd:arm64 (232-25+deb9u6, 232-25+deb9u7)
End-Date: 2019-01-14 01:24:28

Start-Date: 2019-01-14 02:25:59
Commandline: apt remove desktop-mirror
Requested-By: gemini (100000)
Remove: desktop-mirror:arm64 (0.8.1)
End-Date: 2019-01-14 02:26:01

Start-Date: 2019-01-14 20:46:08
Commandline: apt upgrade
Requested-By: gemini (100000)
Upgrade: qtdeclarative5-ubuntu-telephony-phonenumber0.1:arm64 (0.2+gemian+0~20190112143006.17~1.gbp1b2b0b, 0.2+gemian+0~20190114151319.18~1.gbp784b7f), qtdeclarative5-ubuntu-telephony0.1:arm64 (0.2+gemian+0~20190112143006.17~1.gbp1b2b0b, 0.2+gemian+0~20190114151319.18~1.gbp784b7f), gemian-leds:arm64 (0.2+0~20190109163524.18~1.gbp42eccd, 0.2+0~20190114170611.20~1.gbp05ed0a), telephony-service:arm64 (0.2+gemian+0~20190112143006.17~1.gbp1b2b0b, 0.2+gemian+0~20190114151319.18~1.gbp784b7f)
End-Date: 2019-01-14 20:46:14

Start-Date: 2019-01-14 23:42:36
Commandline: apt upgrade
Requested-By: gemini (100000)
Install: libubuntu-application-api3:arm64 (3.0.3+gemian+0~20181125114448.15~1.gbp734b8b, automatic), libubuntu-platform-hardware-api3:arm64 (3.0.3+gemian+0~20181125114448.15~1.gbp734b8b, automatic), ubuntu-application-api3-test:arm64 (3.0.3+gemian+0~20181125114448.15~1.gbp734b8b, automatic)
Upgrade: repowerd-data:arm64 (2017.03+gemian+0~20181111171657.32~1.gbp0646ca, 2017.03+gemian+0~20190114210411.41~1.gbp3a0332), libzmq5:arm64 (4.2.1-4, 4.2.1-4+deb9u1), gemian-lock:arm64 (2.10+0~20180429112217.12~1.gbp94657a, 2.10+0~20190114215247.15~1.gbp2b698d), repowerd:arm64 (2017.03+gemian+0~20181111171657.32~1.gbp0646ca, 2017.03+gemian+0~20190114210411.41~1.gbp3a0332)
End-Date: 2019-01-14 23:44:14

Start-Date: 2019-01-15 02:10:44
Commandline: apt upgrade
Requested-By: gemini (100000)
Upgrade: qtdeclarative5-ubuntu-telephony-phonenumber0.1:arm64 (0.2+gemian+0~20190114151319.18~1.gbp784b7f, 0.2+gemian+0~20190114210353.19~1.gbpf74835), qtdeclarative5-ubuntu-telephony0.1:arm64 (0.2+gemian+0~20190114151319.18~1.gbp784b7f, 0.2+gemian+0~20190114210353.19~1.gbpf74835), telephony-service:arm64 (0.2+gemian+0~20190114151319.18~1.gbp784b7f, 0.2+gemian+0~20190114210353.19~1.gbpf74835)
End-Date: 2019-01-15 02:10:47

Is anybody else facing the same problem? Ideas how to fix or where to get the missing lib (assuming it is the cause)?


12 Nov 2018
After recent upgrades (maybe xorg, maybe repowerd, maybe whatsoever) and a reboot sddm gives a core dump on my gemini (stays at the penguin logo). No useful info in logs. Anybody else experiencing the same? What might have happened?

21 Jun 2018
I don't know exactly what happened and am a bit hopeless now. Maybe after flashing a kernel, maybe after trying to get a mobile connection with linux (ofono) the modem stopped working. System information in Android shows no sim cards (also not the esim), no IMEI numbers and baseband version is unknown.

Already tried full reflash and restoring the nvram backup.

Anybody else also experienced this? How to find out if the modem is broken or just the IMEI numbers are lost? Any ideas for recovery? Maybe using SN Writer (https://forum.hovatek.com/thread-12306.html) if it is just the IMEIs? This requires two database files (MD1_DB and AP_DB) which should be part of the ROM. Where to find these files? Other ideas?

Last Visitors

18 Feb 2019 - 11:16

29 Jun 2018 - 8:13

9 Jan 2018 - 22:09

Other users have left no comments for mithrandir.

There are no friends to display.
RSS Lo-Fi Version Time is now: 20th February 2019 - 05:57 PM