adb shell dumpsys cpuinfo
Load: 2.85 / 2.64 / 2.54
CPU usage from 69256ms to 53673ms ago (2026-09-07 21:41:16.827 to 2026-09-07 21:41:32.410):
59% 9964/com.warrenbrowse.vpn.beta: 50% user + 8.9% kernel / faults: 322 minor
23% 27505/foundation.e.browser:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:7: 21% user + 1.5% kernel / faults: 1776 minor
Mon téléphone chauffe énormément et Warren est le plus gros consommateur (et de loin).
De plus, je ne peux pas joindre les journaux depuis l’app car quand je clique sur “ouvrir l’app”, il ne se passe rien (j’ai ce problème depuis un moment).
How can we make it happen too? (optional)
Aucune idée… Le lancer sur un vieux téléphone ??
Je suis sur un Fairphone 3, /e/OS 4.2 (Android 15)
How often does it happen?
Every time
System
Android 15 (API 35) Fairphone FP3
Filed from the Warren app. Technical logs, when included, are visible to the support team only.
Technical data automatically attached from the Warren app (app version: 1.1.28, system: Android 15 (API: 35) - Fairphone FP3). Full logs are only visible to the support team.
@pisas-kozul-pomof The culprit is our APK: every Android beta version released so far was a debug build, including the encryption engine, therefore not optimized. A Snapdragon 632 pays for it in CPU and heat as soon as the tunnel carries traffic. This is our explanation for what you are measuring. The corrected version will tell.
Corrected today: the next beta will be an optimized build (engine in release mode, minified Android code), signed with the same key, so an in-place update without uninstalling. Its number is not yet fixed, I will post it here. Rerun the same dumpsys cpuinfo on it.
Regarding the “open app” button that does nothing: the Android app does not yet handle the link from the “join your logs” page, regardless of the browser, and the code displayed under this button was the identifier for that page, which the “connection code” screen of the app does not know, hence a false “expired”. This page now sends you to Settings, Report a problem, which you eventually did: your logs are indeed here.
