[GUIDE] How to install Internal GPS Module

Search This thread

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
Having installed the hardware and not killing the Gtab we want to see if the GPS hardware will get a lock. Where do we install/place the needed libgps.so?

We are running VEGAn-Tab. Thanx
Gwyneth

duh!
found it in /system/lib

Yep, sorry I do need to add that location to the tutorial. Also rajeevvp, I still haven't gotten around to testing that last version out yet. Sorry about the wait.
 

rajeevvp

Senior Member
Aug 20, 2010
1,315
406
Bangalore
Last edited:
  • Like
Reactions: fosser2

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
Quick update. I tried the newest honeycomb version gpsfix with Flashback a5.4. On boot, GPS still started up. Next I upgraded to Flashback a5.5 (newest). I first did a data wipe and everything. Then I installed GPS fix (newest). Basically it is still doing the exact same thing as before. On startup for like 2 min, the GPS will turn on randomly then shut back off. Maps turns on and off the GPS like it should. If I go into control panel and disable GPS and then re-enable it GPS will NOT turn back on (although the framework detects that it is enabled). So basically it is doing exactly what it did before. I will post a new logcat when I find more time. Sorry, life has just been really hectic lately.
 

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
Oh, rats! Looks like I'll have to load Flashback to check this out.
I'll have to replace their 1.2 kernel with a 1.1 one and then load it. I'll keep this job for the weekend, if you don't mind.

Totally fine with me. I've been really busy too. At the moment I am making a new logcat for you to look through. I will post it in a few minutes.

EDIT: Deleted... gps.conf seems to be tied to the startup issue...

EDIT2: On another note, unchecking GPS in settings then rechecking it still is not working properly. Once unchecked GPS is "dead" until a reboot.

EDIT3: Crap, I guess I lied about the first edit. It worked for a bit, but for some reason it started doing the same thing again... grrrr.
 
Last edited:

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
Alright, sorry it took me so long to post this. Below you will find the updated logcat.txt that is fully complete with everything that you previously asked for. I'm pretty sure that it is a full logcat and nothing was cut out. To do this logcat, I sat outside so I would get a lock extremely fast. I also had gps.conf edited properly to obtain the fastest fix using the program FasterFix from the Android Market. I'm pretty sure that GPS is still starting up on initial boot, but because I was sitting outside I didn't even see it start up. Basically what I have noticed with the GPS automatically starting on startup is that if the GPS locks right away it will turn back off quickly. If it does not lock it will continue to scan for satellites until it times out (I have no idea the "time-out time.") I am wondering if maybe this is programmed into Honeycomb to do this. Like if Google programmed it into the software so that after startup the GPS would only have to do a "warm" start if used again in the same session. (it was just a guess :p) Then again, maybe it is just a glitch. Also note that in the logcat I went through the GPS on/off bug in the settings. That should be towards the end of the logcat. Rajeevvp, I hope that this information can help you somewhat. Thanks again for all your help.

-Andrew

PS: I was wondering why you are using a 1.1 kernel for HC. Why can't you just use the 1.2 kernel?
 

Attachments

  • logcat.zip
    62.6 KB · Views: 5
Last edited:

rajeevvp

Senior Member
Aug 20, 2010
1,315
406
Bangalore
EDIT2: On another note, unchecking GPS in settings then rechecking it still is not working properly. Once unchecked GPS is "dead" until a reboot.
I just looked at the log files and... you're using an old version of the Honeycomb GPS fix zip file. Get the latest test version from this post, then try that test again. Don't forget to logcat.
 
Last edited:

rajeevvp

Senior Member
Aug 20, 2010
1,315
406
Bangalore
Below you will find the updated logcat.txt that is fully complete with everything that you previously asked for.
...
I am wondering if maybe this is programmed into Honeycomb to do this. Like if Google programmed it into the software so that after startup the GPS would only have to do a "warm" start if used again in the same session. (it was just a guess :p)
I can't make out anything unusual in that logcat--everything looks pretty normal. The GPS is started only because something is using it:

