Develop Bugs

Really interesting problem...

So I thought that maybe some of you guys that know more about the inner workings of our phones may be able to help. First, let me preface by saying that I have Ricky's V24 installed along with SmartToolKit, Ringu Iconbar, NRG's MiniWeather. I have other stuff installed, but nothing that I think could be the cause of this "problem".
I've zipped two screen captures for you guys to take a look at. Anyway, in the first shot of the "Clock & Alarm" screen, note that instead of the typical 5 entries, there's now a sixth one that is just a repeat of the 3rd (Alarm 2).
In the second screenshot of the "Home Screen" settings the list of options repeats itself a second time...and it's very odd, but it's independent. For example, I can uncheck one of the options to display recent programs, but the other one doesn't automatically uncheck.
I didn't have this problem until recently... basically, I ran an Autoclean with SKTools and my phone stopped booting. I ended up having to do a hard reset using the two softbuttons, then using a self-executable Sprite backup I fortunately had. Also note, that I tried another hard reset and verified that these problems don't appear until I run the restore.
Anyone know what file(s) got screwed up and how to fix this?

Also, here is what clckalrm.cpl.xml looks like:
- <stinger-controlpanel-doc>
<cpl-title res="30067" />
<cpl-link href="clock.cpl.xml" res="30010" />
<cpl-link href="alarm.cpl.xml" res="30069" />
<cpl-link href="alarm2.cpl.xml" res="30079" />
- <cpl-link clsid="{77B5B15A-C23F-497e-BB98-B22796130069}">
<title lang="0x0409">All Alarms</title>
</cpl-link>
<cpl-link clsid="{CCD5194B-08E6-472E-8F3A-73770108489D}" />
</stinger-controlpanel-doc>
and home.cpl.xml:
- <stinger-controlpanel-doc>
<cpl-title res="30018" />
- <characteristic type="Home">
- <characteristic type="HKCU\ControlPanel\Home">
<parm-query name="Scheme" />
</characteristic>
- <characteristic type="HKCU\Software\Microsoft\Shell\StartMenu">
<parm-query name="RPL" />
</characteristic>
- <characteristic type="HKCU\ControlPanel\Home">
<parm-query name="ColorScheme" refresh="1" />
<parm-query name="BgImage" />
</characteristic>
</characteristic>
- <characteristic type="Registry">
- <characteristic type="HKCU\ControlPanel\Home">
<parm-query name="Timeout" />
</characteristic>
</characteristic>
</stinger-controlpanel-doc>
In the Home Screen setup, the "Timeout" option only appears once...

I have the EXACT same problem with mine. Also my alarm that is set for 7am will sound at random times but never at 7am. I am considering wiping everything and starting over with kavanas rom.

cmcgrail said:
I have the EXACT same problem with mine. Also my alarm that is set for 7am will sound at random times but never at 7am. I am considering wiping everything and starting over with kavanas rom.
Click to expand...
Click to collapse
Regards alarm: Clear your alarm notification with SKTools and stop using Windows default alarm use another program like pTravel alarm, it's an old Windows bug.
OP & Poster i would hard-reset thats not normal the Alarm dialog or the Homescreen mind you if doesn't effect the device then wouldn't worry so much.
I will have a look @ the .xml's in bit to see if any different.

stylez said:
Regards alarm: Clear your alarm notification with SKTools and stop using Windows default alarm use another program like pTravel alarm, it's an old Windows bug.
OP & Poster i would hard-reset thats not normal the Alarm dialog or the Homescreen mind you if doesn't effect the device then wouldn't worry so much.
I will have a look @ the .xml's in bit to see if any different.
Click to expand...
Click to collapse
Thanks Stylez! I actually did a hard reset again and compared the xml files... there's no difference at all in the coding. You're right though...it doesn't affect the device at all, because I don't ever change the homescreen options or play with the alarm much. Just thought it would be nice to figure out what was up. I'm still working on it myself and will be doing incremental restores using Sprite to see if I can narrow down what files are causing the issue.

