antix 19 base iso android usb tethering wont work

[Member realprogramminglol]

I have switch from minimal Debian to antiX not long ago, I try to use LiveUSB since just carrying around usb pendrive feels so easy

But android usb tethering doesn’t work. It happens on archived Debian 9,8 iso as well.

Check my reddit post: https://www.reddit.com/r/debian/comments/gumneo/old_debian_isos_tested_stretch_in_archive_dont/

It turns out that it is quite important to have this feature for LiveUSB.

Advise me if this is kernel issue or what

• This topic was modified 2 years, 8 months ago by realprogramminglol.

[Member Xecure]

Helpful

Up

0

::

On antiX 17 (Debian 9), Android USB tethering worked using ceni, as you can see in this thread:
https://www.antixforum.com/forums/topic/usb-tethering-with-android-smartphone/

All seems to indicate that it should also work on antiX 19.

As an experiment, I decided to try it out myself on a live USB (no changes, kernel 4.9.212) antiX 19.2.1 base x64.
0. Boot into my antiX 19.2.1 base live USB from my laptop.
1. I made sure connman was running (you should see a corresponding icon in the systemtray). If it isn’t active, Launch it from the COntrol Centre or from App Select (search for connman). Make sure it is running.
2. I connected my phone (Android 9 phone) using a USB cable to the laptop running antiX 19.2.1 base.
3. On my mobile device, I activated “share my connection through USB” (in my language; it probably means “USB Tethering”) in the corresponding section found in “Settings”.
4. After activating it, suddenly my system has internet connection! Success without expecting it at all!

Please explain what steps you followed, what antiX edition are you running, and what errors poped up.

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

[Member realprogramminglol]

Helpful

Up

0

::

Thanks for replying. I have tried the antiX 19.2.1 x64 base ISO again. This time I tried with 5 phones, 4 works out of them.

Details of them, of lsusb and dmesg, as below:

5. HUAWEI nova 4e, Android 10, works fine

Bus 001 Device 029: ID 12d1:108a Huawei Technologies Co., Ltd.

[ 1212.368198] usb 1-2: Product: MAR-LX2
[ 1212.368200] usb 1-2: Manufacturer: HUAWEI
[ 1212.368203] usb 1-2: SerialNumber: 8RBDU19322016627
[ 1309.594850] rndis_host 1-2:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-2, RNDIS device, 0e:56:a4:fe:d1:bf
[ 1331.953220] usb 1-2: USB disconnect, device number 29
[ 1331.953459] rndis_host 1-2:1.0 usb0: unregister ‘rndis_host’ usb-0000:00:14.0-2, RNDIS device

4. HUAWEI nova 2i, Android 8, works fine

Bus 001 Device 023: ID 12d1:108a Huawei Technologies Co., Ltd.

[ 1051.629705] usb 1-3: Product: RNE-L22
[ 1051.629708] usb 1-3: Manufacturer: HUAWEI
[ 1051.629721] usb 1-3: SerialNumber: 8UEDU18109008233
[ 1051.631867] rndis_host 1-3:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-3, RNDIS device, f6:c1:1c:1f:d9:1a
[ 1079.593577] usb 1-3: USB disconnect, device number 23
[ 1079.593819] rndis_host 1-3:1.0 usb0: unregister ‘rndis_host’ usb-0000:00:14.0-3, RNDIS device

3. Vivo V5 1601, Android 6, works fine

Bus 001 Device 020: ID 0e8d:2004 MediaTek Inc.

[ 686.579765] usb 1-3: Product: vivo
[ 686.579768] usb 1-3: Manufacturer: MediaTek
[ 686.579770] usb 1-3: SerialNumber: 4HNFLFJ799999999
rndis_host 1-3:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-3, RNDIS device, aa:50:f0:2c:43:62
[ 923.313902] usb 1-3: USB disconnect, device number 20
[ 923.314030] rndis_host 1-3:1.0 usb0: unregister ‘rndis_host’ usb-0000:00:14.0-3, RNDIS device

2. Samsung A5 2016, SM-A510FD, Android 7, works fine

Bus 001 Device 014: ID 04e8:6863 Samsung Electronics Co., Ltd Galaxy series, misc. (tethering mode)

