Nisarg Jhaveri

``` $ gdb 8188eu.ko ... Reading symbols from 8188eu.ko...(no debugging symbols found)...done. (gdb) l *rtw_txframes_sta_ac_pending+0x64 No symbol table is loaded. Use the "file" command. ```

I have it installed using dkms, if that has anything to do with `no debugging symbols found`.

Sure. I'll try the new version and see if anything happens again.

It happened again. Here is the stack trace. ``` Mar 30 15:48:37 raspberrypi kernel: [38904.745345] Unable to handle kernel NULL pointer dereference at virtual address 00000064 Mar 30 15:48:37 raspberrypi...

Sure. I'll try the new code and report if I find anything. Unfortunately, the problem is that I can't figure out how to reproduce this. This happened a couple of...

The gradle plugin @mortalis13 mentioned seems to be unmaintained and archived. Also, if would be great if android support works without any changes in build.gradle, so that people can easily...

@donat, I'm trying to see how stuff works. I tried adding this to my app/build.gradle and sync in vs code. Doesn't seem to help, the java files still errors that...

Could you please give some more context? This seems to be an error while building, which the extension does not support by itself.

Yes, we should be able to make some of the things work with other simulators or devices, though I've never directly worked with watchOS. Could you please explain your setup...

The steps you described above are very similar to how we work with iOS simulators. I expect we should be able to support watchOS simulator as well with some changes....