You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device (phone) brand: HTC
Device (phone) model: Perspire. Err. Inspire.
Android OS version:
App version: A2.1 or main: Main
What steps will reproduce the problem?
1. Installing
2. Starting Service
3. Getting into my Vehicle (2011 Ford F250 with Ford SYNC)
What is the expected output? What do you see instead?
I expected the bluetooth volume to go to the set level (level 15). When it
didn't happen, I looked at my phone and saw that (the application closed
unexpectedly.
Please provide any additional information below.
Great concept. I know its hard getting everything working on all the
manufacturers phones but get this working and I would be happy to pay for it.
Thanks!
Keith
Original issue reported on code.google.com by ruthe...@gmail.com on 22 Feb 2011 at 6:28
The text was updated successfully, but these errors were encountered:
Sorry for the delays response.
I have tested one some HTC devices but have not yet had this problem. Did this
happen more than once? Is it happening consistently? Are you on Android 2.2
or higher?
When you installed the app, did you set up your truck in the list? Does it
show in the bluetooth device list in my app? Do you use a task killer? Did
the task killer kill it? Was there a "force close" error on the screen? Are
you using the notify icon feature in my app? I have used the app with Ford
Sync (great system) in the past.
Since I made it open source I can't ever charge for it.
Original comment by JimR...@gmail.com on 9 Apr 2011 at 1:54
I have added several robustness improvements to 1.4.3 that I hope will fix this
issue. Make sure you always send a crash report if it crashes and gives you
that option. Also, make sure your task killer is not killing this app. If the
problem persists, submit a new issue with as many details as you can.
Original comment by JimR...@gmail.com on 22 Apr 2011 at 2:30
Original issue reported on code.google.com by
ruthe...@gmail.com
on 22 Feb 2011 at 6:28The text was updated successfully, but these errors were encountered: