Skip to content

Commit

Permalink
Fix typo
Browse files Browse the repository at this point in the history
  • Loading branch information
Dianliang233 authored and ase1590 committed Jan 1, 2025
1 parent 96f6a24 commit ff2a2ee
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions flip-wiki/docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ To fix this, run through the following steps:
- **Debug**: `OFF`
- **Heap Trace**: `None`

After these are set, press back and leave the menu. Reboot your flipper. The issue should not be gone.
After these are set, press back and leave the menu. Reboot your flipper. The issue should now be gone.

### Infrared or SubGHz does not appear to be working
This is an issue that *can* occur from switching between firmwares. To fix this, try the following:
Expand Down Expand Up @@ -113,4 +113,4 @@ ChromeOS users will have to only utilize [Flipper Lab](https://lab.flipper.net),

While ChromeOS does allow USB devices to access Linux environments via `Settings > Linux > USB preferences`, the security hardening features of ChromeOS
prevent udev scripts from applying the `uaccess` property to the device within the context of the secure linux container, which is needed for qFlipper to properly access the Flipper Zero. Attempting to run qFlipper with `sudo -E` is also fruitless.
This roadblock lies firmly on the ChromeOS side for the time being. While Flipper Labs is nearly at feature parity with qFlipper, it cannot perform a DFU recovery. Should such a need arise, you will need temporary access to a non ChromeOS based PC.
This roadblock lies firmly on the ChromeOS side for the time being. While Flipper Labs is nearly at feature parity with qFlipper, it cannot perform a DFU recovery. Should such a need arise, you will need temporary access to a non ChromeOS based PC.

0 comments on commit ff2a2ee

Please sign in to comment.