Android studio, androidstudio

Android studio, androidstudio

The current work is related to Bluetooth, so I am eager to develop Android devices to debug my firmware,

After installing Android Studio and SDK, I would like to thank nordic for its public code and study it for a while.

There are two related codes. The Android-nRF-Toolbox was first found. This code is more comprehensive and needs to be debugged here,

But... For a person I don't know much about, it's still a little hard to understand, and I don't dare to modify it...

So I found this Android-nRF-UART, which is much simpler... Because there are only three java codes for. class.

 

OK, so we can start it After cloning it. Directly succeed, scatter the flowers ~...

 

However, for convenience of modification and debugging, The Uart service is the official uuid of Nordic by default.

    public static final UUID RX_SERVICE_UUID = UUID.fromString("6e400001-b5a3-f393-e0a9-e50e24dcca9e");    public static final UUID RX_CHAR_UUID = UUID.fromString("6e400002-b5a3-f393-e0a9-e50e24dcca9e");    public static final UUID TX_CHAR_UUID = UUID.fromString("6e400003-b5a3-f393-e0a9-e50e24dcca9e");

However, what I need is not this id ,,,

Therefore, it begins to die, starting from applicationId, changing the file name and pack name.

During the final compilation, it was strange that the build and R files of com. nordicsemi. Uart could not be replaced with the new id I needed. After finding a circle, I found that

 

It turns out to be an XML pot .. There are residual configuration information in manifests/AndroidManifesh. xml.

However, for lightweight app development, in addition to resource (png layout string. xml), you need to pay attention to class and manifeshs.

After cleaning all the packages registered in the XML file and the corresponding activity and service.

 

Now everything is normal. This product is the responsibility of Makefile. After this is done, the mystery of Android development disappears,

Visual Testing will soon be able to transform productivity. In fact, the overall difficulty is not as hard as C # developing win gadgets