Database Users

*2 and new froyo 2.2 update

Has anyone notice that when you call *2 from your phone that the sprint app starts. This is with the new update and im wondering how much info on your phone does Sprint have access to.

nunyabiziz said:
Has anyone notice that when you call *2 from your phone that the sprint app starts. This is with the new update and im wondering how much info on your phone does Sprint have access to.
Click to expand...
Click to collapse
Everything.
Sent from my PC36100 using XDA App

They don't keep all of your personal stuff, but all your hardware/software information and any data transferred over the network they technically have access to. Stuff you input on your phone and stuff on your SD card is generally safe. From a privacy stance, you have nothing to worry about. From a hacked phone stance, they possibly could figure it out, if they wanted to I suppose, but usually even that would be harder than its worth.
As for the *2 change, has nothing to do with what they have access to. They just had the dialer changed so that *2 redirected to the app rather than calling a predefined number. Easy to do, really.

When I did call *2 I got different prompt then before the update and it also shows that my firmware is FRF91 which is Froyo. How far and how much information will they get and use. If this would ever be the case, "Sorry Sir/Madam our system shows that you modified your phone so your warranty is now void". Don't get me wrong, I understood clearly before attempting anything that would void my warranty.

Again, it wouldn't be easy for them to figure out, if at all, but technically, they can access most of your version numbers. When you stick with stock roms, there's pretty much no changes in software versions, so almost impossible to tell. If you have a custom Rom, it shows in the software version, but I doubt Sprint would even notice that. Basically, there's nothing to worry about.
Sent from my PC36100 using XDA App

nunyabiziz said:
When I did call *2 I got different prompt then before the update and it also shows that my firmware is FRF91 which is Froyo. How far and how much information will they get and use. If this would ever be the case, "Sorry Sir/Madam our system shows that you modified your phone so your warranty is now void". Don't get me wrong, I understood clearly before attempting anything that would void my warranty.
Click to expand...
Click to collapse
The call center reps dont have access to all of that. It would have to be someone higher up who is looking for it.

I've installed the leaked unofficial Froyo ROM on friday and my *2 still calls the automated customer service. Sprint app does not launch. Oh, and just an fyi, i've never rooted my phone.

Lol, I deleted all of the Sprint apps besides Sprint TV, and when I dial *2, the dialer force closes.

cloud858rk said:
Lol, I deleted all of the Sprint apps besides Sprint TV, and when I dial *2, the dialer force closes.
Click to expand...
Click to collapse
to get *2 to work along with any of the manual inputs like ##775# you need to have sprint zone installed.

theebrownieee said:
to get *2 to work along with any of the manual inputs like ##775# you need to have sprint zone installed.
Click to expand...
Click to collapse
Can you post a link to the sprintzone.apk or post it here?
thanks

Lol I get the force close too... what is Sprint zone? I figured it was bloatware....

I installed Sprint Zone and still get an FC when I try to dial *2.
Any other suggestions?
Btw, here is the apk.

[Q] ATT S4 adds + to calls, making them fail

Hi everyone,
I've got an ATT I337 running the awesome Hyperdrive ROM version 17.1. Several of us --but clearly not all of us!-- over in that thread have noticed a problem with incoming calls. I think there's a setting somewhere that can fix it, so I'm opening it to a wider audience by posting it here, in hopes someone from this group will know what to tweak.
Here's the specific problem.
If my cell phone receives a call from a known contact "Bob" and Bob's contact info (being a U.S. phone number) is 317-555-1212, so far the phone seems to recognize the call as coming from Bob. However, it reports it as coming from +317-555-1212. When I go into the call log and try to return the call, it dials +317-555-1212, and the extra + causes the system to interpret it as an international call attempt, and the call fails. Cannot be completed as dialed, the message says. If it's an non-contact number, the + is still added. IT's not JUST for contacts.
Let's say Bob leaves a message. The voicemail indicator shows and it says offers to dial *86, the correct access code for voice mail for ATT as I understand it. However, tapping that actually dialed +11 then my ten digit phone number. Call fails.
At the dialpad, pressing and holding 1 to invoke voicemail has the same problem.
In Contacts, contacts are NOT listed with +s, and clicking the call button for them makes them dial OK without a + being prepended.
So, this looks like some international feature is being enabled that I'm not sure how to turn off. Does anyone have any idea how to turn this off? Sorta puts a crimp in the basic phone functionality. Seriously, who actually calls anyone these days? But it would be good to fix.
Please, if anyone has an idea of what might be at the root of this, I would appreciate your help!
Marc

