Greetings XDA Members,
I've searched for quite some time, with limited success on keeping a stock rom along with Google Dialer. The best of both worlds if you will, that would allow great features without the loss of another. It was always a debate between using a AOSP rom at the loss of the camera, or sticking to stock and working with xposed to change settings to an agreeable state. With endless google searches, forums read, and opinions given by others; they all seemed to end with "Not Possible". Well, with some trial and error I have found a workable solution that will allow the Google Dialer to replace the stock dialer, and also allow for "In-callui" to replace the stock one.
It also needs to be mentioned, that I cannot guarantee this will work with your variant, custom rom, or other items not factored into the equation. Though this has worked for me without fail on the ATT Model D850 on Cloudy 2.5 but there are a few details to note. The "In-callUI" will show for both Incoming & Outgoing calls, but you will first see your stock one come up for a brief second or so and switch over. For me, this isn't an issue as I don't immediately answer or hang up when a call completes. Some of the items recommended in the prerequisite are optional and provide other ways to find/adjust permissions, or freeze/delete applications (Stock dialer). I'm not personally an avid developer, but if you have any questions I've been able to gain a great deal of knowledge over the years with hands on experience with the Android operating system. Feel free to ask any questions that may come up, and I'll be happy to assist if possible.
Pre-requisites;
LG G3 - Rooted
Custom Recovery with knowledge on Flashing ZIP files.
Root Explorer / File Manager
Nova Launcher / App to launch an activity.
Titanium Backup (recommended to backup Dialer and other applications in case of damage)
Included in the attachments is the file GoogleStockDialerAndMms. This file is a flashable zip that will automatically adjust the permissions necessary to make calls. It's highly recommended that you make a backup of your current rom with TWRP/CWM in case any issues arise. As this adds two files to your system directory, there is always a chance that an error can occur.
If you choose the route of Nova, you can create a shortcut to an activity. Below I've included a screenshot of which activity needs to be chosen in order to use Google Dialer.
Within Nova Launcher, long-press on the home screen.
Choose "Shortcuts"
Select "Activities"
Find "Google Dialer" in the list, then tap to open it up, and select "Phone" (use the first one in the list)
Can I disable my default dialer?
The short answer is no. As a general rule, you will need to keep your present dialer enabled in order to receive calls. The long answer is that on some phones you might be able to disable your stock dialer, but on others you definitely cannot. Feel free to try it on your own device and let us know what your results are. If you choose to do attempt this, I highly recommend against uninstalling and instead move to FREEZING the phone applications with Titanium Backup or similar root enabled application.
747 views, and 44 downloads. Hopefully everything has been smooth for everyone attempted. Please leave feedback if you have any issues.
Good to see it's over 1200 views and counting. If anyone has any issues, feel free to reply so they can be addressed.
hi @Eruvion, just wanted to check if we get the search feature with your google dialer? or does this depend on the country you live in? thanks.
resitm said:
hi @Eruvion, just wanted to check if we get the search feature with your google dialer? or does this depend on the country you live in? thanks.
Click to expand...
Click to collapse
@resitm As far as I have heard and seen so far, it will work locally depending on the information generated from your local area by google. Please let me know if you attempt it and it doesn't work.
Eruvion said:
@resitm As far as I have heard and seen so far, it will work locally depending on the information generated from your local area by google. Please let me know if you attempt it and it doesn't work.
Click to expand...
Click to collapse
thanks, i will try it once im back home.
yesterday i installed the apk from apkmirror and created a shortcut for google dialer. everything worked as should other that the tab in the most left, i think thats the call history. the dialer FC anytime that icon was touched.
Good job on this even if Im already running an AOSP based ROM, I dont need this.
But you took time writing and explaining everything so thanked all your posts,
Have a nice day
Eruvion said:
@resitm As far as I have heard and seen so far, it will work locally depending on the information generated from your local area by google. Please let me know if you attempt it and it doesn't work.
Click to expand...
Click to collapse
i flashed the zip and everything seems to be working fine. i am also able to search close by businesses, i typed pizza and it showed me the closest pizza places.
the only FC i am getting is in settings when i tap call settings-voicemail, call waiting. i don't use that so its ok for me. thanks again.
also i did not have to create a shortcut, the app icon was there after restart.
resitm said:
i flashed the zip and everything seems to be working fine. i am also able to search close by businesses, i typed pizza and it showed me the closest pizza places.
the only FC i am getting is in settings when i tap call settings-voicemail, call waiting. i don't use that so its ok for me. thanks again.
also i did not have to create a shortcut, the app icon was there after restart.
Click to expand...
Click to collapse
@resitm I'm glad everything worked for you! Thanks for letting me know
@Paradoxxx Thank you for your kind words, I'm just glad I was able to give a small contribution to the wonderful community I've used for years!
Good job on your work! I also like Google dialer. Many thanks
This does work on VS985 5.0.1. The settings does crash if you click whatever the second option was (Went back to stock for my own reasons).
SyCoREAPER said:
This does work on VS985 5.0.1. The settings does crash if you click whatever the second option was (Went back to stock for my own reasons).
Click to expand...
Click to collapse
@SyCoREAPER thank you for the update!
Doesn't work here....either when triggered from a Nova Settings widget or from the icon in the launcher. Instant force close. I can try to grab a log if you think it'll help?
D852, running Dene_Bluesman's rom (basically stock LG 5.0.1)
Edit - wonder if its because the rom version i'm using is odexed? Going to try the deodexed version and report back....
Edit 2 - nope still crashes instantly. Super frustrating! Please let me know if a log will help! @Eruvion
I want to try this on my lg G2, is there any reason you think it might not work? Anything that would make this zip specific to the G3?
+1 on this. would like to see if we can get this to work on Cloudy for G2.
Hi
This thread seem's a bit dead. Anyway i have flashed this file and it works. I am on N&N 1.3 rom. It's a stock mm based rom.
Related
REDACTED
FaultException said:
To participate in this poll, download the LATEST CM9 nightly from here, keep everything stock, no kernel changes, framework, or build.prop mods. Follow the instructions in this post, if it fails, do what it says in the post, and provide me with that dumpstate file (via a PM, do not post it here).
* By "completely stock" in the poll question, I mean completely stock CM9, not the stock Android that came with your phone.
* By submitting a poll choice, you agree that you are running COMPLETELY VANILLA CM9; STOCK KERNEL; STOCK FRAMEWORK; STOCK BUILD.PROP
Click to expand...
Click to collapse
For this test, do any of your updated GPS kernels count as stock?
Thanks.
salazar.r1 said:
For this test, do any of your updated GPS kernels count as stock?
Thanks.
Click to expand...
Click to collapse
Yes they do.
Awkward experience, I tested it with my first Vibrant (I have 2) and it didn't work, so i voted The call failed. Then i thought about it, and tried it with my other Vibrant, and returned it to stock CM9, and it worked. Unfortunately the call supporter i got was a big **** about me calling to check in if my location was posted etc. So i didn't call multiple times, but the first time i called with second Vibrant, it worked.
I honestly think its just random for this to happen.
xriderx66 said:
Awkward experience, I tested it with my first Vibrant (I have 2) and it didn't work, so i voted The call failed. Then i thought about it, and tried it with my other Vibrant, and returned it to stock CM9, and it worked. Unfortunately the call supporter i got was a big **** about me calling to check in if my location was posted etc. So i didn't call multiple times, but the first time i called with second Vibrant, it worked.
I honestly think its just random for this to happen.
Click to expand...
Click to collapse
You didn't reboot after the call on your first Vibrant did you? Get me that dumpstate file...
I said in the OP if it fails get me the file
My bad, I actually already flashed another ROM.
I'll get back onto you with that possibly tomorrow. Busy studying for a test tomorrow, so I may get back to you on that. I'll call them again.
xriderx66 said:
My bad, I actually already flashed another ROM.
I'll get back onto you with that possibly tomorrow. Busy studying for a test tomorrow, so I may get back to you on that. I'll call them again.
Click to expand...
Click to collapse
No problem, it's just important to get that file when it does fail, so I can take a look. I raised the note to red letters and a bigger size, so hopefully everyone else that tries will see it.
FaultException said:
To participate in this poll, download the LATEST CM9 nightly from here, keep everything stock, no kernel changes, framework, or build.prop mods. Follow the instructions in this post.
If it fails, provide me with a dumpstate file (via a PM, do not post it here).
The instructions on how to get that file are also in the above link.
* By "completely stock" in the poll question, I mean completely stock CM9, not the stock Android that came with your phone.
* By submitting a poll choice, you agree that you are running COMPLETELY VANILLA CM9; STOCK KERNEL; STOCK FRAMEWORK; STOCK BUILD.PROP
Click to expand...
Click to collapse
Can the dumpstate file be created with terminal? I want to help test, but adb is somehow not working for me. Is there some way that I can produce the file using only commands on my phone?
Thanks,
I tested and reported success in the poll.
I discovered one thing in my testing - it may be of interest to other testers.
I use the "dialer one" app to dial phone numbers. When I dialed 911 and pressed the "call" button, the call did not directly dial - instead I wound up at the built in dialer screen. On the dialer screen "911" was in the number display, and I had to press the "call" button on the build in dialer to actually make the call. Typically a second press of the "call" button is not required to make a call.
Bottom line - when testing 911, if there are any unexpected results, make sure that there is not another dialing application involved in the process. Similarly if there is a real emergency you may want to just use the real dialer.
I hope this is helpful (feel free to leave a thanks if it is
ewillner said:
Can the dumpstate file be created with terminal? I want to help test, but adb is somehow not working for me. Is there some way that I can produce the file using only commands on my phone?
Thanks,
Click to expand...
Click to collapse
Yes:
Code:
su
dumpstate -o /sdcard/CM_dumpstate.txt
ewillner said:
I tested and reported success in the poll.
I discovered one thing in my testing - it may be of interest to other testers.
I use the "dialer one" app to dial phone numbers. When I dialed 911 and pressed the "call" button, the call did not directly dial - instead I wound up at the built in dialer screen. On the dialer screen "911" was in the number display, and I had to press the "call" button on the build in dialer to actually make the call. Typically a second press of the "call" button is not required to make a call.
Bottom line - when testing 911, if there are any unexpected results, make sure that there is not another dialing application involved in the process. Similarly if there is a real emergency you may want to just use the real dialer.
I hope this is helpful (feel free to leave a thanks if it is
Click to expand...
Click to collapse
Maybe Dialer One defers the 911 call to the standard dialer just to be safe.
Hello,
I am writing this to help other newbies who may want to switch to Cyanogen for the first time on their Epic 4G. There were a few things I needed to do after to get everything working the way I liked and I figure this will save some people time.
What do I need to do prior?
There are many how-to's which will help but I had my Epic stock rom rooted so it was as simple as flashing cyanogen through recovery. Here is the link for a "how-to" root the stock rom if you wish to do it this way. It was the easiest way for me though the official guide says "Rooting the stock firmware is neither recommended nor necessary."
http://www.youtube.com/watch?v=C9eaCtiS0Bo
Where do I get Cyanogen?:
You can download it here. I am running the 10.0.0 stable build.
http://wiki.cyanogenmod.org/w/Epicmtd_Info
I have no google apps:
This is a problem with any Cyanogen installation. Easy fix, download & install the gaaps package from the link below and your marketplace will be back.
http://goo.im/gapps
I don’t have Navigation:
Easy fix again, download the google maps app. Here is the app store link.
https://play.google.com/store/apps/...DMsImNvbS5nb29nbGUuYW5kcm9pZC5hcHBzLm1hcHMiXQ..
I don’t have voicemail:
While you can use any voicemail app I wanted the one I had on the stock rom. I linked the app below and your voicemail will be back as soon as you install it. You need to open the app after so that it will activate.
https://od.lk/d/MjRfMjc2MDY5MF8/vtt-sprint.apk
I am getting texts from 9016 every time I get a voicemail:
From reading it seems the stock rom blocks us from seeing these but they are in fact needed for voicemail to work. To fix this I used a free app called “RedList”. Simply add 9016 to the RedList within the app, change the settings to disable both notifications, and this will problem will be solved. Here is the app store link.
https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImNvbS5saW5ub3IuUmVkTGlzdCJd
Text messages no longer have separate colors for me and my recipient:
The stock android text display is white and I hated this after getting used to Samsung’s nice colors but luckily you can solve this in two ways.
(One) A theme manager is built into the interface section of your settings page. After searching through almost every free CM10 theme I found this one I liked. It does NOT touch too many things only adding a brushed metal look and displaying text messages how I wanted them. There are a few colors to choose from but I went with Blue.
http://forum.xda-developers.com/showthread.php?t=1992980
(Two) Replace only the MMS app with one that is color coded. Please note that unlike the above, to reverse this down the road you will need to find a stock mms app package with an installer. This is good for people who are sure they want this and only wish to change the colors of the messenger, while the above is good for people who like to switch themes often being able to revert back at any second. Link for the colored mms app.
http://www.mediafire.com/?hcjukwwkj4y41h3
Morror: https://od.lk/f/MjRfMjc2MDY5MV8
Facebook pictures no longer sync with my existing contacts:
This is a small problem, but still one that I got used to having with the stock rom and wanted to correct. From reading this seems to be a problem related to later Android versions, not just Cyanogen. The fix for this is easy as well, search out a free app called “UberSync for Facebook”. I had the regular facebook app installed & logged in prior and UberSync logged right in, got the pictures, and updated my contacts.
https://play.google.com/store/apps/...wsMSwxLDEsInJvLndlZWRuZXQuY29udGFjdHNzeW5jIl0.
I no longer have Swype:
Despite having the nice physical keyboard (the whole reason I got the Epic) I still got used to using Swype here or there. I don't think I will be allowed to link this file here but you can find it on "certain" sites.
Notes:
Despite reports that Bluetooth can be problematic, I use it daily with an earpiece and have yet to experience any issues. GPS & 4G also work great. If any links are broken send me a PM! I check my email daily.
Get rid of the dropbox download links. Those are absolutely horrible when posting a guide for others to use.
nikon120 said:
Get rid of the dropbox download links. Those are absolutely horrible when posting a guide for others to use.
Click to expand...
Click to collapse
Why are they so bad? The bring you right to the download and I won't be deleting these files from my dropbox. Much better IMO than dealing with one of those sites where you have to wait 45 seconds for a download link to appear in a sea of other spam download buttons.
protivakid said:
Why are they so bad? The bring you right to the download and I won't be deleting these files from my dropbox. Much better IMO than dealing with one of those sites where you have to wait 45 seconds for a download link to appear in a sea of other spam download buttons.
Click to expand...
Click to collapse
Well...
No MD5/SHA1 to compare against to make sure you have a complete download.
People's dropbox tends to get too much traffic and the link becomes dead.
You basically cut out the original author(s) of the file.
Based off # 3: They could need the ad revenue, and/or want to track download activity if they're self-hosting.
nikon120 said:
Well...
No MD5/SHA1 to compare against to make sure you have a complete download.
People's dropbox tends to get too much traffic and the link becomes dead.
You basically cut out the original author(s) of the file.
Based off # 3: They could need the ad revenue, and/or want to track download activity if they're self-hosting.
Click to expand...
Click to collapse
I know this isn't directed at me, but the things I have on my box account are older things( Samsung Moment update tool), things I've done for myself, or things that I've found for other people. In other words, things many people don't care about.
Sent from my SPH-D700 using Tapatalk 2
nikon120 said:
Well...
No MD5/SHA1 to compare against to make sure you have a complete download.
People's dropbox tends to get too much traffic and the link becomes dead.
You basically cut out the original author(s) of the file.
Based off # 3: They could need the ad revenue, and/or want to track download activity if they're self-hosting.
Click to expand...
Click to collapse
#1 - I think more people are concerned with a working link, if they download the archive after and it somehow gets corrupted i'm sure they will just try again
#2 - Valid point though my files don't have a great enough of demand to warrant this. If this changes I will change my links.
#3 The only thing that wasn't mine with a dropbox link was the MMS app and I only mirrored it in case the original link were ever taken down. If it will make you happy I can include the original link as well. For the voice mail app, its simply the sprint one ripped from a stock rom.
Though your points are valid, I think you are sort of just being picky bud
Thanks for the VM download link. Only thing I want is task manager which I had installed on CM9. Is there stockish one that works for 10?
Try the flashable one from here
http://forum.xda-developers.com/showthread.php?t=1452004
Sent from my SPH-D700 using Tapatalk 2
swype
I reinstalled swype 3 or 4 times with various upgrades and it would always "expire" and I'd have to figure out how to get it working again. I am running 10.1 RC5 now and it has a decent generic swype-ish virtual keyboard. The thing missing is that you can't finish your text and go back and fix any misspelled words by touching alternate suggestions. You have to catch them as they come up. It seems like at first I could still do that, but I can't figure out how to get the suggestions to come back up.
I'm over swype.
Just flashed CyanogenMod 10.1... is there any built in overclocking?
I installed SetCPU and it won't step above 1000 MHz.
Kernel
Steelcitymetal said:
Just flashed CyanogenMod 10.1... is there any built in overclocking?
I installed SetCPU and it won't step above 1000 MHz.
Click to expand...
Click to collapse
You need a different Kernel. I have been using didy's kernel for a while. You flash CM10.1 and then you flash the kernel. CM10.1 has its own kernel that overwrites what you flash. So when you update, i think you have to reflash the kernel. I haven't screwed around with it since I installed rc5. I think I did CM, then the kernel, then the big mem patch. I never was able to figure out how to update the radio. I always ended up with "no voice service" or worse.
There is a thread in the developer forum that has the links to the kernel downloads. I am running one from may 30 and haven't updated.
boocephus said:
You need a different Kernel. I have been using didy's kernel for a while. You flash CM10.1 and then you flash the kernel. CM10.1 has its own kernel that overwrites what you flash. So when you update, i think you have to reflash the kernel. I haven't screwed around with it since I installed rc5. I think I did CM, then the kernel, then the big mem patch. I never was able to figure out how to update the radio. I always ended up with "no voice service" or worse.
There is a thread in the developer forum that has the links to the kernel downloads. I am running one from may 30 and haven't updated.
Click to expand...
Click to collapse
I think I found it... Is didy the same as didhiy?
[KERNEL][CM10.1]Nitest Kernel for Crespo4G/Epic4G Modem with Voodoo Sound&Color
When you say you couldn't update the radio, you just mean the cell service radio, right? Not wifi? I don't have cell service on my Epic, so that wouldn't be a problem for me... just as long as the wifi radio still works
Also, what specifically do you mean by "or worse"?
Steelcitymetal said:
I think I found it... Is didy the same as didhiy?
[KERNEL][CM10.1]Nitest Kernel for Crespo4G/Epic4G Modem with Voodoo Sound&Color
When you say you couldn't update the radio, you just mean the cell service radio, right? Not wifi? I don't have cell service on my Epic, so that wouldn't be a problem for me... just as long as the wifi radio still works
Also, what specifically do you mean by "or worse"?
Click to expand...
Click to collapse
Yeah. That's the one. I looked at my about phone and it said "didy".
I saw a thread about the nexus radio being hot **** and I fooled around with it. I got either "no voice service" or no nuthin. I was able to flash back to the regular epic radio. there is another thread that had all the flashable zips with different modems. luckily the epic one undid my stupidity - at least on my phone.
boocephus said:
Yeah. That's the one. I looked at my about phone and it said "didy".
I saw a thread about the nexus radio being hot **** and I fooled around with it. I got either "no voice service" or no nuthin. I was able to flash back to the regular epic radio. there is another thread that had all the flashable zips with different modems. luckily the epic one undid my stupidity - at least on my phone.
Click to expand...
Click to collapse
Thanks man, I'll give it a shot. CM10.1 is running pretty smoothly on my phone, but it could be better and battery life is not an issue for me.
I'll be sure to run backups before I do though :good:
Thanks
These tips helped - I just made the jump to CM 10.1, and although there are a few quirks it has been great. Your list really helped.
FYI, one thing I ran into was the auto-rotate didn't work. I followed the directions here:
http://epiccm.blogspot.com/2012/01/boot-el30-stock-from-sdcard.html
the first time, there was no change. I tried again (and calibrated like 6 times) and it worked.
Has anyone noticed the physical keyboard doesn't always work the same? In some places, you have to hold down shift or Fn while pressing the key you want (for example - hold shift while pressing A, rather then pressing shift then pressing A). It's not consistent - some inputs work like the keyboard did before. Does anyone have any suggestions how to fix this. Not the worst thing (I'm just glad I still have a physical keyboard), but I would prefer it work the way it did before, or if that's not possible, at least be consistent.
And the smiley face button on the physical keyboard doesn't work either. I mean, it's like 2005 where I have to type out my 's!!
any phantom voicemail fix?
phantom voicemails?
TheSkipperCDB said:
Has anyone noticed the physical keyboard doesn't always work the same? In some places, you have to hold down shift or Fn while pressing the key you want (for example - hold shift while pressing A, rather then pressing shift then pressing A). It's not consistent - some inputs work like the keyboard did before. Does anyone have any suggestions how to fix this. Not the worst thing (I'm just glad I still have a physical keyboard), but I would prefer it work the way it did before, or if that's not possible, at least be consistent.
Click to expand...
Click to collapse
I have noticed that the physical keyboard doesn't work right in the browser. Shift and Fn don't seem to work. I am usually in such a hurry that I just close it up and use the virtual keyboard if I want to have punctuation. It honestly didn't occur to me that it might be fixed. I can't offer that fix. I am just offering emotional support and validation.:good:
boocephus said:
I have noticed that the physical keyboard doesn't work right in the browser. Shift and Fn don't seem to work. I am usually in such a hurry that I just close it up and use the virtual keyboard if I want to have punctuation. It honestly didn't occur to me that it might be fixed. I can't offer that fix. I am just offering emotional support and validation.:good:
Click to expand...
Click to collapse
I noticed that the default browser you have to hold the shift or fn key while pressing the desired key to get it to work. Apps and os seem to work with a tap od these keys and then a hit of the desired key.I recall a while back a thread about the smiley and since it was not a default key the consensus was that they would not be adding the functionality to cm. While on the topic...same goes with the .com function.
Sent from my SPH-D700 using xda app-developers app
I'm sorry i want to ask, how we modify system setting look in CM? Thank you..
Well last night I was fed up with my battery consumption as I saw that I had had GPS on all the time for no obvious reason. I wanted to root the phone as I have 815 EU model but googled to check that App ops or similar apps work in Lollipop and found an interesting thing about G3. It has integrated permission manager that can be accessed from activities and does not need root. Wondering would it still be there in G4 I found it and tried it and It works. Now I dont have to give Soundhoud my fine location, Chrome beta does not need camera etc etc. And as I have not seen this brought up by anyone I thought to share it with you and hopefully sort out some bugs like my GPS always on situation.
So in short download a custom launcher ( I use Nova Prime) or Activity launcer and find Settings in the list and in there Access lock activity and add shortcut. Open it up and you see a list of you apps and you can restrict all the permissions app by app. After that exit the app and you are done. There is no even need to restart the phone (of course it wont hurt to reboot). I tried that mine works with Whatsapp by removing camera permissions from the app and it cant open camera anymore.
Awesome, thanks for the info. It works great! This should help with holding me over until we get root.
Same for me. Id like to wait until unofficial root to retain locked status even though I could root now via Lg's tools. This might be one way to stop me rooting until better way comes.
Sent from my LG G4
http://forum.xda-developers.com/g4/general/app-ops-available-root-t3141191
Could've just bumped the thread about it already that's sitting at the bottom of the first page (at least when I typed it)
Bootup said:
http://forum.xda-developers.com/g4/general/app-ops-available-root-t3141191
Could've just bumped the thread about it already that's sitting at the bottom of the first page (at least when I typed it)
Click to expand...
Click to collapse
Sorry, must have not searched with the right keywords and/or just missed it or automatically dismissed the thread as it had App ops in the title as a thing for rooted phones. And as I have not seen any mention of this I thought of making this quick quide for those who missed it.
Hi, My friend has the Note 7 Global Lavender version, like me, he is 82 years old and is having some trouble with answering calls because of the not-so-easy to use green phone slider. Even I sometimes have problem with this one.
So can someone help me with an alternative and a small guide on how to install it(if not like other Apps) and set it as default, so when call comes in that is the one he see? There is no need to change anything else.
Please don't refer me to google, the problem is not that there aren't any Apps but that there are too many of them, and I can't try them all until i find one without a slider but where you just push the green button to answer call - He is starting to regret he bought this phone, as it is not so friendly for old people.
I hope someone here can help.
Jan
May be u can use Truecaller
Ryamoz said:
May be u can use Truecaller
Click to expand...
Click to collapse
Thank you, and yes it looks like what I wanted though it is a very sophisticated app with a lot more functions than I wanted, maybe too much - it is still for an elderly man. Also looks like there have been some complaints that you get more spam calls after you use Truecaller and that they upload your data to their servers for everyone to see - not for me!
I like to hear other options if there are some Preferebly close to the stock dialer, but without slide and only push or an option to set it yourself. And not one that takes advantage of people.
Thank you
insomniacno1 said:
Thank you, and yes it looks like what I wanted though it is a very sophisticated app with a lot more functions than I wanted, maybe too much - it is still for an elderly man. Also looks like there have been some complaints that you get more spam calls after you use Truecaller and that they upload your data to their servers for everyone to see - not for me!
I like to hear other options if there are some Preferebly close to the stock dialer, but without slide and only push or an option to set it yourself. And not one that takes advantage of people.
Thank you
Click to expand...
Click to collapse
You could try google dialer apk from apkmirror.com, it has a simple slide gesture to answer and end calls and isn't too bloated with useless features
Saad. Mk said:
You could try google dialer apk from apkmirror.com, it has a simple slide gesture to answer and end calls and isn't too bloated with useless features
Click to expand...
Click to collapse
Thank you for your answer, I will look at it but would prefer to avoid slide since that is the problem. The Note 7 has slide, but its not easy to use not even for me and I have had many phones with "slide dialer".
Finding "push button" dialer has proven to be some of a challenge, also when you take in mind it should be one not stealing your data
Hope someone can come up with a solution for this
Guess not, but i found this one and it might do the trick, testing next week when my friend available: https://play.google.com/store/apps/details?id=com.luckyme.dadapp2
Update: forget the app above - it works just after install but doesn't do anything when pushing the Answer button. After that it never pop up anymore . Uninstalled it!
If you can root the device and install google dialer framework , you can set the google phone app which has better slider : you just need to slide up, holding the phone icon isn't necessary. And custom roms can also be easier for him as compared to miui.
anyways, i wonder if you could find a feature in miui that makes the incoming calls screen always in 'heads up' mode. That way he just needs to touch the accept or reject. I m not sure if miui provides that
Walden0 said:
If you can root the device and install google dialer framework , you can set the google phone app which has better slider : you just need to slide up, holding the phone icon isn't necessary. And custom roms can also be easier for him as compared to miui.
anyways, i wonder if you could find a feature in miui that makes the incoming calls screen always in 'heads up' mode. That way he just needs to touch the accept or reject. I m not sure if miui provides that
Click to expand...
Click to collapse
I'm sorry and tank you for your input, but I'm not rooting his phone to solve this - too many things can go wrong because you have to unlock bootloader and then install TWRP first before you can root - or so the guide here on XDA states.
I hope for a different solution
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?