Ofono Logger

Your rating: None Average: 5 (1 vote)

Telephony troubleshooting tool for Sailfish OS. Allows to manipulate log verbosity at runtime, capture and pack the log into a tarball. The tarball can be sent to an ofono specialist for analysis. It can also solve certain connectivity problems (such as disabled mobile data switch). If such a problem is detected, the appropriate menu item shows up in the pulley menu.

Requires Sailfish OS 2.0.4 or newer (or ofono version 1.17+git27 or later).

Source code: https://github.com/monich/harbour-logger

Application versions: 

Version 1.0.11
- Run the application as nemo:privileged (for compatibility upcoming changes in ofono)

Version 1.0.10
- Filter for categories
- Polish translations

Version 1.0.9
- Added Swedish translations
- Copy /etc/hw-release to the tarball
- Added autoEnableLogging and autoResetLogging options
- A few minor settings page fixes

Version 1.0.8
- Save the state of the connmans's cellular technology
- Another tweak for disabled mobile data button

Version 1.0.7
- Don't directly invoke Qt code from glib callbacks to avoid memory leaks
- Make sure that verbose trace is enabled
- Save rilerror file

Version 1.0.6
- Save connection context configuration

Version 1.0.5
- Added "Fix mobile data" menu item
- Collect more ofono information

Version 1.0.4
- Added default email

Version 1.0.3
- Compatibility with Qt 5.6

Version 1.0.2
- Initial upload


HrodLand's picture

Hello everybody, I am new here..... Do we have some documentation shared about this tool? I would like to know about commands and other stuffs related to it.

Thanks in advance.

slava's picture

The best documentation is the source code! There is a link to it in the description.

Alex's picture

Hey @slava,

with latest SFOS v. 2.1.1.x I am experiencing spontaneous device reboots/shutdowns at specific locations and I want to log the ofono output. But I am unable to save the log if the device shuts down spontaneously.

Is there a way to redirect the ofono output to a file via terminal or any other way to save the output? Or do I need to use dbuslog-tools for that purpose?

slava's picture

There are several ways to access the log. First, you can do "Pack and save" from the log view and then "Save to documents" from the next dialog. Alternatively, you can check the /tmp/ofono_*/*/ofono.log file which the app is writing during the capture. The file's contents is a little behind the real time logging due to buffering ("Pack and save" flushes it). Finally, there is dbuslog-client from the dbuslog-tools package. It's essentially a command line version of the logger app (try dbuslog-client -a -f org.ofono)

slava's picture

Keep in mind that dbuslog-client won't automatically reset logging options back to default when you terminate it (unlike the UI app). Leaving full logging on will unnecessarily load the system and reduce the battery life.

TMavica's picture

any abnormal found in log?

slava's picture

Replied via email

TMavica's picture

I have a call bugs ever found in 2.0.2, dont know it still exsist in 2.0.4 or not, I reported to Jolla, rhe bug may exsist
. The bug is sometimes cant be dial or receive call, so which option I need enable mostly in the apps?

slava's picture

Better to enable all logs and and then send the tarball to the email pre-filled in version 1.0.4

TMavica's picture

Got the log and email sent!
 No incoming call show and cant be dial bug

slava's picture

And I have received it.

TMavica's picture

Good. Hope you can found the fault. It just happened again after reboot, afterwards few call, it happen again, but I havent run ofono log this time..

TMavica's picture

can you make a daemon run in background? i dont want to keep the cover in task

slava's picture

Probably not. I am not sure that it makes sense, not to mention that it would mean more or less a complete redesign. Such a daemon already exists - it's called systemd-journald. You can use ofono logger app to configure logging categories, then exit the app and the logs will continue to be collected by journald. Most likely, you would have to tweak /etc/systemd/journald.conf to configure journald to not drop the messages. The default setup is quite conservative, to save the space.

There's also command line dbuslog-client (not installed by default, try pkcon install dbuslog-tools or build it yourself) which can also be used to configure ofono logging, for example this:

dbuslog-client -l org.ofono

lists the ofono log categories and their current state. There are also options to enable/disable individual log categories or all of them and to pipe the log to the standard output. So the command line/demonized solution already sort of exists, the purpose of this app was to make collecting logs easy for a casual user.

TMavica's picture

where can I set font size, i cant find it

slava's picture

Run the Settings app, then select Applications -> Ofono Log

coderus's picture

Please first release 2.0.4 :D

slava's picture

That won't take long. Certainly not as long as 2.0.2