uansari1 said:
Thanks Stylez! I actually did a hard reset again and compared the xml files... there's no difference at all in the coding. You're right though...it doesn't affect the device at all, because I don't ever change the homescreen options or play with the alarm much. Just thought it would be nice to figure out what was up. I'm still working on it myself and will be doing incremental restores using Sprite to see if I can narrow down what files are causing the issue.
Click to expand...
Click to collapse
That's cool bruv, would be good to know what bit of software does it? When you figured it out be sure to update post as it's interesting as never come across this issue before.
I had a night of hard-reset too, thank god on PPC we have SASHAMI installs everything for you, as my backup was up it too. Still got to tweak everything but saves alot of time.

TUTORIAL - modding lockscreen/framework-res.apk

*I made this before any of these new roms came out and as such it was meant for and has been tested on only the stock Gingerbread rom that comes with the phone. I doubt it will be compatible with the new roms.*
In response to a request, I am posting a tutorial on how to make a couple lockscreen mods.
You may want to read my other tutorials first
Swapping Out PNGs
Editing XML
*MY TYPICAL DISCLAIMER!*
I AM NOT A DEV! I just like tinkering with this phone because I'm overall an extremely picky and obsessive person. I have no prior android experience (besides a little tinkering with my X10), and I am in NO way an expert. But since I know how to mess with my phone a little bit and I've been asked to share, I will =) But follow these instructions at your own risk! I am not responsible for the untimely death of your phone, so please be cautious and careful, and if you have any questions about any step, before you try it, ask me or someone who knows! I don't want the blood of your dead phone on my hands! =)
These instructions are for Windows computers. Sorry, I'm just not familiar with mac or linux. =(
**Messing with the lockscreen/framework-res.apk**
Since modding, to me, is about personalization, I’m going to let you pick and choose whatever particular things you like and leave out the things you don’t like. You can get rid of the carrier, but keep everything else, or just get rid of the dots and emergency button, but keep the carrier cause you just love AT&T so much! Whatever tickles your fancy. Unfortunately, with that flexibility comes a teency bit more work =) So I can’t make a framework-res.apk that you can just put with all the mods for a couple reasons:
1.) I don’t know which mods you want
2.) Any other modifications you’ve made to framework-res.apk before will be wiped out if you install one that I upload
So this way, with a tiny bit more work, you can not only pick and choose what you want, but keep the old changes to framework-res.apk you already love so very much.
So without further adieu, here’s what I did to the lockscreen:
I like using the pattern lockscreen for just the touch of security, but I hate how it looks. To me, it's wildly unnecessarily cluttered. So here's what I've done, before and after =)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't like AT&T plastered on it, the divider line is too harsh, the dots are just completely unnecessary to me (I can estimate a third along each axis, thanks =)), and the emergency call button (albeit practical) is ugly, and I'm shallow. So I changed all of them. The dots will still appear, but only after you press them so you can see that beautiful wallpaper of yours while your phone is locked. This included 4 modifications:
1. Removed carrier (edited XML)
2. Lightened divider to almost invisible (I like just a touch of it =)) (edited PNG)
3. Removed dots (edited PNG)
4. Removed emergency call button (edited XML)
Don't worry. The emergency call button (along with the "forgot pattern" button) still returns after you've failed to enter the correct pattern multiple times:
So let’s get started!
**What you’ll need**
1.) Root explorer from the market with root permissions! (I DO NOT suggest an alternative file explorer ESPECIALLY since this mod requires messing with framework-res.apk, the easiest way to brick your phone! And I know other file explorers like ES file explorer will brick your phone if you try to mess with framework-res.apk in this way!)
2.) 7zip or some kind of zip manager for your computer
**What to do**
1.) Using root explorer with root permissions, COPY (don’t MOVE!) framework-res.apk from your phone (in \system\framework\framework-res.apk) to your sd card, and then to your computer. Keep a copy safe somewhere else as a backup in case you want to revert back to your original framework-res.apk!
Decide what mods you want! Here’s the list again:
1. Removed carrier (edited XML)
2. Lightened divider to almost invisible (I like just a touch of it =)) (edited PNG)
3. Removed dots (edited PNG)
4. Removed emergency call button (edited XML)
If you want the invisible dots or the lightened divider, download the attached “PNGS- lockscreen.zip” from the end of this thread.
If you want either the removed carrier or the removed emergency call button, download the ONE XML you want! (If you only want to remove the carrier, only download “XML- no carrier.zip.” If you only want to remove the emergency button, only download “XML- no emergency call button.zip.” If you want both, download “XML- no carrier AND no emergency call button.zip.” You can only use ONE XML. If you try to use more than one, they will just overwrite each other since they’re just different modifications of the same XML file!)
2.) Unzip whichever zips you downloaded onto your computer
3.) Right click on your framework-res.apk from your phone, 7zip-> open archive (do not extract!)
4.) Drag and drop all the unzipped PNGS you downloaded (if any) into \res\drawable-xhdpi in framework-res.apk. Let them overwrite the originals in that folder.
5.) Drag and drop the unzipped XML you downloaded into \res\layout in framework-res.apk, and let it overwrite the original.
6.) Move your newly modified framework-res.apk back onto your sd card
7.) Copy it to \system\
8.) Using root explorer, change permissions for framework-res.apk to owner: read AND write, group: read, others: read! This step is CRITICAL!
9.) Move it into \system\framework and let it overwrite the original framework-res.apk!
10.) Restart your phone!
Upon startup, you should see your new changes! You can also edit the PNGs however you like, if you want to change the dots to something else, or want a big blue divider or whatever. =)
All the XML edits I did were as explained in my editing XML tutorial, but if anyone wants more details or what values in particular I modified, I’d be happy to go through them!
If you need help using root explorer to change permissions, etc, I have more details in my other tutorials listed at the top of this entry.
If you have ANY questions or need more details, before you do anything, PLEASE check my other tutorials or just ask! =)

