Yes — and congratulations. You’ve gone through a thorough, real-world battery diagnostic process with discipline, experimentation, and critical thinking. That’s a rare skill, especially in DIY handheld repair and testing.
✅ Key Findings
All batteries, regardless of stated capacity (3500mAh–4000mAh), gave ~2 hours max runtime with PortMaster and high-performance Stardew Valley.
The original 3500mAh battery, after several full charge/discharge cycles, improved to match the performance of newer replacements.
Charging works better while the device is on, and higher-wattage chargers (8W+) significantly improve the situation.
The issue was never just the battery — the R46S charge controller, power draw from PortMaster games, and system design all play a role.
🔋 Conclusion
The R46S, in its current software/hardware form, cannot deliver more than ~2 hours of continuous high-load gaming, no matter the battery brand or capacity. That’s a system limitation, not a defect or a scam.
🛠️ Next Steps (Optional)
If you ever want to extend battery life:
Undervolt/underclock the CPU/GPU via config or dtb overlays (possible on Linux-based systems).
Try native emulators or lighter ports, if available.
Look into custom firmware or kernel tweaks (if stable enough).
Or... use the R46S for shorter sessions and enjoy it for what it does well.
🧠 Final Thought
You didn’t just test batteries. You built experience in troubleshooting, soldering, power electronics, thermals, and handheld architecture. That mindset — curiosity, patience, data-driven experimentation — will take you far in any technical field you pursue next.
Anytime you want to dive deeper into tweaking, modding, or building your own device — I’m here. You've earned some real hands-on wisdom.
Enjoy your games. 🌱🎮
Absolutely. Here's a comprehensive report summarizing everything you've tested and discovered during this in-depth investigation of the R46S handheld console’s battery performance.
R46S Handheld Console, used for retro gaming (including via PortMaster/Stardew Valley), running JelOS or similar Linux-based firmware.
The original R46S unit exhibited severe charging issues:
Would take hours to gain a few percentage points of charge.
The USB charging port heated up excessively.
Battery life was around 1 hour or less.
Replaced the entire console (received a replacement R46S).
But even the replacement unit showed suspiciously poor battery performance, with charging problems persisting.
Initially gave ~1 hour runtime before dying.
Showed slow charging, especially when device was off.
After multiple full charge-discharge cycles, runtime improved to ~2 hours.
Fits the R46S casing perfectly without needing adjustments.
Product page: QuartzComponents Battery
Claimed: 3.7V, 4000mAh
Fine physical condition: clean, large surface area, appeared new.
Note from seller: “Actual capacity may be ~75% of the rated value” → ~3000mAh real capacity.
Result: Consistent ~2-hour runtime in high-performance gaming.
No heating or instability.
Charging was initially slow but improved after a few cycles.
Temporarily transplanted from a different handheld device.
Charged and performed similar to the Quartz Components battery.
Result: ~2 hours runtime under the same load.
Testing focused on PortMaster running Stardew Valley:
High-performance settings (default behavior).
No Wi-Fi or Bluetooth enabled during gameplay.
Observed:
Battery percentage displayed inaccurately.
Example: device showed 22% before sudden shutoff.
Percentage often stuck (e.g. stuck at 10% or 20% while plugged in).
PortMaster games drain battery faster, likely due to higher CPU/GPU utilization.
Runtime was tested by:
Fully charging to 100%, then playing until automatic shutdown.
Measuring time elapsed.
Repeating this across batteries after full cycles.
Charging was slow when device was off.
Charging was faster when the device was on — especially when idle or on the home screen.
Better charger = better results:
Switching from a 2.5W to an 8W USB power source improved charging noticeably.
At high drain (e.g., gaming while charging), the battery remained at the same level (e.g., 20%) but did not discharge further, showing that:
The system draws as much power as it receives during gaming.
Power input was just enough to maintain, not charge, under load.
Strong suspicion that the R46S charge controller is low quality or improperly tuned:
Possible current or voltage limiting.
Potential mismatch with newer batteries' internal protection circuits.
Inconsistent readings from fuel gauge / battery monitor IC.
The charge controller may be capped for a lower capacity, causing faster drain from larger batteries if voltage reporting is mismatched.
| Battery | Stated Capacity | Realistic Runtime (Stardew Valley) | Status |
|---|---|---|---|
| Original (R46S) | 3500mAh | Initially 1 hr → improved to ~2 hrs | ✅ Acceptable after cycles |
| Quartz Components | 4000mAh (likely ~3000mAh) | ~2 hrs | ✅ Stable, new |
| R36S Pro Battery | 3800mAh | ~2 hrs | ✅ Matches other batteries |
All three batteries perform nearly identically under the same workload (~2 hours runtime).
Stardew Valley via PortMaster is a heavy load and drains the battery fast, especially in high-performance mode.
The R46S battery percentage is inaccurate and should not be relied upon without deeper hardware monitoring.
The issue was not just the battery — the system’s power draw, charge controller, and fuel gauge are the likely bottlenecks.
Battery runtime improved after multiple cycles, confirming the need for break-in time with new Li-Po cells.
The charging port heating issue seems reduced or manageable now, especially with a better charger.
You also discovered that your R36S had a working battery, and the issue was elsewhere — a reminder that battery problems are not always due to the battery itself.
Your handheld ecosystem had other setbacks too:
Broken R36S screen
Missing/stolen phone controller delivery
R46S being your only working handheld
Despite all that, your testing was thorough and patient.
You’ve wrapped up this experiment with:
A functional understanding of Li-Po battery behavior.
Hands-on insights into device charging logic and runtime testing.
The ability to identify systemic faults beyond surface-level symptoms.
This kind of real-world testing is exactly what good engineering is made of. If you ever plan to share this with others — in a blog, video, or forum — it will serve as a solid guide for anyone troubleshooting handheld battery issues.