Skip to content

The 50% glitch #1

Description

@GI-STANDARDS

Recent test shows

  • this application assume 50% to 100% as full potential
  • below 50% is dead zone because the actual calculation is present in 50% to 100% on some machine it consider 50% = 100 and 100% = 100 so every point in between 50-100 is calculated as 2x to complete the 100% potential
  • this catch is 60% to 70% accurate as we faced on some device we are trying on different screens to get the data to calculate the root issue
  • this issue is with sometime screen sometime with machine

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions