Develop Bugs

Smartcard API in Nexus devices - SIM secure elements

Many European countries are now rolling out NFC payment services, and the vast majority of them use the SIM as the secure element. The openmobile API, which is incorporated into the stock ROMs of Sony, Samsung and HTC NFC-enabled devices, is what is commonly used to access the SIM secure element.
Unfortunately, Google wants Nexus users to only ever use Google Wallet for NFC payments - even though it's only available in America. They don't want you using your network's NFC payment applications. This is why they did not include SIM secure element support in native Android and this is part of the reason why they do not include MicroSD slots in Nexus devices. So, right now, the Galaxy Nexus and Nexus S can not use any third party NFC payment applications.
However, the API that Samsung, HTC and Sony use is easily available. You can find the official website here. Is there anyone with knowledge of applying patches to stock Android who could create a stock 4.1.1 build with the Smartcard API (for Jelly Bean) and OpenMobile API patches applied? I'd be happy to test.

Could you link me to the source where it states that there are Phones that use SEEK from stock? I can't seem to find those. I'm currently evaluating on going that road, too for a project, though I'm not yet too sure about it.

Damastus said:
Could you link me to the source where it states that there are Phones that use SEEK from stock? I can't seem to find those. I'm currently evaluating on going that road, too for a project, though I'm not yet too sure about it.
Click to expand...
Click to collapse
Scroll down to the 'commercial devices' section here.
If you do go down this route, I'd really appreciate if you made a 4.1 build for the GSM Nexus with the two patches applied. Though, saying that, I'm a bit worried that even if we get the patches into the OS, the Galaxy Nexus might lack the actual hardware needed to communicate with the SIM's secure element. This is why we need to test this ASAP, as a phone without support for SIM secure elements will be pretty much useless for NFC by next year.

LoveNFC said:
Though, saying that, I'm a bit worried that even if we get the patches into the OS, the Galaxy Nexus might lack the actual hardware needed to communicate with the SIM's secure element.
Click to expand...
Click to collapse
Both the Nexus S and the Galaxy Nexus support SWP and the NFC controller is connected to the SIM slot. So hardware support is there, and there are reports that using the UICC as the secure element works just fine with non-stock firmware (search the SEEK mailing list). This however depends on RIL support which is proprietary and the drivers are not public (yet).

[Q] Texas Instrument [TI], GNex & Kitkat

Guys I am non US, GNex Lover, So I want to know is is exact connecttion between TI with GNex Kitkat update?
Anyone?
FYI
There's still no official word on why this is the case, but sources close to the company have pointed the finger at a different hardware issue on the Galaxy Nexus: its Texas Instruments-built chipset. The company is out of the mobile business and as such isn't in a great position to give the support necessary for continuing OS upgrades -- presumably some of those 1,700 employees let go in the shift away from mobile could have helped. Now we'll have to see if the community can pick up where the corporations left off or if this is the end of the road for the Gnex and its other OMAP-based kin like last year's Kindle Fire HD, Nook HD and Droid Bionic.
Click to expand...
Click to collapse
http://www.engadget.com/2013/10/31/google-galaxy-nexus-kitkat/

hirenvasani said:
Guys I am non US, GNex Lover, So I want to know is is exact connecttion between TI with GNex Kitkat update?
Anyone?
FYI
http://www.engadget.com/2013/10/31/google-galaxy-nexus-kitkat/
Click to expand...
Click to collapse
Texas Instruments makes the CPU in the Gnex they no longer make mobile chips for phones and thus 4.4 driver updates are an issue.

cstrife999 said:
Texas Instruments makes the CPU in the Gnex they no longer make mobile chips for phones and thus 4.4 driver updates are an issue.
Click to expand...
Click to collapse
why cant google develop it?
and there may be few good community member who can develop, so what is the problem? Why google doing like this?
Any hope?

hirenvasani said:
why cant google develop it?
and there may be few good community member who can develop, so what is the problem? Why google doing like this?
Any hope?
Click to expand...
Click to collapse
Google doesn't make ti parts and probably has no clue how to. I'm sure devs here will get it done eventually.
Sent from my Galaxy Nexus using xda app-developers app

