Applying support for CarrierConfig overriding

wizoatk

FM-World So isnthese configurations are same as google stock firmware?

They are the same as AOSP. I don't know if Pixel stock varies from this.

https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/CarrierConfig/assets/

In any case, I've changed "carrier_nr_availabilities_int_array" directly with adb shell cmd phone cc set-value and that didn't have any affect for the one provider that I can test with. So I don't think that's the problem/solution.

Freek

@"wizoatk" hi iam new here , iam looking for this back-up calling option from long back and now iam back on this intresting feature.
The back-up calling is working in any custom ROM now ? If some one confirm or is there any work around, i will give a try. And thanks for the info.
Sorry if iam missing something.
By the way is there a way to incorporate or write our own features in GOS , as i see custom ROM's having VPN sharing option , so like that is there any possibility to bypass roaming SIM .

FM-World

wizoatk I DIDNOT FIND ANY FILE FOR PAKISTANI CARRIERS LIKE ZONG, JAZZ AND UFONE , ANY HELP REGARDING THIS?

FM-World

wizoatk I THIS THIS CODE ENABLES 5G IN UNSUPPORTED COUNTRIES CAN U TRY THIS?

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<carrier_config>
<string name="5g_icon_configuration_string">connected_mmwave:5G_Plus,connected:5G,not_restricted_rrc_idle:5G,not_restricted_rrc_con:5G</string>
<string name="5g_icon_display_grace_period_string">connected_mmwave,connected,30;connected_mmwave,not_restricted_rrc_idle,30;connected_mmwave,not_restricted_rrc_con,30</string>
<int-array name="additional_nr_advanced_bands_int_array" num="1">
<item value="78"/>
</int-array>
<int name="nr_advanced_threshold_bandwidth_khz_int" value="60000"/>
<boolean name="enable_nr_advanced_for_roaming_bool" value="true"/>
<boolean name="include_lte_for_nr_advanced_threshold_bandwidth_bool" value="true"/>
</carrier_config>

https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/CarrierConfig/assets/carrier_config_carrierid_2089_Public-Mobile.xml

Developer-Dude

FM-World theres a button on your keyboard that let's you disable all caps, btw.

wizoatk

FM-World

Your caps lock key appears stuck ...

OK, I'll bite. Specifically, why do you think this works?

FM-World

wizoatk i dont know but i want a solution please help

wizoatk

Hmmm. A puzzle within a puzzle ...

Johnnyloans

FM-World

None of us here know how to fix it :[

FM-World

why?

Johnnyloans

FM-World

We are like you.

Developer-Dude

FM-World geez, we ain't all know it all geniuses here. Some things people don't know the answer to. Maybe someone will have an answer. Hope you get this resolved

Rendimento

@wizoatk

you asked for a proper description of how/where to change carrier policy that is still valid for Android 16; here is community research on exactly that:

The carrier profile database at vendor/firmware/carrierconfig/cfg.db (SQLite) controls EN-DC per carrier. For PLMNs without an entry, the modem falls back to the wildcard / regional_fallback profile, which does not enable EN-DC — so 5G NSA never attaches, regardless of the OS-level force toggles. Editing the regional_fallback carrier_id has been confirmed to enable 5G on custom builds: #27610

Current concrete test case: MTEL Switzerland (MVNO on Salt's network, PLMN 228/69) on Pixel 10 Pro, GrapheneOS 17. The testing menu shows NR Available (NSA): true, EN-DC Available (NSA): false, DCNR Restricted (NSA): false, registration state HOME — nothing restricts NR, but EN-DC is not enabled. The same SIM gets 5G on an Oppo Realme 8 at the same locations. Details and screenshots: https://github.com/GrapheneOS/os-issue-tracker/issues/8904

Happy to provide logs or test any change. @

wizoatk

Rendimento

FYI. More recently GrapheneOS has chosen to patch cfg.db with adevtool.

https://github.com/search?q=org%3AGrapheneOS+cfg.db&type=pullrequests

precise-deliciousness

Rendimento Salt's

Found this site from someone sharing it in the GrapheneOS Matrix chat rooms recently, could this be what you might be looking for?https://carrierexplode.com/android/carriers/salt_ch/blazer/79000000004/modem

Rendimento

@wizoatk @precise-deliciousness

Thanks for sharing this!
Im pretty new to all this stuff so im still trying to understand how the modem configs works. I choose mtel because it was a really good deal, and I was happy thinking I could get 5G+ on my Pixel 10 Pro. I honestly didnt expect that I might not get 5G+ when I went with mtel 😅

I noticed that the mtel page for blazer shows no modem config, but Salt has a ch_salt profile (carrier ID 1414, MCC-MNC 22803) with NR settings.

Since GrapheneOS recently made changes to cfg.db in adevtool, I was wondering if something similar could be done for mtel (PLMN 22869)? Or does mtel need its own modem profile and the Salt one wouldnt work?

I dont really know enough about this to say if the missing config is the reason why im not getting 5G+, just thought id ask here in case someone who knows more can help me understand whats going on. Would be really nice if I could get 5G+ working 😅

Thanks for any help!

Rendimento

precise-deliciousness still thanks for the help do you know who might know how to fix it?

precise-deliciousness

Rendimento still thanks for the help do you know who might know how to fix it?

Sorry, I don't know. Have you considered maybe joining the community chat rooms and asking there? https://grapheneos.org/contact#community-chat

« Previous Page