HopelessFantasy / openetna

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

AGPS does not work #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start Google maps
2. Select My Location
3.

What is the expected output? What do you see instead?
The GPS icon should show up. It does not. Its blank. Nor does it show location 
by GPS.

What version of the boot.img and system.img are you using?
System.img V4.1 and boot.img V1.2

Can you provide logcat output during that error?

Please provide any additional information below.

Original issue reported on code.google.com by cosmicbu...@gmail.com on 31 Jul 2010 at 1:07

GoogleCodeExporter commented 9 years ago
GPS Seems to work in the application 'GPS Status' but not in google maps.

Original comment by shept...@gmail.com on 8 Aug 2010 at 9:38

GoogleCodeExporter commented 9 years ago
Seems to work with 4.2

Original comment by 17floy...@gmail.com on 21 Aug 2010 at 9:08

GoogleCodeExporter commented 9 years ago
does not seem to work with google maps still.

Original comment by cosmicbu...@gmail.com on 21 Aug 2010 at 3:40

GoogleCodeExporter commented 9 years ago
I does work for me. So you do not even see the blinkin gps symbol? Did you 
enable GPS under settings? Try to disable and reenable that setting.

If that still does not work, please provide logcat for while opening google 
maps.

Original comment by polyth...@gmail.com on 21 Aug 2010 at 7:24

GoogleCodeExporter commented 9 years ago
It does work for me too.

Original comment by m.pluvin...@gmail.com on 21 Aug 2010 at 7:28

GoogleCodeExporter commented 9 years ago
It works now. A reflash did it for me.

Original comment by cosmicbu...@gmail.com on 22 Aug 2010 at 5:26

GoogleCodeExporter commented 9 years ago
doesn't work for me. I'll try a reflash

Original comment by elmagi...@gmail.com on 23 Aug 2010 at 4:01

GoogleCodeExporter commented 9 years ago
I use Gps Tonight and it take 20 min to have the first position, 
that's work, but, I think the first initialisation is very long

Original comment by cyril.po...@gmail.com on 25 Aug 2010 at 10:06

GoogleCodeExporter commented 9 years ago
If it takes a long time, then maybe AGPS is not working. But I did not have any 
issue with GPS beside that. And it usually takes 1 to 5 minutes for me

Original comment by polyth...@gmail.com on 26 Aug 2010 at 3:02

GoogleCodeExporter commented 9 years ago
What AGPS server is the phone supposed to contact? Is there some generic one or 
is it supposed to use an LG supplied server?

Anyone know if it's only downloading almanac and/or ephemeris data or also 
sending cell/tower/gps signal info to the server?

Whatever type of AGPS scheme used, it should easily (caching a few kB of data 
for a few hours) be possible to get a position within 10 seconds of turning on 
the receiver.

Original comment by h.n.erik...@gmail.com on 27 Aug 2010 at 9:37

GoogleCodeExporter commented 9 years ago
I do not have any clue. One may look at the deodexed framework from 
korean-v10t. But I do not even know how AGPS is supposed to work, so someone 
with a bit more expertise may look into that.

Original comment by polyth...@gmail.com on 27 Aug 2010 at 3:32

GoogleCodeExporter commented 9 years ago

Original comment by polyth...@gmail.com on 1 Sep 2010 at 3:30

GoogleCodeExporter commented 9 years ago

Original comment by polyth...@gmail.com on 2 Sep 2010 at 11:16

GoogleCodeExporter commented 9 years ago
It works very fast for me, but I seems to need a working mobile data connection.
Even if I'm on wifi, it will shortly establish a 3g connection on activiation 
of gps, and then I have a fix after about one minute.

I have did some changes to the GPS subsystem, so maybe something did the trick. 
It will be included in the next version.

Original comment by polyth...@gmail.com on 3 Sep 2010 at 8:21

GoogleCodeExporter commented 9 years ago
I think that this is fixed in 4.3. But you have to have a working APN setting. 
(no APNdroid or something like this activated) as it uses/establishes a 3G 
connection to get some supplemental data.

Original comment by polyth...@gmail.com on 7 Sep 2010 at 3:33

GoogleCodeExporter commented 9 years ago
I wonder how we can know if the phone is using standard GPS or AGPS.

Is there a way i can confirm for real that AGPS is now working properly ?

Original comment by Tetsuo6...@gmail.com on 12 Oct 2010 at 8:46

GoogleCodeExporter commented 9 years ago
One may want to toggle 
config_gps_xtra_download_on_boot
in device/lg/eve/overlay/frameworks/base/core/res/res/values/config.xml
to see if that has any positive or negative influence.

Original comment by polyth...@gmail.com on 12 Oct 2010 at 12:41

GoogleCodeExporter commented 9 years ago
as of 6-rc5 the GPS still does not work. opening google maps provides only cell 
tower localization. The GPS icon does not show up. If gps is disabled and then 
reenabled, opening google maps shows the icon but it constantly flashing and 
does not provide refined location info.

