nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Thu, 22 Aug 2019 09:48:14 GMT

Hi Martin

There isn't that much to it, other than be a bit careful about the interrupt priorities you run your events at.

If your events run at priority 6 or 7 there isn't much to think about. Critical SoftDevice interrupts and event forwarding to the application will have priority, and will not be impacted.

If your events run a priority 2 or 3 you have to be a bit more careful, as you will supersede events coming from the SoftDevice, and you will not be able to call SoftDevice functions from your application event directly.

The remaining interrupt priorities (0, 1, 4 and 5) are unavailable when using a SoftDevice.

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Wed, 21 Aug 2019 15:06:35 GMT

Hi Torbjørn

I started to look for some tutorials on integrating application events/processing into the BLE framework but do you have any recommendations on this. I found something using a scheduler for example.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Wed, 21 Aug 2019 05:18:02 GMT

Hi Martin

This looks good to me. For clarity I would insert the compound_char_handles field in ble_lbs_s struct after the button_char_handles field, and before the event handler, but this has no practical impact on the code (it's just to bundle the char handles together).

Secondly you can also consider renaming the characteristic to something more relevant to the data that you want to send.

The UUID definition looks fine, the main point is to pick a unique 16-bit number for all the new characteristics.

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Tue, 20 Aug 2019 16:52:23 GMT

Hi Torbjørn

I added each code and modified the structure ble_lbs_s.to include float or compound char handles but to start I made a mistake for the type (not using ble_gatts_char_handles) and the compiler gave a warning about an incompatible pointer. Then I compiled with empty callbacks for now. I ran this under debug and also the android end. I just wanted to see if the new UUID was being read ok which appears affirmative and the App runs as expected thereafter. I did not use a unique UUID rather for this test I appended as shown below.

struct ble_lbs_s
{
uint16_t service_handle; /**< Handle of LED Button Service (as provided by the BLE stack). */
ble_gatts_char_handles_t led_char_handles; /**< Handles related to the LED Characteristic. */
ble_gatts_char_handles_t button_char_handles; /**< Handles related to the Button Characteristic. */
uint8_t uuid_type; /**< UUID type for the LED Button Service. */
ble_lbs_led_write_handler_t led_write_handler; /**< Event handler to be called when the LED Characteristic is written. */
ble_gatts_char_handles_t compound_char_handles;
};

So the modified characteristic seems ok so far so next I'll make some event handling for the data etc.

Thanks again but I would be pleased for you to comment.

BR Martin

#define LBS_UUID_BASE {0x23, 0xD1, 0xBC, 0xEA, 0x5F, 0x78, 0x23, 0x15, \
0xDE, 0xEF, 0x12, 0x12, 0x00, 0x00, 0x00, 0x00}
#define LBS_UUID_SERVICE 0x1523
#define LBS_UUID_BUTTON_CHAR 0x1524
#define LBS_UUID_LED_CHAR 0x1525
#define COMPOUND_CHAR_UUID 0x1526

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Tue, 20 Aug 2019 13:00:49 GMT

Hi Martin

Sound good, just let me know if you have more questions 🙂

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Tue, 20 Aug 2019 08:34:46 GMT

Thanks a lot Torbjørn I have added this to my short term list. I'll feedback how I get on.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Tue, 20 Aug 2019 07:51:27 GMT

Hi Martin

If you take a look at the ble_lbs_init(..) function in ble_lbs.c you can see how the characteristics are set up. As long as you change the UUID to something different you can change the service and characteristic configuration any way you like, and change the size of the services.

As an example, to add a new characteristic that supports float just add the following lines of code:

// Add float characteristic.
memset(&add_char_params, 0, sizeof(add_char_params));
add_char_params.uuid              = ADD_UNIQUE_16BIT_UUID_HERE;
add_char_params.uuid_type         = p_lbs->uuid_type;
add_char_params.init_len          = sizeof(float);
add_char_params.max_len           = sizeof(float);
// Read and Notify is typically set when the data flow is from the server (nrf52) to the client (phone)
add_char_params.char_props.read   = 1;
add_char_params.char_props.notify = 1; 

