[Bug]: More accurate freespace size #19

Closed
opened 2024-03-21 16:35:59 +01:00 by moon-cacke · 0 comments

Hi,

Thanks again for your amazing work :)

Currently the free space is indicated in 'kB' which normally correspond to kilobyte but the displayed value is in kilobits... thus the app display more available space compared to the real value...

For instance I have an empty card that display 501 kB free space when it have 489 KB free space in reality.

A simple conversion from bits to byte may be needed to fix the issue (/1024)

Lastly the value seems to be rounded, it would be cool if you round the value to 2 decimal places (xxx,xx KB)

Thanks a lot :)

Hi, Thanks again for your amazing work :) Currently the free space is indicated in 'kB' which normally correspond to kilobyte but the displayed value is in kilobits... thus the app display more available space compared to the real value... For instance I have an empty card that display 501 kB free space when it have 489 KB free space in reality. A simple conversion from bits to byte may be needed to fix the issue (/1024) Lastly the value seems to be rounded, it would be cool if you round the value to 2 decimal places (xxx,xx KB) Thanks a lot :)
moon-cacke changed title from [Bug]: More accurate freespace to [Bug]: More accurate freespace size 2024-03-21 20:53:27 +01:00
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: PeterCxy/OpenEUICC#19
No description provided.