Hello,
I'm working for a telecommunications company in the UK, we are currently deploying a IMS / Volte solution, we have spoken to handset manufacturer vendors regarding the addition of our carrier configuration to support VoLTE, however this is proving difficult and long delays, I'm hoping someone is able to support us in editing or creating a new custom carrier configuration file with our specific parameters and settings,
We have access to various handsets, we have currently rooted a S9 and s9+ in the hope of creating these profiles but we can only view them, for example we installed EE UK CSC, but we can’t edit or add a new profile
Is anyone able to assist, your time and effort will be rewarded
Thanks, Regards
I feel for you, trying to get cooperation out of any of the manufacturers. One problem with what you're trying to do, though: Even if you were successful at modifying the rooted devices you have to accept your carrier IMS profile, that really won't help end users unless the manufacturer helps out. Whatever fix you would discover would no doubt require rooted access to the file system. That's something the vast majority of users won't be able/willing to do to apply the configuration.
I wish you the best. I can believe it's not easy to get them to help.
Thanks for the reply, it’s almost the chicken and egg scenario, we have completed installation of our IMS / VoLTE solution but need to test service, once we are confident on all the parameters and settings we need, we can provide this information to the manufacturers to add our carrier configuration to the OS, but the handset tech teams won’t be able to support until Q4 this year. Am I looking for a Google / Android developer for this?
Thanks, Regards
kieran_je said:
Thanks for the reply, it’s almost the chicken and egg scenario, we have completed installation of our IMS / VoLTE solution but need to test service, once we are confident on all the parameters and settings we need, we can provide this information to the manufacturers to add our carrier configuration to the OS, but the handset tech teams won’t be able to support until Q4 this year. Am I looking for a Google / Android developer for this?
Thanks, Regards
Click to expand...
Click to collapse
Ah, so then you're not looking to develop something for end users to deploy right now. You just want to get it working so you can tell the manufacturers what you need included in the stock OS. That makes way more sense. An Android developer would be useful, but mainly someone on the telecom side to know the parameters would be needed. It should just be editing stock configuration files, unless there's some weird authentication you need to do above and beyond the normal LTE stuff.
No. We're doing it in phases. We will allow inbound users on our network first. Then we'll open to our local customers after a period of time. We know what we need to configure to enable VOLTE, but we don't have access to those configuration files. Rooting obviously doesn't give enough access. Is there anyone online that would be able to support that you know off?
kieran_je said:
No. We're doing it in phases. We will allow inbound users on our network first. Then we'll open to our local customers after a period of time. We know what we need to configure to enable VOLTE, but we don't have access to those configuration files. Rooting obviously doesn't give enough access. Is there anyone online that would be able to support that you know off?
Click to expand...
Click to collapse
If there is, this would be the place to find them. Hopefully this is the forum. Sorry, I don't work for a manufacturer, or I'd help you out more directly.
BUMP, anyone able to support in this request. hoping to build a custom carrier configuration file to support a telecoms operator test VoLTE / IMS features
Thanks
kieran_je said:
Thanks for the reply, it’s almost the chicken and egg scenario, we have completed installation of our IMS / VoLTE solution but need to test service, once we are confident on all the parameters and settings we need, we can provide this information to the manufacturers to add our carrier configuration to the OS, but the handset tech teams won’t be able to support until Q4 this year. Am I looking for a Google / Android developer for this?
Thanks, Regards
Click to expand...
Click to collapse
I am interesting in this, i already pm you with my email . Let me know. thanks
If you know what files or folders you need to access, root does give you access. It sounds like you need to research some basic Unix commands and change permissions for the files/folders that you need to access. Root gives you full access to the entire system with super user (SU) privileges.
Related
Hi XDA Peoples,
I am a noob at android scripting and very new to modifying devices, however the company I work for is rolling out a lot of Samsung S3's and soon S4's to upgrade our device fleet ( we have 3500 employees). There are some settings that we change on devices like Owner information, screen timeout, Battery percentage being displayed, just some basic things. When setting up a few hundred devices manually though it can get tedious and a long process.
I am interested to know is it possible to create a script to modify these settings and run it via OTA or copy it to the phone and run it? I am not looking to root the devices as that would void our warranty and these are company devices. I am just looking to see if I can minimize the amount of manual handling I would need to do.
If people have references or knowledge they can share with me I would appreciate it
Thank you in advance I appreciate any help.
Hi,
Stock ROMs aren't really trustworthy by default (e.g., phandroid.com/2014/11/06/carrier-iq-settlement).
Some manufacturers' devices aren't really trustworthy, even with stock ROMs removed (e.g., theepochtimes.com/n3/830922-chinas-xiaomi-smartphones-may-be-spying-on-you).
Cyanogenmod went donwhill:
We may collect information such as occupation, language, zip code, area code, unique device identifier, location, and the time zone where your product or device is used so that we can better understand customer behavior and improve our products, services, and advertising.
Click to expand...
Click to collapse
(from cyngn.com/legal/privacy-policy) They started on this path long ago, but I won’t go there now.
I would like to buy a new Android phone. I won’t have national secrets on it, but I still don't want any Google-style spying. Assuming I don't add GApps, is AOKP a good choice for me? Does it respect the privacy of its users? Does it contain any components that would ever connect anywhere to trunsmit any information like GApps do. Obivously, I'm not talking about user initiated events.
One more thing, does it have a permission manager? Ideally, something that allows the user to choose for each permission for each apps whether real, fake or blank data is shared, but a bit cleaner than XPrivacy.
Thanks!
Howdy, folks. I hope someone can help answer this question. Mods, if I posted this in the wrong section, please relocate.
I'm helping a friend who is expanding his business by hiring 3 field sales reps and they need to be provisioned with smartphones and tablets for doing quotes, reviewing e-blueprints, accessing email, and so on. So, that's six devices in question, with more to come.
There's a question about whether iOS or Android is the better platform for what we're gong to need. Yes, I know XDA is Android-centric, but this decision isn't about what I want to do, but about what's right for his business. So, your honest input is appreciated.
Essentially, what I think we need is an ACL Management utility of some sort that will support these functions:
Remote access to configure devices in the field
Track and 'nuke' devices if lost/stolen
Remote backup of data/settings
Remote install/configuration of apps by managment
Enforce password protection
Good antivirus/malware/firewall software(?)
Prevent users from installing or deleting data/apps
Prevent users from changing settings
Though I have some technical skills, a 'dashboard' style interface to manage the devices and set a group policy would be preferred. I am aware of Android Device Manager, but I was unable to determine if it will do all of the above that we need.
If you think I've left anything out, please let me know.
Thanks in advance for your help!
Hi guys, not sure if this is the right place to do this but i've got a question i hope i can get clarified here with you experts
I am a PM that is in charge of a managing the delivery and development of a business's mobile application. Recently the company is looking to get rid of the incumbent developer due to unprofessional-ism and exorbitant fees. The other technology partner i am directly engaging with is a newly appointed development house and is tasked to clone the app and add additional features the incumbent refuses to add on.
Come launch date, the business requires the new app to replace the old app. To the existing customer base, the goal is to ensure that the transition is as seamless as possible. They are hoping that when existing users open the app, they will be prompted to install an update where the old one is then replaced with the old one. As such, is it possible for the new technology partners to this? What are the necessary steps required? I am trying to ensure that all necessary precautions and dependencies are covered to ensure any potential backlash / fallout. Is it as simple as obtaining the app certificate and ensuring the apk is named exactly the same? Any advice would be helpful.
The worst case scenario here would be to get the users to reinstall the app entirely or treat it as a completely separate app. :crying:
You need the signature keys of your first developer to sign the new APK which needs to have the same package name. And access to the dev console. Then you can upload the new app which will be treated as every other update by Google Play. Without changing the first app you won't be able to force the users to update AFAIK.
Fellhuhn said:
You need the signature keys of your first developer to sign the new APK which needs to have the same package name. And access to the dev console. Then you can upload the new app which will be treated as every other update by Google Play. Without changing the first app you won't be able to force the users to update AFAIK.
Click to expand...
Click to collapse
Hi thanks for the reply. Much appreciated! Would this be similar for iOS as well?
Relating to the last statement. What do you mean by "without changing the first app.."
androFRUST said:
Hi thanks for the reply. Much appreciated! Would this be similar for iOS as well?
Click to expand...
Click to collapse
I don't have enough experience with iOS to comment on that.
Relating to the last statement. What do you mean by "without changing the first app.."
Click to expand...
Click to collapse
While you can upload a new version of the same app the users would still have to manually (or automatically if their device is configured that way) download it. Google released a "forced update" API a while ago. If that is included in your old app that might help. Otherwise you would have to add it manually which would require access to the source code. But then the users would have to manually update too so it would be quite useless.
So one way to force them to update is to disable all APIs the app might use but that might alienate the users as they have no clue why it stopped working. So as long as you have no notification system that is working right now you have to depend on your users updating.
Please excuse me, but I've been looking for 3 hours now and, frankly, I'm now more utterly confused than ever - sorry
I am genuinely desperate to get back call recording to my S9 Plus for business purposes. I've seen that for some UK phones it is apparently now possible to record even with Pie but I can't, despite genuinely trying, find how I'd make that work.
It worked fine until Pie, so I fully understand I will have to go back to Oreo. I also understand I will have to lose all my data. I'll live with those little things. However, can someone PLEASE point me to:
oldest O2 UK Oreo firmware. I don't seem to be able to download from anywhere I've seen them advertised without 'signing up' to frankly dodgy looking sites
Instructions on how to actually do what I need to do
Thank you
Can help with part of your question...
The how to flash was posted at the link below. The instructions are actually pretty clear, they tell you what to do.. Click on the show content under the "how to flash the stock flashable odin firmware".
https://forum.xda-developers.com/showpost.php?p=75917820&postcount=1
Just be aware that you can only flash firmware that has a bootloader equal too or higher then what is installed on your phone right now. You can not flash firmware that has a bootloader version that is lower then what is currently on the phone.
To locate your bootloader version look under settings > about phone > software information > baseband version
Once you locate the baseband version count 5 characters in to the left (starting at the far right as character number 1). The number at the 5th character will be the bootloader version.
If you have a recently updated your phone to android pie then you will not be able to downgrade it to oreo... so from what I can tell if you installed android pie updates released after April 2019 you will not be able to downgrade to oreo
I used the link below to determine what firmware versions your looking for. Unfortunately I can not get the files you need, which is why I am only able to help with part of your request.
https://www.sammobile.com/samsung/galaxy-s9-plus/firmware/SM-G965F/O2U/
scottusa2008 said:
Can help with part of your question...
The how to flash was posted at the link below. The instructions are actually pretty clear, they tell you what to do.. Click on the show content under the "how to flash the stock flashable odin firmware".
https://forum.xda-developers.com/showpost.php?p=75917820&postcount=1
Just be aware that you can only flash firmware that has a bootloader equal too or higher then what is installed on your phone right now. You can not flash firmware that has a bootloader version that is lower then what is currently on the phone.
To locate your bootloader version look under settings > about phone > software information > baseband version
Once you locate the baseband version count 5 characters in to the left (starting at the far right as character number 1). The number at the 5th character will be the bootloader version.
If you have a recently updated your phone to android pie then you will not be able to downgrade it to oreo... so from what I can tell if you installed android pie updates released after April 2019 you will not be able to downgrade to oreo
I used the link below to determine what firmware versions your looking for. Unfortunately I can not get the files you need, which is why I am only able to help with part of your request.
https://www.sammobile.com/samsung/galaxy-s9-plus/firmware/SM-G965F/O2U/
Click to expand...
Click to collapse
Thanks Scott. I think.
I guess this is yet a further example of how consumers are being actively denied genuine choice whilst the companies tell us what is happening is in 'our' best interest. God help us.
I have read that Google are releasing new firmware updates to Pie for the UK that allows recording again. Does anyone know where I can get hold of it for my S9 plus please?
YorkshireDave said:
Thanks Scott. I think.
I guess this is yet a further example of how consumers are being actively denied genuine choice whilst the companies tell us what is happening is in 'our' best interest.
Click to expand...
Click to collapse
There's more to it then that, the updates we get contain security patches and the bootloader is always going to receive patches as well to curb vulnerabilities and etc.
If your phone is used for work they may have an IT policy that requires your phone to be updated as to be secure from vulnerabilities.. so I would check with them to be sure. Reason why i suggest this is because If your using call recording then the recording of customers calls would need to be kept updated so it's secure... If they don't have a policy then they should because it makes it that much easier for a data breach to happen running devices that are behind on patches/updates.
Maybe this will be of help to you in the meantime? You can use a PBX calling app with a voip provider (like voip.ms or one of the other ones). The PBX calling apps generally do have voice recording abilities that work really well. I ran my own PBX voice server with an older computer (used a voip provider for calling to/from landlines) to help filter spam calls, but I also recorded my calls since it was easier to remember important dates/info that way.
Also here's some info on the removal of the call recording API.. Originally it was done around android 6.0 for privacy reasons. It was the developers of 3rd party applications who found ways around the removal of the API to make call recording to work.. When Android Pie was released that the work around was patched. Also while our phone's are capable of native call recording, this is only enabled when it is allowed by your country/region/cellular provider (which is nothing Google can control).
In your case you could root your phone and modify it to accommodate call recording if you wanted (not sure if that is viable since you indicated your phone and a work environment).
Google has indicated they would like to return the api for call recording, but so far has only said it is on there roadmap. So I would hope someday they do but it doesn't look like it will be at the release of Android Q.
Link to the XDA article on Google adding call recording api back someday:
https://www.xda-developers.com/future-android-version-call-recording/
scottusa2008 said:
There's more to it then that, the updates we get contain security patches and the bootloader is always going to receive patches as well to curb vulnerabilities and etc.
If your phone is used for work they may have an IT policy that requires your phone to be updated as to be secure from vulnerabilities.. so I would check with them to be sure. Reason why i suggest this is because If your using call recording then the recording of customers calls would need to be kept updated so it's secure... If they don't have a policy then they should because it makes it that much easier for a data breach to happen running devices that are behind on patches/updates.
Maybe this will be of help to you in the meantime? You can use a PBX calling app with a voip provider (like voip.ms or one of the other ones). The PBX calling apps generally do have voice recording abilities that work really well. I ran my own PBX voice server with an older computer (used a voip provider for calling to/from landlines) to help filter spam calls, but I also recorded my calls since it was easier to remember important dates/info that way.
Also here's some info on the removal of the call recording API.. Originally it was done around android 6.0 for privacy reasons. It was the developers of 3rd party applications who found ways around the removal of the API to make call recording to work.. When Android Pie was released that the work around was patched. Also while our phone's are capable of native call recording, this is only enabled when it is allowed by your country/region/cellular provider (which is nothing Google can control).
In your case you could root your phone and modify it to accommodate call recording if you wanted (not sure if that is viable since you indicated your phone and a work environment).
Google has indicated they would like to return the api for call recording, but so far has only said it is on there roadmap. So I would hope someday they do but it doesn't look like it will be at the release of Android Q.
Link to the XDA article on Google adding call recording api back someday:
https://www.xda-developers.com/future-android-version-call-recording/
Click to expand...
Click to collapse
Hi Scott.
Whilst I mentioned 'work', it is my company so I control what goes on. Additionally, recording anything without informing the other party is perfectly legal in the UK so long as it is for personal use only. I even have a call recorded where the Information Commissioners Office told me this
As I am seriously desperate to record my calls, and my phone is now out of warranty, would you be kind enough to point me to a thread or two where I can find a well trodden and not too complicated rooting procedure pls?
YorkshireDave said:
Hi Scott.
Whilst I mentioned 'work', it is my company so I control what goes on. Additionally, recording anything without informing the other party is perfectly legal in the UK so long as it is for personal use only. I even have a call recorded where the Information Commissioners Office told me this
As I am seriously desperate to record my calls, and my phone is now out of warranty, would you be kind enough to point me to a thread or two where I can find a well trodden and not too complicated rooting procedure pls?
Click to expand...
Click to collapse
This thread deals with rooting the model you have.. perhaps it will be of use for you?
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974
Also the ability to add native call recording seems to be a csc feature tweak. Two ways you could try this:
1.) I am not sure if this still works or not, but you can try this. Edit the cscfeature.xml and add the following to it at the bottom:
Code:
<CscFeature_VoiceCall_ConfigRecording> RecordingAllowed </CscFeature_VoiceCall_ConfigRecording>
2.) Install a custom rom that has the feature as an optional addition. One rom I see mentioned often is this one
https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346
Others may have ideas too.. so before you do anything maybe consider waiting to see if others post ideas?