How to Install LineageOS on OnePlus 3T with GApps

This is the minimal guide for installing LineageOS 17.1 on OnePlus 3T abtracted from LineageOS offical guide. It works at the time of writing so no gurantee for further updates.

  1. Enable OEM unlocking and USB debugging on your phone with developer mode.
  2. Download latest Android platform tools for Windows, for Linux, or for macOS from Google. The full guide can be found at Using ADB and fastboot.
  3. Connect your phone into your computer with USB mode.
  4. Install the built-in OnePlus USB Drivers or use UniversalAdbDriver.
  5. cd to the platform-tools directory, run adb devices to see if your phone is connected.
  6. Run adb reboot bootloader to boot your phone into bootloader mode.
  7. Run fastboot devices while in bootloader mode to see if your computer still connects to it.
  8. Run fastboot oem unlock. Your phone should be reset and reboot automatically.
  9. Setup your phone. Then re-enable USB debugging.
  10. Download latest custom recovery from TWRP.
  11. Run adb reboot bootloader to boot your phone into bootloader mode. Also make sure your phone can be find in fastboot mode by re-typing fastboot devices.
  12. Run fastboot flash twrp-3.4.0-0-oneplus3.img to flash custom recovery.
  13. Run fastboot boot twrp-3.4.0-0-oneplus3.img to boot into new recovery mode.
  14. Download the LineageOS installation package.
  15. Download Google Apps using the arm64 architecture. Choose the packages you prefer (I recommend nano package).
  16. In recovery mode, tap Swipe Format Data
  17. Return to the previous menu and tap Advanced Wipe, then select the Cache and System partitions and then Swipe to Wipe.
  18. Sideload the LineageOS and Google Apps packages:
    1. On your phone, tap AdvancedADB Sideload, then swipe to begin sideload
    2. On your computer, sideload the package using adb sideload lineage-17.1-20201026-nightly-oneplus3-signed.zip.
    3. Then sideload the Google Apps using adb sideload open_gapps-arm64-10.0-nano-20201031.zip.
  19. Back to recovery main menu. Reboot your device.
  20. Setup your LineageOS.

Apple AirPods Pro vs Sony WH-1000XM4 vs Samsung Galaxy Buds+

不废话,来个经典的优缺点列表式测评

Apple AirPods Pro

优点

  • 优质的 ANC(主动降噪)效果,主管感受上基本打平 Sony
  • 无敌的 Transparency Mode,在目前所有的 TWS 中是最强的,穿透进来的环境声音不强不弱,大部分情况下确实可以达到「transparent」的水准
  • 小巧便携,放进裤兜里即可
  • 与 Apple 设备高度集成,体验流畅

缺点

  • 续航短,开启 ANC 基本就 3 个小时左右,只适用于国内航班
  • 不支持多设备同时在线(类似蓝牙 Multipoint 的特性)
  • 低频表现一般

Sony WH-1000XM4

优点

  • 手感、做工不错
  • 超长续航,开启 ANC 也可以有 30 小时的续航,轻松应对国际航班/一整天的工作环境
  • 双设备同时在线
  • 可以 3.5 mm 有线连接

缺点

这款耳机的很多优点也都是它的缺点,比如:

  • 虽然支持超长续航,但没有无线充电或 Qi 充电
  • 支持双设备同时在线,但仅支持双设备,不支持更多设备,也不支持多设备快速切换。并且开启双设备同时在线后,无法开启 LDAC,这点很重要,没有 LDAC 的 1000XM4 音质真的只能用渣来形容,然而这一点几乎所有的 KOL、测评都不会提及
  • 用 3.5 mm 有线连接后,如果这时候你拔出接头,耳机会执行一次关机,不知道这样设计的逻辑是什么?导致我每次关机后都需要再手动开机然后蓝牙配对
  • 耳机上执行上划/下划切换音量时并没有绑定系统音量。也就是说这个切换不会同步设备中的系统音量

除此之外还有以下缺点:

  • 佩戴不舒适,真不知道是不是索尼在国内的水军太多了,还是我的头部构造离谱。我佩戴超过 2 小时后必头疼,夹耳朵,无论怎样调整都夹耳朵
  • 环境音模式(类似 AirPods Pro 的 Transparency Mode)效果很一般,开启低等级听不清人声,开启高等级后底噪高的离谱。可能全封闭式耳机想要达到入耳式耳塞的「透明模式」的效果确实更难一些

Samsung Galaxy Buds+

作为这几款中最便宜的耳机,也是唯一没有主动降噪的耳机。不能要求过多:

优点

  • 价格便宜
  • 续航略优于 AIrPods Pro
  • 但在 Galaxy Wearable 中,可以调出「超高环境音量」模式,可以将环境音以高于正常的音量传入耳朵。很有意思,感觉像带了耳返