add_char_params.read_access       = SEC_OPEN;
add_char_params.cccd_write_access = SEC_OPEN;

// You need to extend the p_lbs service type to include char handles for your new characteristic
err_code = characteristic_add(p_lbs->service_handle,
                              &add_char_params,
                              &p_lbs->float_char_handles);
if (err_code != NRF_SUCCESS)
{
    return err_code;
}

If you have a lot of smaller values you want to send together it makes sense to define them as a struct, and set up your characteristic to send the entire struct in one go. Then you can more effectively send a lot of smaller values at once:

typedef struct
{
    int int_var;
    float a_float;
    bool and_a_bool;
}compound_type_t;

// Add compound characteristic.
memset(&add_char_params, 0, sizeof(add_char_params));
add_char_params.uuid              = COMPOUND_CHAR_UUID;
add_char_params.uuid_type         = p_lbs->uuid_type;
add_char_params.init_len          = sizeof(compound_type_t);
add_char_params.max_len           = sizeof(compound_type_t);
add_char_params.char_props.read   = 1;
add_char_params.char_props.notify = 1;

add_char_params.read_access       = SEC_OPEN;
add_char_params.cccd_write_access = SEC_OPEN;

err_code = characteristic_add(p_lbs->service_handle,
                              &add_char_params,
                              &p_lbs->compound_char_handles);
if (err_code != NRF_SUCCESS)
{
    return err_code;
}

After you change this on the peripheral side you also have to change your app code to read/write the characteristics properly. In Java this is a bit fiddly as you have to convert byte buffers to float/int/bool etc, but nothing a google search won't tell you how to do ;)

To generate your own unique 128-bit base UUID you can use this site:
https://www.uuidgenerator.net/

Just remember to pick a version 4 UUID (random), not version 1.

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Mon, 19 Aug 2019 11:22:22 GMT

Hi Again

I now have a real requirement to build a demo app which uses the nRF52 kit. So I have revisited this Blinky example again and have been able to build in additional funcionality like handling more buttons and leds. In fact this modified Blinky already does >60% of what I expect to need for the demo. However, this is ok for boolean types but I need to add some more variables (say 6) like integer and possibly float. These would typically just need to be sent from the embedded end.

I was contemplating adding more functionalty to accomplish this but would like to know your recommendations. For example is it easy to add this to the Blinky example or should I be looking at another example. Of course I have a "Thingy" (nice job) but that is doing a lot and it could me quite sometime to figure out how to extract what I need. So I am trying to work with efficiency in mind and coming from the fact I am not a regular user of the underlying BLE software just now.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Wed, 10 Oct 2018 11:16:12 GMT

Hi Martin

That's an interesting find!

I double checked it myself and see the same issue here. For some reason I only ever click it, and I guess the same goes for the developer ;)

I reported it to the apps guys, and they opened an issue on the github:
https://github.com/NordicSemiconductor/Android-nRF-Blinky/issues/13

Knowing their turnaround time we should have a fix out pretty soon 🙂

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Tue, 09 Oct 2018 12:09:55 GMT

Hi Torbjørn

I think this has helped uncover the issue. What I notice is if I put my finger on the LED slider control and move from left to right or right to left, I don't see the LED status change. If I tap the slider at either end I see the LED toggle ON/OFF ok ;-)

You can see these two types of behaviour in the log below. Firstly I tap the slider and you see LED OFF response and then I tap the other end of the slider and the response is LED ON. After that I slide my finger across the slider and then the status does not change, only the ViewPosttime pointer 0 or 1 message is shown.

It's quite a small slider on my phone and of course it gives the impression that toggle LED ON/OFFcommand is handled through ok through visual feedback on the slider object.

D/BlinkyManager: Turning LED OFF...
                 Writing characteristic 00001525-1212-efde-1523-785feabcd123 (WRITE REQUEST)
                 gatt.writeCharacteristic(00001525-1212-efde-1523-785feabcd123)
D/BlinkyManager: Data written to 00001525-1212-efde-1523-785feabcd123, value: (0x) 00
                 LED OFF
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 0
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 1
D/BlinkyManager: Turning LED ON...
                 Writing characteristic 00001525-1212-efde-1523-785feabcd123 (WRITE REQUEST)
                 gatt.writeCharacteristic(00001525-1212-efde-1523-785feabcd123)
D/BlinkyManager: Data written to 00001525-1212-efde-1523-785feabcd123, value: (0x) 01
                 LED ON
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 0
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 1
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 0
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 1
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 0
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 1
D/ViewRootImpl@1cda049[BlinkyActivity]: ViewPostIme pointer 0

Thanks for this I will now move forward and add some customisations to the App and embedded control.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Tue, 09 Oct 2018 09:06:46 GMT

Hi Martin

Apparently there is a trick to getting more logging info from the Blinky app.

In the BlinkyManager.java file, please add the following function to the BlinkyManager class:

@Override
public void log(int level, @NonNull String message) {
   super.log(level, message);
   Log.d("BlinkyManager", message);
}

Then you should see log messages when the app sends data to the peripheral, and when the writeCharacteristic callback is triggered, which means the data was successfully sent.

The log should look something like this if everything works correctly:

10-09 11:03:33.038 21893-21893/no.nordicsemi.android.nrfblinky D/BlinkyManager: Turning LED OFF...
10-09 11:03:33.290 21893-21925/no.nordicsemi.android.nrfblinky D/BlinkyManager: LED OFF
10-09 11:03:33.928 21893-21893/no.nordicsemi.android.nrfblinky D/BlinkyManager: Turning LED ON...
10-09 11:03:34.263 21893-21907/no.nordicsemi.android.nrfblinky D/BlinkyManager: LED ON
10-09 11:03:34.582 21893-21893/no.nordicsemi.android.nrfblinky D/BlinkyManager: Turning LED OFF...
10-09 11:03:34.849 21893-21907/no.nordicsemi.android.nrfblinky D/BlinkyManager: LED OFF

Can you give this a try and see if the results are similar?

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Mon, 08 Oct 2018 11:34:42 GMT

Don't forget I had the observation that nRF Connect App works. Meaning toggling the LED works every time. So I suspect the nRF Blinky App is at fault somehow.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Mon, 08 Oct 2018 08:42:42 GMT

Hi Martin

That's newer than both my kits, so I guess the old kit theory goes out the window ;)

Do you have the log enabled while running the example?
It would be interesting to know if the command is actually received or not.

With the log running you should see a message whenever the LED is turned on or off.

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Mon, 08 Oct 2018 07:24:39 GMT

Hi Torbjørn

I have PCA10040, 1.2.4, 2018.12, 682351679 printed on the white sticker on the dev board chip.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Mon, 08 Oct 2018 06:51:40 GMT

Hi Martin

Can you let me know the version and date string printed on your development kit?
This should be visible on the square, white sticker.

I have an older kit that exhibits the issue, and a newer one that does not.

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Wed, 03 Oct 2018 17:32:33 GMT

Hi Torbjørn

So I synced with the develop branch and ran the application in debug mode but the LED behaviour is the same. So the LED is not controlled successfully from the Android App, only occasionally does it work.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Wed, 03 Oct 2018 16:19:36 GMT

Hi Torbjørn

Disabling Instant Run prevents an App Instant Crash, thanks for that. Now I check the latest with the develop branch.

Have a good trip.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Wed, 03 Oct 2018 15:03:28 GMT

Hi Martin

A comment from the app developer was to disable instant run in the Android Studio settings. Can you try that and see if debugging works?

