Network Mode change is not reflected automatically
**NOTE** Issues relating to the **general OS** can be filed under: * [OS issues](https://source.puri.sm/Librem5/OS-issues) Issues for **core apps** can be filed in their respective existing repositories: * [Libhandy](https://source.puri.sm/Librem5/libhandy/issues) - GTK+ library for developing UIs for applications * [Calls](https://source.puri.sm/Librem5/calls/issues) - phone calling application * [Chatty](https://source.puri.sm/Librem5/chatty/issues) - messaging application * [Phosh](https://source.puri.sm/Librem5/phosh/issues) - shell * [wlroots](https://source.puri.sm/Librem5/wlroots/) - compositor * [Virtboard](https://source.puri.sm/Librem5/virtboard/issues) - onscreen keyboard Use this template for actual problems in other applications. Use the "wishlist" template (still this repo) for requesting applications to be added/ported to the Librem 5.
What application is this relating to?
What problem did you encounter
Network Mode change needs a manual restart of mobile services.
What is the actual behaviour?
Switching from 2G, 3G, 4G (preferred) to 2G, 3G (preferred) or reverse don't change the mode without manual restart of mobile service.
What is the expected behaviour?
Immediate change like android.
How to reproduce
From Settings -> Mobile -> Network Mode.
Please provide steps to reproduce the issue. If it's a graphical issue please attach screenshots.
Which version did you encounter the bug in?
I compiled it myself. If you compiled the application from source please provide the git revision via e.g. by running
git log -1 --pretty=onelineand pasting the output below.
[x ] I used a precompiled Debian package. Please paste the output of
dpkg -s <package name>below.
I used a prebuilt flatpak. Please paste the output of
flatpak info <application-id>below.
I used something else (please elaborate).
Application version (output of `dpkg -l | grep <application name>`): Kernel version (output of `uname -a`):
What hardware are you running on?
amd64 qemu image
Librem5 devkit (please list what build number you are running)
other (please elaborte)
Please provide relevant logs. Since the relevant log files can vary depending on the application, here are some tips for gathering helpful logs:
- If you compiled the application yourself, the build log would be helpful.
- If you used a prebuilt debian package, you can provide the logs on an
journalctl -b 0 | grep "<application-name>".