Hi @Charly. Welcome to the UBports community.

Ok I've found a way to solve keyboard bugs (in X, in a very hacky way) . I will make a new release soon, Alongside optimizations to make the app less sluggish. With those, it will reach the stage of good client for text-only notification-less chat! (Other features will come later)

OP can you update the title to be more descriptive please, something along the lines of Fingerprint Sensor Fairphone 5 or similar. It'll help others find the post.

If a trusted & skilled dev wants to take this on I am will to buy them a used 1st gen Pixel Fold. I may be willing to pay $300 towards a Fold 9, but I hate how big those are, though they have display out which the smaller 1st gen doesn't have:( Ah shoot, I just realized Halium might be an issue for both those, as far as I can tell we don't have one for Android 14 or 15 yet. o7

@peat_psuwit Hello, I installed 24.04-1.0 again and the micro SD card is mounted read only there too. I believe it still worked on 20.04. Many thanks & best regards Charly

@Biplabro said in paste in terminal, clock widget in home screen help request: i like the launcher moduler app. it hs the clock as well. I wanted to mae it autostart but the ctrlV seems not working. well, I have trouble trying to guess what you mean by that...and no, I did not succeed at looking at your video either.Are you still attempting to use Ctrl V in the terminal app of UT ? I have tried to steer you toward another solution that works. If it's ssh or adb, try the solution by @Vlad-Nirky - or just use your mouse to select and paste.

@ufoddos said in New mobile system solution to replace Android: Establish a unified national alliance National? Which nation are you thinking of? Anyway, sounds like you have given yourself quite a job to do. Good luck and let us know how it goes!

hi guys, thanks for your posts, it open a window to me. i set and use an esim on android before flashing to ubtouch. i cannot find any ways to use this esim now on my Pixel3a. can you give some tips to do so? regards Marc

I just installed this and it works great except I have a crackling sound from the speakers and headphones when I'm listening to anything. The speakers were fine with android.

@pparent said in How to use volte: I would like to know more. after enabling debug logs on my FP5 according to the procedure given by @Vlad-Nirky here are my (very preliminary) results: After disabling the Volte indicator in the UI, restarting the phone, and reading the logs with journalctl --file=<last occurence of user-1001xxx file> (on my system 1001 is the ID of the 'radio' user) I see numerous occurences of src/ims.c:ims_registration_check() checking ims state src/ims.c:ims_registration_check() ims is disabled, leaving it unregistered After enabling again the Volte indicator in the UI, restarting the phone and reading the logs again, I see occurences of: ims_registration_check() checking ims state ims_registration_check() leaving ims registered and before a call: src/binder_gprs.c:binder_gprs_check_data_allowed() slot1 1 1 when VolTe is disabled in the UI I do NOT see the previous line. So, when Volte is disabled, the phone don't check with the provider if it can use it. Seems logical but needed confirmation IMO. In short, Volte is called in the debug logs 'ims state' or 'data'. Maybe you could check a similar log for your device and search for such strings. Also reading the code for the UI settings to try to search if there is any logging of the decision path to disable the switch on your device. From lomiri-system-settings-cellular, the code reads like this; text: I18nd.tr("4G calling (VoLTE)") Switch { enabled: Connectivity.imsSupported && sim.ims !== null && ( sim.radioSettings.technologyPreference == 'lte' || sim.radioSettings.technologyPreference == 'nr') the first line should be linked to scanning of the setup/sim at initialization of the phone, so the debug log in the journal before any attempt of calling is done. I'd say that sim.ims is probably the carrier configuration, and Connectivity.imsSupported is the device itself. Unfortunately there is a test for 2 conditions and one result, not enabled. if the debug don't show anything suspicious, it may be the device setup to be checked with the port owner (Volla most probably) If you want to go that way, I can send you the anonymised logs of my device for comparison (even if it's not the same hardware).