search

Omeya / a2dpvolume

Automatically exported from code.google.com/p/a2dpvolume
0 stars 0 forks source link

location does not store or retrieve on Galaxy S #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Volume works fine.  Detect connect and disconnect fine.  Spawns location 
listener fine.  However clicking stored location always shows "no data".  Both 
long and short press produce the same result.  Works fine on motorola, htc, and 
other samsung models.  This issue has been the cause of every poor rating of 
this app.

Original issue reported on code.google.com by JimR...@gmail.com on 19 Dec 2010 at 7:08

GoogleCodeExporter commented 9 years ago 
I could use some help with this.  I need an early Galaxy S phone for 
troubleshooting.  The issue appears to be only with Samsung Galaxy.  Those 
devices don't appear to have satellite GPS.  They appear to use only cellular.  
However, that should still work since my app first catches the last known 
location, then looks for a better one.  Also, the galaxy devices are still on 
Android 2.1.  Maybe something with 2.1 not working right.

Original comment by JimR...@gmail.com on 20 Dec 2010 at 2:30

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
After more investigation it appears that Samsung has a problem with very slow 
location updates.  The device will store a location sometimes but often it is a 
very stale location.  Users should set the "GPS listener timeout" to 45s in the 
A2DP Volume app preferences.  Also make sure your location services are all 
running.  It's best to enable all sources.  Use the settings in Android, 
location and security settings. Make sure all the location sources are enabled. 
 Samsung devices don't appear to have satellite based GPS.  The only have the 
cellular based GPS which is far less accurate.  

It is also possible for A2DP Volume to be kicked out of memory by other apps 
and services.  To prevent this, enable the "notify in foreground".  This will 
keep the service always running.  Generally it is the most important to know 
where you parked when you are in an unfamiliar place, one that you likely used 
navigation to get to.  

Another thing that should help is to have an application that requests location 
updates often open.  For instance, if you have navigation open the device will 
be getting more frequent updates.  A2DP Volume will also have access to those 
updates.  

I made a release today to try to help Samsung devices.  The new release 1.3.4 
(and 1.3.4.1 of the A2.1 version) also enables a network listener instead of 
just the GPS listener.  Please let me know if this helps.

Original comment by JimR...@gmail.com on 25 Dec 2010 at 5:59

GoogleCodeExporter commented 9 years ago 
I looked into this more.  It seems many are having problems with Samsung 
devices not calling the location update functions.  This means that it either 
does not find a location fast enough, or it just does not ever call the 
function.  Some mentioned taking over 2 minutes to get a location update.  Here 
is one of the threads: http://developerlife.com/tutorials/?p=1375
My changes today added all 3 listeners to the main version of the app.  
Unfortunately Android 2.1 does not support the passive service so the A2.1 
version of this app does not have it.  A2DP Volume starts by grabbing the best 
location from any source, then spawns the GPS listener looking for a better 
one.  On Droid it would usually find a great satellite GPS location in a few 
seconds.  If the device does not have satellite GPS, then this listener is 
never called so that first location capture is all you get and that is often 
not very good or not even available.  Adding the new location providers should 
really fix this issue.  Users of devices that update the location slower should 
try using a longer listener timeout setting in A2DP volume.  It can be set as 
high as 45s.  I thought about adding a 1 minute configuration but that is just 
too long to be useful.  Often the bluetooth takes a few seconds to disconnect, 
then the listener is called.  Even the 45s setting is a bit long.  You could be 
quite a way from the vehicle by then.

I really need feedback on the improvements here.   Especially anyone with a 
Samsung phone.  Please respond to this issue with any info good or bad.  Thanks.

Original comment by JimR...@gmail.com on 26 Dec 2010 at 3:18

GoogleCodeExporter commented 9 years ago 
Must have made some progress.  Just got this user feedback with a 5-start 
rating: Works execellent on the Galaxy!!!

Original comment by JimR...@gmail.com on 31 Dec 2010 at 1:44

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 10 Apr 2011 at 12:48