<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coinosv3.git/android, branch fdroid-v1.15</title>
<subtitle>coinos v3 — bitcoin, Ark, Lightning and nostr wallet (web + Android)</subtitle>
<id>https://git.coinos.io/coinosv3.git/atom?h=fdroid-v1.15</id>
<link rel='self' href='https://git.coinos.io/coinosv3.git/atom?h=fdroid-v1.15'/>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/'/>
<updated>2026-11-18T20:16:05Z</updated>
<entry>
<title>Android 1.15 (code 16) for F-Droid; the WebView builds reach /live/ and /vmedia/. The bundled builds (fdroid, webview, fcm) answered every v3.coinos.io path they don't carry with a 404, so calls got no TURN credentials (/live/turn), live streams and Go live couldn't reach their server, and the video help (/vmedia/) never answered. Those two prefixes now go to the network, like /electrum and /api/; both serve data and media, never pages. F-Droid changelog 16 lists what the app gains since 1.9 (passkeys, system bars, calls and streams).</title>
<updated>2026-11-18T20:16:05Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-11-18T20:16:05Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=8efa0378a920dfd80951fd03f9aa648608a8ee29'/>
<id>urn:sha1:8efa0378a920dfd80951fd03f9aa648608a8ee29</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01VMan6TV6sjEZSpqqBen9T5
</content>
</entry>
<entry>
<title>Passkeys in the WebView builds: the apps name v3.coinos.io too, and a failed passkey sign-in no longer goes on to make a new one. Coinos Beta's passkey sign-in failed after the account was picked — "CredMan getCredential call failed … RP ID cannot be validated" (Pixel 9, 2026-11-06). An app's association with a site runs both ways: the site's assetlinks.json names the app (it did), and the app's manifest names the site through asset_statements meta-data — which the TWA has and the webview/fcm manifests didn't. They declare it now, and the shared asset_statements string carries get_login_creds beside handle_all_urls. And passkeyLogin rolled any sign-in failure into creating a passkey, so the validation error was followed by a second, failed create dialog: only NotAllowedError (how browsers report "no passkey here", or a dismissed sheet) leads to creating one now; any other error is shown</title>
<updated>2026-11-07T06:37:49Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-11-07T06:37:49Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=5e315005b72a8e9e6670f10b1d30b532763f7fe6'/>
<id>urn:sha1:5e315005b72a8e9e6670f10b1d30b532763f7fe6</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01VMan6Ts5Tktega8VbLg31q
</content>
</entry>
<entry>
<title>Coinos Beta (io.coinos.beta, 1.14-beta) is published for a trial at https://v3.coinos.io/coinos-beta.apk — the wallet in its own WebView with Firebase push, installed beside the current app. Built with the coinos-v3 Firebase project's config (android/app/google-services.json, fetched with the project's service account through the Firebase Management API; gitignored) and signed with the usual key; nwcpush sends fcm: endpoints with the same service account (on cs in the nwcpush state, config fcm.serviceAccount). Verified on a Pixel 9: the token reaches the page as its push endpoint, and a data message sent through FCM v1 woke the off-screen wallet ("wake: job started", the service worker's NWC responder up) and raised its notification. Not on Zapstore. FcmService no longer resets the "endpoint handed to the page" flag when the first token arrives a second time through onNewToken</title>
<updated>2026-11-07T06:18:27Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-11-07T06:18:27Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=fc5ac3df7477e416c4241d6e88b13d9f5190e40a'/>
<id>urn:sha1:fc5ac3df7477e416c4241d6e88b13d9f5190e40a</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01VMan6Ts5Tktega8VbLg31q
</content>
</entry>
<entry>
<title>The WebView builds fit between the system bars, wear the page's colour there, and offer passkeys. Android 15 draws every app edge to edge, so the page ran under the status bar and the navigation buttons sat on its bottom row: MainActivity now hosts the WebView in a frame padded by the system bars, the display cutout and the keyboard; the frame takes the page's theme-color (read on load and watched for theme switches, through CoinosHost.bars) with dark or light bar icons to match, and 3-button navigation's own light scrim is turned off. And a WebView exposes no WebAuthn unless the app asks, so passkey sign-in and the fingerprint lock were missing (Adam, 2026-11-06, on the Beta): the webview, fcm and fdroid builds turn on androidx.webkit's WebAuthn support (WEB_AUTHENTICATION_SUPPORT_FOR_APP), and assetlinks.json grants get_login_creds for v3.coinos.io to io.coinos.app, io.coinos.beta, io.coinos.webview and io.coinos.fdroid (same signing certificate; the TWA's handle_all_urls entry unchanged)</title>
<updated>2026-11-07T06:05:05Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-11-07T06:05:05Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=f698dd9b1c638092c5c313889c1ac94feb91245f'/>
<id>urn:sha1:f698dd9b1c638092c5c313889c1ac94feb91245f</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01VMan6Ts5Tktega8VbLg31q
</content>
</entry>
<entry>
<title>A third Android build, fcm (io.coinos.beta, "Coinos Beta"): the wallet in its own WebView, as the webview build, with Firebase Cloud Messaging for push on phones with Google Play Services — no distributor app to install. A user on the TWA APK found launching slow next to Minibits (2026-11-05); measured on a Pixel 9, a WebView paints ~0.7 s sooner than a cold Chrome. This build installs beside the TWA for a side-by-side trial before deciding whether it replaces it. Fcm asks for the token and stores "fcm:&lt;token&gt;" as the push endpoint, which reaches the page down the UnifiedPush road (?up= on the next launch, or written straight into the page's localStorage once it has loaded, since the token arrives after the first load starts); nwcpush (coinosv3-server 0c50417) sends an fcm: endpoint through Firebase. FcmService hands a message's "body" to the same handler UnifiedPush messages use (PushReceiver.onPush: wake the wallet off-screen, notify unless it answered a silent request). Firebase is set up in code (CoinosApp → Fcm.init) from values build.gradle reads out of app/google-services.json (gitignored) — without it the build still builds and falls back to UnifiedPush. The webview and fdroid builds get a stub Fcm (src/nofcm) and carry no Google code; the notification permission is asked when Firebase or a distributor can deliver; CoinosHost.env reports app "fcm"</title>
<updated>2026-11-07T06:01:15Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-11-07T06:01:15Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=8969744783e2851b287e937f71033ce4b6bb4dc3'/>
<id>urn:sha1:8969744783e2851b287e937f71033ce4b6bb4dc3</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01VMan6Ts5Tktega8VbLg31q
</content>
</entry>
<entry>
<title>Android 1.14 (code 15): UnifiedPush only where web push can't reach the app. isolabellart asked why Coinos opens a prompt inside ntfy: every launch of the TWA asked whatever UnifiedPush distributor was installed for an endpoint (and asked for notification permission for it), Play Services or not. UnifiedPush is there for phones without Google Play Services (GrapheneOS and the like); with Play Services, web push reaches Chrome — and so the TWA — through Google already, and asking ntfy too only put up its prompt (and would bring every notification twice). The TWA now asks a distributor only when Play Services isn't installed and enabled (Push.playServices; its package named in the manifest's queries for Android 11+), or when it already holds an endpoint — whoever has one has been through the prompt and may be counting on it. The WebView builds (webview, fdroid) are unchanged: web push never reaches a WebView, so UnifiedPush is their only way in either way.</title>
<updated>2026-10-13T06:51:13Z</updated>
<author>
<name>Adam Soltys</name>
<email>asoltys@gmail.com</email>
</author>
<published>2026-10-13T06:51:13Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=90bc4d3d54b91cb9845cda4edc53ed148ae00251'/>
<id>urn:sha1:90bc4d3d54b91cb9845cda4edc53ed148ae00251</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01KPw21NEpWeTGu6swVASmBt
</content>
</entry>
<entry>
<title>Android 1.13 (code 14): the app runs immersive. Adam doesn't want Chrome's "v3.coinos.io – To exit full screen, drag from the top and touch the back button", which Chrome shows whenever a page enters its full screen and a page can't turn off. The TWA now launches in sticky-immersive display mode (android-browser-helper's DISPLAY_MODE): the status and navigation bars are hidden, and a swipe in from an edge shows them for a moment. The page — in display-mode fullscreen, which installedApp() counts — fills the screen with the pager without ever asking for the browser's full screen. A Custom Tab's window is the browser's, so the page can't switch this on and off: it's the whole app. Thread clips and YouTube still ask for the browser's full screen, and so still get the notice. 1.12 (code 13) was published without its APK committed here; this sits above it.</title>
<updated>2026-10-13T06:28:40Z</updated>
<author>
<name>Adam Soltys</name>
<email>asoltys@gmail.com</email>
</author>
<published>2026-10-13T06:28:40Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=bcf5f54c928dcc8e1893fe1227b9d8930f2744df'/>
<id>urn:sha1:bcf5f54c928dcc8e1893fe1227b9d8930f2744df</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01KPw21NEpWeTGu6swVASmBt
</content>
</entry>
<entry>
<title>Dark mode: your own chat bubbles are a gray (#343a44, light text) instead of the white accent, which glared among the dark bubbles. Android 1.12 (code 13): the TWA no longer names a navigation-bar colour — the helper library always passed one (white when the manifest named none), and Chrome 154's Custom Tab window paints that bar white anyway while the buttons follow the colour asked for, so the colour extras are stripped from the launch intent (both schemes) and the bar is left to the browser and the system. Untested on a device yet; not published.</title>
<updated>2026-10-09T16:46:29Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-10-09T16:46:29Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=479959cdd77fdd18ca03f63af9b94eae291d0e2a'/>
<id>urn:sha1:479959cdd77fdd18ca03f63af9b94eae291d0e2a</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Vps2H27rhbG9ZqseGfMrc3
</content>
</entry>
<entry>
<title>Android 1.11 (code 12): 1.9's per-theme system-bar colours, rebuilt to sit above a 1.10 test build. The navigation buttons stay white on white on Android 17 / Chrome 154 whatever the app asks for: the TWA's Custom Tab window ignores the navigation-bar colour (plain Chrome tabs are fine), reported to Chromium</title>
<updated>2026-10-09T16:30:07Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-10-09T16:30:07Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=4d0fc6bf4fd0494df1405899f51f9abbf5ab34a1'/>
<id>urn:sha1:4d0fc6bf4fd0494df1405899f51f9abbf5ab34a1</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01MgAFLnkF7KrdhuyCLMNgtL
</content>
</entry>
<entry>
<title>README rewritten for today's coinos v3; build switches are COINOS_* (HAL_* still accepted); silent-payment leftovers removed</title>
<updated>2026-10-06T05:35:56Z</updated>
<author>
<name>Adam Soltys</name>
<email>adam@coinos.io</email>
</author>
<published>2026-10-06T05:35:56Z</published>
<link rel='alternate' type='text/html' href='https://git.coinos.io/coinosv3.git/commit/?id=f571e46937d423d9ba44154a92aeb4136466daaa'/>
<id>urn:sha1:f571e46937d423d9ba44154a92aeb4136466daaa</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01YRC6aKhwAud231ot9FPmhi
</content>
</entry>
</feed>
