search

AsteroidOS / meta-smartwatch

OpenEmbedded layer that provides support for various smartwatches.
26 stars 18 forks source link

Bt works , but didn't connect to my phone #57

Open ItsVixano opened 5 years ago

ItsVixano commented 5 years ago

hi , i'm using a mooneye , and after installed it , i tried to connect to my phone but , he make a loop of connect/disconnect i love this project and i want to use it every day , but i cannot do this it see be a phone issue "Whyred with EvoX" but i don't know

i'm using the last snapshot release

sorry for my grammar , i'm italian

Qiangong2 commented 4 years ago

Can anyone confirm that this is still the issue with mooneye? Or does bluetooth now work?

gortbrown commented 4 years ago

I just flashed it to my Ticwatch E, and I can confirm this is still an issue. Just keeps bouncing back and forth between connect and disconnect.

sayopaul commented 4 years ago

thanks for the info. I am seriously considering flashing to my Ticwatch E however I want to wait till bluetooth is working

AyoPrez commented 4 years ago

Yeah, I just flashed my Ticwatch E and this is still happening. Does someone know where or what is the problem?

archaicmeander commented 4 years ago

Still an issue on Ticwatch E with AsteroidOS 1.1-nightly. Infinite connect-disconnect loop. Anyone have any suggestions? Has any headway been made?

Sustenance commented 4 years ago

@FlorentRevest I know it's been a couple years, but I see that you did spend time backporting and patching the BT for mooneye. I tried watching /dev/kmsg but it was hard for me to pinpoint what might be going wrong (I'm also not experienced with debugging drivers). I can provide that log though, if you have time to look. If not, do you have any pointers for where one of us should start investigating? Thanks in advance.

FlorentRevest commented 4 years ago

Hey @Sustenance, thanks for reaching out :) If I recall correctly, MediaTek android kernels come with a bluetooth driver that does not support HCI and even though it's fine on Android, it makes it impossible to use a BlueZ stack. I had found a MTK HCI driver in some random Ubuntu Touch kernel. It works on harmony and it seems to kinda work (a little bit) on mooneye but I don't remember exactly what stopped working. Maybe you could use hcidump to get HCI logs of what happens during a connection to your watch and this could be compared with another Asteroid watch where the connection works. I unfortunately no longer have the time necessary to look into this.

MagneFire commented 3 years ago

Apparently there is also https://github.com/mer-hybris/bluebinder that creates a virtual HCI devices and bridges data and events to the Android binder. This is available for Android bases 8 and up. We currently have two devices that are based on Android 8: mooneye and sawfish (Currently on Nougat but I have it working on Oreo too).

I don't own a mooneye but I can try this in the future on my sawfish. Keep in mind that this a low priority thing for me as Bluetooth works fine on sawfish using the traditional patches (backport 4.1 patches and patch Bluesleep).

KulguninAr4i commented 3 years ago

Apparently there is also https://github.com/mer-hybris/bluebinder that creates a virtual HCI devices and bridges data and events to the Android binder. This is available for Android bases 8 and up. We currently have two devices that are based on Android 8: mooneye and sawfish (Currently on Nougat but I have it working on Oreo too).

I don't own a mooneye but I can try this in the future on my sawfish. Keep in mind that this a low priority thing for me as Bluetooth works fine on sawfish using the traditional patches (backport 4.1 patches and patch Bluesleep).

Hello. I am actively testing this watch. Has there been any progress for the Ticwatch S / E?

MagneFire commented 3 years ago

Apparently there is also https://github.com/mer-hybris/bluebinder that creates a virtual HCI devices and bridges data and events to the Android binder. This is available for Android bases 8 and up. We currently have two devices that are based on Android 8: mooneye and sawfish (Currently on Nougat but I have it working on Oreo too). I don't own a mooneye but I can try this in the future on my sawfish. Keep in mind that this a low priority thing for me as Bluetooth works fine on sawfish using the traditional patches (backport 4.1 patches and patch Bluesleep).

Hello. I am actively testing this watch. Has there been any progress for the Ticwatch S / E?

Unfortunately not for the moment. I didn't have time to work on this. When I will get time for it I will pretty much just use the flow described in https://sailfishos.org/wiki/Architecture (i.e. Bluez5 <> kernel VHCI <> bluebinder <> libgbinder <> Android BSP HAL: android.hardware.bluetooth ) Once I have something I will of course update this thread :smile:

fluffysfriends commented 1 year ago

Any news regarding this issue?

fluffysfriends commented 1 year ago

hcidump HCI sniffer - Bluetooth packet analyzer ver 5.65 device: hci0 snap_len: 1500 filter: 0xffffffff

HCI Event: Disconn Complete (0x05) plen 4 status 0x00 handle 512 reason 0x08 Reason: Connection Timeout HCI Event: Command Complete (0x0e) plen 4 LE Set Advertising Parameters (0x08|0x0006) ncmd 1 status 0x00 HCI Event: Command Complete (0x0e) plen 4 LE Set Advertise Enable (0x08|0x000a) ncmd 1 status 0x00 HCI Event: Disconn Complete (0x05) plen 4 status 0x00 handle 512 reason 0x08 Reason: Connection Timeout HCI Event: Command Complete (0x0e) plen 4 LE Set Advertising Parameters (0x08|0x0006) ncmd 1 status 0x00 HCI Event: Command Complete (0x0e) plen 4 LE Set Advertise Enable (0x08|0x000a) ncmd 1 status 0x00 I tried to connect two times using Gadgetbridge on Android 13 using a Sony Xperia X10 III

MagneFire commented 1 year ago

Any news regarding this issue?

Nope, last time I checked the proposed idea of using bluebinder won't work since mooneye doesn't use the /dev/hwbinder interface. This means there's work required on the kernel driver to figure out what's going wrong.