Repository navigation
Conversation
|
Heads-up: #344 just landed as omamobile-shell 0.2.79 (the Hyprland 0.57 transparency fix), so this PR needs |
e035c53 to
6ba3b8f
Compare
|
Thank you, @W4HO-ham, and thanks for the quick bump to 0.2.80. Running Omarchy's own One small change, please. The new last line of One note for the record, nothing to change: Omarchy's script makes a plaintext keyring A heads-up on timing: a release is being published right now, so I'll merge package bumps |
6ba3b8f to
71fd5c2
Compare
|
Thanks, Derek. Done (71fd5c2): the step is now |
71fd5c2 to
0fbdcb3
Compare
|
Thanks, @W4HO-ham. Both changes are in exactly as asked: the Main has moved again (#377 took omamobile-shell 0.2.94), so the version file conflicts. Could you merge main and set |
0fbdcb3 to
56fb9e7
Compare
|
Done: rebased on main, |
…1-03 keys (modem-sit 0.3.29, mmd 0.1.2, shell 0.2.96) main moved under this PR (#384, #386, #387, #388): modem-sit 0.3.24-0.3.27 brought attach_apn = none, ims_first, internet_cid, [profiles], carrier_manifest and ims_pcscf_from_isim, and the internet bearer's rmnet device is now found by omamobile-sit-data. Where both sides changed the same thing, main's code wins: bringup.start() is main's order with the carrier lookup in front of it (the SIM read once after the USIM is READY, what isn't typed comes from the lookup); data_network.py is main's device search with this PR's roaming check on the device found; paths.py, sit.py, modem-sit.conf and test_bringup.py merged by hand. What registered IMS and carried calls and texts on the 7 Pro on 2026-11-03 (NOTES, IMS-SHANNON 11-12) was five typed values beyond the APN, so the lookup now produces them: an override section carries attach_apn (an APN or none), ims_apn, ims_first, internet_cid and profile_<ID> lines, and "like = MCC/MNC" lets a carrier's codes share one section. ims_apn, ims_first and internet_cid default to auto; an empty [profiles] takes the override's set. Verizon's codes give apn = VZWINTERNET, attach_apn = none, ims_apn = IMS, ims_first = yes, internet_cid = 3 and stock's four profiles. The 11-02 value attach_apn = vzwims registered but never got IMS: gone, and the file says why. mmd treats none as no attach settings; the Mobile network page shows it as "Not sent: the carrier profile's own". Versions: modem-sit 0.3.29 (main 0.3.27, #389 claims 0.3.28), mmd 0.1.2 (main 0.1.1), shell 0.2.96 (main 0.2.94, #343 claims 0.2.95). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
|
Thanks, that's everything: 0.2.95 with the title to match, rebased on main, and the setup-user test still passes here with both keyring cases. Merging; I'll set the version at merge if another shell bump landed first. |
Omarchy's installer gives each user an unlocked default keyring, but a phone user is made without that installer, so on the Pixel 9a Chromium's first start opened an oversized "Choose password for new keyring" prompt that the palmtop couldn't get past. The user setup now runs Omarchy's own default-keyring step, which creates only what is missing. The step is an if-block, so the script still succeeds when a later Omarchy moves the file, with a test for that.
56fb9e7 to
6ba424a
Compare
|
Rebased again: #394 took 0.2.97, so this is 0.2.98 now (version file and title). |
#397, from #343) Omarchy's installer gives each user an unlocked default keyring, but a phone user is made without that installer, so on the Pixel 9a Chromium's first start opened an oversized "Choose password for new keyring" prompt that the palmtop couldn't get past. The user setup now runs Omarchy's own default-keyring step, which creates only what is missing. The step is an if-block, so the script still succeeds when a later Omarchy moves the file, with a test for that. Co-authored-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
derekross#397, from derekross#343) Omarchy's installer gives each user an unlocked default keyring, but a phone user is made without that installer, so on the Pixel 9a Chromium's first start opened an oversized "Choose password for new keyring" prompt that the palmtop couldn't get past. The user setup now runs Omarchy's own default-keyring step, which creates only what is missing. The step is an if-block, so the script still succeeds when a later Omarchy moves the file, with a test for that. Co-authored-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
On the palmtop (Pixel 9a), Chromium's first start opened GNOME Keyring's "Choose password for new keyring" prompt, scaled far past the screen, and nothing behind it could be reached. The user had no default keyring: Omarchy's installer makes one for each user (
install/user/default-keyring.sh, an unencrypted keyring that never locks, so nothing asks for a password the autologin never types), but a phone user is made by our setup, not that installer.omamobile-setup-usernow runs Omarchy's own script from$OMARCHY_PATH(default/usr/share/omarchy) when it's there. That script creates only the files that are missing, so a user who already has a default keyring keeps it, and later logins change nothing. It isn't anomarchy-donestep for that reason.Tested on the palmtop: I closed the prompt, ran Omarchy's script as the session user and restarted
gnome-keyring-daemon. Chromium then started with no prompt, and the owner has used it since.test/setup-user.shgains a case with a stand-in for Omarchy's script: a new user gets the default keyring, and a user's owndefaultfile is kept.packages/omamobile-shell/test/allandtools/pr-checkpass.