Original comment by jonathan...@gmail.com on 20 Oct 2010 at 6:34

GoogleCodeExporter commented 9 years ago
With 6.1-rc1 (and 6-rc6), I must disable and after enable the GPS for it 
works... If my phone is stolen, I can't located it !

Sorry for my english.

Original comment by maxgenil...@gmail.com on 24 Oct 2010 at 2:09

GoogleCodeExporter commented 9 years ago
I can confirm what maxgenilloud says.

Original comment by vandewal...@gmail.com on 24 Oct 2010 at 3:05

GoogleCodeExporter commented 9 years ago
Can you confirm that it works or just turns on. For me it seems like it comes 
on but never gets a fix.

Original comment by jonathan...@gmail.com on 24 Oct 2010 at 5:56

GoogleCodeExporter commented 9 years ago
For me it turns on and after some minutes (like 2 or 3 minutes) it gets a fix.

Original comment by trysta...@gmail.com on 25 Oct 2010 at 2:20

GoogleCodeExporter commented 9 years ago
6.1-rc2, doesn't work. Only turns on. I have been waiting for 20 minutes on the 
rooftop and didn't get signal.

Original comment by emiron...@gmail.com on 28 Oct 2010 at 4:56

GoogleCodeExporter commented 9 years ago
I agree with emironoff. In sattelites 0/10 appears but location can not be 
determined. Some times it works.

Original comment by iareh...@gmail.com on 29 Oct 2010 at 4:24

GoogleCodeExporter commented 9 years ago
I can confirm that the GPS isn`t working i`m trying to get some logs and post 
it here.

Original comment by Vinnie...@gmail.com on 29 Oct 2010 at 9:53

GoogleCodeExporter commented 9 years ago
By moments AGPS works (Usually about one day after the flash of the new 6 
release, the google meteo widget, wich seems to use AGPS, starts locating me 
without doing anything more ???)
GPS is really slow to fix. (in LG korean 1.6 it taked about 15 seconds, maybe 
less, but OpenEtna is so awesome that i can't revert to 1.6 now !!!)

Original comment by aurelien...@gmail.com on 29 Oct 2010 at 10:02

GoogleCodeExporter commented 9 years ago
How is this confirmed fix? I flashed 6.1 rc 3 boot 2.4.1 and my gps is unable 
to locate me. do I need fastboot -w??

Original comment by iareh...@gmail.com on 1 Nov 2010 at 5:37

GoogleCodeExporter commented 9 years ago
Actually this does not seem to work. I'll have a look at the opensource drivers.

Original comment by polyth...@gmail.com on 1 Nov 2010 at 8:58

GoogleCodeExporter commented 9 years ago
Thanks to take care of us Polutheus :p
Does not work for me anymore (boot v2.4 & system v6.1 rc2)

Original comment by bourgeoi...@gmail.com on 4 Nov 2010 at 8:06

GoogleCodeExporter commented 9 years ago
I think GPS works. It's just very long to get an accurate position.
Hope AGPS could be fixed. It will seriously enhance the locating speed.

Original comment by Tetsuo6...@gmail.com on 4 Nov 2010 at 10:56

GoogleCodeExporter commented 9 years ago
Hi, I'm from Italy (we have a GW620 Forum) and I think I can confirm comment 
30, because one of our users has tried GPS (V. 6.1 RC3). It works, but Fix 
takes a long time.

Original comment by giuv...@gmail.com on 4 Nov 2010 at 11:28

GoogleCodeExporter commented 9 years ago
If you really think GPS can't find a position, sometime reseting GPS (with the 
widget) can make it work again.

Once the position is correct i found it to be quite accurate. Used google 
navigation for a 2h ride, and it was perfect. Except the fact that it emptied 
my battery from full to 0% in that lapse.

Original comment by Tetsuo6...@gmail.com on 4 Nov 2010 at 12:40

GoogleCodeExporter commented 9 years ago
Hello,

i have install GPS Status and before i start google maps i run it and the 
problem is solve. So the problem is related to the gps

Original comment by jcmedei...@gmail.com on 4 Nov 2010 at 2:24

GoogleCodeExporter commented 9 years ago
I had a play and got it working nicely with the open source drivers. This 
dropped about 4 proprietary libs from the Korean LG image. On a clean boot I 
get a fix in around 20 seconds, subsequent fixes (quite soon after) in as 
little as 2 seconds. Not had to enable/disable gps with the widgets first, 
worked every time for me from boot.

I've pushed the changes so anyone who wants to can have a play. Note: you'll 
probably want to clean out the proprietary libs from your build system to make 
sure you get a clean image, they are libgps.so, libloc_api.so, 
libloc_api-rpc.so & libcommondefs.so. Remove them from your extracted 
proprietary folder and anywhere you find them in the out folder (including 
system/lib, else they'll still end up flashed to the device even if they don't 
get used).

Richard.

Original comment by richarda...@gmail.com on 6 Nov 2010 at 2:13

