Skip to content

Chromium

dwiigoy edited this page Jul 19, 2026 · 2 revisions

Chromium

NoBrain's Chromium launcher uses a persistent profile:

/home/nobrain/.config/nobrain-chromium

Bookmarks, cookies, preferences, and normal login state survive application restarts and official in-place APK updates.

Close Chromium safely

Close Chromium normally or use NoBrain menu -> Shutdown. The Shutdown helper first requests a graceful exit so Chromium can flush its profile and uses forced termination only as a bounded fallback.

Avoid killing Chromium manually with kill -9 unless the process is genuinely stuck.

Expected warnings

The packaged Chromium may display warnings about unavailable Google API keys and the required --no-sandbox flag. NoBrain runs inside PRoot, where the normal Chromium sandbox is not available.

These warnings must not be hidden with fake Google API credentials or Chromium testing mode. Earlier experiments showed that such workarounds can interfere with Google authentication even while making the banner disappear.

Login troubleshooting

If a login does not persist:

  1. Make sure Chromium is using the persistent profile path above.
  2. Close all Chromium windows normally.
  3. Use NoBrain Shutdown and reopen the application.
  4. Compare behavior on Wi-Fi and mobile data if Google repeatedly requests a CAPTCHA; shared mobile/CGNAT address reputation can be a separate cause.

Do not delete the profile unless you intentionally want to erase browser data.


Previous: WPS Office · Next: Storage and Files

Clone this wiki locally