I have started working on an extensive update of the UBports porting guide. I posted the first version to a select few more than a week ago and now shared an updated version in the porting channel on Telegram. So far, no feedback. It needs scrutiny from experienced devs specifically, but also from novices. What is the best way to do this? Note: I have gained experience using AI tools and am using these for this task. This makes it even more important to get feedback from people with more experience than myself.

@katharinechui I have now confirmed that I can connect my device to my car via bluetooth without any additional steps. Receiving a call seemed to work well also. The sound was a bit choppy at first, but this might have been caused by the caller being in a place where the cellular reception was not ideal.

@katharinechui I have been using the S7 (herolte) in parallell with my work phone. I have a twin SIM. Here is what I have noticed about the cellular functionality.

SIM card pin unlock works consistently.

MMS works, but not consistently. Occasionally, I have received this message:
"Could not fetch the MMS message. Maybe the MMS settings are incorrect or cellular data is off?"
It is possible that cellular data was in fact off in one case, but even though it is now on and I have also rebooted the phone since, the 'download' button in the same message is inactive. It is also worth noting that I have successfully received several MMS messages from the same phone number since this. (Not sure if any of these might possibly be the original ones that triggered the error message?)

Another thing I have noticed is that if I leave the phone on overnight, something happens to the cellular connection. In this situation I have tried twice to call the same person. It looks as though the call is going through at first, but then it is suddenly cut off. At this point I have not heard any tone signaling that the phone is ringing at the other end. Also, the other party has confirmed that their phone rang, so something still worked. When they called back, though, the call did not go through on this device, but only on the other one (with the twin SIM) which runs Android.

After rebooting the phone, things were back to normal.

I will continue trying it out and post anything more info or other issues I come across.

All in all a very impressive port! Good work!

A port for the LG G4 is now available for testing using the UBports installer. The port has not been released officially through the installer yet, but it can be installed by using the installer from the command line, as described below.

1. Download and install the UBports installer. https://github.com/ubports/ubports-installer/releases/tag/0.8.8-beta
2. Download the installer config file: https://github.com/abkro/H815
3. From the command line, issue the following command:
   ubports-installer -f <path-to-h815,.yml>
4. Follow the instructions.

Note that you may have to remove and replace the battery after being in bootloader, when you subsequently need to boot into recovery.

The device page for the LG G4 will get updated (minor changes) shortly.

A few known issues worth noting are:

• wifi authentication is not remembered across boots
• bluetooth starts, but does not work properly yet
• after being connected to an external monitor (cabled connection/slimport) some of the icons at the top of the screen may be displayed with incorrect scaling.

Re: LG G4

@ubportsnews
As I am currently working on extending and improving the porting guide, I thought it might be a good idea to do a survey of the challenges people are meeting with while porting. This could bring to light any common issues that are currently not dealt with in the guide, but should be. However, there is a problem: I am not really sufficiently qualified to make the distinction between what should go into it and what doesn't need to. In other words, I would need to team up with someone to do this. So my question is:

Is there anyone with good knowledge of the porting process who would be willing to assist? I would be happy to do the information gathering, but would need help to ask the right questions and someone would need to look through the responses and help draw conclusions.

@UBportsNews

Please give us an update on the improvements that have recently been merged into the armhf and arm64 root file systems, as well as those you expect to land in the immediate future.

Thanks,
Ari

@Guf said in Ubuntu Touch on LG G6 (h870 model): call for testers:

@makeixo @walidham Fixed! I applied the patch for bullhead which suggested the same: to disable CONFIG_ANDROID_PARANOID and to enable SECURITY_ANDROID_GID_CAPABILITIES, but I hadn't done it well. With the help of @tanevanwifferen (who suggested what was wrong), we fixed it ... so let's go for other issues, now

Could you be more specific, please? I am porting the LG G4 and the patch did not resolve the issue. But then my port is also based on a different kernel version (the 3.10). Don't know how relevant the fix is for my version?

Ari

@vadikas I am dealing with the same situation and the patch did not resolve the issue. Have you succeeded in solving this?

@Keneda Thanks.

The reason is that I passed the argument 'rate=44100' to the module module-droid-discover in the file touch.pa, which in turn means that this argument gets passed in the correct way.

However, the effect should be that that the sampling rate gets set to this value, but that does not happen, and I do not understand why, since I can set it correctly from the command line using pactl

Update:
I got help reading the output of

cat /var/log/syslog | grep pulseaudio

Based on error messages therein, I edited out three sections from audio_policy.conf

After recompiling I now have sound, but it is not clean. The quality is like "poor FM radio reception".

Now I need to determine the cause of this and make adjustments accordlingly. So far I have few clues. Some say sampling rate could be the cause. I adjusted the argument in my touch.pa file which passes rate to the module-droid-card-24 at load time. This did not help. syslog shows that 'requested rate=44100 but got rate=48000'

I don't know what to try next...

I am working on a porting Ubuntu Touch to the Samsung Galaxy S7 - herolte. I have added info on the current state of things here: https://docs.halium.org/en/latest/supplementary/devices/index.html

The issue I am currently working on is sound. Here is what I have found out so far:

• A sound card is registered, as confirmed from the output of 'aplay -l' and 'aplay -L'
• 'sudo dmesg | grep audio' gives 'lucky-audio sound: lucky_suspend_post : set AIF1 to slave'
• 'cat /var/log/syslog | grep pulseaudio' gives a good deal of output, among other things a few error messages, notably a complaint about not being able to parse any configuration, as well as not being able to load module-droid-card-24 and failing to open module-droid-glue-24

What configuration is it pulseaudio cannot find/parse, and where should it be located?
Why does module-droid-card-24 not get loaded when it is definitely present?
And why can module-droid-glue-24 not be read when it also clearly is present?

Are there other steps I need to take to pinpoint the source of the problem? I have been banging my head at this for a couple of weeks now with no luck, so help would be greatly appreciated!

Thank you!

Unfortunately, the bluetooth headset I secured was not registered by my N5. So I tested once more with my JBL bluetooth speakers. I got a connection between the device and the speakers, but the sound was not routed to the BT speakers. Instead, sound came from the device itself. After rebooting the device connected automatically to the BT speakers and I was able to play music on them. But when I disconnected the speakers from the bluetooth menu and then reconnected them, the sound once again came only from the device itself.

I have collected logs using the script you pointed out and will send them to you.

@peat_psuwit said in Call for testing: Updated Pulseaudio & better Bluetooth headset support:

@aribk The issue that the playing streams won't switch to the headset after a re-connect is issue #1045. However, the rest of the issues is not known to me. If you care enough, could you please check if it's a regression or not. If it is, or it's inconvenient to test with the previous version, please follow the instructions for collecting the log.

OK. Today I resumed testing on my N5. I reinstalled devel with the UBports installer and repeated your steps above.

I tried out a wired headset and this works well.

Then I followed some of canonical's steps that you linked to. I have the output of all the 'pactl list sink' tests if you're interested. They all give the expected media.role output, except when playing a ringtone. In this case I got 'media.role = "multimedia" ' But I played the ringtone from settings > sound > ringtones . Just thought it might be worth mentioning in case this gives a different result from an actual call.

I hope to secure a bluetooth headset during the course of the day to be able to test this. Will follow up and send you the logs if I run into trouble.

First, it would be great with an update on the Vollaphone.

Second, how important do you consider the community porting effort in bringing interest to the UBPorts Ubuntu Touch project as a whole? Given that there seem to be a number of half-functioning ports which cannot be installed using the installer, is this at all beneficial to the project? If the porting effort is a good thing in your view, can you recommend any specific sources of knowledge to those who are meeting hardware enablement challenges on their devices?

Third, could you give an update on Halium 7 & 9 again, like last week? Regarding Halium 9, what is the probability of success in creating a fully functional Halium 9 based port of UT on any device at the moment (and which are the best candidates) ? What are the main blockers, and when you peek into your crystal ball, how long do you think we will be burdened with them?

And last, with FIDO2 security beginning to be adopted within organizations and companies, is this on the roadmap for UT?

@peat_psuwit said in Call for testing: Updated Pulseaudio & better Bluetooth headset support:

@aribk The issue that the playing streams won't switch to the headset after a re-connect is issue #1045. However, the rest of the issues is not known to me. If you care enough, could you please check if it's a regression or not. If it is, or it's inconvenient to test with the previous version, please follow the instructions for collecting the log.

Thank you!

I read this only now, sorry! I will see if I can get round to it within the next couple of days.

Tested on N5

JBL and Bose speakers both work nicely.
I connected the phone to the sound system of my car (which is registered as a bluetooth headset) and there were issues. I did not have a SIM installed, so the following is based on playing music (which worked perfectly on the aforementioned speakers):

1. I got sound on the in-car sound system.
2. Sound was a bit low, even with in-car volume near max, so I decided to turn up the volume on the N5. This worked for a couple of seconds, then the sound was cut off. The music app (Cloud Music v. 1.6.2) intermittently showed progress playing the song, but no sound came over the speakers (nor from the phone).
3. I disconnected the phone from the car and was able to restart the app and get sound on the phone. I then reconnected while a song was playing. The phone showed it was connected, but sound emanated from the phone itself, not the in-car sound system. I was still on the in-car menu for connecting a bluetooth device. When I switched to the media menu, sound came from the car speakers a couple of seconds, then cut off completely. The device was still registered as connected. No sound came from the device itself either.

I also tested using the device hooked up to an external display. Previously, on RC, when using a bluetooth keyboard and mouse, the mouse would continue to work when the external display was connected, but the keyboard would not. It would still be connected, but text could not be typed from it. Now, using devel and testing your bluetooth modifications the keyboard functions perfectly when the external display is connected.

Hi

I would like to volunteer to help go over and edit the porting documentation and get it up to date. Problem is, I have insufficient knowledge to do this all on my own, but I thought if someone would care to point out what is out of date and what needs to be revised +explain a bit, I would be more than happy to do the writing and editing. (Maybe it could even help me overcome some obstacles I am experiencing myself in my current porting efforts.)

Best
Ari

I'd be happy to help with the testing. Will possibly need to wait a couple of days, as my N5 is currently my daily driver, but from some time early next week I should be ready.

3 questions:

First:

With recent changes in the UI on UT I can apparently configure a Libertine container and install desktop apps, but it looks like there is no way of using them. (My device is a Nexus 5)

Could you give a recap of which of the core devices (and community devices) are the ones that in theory can handle an external display, and what the status of the system is on these being able to connect to a display and run desktop apps?

Second:

Are there plans for improving bluetooth connectivity in the near future?

Third:

What is the most effective way someone can assist development when one does not have solid programming skills. (Besides translating, of which I have already done quite a bit)