Lose mobile data when roaming, or share data are switched on

I found today, while using cell phone mobile data, with a good signal, that when I turned on mobile data sharing, that I immediately lost correction input. With further experimentation I found that when I turned on either data roaming, or mobile data sharing, the mobile data option would turn itself off, and not allow activation until after a reboot. Is this normal?

Reach RS2, ver 2.25.2 Dev. Ting mobile. (Works well)
In the US,

Simple system report
app version: 2.25.2-dev
current_network:
  ip: 192.168.42.1
  security: wpa-psk
  ssid: reachRS2-O:85:75
enabled: true
mode: hotspot
base_mode:
  base_coordinates:
    accumulation: 600
    mode: fix-and-hold
  output:
    io_type: 'off'
    settings:
      cloud:
        mount_point: ''
      lora:
        air_rate: 18.23
        frequency: 927300
        output_power: 6
      ntripsvr:
        address: ''
        mount_point: ''
        password: '***'
        port: -1
      serial:
        baud_rate: 38400
        device: ttyEXTS0
      tcpcli:
        address: localhost
        port: 9001
      tcpsvr:
        port: 9000
  rtcm3_messages:
    message_1004:
      enabled: false
      frequency: 1
    message_1006:
      enabled: true
      frequency: 0.10000000000000001
    message_1008:
      enabled: false
      frequency: 1
    message_1012:
      enabled: false
      frequency: 1
    message_1033:
      enabled: false
      frequency: 1
    message_1074:
      enabled: true
      frequency: 1
    message_1084:
      enabled: true
      frequency: 1
    message_1094:
      enabled: true
      frequency: 1
    message_1124:
      enabled: true
      frequency: 1
    message_1230:
      enabled: false
      frequency: 1
bluetooth:
  enabled: true
  pairing:
    discoverable: false
    pin: '***'
correction_input:
  base_corrections:
    io_type: ntripcli
    settings:
      bluetooth:
        send_position_to_base: false
      cloud:
        mount_point: ''
        send_position_to_base: true
      lora:
        air_rate: 18.23
        frequency: 927300
        output_power: 6
        send_position_to_base: false
      ntripcli:
        address: 20.185.11.35
        mount_point: VRS_RTCM3
        password: '***'
        port: 2101
        send_position_to_base: true
        username: bwolv
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        send_position_to_base: false
      tcpcli:
        address: localhost
        port: 10001
        send_position_to_base: false
      tcpsvr:
        port: 10000
        send_position_to_base: false
device:
  power_on_bottom_connector: false
  privacy_policy_accepted: true
  role: null
  usage_analysis_accepted: true
logging:
  logs:
    base:
      format: RTCM3
      started: false
    correction:
      format: RTCM3
      started: true
    raw:
      format: RINEX
      started: false
      version: '2.11'
    solution:
      format: LLH
      started: false
  settings:
    debug: false
    interval: 24
    overwrite: true
network:
  tcp_over_modem: false
position_output:
  output1:
    io_type: 'off'
    nmea_settings:
      bluetooth:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      serial:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpcli:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpsvr:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
    settings:
      bluetooth:
        format: NMEA
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        format: ERB
      tcpcli:
        address: localhost
        format: ERB
        port: 9000
      tcpsvr:
        format: LLH
        port: 9001
  output2:
    io_type: 'off'
    nmea_settings:
      bluetooth:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      serial:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpcli:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpsvr:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
    settings:
      bluetooth:
        format: NMEA
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        format: ERB
      tcpcli:
        address: localhost
        format: ERB
        port: 9000
      tcpsvr:
        format: LLH
        port: 9001
positioning_settings:
  elevation_mask_angle: 13
  glonass_ar_mode: false
  gnss_settings:
    positioning_systems:
      beidou: true
      galileo: true
      glonass: true
      gps: true
      qzss: true
    update_rate: 10
  gps_ar_mode: fix-and-hold
  max_horizontal_acceleration: 1
  max_vertical_acceleration: 1
  positioning_mode: kinematic
  snr_mask: 32
sound:
  mute: false
  volume: 40

Hi @bwolv,

Thanks for the report!

Could you please specify whether you noticed such behavior only after the update to v2.25.2?

It’d be also helpful if you could share the Full System Report. It contains the detailed logging of the processes happening on the device. So we’ll be able to see the full picture. As the report contains sensitive information, please, use the support@emlid.com or PM to share it.

Hi @bwolv,

Did you have a chance to generate the Full System Report on the unit?

2 posts were split to a new topic: Issues with enabling mobile data