GoogleCodeExporter commented 9 years ago
Wow, great! Do you need a working data connection to get the fast fix or not?

Original comment by saxand...@gmail.com on 6 Nov 2010 at 2:38

GoogleCodeExporter commented 9 years ago
I assume you need a connection to something to get a very fast fix. Don't know 
if this will also improve unaided offline fix times too.

Original comment by richarda...@gmail.com on 6 Nov 2010 at 2:43

GoogleCodeExporter commented 9 years ago
Sorry but I speak French and I didn't understand everything... I just must to 
delete all libgps.so, libloc_api.so, libloc_api-rpc.so and libcommondefs.so for 
the GPS works ?!

Original comment by maxgenil...@gmail.com on 6 Nov 2010 at 2:50

GoogleCodeExporter commented 9 years ago
No, you need to sync the repo and rebuild the system image (or at least parts 
of it). The bit about removing the old gps stuff was for cleaning up your build 
system before building the changes.

Original comment by richarda...@gmail.com on 6 Nov 2010 at 3:04

GoogleCodeExporter commented 9 years ago
As far as i know, AGPS needs wifi or 3G connection data to download location 
data the first time.

Original comment by caf...@gmail.com on 6 Nov 2010 at 3:33

GoogleCodeExporter commented 9 years ago
I tried to build the gps module and made make clean + deleted propietary stuff 
and ran extract-files.sh however i get the following error when issuing make:
build/core/base_rules.mk:128: *** hardware/qcom/gps/loc_api/libloc_api: 
MODULE.TARGET.SHARED_LIBRARIES.libloc_api already defined by 
hardware/msm7k/loc_api/libloc_api

Original comment by caf...@gmail.com on 6 Nov 2010 at 3:45

GoogleCodeExporter commented 9 years ago
Interesting, hardware qcom is the source of the opensource driver (I had to 
copy it to hardware/msm7k because we build for msm7k not qcom), but looks like 
it's trying to build both on yours. I'm not sure why though, mine doesn't. I'll 
have a look...

Original comment by richarda...@gmail.com on 6 Nov 2010 at 3:54

GoogleCodeExporter commented 9 years ago
Well after an hour it's still building, so I assume it's got further than yours 
did. I did a clean (hence the long build time) and a new extract, etc.

Original comment by richarda...@gmail.com on 6 Nov 2010 at 4:50

GoogleCodeExporter commented 9 years ago
Well, 2.5 hours later I have a complete build, from clean, without your error. 
Anyone else seeing this? The build I have installed on my phone is here 
http://dl.dropbox.com/u/5500141/system.img if anyone wants to try it.

Original comment by richarda...@gmail.com on 6 Nov 2010 at 6:14

GoogleCodeExporter commented 9 years ago
maybe you forgot to commit something? I had the same behaviour, deleting the 
gps folder inside qcom fixed it. I don't know if the right source is in msm7k 
or in qcom though...

Original comment by saxand...@gmail.com on 6 Nov 2010 at 6:46

GoogleCodeExporter commented 9 years ago
That would seem logical, but repo diff & repo status both come back clean. As 
for the code, either is fine, it's the same driver, as I said I had to copy it 
to get it to build (because on mine it doesn't do what it does on yours - yours 
is better). Are you sure there are no changes in your repo? Can anyone else out 
there try it?

Original comment by richarda...@gmail.com on 6 Nov 2010 at 7:00

GoogleCodeExporter commented 9 years ago
If either is fine I'll commit the removal from one of those places. I'll check 
what's the most common place for that code and keep it there...

Original comment by saxand...@gmail.com on 6 Nov 2010 at 7:11

GoogleCodeExporter commented 9 years ago
Either code is fine (i.e. it's the same code), problem is that the build system 
makes no attempt to compile the original version (in qcom) for me, but would 
for cafg10 (and so fails for him with a duplicate target error from make). What 
do you get saxando4u? Make error or working build?

Original comment by richarda...@gmail.com on 6 Nov 2010 at 7:15

GoogleCodeExporter commented 9 years ago
GPS Works fine, the only thing you need is to is to keep your phone in the open 
position as the keyboard then grabs the satellite signal almost immediately

Original comment by RafalHar...@gmail.com on 6 Nov 2010 at 8:09

GoogleCodeExporter commented 9 years ago
i get the same error as comment 40, this after a "make clean" and also after 
checking out again the whole repositories from scratch...

Original comment by skun...@gmail.com on 6 Nov 2010 at 8:21

GoogleCodeExporter commented 9 years ago
Very odd, I mean it might actually make sense, except for the fact that that's 
not how it works for me! Very odd indeed. Anyway, if this is what everyone is 
getting the answer is to remove dir hardware/msm7k/lib_loc and edit 
hardware/msm7k/Android.mk to remove remove loc_api from the end of the list of 
msm7k_dirs.

Then someone needs to suggest how to make my build system build the qcom 
version like everyone elses or I'll be the only person not able to build my 
change!

Original comment by richarda...@gmail.com on 6 Nov 2010 at 8:31