How to disable the Wifi feature?

1

My application doesn’t need Wifi at all: I only need the cellular network for my data connection.

How can I remove the Wifi feature?
I use le_data_SetTechnologyRank(1, LE_DATA_CELLULAR) to indicate that I need cellular network, but, how can I avoid that my application still tries to connect to wifi if my cellular network drops for a while?
I tried to stop the wifiService app, but, then the dataConnectionService app crashes.

2

Hi annaertd,

May I ask what software version you are using?

In my case using Legato 16.10.3, “app stop wifiService” does not crash dataConnectionService.
And after “app restart dataConnectionService”, it shown “wifi” is unsupported so not added to the list.

Would you try “app remove wifiService” then reboot device and see any improvement?

Thank you.

3

Hi,

I use Legato 16.10.3.

When I stop the wifiService, my dataConnectionService crashes, and I get the following log info:
Nov 7 16:23:01 swi-mdm9x15 user.info Legato: INFO | supervisor[478]/supervisor T=main | app.c app_Stop() 2731 | Stopping app ‘wifiService’
Nov 7 16:23:01 swi-mdm9x15 user.emerg Legato: EMR | dcsDaemon[535]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (dcsDaemon.dataConnectionService.le_wifiClient:be9ebfafe0e78e555703d0c8fc00208e).
_Nov 7 16:23:01 swi-mdm9x15 user.warn Legato: -WRN- | appStopClient[11063]/framework T=main | LE_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!
Nov 7 16:23:01 swi-mdm9x15 user.info Legato: INFO | supervisor[478]/supervisor T=main | apps.c DeactivateAppContainer() 340 | Application ‘wifiService’ has stopped.
Nov 7 16:23:01 swi-mdm9x15 user.info Legato: INFO | supervisor[478]/supervisor T=main | proc.c proc_SigChildHandler() 1942 | Process ‘dcsDaemon’ (PID: 535) has exited with exit code 1.
_Nov 7 16:23:01 swi-mdm9x15 user.warn Legato: -WRN- | appStopClient[11064]/framework T=main | LE_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!

I removed the wifiService, and performed a device reboot.
Now, the issue is solved.

Thanks.

Greetings.