TI OMAP 4460 is closed-source, there's no documentation about that chip, makes the job really hard.

Money makes the world move, not economical to continue development on a 2 year old device for Google.
Beamed from my Maguro

Loureiro said:
TI OMAP 4460 is closed-source, there's no documentation about that chip, makes the job really hard.
Click to expand...
Click to collapse
With respect, that couldn't be further from the truth -- TI makes a ~6,000 page public Technical Reference Manual documenting the workings of most of the chip, and the kernel and publicly-available Android hardware enablement sources are in excellent shape. That's a lot more than can be said for any other SOC manufacturer.
That said, the difficulties encountered so far in running 4.4 on Galaxy Nexus can be traced back to the closed-source PowerVR GPU drivers -- and because TI's winding down its OMAP division and GPU maker Imagination Technology has moved on to its next-generation Series 6 designs, we're unlikely to get new ones. I suspect Google had the same problem getting new GPU drivers, and elected not to carry forward compatibility code in the base Android system to support the old ones.

Google doesn't seem to want to acknowledge it, but it seems like drivers are becoming the driving force behind stalled updates. It's gotten so bad it's affecting Google's own devices. This should not have been a surprise since anyone involved in Linux knows closed source drivers are always causing problems.
Their dropping support after "18 months" sets a dangerous president since the device was still their "new" phone less than a year ago. Heck Verizon was still selling it until very recently, and we still don't have 4.3.
It's actually discouraging me from getting the nexus 5.
Sent from my Galaxy Nexus using Tapatalk