I am confused. Does this only happen on the Hyper rom or all roms for you.
Not sure how anyone else does their contacts. But, I always enter numbers as 1-555-555-5555 even if local.
My voicemail number is set as +15555555555
I never had issues--
I remember some talk of that on Hyper awhile back. But, never paid attention--

Only happens on Hyperdrive. Or at least, I can say I never saw it on stock. Hyper is the only ROM I've actually gotten so far as to run while SIM card is inserted. :good:
My contacts are almost all US based and are just ten digits, no leading 1. I did try editing the contact to my work cell phone by adding a 1 to it, and calling my S4 phone. It still was registered as +317-555-1212 format and return call didn't work.
So, it's not really about the way the contacts are stored, more about how the phone interprets incoming calls.

Try the 1+ and see what happens. Just do a few of your most used numbers to start--
Can you put a different dialer on phone and see

rugmankc said:
Try the 1+ and see what happens. Just do a few of your most used numbers to start--
Can you put a different dialer on phone and see
Click to expand...
Click to collapse
Just edited above, adding 1 to the way contacts are stored doesn't change the behavior. I can certainly try a different dialer and see what happens, but it seems to be based on how incoming calls are interpreted. I'm guessing there's a build.prop item or somesuch that needs a-tweaking.
Marc

so you changed the contact number to 1-555-555-5555 with hyphens
i ran hyper for quite a bit awhile back never any issues. of course could be something new--
i am not thinking rom or a lot more would have issue--

I did some tests.
On the phone in question, I edited the google contact for a test phone number. I then called the phone from that tested phone number.
It didn't matter whether the contact was saved in the formats:
317-555-1212
1-317-555-1212
+1-317-555-1212
+317-555-1212
In all cases, the incoming call was recognized as +317-555-1212, which isn't a valid call-back number, and return calls failed. Since this only happened when I put a custom ROM on, I'm sure it's something buried inside the ROM. However, I'm at a loss as to where to check various settings.
Gotta be something deep in there...

If all else fails you can Odin back to stock, reformat your internal card and reroot.
Under Phone Settings/Additional Settings/My Phone Number--is it in format 15555555555
Also, and I don't know where to check, your country code may not be set. I don't know if we even have that setting anymore or would it be in Build Prop.
Probably under ro.something

rugmankc said:
If all else fails you can Odin back to stock, reformat your internal card and reroot.
Under Phone Settings/Additional Settings/My Phone Number--is it in format 15555555555
Also, and I don't know where to check, your country code may not be set. I don't know if we even have that setting anymore or would it be in Build Prop.
Probably under ro.something
Click to expand...
Click to collapse
Interesting thought. I had gone into the dialer settings, and checked the Current Country... it listed United States of America. Then I stopped. But looking further it turns out that in the Assisted Dialing settings just below that, there might be stuff that matters. Currently my assisted dialing is OFF. The settings inside are:
Country code: 1
IDD prefix: 011
NDD prefix 1
City/area code: 131
National number length: 11
The area code probably doesn't matter, but I'm interested in the national number length. Ours tend to be 10. Could you please see what your settings are in there, and let me know if anything is different?
I can always backup (ug, safestrap backup), return to stock, poke around, re-root/restore. But if you could take a quick peek I'd be grateful.
Thank you!
Marc
I tried an alternative dialer... it acted just like the stock with the + thing.

I am on a rom that doesn't have those settings--sorry

Thanks anyway! I experimented changing the last setting to 10, and enabling assisted dialing, and it didn't change anything. Sigh.

Ok, you can still go back to stock with Odin. Or, try one of iB's roms they are very good too, I use them almost exclusively now--
Good Luck--:good:

Yeah. I've been back to stock a couple times with Odin. I've got the process down pat! I prefer the hyperdrive rom if I can work through the few small warts. It's just such an elegantly crafted piece of work. Worth the effort, if I eventually sort out the call issue. Appreciate your help.
Sent from my SCH-I337 using Tapatalk