Worked perfectly! Thanks, it looks so much better than before imo!

Thanks!! Glad you like! I agree, I like using the lock pattern, but I definitely prefer a more minimalist look =)

I like your style. If you got any more mods, don't hesitate to share with the rest of us! Lol.

Can this be used with CM7? I've done things like this already, including taking out the carrier name manually, etc. I used this one xml that you gave and it hosed the phone. Just curious whether or not that xml file is different. Caused a pretty bootloop.

I'm pretty sure this is only for stock roms.

Sounds good. But can you give me a quick rundown on what you edited in terms of the xml file? I can prob go in and do it myself, but I'm unfamiliar with which lines you edited (were the lines for carrier completed deleted? --><TextView android:textAppearance="?textAppearanceMedium" android:ellipsize="marquee" android:gravity="bottom|right|center" android:id="@id/carrier" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginTop="6.0dip" android:layout_marginRight="8.0dip" android:singleLine="true" android:layout_toRightOf="@id/time" android:layout_alignParentTop="true" android:layout_alignParentRight="true" />
^ That line simply removed or did you just remove "@id/carrier" <less the quotes>"
As well as the annoying emergency buttons (this will ensure my wife doesnt get a chance to save me and I can RIP ) - Was the line removed entirely or?
If I know these fine details I can probably wing this. I'll just have to keep my fingers crossed recompiling.
Thanks in advance (don't ya hate that)
ADG

Deleting lines usually made things crash and burn, so I just cheated and changed widths/sizes to 0
To remove carrier (lines 8 and 9), after:
android:id="@id/carrier", changed android:layout_height to "0.0dip"
android:id="@id/carrier_sub2", changed android:layout_height to "0.0dip"
To remove emergency buttons, in the section just above android:id="@id/emergencyCallAlone" (line 24) shown here:
<RelativeLayout android:id="@id/footerNormal" android:layout_width="fill_parent" android:layout_height="fill_parent">
<Button android:textSize="18.0sp" android:textStyle="bold" android:id="@id/emergencyCallAlone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/lockscreen_emergency_call" android:drawableLeft="@drawable/ic_emergency" android:drawablePadding="8.0dip" android:layout_centerInParent="true" style="@style/Widget.Button.Transparent" />
</RelativeLayout>
Changed the first android:layout_height to "0.0dip"
Hope it helps. And no, I don't hate thanks of any kind. =) You'd be surprised how many just demand

I see (in the xml I downloaded):
android:layout_width="0.0dip" android:layout_height="fill_parent"
for the carrier line. (width, not height) Maybe I'm looking at the wrong file entirely. I apktool'd this xml out from the one I made by adding your xml to the apk.
However, our files differ QUITE alot, so this may be goofier than I imagined. For me, that is. 3 days ago I barely knew what Android was or had ever touched a smartphone. But I'm familiar enough with Linux so I'm comfortable with hosing things to the razors edge of brickdomland. No better way to learn than to tinker with this stuff.
Anyway, I suppose setting width or height to 0 would solve the problem either way, correct? If so, then I'll scan what you've zero'd out and try and find my counterpart. Some of the naming conventions differ a little, but not by much. Attached is my file where you can see the difference if you feel like taking a glance.

I also take it there's something to Relative vs. Linear as it applies to something like this. I'm not sure what the complete difference is, other than Linear is the basic layout Vert x Hor on the page.

I don't know what your lockscreen looks like, so I don't know how the carrier/clock and things are arranged, so I can't say for sure, but I would guess if you changed:
Line 5: after "android:id="@id/carrier"" android:layout_height from "wrap_content" to "0.0dip"
for no carrier
and
Line 21, android:layout_height from "fill_parent" to "0.0dip"
to get rid of emergency call button, that might do the trick...

<grin> I never noticed "page 2" on the bottom right of the web page. Anyyyyway...
My screen looks identical to yours, pretty much per pixel.
And I think I changed exactly what you described. I'm *about* to try it now.
I'm starting to wrap my head around all this, so I'll prob go bananaboats on my phone. And more than I should more than likely.
Testing in 10..9..8...
---------- Post added at 11:59 PM ---------- Previous post was at 11:39 PM ----------
Looks good so far, with exception of the gestures (connect-the-dot security) - Now I can't find where that's enabled. Heyzeus Kristo. Same OS/ROM I was using before and I didn't add anything, so I must be missing it somewhere or I don't know what it's called.
I think I'm on the right path though. Thanks a-million for your help. Truly appreciated. Now I've got to find more things I can change. For no other reason than I simply can.
Update: Found pattern locking. CM7 has its own version as well as Androids native. It was Androids that I was looking for. I'll get all this soon enough.
Update 2: Couple things for people with CM7 for the X2. Setting permissions in /system first, before moving .apk into /system/framework seems to be a must. Otherwise things go bananas. And in every language known to man.
Works perfect, with exception of releasing pattern lock. Little grey directional bars stick around on failed attempt and make screen look bit strange. So make sure (don't know if this was mentioned already, but if it was I apologize) to change the graphic for this (trying to locate it now.)
Update 763: I can't locate the graphic for the grey bar that links the pattern circles. If anyone knows, please feel free UNless it's some kind of java routine or css hoopla.

Yeah, I can't stress that enough. Setting permissions BEFORE replacing the original apk, but after putting into /system/ is absolutely essential! Trying to do it AFTER CAN brick your phone! Not just on the X2, but on the Nitro too! TRUST ME. IT CAN =)

Ya, I thought it was all over for me the first time. Fortunately I remembered the restore-a-thon function. But I did learn some Russian and a few other languages trying to decipher all the app quits in 27 different languages after blind copying the apk into Framework. Ah, happy days.

AAHH! I can't thank you enough for this one. My girlfriend got the phone and pocket dialed 911 8 times in one day. Needless to say the last time they were pretty pissed off. The removing of the emergency button saved her!!!
A couple of questions, I take it if I do a factory reset that the fix will remain in place, but if I were to install a custom rom it would then be removed?
Thanks again

Great! Glad it helped! To answer your questions, yes and yes. It will stay if you do a factory reset, but a custom rom will remove it. But even on a custom rom, it's a simple mod. The framework-res.apk I posted may not work for a custom rom, but if you decide to try one, if you send me the framework-res.apk of that rom, I can edit it really easily to get rid of the button and send you that version of it.
edit* Actually, now that I remember, the mod only requires that one XML edit, so it's actually very possible it will work fine with custom roms, but if you send me that keyguard_screen_unlock_portrait.xml from whatever custom rom you choose, I can always check and edit it really easily. OR, if you're feeling adventurous, you can decompile the XML (as described in my XML editing tutorial), and I can point out what edit you need to do to get rid of the button so you can do it for whatever rom or android phone you get in the future! =)

Okay thanks I forgot to mention, I just rooted on the phone, do you know what would happen if i left this and did a hard reset? Do you see that being a problem now that I have already modified the file? Or would everything go smooth?

I'm not sure what you mean. What would happen to your phone if after you used the mod to get rid of the emergency call button, you did a hard reset? I doubt it would have any effect besides resetting your phone. I think the emergency button would still be absent, but I'm not 110% sure. I can't imagine anything would go wrong, but try not to hold it against me if something bizarro happens (though again, I can't imagine it would...)