[ 302.590980] usb 1-3: Product: SAMSUNG_Android
[ 302.590983] usb 1-3: Manufacturer: SAMSUNG
[ 302.590985] usb 1-3: SerialNumber: 33009d5bcc6eb2cb
[ 303.149552] usbcore: registered new interface driver cdc_ether
[ 303.155598] rndis_host 1-3:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-3, RNDIS device, fa:b8:26:dd:f5:5f
[ 303.155610] usbcore: registered new interface driver rndis_host
[ 303.187931] 8021q: 802.1Q VLAN Support v1.8
[ 433.648176] usb 1-3: USB disconnect, device number 14
[ 433.648302] rndis_host 1-3:1.0 usb0: unregister ‘rndis_host’ usb-0000:00:14.0-3, RNDIS device

1. Xiaomi Mi A3, Android 10, not working

Bus 001 Device 017: ID 2717:ff80 Xiaomi Inc. Mi/Redmi series (RNDIS)

[ 513.533327] usb 1-3: Product: Mi A3
[ 513.533330] usb 1-3: Manufacturer: Xiaomi
[ 513.533332] usb 1-3: SerialNumber: 677434b06a06

I will proceed to test my Debian 10 and Arch Linux ISOs with my Mi A3 (again), will report here later

• This reply was modified 2 years, 8 months ago by realprogramminglol.
• This reply was modified 2 years, 8 months ago by realprogramminglol.

[Member realprogramminglol]

Helpful

Up

0

::

I think my previous post has hit limit on editing within short period of time.

I have tried 5 Android phones, 4 out of them were working, only 1 phone Mi A3 Android 10 was not working.

So I went ahead and tested with Debian 10 and Arch Linux ISOs, turned out that Mi A3 was working fine with them.

Yea, something is wrong I think, not sure why Mi A3 is not picked up by antiX and archived Debian ISOs.

[Member Xecure]

Helpful

Up

0

::

