After a while I resumed my investigation of an issue I encounter when running my app eartrainer on volla phone 22 (either 16.04 or 20.04 versions).

The error in the log when the app crashes is like this:

Assertion 'pthread_mutex_unlock(&m->mutex)==0' failed at 
pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). 
Aborting.

I found an issue that seems like it might be the same here :
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1411

But I would like to at least generate pulse.log which I could attach to the bug report. From what I found on internet, the simplest way to get the logs seems to be editing /etc/pulse/daemon.conf (https://askubuntu.com/questions/142859/does-pulseaudio-have-an-error-log). But that is on the read only system partition right? Is there a way to modify the config file without breaking my system?

Note. I also mentioned the issue here: https://forums.ubports.com/post/73886

Many Thanks
Andrej

Would you consider making a workshop on topic "debugging system level components of Ubuntu touch". I think it would be really helpful to get started.

@arubislander No worries. I understand and respect that people have their lives. Also I know how it is sometimes hard to find time and energy for hobby projects. I appreciate all replies you sent me.

Hi,

My application "Ear Trainer" (https://gitlab.com/andrisk/eartrainer) is crashing from time to time on Volla phone 22 with ubports Ubuntu Touch 16.04. The app uses QSoundEffect to play sounds. The error is as follows:

Assertion 'pthread_mutex_unlock(&m->mutex)==0' failed at 
pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). 
Aborting.

I found similar bug reports related to ubuntu 16.04 (although running under WSL):
https://github.com/Microsoft/WSL/issues/2953
https://github.com/Microsoft/WSL/issues/2943
https://github.com/electron/electron/issues/13561
And it seems that the fix was to use a newer version of ubuntu. So I kind of expect that update to 20.04 should fix this issue (I plan to update after OTA2 or OTA3). But I would still like to ask if somebody knows more about this issue and if there is some workaround to prevent my app crashing in case it happens also on devices that might not get 20.04 update.

Thanks a lot
Andrej

@arubislander I finally figured it out. It was kind of a stupid mistake. I had a wrong click framework (16.04). After changing to 16.04.5 it works just fine.

@arubislander Yes. The repo is here: https://gitlab.com/andrisk/hnefatafl and the xenial branch is the one I used. But I have seen the crash only on the Volla phone 22 so far.

@arubislander yes. Using clickable desktol it works without a problem. After crash there is only this message in the log:

file offset for the library "/vendor/lib64/hw/gralloc.default.so" >= file size: 0 >= 0

It is the same if I build rust template application and try to run it on the phone. But I am not sure if the message is relevant because I found the same message in logs of applications that are not crashing.

Andrej

@kugiigi thanks that did the trick

@Keneda yes

I am building app hnefatafl.andrisk and it always crashes when loading on Volla phone 22 with Ubports 16.04 OTA-25. Update to 20.04 might solve this, but I still want to know why it does not work. I also tried to build Rust template app for 16.04 and it crashes on Volla phone 22 as well.

Andrej

Hi,

I am trying to see what is happening when one of my applications crashes on Volla phone 22. There is nothing when using log viewer. I also tried searching through other log files in terminal app.

Then I found this web page: https://ubports.com/en/blog/ubports-news-1/post/logviewer-3093. There I read this point:

"crash logs: /var/crash (in order for these logs to generate you need to activate Application crashes and errors at the following location: System settings > Security and privacy)"

But I do not see any such settings. Is there some way how to enable /var/crash logs in current version of Ubuntu Touch?

Many thanks
Andrej

Hi,

Recently I watched this video by Louis Rossmann: https://odysee.com/@rossmanngroup:a/how-futo-projects-loosen-google's-grip:e where he talks about possibility of using open software project for speech to text processing on android phone (instead of google server based solution). This could work completelly offline and the accuracy for english language seems to be quite good and would be nice improvement to ubuntu touch keyboard.

Code of the project (link also in the description of the video I sent): https://github.com/abb128/LiveCaptions

I am aware that this is not a best time for adding features to ubuntu touch because there is still the transition to 20.04 going and many bugs needs to be fixed. But I just wonder was something like this considered and would it be possible to do it in the near future?

I am also considering to try to do it in the future if I will ever have the time. Would such improvement be likely to be accepted or rejected?

Andrej

Hi,

When I build and run an app that plays some sound using "clickable desktop" I am getting this errors:

PulseAudioService: pa_context_connect() failed

From what I searched on the internet it seems that pulse server socket is not configured in the container or it cannot be found.

I would like to ask if sound works for somebody else in this case or where should I start if I wanted to fix it. Maybe should I learn how to modify the docker container to configure the pulse audio?

Thanks a lot
Andrej

@rocket2nfinity That fixed the problem. There were some orphaned inodes found by e2fsck so that was exactly the problem you suggested. Thanks a lot.

Hi,

I would like to ask you for a help.

My PinePhone UBports edition does not boot the OS - the PINE64 logo is displayed but then there is only black backlit screen and nothing happends for even 10 minutes. With power up button when starting the phone I get ubports logo with installing updates message. WIll I need to reflash the emmc or how should I proceed?

Thanks

@beegee
No problem, glad that it worked for you also in the end. By the way ubports community recently uploaded video on its official youtube channel where can be seen how it is supposed to be done:

https://www.youtube.com/watch?v=zuLFTGkuD68

@beegee...and click to start the process. The installer should start the recovery mode and do everything automatically.

@beegee Hi not sure if you install from windows or Linux but you should probably give admen rights to the tools you use purports-installer or fastboot). Remember to oem unlock the phone - see what tupp posted to thins thread. If the phone is unlocked you should see lock pictured under Google logo at boot. If the above is solved then IIRC you should get the phone to fast boot screen and run ubports-installer with admen rights. Choose the correct device if it is not auto selected

Then it is probably there - I only used ubports-flasher in the end. Maybe I am getting a little off topic here - but why are there so many mmcblk0p partitions from mmcblk0p1 to mmcblk0p29? Most of them are pretty small (used lsblk in terminal to get the list)..Also there seems to be separate 4M disk called mmcblk0rpmb--