Is there anyone working on this?
Or close to being done?
ForceRom has them on the to do list.
But im not sure on progress.
anyone have any updates?
Also I know some international roms have in app call recording toggle, is there anyway to port that for sprint? I dont see why it wouldnt work since it has nothing to do with the phone radio. Im guessing it the rom it will just be the secphone.apk? If someone confirms that ill give it a shot and report back.
I, too, really want the Call Recorder function but it seems like either no one on the Sprint side knows how to implement it or don't care enough about it. I know the Wanam rom for the i9505 has Call Recording enabled. You could flash that rom & get it. Just follow the tutorial for installing ROMs from other S4's to our S4.
optimummind said:
I, too, really want the Call Recorder function but it seems like either no one on the Sprint side knows how to implement it or don't care enough about it. I know the Wanam rom for the i9505 has Call Recording enabled. You could flash that rom & get it. Just follow the tutorial for installing ROMs from other S4's to our S4.
Click to expand...
Click to collapse
do you have a link to that to tutorial?
So I decided im going to try using thee Wanam Lite secphone.apk, and push it to Force Rom.
I am downloading Wanam right now, so when I get done ill report back and let yall know if it worked or not.
It will be super awesome if this works, because I know many sprint users would love to have call recording,
and this should be a pretty simple process.
com.sec.phone kept crashing over and over. and I had no signal.
shuld I get the com.sec.phone from wanam also?
Another Sprint S4 user had success & got Call Record working by flashing the entire Wanam ROM. The tutorial has been deleted, it seems. If I remember correctly, you're supposed to flash the Wanam ROM then flash a Sprint S4 kernel right after in the same session.
Perhaps create a nandroid first then try? If I remember that user's name, I'll let you know or maybe he'll chime in here.
optimummind said:
Another Sprint S4 user had success & got Call Record working by flashing the entire Wanam ROM. The tutorial has been deleted, it seems. If I remember correctly, you're supposed to flash the Wanam ROM then flash a Sprint S4 kernel right after in the same session.
Perhaps create a nandroid first then try? If I remember that user's name, I'll let you know or maybe he'll chime in here.
Click to expand...
Click to collapse
I dont mind flashing it, but the thing is i saw a thread talking about it and apparently people still couldnt get data after, even after they flashed the sprint kernel. Also read it needs to be a touchwiz kernel.
i flashed it, and its working great. everything works on it except for data.
so can anyone help me out with the apns?
and where do I enter the apn settings on the gs4?
chase357_501 said:
i flashed it, and its working great. everything works on it except for data.
so can anyone help me out with the apns?
and where do I enter the apn settings on the gs4?
Click to expand...
Click to collapse
Exactly
I posted this in another thread, not sure if it works. My guess is that you'd have to copy the settings from a Sprint ROM and then manually input them after flashing an I9505 ROM.
http://www.phonebuff.com/2012/07/configure-apn-settings-for-android/
You should be able to get to some if not all of those settings, by dialing ##3282##. You will need to enter your MSL number. There is a thread here in the Sprint forum, on how to get your MSL. I used, get my MSL from Gplay and it worked. Just follow the directions Once in, right down all of the settings and then put those settings in, once the different carrier's rom is installed. Good luck, and let us know the outcome
cerj said:
You should be able to get to some if not all of those settings, by dialing ##3282##. You will need to enter your MSL number. There is a thread here in the Sprint forum, on how to get your MSL. I used, get my MSL from Gplay and it worked. Just follow the directions Once in, right down all of the settings and then put those settings in, once the different carrier's rom is installed. Good luck, and let us know the outcome
Click to expand...
Click to collapse
1st of all, my main problem, was finding the apns in the wanam rom. I was able to find them in the sprint rom, because ##data# works. but when you go to the i9505 rom, that dial code does not work. I actually ended up getting access to the aps by using an app from gplay, called offline sim apn database. it has an option that opens up your apn list, and from there you can edit them, so I took all 4 of my sprint apn's, and entered them. there was 2 lte apn's and 2 ehrpd apn's. Well after high hopes, that was all I had. nothing happened. so there is definitely more than just entering apn's. I messed around with *#0011# for like 2 hours, trying to figure something out, but I got no results. so imo, we will just have to wait til something gets figured out. I personally am stuck for now,
chase357_501 said:
1st of all, my main problem, was finding the apns in the wanam rom. I was able to find them in the sprint rom, because ##data# works. but when you go to the i9505 rom, that dial code does not work. I actually ended up getting access to the aps by using an app from gplay, called offline sim apn database. it has an option that opens up your apn list, and from there you can edit them, so I took all 4 of my sprint apn's, and entered them. there was 2 lte apn's and 2 ehrpd apn's. Well after high hopes, that was all I had. nothing happened. so there is definitely more than just entering apn's. I messed around with *#0011# for like 2 hours, trying to figure something out, but I got no results. so imo, we will just have to wait til something gets figured out. I personally am stuck for now,
Click to expand...
Click to collapse
If you decide you really want to do it, check around XDA for Rom porting threads. There are a few easy to follow TUT's on this. They may just get you where you wanna be
Stock TW has a flashlight widget called "Assistive Light" that is built in and super quick.
Sent from my SPH-L720 using Tapatalk 2
For a flashlight toggle, I'm using "Mappz Quick Settings" from Play Store. It gives you AOSP-style Quick Settings tiles, including one for Torch, that you get by pulling down from the center of the top. If you pull down from the top left or top right you get the regular TW Quick Settings and Notifications.
The "Torch" moment's likely csn be interested into the Lockscreen and prolly added to the notification tray. I'm hoping to finish the toggle for turning on/off the am/pm & Time today. I'll look I to the Torch toggle this afternoon.
Sent from my SPH-L720 using Tapatalk 2
Related
I have never seen this before, and I am hoping someone knows what to do.
After installing Hyperdrive 17.1 when i receive a phone call it will display +1(and the number) even if I have the person as a contact, then if i want to call back i have to remove the + sign before trying otherwise it simply won't do anything. I am not saying this is an issue with the rom (and I really doubt it) maybe something i am missing.. Any idea?
After doing some more research this seems to be related to the Global ready settings, but I can't find how to disable this.
genesiss said:
I have never seen this before, and I am hoping someone knows what to do.
After installing Hyperdrive 17.1 when i receive a phone call it will display +1(and the number) even if I have the person as a contact, then if i want to call back i have to remove the + sign before trying otherwise it simply won't do anything. I am not saying this is an issue with the rom (and I really doubt it) maybe something i am missing.. Any idea?
After doing some more research this seems to be related to the Global ready settings, but I can't find how to disable this.
Click to expand...
Click to collapse
I get a 1 before it too but no +1 and the call back function works fine ... Im on RLS17.1 also ... My phone is unlocked and I am using tmobile but I was using att just a few days ago and it wasn't a problem .. must be something you need to change in your network setting (Possibly)
spirodave said:
I get a 1 before it too but no +1 and the call back function works fine ... Im on RLS17.1 also ... My phone is unlocked and I am using tmobile but I was using att just a few days ago and it wasn't a problem .. must be something you need to change in your network setting (Possibly)
Click to expand...
Click to collapse
Still looking, but i had to change roms.. unfortunately..
genesiss said:
Still looking, but i had to change roms.. unfortunately..
Click to expand...
Click to collapse
That sucks ... I would put a post in the Hd thread with this issue .. sbreen is good about answering and fixing .. Im a safestrap user and there is really no other rom that I want to use ... Although they are all good HD has more functions without the need to install xposed framework .. Also the 4way multiwindow is the sh!t... Hats off to all the developers
Several of us with hyperdrive are seeing this. See recent posts in the hyperdrive att rom thread. I started a general q&a thread about it in hopes of finding solution, figuring it is a setting not just specific to that ROM. I hope a solution is found because I like that ROM.
Marc
Sent from my SCH-I337 using Tapatalk
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!
Hey guys I have a rooted LG v20 vs995 I cant make calls or send text messages I can receve texts just not senf them I have metro pcs is my service provider how can I fix this and help is greatly appreciated thank you for taking time out of your busy life to help a newbie
Saldivar said:
Hey guys I have a rooted LG v20 vs995 I cant make calls or send text messages I can receve texts just not senf them I have metro pcs is my service provider how can I fix this and help is greatly appreciated thank you for taking time out of your busy life to help a newbie
Click to expand...
Click to collapse
Check you have correct apn settings
Still_living714 said:
Check you have correct apn settings
Click to expand...
Click to collapse
I just tried 3 differnt apns and still cant send text messages
Saldivar said:
I just tried 3 differnt apns and still cant send text messages
Click to expand...
Click to collapse
(Update) fixed the calling and texting but now I dont have 4g lte
Saldivar said:
(Update) fixed the calling and texting but now I dont have 4g lte
Click to expand...
Click to collapse
Where are you getting your apn settings from? Make sure there the right ones
Still_living714 said:
Where are you getting your apn settings from? Make sure there the right ones
Click to expand...
Click to collapse
https://bestmvno.com/apn-settings/metropcs-apn-settings/ from here thats where I got my 3 apns from
Saldivar said:
https://bestmvno.com/apn-settings/metropcs-apn-settings/ from here thats where I got my 3 apns from
Click to expand...
Click to collapse
try this
http://apn-settings.com/us/metropcs-apn-settings-step-by-step-configuration/
Still_living714 said:
try this
http://apn-settings.com/us/metropcs-apn-settings-step-by-step-configuration/
Click to expand...
Click to collapse
When I try to change the mnc it wont resterger the apn its set to 260 and if I try to change it the apn wont save and now my 4g lte is just and E
I am rooted is there anything that I can flash or install to trick my phone so I can have 4g lte
Saldivar said:
When I try to change the mnc it wont resterger the apn its set to 260 and if I try to change it the apn wont save and now my 4g lte is just and E
I am rooted is there anything that I can flash or install to trick my phone so I can have 4g lte
Click to expand...
Click to collapse
Not sure if this will help 100%, but I am sure i can't hurt.
Since you're rooted you can go ahead and install this by flashing the zip in recovery.
After you have booted back up, open the new incall modz control app.
Then hit the three lines on the top left to open the control menu options.
Scroll down and click the advanced hidden menu section.
This section opens up several hidden menus.
You can look through and see what may give you the options you're looking for.
I suggest using the "apn unlocking" to give you access to edit the apn setting.
You can also play around in the "phone testing menu" section and look within the field test secrion to force LTE.
I must say BE CAREFUL because you could change a setting that may require a restore/reinstall of your rom!.
I have played with a lot of settings and never done any real damage, seems like it would just close the app of the option wasn't compatible with my phone.
The hidden menus are also accessible via a dialer code (which varies per device variant and there are playstore apps as well, don't remembwr the names.
I only suggest the mod, because it is part of ny oZoP project and it will give you lots of customizations for the caller id, plus the advanced hidden menu that i beleive you could use. Like i said though, there are other options and the choice is yours.
Good luck
stangdriver44 said:
Not sure if this will help 100%, but I am sure i can't hurt.
Since you're rooted you can go ahead and install this by flashing the zip in recovery.
After you have booted back up, open the new incall modz control app.
Then hit the three lines on the top left to open the control menu options.
Scroll down and click the advanced hidden menu section.
This section opens up several hidden menus.
You can look through and see what may give you the options you're looking for.
I suggest using the "apn unlocking" to give you access to edit the apn setting.
You can also play around in the "phone testing menu" section and look within the field test secrion to force LTE.
I must say BE CAREFUL because you could change a setting that may require a restore/reinstall of your rom!.
I have played with a lot of settings and never done any real damage, seems like it would just close the app of the option wasn't compatible with my phone.
The hidden menus are also accessible via a dialer code (which varies per device variant and there are playstore apps as well, don't remembwr the names.
I only suggest the mod, because it is part of ny oZoP project and it will give you lots of customizations for the caller id, plus the advanced hidden menu that i beleive you could use. Like i said though, there are other options and the choice is yours.
Good luck
Click to expand...
Click to collapse
Will this mess with weta that's what I have on my phone right now
Saldivar said:
Will this mess with weta that's what I have on my phone right now
Click to expand...
Click to collapse
I've looked through the app and I can't find force lte I scrolled down and that's all I can view
Saldivar said:
Will this mess with weta that's what I have on my phone right now
Click to expand...
Click to collapse
Saldivar said:
I've looked through the app and I can't find force lte I scrolled down and that's all I can view
Click to expand...
Click to collapse
Well it looks like I don't need to answer the first question, but I will just mention for other users, the mod has been tested and confirmed working on every "stock" based rom without issue.
As far as the menu options not showing, it looks to me if the setup you are running has had the files needed for the options debloated or possibly that variant doesn't include them by default.
I have attatched a flashable zip of the files needed, but I DO RECOMMEND MAKING A FULL BACKUP just in case.
After you get your backup finished just flash the zip in recovery and proceed back to the app for the extra options.
Good luck again and let me know how that goes. Your feedback is valuable to me so I can ensure that everyone gets the same experiance as I intended
stangdriver44 said:
Well it looks like I don't need to answer the first question, but I will just mention for other users, the mod has been tested and confirmed working on every "stock" based rom without issue.
As far as the menu options not showing, it looks to me if the setup you are running has had the files needed for the options debloated or possibly that variant doesn't include them by default.
I have attatched a flashable zip of the files needed, but I DO RECOMMEND MAKING A FULL BACKUP just in case.
After you get your backup finished just flash the zip in recovery and proceed back to the app for the extra options.
Good luck again and let me know how that goes. Your feedback is valuable to me so I can ensure that everyone gets the same experiance as I intended
Click to expand...
Click to collapse
Thank you for your help I can't get around having lte on my v20 with metro pcs when I force lte only my phone says I have no service so looks like I'm going to have to switch service providers
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.
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?