| Autor |
Nachricht |
nissangold86
Anmeldedatum: 18.11.2012
Beiträge: 3
|
 Verfasst am:
So Nov 18, 2012 11:21 |
  |
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. |
|
|
   |
|
amrs
Anmeldedatum: 22.11.2012
Beiträge: 5
|
| Verfasst am:
Do Nov 22, 2012 12:09 |
|
I have the same problem with my Galaxy Nexus after the update to JB 4.2. Well, at least USB cable works. |
|
|
|
|
TON
Anmeldedatum: 16.11.2012
Beiträge: 2
|
| Verfasst am:
Fr Nov 23, 2012 08:49 |
|
|
|
|
arno
Anmeldedatum: 03.10.2012
Beiträge: 10
|
| Verfasst am:
Fr Nov 23, 2012 11:11 |
|
The same here on samsung galaxy nexus.
But I think this is not a problem of myphoneexplorer! |
|
|
|
|
TheLandYacht
Anmeldedatum: 09.06.2011
Beiträge: 143
|
| Verfasst am:
Fr Nov 23, 2012 21:58 |
|
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. |
|
|
|
|
nissangold86
Anmeldedatum: 18.11.2012
Beiträge: 3
|
| Verfasst am:
Mi Nov 28, 2012 11:30 |
|
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. |
|
|
|
|
FJ
Site Admin
Anmeldedatum: 15.02.2006
Beiträge: 31898
Wohnort: Tirol
|
| Verfasst am:
Do Dez 06, 2012 22:50 |
|
@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. |
_________________
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.
Bitte benutzt auch die Forum-Suche bzw. die FAQ |
|
 |
|
Krutzi
Anmeldedatum: 02.01.2011
Beiträge: 3
|
| Verfasst am:
Di Dez 11, 2012 10:52 |
|
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. |
|
|
|
|
user_deleted
Gast
|
| Verfasst am:
Di Dez 11, 2012 12:42 |
|
| Krutzi hat Folgendes 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... |
|
|
|
|
amrs
Anmeldedatum: 22.11.2012
Beiträge: 5
|
| Verfasst am:
Do Dez 13, 2012 14:12 |
|
| FJ hat Folgendes 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? |
|
|
|
|
user_deleted
Gast
|
| Verfasst am:
Do Dez 13, 2012 16:54 |
|
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... |
|
|
|
|
spile
Anmeldedatum: 27.10.2010
Beiträge: 134
|
| Verfasst am:
Mo Jan 21, 2013 15:39 |
|
| Krutzi hat Folgendes 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. |
|
|
|
|
epp_b
Anmeldedatum: 04.06.2012
Beiträge: 19
|
| Verfasst am:
Mi Feb 06, 2013 17:46 |
|
|
|
|
Mandos
Anmeldedatum: 14.02.2013
Beiträge: 1
Wohnort: Darmstadt
|
| Verfasst am:
Do Feb 14, 2013 11:00 |
|
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. |
|
|
|
|
|
|