Code:
07-21 06:00:22.179 I/ActivityManager( 1024): Start proc com.google.android.apps.maps:NetworkLocationService for service com.google.android.apps.maps/com.google.android.location.internal.server.NetworkLocationService: pid=2318 uid=10024 gids={3003, 1015}
...
07-21 06:00:22.848 D/NlpVersionInfo( 2318): com.google.android.location not found
07-21 06:00:23.258 D/CountryDetectorService( 1024): The first listener is added

I'm going to call this something specific to Flashback (or whatever it was derived from).
 
  • Like
Reactions: fosser2

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
I can't make out anything unusual in that logcat--everything looks pretty normal. The GPS is started only because something is using it:

Code:
07-21 06:00:22.179 I/ActivityManager( 1024): Start proc com.google.android.apps.maps:NetworkLocationService for service com.google.android.apps.maps/com.google.android.location.internal.server.NetworkLocationService: pid=2318 uid=10024 gids={3003, 1015}
...
07-21 06:00:22.848 D/NlpVersionInfo( 2318): com.google.android.location not found
07-21 06:00:23.258 D/CountryDetectorService( 1024): The first listener is added

I'm going to call this something specific to Flashback (or whatever it was derived from).

Hmm, thats weird. Maybe I'll try sending a PM to the maker of Flashback.
 

sharshas

Member
Jan 7, 2009
26
1
USA
I Have old Megallan Roadmate 700 which I'm not using any more, any chance that I can use the GPS module from GPS in GTablet? just exploring the possibility...
 

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
I Have old Megallan Roadmate 700 which I'm not using any more, any chance that I can use the GPS module from GPS in GTablet? just exploring the possibility...

You would have to find a hardware breakdown of the device. Most likely you could get it to work, but since the pinouts on the chips would probably be different you would have the same problem John did and the GPS would not fit into the tablet.
 

BuckeyBall

Member
Oct 21, 2010
15
26
Hi there guys, MrGuy from TabletRoms again.

So - it turns out the GB/HC interface was the same huh? That's great news for us :) Since us Adam users never had a decent libgps.so even for froyo, I've gone ahead and written a GPS library for the Adam to use without the wrapper. Considering how similar the Gtab and Adam are, you could no doubt use almost the same module to get a native library for your device too (Perhaps it needs just a different tty port define?).

It's up to you whether you use it or not, but I thought if you wanted to customize things a bit - It'd give you a great start point!

Source code is at GitHub.
 
  • Like
Reactions: rajeevvp

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
Hi there guys, MrGuy from TabletRoms again.

So - it turns out the GB/HC interface was the same huh? That's great news for us :) Since us Adam users never had a decent libgps.so even for froyo, I've gone ahead and written a GPS library for the Adam to use without the wrapper. Considering how similar the Gtab and Adam are, you could no doubt use almost the same module to get a native library for your device too (Perhaps it needs just a different tty port define?).

It's up to you whether you use it or not, but I thought if you wanted to customize things a bit - It'd give you a great start point!

Source code is at GitHub.

My guess is that the port is the same. I mean we did use the libgps.so file from the Adam to get ours working. Thats the funny thing, the Adam libgps.so file has actually worked very well on the G-Tablet. I was kind of wondering why Adam users were complaining about it...
 

BuckeyBall

Member
Oct 21, 2010
15
26
My guess is that the port is the same. I mean we did use the libgps.so file from the Adam to get ours working. Thats the funny thing, the Adam libgps.so file has actually worked very well on the G-Tablet. I was kind of wondering why Adam users were complaining about it...

That's odd. Maybe you're using a libgps from a newer NI version that worked? As far as I can remember the libgps.so never actually 'locked' on the GPS signals. It always said it saw x satellites and occasionally returned a position - but never indicated that it ever had a locked signal. This means things like Google Navigation never worked.

Edit: Here's an example I found on youtube:
 
Last edited:

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
MrGuy, one last question for now. What is the difference between your HC gps for Adamcomb and rajeevvp's? I understand that you made the libgps.so file but was there any other difference?
 

BuckeyBall

Member
Oct 21, 2010
15
26
MrGuy, one last question for now. What is the difference between your HC gps for Adamcomb and rajeevvp's? I understand that you made the libgps.so file but was there any other difference?

