Posts

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 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: 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: ...

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. $ 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. ...

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. This library implements core concept of CRDT and it’s pretty basic. Here some types of CRDT that often used: ...

I installed Linux (EndeavourOS) 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 $ 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: ...

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. ...