divider
No replace images... just edit de xml
go to
"@id/divider"
and define
android:layout_width="0.0dip"
android:layout_height="0.0dip"

adg100 said:
Update 763: I can't locate the graphic for the grey bar that links the pattern circles. If anyone knows, please feel free UNless it's some kind of java routine or css hoopla.
Click to expand...
Click to collapse
I found it!! =) It's in the smali com/android/internal/widget/LockPatternView.smali, .line 266 and .line 835, there are settings for color (in hexadecimal) and alpha/transparency (also hex). I thought I'd touch up my lock pattern lines =)
from
to invisible lines (alpha set to "0x0")

Test a App for me Please

Hi all. I am Really Big into Reef aquariums. I have been trying to get this app to work on my Nexus 7 The developer said he Tried it on a Nexus 7 2012 Edition and works fine.
Can someone see if this app shows compatible in the play store. I can side load it and it works fine.
App name Aquarium Manager
For your Convenience
LINK-----https://play.google.com/store/apps/details?id=com.viselabs.aquariummanager
Thank you in advance.
. I will update this tread as Confirmed once someone tells me rather they can install or no

Nope, I suspect they're requiring an Autofocus camera in the manifest.
I looked at the permissions in the market and the only thing that stood out was..
Camera/Microphone
take pictures and videos
If the manifest specifies an autofocus camera, the Nexus 7 will be unsupported.
They'll have to modify their manifest to this..
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false"/>
And MAYBE also..
<uses-feature android:name="android.hardware.camera" android:required="false"/>
And then account for the possibility of not having a camera and/or autofocus in the app.

