Describe the bug

Hi! Attempting an UTF_8 searches on version 0.3; fails on Encoding. Performing another DataTypes is working but it's not for text related searches. Using a provided template also fails, the console omits the following:

Traceback (most recent call last):
  File "/data/media/0/Pictures/test.py", line 6, in <module>
    values = tool.read_value('Traffic')
  File "/data/data/com.termux/files/usr/lib/python3.10/site-packages/androidMemoryTool/androidMemoryTool.py", line 46, in read_value
    self._SearchAndReadObject.search_and_read_text(proc_id, maps_addr, value_to_read)
  File "/data/data/com.termux/files/usr/lib/python3.10/site-packages/androidMemoryTool/search_and_readers.py", line 122, in search_and_read_text
    byte_strings = mem_file.read(total_bytes)
OSError: [Errno 5] I/O error

To Reproduce

A code snippet to reproduce the same behavior:

tool = AndroidMemoryTool(PKG="com.emanuelef.remote_capture", TYPE=AndroidMemoryTool.DataTypes.UTF_8, SPEED_MODE=False, WORKERS=55,
                        pMAP=AndroidMemoryTool.PMAP(ALL=True))
values = tool.read_value('Traffic')
founded_values = values[1]
print(founded_values)

Expected behavior

Performing searches with another DataTypes (DWORD) returns expected number of values exist. Using the provided template:

2062
['0x25b00c98', '0x25b02d9c', '0x25b049d0',....]

Screenshots

image

Specification

• Device: LDPlayer 9
• OS: Android 9
• Version: androidMemoryTool 0.3

Additional context

I/O Error
Running a workable searches (DWORD) still also omits I/O Error exception, although the result is working fine. Is this a normal behaviour that should be ignored?
image

Documentation
I hope there's more documentation or examples for each DataTypes. Especially for recent 0.3, this is a bummer with such a great tool.