I don’t have a new phone with Android 10 with me to test. You could try to update the live kernel to 4.19 (https://www.antixforum.com/forums/topic/video-update-your-kernel-on-antix-live-usb/) or try a different live edition with 4.19 kernel (https://sourceforge.net/projects/antix-linux/files/Final/antiX-19/4.19_kernel/) and see if with a newer kernel (Debian 10 buster uses a 4.19 kernel) you can get antiX to properly work with your Mi A3.

Does someone else have this (or a similar) device and can test if they also experience problems with USB tethering?

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

[Member realprogramminglol]

Helpful

Up

0

::

Yea, I updated kernel to 5.5, now USB Tethering is working with Mi A3

[ 419.733567] usb 1-3: Product: Mi A3
[ 419.733570] usb 1-3: Manufacturer: Xiaomi
[ 419.733572] usb 1-3: SerialNumber: 677434b06a06
[ 419.747887] rndis_host 1-3:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-3, RNDIS device, e6:7b:8f:d8:0a:99

Well, so it was patched in newer kernel. Maybe one day I will understand it after learning how to git-send-email and Linux development
Write and Submit your first Linux kernel Patch (Watched it yesterday)

By the way, below are my experience and my doubts when using antiX:

1. The original linuxfs in antiX ISO is compressed by xz right? When remastering I always choose xz

2. Current live system (toram) is booted via UEFI with GPT. Cloning this live system in Live USB maker to a USB drive (with GPT option), and booting it via UEFI went directly to grub (not grub rescue), which means it failed to find config file. However, this issue cannot be reproduced using antiX 19.2.1 base ISO with Live USB Maker (GPT option). Repair Linux Boot with Grub Rescue

3. Do you know how ISO snapshot will behave? If I ISO snapshot under BIOS/MBR scheme, can UEFI/GPT boot the USB drive made via Live USB maker with that generated ISO? and vice versa

4. Not sure if I am paranoid, but with Default settings (without persistence or frugal), I actually saw connman saved my wifi password and connect automatically (Not gonna retry this step though), maybe you can correct me

[Member Xecure]

Helpful

Up

0

::

Good thing you got it to work with a kernel update. If most things could be solved like this it would be great.

realprogramminglol wrote:

1. The original linuxfs in antiX ISO is compressed by xz right? When remastering I always choose xz

You see the options there. Some are bigger but uncompress faster than the ones that ocupy less space. It is up to you to choose the one that works best for you (for slow CPU, the bigger less compressed is best, for example).

realprogramminglol wrote:

2. Current live system (toram) is booted via UEFI with GPT. Cloning this live system in Live USB maker to a USB drive (with GPT option), and booting it via UEFI went directly to grub (not grub rescue), which means it failed to find config file. However, this issue cannot be reproduced using antiX 19.2.1 base ISO with Live USB Maker (GPT option). Repair Linux Boot with Grub Rescue

Never experienced this. I will have to test at some point when i have the time. For now you could boot toram, create a snapshot, and then use Live USB maker using the .iso snapshot instead of the live/toram system.

realprogramminglol wrote:

3. Do you know how ISO snapshot will behave? If I ISO snapshot under BIOS/MBR scheme, can UEFI/GPT boot the USB drive made via Live USB maker with that generated ISO? and vice versa

I think there shouldn’t be a problem. I believe dolphin_oracle mentioned this in one of his videos, but I am not 100% sure.

realprogramminglol wrote:

4. Not sure if I am paranoid, but with Default settings (without persistence or frugal), I actually saw connman saved my wifi password and connect automatically (Not gonna retry this step though), maybe you can correct me

antiX live DOES save some things on the live system (mainly for easier wifi setup and other stuff, so that they don’t have to be configured each time).
I think this can be desabled with the nosavestate bootcode. You can also change what specific files are saved editing /live/boot-dev/antiX/state/general-state-files and /live/boot-dev/antiX/state/machine-state-files
Read more about boot parameters: http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/boot-params.html

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

[Member kouroukinos77]

Helpful

Up

0

::

after read my topic (https://www.antixforum.com/forums/topic/how-to-enabled-usb-tethering-android/) ,

after upgrade I’m on this kernel :

$ uname -a
Linux antix1 5.8.7-antix.1-amd64-smp #1 SMP PREEMPT Sun Sep 6 20:52:44 EEST 2020 x86_64 GNU/Linux

I don’t have usb tethering internet with my USB. So I don’t know how to do that, this command say me :

$ connmanctl tether gadget on

Commands for making a wifi connections in connmanctl
----------------------------------------------------
    agent on
    enable wifi
    services
    connect wifi_<tab>
    [wait for connection to appear]
    quit
    ifconfig -s
----------------------------------------------------

Error enabling gadget tethering: Method "SetProperty" with signature "sv" on interface "net.connman.Technology" doesn't exist

I have Xiaomi mi A3 phone on Android 10

$ uname -r
4.9.212-antix.1-amd64-smp
Mon retour de inxi -Fxz : https://pastebin.com/kqRMrRZZ
my xmpp : weerbor@jabber.fr

[Member kouroukinos77]

Helpful

Up

0

::

Heh ! Sorry it work now, It’s my old usb cable doesn’t work good, I try to use another USB cable ! Thank you very mutch.

But My network is very slowly, I need to change my ISP … Maybe. And I don’t have upload :/

3,44 for download and 0 for upload ! Wow vive La France !

• This reply was modified 2 years, 6 months ago by kouroukinos77.

$ uname -r
4.9.212-antix.1-amd64-smp
Mon retour de inxi -Fxz : https://pastebin.com/kqRMrRZZ
my xmpp : weerbor@jabber.fr

[Member ModdIt]

Helpful

Up

0

::

Hi kouorokinos,
You may find moving the phone to a window will give better speed, try different ones to get the best signal strength and up/download speeds.
Make sure screen is off, all possible apps closed and before hotspot or tethering usage clearing cache can often help.
And do use a good cable, the difference can be great.

Like most devices, The phone you have tends to slow down badly due to throttling, you can put it in a plastic bag then place on a cooling pack if
you are using it for longer periods. I have a 1/2 liter Gel Cool pack at about 5C, that makes a big difference.

If you do cool the phone let it warm up in the bag afterwards to prevent possible condensation damage.

[Author]

Posts