Warning over Bluetooth fails after some time

[CAA_0821145133]

Phone: Nexus 4, stock JB 4.2.1
Car: 2011 C Class with Command Online.

No problem connecting to car Bluetooth. Handles calls with no issues.

Setup CamerAlert to deliver warning over Bluetooth. (device linked to account)

Initially everything work as it is supposed to. App is running in foreground
Then
CameraAlert stops sending the warnings over bluetooth after some time (about 10 minutes). Warnings are still shown on the phone screen, but no sound (via bluetooth). Phone remains connected to bluetooth as can still make and receive calls,


Can anyone help? Is this a bug in the app?

[lbendlin]

So you specifically selected Bluetooth Headset in the CamerAlert sound settings? Do you know if your car also supports A2DP (Stereo audio)? If yes, then you may be able to use the default audio routing setting instead, and maybe let us know if that behaves differently?
_________________
Lutz

Report Map Errors here:
TomTom/TeleAtlas NAVTEQ

[DennisN]

Lutz this happens on iOS too. Phone call stops BT audio. Close and restart CA restores audio. I thought we had long ago reported this and it was in the pipeline for fix.
_________________
Dennis

If it tastes good - it's fattening.

Two of them are obesiting!!

[CAA_0821145133]

OK looks like this may be the solution.

The car does support A2DP

What I have done is under Bluetooth settings,

The options for the car Bluetooth (MB Bluetooth) was for Phone Audio and Media Audio. Both were selected.

I have unchecked Media Audio (as I don't stream from my phone anyway)

will report back.



On a different note completely, it seems Google is crippling Android more and more with each update, e.g. now Airplane mode is now secure, so you cannot get Profile Apps like Llama to get the phone into Airplane mode at set times ... grrrr

[CAA_0821145133]

Update

Above this does not fix this.

Also cannot get Google navigation to output guidance over bluetooth

Any ideas?

[CAA_0821145133]

More tweaking, but still not quite acceptable.

If I have Google navigation (which seems to only work via phone speaker)
ALSO running in the background
AND keep the screen ON

(I don't usually have a lock screen set up anyway, when I switch on the screen I go straight to the homescreen)

then and only then it seems, the warnings goes and continues over bluetooth

[CAA_0821145133]

Given up on Bluetooth issue.

But now, it seems, the app just stops working in the background.

7 hr drive yesterday, initially working (via phone speaker). once screen goes off, it seems to stop working. Switching the screen ON seems to starts the GPS listener again.

[lbendlin]

sorry to hear about your issues. The app normally only terminates after 10 minutes of no GPS changes. In your trip did you maybe have breaks where you were stationary for more than 10 minutes?
_________________
Lutz

Report Map Errors here:
TomTom/TeleAtlas NAVTEQ

[CAA_0821145133]

Stationary : YES, but the app stopped sending warnings long before that
(at least 1 hr before I stopped)


Once I resumed my journey, the app started working again after a few of hours (despite screen being off)


So not quite sure what's going on there ...

[lbendlin]

Not sure what to suggest (apart from the non-productive "get another car").

Is it feasible to use the phone speaker instead of Bluetooth?
_________________
Lutz

Report Map Errors here:
TomTom/TeleAtlas NAVTEQ

[CAA_0821145133]

I have given up on the bluetooth.

But the main issue at the moment is that CamerAlert does not seem to work reliably in the background (stops working after 15-30 minutes)

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!