Regarding the app he suggested trying the develop branch rather than the master branch, to see if it fixes the issue with the missing LED update:
https://github.com/NordicSemiconductor/Android-nRF-Blinky/tree/develop

Please give it a go and see if it helps. If it doesn't I will do more testing on my end to get to the bottom of the issue. Unfortunately I won't be able to continue this until next week, as I am going on a business trip for the next couple of days.

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Tue, 02 Oct 2018 12:55:11 GMT

Hi Torbjørn

Here is a debug log I just recorded in the attached txt file.

I used Notepad++ to highlight and mark all nrfblinky fyi.

BR Martindevzone.nordicsemi.com/.../blinkycrash.txt

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Tue, 02 Oct 2018 12:11:31 GMT

Hi Torbjørn

Quick response = Yes your summary is correct in the last mail.

Thanks

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Tue, 02 Oct 2018 11:47:05 GMT

Hi Martin

Please have a look at the attached screenshot. I simply add nrfblinky in the search field in logcat, setting up a custom filter should not be necessary.

Then I can focus on the app related messages easily, and the log doesn't get overflowed with system messages.

An interesting observation is that I can reproduce the problem with the LED characteristic. Changing the LED in the app doesn't appear to have any effect on the kit. I need some more time to look into this and discuss it with the developers.

To summarize your issues, if you try to use the debugger in Android Studio the app won't even start?

If you don't use the debugger it works, but you are unable to control the LED?

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Mon, 01 Oct 2018 16:16:05 GMT

Not sure about the filter but I set up this in logcat...

and then the debug log was abbreviated to this...

