Search Results for 'bluetooth'

[Member Xecure]

For most cases, if wifi works, bluetooth should work. For other cases, it is very possible someone has already build a driver for the specific bluetooth device, so compiling it with dkms should work well. Also, firmware may be missing, so finding the correct firmware may also be needed.
In my case, I was experimenting so much with different kernel builds and customizing so much stuff, I deleted something (probably firmware for the bluetooth device) I just stoped caring. I know it didn’t work out of the box and I really didn’t have any more energy to continue trying to fix this specific problem. I was too lazy to start everything from the beginning. Maybe some day in the future.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

My experience with Teclast x98 plus ii, a dual-boot android/windows cherrytrail (intel atom) based tablet.

Specs:
CPU: Intel Atom x5-Z8350
RAM: 4GB LPDDR3
Disk: 64GB eMMC ROM
Battery: 7800mAh
Screen: 9.7 inches – 2048 x 1536 (QXGA)
Wifi: shitty (have to use an external USB wifi receiver for better signal if needed)
Touchscreen: silead (medicre/shitty)

Android experience: really slow and buggy.
Windows experience: OK at the start. Every new update made it slower.

First solution: delete android and have a Windows only system.
Result: It worked well for some time, ended up being extremely slow starting up programs, writing on the virtual keyboard, etc. Last update made the “Updating” screen display for over 2 hours. I got fed up and decided to jump to linux on this device.

My linux journey
From Live USB, tested:
– XJUbuntu (Xfce ubuntu with drivers for the atom tablets): Even slower than windows. VERY buggy, but the most important things (for me) worked.
– MX Linux 18: Slow but better than windows. Wifi worked out of the box, but the touchscreen not. Did detect battery but couldn’t display changes
– antiX 17: The fastest of all systems I had tested. Wifi didn’t work, but the USB wifi receiver did. Touchscreen worked after adding the firmware to the correct folder. Did not detect battery. Updating the kernel to 4.19 had wifi working properly. Resolution was too big, and DPI only worked for text, so I “halfed” it to 768×1024. Needed to delete a package to get touch to work properly (only using evdev for touch, and needed xinput_calibrator to correctly calibrate, but it took some work calibrating it). After compiling a customized kernel, I now have the correct battery information.
– others: Had problems starting up, couldn’t detect/install in an eMMC disk, extremely slow systems, etc.

Fast forward to today, I have a very fast antiX 19 tablet with a customized fluxbox desktop and many scripts to make life easier. I have dual boot with windows (just in case), but I only use the antiX system on this device. I use this tablet mainly for reading and navigating the web. The battery can last over 7 hours of reading (estimate, I have never measured it) so it is more than enough. I can read infinitely if connected to the charger 😉

What does work:
– Screen
– Touchscreen
– Wifi
– Battery
– Hardware buttons

What doesn’t work
– Audio (jack or speakers/microphone) -> driver related
– Bluetooth
– Webcams (probably could work easily, but I don’t want them to)
– Auto-rotate sensors (not interested)

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member ModdIt]

You might find some more pertinent information here. Thread includes links. Armbian is not so far away from Debian.
https://forum.armbian.com/topic/6480-bluealsa-bluetooth-audio-using-alsa-not-pulseaudio/

Firstly, new user & first time poster to give thanks for AntiX. Cheers!

AntiX 19.2 runs on on an old broken HP 625 64 bit laptop.

Via ConnMan, I’ve been attempting to set default domain name servers;- for all users, for all connections, on this laptop.

(This is to use CleanBrowsing_Org’s DNS filtering as per their filters page.)

1) In /etc/connman/main.conf, add
Nameservers=185.228.169.168,185.228.168.168
From connman.conf(5), Nameservers is not listed as valid & doesn’t work.

2) Edit /var/lib/connman/settings to be:-

[global]
OfflineMode=false

[WiFi]
Enable=true
Tethering=false
Nameservers=185.228.169.168,185.228.168.168

[Bluetooth]
Enable=false
Tethering=false

[Wired]
Enable=true
Tethering=false
Nameservers=185.228.169.168,185.228.168.168

This idea does not work either.

For Linux, Clean Browsing recommends creating an immutable /etc/resolv.conf file on their Linux guide page.

What is the AntiX method of setting default DNS entries, for all user accounts, for all connections?

Thanks,
Craig.

