asked 2014-07-14 22:57:58 +0300
After the 1.0.8.19 update, the airplane icon is displayed on the homescreen instead of the network signal icon. Also, the airplane mode is "not" activated...
Any ideas ?
answered 2015-01-21 12:06:13 +0300
Now the root cause of the issue is unknown because it is rare and we did not observe it yet ourselves, also journal provided by @ced117 did not help, there is no useful information there. If somebody who has this issue is living near Helsinki and can come to the Jolla office (Ruoholahti) we can try to investigate the issue and fix it. Otherwise the only way I see now to investigate the issue is to wait until we will create remote assistance application.
Update #1: So, according to comments, if some application or component leaves mce cellular flag state as offline it results in "Airplane mode" displayed. One who observes this issue, has "Developer mode" on and able to execute commands in Terminal can try to execute there mcetool --enable-radio=cellular and check does it solve the issue,
And we will just change responsible component to take the radio state from connman instead of mce. Hopefully it'll help.
My steps to reproduce, if it helps:
mcetool --disable-radio=cellularmcetool return that
Cellular: disabledIf set flight-mode from Settings,then everything works as it should. I have latetst Sailfish 1.1.1.27
zaharov.andrei ( 2015-01-21 12:23:47 +0300 )editThe radio control in mce is inherited from Nokia devices like N9 & N900 - which had daemons listening to notifications from mce and turning appropriate radios on/off.
The cellular / networking daemons used in Jolla phone do not utilize these signals, so nothing happens if they are toggled on/off via mcetool.
The only exception to this - at least for now - is the "master" radio toggle, which mirrors (reverse of) OfflineMode property from connman, i.e.
Also the reverse is true: Toggling the airplane mode from settings changes what mcetool reports for the master radio state.
spiiroin ( 2015-01-21 13:49:33 +0300 )editanswered 2014-07-19 10:03:04 +0300
I did a factory reset, so far it seems to work as usual.
@NuklearFart Had this issue and found a way to solve it (aside from doing a factory reset...)
Open a terminal and do this:
devel-su
pkcon install mce-tools
mcetool --enable-radio=cellular
And, voila... ! :-)
I understand. I still have the airplane. Sometimes I can't even switch to flight mode or leave the flight mode, I have to reboot. Sometimes ambiances are mixed (up to three): the glowing color of one ambiance, the main background image of another and the covers' background of a third ! Changing ambiance often fails or it mixes them. It seems that the UI is messed up. Perhaps a problem of disk space, I'll try a btrfs balance.
smartiz ( 2014-09-22 23:42:22 +0300 )editAsked: 2014-07-14 22:57:58 +0300
Seen: 988 times
Last updated: Dec 01 '15
Oddly enough, I have an always present bluetooth icon, even with bluetooth off since the update.
paulvt ( 2014-07-15 00:04:06 +0300 )editI have also airplane mode icon there, stays there after reboots and enabling and disablíng the mode.
stimpson ( 2014-07-15 01:05:28 +0300 )editUpdated to the new version yesterday & I did not have the problem until today morning. After a reboot, the bluetooth icon shows up on the homescreen when it is deactivated.
chsailor ( 2014-07-15 09:03:23 +0300 )editThe flight-mode-icon-always-displayed thing happened to me last week on 1.0.7.16. I was hoping that yesterday's 1.0.8.19 update would solve it, but it hasn't. https://together.jolla.com/question/50296/flight-mode-icon-always-displayed/
DrCheeseCake ( 2014-07-15 12:07:17 +0300 )editI have had the flight mode icon on the screen since one of the first versions of Sailfish. Every time I hope that update will fix it but no luck. Seemed too minor to report a bug but I would still be glad to get rid of it.
Lauri Laanemets ( 2014-07-15 15:47:15 +0300 )editCould you provide some logs for the airplane icon issue? It is quite hard to reproduce and logs will help a lot identifying the problem
jiit ( 2014-07-16 15:06:21 +0300 )editWhich logs exactly?
Lauri Laanemets ( 2014-07-16 15:08:59 +0300 )editIf your device has Developer mode enabled (Settings > Developer Mode) by the time you observed this issue, you can extract a journal log from your device. You can upload it and share the link here, if possible
jiit ( 2014-07-16 15:29:38 +0300 )edit@jiit which log file are you talking about ? Or which command ?
ced117 ( 2014-07-16 19:30:48 +0300 )edit@ced117 Do you have "Developer mode" switched on?
dez ( 2014-07-17 10:35:56 +0300 )edit@dez yes, "Developer mode" is enabled.
ced117 ( 2014-07-17 18:55:55 +0300 )edit@ced117 So, you can go to the terminal or ssh to the device, login as root (devel-su) and execute:
dez ( 2014-07-18 10:08:24 +0300 )editjournalctl | gzip > /home/nemo/journal.gzIf you send this journal file (/home/nemo/journal.gz) to me (you can check is there any sensitive information inside of it by just executingjournalctlas root) as also the resulting file of the commandrpm -qa > /home/nemo/packages.gzit can help to find the root cause. You can send it by contacting care@jolla.com referencing the issue and me@dez Message sent!
ced117 ( 2014-07-18 15:55:28 +0300 )editI have the same issue. Something new ?
smartiz ( 2014-09-07 19:33:19 +0300 )editI also have the same issue. How to fix?
Jones14 ( 2014-12-30 20:05:27 +0300 )edit