10-01 17:12:03.074 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: setView = DecorView@d7da730[nrfblinky] TM=true MM=false
10-01 17:12:03.078 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: dispatchAttachedToWindow
10-01 17:12:03.099 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: Relayout returned: old=[0,0][0,0] new=[32,775][1047,1217] result=0x7 surface={valid=true 543709986816} changed=true
10-01 17:12:03.101 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: MSG_WINDOW_FOCUS_CHANGED 1
10-01 17:12:03.127 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: MSG_RESIZED_REPORT: frame=Rect(32, 775 - 1047, 1217) ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
10-01 17:12:03.152 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: ViewPostIme pointer 0
10-01 17:12:03.161 2997-3031/? D/ViewRootImpl@64340e2[nrfblinky]: dispatchDetachedFromWindow
10-01 17:12:03.190 2997-3031/? W/ViewRootImpl@64340e2[nrfblinky]: Dropping event due to root view being removed:
10-01 17:12:03.190 2997-3031/? E/ViewRootImpl@64340e2[nrfblinky]: mStopped=false mHasWindowFocus=true mPausedForTransition=false
10-01 17:12:05.124 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: setView = DecorView@ea2fd69[nrfblinky] TM=true MM=false
10-01 17:12:05.128 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: dispatchAttachedToWindow
10-01 17:12:05.145 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: Relayout returned: old=[0,0][0,0] new=[32,775][1047,1217] result=0x7 surface={valid=true 543710330880} changed=true
10-01 17:12:05.149 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: MSG_WINDOW_FOCUS_CHANGED 1
10-01 17:12:05.179 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: MSG_RESIZED_REPORT: frame=Rect(32, 775 - 1047, 1217) ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
10-01 17:12:05.330 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: ViewPostIme pointer 0
10-01 17:12:05.344 2997-3031/? D/ViewRootImpl@6248433[nrfblinky]: dispatchDetachedFromWindow
10-01 17:12:05.368 2997-3031/? W/ViewRootImpl@6248433[nrfblinky]: Dropping event due to root view being removed:
10-01 17:12:05.368 2997-3031/? E/ViewRootImpl@6248433[nrfblinky]: mStopped=false mHasWindowFocus=true mPausedForTransition=false
10-01 17:12:07.820 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: setView = DecorView@1d8ee14[nrfblinky] TM=true MM=false
10-01 17:12:07.839 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: dispatchAttachedToWindow
10-01 17:12:07.906 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: Relayout returned: old=[0,0][0,0] new=[32,775][1047,1217] result=0x27 surface={valid=true 543710629888} changed=true
10-01 17:12:07.912 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: MSG_WINDOW_FOCUS_CHANGED 1
10-01 17:12:07.940 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: MSG_RESIZED_REPORT: frame=Rect(32, 775 - 1047, 1217) ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
10-01 17:12:08.803 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: ViewPostIme pointer 0
10-01 17:12:08.956 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: ViewPostIme pointer 1
10-01 17:12:08.963 2997-3031/? D/ViewRootImpl@2625381[nrfblinky]: dispatchDetachedFromWindow
10-01 17:12:49.571 2997-3089/? D/ViewRootImpl@b3a2ec4[nrfblinky]: setView = DecorView@ee32ce2[nrfblinky] TM=true MM=false
10-01 17:12:49.572 2997-3089/? D/ViewRootImpl@b3a2ec4[nrfblinky]: dispatchAttachedToWindow
10-01 17:12:49.584 2997-3089/? D/ViewRootImpl@b3a2ec4[nrfblinky]: Relayout returned: old=[0,0][0,0] new=[0,0][1080,1920] result=0x7 surface={valid=true 543383703552} changed=true
10-01 17:12:49.586 2997-3089/? D/ViewRootImpl@b3a2ec4[nrfblinky]: MSG_RESIZED_REPORT: frame=Rect(0, 0 - 1080, 1920) ci=Rect(0, 72 - 0, 0) vi=Rect(0, 72 - 0, 0) or=1
10-01 17:12:49.769 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: setView = DecorView@1b34049[nrfblinky] TM=true MM=false
10-01 17:12:49.772 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: dispatchAttachedToWindow
10-01 17:12:49.799 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: Relayout returned: old=[0,0][0,0] new=[32,624][1047,1368] result=0x7 surface={valid=true 543711801344} changed=true
10-01 17:12:49.801 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: MSG_WINDOW_FOCUS_CHANGED 1
10-01 17:12:49.889 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: MSG_RESIZED_REPORT: frame=Rect(32, 624 - 1047, 1368) ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
10-01 17:12:52.044 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: ViewPostIme pointer 0
10-01 17:12:52.109 2997-3031/? D/ViewRootImpl@f97cfe4[nrfblinky]: dispatchDetachedFromWindow
10-01 17:12:52.306 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: setView = DecorView@85a4393[nrfblinky] TM=true MM=false
10-01 17:12:52.308 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: dispatchAttachedToWindow
10-01 17:12:52.317 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: Relayout returned: old=[0,0][0,0] new=[32,775][1047,1217] result=0x7 surface={valid=true 543304855552} changed=true
10-01 17:12:52.319 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: MSG_WINDOW_FOCUS_CHANGED 1
10-01 17:12:52.334 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: MSG_RESIZED_REPORT: frame=Rect(32, 775 - 1047, 1217) ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
10-01 17:12:53.143 2997-3089/? D/ViewRootImpl@b3a2ec4[nrfblinky]: dispatchDetachedFromWindow
10-01 17:12:54.930 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: ViewPostIme pointer 0
10-01 17:12:55.046 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: ViewPostIme pointer 1
10-01 17:12:55.056 2997-3031/? D/ViewRootImpl@d6fcd[nrfblinky]: dispatchDetachedFromWindow

Might need to advise on the filter, thanks.

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Mon, 01 Oct 2018 14:51:31 GMT

Hi Martin

Sorry for all the requests, but could you also do a log with the "nrfblinky" filter applied, so that only the app messages are shown?

Best regards
Torbjørn

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

MPH — Mon, 01 Oct 2018 12:38:25 GMT

Ok this is what I get in the adb log when trying to run Blinky App on my phone......

