Love the phone. I think the included dialer (phone app) can use some work. Does anyone have any recommendations on alternate dialer apps?
My favorite phone app is the Pixel Google Phone app. Does anyone have a script or directions on how to install it on a 5T?
You can try "True Phone". A very good dialer/contacts app. Manage well the dual sim.
Magisk+Google Dialer works like a charm for me. No problems whatsoever
Just to follow up my thread and logonaniket's suggestion, I used Google Dialer install zip from Oneplus 5 forum. Here is the link for others:
https://forum.xda-developers.com/oneplus-5/themes/magisk-oneplus-5-google-dialer-contacts-t3640993
I flashed it using twrp and it works great. Sounds like logon used Magisk Module and it worked for him also.
Hi all,
my main problem with the OxygenOS Dialer is that the screen sometimes suddenly switches on, even when the phone is very close to my ear. Then I touch the screen with my ear and someting is triggered (Flash light on,...).
I installed 'Drupe' which is a bit of an overkill in my opinion., but the proximity sensor works fine there.
Did anybody try the flashable google dialer from here? https://forum.xda-developers.com/android/apps-games/g-d-m-c-dpi-t3805463
Or should I use the Magisk module and anothe Google Phone version?
Any other good dialer recommendation is very welcome
Thanks
logonaniket said:
Magisk+Google Dialer works like a charm for me. No problems whatsoever
Click to expand...
Click to collapse
I tired that. Installed the module and disabled my contacts and Dailer but then when I was trying to call someone the Dailer screen would disappear while the call was going through. Means I could not end the call. Did you come across this by any chance?
digitalmahdi said:
I tired that. Installed the module and disabled my contacts and Dailer but then when I was trying to call someone the Dailer screen would disappear while the call was going through. Means I could not end the call. Did you come across this by any chance?
Click to expand...
Click to collapse
I use it in the same way. Magisk plus disable the bulit in versions. It's works like a charm since around a month. Tomorrow the dailer crashed when on the call but when the call ended (from the other side) the app works fine again. Never faced any issues like that
digitalmahdi said:
I tired that. Installed the module and disabled my contacts and Dailer but then when I was trying to call someone the Dailer screen would disappear while the call was going through. Means I could not end the call. Did you come across this by any chance?
Click to expand...
Click to collapse
I had the same issue when I switched to the Google Dialer. I found that I needed to make the Google Dialer the default phone app before disabling the system dialer... for some reason OmniRom didn't know what to do... phone would ring, but I got no screen to pick up.
The flashable zip i mentioned 4-5 posts ago seems to works fine for me on OxygenOs
Try ExDialer app. I'm using it for many years, on different phones. No mistakes with it!
Google Dialer, no root required.
True Phone
abel06 said:
You can try "True Phone". A very good dialer/contacts app. Manage well the dual sim.
Click to expand...
Click to collapse
I second that. I have been using True Phone for a couple years, works great.
Related
Hey guys,
I just tried the NoLED on my s3 mini and it's working well.
If you need visual notifications about your incoming messages and emails, missed calls or you want an always visible clock on your phone's screen I suggest this little application:
http://forum.xda-developers.com/showthread.php?t=730692
It is not my development, I can't be responsible if something goes wrong with it, but it's working perfectly on my device with ALL2 rooted 4.1.1 firmware.
Hey thank`s for this i will give it a try.:laugh: Quite a few options in the App.
avers said:
Hey guys,
I just tried the NoLED on my s3 mini and it's working well.
If you need visual notifications about your incoming messages and emails, missed calls or you want an always visible clock on your phone's screen I suggest this little application:
http://forum.xda-developers.com/showthread.php?t=730692
It is not my development, I can't be responsible if something goes wrong with it, but it's working perfectly on my device with ALL2 rooted 4.1.1 firmware.
Click to expand...
Click to collapse
Yes its working, i tried it few days ago.. But its no good for me. i tried another ap too button led, and it uses tasker comands and scripts(?) but dont work well on jb.. So we should wait for a dev to develop a bln kernel..
Sent from my GT-I8190 using Tapatalk 2
Working great on stock rom here!
Thanks for the tip! Downloaded it and works perfectly on stock (rooted) rom.
I did have a problem with the TTS when allowing NoLED to accessibility (screen 1 of 7, map opened, ...), but disabling the Google and Samsung TTS services, and renabling them, solved the problem.
How's the battery consumption on your SGS minis after installing the app?
Hello all, I recently purchased this phone for T-Mobile USA. Pretty happy so far but one item is extremely irritating.
When texting (via stock messaging or hello sms) or writing an email via the Gmail app, any word that is underlined as a spelling mistake results in a pop up box for correction, when I select the correct word it will crash the app and show the message "Unfortunately, ____ has stopped." And it will close the app and not even save it as a draft. Lost some emails and many text messages to this. Simple example, "You're stupdi..." Stupdi will be underlined in red, as I select the word the popup dialog box gives suggestions, when I select stupid it will crash the app. I'm not referring to the hovering words but the actual pop-up dialog box.
Is this a known bug? Any suggestions on how to fix it?
I've never seen this on the z1c before, however I experienced something similar on an older htc phone. A factory reset got rid of the issue for me.
Sent from my D5503 using Tapatalk
Still there..
Have factory reset the phone 3 times and cleared the cache each time before and after. Can still reproduce the problem without fail. Annoying as hell.
Not sure what to do.
darkmanx21 said:
Have factory reset the phone 3 times and cleared the cache each time before and after. Can still reproduce the problem without fail. Annoying as hell.
Not sure what to do.
Click to expand...
Click to collapse
Yep I have exactly the same problem...
+1 as well. VERY VERY VERY annoying.
Yes, I suffer this as well. Anyone made a bug report with Sony referencing to this thread?
Nope...I wouldn't know where to start but I'll happily back you up!!
For that matter, does anyone else have problems with the proximity detection playing up when you are on a call so that sometimes you press buttons with your face? Or do I just have a really fat face?
woodchippings said:
Nope...I wouldn't know where to start but I'll happily back you up!!
For that matter, does anyone else have problems with the proximity detection playing up when you are on a call so that sometimes you press buttons with your face? Or do I just have a really fat face?
Click to expand...
Click to collapse
Glad I'm not the only one. Drove me crazy/
Temporarily solved the spelling issue by just turning it off and installing Swiftkey. Eh..guess I should be thankful for 3rd party apps.
Also realized the native text messaging app doesn't do group messaging. Sigh.
Nah, you don't have a fat face - I have the exact same issue also. Have to press the Home key to exit the dialer during calls or it keeps registering key presses. Doesn't matter if I smash the phone into ear/cheek.
Also random, when trying to us the camera, it will start but not show anything.
Some stupid bugs..hopefully in the new fix.
What ROM are you guyed using having this problem? As it's now occurring on a 4.4.3 kit kat PAC rom.
dillalade said:
What ROM are you guyed using having this problem? As it's now occurring on a 4.4.3 kit kat PAC rom.
Click to expand...
Click to collapse
Having same problem in AOSB 1.3.3/KitKat 4.4.2 and AOSB 1.3.2/KitKat 4.4.2
Does not occur on Cyanogen 11-20140218-Nightly-mb886.
and there is a particular peculiarity to this (other than the absolute frustration of loosing a well composed email). As as I was about to post in the AOSB thread:
FCs in any app where word replace is used - but does not occur on the the first word that awaits correction.
For instance in new Gmail message type
mappp
mappp
Tap the first word, select from a list of possible corrections (map) and the word is properly replaced then, on the second instance, whether or you corrected the first one of left it alone, when you select from the list of available corrections (map) the app crashes. The same pattern is in evidence when the words the same (as shown here) or different.
100% recreate-able
Motorola AT&T Atrix HD (MB886) on Tmobile service
darkmanx21 said:
...installing Swiftkey. ...Some stupid bugs..hopefully in the new fix.
Click to expand...
Click to collapse
Interesting. Thanks for suggestion. Switkey did not fix for me but perhaps because I'm on different ROM and phone. Still it looks really nice!
Latest Sony keyboard update from today fixes the issue so far for me.
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
try the replacement handset. I've had my G3 since it came out with no problems whatsoever.
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
Wow, my G3 just started doing this too. I've had it for 6 months and it's just been the past week that I've been having issues. It's hit or miss, but about 90% of the time I get complaints that the other person can't hear me or that I sound very faint. It's been driving me crazy. I've figured out that I can toggle speaker mode and it fixes it. Can you try that out see if it's the same for you?
I noticed this about a week ago, interesting. Wonder if it's something on tmobile's network.
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
---------- Post added at 09:48 AM ---------- Previous post was at 09:04 AM ----------
madmanjsm said:
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
Click to expand...
Click to collapse
I'm now running in safe mode and a couple test calls to my Google Hangout sound fine. Don't think it's a hardware issue.
I've started to experience this too. It's really annoying. I hope it gets fixed soon. Though, I am glad to know it's not just me. I really didn't want to dig around in my apps to find the offender.
Question: Do any of you guys have the Nova Launcher Beta running? I think I started having issues around then.
Sent from my LG-D851 using Tapatalk
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
bryanwny said:
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
Click to expand...
Click to collapse
Thanks! I downgraded and installed Google App 4.1.29 here http://www.apkmirror.com/apk/google-inc/google-search/google-app-4-1-29-1706998-arm-android-apk-download/. Also disabled auto-update for Google Apps so it doesn't update to 4.2.16.87075793. I'll test it out and see what happens.
I also have had the same problem lately, just twice. A reboot fixed it
This is affecting me as well. I'm also in Los Angeles and the phone was fine until some time last week. I'm trying to the google apps downgrade now...
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Lookatthemonkeys said:
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Click to expand...
Click to collapse
Try downgrading the Google app. Worked fine for me.
Downgraded, seems better. Are people also recommending not to use voice activated Google now?
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
tippingvan said:
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
Click to expand...
Click to collapse
In the play store for the Google search app click the uninstall button. That will return the app to it's factory version. Then just install the version that's linked earlier in this thread. Make sure you have automatic updates turned off for the app or it will keep updating.
Sent from my LG-D851 using Tapatalk
Same thing happens to me. I had my phone for about 2 months now and sometimes people cant hear me or i sound like a transformer. i restart my phone and it fixes the problem but still does it after a couple days. I'm not rooted or anything like that. I also have a problem when I'm on a call. my volume bare goes up and down if i wanna lower and or raise it and the volume sounds the same even on speaker phone it does it too..
I had the problem turn off ok google from any screen and reboot and problem with voice calls fixed
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
JohnnyDanger said:
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
Click to expand...
Click to collapse
I was gonna do a factory reset and if that didn't work i was gonna get a replacement . Hopefully this fixed the problem. The only issue I seem to be having is. when I'm on speaker phone or have it to my ear. and when i go to adjust the volume it doesn't change it. like i see the meter go up and down but the volume stays the same. its weird
I can confirm that after enabling voice activation for google now from any screen was the culprit of Mt audio issues. I was told I sounded far away or like a robot far away. Reset my device numerous times and reinstalled all apps and made calls. Once I enabled OK google from google now the issue came back. Disabled it and BOOM it worked fine. Haven't had an issue since.
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
teostar said:
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
Click to expand...
Click to collapse
Wrong place to post this.
dpryor88 said:
Wrong place to post this.
Click to expand...
Click to collapse
OK, maybe a mod can move it to the correct area. I didn't post in any specific rom thread since it occurs on various ROMs.
teostar said:
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
Click to expand...
Click to collapse
I'm not using pixels dialer and I have echo bug.
ivicakc said:
I'm not using pixels dialer and I have echo bug.
Click to expand...
Click to collapse
When it happens do you notice the double phone icons in the status bar?
teostar said:
When it happens do you notice the double phone icons in the status bar?
Click to expand...
Click to collapse
Nope, one icon..
teostar said:
Hi, I'm new here however I've read on a few rom threads about an echo on voice calls. Today I started experiencing the echo for the 1st time and I think I have and idea what's the cause.
I am running freedomos ce v1.10 but I've seen the issue as a known bug on other ROMs and it doesn't affect everyone.
I think it affects those of us who flash the pixel dialer, maybe other dialers as well but in my case it's the pixel dialer.
Why do I think so?
Today it started, i received a call and I noticed the call screen was the default phone app screen not the pixel screen. (I've disabled the stock app). but somehow its still activating when there's an incoming call.
Also after accepting the call I notice 2 phone icons in the status bar suggesting maybe that there's 2 phone calls active.
I've checked and the stock phone app is still disabled so there may be an OS level trigger still allowing it to accept incoming calls.
Click to expand...
Click to collapse
In which threads you have read about the echo issue? This issue is mainly present on the nougat roms and it's due to the audio hal, however workaround was found and now everything is fine(when you flash the fix ofc). I have never had this issue on MM roms and especially on stock(ye, freedom rom is stock based), so maybe the problem you have is really somewhere with the apps you use. And can you tell how did you find that you have the issue?
siankatabg said:
In which threads you have read about the echo issue? This issue is mainly present on the nougat roms and it's due to the audio hal, however workaround was found and now everything is fine(when you flash the fix ofc). I have never had this issue on MM roms and especially on stock(ye, freedom rom is stock based), so maybe the problem you have is really somewhere with the apps you use. And can you tell how did you find that you have the issue?
Click to expand...
Click to collapse
As I stated I noticed that incoming calls seemed to come in the stock phone app not the pixel dialer. But because the stock app is disabled think that may have been the issue.
ivicakc said:
Nope, one icon..
Click to expand...
Click to collapse
Here's what happens for me.
teostar said:
Here's what happens for me.
Click to expand...
Click to collapse
Do you have root? If yes, just go to the system folder, find the app that you don't want to use and rename it(add .back at the end), so you can revert to it later if you want, then reboot
siankatabg said:
Do you have root? If yes, just go to the system folder, find the app that you don't want to use and rename it(add .back at the end), so you can revert to it later if you want, then reboot
Click to expand...
Click to collapse
I'm not sure which is the stock phone app. Apart from "Google dialer" there's "OPincalui", "phonesky", "telecom" and "telephonyprovider"
I'm not sure which is the actual phone app.
teostar said:
I'm not sure which is the stock phone app. Apart from "Google dialer" there's "OPincalui", "phonesky", "telecom" and "telephonyprovider"
I'm not sure which is the actual phone app.
Click to expand...
Click to collapse
I would eliminate Phonesky (Play Store), and TelephonyProvider from the list because those are not directly tied to the phone app.
teostar said:
Here's what happens for me.
Click to expand...
Click to collapse
I have the same problem. Freedom OS, stock kernel and google dialer and contacts....
teostar said:
I'm not sure which is the stock phone app. Apart from "Google dialer" there's "OPincalui", "phonesky", "telecom" and "telephonyprovider"
I'm not sure which is the actual phone app.
Click to expand...
Click to collapse
Actually you should be able to see the app icon when you go to the folder, so try with some other file manager that support this function. I can bet that OPIncallUI is the dialer, but to be sure, try with other manager
siankatabg said:
Actually you should be able to see the app icon when you go to the folder, so try with some other file manager that support this function. I can bet that OPIncallUI is the dialer, but to be sure, try with other manager
Click to expand...
Click to collapse
OK, with solid explorer I see this. It gets even more confusing...
teostar said:
OK, with solid explorer I see this. It gets even more confusing...
Click to expand...
Click to collapse
Rename the OPIncallUI, don't touch the other apps, that should do the job
siankatabg said:
Rename the OPIncallUI, don't touch the other apps, that should do the job
Click to expand...
Click to collapse
OK, just rename the apk, not the actual folder?
teostar said:
OK, just rename the apk, not the actual folder?
Click to expand...
Click to collapse
Just the .apk, rename it to .apk.back and if you get problems just rename it back to .apk
Sent from my ONEPLUS A3003 using Tapatalk
siankatabg said:
Just the .apk, rename it to .apk.back and if you get problems just rename it back to .apk
Click to expand...
Click to collapse
Thanks. That worked.
Hello,
I have been struggling recently to answer or reject calls when given the swipe up or down option.
When its unlocked and I get the tap to answer or reject as a notification its fine.
I'm just wondering if anyone else had a similar issue or had found a fix.
I'm on the official firmware, running 8.1.0
I've experienced something similar too. Sometimes I find myself swiping over and over again just to get one call answered or rejecte I have no idea why it does that, or when, it seems to be random on mine
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
I've found you can swipe down from the top of the screen and can answer it from the notification menu instead.
Just takes longer.
cobben said:
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
Click to expand...
Click to collapse
Just after having written the above, the phone corrected itself.
Now I can answer calls on the first swipe.
Interesting . . .
Sometimes my phone will let me answer normally. most of the time however I have to use the notification bar.
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Yup, been having the same issue. Stock phone, no root. What's frustrating is there as no further updates.
iliais347 said:
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Click to expand...
Click to collapse
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
cobben said:
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
Click to expand...
Click to collapse
What i did is i added the google dialer app to my phone, then to game booster and set its fps to 40. Now i can answer the calls.