Incorrect Current/Wattage Parsing and Unread Cycle Counts on Samsung Galaxy A15 5G (MediaTek Dimensity 6100+)

On the Samsung Galaxy A15 5G running One UI, Amply reads charging current as 0W (or 1mA), and charge cycles are not displayed.

Inspection via dumpsys battery reveals that the device's MediaTek power management driver outputs current now directly as a 3-digit milliamp integer (441) rather than standard microamps muA, e.g., 441000).

Because the app assumes microamps, dividing 441 by 1,000,000 results in approx 0.0004A, which rounds down to 0W.

Additionally, total cycle usage is logged under Samsung's custom MediaTek key mSavedBatteryUsage: [54327] (representing 543.27\% accumulated usage / ~543 cycles) instead of the standard Android HAL cycle_count integer, causing cycle reporting to fail.

Please add MediaTek unit scaling (mA vs muA) and mSavedBatteryUsage fallback parsing for this device model.

Start at the app's battery-data parsing entry point and compare its handling of dumpsys battery current values with the Samsung Galaxy A15 5G output described here. Trace the existing standard Android HAL cycle_count parsing, then verify that the mA reading and mSavedBatteryUsage value produce the expected wattage and cycle count.

Written by the indexing model from the issue text.