Related
I had asked this before but wasn't sure it could be done. Well now its been done for the EVO can someone please do this for the vibrant. This has become even more important to me now that vlingo is free.
Link to swype with voice for evo
http://forum.xda-developers.com/showthread.php?t=752040
Can that not work on our phone as well, its the beta that determines what phone you have.... PM the guy who made the edits and ask. I would think it would work fine.
I have tried installing it directly as an apk and the install fails. I have also tried renaming and copying over the current skype and this has no effect, aka the keyboard for skype remains unchanged.
I also went as far as to try the original droid x file with the above two methods and had the same results.
Apparently there are some dependencies or other files involved.
Anyone have any ideas?
If I'm not mistaken you are supposed to flash via recovery. I spent like 3 minutes looking at that thread.
Thanks I missed that as was working with the origonal apk file posted. Trying the zip now
Keep us updated, that looks awesome
Ok ran and installed the zip file and no change. No errors but same as when I copied over the skype file manually. The skype keyboard is unchanged. In my case still the grey smoke colored version from eugene's vibrant4 build.
Anymore ideas? I would really love to get this working but do not know enough to reverse engineer what was done.
adm1jtg said:
Ok ran and installed the zip file and no change. No errors but same as when I copied over the skype file manually. The skype keyboard is unchanged. In my case still the grey smoke colored version from eugene's vibrant4 build.
Anymore ideas? I would really love to get this working but do not know enough to reverse engineer what was done.
Click to expand...
Click to collapse
It would be nice if they shared what they did so we could try to reproduce it. I would love this mod combined with vlingo now that it's free, since Google's new stuff only works on 2.2.
I'll try to find time to download all the APKs from the various phones and see what's different. If you want to speed things up, send me links to all of them.
All I have is the APK file from the above posted link and I believe I have the original droid x apk for skype as well but it appears it is more then just the single skype file.
I have sent a pm to the creator in hopes he/she will share their secrets as to what has to be done to make this work.
adm1jtg said:
All I have is the APK file from the above posted link and I believe I have the original droid x apk for skype as well but it appears it is more then just the single skype file.
I have sent a pm to the creator in hopes he/she will share their secrets as to what has to be done to make this work.
Click to expand...
Click to collapse
Yeah, I thought we wern't supposed to share swype apks on here though, so I was wanting the original one from the droidx as well as the evo in addition to the one in the post you linked to. I can of course get the Vibrant one from my phone. Let me know if the other devs answer you and I'll try to help out.
http://www.androidpolice.com/2010/0...ent-on-samsung-galaxy-s-and-motorola-droid-x/
Does the i9000 have it? Maybe we can borrow their version?
Well.. what do you know? That EVO one works! Instructions..
backup your existing swype, just in case.
adb pull /system/app/Swype.apk swype-backup.apk
Change your keyboard to a different one, I just switched to the Android keyboard.
adb push swype-evo-tts.apk /system/app/Swype.apk
Now change back to swype. Mic button is now there and it works!
bug/oddness: The pop-up that shows you suggestions is now yellow with light text, it's damn hard to read some of them.
This fixes the word choice window to not be yellow anymore. I used the stock graphics files from the Swype that came with our phones.
Metamorph required, market.
Couldn't make this work no matter what I tried. Your directions were very good but they just didnt seem to work. I sent you a PM let me know what else to try.
adm1jtg said:
Couldn't make this work no matter what I tried. Your directions were very good but they just didnt seem to work. I sent you a PM let me know what else to try.
Click to expand...
Click to collapse
UPDATE
Got it all working now and while they keyboard is a little different all the voice functionality works perfectly. This coupled with vlingo makes for one awesome combination. Thanks to everyone for all your help.
Skype yellow fix locks up when trying to install and I cannot figure out where to copy the files manually it says to a skype directory but i dont see the directory in root explorer
adm1jtg said:
UPDATE
Got it all working now and while they keyboard is a little different all the voice functionality works perfectly. This coupled with vlingo makes for one awesome combination. Thanks to everyone for all your help.
Click to expand...
Click to collapse
Are you using vlingo for the voice button? I haven't tried to do that, it just brings up google's voice input app.
adm1jtg said:
Skype yellow fix locks up when trying to install and I cannot figure out where to copy the files manually it says to a skype directory but i dont see the directory in root explorer
Click to expand...
Click to collapse
You have to put them in the swype.apk. did you load it in metamorph? It's not an update.zip that you flash in recovery.
The screen looks the same as googles so maybe it interfaces with it but yes I hit the mic from the keyboard and speak and it works. I know it is somehow interfaced to vlingo as if I turn on filtering so I cant swear in vlingo setup then send a nasty text it filters it out. If i turn off word filtering in vlingo it sends the bad words.
ttabbal said:
You have to put them in the swype.apk. did you load it in metamorph? It's not an update.zip that you flash in recovery.
Click to expand...
Click to collapse
Ok I am clueless no idea how to make my own apk and not loaded metamorph. Any chance I could get you to prebuild it into a single apk for me?
If not then a link to the process or a step by step would be much appreciated.
Yesterday I got the mandatory Sprint Voice to text update. This really upset me as the main reason I rooted my phone was to get rid of the bloat ware. So now I have Sprint nagware to deal with. So today I installed and set up the Google Voice Mail program and it works really nice. So I decided to delete/uninstall the Sprint Voice Mail Program. I used Titanium back up and I deleted the program. Everything still works well so I figured it was gone and that was that. Later I looked in my app drawer and was surprised to see that the icon for the sprint voice mail was still there. So I tried to drag it into the garbage and it wouldn't go. So I go into root explorer and to to system>app and go down the list looking for a sprint widget that I needed to get rid of and didn't find one. I also made sure that the sprint voice mail program wasn't in there either. So I shut off the phone and started it again figuring that the program was still in memory. Well after the reboot the program is still on my phone and now it's acting like it's a brand new account and asking me if I want to set it up. So this comes to my question how do I get rid of the Sprint Voice Mail. I can't find it in my system folder so what's going on? Anyone else experience this???
Help is always appreciated............
Lisa
You can try to mount your system and remove it via Terminal Emulator. Its a pretty simple process with only a few commands if you want to have a go that route.
Sent from my HERO200 using XDA App
So what .apk am I looking for now? I couldn't find it with root explorer so it's technically gone but this thing is insidious........
mslisaj said:
So what .apk am I looking for now? I couldn't find it with root explorer so it's technically gone but this thing is insidious........
Click to expand...
Click to collapse
It's a system app, updatecore.apk or such
Not sure what updatecore.apk is but as you pointed out it's probably a big deal.
Driving home from work today I was thinking about all this and then it dawned on me that I didn't really delete the Sprint Voicemail app as I thought. Earlier I was using Titanium and I was about to delete the Sprint voice mail app when I realized that it was telling me it was going to delete "Data" only. So in reality I only deleted the Voicemail data and not the entire program. You are probably correct that this program is securely nestled within the core of the Android/HTC/Sprint package. Truly amazing as this may be one of those things that you cannot get rid of. Unless it resides in it's own .apk somewhere and I can target that one program I'm very hesitant at this point to go after it. The interesting thing about deleting the data is it seems to have reverted back to the older version. A box came up after I rebooted the phone asking me if I wanted to personalize my voice mail like I did the first time months ago. Plus being it's not technically "working" as it's not personalized the sprint genie can't target me for upgrade as it doesn't know I'm using it. What do you think of that idea?
So here is where I am. I have the Google voice mail working and it's a very cool little program. I have a "Google phone number" that is free and actually works but I don't have to do anything about it as my original phone number works the voice mail just fine. So in reality I may have beaten Sprint to at least a draw on this one................
So to recap, I would say, if you don't want the voice to text sprint app you could go into Applications and delete the "DATA" and then it doesn't know who you are. Just leave the sprint voice mail application in the "unsetup state" and the monster "Mandatory Update" can't find you. You have effectively turned off the sprint voice mail that way and then you can install a third party like Google voice mail or You mail or anything you want.
Give me you take on this idea. I think this is whats going on and this may be the only fix to opt out of the Sprint program.................
For future reference, all system (non-deletable) applications are located in /system/app. Use Root Explorer to go there and delete them. I think what he meant was to delete the Sprint Updater, which I think is Sprint_Updater.apk, also in that folder.
mslisaj said:
Not sure what updatecore.apk is but as you pointed out it's probably a big deal.
Driving home from work today I was thinking about all this and then it dawned on me that I didn't really delete the Sprint Voicemail app as I thought. Earlier I was using Titanium and I was about to delete the Sprint voice mail app when I realized that it was telling me it was going to delete "Data" only. So in reality I only deleted the Voicemail data and not the entire program. You are probably correct that this program is securely nestled within the core of the Android/HTC/Sprint package. Truly amazing as this may be one of those things that you cannot get rid of. Unless it resides in it's own .apk somewhere and I can target that one program I'm very hesitant at this point to go after it. The interesting thing about deleting the data is it seems to have reverted back to the older version. A box came up after I rebooted the phone asking me if I wanted to personalize my voice mail like I did the first time months ago. Plus being it's not technically "working" as it's not personalized the sprint genie can't target me for upgrade as it doesn't know I'm using it. What do you think of that idea?
So here is where I am. I have the Google voice mail working and it's a very cool little program. I have a "Google phone number" that is free and actually works but I don't have to do anything about it as my original phone number works the voice mail just fine. So in reality I may have beaten Sprint to at least a draw on this one................
So to recap, I would say, if you don't want the voice to text sprint app you could go into Applications and delete the "DATA" and then it doesn't know who you are. Just leave the sprint voice mail application in the "unsetup state" and the monster "Mandatory Update" can't find you. You have effectively turned off the sprint voice mail that way and then you can install a third party like Google voice mail or You mail or anything you want.
Give me you take on this idea. I think this is whats going on and this may be the only fix to opt out of the Sprint program.................
Click to expand...
Click to collapse
Product F(RED) said:
For future reference, all system (non-deletable) applications are located in /system/app. Use Root Explorer to go there and delete them. I think what he meant was to delete the Sprint Updater, which I think is Sprint_Updater.apk, also in that folder.
Click to expand...
Click to collapse
Yeah, that may be the actual name of the app, I don't remember Just delete the VVM app and problem solved!
theimpaler747 said:
Yeah, that may be the actual name of the app, I don't remember Just delete the VVM app and problem solved!
Click to expand...
Click to collapse
I meant delete the Voicemail app AND the updater. I believe the app is called Sprint_VM.apk.
Product F(RED) said:
I meant delete the Voicemail app AND the updater. I believe the app is called Sprint_VM.apk.
Click to expand...
Click to collapse
Ok.... I thought it was something VMCore.apk
I don't remember. I deleted it and put it back with the name "Sprint_VM.apk". Doesn't matter what it's named, but I think you're right about "VMCore.apk".
Okay Gentlemen, I have looked for all those files and the only one that is there is the Sprint_Updater.apk. Nothing there that has a VM or VVM or Sprint VVM or anything like that. I am running the .6 version of the Sprint stock 2.1. But I believe I have it disable for now. As I wrote previously by deleting the data file I have essentially not activated the program. If you do come up with the file to delete that would take the VVM with it I will certainly give it a try but there is nothing in the system>app folder that looks even close.
I so appreciate you taking you time to weigh in on this problem.
Thank you.........
Lisa
For the life of me I couldn't find what the apk was named -_- Was about to flash 2.1 to find out ha ha
Though I think Regaw's toolbox may allow you to remove it.
Sent from my HERO200 using XDA App
Nate14 said:
For the life of me I couldn't find what the apk was named -_- Was about to flash 2.1 to find out ha ha
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Just looked, it's:
Sprint_VVM.apk
mslisaj said:
Okay Gentlemen, I have looked for all those files and the only one that is there is the Sprint_Updater.apk. Nothing there that has a VM or VVM or Sprint VVM or anything like that. I am running the .6 version of the Sprint stock 2.1. But I believe I have it disable for now. As I wrote previously by deleting the data file I have essentially not activated the program. If you do come up with the file to delete that would take the VVM with it I will certainly give it a try but there is nothing in the system>app folder that looks even close.
I so appreciate you taking you time to weigh in on this problem.
Thank you.........
Lisa
Click to expand...
Click to collapse
See above, delete that to get rid of SVVM for good
Well Gentlemen, again I just went though that directory vary carefully again and there is nothing that even comes close to a VVM or "voice mail" reference at all. It's simply not there.
Have you guys deleted this off your phones before? I guess you all are running some other Rom then the stock one so you haven't faced this mandatory update thing. But the files you are suggesting to remove are not in that directory. As I mentioned the Updater is there in two versions Sprint Updater and just plane Updater.
I don't believe this issue is worth you flashing the stock rom just to check it but that is a real offer and I appreciate that. I admire you guys that flash these phones just for the heck of it. When I have flashed the phone it makes my heart stop.
But thank you for all your responses. I certainly appreciate it........
Lisa
mslisaj said:
Well Gentlemen, again I just went though that directory vary carefully again and there is nothing that even comes close to a VVM or "voice mail" reference at all. It's simply not there.
Have you guys deleted this off your phones before? I guess you all are running some other Rom then the stock one so you haven't faced this mandatory update thing. But the files you are suggesting to remove are not in that directory. As I mentioned the Updater is there in two versions Sprint Updater and just plane Updater.
I don't believe this issue is worth you flashing the stock rom just to check it but that is a real offer and I appreciate that. I admire you guys that flash these phones just for the heck of it. When I have flashed the phone it makes my heart stop.
But thank you for all your responses. I certainly appreciate it........
Lisa
Click to expand...
Click to collapse
I don't use stock, and yes I have been able to eliminate VVM.... did you reboot after deleting? Are you looking under system/app?
Yes to both of your questions.
I was thinking the same thing that maybe the program was still resident in the memory so I pulled the battery and everything. It's Sprints FU to the rooting community I guess...............
mslisaj said:
Yes to both of your questions.
I was thinking the same thing that maybe the program was still resident in the memory so I pulled the battery and everything. It's Sprints FU to the rooting community I guess...............
Click to expand...
Click to collapse
Still, it should be removable Is it hiding in data/app or data/app-private for some reason?
Okay, you guys aren't going to believe this. But I rebooted the phone and I checked the data/app and the data/app-private. Found nothing in there. Then I went back to the app drawer and the offending program is GONE! I can't find any vestige of it anywhere. So I gather mission accomplished! I don't know what happened as earlier I did the reboot twice and pulled the battery each time and the third time was the charm for some reason. The only file I didn't remove was the Sprint_updater.apk. It's still there. But I have turned off the updates so I shouldn't be bothered by that either..............
Thank you all for your help. The android mystery continues..........
I really can't thank you guys enough as you have always come through..........
Lisa
mslisaj said:
Okay, you guys aren't going to believe this. But I rebooted the phone and I checked the data/app and the data/app-private. Found nothing in there. Then I went back to the app drawer and the offending program is GONE! I can't find any vestige of it anywhere. So I gather mission accomplished! I don't know what happened as earlier I did the reboot twice and pulled the battery each time and the third time was the charm for some reason. The only file I didn't remove was the Sprint_updater.apk. It's still there. But I have turned off the updates so I shouldn't be bothered by that either..............
Thank you all for your help. The android mystery continues..........
I really can't thank you guys enough as you have always come through..........
Lisa
Click to expand...
Click to collapse
No problem! Glad you got it... let me know if you need anything else before I go to my Epic in a week or two
I've found a way to get the Republic Wireless app to work in custom ROMS, well at least CM11 & CM12 but I don't know why the method wouldn't work elsewhere. Currently I've been able to get the phone activated and I can send text messages in CM11 but phone calls do not work on either CM11 or CM12. Also, text messages show up as the "secret number" and not your actual number. The phone will show that it's getting signal but the MEID space is null in the Republic app. I'm sure there are things that I'm missing that need to be copied over for a fully functional ROM but here's what I've got so far.
In the build.prop:
#begin build properties
CHANGE
ro.product.name=
TO
ro.product.name=ghost_repw
#additional build properties
ADD THE FOLLOWING
ro.build.repw=true
That should be it for the build.prop
These you can copy and paste into your ROM. I recommend taking them from the RW Stock ROM.
system > app
RepWNetworkManager.apk
RepWNetworkManager.odex
RepWTrafficManager.apk
RepWTrafficManager.odex
I'm not sure if you need .odex and .apk, I copied both just in case.
system > etc > permissions
com.bandwidth.rw.system.xml
com.sprint.xml
system > framework
com.bandwidth.rw.system.jar
com.bandwidth.rw.system.odex
com.sprint.jar
com.sprint.odex
again, not sure if both are necessary.
system > priv-app
Republic.apk
If you change the build.prop, copy the needed files over and zip the ROM back up, you should have a functioning Republic app. If anyone has any ideas as to how to make this fully functional, feel free to post your ideas.
This is very interesting. I have been wanting to get custom roms on republic. Keep us up to date on your progress.
Is it possible to get a flashable zip?
Have you tried installing the RW Messaging and Dialer apks, as well?
The Mexinerd said:
Is it possible to get a flashable zip?
Click to expand...
Click to collapse
I don't have anywhere to host a file so unfortunately not.
Nicene Nerd said:
Have you tried installing the RW Messaging and Dialer apks, as well?
Click to expand...
Click to collapse
I'm not sure what those apks are. I wasn't aware RW had either of those.
I haven't done much with this lately because I can't seem to make any progress on it.
bstevens23 said:
I'm not sure what those apks are. I wasn't aware RW had either of those.
I haven't done much with this lately because I can't seem to make any progress on it.
Click to expand...
Click to collapse
RW had to modify both the Messaging and the Dialer apps in order to make them work with their WiFi calling system. Although I haven't compared them to the stock apps I suspect that if you do you will see that they are not the same.
It's occurred to me that even if we could get CM11 working properly, I doubt we could do so with any Lollipop ROM before the official update.
I've done further research by using the RW Dialer.apk and Mms.apk. Here are my findings:
Opening the Dialer or Messaging apps caused immediate FC.
Calls to my RW number came through, but could not be answered because the Dialer would FC.
By switching back to the CM Dialer, I could send and receive calls from the HSN (hidden Sprint number).
By installing a secondary texting app (i.e. Google Messenger), I could send/receive SMS with the HSN.
Also using a secondary texting app, I could send/receive MMS with my RW number (a peculiar result).
SMS to my RW number never came through at all.
Calls never seemed to work over Wi-Fi, but the MMS did, and some of the SMS might have.
From my research so far, it seems you could have a fully functional normal phone by using your hidden Sprint number in this method. You would lack the RW feature of Wi-Fi calling, though Wi-Fi MMS seems to work with your RW number.
glarepate said:
RW had to modify both the Messaging and the Dialer apps in order to make them work with their WiFi calling system. Although I haven't compared them to the stock apps I suspect that if you do you will see that they are not the same.
Click to expand...
Click to collapse
I'll have to look into the Dialer but I've used Messenger in CM11 and it mostly worked, but went to the Sprint Number. I'll try swapping out the messaging and dialer apps and see if that effects anything. I don't think just the apps would make a difference though as apps like Messenger do work on the RW ROM without modification. I'm betting, the messaging apps at least, are routed through a file(s) that I'm not aware of. I think one of the files I mentioned in my OP or something similar to them is what routes messages and allows it to work with WiFi. I know I'm missing something that makes the RW app/framework recognize my actual phone number/MEID.
Nicene Nerd said:
It's occurred to me that even if we could get CM11 working properly, I doubt we could do so with any Lollipop ROM before the official update.
I've done further research by using the RW Dialer.apk and Mms.apk. Here are my findings:
Opening the Dialer or Messaging apps caused immediate FC.
Calls to my RW number came through, but could not be answered because the Dialer would FC.
By switching back to the CM Dialer, I could send and receive calls from the HSN (hidden Sprint number).
By installing a secondary texting app (i.e. Google Messenger), I could send/receive SMS with the HSN.
Also using a secondary texting app, I could send/receive MMS with my RW number (a peculiar result).
SMS to my RW number never came through at all.
Calls never seemed to work over Wi-Fi, but the MMS did, and some of the SMS might have.
From my research so far, it seems you could have a fully functional normal phone by using your hidden Sprint number in this method. You would lack the RW feature of Wi-Fi calling, though Wi-Fi MMS seems to work with your RW number.
Click to expand...
Click to collapse
I've had similar results with my steps and using Messenger. I was able to send texts on CM11 and receive them but they were all through my Sprint # and the formatting was strange. I don't recall if I could make calls at all.
I think making it work on CM12 is possible. But I agree that it's not possible quite yet. Without a stock image to look through I have no idea how they've organized everything. I haven't checked in a few days, but if someone has been able to make a ROM out of the nandroid backup, I could decompress that, move the RW files over, recompress and attempt to flash it. I'm almost certain there's something I'm still missing, I'm just not sure what it is.
bstevens23 said:
I'll have to look into the Dialer but I've used Messenger in CM11 and it mostly worked, but went to the Sprint Number. I'll try swapping out the messaging and dialer apps and see if that effects anything. I don't think just the apps would make a difference though as apps like Messenger do work on the RW ROM without modification. I'm betting, the messaging apps at least, are routed through a file(s) that I'm not aware of. I think one of the files I mentioned in my OP or something similar to them is what routes messages and allows it to work with WiFi. I know I'm missing something that makes the RW app/framework recognize my actual phone number/MEID.
I've had similar results with my steps and using Messenger. I was able to send texts on CM11 and receive them but they were all through my Sprint # and the formatting was strange. I don't recall if I could make calls at all.
I think making it work on CM12 is possible. But I agree that it's not possible quite yet. Without a stock image to look through I have no idea how they've organized everything. I haven't checked in a few days, but if someone has been able to make a ROM out of the nandroid backup, I could decompress that, move the RW files over, recompress and attempt to flash it. I'm almost certain there's something I'm still missing, I'm just not sure what it is.
Click to expand...
Click to collapse
If it would help I think I have the 4.4.4 sbf files for RW.. all stock. If you want them pm me and I will upload them somewhere so you can get it!
poixninja said:
If it would help I think I have the 4.4.4 sbf files for RW.. all stock. If you want them pm me and I will upload them somewhere so you can get it!
Click to expand...
Click to collapse
I would love to see those.
Nicene Nerd said:
I would love to see those.
Click to expand...
Click to collapse
Ok uploading now to my gdrive.. it probably wont be done by the time I have to go to work, But I'll try to get you the link either on break, or after I get off!
Nicene Nerd said:
I would love to see those.
Click to expand...
Click to collapse
Here is the G-drive link to the 4.4.4 repw sbf
https://drive.google.com/file/d/0B3haitXafLKcZmpaZXg5R1h4Um8/view?usp=sharing
Really cool findings in here... I've wondered about this myself, and whether it might be possible to install CM in a rom slot and then use a global pre-paid sim card while traveling.
bstevens23, did you flash the CM image into a TWRP romslot or have you used sunshine to unlock and flashed over everything? I'm a little fuzzy on how the flash mem in the phone is actually partitioned up, especially when it comes to stuff like radio firmware vs. os partitions.... not sure what would work here.
Cool stuff!:good:
I saw this on reddit. As we know were also not allowed access on stock to the APN settings. There is a utility on f droid that gives you access the APN settings. There are about 15 various APNs that seem to be included that you can't edit, select, or delete. Likely these are chosen by the RW app.
It is too bad that there is not a utility that allows you to compare two roms and displays the differences
Sent from my XT1049 using Tapatalk
Looking into the data folder it would seem like w ebb might want to move over the shared press as well as looking through the xml files it calls out authentic devices for the RW apps. Perhaps this will allow the backend to interface with the rest of the Rw applications?
Sent from my XT1049 using Tapatalk
I wish it would work on moto g but that's wishful thinking.... Any progress???
So, looking at the logcat for mms, it looks like it crashes on loading or accessing MmsApp.java and MmsConfig.java
No idea how to fix tho
Sent from my XT1049 using XDA Free mobile app
poixninja said:
So, looking at the logcat for mms, it looks like it crashes on loading or accessing MmsApp.java and MmsConfig.java
No idea how to fix tho
Sent from my XT1049 using XDA Free mobile app
Click to expand...
Click to collapse
Have those been replaced with the RW versions?
Sent from my XT1049 using Tapatalk
Nooblet said:
Have those been replaced with the RW versions?
Sent from my XT1049 using Tapatalk
Click to expand...
Click to collapse
I haven't been able to find them.. Not sure where to look..
Sent from my XT1049 using XDA Free mobile app
Any ideas? On where those java files are?
Sent from my XT1049 using XDA Free mobile app
Can anybody tell me what this is? com.sec.vsimservice
Uknowdis said:
Can anybody tell me what this is? com.sec.vsimservice
Click to expand...
Click to collapse
I know replacing it removes the rcs and volte icons that show up after rooting. That's all I know tho lol. It has to do with data service I believe.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
I know replacing it removes the rcs and volte icons that show up after rooting. That's all I know tho lol. It has to do with data service I believe.
Click to expand...
Click to collapse
I was a lil nervous when i saw a notification for it...it was a devil face smiley lol. If it pops up again ill screenshot it
Uknowdis said:
Can anybody tell me what this is? com.sec.vsimservice
Click to expand...
Click to collapse
If I remember correctly that should have to do with video calling but not positive.
Sent from my SM-G935T using Tapatalk
Do we know anymore info on this? After rooting the s7 (at&t) everything was fine, accept sending texts through messeges failed. Then this notification came up, I could not remove it from notifications. I did a restart and got stuck in boot loop and had to factory reset. Now, I haven't finished root yet, but still on same rom and this has popped up again.
Skizzy034 said:
I know replacing it removes the rcs and volte icons that show up after rooting. That's all I know tho lol. It has to do with data service I believe.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Uknowdis said:
I was a lil nervous when i saw a notification for it...it was a devil face smiley lol. If it pops up again ill screenshot it
Click to expand...
Click to collapse
jds3118 said:
If I remember correctly that should have to do with video calling but not positive.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
i got the stupid devil faced notification too. its also from com.sec.vsimservice . I never had this before but it seems ever since i started using Digits from t-mobile.
I cannot remove it for the life of me and it doesnt matter what rom i am on. I tried clearing cache and data and also blocking notifications but i can still see it when i pull down the notifications. I get it right after i send a chat message using default samsung chat app. BTW im on the note 5 t-mobile.
EDIT: i found out that vsimservice stands for virtual sim service. Well it must be freaken t-mobile Digits beta program... =/ so annoying.
I started getting the devil notification after root on stock every time I get a voicemail. I can clear it like any other notification, it's just annoying.
monkeyass408 said:
i got the stupid devil faced notification too. its also from com.sec.vsimservice . I never had this before but it seems ever since i started using Digits from t-mobile.
I cannot remove it for the life of me and it doesnt matter what rom i am on. I tried clearing cache and data and also blocking notifications but i can still see it when i pull down the notifications. I get it right after i send a chat message using default samsung chat app. BTW im on the note 5 t-mobile.
EDIT: i found out that vsimservice stands for virtual sim service. Well it must be freaken t-mobile Digits beta program... =/ so annoying.
Click to expand...
Click to collapse
Anyone ever figure out how to get rid of. Not t-mobile as I'm AT&T. Also flashedvthe volt fix and he came back. I know something to do with messages but not out there on him that i found.
Mike the file nerd
I'm far from an expert at this but I could tell you how to avoid the problem in the future. I assume that if you have access to directories that contain system preconfig apps you must be running root privilege. Follow down the path to you're particular carrier. In my case I'm technically running on unlocked carrier but for the most part my phone still believes it is AIO(Cricket) ie boot still runs cricket sales code still runs as AIO. ECT. so in my example the file path would be /system/omc/AIO/etc. Inside your carriers file you will find several manifest (.xml) and text (.txt) files somthing along the lines of default_application_order.xml and/or enforcedskippingpackages.txt In my case on my s8 I have both. I haven't personally tried this yet so don't blame me if you try it and turn you phone into an 800$ paperweight (disclaimer) not to mention tampering xml is slightly outside of ethical phone use! That being said I'm of the opinion at least in my own case; if I pay for a device and don't have a contract against it i.e. I outright own the device I may set it up as i please. (Disclaimer) So ethics behind us. If I were to be experiencing this problem I would start by adding the problem pkg (...vsim...apk) whatever yours is called to the enforcedskipping.txt first (as it's slightly less unethical to change a text than a manifest) second find the system app either by an app like sysapp remover or like a real man inside the file system under probably something along the lines of "priv-app" dir or by superuser enabled terminals either abd via your computer/mac/linux whatever you run or by one of the many available terminals in the store of your choice and uninstall your problem apps (i highly suggest making a complete nandroid backup or tar or whatever recovery you use first and also saving a copy of the apk just in case) reboot your phone to recovery clear your cache partition remount the system and reboot. If this hasn't cleared up your problem back to recovery for a factory wipe with said modified files in place and backup ready. Reinstall everything then restore your backup via cmw/twrp/safestrap/bootstrap/odin/lgbridge/etc.etcetc whatever your preferred recovery method is your problem should be fixed. If still not mod the xml instead of the txt and restart from step one. Once again I do not know what dependency/gradles/etc may or may not depend on this what functions you may kill sim cards locked/ruined etc and I'm no professional so if you brick☠??? your ??that's on you for listening to an amateur enthusiast. Now I'm sure one of our wonderful experts here will come along and correct everything I've just said but I'm ok with this I listen to these guys every day I wouldn't know a fraction of the things I do without this wonderful forum and these amazing devs. So I appreciate their criticism as tutoring.
---------- Post added at 04:44 AM ---------- Previous post was at 04:38 AM ----------
With all that said and out of the way I would like to hear from anyone who has tried this personally or other method for removing this as I myself was led to this particular thread because I was investigating the possibility of what I could change within this particular system app myself. I brick my phone phone twice a day usually so before I crash my very well set up system I usually investigate first the reciprocation/ramifications of adjusting system orientated files/apps.
Has anyone attempted to use The Google Dialer and get call screening working? Wasn't sure if anyone had yet, but was curious. I'd gotten it working on my 6T and 7 Pro, but understand the development has been very different for our device.
champ784 said:
Has anyone attempted to use The Google Dialer and get call screening working? Wasn't sure if anyone had yet, but was curious. I'd gotten it working on my 6T and 7 Pro, but understand the development has been very different for our device.
Click to expand...
Click to collapse
I couldn't get call screening working granted I didn't exactly try that hard to get it working. Just systemized the dialer app and flashed Google dialer framework magisk module
Idk what else is needed to make it work.
I bet I can get it working. I remember a
the thread for the OnePlus 7 Pro about call screening, everyone said that it wasn't working, I had mine up and running without any problems. Currently I'm waiting for my unlock token from OnePlus, so I can't confirm if this method will work, but I'll tell you exactly what I did before and I don't see a reason why it shouldn't work now. Try it out and then let me know if it works or not. It doesn't, maybe we can come up with a workaround.
The version number of the dialer that you use is critical. New versions of the Google dialer from the Play store via Google Framework do not work. Here's the link to the APK that I used:
https://www.apkmirror.com/apk/googl...le-phone-39-0-270797297-android-apk-download/
The initial steps I performed were downloading the Magisk modules Busybox for NDK, Google Framework, and App Systemizer alongside installing Preferences Manager from the Play Store.
Then I cleared the storage for the stock dialer app, denied all of its permissions, and finally disabled it. Then I used App Systemizer to convert the Google Dialer into a system app. When App Systemizer gives you the option to install either the app as a 1 - system app or 2 - priv-app, always choose number 2. Then make sure to go into system settings and choose the Google Dialer as the default dialer app, otherwise icall screen won't work at all. Also go ahead and clear Google Dialer's storage while enabling all of it's permissions. Also go under Apps & Notifications in the system menu and choose special app access. Enable the Google Dialer to draw over other apps, modify system settings, and have usage access.
Next open up Preferences Manager. Grant it superuser access and from options choose "show system apps". Scroll down the list until you come to where you start seeing entries for "phone". On my old OnePlus 7 Pro, the one to choose was the first one listed as "phone". It didn't have an icon next to it versus the stock Dialer app which did. When you open this option up, swipe from left to right until you get to the heading "dialer_phenotype_flags.xml". First, choose backup under the menu in case there's a problem afterwards and you need to restore the flags to their previous settings. Then go to the search field and search for all the flags with "speak_easy", "speakeasy", "call_screen", and "callscreen", then update all of these flags with values of "true".
The way to determine if this procedure worked is to now open up ithe Google Dialer and choose the three dot menu and choose "Settings". You should see an option listed for "Call Screen". If you do see it then the process worked.
Let me know if you need any further information but I think that should work.
smreker said:
I bet I can get it working. I remember a
the thread for the OnePlus 7 Pro about call screening, everyone said that it wasn't working, I had mine up and running without any problems. Currently I'm waiting for my unlock token from OnePlus, so I can't confirm if this method will work, but I'll tell you exactly what I did before and I don't see a reason why it shouldn't work now. Try it out and then let me know if it works or not. It doesn't, maybe we can come up with a workaround.
The version number of the dialer that you use is critical. New versions of the Google dialer from the Play store via Google Framework do not work. Here's the link to the APK that I used:
https://www.apkmirror.com/apk/googl...le-phone-39-0-270797297-android-apk-download/
The initial steps I performed were downloading the Magisk modules Busybox for NDK, Google Framework, and App Systemizer alongside installing Preferences Manager from the Play Store.
Then I cleared the storage for the stock dialer app, denied all of its permissions, and finally disabled it. Then I used App Systemizer to convert the Google Dialer into a system app. When App Systemizer gives you the option to install either the app as a 1 - system app or 2 - priv-app, always choose number 2. Then make sure to go into system settings and choose the Google Dialer as the default dialer app, otherwise icall screen won't work at all. Also go ahead and clear Google Dialer's storage while enabling all of it's permissions. Also go under Apps & Notifications in the system menu and choose special app access. Enable the Google Dialer to draw over other apps, modify system settings, and have usage access.
Next open up Preferences Manager. Grant it superuser access and from options choose "show system apps". Scroll down the list until you come to where you start seeing entries for "phone". On my old OnePlus 7 Pro, the one to choose was the first one listed as "phone". It didn't have an icon next to it versus the stock Dialer app which did. When you open this option up, swipe from left to right until you get to the heading "dialer_phenotype_flags.xml". First, choose backup under the menu in case there's a problem afterwards and you need to restore the flags to their previous settings. Then go to the search field and search for all the flags with "speak_easy", "speakeasy", "call_screen", and "callscreen", then update all of these flags with values of "true".
The way to determine if this procedure worked is to now open up ithe Google Dialer and choose the three dot menu and choose "Settings". You should see an option listed for "Call Screen". If you do see it then the process worked.
Let me know if you need any further information but I think that should work.
Click to expand...
Click to collapse
Just finished trying this, worked like a charm! Thank you so much! This was the only thing making me consider going back to my pixel 3a xl, but now it's clear that you can have the best of both worlds!
Should we post this in the Mods category for this device? I know a lot of people would be happy to have this!
First off I'm so glad to hear that it worked for you! It's a pretty nifty feature and I personally think it's pretty cool.
To be honest with you, that was pretty much my first time ever posting anything to XDA. Most of the time I just go through the forums and tried to get new features to work on my phone, but hardly ever participate in the actual discussions
if you honestly think this could help other XDA members get this up and running, I'd love to help. But to be honest with you I'm not really familiar with starting a thread and stuff like that. If you don't mind, could you tell me what I need to do to do that? Is that like starting a new thread somewhere in the OnePlus 7T Pro McLaren edition discussions? I'm an absolute total new when it comes to posting and forums and discussion groups, and I have no idea what the protocol is for doing something like that. I'd really appreciate it if you could kind of guide me in the right direction or make some suggestions as to how I go about doing it.
Well, just to reiterate, I'm really excited that it work for you and hopefully we can get it to work for other people as well. Just respond to this message and let me know what I can do to help. Thanks again!
smreker said:
First off I'm so glad to hear that it worked for you! It's a pretty nifty feature and I personally think it's pretty cool.
To be honest with you, that was pretty much my first time ever posting anything to XDA. Most of the time I just go through the forums and tried to get new features to work on my phone, but hardly ever participate in the actual discussions
if you honestly think this could help other XDA members get this up and running, I'd love to help. But to be honest with you I'm not really familiar with starting a thread and stuff like that. If you don't mind, could you tell me what I need to do to do that? Is that like starting a new thread somewhere in the OnePlus 7T Pro McLaren edition discussions? I'm an absolute total new when it comes to posting and forums and discussion groups, and I have no idea what the protocol is for doing something like that. I'd really appreciate it if you could kind of guide me in the right direction or make some suggestions as to how I go about doing it.
Well, just to reiterate, I'm really excited that it work for you and hopefully we can get it to work for other people as well. Just respond to this message and let me know what I can do to help. Thanks again!
Click to expand...
Click to collapse
Personally, running a year old version of Google Dialer just to get Call Screen isn't worth it. Have you tested Call Screen to see if it actually fully works? Or if in reality the person calling hears nothing at all?
starcms said:
Personally, running a year old version of Google Dialer just to get Call Screen isn't worth it. Have you tested Call Screen to see if it actually fully works? Or if in reality the person calling hears nothing at all?
Click to expand...
Click to collapse
I've been running it with no issues on OOS and it works perfectly fine. Tested call screening and it works perfectly fine. Personally, I think it's worth it.
I'm running AOSiP now and I've yet to test it there. But OOS is confirmed to be working with it.
Has anybody been able to make it work on any of the custom ROMs? I tried smreker's steps on aosip but I couldn't get Google dialer to install. Just finished flashing lineage and aside from the fingerprints, this thing is running like it's good enough to say bye bye to oxygen.
raphi809 said:
Has anybody been able to make it work on any of the custom ROMs? I tried smreker's steps on aosip but I couldn't get Google dialer to install. Just finished flashing lineage and aside from the fingerprints, this thing is running like it's good enough to say bye bye to oxygen.
Click to expand...
Click to collapse
I'm getting ready to try it myself.. If I can get it working, I'll post about it here
champ784 said:
I'm getting ready to try it myself.. If I can get it working, I'll post about it here
Click to expand...
Click to collapse
Soooo.... Any luck ?? ?
raphi809 said:
Soooo.... Any luck ?? ?
Click to expand...
Click to collapse
I was testing today on aosip ROM and it did not work. The caller can't hear the Google assistant voice. I'm going to be looking into this more to see why it works on stock ROM, but not a customer ROM..
Aosip ships with Google dialer pre-installed, so you need to use debloat magisk module to uninstall it, and then reinstall it with the older APK file.. I may have messed up the installation on my end, so any other testing from other users would be greatly appreciated. I may reach out to the developers to see if they can figure out what I may be missing.
I never reinstalled another dialer app, so that could have something to do with it. However, I don't see why that would be the case, but you never know with these things. Thinking about it now, I didn't remove telophony apps on the phone either, so that could also have something to do with it? Any ideas?
https://forum.xda-developers.com/an...how-to-enable-google-call-t4150585?styleid=19
ih8legal said:
https://forum.xda-developers.com/an...how-to-enable-google-call-t4150585?styleid=19
Click to expand...
Click to collapse
Followed new instructions, option appears, but caller still can't hear and there's no transcription on my end :/
Currently running on AOSiP ROM, latest build (August)
champ784 said:
Followed new instructions, option appears, but caller still can't hear and there's no transcription on my end :/
Currently running on AOSiP ROM, latest build (August)
Click to expand...
Click to collapse
I'm trying to think of the different variables that could affect it, maybe something I did, that I didn't mention. Did you disable your stock dialer? Cause I tried it to today and it works super, transciptions and everything. Nothing should be different than the previous instructions, besides spoofing the device fingerprint. Maybe try disabling it and clearing data and then enabling it again?
Edit: I just read your previous posts. Never mind the stock dialer. This new method works with the latest Google phone update, so maybe try reverting your stock dialer back and then updating it?
ih8legal said:
I'm trying to think of the different variables that could affect it, maybe something I did, that I didn't mention. Did you disable your stock dialer? Cause I tried it to today and it works super, transciptions and everything. Nothing should be different than the previous instructions, besides spoofing the device fingerprint. Maybe try disabling it and clearing data and then enabling it again?
Edit: I just read your previous posts. Never mind the stock dialer. This new method works with the latest Google phone update, so maybe try reverting your stock dialer back and then updating it?
Click to expand...
Click to collapse
I'm on AOSiP which ships with Google Phone Dialer by default. Could that be my problem?
champ784 said:
I'm on AOSiP which ships with Google Phone Dialer by default. Could that be my problem?
Click to expand...
Click to collapse
That's a little beyond my expertise. I can only describe what I did, and those steps made it work for me. I haven't heard any other reports of it not working or working so we shall see. I'm thinking that the downloads for call screening are corrupted for you or something, if you're saying that the audio is not working, if you could clear that and start the process afresh?