Unable to set up Boron LTE

ScruffR · December 14, 2018, 6:52am

You probably haven’t got a DFU driver installed or your device is not flashing yellow.

paul.io · December 14, 2018, 3:10pm

Yes, it’s in listening mode flashing yellow. With Electron I can run dfu-util -l and it detects the device. In the Control Panel I see libusbK Devices / Electron DFU Mode. If I connect Boron and put it in listening nothing happens.

ScruffR · December 14, 2018, 3:21pm

Listening Mode would be blinking blue.
Blinkin yellow is DFU Mode.

That is because the libusbK driver was assigned to be applied on Electrons in DFU Mode, but that assignment has obviously not been made for Boron in DFU Mode, so you need to do that.

I found the easiest way to do that in Windows is zadig.

paul.io · December 15, 2018, 5:55am

Installing Zadig and registering USB drivers for Boron with it helped. I was able to flash it and then pair and activate it. Thanks!

cairn · December 16, 2018, 8:15pm

Success!!! I was able to pair with the Boron after flashing the hybrid-0.8.0-rc.26-boron.bin firmware over USB and verifying that the Nexus 6 was using app version 2.3.8. After pairing, I was able to get through the following steps to set up the cell connection and the mesh network. Thanks to all who helped out with troubleshooting this!

al.bertorio · December 17, 2018, 5:28pm

I’ve been flashing my Boron with new firmware hybrid-0.8.0-rc.26-boron.bin through Particle CLI and still cannot pairing with my phone.
I’ve following all of the alternative solutions in this thread and still stuck. I use LG K8 Android 6.0.1. Is it because of my phone?

ScruffR · December 17, 2018, 5:34pm

Could be or the settings/permissions for the app on your phone.
One thing recently turned up to be blocking other users. The app needs to have permission to acquire your location and location and BT scanning has to be turned on too.

ninjatill · December 17, 2018, 6:19pm

The new version of the Android Particle app has a debug log built in. I would try to run through the setup and after you can’t pair, dump the log and send it to support. You can find the log in the top-right of the screen where you see three little dots (next to the magnifying glass “search” button). You could post the log here but I only took a brief look at what it contained (not sure if it’s sensitive data or not) and I’m not sure anyone here will understand the logs anyways.

al.bertorio · December 18, 2018, 8:37am

This is the app debug log after I try to pair my argon with my phone for about 5 minutes.
I cannot really understand the log. Anyone can help me?

--------- beginning of system
12-18 15:23:18.005 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_DOWN
12-18 15:23:18.078 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_UP
12-18 15:24:19.537 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_DOWN
12-18 15:24:19.666 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_UP
--------- beginning of main
12-18 15:24:19.791 D/PhoneWindowEx( 7879): [PWEx][generateLayout] setLGNavigationBarColor : colors=0xff000000
12-18 15:24:19.791 I/PhoneWindow( 7879): [setLGNavigationBarColor] color=0x ff000000
12-18 15:24:19.805 D/PhoneWindow( 7879): notifyNavigationBarColor, color=0x: ff000000, token: android.view.ViewRootImplAO$WEx@1bd3362
12-18 15:24:19.887 V/ViewRootImpl( 7879): Contents drawing finished : io.particle.android.app/io.particle.mesh.setup.ui.MeshSetupActivity
12-18 15:24:20.860 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_DOWN
12-18 15:24:20.941 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_UP
12-18 15:24:21.050 I/FirebasePerformance( 7879): Session ID - 8cd270dfb12d4ebd8d91a2bbe86dbc5a
12-18 15:24:21.063 V/SoftAPConfigRemover( 7879): reenableWifiNetworks()
12-18 15:24:21.181 I/Timeline( 7879): Timeline: Activity_idle id: android.os.BinderProxy@6b3cee1 time:100647834
12-18 15:24:21.183 I/io.particle.mesh.common.android.livedata.ClearValueOnInactiveLiveData( 7879): LD deactivated, clearing value
12-18 15:24:21.183 I/io.particle.mesh.common.android.livedata.ClearValueOnInactiveLiveData( 7879): LD deactivated, clearing value
12-18 15:24:21.211 I/io.particle.mesh.setup.ui.FlowManagerAccessModel( 7879): onCleared()
12-18 15:24:21.211 I/io.particle.mesh.setup.ui.FlowManagerAccessModel( 7879): onCleared()
12-18 15:24:21.217 I/io.particle.mesh.setup.flow.FlowManager( 7879): clearState()
12-18 15:24:21.217 I/io.particle.mesh.setup.flow.FlowManager( 7879): clearState()
12-18 15:24:21.231 I/io.particle.mesh.setup.flow.modules.cloudconnection.BoronSteps( 7879): clearState()
12-18 15:24:21.232 I/io.particle.mesh.setup.flow.modules.cloudconnection.BoronSteps( 7879): clearState()
12-18 15:24:21.951 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_DOWN
12-18 15:24:22.049 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_UP
12-18 15:24:22.101 I/ListPopupWindow( 7879): Could not find method setEpicenterBounds(Rect) on PopupWindow. Oh well.
12-18 15:24:22.244 V/ViewRootImpl( 7879): Contents drawing finished : PopupWindow:17aa788
12-18 15:24:22.637 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): >> CONNECTION 505249202a20485454502f322e300d0a0d0a534d0d0a0d0a
12-18 15:24:22.640 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): >> 0x00000000     6 SETTINGS      
12-18 15:24:22.642 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): >> 0x00000000     4 WINDOW_UPDATE 
12-18 15:24:22.644 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): >> 0x00000003   114 HEADERS       END_STREAM|END_HEADERS
12-18 15:24:22.747 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_DOWN
12-18 15:24:22.845 I/ViewRootImpl( 7879): ViewRoot's Touch Event : ACTION_UP
12-18 15:24:22.902 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): << 0x00000000    18 SETTINGS      
12-18 15:24:22.905 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): >> 0x00000000     0 SETTINGS      ACK
12-18 15:24:22.908 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger( 7879): << 0x00000000     4 WINDOW_UPDATE 
12-18 15:24:23.022 D/PhoneWindow( 7879): notifyNavigationBarColor, color=0x: 0, token: android.view.ViewRootImplAO$WEx@e27aaef