Well, as I understand it - the solution proposed here is a wrapper implementation. Basically, it allowed the newer HC interface to plug into the old libgps.so. This is a completely different and direct implementation of the newer HC/GB interface without using a file names libgps.so at all (rather gps.tegra.so).

I suppose the main advantage would be the complete source availability of the whole module rather then using the closed source libgps.so. I imagine the overhead for the wrapper would be minimal, so there's probably not any CPU or memory benefit. Overall it means if there's an issue that crops up - you can fix it using the available source code and in my opinion the solution is neater :)

EDIT: I of course don't mean any disrespect to the work here. Both solutions work just fine and rajeevvp along with yourself have definitely done a great job getting it sorted.
 
Last edited:

sharshas

Member
Jan 7, 2009
26
1
USA
You would have to find a hardware breakdown of the device. Most likely you could get it to work, but since the pinouts on the chips would probably be different you would have the same problem John did and the GPS would not fit into the tablet.
Hmm... I guessed it. Let me breakdown the hardware and try to match the pins. Not hoping it to work, but if it works then its bonus...

Will update. Thanks fosser :)
 

fosser2

Senior Member
Apr 14, 2011
833
463
Wisconsin
Well, as I understand it - the solution proposed here is a wrapper implementation. Basically, it allowed the newer HC interface to plug into the old libgps.so. This is a completely different and direct implementation of the newer HC/GB interface without using a file names libgps.so at all (rather gps.tegra.so).

I suppose the main advantage would be the complete source availability of the whole module rather then using the closed source libgps.so. I imagine the overhead for the wrapper would be minimal, so there's probably not any CPU or memory benefit. Overall it means if there's an issue that crops up - you can fix it using the available source code and in my opinion the solution is neater :)

EDIT: I of course don't mean any disrespect to the work here. Both solutions work just fine and rajeevvp along with yourself have definitely done a great job getting it sorted.

The only difference us G-Tabbers need for this to work is a "1" needed to be written to /sys/devices/platform/gps_control/enable. This "1" physically powers on the GPS chip in the G-Tablet. The Adam does not have this feature and their chip is "always on." MrGuy, I tried out your GPS files that I ripped out of AdamComb 0.3. Everything works G-Tablet side aside from enabling the GPS. I did verify that you were pulling data from "ttyHS3" and it was defined in gpslib.c
 

