Gurux DLMS Android App not running.

PS: Is there any way to attach screenshots here?

Okay, so then, how will I be able to use the app, without the UI?

Hello @Kurumi Sir,
I have somehow managed to run the Gurux DLMS Component for Android on my Android 14 device, but I'm unable to find all the screens as we have in the Windows application.

I need to connect to the smart meter using these credentials :-
{Password/LLS, Transaction Key/HLS Key, Upgrade Key, Encryption Key, Authentication Key, System Title} and, I am not able to find all of these fields in the android app.

Please respond what can I do?

Basically, I am able to make a PC, but not MR or US, because for making a US, I need to input the encryption key, authentication key, and system title. And, there is no such screen available for inputting these values.

Okay, thanks!

What difference will it create after adding this line in build.gradle?
Also, is there any pre-built apk which runs smoothly and have all the screens?

Hello Kurumi Sir,
Thanks for the reply, after changing some dependency versions in build.gradle file, the project successfully builds in android studio and the app Gurux DLMS runs on my android 14 device.

I have somehow managed to make MR and US association (authentication after selecting manufacturer - Indian Standard).
But, I am not able to connect/disconnect relay connection, there are no buttons like in the Windows application.

Can you please guide on how do I make relay connection buttons?
This property can be found named "DisconnectControl".

Hello Kurumi Sir,
Again, a big thanks to your support.
The code you've provided for relay connections words fine. I can connect/disconnect on button click. This would have taken much longer time without your help.

Just a little issue I'm getting in finding the getter/setter of Frame Counter.
There is a field named "Frame Counter LN" in the Windows GXDLMSDirector application (in "Secured Connections" tab when adding a device).

In that Frame Counter LN, we enter a String value like "0.0.43.1.255" format, and it is a fixed value for a particular manufacturer meter (please correct me if I'm wrong).
I am not able to find this parameter in the code, instead, I am using the following line of code in MainFragment.java :-
mClient.getCiphering().setInvocationCounter(userInput); // Try starting with 0

In this scenario, I have to check the new invocation counter value and update it everytime I reconnect to the meter.

We need to make it more efficient for using the app.
Please suggest a way to implement it (or any other way, if this is not possible).

Thanks again.

Okay sir,
I'll create the new topic from next time.

Where should I use this function updateFrameCounter() ?

Can you provide an alternate for this, where user can enter "Invocation Counter Data Object Logical Name" (for e.g. "0.0.43.1.1.255") ?

Okay, sir.

Hello Mikko Kurumi Sir, 
Thanks for the updates. 
I've tried the code you provided: mDevice.setInvocationCounter(LOGICAL_NAME);
It connects to the meter sometimes, and sometimes not, the value is updated in the updated android code, but sometimes it does not matches the actual one (I put logs for checking the value of invocation counter everytime). 
Yet, I've made another way of doing it:-

   /**
    * Update invocation counter manually
    */
   private void updateInvocationCounter() {
       long invocationCounter = mClient.getCiphering().getInvocationCounter() + 100;
       mClient.getCiphering().setInvocationCounter(invocationCounter);
       editor.putLong("invocationCounter", invocationCounter);
       editor.apply();
   }

I'm incrementing the counter by 100 after every "read" or "refresh" operation, as it connects if we give a greater value to the meter, and meters rejects the association if we provide a value of invocation counter lesser than the actual one.

This approach is running successfully in my case. 
Please tell if I'm following a doable approach. 

Okay, sir.
I don't have a problem reading the counter before connecting to the meter, but the code you updated does not work in every case.
It doesn't let smoothly connect to the meter everytime, in the end, I have to reset the counter by turning the electricity on-off.
I have read the updateFrameCounter() function, may be the issue lies in updating the counter when initializing connection.
The counter is updated only when we open the connection, sometimes, connection breaks in between reading the values, so the counter inside the meter is increased, but not in the application, what is the possible solution to this?

Hi,

On establishing the connection again, the app throws GXGeneral error after 15 seconds.
Once, the app is closed and opened again, it is no longer able to connect to the meter because invocation counter in the meter has increased, but not saved in the app.

I've also tried saving in sharedpreferences : editor.putLong("invocation_counter", iv);
but, I'm not able to keep track of the value of invocation counter in any case.
Then what is the use of the function :- mDevice.setInvocationCounter(LOGICAL_NAME);

??

It only connects to the meter once, when the counter is already 0.

Thanks,
Kshitiz

Okay, sir, 
I'll try, if you can tell me where exactly should I use this function :- 
mDevice.setInvocationCounter(LOGICAL_NAME);

For now, I'm using it immediately after the click event of "Open" button. 
My code looks like this :-

mOpen.setOnClickListener(v -> {
    try {
        mDevice.setManufacturer("ind");
//          GXAuthentication auth = new GXAuthentication();
//          auth.setType(Authentication.HIGH);
//          mDevice.setAuthentication(auth);
        mClient.getCiphering().setSecurity(Security.AUTHENTICATION_ENCRYPTION);
        mClient.getCiphering().setSystemTitle("title".getBytes(getString(R.string.ascii)));
        mClient.getCiphering().setAuthenticationKey("key1".getBytes(getString(R.string.ascii)));
        mClient.getCiphering().setBlockCipherKey("key2".getBytes(getString(R.string.ascii)));
        mClient.setPassword("passwd".getBytes(getString(R.string.ascii)));
        mDevice.setInvocationCounter("0.0.43.1.3.255");

Yes, sir,
I am using the same logical name.
In the previous post, I gave an example logical name.

Yes, sir,
0.0.43.1.3.255 - This is the actual logical name of the invocation counter object.

0.0.43.1.1.255 was just an example I gave in my previous post.