Frankenscript said:
Yeah. I've been back to stock a couple times with Odin. I've got the process down pat! I prefer the hyperdrive rom if I can work through the few small warts. It's just such an elegantly crafted piece of work. Worth the effort, if I eventually sort out the call issue. Appreciate your help.
Sent from my SCH-I337 using Tapatalk
Click to expand...
Click to collapse
i got the same problem too. We'll get it figured out!

Damani311 said:
i got the same problem too. We'll get it figured out!
Click to expand...
Click to collapse
I figured out the clock on status bar thing. Like someone else said it was under the alignment options ... hidden by default. One by one warts going away.
Sent from my SCH-I337 using Tapatalk

Have the same issue here ..can't dial vm..on hyper
Sent from my SCH-I545 using XDA Premium 4 mobile app

jshua said:
Have the same issue here ..can't dial vm..on hyper
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you haven't done so yet i suggest noting the issue in the hyper thread ... either the Verizon or att one depending on your phone. Seems to be a bunch of us... more folks report it the common thread will emerge.
Sent from my SCH-I337 using Tapatalk

Same issue here i can not dial voicemail and can not call a number back without typing the number in manually. Deal breaker for me hope it gets fixed soon so i can go back to Hyperdrive. Or somebody comes up with some sort of fix.

Download Prefixer and remove the + for outgoing call

BBG037 said:
Download Prefixer and remove the + for outgoing call
Click to expand...
Click to collapse
When I get back from vacation I will have to try this. Thanks!

Need package info

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.

sprint voicemail on the 935U software

Hey, any of you root people, could you pull the voicemail apk off your phone so I can use it with my flashed universal phone? Have tried the s6 edge software but no go. Thank you

This is simple through titanium backup. No one?

The one on official firmware will not install correctly. But this is an older one that works. Download and install like normal.
https://mega.nz/#!z5sAiJKK!Ig_iEGEqYMTXfm-yRPmvsC05pgiKYlEPvonlpqXuVwk

It work for you on the U firmware?

heathmcabee said:
It work for you on the U firmware?
Click to expand...
Click to collapse
Yes.

Thanks again seems to be working

Once you set up, it may take a while to actually activate. I just left the app, came back to it 5-10 min later, and it was running normally.

Ya took me almost an hr. Worked well though. Downloaded many that didn't work. Just needed 1 that did.