Top Liked Posts

  • There are no posts matching your filters.
  • 31
    Official Tutorial

    Ok, here is the tutorial that people have been waiting for. It is not a complete finished work of art and will have changes made to is as discoveries are made.

    Disclaimer: Please do not attempt this project unless you really understand the risks of soldering onto a circuit board. This could end up frying your G-Tablet if you are not careful and I take no responsibility if anything bad happens to your tablet.

    That said, this has been a very enjoyable project and greatly improves the usability of the G-Tablet. If you have the balls to do this, I think this mod is very useful.

    Parts List: (thanks to twistedrotors)
    *U28 GPS Module - RXM-GPS-SG-B-ND http://search.digikey.com/scripts/D...g=en&site=us&keywords=RXM-GPS-SG-B-ND&x=0&y=0

    *U29 5vdc VCC Reg - NCP551SN33T1GOSCT-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=NCP551SN33T1GOSCT-ND
    C348 - U29 In to GND (0.1 uf 0402) - 445-3445-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-3445-1-ND
    C349 - U29 Out to GND (1.0 uf 0402) - 445-4978-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-4978-1-ND

    ̶U̶2̶2̶ ̶3̶.̶3̶v̶d̶c̶ ̶B̶k̶p̶b̶a̶t̶t̶ ̶R̶e̶g̶ - ̶M̶C̶P̶1̶7̶0̶0̶T̶1̶8̶0̶2̶E̶T̶T̶C̶T̶-̶N̶D̶ http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=MCP1700T1802ETTCT-ND (This part does not work. I have tried in 2 tablets now and it just makes the tablet not boot. Just jumper this location.)
    C347 - U22 Out to GND (1.0 uf 0402) - 445-4978-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-4978-1-ND
    C355 - U22 In to GND (1.0 uf 0402) - 445-4978-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-4978-1-ND

    *L11 Ferrite Bead - 445-2171-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-2171-1-ND
    (This ferrite bead is the one that I am using. There have been a few different ones recommended in this post including this one also (240-2391-1-ND. Mine seems to function the proper way.)

    *U34 Voltage Level Translator - 296-21978-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=296-21978-1-ND
    R302 – (1k ohm 0201) - P1.0KAGCT-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=P1.0KAGCT-ND
    C273 – (0.1 uf 0201) - 445-4711-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-4711-1-ND
    C272 – (0.1 uf 0201) - 445-4711-1-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=445-4711-1-ND

    *ANT2 Antenna Connector U.FL - H9161CT-ND http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=H9161CT-ND

    *ANT Antenna (Active) - 931-1014-ND http://search.digikey.com/scripts/D...&lang=en&site=us&keywords=931-1014-ND&x=0&y=0

    Parts that are needed have an "*" in front of them. Most of the capacitors and resistors are not needed but "should" be there because thats how the company intended. I personally, have not used any of them :p .

    Non-Digi-Key Supplies:
    Flux: http://www.radioshack.com/product/index.jsp?productId=2049774
    LED: http://www.radioshack.com/product/index.jsp?productId=3496417
    Multimeter: http://www.amazon.com/Equus-3310-Ha...EXWA/ref=sr_1_6?ie=UTF8&qid=1306286612&sr=8-6


    Step 0: Please remember where things go while you take apart your tablet. This is not a tutorial explaining to take out specific screws and put them back. Common sense is needed in doing this mod. :p

    (ok, onto the good stuff :D)
    Step 1: Remove tablet backing.
    This is done by using a small screwdriver to pry out the 4 rubber pads on the backside of the tablet. If done properly they should not scuff or make marks. After these are out 4 screws will be exposed, remove those with a phillips head screwdriver. Next near the dock connector (bottom of the tablet) slide a credit card in the slot where the plastic on the tablet comes together. There are 3 clips holding the plastic backing per side so, sliding the credit card around the tablet should pop them out of place. Do this with your tablet face down. If done sucessfully, the tablet should pop apart. You should see something like the following.
    With just the tablet backing off, you should be able to solder most components just like this (excluding the chip on the backside).

    Step 2: Pre-solder the pads.
    This is how I started off my project. UNPLUG THE BATTERY BEFORE SOLDERING. When soldering components onto the board it was nice to have pre-solder already layed on the board. If there is a better way to do this let me know, but this method is what I used. For starters use a pencil eraser to clean off the pads that you will be soldering. This makes the surface as clean as possible to solder on. Next each pad has to be soldered. To do this flux the areas that will have solder applied to them. Then put solder on the tip of your iron. Quickly touch the points that components will be soldered to (do not overheat). You will notice solder flow from the tip of the iron onto the pad. Do not put too much solder on the pads. Below is a picture of the board and the blue areas are where "pre-solder" should be applied.

    Step 3: Solder on GPS Chip (RXM-GPS-SG-B-ND)
    I figure since this is the biggie of the project why not start with it :p Take the GPS chip and align it in the proper orientation. Here is how the chip should sit.
    Once you have the chip alligned, flux one side of the chip and apply some more flux on the board. Put more solder on the tip of your iron and quickly run it along one edge of your chip. If done properly, the pre-solder should "flow" onto the chip. The added solder on your gun should ensure a secure connection. If the solder does not flow perfectly touch off on each pin to ensure they are connected to the board properly. After you finish one side do the same to the other side of the chip. After all 22 solder points have been secured to the board, pull out your handy-dandy multimeter and switch it to the ohm setting. Verify that all points are properly connected.

    Step 4: Solder on Antenna Connector (H9161CT-ND)
    Below is the orientation that this connector should be soldered on. It is a pretty self-explanatory. As for the soldering it is done pretty much the same way as the GPS Chip. Flux the edges of the antenna connector and re-flux the area where the antenna goes. With a bit of solder on the end of the iron, tap each point and watch the solder flow onto the connector. After done, verify that points are connected with your multimeter. All three of the blue points are ground and the yellow is hot.

    Step 5: Solder on Ferrite Bead (445-2171-1-ND - Or whatever ferrite bead you choose)
    So what exactly is a ferrite bead? This small component blocks any "bad" signals coming back from the antenna due to the antenna being powered. This part is tougher to solder on because it is ridiculously small. Again like the other solder points, re-flux the points being solder. Using a tweezers (trust me, you need them) hold the chip in place and solder down one end quickly. After the end is soldered down push down on the top of the chip with the tweezers and solder the other end. If all goes well, this should stick fine. In the picture below the yellow represents where the chip will be sitting once solder in. It is in location (L11). Once the chip is in, use your multimeter to test the chip. On the picture touch your multimeter to the two blue dots. If you have a connection with no resistance (or very little) you should be fine. If you do not have a connection, go back and re-solder.

    Step 6: Solder in 5vdc VCC Regulator (NCP551SN33T1GOSCT-ND)
    This chip directly controls the GPS turning on and off when you enter a program like "Google Maps" or "Google Navigation" on your tablet. This chip will save the battery life greatly, by shutting off the gps when you are not using it (very helpful :p) Again, flux the area to be solder and flux the pins on the chip. Using tweezers set the chip in the correct location on the board (pretty hard to mess this up). Solder down 1 pin per side to hold the chip down the proceed to solder the last 3 pins. The 5 pins that need to be soldered down are marked in yellow.
    Minus the jumper here is what yours should look like so far:

    Step 7:̶ ̶S̶o̶l̶d̶e̶r̶ ̶i̶n̶ ̶3̶.̶3̶v̶d̶c̶ ̶B̶k̶p̶b̶a̶t̶t̶ ̶R̶e̶g̶u̶l̶a̶t̶o̶r̶ ̶(̶M̶C̶P̶1̶7̶0̶0̶T̶1̶8̶0̶2̶E̶T̶T̶C̶T̶-̶N̶D̶)̶
    This chip provides power to pin 11 of the GPS chip. It is used for a "Backup Battery" power supply. Apparently there is no battery :p but for the chip to work, this still needs power. Now this component is not required. Proper function of VBACKUP can be achieved by just using a jumper. As seen in the above picture I am using a jumper. The picture below on the left shows the 3 points to solder to put the chip in. The picture below on the right shows the location to jumper. Just use a small piece of wire to complete jumper circuit. On a side note: I did try to put in this chip but for some reason my tablet would not start up when I had it soldered in. I have no idea why (possibly a faulty chip?) Other people have looked over the chip datasheet and say it should work though so that's why I kept it in this tutorial.
    EDIT Just use the jumper in this step. I have tried 2 different 3.3vdc chips in 2 different tablets now. It causes the tablet not to boot at all. Just jumper this location.

    Step 8: Flip the mainboard over
    I am not going to go into detail about how to do this because it's not too hard. I figure if you are inside of the tablet already you probably have an idea of how to do this :p Disconnect all wires from mainboard and unscrew all screws. There should be about 8 of them (screws). Once you do that pull the board out and set it on a level surface. Make sure you have yourself grounded because of static electricity. Once the board is out, flip it over and it should look somewhat like this.

    Step 9: Locate and pre-solder last chip location
    Just like you did on the front side, last chip location and presolder the 8 points for the chip and the 2 points for the jumper/resistor.

    Step 10: Solder in Voltage Level Translator (296-21978-1-ND)
    This chip is used to pass serial data from the GPS chip to the Tegra2 processor. If it is not in, the GPS will NOT be detected by the tablet. Using a tweezers put the chip in the correct orientation. (There should be writing on this chip, if you look at the chip directly below this location (U32) the writing should be in the same orientation [should line up]) Solder this chip in as you have the last few. At location R302 a jumper or resistor (P1.0KAGCT-ND) has to be added. This location is power for the "enable" pin on this chip. Use a wire for a jumper or the resistor. Test locations with multimeter to ensure proper connection (and so you do not have to remove your board again :p ) Here's what it should look like.
    (ya ya ya, I know this soldering job looks like crap but it works right? :p )

    Step 11: Optional LED Indicator Light
    If you have been reading through this thread you will know that I installed an LED indicator light to show then my GPS chip had obtained a signal lock. This is easy to install. From pin 7 on the GPS chip run a wire and connect is to the positive lead on an LED. Attach the negative lead either to a ground location on the board, or even easier, just attach it under a screw on the case. Take a look at my picture to see how I hooked mine up. After the LED is in place drill a small hole through the top of your case so you can see it blinking even with the case backing on.

    Step 12: Reassemble the tablet
    At this point in the tutorial choose whether or not you want to use the antenna tutorial. If yes, jump to that tutorial if not...Reverse all steps for breaking down tablet. Put it back together and cross fingers while pushing power button :p (I would recommend making this antenna modification; the signal is much better)

    Step 13: Go to the bottom of this page and read the portion entitled "Software Installation." It will give you the steps needed to get things working software side.


    Official Antenna Tutorial:

    The antenna is a critical component of this project because it is tough to sometimes get a satellite lock with the back case on. For those of you who have been following this project the other location for the antenna works but not as well. I would recommend this spot if you are installing this into your system.

    Step 0: Please remember where things came from, screws, wires, etc. It will make your life much easier. Not all of my pictures will be able to explain where things are supposed to go back to.

    Step 1: Take motherboard and battery completely out of tablet.
    After this is done, your table should look like the following. (for some reason my tablet looked a bit different when opened up, but you get the gist)

    Step 2: Remove metal bracket
    This part is easy, just make sure the cords are out of the way. Just remove approx. 8 screws from the frame and it just lifts right off. Here is a pic of what it should then look like.

    Step 3: This is where things get interesting.
    At the top of the bottom section there is a screw hole which has to be removed. You can use any method of removal that you want but here is what I did. First take a screwdriver and pry the metal "screw thread" out of the plastic housing around it. Next use a pair of needle nose pliers to pull up as much plastic that was holding the "screw thread" in as possible. To finish it off use a razor blade to cut flush, the rest of where the "screw thread" was located. It's kinda hard to put this in words but pictures should do this justice.


    (This is the completed image)

    Step 4: Modify metal bracket.
    This part is actually pretty easy and may not even be required. I only did it to gain as much space for the antenna to do its job as possible. I would recommend doing this. As you can see in the "before and after" pictures below a tab on the bracket needs to be ground off. This tab was not screwed into my tablet in any such way, so it's not like it mattered. To remove the tab get creative :p . I used a grinding wheel, but I'm sure that you could use a hacksaw or any other method. Take a look at the below pics and you'll understand better :D

    Before:


    After:


    Step 5: Put the GPS antenna in.
    Put the GPS antenna in the location that you just cleared out. You will have to remove a corner of the foam that is holding the camera down (not really a big deal). Put the chip in and if you choose you can secure an edge using any method of your choosing (just so it doesn't move) I used a tiny piece of sticky tack. Look at a few of the images below to figure out antenna orientation. It is pretty easy to see.

    Step 6: Put it back together.
    Reverse everything that you just did taking it apart. If you did it properly, you should have an antenna mounted as pictured below. It gets better reception and is probably the best location in the tablet for this antenna.


    I hope that this helps out those who are having trouble finding a "good" location for their antennas. Post any questions that you have about this. I would be glad to help you out.

    Battery Use:
    • The tablet gets about 8 hours and 5 minutes of battery life while in a GPS application (pretty solid time!). The entire time the screen was on and the satellites were locked. I did turn wi-fi off during this test. Since this will be used during driving I did not feel like wi-fi was necessary to be turned on. If someone else wants to post results with wi-fi enabled, be my guest. I will update accordingly.

    Data Connection:
    • This is kind of a bummer when it comes to this tablet. Since the G-Tablet does not have a 3G card built into it, programs like "Google Maps" and "Google Navigation" have issues working. These programs need an Active Data Connection and since the G-Tablet only has WI-FI these programs do not operate like they should. The good news is that there are other programs out there that do not need an active data connection to operate. I am currently using a program called CoPilot Live 8. This program relies on pre-stored maps in the tablet to run. It works very well and I would recommend it for use on the G-Tablet. Here is a link to the software page. http://www.alk.com/copilot/

    ROMS Tested
    • GPS is now fully functional in all latest Android distributions (Froyo, Gingerbread & Honeycomb)
    • VEGAn-Tab 5.1.1 (1.1 based ROM) - Works
    • GtabComb - Works
    • Flashback - Works
    • CyanogenMod 7.1.x - Works
    • All of the above I personally tried
    • Brillant Corners 1.2.1 (1.2 based ROM) - Works
    • MrGuy over at TabletRoms re-coded and released source code for "libgps.so" which is now "gps.harmony.so" in Gingerbread and Honeycomb. Rajeevvp took his latest file and ported it to the G-Tablet. If you are on Honeycomb and want to mess around with it here is the installer link to get GPS working on HC. (This method is more for developers that want source code to see how things work) If anyone wants to dig deeper into how the Honeycomb GPS works here is a link to the source code that MrGuy released. For the average user just stick to the following post on how to install GPS normally.

    Software Installation
    • Rajeevvp put together an "update.zip" for all firmware distributions. To use visit the following page and select the firmware version that you have (froyo, gingerbread or honeycomb). Install the "update.zip" via ClockworkMod like you would install any other updates. The "update.zip patches your current install files to enable GPS functionality. After install reboot your tablet and enjoy native GPS. If rajeevvp posts any updated versions of installers, he will always add the new ones to the above post.

    Thanks: Special thanks for the following users twistedrotors and rajeevvp. Without their help this project would not be close to finished.
    13
    UPDATE 5/26/2011: I have put together a tutorial and will keep it updated. It can be found at this link. http://xdaforums.com/showpost.php?p=14111386&postcount=207 The project is not fully completed but working! Keep following us as we progress through this thread.


    Ok, I’ve been digging around recently and have been getting nowhere. From a bunch of emails and PM’s that took me a long time to write, I have gotten nothing back. So I am starting a new thread here.

    I am in the process of finding info on the internal GPS module that the G-Pad is capable of having installed. I am willing to use my tablet as a demo to see if I can get it working! If it works, I will make a detailed thread on how to go about installing a GPS module into the G-Tablet. So speak up if you know your electronics please!!! :p

    What I have compiled so far

    A member from XDA forums literally bought a kit (eBay Post) that enabled GPS use. He posted that the chip that he installed was a RXM-GPS-SG-B found at this link (http://search.digikey.com/scripts/DkSearch/dksus.dll?lang=en&site=US&KeyWords=RXM-GPS-SG-B&x=0&y=0). After looking at the data sheet for this chip I’m pretty sure that this chip will work on the G-tablet board. All of the pins line up properly and everything. In the XDA post that I read, after the install of the chip he posted “I now have power to the chip and its working. When I click on the place app now it no longer just says wait but comes up with aps where to go.” This is a good sign in that it is already enabled in the VS bootloader kernel. Basically if you can get it soldered in and enabled it should work. The problem is that he claimed that pin 12 (vcc) did not have power and he had to power it from another source. He claimed that he tapped into the USB +5v power. That would have worked ok if the GPS chip needed 5v power. The chip itself needs 3.3v of power. This user was overvolting his GPS chip from the get-go. He had reported some issues with it and I think that this overvolting was part of the problem.

    Here is a picture of the installed chip via the XDA forums. Sorry for the smallness it was as big as I could find. http://xdaforums.com/attachment.php?attachmentid=585865&stc=1&d=1304460793

    My theory is that you can tap into the 3.3v pin that is located on the mini PCI e headers and use this for power. This will provide the correct voltage. Here is a picture of the empty spots on the board. http://xdaforums.com/attachment.php?attachmentid=585866&d=1304460792

    As you can see in the picture above there is an “empty” power circuit located below where the GPS chip would reside. I read a post on XDA that claimed that if properly hooked up correctly it would probably produce the 3.3v output needed for the GPS chip also. The items that the user claimed could possible make it work were as follows.
    I do not have enough knowledge about IC’s to know how these are used. If anyone has an idea let me know. They go in the power circuit somehow.

    The next part is the antenna connector. This would get installed in the empty “ANT2” connector. This should be an easy mount and is exactly how “ANT1” the wifi antenna is connected. http://xdaforums.com/attachment.php?attachmentid=585863&d=1304460740
    Finally onto the antenna itself. Although I have read that a passive antenna can be hooked up to this chip, an active antenna seems like it would get much better reception. The antenna that I have read a lot about is the following.
    This antenna would literally just snap onto the antenna 2 connector and it should work. Now to run an active antenna the GPS data sheet says that a 300ohm ferrite bead needs to be installed. This is the part where the member at XDA also messed up. He wired an antenna with a 300ohm resistor thinking it worked the same as a ferrite bead. A ferrite bead basically reduces any interference coming from the antenna going to the chip. Here is a link to the proper ferrite bead.
    The ferrite bead is also where I have run into problems. I do not know how to properly install one of these and I have no idea if there is even a spot on the board to do so. Any help in this area would also be appreciated. http://xdaforums.com/attachment.php?attachmentid=585873&stc=1&d=1304461146

    The antenna should be able to fit in the plastic up at the top of the case while also providing ample reception.

    After all of this is installed hopefully the GPS chip will work. Although this sounds like a complicated project there is not actually that much soldering to do. The main GPS chip is actually most of the soldering. I am hoping that someone reads and appreciates that work that I have compiled/done so far. Any help on this project would be greatly appreciated. Also please do not post “why don’t you just use an external Bluetooth module.” I get that these work great, but I just want to see if the internal GPS will function. Attached below is everything I could possibly obtain after browsing through the entire internet looking for any type of documentation on this project :p Thanks for taking time to read through this post.

    Last Thoughts

    References
    Thanks to the following people from XDA
    • mystkrh
    • 6.055chevy
    • vsc
    • also to anyone I missed sorry
    4
    AHHHHHHHH IT WORKS!!!!!!!!!!!!!! REPLACE THE "libgps.so" FILE FROM THE NORTON ADAM INK AND IT GOES!

    HERE IS THE FILE!

    EDIT: ok sorry for the freakout (I'm just really happy :p ). The gps does now work like it is supposed to. Google Maps and Google Navigation both function like they should. I will be messing around w/ other programs in a bit here. Thank you to everyone who has devoted time to this project.

    EDIT2: In the next few days I will be writing a tutorial complete with pictures and such on how to install one of these in a G-Tablet. I'm sure for all of those that have been following this thread you will be very happy.
    3
    Here is a modified version of BlueGPS4droid in order to read NMEA data from a file.
    Instead of giving the name of a bluetooth device you have to give the path of a file. It's working with plain files so I hope it will also work with /dev/ttyHS3.

    You will still have to start the GPS manually (echo command).
    You should be able to see on the logcat if it recognizes NMEA sentences or not.
    If you can post a copy of the logcat it could be usefull for me.

    If it's working, we should be able to integrate the echo command later and clean the code...

    For the source code, the simplest option could be to have a git repository somewhere (github/google code/sourceforge as you want), so we all could modify the code.

    So how to use it :
    1) enable GPS (don't know if you can)
    2) start internalGPS4GTab
    3) choose a NMEA device (device path: ako /dev/ttyHS3)
    4) eventually activate "auto-enable location provider" in "location provider options"
    5) start the reading service using the start checkbox
    6) start GPS using the echo command
    look if something happens in the locat...

    PS : I don't know if you should use the echo command after or before starting the GPS app... perhaps you could try both.
    2
    Do you have any info re: the communication protocol used with the GPS module? Do you have to, for instance, send a command string to get it to start or stop sending the GPS co-ords? Or does it just keep spitting the stuff out as soon as it is enabled electrically? What's the frequency of the co-ordinate update?

    The module spits out GPS data as soon as it gets 3.3vdc. The data is sent out on its UART I/O port every 1 second. No start or stop command is necessary. There is both a TX and RX pin. TX has the GPS output data on it and RX can be used for config settings and firmware upgrades. I have not needed to change any settings (baud rate, etc.) so my RX pin is not hooked up. The data output is in NMEA output protocol V.3.00 (I'm not sure what this means, I just pulled it from the data sheet).
    I am using an Arduino (with the microcontroller removed) as a serial UART->USB adapter and power supply for the module.
    My module is pretty similar to Fossers, the big exception is that mine has an integrated antenna. The output data and voltage levels all appear to be virtually identical between our two modules.
    This is fun! :D
    -John

    P.S. - Here's the link to the module I have, if anyone finds this interesting. http://www.cutedigi.com/product_info.php?cPath=248&products_id=4289