I 'hijacked' this other thread:

http://www.blackberryforums.com/gps-...tml#post531029

But thought I should start a new one.

Basically, here is what we're talking about:

1. TeleNav 4.7 + 8100 + some pucks (specifically iBlue) don't work.

2. TeleNav 5.1 for the 8800 doesn't work on the 8100 because it only works with built in GPS.

3. I am trying to find out from TeleNav people when they will release 5.1 for the 4.2.1.x firmware.

4. I am thinking about switching to another GPS program if the issue isn't resolved soon.

5. I don't want to regress back to the 4.2.0.x firmware.

I'm not the only one in this situation.

Does anyone have any info on this?

Thanks,

--mobrien118

I don't know whether this helps, but I'm running Telenav 4.7 on my pearl with OS 4.2.1. It worked with the TIM OS, and now it's working with the new Rogers OS.

I have the Globalsat359 GPS puck.

I was the other 'hijacker' of that last thread, and I can attest to having the same problem. The Bluetooth connection between my Pearl and iBlue 737 simply won't stick when I use Telenav 4.7 and OS 4.2.1. I've tried everything--complete wipe of the handset between OS versions, deleting and re-pairing... nothing works.

I've switched to Mapquest Navigator for the time being, but I'd really like to use TeleNav.

when i spoke to telenav they said something to the effect that 5.1 is not supported for the pearl....probably because of differences in hardware between the 8800/8100.

currently 4.7 is what works on the pearl, and 5.1 on the 8800.

maybe one of the reasons it's taking a while is because there's different versions of OS out for the pearl. for example, if tmobile currently supports pearls with 4.2.0.64 and that version is holding telenav back from issuing new SW, then 4.7 is all that will work on it.

if telenav needs an updated OS in order to run it's software on tmobile phones, then that needs to be collaborated between those 2 companies so that tmobile issues and supports a newer OS.

likewise for other service providers.....

when people start modding their phones and upgrading OS's that are not 'officially' supported by their carriers, it starts causing messes like this.

i'm gonna wait it out and stick with 4.2.0.64 and telenav 4.7.....

WARNING: Rant to follow.

I'm going to have to disagree with you, just a bit. But also clarify what I have experienced. I have a little experience with this type of process, being a software engineer.

I agree that 5.1 doesn't work on the Pearl. I know because I installed it. The reason, however, that it didn't work is because the version of the 5.1 software for the 8800 (which I installed) expects a built in GPS unit. There is no option to connect to an external puck. Other "builds" of 5.1 have this option, though, because they have it out for other phones that need an external bluetooth receiver. Otherwise, hardware should be transparent to the application. This is the function of an operating system. Which brings up a question: What OS version are 8800 users using that is supported with TeleNav?

As I noted above, 5.1 works on the Pearl, just can't connect to an external GPS.

This is very possible, that is why we are requesting 5.1 for the 4.2.1.x firmware/OS. I will restate the question: What OS version are 8800 users using that is supported with TeleNav?

