Mobile Hotspot doesn't work FP3 - 1.13

[Jaguell]

Hi,

I have installed the last version 1.13-s-20230724313396-stable-FP3 yesterday and left a feedback on the forum.

I use mobile hotspot to work on my laptop, and since the last update, it doesn’t work any more.

I’m using both FP3 on /e/OS and a Samsung (s10) on Android, with the same provider (Bouygues). The Android works well, but when I turn mobile hostpot on my FP3, my laptop (windows 11) doesn’t display any network any more.

Could anyone help me?

Thanks,

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services

[MRTN]

Hotspot is working for me, my device is also FP3 with /e/OS 1.13-s stable build.

Perhaps you could try deleting/resetting the connection on your laptop, then connecting back to your hotspot…?

Another (quick) solution is the use USB-tethering or Bluetooth-tethering.

[AnotherElk]

Wi-Fi hotspot worked for me, too, between my Fairphone 3 on 1.13-s-20230727314102-dev-FP3 and my Fairphone 2.

[Jaguell]

I reset connection on my laptop (Win 11) and mobile, both are updated, drivers as well, it’s not working.

I put my FP3 simcard in the Android smartphone to check hotspot network on my laptop, and it works very well.

Set it back into the FP3, hotspot is still not working on my laptop.

But strange, FP3 hotspot is working on my Android phone.

I tried then to share network with hostpot between FP3 to Android to laptop, but it’s not working.

Guess there’s something which changed in this 1.13 version between my FP3 and my laptop.

[aibd]

This does not seem very likely unless you have other mobile data issues, but I do seem to remember reported #apn changes in the case of an FP3 update.

(My speculation is that your “working” Bouygues APN settings may have been adjusted to an “deficient” set from apns-conf.xml).

You might

• Ask your carrier to reset your APN settings, that is send the settings OTA to the phone.
• Check the published APN settings against what you have on the phone.
• Check published APN against the “inbuilt pre-selections” obtained from apn-conf.xml

I found these lines for Bouygues within apn-conf.xml – Android 12 (S)

  <apn carrier="Bouygues Telecom" mcc="208" mnc="20" apn="mmsbouygtel.com" mmsc="http://mms.bouyguestelecom.fr/mms/wapenc" mvno_type="spn" mvno_match_data="Bouygues Telecom" type="default,dun,mms,supl" authtype="1" protocol="IPV6" roaming_protocol="IP" />
  <apn carrier="Bouygues Pro" mcc="208" mnc="20" apn="a2bouygtel.com" user="a2b" password="acces" type="default,supl" />
  <apn carrier="Bouygues WAP" mcc="208" mnc="20" apn="mmsbouygtel.com" type="default,supl" />
  <apn carrier="Bouygues MMS" mcc="208" mnc="20" apn="mmsbouygtel.com" proxy="" port="" user="" password="" mmsc="http://mms.bouyguestelecom.fr/mms/wapenc" mmsproxy="62.201.129.226" mmsport="8080" mvno_type="spn" mvno_match_data="Bouygues Telecom" type="default,supl,mms" />
  <apn carrier="BouyguesGPRS ISP" mcc="208" mnc="21" apn="ebouygtel.com" proxy="" port="" user="" password="" mmsc="" type="default,supl" />
  <apn carrier="MMS Bouygues" mcc="208" mnc="21" apn="mmsbouygtel.com" proxy="" port="" user="" password="" mmsc="http://mms.bouyguestelecom.fr/mms/wapenc" mmsproxy="62.201.129.226" mmsport="8080" type="mms" />
  <apn carrier="BouyguesGPRS ISP" mcc="208" mnc="88" apn="ebouygtel.com" proxy="" port="" user="" password="" mmsc="" type="default,supl" />
  <apn carrier="MMS Bouygues" mcc="208" mnc="88" apn="mmsbouygtel.com" proxy="" port="" user="" password="" mmsc="http://mms.bouyguestelecom.fr/mms/wapenc" mmsproxy="62.201.129.226" mmsport="8080" type="mms" />

[Jaguell]

Thanks, I’m going to try this.

I have another laptop running with Linux Mint, and FP3 hotspot is working very well on Linux.

[aibd]

In that case much more likely to be a Windows issue, I just found a few relevant hits online, here is one https://www.makeuseof.com/windows-11-mobile-hotspot-not-working/

[Jaguell]

So Windows wrote DNS record was missing on this network, so I opened properties in Wifi network, and saw that IPv6 wasn’t tick so I ticked it (in red in picture), and it finally worked !

I’ll check that next time I update /e/OS.

Thanks for your help!