http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506
I have tried to make the edits the OP of the above thread illustrated but for the life of me I can't get any of them to work. Just curious if any of you guys have tried it and got it to work?
FYI the "hidden features" include things like Call Recording, Camera Sound Toggle, Removal of NFC icon and a few other things.
Didn't work for me either..
Only thing that kinda worked was the camera shutter sound can be gotten rid of by turning the ringtone or media volume off before starting the camera..
If you go into System-Media-Ui you can delete all the annoying boot sounds and camera shutter noise
So after messing with this stuff for hours i finally figured it out.
The guide tells you to alter system/csc/others.xml
however in my trials nothing would work - so i did my thing and found out at least on the sprint variant here you have to put the edits into this file --> system/csc/feature.xml once i did the edits to that file and rebooted everything works now, so try that out and let me know how it worked out for you guys
Ah, excellent detective work there. When I have a chance I'll check that out!
EDIT: I followed your instructions and I still couldn't get those features to work. I have no idea what I'm missing.
Where do you find the Wi-Fi Calling after you enabled it? Can you upload your FEATURE.XML file for me so I can compare it to mine? I must be missing something
SantinoInc said:
Ah, excellent detective work there. When I have a chance I'll check that out!
EDIT: I followed your instructions and I still couldn't get those features to work. I have no idea what I'm missing.
Where do you find the Wi-Fi Calling after you enabled it? Can you upload your FEATURE.XML file for me so I can compare it to mine? I must be missing something
Click to expand...
Click to collapse
I think the wifi caling option is in the phone app but i could be wrong sonce i dont use that feature. The only other thing i did was put my new code in the middle of the featre.xml instead of at the end and i made a new section that i named custom edits. From something i read somewhere u have to make sure your edits are before the very last few lines that say </feature> and </Samsung>
franky_402 said:
So after messing with this stuff for hours i finally figured it out.
The guide tells you to alter system/csc/others.xml
however in my trials nothing would work - so i did my thing and found out at least on the sprint variant here you have to put the edits into this file --> system/csc/feature.xml once i did the edits to that file and rebooted everything works now, so try that out and let me know how it worked out for you guys
Click to expand...
Click to collapse
Do I need root for this? If not could you help be get voice with net working?
mobgod said:
Do I need root for this? If not could you help be get voice with net working?
Click to expand...
Click to collapse
Yes you do need root, we are modifying a system file here. With sprints spark you can only get data and voice if your connected to wifi, or you are on a voip call which uses data so then its all the same. No other way around it.
franky_402 said:
Yes you do need root, we are modifying a system file here. With sprints spark you can only get data and voice if your connected to wifi, or you are on a voip call which uses data so then its all the same. No other way around it.
Click to expand...
Click to collapse
OK so even with root I can't get voice and data without Wi-Fi?
Related
I have an app on the market that forces roam. It requires root access, and it has not been tested on every phone/ROM yet, so please let me know if you encounter any issues.
http://www.appbrain.com/app/com.vuvuzela.roamcontrol
------------------------------------------------------------
I also have a mod to enable forced roam, however it has been difficult to get it to work with many ROMs. I'll be happy to help you out with any questions, although I don't understand why some apks recompile correctly and others do not.
I modded Phone.apk to enable forced roaming. I have a couple of apks attached, but Fresh 2.3.3 is the only one that I've tested. It sounds like people are having mixed success with the DC version, and the EVO version doesn't work.
Lots of credit to incognito03:
http://code.google.com/p/android/issues/detail?id=7603#c24
Rename the attached file to "Phone.apk" and push it to /system/app. Not sure if a reboot is required. Remember, always do a nandroid backup when trying something new!
If you want to use this with a different ROM, you should decompile/modify/recompile/sign the apk from the ROM you are using. I attached a diff report for the files I modified so you can see the changes. See my post for instructions: http://forum.xda-developers.com/showthread.php?p=7625035#post7625035
In the code diff, 0x2 is for "Automatic", and 0x4 is for "Sprint only". There is also code for 0x3 (I'm not sure what this is, EVDO only perhaps? As far as I can tell, it's not used), which I changed to 0x1 for "Roam only".
Let me know if you find any issues. The only thing I've noticed is after enabling, when you go back to change the setting again, it doesn't remember/highlight the "roam only" option like it would for the other settings...seems purely cosmetic.
Could you please enumerate the advantages and useful applications of being able to force roaming?
It would be awesome to have this ported to the moment, what would it take for that to happen?
c00ller said:
Could you please enumerate the advantages and useful applications of being able to force roaming?
Click to expand...
Click to collapse
At my office, I get a terrible Sprint signal but a great Verizon signal. When on automatic, the phone is constantly searching for towers and switching between Sprint and Verizon. The phone is incredibly unreliable (almost unusable), and the battery drains rather quickly. Now when I'm at work, I can just force it to roam and everything is peachy.
Forced roaming is available on winmo phones, and it was the one reason I was hesitant to switch to android.
Wow, well congrats on successfully taking matters into your own hands!
Could you post a screenshot of what it looks like? Just a screenshot of the settings page would be nice.
thats a cool apk
but why not just switch PRLs since you get better Verizon at your work?
I do that at my job or whenever i leave town and its fine dont gotta roam
macvalentine said:
thats a cool apk
but why not just switch PRLs since you get better Verizon at your work?
I do that at my job or whenever i leave town and its fine dont gotta roam
Click to expand...
Click to collapse
I tried that but got mixed results. My phone would stop being very responsive and my speeds weren't that great. This is a bit quicker for me since I plan on forcing roam 5 days a week.
AWESOME!
THis is what I've been needing TOO. MrGREG thanks for sharing. Unfortunately when I tried it on CM6 it just closed down all cell reception. When I tried to go to settings it said Phone.apk had FC'ed. Is there anyway to get this running on CM6? I am in the same situation as you are and Being able to ROAM would Help Tremendously.
MrGreg said:
I tried that but got mixed results. My phone would stop being very responsive and my speeds weren't that great. This is a bit quicker for me since I plan on forcing roam 5 days a week.
Click to expand...
Click to collapse
oh got ya. its gonna be good for the peoples that dont get the right results from doin the PRL switch
KueDAWG said:
THis is what I've been needing TOO. MrGREG thanks for sharing. Unfortunately when I tried it on CM6 it just closed down all cell reception. When I tried to go to settings it said Phone.apk had FC'ed. Is there anyway to get this running on CM6? I am in the same situation as you are and Being able to ROAM would Help Tremendously.
Click to expand...
Click to collapse
I've only tested my version with Fresh (since it was based off Fresh). I probably wouldn't try it with other ROMs. Doesn't the latest build of CM6 have force roaming built in?
Failed to copy
When trying to push Phone.apk to /system/app I get the message... "failed to copy 'Phone.apk' to '/system/app/Phone.apk': Read-only file system"
How do I get around this?
Thanks
raddfood said:
When trying to push Phone.apk to /system/app I get the message... "failed to copy 'Phone.apk' to '/system/app/Phone.apk': Read-only file system"
How do I get around this?
Thanks
Click to expand...
Click to collapse
Be sure to enter the command adb remount before you try to push to your phone.
MrGreg said:
I've only tested my version with Fresh (since it was based off Fresh). I probably wouldn't try it with other ROMs. Doesn't the latest build of CM6 have force roaming built in?
Click to expand...
Click to collapse
It does have it builtin, but it forces the data connection to 1x...
Jedis said:
It does have it builtin, but it forces the data connection to 1x...
Click to expand...
Click to collapse
My mod does the same thing. Sprint has an agreement with Verizon to roam with 1x, not EVDO. I believe the PRL hack (mentioned earlier in this thread) will allow you to roam with EVDO, but I never had much luck with that.
JCFrancis said:
It would be awesome to have this ported to the moment, what would it take for that to happen?
Click to expand...
Click to collapse
Unfortunately I don't think I can take the time to port the changes. You (or someone) would have to decompile your Phone.apk (using Apk Manager, http://forum.xda-developers.com/showthread.php?t=695701) and see if the changes I made (see attachment on my first post) apply to the Moment.
Just had to say that this is awesome, thanks !
FINALLLLY THANK YOU i have no service in my room and i used to use windows where i could switch it at anytime i actually had this phone for 3 months before i used it because of this problem
spoke to soon lol tried on stock rom didnt replace phone.apk just added another i tried deleting the old but now i just get no service will play around with it probly just user error on my part
PRL Hack, U say?
For now 1x roaming is fine for me. And so I will use CM6's forced roam. But this PRL hack sounds intriguing. I'll Search the forum for it. Still I'm glad U got it working for you. Thanks for all the help.
eh no luck just nandroided back
this is the stock phone.apk and phone.odex if you could go in to more detail on what i have to do to change this file id really appreciate it thanks
Hi all,
I've recently update Bionix's ROM from 1.0 to 1.1, and have lost the ability to do wi-fi calling. I know those guys consider it bloatware, but with the cell reception in my house it's the only way to get calls in/out.
Can anyone point me to a wi-fi install .zip that'll work with it? I tried the one on MIUI's page, but it just craps out on me.
It worked w/ 1.0, so I'm not sure what changed, and I can't post to the dev forums 'cause I just registered.
TIA,
ByTor
VMD_ByTor said:
Hi all,
I've recently update Bionix's ROM from 1.0 to 1.1, and have lost the ability to do wi-fi calling. I know those guys consider it bloatware, but with the cell reception in my house it's the only way to get calls in/out.
Can anyone point me to a wi-fi install .zip that'll work with it? I tried the one on MIUI's page, but it just craps out on me.
It worked w/ 1.0, so I'm not sure what changed, and I can't post to the dev forums 'cause I just registered.
TIA,
ByTor
Click to expand...
Click to collapse
Did you read the options? You can install Bloater to install WiFi Calling.
Yeah, I saw that. But when I read up on bloater, it looked like a gps tool (w/r/t the G2X), and I couldn't find much other info on it than that.
VMD_ByTor said:
Yeah, I saw that. But when I read up on bloater, it looked like a gps tool, and I couldn't find much other info on it than that.
Click to expand...
Click to collapse
Yes, Roman built it to swap out gps.conf on the G2x, but it was originally designed to install bloat, like WiFi Calling. Go to the thread, install it. When you open it, go to G2x (lotherius), then Utilities, then hit install next to Wifi Calling.
Thanks Mr. Apocalypse, and Roman. Success!
I can't figure this out to save my life.
WiFi calling simply doesn't work. When I try to open the app on any ROM I get an immediate FC.
I've tried the wifi calling patches. I've tried fresh ROM installs. I've tried all the kernels. I've tried reinstalling the WiFi calling apk. (Though I don't think I properly got rid of the old one first, so that might be it)
The patches REALLY don't work. When I flash those the phone boot loops forever.
It's not that the wifi calling app opens then simply doesn't work right. It won't even open. It certainly acts like a problem with the app itself, rather than than the phone's ability to properly utilize the app...but I'm just guessing.
Any thoughts?
I'm very open to proper steps to completely remove wifi calling so I can do a proper reinstall instead of just trying to install over the existing version, which is what I think I've done.
I did recently upgrade to the updated firmware, in case that's a known cause.
I can't imaging the radio has much to do with it since wifi works fine in general, just not for calling.
The goal is to get it working right on CM7 for right now.
And if this is like a REALLY noob problem that I'm missing an insanely obvious answer on.....then you get double thanks for dealing with me.
Well first off do you have the tmobile cid and the right mid? If you don't have either it won't show on first boot for tmobile sensation
I have SuperCID 11111111
Does that louse it up?
I have no idea what my Mid is
Skipjacks said:
I have SuperCID 11111111
Does that louse it up?
I have no idea what my Mid is
Click to expand...
Click to collapse
Yeah that my, as for mid look for a thread called or similar to guide to fix wifi calling
Okay...still working on this.
I put my CID back to a stock T Mobile one.
My MID is PM581000
So that's all normal. I can see the app icon just fine. It just doesn't run.
The force close error says com.android.kineto has stopped.
What could be making the process stop?
Bumping this to see if anyone has thoughts on this.
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !
Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?
crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.
I just got the NA version of the ROG Phone 5 and sadly I cannot get VoWiFi working on TMobile. Sadly I'm in an area where I don't get the best signal and it's extremely important for this feature to work. Especially considering I spent 1k+ for this phone... Any help/guidance would be appreciated.
Have you enabled it in settings and then tried a reboot?
I've also noticed that it may not work until the SIM is installed BEFORE initial setup (or before a factory reset)
I confirmed with other people too. US version doesnt have Tmobile wifi. If it would, I would have bought one
twistedumbrella said:
Have you enabled it in settings and then tried a reboot?
I've also noticed that it may not work until the SIM is installed BEFORE initial setup (or before a factory reset)
Click to expand...
Click to collapse
Yeah I tried that but didnt work so i manually enabled it using the phone dialer and after i toggle it on or off it will turn on but it turns off after reboot so need to root it so i can make the settings stick.
daviddem said:
I confirmed with other people too. US version doesnt have Tmobile wifi. If it would, I would have bought one
Click to expand...
Click to collapse
It actually does work
My AT&T and T-Mobile SIMs (both Red Pocket MVNO) have VoLTE but not VoWiFi.
kva1992 said:
It actually does work
Click to expand...
Click to collapse
So do you get wifi calling with US ROG phone on Tmobile?
daviddem said:
So do you get wifi calling with US ROG phone on Tmobile?
Click to expand...
Click to collapse
Yup just have to manually enable it Everytime it boots up but if you root it you can set the props and it will be permanent. In the process of doing that atm.
kva1992 said:
Yup just have to manually enable it Everytime it boots up but if you root it you can set the props and it will be permanent. In the process of doing that atm.
Click to expand...
Click to collapse
Thank you. I was debating between ROG or xperia 1iii. but if this works. Ill get ROG.
If you dont mind, can you please post the dialer code
daviddem said:
Thank you. I was debating between ROG or xperia 1iii. but if this works. Ill get ROG.
If you dont mind, can you please post the dialer code
Click to expand...
Click to collapse
Sure here you go *#*#3642623344#*#*
You should be able to copy and paste if that doesn't work try pasting but delete the last * and add it manually. If that still doesn't work just manually type it in. But I tested it out a few times nd it works even turned on airplane mode and it works. Wi-fi calling was a deciding factor for me lol was about to return it until I found out I could get it to work properly.
daviddem said:
Thank you. I was debating between ROG or xperia 1iii. but if this works. Ill get ROG.
If you dont mind, can you please post the dialer code
Click to expand...
Click to collapse
kva1992 said:
Sure here you go *#*#3642623344#*#*
You should be able to copy and paste if that doesn't work try pasting but delete the last * and add it manually. If that still doesn't work just manually type it in. But I tested it out a few times nd it works even turned on airplane mode and it works. Wi-fi calling was a deciding factor for me lol was about to return it until I found out I could get it to work properly.
Click to expand...
Click to collapse
I'd like to add that after running the dialing code you have to enable wifi calling in the settings app.
Aswell as that, at least for me, I need to disable and re-enable it within settings after re-running the dial after reboot, for it to actually reconnect
Just to avoid any confusion.
This does work tho! Kva is right!
Trickster29 said:
I'd like to add that after running the dialing code you have to enable wifi calling in the settings app.
Aswell as that, at least for me, I need to disable and re-enable it within settings after re-running the dial after reboot, for it to actually reconnect
Just to avoid any confusion.
This does work tho! Kva is right!
Click to expand...
Click to collapse
Thank you both. Ill order the phone and try it.
Trickster29 said:
I'd like to add that after running the dialing code you have to enable wifi calling in the settings app.
Aswell as that, at least for me, I need to disable and re-enable it within settings after re-running the dial after reboot, for it to actually reconnect
Just to avoid any confusion.
This does work tho! Kva is right!
Click to expand...
Click to collapse
It's so stupid wish they enabled it by default would make all our lives easier
kva1992 said:
It's so stupid wish they enabled it by default would make all our lives easier
Click to expand...
Click to collapse
I agree, but idk if they need some authorization from T-Mobile to enable it by default and we're just the end user working around that.
Otherwise, I'm not really sure at all why the functionality is developed but not enabled by default.
Trickster29 said:
I agree, but idk if they need some authorization from T-Mobile to enable it by default and we're just the end user working around that.
Otherwise, I'm not really sure at all why the functionality is developed but not enabled by default.
Click to expand...
Click to collapse
Yeah it's stupid I ended up talking to advanced tech support and the guy has never heard of ROG phone 5 and said I should return it cuz it seems like it's a hardware issue.... I'm like dude it's your system not giving me proper access's and authorizing my phone... He's like I guess you know more about phones than I do... The idiot even made me reset my phone to try and fix it even though I told him several times that has nothing to do with it.... I swear I have no idea how some of these morons get jobs as IT... At least have basic IT understanding....
They're not in IT. They're customer service reps. They read from a script.
Check out the movie The Internship. It's just like that.
twistedumbrella said:
They're not in IT. They're customer service reps. They read from a script.
Check out the movie The Internship. It's just like that.
Click to expand...
Click to collapse
Well, when I'm talking to the advanced Technical team I am not talking to customer service reps... I talked to a customer service rep and they forwarded me to the IT team. Considering they are called advanced technical teams I would assume they are in IT. whereas the initial person I talked to was and clearly stated she was a customer service rep.
The only difference between the two people you spoke with is that one had access and authorization to suggest more "advanced" solutions. I'm not saying they shouldn't have better training, but legitimate IT professionals rarely work the call center as more than a summer job.
Anyway, the point was that they're a waste of time unless the issue is the SIM card or your plan. It's unfortunate.
Dial codes typically trigger an intent. If you can track down the intent, you can have it launch automatically on boot. Once that's taken care of, it shouldn't be too hard to automatically enable the setting. That is assuming you called because setting the prop didn't work.
Another alternative if you do have a property and can't write to system is setting it with a magisk module, since the system is read only on a firmware level.
twistedumbrella said:
The only difference between the two people you spoke with is that one had access and authorization to suggest more "advanced" solutions. I'm not saying they shouldn't have better training, but legitimate IT professionals rarely work the call center as more than a summer job.
Anyway, the point was that they're a waste of time unless the issue is the SIM card or your plan. It's unfortunate.
Dial codes typically trigger an intent. If you can track down the intent, you can have it launch automatically on boot. Once that's taken care of, it shouldn't be too hard to automatically enable the setting. That is assuming you called because setting the prop didn't work.
Another alternative if you do have a property and can't write to system is setting it with a magisk module, since the system is read only on a firmware level.
Click to expand...
Click to collapse
How would I set that up using magisk module? One Issue I have noticed is the wifi calling turns itself off after a while. sometimes it works for several hours other times maybe a day but then turns off and I have to restart the phone and run the command again.
Developer Guides
The Magic Mask for Android
topjohnwu.github.io