Related
I have a lot of apps installed, and while Go Launcher does indeed allow me to add more icons than the MotoBlur launcher, sometimes I need that odd app that I haven't pinned to the home screen.
Google Search -- the app itself, that launches through the search button when you're at the home screen -- allows searching for installed apps and launching them directly, as long as you type the first few letters of the program.
I got used to this on my old Nexus One, especially with CM7, which allowed me to long press the Search button and it would launch GSearch no matter where I was. After finding a way to do this via a third party helper utility on the Atri, I can launch Search via a long press, but the app search itself works about 1/3 of the time. Most of the time it returns nothing.
I may be in the minority of users who use search to launch apps, but when I have around 150 installed apps, it's a pain to have to look through the launcher every time you need a particular app.
On Froyo, the app search feature was also buggy, and was hoping they would fix it by now, but on GB it's the same story.
Anyone experience this as well?
Click the search button then the top left icon and on the top right click on the preference button ..make sure app search is checked.
Works fine for me. Give me an app that doesn't work for you and I'll be glad to try it.
Xda app via atrix
I've enabled it, disabled web and contacts search, so app search results should be the only thing coming up.
What I mean is not that a particular app doesn't come up, but rather that the search functionality stops working all together. As in, no matter what I type, nothing is returned in the search results. I can't figure what triggers this. I just rebooted the phone and it's working fine, and as I continue using the phone, it will stop working.
At the end of the day, it's just a nuisance that can be worked around, but it was a neat little shortcut I got used to.
i have about 75 or so apps installed, so i kinda know your pain. but, the search feature has always worked for me in the past, currently using ninja speed freak 0.4.5 with Faux's kernel.
do you have any mods/roms installed on your Atrix?
Deblured by freezing some Motorola processes and of course rooted. Nothing else, and like I said, it works, but only some of the time.
I would suggest checking it after it's been a while since last reboot to see if you can reproduce the problem.
This happened in Froyo as well, and on my previous Atrix, so it's definitely reproducible between phones and different OS versions.
Well. At least you can use the app groupings!
Sent from my MB860 using Tapatalk
I also had such issue till now. just now i tried going to the setting of search and unselected selected apps and google search. it now work.. may be the setting got refreshed.. u may try this..
Works completely fine for me. Could be something your freezing that makes it buggy? Or maybe GoLauncher?
ive always had the same issue, on stock, roms, whatever i'm running. I would search for an app, and the only thing that would show up is the term i typed in with a magnifying glass (signifying searching the web). I'd go into search settings and make sure APPs are checked... then i search again, and the apps show up!
I find I have to constantly go into search settings and then press back for applications to show up. it's annoying. It ends up working though, but why can't it work the first time?
Seems to me that something so basic should not be so buggy by version 2.3.4 of an OS. Maybe once we get CM7 it won't be a problem anymore, based on my experience with it on my n1.
s1mpd1ddy said:
ive always had the same issue, on stock, roms, whatever i'm running. I would search for an app, and the only thing that would show up is the term i typed in with a magnifying glass (signifying searching the web). I'd go into search settings and make sure APPs are checked... then i search again, and the apps show up!
I find I have to constantly go into search settings and then press back for applications to show up. it's annoying. It ends up working though, but why can't it work the first time?
Click to expand...
Click to collapse
You don't need to go to setting everytime just type the app name expand search icon and tap on app your app will show in search result works for me
Sent from my unlocked rooted and 2.3.4 Atrix using tapatalk
Hem, that does work, thank you. It's still annoying that searching "all" doesn't work, but the "apps" sub category does, but I'll just have to get used to it till they get it working correctly.
Works just fine for me, 4.5.91 installed ota (rooted w/ preinstall, no bl unlock)
hem.acharya said:
You don't need to go to setting everytime just type the app name expand search icon and tap on app your app will show in search result works for me
Sent from my unlocked rooted and 2.3.4 Atrix using tapatalk
Click to expand...
Click to collapse
lol it works! but damn it should be the FIRST thing that shows up! instead of having to go thru all the other options
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.
Normally I'd have this issue fixed per the typical ways to fix but as of yesterday I cannot change any permissions nor can I access my camera or video files. Before you go into the rant of going into settings and disabling any apps that use screen overlay I have done that to every single app and system app as well as disabled the accessibility options....I still get the message. Any clues that might be helpful? I have Build MRA58k version BLU_R0011UU_v21_GENERIC 05-05-2017 short of doing a twerp recovery to an old image I don't know what to do.
Talzoid said:
Normally I'd have this issue fixed per the typical ways to fix but as of yesterday I cannot change any permissions nor can I access my camera or video files. Before you go into the rant of going into settings and disabling any apps that use screen overlay I have done that to every single app and system app as well as disabled the accessibility options....I still get the message. Any clues that might be helpful? I have Build MRA58k version BLU_R0011UU_v21_GENERIC 05-05-2017 short of doing a twerp recovery to an old image I don't know what to do.
Click to expand...
Click to collapse
Please more deatil on your problem.
what are you tring to do?
what app cannot access photo files?
and also try search the forrum for "overlay" I think there was one other disscussion about it, dont remember if anything got resovled or not.
Here:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333/page23
start at post 222-- its not much help but I knew this had been disscussed before.
mrmazak said:
Please more deatil on your problem.
what are you tring to do?
what app cannot access photo files?
and also try search the forrum for "overlay" I think there was one other disscussion about it, dont remember if anything got resovled or not.
Here:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333/page23
start at post 222-- its not much help but I knew this had been discussed before.
Click to expand...
Click to collapse
I am trying to change my permissions so that I can use my phone for recording videos but it refuses to let me view any of my files in my gallery. It doesn't matter if I go through the app or if try to view it through a file viewer such as file manager, nothing will let me access them. In fact I can not change permissions for any app, can't change what can and cannot access my storage, can not change what accesses my phone, nothing can be changed. It's not just those apps, every app I try to change permissions for has the same message. As I stated before I have disabled ALL draw over other apps, System as well as normal but the message still pops up even after a reboot........It all started 3 days ago, I didn't install anything new and as far as my security programs show, I have not been infected with a virus or malwear....
Just an update... 9 days and still not fixed... I have had to install different programs for some of my functionality back however I still cannot change any permissions... Some apps will allow me to tap outside of the notification and still use them however some things I still cannot do such as view recently recorded vids or recently taken pictures. Still hoping someone can find a fix for this issue.
So I downloaded an unzipped the files, anyone notice there seems to be a lot less files...... anyone notice this? I did last year's DP1 but I don't remember the details.
djcrystals said:
So I downloaded an unzipped the files, anyone notice there seems to be a lot less files...... anyone notice this? I did last year's DP1 but I don't remember the details.
Click to expand...
Click to collapse
Got the ota running it seams faster than android pie
I think it isnt that smooth , at least compared to pie
I tried to use Deuce's flash, that didn't work. I tried to root it using Canary Magisk. That didn't work.
djcrystals said:
I tried to use Deuce's flash, that didn't work. I tried to root it using Canary Magisk. That didn't work.
Click to expand...
Click to collapse
No Q root via Magisk until major rewrite it seems.
https://twitter.com/topjohnwu/status/1105947979679191041
There are more tweets after that explaining why and the complexities of the new Q partition layout.
Thanks! I was rushing before work. I figured I'd give it a shot. I wasn't totally surprised it ended in failure.
Cant find dark mode ... Cant tell any major diferecnces ... Its basically pie with a Q
DMart9406 said:
Cant find dark mode ... Cant tell any major diferecnces ... Its basically pie with a Q
Click to expand...
Click to collapse
Need to set it before upgrading or set it via ADB:
https://www.androidpolice.com/2019/...toggle-so-turn-it-off-or-on-before-upgrading/
DMart9406 said:
Cant find dark mode ... Cant tell any major diferecnces ... Its basically pie with a Q
Click to expand...
Click to collapse
Apparently you gotta use ADB to enable it. There's a recent article regarding it.
https://www.xda-developers.com/android-q-toggle-dark-theme/
I cant upload photos , dont know why , it takes me to main xda page when i close the window , but in dev options ( in settings) the last section lets you choose font type (2 available ) , main colour of the ui and icon type( 4 available )
I cant tell if they were there before
Trying to upload the screenshot i took , i found that the app to choose files is renewed , for better
DMart9406 said:
I cant upload photos , dont know why , it takes me to main xda page when i close the window , but in dev options ( in settings) the last section lets you choose font type (2 available ) , main colour of the ui and icon type( 4 available )
I cant tell if they were there before
Trying to upload the screenshot i took , i found that the app to choose files is renewed , for better
Click to expand...
Click to collapse
Using Chrome?
Did we have root on DP1 Pie? I can't remember.....
djcrystals said:
Did we have root on DP1 Pie? I can't remember.....
Click to expand...
Click to collapse
Yep. TJW had that one handled a couple of days after it was out. Doesn't look like the case this time however. Google apparently doesn't like us rooting evidently!
Anyone know if OnePlus gestures works okay on Q?
biggiestuff said:
Anyone know if OnePlus gestures works okay on Q?
Click to expand...
Click to collapse
It's working for me, but it appears to need more forceful gestures than previously. But this might be because I fitted a new screen protector yesterday!
In reading the twitter feed by Magisk dev John Wu, it may come sooner than expected, his last couple of tweets made it seem like he had narrowed the problem down a bit. Also, another user hinted at a possibility of getting it working via an alternate method, but I haven't seen anything else.
But since this thread is about Q, let me say this:
1) I already had dark mode on in Pie.
2) I had root via Magisk, but completely uninstalled it (without locking the bootloader though), so no FDR needed.
3) First attempt at taking the OTA left me in a weird partial (stock) recovery where it said that the OTA could not be applied (I'm paraphrasing), and had the options to try again or FDR. I hit try again and it rebooted back to the same place - I hit try again a second time and et voila! it rebooted to Android and I have Q now on my Taimen. No idea why that happened, and I haven't performed any checks to see if it maybe flipped to the other slot or something (which I highly doubt, as it was extremely quick from when I pressed the try again to when it rebooted and started booting Android Q).
So, first thoughts:
The Google Feed now has a bit of translucency - pretty cool!
Settings is now dark mode
Notifications are also dark, double yay!
Night light is working better - the blue accents in settings, etc now also dull, the way they should.
Redesigned Files app - looks nice! Those items at the top are selectable, individually or in groups.
I've started an album at my GPHotos with screenshots I've taken thus far. See https://photos.app.goo.gl/pdbTnXZNYpQ3xBFS6
It's 1:30 AM now. I'm off to bed.
I feel the fingerprint sensor works very fast and very accurate. Can anyone please conform.
Battery Saver activates Dark Mode
Rvarma said:
I feel the fingerprint sensor works very fast and very accurate. Can anyone please conform.
Click to expand...
Click to collapse
I can confirm this. I'm using Pixel 2 XL and Pixel XL and after update to Q beta I can feel fingerprint sensor works faster on both devices. even I can feel so much faster response on Pixel XL
Can anyone confirm that edit button on screenshot notification is broken for you too ?
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?