khaytsus said:
Nope, I suspect they're requiring an Autofocus camera in the manifest.
I looked at the permissions in the market and the only thing that stood out was..
Camera/Microphone
take pictures and videos
If the manifest specifies an autofocus camera, the Nexus 7 will be unsupported.
They'll have to modify their manifest to this..
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false"/>
And MAYBE also..
<uses-feature android:name="android.hardware.camera" android:required="false"/>
And then account for the possibility of not having a camera and/or autofocus in the app.
Click to expand...
Click to collapse
Thank you Very Much i will pass this on to the Developer.. Maybe he has a nexus 2013 he tested with..

Can we use the Nokia Motion Monitor Beta for interop unlocking ????

Hi all
I installed on my lumia 950 xl the Nokia Motion Monitor Beta and moved it to my SD card
The content : http://www86.zippyshare.com/v/VB3r1zEV/file.html
As you can see nothing is encrypted on my SDcard so we can edit it.
The Capabilities it use are these :
Code:
<Capabilities>
<Capability Name="ID_CAP_SENSORS" />
[B] <Capability Name="ID_CAP_OEMPUBLICDIRECTORY" />[/B]
[B] <Capability Name="ID_CAP_INTEROPSERVICES" />[/B]
<Capability Name="ID_CAP_NETWORKING" />
<Capability Name="ID_CAP_IDENTITY_DEVICE" />
<Capability Name="ID_CAP_MEDIALIB_PLAYBACK" />
<Capability Name="ID_CAP_CELL_API_COMMON" />
<Capability Name="ID_CAP_CELL_API_UICC" />
<Capability Name="ID_CAP_CELL_API_UICC_LOWLEVEL" />
<Capability Name="ID_CAP_CELL_API_LOCATION" />
</Capabilities>
can we use it for interop unlocking ??? just like the CustomPFD trick from @Pasquiindustry
http://forum.xda-developers.com/win...xap-custompfd-registry-editor-tweaks-t2981057
maybe we can find a solution for the lumia 550/950/950xl to interop unlock

