Bluetooth and Verizon LGVX8300
Bluetooth and Verizon LGVX8300
We are about to upgrade our current phones and have a G35S with Nav on order to be received in July. Does anybody have an LGVX8300 phone and paired it with the G35? If so, were there any problems with connection and transferring contacts? We like the LGVX8300 for several reasons but before we commit, we would like to know other member's experience.
Thanks,
PrairieG35.
Thanks,
PrairieG35.
I think most new(er) devices don't have any quality problems, and pairing it might not be an issue.
The only big deal would be address book transfer, but if the phone supports OBEX push then you should be alright. I know with my previous 2 blackberries I had no problems making calls but I couldn't transfer the address book, but now that I have a T-Mobile 8800 it works just fine.
FWIW, the address book thing is a mess though... you can't call from the downloaded address book on the move (the car won't let you), so I've ended up barely using it and just dialing from the phone's address book anyway. I don't wanna set up the voicetags because of the problems some people have had losing them.
The only big deal would be address book transfer, but if the phone supports OBEX push then you should be alright. I know with my previous 2 blackberries I had no problems making calls but I couldn't transfer the address book, but now that I have a T-Mobile 8800 it works just fine.
FWIW, the address book thing is a mess though... you can't call from the downloaded address book on the move (the car won't let you), so I've ended up barely using it and just dialing from the phone's address book anyway. I don't wanna set up the voicetags because of the problems some people have had losing them.
mine works fine almost always. Twice it did not find my phone and i had to synch it again and the other time i turned my phone off and then back on again. I had more difficulty after i also paired my wife's phone. It has a hard time deciding which phone to pick up.
Joined: Feb 2006
Posts: 13,068
Likes: 101
From: Southern Cali --> 818
I have an LG VX8600 and it works perfectly fine on my 06 G35 Coupe.
I'm assuming your phone should work on the 07 Sedan, since it uses the same bluetooth functionality as my 8600.
.
I'm assuming your phone should work on the 07 Sedan, since it uses the same bluetooth functionality as my 8600.
.
I have the 8300 and have had no problems with it and my G (same as what you are looking at G35S w/nav. Contacts have to be transfered 1 at a time, but no issues. Good luck!
Originally Posted by PrairieG35
We are about to upgrade our current phones and have a G35S with Nav on order to be received in July. Does anybody have an LGVX8300 phone and paired it with the G35? If so, were there any problems with connection and transferring contacts? We like the LGVX8300 for several reasons but before we commit, we would like to know other member's experience.
Thanks,
PrairieG35.
Thanks,
PrairieG35.
yea...phone works fine...i have three phones hooked up to it, with priorities...mine being first...haha...only bad part of the phone is you cannot transfer all contacts at once...which is odd because i also have a handheld gps in my other car and the contancts automatically transfer based on whoes phone is paired with it...but all in all...no problems
Trending Topics
Well, after doing some research, I found out that Verizon disables the OBEX function on all of their phones. OBEX is the function that allows file transfers to computers, auto BT kits, etc. The Infiniti use the XANAVI (Hitachi) BT-Kit. This kit is compatible with phonebook transfers from several phones but not those that have had the OBEX function disabled. The reason that Verizon has done this is they want users to pay for transferring pictures, music, etc. through their Get-It-Now service. The only phone that can be hacked to restore the OBEX capability is the Motorola RAZR V3. You need to go to a web site like Howards Forum to find out how to do this. Needless to say, I may end up switching to T-Mobile and get one of their phones.
Originally Posted by PrairieG35
Well, after doing some research, I found out that Verizon disables the OBEX function on all of their phones. OBEX is the function that allows file transfers to computers, auto BT kits, etc. The Infiniti use the XANAVI (Hitachi) BT-Kit. This kit is compatible with phonebook transfers from several phones but not those that have had the OBEX function disabled. The reason that Verizon has done this is they want users to pay for transferring pictures, music, etc. through their Get-It-Now service. The only phone that can be hacked to restore the OBEX capability is the Motorola RAZR V3. You need to go to a web site like Howards Forum to find out how to do this. Needless to say, I may end up switching to T-Mobile and get one of their phones.
According to the data on the car presented on my Samsung SPH-A640 (Sprint) the car ('07 G35 Journey w/Nav) supports only the OPP and HFP profiles. OPP is a subset of OBEX and may or may not be crippled by your carrier.
The G35 doesn't recognize the vCard format so any name in the phone will have its first word transposed with the others. And since the keyboard function in the car can't edit, you get a sort by lastname (or whatever's after the first word in the phonebook's text entry) unless you backspace out the entire name and re-enter it. What a pita.
I don't know about anyone else's phone but the Bluetooth Info page in the car returns Poor for the connection quality if I have the phone in my left pocket or driver's armrest. It reads Good from the dash down the console to the middle of the back seat. And sometimes it won't find it and I have to cycle power, dunno why.
Seems the Hitatchi BT setup isn't fully compliant or manages the RF link very well within the cabin. But at least it works, after a fashion. I'm changing over to Sprint's Voice Command to eliminate dependence on the car's limited voicetag supported phonebook and its disabling of the downloaded phonebook while driving.
Oh yeah, and the download went well after getting rid of unsupported characters but about a fourth of the contacts in the phone didn't make it nor will they transfer one at a time. Any attempt is met with loss of the BT connection when the enter button on the Infiniti controller is clicked to OK a transfer.
FWIW, Pete
The G35 doesn't recognize the vCard format so any name in the phone will have its first word transposed with the others. And since the keyboard function in the car can't edit, you get a sort by lastname (or whatever's after the first word in the phonebook's text entry) unless you backspace out the entire name and re-enter it. What a pita.
I don't know about anyone else's phone but the Bluetooth Info page in the car returns Poor for the connection quality if I have the phone in my left pocket or driver's armrest. It reads Good from the dash down the console to the middle of the back seat. And sometimes it won't find it and I have to cycle power, dunno why.
Seems the Hitatchi BT setup isn't fully compliant or manages the RF link very well within the cabin. But at least it works, after a fashion. I'm changing over to Sprint's Voice Command to eliminate dependence on the car's limited voicetag supported phonebook and its disabling of the downloaded phonebook while driving.
Oh yeah, and the download went well after getting rid of unsupported characters but about a fourth of the contacts in the phone didn't make it nor will they transfer one at a time. Any attempt is met with loss of the BT connection when the enter button on the Infiniti controller is clicked to OK a transfer.
FWIW, Pete
Srry, one more issue with the G's BT implementation.
A significant portion of the time, but less than 50%, the first call made works with the exception that outbound audio doesn't exist, like I'm on mute but which hasn't been activated. Works the second time whether I hit redial on the car's display or dial another number. Never had it screw up on two calls in a row or any call other than the first. Not sure if it's the phone or the car but I haven't had it happen with a Jawbone BT headset so I'm leaning toward the latter.
Anyone else seen this kind of problem?
FWIW, Pete
A significant portion of the time, but less than 50%, the first call made works with the exception that outbound audio doesn't exist, like I'm on mute but which hasn't been activated. Works the second time whether I hit redial on the car's display or dial another number. Never had it screw up on two calls in a row or any call other than the first. Not sure if it's the phone or the car but I haven't had it happen with a Jawbone BT headset so I'm leaning toward the latter.
Anyone else seen this kind of problem?
FWIW, Pete
Thread
Thread Starter
Forum
Replies
Last Post
1Typhoon
Audio, Video & Electronics
9
Sep 25, 2015 08:45 PM
AuAltima3.5
Audio/Video/Electronics
4
Sep 13, 2015 11:48 AM
beevanhuynh
Audio, Video & Electronics
1
Jul 14, 2015 09:06 AM





