Closed GoogleCodeExporter closed 9 years ago
Thinking I may call it "Drive".
Original comment by JimR...@gmail.com
on 19 Apr 2013 at 10:59
I am rethinking the rename thing. Instead I will completely replace this app
with a new app I make from scratch. I have learned many things since I started
this app. Things I would do differently next time. Things that would make the
app perform better. Improvements that can be made to the GUI. I will probably
make a few more releases of A2DP Volume cleaning up issues and adding some of
the requested enhancements. After that it will just be in maintenance mode
until usage drops away. The new app will focus on enhancing the interaction of
the device with Bluetooth car systems for driving. The goal is to reduce
driver distraction while also leveraging the capabilities of the mobile device.
Please post some name ideas for the proposed app. If I don't hear anything I
think I will call it simply Drive.
Original comment by JimR...@gmail.com
on 21 Apr 2013 at 8:59
I just found this app, although it isn't directly what I was looking for, but
it seems like it will work great. I always lose (misplace) my bluetooth
headset. I will go for days before I find it again. Sometimes I leave it at
work, or in my gym bag, in a pair of pants, who knows. My problem is that with
so many places to look, I often don't know where to start or focus. What I am
hoping is that this will allow me to pinpoint where I should look for my
headset. Even knowing that the last place I had a connection was at home is
helpful, because that tells me I didn't leave it on the table at the restaurant
I was at.
So, I think you could actually create a totally independent 'product' with that
focus, using what you already have developed. I would call it 'BT tracker' or
'Bluetooth Tracker'.
Good luck!
Original comment by becker.t...@gmail.com
on 20 Jun 2013 at 7:30
I think I will give up on the name change. I am not in this for money and I
make none from it so why try to expand usage?
Original comment by JimR...@gmail.com
on 25 Dec 2013 at 9:44
Original issue reported on code.google.com by
JimR...@gmail.com
on 19 Apr 2013 at 12:37