I'd like to monitor my bluetooth traffic on my andorid device.
I have tried this stuff:
Sniffing/logging your own Android Bluetooth traffic
But sady, i still cant find the saved file. The only File I can find is in the /sdcard/Android/data/ folder. But this file is empty and old.
I turned bt off to switch the tracking functionality on and turned it on again when started. Same when i was finished.
Oh, and its said that the phone doesnt need to be rooted. I've found an app which does the same but needs the phone to be rooted... so maybe i also need to root it to make the androids built in feature work?
And I tried this on an s10 and s7.
I hope someone can help me out here.
Have a nice day and thanks for reading :)
Related
I have searched a lot of places on Google and I just can't seem to figure out how to get my computer (which is running Windows 10) to recognize my phone so I can use it for programming. I was hoping someone can help me. It used to be simple before Android version 6.0.1 so I'm not sure if I am just not finding the right setting or what, so please if you have specific instructions or a site I can go to to help me out I would greatly appreciate it.
Like I said before, all I am trying to do is somehow get my computer to recognize my phone so I can transfer files. It used to be that all I had to do was turn on USB mass storage but I can no longer find that option.
Well first You need to make sure You have to install your drivers
Second thing Plug in your Phone in when click in notification tray see if you can find an option saying "Photo transfer" if you connect to that maybe your device will get recognized.
That worked for me on my nexus 5x on 6.0.1
If transering file is your only concern than check out Apps like xender , Zapya they will server the purpose
I recently bought an android tv box (dongle) model mk808b plus which some of you might be familiar with. What I want to do is use it for development, I want to program on it using adb, Android Studio.
The problem I am facing and its not the first of its kind, I get this with all the media boxes that I tried, they dont work as adb devices at all, I dont get any device in my device manager when I connect them on the usb (not even an unknown one). I tried reflashing the android, I put cyanogen mod on it, but to no avail, it still happens. Another thing is, if I put my device in Recovery Mode it does detect an unknown device in my control panel, but never after I boot up my android os.
Now before you say I didnt enable Developer Options Usb Debugging or I didnt put my device as MTP device, I did. I checked these and the cables im using are fine.
I dont have any problem with my Nexus 5 or S5 for the matter, just when I try these android boxes that come up with these tv like custom roms.
If you guys have any idea, I'll be happy to read, I did not find anything related to this on the internet.
PS: Why not use my Nexus 5 or S5? because the app im developing is for these boxes, so testing some of the features such as hdmi connectivity etc etc is very useful to me.
Thank you,
Andi
Unfortunately I couldn't do anything, maybe it's because of the custom ROM on it, but I did find an alternative, I'm using adb on tcp ip, it seems to work after I rooted my device, still no usb adb interface.
I'm encountering a very strange problem while developing on android. My project is a bit unorthodox, so please bear with me.
I'm developing a game that uses an external controller that's connected to the phone using an OTG cable. All works OK, until the phone's temperature crosses a certain threshold, In which case the operating system shuts down the communication with the OTG and I'm unable to restart it in any way other then disconnecting the OTG cable, and reconnecting it, which is a process I would really like to avoid.
So my question is does anyone know what part of the operating system is the one performing this action of shutting down the USB input when the device gets overheated, and where can I control\reboot it?
Would very much appreciate your help, as I don't even know where to start looking, just please avoid answers like "just unplug and plug back the otg", or "just make sure your device doesn't overheat"
Much obliged
It's probably a hardware issue. If it's actually implemented in the OS itself, then you should probably look in the kernel code. It's not the standard behavior in all android devices, so you should try using another device.
I have a game built on Unity running in an android device. In theory it should be possible to step through the unity code by attaching to AndroidPlayer at runtime.
Well I followed the rules on how to do this.
1) Created development build with script debugging enabled.
2) run the app with script debugging on wifi that has the player.
Initially it worked. Then perhaps a change or two in my network, and I no longer see AndroidPlayer as an option in MonoIDE to attach to. Its vanished and for several days now I am not able to debug. Not only that but i really don't know where to check this. I yanked out the ethernet cable so device and Mac are both on same wifi running on single subnet. Nothing seems to help. But what really dissappoints me is there is really nothing to check in Unity when this type of thing happens. It just try to attach to proess. Hope AndroidPlayer process is there and if its not. Tough luck.
PS: I should add I am on Unity Pro 4.2.04f. It worked fine, then who knows what and it stopped finding the AndroidPlayer. What a mess!
PS: Things I have tried. Pinging to ip address, and telneting to port (successfully to ip:5555)
Note: This is not the Android Debugger I am talking about but a player that needs to be running in the app, and visible to MonoIDE in order to debug.
What I am really trying to understand is what are my options when I cannot see AndroidPlayer as an process to attach to?How does one debug this problem? Are there things in the logg if AndroidPlayer is sucessfully running? How could monodebug not see it? How do I know it it is or is not running on the devices.
Thanks
Have you looked at the IP address of the Android device and attempted to ping it? I find that, here in the UK, our BT provided "home hub" will often, randomly, stop routing traffic between devices on the same network.
I find that if I can't debug (and I believe Unity 4.2 still used wifi debugging) then I usually can't print either and it's because the router has stopped routing traffic.
A quick reboot of the router usually fixes it.
PS Just read about the ping being successful. Have you downloaded and run "wireshark" to see what network traffic is happening? At least that will show you what is happening on the network layer.
Other thought, any sort of firewall running on the debugging machine?
Try to:
1) Disable antivirus
2) Disable firewall
3) Deinstall Xamarin (in case when you use VS for debugging)
That did help me when I had the same problem
I don't expect you to correct my code, since it should be working, at least works on emulator. Unfortunately gives different output on the devices. My question is:
How to debug in such cases, when the device is not working as the emulator, and what could cause that (device model, a custom ROM?)
I heard some rumors some time ago, about possibility using the device instead an emulator somehow connected to the SDK. Could you also confirm or deny that?
You'll find it's not uncommon to find little quirks between devices. Many developers will have several physical devices to test their software on.
You can find information on using a physical device for debugging (including using it inside Eclipse, just as you would the emulator) on the Android website: http://developer.android.com/guide/developing/device.html
Yes you can do that. Just put your device into debugging mode, and connect it to the computer with the micro-usb port on the device. You will also need to download the drivers from the manufactures website.