Hexo

Prerequisites

• MIUI 14 firmware or MIUI 14 ROM
• Back up all apps, images, videos, contacts, etc. to cloud or external storage
• Latest platform-tools
• Unlocked bootloader and Arrow Recovery
  Read more »

Getting to the Point: What is GKI

GKI stands for Generic Kernel Image, also known as Android Common Kernels.

What’s Its Purpose?

The purpose of GKI is to address Android fragmentation. Manufacturers often modify the kernel source code and add device drivers to provide support for System-on-Chips (SoCs) and peripheral devices. However, these modifications can be extensive, leading to a situation where up to 50% of the code running on a device is out-of-tree code (not from the upstream Linux and AOSP common kernels).
A device kernel consists of the following parts:

Arch install Redis

1

sudo pacman -Syu # update system

1

sudo pacman -S redis # install redis

config Redis Service

Dot not start redis service after install, we need to config redis service first.

redis default config file is located at /etc/redis/redis.conf,but we dot not use this file, we use /etc/redis/minimal-redis.conf instead.

file demo /etc/redis/minimal-redis.conf:

the file is a minimal configuration file for redis, we can use this file to start redis service.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

# Redis minimal configuration file

# Specify the Redis server port
port 6379

# Specify the directory for storing data files
dir /var/lib/redis

# Specify the log file (empty string for standard output)
logfile ""

# Bind to localhost to accept connections only from the local machine
bind 127.0.0.1

# Set the database number (default is 16)
databases 16

# Disable protected mode to allow connections only from localhost
protected-mode yes

Arch Redis start service file is located at /usr/lib/systemd/system/redis.service

the config file use Chinese locale, so we need to add locale config to the service file.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

[Unit]
Description=Advanced key-value store
After=network.target

[Service]
Environment="LANG=zh_CN.UTF-8"  # Fix Failed to configure LOCALE for invalid locale name
Environment="LC_ALL=zh_CN.UTF-8" # Fix Failed to configure LOCALE for invalid locale name
Type=notify
User=redis
Group=redis
ExecStart=/usr/bin/redis-server /etc/redis/minimal-redis.conf --supervised systemd # Change the configuration file to start Redis with our set minimal configuration file.
TimeoutStartSec=60
TimeoutStopSec=60
CapabilityBoundingSet=
PrivateTmp=true
PrivateDevices=true
ProtectSystem=full
ProtectHome=true
NoNewPrivileges=true
RuntimeDirectory=redis
RuntimeDirectoryMode=755
LimitNOFILE=10032

[Install]
WantedBy=multi-user.target

Set Redis service privilege (maybe not necessary)

1
2
3

sudo mkdir -p /var/run/redis
sudo chown redis:redis /var/run/redis
sudo chmod 755 /var/run/redis

Start Redis service

1

sudo systemctl start redis # start redis service

1

sudo systemctl enable redis # enable redis service

Check Redis service status

1

sudo systemctl status redis # active (running)

Test Redis service connection

1

redis-cli ping # PONG

Essay

Essay

After installing Arch, I found that VMware’s 3D acceleration was not enabled.

However, in Settings - Hardware - Display - 3D Graphics - Accelerate 3D Graphics, it was already checked.

Then I came across this Enable 3D HW acceleration on VMWare Workstation 10 on Ubuntu 14.04 solution.

It just required adding a line of configuration.

Open

1

vim ~/.vmware/preferences

Add

1

mks.gl.allowBlacklistedDrivers = "TRUE"

But what truly amazed me is that this answer is already nine years old.

From Ubuntu 14.04 LTS - vmware-workstation-10 to the current Ubuntu 22.04 LTS - vmware-workstation-17, it still works.

All is well in 2024 , Happy New year

This is My Buyvm of Roost Bissen

1
2
3
4
5
6
7
8
9
10
11
12
13

    Speedtest by Ookla

        Server: CONSULTIC - Bettembourg (id: 57169)
            ISP: FranTech Solutions
Idle Latency:     0.97 ms   (jitter: 0.03ms, low: 0.94ms, high: 1.03ms)
     Download:   979.13 Mbps (data used: 440.7 MB)
                        1.08 ms   (jitter: 0.10ms, low: 0.89ms, high: 1.68ms)
        Upload:  1019.50 Mbps (data used: 1.7 GB)
                        1.11 ms   (jitter: 0.19ms, low: 0.94ms, high: 4.38ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/ecbbf771-94af-4883-8190-05e8fbfffe4c

Build fastboot Rom shell

1

mka updatepackage # this will all threads build fastboot rom

Build recovery Rom shell

1

mka bacon -j$(nproc --all) # -jx is number of thread   ,$(nproc --all) is all thread

flash rom

if fastboot rom

1
2

fastboot -w # clean data and cache
fastboot update <rom.zip> # flash

if recovery rom

1
2

fastboot reboot recovery # reboot to recovery
adb sideload <rom.zip> # sideload rom

Prerequisites

Before you begin, make sure you have the following:

• A computer with Fastboot installed.
• A compatible ROM file for your device.
• USB debugging enabled on your Android device.
• A USB cable to connect your device to the computer.

Step 1: Boot your Device into Fastboot Mode

1. Power off your Android device.
2. Press and hold the Volume Down button and the Power button simultaneously.
3. Keep holding the buttons until you see the Fastboot mode screen.

Step 2: Connect your Device to the Computer

1. Use a USB cable to connect your Android device to the computer.
2. On your computer, open a command prompt or terminal window.

Step 3: Verify Device Connection

1. In the command prompt or terminal window, type the following command and press Enter:

1

fastboot devices

Seeking a Balance: Openness and Security, Freedom and Privacy

We aim for open system and kernel source code while also being committed to digital forensics security. We demand a smooth system but also wish our privacy and freedom to be protected. Admittedly, this creates a contradiction.

Pixel: A Strong Contender