Related
So far with Custel 1.0/2.0 and XDA live 1.1/1.2 Inesoft Address Book Caller ID becomes disabled, and the entire program becomes essentially useless after installing and soft resetting. Any reason the roms are suppressing this program? Fixes?
Is it a compatibility issue or a simple registry fix?
marscandybars said:
So far with Custel 1.0/2.0 and XDA live 1.1/1.2 Inesoft Address Book Caller ID becomes disabled, and the entire program becomes essentially useless after installing and soft resetting. Any reason the roms are suppressing this program? Fixes?
Is it a compatibility issue or a simple registry fix?
Click to expand...
Click to collapse
Its running fine on Dutty's latest verison
Try 2.0 since it is the latest version. It's free if you bought after July 2006.
I am using 2.0. And I even tried the 2.1 Beta.
Its odd, I put the original ATT Tilt Rom back on it, and it just keeps getting disabled. Is there any fix?
I even tried a hard reset and installing Inesoft Address Book 2.0 by itself then resetting. Then it just gets disabled and my bottom launch tray disappears.
taiseer999 said:
Its running fine on Dutty's latest verison
Click to expand...
Click to collapse
I just tried it on Dutty's Version. After 2 soft resets it just completely stopped working! How can i fix this
First, let's verify it is the address book. I have been usin git for along tie and it works FINE. I have read reports that there is a hacked version (warez) floating around that the caller ID does not work.
I'd contact Inesoft directly for support.
I have contacted Inesoft. Still awaiting a response. I've only had this problem with the Tilt/Kaiser. It worked fine until doing some soft resets and then PRESTO it was gone. And yes I am using a legit version.
It seems as if my bottom launch tray (where the small inesoft address book icon is) gets completely disabled, and consequently disables inesoft. The program doesn't disappear right away. It disappears probably over an entire day after multiple soft resets.
So, just to clarify....
It works find after a soft reset, but after an entire days of multiple soft resets it does not work?
After 1 soft reset it still works?
After 2 soft resets it still works?
But after 3-4-5 it dosent work any more?
Everything else works after these resets? Like it being the default contacts; or the default history manager, etc?
I have the issue happenning with Dutys Rom#5. Caller ID doesn't stay enabled and every so often the address book comes up blank. I use it for the address book shortcuts.
-McMex
grizzley said:
So, just to clarify....
It works find after a soft reset, but after an entire days of multiple soft resets it does not work?
After 1 soft reset it still works?
After 2 soft resets it still works?
But after 3-4-5 it dosent work any more?
Everything else works after these resets? Like it being the default contacts; or the default history manager, etc?
Click to expand...
Click to collapse
There is no "exact" amount of resets but eventually it just completely gets shut out. The only thing it can do after it shuts down is just edit my contacts and add photos to names etc. But as for Caller ID and Call history functions etc, it just keeps getting disabled no matter how many times i try to re-enable it.
xda live 1.2
Works fine on xda live 1.2...actually have used it on all variants of xda live.
Help Help Help
Does anyone know how to change the skin of the contacts menu in inesoft address book?!? I have posted so many questions on different blogs and haven't gotten one answer. I would love to change th eugly blue to like black or something...I would like to customize it and have no idea how Please if anyone knows how to do this HELP!!!
Hi
I am having a problem that just cropped up on a Xoom 3g running unrooted, Motorola Jelly Bean 4.2.1. I am using it on wi-fi only, no Verizon account. The unit will get past the M screen and then ususally hangs up when it gets to the screen with the expanding colored rectangles. Sometimes the home screen will flash up for a split second, sometimes with enough time to log in. In either case it is back to the colored rectangles shortly, even if I get it to log in. I can get to the factory reset screen during the boot and do a full factory reset reload the apps and settings. I have done this twice. It works for about 20 or 30 boots and then colored rectangles show up in the middle of a session and its back to the boot problem.
Questions:
Does anyone have a quick answer?
Will rooting and reloading Android help or it is a hardware issue?
Thanks for any help
John
Have tried a full factory reset without restoring your apps and settings to see if the issue persist?
Strange boot
Domunus said:
Have tried a full factory reset without restoring your apps and settings to see if the issue persist?
Click to expand...
Click to collapse
It seemed to work ok with the apps installed for a while. There were a couple which were suspect and I did not reinstall after the factor reset. It could be a problem though. Maybe I will try the reset again with only a couple of apps. I am still undescided on the root and updating the OS.
OldTacoman said:
It seemed to work ok with the apps installed for a while. There were a couple which were suspect and I did not reinstall after the factor reset. It could be a problem though. Maybe I will try the reset again with only a couple of apps. I am still undescided on the root and updating the OS.
Click to expand...
Click to collapse
Hi again.
I did some thinking and now I suspect the Bluetooth connection. I had enabled an app that required BT (Logitech Harmony Hub). I also enabled the BT but not the app after the second factory reset. I did another factory reset and did not enable Bluethooth. The unit has been running flawless as before. I did a little searching on the web and found a guy with an identicle problem but it was not clear if it was resolved.. Does anyone know know if this is a common problem and if there is a solution. I could not find anything elso on the web or in the formum that helped. If this is a persistant problem, I am wondering if a custom rom would help.
Thanks
John
Hey guys,
I just got my OPO today and have been loving every bit of it, but it seems that my SMS isn't working correctly. I checked the APN settings multiple times and even tried some of the preset ones with no luck. My issue is that I can both receive SMS messages as well as send and receive MMS messages, but when it comes to sending an SMS, I get a "Message note sent. Touch to retry" message. I've tried both the default app AND Google Hangouts with no luck from either. It's not a huge issue because I use mostly group chats and my gf can use hangouts, but it's still incredibly frustrating. Do you guys have any hints or tricks I should try out? I seriously love this device, but I am going crazy over the SMS issue.
I'm running the stock CM11S rooted with TWRP 64GB model on AT&T. Mobile data, LTE, everything else works. Just not actually sending SMS. I thank you for the responses ahead of time.
Hey @Bliznade.. .i see you posted about this sms issue. I am also having exact same issue now with my oneplus. Did you manage to find a solution of your issue? If yes, then can you share it with me? It is driving me crazy.
OR if anyone else can help me here?
Guys, basically you have to get the apn that is used by AT&T. Idk if you already have that apn, but the preset ones are made for the T-Mobile bands not really AT&T as I know it.
Parvinder25 said:
Hey @Bliznade.. .i see you posted about this sms issue. I am also having exact same issue now with my oneplus. Did you manage to find a solution of your issue? If yes, then can you share it with me? It is driving me crazy.
OR if anyone else can help me here?
Click to expand...
Click to collapse
Yes, I was! It was actually Google Voice setting itself up wrong or something and after I factory reset my SMS/MMS was working fine. I turned off Google's auto-app-restore and installed only the apps I needed and one at a time, trying SMS inbetween, since I knew it HAD to be an app if it worked after a factory reset but didn't after setting up my phone. I'd say if you have Google Voice to uninstall it completely. Some setting in there messed up my phone. If you don't have Voice installed, honestly the best thing to do is factory reset and makes sure SMS is working, then install each app one at a time. I know it sounds like a lot but that's what worked for me.
If that doesn't work, this is what OnePlus's customer service had to say. It was seriously a lot of back and forth, and they were incredibly helpful, even if it didn't fix my issue, it might fix yours, so I'll post out conversation below:
Email with R (OnePlus) said:
Jacob K
Jul 20 09:34
I got my device today, the 64GB sandstone black, and put in my AT&T sim card. The phone worked as usual-or so I thought. My data works. 4g LTE on the wireless network, group MMS works, and I even receive SMS fine. But I'm not able to send out any SMS for some reason. I get left with a "Message not sent" notification. I tried this first with the stock app then tried Hangouts and neither worked. I checked my APN and everything seems to be correct. I'm just at a loss, as it's odd that I can receive both SMS and MMS and even send MMS but I can't send out SMS. Is there something I can do to resolve this?
R (OnePlus)
Jul 22 13:27
Hi Jacob,
Let's try a few things to help you solve your SMS problem.
First, turn off your OnePlus One, carefully remove the SIM tray, and then power on your OnePlus One. Let it finish booting up. Obviously it will say there is no SIM inserted, cause there isn't!
Next, turn off your OnePlus One again. Carefully put the SIM tray/card back in the same way you took it out and power on again. Give your phone a few minutes to register on the network and get settled. Now, try to send an SMS, see if it works.
If we are back to square one, I'm going to have to gather a bit more info. As you probably already know, this problem is typically APN related. Are you using the PTA APN on At&t?
Would you mind downloading an SMS app called Textra (free) to see if you can send an SMS using this app please? Let me know if any of this stuff works, or not. Thanks.
Jacob K
Jul 22
to OnePlus
Alright, I tried all of the steps you gave me and it didn't work, so I tried again waiting longer in between each step and no luck. I also tried Textra and upon hitting the send button got an immediate notification that the message failed. I realize this seems to be a very specific problem because I've searched all over the internet and I've come up with no solutions. I posted in multiple forums with just one reply from someone else with the same issue. But since putting the ticket in I've also tried inputting the correct AT&T SMSC in all 4 formats to no avail. Every time I press update and re-enter it goes back to the old, which is in fact one of the correct SMSC's for AT&T (the one in quotes) with a ,145 tailing it (not sure what that's for). But any information you need I'll be glad to provide, and I greatly appreciate your response. I've been living off of Facebook messages and group chats the last few days, haha.
R (OnePlus)
Jul 22 14:46
Hey Jacob,
Cool, thanks for enduring a little troubleshooting and glad you understand the language of tech. Just to remove another obvious layer of doubt, please make sure you have updated to the latest version of CM via OTA. The fact that you can receive SMS messages makes this an interesting puzzle to solve.
For our next attempt, we will try something a little more drastic before I ultimately suggest a factory reset, but lets put that on the back burner for now.
Go to settings/apps and then swipe right 2 times to reach the 'All' category
For each of these apps: Phone/Messaging Storage , Messaging , Hangouts , and com.android.smspush
Perform this process: Force stop, Clear cache, Clear data
Do a restart when you are done and fire off an SMS when you are rebooted to a stable state. Any luck?
Jacob K
Jul 22
to OnePlus
Alright, no luck with that either, so I just sucked it up and did a factory reset. I tried sending an SMS immediately after and it worked, so I thought I was good. But then after I allowed Google to install all of my old apps, I tried it again and no luck. But I did notice when Google Voice installed, CM asked me if I wanted to use Voice+ (or something along those lines) and I said yes, chose my Gmail and allowed it to access my G+ info, but after that it asked me which email to use again and wouldn't go away until I clicked out of it. Then I had to swipe the notification away, so I figured Voice might be the culprit, uninstalled and voila, working SMS.
So maybe something in the Voice settings was messing things up, or maybe the CM Voice+ thing messed it up since it worked fine on my old phone. Not sure, but I'm happy to have fixed it. Everything works great now! And even though we weren't able to fix the problem through the troubleshooting steps you provided, I realize this was a difficult and very specific and local issue.
[insert nerdy thank you note here]
Click to expand...
Click to collapse
Bliznade said:
Yes, I was! It was actually Google Voice setting itself up wrong or something and after I factory reset my SMS/MMS was working fine. I turned off Google's auto-app-restore and installed only the apps I needed and one at a time, trying SMS inbetween, since I knew it HAD to be an app if it worked after a factory reset but didn't after setting up my phone. I'd say if you have Google Voice to uninstall it completely. Some setting in there messed up my phone. If you don't have Voice installed, honestly the best thing to do is factory reset and makes sure SMS is working, then install each app one at a time. I know it sounds like a lot but that's what worked for me.
If that doesn't work, this is what OnePlus's customer service had to say. It was seriously a lot of back and forth, and they were incredibly helpful, even if it didn't fix my issue, it might fix yours, so I'll post out conversation below:
Click to expand...
Click to collapse
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Parvinder25 said:
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks.. Didn't find that setting but uninstall works perfect.
Sent from my A0001 using XDA Free mobile app
Parvinder25 said:
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Parvinder25: Could you perhaps elaborate on exactly where these "connection settings" are located? I could not find them anywhere within the Google Voice app. I'd like to keep using GV for its visual voicemail feature, however it seems to completely disable my ability to send MMS messages (although they do send after GV is uninstalled). I've located a toggle to receive text messages either within google or through the messaging app, however the messaging app was already selected. That would be the only toggle I could locate within GV that remotely relates to messaging. Thanks in advance.
Hello Parvinder,
It was glad that you have resolved this issue, i am also facing similar issue with my One Plus One mobile - MESSAGING. I am using AT&T network. I couldn't fine Google Voice+ in the apps or settings. I can just see Google Voice but, i am not able to find which setting needs to be disabled or Uninstalled? Could you please provide exact navigation for the same would be great help for me and other users on this blog.
Appreciate your help.
Thanks,
Venki
So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou
It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.
Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon
I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.
The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.
Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.
Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!
I tried uninstalling and reinstalling the Google app, clearing cache in app and on phone. Retrained the voice in Google app a dozen times. Nothing is working. Side note: my SIM card is still installed in my old 5T. the 7 Pro doesn't have a SIM card. Not sure if that is a factor. Assistant works fine. *UPDATE: "OK Google" will launch when prompted when display is locked but it won't answer or respond to whatever I ask it. "OK Google" will not launch or respond when phone is unlocked at all.
I'm having similar issues but mine stops responding once I connect to my car stereo... And doesn't respond even after disconnecting until I reboot.
7 pro?
Same issue OK Google will NOT work on the One Plus 7 pro for some reason on my end
Did all that was suggested , Clear Cache , Clear Data, Disable Google, Reboot, then Endable google, retrain my voice
But still on the home screen when I say OK Google nothing happens
Anyone have a FIX for the Oneplus 7 pro? Thanks
BTW Stock 9.5.7 GMA21AA Firmware
Model GM1917
STOCK Not Rooted
I'm assuming you are rooted using Magisk? See my post here:
https://forum.xda-developers.com/oneplus-7-pro/help/google-match-lockscreen-t3936647
qwen3579 said:
I'm assuming you are rooted using Magisk? See my post here:
https://forum.xda-developers.com/oneplus-7-pro/help/google-match-lockscreen-t3936647
Click to expand...
Click to collapse
Not rooted. Using Nova and I restored from a Nova backup if that matters.
robdam1001 said:
Not rooted. Using Nova and I restored from a Nova backup if that matters.
Click to expand...
Click to collapse
Interesting. Sorry I can't help then. I had the exact same issue but was able to to resolve it by adding Google Framework to Magisk Hide. Since you're not rooted, this doesn't apply. Maybe try resetting to factory and see if it works before restoring any backups?
rooted, with custom kernel and custom launcher. OK Google works like a charm.
qwen3579 said:
Interesting. Sorry I can't help then. I had the exact same issue but was able to to resolve it by adding Google Framework to Magisk Hide. Since you're not rooted, this doesn't apply. Maybe try resetting to factory and see if it works before restoring any backups?
Click to expand...
Click to collapse
Just did factory reset and ok Google is now working. It hasn't finished restoring, however. I'll report back once it has. What a pita.
UPDATE: OK Google is working fine after Factory Reset, (PITA), and full restore.
That is what I was afraid of ,doing a full factory reset
If anyone has another solution that avoids that please let me know
Thanks all
Mine seems to work when the phone is awake however I have noticed that for some reason the Google pill widget does not show the 'ok google' text that normally shows up on my other phones.
Using stock launcher so not a 3rd party problem.
Anyone else notice this?
Not entirely helpful here other than to tell you that I'm not experiencing the same thing. ?
Full factory reset as a solution, lol. C'mon guys
No better solutions? Are we the only unlucky ones here.
The similar issue I have also come across on my phone and believe me, it was very irritating situation as I am not getting any way to fix it. Even I was not able to understand why it was happening but after searching a lot, I have got some solutions given in one blog. So if you are also coming across the same issue like "OK Google Not Working" then try the below solutions:
Solution 1: Restart Your Android Phone
Solution 2: Force Stop Google App
Solution 3: Clear Cache of Google App
Solution 4: Turn Off Bixby [For Samsung Users]
Solution 5: Make Sure That OK Google Command Is Enabled
Solution 6: Check Microphone On Your Device
Solution 7: Turn Off Adaptive Battery And Battery Saver Option
An old one here but have you installed any third party notification app like notifybuddy or plus beat? Ok Google won't work with these installed. The only notification app that doesn't interfere is AOE.
I have noticed a similar issue with voice-to-text being terrible and when this is happening OK Google does not work although it could be problem that happens even after OK Google is working but the voice to text is terrible at recognizing words. After android 10