https://github.com/akotov-dev/areditor
Automatic rule editor for Android devices (Mageia/Ubuntu)
https://github.com/akotov-dev/areditor
android udev usb
Last synced: 12 months ago
JSON representation
Automatic rule editor for Android devices (Mageia/Ubuntu)
- Host: GitHub
- URL: https://github.com/akotov-dev/areditor
- Owner: AKotov-dev
- License: gpl-3.0
- Created: 2021-06-27T09:13:24.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2022-01-16T07:37:37.000Z (over 4 years ago)
- Last Synced: 2025-04-13T20:03:06.188Z (about 1 year ago)
- Topics: android, udev, usb
- Language: Pascal
- Homepage:
- Size: 77.4 MB
- Stars: 3
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ArEditor - automatic rule editor for Android devices
51-android.rules: https://github.com/M0Rf30/android-udev-rules
1. In the list of connected USB-Devices (1), find your device that is not recognized when working with ADB and select it with the mouse
2. If the device is not in the list of rules, the necessary line (2) will be offered to insert into the file with the rules
3. Specify the environment variable (`ENV{adb_adb}="yes"` - adb only by default)
4. Click the button "Plus" (Add & Apply) and reconnect the device
5. Now the device is contained in the list of rules and should be recognized after the `adb` restart
**Reasons why Android devices may not be displayed:**
1. The USB debugging mode is not enabled on the smartphone
2. The device is not in the list of rules `/etc/udev/rules.d/51-android.rules`
3. The User is not included in the group described in `/etc/udev/rules.d/51-android.rules`
4. The connection is hindered by the old key, which you need to delete and restart `adb`:
`adb kill-server; rm -rf ~/.android/*; adb start-server`
`ArEditor` works with the new versions `android-tools`: https://github.com/AKotov-dev/android-tools-rpm