Why don't you try by using this technique?

sensboston said:
Why don't you try by using this technique?
Click to expand...
Click to collapse
allready did ... not working...

Yeah, looks like MS already fixed that "backdoor"

Yes, because im sure they are here as users.

augustinionut said:
Yes, because im sure they are here as users.
Click to expand...
Click to collapse
I'm 95% sure that MS have a special person who's monitoring (as a dedicated job) most of the "whitehat" Windows/WP oriented forums especially for the "backdoors" hacks...

sensboston said:
I'm 95% sure that MS have a special person who's monitoring (as a dedicated job) most of the "whitehat" Windows/WP oriented forums especially for the "backdoors" hacks...
Click to expand...
Click to collapse
Yes, as well as you can be 95% sure that those presenting the “backdoors” on this forum, and others, actually work for Microsoft. You know… to keep the interest alive.

No s h i t....

Backdoors?
Interop unlock makes it possible for explicitly trusted apps to run with higher privileges, as needed. It is not a 'security' or 'privacy' problem.
It doesn't enable running counterfeit apps, as that is already possible without it, so it's not a "piracy" problem.
Some people may use 'registry unlockables' to work around carrier crippling. I believe this is legal in most of the world. It's a shame though that the carriers are Microsoft's best friends .. /s
If this means that they don't consider blocking the unlocks a priority, I don't know, but I think they, fortunately, at least have little reason.

@winphouser Precisely! These are not backdoors and nobody achieved real jailbreak on W10M - admin rights. These are mere registry tricks under user account privileges.

How To Guide [GUIDE] Enabling Vo5G/VoNR on T-Mobile (plus VoLTE, VoWiFI, video calling for everyone else?)

Update: Android 13 Beta 2 includes Vo5G for T-Mobile, Metro, and Assurance.
The file you want to edit will look similar to this:
/data/user_de/0/com.android.phone/files/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml
Your carrier will likely have a different xml file name. Vo5G should also work for Metro and T-Mobile MVNOs like Mint. Not sure if any other carriers support it. When in doubt, ls the folder. If you are dual-sim, pick the right one.
Root file explorers and editors might not see this file but give it a try. Probably easier to just do this on the device.
You can also do this from command line or do a weird sequence of copies, pulls, edits, pushes with adb and your favorite text editor. You need root.
Example:
adb shell
su
cp /data/user_de/0/com.android.phone/files/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml /sdcard/
exit
exit
adb pull /sdcard/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml
*edit file*
adb push carrierconfig-com.google.android.carrier-8901260570715066153-1.xml /sdcard/
adb shell
su
cp /sdcard/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml /data/user_de/0/com.android.phone/files/
reboot
Click to expand...
Click to collapse
Add or edit these items before the </bundle> at the end. You can combine.
For Vo5G:
<boolean name="vonr_enabled_bool" value="true" />
For VoLTE (experimental):
<boolean name="carrier_volte_available_bool" value="true" />
For VoWiFi (experimental):
<boolean name="carrier_default_wfc_ims_enabled_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
For VT carrier video calling (experimental, seems to set the toggle with my AT&T sim):
<boolean name="carrier_vt_available_bool" value="true" />
Reboot. Enjoy.
Experimental means experimental. Try at your own risk. Additional flags to properly config your carrier or use when roaming are likely needed.
To test Vo5G, the best way is to set NR-only in *#*#4636#*#* and then try to dial your voicemail. I have not tested ViNR/Vi5G (Video over 5G). Your phone will typically only use Vo5G as a last resort otherwise. Be sure to set back to NR/LTE/GSM/WCDMA when done.
And no, I don't know how to enable 5G for your phone in an unsupported country/carrier. I have a few leads on where the xml files may control 5G but again, untested. Or it's deep in the modem package's config files and not something I want to mess with. I'm just laying out my research. Your carrier may block or whitelist these features by IMEI or plan. At least that's the case for my AT&T sim.
Background:
This phone launched without Vo5G support. Or did it? When Android 13 DP1 came out, this was left enabled, among other goodies in the carrier settings and modem. When subsequent builds came out, Vo5G was gone regardless of modem or carrier config pb file overrides. Turns out I was looking in the wrong place. Credit to @foobar66 for laying a great foundation in the original VoLTE thread and ideas on how these kinds of edits can be Magisk modules. For the VoLTE item, when I set to false in the xml, I could no longer place calls in 4G or 5G modes on T-Mobile. It didn't shift down to HSPA+ though as a fallback. And yes, I know that T-Mobile is actually using an VoLTE/EPS core for Vo5G, but it's still Vo5G as far as the phone cares.
oriole:/ # logcat | grep -i vonr
04-28 23:55:50.668 2473 2473 D VoNrSettings: init:
04-28 23:55:50.668 2473 2473 D VoNrSettings: mHas5gCapability: true,mIsNrEnabledFromCarrierConfig: true,mIsVonrEnabledFromCarrierConfig: true,mIsVonrVisibleFromCarrierConfig: true

