Unable to set up Boron LTE


#54

I got the ICCID from my SIM card another way. However, trying to activate it using the way you suggested… says it is an Invalid SIM card. It is not a Particle SIM… it is a 3rd party SIM card.


#55

You cannot activate a 3rd-party SIM card using the mobile apps. You need to follow the instructions in the 3rd-party SIM guide:

https://docs.particle.io/support/particle-devices-faq/electron-3rdparty-sims/


#56

@jensck I’m sure you already know this but my device does indeed pair right up using an IOS device (old ipad). I haven’t seen any info regarding a fix for android based devices yet. I noticed the ios app does things in different order than the android app. Probably doesn’t matter, just odd.


#57

There are two things that may help with Android:

  1. Upgrading the device to 0.8.0-rc.26 first will help with pairing issues as well as failures during data communication. This was particularly prevalent with Android 7 devices.

  2. Version 2.3.8 of the Android app was just released to the Play store and should be available in a few hours. It has a debugging log feature that will make debugging these types of failures much easier. (The iOS app has had the debug log for a week or so.)


#58

Hi folks,

Just received my first Boron and am having the same issue: it’s stuck on pairing step. Using USB and particle identify returns “Could not identify device: No serial port identified”.


#59

You won’t be able to particle identify until you’ve upgraded the device the first time.

Follow the instructions here to update the Boron by CLI:

Once you’ve upgraded the Boron to 0.8.0-rc.26 you should be able to pair with most Android devices, and also particle identify will be supported.


#60

Unable to flash with new firmware: No DFU device found. CLI is updated to latest version.


#61

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


#62

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.


#63

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.


#64

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


#65

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!


#66

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?


#67

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.


#69

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.


#70

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

#71

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, …)


#72

@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.


#73

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


#74

@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).