CHOICE Additions not supported yet

[elixx]

The install process didn't work as expected -- I was able to write one of the init files to /etc/init.d but not the other, which is very strange. Appears to be unrelated issues with rooting the device.
Despite that, I got it running manually and am able to retrieve PCAPs from the application, which is really cool!

However all of the entries output from the web interface read like:

      "DecodingError(UperDecodeError(Error { cause: EncodeNotSupported, msg: \"CHOICE Additions not supported yet.\", context: [] }))"

Is this due to the configuration of my area's cell network, or something else?

[elixx]

I traced the error back to https://github.com/ystero-dev/hampi/blob/1c310f580fe3a48dc70006de79d98752058968b0/codecs_derive/src/per/choice.rs#L70

Still figuring out the relevance...

[elixx]

This is with an invalid Verizon SIM card that shipped in it (eBay auction), but the device didn't indicate it was invalid, just stuck at 'Retrieving data usage info". I just swapped in an old defunct SIM and get a "NO SERVICE" message as well, now, and I'm no longer getting the CHOICE message, but no pcap data, either.
I'm going to try a few other SIMs and see what happens.

[elixx]

I just swapped in a working FreedomPop SIM from a working handset, but still get the NO SERVICE message (probably because I did not register the SIM to the new device's IMEI, which I believe the carrier requires).
I'm now getting PCAP data, again, but see different errors logged from the application, now, and not as frequent:

    "timestamp": "2025-03-14T12:54:49.181110077-04:00",
    "skipped_message_reasons": [
      "DecodingError(UperDecodeError(Error { cause: BufferTooShort, msg: \"PerCodec:DecodeError:Requested Bits to decode 9, Remaining bits 4\", context: [] }))"
    ],
    "analysis": []
  },
  {
    "timestamp": "2025-03-14T12:54:51.110519764-04:00",
    "skipped_message_reasons": [
      "DecodingError(UperDecodeError(Error { cause: BufferTooShort, msg: \"PerCodec:DecodeError:Requested Bits to decode 3, Remaining bits 1\", context: [] }))"
    ],
    "analysis": []
  },
  {
    "timestamp": "2025-03-14T12:54:55.398137262-04:00",
    "skipped_message_reasons": [
      "DecodingError(UperDecodeError(Error { cause: BufferTooShort, msg: \"PerCodec:DecodeError:Requested Bits to decode 3, Remaining bits 1\", context: [] }))"
    ],
    "analysis": []
  },
  {
    "timestamp": "2025-03-14T12:58:31.100808586-04:00",
    "skipped_message_reasons": [
      "DecodingError(UperDecodeError(Error { cause: BufferTooShort, msg: \"PerCodec:GetBitError:Requested Bit 6, Remaining bits 0\", context: [] }))"
    ],
    "analysis": []
  },
  {
    "timestamp": "2025-03-14T12:58:38.118713115-04:00",
    "skipped_message_reasons": [
      "DecodingError(UperDecodeError(Error { cause: BufferTooShort, msg: \"PerCodec:DecodeError:Requested Bits to decode 3, Remaining bits 1\", context: [] }))"
    ],

[wgreenberg]

oh wow, i haven't seen the CHOICE issue before. what's happening is our telcom-parser is encountering messages not described in the RRC specs we've provided. without seeing the QMDL files, it's hard to say what types of messages they are.

the errors from your FreedomPop SIM look like ones mentioned here #139, which is a similar issue

[cooperq]

I've seen the choice addons issue before but I can't remember where.

[elixx]

I can try swapping the verizon SIM back in to hopefully reproduce the CHOICE messages, and collect some dumps for analysis later this week.