Homelab, Linux, JS & ABAP (~˘▾˘)~
 

Month: May 2025

Android

[Android] Installing LineageOS on a Motorola Moto G100

 , , , , , , ,

Just installed LineageOS on a used Moto G100. Following are a few notes I made while working through the excellent installation guide.

Two settings must be enabled in the Developer options on your device before you start:

  • Developer options → Enable USB-Debugging
  • Developer options → Enable OEM unlocking

Otherwise, you will encounter the same error as I did when unlocking the bootloader.

adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
fastboot oem unlock UNIQUE_KEY

After entering the UNIQUE_KEY, select “Unlock Bootloader” on your phone with the volume down button and confirm with the power button.

The next point that confused me for a second was this:

But you just have to use the volume buttons and select recovery on the smartphone screen from the menu you’re in. I just didn’t realize it was a menu at first…

All in all, everything worked without any problems and took maybe 30 minutes in total.

BTP, SAP

[BTP] Change S-User Password

 , , , , , , , ,

When testing API Endpoints of applications running on BTP, it can be necessary to authenticate using the right S-User credentials. In such a scenario, the Universal ID password will not help.

Universal ID password can be changed via https://accounts.sap.com (will forward to the Standard SAP ID Service)

A specific S-User password can be changed via https://account.sap.com (will forward to Manage my Account, where you see the different S-User and P-User, linked to your Universal ID)

Home Assistant

[Home Assistant] HASS VM High CPU Usage on Proxmox

 , , , , ,

Since my Proxmox Server is also my HTPC in my living room, I noticed that suddenly the CPU fan become very noisy. When checking all LXCs and VMs, it turned out that the Home Assistant VW was the cause.

When checking the Supervisor logs, I saw that there was a docker container that got terminated. This semmed to match the CPU usage pattern I checked before.

To inspect the docker container via the Advanced SSH & Web Terminal add-on, you must disable the Protection mode first.

After that, simply run docker stats.

If there are no suspicious values, simply open some of the add-ons in another window and check how the values behave. In the above screenshot, I simply opened the VSCode editor, and you can immediately see an extreme high CPU usage. After a quick search, I found open issues that seem to be related to this issue:

As a workaround, a user had the idea to simply restart VSCode via an automation, when its CPU rises above a threshold. To do this, you have to enable some CPU & Memory sensors of the VSCode add-on. Search for your Home Assistant Supervisor Integration.

Select the Studio Code Server add-on.

And enable the sensors.

Now you can set up a simple automation like the following.

alias: Restart VSCode when cpu/memory too high
description: ""
triggers:
  - trigger: numeric_state
    entity_id:
      - sensor.studio_code_server_cpu_percent
    for:
      hours: 0
      minutes: 5
      seconds: 0
    above: 50
  - trigger: numeric_state
    entity_id:
      - sensor.studio_code_server_memory_percent
    above: 30
    for:
      hours: 0
      minutes: 5
      seconds: 0
conditions: []
actions:
  - action: hassio.addon_restart
    metadata: {}
    data:
      addon: a0d7b954_vscode
mode: single

Since I have the automation setup, the Proxmox CPU fan is quiet again and the VM behaves normal.