maruos
maruos copied to clipboard
maruos
Bluetooth dying with wrong indication on hammerhead
Hi, my Nexus5 (hammerhead) does often loose bluetooth connection (e.g. to my smartwatch). The Bluetooth symbol is still displayed, but any bluetooth devices do not connect anymore. Switching to "plane mode" and back sometimes helps, but sometimes the bluetooth device itself is gone (inside the settings menu) and the phone has to be rebootet. After reboot everythings works again for a while.
I am not sure if this is software related or a hardware issue of my good, old phone - so please, could someone confirm this problem before the experts waste time on a single device problem?
Could I collect some debugging logs / informations? Is there some information in the developer section of the mobile?
@pdsouza: I couldn't find the function to add the label #device/hammerhead.
Regards, PifPof73
Hello! Looks like I forgot to migrate the bug reporting instructions to our new docs website. Here is the page from our old wiki: https://github.com/maruos/maruos/wiki/Bug-Reports.
@PifPof73 The log is huge but I don't see anything obviously wrong from a quick scan. I will need to try to replicate this on my end with a long-lived BT connection. I have not experienced anything with my BT keyboard or mouse like you describe, but they will suspend with inactivity so maybe I have not run into your issue.
Are there any other specific devices other than a smartwatch where this bug shows up? If not, I'll try to get my hands on an Android smartwatch to test this out.
Also, does Maru Desktop running have anything to do with when this Bluetooth issue occurs or does it occur even if Maru Desktop not enabled?
Hi pdsouza, sorry for the huge logs. The issue occurs without starting the Maru Desktop (so I think it is more on the lineage side of your project). Sometimes I want to use desktop mode, but don't get the keyboard connected. I than have to switch several times the flight mode on and off, to get the BT stack restarted - sometimes it does not work at all and I have to reboot the phone. I have these problems with all my BT devices (car entertainment system, smart watch, keyboard, my balance in the bathroom, load speakers etc.). My smart watch mostly is disconnected and if I don't care sometimes I get a feedback during the day (smartwatch is suddently vibrating if I received a message), but than shortly afterwards the connection is lost again.
The BT sign in the top of the lineage screen is always on, but BT is not active - it seems like power napping on the BT stack and I don't know how to wake it up properly.
In the developer menu of lineage os I see a "BT HCI-Snoop protocol", which I know activate. Than all BT pakets should be locked inside a file - maybe this give more hints.
Thanks again for your time and energy. Regards, PifPof73
OK, thanks for the clarification.
Maybe I can reach out to the LineageOS hammerhead devs to see if they have encountered similar reports to save time.
On Tue, Oct 22, 2019 at 12:10 AM PifPof [email protected] wrote:
Hi pdsouza, sorry for the huge logs. The issue occurs without starting the Maru Desktop (so I think it is more on the lineage side of your project). Sometimes I want to use desktop mode, but don't get the keyboard connected. I than have to switch several times the flight mode on and off, to get the BT stack restarted - sometimes it does not work at all and I have to reboot the phone. I have these problems with all my BT devices (car entertainment system, smart watch, keyboard, my balance in the bathroom, load speakers etc.). My smart watch mostly is disconnected and if I don't care sometimes I get a feedback during the day (smartwatch is suddently vibrating if I received a message), but than shortly afterwards the connection is lost again.
The BT sign in the top of the lineage screen is always on, but BT is not active - it seems like power napping on the BT stack and I don't know how to wake it up properly.
In the developer menu of lineage os I see a "BT HCI-Snoop protocol", which I know activate. Than all BT pakets should be locked inside a file - maybe this give more hints.
Thanks again for your time and energy. Regards, PifPof73
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/maruos/maruos/issues/122?email_source=notifications&email_token=AACMM4VANOLQ324PD6TK6PLQPZ4KBA5CNFSM4IUXEXJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB4PJCQ#issuecomment-544797834, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACMM4VFU2EZ7M47PMYL4LLQPZ4KBANCNFSM4IUXEXJQ .
-- https://preetam.io
Hi, since my last post, the USB debug log file is active and now, BT is working like a charme, the complete day my smartwatch stayed connected, on my way to work and back the car entertainment system direct connected and worked. So enabling the logging solves the problem.
I guess it could be some sort of BT hibernate, which is not waking up and stayed sleeping if logging is turned off? Maybe the LineageOS devs do know something about BT hibernating problems (its just a guess).
Tomorrow I will disabling the logging again and check if the problem comes back. Greetings from Germany, PifPof73