缺点

  • 没有 LDAC
  • 由于它造型的原因,无法或较难单手打开电池仓
  • 与 1000XM4 一样操作音量时不会绑定系统音量,不过这个默认是关闭的,在「实验室功能」里

Use IKEA TRÅDFRI Driver with HomeKit

You must use IKEA TRÅDFRI Gateway to add your drivers. Philips Hue Bridge can add TRÅDFRI drivers but they won’t appear in your Home app. That means TRÅDFRI drivers with Philips Hue Bridge won’t work with HomeKit. So dig into your pockets to buy a TRÅDFRI Gateway.

After you setting up your TRÅDFRI Gateway with IKEA Home smart app. The app will force you to add a controller (Wireless Dimmer, On-Off Switch/Dimmer, etc.) to control any smart devices. That prevents you from adding any driver directly to the app. You have to add the driver through a controller. So again, dig deeper into your pockets to buy a switch/dimmer. I recommend TRÅDFRI Wireless dimmer. I just bought one as the device adoptor since I won’t use it to control my devices.

You can pair the wireless dimmer with more than one drivers. When you push on/off on the dimmer. All paired drivers will respond. It’s okay if you just use it as the device adoptor like me. But if you want to use it later as a normal dimmer. Just remove it from the app and re-pair it the right driver.

Don’t buy any other IKEA smart devices at the time of writing. Like motion sensors, bulbs, etc. Blinds are okay but reported the motors are louder than other brands. That means most of them suck.

Low Latency HomeKit Camera Support: Homebridge FFmpeg Plugin with Custom Codec Configuration

Stream passthrough method for low latency HomeKit camera support:

  • Device: EZVIZ (萤石) CS-C6CN-3H2CWF (星光夜视版)
  • Low latency (as low as 100ms) from the camera to homebridge-camera-ffmpeg
  • Low CPU load since all streams are passthrough from FFmpeg without re-encoding
  • No audio support due to compatibility issue from the source stream

The configuration should be look like:

"videoConfig": {
    "source": "-rtsp_transport tcp -i rtsp://admin:<device_passcode>@<device_ip>:554/h265/ch1/main/av_stream",
    "maxFPS": 30,
    "audio": false,
    "vcodec": "copy",
}

Here’s the tricky part: the EZVIZ CS-C6CN-3H2CWF will output h265 by default, which is not supported by HAP. And the default bitrate is also too high to handle for iOS devices. So you will need to update some settings for the camera:

  • Download the Chinese version of EZVIZ Studio from the official website (direct link).
  • Install and run
  • Click 本地设备 (Local Devices) on the sidebar
  • Right-click the camera you want to modify, then choose 高级设置 (Advanced Settings)
  • In the popup window, click 图像 (Images) – 视音频 (Audio/Video) on the sidebar, change the following settings:
    • 编码类型 (Encoding Type): STD_H264
    • 码率上限 (Bitrate Limit): 1024 Kbps
    • (Optional) 分辨率 (Resolution): HD720P
  • Click 保存 (Save) to save the settings

Please note this step will slightly reduce the quality of your video stream when you view the stream in EZVIZ official app, but it’s mandatory for the camera to work with HomeKit.

Bonus: audio support without compiling FFmpeg after version 1.0.0:

"videoConfig": {
    "source": "-rtsp_transport tcp -i rtsp://admin:<device_passcode>@<device_ip>:554/h265/ch1/main/av_stream",
    "maxFPS": 30,
    "audio": true
}

This will make FFmpeg re-encode your stream and hurt your CPU. The latency is about 0.6-1 second. I suggest you install Homebridge on a Mac mini for better performance.

Update for homebridge-camera-ffmpeg 3.0.0 and later: It’s finally stable enough to stream passthough with audio support. You can now use the following config:

"videoConfig": {
    "source": "-rtsp_transport tcp -i rtsp://admin:<device_passcode>@<device_ip>:554/h265/ch1/main/av_stream",
    "maxFPS": 30,
    "audio": true,
    "vcodec": "copy",
}

Allow WordPress Embedded Posts with Global X-Frame-Options for Nginx Servers

The problem: when you enables X-Frame-Options globally. You won’t be able to embed your posts with latest WordPress embed posts method.

The solution: you can simply exclude it in your Nginx configuration. I’ll use Nginx map for better performance:

map $request_uri $x_frame_options_headers {
  default                 SAMEORIGIN;
  # Matching WordPress embed page, ie. https://example.com/my-post/embed#?secret=vLi4CQcWkH
  ~/embed                 "";
}

# Don't allow the browser to render the page inside an frame or iframe
add_header X-Frame-Options $x_frame_options_headers;
Embedding Demo

balenaEtcher: Source and destination checksums do not match errors

If you got the following errors:

\\.\PhysicalDrive1: Source and destination checksums do not match: <hash1> !== <hash2>

You can try to disable removable drives to be added to libraries setting for System Volume Information folder creation:

How to prevent creation of “System Volume Information” folder in Windows 10 for USB flash drives?