I believe that they should work with RIM. RIM writes the OS fluidly. Service Providers pick up a particular version (probably built bi-weekly, from what I've seen) and integrate and test it. Meanwhile, RIM keeps developing/bugfixing/feature adding. TeleNav should have known that this major OS update was coming and been ready with updates to their software. I'd imagine that BlackBerry users are a large constituent of their customers.

Thanks for saying that I am causing a mess. Sooner of later (most likely sooner) T-Mobile is going to roll out some flavor of 4.2.1.x and then a lot of TeleNav users are going to be upset. The way I see it, I am an early adopter and a whistle blower. My discovery and reporting on this issue might put TeleNav in a better position to address the issue and have a fix in place by the time tmobile does release their update.

After saying all that, I would like to add that I think that the inherent problem is caused by a problem with the OS and the hardware. I say this because some people are not having a problem. The people who are having the problem are using the iBlue pucks with the 4.2.1.x firmware. Since the problem didn't occur until we upgraded the firmware, the problem is most likely a bug in the firmware/OS that only manifests itself when used in conjunction with the TeleNav software. So, if TeleNav wants to keep customers, they should find a workaround or use leverage to get RIM to fix the problem. Either way, both TeleNav and RIM have a vested interest in fixing the problem. TeleNav is in a tough market position because most of their competitors offer a one time payment pricing schedule, which means that once they switch, they ain't coming back. This means that they stand to lose more (harder) if a widespread bug affects their user base.

So, again, if anyone has any info/workarounds/fixes/information that it IS working on your setup (maybe your puck just happens to work with the new firmware), please post.

Thanks for reading,

--mobrien118

being a whistle-blower can be good, but it can also be bad, and the reason is that not all folks who are active in upgrading/updating the software for their phones are as coherent/inclined as you or someone else who's savvy in this stuff.

so when they say something and they sound like they are on the ball, when in fact they missed something (that was specific to their setup) or just goof and make the mistake of incorrectly stating the facts....then that throws others off.

my post was my speculations, i guess i should have noted so on the post, and for what it's worth it's good that you replied to my post because it sheds more insight into what i (as well as others) don't quite know or understand completely....

out of all this mess....i just want to have a setup that's got the minimum number of bugs....
this is why i decided to stick with the recommended SW so that i don't wind up with a problematic phone and time to fix it.

I am using 4.2.1.90, but I want 4.2 since it has A2DP.

I use Telenav 4.7 on a Tmobile 8700g and an iBlue gps puck. I upgraded to the 4.2 chinese being talked about in the 8700 general forums. I could not maintain a connection to my iBlue puck either. Sometimes it would last 15 minutes or more, other times less than a mile. I tried this repeatedly over 2 days. I downgraded back to the Cingular 8700 firmware, and my gps connection is stable again.

Personally, I figure it was my problem since the combination of device, carrier, OS, and telenav wasn't supported by anyone.

I'm not going to get into the whole argument of who should be getting their stuff ready for the next release of everybody else's stuff, I just wanted to confirm that I had the same issue maintaining a bluetooth connection between telenav and my iBlue after upgrading to 4.2

I'm having the same issue, and the bluetooth connection drops out in all the programs (BBmaps, Google Maps, TeleNav). Didn't try Mapquest, but I'd assume it's the same.

Thanks. You are helping verify that it is an OS related problem.

What type of puck are you using?

Thanks,

--mobrien118

I have an i-Blue 747, which is the same chipset as the 737, but has GPS logging capabilities.

I've had problems with my BT dropping out. When I close TN and exit to the home screen the BT icon still shows it's connected and I have to turn off BT and turn it back on and then go back into TN to get it to work again. I can't confirm but it seems like it happens when the BB is tasked too hard and/or low on memory. it works better if Google Talk is closed and not running in the background. Also, the more memory free, the better it works.

Yeah, my problem is exactly as you described, John. What puck are you using?

Has anyone with an 8700 tried this with 4.2.1.141 yet? I actually am not travelling this week, which is rare, so I'm thinking about giving it a shot around town.

This isn't going to surprise anyone, but I got the same behavior with 4.2.1.141

What puck are you using?

Just for the record, I've downgraded to T-Mobile's 4.2.0.64, and it works great. I'm debating returning my puck while I can and getting a SiRFstarIII one instead while my return period is still valid...

i-Blue PS-3200

Kewl. Me 2. I posted a poll to try to narrow down exactly where the problem is.

Check it out:

http://www.blackberryforums.com/gps-...you-using.html

--mobrien118

After a short period of time, my bluetooth GPS adapter (Holux) will disconnect and Telenav will say "trying to connect to Bluetooth device", but... The blackberry itself says its connected to a bluetooth device (on home screen it shows the bluetooth icon with the arrows)...

Is this a blackberry OS problem, Telenav, or the GPS adapter hardware not working properly? Thanks!

This is the same problem we're having.

It looks like it is a problem with the GPS device that only manifests itself through the 4.2.1.x BlackBerry software.

--mobrien118