And this is the debug log for my Boron.

--------- beginning of system
12-18 16:23:20.979 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_DOWN
12-18 16:23:21.060 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_UP
--------- beginning of main
12-18 16:23:21.095 D/PhoneWindowEx(10177): [PWEx][generateLayout] setLGNavigationBarColor : colors=0xff000000
12-18 16:23:21.096 I/PhoneWindow(10177): [setLGNavigationBarColor] color=0x ff000000
12-18 16:23:21.103 D/PhoneWindow(10177): notifyNavigationBarColor, color=0x: ff000000, token: android.view.ViewRootImplAO$WEx@18bc0a3
12-18 16:23:21.154 V/ViewRootImpl(10177): Contents drawing finished : io.particle.android.app/io.particle.mesh.setup.ui.MeshSetupActivity
12-18 16:23:22.516 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_DOWN
12-18 16:23:22.614 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_UP
12-18 16:23:22.674 I/FirebasePerformance(10177): Session ID - 2d36d2d5c904490885592fa8e0e250ef
12-18 16:23:22.678 V/SoftAPConfigRemover(10177): reenableWifiNetworks()
12-18 16:23:22.780 I/Timeline(10177): Timeline: Activity_idle id: android.os.BinderProxy@fcde467 time:102854363
12-18 16:23:22.783 I/io.particle.mesh.common.android.livedata.ClearValueOnInactiveLiveData(10177): LD deactivated, clearing value
12-18 16:23:22.783 I/io.particle.mesh.common.android.livedata.ClearValueOnInactiveLiveData(10177): LD deactivated, clearing value
12-18 16:23:22.786 I/io.particle.mesh.setup.ui.FlowManagerAccessModel(10177): onCleared()
12-18 16:23:22.788 I/io.particle.mesh.setup.ui.FlowManagerAccessModel(10177): onCleared()
12-18 16:23:22.790 I/io.particle.mesh.setup.flow.FlowManager(10177): clearState()
12-18 16:23:22.790 I/io.particle.mesh.setup.flow.FlowManager(10177): clearState()
12-18 16:23:22.794 I/io.particle.mesh.setup.flow.modules.cloudconnection.BoronSteps(10177): clearState()
12-18 16:23:22.794 I/io.particle.mesh.setup.flow.modules.cloudconnection.BoronSteps(10177): clearState()
12-18 16:23:23.674 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_DOWN
12-18 16:23:23.756 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_UP
12-18 16:23:23.851 V/ViewRootImpl(10177): Contents drawing finished : PopupWindow:e8a2fb7
12-18 16:23:24.244 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): >> CONNECTION 505249202a20485454502f322e300d0a0d0a534d0d0a0d0a
12-18 16:23:24.246 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): >> 0x00000000     6 SETTINGS      
12-18 16:23:24.247 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): << 0x00000000    18 SETTINGS      
12-18 16:23:24.248 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): >> 0x00000000     4 WINDOW_UPDATE 
12-18 16:23:24.251 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): << 0x00000000     4 WINDOW_UPDATE 
12-18 16:23:24.255 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): >> 0x00000000     0 SETTINGS      ACK
12-18 16:23:24.257 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(10177): >> 0x00000003   114 HEADERS       END_STREAM|END_HEADERS
12-18 16:23:24.424 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_DOWN
12-18 16:23:24.521 I/ViewRootImpl(10177): ViewRoot's Touch Event : ACTION_UP
12-18 16:23:24.626 D/PhoneWindow(10177): notifyNavigationBarColor, color=0x: 0, token: android.view.ViewRootImplAO$WEx@c0236b5
12-18 16:23:24.692 V/ViewRootImpl(10177): Contents drawing finished : io.particle.android.app/io.particle.android.sdk.ui.DeviceListActivity