• This topic was modified 3 years ago by Craig. Reason: Formatting
• This topic was modified 3 years ago by Craig. Reason: Argh! Formatting
• This topic was modified 3 years ago by anticapitalista. Reason: changed title since there are some excellent tips in the thread

[Member Xecure]

With Connman
antiX 19.2.1 base
Hit the network icon in the system tray. Move the wifi switch ON. Connect
antiX 19.2 full
Control Center > Network > Wifi Connect (Connman). Move the Wifi switch to on (green).

Without connman (only Ceni)
antiX 19.2 full -> uninstall Connman
https://www.antixforum.com/forums/topic/failing-with-liveusb-persistence/#post-32414
antiX 19.2.1 base -> uninstall Connman
https://www.antixforum.com/forums/topic/failing-with-liveusb-persistence/#post-32414
Change the uninstall code to:
sudo apt-get remove --purge connman connman-ui-gtk connman-bluetooth-firmware-antix

• This reply was modified 3 years ago by Brian Masinick.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member olsztyn]

Xecure wrote:

I will test this out today, but I believe you may be missing pulseaudio-module-bluetooth.

Thank you Xecure for your testing and confirming bluetooth is working fine with Runit variant of 19.2 Hannie Schaft… Looks like it was my overlooking pulseaudio-module-bluetooth after all…
After installing this missing module I also confirm bluetooth works fine for me with Runit variant of 19.2.
I apologize for confusion…
On memory requirements I will redo my testing as well with all components in place so I do not jump to conclusion…
Thanks and Regards.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Xecure]

Tested on antiX 19.2 (with 4.19 kernel) runit full x64 (only live, no persistence)
Installed pulseaudio, pavucontrol and pulseaudio-module-bluetooth. Enabled bluetooth using connman.

1. First test. Bluetooth had problems. Not able to launch “bluetoothctl” or “blueman-applet”
Diagnostic: Checking if bluetooth service is on/working

$service bluetooth status
[FAIL] bluetooth is not running ... failed!

Solution: Starting bluetooth service
sudo service bluetooth start

2. Second test (after starting bluetooth service). Bluetooth works well.
Starting blueman-applet and connecting to my bluetoth headphones works.
Setting the bluetooth headphones as output device in pavucontrol and then playing a youtube video. Audio works for bluetooth headphones.

Conclusion: bluetooth works for antiX 19.2 runit edition

My thoughts.
I barely understand sysV init, and I know nothing about runit. I know a bit about how to change stuff using the sysV Runlevel config (sudo sysv-rc-conf) but I have no idea of how to do things with runit (reason for me not using this antiX flavor). After starting the bluetooth service on runit, will it start again on the next boot? Does the user need to change something on their system for it to automatically start?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

olsztyn wrote:

– antiX 19.2 with respectable name of Hannie Schaft unfortunately does not work with bluetooth, regardless variant is Sysvinit or Runit.

I will test this out today, but I believe you may be missing pulseaudio-module-bluetooth.
I will return when I have done the experiments with antiX 19.2 runit edition.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member olsztyn]

rokytnji wrote:

But. Your runit reasons mystify me. Works on one. Not the other. Weirdness indeed.

Edit: But then again. Systemd distros sometimes is needed to make bluetooth gear work. Which leaves us out.

My preliminary testing indicates that antiX (Full) 19.2 Hannie Schaft Sysvinit variant behaves the same way as Runit variant for Bluetooth. Does not seem to work for either.
This means to me:
– antiX 19 fully updated Sysvinit variant works fine with bluetooth (Which means systemd is not required for this to work, but pulseaudio is).
– antiX 19.2 with respectable name of Hannie Schaft unfortunately does not work with bluetooth, regardless variant is Sysvinit or Runit.

This also means that 19.2 Sysvinit is not fully equivalent to 19 fully updated, which seems the latest working fine with bluetooth.
However, again to point out, bluetooth is not important to antiX, as apparently not many users care about bluetooth and the requirement of pulseaudio to make bluetooth work means additional huge ~70M memory demand, which is against antiX being lean principle. So from this perspective you may be right on being left out…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin rokytnji]

But. Your runit reasons mystify me. Works on one. Not the other. Weirdness indeed.

Edit: But then again. Systemd distros sometimes is needed to make bluetooth gear work. Which leaves us out. My example. Same speaker. Different distro.

https://www.linuxliteos.com/forums/network/skullcandy-soundmine-bluetooth-external-speaker/

• This reply was modified 3 years ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Forum Admin rokytnji]

