-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Root support #1
Comments
Do you have any recommendation to enable root access ? It seems that :
Are you using a version >= 5.0 ? If not you could build the app with this additional permission. |
Hello @bertrandmartel Im using LineageOS 14.1 - Codebase 7.1.2. In fact, this android does save HCI log from Developer Options, but this tshark cannot open the btsnoop file because some packet is hugelly big, so something is corrupted. And Im trying to use you software, but you software cannot access the default folder and even the storage API, so I can set a file to be saved. About building, how can I do this? I'm using linux, but if possible to do not install entire eclipse and development tools, i prefer. Thanks! |
Are you sure it is a permission issue, when you click to browse the file you cant access /sdcard/data ? Or you dont see it ? Or you can access it but showing "processing HCI..." indefinitely ? |
Hello, just dont see anything.. |
Hi, with an OnePlus One and a custom rom on Nougat I had the same problem than leleobhz. I don't see anything when I try to browse the log file. So, to obtain something I have to scan and after that, copy the log file into the sdcard which is accessible from anyone with a rooted File Manager. (not all rooted File Manager works, and I didn't found one which is free-software to take the code to access to the log file) |
Hello dev,
Im using you app in a i9300 with LINEAGEOS 14.1 and I can't open /data/misc/bluetooth/logs/btsnoop_hci.log because lack of permission. This phone does have root but you dont support it. Its possible to add a option to use root to open the hci log?
Thanks!
The text was updated successfully, but these errors were encountered: