Issue Connecting Smart Meter via Optical Probe on Android (Invalid Logical Name / Limited Data Issue)

Sir,

I am able to connect successfully using GXDLMSDirector with the following parameters:

Security Policy: Authentication + Encryption

Block Cipher Key: [Provided]

Authentication Key: [Provided]

Client System Title: [Provided]

Manufacturer: India Standard

Referencing: Logical Name

Interface: HDLC

Authentication: US

Password: [Provided]

Wait Time: 00:00:05

Address Type: Default

Physical Address: 1

Logical Address: 0

Client Address: 48

However, when I use the same parameters in the Gurux Android App, I get an error

saying “Invalid Logical Name.”

Sir,

The value of Invocation counter field is 0

Sir,

When I leave the Invocation Counter empty and try to read the meter using the Android app, I get the same error: “Invalid Logical Name.”

However, with the exact same parameters in GXDLMSDirector, the connection works without any issue.

Every time I attempt to connect to the meter using the Gurux Android app, I carefully check that Logical Name Referencing is selected, but the app still fails to connect and shows the same error

Sir,

As per your earlier suggestion, I downloaded and tested the latest version of the Gurux Android library. However, I have still faced the same issue: “Invalid Logical Name.”

Debugging Observations :

1) I debugged the code and noticed that the error originates from line 106 in the

GXDLMSObject.java class.

2) Initially, when the Invocation Counter was left empty, the Android app returned the

“Invalid Logical Name” error.

3) To test further, I used the same Invocation Counter (0.0.43.1.3.255) that I obtained

from GXDLMSDirector. After providing this value in the Android app, I started receiv

ing HDLC frames in Android App.

22:59:21.431 7E A0 07 03 21 93 0F 01 7E
-> 22:59:21.480 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 22:59:21.485 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 42 1E 5D FF FF 19 35 7E
-> 22:59:21.599 7E A0 37 21 03 30 6C 7C E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 00 10 03 40 00 07 D1 F0 7E
<- 22:59:21.606 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 01 00 00 2B 01 03 FF 02 00 B0 AA 7E
-> 22:59:21.858 7E A0 15 21 03 52 5D 8A E6 E7 00 C4 01 C1 00 06 00 00 00 00 7D 18 7E
Invocation counter: 1
<- 22:59:21.866 7E A0 07 03 21 53 03 C7 7E
-> 22:59:21.915 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 22:59:21.919 7E A0 07 03 3D 93 3E 3D 7E
-> 22:59:21.969 7E A0 20 3D 03 73 45 B8 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 22:59:21.976 7E A0 5C 03 3D 10 AE 9E E6 E6 00 60 4E A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 30 31 32 33 34 35 36 37 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 02 80 00 BE 24 04 22 21 20 30 00 00 00 01 A9 F9 D0 12 A4 D6 E2 91 83 76 BB 4D 69 3B C7 7B F0 5F EF 56 8D F7 A3 27 D5 D4 57 99 8F 7E
-> 22:59:22.134 7E A0 2D 3D 03 30 55 43 E6 E7 00 61 1F A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A1 03 02 01 01 BE 06 04 04 0E 01 03 00 AA 30 7E

Could you please check whether the Android library requires an update in handling Invocation Counter or Logical Name referencing?

Do I need to make any additional configuration changes in the app to ensure proper connection, since GXDLMSDirector works with the same parameters?

Sir,

When I read the meter through Gurux DLMS Director and opened the Data section af
ter a successful reading, the software displayed multiple invocation counters. The following logical names were available:

Invocation Counter #2 (MR): 0.0.43.1.2.255

Invocation Counter #3 (US): 0.0.43.1.3.255

Invocation Counter #4 (Push): 0.0.43.1.4.255

Invocation Counter #5 (FW): 0.0.43.1.5.255
To comprehend what I see when connecting with the meter through GuruXDLMS director, I show you this :

image.https://i.postimg.cc/B6dgKN62/Screenshot-2025-09-03-192517.png
https://i.postimg.cc/8C7MmWx4/Screenshot-2025-09-03-192708.png
https://i.postimg.cc/CK8dK4W3/Screenshot-2025-09-03-192719.png
https://i.postimg.cc/rFW8xph4/Screenshot-2025-09-03-192738.png

Sir,
As per your suggestion, I have configured these properties in the app. Please review them, I’ll show you now :

This is my media setting in android app :
https://i.postimg.cc/2ScmFRFn/Screenshot-2025-09-04-13-49-34-52-292f262…

These are my meter settings. I have also entered the password in place of "password":
https://i.postimg.cc/Jh0Z7kQZ/IMG-20250904-140116.jpg

This is my security setting with invocation counter:
https://i.postimg.cc/fWpHGwD8/Screenshot-2025-09-04-13-49-50-79-292f262…

This is my security setting with different invocation counter:
https://i.postimg.cc/RC6dQjKK/Screenshot-2025-09-04-13-57-33-07-292f262…

Once I did this, I read the data, and the output was:
https://i.postimg.cc/SswWvxC8/Screenshot-2025-09-04-13-57-59-86-292f262…

I tried using different invocation counters as shown above. When I run it with an empty invocation counter, it gives me an "invalid logical name" error andI have modified the client address, testing with both 48 and 30.

Sir,
This is the meter configuration in Gurux GXDLMSDirector. Using this configuration, I was able to read data, and I entered my actual password in place of "password":
https://i.postimg.cc/02mChFkm/Screenshot-2025-09-04-153122.png
https://i.postimg.cc/25Hd4fGp/Screenshot-2025-09-04-153141.png
https://i.postimg.cc/RC1F8Trh/Screenshot-2025-09-04-153202.png

But when I use the same parameters in your Android app, it does not work. I have already shared the Android configuration in the previous forum post.

Sir,
This is the meter configuration in Gurux GXDLMSDirector. Using this configuration, I was able to read data, and I entered my actual password in place of "password":
https://i.postimg.cc/02mChFkm/Screenshot-2025-09-04-153122.png
https://i.postimg.cc/25Hd4fGp/Screenshot-2025-09-04-153141.png
https://i.postimg.cc/RC1F8Trh/Screenshot-2025-09-04-153202.png

But when I use the same parameters in your Android app, it does not work. I have already shared the Android configuration in the previous forum post.

Sir,
This is the meter configuration in Gurux GXDLMSDirector. Using this configuration, I was able to read data, and I entered my actual password in place of "password":
https://i.postimg.cc/02mChFkm/Screenshot-2025-09-04-153122.png
https://i.postimg.cc/25Hd4fGp/Screenshot-2025-09-04-153141.png
https://i.postimg.cc/RC1F8Trh/Screenshot-2025-09-04-153202.png

But when I use the same parameters in your Android app, it does not work. I have already shared the Android configuration in the previous forum post.

Sir,
The version I’m using is 3.0.4, and the following trace was displayed:

Connecting /dev/bus/usb/001/005
Security level: Authentication Encryption
Block cipher key: 41 45 57 5F 50 57 52 5F 41 4B 5F 45 4B 5F 32 34
Authentication key: 41 45 57 5F 50 57 52 5F 41 4B 5F 45 4B 5F 32 34
<- 18:42:05.475 7E A0 07 03 21 93 0F 01 7E
-> 18:42:05.523 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 18:42:05.526 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 62 1E 5D FF FF 88 55 7E
-> 18:42:05.639 7E A0 37 21 03 30 6C 7C E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 00 10 03 40 00 07 D1 F0 7E
<- 18:42:05.644 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 01 00 00 2B 01 03 FF 02 00 B0 AA 7E
-> 18:42:05.703 7E A0 15 21 03 52 5D 8A E6 E7 00 C4 01 C1 00 06 00 00 00 02 6F 3B 7E
Invocation counter: 3
<- 18:42:05.710 7E A0 07 03 21 53 03 C7 7E
-> 18:42:05.759 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 18:42:05.763 7E A0 07 03 61 93 69 47 7E
-> 18:42:05.812 7E A0 20 61 03 73 05 9E 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 18:42:05.817 7E A0 5B 03 61 10 D8 B3 E6 E6 00 60 4D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 30 31 32 33 34 35 36 37 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 02 80 00 BE 23 04 21 21 1F 30 00 00 00 03 CF EE 2C 2C 4F 70 D4 10 B7 D5 B8 AA FC 99 8B 61 97 B4 1E A7 E3 E0 32 E5 F8 AA 1C 78 7E
-> 18:42:05.994 77 E6 E7 00 61 32 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A1 03 02 01 01 BE 19 04 17 2E 15 30 00 00 00 00 A1 41 75 9A 17 DF 15 1D 96 A1 BD 12 F6 3F D6 2E 8F 0C 7E

Sir,

This is the trace of gurux GXDLMS Director :

19:23:02 Initializing serial connection.
19:23:03 Send SNRM request.
7E A0 07 03 61 93 69 47 7E
19:23:03
7E A0 20 61 03 73 05 9E 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
19:23:03 Parsing UA reply succeeded.
19:23:03 Send AARQ request.
7E A0 6B 03 61 10 2A FF E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 30 31 32 33 34 35 36 37 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 04 6E 4C 12 4D 09 27 59 09 14 49 26 55 13 1D 6D BE 23 04 21 21 1F 30 00 00 00 00 40 D0 27 82 F4 90 B4 12 35 B8 14 B7 87 C4 B0 29 25 C1 E0 53 2C AE 3C F6 CB 50 D9 12 7E
19:23:03
7E A0 77 61 03 30 AD 6C E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 41 4C 4C 00 00 7A 26 C4 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 31 45 4E 45 53 41 53 5F 50 36 77 52 4A 32 31 46 BE 23 04 21 28 1F 30 00 00 00 00 A7 40 70 C5 D3 94 F8 CD 87 44 E0 53 31 B2 36 B4 2F 9B CE AC 96 F3 27 E6 39 40 79 BC 7E
19:23:03 Parsing AARE reply succeeded.
19:23:03 Authenticating.
7E A0 3E 03 61 32 7B 46 E6 E6 00 CB 30 30 00 00 00 01 6B F9 11 12 AB D0 BD A6 87 76 06 52 35 31 97 51 9D 2F E8 78 22 12 C1 DA 66 C7 28 E6 3E 1D 3D A3 08 86 FA A4 F9 17 FB B9 B3 D3 B2 08 AC 7E
19:23:03
7E A0 37 61 03 52 0E 3A E6 E7 00 CF 29 30 00 00 00 01 7A A2 25 2F 20 0E AF E7 90 E1 BA F3 F4 A3 49 A5 51 B3 C6 FA 01 6E FF E6 D5 26 F0 89 34 0E 3B 13 79 D3 0D B1 AB 2D 7E
19:23:05 --- Collecting objects. ---

Sir,

Could you provide your input on the above forum?

Sir,
I am currently working with version 3.0.5 and I am passing the parameter, which can be seen in the screenshot below.
https://i.postimg.cc/Z5BHwTNY/Screenshot-2025-09-08-12-12-39-28-292f262…
https://i.postimg.cc/zfysSZzT/Screenshot-2025-09-08-12-12-46-16-292f262…

but it is not able to read data but it show connected the traces its show me is :
Connecting /dev/bus/usb/001/002
Security level: Authentication Encryption
Block cipher key: 41 45 57 5F 50 57 52 5F 41 4B 5F 45 4B 5F 32 34
Authentication key: 41 45 57 5F 50 57 52 5F 41 4B 5F 45 4B 5F 32 34
<- 11:58:30.695 7E A0 07 03 21 93 0F 01 7E
-> 11:58:30.749 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 11:58:30.759 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 62 1E 5D FF FF 88 55 7E
-> 11:58:30.879 7E A0 37 21 03 30 6C 7C E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 00 10 03 40 00 07 D1 F0 7E
<- 11:58:30.894 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 01 00 00 2B 01 03 FF 02 00 B0 AA 7E
-> 11:58:30.963 7E A0 15 21 03 52 5D 8A E6 E7 00 C4 01 C1 00 06 00 00 00 00 7D 18 7E
Invocation counter: 1
<- 11:58:30.992 7E A0 07 03 21 53 03 C7 7E
-> 11:58:31.052 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 11:58:31.069 7E A0 07 03 61 93 69 47 7E
-> 11:58:31.131 7E A0 20 61 03 73 05 9E 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
<- 11:58:31.153 7E A0 6B 03 61 10 2A FF E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 30 31 32 33 34 35 36 37 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 07 1E 6A 53 60 1A 21 07 15 6C 43 6A 78 6A 35 24 BE 23 04 21 21 1F 30 00 00 00 01 A9 F8 D0 12 A2 8F A2 8A 87 14 E7 0E CB C7 3F 66 47 65 D2 6B 76 68 7D 86 94 D9 3F C8 7E
-> 11:58:31.427 7E A0 77 61 03 30 AD 6C E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 41 4C 4C 00 00 7A 26 C4 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 31 45 4E 45 53 41 53 5F 50 36 77 52 4A 32 31 46 BE 23 04 21 28 1F 30 00 00 00 01 B5 A3 E2 70 3E 0A A6 D7 60 52 90 4C 7F 07 CA 5A 5B DB 50 AB 7A 40 B3 A9 6A 8E 6D 72 7E
<- 11:58:31.462 7E A0 3E 03 61 32 7B 46 E6 E6 00 CB 30 30 00 00 00 02 7A D3 CC 37 01 EE B1 C3 A3 D6 8C 4D 73 55 AE 1B 7B 3D D2 9A 19 4D CC 94 D6 87 B2 D1 48 59 1E 29 C7 0D 9C 86 19 BE A3 0F 87 10 BD 06 47 7E
-> 11:58:31.632 7E A0 37 61 03 52 0E 3A E6 E7 00 CF 29 30 00 00 00 02 4C 23 33 DB 39 F8 C8 5C 56 EF 73 D6 1D 3D 84 B0 31 B3 FE 84 DF 17 3E 47 5F 82 9F 89 01 41 60 72 D5 FA EB 17 EB DD 7E

Sir,
When I tap the read button, the import association view is displayed, but if I click on OK, the app will close or crash after a few seconds​, The attached video demonstrates the challenge I am encountering :
https://drive.google.com/file/d/1KjeyObm9Z-uPBgojwfecN-3quuCnUzz7/view?…
And these log is display on Android Studio :
2025-09-09 02:28:34.255 23146-24747 ux.dlms.android gurux.dlms.android I ThreadFlipBegin blocked for 133.898ms
2025-09-09 02:28:34.255 23146-23146 ux.dlms.android gurux.dlms.android I IncrementDisableThreadFlip blocked for 109.307ms
2025-09-09 02:28:34.277 23146-24747 ux.dlms.android gurux.dlms.android I Background young concurrent copying GC freed 2240KB AllocSpace bytes, 7(148KB) LOS objects, 26% free, 7728KB/10MB, paused 100us,19us total 156.768ms
2025-09-09 02:28:34.852 23146-23146 oplus.andr...actoryImpl gurux.dlms.android I get feature:IOplusDynamicVsyncFeature
2025-09-09 02:28:34.852 23146-23146 oplus.andr...actoryImpl gurux.dlms.android I get feature:IOplusDynamicVsyncFeature
2025-09-09 02:28:34.852 23146-23146 oplus.andr...actoryImpl gurux.dlms.android I get feature:IOplusDynamicVsyncFeature
2025-09-09 02:28:34.858 23146-23146 oplus.andr...actoryImpl gurux.dlms.android I get feature:IOplusDynamicVsyncFeature
2025-09-09 02:28:34.858 23146-23146 oplus.andr...actoryImpl gurux.dlms.android I get feature:IOplusDynamicVsyncFeature
2025-09-09 02:28:34.858 23146-23146 oplus.andr...actoryImpl gurux.dlms.android I get feature:IOplusDynamicVsyncFeature
2025-09-09 02:28:34.872 947-3128 SurfaceFlinger surfaceflinger I [SF client] NEW(0xb40000766feda540) for (23146:gurux.dlms.android)
2025-09-09 02:28:34.874 23146-23146 WindowManager gurux.dlms.android D Add to mViews: DecorView@3d67e0c[MainActivity],pkg= gurux.dlms.android
2025-09-09 02:28:34.881 1562-2741 OplusFullS...layManager system_server D adjustWindowParamsLw gurux.dlms.android, no change cutoutMode: 0
2025-09-09 02:28:34.882 1562-2741 WindowManager system_server V Changing focus from Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity} to Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity},diplayid=0
2025-09-09 02:28:34.885 1562-2741 WindowManager system_server I addWindow: New client android.os.BinderProxy@ae4bef9 : window=Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity}
2025-09-09 02:28:34.886 23146-23146 ViewRootImplExtImpl gurux.dlms.android D onDisplayChanged -1 for VRI android.view.ViewRootImpl@c736ef8
2025-09-09 02:28:34.888 23146-23146 InputEventReceiver gurux.dlms.android D Input log is disabled
2025-09-09 02:28:34.889 23146-23146 Choreographer gurux.dlms.android I Skipped 85 frames! The application may be doing too much work on its main thread.
2025-09-09 02:28:34.889 23146-23146 Quality gurux.dlms.android I Skipped: false 85 cost 1425.0681 refreshRate 16666667 bit true processName gurux.dlms.android
2025-09-09 02:28:34.890 23146-24757 Quality gurux.dlms.android I Blocked msg = Package name: gurux.dlms.android [ schedGroup: 5 schedPolicy: 0 ] process the message: { when=-1s428ms what=0 target=android.os.Handler callback=gurux.dlms.android.ui.main.MainFragment$$ExternalSyntheticLambda15 } took 1414 ms
2025-09-09 02:28:34.890 1562-2741 CoreBackPreview system_server D Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@b9cd8d8, mPriority=0}
2025-09-09 02:28:34.910 1562-2741 OplusFullS...layManager system_server D adjustWindowParamsLw gurux.dlms.android, no change cutoutMode: 0
2025-09-09 02:28:34.910 1562-2741 WindowManager system_server V Relayout Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity}: viewVisibility=0, oldvis=0, req=1026x602
2025-09-09 02:28:34.911 947-1103 BufferQueueDebug surfaceflinger I [gurux.dlms.android/gurux.dlms.android.MainActivity#983](this:0xb400007674a859e8,id:-1,api:0,p:-1,c:-1) BufferQueue core=(947:/system/bin/surfaceflinger)
2025-09-09 02:28:34.925 947-3128 [OSIE] surfaceflinger D scltmLayer_name VRI[MainActivity][gurux.dlms.android/gurux.dlms.android.MainActivity]
2025-09-09 02:28:34.925 23146-23146 BufferQueueConsumer gurux.dlms.android D [](id:5a6a00000002,api:0,p:-1,c:23146) connect: controlledByApp=false
2025-09-09 02:28:34.925 23146-23146 IPCThreadState gurux.dlms.android E attemptIncStrongHandle(57): Not supported
2025-09-09 02:28:34.926 23146-23146 ZoomWindowDecorView gurux.dlms.android V setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.64388620
2025-09-09 02:28:34.930 23146-23146 VRI[MainActivity] gurux.dlms.android D registerCallbacksForSync syncBuffer=false
2025-09-09 02:28:34.944 23146-24762 BLASTBufferQueue gurux.dlms.android D [VRI[MainActivity][gurux.dlms.android/gurux.dlms.android.MainActivity]#2](f:0,a:1) acquireNextBufferLocked size=1218x794 mFrameNumber=1 applyTransaction=true mTimestamp=1412413233314(auto) mPendingTransactions.size=0 graphicBufferId=99411313033233 transform=0
2025-09-09 02:28:34.945 23146-24762 VRI[MainActivity] gurux.dlms.android D Received frameCommittedCallback lastAttemptedDrawFrameNum=1 didProduceBuffer=true syncBuffer=false
2025-09-09 02:28:34.946 23146-24762 Parcel gurux.dlms.android W Expecting binder but got null!
2025-09-09 02:28:34.946 23146-23146 VRI[MainActivity] gurux.dlms.android D draw finished.
2025-09-09 02:28:34.946 23146-23146 VRI[MainActivity] gurux.dlms.android D onFocusEvent false
2025-09-09 02:28:34.948 947-947 BufferStateLayer surfaceflinger D gurux.dlms.android/gurux.dlms.android.MainActivity#983 setBuffer frameId=1, bufferId=99411313033233 fenceId=600, w= 1218, h=794
2025-09-09 02:28:34.948 947-947 OplusLayer surfaceflinger D (983,gurux.dlms.android/gurux.dlms.android.MainActivity#983,gurux.dlms.android) setBuffer
2025-09-09 02:28:34.951 23146-23146 Quality gurux.dlms.android I Skipped: false 3 cost 56.663925 refreshRate 16554565 bit true processName gurux.dlms.android
2025-09-09 02:28:34.952 23146-25083 OpenGLRenderer gurux.dlms.android I Davey! duration=1478ms; Flags=1, FrameTimelineVsyncId=154120, IntendedVsync=1410933357140, Vsync=1412350023835, InputEventId=0, HandleInputStart=1412358847776, AnimationStart=1412358849545, PerformTraversalsStart=1412359128083, DrawStart=1412399407776, FrameDeadline=1410953357140, FrameInterval=1412358425314, FrameStartTime=16554464, SyncQueued=1412406715391, SyncStart=1412409016391, IssueDrawCommandsStart=1412409157007, SwapBuffers=1412412342853, FrameCompleted=1412414648930, DequeueBufferDuration=21230, QueueBufferDuration=551461, GpuCompleted=1412414648930, SwapBuffersCompleted=1412413996930, DisplayPresentTime=0, CommandSubmissionCompleted=1412412342853,
2025-09-09 02:28:34.952 23146-25083 OpenGLRenderer gurux.dlms.android I Davey! duration=1445ms; Flags=0, FrameTimelineVsyncId=154120, IntendedVsync=1410933357140, Vsync=1412350023835, InputEventId=0, HandleInputStart=1412358847776, AnimationStart=1412358849545, PerformTraversalsStart=1412359128083, DrawStart=1412362749314, FrameDeadline=1410969911705, FrameInterval=1412358425314, FrameStartTime=16554565, SyncQueued=1412367104083, SyncStart=1412367178545, IssueDrawCommandsStart=1412367432007, SwapBuffers=1412376246776, FrameCompleted=1412379237930, DequeueBufferDuration=6390692, QueueBufferDuration=241923, GpuCompleted=1412379237930, SwapBuffersCompleted=1412376970545, DisplayPresentTime=1404981225545, CommandSubmissionCompleted=1412376246776,
2025-09-09 02:28:34.954 1562-2741 WindowManager system_server D finishDrawingWindow: Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity} mDrawState=DRAW_PENDING
2025-09-09 02:28:34.965 23146-23146 VRI[MainActivity] gurux.dlms.android D registerCallbacksForSync syncBuffer=false
2025-09-09 02:28:34.969 23146-24762 VRI[MainActivity] gurux.dlms.android D Received frameCommittedCallback lastAttemptedDrawFrameNum=3 didProduceBuffer=true syncBuffer=false
2025-09-09 02:28:34.969 23146-23146 VRI[MainActivity] gurux.dlms.android D draw finished.
2025-09-09 02:28:34.981 1562-2741 WindowManager system_server D finishDrawingWindow: Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity} mDrawState=HAS_DRAWN
2025-09-09 02:28:34.999 1562-2741 FocusResolver system_server I updateFocusedWindow, 32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity on display 0, reason: Window became focusable. Previous reason: NOT_VISIBLE, result: FocusedWindows:
displayId=0, name='32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity'
2025-09-09 02:28:35.000 23146-23146 VRI[MainActivity] gurux.dlms.android D onFocusEvent true
2025-09-09 02:28:35.147 947-947 Layer surfaceflinger D reparent to null sequence=984, seq[26], name=Surface(name=32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity)/@0xda01897 - animation-leash of window_animation#984
2025-09-09 02:28:35.147 947-947 OplusLayer surfaceflinger D ~Layer() sequence=984, name=Surface(name=32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity)/@0xda01897 - animation-leash of window_animation#984
2025-09-09 02:28:37.431 1562-2741 NotificationService system_server W Toast already killed. pkg=gurux.dlms.android token=android.os.BinderProxy@e87aba1
2025-09-09 02:28:40.061 23146-23146 OplusScrollToTopManager gurux.dlms.android D unregisterGuidePopupDismissReceiverInSystemUI
2025-09-09 02:28:40.061 23146-23146 OplusScrollToTopManager gurux.dlms.android D Receiver not registered: android.view.OplusScrollToTopManager$1@2a3432a
2025-09-09 02:28:40.061 23146-23146 OplusScrollToTopManager gurux.dlms.android D unregisterSystemUIBroadcastReceiver
2025-09-09 02:28:40.062 23146-23146 OplusScrollToTopManager gurux.dlms.android D java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@a76951b
2025-09-09 02:28:40.063 1562-4686 CoreBackPreview system_server D Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity}: Setting back callback null
2025-09-09 02:28:40.063 23146-23146 ZoomWindowDecorView gurux.dlms.android V removeZoomView
2025-09-09 02:28:40.065 23146-24762 OpenGLRenderer gurux.dlms.android D endAllActiveAnimators on 0xb400007434672c00 (RippleDrawable) with handle 0xb400007486bdb260
2025-09-09 02:28:40.066 1562-4686 InputManager-JNI system_server W Input channel object '32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity (client)' was disposed without first being removed with the input manager!
2025-09-09 02:28:40.068 1562-4686 WindowManager system_server V Changing focus from Window{32b5e3e u0 gurux.dlms.android/gurux.dlms.android.MainActivity EXITING} to Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity},diplayid=0
2025-09-09 02:28:40.076 23146-24751 BLASTBufferQueue gurux.dlms.android D [VRI[MainActivity][gurux.dlms.android/gurux.dlms.android.MainActivity]#2](f:0,a:3) destructor()
2025-09-09 02:28:40.076 23146-24751 BufferQueueConsumer gurux.dlms.android D [VRI[MainActivity][gurux.dlms.android/gurux.dlms.android.MainActivity]#2(BLAST Consumer)2](id:5a6a00000002,api:0,p:-1,c:23146) disconnect
2025-09-09 02:28:40.077 23146-23146 Quality gurux.dlms.android I Skipped: false 1 cost 24.056725 refreshRate 16666667 bit true processName gurux.dlms.android
2025-09-09 02:28:40.107 1562-4686 FocusResolver system_server I updateFocusedWindow, 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity on display 0, reason: setFocusedWindow, result: FocusedWindows:
displayId=0, name='1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity'
2025-09-09 02:28:40.254 947-947 Layer surfaceflinger D reparent to null sequence=983, seq[4], name=gurux.dlms.android/gurux.dlms.android.MainActivity#983
2025-09-09 02:28:40.255 947-947 Layer surfaceflinger D reparent to null sequence=980, seq[10], name=32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity#980
2025-09-09 02:28:40.255 947-947 Layer surfaceflinger D reparent to null sequence=987, seq[25], name=Surface(name=32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity)/@0xda01897 - animation-leash of window_animation#987
2025-09-09 02:28:40.255 947-947 OplusLayer surfaceflinger D ~Layer() sequence=987, name=Surface(name=32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity)/@0xda01897 - animation-leash of window_animation#987
2025-09-09 02:28:40.255 947-947 OplusLayer surfaceflinger D ~Layer() sequence=980, name=32b5e3e gurux.dlms.android/gurux.dlms.android.MainActivity#980
2025-09-09 02:28:40.257 947-947 BufferQueueDebug surfaceflinger I [gurux.dlms.android/gurux.dlms.android.MainActivity#983](this:0xb400007674a859e8,id:-1,api:0,p:-1,c:947) onDestructor()
2025-09-09 02:28:40.257 947-947 OplusLayer surfaceflinger D ~Layer() sequence=983, name=gurux.dlms.android/gurux.dlms.android.MainActivity#983
2025-09-09 02:28:41.584 23146-25055 Quality gurux.dlms.android I stackInfo :----- pid 23146 at 2025-09-09 02:28:41.582 -----;Cmd line: gurux.dlms.android;"main" prio=5 tid=2 TIMED_WAITING sysTid=23146; at java.lang.Object.wait(Native Method); at java.lang.Object.wait(Object.java:405); at gurux.common.AutoResetEvent.waitOne(AutoResetEvent.java:94); at gurux.common.GXSynchronousMediaBase.findData(GXSynchronousMediaBase.java:378); at gurux.common.GXSynchronousMediaBase.receive(GXSynchronousMediaBase.java:460); at gurux.serial.GXSerial.receive(GXSerial.java:1068); at gurux.dlms.android.ui.main.MainFragment.readDLMSPacket(MainFragment.java:558); at gurux.dlms.android.ui.main.MainFragment.readDataBlock(MainFragment.java:610); at gurux.dlms.android.ui.main.MainFragment.readDataBlock(MainFragment.java:593); at gurux.dlms.android.ui.main.MainFragment.refresh(MainFragment.java:386); at gurux.dlms.android.ui.main.MainFragment.lambda$readAssociationView$0$gurux-dlms-android-ui-main-MainFragment(MainFragment.java:99); at gurux.dlms.android.ui.main.MainFragment$$ExternalSyntheticLambda7.run(D8$$SyntheticClass:0); at android.os.Handler.handleCallback(Handler.java:942); at android.os.Handler.dispatchMessage(Handler.java:99); at android.os.Looper.loopOnce(Looper.java:240); at android.os.Looper.loop(Looper.java:351); at android.app.ActivityThread.main(ActivityThread.java:8377); at java.lang.reflect.Method.invoke(Native Method); at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584); at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013);
2025-09-09 02:28:43.086 23146-25055 Quality gurux.dlms.android I stackInfo :----- pid 23146 at 2025-09-09 02:28:43.085 -----;Cmd line: gurux.dlms.android;"main" prio=5 tid=2 RUNNABLE sysTid=23146; at android.graphics.text.LineBreaker.-$$Nest$smnGetLineFlag(Unknown Source:0); at android.graphics.text.LineBreaker$Result.hasLineTab(LineBreaker.java:418); at android.text.StaticLayout.generate(StaticLayout.java:835); at android.text.DynamicLayout.reflow(DynamicLayout.java:612); at android.text.DynamicLayout$ChangeWatcher.reflow(DynamicLayout.java:1091); at android.text.DynamicLayout$ChangeWatcher.onTextChanged(DynamicLayout.java:1102); at androidx.emoji2.text.SpannableBuilder$WatcherWrapper.onTextChanged(SpannableBuilder.java:390); at androidx.emoji2.text.SpannableBuilder.fireWatchers(SpannableBuilder.java:297); at androidx.emoji2.text.SpannableBuilder.endBatchEdit(SpannableBuilder.java:270); at androidx.emoji2.text.EmojiProcessor.process(EmojiProcessor.java:358); at androidx.emoji2.text.EmojiCompat$CompatInternal19.process(EmojiCompat.java:1777); at androidx.emoji2.text.EmojiCompat.process(EmojiCompat.java:1134); at androidx.emoji2.viewsintegration.EmojiTextWatcher.onTextChanged(EmojiTextWatcher.java:83); at android.widget.TextView.sendOnTextChanged(TextView.java:11173); at android.widget.TextView.handleTextChanged(TextView.java:11288); at android.widget.TextView$ChangeWatcher.onTextChanged(TextView.java:14291); at android.text.SpannableStringBuilder.sendTextChanged(SpannableStringBuilder.java:1268); at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:577); at androidx.emoji2.text.SpannableBuilder.replace(SpannableBuilder.java:315); at android.text.SpannableStringBuilder.append(SpannableStringBuilder.java:292); at androidx.emoji2.text.SpannableBuilder.append(SpannableBuilder.java:360); at androidx.emoji2.text.SpannableBuilder.append(SpannableBuilder.java:49); at android.widget.TextView.append(TextView.java:6163); at android.widget.TextView.append(TextView.java:6144); at gurux.dlms.android.ui.main.MainFragment$2.run(MainFragment.java:478); at android.app.Activity.runOnUiThread(Activity.java:7412); at gurux.dlms.android.ui.main.MainFragment.writeTrace(MainFragment.java:475); at gurux.dlms.android.ui.main.MainFragment.readDLMSPacket(MainFragment.java:579); at gurux.dlms.android.ui.main.MainFragment.readDataBlock(MainFragment.java:610); at gurux.dlms.android.ui.main.MainFragment.readDataBlock(MainFragment.java:593);
2025-09-09 02:28:43.223 23146-24747 ux.dlms.android gurux.dlms.android I ThreadFlipBegin blocked for 76.546ms
2025-09-09 02:28:43.223 23146-23146 ux.dlms.android gurux.dlms.android I IncrementDisableThreadFlip blocked for 47.971ms
2025-09-09 02:28:43.265 23146-24747 ux.dlms.android gurux.dlms.android I Background concurrent copying GC freed 4241KB AllocSpace bytes, 7(204KB) LOS objects, 49% free, 6296KB/12MB, paused 91us,39us total 147.378ms
2025-09-09 02:28:43.619 1562-1906 QUALITY system_server I PRE_ANR: ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity} t165} - 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity
2025-09-09 02:28:45.108 1562-1906 InputDispatcher system_server W Window 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) is unresponsive: 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) is not responding. Waited 5000ms for FocusEvent(hasFocus=true)
2025-09-09 02:28:45.108 1562-1906 InputDispatcher system_server W Canceling events for 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) because it is unresponsive
2025-09-09 02:28:45.108 1562-1906 QUALITY system_server I ANR: ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity} t165} - 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity
2025-09-09 02:28:45.109 1562-1906 WindowManager system_server I ANR in Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity}. Reason:1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) is not responding. Waited 5000ms for FocusEvent(hasFocus=true)
2025-09-09 02:28:45.109 1562-1562 OIM_Policy system_server I receive gesture unResponsive msg, reason = 1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) is not responding. Waited 5000ms for FocusEvent(hasFocus=true) OPLUS_EX_CHANNEL_NAME = OplusExInputReceiver1
2025-09-09 02:28:45.163 1562-25695 OplusWindo...rolService system_server W respondANR: all info about WindowContainer: Stack: Counter{ }; Task: Counter{ gurux.dlms.android/.MainActivity(1) } Counter{ com.android.launcher/.Launcher(1) }
2025-09-09 02:28:45.164 1562-25695 OplusWindo...rolService system_server W respondANR: all info about WindowContainer: Stack: Counter{ }; Task: Counter{ gurux.dlms.android/.MainActivity(1) } Counter{ com.android.launcher/.Launcher(1) }
2025-09-09 02:28:45.164 1562-25695 OplusWindo...rolService system_server W respondANR: all info about WindowContainer: Stack: Counter{ }; Task: Counter{ gurux.dlms.android/.MainActivity(1) } Counter{ com.android.launcher/.Launcher(1) }
2025-09-09 02:28:45.210 1562-25695 OplusWindo...rolService system_server W respondANR: all info about WindowContainer: Stack: Counter{ }; Task: Counter{ gurux.dlms.android/.MainActivity(1) } Counter{ com.android.launcher/.Launcher(1) }
2025-09-09 02:28:45.215 1562-25695 ITheiaManagerExt system_server W [sendEvent] {0x3 1422683 0x10001003 23146 10331 gurux.dlms.android} reported frequently, then we return.
2025-09-09 02:28:45.215 1562-25695 ActivityManager system_server D TheiaManager sendEvent:gurux.dlms.android ANR happen
2025-09-09 02:28:45.815 23146-24743 ux.dlms.android gurux.dlms.android I Thread[2,tid=24743,WaitingInMainSignalCatcherLoop,Thread*=0xb4000074a4626000,peer=0x2e00280,"Signal Catcher"]: reacting to signal 3
2025-09-09 02:28:45.815 23146-24743 ux.dlms.android gurux.dlms.android I
2025-09-09 02:28:46.067 23146-24743 ux.dlms.android gurux.dlms.android I Wrote stack traces to tombstoned
2025-09-09 02:28:49.458 1562-25695 ActivityManager system_server E ANR in gurux.dlms.android (gurux.dlms.android/.MainActivity)
PID: 23146
Reason: Input dispatching timed out (1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) is not responding. Waited 5000ms for FocusEvent(hasFocus=true))
Parent: gurux.dlms.android/.MainActivity
ErrorId: f5d225c7-b996-48bb-90c5-bc8eeccd8b32
Frozen: false
Load: 20.66 / 19.98 / 16.26
----- Output from /proc/pressure/memory -----
some avg10=0.00 avg60=0.00 avg300=0.00 total=2150933
full avg10=0.00 avg60=0.00 avg300=0.00 total=710492
----- End output from /proc/pressure/memory -----

CPU usage from 45387ms to 0ms ago (2025-09-09 02:27:59.777 to 2025-09-09 02:28:45.164):
18% 23146/gurux.dlms.android: 14% user + 3.8% kernel / faults: 12184 minor
11% 1562/system_server: 7.5% user + 3.8% kernel / faults: 8384 minor
9.4% 947/surfaceflinger: 6.1% user + 3.3% kernel / faults: 1134 minor
7.4% 4548/com.google.android.inputmethod.latin: 7.1% user + 0.3% kernel / faults: 8575 minor
4.4% 834/android.hardware.graphics.composer@2.3-service: 1.8% user + 2.6% kernel / faults: 8 minor
4.3% 2146/com.android.systemui: 2.7% user + 1.5% kernel / faults: 6033 minor
1.4% 2372/com.android.phone: 1% user + 0.4% kernel / faults: 2029 minor
1.2% 3607/com.google.android.gms.persistent: 0.8% user + 0.3% kernel / faults: 1736 minor
1% 1177/adbd: 0.2% user + 0.8% kernel / faults: 409 minor
0.3% 829/android.hardware.audio.service.mediatek: 0.2% user + 0.1% kernel / faults: 352 minor
0.9% 2075/hif_thread: 0% user + 0.9% kernel
0.9% 563/logd: 0.3% user + 0.5% kernel / faults: 637 minor
0.9% 2074/main_thread: 0% user + 0.9% kernel
0.7% 17581/process-tracker: 0.1% user + 0.6% kernel / faults: 38 minor
0.7% 1018/kworker/u25:5-rx4_worker: 0% user + 0.7% kernel
0.6% 941/audioserver: 0.4% user + 0.1% kernel / faults: 212 minor
0.6% 1645/mtkfusionrild: 0.4% user + 0.1% kernel / faults: 4 minor
0.5% 17945/logcat: 0.1% user + 0.4% kernel
0% 1228/mediaserver: 0% user + 0% kernel / faults: 424 minor 5 major
0.5% 815/zygote64: 0% user + 0.4% kernel / faults: 2107 minor
0.5% 22526/kworker/u25:8-erofs_unzipd: 0% user + 0.5% kernel
0.5% 2276/com.android.networkstack.process: 0.4% user + 0% kernel / faults: 1101 minor
0.4% 1290/vendor.mediatek.hardware.pq@2.2-service: 0.3% user + 0.1% kernel
0.4% 854/vendor.mediatek.hardware.mtkpower@1.0-service: 0.1% user + 0.2% kernel
0.4% 22332/kworker/u24:0-events_unbound: 0% user + 0.4% kernel
0.3% 1875/kworker/u24:15-events_unbound: 0% user + 0.3% kernel
0.3% 235/pbm: 0% user + 0.3% kernel
0.3% 2396/com.oplus.athena: 0.2% user + 0% kernel / faults: 1083 minor
0% 85/oom_reaper: 0% user + 0% kernel
0.3% 813/statsd: 0.1% user + 0.1% kernel / faults: 12 minor
0.3% 23685/kworker/u24:4-events_unbound: 0% user + 0.3% kernel
0.2% 133/dlpt_notify_thr: 0% user + 0.2% kernel
0% 1375/media.swcodec: 0% user + 0% kernel / faults: 147 minor
0.2% 2077/rx_thread: 0% user + 0.2% kernel
0.1% 229/kworker/u25:1-rx4_worker: 0% user + 0.1% kernel
0.1% 417/ipi_cpu_dvfs_rt: 0% user + 0.1% kernel
0.1% 565/servicemanager: 0.1% user + 0% kernel
0.1% 4082/android.process.acore: 0.1% user + 0% kernel / faults: 538 minor
0.1% 5215/com.oplus.deepthinker: 0% user + 0.1% kernel / faults: 112 minor
0.1% 24310/irq/185-touchpa: 0% user + 0.1% kernel
0.1% 11/rcu_preempt: 0% user + 0.1% kernel
0.1% 387/oplus_rmfb_thre: 0% user + 0.1% kernel
0.1% 839/android.hardware.sensors@2.0-service.multihal-mediatek: 0% user + 0% kernel
0.1% 2404/com.oplus.subsys: 0% user + 0% kernel / faults: 26 minor
0.1% 4883/com.lianhezhuli.hyfit: 0% user + 0% kernel / faults: 72 minor
0.1% 23729/kworker/4:2-events: 0% user + 0.1% kernel
0.1% 406/sf_pf_release_t: 0% user + 0.1% kernel
0.1% 496/ueventd: 0% user + 0% kernel
0.1% 1211/cameraserver: 0% user + 0% kernel / faults: 164 minor
0.1% 1581/gsm0710muxd: 0% user + 0% kernel
0.1% 19051/kworker/u24:7-events_unbound: 0% user + 0.1% kernel
2025-09-09 02:28:49.458 1562-25695 ActivityManager system_server E +0% 25061/kworker/1:2-events: 0% user + 0% kernel
+0% 25072/kworker/7:1-sock_diag_events: 0% user + 0% kernel
+0% 25085/com.google.android.googlequicksearchbox:search: 0% user + 0% kernel
+0% 25122/com.google.process.gservices: 0% user + 0% kernel
+0% 25156/com.oplus.midas: 0% user + 0% kernel
+0% 25174/com.facebook.services: 0% user + 0% kernel
+0% 25188/com.oplus.powermonitor: 0% user + 0% kernel
+0% 25197/com.truecaller: 0% user + 0% kernel
+0% 25220/com.oplus.cosa: 0% user + 0% kernel
+0% 25546/com.oplus.onetrace: 0% user + 0% kernel
+0% 25623/com.whatsapp: 0% user + 0% kernel
13% TOTAL: 7.5% user + 4.2% kernel + 0% iowait + 1% irq + 0.3% softirq
CPU usage from 96ms to 609ms later (2025-09-09 02:28:45.260 to 2025-09-09 02:28:45.773):
68% 563/logd: 0% user + 68% kernel / faults: 626 minor
55% 1562/system_server: 16% user + 38% kernel / faults: 845 minor
47% 25695/AnrConsumer: 11% user + 35% kernel
4.7% 1937/WifiHandlerThre: 2.3% user + 2.3% kernel
4.7% 2400/binder:1562_8: 2.3% user + 2.3% kernel
+0% 25738/AnrCrashDebug#6: 0% user + 0% kernel
18% 23146/gurux.dlms.android: 14% user + 3.6% kernel / faults: 3 minor
7.2% 25487/Thread-4: 3.6% user + 3.6% kernel
3.6% 23146/ux.dlms.android: 3.6% user + 0% kernel
3.8% 1/init: 1.9% user + 1.9% kernel / faults: 111 minor
1.9% 1/init: 0% user + 1.9% kernel
2.2% 839/android.hardware.sensors@2.0-service.multihal-mediatek: 0% user + 2.2% kernel
2.2% 1177/adbd: 0% user + 2.2% kernel / faults: 1 minor
2.2% 17477/adbd: 0% user + 2.2% kernel
2.4% 2074/main_thread: 0% user + 2.4% kernel
3.5% 22333/kworker/u24:1-events_power_efficient: 0% user + 3.5% kernel
59% TOTAL: 22% user + 34% kernel + 0.2% iowait + 1.2% irq + 0.4% softirq
2025-09-09 02:28:49.460 1562-25695 OplusWindo...rolService system_server W respondANR: all info about WindowContainer: Stack: Counter{ }; Task: Counter{ gurux.dlms.android/.MainActivity(1) } Counter{ com.android.launcher/.Launcher(1) }
2025-09-09 02:28:49.462 2108-2131 abnormalUtils com.oplus.exsystemservice D gurux.dlms.android is foreground =true
2025-09-09 02:28:49.462 1562-25695 ActivityManager system_server D Completed ANR of gurux.dlms.android in 4299ms, latency 0ms
2025-09-09 02:28:49.463 1562-1652 OplusWindo...rolService system_server W respondANR: all info about WindowContainer: Stack: Counter{ }; Task: Counter{ gurux.dlms.android/.MainActivity(1) } Counter{ com.android.launcher/.Launcher(1) }
2025-09-09 02:28:49.463 1562-1652 ActivityTaskManager system_server W Force finishing activity gurux.dlms.android/.MainActivity
2025-09-09 02:28:49.466 1562-1652 WindowManager system_server V Changing focus from Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity} to null,diplayid=0
2025-09-09 02:28:49.467 1562-1652 OplusZoomW...gerService system_server V prepareZoomTransition: curStack=Task{c646f9e #165 type=standard A=10331:gurux.dlms.android U=0 visible=false visibleRequested=true mode=fullscreen translucent=true sz=1} nextStackTask{33e12b9 #1 type=home ?? U=0 visible=true visibleRequested=false mode=fullscreen translucent=true sz=1}
2025-09-09 02:28:49.474 1562-1652 ActivityManager system_server I Killing 23146:gurux.dlms.android/u0a331 (adj 0): user request after error:Input dispatching timed out (1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (server) is not responding. Waited 5000ms for FocusEvent(hasFocus=true))
---------------------------- PROCESS ENDED (23146) for package gurux.dlms.android ----------------------------
2025-09-09 02:28:49.553 1562-4712 WindowManager system_server I WIN DEATH: Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity}
2025-09-09 02:28:49.553 1562-4712 InputManager-JNI system_server W Input channel object '1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity (client)' was disposed without first being removed with the input manager!
2025-09-09 02:28:49.555 947-979 SurfaceFlinger surfaceflinger I [SF client] REMOVE (0xb40000766feda540) for (23146:gurux.dlms.android)
2025-09-09 02:28:49.555 947-3128 SurfaceFlinger surfaceflinger I [SF client] REMOVE (0xb4000076701b3280) for (23146:gurux.dlms.android)
2025-09-09 02:28:49.559 1562-2472 OplusHansManager system_server I onUidGone(), 10331 gurux.dlms.android exit SM
2025-09-09 02:28:49.561 1562-4686 OplusUIFirst_FB system_server D gurux.dlms.android remove pid: 23146
2025-09-09 02:28:49.561 1562-4686 mtkpower_client system_server I [Legacy][PowerHal_Wrap_notifyAppState] gurux.dlms.android/gurux.dlms.android pid=23146 state:3
2025-09-09 02:28:49.561 1562-4686 game_scn system_server I collectForegroundAppList packName=gurux.dlms.android, actName=gurux.dlms.android, pid=23146, uid=10331, state:DEAD
2025-09-09 02:28:49.564 1562-4686 OplusHansManager system_server I front pkg: com.android.launcher, uid: 10094, prev pkg: gurux.dlms.android, prev uid: 10331
2025-09-09 02:28:49.565 1562-2052 Osense-DecisionMaker system_server I notifySceneToAthenaPolicy: SCENE_LAUNCHER, bundle: Bundle[{prevPkgName=gurux.dlms.android, curUid=10094, curPkgName=com.android.launcher, prevUid=10331}]
2025-09-09 02:28:49.566 1562-2475 OplusResou...oadManager system_server I resume pkg: com.android.launcher, uid:10094, prev pkg: gurux.dlms.android, prev uid: 10331
2025-09-09 02:28:49.615 1562-1655 WindowManager system_server W Failed to deliver inset state change to w=Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity EXITING}
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:672)
at android.view.IWindow$Stub$Proxy.insetsControlChanged(IWindow.java:473)
at com.android.server.wm.WindowState.notifyInsetsControlChanged(WindowState.java:4298)
at com.android.server.wm.InsetsStateController.lambda$notifyPendingInsetsControlChanged$5$com-android-server-wm-InsetsStateController(InsetsStateController.java:540)
at com.android.server.wm.InsetsStateController$$ExternalSyntheticLambda4.run(Unknown Source:2)
at com.android.server.wm.WindowAnimator.executeAfterPrepareSurfacesRunnables(WindowAnimator.java:357)
at com.android.server.wm.WindowAnimator.animate(WindowAnimator.java:238)
at com.android.server.wm.WindowAnimator.lambda$new$1$com-android-server-wm-WindowAnimator(WindowAnimator.java:114)
at com.android.server.wm.WindowAnimator$$ExternalSyntheticLambda1.doFrame(Unknown Source:2)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1386)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1396)
at android.view.Choreographer.doCallbacks(Choreographer.java:1033)
at android.view.Choreographer.doFrame(Choreographer.java:912)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1371)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
2025-09-09 02:28:49.636 1562-1655 WindowManager system_server W Exception thrown during dispatchAppVisibility Window{1a69dcf u0 gurux.dlms.android/gurux.dlms.android.MainActivity EXITING}
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:672)
at android.view.IWindow$Stub$Proxy.dispatchAppVisibility(IWindow.java:536)
at com.android.server.wm.WindowState.sendAppVisibilityToClients(WindowState.java:3749)
at com.android.server.wm.WindowContainer.sendAppVisibilityToClients(WindowContainer.java:1266)
at com.android.server.wm.WindowToken.setClientVisible(WindowToken.java:421)
at com.android.server.wm.ActivityRecord.setClientVisible(ActivityRecord.java:7357)
at com.android.server.wm.ActivityRecord.onAnimationFinished(ActivityRecord.java:8231)
at com.android.server.wm.ActivityRecord.postApplyAnimation(ActivityRecord.java:5886)
at com.android.server.wm.ActivityRecord.commitVisibility(ActivityRecord.java:5858)
at com.android.server.wm.ActivityRecord.commitVisibility(ActivityRecord.java:5862)
at com.android.server.wm.AppTransitionController.handleClosingApps(AppTransitionController.java:1252)
at com.android.server.wm.AppTransitionController.handleAppTransitionReady(AppTransitionController.java:309)
at com.android.server.wm.RootWindowContainer.checkAppTransitionReady(RootWindowContainer.java:1074)
at com.android.server.wm.RootWindowContainer.performSurfacePlacementNoTrace(RootWindowContainer.java:916)
at com.android.server.wm.RootWindowContainer.performSurfacePlacement(RootWindowContainer.java:858)
at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementLoop(WindowSurfacePlacer.java:177)
at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement(WindowSurfacePlacer.java:126)
at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement(WindowSurfacePlacer.java:115)
at com.android.server.wm.WindowSurfacePlacer$Traverser.run(WindowSurfacePlacer.java:57)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
2025-09-09 02:28:49.636 1562-1655 OplusZoomW...gerService system_server V onAnimationFinished: r = ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity} t165 f} isExiting}
2025-09-09 02:28:49.645 947-947 Layer surfaceflinger D reparent to null sequence=933, seq[6], name=gurux.dlms.android/gurux.dlms.android.MainActivity#933
2025-09-09 02:28:49.645 947-947 Layer surfaceflinger D reparent to null sequence=932, seq[9], name=1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity#932
2025-09-09 02:28:49.646 947-947 OplusLayer surfaceflinger D ~Layer() sequence=932, name=1a69dcf gurux.dlms.android/gurux.dlms.android.MainActivity#932
2025-09-09 02:28:49.648 947-947 BufferQueueDebug surfaceflinger I [gurux.dlms.android/gurux.dlms.android.MainActivity#933](this:0xb40000766ff339e8,id:-1,api:0,p:-1,c:947) onDestructor()
2025-09-09 02:28:49.648 947-947 OplusLayer surfaceflinger D ~Layer() sequence=933, name=gurux.dlms.android/gurux.dlms.android.MainActivity#933
2025-09-09 02:28:49.661 1562-1655 OplusScreenSecurityMask system_server I onStackRemoved task = Task{c646f9e #165 type=standard A=10331:gurux.dlms.android U=0 visible=false visibleRequested=false mode=fullscreen translucent=true sz=0} record = null displayId = 0
2025-09-09 02:28:49.661 1562-1655 OplusAlwaysAliveManager system_server D removing: 165, ComponentInfo{gurux.dlms.android/gurux.dlms.android.GXSplashScreen}
2025-09-09 02:28:49.662 1562-1655 TaskFragmentExtImpl system_server D remove ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity} t-1 f}} to mActivityRecordSum = Counter{ }
2025-09-09 02:28:49.677 947-947 Layer surfaceflinger D reparent to null sequence=928, seq[4], name=ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity}#928
2025-09-09 02:28:49.678 947-947 OplusLayer surfaceflinger D ~Layer() sequence=928, name=ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity}#928
2025-09-09 02:28:49.678 947-947 OplusLayer surfaceflinger D ~Layer() sequence=940, name=2654ba6 ActivityRecordInputSink gurux.dlms.android/.MainActivity#940
2025-09-09 02:28:49.715 1562-4712 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android
2025-09-09 02:28:49.717 1562-4712 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android
2025-09-09 02:28:49.965 1562-1654 ActivityTaskManager system_server W Activity top resumed state loss timeout for ActivityRecord{9d5e101 u0 gurux.dlms.android/.MainActivity} t-1 f}}
2025-09-09 02:28:49.965 1562-1654 PowerHalWrapper system_server I amsBoostNotify pid:2432,activity:com.android.launcher.Launcher, package:com.android.launcher, mProcessCreatePackgurux.dlms.android
2025-09-09 02:28:49.966 1562-2606 OplusAppSwitchListener system_server D Detect gurux.dlms.android switch to background
2025-09-09 02:28:49.966 854-863 mtkpower@impl ven...hardware.mtkpower@1.0-service I [notifyAppState] pc:0, gurux.dlms.android => com.android.launcher
2025-09-09 02:28:49.966 1562-2606 OplusEapManager system_server D mTargetExitName :gurux.dlms.android
2025-09-09 02:28:49.966 1562-2606 DCSEX-AppSwitchManager system_server V OnAppSwitchObserver: onAppExit, resuming = com.android.launcher, target = gurux.dlms.android, is ResumingFirstStart = false, is ResumingMultiApp = false, extensionInfo = Bundle[{taskId=3, uid=10094}]
2025-09-09 02:28:49.966 1562-2606 VRR [OPlus...ppManager] system_server D OnAppSwitchObserver: onAppExit , info.targetName = gurux.dlms.android
2025-09-09 02:28:49.966 1562-8149 DCSEX-AppL...ntRecorder system_server D onAppSwitch from = gurux.dlms.android to = com.android.launcher
2025-09-09 02:28:49.966 1562-1782 VRR [OPlus...teManager] system_server D setFrontPackageName pkgName: null CurPkgName: gurux.dlms.android
2025-09-09 02:28:49.966 1562-8149 DCSEX-AppL...ntRecorder system_server D recordExitApp = gurux.dlms.android
2025-09-09 02:28:49.968 1562-3862 VRR [OPlus...teService] system_server D setFrameRateTargetControl [ 0.0 , gurux.dlms.android , false , com.oplus.battery ]
2025-09-09 02:28:49.968 1562-3862 VRR [OPlus...teManager] system_server D [FRTC] FrameRate : 0 gurux.dlms.android false com.oplus.battery 0 1000
2025-09-09 02:28:49.969 2396-2421 Athena com.oplus.athena I AthenaDynamicReceiver: pre_app:gurux.dlms.android, next_app:com.android.launcher(10094|2432)
2025-09-09 02:28:49.970 1562-1782 VRR [OPlus...ontroller] system_server D add frtc FrameRate : 0 gurux.dlms.android false com.oplus.battery
2025-09-09 02:28:49.970 947-3128 VRR [FRTC] surfaceflinger I setFrameRateTarget with [0, gurux.dlms.android, 0, com.oplus.battery, 1, 0, 1000]
2025-09-09 02:28:49.970 947-3128 VRR [FRTC] surfaceflinger W invalid param { fps 0, proc_name gurux.dlms.android, strict_mode 0, description com.oplus.battery, proc_id 0, rate_status 0, backend Surface, version 1, pid 0, uid 1000, enable at 2025-09-09 02:28:49, disable waiting } for current status.
2025-09-09 02:28:52.647 1562-1562 TrimMemoryHandler system_server D Unable do gfx trim on fg process: ProcessRecord{994b64f 0:gurux.dlms.android/u0a331}, state=2
2025-09-09 02:28:54.720 1562-4712 PowerHalWrapper system_server I amsBoostNotify pid:4515,activity:com.google.android.apps.search.lens.LensActivity, package:com.google.android.googlequicksearchbox, mProcessCreatePackgurux.dlms.android
2025-09-09 02:28:54.722 1562-4712 PowerHalWrapper system_server I amsBoostNotify pid:2432,activity:com.android.launcher.Launcher, package:com.android.launcher, mProcessCreatePackgurux.dlms.android
2025-09-09 02:28:54.824 1562-4712 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android
2025-09-09 02:28:54.884 1562-4657 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android
2025-09-09 02:28:55.202 1562-4657 PowerHalWrapper system_server I amsBoostNotify pid:2432,activity:com.android.launcher.Launcher, package:com.android.launcher, mProcessCreatePackgurux.dlms.android
2025-09-09 02:28:55.805 1562-3862 PowerHalWrapper system_server I amsBoostNotify pid:25085,activity:com.google.android.apps.search.assistant.surfaces.voice.robin.ui.floaty.activity.FloatyActivity, package:com.google.android.googlequicksearchbox, mProcessCreatePackgurux.dlms.android
2025-09-09 02:28:55.812 1562-3862 PowerHalWrapper system_server I amsBoostNotify pid:4515,activity:com.google.android.apps.search.lens.LensActivity, package:com.google.android.googlequicksearchbox, mProcessCreatePackgurux.dlms.android
2025-09-09 02:29:03.568 947-947 OplusLayer surfaceflinger D ~Layer() sequence=925, name=Surface(name=a160a3b gurux.dlms.android/gurux.dlms.android.GXSplashScreen)/@0xfb0a770 - animation-leash of starting_reveal#925
2025-09-09 02:29:19.403 1562-3862 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android
2025-09-09 02:29:59.595 1562-2835 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android
2025-09-09 02:30:19.594 1562-2835 OplusAppLi...eptManager system_server D shouldFilterTask::packageName = gurux.dlms.android

Sir,
I am using the latest version 3.0.5 and my android phone version is 13

Sir,
I am using the latest version 3.0.5

Sir,
As per your suggestion, I attempted to connect with the meter and recorded the process. Please have a look at the recording.

https://drive.google.com/file/d/1LQXvi0TnYaRCEMOQpDKhMzMXGY3X8-Al/view?…

Sir,
can you tell me the mininimum configuration required for this progam like RAM,Processor ?

Sir,

Could you provide your input on the above forum?

Sir,
Today, I was able to make small changes in the code and successfully download the association. However, I still cannot see the Disconnect Control enabled. Could you please clarify what is required to enable it? In our handshake, we sent the security request with Get/Set conformances, but the meter is only replying with Get. What steps are needed to perform actions like setting the clock or disconnect control on the meter using the probe? I am also providing a video of my testing for reference:

https://drive.google.com/file/d/1aOY9URfT-ejc9wpUjuZUkA7rXaB2RqUK/view?…

Sir,

In the Gurux DLMS Director application, it shows the option: Disconnect Control:

https://i.postimg.cc/VLxgjPjT/Screenshot-2025-09-11-123053.png

I also checked the access rights, and it shows the following:
https://i.postimg.cc/8Pw2mHpM/Screenshot-2025-09-11-125503.png
After making some modifications, the application now displays different logical names. However, I am still unable to access the corresponding values. I have also provided a video for reference
https://drive.google.com/file/d/134UadiIFalVnZUjugqFmq6oTGeUEua_v/view?…

This is the Android application framework in which we send different types of conformance bit names. However, it only displays the 'get' operation:

<AssociationRequest>
<ApplicationContextName Value="LN" />
<InitiateRequest>
<ProposedDlmsVersionNumber Value="06" />
<ProposedConformance>
<ConformanceBit Name="GeneralProtection" />
<ConformanceBit Name="GeneralBlockTransfer" />
<ConformanceBit Name="DeltaValueEncoding" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithAction" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="Access" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Action" />
</ProposedConformance>
<ProposedMaxPduSize Value="FFFF" />
</InitiateRequest>
</AssociationRequest>
</PDU>
</HDLC>
4: 7E A0 37 21 03 30 6C 7C E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 00 10 03 40 00 07 D1 F0 7E
<HDLC len="36" >
<TargetAddress Value="10" />
<SourceAddress Value="1" />
<!-- AARE frame. -->
<FrameType Value="30" />
<PDU>
<AssociationResponse>
<ApplicationContextName Value="LN" />
<AssociationResult Value="00" />
<ResultSourceDiagnostic>
<ACSEServiceUser Value="00" />
</ResultSourceDiagnostic>
<InitiateResponse>
<NegotiatedDlmsVersionNumber Value="06" />
<NegotiatedConformance>
<ConformanceBit Name="Get" />
</NegotiatedConformance>
<NegotiatedMaxPduSize Value="0340" />
<VaaName Value="0007" />
</InitiateResponse>
</AssociationResponse>
</PDU>
</HDLC>

This is my Gurux DLMS Director frame:

<AssociationRequest>
<ApplicationContextName Value="LN_WITH_CIPHERING" />
<CallingAPTitle Value="3031323334353637" />
<SenderACSERequirements Value="1" />
<MechanismName Value="High" />
<CallingAuthentication Value="721D1C4A3D3917674556197967383337" />
<!-- Decrypt failed. Invalid authentication tag. -->
<!-- Decrypted data:
Security: AuthenticationEncryption
Invocation Counter: 0
# Error: Failed to decrypt data.
-->
<glo_InitiateRequest Value="300000000040D02782F490B41235B814B787C4B02925C1E0532CAE3CF6CB50" />
</AssociationRequest>
</PDU>
</HDLC>
4: 7E A0 77 61 03 30 AD 6C E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 41 4C 4C 00 00 7A 26 C4 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 31 45 4E 45 53 41 53 5F 50 36 77 52 4A 32 31 46 BE 23 04 21 28 1F 30 00 00 00 00 A7 40 70 C5 D3 94 F8 CD 87 44 E0 53 31 B2 36 B4 2F 9B CE AC 96 F3 27 E6 39 40 79 BC 7E
<HDLC len="76" >
<TargetAddress Value="30" />
<SourceAddress Value="1" />
<!-- AARE frame. -->
<FrameType Value="30" />
<PDU>
<AssociationResponse>
<ApplicationContextName Value="LN_WITH_CIPHERING" />
<AssociationResult Value="00" />
<ResultSourceDiagnostic>
<!-- AuthenticationRequired -->
<ACSEServiceUser Value="0E" />
</ResultSourceDiagnostic>
<!-- DLMS system title:
Manufacturer Code: ALL
Serial number: 8005316
-->
<RespondingAPTitle Value="414C4C00007A26C4" />
<ResponderACSERequirement Value="1" />
<MechanismName Value="High" />
<RespondingAuthentication Value="31454E455341535F503677524A323146" />
<!-- Decrypt failed. Invalid authentication tag. -->
<!-- Decrypted data:
Security: AuthenticationEncryption
Invocation Counter: 0
# Error: Failed to decrypt data.
-->
<glo_InitiateResponse Value="3000000000A74070C5D394F8CD8744E05331B236B42F9BCEAC96F327E63940" />
</AssociationResponse>
</PDU>

Sir,
In Gurux DLMS Director, we use the same meter settings and other configurations, and we are able to read the data properly. Additionally, with the use of the Disconnection Control, we can successfully perform reconnection and disconnection operations.
However, in the Android application, although the Association View is accessible and logical names are displayed, the actual values are not shown. Furthermore, I have not used the Disconnection Control feature in the Android app."

Sir,
I am using the latest version of the Gurux DLMS Android Client (3.06) and facing some issues.
In the Android app, after importing the Association View, I can see the logical names of objects. However, when I tap on an object, it only displays the entries and headers but does not show the actual values.

I also tested the Disconnection Control object. Although it appears enabled, the reconnection and disconnection options are not accessible.

I have attached a video of the testing process for reference. Could you please review it and guide me on how to properly connect with the meter in the Android application?
https://drive.google.com/file/d/1GDsaMk9UKopSZ4jA4k0r_nELC6OpHqAf/view?…

Sir,
I am using the latest version of the Gurux DLMS Android Client (3.06) and facing some issues.
In the Android app, after importing the Association View, I can see the logical names of objects. However, when I tap on an object, it only displays the entries and headers but does not show the actual values.

I also tested the Disconnection Control object. Although it appears enabled, the reconnection and disconnection options are not accessible.

I have attached a video of the testing process for reference. Could you please review it and guide me on how to properly connect with the meter in the Android application?
https://drive.google.com/file/d/1GDsaMk9UKopSZ4jA4k0r_nELC6OpHqAf/view?…