CarrierConfig vendor.xml for Pixel 2 (XL)

[thestinger]

No description provided.

[thestinger]

It seems they might have stopped using this and moved to the protobuf files, without code in AOSP to handle them.

[thestinger]

It seems they might have stopped using this and moved to the protobuf files, without code in AOSP to handle them.

[xbtc-im]

What's this with the CarrierConfig anyway ? Wasn't the SIM card supposed to handle all that ?

[xbtc-im]

What's this with the CarrierConfig anyway ? Wasn't the SIM card supposed to handle all that ?

[thestinger]

Well, it doesn't, there's a massive database of default APNs and the right one is picked based on ids from the SIM card. If there isn't an entry, you need to manually enter an APN for working SMS/MMS and data. This CarrierConfig stuff is needed for some things outside the scope of APN configuration.

[thestinger]

Well, it doesn't, there's a massive database of default APNs and the right one is picked based on ids from the SIM card. If there isn't an entry, you need to manually enter an APN for working SMS/MMS and data. This CarrierConfig stuff is needed for some things outside the scope of APN configuration.

[xbtc-im]

Yes, but besides the APN-s there are other issues ? For me there is no issue manually editing the APN settings for the internet, those can easily be looked up anyway ... And does anyone still use MMS ? :)

[xbtc-im]

Yes, but besides the APN-s there are other issues ? For me there is no issue manually editing the APN settings for the internet, those can easily be looked up anyway ... And does anyone still use MMS ? :)

[thestinger]

Yes, there are other issues, but it mostly works fine with just the standard APN database otherwise we wouldn't have launched Pixel 2 (XL) support. We only do this on the Pixel and Pixel XL, never did it on the Nexus 5X and 6P.

[thestinger]

Yes, there are other issues, but it mostly works fine with just the standard APN database otherwise we wouldn't have launched Pixel 2 (XL) support. We only do this on the Pixel and Pixel XL, never did it on the Nexus 5X and 6P.

[thestinger]

https://github.com/CopperheadOS/device_google_marlin/blob/oreo-m2-release/overlay/packages/apps/CarrierConfig/res/xml/vendor.xml

[thestinger]

https://github.com/CopperheadOS/device_google_marlin/blob/oreo-m2-release/overlay/packages/apps/CarrierConfig/res/xml/vendor.xml

[xbtc-im]

As an edit for my previous post: As i see it, MMS is an useless feature, that only adds unnecessary attack surface to the *G standards... It should totally be removed.
So without the CarrierConfig, the phone will not be useless, you just need to do a bit of work when you swap sim cards ?

[xbtc-im]

As an edit for my previous post: As i see it, MMS is an useless feature, that only adds unnecessary attack surface to the *G standards... It should totally be removed.
So without the CarrierConfig, the phone will not be useless, you just need to do a bit of work when you swap sim cards ?

[thestinger]

No, that's not what I said at all.

[thestinger]

No, that's not what I said at all.

[thestinger]

Well, it doesn't, there's a massive database of default APNs and the right one is picked based on ids from the SIM card. If there isn't an entry, you need to manually enter an APN for working SMS/MMS and data. This CarrierConfig stuff is needed for some things outside the scope of APN configuration.

[thestinger]

Well, it doesn't, there's a massive database of default APNs and the right one is picked based on ids from the SIM card. If there isn't an entry, you need to manually enter an APN for working SMS/MMS and data. This CarrierConfig stuff is needed for some things outside the scope of APN configuration.

[thestinger]

outside the scope of APN configuration.

i.e. nothing to do with basic mobile data and MMS

[thestinger]

outside the scope of APN configuration.

i.e. nothing to do with basic mobile data and MMS

[xbtc-im]

Yes, sorry about that. There are a lot of other settings too ... Missed that.

[xbtc-im]

Yes, sorry about that. There are a lot of other settings too ... Missed that.

[thestinger]

Look at what's in the one we ship for the Pixel / Pixel XL.

[thestinger]

Look at what's in the one we ship for the Pixel / Pixel XL.

[xbtc-im]

Off topic, i wonder what the software in the radio partition is capable of ... AFAIK that's a RTOS handling all the network/radio stuff, i wonder how much access does it have to the main memory / cpu.

[xbtc-im]

Off topic, i wonder what the software in the radio partition is capable of ... AFAIK that's a RTOS handling all the network/radio stuff, i wonder how much access does it have to the main memory / cpu.

[thestinger]

Components like the cellular radio, GPU, media decode/encode engine, etc. are contained by IOMMUs.

[thestinger]

Components like the cellular radio, GPU, media decode/encode engine, etc. are contained by IOMMUs.

[thestinger]

PCIe peripherals may or may not be contained well. You would need to do research more specific to devices. Most of these kinds of components are part of the SoC and the IOMMU configuration is reused across all the devices using the SoC unless they do something very strange.

There's a higher chance of a component separate from the SoC not being properly isolated. A component being on the SoC or having access to memory doesn't mean it isn't contained and likewise a component not being on the SoC doesn't mean it is contained.

[thestinger]

PCIe peripherals may or may not be contained well. You would need to do research more specific to devices. Most of these kinds of components are part of the SoC and the IOMMU configuration is reused across all the devices using the SoC unless they do something very strange.

There's a higher chance of a component separate from the SoC not being properly isolated. A component being on the SoC or having access to memory doesn't mean it isn't contained and likewise a component not being on the SoC doesn't mean it is contained.

[xbtc-im]

Thanks for the clarification

[xbtc-im]

Thanks for the clarification