FJ Software

After upgrading my Nexus 7 to JB 4.2, my bluetooth service no longer, on Windows 7, shows the Nexus 7 COM port service to allow for bluethooth connection. My Android 2.3.4 phone is fine but not the nexus. This worked fine on version 4.1.2.

It would appear that the client 1.0.22 no longer works properly on the 4.2.

I have the same problem with my Galaxy Nexus after the update to JB 4.2. Well, at least USB cable works.

I have the same issue.

The same here on samsung galaxy nexus.
But I think this is not a problem of myphoneexplorer!

Well, at least this answers a question I was about to ask in a separate topic...that being, "Does MPE work with 4.1/4.2. Thanks for answering that.

The bluetooth doesn't matter to me because I've always connected via USB anyway.

I have not been able to get the USB to work with the Google Nexus 7, even if I have the debug turned on the USB connection. The nexus 7 automatically connects as a shared disk to the Windows 7, so the myphoneexplorer gives a USB not connected error.

@all: The bluetooth issue of 4.2 is known. It has to do with the new bluetooth stack which was changed from BlueZ to Broadcom. The issue is based on Android, currently its not possibe to fix it for me and i have also no workaround. I hope Google will fix it soon

@nissangold: Check if you have installed the adb drivers for your device. Take a look at the device manager.

I had the same problem with my new nexus 4.

After activating the usb debugging modus ("settings" --> "about you phone" and then tab 7 - 10 times on "Build Number". After that, you will see the "developer options" in the "settings" menu and can activate the debugging modus)

At last i installed the USB driver with comes with this programm http://junefabrics.com/android/download.php
and choosed "LG" as manufacturer.

Krutzi hat geschrieben:I had the same problem with my new nexus 4.

After activating the usb debugging modus ("settings" --> "about you phone" and then tab 7 - 10 times on "Build Number". After that, you will see the "developer options" in the "settings" menu and can activate the debugging modus)

At last i installed the USB driver with comes with this programm http://junefabrics.com/android/download.php
and choosed "LG" as manufacturer.

Yes, under 4.2(.1) this is right, but it does affect USB connections only,
not WLAN- or BT-connections.

best regards...

FJ hat geschrieben:@all: The bluetooth issue of 4.2 is known. It has to do with the new bluetooth stack which was changed from BlueZ to Broadcom. The issue is based on Android, currently its not possibe to fix it for me and i have also no workaround. I hope Google will fix it soon

Can we have a tiny bit of information as to what the problem is? Some profile missing from the new Bluetooth stack or?

Problem is, that MPE client needs to create a SPP service on smartphone side and this is not implemented yet in current version of Android's 4.2(.1) new BT stack.
SPP service is needed to have a virtual COM port over bluetooth to communicate with the interface.

best regards...

Krutzi hat geschrieben:I had the same problem with my new nexus 4.

After activating the usb debugging modus ("settings" --> "about you phone" and then tab 7 - 10 times on "Build Number". After that, you will see the "developer options" in the "settings" menu and can activate the debugging modus)

At last i installed the USB driver with comes with this programm http://junefabrics.com/android/download.php
and choosed "LG" as manufacturer.

Fantstic advice - many thanks for this.

I'm having the same issue with my Nexus 4. My old Android phone connected on bluetooth just fine, but the Nexus 4 won't.

Would this possibly have any effect?

https://play.google.com/store/apps/deta ... hSPP&hl=en

I just updated my Nexus 7 to Android 4.2.2 and tested Bluetooth. Good news: I got it to work, SPP service is available again.