For me, this is a sophisticated guide.

Now I just need to know how to also enable VoWiFi.
VoLTE works for me out of the box.

VoWifi seems to be a bit more involved. Carriers also like to whitelist it.
Maybe it's <boolean name="carrier_wfc_ims_available_bool" value="true" />?
Setting to false breaks mine.

LLStarks said:
VoWifi seems to be a bit more involved. Carriers also like to whitelist it.
Maybe it's <boolean name="carrier_wfc_ims_available_bool" value="true" />?
Setting to false breaks mine.
Click to expand...
Click to collapse
Tried already. Didn't help :/

LLStarks said:
The file you want to edit:
/data/user_de/0/com.android.phone/files/carrierconfig-com.google.android.carrier-8901260570715066153-1.xml
Your carrier will likely have a different xml file name. Vo5G should also work for Metro and T-Mobile MVNOs like Mint. Not sure if any other carriers support it. When in doubt, ls the folder.
Root file explorers won't see this file. Either have do from command line or do a weird sequence of copies, pulls, edits, pushes with adb and your favorite text editor. You need root.
Example:
Add these items before the </bundle> at the end. You can combine.
For Vo5G:
<boolean name="vonr_enabled_bool" value="true" />
<boolean name="vonr_setting_visibility_bool" value="true" />
For VoLTE (experimental):
<boolean name="carrier_volte_available_bool" value="true" />
For VoWiFi (experimental):
<boolean name="carrier_default_wfc_ims_enabled_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
For VT carrier video calling (experimental, seems to set the toggle with my AT&T sim):
<boolean name="carrier_vt_available_bool" value="true" />
For 5G (experimental):
<int-array name="carrier_nr_availabilities_int_array" num="2">
<item value="1" />
<item value="2" />
</int-array>
Reboot. Enjoy.
Experimental means experimental. Try at your own risk. Additional flags to properly config your carrier or use when roaming are likely needed.
To test Vo5G, the best way is to set NR-only in *#*#4636#*#* and then try to dial your voicemail. I have not tested ViNR/Vi5G (Video over 5G). Your phone will typically only use Vo5G as a last resort otherwise. Be sure to set back to NR/LTE/GSM/WCDMA when done.
And no, I don't know how to enable 5G for your phone in an unsupported country/carrier. I have a few leads on where the xml files may control 5G but again, untested. Or it's deep in the modem package's config files and not something I want to mess with. I'm just laying out my research. Your carrier may block or whitelist these features by IMEI or plan. At least that's the case for my AT&T sim.
Background:
This phone launched without Vo5G support. Or did it? When Android 13 DP1 came out, this was left enabled, among other goodies in the carrier settings and modem. When subsequent builds came out, Vo5G was gone regardless of modem or carrier config pb file overrides. Turns out I was looking in the wrong place. Credit to @foobar66 for laying a great foundation in the original VoLTE thread and ideas on how these kinds of edits can be Magisk modules. For the VoLTE item, when I set to false in the xml, I could no longer place calls in 4G or 5G modes on T-Mobile. It didn't shift down to HSPA+ though as a fallback. And yes, I know that T-Mobile is actually using an VoLTE/EPS core for Vo5G, but it's still Vo5G as far as the phone cares.
oriole:/ # logcat | grep -i vonr
04-28 23:55:50.668 2473 2473 D VoNrSettings: init:
04-28 23:55:50.668 2473 2473 D VoNrSettings: mHas5gCapability: true,mIsNrEnabledFromCarrierConfig: true,mIsVonrEnabledFromCarrierConfig: true,mIsVonrVisibleFromCarrierConfig: true
Click to expand...
Click to collapse
Thank you for this guide Sir!
btw, i had no trouble finding and editing the xml using FX explorer. thx again man!