10/01 13:27:58: Launching app
$ adb install-multiple -r -t C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_4.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\resources\instant-run\debug\resources-debug.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_5.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_3.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_0.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_1.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_2.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_7.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\dep\dependencies.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_6.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_8.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\split-apk\debug\slices\slice_9.apk C:\Users\Martin\Documents\GitHub\Android-nRF-Blinky\app\build\intermediates\instant-run-apk\debug\app-debug.apk
Split APKs installed
$ adb shell am start -n "no.nordicsemi.android.nrfblinky/no.nordicsemi.android.blinky.SplashScreenActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -D
Waiting for application to come online: no.nordicsemi.android.nrfblinky | no.nordicsemi.android.nrfblinky.test
Waiting for application to come online: no.nordicsemi.android.nrfblinky | no.nordicsemi.android.nrfblinky.test
Connecting to no.nordicsemi.android.nrfblinky
Capturing and displaying logcat messages from application. This behavior can be disabled in the "Logcat output" section of the "Debugger" settings page.
W/ActivityThread: Application no.nordicsemi.android.nrfblinky is waiting for the debugger on port 8100...
I/System.out: Sending WAIT chunk
I/zygote64: Debugger is active
I/System.out: Debugger has connected
waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
Connected to the target VM, address: 'localhost:8601', transport: 'socket'
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: debugger has settled (1356)
I/zygote64: no shared libraies, dex_files: 1
I/InstantRun: starting instant run server: is main process
D/AndroidRuntime: Shutting down VM
E/AndroidRuntime: FATAL EXCEPTION: main
Process: no.nordicsemi.android.nrfblinky, PID: 26198
java.lang.RuntimeException: Unable to get provider android.arch.lifecycle.ProcessLifecycleOwnerInitializer: java.lang.ClassNotFoundException: Didn't find class "android.arch.lifecycle.ProcessLifecycleOwnerInitializer" on path: DexPathList[[zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/base.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_dependencies_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_resources_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_0_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_1_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_2_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_3_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_4_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_5_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_6_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_7_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_8_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_9_apk.apk"],nativeLibraryDirectories=[/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/lib/arm64, /system/lib64, /system/vendor/lib64]]
at android.app.ActivityThread.installProvider(ActivityThread.java:6581)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:6133)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6043)
at android.app.ActivityThread.-wrap1(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1764)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
E/AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "android.arch.lifecycle.ProcessLifecycleOwnerInitializer" on path: DexPathList[[zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/base.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_dependencies_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_resources_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_0_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_1_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_2_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_3_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_4_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_5_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_6_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_7_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_8_apk.apk", zip file "/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_slice_9_apk.apk"],nativeLibraryDirectories=[/data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/lib/arm64, /system/lib64, /system/vendor/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
at android.app.ActivityThread.installProvider(ActivityThread.java:6566)
... 10 more
Suppressed: java.io.IOException: No original dex files found for dex location (arm64) /data/app/no.nordicsemi.android.nrfblinky-Abaq71A2nyPIFytIPBL22w==/split_lib_resources_apk.apk
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:353)
at dalvik.system.DexFile.<init>(DexFile.java:100)
at dalvik.system.DexFile.<init>(DexFile.java:74)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:374)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:337)
at dalvik.system.DexPathList.<init>(DexPathList.java:157)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:65)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:64)
at com.android.internal.os.PathClassLoaderFactory.createClassLoader(PathClassLoaderFactory.java:43)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:69)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:36)
at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:678)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:711)
at android.app.LoadedApk.getResources(LoadedApk.java:944)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2303)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5943)
... 8 more

BR Martin

RE: nRF52 Ble Peripheral Example - ble_app_blinky not showing led/button service

ovrebekk — Mon, 01 Oct 2018 07:31:52 GMT

Hi Martin

Thanks for the update.

If you capture the ADB log when the Blinky app crashes I can show it to the app developers, and they might have some input.

Best regards
Torbjørn