T-Keith said:
Google doesn't seem to want to acknowledge it, but it seems like drivers are becoming the driving force behind stalled updates. It's gotten so bad it's affecting Google's own devices. This should not have been a surprise since anyone involved in Linux knows closed source drivers are always causing problems.
Their dropping support after "18 months" sets a dangerous president since the device was still their "new" phone less than a year ago. Heck Verizon was still selling it until very recently, and we still don't have 4.3.
It's actually discouraging me from getting the nexus 5.
Click to expand...
Click to collapse
That's a noble sentiment, but reality says that there isn't a single ARM SOC on the market right now that's not afflicted with closed-source driver blobs -- meaning there's quite literally nothing you can buy, or even design and build yourself, that would be an improvement on that front. (Down the road, there may be hope for Intel parts with documentation and fully open drivers, but even that's not a guarantee.)

steven676 said:
With respect, that couldn't be further from the truth -- TI makes a ~6,000 page public Technical Reference Manual documenting the workings of most of the chip, and the kernel and publicly-available Android hardware enablement sources are in excellent shape. That's a lot more than can be said for any other SOC manufacturer.
That said, the difficulties encountered so far in running 4.4 on Galaxy Nexus can be traced back to the closed-source PowerVR GPU drivers -- and because TI's winding down its OMAP division and GPU maker Imagination Technology has moved on to its next-generation Series 6 designs, we're unlikely to get new ones. I suspect Google had the same problem getting new GPU drivers, and elected not to carry forward compatibility code in the base Android system to support the old ones.
Click to expand...
Click to collapse
If there is no drivers, how custom rom is available, I saw 3 rom, out of one, one is exact copy of actual 4.4 but only for verizon.
If developers cam develop rom just day or 2? why Google Cant? And 18 months support policy is just bull****.

hirenvasani said:
If there is no drivers, how custom rom is available, I saw 3 rom, out of one, one is exact copy of actual 4.4 but only for verizon.
If developers cam develop rom just day or 2? why Google Cant? And 18 months support policy is just bull****.
Click to expand...
Click to collapse
You can develop a rom without the proper drivers however there'll be problems. Devs are trying to find a workaround for the GPU drivers but so far, no luck. Aside from that, looks like google tried to work on the GPU drivers but they gave up. Maybe there's nothing to do with the 18 months policy.

Google doesn't want to put money, people and rest of resources into 2 year old device. It never did and it never will. That's the only real reason. The TI **** was posted and reblogged so many times that it became ''truth''. What Google posted in their FAQ about being ''too old'' simply means it falls out of their device update timeline.
End of story.

https://www.youtube.com/watch?v=Gld4RcF0MKc

Sesme said:
https://www.youtube.com/watch?v=Gld4RcF0MKc
Click to expand...
Click to collapse
Rom's actually faster & eventually needs updates though, thanks for the video :good: !

Castro27 said:
You can develop a rom without the proper drivers however there'll be problems. Devs are trying to find a workaround for the GPU drivers but so far, no luck. Aside from that, looks like google tried to work on the GPU drivers but they gave up. Maybe there's nothing to do with the 18 months policy.
Click to expand...
Click to collapse
Well, i would not be so negative about that ! As I said on the other post, I've tried the two 4.4 roms in the Development forum. There is still some graphic glitches, but i'm with "A taste of KitKat" since yesterday, had only 1 random reboot at the beginning, deep sleep is amazing, etc. And it's like 48h since the Nexus5 is on sale !
I think since developper made something very usable after 48h, I believe they can workaround those GPU problems. I mean even if google backed down, you can't know who was working on the GPU back there ... it could have been an intern ! Here I know there is 2 guys that each made a 4.4 ROM usable in 48h that are working on it, so I believe

ericmas001 said:
Well, i would not be so negative about that ! As I said on the other post, I've tried the two 4.4 roms in the Development forum. There is still some graphic glitches, but i'm with "A taste of KitKat" since yesterday, had only 1 random reboot at the beginning, deep sleep is amazing, etc. And it's like 48h since the Nexus5 is on sale !
I think since developper made something very usable after 48h, I believe they can workaround those GPU problems. I mean even if google backed down, you can't know who was working on the GPU back there ... it could have been an intern ! Here I know there is 2 guys that each made a 4.4 ROM usable in 48h that are working on it, so I believe
Click to expand...
Click to collapse
What you don't understand is that it is very difficult to make a build without the software to match the hardware. This same issue happened with my motorola Photon 4G. We were promised ICS on our phones, however motorola took back that promise and we were left in the dust. Enter the wonderful devs in that community. They quickly pounced on the ICS builds and developed one for our devices, but there was an issue... the drivers were outdated and the kernel would not play nice with the old drivers. It was tegra 2, and NVIDIA had stopped supporting that chipset, so what did we get? A build of ICS using the old GB kernel, with constant display and performance issues. That is what will happen with this device.

hirenvasani said:
If there is no drivers, how custom rom is available, I saw 3 rom, out of one, one is exact copy of actual 4.4 but only for verizon.
If developers cam develop rom just day or 2? why Google Cant? And 18 months support policy is just bull****.
Click to expand...
Click to collapse
ericmas001 said:
Well, i would not be so negative about that ! As I said on the other post, I've tried the two 4.4 roms in the Development forum. There is still some graphic glitches, but i'm with "A taste of KitKat" since yesterday, had only 1 random reboot at the beginning, deep sleep is amazing, etc. And it's like 48h since the Nexus5 is on sale !
I think since developper made something very usable after 48h, I believe they can workaround those GPU problems. I mean even if google backed down, you can't know who was working on the GPU back there ... it could have been an intern ! Here I know there is 2 guys that each made a 4.4 ROM usable in 48h that are working on it, so I believe
Click to expand...
Click to collapse
One way to describe this for the simple/non-dev users is the current 4.4 builds you are trying a "new package, with old contents". Or you got a new car but it still has the old engine.
Until the OMAP issues are resolved we are sitting around twiddling thumbs. Which it seems google did when it had no luck in accomplishing and therefore decided to default on their non-fragmentation theology - it's easier to EOL or end support for the device.
I just wish that google would have told us earlier about this rather than wait until release. A simple PR statement months ago when KK/KLP was in development "We have issues getting Gnex/TI OMAP compatibility" would have saved itself from the onslaught of complaints it is getting now.

Why google did not make Android 4.4 backward driver compatible as an option?

TI don't develop new kernel

This situation pushed me to unlock my phone and install custom ROMs. Now I know that i should done it earlier. No drivers for OMAP it's not a problem to developers and CM11 is running very smoothly. No update it's in my opinion only $$ issue.

NFC drivers TW vs CW*

So let me get this straight, we have a working TW NFC, but cant use Google wallet because of no Emulator in the current kitkat version? How is it that when i had the LG Flex i could use google wallet without any issues and it was on 4.2 for the longest. I assume that all KITKAT versions had this feature, and only reason why CW is not working because of drivers for our chipsets. So if TW has the drivers already, how is this preventing to be introduce in the CW version of android that has the Emulation built in it? If sprint has it, how is that not ported over as well if they have the same chipset? Please dumb this down, if you can to make it easier for all of us to understand. I try to use softcard, but get denied because im rooted. Bypass?

Xposed and the rootcloak module will get softcard to work.
As I understand it, our NFC chip is not used in any other device right now that does support Google wallet. Because of that, we can't port it from another device, there's nothing to port it from. It's not built in to the main chip like many other functions. It's a separate chip that we don't have open source drivers for. Or really any complete drivers that will work for GW. AOSP ROMs can't get any NFC at all because of driver issues.
The carriers are really pushing Softcard, so even a newer version of Android might not support it on our devices. If that is a big deal for you, you need to buy a device that can do it out of the box. There are no guarantees that we will ever be able to use Google wallet payments. Having used Google wallet and softcard, I don't see the point other than as a novelty. Not enough places support it, and some have problems with it. So it might not work even if the store has the equipment. So I have to keep another payment option available anyway. And there's the need to carry ID..

ttabbal said:
Xposed and the rootcloak module will get softcard to work.
As I understand it, our NFC chip is not used in any other device right now that does support Google wallet. Because of that, we can't port it from another device, there's nothing to port it from. It's not built in to the main chip like many other functions. It's a separate chip that we don't have open source drivers for. Or really any complete drivers that will work for GW. AOSP ROMs can't get any NFC at all because of driver issues.
The carriers are really pushing Softcard, so even a newer version of Android might not support it on our devices. If that is a big deal for you, you need to buy a device that can do it out of the box. There are no guarantees that we will ever be able to use Google wallet payments. Having used Google wallet and softcard, I don't see the point other than as a novelty. Not enough places support it, and some have problems with it. So it might not work even if the store has the equipment. So I have to keep another payment option available anyway. And there's the need to carry ID..
Click to expand...
Click to collapse
ok thanks, i assume that other notes had the same chip. So the question is why did tmobile request another chip, when the other models are working just fine with another version. Was this requested, or just random chip they wanted to introduce. I cant use softcard because i dont have those cards they use, and i refuse to get them. If it has a standard mastercard or visa, than i would..

We don't know why the other NFC chip was chosen. Only Samsung and T-Mobile know for sure. The engineers could have just found it easier to layout the board with it. Unless an official statement is made, which probably won't happen, we'll never know.
The card is just a placeholder. It's not any different than a paypal account. You put money in from normal Visa or MC. If you don't want to, that's your choice. Just making sure you know what it is. Some people were thinking it was a normal AMEX credit account.
Even though I don't have any real desire to use either app, I find it annoying that users can't choose the one that works best for them. That should never be an issue.

yea that is why I love GW, u can add any CC to it, no need to buy another card to xfer money to it over and over when u need to use it.

Best options to degoogle G980F?

Hello all! I have a galaxy s20 g980f stock with oneui 4 beta 1. What are my options to get rid of as much as possible bloatware, de-google, de-samsung etc.? im aware of adb debloating, but it has certain lmitations like knox. so what else? Custom rom? Which one is most debloated and 100% functional?

and1ronik said:
Hello all! I have a galaxy s20 g980f stock with oneui 4 beta 1. What are my options to get rid of as much as possible bloatware, de-google, de-samsung etc.? im aware of adb debloating, but it has certain lmitations like knox. so what else? Custom rom? Which one is most debloated and 100% functional?
Click to expand...
Click to collapse
De-bloating is subjective: one man's bloat is another man's treasure. Moreover, aggressive debloating tends to result in broken functionality and it is time consuming to track down the removed package that causes a failure.
Custom ROMs vary greatly in objectives and quality. At the end of the day, the only way you will get exactly what you want is to roll your own.

sjevtic said:
De-bloating is subjective: one man's bloat is another man's treasure. Moreover, aggressive debloating tends to result in broken functionality and it is time consuming to track down the removed package that causes a failure.
Custom ROMs vary greatly in objectives and quality. At the end of the day, the only way you will get exactly what you want is to roll your own.
Click to expand...
Click to collapse
Well, I cant agree here. I assume there is a common meaning for debloating - getting rid of all preinstalled software that has spying and advertising functions, and replacing it with analog functional software without spying and advertising parts. For example i uninstalled samsung keyboard and replaced with one of foss options.
Now the main and only problem I got is that i was not able to find official detailed explanation of each stock package - over 400 of them. Do you now where this can be found?

and1ronik said:
Well, I cant agree here. I assume there is a common meaning for debloating - getting rid of all preinstalled software that has spying and advertising functions, and replacing it with analog functional software without spying and advertising parts. For example i uninstalled samsung keyboard and replaced with one of foss options.
Now the main and only problem I got is that i was not able to find official detailed explanation of each stock package - over 400 of them. Do you now where this can be found?
Click to expand...
Click to collapse
This is exactly my point. I actually like the Samsung Keyboard. That said, if you *really" want every last piece of invasive software off, you will likely be better served with LineageOS or some other close descendant of AOSP. For what it's worth, one of the most invasive pieces of software on just about any stock device is Google Play Services. However, without it, most of the Google apps won't work, and plenty of other apps downloaded from the Play Store will have issues too.
The closest I've seen to a list of stock packages I've seen is this: https://docs.samsungknox.com/CCMode/G980F_R.pdf. It doesn't provide descriptions though.
As you encounter .apk files in the firmware package, here's an easy way to determine the package name from the occasionally less than informative file name:
Bash:
aapt dump badging file.apk | grep -Po "^package: \Kname=\'\S+?\'"
Attached is the list of bloat specs I used when building my image for the G986B culled from a variety of sources. It should serve as a useful starting point.

Try florisboard from f-droid, i personally found it perfect. But off course I understand your point, it is common too. I go radical, i deleted google play, framework and all google apps, i simply do not use any soft that requires google, for me its an affordable price for privacy and freedom.
By the way for debloating I am using AppManager from Muntashirakon, in ADB mode. I see the packages there, but no description, so yeah its a hit or miss. But there is an option to disable, then you see what happens and if problems you enable it back. Pretty decent, but not perfect. I wish I could root at least, but i guess need to wait for full A12 firmware and a matching TWRP recovery. Currently device is running on A12 Oneui 4 beta1.
Thanks a lot, I was going to ask you for this, where to start putting together own rom!!
Wondering, why are Calyx and Graphene roms not getting much attention here on XDA? And linux phones deserve some, even though they're technically not XDA..
The g980f in subject I just happen to have, if i would have to buy a phone now I wouldn't consider Samsung at all for the restrictions. Few months ago I disabled Samsung Pay Services - phone got locked irreversibly. I called Samsung and only option they offered is hard reset. Lost some sweet stuff with it and will never go Samsung again.

and1ronik said:
Try florisboard from f-droid, i personally found it perfect. But off course I understand your point, it is common too. I go radical, i deleted google play, framework and all google apps, i simply do not use any soft that requires google, for me its an affordable price for privacy and freedom.
Click to expand...
Click to collapse
That keyboard actually looks pretty good. That said, I don't have the patience to fully cut Google/Samsung out of my life.
and1ronik said:
By the way for debloating I am using AppManager from Muntashirakon, in ADB mode. I see the packages there, but no description, so yeah its a hit or miss. But there is an option to disable, then you see what happens and if problems you enable it back. Pretty decent, but not perfect. I wish I could root at least, but i guess need to wait for full A12 firmware and a matching TWRP recovery. Currently device is running on A12 Oneui 4 beta1.
Click to expand...
Click to collapse
I don't know that you need an Android 12-based TWRP, but you definitely need a compatible version of Magisk. Modding is generally a lot harder when you're on the bleeding edge, and is further complicated by the fact that you can't roll back the bootloader; you'll never find me on the latest build. It looks like there is a Android-12 compatible Magisk Canary build but I haven't tried it yet.
and1ronik said:
Wondering, why are Calyx and Graphene roms not getting much attention here on XDA? And linux phones deserve some, even though they're technically not XDA..
Click to expand...
Click to collapse
Because the Android phone market is too fragmented. Any custom ROM is available for at most a handful of the hundreds of actively marketed devices in the Android ecosystem.
Of course the bigger question is why we even need the abomination of an OS that is Android. In short, we don't: Sharp was already selling its Zaurus line of Linux PDAs 20 years ago. Google, however, decided it needed to insert itself into the mobile market, and the rest is history.
and1ronik said:
The g980f in subject I just happen to have, if i would have to buy a phone now I wouldn't consider Samsung at all for the restrictions. Few months ago I disabled Samsung Pay Services - phone got locked irreversibly. I called Samsung and only option they offered is hard reset. Lost some sweet stuff with it and will never go Samsung again.
Click to expand...
Click to collapse
Samsung's "security" practices are obnoxious, though at least in the US, the carriers share plenty of blame for phones being locked down. That said, I have yet to find to find hardware that is more compelling--the lack of a SD card slot is a deal breaker.

By the way i am on beta oneui 4, and i'm not going to update to full A 12 yet, so I keep an option to go back to 11 anytime, and there I can go custom rom or root at least.
And the lack of sd card in pixels is the only thing holding me from switching too.. but very little, im actually going to get a pixel 5 as parallel to the s20. Lack of SD card can be partiality cured by cloud storage. I guess its less inconvenience comparing to struggling with samsung's bs..
From what i see online, pixels have widest rom options, Calyx, Graphene, e/OS, so I can experiment and see what works best for me.

Question 5G in an unlisted country.

Had anyone figured a way to do this? i searched throughout all the internet about this.. and yet to find a solution.
I don't live in a country that Google sells the GP6P and(from my understanding) they'll lock it, NR availability will be set to False. Now i'm on a rooted GP6P and tried some modules(old mostly), none of them worked -- my ISP definitely supports 5G -- , if there is a module to enable it please upload it.
And whilst at that.. a way to get call screening enabled aswell...

No one figured out yet or simply don't want to.. For now we only have VoLTE by changing some build.prop parameters with Magisk module.
I was wondering... @Freak07 you seem to be a cool dude who eagerly supports the Pixel 6, maybe you would have any idea about it?
My carrier (Orange Poland) uses same 5G band and frequency as officially supported one (Magenta Austria) and I can't use 5G anyway..
On Pixel 5 it was simple because of QPST tool, with Tensor we are doomed
Another idea is to simply create a bounty, money would quickly improve the success

+1 for the bounty.
I am done waiting for my carrier to play nice with Google. My problem is that I also totally dislike Samsung, Oneplus etc.
We need to get this organised asap, I am sure there are plenty developers here on XDA willing to take that bounty.
Maybe we can use a platform like bountysource.com ?

mightyvenom said:
Maybe we can use a platform like bountysource.com ?
Click to expand...
Click to collapse
GoFundMe would be better, because you can't collect $ from people on the site you mentioned. Actually as someone who is on XDA since 2010 and already organized one bounty...maybe I'd be someone trustworthy enough to organise it

reas0n said:
GoFundMe would be better, because you can't collect $ from people on the site you mentioned. Actually as someone who is on XDA since 2010 and already organized one bounty...maybe I'd be someone trustworthy enough to organise it
Click to expand...
Click to collapse
Oh yeah, I totally forgot about gofundme, sorry!
Feel free to organize this, hopefully we can get enough people onboard to make for a tempting bounty.

I'm in too. (Vodafone Czech Republic)

I will try to work on it this weekend
Gonna use GiveButter since GoFundMe isn't supported in Poland.. GiveButter works worldwide in theory

I can provide any data from P6 latest Android 13DP2 (DP3 should be soon)

Oh I am in for middle east UAE Pixel fans

The Pixel 6 (non pro) community made a module for that purpose, I don't know if that one works for the P6 Pro, I'd advise not to use it, but you could ask the creator of the mod (github page is linked in that thread) if he is able to help you guys.
Activating 5G in unsupported countries?
I know this might require root, which I am more than willing to do. But is there a process or a magisk module that can activate 5G on unsupported countries? (btw im from PH)
forum.xda-developers.com
I remember that there was a relatively easy fix for the p4(a) and p5 to activate 5G in unsupported countries, even though I'm not sure if that still applies to the P6 Pro. Root required for both methods.
You could try these steps out (make backups!!!), but be warned that it might brick certain things.
https://www.getdroidtips.com/enable-5g-unlisted-countries-pixel-4a5g-pixel-5/

Morgrain said:
The Pixel 6 (non pro) community made a module for that purpose, I don't know if that one works for the P6 Pro, I'd advise not to use it, but you could ask the creator of the mod (github page is linked in that thread) if he is able to help you guys.
Activating 5G in unsupported countries?
I know this might require root, which I am more than willing to do. But is there a process or a magisk module that can activate 5G on unsupported countries? (btw im from PH)
forum.xda-developers.com
I remember that there was a relatively easy fix for the p4(a) and p5 to activate 5G in unsupported countries, even though I'm not sure if that still applies to the P6 Pro. Root required for both methods.
You could try these steps out (make backups!!!), but be warned that it might brick certain things.
https://www.getdroidtips.com/enable-5g-unlisted-countries-pixel-4a5g-pixel-5/
Click to expand...
Click to collapse
The pixel 6 lineup isn't on a Qualcomm chipset, Google has made their own chip called Tensor. Now the difference is that in Qualcomm's way they give you developer tools such as the Qualcomm Product Support Tools (QPST) which makes the Chip unlock its 5G capability, easy. Now in Googles Tensor's case we don't have access to these type of tools, and the Chip itself can lock the 5G modem.

TheShinyEnd said:
The pixel 6 lineup isn't on a Qualcomm chipset, Google has made their own chip called Tensor. Now the difference is that in Qualcomm's way they give you developer tools such as the Qualcomm Product Support Tools (QPST) which makes the Chip unlock its 5G capability, easy. Now in Googles Tensor's case we don't have access to these type of tools, and the Chip itself can lock the 5G modem.
Click to expand...
Click to collapse
That eliminates the second method with the file editing, but the first method was successful for the Pixel 6 non Pro, so that should be a possibility for you guys here, even though that Magisk mod might have to be adjusted slightly.

Morgrain said:
That eliminates the second method with the file editing, but the first method was successful for the Pixel 6 non Pro, so that should be a possibility for you guys here, even though that Magisk mod might have to be adjusted slightly.
Click to expand...
Click to collapse
If so I'll give it a ago in a little bit..
- I have the Pro version.

Do not flash that file. It's for Qualcomm chips and you're basically flashing Qualcomm directories onto your phone.
I don't know how anyone can say it was successful.
5G and other 5G features are controlled by the carrier settings. And that's not easy to manipulate.
Don't ever approach this phone with a "well this module works for 4/4a/5/5a" mentality.

+1 don't do it, Tensor is Exynos based, QPST only worked on previous Pixels

Getting lucky with the relatively simple flags to enable VoLTE by flashing tons of other crap onto your phone is not a validation.

Okay I won't do it. And yeah that's what I thought.
Just that the fact that it worked on the non pro model caught my attention.

I've given up on 5G now even though my network supports it Google have said they wont certify the device, certainly won't be getting another Google phone after this

I'm still confused as to why people imported this device when carrier support was clear from day one.
I don't think it's right that an OEM controls that, but that's the reality we're dealing with.

LLStarks said:
I'm still confused as to why people imported this device when carrier support was clear from day one.
Click to expand...
Click to collapse
I think I know why, I will give my best shot:
Many prefer using Pixel phones as they offer the closest experience to iPhone (regularly OS updates for years to come, clean OS without unnecessary bloatware and clutter etc.) and they are willing to accept the current state of not having full connectivity support with a hope that things might change in the (near) future.
It's not like the first time a phone manufacturer aknowledges customer feedback. Call me overly optimistic but I think they will eventually cave in, at least for unlocking VoLTE and VoWiFi. Because more and more countries are shutting down the 3G cell towers.
As for unlocking 5G support - from my understanding that would be more complicated as that's subject to each country's policy and legislation.