Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 2 days, 15 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 3 days, 10 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 5 days, 19 hrs ago - more...
 |
|
2019-12-22
, 21:02
|
|
Posts: 1,092 |
Thanked: 4,995 times |
Joined on Dec 2009
@ beautiful cave
|
#22
|
I flashed again! It's NOT the SIM Card setting. I think there is an app or a patch which breaks it. I will leave it now for a while with no apps installed and do some reboots. ANd watch.
The SIM Card by the way is only getting lost after reboots. Not while Sailfish is running.
@mosen and @Kabouik can you make a list what apps and what patches you have installed. That would help me to find the culprit.
I'm quite sure there is no hardware problem! EVERY time I flash SIM is recognized again without any problems! I never ad problems on Android and at the beginning with not much installed.
You know, that I didn't waited to long with flashing, so the device had no problems with the SIM Card under Sailfish for quite a long time. It always started, when I started to install a lot of stuff.
The SIM Card by the way is only getting lost after reboots. Not while Sailfish is running.
@mosen and @Kabouik can you make a list what apps and what patches you have installed. That would help me to find the culprit.
I'm quite sure there is no hardware problem! EVERY time I flash SIM is recognized again without any problems! I never ad problems on Android and at the beginning with not much installed.
You know, that I didn't waited to long with flashing, so the device had no problems with the SIM Card under Sailfish for quite a long time. It always started, when I started to install a lot of stuff.
|
|
2019-12-22
, 21:11
|
|
Posts: 194 |
Thanked: 1,167 times |
Joined on May 2016
|
#23
|
@Fellfrosch, could you please install https://openrepos.net/content/slava/ofono-logger and send the logs (first review and edit in case there is sensitive data like numbers there) if the SIM is gone again? It should at least give some hints what to look at.
| The Following 5 Users Say Thank You to TheKit For This Useful Post: | ||
|
|
2019-12-22
, 21:12
|
|
Posts: 1,335 |
Thanked: 3,931 times |
Joined on Jul 2010
@ Brittany, France
|
#24
|
Ha! Now I finally lost my SIM card support too. :< Not particularly excited about reflashing after all the stuff I had already tweaked. :<
The SIM was still recognized, but I couldn't dial any number (an issue I reported on Github then closed because it was gone after a reboot). Therefore, I tried to reboot again, and this time there is no SIM slot listed in Setting > SIM cards.
Last edited by Kabouik; 2019-12-22 at 21:18.
The SIM was still recognized, but I couldn't dial any number (an issue I reported on Github then closed because it was gone after a reboot). Therefore, I tried to reboot again, and this time there is no SIM slot listed in Setting > SIM cards.
Last edited by Kabouik; 2019-12-22 at 21:18.
| The Following 4 Users Say Thank You to Kabouik For This Useful Post: | ||
|
|
2019-12-22
, 21:15
|
|
Posts: 1,335 |
Thanked: 3,931 times |
Joined on Jul 2010
@ Brittany, France
|
#25
|
Originally Posted by TheKit
I just get "Connected to ofono." in the logs, nothing else.
@Fellfrosch, could you please install https://openrepos.net/content/slava/ofono-logger and send the logs (first review and edit in case there is sensitive data like numbers there) if the SIM is gone again? It should at least give some hints what to look at.
When I try to dial a number from terminal, I get this:
Code:
[nemo@Sailfish ~]$ gdbus call -e -d org.nemomobile.voicecall -o / -m org.nemomobile.voicecall.VoiceCallManager.dial '+33611111111' Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'dial' in interface 'org.nemomobile.voicecall.VoiceCallManager' at object path '/' (signature 's')
(I got the command line from TJC.)
Last edited by Kabouik; 2019-12-22 at 21:27.
| The Following 4 Users Say Thank You to Kabouik For This Useful Post: | ||
 |
