In the latest weeks, on the Xperia X, it's happening that systemd start using high percentages of two CPUs. One of the offending tasks has PID 1. The only solution I found so far is to reboot the phone. The phenomenon might be related to the use of certain Android apps; in particular, the game Hay Day appears to trigger it. I still have to investigate more about this.
![]() | 2 | No.2 Revision |
In the latest weeks, on the Xperia X, it's happening that systemd start using high percentages of two CPUs. One of the offending tasks has PID 1. The only solution I found so far is to reboot the phone. The phenomenon might be related to the use of certain Android apps; in particular, the game Hay Day appears to trigger it. I still have to investigate more about this.
![]() | 3 | No.3 Revision |
In the latest weeks, on the Xperia X, it's happening that systemd start starts using high percentages of two CPUs. One of the offending tasks has PID 1. The only solution I found so far is to reboot the phone. The phenomenon might be related to the use of certain Android apps; in particular, the game Hay Day appears to trigger it. I still have to investigate more about this.
![]() | 4 | No.4 Revision |
In the latest weeks, on the Xperia X, it's happening that systemd starts using high percentages of two CPUs. One of the offending tasks has PID 1. The only solution I found so far is to reboot the phone. The phenomenon might be related to the use of certain Android apps; in particular, the game Hay Day appears to trigger it. I still have to investigate more about this.this.
EDIT: The issue is due to a leftover from OSM Scout Server. See answer for the solution.
![]() | 5 | No.5 Revision |
In the latest weeks, on the Xperia X, it's happening that systemd starts using high percentages of two CPUs. One of the offending tasks has PID 1. The only solution I found so far is to reboot the phone. The phenomenon might be related to the use of certain Android apps; in particular, the game Hay Day appears to trigger it. I still have to investigate more about this.
this.
EDIT: The issue is due to a leftover from OSM Scout Server. See answer for the solution.