Related
It's supprising how few people use sip at least those who own Razri. I found it very useful and money saving, especially when travelling.Unfortunatelly Razri uses proprietary phone.apk as a part of Motoblur and Motorola stripped off the entire Internet calling part from the application. It was the case in previous ICS and it remains in JB. Other manufacturers which opt for the similar solution use predictive way to remove android.software.sip.xml from the system and change sip value to false in framework-res.apk. But not Motorola. It obviously used more sophisticated approach. Both above mentioned files remains intact as far as the sip is concerned.
There is an application on the Google Play named Sipswitch which enable widget to enter voip credentials. In previous ICS you couldn't activate the connection. Suprisingly with JB the system accepts the credentials and communicates with the VOIP provider. And the SIP app appears as an extension of the Motorola Phone.apk. But unfortunatelly the SIP is not triggered though it is enabled. There is still the missing link remains. Is the failure result of the fact that Sipswitch is not the system application?
I'm aware that there are many SIP applications on the market. I tried most of them but with Razri they have voice issues. I have best experience with native Voip from previous phones. Does someone else plays with SIP or has otherwise useful advice how to proceed?
piskr said:
It's supprising how few people use sip at least those who own Razri. I found it very useful and money saving, especially when travelling.Unfortunatelly Razri uses proprietary phone.apk as a part of Motoblur and Motorola stripped off the entire Internet calling part from the application. It was the case in previous ICS and it remains in JB. Other manufacturers which opt for the similar solution use predictive way to remove android.software.sip.xml from the system and change sip value to false in framework-res.apk. But not Motorola. It obviously used more sophisticated approach. Both above mentioned files remains intact as far as the sip is concerned.
There is an application on the Google Play named Sipswitch which enable widget to enter voip credentials. In previous ICS you couldn't activate the connection. Suprisingly with JB the system accepts the credentials and communicates with the VOIP provider. And the SIP app appears as an extension of the Motorola Phone.apk. But unfortunatelly the SIP is not triggered though it is enabled. There is still the missing link remains. Is the failure result of the fact that Sipswitch is not the system application?
I'm aware that there are many SIP applications on the market. I tried most of them but with Razri they have voice issues. I have best experience with native Voip from previous phones. Does someone else plays with SIP or has otherwise useful advice how to proceed?
Click to expand...
Click to collapse
Nobody engaged with the SIP? OK, since I'm not a programmer I'm kindly asking developers to take a close look to the attached applications. The first is Motorola's Blur Phone.apk, the second is original ICS Phone.apk. My question is: supposed I root the phone, if I delete Blur Phone.apk and install the original one (which has SIP option included) into the system, do I solve the problem or this is not the appropriate method? Perhaps because of diferrent apk frames or something else? Or must I replace the appropriate (original) Contact.apk as well? Thanks.
Aw: [q] sip/voip
Hi, i have the same problem. I'd like to use my VoIP number with the standard phone app.
I hope that someone can help with this.
Sent from my XT890 using xda app-developers app
me too!
Hi,
I have same problem (ThL W8 phone JB4.1.2 with mt6589 cpu) great phone, but SIP capability has been crippled somehow. Its in the framework-res.apk and the other setup files are there, it seems to be in the code for phone.apk, but there is nothing visible in the menu's and the SIP tester app reports no sip or voip capability. I'd love to know what has been done and how to undo it. It seems somebody has spent quite a lot of time and effort hiding this capability and the only reason I can see is bowing to pressure from the 'airtime sellers'.
I hope someone will point us in the right direction and soon.
gmincca said:
Hi,
I have same problem (ThL W8 phone JB4.1.2 with mt6589 cpu) great phone, but SIP capability has been crippled somehow. Its in the framework-res.apk and the other setup files are there, it seems to be in the code for phone.apk, but there is nothing visible in the menu's and the SIP tester app reports no sip or voip capability. I'd love to know what has been done and how to undo it. It seems somebody has spent quite a lot of time and effort hiding this capability and the only reason I can see is bowing to pressure from the 'airtime sellers'.
I hope someone will point us in the right direction and soon.
Click to expand...
Click to collapse
Well, you missed the forum, but regarding your problem it is not quite the same as here. If the SIP tester doesn't recognize the necessary conditions for SIP, you can try this method: http://forum.xda-developers.com/showthread.php?t=1592890
Motorola as the most qualified phone company uses more sophisticated and dirty methods to screw its customers: the SIP tester does detect sip capability and all necessary files and settings are enabled. But the SIP part is simply stripped off from the core phone.apk.
If you don't dare to try the suggested method you could always use Keyyo voip which has been updated recently and works flawlessly: https://play.google.com/store/apps/...DEsImNvbS5rZXl5b21vYmlsZS5hbmRyb2lkLnZvaXAiXQ..
piskr said:
Well, you missed the forum, but regarding your problem it is not quite the same as here. If the SIP tester doesn't recognize the necessary conditions for SIP, you can try this method: http://forum.xda-developers.com/showthread.php?t=1592890
Motorola as the most qualified phone company uses more sophisticated and dirty methods to screw its customers: the SIP tester does detect sip capability and all necessary files and settings are enabled. But the SIP part is simply stripped off from the core phone.apk.
If you don't dare to try the suggested method you could always use Keyyo voip which has been updated recently and works flawlessly: https://play.google.com/store/apps/...DEsImNvbS5rZXl5b21vYmlsZS5hbmRyb2lkLnZvaXAiXQ..
Click to expand...
Click to collapse
Hi,
Thanks, but the whole point of my posting is because all of the sip information in post 1592890 is already in place, everything looks as though SIP should work, but SIP tester doesn't recognise sip or voip capability and there is nothing in the menus. As for sip/voip apps yes there are countless of them good and bad, but this capability is built into Android and I want to be able to use it as I did on my old 2.3.6 phone. I'm just completely lost as to how to get it enabled.
So thanks, but really not much help so far.
gmincca said:
Hi,
Thanks, but the whole point of my posting is because all of the sip information in post 1592890 is already in place, everything looks as though SIP should work, but SIP tester doesn't recognise sip or voip capability and there is nothing in the menus. As for sip/voip apps yes there are countless of them good and bad, but this capability is built into Android and I want to be able to use it as I did on my old 2.3.6 phone. I'm just completely lost as to how to get it enabled.
So thanks, but really not much help so far.
Click to expand...
Click to collapse
If you have both files set correct (SIP enabled in framework-res.apk and xml) than you have virtually the same problem as it is with RazrI. The core phone.apk is rebuild in the manner that the sip part is stripped off. I prefer native SIP too, regarding my previous experience is the best, but I'm afraid that the only solution in our case is to get AOSP Phone.apk (or similar with SIP as CM) and reconstruct the framework-res.apk accordingly. I'm not the programmer, I'm not sure if it could be done with this method or the whole system is to be replaced with AOSP or CM since Phone.apk is a core application cross related with a lot of other stuff.
What you can try eventually is to deploy two apps: SipSwitch Widget and Zeynalov's Call Manager (Google Play). Sip Switch Widget enables inserting your voip providers credentials and Call Manager supposed to serve as sip trigger. For me the combination wasn't work and I doubt that it would in your case since in your case sip is even not recognised as existed. But it cause no harm to give them a try.
Just use this method, works for me:
http://forum.xda-developers.com/showpost.php?p=24710862&postcount=2
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
You can probably unpair (from both the phone and sync) and then repair and when you repair just deny the MAP access request.
Also, you should be able to turn off new message download in Sync
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
boosting1bar said:
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
Click to expand...
Click to collapse
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Yeah that's exactly what I'm getting in my 14 Raptor. Terrible, I guess I have to disable it every time I get in the car now.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
dtg7 said:
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
Click to expand...
Click to collapse
Great idea, however I just tried it with no avail.
I just thought of something as well... my fiance has a '13 Focus SE with the base stereo, and she has the same model phone as me (VZW X Dev). Her SYNC doesn't alert her to new messages, but my truck with the same SYNC setup did, but I figured my truck had a more recent version of SYNC. I dunno, all I know is it's annoying as hell and I'd like to find a more permanent solution. Especially since I'm contemplating on buying the Droid Turbo in the future and I'm sure it will do the same thing.
triton302 said:
Great idea, however I just tried it with no avail.
Click to expand...
Click to collapse
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
dtg7 said:
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
Click to expand...
Click to collapse
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
boosting1bar said:
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
Click to expand...
Click to collapse
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
https://play.google.com/store/apps/details?id=cn.wq.disableservice
good luck.
dtg7 said:
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
good luck.
Click to expand...
Click to collapse
Thanks so much! Option 2 is exactly what I've been looking for! Option 1 doesn't work for me because I use Trigger and have conditional BT on/off and that would just recreate the same problem lol.
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
triton302 said:
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
Click to expand...
Click to collapse
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
boosting1bar said:
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
Click to expand...
Click to collapse
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of profile).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Roger, I'm off work today so I'll try these out here shortly.
EDIT: From what I recall, if you have a recent version of MFT, there are no options whatsoever for MAP, in phone or system settings. I'll double check.
EDITING EDIT: #2 doesn't work.
dtg7 said:
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of protocol).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Click to expand...
Click to collapse
I think we have a winner! #3 works perfectly.
I tested it with the phone unlocked and locked, rebooting the phone, toggling bluetooth on and off, turning the car on and off... seems to work every time. As long as you turn off just the SMS/MMS options, you can still have it send and receive calls and allow the device to remain unlocked while connected.
Ahhhh...... Success feels good...
Xposed is pretty amazing... It gives us a fighting chance lol.
if only they'd installed Xposed on Skynet things might have turned out differently...
dtg7 said:
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
Click to expand...
Click to collapse
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
You're welcome!
boosting1bar said:
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
Click to expand...
Click to collapse
How did you get this yo work? I am on a cm12 Rom also with the same issue.
Did all the above, but anytime I start the Bluetooth afterwards, it just reactivates the "Read / Write sms messages permission all over again nd im back to square 1.
Sorry to bump an old thread. But its still yhe same issue I am dealing with.
Hey folks!
I followed the instructions posted by allcaps33 at http://forum.xda-developers.com/showthread.php?p=53549710 to get provisioning disabled, and the native hotspot app is working for me now! I just wanted to confirm if this was an operation similar to running Wifi Tether Router on an unlocked/rooted device (I had an S2Sky prior that I tethered off of regularly). I've got one of those too-rare Unlimited Data plans and am traveling cross-country, made possible by being able to tether my laptop to my phone to work. Just wanting to confirm that this was relatively as secure as using the Wifi Tether Router on my S2Sky. On a semi-related note, that app doesn't seem to want to run properly on my S5; when I click Enable Router it turns on the Wifi, which immediately connects to the house's wired router. It still broadcasts but doesn't send data, and it's hit or miss if a device can even connect to it from there.
Next question - I'm used to flashing a CM ROM within the first couple days of getting a new phone, which doesn't seem feasible just yet with the S5 (from what I can tell anyway; I'm not used to having a current-gen device). I've heard about the myriad evils of OTA updates, and was hoping to get help on how to disable them. I would like to avoid my device upgrading to a point where my above-stated desired functionality is disabled. Ideally, I'd like to get rid of the various bloatware apps as well, though am not sure how to go about that.
I appreciate your time and support, and thanks for being a community that's always been there for me as I derp along with my fancy internet boxes!
Hi!
The absolute easiest way is to use Rom Toolbox. I have the pro version, but I believe it's available in the lite version as well.
Download and open up RTB.
Tap on "App Manager"
Then scroll down until you see "AT&T Software Update"
Tap on it.
A popup will display. Swipe from right to left, and you will be on the "Advanced" tab.
Scroll down and tap on "Advanced Freeze."
You will come to a screen which shows you the Activities, Recievers, Services, and Providers. Tap on EACH box/line. This will Disable OTA services.
We're not done yet!
Go back to the App Manager screen again, and repeat the process for an app called "LocalFOTA"
Finished!
I also Disable most of the bloatware and Knox this way.
Have fun!
---------- Post added at 12:58 PM ---------- Previous post was at 12:49 PM ----------
Now for the hard part...
Yes this can be as secure as the other the tether. Ensure you use and change the password service with the app.
As for the tether turning your wifi on, it is supposed to do that. The best way to get this to work is to turn the tether on and off (then on again). If this does not work, try emptying the data/cache for the built-in tether app. And start from scratch.
allcaps33 said:
I also Disable most of the bloatware and Knox this way.
Click to expand...
Click to collapse
KNOX - What is it? I'm under the impression it's some sort of security for the phone, to protect from malicious activity that you might not be aware of, but also that it'll "tattle" on you if you mod your phone in a way AT&T doesn't approve.
Knox is two things.
1) It is a security container for apps. It works as both a license/drm type software for Samsung official apps.
And
2) Android contains a root environment at all times. This is what makes SU possible. It used to be quite easy to invoke Android system calls as root.
Root is actually separate from super user. Knox, like SEPolicy, helps dev companies detect, halt, and/or hinder apps, not su itself, but apps that that use these root system calls.
Be wise, even though Knox itself does not "report" these types of actions, it still logs them. And there are other apps that can read these logs and send out these reports. I should say (and I'm only guessing) that only work/company issued phones are setup like this. Not your personal phone.
In fact, our phones actually contain a file which logs all root system calls. It has nothing to do with Knox but, I believe this binary is what hinders us open devs, but makes it easy for Samsung and AT&T to restore/repair our phones.
For more info on Knox:
https://www.samsungknox.com/en/partners/app-developers
Update: This module was a trial. The results seem to indicate that there is significantly more work to do to enable VoWiFi or VoLTE.
I will leave this module up for anyone interested in enabling the options, but please be aware it will not make these features work.
VoEnabler
This module edits build.prop to enable VoLTE & VoWiFi features on your device.
Download via Magisk Manager or from GitHub.
Important:
This module will not add VoLTE/VoWiFi support to a device that doesn't already support it.
The module will not add VoLTE/VoWiFi support to a carrier that doesn't already support it.
Notes: 2017/08/01
I've changed the module from VoLTE Enabler to VoEnabler and added VoWiFi options. I was going to split them into different modules, but I don't think there's really a point. If you want one you probably want the other and if your device doesn't know what the options are then it should ignore them anyway.
Suggestions: I'd remove the "VoLTE Enabler" module before installing this because the options are the same, but even if you didn't, it won't cause problems.
What did I change?
Code:
# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Why?
My carrier supports VoLTE/VoWiFi but not on my device. I made this module to forcefully enable it to test if it worked (it hasn't so far).
The only reason I've published this is to give others the chance to try. It may very well do nothing at all. If no one reports success, then I'll update the topic and ask the mods to lock it.
As I understand it, VoLTE and VoWiFi both require carrier side support anyway. Next step would be to see if it's possible to get the settings from compatible devices and see if it's still possible to make a module.
If anyone has any to add or suggestions for doing this, please let me know.
I'm not going to be providing any support for this because I'm not convinced it even works, but your mileage may vary. *shrug*
Credits:
@topjohnwu for Magisk. Especially the documentation and templates.
@shadowstep because I used his Enable Call Recording module as reference.
@fards for some additional build.prop values.
Last updated: 2018/09/20
2018-09-19 (v1.3): Update template for Magisk v17.x and removed post attachments. Please check Magisk Manager or GitHub for downloads.
2017-08-16: Updated post to reflect that this module will enable the options, but won't make them work. Leaving module up for anyone who wishes to experiment.
2017-08-02 (v1.1): Removed "persist.data.iwlan.enable=true" as this was reported to break WiFi calling on some carriers.
2017-08-01 (v1): Renamed to VoEnabler and added VoWiFi options. Replaced attachment.
2017-07-31 (Beta): Initial commit.
How to know it work or not
psychoela said:
How to know it work or not
Click to expand...
Click to collapse
Make a call to someone，When you are on call，open browser，fresh a webpage，if it freshed，it's OK
---------- Post added at 03:28 AM ---------- Previous post was at 03:27 AM ----------
Volte=connect to mobile network when calling
daxiaamu said:
Make a call to someone，When you are on call，open browser，fresh a webpage，if it freshed，it's OK
---------- Post added at 03:28 AM ---------- Previous post was at 03:27 AM ----------
Volte=connect to mobile network when calling
Click to expand...
Click to collapse
It is not like that. It supposed to be your are on LTE, and then when you trying to make a phone call, it will immediately switch to HSPDA/3G, and get back to LTE as soon as the call ends. That is the symptom that VoLTE is not supported by the carrier. So if it is working, it should remain on LTE whenever you making a phone call.
What advantage does the flame make and is it maintained in LTE?
psychoela said:
How to know it work or not
Click to expand...
Click to collapse
If it's working, you'll see a little VoLTE icon in the status bar like either of these...
Edit: Sorry. Just to clarify, if the module is working you'll see something like this... in "SIM & Network" in settings.
Nitram08 said:
What advantage does the flame make and is it maintained in LTE?
Click to expand...
Click to collapse
The advantage is higher quality voice when on phone calls. That's really about it.
VoWiFi also exists which lets you make and receive calls from WiFi in case you don't have signal.
Not only higher voice quality but faster dialing too. [emoji6]
Thanks
On my phone i changed the CSC-File to enable VoLTE and VoWiFi, i didn't know that it can be enabled in the build.prop too. i have a S7 Edge BTW.
Iradj said:
On my phone i changed the CSC-File to enable VoLTE and VoWiFi, i didn't know that it can be enabled in the build.prop too. i have a S7 Edge BTW.
View attachment 4229633
Click to expand...
Click to collapse
From memory, that's a Samsung only feature? CSC files.
The build.prop stuff is generic so should work on any device. And Magisk so means not modifying /system.
I'm still not convinced it does anything by itself, but I figure it's easier to make a simple module and let folks give it a try. If it genuinely does nothing and no one can figure anything else out, then I'll delete the attachment and modify the first post so at least there is something to search for that says "THIS DOESN'T WORK. DON'T BOTHER".
Just tried this on my OP3, gave me the enhanced 4g option but when I turn it on it doesnt make any difference. On call the network drops down to 3g/H from 4g LTE
Raharazod said:
From memory, that's a Samsung only feature? CSC files.
The build.prop stuff is generic so should work on any device. And Magisk so means not modifying /system.
I'm still not convinced it does anything by itself, but I figure it's easier to make a simple module and let folks give it a try. If it genuinely does nothing and no one can figure anything else out, then I'll delete the attachment and modify the first post so at least there is something to search for that says "THIS DOESN'T WORK. DON'T BOTHER".
Click to expand...
Click to collapse
Yes in the CSC-File you can enable and disable, some hidden features specifically for Samsung Phones. I also made an Magisk Module to activate some features systemlessly like App-Lock, Floating Messages, VoLTE, VoWiFi and other but I will test out your Module and look if it works with my phone.
Just tried this on my OnePlus 3 that is on ATT and it did not work. I did enable it in settings as well before trying. If we could get this to work that would be great!
Sent from my OnePlus 3 using XDA Labs
I have a Huawei P9 lite and I installed this module. New options have appeared in the settings but unfortunately despite my provider supporting VoLTE when I call it always goes to 3G
doesnt work with BQ Aquaris X5 Plus (Gohan)
With the 1.1 update I'm getting VoWiFi and it seems to work. VoLTE remains elusive.
I don't think it's that easy.
I asked the developer of the ROM I'm currently using for activating VoLTE.
He said maybe in the future, because a lot of modifications have to be made, not just editing build.prop.
Sent from my HTC 10 using XDA Labs
Magyar Telekom also introduced the VOLTE service. I asked why it did not work on my OP3 phone. I got the answer that it would only work on Samsung phones on their network.
No comment...
How to edit the VoWiFi settings to put my carriers server to connect ? I'm on Orange ro and we have VoLTE and VoWiFi.
Mtk devices support ???
(Le Eco 1s x509)
Hi all,
after updating to 47.1.A.8.49 my XZ1 compact (german firmware, retail) keeps on consuming like 8% battery on RCS.
I already disabled VoLTE and Wifi-Calling but it did not help.
I read that normally there should be an option to deactivate Rich Communication in the Messages App, but I can't find any there.
(I know it should help to deactivate/deinstall the Messages App, but I would like to keep receiving SMS, I only do not need the "chat" feature of RCS.)
Anyone knows how I can deactivate RCS?
best wishes
nospherato
nospherato said:
Hi all,
after updating to 47.1.A.8.49 my XZ1 compact (german firmware, retail) keeps on consuming like 8% battery on RCS.
I already disabled VoLTE and Wifi-Calling but it did not help.
I read that normally there should be an option to deactivate Rich Communication in the Messages App, but I can't find any there.
(I know it should help to deactivate/deinstall the Messages App, but I would like to keep receiving SMS, I only do not need the "chat" feature of RCS.)
Anyone knows how I can deactivate RCS?
best wishes
nospherato
Click to expand...
Click to collapse
If you have ADB set up on your laptop/desktop it would be easy.
ADB Shell
pm list packages ?
pm uninstall --user 0 "package name goes here"
Sorry, I am not at home with my machine in front of me, so I can't tell you what the package name is.
I also have had big battery drain since the 8.49 update. If you're in the uninstalling mood, removing 'home network' made a difference to battery life, as did removing 'Find My Device' from admin apps.
To remove home network, look for a package called 'com.sony.android.dnla', or something similar, sorry not in front of my machine to check.
RCS isn't actually the problem. It's a bug in Oreo. Android System is sometimes showing up as RCS or Phone in the battery stats or monitoring apps. So disabling RCS won't actually help you.
@Didgesteve
Thanks for your post. As I do not use "find my device" I removed it after your post. I don't really know if it got the battery usage better, but well.. I didn't use it before, so why keep it in admin apps
Do I really need to remove the dnla package to save battery? (It's deactivated anyway in my settings)
@jrbmed08
Thank you, too. I once thought I have seen exactly this: After a reboot the x% usage were shown as Android System; after 1-2min it said RCS.
nospherato said:
@Didgesteve
Thanks for your post. As I do not use "find my device" I removed it after your post. I don't really know if it got the battery usage better, but well.. I didn't use it before, so why keep it in admin apps
Do I really need to remove the dnla package to save battery? (It's deactivated anyway in my settings)
@jrbmed08
Thank you, too. I once thought I have seen exactly this: After a reboot the x% usage were shown as Android System; after 1-2min it said RCS.
Click to expand...
Click to collapse
I don't think there's any one thing that will miraculously change your battery usage, it's the unwritten scripture that drives all us modders and obsessive fiddlers to keep trying to improve.
But if you are into tweaking for the better, the new Google Play services beta did seems to make a small difference.
Download from APK mirror and update.
nospherato said:
Hi all,
after updating to 47.1.A.8.49 my XZ1 compact (german firmware, retail) keeps on consuming like 8% battery on RCS.
I already disabled VoLTE and Wifi-Calling but it did not help.
I read that normally there should be an option to deactivate Rich Communication in the Messages App, but I can't find any there.
(I know it should help to deactivate/deinstall the Messages App, but I would like to keep receiving SMS, I only do not need the "chat" feature of RCS.)
Anyone knows how I can deactivate RCS?
best wishes
nospherato
Click to expand...
Click to collapse
I did some digging with your tip about RCS. When I first got this phone I was getting almost 4 days on one charge (I'm not a heavy user), but I thought it was a bit strange that since November I have had much worse battery. I put it down to the new firmware, perhaps 8.49 was much more thirsty. Aparently, since November, Google have activated RCSService, I keep seeing this coming up my battery usage charts, next to Carrier Service, using more battery than bluetooth and I do 2 hours of bluetooth music a day. I never saw it before, suddenly it's on all the time, using batrery and data.
Turning on the 'background data only' makes no difference, likewise 'background activity'
So the intention here is to stop and disable carrier services and disable RCSService (it's impossible to stop or uninstall).
adb shell
pm disable --user 13 com.gsm.service.rcs
pm disable --user 13 com.google.ims
pm disable --user 13 com.android.service.ims.rcsservice
pm disable --user 13 com.android.ims.rscmanager
pm uninstall -k --user 0 com.qualcomm.qti.uceShimService
To find which is your elevated user
pm list users
and pick the higher user number
The offending package is called com.qualcomm.qti.uceshimservice.
My battery usage has never been so good, I've gone from 2 days to almost 4.
But, there are consequences, I don't get a 'delivered' notice on my SMS anymore and perhaps this rolls over to other messanger apps. I've tested Whatsapp and Telegram, eveything apears to be ok.
I might be doing something awful to the messanger and it would be great if someone could tell me what I've done, but so far I can live with it if I get my amazing battery back.
It could be to undo disabling the services you need to factory reset your phone, just sayin.
Edit: my fault if you were having problems copy/pasting these as I had not put a space inbetween User & 13. I have corrected it now, so copy/paste should work.
Sorry, I can not tell you what you did there, but what I can tell you is that on my device none of these packages exist (yes my id is also 13):
1|G8441:/ $ pm disable --user13 com.gsm.service.rcs
Error: java.lang.IllegalArgumentException: Unknown package: com.gsm.service.rcs
1|G8441:/ $ pm disable --user13 com.google.ims
Error: java.lang.IllegalArgumentException: Unknown package: com.google.ims
1|G8441:/ $ pm disable --user13 com.android.service.ims.rcsservice
Error: java.lang.IllegalArgumentException: Unknown package: com.android.service.ims.rcsservice
1|G8441:/ $ pm disable --user13 com.android.ims.rscmanager
Error: java.lang.IllegalArgumentException: Unknown package: com.android.ims.rscmanager
The qualcomm package exists, but as you said: No way to disable it...
package:com.qualcomm.qti.uceShimService
There is also a
package:com.google.android.ims
there, but like the qualcomm one, you can not disable this one, too.
My workaround at the moment is just to let the phone disable wifi in standby. This way I get like 4-5 days standby (+just a little bit usage).
pm uninstall -k --user 0 com.qualcomm.qti.uceShimService
did the trick @Didgesteve
This is working for weeks now.
nospherato said:
Sorry, I can not tell you what you did there, but what I can tell you is that on my device none of these packages exist (yes my id is also 13):
1|G8441:/ $ pm disable --user13 com.gsm.service.rcs
Error: java.lang.IllegalArgumentException: Unknown package: com.gsm.service.rcs
1|G8441:/ $ pm disable --user13 com.google.ims
Error: java.lang.IllegalArgumentException: Unknown package: com.google.ims
1|G8441:/ $ pm disable --user13 com.android.service.ims.rcsservice
Error: java.lang.IllegalArgumentException: Unknown package: com.android.service.ims.rcsservice
1|G8441:/ $ pm disable --user13 com.android.ims.rscmanager
Error: java.lang.IllegalArgumentException: Unknown package: com.android.ims.rscmanager
The qualcomm package exists, but as you said: No way to disable it...
package:com.qualcomm.qti.uceShimService
There is also a
package:com.google.android.ims
there, but like the qualcomm one, you can not disable this one, too.
My workaround at the moment is just to let the phone disable wifi in standby. This way I get like 4-5 days standby (+just a little bit usage).
Click to expand...
Click to collapse
Hmm, it worked for me, each line comes back 'Package "package name" new state: disabled'
I'm not sure that user 13 necessarily exists on other phones. You have to see what number your elevated user is and use that.
I checked the users before I used the commands, my user has also id 13, nur even of I do not use this option the return message is the same...
@shaftenberg
If I would deinstall the package and would need it later, how would I reinstall it?
I checked the users before I used the commands, my user has also id 13, but even if I do not use this option the return message is the same...
@shaftenberg
If I would deinstall the package and would need it later, how would I reinstall it?
with install
shaftenberg said:
pm uninstall -k --user 0 com.qualcomm.qti.uceShimService.
Click to expand...
Click to collapse
It won't let you uninstall, it's a system file. You need elevated access.
nospherato said:
I checked the users before I used the commands, my user has also id 13, nur even of I do not use this option the return message is the same...
@shaftenberg
If I would deinstall the package and would need it later, how would I reinstall it?
Click to expand...
Click to collapse
Are you using ADB shell from a command prompt on a PC, or an emulator on the phone?
Hi, I tested it too.
I got the same results as in #7.
I got my Packages with "pm list packages ?" copied it into notepad and searched for the rcs packages, found nothing.
This Package I haven't too: package:com.qualcomm.qti.uceShimService
The Result for "pm list users" is:
UserInfo{0:...:13} running
... shows my real name.
I'm using FW DE 8.49.
Best regards, mates.
@Didgesteve
I did my commands via ADB. It showed my user correctly and his ID.
Like Raz0Rfail I also copied the complete list into notepad and searched for the packages. Didn't find them there, too.
(Just the qualcomm one as mentioned. Also using FW DE 8.49)
@Didgesteve
I did my commands via ADB. It showed my user correctly and his ID.
Like Raz0Rfail I also copied the complete list into notepad and searched for the packages. Didn't find them there, too.
(Just the qualcomm one as mentioned. Also using FW DE 8.49)
@shaftenberg
Ahh okay, thanks
I thought I would need to download the install package or something like this. (Because uninstall would really "wipe" the package.)
Perhaps I need to check my spelling, but here is the results I got.
I did RCSService twice by mistake, but otherwise, they all show as disabled.
All,
You should be aware that the RCS and IMS services are required for VoLTE and VoWiFi.
So if you have disabled them, your VoLTE will not work.
I'll repeat my statement from here, that:
IMS is the "IP Multimedia Subsystem" and is used as the framework for telephony over IP based data connections. That's essentially what VoLTE is: VOIP for mobile phones.
I'll also note that RCS is the "Rich Communication Services" and is the successor to SMS and is essentially an extension of SMS and MMS as better described here.
So you're probably guaranteed to be breaking some advanced SMS/MMS features by disabling RCS services.
Yes, only I don't use VoLTE or VoWifi, and also my carrier does not really support RCS features... So in my case it's only extra battery usage for features I don't need or use
pbarrette said:
So you're probably guaranteed to be breaking some advanced SMS/MMS features by disabling RCS services.
Click to expand...
Click to collapse
Yes @pbarrette , you're right. But I have looked into this. I'm not suggesting that everyone starts deleting random system files on their phone.
Carrier services was rolled out by Google to try and claw back some of the market share of the messaging market.
It theory it brings group messaging, bigger pictures, read receipts and of course emojis to SMS.
Google realised that they were losing to the likes of Whatsapp and Telegram, but as usual it's too little too late.
I don't use group SMS messaging. Group messaging belongs in Whatsapp, obviously. I don't use emojis in texts. If I lose read receipts to claim back 20% battery, then that's a hardship I'll suffer.
I'm not sure what happened to the November update of carrier services, but I'm not alone in noticing HUGE battery drain from an app that I didn't ask for and don't want.
I've explained their might be risks, but for me, removing these services has made no difference to my SMS use and my battery is lasting longer. I'm just saying it like it is.