|
2019-12-22
, 21:19
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#26
|
In patch manager 3
- vibrate when call answer
- Launcher combined
- disble volume warning
- Show total partition size
Else
- Advanced camera
- AIDA64
- Battery Buddy
- Battery Log
- Compass
- Depecher
- Filecat
- fotokopierer
- gPodder
- GPSInfo
- InfraView
- Jolla Together
- Laufhelden
- LLs video
- ”tube
- NFC log
- Nightly Clock
- OBDFish
- Personal Ringtone
- Photofunia
- pico player
- Piepmatz
- Puremaps
- Quasar Mx lite
- Quickddit
- QR clip
- Recorder
- Sailbook
- SailDBMeter
- Sailfish Connect
- Sail Soma
- Screen Message
- Situation & started by sturman
- Storeman
- ToeTerm
- Ytplayer
- Zaster Banker
- vibrate when call answer
- Launcher combined
- disble volume warning
- Show total partition size
Else
- Advanced camera
- AIDA64
- Battery Buddy
- Battery Log
- Compass
- Depecher
- Filecat
- fotokopierer
- gPodder
- GPSInfo
- InfraView
- Jolla Together
- Laufhelden
- LLs video
- ”tube
- NFC log
- Nightly Clock
- OBDFish
- Personal Ringtone
- Photofunia
- pico player
- Piepmatz
- Puremaps
- Quasar Mx lite
- Quickddit
- QR clip
- Recorder
- Sailbook
- SailDBMeter
- Sailfish Connect
- Sail Soma
- Screen Message
- Situation & started by sturman
- Storeman
- ToeTerm
- Ytplayer
- Zaster Banker
__________________
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
| The Following 4 Users Say Thank You to mosen For This Useful Post: | ||
|
|
2019-12-22
, 21:39
|
|
Posts: 1,335 |
Thanked: 3,931 times |
Joined on Jul 2010
@ Brittany, France
|
#27
|
There is a "jolla-settings-networking-multisim" in the repository package that I tried reinstalling using "devel-su zypper in --force jolla-settings-networking-multisim", but no change.
I did the same with "jolla-settings-networking".
Both reinstallations gave some warnings:
Can these NOKEY issues be related to our issue?
Last edited by Kabouik; 2019-12-22 at 21:44.
I did the same with "jolla-settings-networking".
Both reinstallations gave some warnings:
[root@Sailfish nemo]# zypper install --force jolla-settings-networking-multisim
Loading repository data...
Reading installed packages...
Forcing installation of 'jolla-settings-networking-multisim-0.5.58-1.25.1.jolla.armv7hl' from repository 'jolla'.
Resolving package dependencies...
The following package is going to be reinstalled:
jolla-settings-networking-multisim
1 package to reinstall.
Overall download size: 81.2 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
Continue? [y/n/...? shows all options] (y): y
Retrieving package jolla-settings-networking-multisim-0.5.58-1.25.1.jolla.armv7hl
(1/1), 81.2 KiB ( 30.4 KiB unpacked)
Retrieving: jolla-settings-networking-multisim-0.5.58-1.25.1.jolla.armv7hl.rpm ....................[done (15.5 KiB/s)]
Checking for file conflicts: .................................................. .................................[done]
(1/1) Installing: jolla-settings-networking-multisim-0.5.58-1.25.1.jolla.armv7hl ...............................[done]
Additional rpm output:
warning: /home/.zypp-cache/packages/jolla/non-oss/armv7hl/jolla-settings-networking-multisim-0.5.58-1.25.1.jolla.armv7hl.rpm: Header V3 DSA/SHA1 Signature, key ID f2633ee0: NOKEY
add-oneshot: /etc/oneshot.d/0/dconf-update - job saved OK
[root@Sailfish nemo]# zypper install --force jolla-settings-networking
Loading repository data...
Reading installed packages...
Forcing installation of 'jolla-settings-networking-0.5.58-1.25.1.jolla.armv7hl' from repository 'jolla'.
Resolving package dependencies...
The following package is going to be reinstalled:
jolla-settings-networking
1 package to reinstall.
Overall download size: 112.0 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
Continue? [y/n/...? shows all options] (y): y
Retrieving package jolla-settings-networking-0.5.58-1.25.1.jolla.armv7hl (1/1), 112.0 KiB (204.9 KiB unpacked)
Retrieving: jolla-settings-networking-0.5.58-1.25.1.jolla.armv7hl.rpm ..........................................[done]
Checking for file conflicts: .................................................. .................................[done]
(1/1) Installing: jolla-settings-networking-0.5.58-1.25.1.jolla.armv7hl ........................................[done]
Additional rpm output:
warning: /home/.zypp-cache/packages/jolla/non-oss/armv7hl/jolla-settings-networking-0.5.58-1.25.1.jolla.armv7hl.rpm: Header V3 DSA/SHA1 Signature, key ID f2633ee0: NOKEY
Last edited by Kabouik; 2019-12-22 at 21:44.
| The Following 2 Users Say Thank You to Kabouik For This Useful Post: | ||
|
|
2019-12-22
, 21:55
|
|
Posts: 194 |
Thanked: 1,167 times |
Joined on May 2016
|
#28
|
Originally Posted by Kabouik
No, that's something with package signing, totally unrelated to telephony stack.
There is a "jolla-settings-networking-multisim" in the repository package that I tried reinstalling using "devel-su zypper in --force jolla-settings-networking-multisim", but no change.
I did the same with "jolla-settings-networking".
Both reinstallations gave some warnings:
Can these NOKEY issues be related to our issue?
Could you please fetch the following (better after fresh boot):
Code:
systemctl status ofono journalctl > journalctl.txt /system/bin/logcat > logcat.txt /system/bin/logcat -b radio > logcat-radio.txt
| The Following 4 Users Say Thank You to TheKit For This Useful Post: | ||
|
|
2019-12-22
, 22:05
|
|
Posts: 1,335 |
Thanked: 3,931 times |
Joined on Jul 2010
@ Brittany, France
|
#29
|
Sending you all that on Discord TheKit.
| The Following 4 Users Say Thank You to Kabouik For This Useful Post: | ||
|
|
2019-12-22
, 22:38
|
|
Posts: 194 |
Thanked: 1,167 times |
Joined on May 2016
|
#30
|
It seems we tracked down what happened. SailfishOS devel repository version on OBS got bumped to 3.2.1.20, so nemo:devel:hw:fxtec:t5 got rebuilt against the latest and in this state doing zypper update broke ofono RIL binder transport due to RIL binder plugin and ofono version mismatch.
The easiest fix without reflashing seems to be updating to 3.2.1.20:
The easiest fix without reflashing seems to be updating to 3.2.1.20:
Code:
ssu re 3.2.1.20 version --dup dd if=/boot/hybris-boot.img of=/dev/block/bootdevice/by-name/boot_a # Allow all rotations hack (if needed, homescreen won't work in landscape otherwise) sed -e "s/return allowed/return Orientation.All/" -i /usr/lib/qt5/qml/Sailfish/Silica/Page.qml
 |
| Tags |
| fxtec pro1, sailfish os |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 16:05.
edit... oh, even with stock Android...
--
N9 - My Precious...
"Gods have mercy. Cats don't..." <- Kaotik@iotech