_ALIGN(4) uint8_t sixteen = 16 appears as 10 in characteristic read value?

[myNrfDoesntWork]

I defined an integer value _ALIGN(4) uint8_t sixteen = 16 and assigned sixteen to a FDS record that is later assigned to the p_data of a custom characteristic. However, when I read the characteristic the value shows up as 10. When I try doing _ALIGN(4) uint8_t seventeen = 17 the characteristic value also reads as 11, etc. I tried searching online for whether this is something that C does for alignment in integer data type, but couldn't find any clear results. 

If I want uint8_t sixteen = 16 to appear as 16 in the characteristic read value, how should I do it? I think the integer data structure still needs to be aligned so it can be used for .p_data in FDS record. 

[awneil]

Sounds like it's just displaying in hex in one case, and decimal in the other?

 How, exactly, are you viewing these values?

[myNrfDoesntWork]

I am viewing these values by doing a characteristic read with the nrf_connect mobile app

[awneil]

So, as I said, it sounds like it's just displaying in hex in one case, and decimal in the other.

[myNrfDoesntWork]

Is there any way to change this if I want the characteristic value to be read by nrf_connect app as 16 or 17 instead of 0x10, 0x11, etc? 

I know the nrf_connect app displays the characteristic read values in hex, but I don't want a user to get confused if they are expecting a value of 16 and instead see (0x)10. 

[awneil]

Remember that nRF Connect is just a simple engineering app for test/development - it is not intended for end users.