It doesn't appear to actually work. You all just think it is.
If you leave a vm it wont download it (or mine doesn't seem to).
If you go into settings and pref, it shows it's not verified still also. You just stopped seeing the prompt because once the screen times out it is no longer on top but if you fully kill the app and re-open it still says verifying.
These are my findings at least? If you go into settings and pref does it say you're verified?

Yeah I couldn't get it to work either

Didn't work for me either

Try this one it worked for me on my unbranded piece o sh!t locked bootloader s7 edge with the added ticking timebomb feature.
Link vvm
On a side note samsung got what they deserve for [email protected] us usa s7 owners. I hope they lose tons of money

brendan802 said:
Try this one it worked for me on my unbranded piece o sh!t locked bootloader s7 edge with the added ticking timebomb feature.
Link vvm
On a side note samsung got what they deserve for [email protected] us usa s7 owners. I hope they lose tons of money
Click to expand...
Click to collapse
No dice, didn't work for me either... Did you do anything special to install it?

brendan802 said:
Try this one it worked for me on my unbranded piece o sh!t locked bootloader s7 edge with the added ticking timebomb feature.
Link vvm
On a side note samsung got what they deserve for [email protected] us usa s7 owners. I hope they lose tons of money
Click to expand...
Click to collapse
Thanks seemed to work. Finally got account verification

heathmcabee said:
Thanks seemed to work. Finally got account verification
Click to expand...
Click to collapse
Are you sure?
I've got the same issues all the others did. It can't activate. Just because it stops popping it up doesn't mean it's activated now either. That message suppresses after a while.
It seems to tie into something that it and Sprint Zone use from what I can tell and thus why won't work on these non-branded firmwares.
Leave yourself a VM and see if it shows up...

It usually wouldn't go past the account verification at all. I'm not 100 %sure yet. But it did go farther than before and I'm trying it out now to verify. Will get back

If you press home and go back into it the app will hide the message but it still wont work.
I actually found the outbound activation messages in it that are failing to send even.
So this is another bust.
I think our best luck is if someone can either reverse eng. this thing to modify it to not try to use whatever sprint bloat it's looking for or we find what it's looking for and find a way to put it on our phones.
Sadly it's not a new issue. All the Nexus people have had the issue from day 1. And it seems to be only sprint because they won't make a darn public compatible app.
I can't use GVoice as I already use it for a second number and I don't like any of the third party ones that make you use conditional call forwarding to them to do this...
Another question for you all. I've noticed if NO voicemail app is installed I do not get any notification I have voicemails. If I do install one (despite it not working) I get notified because it says pending voicemail download at least.
With no VM App installed are your phones telling you that you got VM?

Yeah same boat here man. Looks like we beating a dead horse

Yea, Sprint should upload visual voicemail to the Play Store like T-Mobile does. So stupid.
Sent from my SM-G935U using Tapatalk

Can anyone post the Sprint VM app for Nougat?
Sent from my SM-G935U using Tapatalk

Unknown new app installed through LG Service Center Update - DrAPN_N

A few hours ago I received a notification on my Sprint LG V20 that an app was updated. Upon closer inspection I found that it was actually a new app installed through the LG Update service center or "LGinstallservice" i.e the one that updates LG's stock proprietary apps like Qmemo and their Clock app and so forth.
The app is called DrAPN_N and it installed itself as a system app. It is currently and has been running in the background process of my phone since that time.
A quick Google search only yielded a Reddit thread with a few more confused LG users with a couple different LG devices that had received the same app on their device (a few posts from today and some a few days back).
My guess (and big emphasis on the word guess) is that it's some sort of hotfix that updates the apn info that sprint has them lock down and isnt editable to a user without modifications, hence the name "Dr. APN". If that's the case I'd be curious what it changes and why. I also just remembered Sprint was doing some spectrum modifications on their old 2g network (or something like that) and realize now that it could have something to do with Sprints repurposing to increase coverage in rural areas. I forget what they are calling that rollout but that along with the name kinda equals my best guess on all of this as of now.
Screenshot below. Thanx for any input or info.

My stock unrooted TMobile variant just got that yesterday. I was wondering what it was.
I remember seeing DRapn. So i guess it's not just a Sprint thingy.

I got this app yesterday. I'm using a sprint v20, but not on sprint or in America. Previously I had been using Textra to use custom APN settings to get MMS working, and it had been fine. But upon installation of this app, those custom changes were no longer applied. Reapplying them has no effect, and now, though sms and call still functions, MMS does not. If this app represents an attempt to lock down custom APN usage, that would be distressing but would explain my failure to get MMS working now despite my efforts. I'm still looking for (an unrooted) solution to uninstall or work around this app. (I would root but am on the latest firmware and don't believe it's rootable right now, though I haven't checked in a while.)

This app just installed on my Sprint LG G5 about an hour ago and I called LG support about it. They didn't have an answer for me, but they said they would call me back when they had an answer. I'll post anything I find out here.

The app installed on my phone today. LG V20

If someone can post the apk, it could probably be disassembled to see what it does... Otherwise everyone's making guesses

DrAPN_N
It just intalled itsself on my rooted sprint v20, link to apk:
https://drive.google.com/file/d/1-R7ZSHt-19Bl2XJvV9sANjWsEdat8rb-/view?usp=drivesdk
Uninstalling it and disabling the LG service that installed it now. :good:

I thought I would add that (as this app was making it impossible for my APN settings to be retained longer than a few minutes on my sprint lg V20 being used outside USA) I set about to disable it. The disable button was greyed out so I denied it permissions to change system settings and deleted its cache. To my suprise it still had the effect of undoing my APN settings. So I disabled it via ADB, and that did the trick. Been using the phone for 24 hours since and noticed no issues.

ADB?
Thusthusthus said:
I thought I would add that (as this app was making it impossible for my APN settings to be retained longer than a few minutes on my sprint lg V20 being used outside USA) I set about to disable it. The disable button was greyed out so I denied it permissions to change system settings and deleted its cache. To my suprise it still had the effect of undoing my APN settings. So I disabled it via ADB, and that did the trick. Been using the phone for 24 hours since and noticed no issues.
Click to expand...
Click to collapse
Can you please explain how you did the process through ADB? I'm in need of doing this myself...thanks

posvar8 said:
Can you please explain how you did the process through ADB? I'm in need of doing this myself...thanks
Click to expand...
Click to collapse
This link explains the process.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/

Thusthusthus said:
I thought I would add that (as this app was making it impossible for my APN settings to be retained longer than a few minutes on my sprint lg V20 being used outside USA)
Click to expand...
Click to collapse
according to LG , this app is supposed to determine and program APN automatically based on inserted SIM.
Would be nice if it had a GUI to disable itself. Do you have non-Sprint APN? What happens to your APN settings? do they reset back to sprint?
Does new APN gets unselected? deleted?

leond said:
according to LG , this app is supposed to determine and program APN automatically based on inserted SIM.
Would be nice if it had a GUI to disable itself. Do you have non-Sprint APN? What happens to your APN settings? do they reset back to sprint?
Does new APN gets unselected? deleted?
Click to expand...
Click to collapse
Thanks for that information.
I do have a non Sprint APN. I'm using a Sprint phone outside USA. I had had to set my phone to expect an AT&T connection, in a secret dialer menu, to get it fully working. (I described the process above.) I expect my weird set up did something Drapn was not expecting, causing it to mess up the issue it was meant to address.
Forgive this lengthy reply, but I'll leave it in case others have the same problem. Before this Drapn issue, just editing APN in regular stock android settings, while it allowed most data to work, and sms, would not allow MMS or certain kinds of messaging, like WhatsApp or Facebook Messenger. I have no idea why, though I did find other users online with the same problem using sprint phones outside America. Eventually I fixed the problem by marking the phone AT&T in the secret dialer menu, as described in my previous post in this thread. At that point the APN settings took hold. Until Drapn was installed, which perhaps got confused between the Sprint/AT&T/My Carrier settings. I could input APN settings into the stock android system settings, and sometimes it would work initially (other times, if I edited too many fields, the entry would vanish after I saved it) but always it would stop working after a few minutes or at least inside an hour. Had I factory reset the phone, and attempted my modifications from scratch with Drapn installed, perhaps it would have worked fine. Then again perhaps the necessary changes would have been impossible to implement.
I am not sure what APN settings Drapn was reverting me to. My custom entry would either remain but stop functioning, or else be deleted, and also stop functuoning. All I know is that nothing worked until I disabled Drapn with ADB, having deleted its cache and revoked its permissions.
Because I was using a phone modified within a secret dialer menu, I don't figure I can get 100% mad at LG for pushing an app that borked my phone. You play with fire you get burned, etc. Then again, pushing an app with no transparency as to what it does, and no freedom to disable it, is certainly not the best. I suppose now I have to worry if accepting the Oreo update will reintroduce this issue and leave my phone inoperable outside the USA.

Thusthusthus said:
Because I was using a phone modified within a secret dialer menu, I don't figure I can get 100% mad at LG for pushing an app that borked my phone. You play with fire you get burned, etc. Then again, pushing an app with no transparency as to what it does, and no freedom to disable it, is certainly not the best. I suppose now I have to worry if accepting the Oreo update will reintroduce this issue and leave my phone inoperable outside the USA.
Click to expand...
Click to collapse
check out the LG V30 threads. this is exactly what happened there. Unlocked by sprint phones became locked again after Oreo update. And if you are no longer on Sprint network you are stuck. So yes, you have all the reasons to worry.

leond said:
check out the LG V30 threads. this is exactly what happened there. Unlocked by sprint phones became locked again after Oreo update. And if you are no longer on Sprint network you are stuck. So yes, you have all the reasons to worry.
Click to expand...
Click to collapse
Yikes. Thanks for that. Just read through a big thread, what a mess. Looking like I'll likely be trapped on Nougat. Much appreciated, at least I didn't find out the hard way.