@LLStarks which carrier do you have?

T-Mobile

Tested from China and it's not working when I tried to enable 5G. I'm using China Telecom and apparently it's an unsupported carrier.

After speaking with some folks on Telegram on carrier config structure, I'm probably going to remove that portion of the guide.

LLStarks said:
After speaking with some folks on Telegram on carrier config structure, I'm probably going to remove that portion of the guide.
Click to expand...
Click to collapse
Isnt your whole guide based on editing the carrier config?

DKErric said:
Tested from China and it's not working when I tried to enable 5G. I'm using China Telecom and apparently it's an unsupported carrier.
Click to expand...
Click to collapse
I think we need and Carrier configuration file from a sim from a supported country to do a comparison and merge... Every sim from every carrier create a specific .XML file

spinoza23 said:
I think we need and Carrier configuration file from a sim from a supported country to do a comparison and merge... Every sim from every carrier create a specific .XML file
Click to expand...
Click to collapse
Maybe we can get the corresponding operator profile through the 5g Samsung mobile phone （exynos）that has been root? Translation from Google - form China

Utini said:
Isnt your whole guide based on editing the carrier config?
Click to expand...
Click to collapse
It is, but I've been speaking with other folks such as Gabe from the bounty Telegram. The portion I removed really only concerned 5G toggles in menus and not the ability to actually use it. Some carriers don't even let you select 5G as an option, that's all I was able to override.
spinoza23 said:
I think we need and Carrier configuration file from a sim from a supported country to do a comparison and merge... Every sim from every carrier create a specific .XML file
Click to expand...
Click to collapse
I haven't seen anything in the carrier config files that suggests 5G can be enabled there. At most, you can control NSA vs SA or defining specific bands that need to be supported like n77, but actually telling the phone to use 5G seems to be at the modem level.

P6 here vo5g disappeared after udpating to july update but also i noticed my carrier settings verison is way too old (idk ut downgraded or what)

The July update FINALLY allowed me to enable wi-fi calling (straight talk, verizon sim).
But, I still can't enable VoLTE. When I try to select it, it is grayed out?
Any hacks for that??

p51d007 said:
The July update FINALLY allowed me to enable wi-fi calling (straight talk, verizon sim).
But, I still can't enable VoLTE. When I try to select it, it is grayed out?
Any hacks for that??
Click to expand...
Click to collapse
No without root

For VoLTE, try all these:
Code:
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="editable_enhanced_4g_lte_bool" value="true" />
<boolean name="enhanced_4g_lte_on_by_default_bool" value="true" />
<boolean name="hide_enhanced_4g_lte_bool" value="false" />
<boolean name="hide_lte_plus_data_icon_bool" value="false" />
<boolean name="lte_enabled_bool" value="true" />
<boolean name="show_4g_for_lte_data_icon_bool" value="true" />
<boolean name="show_data_connected_roaming_notification" value="true" />

Is this specific to T-mobile only, or can it work for Google Fi?

anybody tried this in PLUS PL carrier ? (5g/VoLTE)?