From your tip I infer that problem might be specific to my bluetooth devices? That is possible, of cours

Not all bluetooth devices.hardware are linux compatible. Just like wireless dongles. Some are drm. Locked into Windows or Mac.
Usually lat4ely. I google for linux compatibility.

But my wife. A Windows User. Buys me presents I try and make work sometimes. It is how I learn this stuff.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member olsztyn]

rokytnji wrote:

I usually troubleshoot this kind of problem with the terminal and the dmesg command to find my errors.
You will have to know some info on your bluetooth speaker though to use dmesg command.

Thanks rockytnji for these tips. I will figure this out how to use dmesg command.
From your tip I infer that problem might be specific to my bluetooth devices? That is possible, of course…
However, regardless of that, collecting facts after meticulous testing of various variants of antiX it is fact that bluetooth works fine on these devices in fully updated antiX 19 Sysvinit variant, regardless kernel is 4.9, 4,19 or 5.5.
Currently such fully updated antiX 19 Sysvinit, kernel 5.5 is the one I use… Particularly that in my testing it uses the least of memory, appears fastest and all that I use does work. My venture into Runit 19.2 seems to indicate it is in beta at this point, so I would not expect all is smooth yet. This topic was just my question if it works for anyone…
I understand that bluetooth is probably the least important for antiX, particularly that it requires pulseaudio and from my observation pulseaudio increases the memory use by rather large amount, seems like by 70M in reality… So not a priority.
Next I will try to install the latest 19.2 Sysvinit variant of Hannie Schaft and try to load with the same kaboodle of apps and test.
One thing I do not understand from my testing though: Runit variant (Full) of 19.2 Hannie Schaft appears to use more memory in the same setting for me than fully updated 19 Sysvinit. But this observation is outside the scope of this topic…

• This reply was modified 3 years ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin rokytnji]

I had to use pulse audio to get my bluetooth speaker working.

Skullcandy usb speaker.

I usually troubleshoot this kind of problem with the terminal and the dmesg command to find my errors.
You will have to know some info on your bluetooth speaker though to use dmesg command.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

My question to team arises from the fact that in my testing of 19.2 Runit version of Hannie Schaft antiX I was not able to make bluetooth work under the same conditions as Sysvinit version.
Specifically it works fine for me for the following:
– antiX 19 Sysvinit version fully updated as of today – this I understand is equivalent to antiX 19.2 Hannie Schaft.
– Bluetooth turned on, paired to bluetooth devices (tested on two)
– Pulseaudio daemon started (pulseaudio -D &). Just to be clear: I do understand pulseaudio is using about 30M more memory and I do not like it for that reason, but in cases you need bluetooth to work there seems no other option…
– Bluetooth works fine in such environment both with Kernel 4.19 and 5.5 as tested.

Bluetooth does not work for me with the same prerequisites when antiX is 19.2 Runit version of Hannie Schaft, both when kernel is either 4.19 or 5.5. Bloetooth pairs but connection to device fails.
I have not done testing of the same under 19.2 Sysvinit version of Hannie Schaft, relying on statements in this forum that fully updated antiX 19 is equivalent to 19.2.
So my conjecture seems to be pointing to any of the following:
– Can this behavior be attributed to some difference between fully updated antiX 19 and antiX 19.2 in spite of assumptions it is the same?
– Is this behavior related to Runit?

I would appreciate some tips as otherwise Runit version of Hannie Schaft seems to work fine, so it would be great if this happens to be something simple…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member AA BB]

Thank you BobC I think you hit the nail on the head.

I spent the better part of this evening installing a fresh downloaded copy of 19.2 386 base on another box that has MX installed.

After the install, the only changes I made were those recommended by anticapitalista :
1 Remove connman and cmst
sudo apt-get remove –purge connman cmst connman-bluetooth-firmware-antix
For antiX-19.2-base, cmst is not installed, nor connman-bluetooth-firmware-antix
but you should remove connman-ui in step 1
2 Delete the resolv.conf sym link in /etc/
3 Create a new symlink in etc like this (in a terminal)
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
4 Then use ceni

ceni sent back error messages so I remove file /run/wpa_supplicant/eth1 manually, then re-booted
… waited a minute…then run ceni again.
BUT ceni gives me the same output my other box gave me.

When I was running my antiX version prior to 19.2, I was able to connect using connman, but it kept dropping the connection after 1-5 minutes
Using ceni under 19.2 doesn`t seem to improve things .