Done - working!
Put together the keyboard and tested again: Works, charges.
Thanks again to megi! His work can be found here: https://xnux.eu/
To make it safe giving the mini computer phone thing to my kids I hot glued close the usb-c of the #pinephone since it is strongly adviced not to use it while connected to the keyboard - especially for charging which would be the only connections my kids do regularly.
Like shown on the pictures in the forum post I shorted D1 with a tiny little piece of wire.
I guess I'll go for one of those magnifying glasses my dentist uses. Even in good light I can barely see this stuff without magnification.
To check my job I took this picture. It works. It really works and charges again.
Still gotta put together all the parts for a final check...
Uh, #repair morning.
Had a #PinePhone keyboard delivered. But it didn't work at all.
Support didn't know what to do about it and offered to send a replacement.
I asked megi (firmwares author) whether he could make use of the broken device. No.
I disassembled it, didn't find any obvious problem, plugged everything back in and the keyboard suddenly worked, but the internal battery did not charge.
Megi pointed me into the right direction and I found this post:
But the last time I tried to get the screen of the nexdock working with the pinephone it didn't switch on at all. Keyboard and touchpad are working, convergence symbol is shown in mobian and I can move windows to the inactive screen of the nexdock.
Everything looks as if the mobian is using the second screen even though no picture is shown.
Can't get the pinephone (#mobian) to work stable with the nexdock - nexdock as single screen. Connecting needs often a few tries and usually includes some waiting until the screen of the nexdock activates. After that it isn't stable: after some time the screen on the nexdock deactivates and the screen on the pinephone doesn't show anything.
To get back control I either have to reboot or try to reconnect until I can reconfigure the screens. kanshi helps a bit.
anton.app works o.k. in Gnome Web. Geary does work also and now my son can use his email address on his own. The #Pinephone is connected to a Lycander USB-C dock with ethernet, 2x USB-A (mouse and keyboard) and an HDMI. I still have to configure some magic to have it start in convergence mode all the time or just stay in convergence mode until it is disconnected from the usb-c dock. If the hdmi monitor is switched off it resets the monitor configuration half hearted to an unusable state. #mobian
O.k., the #Pinephone does have a new SIM now and mine moved to the #Librem5. If I'm not reachable... The #Pinephone will serve now as a computer for my eldest son. I hope he'll get along with it until #PinephonePro. If this works he'll have no problems deciding which his first phone will be.
Unbelievable. I'm looking at a #Librem5 on my desk. Red LED on, charging. First impression: compared to the #Pinephone really fast, touch screen has better responsibilty. Heavier, thicker. Really looking forward to flash it with #PureOS #Byzantium (Bullseye) and copy my configuration from the Pinephone.
Yeah, #nexdock arrived today. First impression: I like it. It's right now connected to a #pinephone and works like a charm. It charges the phone. The keyboard feels nice even though I'm not used, yet, to the layout. The touchpad can be disabled (and if it is on, I can't really type without moving the focus out of the window). I'm looking forward to some more experience...
mental note to myself: it is not safe anymore to have my #OTP keys in #Authenticator on my #pinephone. I started to login from the phone to places where I need the OTPs. Login and generating OTP (and thereby the seed of the OTP) should stay on different devices. Gotta look into using the #nitrokey for OTP and how I could use it on the pinephone also.
A web frontend with a light and for mobile optimized interface could be a solution also ( if it'd be foss for selfhosting).
Keyboard and mouse connected via bluetooth just worked fine - on-screen keyboard didn't show thanks to udev hack.
#tootle does not show the pictures I append which makes it necessary while writing their description to switch back ...
Just looked in #firefox for a setting to tell it where to set the focus. Did'nt find what I've been looking for.
On my #pinephone every time I switch to the firefox window or change the active tab the virtual keyboard pops up.
This is anoying. I guess it happens because firefox puts the focus on the address field.
Installed #tootle flatpak 1.0.0 on my #pinephone running #mobian. First it didn't decide on font size which ended after I set text size to 200% to make it readable and then back to 100% to make it readable after the next start of tootle.
But the scrolling doesn't work for me no more. Reinstalled the apk 1.0.0alpha to check and it works as before when started from the command line to not run the flatpak.
Does that make sense, @bleakgrey?
This is my mastodon account which I still use frequently to read.
I started publishing via microblog.pub recently.