IssueTracker

The debugger always highlights the last line with code on it before returning from a method.  It doesn't actually execute the "return -1" in that case, even though it appears to do so.  Check the return value you get from the method.

what does Eclipse do if you debug the same code running on Sun's JVM?

If I try debug the same code in eclipse like normal Java application on Sun's JVM everything is OK, it work as I expect, problem is only if I debug android application.

yeah, if i run this on the RI i don't see the apparent step to "return -1" but on dalvik i do. looking at the dex file, it's obvious that dx has done this to us by compiling all three returns into one (instruction 0x7):

0001f4:                                        |[0001f4] HelloWorld.f:()I
000204: 1211                                   |0000: const/4 v1, #int 1 // #1
000206: 3a01 0900                              |0001: if-ltz v1, 000a // +0009
00020a: 1300 0a00                              |0003: const/16 v0, #int 10 // #a
00020e: 3d00 0300                              |0005: if-lez v0, 0008 // +0003
000212: 0f00                                   |0007: return v0
000214: 1200                                   |0008: const/4 v0, #int 0 // #0
000216: 28fe                                   |0009: goto 0007 // -0002
000218: 12f0                                   |000a: const/4 v0, #int -1 // #ff
00021a: 28fc                                   |000b: goto 0007 // -0004
      catches       : (none)
      positions     :
        0x0000 line=8
        0x0001 line=10
        0x0003 line=11
        0x0005 line=12
        0x0007 line=18
        0x0008 line=15
        0x000a line=18
      locals        :
        0x0005 - 0x0007 reg=0 count I
        0x0008 - 0x000a reg=0 count I
        0x0001 - 0x000c reg=1 row I

i'd guess the debug information for that instruction gets overwritten each time we compile a return, leaving us reporting the final return to the debugger. this is shit, and should be fixed, but sadly this isn't something i can fix in jdwp.

i've raised internal bug 36949180 for this.

same thing here, glad i'm not alone. :)

Does the bug also occur in Android Studio?

When will the bug be fixed??

dx still has this bug, but its replacement jack does not:

http://tools.android.com/tech-docs/jackandjill

as work on dx is effectively stopped, marking this obsolete.

[Comment deleted]

Just run into this issue today,
Tested it with Jack -> does not happen

since :
"The Jack toolchain is deprecated,"
https://developer.android.com/guide/platform/j8-jack.html
https://android-developers.googleblog.com/2017/03/future-of-java-8-language-feature.html

I cannot trust my tools now :(
will it be fixed?

I opened new report of this here
https://issuetracker.google.com/issues/38081065
5 year is quite long time :-(

It is very funny. Because of this issue is closed I created new one, which was closed like duplication of another one, which was closed as duplication of this one. Circle is finished :-(
I hope that somebody still working on it.

Tomáš is correct to highlight a silly circularity here; Jack is no longer the replacement so this seems like it should still be valid.

This has been fixed in the new Dexer of which we announced preview availability today: https://android-developers.googleblog.com/2017/08/next-generation-dex-compiler-now-in.html
Please give D8 a try and let us know your experience!

I tried to use D8 and the problem with debugger is really fixed.
I tried to use it also for one beta release of my app, I have just 200 beta testers
And one of them wrote me that he is not able to install this build.
He has Lenovo device with non oficial Cyanogen ROM:
Device: P70
romInfo: cm_P70-userdebug 5.1.1 LMY49J fd77b65ea8 test-keys
romFingerprint: Lenovo/cm_P70/P70:5.1.1/LMY49J/fd77b65ea8:userdebug/test-keys

So probably not a big deal, but I will just for sure wait before bigger release of this new D8.

Sorry to hear that, I'm guessing this is caused by https://issuetracker.google.com/issues/64740479

Yes, it was also error 504 during installing from Play

Hi! Please read the following discussion, especially message #4:
http://discussions.tomtom.com/t5/MySports-Connect/Lollipop-bluetooth-pairing-issue-unable-to-enter-the-passcode/td-p/955054

Hi,
Any updates about this issue ?

Hi,

I tried with Android 5.0.1, same issue. Seems like bugs are not fixed yet.

Ditto hear, was working fine in KitKat but now BLE devices requiring PIN bring up the dialog but there's no place to enter PIN and no way to get keyboard up.
Note Bluetooth Classic dialog in Lollipop does work correctly, dialog does have PIN entry field - this bug only affects BLE 4.0 devices.

I'm having the same problem with pairing my Nexus 5 to my 2014 Ford Fiesta Sync.
It asks for a Pin Entry but there is no Pin entry field.

we got stuck with our entire BLE product line. come on!!! are you trying to kill the market?

We have the same problem here on multiple devices.

Using Nexus 4 or 5 with KitKat 4.4.4, everything works fine. When try to establish connection to ble device with pin code authentication, the pin dialog is opened in android.

When we update the same devices to lollipop 5.0.1, nothing is working.  When try to establish connection to ble device with pin code authentication, only a toast with error appear. No dialog is shown.

I tried to pair a bluetooth keyboard on android 5.0.1. I got a pairing code, but nothing to enter it!!

moi aussi meme chose pas capapble de rentrer le code

Same problem as here: https://code.google.com/p/android/issues/detail?id=79668 . The system broadcasts BOND_STATE = BOND_BONDED even though it's not bonded and can't read encrypted characteristics.

I am also having this issue on my Nexus 5.

Hi - I am having the exact same issue on my Nexus 10 running lollipop when trying to pair with my brand new Bluetooth keyboard from Kensington. It gives a pin to pair the device but there is no where to enter the PIN! What is the status of this fix?

Nexus family of devices have this issue while it's not happening on Samsung Galaxy S5 and LG G3. Can't believe that this defect isn't triaged yet after more than 2 months.

Priority small? You've got to be joking!

Might have found a solution.

Encountered this issue today, working out for the first time since updating to Lollipop on my Samsung galaxy s5. I have the tomtom gps running watch, not the cardio version.

After 5min of messing with it, what worked was turning off bluetooth on my phone under the bluetooth settings (not from the quick menu, but from settings>bluetooth settings). I made sure the mysports app task was closed. I put my watch into flight mode. I then turned on my phone's bluetooth. Then I turned off flight mode on the watch, then choose to pair new on the watch. This time the watch showed the bluetooth symbol with a 7 or so digit pin code, that I entered on the pop up on the phone. Then I opened the mysports app, and the activity synced successfully.

In short: disabled phone BT > kill mysports app > flight mode ON on watch > phone BT ON > flight mode OFF on watch > pair new on watch > enter code > should sync

Upgrading to lollipop seems to confused paired devices and the phone, wanting to add the BT device as new but trying to try to sync as if recognized at the same time. So the pop-up BT menu on watch and phone keep trying to sync, so you have to get both devices to stop trying to communicate completely, then start the watch under pair new then get the phone to start. Once on the same page, with the pin code it newly-recognizes the device.

Hopefully this works for y'all.

Nope JJohnsto #32, as others have said, you do get the pincode popup on Samsung Galaxy S5. Google have removed the pincode popup on Nexus devices.

I have the same issue with a BT keyboard any my 2nd Gen Nexus 7 tablet, not way to enter the passcode that it displays.

Guys

I found a solution to my problem.

To pair the device, based on my understanding of the unclear instructions provided by the Android operating system -  I was waiting for a dialogue box to appear on the Nexus device so that I code put the code into the tablet BUT ...

what I was required to do was to key the code using the physical BT keyboard and push the <enter> button on the physical BT keyboard and the device paired.

Search on your Watch for a new Phone with bluetooth. then enter the code was shown on your Watch and it's working like before...good and bad....

please fix this issue prompto, thanks, user of Nexus 5 on Lollipop

Same problem here... TomTom multisports watch

I have this problem as well... Just bought the watch, too.  Has this problem really been constant since 3 months ago and no solution?!  How can Tomtom let it go that long without fixing it.  Clearly there's plenty of people with the issue.  I'd almost rather sending the watch back.. I bought it to use it, not wait for a solution to be found.

It's not at all TomTom's problem! Google in their wisdom decided to remove the pin code screen for nexus devices. Read the thread! People with devices other than the TomTom watch are having the same problem. Google doesn't give a crap. Enough to make you want to buy an iPhone.

We are developing and producing our own line of BLE devices and we're unable to pair it with Nexus on Android 5.x.x. But it works on LG G3 and probably would also work with Samsung S5 as someone mentioned before in this thread.

Why does this still have a 'Small' priority?

This seems to render whole swaths of devices unusable with Loli-Nexus phones/tablets.  Iwould think it warrants more attention, as well.

After doing HCI snooping, going through logs on Wireshark and Android code,
it was obvious that the problem is buried in depths of BT/BLE stack.

Nexus devices are declaring its IO capability on pairing request as
DisplayYesNo instead of KeyboardDisplay, which is the case with Samsung
Galaxy S5 and some other devices. I guess Samsung is using it's own BT
stack which handles this nicely while Google/Nexus is having it's own which
is causing those issues.

Since watch is declaring itself as DisplayOnly on pairing, Google's or
whoever's BT stack is the only place where fingers should be pointed at.

They've managed to fix most of the issues which were there from 4.3 (losing
LTK on disconnections, zombie paired devices, false true for GATT
operations return, etc...) but this just made it completely useless.

To be honest, this is one of the rare occasions where I must say "Well
done, Samsung!" and "Shame on you, Google".

After almost 6 months without even triaging this we did the job for you so
now you can finally FIX IT!!!!

Just to add on list of disappointments, Nexus 5 decides on it's own that just about 5 seconds after you reconnect to BLE device, it decides to clear the cache and render all services, characteristics and , especially, notifications useless.

Like it was hard to clear the cache on connection or before triggering onServicesDiscovered...

So, before I stop ranting about BLE and Android, this would be acceptable on JB, maybe even on KK but after so many updates, this is completely unacceptable and considered as complete fail.

We are building a BLE device and we plan to hit the market by late summer.  We are going to have a lot of upset Android customers who buy our gadget and can't use it.  We are getting close to punting on this and doing the iOS version first since 5.0 isn't ready and we haven't been told when it will be ready.

It seems that this issue has been resolved in Android 5.1 factory image for Nexus 5.

I can confirm that this is now working with my tomtom watch, on a nexus 5, with the 5.1 factory image.

That's great news!  Hopefully once all the countries start getting 5.1
pushed to their phones we can finally have closure on this issue!

Can you key the code into the Tom Tom watch and then push enter? I found
that Google is not expecting you to key the PIN into the Nexus device -
rather enter it into the physical device. See if this works...

--

*---------------------------------------------------------------------------------------------------*

*Richard Mackenzie*

Mobile:  0419 813 173

Email:  *richard.mackenzie@ncardia.com.au
<richard.mackenzie@ncardia.com.au>*

I can confirm, the issue seems to be resolved in android 5.1. Tested on Nexus 5 with factory image

https://dl.google.com/dl/android/aosp/hammerhead-lmy47d-factory-6c1ad81e.tgz

Same problem here, 5.0.1 on Moto G 1^ gen

Do exist any apps tha can help us ?

[Comment deleted]

Same problem on my Nexus 5, I'm expecting the update to 5.1 in order to get a fix for this bug.

http://officialandroid.blogspot.de/2015/03/android-51-unwrapping-new-lollipop.html

" ... Android 5.1 Lollipop also provides enhancements such as the ability to join Wi-Fi networks and control of your paired Bluetooth devices directly from Quick Settings. ..."

Anybody knows the release date for this update?

I side loaded mine and I'll try pairing again tomorrow.. I'll let you all
know how it goes. If what some people have said is true then I am hoping to
finally get my watch synced again to my Nexus 5.

Flashed the 5.1 image onto my Nexus 5. The issue seems to be fixed.

5.1 does fix the issue. If you can't wait for the update to come OTA sideload the update to your Nexus.

Why am i still having this issue then? Ny phone is updated and it will not allow me to enter in a passcode to my alpine stereo system on my nexus 5

Its updated to 5.01

#58, #59 dott...

You need 5.1, not 5.01

What's everyones thoughts on the recent updates from the tom tom app? This most recent update has fixed it for me now even though upgrading to 5.1 fixed  the pairing issue.

I updated to 5.1 and I am still seeing the issue. I am getting a pop up to enter the code. But there is no place to enter the code..

exactly the same : tomtom multisport and moto G 4G (1st gen) with lollipop 5.1 (OTA 1 week ago).
Anyway this pairing issue is at least 4 month old and happened also with kitkat. This issue appeared after tomtom mysport app update...but I don't remember exactly the version.

Guys use the physical Bluetooth to enter the number.

Hey guys, I made this work on my Nexus 5!

1. Go to your Bluetooth settings and add the watch this way
2. Go into the app, pair it as you would have before when it wouldn't let you enter a PIN
3. It should now bring up a screen within the app where you can enter the PIN
4. BOOM!

Worked for me. If anyone has any trouble fire me an e-mail at mcquid@gmail.com and I can try to walk you through it!

I just followed #65's instructions and it worked for me.

I followed #65's instructions but not successful.
Galaxy S4, CyanogenMod 12.1

Received the Marshmallow update (Android 6.0) for my Nexus 5 and Nexus 9 yesterday, but the bluetooth issue is still not fixed.
Both devices do not pair with my "Moto 360" Smartwatch.
I reset the Smartwatch to factory settings, but that also did not help.
Other device which require entering a passcode (radio in my car) do not pair too.
Devices which do not require entering a generated passcode (Headphone) do pair.

This issue seems to be an incompatibility with the TI 1.4.0 stack.  See https://e2e.ti.com/support/wireless_connectivity/f/538/t/457958

Need this fixed. I have 5.1, and there is still a problem with my Chromebook/Nexus 5.

Also, my problem is that when I try to pair, the pairing number shows up on both the Chromebook and the Nexus 5; but when I hit "accept" or otherwise show I want to complete, including typing in the number on the CB keyboard, it says it can't pair.

With the first Marshmallow Release my Nexus 5 did not connect (as said at #68).
Now I installed another update Abdroid 6.0 - Build MRA58N and the issue is fixed.
My Moto 360 connects again and my car radio does too.   :-)

Issue is not seen on latest android M build.
Please confirm the same.

This issue could not be reproduced in Marshmallow builds. At this point, our eng teams are not prioritizing changes on earlier releases. Please file a new bug if you encounter this issue on 6.0+.

I am having problem with cookoo 2 watch and nexus 5. I am running Android 6.0, anyone has the same issue ?

Same problem with Android 6. O. 1 on the Nexus 6p. Unable to connect to TomTom Spark! WAKE UP GOOGLE! this is inacceptable. I cannot believe this. It feels like 1998. Reason enough to revert back to iOS.

Same problem happened with Android 6.0.1 Nexus 5. Pairing window not generated. Only header showed "Pair with %1$s? " and Keyboard opens. But when I enter anything in Keyboard, nothing displays on screen. Please fix this problem as soon as possible

Note : This problem do not happen after once successfully pairing dialog displays with any other device

I don't understand why Google is creating problem with pairing by pin code. We must look for alternative android!

Same problem on Android 6.0.1 and Android 8.0.0, after more than 3 years...

I'm having this issue in 6.01 on my Xperia z3 compact. It won't pair automatically with headphones when I switch headphones on (incorrect pin or passed error) but if I go to More Settings in the Bluetooth menu my headphones are listed in the paired devices. If I longpress the headphone name I can then pair them.

I've tried unpaired / forgetting on phone and headphones, clearing Bluetooth cache on phone. But I can't get the autopair to work.