robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
Mathew has quit [Quit: Leaving]
mcbridematt has joined #aarch64-laptops
Kira has quit [Remote host closed the connection]
Kira has joined #aarch64-laptops
baozich has joined #aarch64-laptops
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
possiblemeatball has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
jglathe_volterra has joined #aarch64-laptops
hightower4 has quit [Remote host closed the connection]
hightower4 has joined #aarch64-laptops
Kira has quit [Remote host closed the connection]
Kira has joined #aarch64-laptops
Kira has quit [Remote host closed the connection]
Kira has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit []
<lollaritits[m]>
is stuttering with bluetooth audio a known issue?
<lollaritits[m]>
and what can i do against that ?
<jhovold>
bluetooth range on the x13s is crap as we haven't been able to get qcom to release the required board file
<jhovold>
I get like 2-3 meters here before things break up
<jhovold>
you can get better range by knowingly using an incorrect board file, perhaps the fw falls back to some default, or possibly even just uses random values that happen to work better
<jhovold>
not sure i'd recommend it, with the windows board file the range even appears to be too good...
<Segfault[m]>
lol in windows my x13s gets better bluetooth range than my desktop with its full size antenna
<Segfault[m]>
i thought lenovo released the board file though? or was that for wifi
<jhovold>
yeah, that was for wifi
<Segfault[m]>
:/
<Segfault[m]>
and the board file can't somehow be extracted from windows?
<jglathe_x13s>
hmm I have qca/hpnv21.b8c loaded, good BT connection - this is from windows, yes
iivanov has joined #aarch64-laptops
<jhovold>
you can just copy and use the windows patch file as I mentioned above, but it seems that the firmware expects the patch file to come from the same build
iivanov has quit []
iivanov has joined #aarch64-laptops
<jhovold>
I get much better range by just using the previous patch file with the latest firmware in linux-firmware
<jhovold>
when the versions (builds) match up, I only get 2-3 meters
<jglathe_x13s>
konradybcio I have downloaded and innoextracted the drivers from lenovo, qcadsp8280.mbn is identical
<jglathe_x13s>
that's the one that gets loaded on windows, hmm
jglathe_ has joined #aarch64-laptops
jglathe_volterra has quit [Ping timeout: 480 seconds]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
z3ntu has joined #aarch64-laptops
abelvesa has joined #aarch64-laptops
f_ has joined #aarch64-laptops
<wiley[m]>
jhovold: yes, rebuilt with CONFIG_BT_HIDP enabled and that seems to make earbuds behave
<wiley[m]>
oh wait, false alarm, still broken
<wiley[m]>
they connect and then disconnect
<jhovold>
wiley[m]: anything in the logs? Did HIDP make any difference?
<wiley[m]>
spotted luetoothd[1798]: src/profile.c:connect_io() Unable to connect Hands-Free Voice gateway: socket(STREAM, RFCOMM): Protocol not supported (93)
<jhovold>
ok, I need to enable RFCOMM as well then
<wiley[m]>
so I'm enabling RFCOMM to see if that helps
<jhovold>
please try, would be good to know if HIDP was actually needed too
<wiley[m]>
RFCOMM enabled, HIDP disabled, and they work now
f_ has quit [Remote host closed the connection]
f_ has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
f_ has quit [Ping timeout: 480 seconds]
<jhovold>
wiley[m]: thanks for confirming, I'll go enable rfcomm in johan_defconfig
driver1998 has joined #aarch64-laptops
<driver1998>
Hello guys, I have a 8180x primus prototype device and ran MollySophia's v6.4-rc2 tree, and it works fine there
<driver1998>
But when I try mainline the screen is garbled in Wayland.
<driver1998>
X11 and framebuffer console are unaffected