Prune commentary and stale Rust port notes

app-rust/src/android/bench_jni.rs

@@ -1,24 +1,3 @@
-//! JNI calls the `bench` feature needs that go through the shell's own
-//! Java side rather than anything `iris`/`android-view` already wraps:
-//! `BatteryManager.getIntProperty(BATTERY_PROPERTY_CURRENT_NOW)` for the
-//! per-second battery sample, `ClipboardManager.setPrimaryClip` for the
-//! "Copy report" control (P0's iris half, docs/RUST.md), and -- added for
-//! RUST.md's "Benchmark v2" -- `Display.getRefreshRate()` for the phase
-//! report's real late-frame budget and `InputMethodManager.
-//! showSoftInput`/`hideSoftInputFromWindow` for the keyboard phase. None
-//! of these are part of `android_view::context`'s own `Context`/
-//! `Resources` wrappers (that file's own `// TODO: more methods?`), so
-//! this calls them directly rather than growing that crate's wrapper for
-//! calls this crate alone needs.
-//!
-//! Holds its own `JavaVM` + `GlobalRef` to the view (handed in through
-//! [`iris::android::AndroidAppState::platform_ready`]) so it can attach
-//! whichever thread calls it -- the battery sampler runs on a background
-//! tokio task, not the UI thread the rest of `IrisViewPeer`'s JNI calls
-//! run on. `JavaVM::attach_current_thread` is safe to call from a thread
-//! already attached (the `jni` crate detects it and does not double
-//! attach), so no caller here needs to know or care which thread it is.
-
 use android_view::jni::{
     JNIEnv, JavaVM,
     objects::{GlobalRef, JObject, JValue},
@@ -69,13 +48,6 @@ impl PlatformHandle {
         .ok()
     }
 
-    /// One sample of `BATTERY_PROPERTY_CURRENT_NOW`, in microamps. `None`
-    /// on any JNI failure, on a device with no `BatteryManager` service,
-    /// or when the platform itself answers "not supported" -- `0` or
-    /// `Integer.MIN_VALUE` are both documented SDK answers for that, and
-    /// both would read as a real (and wrong) measurement if folded into an
-    /// average rather than named apart. UI_RULES.md: never present an
-    /// inferred value as a measured one.
     pub fn battery_current_ua(&self) -> Option<i32> {
         let mut guard = self.vm.attach_current_thread().ok()?;
         let env: &mut JNIEnv = &mut guard;
@@ -135,14 +107,6 @@ impl PlatformHandle {
         Some(())
     }
 
-    /// The display's own refresh rate in Hz (`View::getDisplay()` ->
-    /// `Display::getRefreshRate()`), for RUST.md's "Benchmark v2": late
-    /// frames are judged against *this* device's real budget, not an
-    /// assumed 60Hz -- a 90Hz or 120Hz phone would otherwise call frames
-    /// "late" that met their own faster deadline. `None` if the view is
-    /// not yet attached to a window (`getDisplay` returns `null`) or the
-    /// platform reports a non-positive rate, which is not a real answer
-    /// either.
     pub fn refresh_rate_hz(&self) -> Option<f32> {
         let mut guard = self.vm.attach_current_thread().ok()?;
         let env: &mut JNIEnv = &mut guard;
@@ -167,20 +131,10 @@ impl PlatformHandle {
         if rate > 0.0 { Some(rate) } else { None }
     }
 
-    /// `InputMethodManager.showSoftInput(view, 0)` -- the keyboard phase's
-    /// own show, called directly rather than through the focus-driven
-    /// `pending_show_keyboard` path `android/view.rs` uses for a real tap,
-    /// since RUST.md's "Benchmark v2" spec asks for this "through the
-    /// shell's InputMethodManager" independent of focus state. `true` only
-    /// if the platform itself reports the request succeeded -- whether the
-    /// IME actually became visible is confirmed separately, from
-    /// `on_insets_changed`, per UI_RULES.md ("never present an inferred
-    /// value as a measured one").
     pub fn show_ime(&self) -> bool {
         self.try_toggle_ime(true).unwrap_or(false)
     }
 
-    /// `InputMethodManager.hideSoftInputFromWindow(windowToken, 0)`.
     pub fn hide_ime(&self) -> bool {
         self.try_toggle_ime(false).unwrap_or(false)
     }