Give me 10
2 Likes
While @PhaseLockedLoop is writing, go ahead and re-check the different options in the advanced tab now that your outputs are recognized.
1 Like
I can defintely hear a slight static pop when switching from speaker playback to headphone playback. I think I am close 
Thereās different audio modes under the advanced tab, if you have a faulty setting you wonāt get audio, but if itās still silent after testing every option then wait for a more advanced reply
First off welcome to the community! thanks for stopping in
as for your issue. I realize your running with Ubuntu. Im going to post my response to this on the exact same issue on red hat based distros then we can adapt it below this post
For audio to work on Bay Trail or Cherry Trail bases devices you need to have an UCM profile for your device.
You need to basically build a backported alsa lib. Its not too hard but lets roll with it
https://fedorapeople.org/~jwrdegoede/alsa-lib-ucm/
Download the alsa-lib-1.1.6... and alsa-ucm-1.1.6... files and in a directory with both these files run:
sudo rpm -Uvh alsa-*.rpm
To install the new version, then do:
killall pulseaudio
After this you should have working sound. Chances are that your device has only a single speaker and needs a kernel quirk to mark it as such, to test this go to the sound settings in gnome-control-center and hit the "test speakers" button, you will likely only hear sound for the left speaker.
To test if the mono speaker quirk helps, add the following to the kernel commandline: snd_soc_sst_bytcr_rt5640.quirk=0x563432
Your device may also need a quirk for the internal microphone and for detecting if headphones/a-headset are plugged in.
To test the internal microphone do:
sudo dnf install gnome-sound-recorder
And then run gnome-sound-recorder (without any headphones / headset plugged in) and make a test recording. If this does not work, try using the following quirk
setting instead:
snd_soc_sst_bytcr_rt5640.quirk=0x563433
Notice the last 2 has changed to a 3 and no other changes.
Once you've the microphone working, please test that headphones get seen when plugged in (they should show up in the sound settings in gnome-control-center)
if you had to change the quirk for the microphone you likely also need to change it for jack-detect into:
snd_soc_sst_bytcr_rt5640.quirk=0x563423
Note this time the second to last number has changed from 3 to 2. So if you did not need to change the microphone settings, but the jack detect is not working with the defaults, then this becomes:
snd_soc_sst_bytcr_rt5640.quirk=0x563422
Please let me know if the updated alsa-lib fixes things and what the rights quirks are for your device. When you know the right quirks please also run the following command as a user, not as root :
grep . /sys/class/dmi/id/* 2>/dev/null
And copy and paste the output here, this will allow me to add the correct quirks to the quirk table in the kernel so that future kernel versions will do the right thing automatically.
Now we need to migrate this from fedora to ubuntu lets do it. The directions will likely be quite different so I may have missed it butWhich version of ubuntu are you running. That is where we will start
better yet run sudo apt install neofetch ā¦ install itā¦ run itā¦ paste it hereā¦ Should be similar to :
HEIMDALL& (
((( ( (((
(( ((((# (( heimdallr@WiFightWhenWeCanMakeLove
((( ((( ((((((( ((( ((( -----------------------------
((( ((( ( (( ((( OS: Ubuntu 18.04.2 LTS x86_64
(( ((( (( ( (( ((& (( Host: GL502VT 1.0
(( (( (( ((( (((((( (( (( ( Kernel: 4.18.0-17-generic
(( (( (( ( (( (( (( ((( ( Uptime: 1 min
(( (( ((( (( (( (( ((( (( ( Packages: 2565
((( (( ((( ( (( ( ((( (( ( Shell: bash 4.4.19
(( (( (( ((((((((( (( (( ( Resolution: 1920x1080
(( #(( ((( ( ( ((( (( ( DE: GNOME 3.28.3
((( ((( ((( (((( (((( (( ((( (( WM: GNOME Shell
((( ((( ( ((( #( ((( ((( WM Theme: Adwaita
((( ((( ((( ((( ((( ((( Theme: Telinkrin-Gradient-rig
((( ( ((( ((( ( ((( Icons: Suru++ [GTK2/3]
((( ( (( (( ( ((( Terminal: guake
(( (( ((((( ( (( CPU: Intel i7-6700HQ (8) @ 3.
(((( (((( GPU: Intel Integrated Graphic
(( (( GPU: NVIDIA GeForce GTX 970M
(( ((& ((( (( Memory: 1254MiB / 15904MiB
(( ((( ((
( ((( (( (
(( (( (( ((
((( (((
Im working on finding the ubuntu UCM port for alsa lib right now. Essentially we just need to do that. I am assuming no linux experience or some?
EDIT: Seems I miscalculated your linux experience. Okay Lubuntu 18.10 Ill have to look if the version of alsa in there is working out of box and is just a matter of conf or not
1 Like
Sorry for the delay had to switch computers to make it easier to dump text
tjr@tjr-pc:~$ neofetch
.-/+oossssoo+/-. tjr@tjr-pc
`:+ssssssssssssssssss+:` ----------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 18.10 x86_64
.ossssssssssssssssssdMMMNysssso. Host: HP Pavilion x2 Detachable P
/ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 4.18.0-10-generic
+ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 56 mins
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 1906 (dpkg)
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 4.4.19
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Resolution: 1280x800
ossyNMMMNyMMhsssssssssssssshmmmhssssssso DE: LXQt
ossyNMMMNyMMhsssssssssssssshmmmhssssssso WM: Openbox
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Theme: Arc-Darker [GTK3]
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Icons: Adwaita [GTK3]
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ Terminal: qterminal
+sssssssssdmydMMMMMMMMddddyssssssss+ Terminal Font: Ubuntu Mono 14
/ssssssssssshdmNNNNmyNMMMMhssssss/ CPU: Intel Atom Z3736F (4) @ 2.16
.ossssssssssssssssssdMMMNysssso. GPU: Intel Atom Processor Z36xxx/
-+sssssssssssssssssyyyssss+- Memory: 874MiB / 1922MiB
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
a
Neat stuff!
LOL cool okayā¦ now you mentioned having the correct ucm installed
so maybe we are past the fedora specific directions. read through those and see if you can make the same modifications on ubuntuā¦ I think this issue is fixed in 19.04 I could be wrong
Wil do, thanks I will read through it and update everyone on what happens.
It would likely be wise to migrate there or back to the 18.04 LTS with less than 3 months support left on 18.10. I installed Lubuntu 19.04 on a spare PC but havenāt had the chance to see what all has been fixed.
1 Like
18.04 for long term stability
19.04 for just make it work
1 Like
Ill install 19.04 and see what happens
1 Like
Wish I could help but donāt know enough about these kinds of problems, I am interested to see where it goes, though
2 Likes
I have added a new update in my original post, TLDR: blutooth audio works now but still no internal sound or wifi. But i am happy just to be able to listen to music and watch Level1News.
1 Like
I have another update, if anyone wishes to read it please take a look at my original post. I believe, though not perfect I have arrived at a happy medium between convience and usability with the HP tablet. Thanks again to all who responded, I guess we can mark this as resolved though the solution was not perfect.
1 Like
You have learned how to troubleshoot - you have reached level 1! āPadum-tssā
Some hardware just isnāt all too linux-friendly.
1 Like
I followed your instructions and built and installed the rpm files but i ran into issues with getting gnome-control-center to run, it may be a issue with Lubuntu using a differnt UI shell then Gnome. The install was successful after --force-all and overwriting the existing files. After the install though the HDMI audio was intermittingly fading in and out. I didnt get the mic or speakers to work though I but since the audio was not working i didnt add those quirks to the kernal command line. Let me know if i should add those quirks just for the heck of it.
Well you should not have built rpms on Ubuntu those were for fedora and red hat based distros unless your saying you built the software for Ubuntu and just confused some wording?
You could add those to the kernel command line to see if the built in Ubuntu packages handle it
Yes I built them into .deb package using alien and installed using dkpg. I will let you know if anything happens with messing around with those quirks.
Excellent. The dependencies should have all been taken care of if it was done correctly.
Yeah throw those in. Its mainly the controller that has weird issues
Hi there
Thanks for your post.
I could fix the audio issue on Fedora 33: bugzille id=1896924 (somehow I am not allowed to post links, so just go to the bugzilla website and use the id i meantioned).
Maybe the same quirk can be applied on Ubuntu? I have no idea, since I have no idea about any of this. But maybe, if you are still looking for a solution, there would be one for Fedora.
Cheers
1 Like