Skip to content
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

real phone got wrong warning #485

Closed
r0ysue opened this issue Feb 21, 2024 · 1 comment
Closed

real phone got wrong warning #485

r0ysue opened this issue Feb 21, 2024 · 1 comment
Labels
question Further information is requested

Comments

@r0ysue
Copy link

r0ysue commented Feb 21, 2024

Describe the bug
using Pixel 6 but got wrong warning :
2024/02/21 15:18:21 Your environment is like a container. We won't be able to detect the BTF configuration.

and capture traffic just works as normal

To Reproduce
Steps to reproduce the behavior:
just run ./ecapture --help

Expected behavior
no any warning

Screenshots
截屏2024-02-21 23 18 36

Linux Server/Android (please complete the following information):

  • Env: Pixel 6 [oriolet]
  • OS: latest android 14 ,14.0.0 (UQ1A.240205.002, Feb 2024)
  • Arch: [aarch64]
  • Kernel Version: 5.10.117
  • Version:5.10.177-android13-4-00003-ga7208022a7ea-ab10815828
  • root Method:Magisk v27.0
@cfc4n cfc4n added the question Further information is requested label Feb 22, 2024
@cfc4n
Copy link
Member

cfc4n commented Feb 22, 2024

That's right, this is just a reminder and does not affect the functionality.

The purpose is that eCapture cannot determine whether the current environment supports CO-RE, and users need to make their own judgment and select the corresponding version.

@cfc4n cfc4n closed this as completed Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants