add blog posts
This commit is contained in:
parent
16a73319ef
commit
0e397c444d
42 changed files with 2235 additions and 237 deletions
130
src/content/blog/crdt-conflict-free-replicated-data-types.md
Normal file
130
src/content/blog/crdt-conflict-free-replicated-data-types.md
Normal file
|
|
@ -0,0 +1,130 @@
|
|||
---
|
||||
title: 'CRDT - Conflict Free Replicated Data Types'
|
||||
description: 'A brief intro to Conflict Free Replicated Data Types'
|
||||
date: 2025-02-24T09:58:08+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- programming
|
||||
- dart
|
||||
- data
|
||||
---
|
||||
|
||||
# Background
|
||||
When searching techniques for syncing data between peers, I stumbled upon CRDT (Conflict-free Replicated Data Types). It's basically a algorithm for syncing for distributed systems. CRDT ensures all data changes between peer will be synced with correct order and no data loss.
|
||||
|
||||
Since I working with Dart (for Flutter project), I use a [CRDT library for Dart](https://github.com/cachapa/crdt). This library implements core concept of CRDT and it's pretty basic. Here some types of CRDT that often used:
|
||||
|
||||
1. **G-Counter (Grow-only Counter)**: A counter that can only be incremented.
|
||||
2. **P-Counter (Decrement Counter)**: A counter that can be both incremented and decremented.
|
||||
3. **G-Set (Grow-only Set)**: A set that only allows elements to be added.
|
||||
4. **2P-Set (Two-Phase Set)**: A set that allows elements to be added and removed, maintaining two sets (one for additions and one for removals).
|
||||
5. **OR-Set (Observed Remove Set)**: A set that allows elements to be added and removed, using unique identifiers to track additions and removals.
|
||||
6. **LWW-Register (Last Write Wins Register)**: A register that stores the last written value, using a timestamp to determine the most recent update.
|
||||
7. **MV-Register (Multi-Value Register)**: A register that stores all values that have been written, using unique identifiers to track writes.
|
||||
# How it works -- basic version
|
||||
Main components:
|
||||
- HLC (Hardware Logical Clock). Combines _wall clock/local time_, a counter that increments, and an optional _node ID_ for uniqueness sake.
|
||||
- The data itself (usually contains a key, value, and the HLC object).
|
||||
## **Scenario: Two Devices Synchronizing Data**
|
||||
We have two devices, **Device A** and **Device B**, which both maintain their own local datasets. Each device can modify data independently. When they synchronize, their CRDT implementations will merge their changes and resolve conflicts.
|
||||
## Initial State
|
||||
- Both devices start with the same data:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice | false | HLC: A1 |
|
||||
| 2 | Bob | false | HLC: A2 |
|
||||
|
||||
- Device A's last modified HLC: `A2`.
|
||||
- Device B's last modified HLC: `A2`.
|
||||
|
||||
---
|
||||
## Changes Made on Each Device
|
||||
1. **Device A deletes Bob's record (key 2):**
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 2 | null | true | HLC: A3 |
|
||||
|
||||
2. **Device B updates Alice's name to Alice Smith (key 1):**
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice Smith | false | HLC: B3 |
|
||||
|
||||
---
|
||||
## Synchronization and Merge
|
||||
- Device A sends its **changeset** to Device B:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 2 | null | true | HLC: A3 |
|
||||
|
||||
- Device B sends its **changeset** to Device A:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice Smith | false | HLC: B3 |
|
||||
|
||||
---
|
||||
## Step-by-Step Conflict Resolution
|
||||
|
||||
The `merge` method processes these changes:
|
||||
1. **Validate Changeset**:
|
||||
Each incoming record is validated to ensure it matches the expected schema and contains valid HLC timestamps.
|
||||
|
||||
2. **Compare Records for Key 1 (`Alice`)**:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice | false | HLC: A1 |
|
||||
|
||||
Incoming record from Device B:
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice Smith | false | HLC: B3 |
|
||||
|
||||
**Conflict Resolution Rule**: The record with the higher `Last Modified` HLC wins. HLC `B3 > A1,` so Device A updates Alice's record to:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice Smith | false | HLC: B3 |
|
||||
|
||||
3. **Compare Records for Key 2 (`Bob`)**:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 2 | Bob | false | HLC: A2 |
|
||||
|
||||
Incoming record from Device A:
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 2 | null | true | HLC: A3 |
|
||||
|
||||
**Conflict Resolution Rule**: The record with the higher `Last Modified` HLC wins. HLC `A3 > A2`, so Device B updates Bob's record to:
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 2 | null | true | HLC: A3 |
|
||||
|
||||
4. **Propagate Changes**:
|
||||
Both devices now have identical datasets after merging.
|
||||
|
||||
---
|
||||
## Final Merged Dataset on Both Devices
|
||||
|
||||
| Key | Value | isDeleted | Last Modified |
|
||||
| --- | ----- | --------- | ------------- |
|
||||
| 1 | Alice Smith | false | HLC: B3 |
|
||||
| 2 | null | true | HLC: A3 |
|
||||
|
||||
---
|
||||
## Summary of Conflict Resolution Rules
|
||||
|
||||
1. **Higher HLC Wins**
|
||||
Records with higher HLCs (later timestamps) overwrite those with lower HLCs.
|
||||
2. **Soft Deletes**
|
||||
A `null` value with `isDeleted: true` is treated as a soft delete. It wins if its HLC is higher.
|
||||
3. **Deterministic Behavior**
|
||||
All nodes independently apply the same conflict resolution logic, ensuring eventual consistency.
|
||||
|
||||
54
src/content/blog/fix-adb-unsufficient-permission-linux.md
Normal file
54
src/content/blog/fix-adb-unsufficient-permission-linux.md
Normal file
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
title: 'Fix ADB Insufficient Permission'
|
||||
description: 'udev rules for fixing ADB Insufficient permission in Linux'
|
||||
date: 2025-02-24T11:29:30+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- android
|
||||
- adb
|
||||
- linux
|
||||
---
|
||||
|
||||
# Why need this?
|
||||
Connecting an Android device to a Linux computer could has problem with permission. Listing devices with `adb devices` might show `unauthorized` status or `insufficient permission` error message.
|
||||
|
||||
```bash
|
||||
$ adb devices
|
||||
|
||||
List of devices attached
|
||||
15241JEC211677 device
|
||||
RR2M9002AHY unauthorized
|
||||
```
|
||||
|
||||
This happens because by default, in Linux, when you connect an Android device via USB, the system assigns it to the `root` user and a restrictive permission mode (often 0600), meaning that regular users cannot access it.
|
||||
|
||||
# How to fix
|
||||
|
||||
1. Check `vendor id` and `device id` from connected Android device with `lsusb`.
|
||||
|
||||
```bash
|
||||
$ lsusb
|
||||
|
||||
...some other devices
|
||||
Bus 001 Device 005: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device
|
||||
```
|
||||
|
||||
`18d1` is *vendor id* and `4ee7` is the *product id*.
|
||||
|
||||
2. Create an `udev` rule for this device, I create mine in `/etc/udev/rules.d/51-android.rules`.
|
||||
|
||||
```bash
|
||||
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="4ee7", MODE="0666", GROUP="plugdev", SYMLINK+="google_pixel_4a_%n"
|
||||
```
|
||||
|
||||
- `SUBSYSTEM=="usb"` ensures the rule applies only to USB devices.
|
||||
- `ATTRS{idVendor}=="18d1" and ATTRS{idProduct}=="4ee7"` match the Google Pixel USB devices by their vendor and product IDs.
|
||||
- `MODE="0666"` sets the device's permission mode to 0666, meaning read/write access for all users.
|
||||
- `GROUP="plugdev"` assigns the device to the plugdev group, which allows users in that group to access it.
|
||||
- `SYMLINK+="google_pixel_4a_%n"` creates a symlink (shortcut) under /dev/ with a readable name for easier identification.
|
||||
|
||||
3. Reconnect the device to make sure the rule is correct. If not, try to reload `udev` rules and restart it.
|
||||
|
||||
```bash
|
||||
$ sudo udevadm control --reload-rules
|
||||
```
|
||||
|
|
@ -0,0 +1,91 @@
|
|||
---
|
||||
title: 'Fix Infinix Air Pro+ Quad Speakers in Linux'
|
||||
description: 'A fix for Infinix Air Pro+ -- only 2 of 4 speakers working in Linux'
|
||||
date: 2025-02-23T23:27:49+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- laptop
|
||||
- infinix
|
||||
- tweak
|
||||
- linux
|
||||
---
|
||||
|
||||
I installed Linux ([EndeavourOS](https://endeavouros.com/)) in my Infinix Air Pro+ last week and noticed that the sound coming from the speakers was bad. This laptops has 4 speakers, hence only 2 of them are working. This is how I fix this issue.
|
||||
|
||||
# Check ALSA for Hidden Speakers
|
||||
|
||||
```bash
|
||||
$ cat /proc/asound/card0/codec* | grep -i "node"
|
||||
|
||||
State of AFG node 0x01:
|
||||
Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
|
||||
Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
|
||||
Node 0x04 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x05 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x06 [Audio Output] wcaps 0x611: Stereo Digital
|
||||
Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In
|
||||
Node 0x09 [Audio Input] wcaps 0x10051b: Stereo Amp-In
|
||||
Node 0x0a [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
|
||||
Node 0x0c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
|
||||
Node 0x0d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
|
||||
Node 0x0e [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x0f [Audio Mixer] wcaps 0x20010a: Mono Amp-In
|
||||
Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
|
||||
Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
|
||||
Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
|
||||
Node 0x16 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x17 [Pin Complex] wcaps 0x40050c: Mono Amp-Out
|
||||
Node 0x18 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
|
||||
Node 0x19 [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
|
||||
Node 0x1a [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
|
||||
Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
|
||||
Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x1d [Pin Complex] wcaps 0x400400: Mono
|
||||
Node 0x1e [Pin Complex] wcaps 0x400781: Stereo Digital
|
||||
Node 0x1f [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono
|
||||
Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono
|
||||
Node 0x22 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
|
||||
Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
|
||||
State of AFG node 0x01:
|
||||
Node 0x03 [Audio Output] wcaps 0x6611: 8-Channels Digital
|
||||
Node 0x04 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x05 [Audio Output] wcaps 0x6611: 8-Channels Digital
|
||||
Node 0x06 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x07 [Audio Output] wcaps 0x6611: 8-Channels Digital
|
||||
Node 0x08 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x09 [Audio Output] wcaps 0x6611: 8-Channels Digital
|
||||
Node 0x0a [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x0b [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x0c [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x0d [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x0e [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
Node 0x0f [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
|
||||
```
|
||||
|
||||
Looking at that output, it seems that this laptop has several nodes that could be an audio output. They are nodes with `Stereo Amp-In Amp-Out` in it's description. Filtering the result with that, I got:
|
||||
|
||||
- 0x14 - Stereo Amp-Out (I suspect this is the front speakers that are working)
|
||||
- 0x15 - Stereo Amp-Out (likely another speakers?)
|
||||
- 0x18, 0x19, 0x1a, 0x1b - Stereo Amp-In Amp-Out (might be extra speaker outputs)
|
||||
|
||||
# Enable Additional Speakers with `hdajackretask`
|
||||
|
||||
`hdajackretask` is a tool from ALSA that allow us to remap/retask those nodes/jack into different purposes.
|
||||
|
||||
```bash
|
||||
$ sudo pacman -S alsa-tools
|
||||
$ sudo hdajackretask
|
||||
```
|
||||
|
||||
After opening the tool, check the `Show unconnected pins` and there will be list of nodes that can be retasked.
|
||||
I need to experiment with this remapping. After trials and errors, I found that `0x1a` and `0x1b` is the responsible nodes for my extra speakers. Overriding them and changing their role as `Internal Speaker` solve my issue.
|
||||
|
||||
|
||||
|
||||
Now all my speakers is working! I hope this will help someone in the future.
|
||||
180
src/content/blog/fix-infinix-air-pro-plus-screen-color.md
Normal file
180
src/content/blog/fix-infinix-air-pro-plus-screen-color.md
Normal file
|
|
@ -0,0 +1,180 @@
|
|||
---
|
||||
title: 'Fix Infinix Air Pro+ Screen Color'
|
||||
description: 'Fixing Infinix Air Pro+ washed out screen color in Windows and Linux'
|
||||
date: 2025-02-21T18:09:54+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- laptop
|
||||
- infinix
|
||||
- tweak
|
||||
- script
|
||||
---
|
||||
|
||||
I have Infinix Air Pro+ and I use it for my work. I can say it is a good laptop coding mainly because it has 2.5k OLED 16:10 screen. But I found a problem with its screen color. When the screen brightness is below about 50% and the screen turned off (to save power, not necessarily going system sleep/suspend) and turns back on, the color looks washed out.
|
||||
|
||||
First time I noticed this issue is because I was using a pitch black wallpaper image (so I can flex my OLED display). After my screen turns back on, my wallpaper's black color becomes grainy, washed out, as its doesn't have pitch black color anymore. Then I noticed, the color will be fixed after I crank the brightness to above 50%. Turning the brightness down again after this still gives me correct black level.
|
||||
|
||||
So, I was wondering if I create a script that will turn the brightness to above 50% and restore it to where it was every time my screen is waking up from a sleep. With a help from Google and ChatGPT, I create these scripts as a workaround for this annoying issue.
|
||||
|
||||
# Windows
|
||||
Before continuing, I'm sorry I can't give any screenshot for this Windows section because I already switched to Linux, but I hope I can write it clearly.
|
||||
|
||||
## Get screen wake up event
|
||||
I need to listen to an event that tells me "Hey, the screen is turning on". Fortunately, Windows has [Event Viewer](https://learn.microsoft.com/en-us/shows/inside/event-viewer) that I can use for this. I found that an event from *Kernel-Power* with event ID *507* is the correct event that means the screen in turned back on.
|
||||
|
||||
## Script
|
||||
Next thing to do is create the script to control screen brightness. After trial and error, I found [NirCmd](https://www.nirsoft.net/utils/nircmd.html) can help me to change my screen brightness. Then I create this Powershell script.
|
||||
|
||||
```powershell
|
||||
# Infinix Air Pro Plus suffers from washed out colors
|
||||
# after the display goes off and back on if the brightness is below 50%.
|
||||
# This script will increase the brightness to 60% when initial brightness
|
||||
# is below 50% else it will increase 10% from current brightness and turn
|
||||
# back to initial brightness value.
|
||||
|
||||
# Path to NirCmd executable
|
||||
$nircmd = "C:\nircmd-x64\nircmd.exe"
|
||||
|
||||
# Function to temporarily adjust brightness
|
||||
function Adjust-Brightness {
|
||||
param (
|
||||
[int]$InitialBrightness,
|
||||
[int]$TargetBrightness
|
||||
)
|
||||
|
||||
# Set brightness to target
|
||||
& $nircmd "setbrightness" $TargetBrightness
|
||||
Start-Sleep -Seconds 2
|
||||
|
||||
# Restore to initial brightness
|
||||
& $nircmd "setbrightness" $InitialBrightness
|
||||
}
|
||||
|
||||
# Dummy current brightness (replace this with actual detection logic if available)
|
||||
$currentBrightness = (Get-CimInstance -Namespace root/WMI -ClassName WmiMonitorBrightness).CurrentBrightness
|
||||
|
||||
if ($currentBrightness -lt 50) {
|
||||
# If brightness is below 50%, temporarily set to 60
|
||||
Adjust-Brightness -InitialBrightness $currentBrightness -TargetBrightness 60
|
||||
} else {
|
||||
# Otherwise, increase brightness by 10%
|
||||
$newBrightness = [Math]::Min($currentBrightness + 10, 100)
|
||||
Adjust-Brightness -InitialBrightness $currentBrightness -TargetBrightness $newBrightness
|
||||
}
|
||||
```
|
||||
|
||||
## Make a schedule
|
||||
I use Windows' [Task Scheduler](https://www.windowscentral.com/how-create-automated-tasks-windows-11) to run the script each time *Kernel-Power* with event ID *507* occurs. I can't show the step-by-step guide because I'm on Linux now, but I have a backup file for this task. All you need is just to import [this task](/misc/Restore%20OLED%20Colors.xml) in Task Scheduler.
|
||||
|
||||
> Note: You have to change the command it executes to where you save the Powershell script. Also change the author into `YOUR_PC_NAME\YOUR_USERNAME`.
|
||||
|
||||
# Linux
|
||||
I'm using [EndeavourOS](https://endeavouros.com/) which use `systemd`. So this guide is applicable to `systemd` init system only. If your linux use something else, you need to adjust it with your init system.
|
||||
|
||||
## Get screen wake up event
|
||||
I already tried several ways to listen the screen wake up events. But I can't find any using `acpi` and `udev`. So I tried different approach. I check `dpms` property from screen device in `/sys/class/drm/card1-eDP-1/dpms`. It has `On` and `Off` value that I can use for triggering a script to fix the color.
|
||||
|
||||
## Script
|
||||
I have 2 scripts for this approach. One for checking `/sys/class/drm/card1-eDP-1/dpms` value and another one for fixing the color.
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
# monitor /sys/class/drm/card1-eDP-1/dpms value
|
||||
# place it to /usr/local/bin/monitor_screen_power.sh
|
||||
|
||||
prev_state=""
|
||||
|
||||
while true; do
|
||||
state=$(cat /sys/class/drm/card1-eDP-1/dpms)
|
||||
|
||||
if [[ "$state" != "$prev_state" && "$state" == "On" ]]; then
|
||||
echo "Screen turned on! Running script..."
|
||||
/usr/local/bin/brightness_fix.sh
|
||||
fi
|
||||
|
||||
prev_state=$state
|
||||
sleep 1 # Adjust polling interval as needed
|
||||
done
|
||||
```
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
# adjust the brightness
|
||||
# place it to /usr/local/bin/brightness_fix.sh
|
||||
|
||||
# Path to brightness control (may vary based on hardware, check /sys/class/backlight/)
|
||||
BRIGHTNESS_PATH="/sys/class/backlight/intel_backlight/brightness"
|
||||
MAX_BRIGHTNESS_PATH="/sys/class/backlight/intel_backlight/max_brightness"
|
||||
|
||||
# Read current brightness
|
||||
CURRENT_BRIGHTNESS=$(cat "$BRIGHTNESS_PATH")
|
||||
MAX_BRIGHTNESS=$(cat "$MAX_BRIGHTNESS_PATH")
|
||||
|
||||
# Convert brightness levels to percentage
|
||||
CURRENT_PERCENT=$(( CURRENT_BRIGHTNESS * 100 / MAX_BRIGHTNESS ))
|
||||
|
||||
# Function to set brightness based on percentage
|
||||
set_brightness() {
|
||||
local TARGET_PERCENT=$1
|
||||
local TARGET_BRIGHTNESS=$(( TARGET_PERCENT * MAX_BRIGHTNESS / 100 ))
|
||||
echo $TARGET_BRIGHTNESS | sudo tee "$BRIGHTNESS_PATH" > /dev/null
|
||||
}
|
||||
|
||||
# Adjust brightness logic
|
||||
if [ "$CURRENT_PERCENT" -lt 50 ]; then
|
||||
set_brightness 60
|
||||
sleep 0.5
|
||||
set_brightness "$CURRENT_PERCENT"
|
||||
else
|
||||
TARGET_PERCENT=$(( CURRENT_PERCENT + 10 ))
|
||||
if [ "$TARGET_PERCENT" -gt 100 ]; then
|
||||
TARGET_PERCENT=100
|
||||
fi
|
||||
set_brightness "$TARGET_PERCENT"
|
||||
sleep 0.5
|
||||
set_brightness "$CURRENT_PERCENT"
|
||||
fi
|
||||
```
|
||||
|
||||
## Make a systemd service
|
||||
Make a `systemd` service in `/etc/systemd/system/brightness-fix.service` to run the first script.
|
||||
|
||||
```plaintext
|
||||
[Unit]
|
||||
Description=Fix screen brightness on wake
|
||||
After=multi-user.target
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/local/bin/monitor_screen_power.sh
|
||||
Restart=always
|
||||
User=dhemas
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
```
|
||||
|
||||
and another one to run `brightness-fix.sh` after waking up from suspend/sleep, I put it in `/etc/systemd/system/brightness-fix-wakeup.service`.
|
||||
|
||||
```plaintext
|
||||
[Unit]
|
||||
Description=Fix screen brightness after wakeup
|
||||
After=suspend.target
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
ExecStart=/usr/local/bin/brightness_fix.sh
|
||||
|
||||
[Install]
|
||||
WantedBy=suspend.target
|
||||
```
|
||||
|
||||
Then register, enable, and start it.
|
||||
|
||||
```bash
|
||||
sudo systemctl daemon-reload
|
||||
sudo systemctl enable brightness-fix.service
|
||||
sudo systemctl enable brightness-fix-wakeup.service
|
||||
sudo systemctl start brightness-fix.service
|
||||
```
|
||||
|
||||
One more thing, you can add also `/usr/local/bin/brightness_fix.sh` to autostart (I'm using KDE) so it will run each time you login.
|
||||
25
src/content/blog/flutter-android-emulator-not-showing.md
Normal file
25
src/content/blog/flutter-android-emulator-not-showing.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
title: 'Android Devices Not Showing on Flutter Project'
|
||||
description: "A fix for new Flutter project that doesn't have Android devices showing up"
|
||||
date: 2025-02-22T09:21:22+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- programming
|
||||
- flutter
|
||||
- android
|
||||
- emulator
|
||||
---
|
||||
|
||||
When I create a new Flutter project targeting Android device, I can't choose which Android device to run it. Either it a real connected devices or AVDs, even the devices is available and listed in `Device Manager` tab.
|
||||
|
||||
|
||||
|
||||
All I need to do is open `File > Project Structure...` or `Ctrl + Alt + Shift + S`.
|
||||
|
||||
|
||||
|
||||
As you can see, I have no Android SDK selected for my Flutter project. So, go ahead and select one of SDK listed there and click `OK`. That's it! Now you can see all the devices available to run my Flutter project.
|
||||
|
||||
|
||||
|
||||
Hope this can help someone who has similar issues with Flutter project and Android devices.
|
||||
1216
src/content/blog/flutter-clean-architecture.md
Normal file
1216
src/content/blog/flutter-clean-architecture.md
Normal file
File diff suppressed because it is too large
Load diff
46
src/content/blog/kuwot-flutter-daily-quote-app.md
Normal file
46
src/content/blog/kuwot-flutter-daily-quote-app.md
Normal file
|
|
@ -0,0 +1,46 @@
|
|||
---
|
||||
title: 'Kuwot'
|
||||
description: 'Flutter Daily Quote App'
|
||||
date: 2025-02-20T15:26:04+07:00
|
||||
draft: true
|
||||
tags:
|
||||
- programming
|
||||
- flutter
|
||||
---
|
||||
|
||||
I made [Kuwot](https://play.google.com/store/apps/details?id=com.dhemasnurjaya.kuwot) last year in my spare time. I want to share it, you can use it as an inspiration, practice app, or something else is up to you since I open-sourced the code (links below).
|
||||
|
||||
# Introduction
|
||||
The Flutter app itself was built using [Clean Architecture]({{< ref "/posts/flutter-clean-architecture/index.md" >}}). It has all basic features from a daily quote application. At first, my idea is to make a simple daily quote application. Showing random quote everytime the app is opened, and give it an image background to make it more appealing.
|
||||
|
||||
# Hunting for quote data
|
||||
First thing I did was searching some kind of quote data that available for free. I stumbled across several choices:
|
||||
|
||||
- Use available quote API, eg: [Zen Quotes](https://zenquotes.io)
|
||||
- Scraping quotes website
|
||||
- Find dataset that already compiled somewhere in [Github](https://github.com)
|
||||
|
||||
After many consideration, I'd like to use this [Quotes 500k](https://github.com/ShivaliGoel/Quotes-500K) as my quote data source. Originally, that quote data was used for a research paper and made by scraping several quote websites.
|
||||
|
||||
First problem solved, since I have the quote dataset I was thinking whether I embed this dataset as SQLite database into the app or do something else. But then I remember that I still need to get the background image for the app and it will make no sense to embed the background images into the app as well. So I decided to create a simple REST API for Kuwot.
|
||||
|
||||
# Building the API
|
||||
Now I need a simple, easy to make REST API. I was thinking to use Python's [FastAPI](https://fastapi.tiangolo.com/) but after some onboarding tutorial, I just don't like it. Then I found [dart_frog](https://dartfrog.vgv.dev/)! It's a minimalist backend framework written in Dart. There are no reason to not use this since it use same language as my Flutter app, that was I thought.
|
||||
|
||||
Building the API is straight-forward, [dart_frog](https://dartfrog.vgv.dev/) has everything I need to build the API.
|
||||
|
||||
# Reshaping dataset
|
||||
The data I got from [Quotes 500k](https://github.com/ShivaliGoel/Quotes-500K) is looking like this:
|
||||
|
||||
| Quote | Author | Tags |
|
||||
| ----- | ------ | ---- |
|
||||
| A friend is someone who knows all about you and still loves you. | Elbert Hubbard | friend, friendship, knowledge, love |
|
||||
|
||||
Now, I didn't want the tags and I don't want a long quote. So I make a Python script to filter those quotes into a new dataset I need.
|
||||
|
||||
```python
|
||||
|
||||
```
|
||||
|
||||
# UI Design
|
||||
I want to make it as simple as possible while focusing on the functionality.
|
||||
44
src/content/blog/remap-copilot-key-infinix-air-pro-plus.md
Normal file
44
src/content/blog/remap-copilot-key-infinix-air-pro-plus.md
Normal file
|
|
@ -0,0 +1,44 @@
|
|||
---
|
||||
title: 'Remap Infinix Air Pro+ Copilot Key in Linux'
|
||||
description: 'Re-using Copilot key for something else more useful'
|
||||
date: 2025-03-01T22:41:32+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- linux
|
||||
- laptop
|
||||
- infinix
|
||||
- tweak
|
||||
---
|
||||
|
||||
> Since I'm moving to Linux, my Copilot key becomes useless.
|
||||
|
||||
Let me rephrase that! Even when I was using Windows, I never using this Copilot shortcut key in my keyboard 😬. Fortunately, using Linux I can remap this key for something else ~~more useful~~.
|
||||
|
||||
# Requirements
|
||||
- A laptop (I'm using Infinix Air Pro+) with a working keyboard.
|
||||
- [keyd](https://github.com/rvaiya/keyd)
|
||||
|
||||
# Finding what this Copilot key do
|
||||
- Open your favorite terminal and execute `sudo keyd monitor`. This command will print what events are triggered when a particular key is pressed.
|
||||
- Press the Copilot key and read the output. In my laptop, it print out this:
|
||||
|
||||
```bash
|
||||
AT Translated Set 2 keyboard 0001:0001:70533846 leftmeta down
|
||||
AT Translated Set 2 keyboard 0001:0001:70533846 leftshift down
|
||||
AT Translated Set 2 keyboard 0001:0001:70533846 f23 down
|
||||
```
|
||||
|
||||
- Now I know that my copilot key triggers `leftmeta`, `leftshift`, and `f23`. It's seem legit combination of modifier keys and a function key. But unfortunately when I tried to use it in my desktop environment (I use KDE) to bind a shortcut, it only detect the modifier `meta` and `shift`.
|
||||
|
||||
# `keyd` for the rescue
|
||||
Edit `/etc/keyd/default.conf` file and I added these lines:
|
||||
|
||||
```plaintext
|
||||
[ids]
|
||||
0001:0001:70533846
|
||||
|
||||
[main]
|
||||
f23 = f13
|
||||
```
|
||||
|
||||
`ids` is my keyboad ID, and the last line tells to remap `f23` key to `f13` (which is doesn't exist physically). Then reload `keyd` with `sudo keyd reload`. Now I can bind my Copilot key to something else. I'm using it for [yakuake](https://github.com/KDE/yakuake) show/hide toggle.
|
||||
23
src/content/blog/welcome.md
Normal file
23
src/content/blog/welcome.md
Normal file
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
title: 'Welcome'
|
||||
description: 'Initial commit!'
|
||||
date: 2024-03-18T14:16:19+07:00
|
||||
draft: false
|
||||
tags:
|
||||
- misc
|
||||
---
|
||||
|
||||
# Introduction
|
||||
|
||||
Hi there! I'm Dhemas, an Indonesian software engineer. I grew up in a small town called Salatiga, Central Java, Indonesia. I really like to tinker with computer since I was a child. Playing games (SkiFree to Age of Empires II) in my dad's office computer, then learn some office softwares, buying a floppy disk to save my diary (encrypted with Webdings font!), buying PC magazines, leads to learn how to assemble my own computer and do an OS install. That was a good time!
|
||||
|
||||
Long story short, I decide to take an Information Technology major in my local university then got accepted in my first company right after graduated, working as a mobile application developer. Since then, it is already 7 years I work as a software developer and now I'm a part of a software house startup company.
|
||||
|
||||
I never really write anything in my 7 years journey and I feel kinda regretted it. So I decide to create this blog, where I can write anything I found interesting. Maybe it's a coding-related thing, technology heads up, or maybe just my random thought. Feel free read and share!
|
||||
|
||||
|
||||
# Bonus
|
||||
|
||||
This is a cat from my work, maybe someday she can be a good software tester to find ~~mice~~ bugs from my code.
|
||||
|
||||
  
|
||||
Loading…
Add table
Add a link
Reference in a new issue