ScruffR · December 18, 2018, 8:44am

It would be better if you would post the log as text block (wrapped in a </> block).

Or if the log is too long to post, you can share a link (e.g. Dropbox, OneDrive, GoogleDrive, …)

jensck_particle · December 18, 2018, 10:08pm

@al.bertorio Are you getting that log from ADB directly, or is that just the tail end of what you got from the “share logs” feature in the app?

Also, as mentioned above, please confirm that you have location services are enabled. The next release of the app will check this for you and help you fix it, but for now you’ll have to check it for yourself.

al.bertorio · December 19, 2018, 1:24am

I get the log from the app.
Yes. I already enable the location services.

jensck_particle · December 19, 2018, 4:26pm

@al.bertorio So when you get the logs from the app, that’s all you see, just those few dozen lines?

You mentioned that the Argon log was after trying “for about 5 minutes”. Can you try for something like 30 seconds and then try grabbing the logs? (Some Android devices have small log buffers, which may explain why we’re only getting this very brief log).

al.bertorio · December 19, 2018, 5:34pm

Yes, that all I got.

Okay, let me try with just 30 seconds.
This is the results:

--------- beginning of main
12-20 00:51:48.725 D/PhoneWindowEx(25852): [PWEx][generateLayout] setLGNavigationBarColor : colors=0xff000000
12-20 00:51:48.725 I/PhoneWindow(25852): [setLGNavigationBarColor] color=0x ff000000
12-20 00:51:48.732 D/PhoneWindow(25852): notifyNavigationBarColor, color=0x: ff000000, token: android.view.ViewRootImplAO$WEx@1fa5655
12-20 00:51:48.787 V/ViewRootImpl(25852): Contents drawing finished : io.particle.android.app/io.particle.mesh.setup.ui.MeshSetupActivity
12-20 00:51:49.778 I/ViewRootImpl(25852): ViewRoot's Touch Event : ACTION_DOWN
12-20 00:51:49.873 I/ViewRootImpl(25852): ViewRoot's Touch Event : ACTION_UP
12-20 00:51:49.951 I/FirebasePerformance(25852): Session ID - f77a778b7d524ee3a0aaa757f8ac4723
12-20 00:51:49.953 V/SoftAPConfigRemover(25852): reenableWifiNetworks()
12-20 00:51:49.982 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(25852): >> 0x00000007   114 HEADERS       END_STREAM|END_HEADERS
12-20 00:51:50.038 I/Timeline(25852): Timeline: Activity_idle id: android.os.BinderProxy@9cc5026 time:139921239
12-20 00:51:50.042 I/io.particle.mesh.common.android.livedata.ClearValueOnInactiveLiveData(25852): LD deactivated, clearing value
12-20 00:51:50.042 I/io.particle.mesh.common.android.livedata.ClearValueOnInactiveLiveData(25852): LD deactivated, clearing value
12-20 00:51:50.044 I/io.particle.mesh.setup.ui.FlowManagerAccessModel(25852): onCleared()
12-20 00:51:50.044 I/io.particle.mesh.setup.ui.FlowManagerAccessModel(25852): onCleared()
12-20 00:51:50.046 I/io.particle.mesh.setup.flow.FlowManager(25852): clearState()
12-20 00:51:50.046 I/io.particle.mesh.setup.flow.FlowManager(25852): clearState()
12-20 00:51:50.049 I/io.particle.mesh.setup.flow.modules.cloudconnection.BoronSteps(25852): clearState()
12-20 00:51:50.050 I/io.particle.mesh.setup.flow.modules.cloudconnection.BoronSteps(25852): clearState()
12-20 00:51:50.281 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(25852): << 0x00000007   126 HEADERS       END_HEADERS
12-20 00:51:50.283 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(25852): << 0x00000007     2 DATA          
12-20 00:51:50.285 D/com.squareup.okhttp.internal.framed.Http2$FrameLogger(25852): << 0x00000007     0 DATA          END_STREAM
12-20 00:51:50.618 I/ViewRootImpl(25852): ViewRoot's Touch Event : ACTION_DOWN
12-20 00:51:50.717 I/ViewRootImpl(25852): ViewRoot's Touch Event : ACTION_UP
12-20 00:51:50.750 I/ListPopupWindow(25852): Could not find method setEpicenterBounds(Rect) on PopupWindow. Oh well.
12-20 00:51:50.857 V/ViewRootImpl(25852): Contents drawing finished : PopupWindow:32298c9
12-20 00:51:51.446 I/ViewRootImpl(25852): ViewRoot's Touch Event : ACTION_DOWN
12-20 00:51:51.562 I/ViewRootImpl(25852): ViewRoot's Touch Event : ACTION_UP
12-20 00:51:51.624 D/PhoneWindow(25852): notifyNavigationBarColor, color=0x: 0, token: android.view.ViewRootImplAO$WEx@e0612c4
12-20 00:51:51.713 V/ViewRootImpl(25852): Contents drawing finished : io.particle.android.app/io.particle.android.sdk.ui.DeviceListActivity

Still just 4 second recorded on the log from the beginning of main.

I have no problem when pairing my other boron that hasn’t receive any DeviceOS update. It’s all start after I update the Devices OS both over the app and over USB using particle CLI. On both version 0.8.0-rc.25 & 0.8.0-rc.26. On both boron and argon.

I also try using my friend’s phone, Samsung J2 prime android 6.0.1. Even worse, it fails to scan the barcode.

al.bertorio · December 19, 2018, 7:54pm

This is the log from my last Boron setup and firmware updates over the apps.
Maybe from this log, we can find why it cannot pair after the updates.
https://drive.google.com/open?id=1wtA9mkEmLUcppt0ujoUBwj6-0r_BU-b5

jensck_particle · December 20, 2018, 3:45am

@al.bertorio Hm, that’s still very, very short. I wonder if your phone’s logging buffer was configured to be extra tiny by LG? If you’re comfortable with it, would you mind enabling developer options on your phone, and then going into the Developer options --> Logger buffer sizes and make sure that it’s set to at least 256K per buffer?

Also, if you go into your phone’s Bluetooth settings, does your Boron show up in BT scans there when it’s in listening mode?

*EDIT: or just try quitting the pairing attempt after only 5 seconds instead of 30?

al.bertorio · December 20, 2018, 9:14am

It’s already set at 256K per log buffer.
Yes. In the Bluetooth setting, my argon & boron both detected.

Oh man, you’re right. I try to set the buffer at 1M if there might be some differences.
And this is the result.
https://drive.google.com/open?id=159OhMJOZj2KGD3r1Jjc6EU0Wj6FfJMUR

al.bertorio · December 20, 2018, 10:52am

I also try with the new firmware v0.8.0-rc.27 and still stuck in pairing. This is the log:
https://drive.google.com/open?id=1LnQPXjnv-8LAwQVL1srssZSzJ3x_QJUX

Topic		Replies	Views
Unable to pair with new Xenon Troubleshooting	18	3611	March 31, 2019
Unable to pair with new Boron Troubleshooting	4	1767	November 11, 2018
Boron stuck in listening mode and will not pair via the iPhone App Troubleshooting	4	790	October 17, 2019
Boron 3G stuck in setup Troubleshooting boron-3g	0	785	May 20, 2019
Boron LTE Stopped Working after Months of Success Troubleshooting boron	4	638	April 26, 2019

Unable to set up Boron LTE

Related Topics