Related
Hey guys, these instructions are based around Cyanogenmod 6 RC2, but should work fine for other ROMs if you've had trouble installing the updated Voice Search from the Market.
You MUST be running 2.2 (Froyo) for this to work however!
Updated this with instructions on how to fix the Google Search widget as well. Thanks to klinster, devlogic and OhioDroid.
Hey everybody, I don't know if anybody else is having this issue, but the new version of Google's Voice Search released today wouldn't install on my G1 (running CM6RC2) due to an incorrect signature. Anyway, there's a quick workaround, you just have to uninstall the voice search installed by default in CM6.
Anyway, if you have adb, plug into usb and run:
Code:
adb pull /system/app/ ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
If you don't, open Terminal Emulator on your phone (This does NOT backup the .apk's, so proceed at your own risk!) and run:
Code:
su
mount -o rw,remount /system
rm -f /system/app/VoiceSearch.apk
pm uninstall com.google.android.voicesearch
rm -f /system/app/GoogleQuickSearchBox.apk
pm uninstall com.google.android.googlequicksearchbox
Your old out of date versions are now removed. Now go to the Market and install "Voice Search" and "Google Search".
Anyway, this is all pulled from the Cyanogenmod Wiki and most have you probably have already figured this out. In case you were stuck though, hopefully this helped you resolve the problem.
What's working:
Google Search Box (Reply if you have problems with listed method)
Most Voice Actions
What isn't:
"set alarm" action seems to rely on an as-of-yet unreleased Clock app from google. I am unable to confirm this as I do not have access to a stock Nexus One.
-Thanks to klinster for backup line for adb
-Thanks to devlogic and OhioDroid for search widget fix
-Thanks to BinaryMan, fixed typo in adb commands
wow works perfect thank you!!
I was just thinking that someone should post this. Thanks for taking the time to write it up!
I just removed the voice search using the terminal emulator. Downloaded it from the market and it works fine without having to remove the quick search box.
everytime I run:
pm uninstall com.google.android.voicesearch
I get "failure"
Any ideas?
Thanks so much! This gave new life to my phone. I used terminal and after a few fails (my typing) entering commands I got it to work
I followed the directions and installed it successfully, but none of the new features seem to be working for me. Note to self doesnt work, text message doesn't work, email doesn't work. Every time I do it, it tries to google search whatever I said.
apreichner said:
I followed the directions and installed it successfully, but none of the new features seem to be working for me. Note to self doesnt work, text message doesn't work, email doesn't work. Every time I do it, it tries to google search whatever I said.
Click to expand...
Click to collapse
This is exactly what I'm experiencing too. I thought I was using the wrong syntax at first but it isn't that. Directions, search and calling work but the "note to self" , "send text to" and e-mail don't work.
It's case sensitive.
I got it to instal from market. But no widget. Is this correct?
on my myTouch 3G with Cyanogen 6, everything works except the search widget, and the physical search button.
the widget will only let you type 1 letter before dissapearing, then when you hit back, it's still in it's "searching" position at the top of the screen.
If you hold down the physical search button, it does bring up the voice search, but 1 tap no longer brings up the regular search box. I would REALLY like to see a fix for this soon, cause that's something I use probably 10-20 times a day.
Alright, if you've been having troubles with this bit:
Code:
pm uninstall com.google.android.voicesearch
Try running it as com.android.google.voicesearch instead.
The original documentation I found listed this com.android.google as the correct form, but it did not work on mine and several other people's roms. You may have the "correct" install listing on your rom however, so this could help.
The search widget should come with the Google Search .apk, and if you have not installed the latest Google Search version, the widget's voice command may not work. Try starting a voice action from the "Voice Search" app in your app drawer instead of the widget.
Lastly, the hard search button is currently not working and I do not know of a fix. It may be something that has to be rolled into a custom ROM later, as HTC and Google probably never considered support for hardware as old as the G1/MT3G :-/
thecolorifix said:
the widget will only let you type 1 letter before dissapearing, then when you hit back, it's still in it's "searching" position at the top of the screen.
Click to expand...
Click to collapse
I had the same problem. It was driving me nuts, and I just assumed the widget was worthless. But with the new apps, you get icons in your app drawer. One for Google Search and one for Voice Search. So I just put the two icons on my homescreen side by side. They take up half the space of the widget and work exactly the same, since tapping the Google Search icon starts the search bar just like the widget, and it works.
So, maybe not as elegant as having the search widget, but it takes up less space, looks nice, and works perfectly.
Are we waiting on an updated music player as well? When i use "listen to" it will only pull up pandora and not any of the music on my sd card.
Anyone else?
ty for the write up, worked perfectly thru terminal.
now i just have one question that may or may not be considered related but i tend to think it is.
how do a reasign apps to long press on buttons.
like when i long press the green phone button, it takes me to a bluetooth voice dialer which doesnt work, id like to set it to the actualy voice dialer then does work.
when i long press the search button i do get the brand new voice search application pop up which works amazingly, i have already tested out mutliple commands like text or navigate to.
Are there any issues with updating the voice search thing only and keeping the old version of the Google Search widget?
I got rid of the on screen search widget since I didn't see a point in dedicating the screen real estate to it if I could bring it up with a single button press anyway. However since the new one doesn't work with the button this is kind of a bummer
Thanks, worked like a charm on my G1
Thanks guys.
Tsenru said:
Hey guys, these instructions are based around Cyanogenmod 6 RC2, but should work fine for other ROMs if you've had trouble installing the updated Voice Search from the Market.
You MUST be running 2.2 (Froyo) for this to work however!
Updated this with instructions on how to fix the Google Search widget as well. Thanks to klinster, devlogic and OhioDroid.
Hey everybody, I don't know if anybody else is having this issue, but the new version of Google's Voice Search released today wouldn't install on my G1 (running CM6RC2) due to an incorrect signature. Anyway, there's a quick workaround, you just have to uninstall the voice search installed by default in CM6.
Anyway, if you have adb, plug into usb and run:
Code:
adb pull /system/app/ ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
If you don't, open Terminal Emulator on your phone (This does NOT backup the .apk's, so proceed at your own risk!) and run:
Code:
su
mount -o rw,remount /system
rm -f /system/app/VoiceSearch.apk
pm uninstall com.google.android.voicesearch
rm -f /system/app/GoogleQuickSearchBox.apk
pm uninstall com.google.android.googlequicksearchbox
Your old out of date versions are now removed. Now go to the Market and install "Voice Search" and "Google Search".
Anyway, this is all pulled from the Cyanogenmod Wiki and most have you probably have already figured this out. In case you were stuck though, hopefully this helped you resolve the problem.
What's working:
Google Search Box (Reply if you have problems with listed method)
Most Voice Actions
What isn't:
"set alarm" action seems to rely on an as-of-yet unreleased Clock app from google. I am unable to confirm this as I do not have access to a stock Nexus One.
-Thanks to klinster for backup line for adb
-Thanks to devlogic and OhioDroid for search widget fix
-Thanks to BinaryMan, fixed typo in adb commands
Click to expand...
Click to collapse
GREAT guide. I was finally able to Install the apps.
it worked.....thanx for the great post
robkoehler said:
Are we waiting on an updated music player as well? When i use "listen to" it will only pull up pandora and not any of the music on my sd card.
Anyone else?
Click to expand...
Click to collapse
I'm having the same issue.
Music add-ons: iSyncr and Music Mod, music folder on sd card/syncr.
HTC Incredible
SkyRaider 2.5.2 Vanilla
Baseband: 2.05.00.06.11
Hi,
There's an app that I really want to use but it keeps crashing, and I'd to send me a bug report with all the error messages. I was told that logcat does just that, and I'd be most appreciative if anyone could give me some help on how to use it. Specifically,
1) As I recall adb does not quite work with our g-tab (e.g. remount); how then should I run logcat?
2) I'm running adb on a terminal in an XP box. Is there a way to increase the number of "lines" the terminal would store, and how do I "save" these output?
3) My plan is to boot up the g-tab, start adb, then run the app and save all the error messages. Is that the correct procedure?
THANKS!
case-sensitive said:
Hi,
There's an app that I really want to use but it keeps crashing, and I'd to send me a bug report with all the error messages. I was told that logcat does just that, and I'd be most appreciative if anyone could give me some help on how to use it. Specifically,
1) As I recall adb does not quite work with our g-tab (e.g. remount); how then should I run logcat?
2) I'm running adb on a terminal in an XP box. Is there a way to increase the number of "lines" the terminal would store, and how do I "save" these output?
3) My plan is to boot up the g-tab, start adb, then run the app and save all the error messages. Is that the correct procedure?
THANKS!
Click to expand...
Click to collapse
There's an easier way. Get "Log Collector" from the market, then right after the app crashes, run Log Collector and it will easily let you email the log to the developer.
Hello everybody I was annoyed by the new camera and messenger icons that came with the latest Facebook update so I wrote Facebook Icon Remover to easily disable them. This application requires root. I've had reports that when disabling/enabling the icons the main Facebook icon may disappear from your home screen (but not your application drawer) but you can simply add it back. Let me know if you have any issues using this application.
EDIT: Just a heads up that I will no longer be supporting Facebook Icon Remover. If you wish to hide icons for any applications you should checkout my latest app CCSWE App Manager. More info here: http://forum.xda-developers.com/showthread.php?t=1639707
machx0r said:
NOTE: You shouldn't need this application if you are running ICS as it already provides a mechanism to hide applications in the app drawer.
Click to expand...
Click to collapse
Turns out it's very simple for manufactures to disable this option in the stock ICS settings app and from what I've seen it looks like most of them do. The latest version 1.0.4 has been updated to support ICS devices.
Thank you! Thank you! Thank you! Thank you!
Unintentionally sent from my Nexus One using xda Premium app.
Thank you very much, this is very useful.
Yeah! Thanks!
Works perfectly! AND! Keeps the icons off even after removing the app. Nice.
machx0r said:
Turns out it's very simple for manufactures to disable this option in the stock ICS settings app and from what I've seen it looks like most of them do. The latest version 1.0.4 has been updated to support ICS devices.
Click to expand...
Click to collapse
Out of curiosity: in Java, how do you disable apps for ICS? Always met by segmentation faults when using the PackageManager.
sibbor said:
Out of curiosity: in Java, how do you disable apps for ICS? Always met by segmentation faults when using the PackageManager.
Click to expand...
Click to collapse
I'm launching a process to start su and executing the pm command to disable components. There seems to be an issue in ICS with the LD_LIBRARY_PATH environment variable not getting set in a shell launched by su. See this thread for more details:
https://github.com/ChainsDD/su-binary/issues/6
machx0r said:
I'm launching a process to start su and executing the pm command to disable components. There seems to be an issue in ICS with the LD_LIBRARY_PATH environment variable not getting set in a shell launched by su. See this thread for more details:
https://github.com/ChainsDD/su-binary/issues/6
Click to expand...
Click to collapse
so u simply use
pm disable com.facebook.katana
or some additional commands are needed?
mike1986. said:
so u simply use
pm disable com.facebook.katana
or some additional commands are needed?
Click to expand...
Click to collapse
That would disable the entire Facebook application and all it's components. If you want to disable a specific component you need to provide the class also. From the pm help:
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
And...
The enable and disable commands change the enabled state of a given package or component (written as "package/class").
machx0r said:
That would disable the entire Facebook application and all it's components. If you want to disable a specific component you need to provide the class also. From the pm help:
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
And...
The enable and disable commands change the enabled state of a given package or component (written as "package/class").
Click to expand...
Click to collapse
soo...
that would be:
pm disable com.facebook.katana.activity.media.CameraLauncherActivity
pm disable com.facebook.katana.orca.ThreadListLauncherActivity
correct?
EDIT:
Nope, keep searching...
mike1986. said:
soo...
that would be:
pm disable com.facebook.katana.activity.media.CameraLauncherActivity
pm disable com.facebook.katana.orca.ThreadListLauncherActivity
correct?
Click to expand...
Click to collapse
That might work but I'm using the full names:
Code:
pm disable com.facebook.katana/com.facebook.katana.activity.media.CameraLauncherActivity
pm disable com.facebook.katana/com.facebook.katana.orca.ThreadListLauncherActivity
Now that the secret is out all my ad revenue is going to disappear ;-)
machx0r said:
Now that the secret is out all my ad revenue is going to disappear ;-)
Click to expand...
Click to collapse
oh damn I didn't know that was suppose to be a secret. I can remove my posts!
mike1986. said:
oh damn I didn't know that was suppose to be a secret. I can remove my posts!
Click to expand...
Click to collapse
No lol I'm totally joking. I've already told several people the commands I'm using and imagine the application will continue to be useful for people who don't want to go through the trouble of doing it manually. Glad I can help
machx0r said:
No lol I'm totally joking. I've already told several people the commands I'm using and imagine the application will continue to be useful for people who don't want to go through the trouble of doing it manually. Glad I can help
Click to expand...
Click to collapse
I wrote init.d script, might work as well
Code:
#!/system/bin/sh
# ========================================
# init.d script for Android Revolution HD
# ========================================
(
while : ; do
COMPLETED=$(logcat -d *:I *:D | grep -c android.intent.action.BOOT_COMPLETED)
if [ $COMPLETED -ne 0 ] ; then
echo "BOOT_COMPLETED: disabling Facebook icons"
pm disable com.facebook.katana/com.facebook.katana.activity.media.CameraLauncherActivity
pm disable com.facebook.katana/com.facebook.katana.orca.ThreadListLauncherActivity
sysrw
rm /system/etc/init.d/96facebook
sysro
exit 0
fi
sleep 1
done
) &
was just looking to how to remove this **** yesterday! thank you!
can you make one that can remove all the Latitude and google places icons... those annoy the hell out of me :S
danial.aw said:
can you make one that can remove all the Latitude and google places icons... those annoy the hell out of me :S
Click to expand...
Click to collapse
Working on it ;-) Shoot me a PM so I can let you know when my next app is ready.
machx0r said:
Working on it ;-) Shoot me a PM so I can let you know when my next app is ready.
Click to expand...
Click to collapse
I'm trying now to disable HTC Setup Wizard icon Also pissing me off
EDIT:
Code:
<application android:theme="@style/CommonTheme" android:label="@string/stupwizard_app_name" android:icon="@drawable/icon_launcher_htc_setup_wizard" android:taskAffinity="" android:description="@string/htc_company_name" allowSkinChange="true">
<activity android:label="@string/stupwizard_app_name" android:name=".MainActivity" android:taskAffinity="android.task.htcsetupwizard" android:screenOrientation="unspecified" android:configChanges="locale|mcc|mnc|keyboardHidden|orientation|screenSize">
So I guess there is no separated taskAffinity and I can't disable the icon without disabling the whole app.
Thanks you. Just what I was looking for since few days.
Among the slight annoyances I have with touchwiz, I really don't like Samsung's keyboard. If I disable it in input methods, it only stays disabled until I actually use the other keyboard/input method I have selected.
It turns itself back on and gives me a notification to select input method. As it's a samsung app, it can't be disabled in app settings. Would it be safe to just delete it completely? I don't think there's an option to disable the notification popup when you have multiple input methods turned on. extreme phone ocd
edit: nvm I guess, yolo deleted it, now to get rid of sfinder and QC in notification menu
#yolo
/thread
I'm unrooted and I disabled the keyboard via the ADB hide command. I'm guessing it can also be done using the app package disabler.
Fruktsallad said:
I'm unrooted and I disabled the keyboard via the ADB hide command. I'm guessing it can also be done using the app package disabler.
Click to expand...
Click to collapse
Did it stay hidden? Can you outline the steps to do this?
Yes, it stays hidden. Out of my memory, it goes along these lines; enable USB debugging in developer settings, connect your phone to your pc, open a terminal window and type:
adb shell
pm hide <name of the package to hide>
The "hide" command is supposedly new for lollipop, and is the equivalent of "block" which used to work in Kitkat. This can be done for other bloat as well and I've disabled a few other annoyances like this. Can't remember the name of the TouchWiz keyboard package right now (it's nothing logical like com.samsung.keyboard, but it's in there somewhere). I think the command for listing all packages is "pm list packages".
There are plenty of guides out there if you google it. It's really nice to be rid of that annoying notification.
Awesome. I will try this. Thank you so much.
---------- Post added at 09:05 AM ---------- Previous post was at 08:40 AM ----------
Fruktsallad said:
Can't remember the name of the TouchWiz keyboard package right now (it's nothing logical like com.samsung.keyboard, but it's in there somewhere).
Click to expand...
Click to collapse
Is it possibly com.samsung.InputEventApp?
flu13 said:
Awesome. I will try this. Thank you so much.
---------- Post added at 09:05 AM ---------- Previous post was at 08:40 AM ----------
Is it possibly com.samsung.InputEventApp?
Click to expand...
Click to collapse
Nope, mine was com.sec.android.inputmethod.
That did it. You are so awesome. Thank you.
Could this work on a Mac? I can't seem to get my device online when trying to run adb
I'm not a mac user, but I don't see why it wouldn't. ADB should actually work better on a mac than on Windows. Make sure you've enabled USB debugging under Developer Options on your phone and that you have the latest Samsung USB drivers installed.
I solved this issue by using Titanium Backup (rooted), click [Backup/Restore] button on top, look for 'Samsung Keyboard 4.0' then click 'Freeze'
There is a perfect app to disable any Samsung app without being rooted.
Its "Package Disabler Pro" on Google Play store.
Cost is $1.5 but it's extremely simple to use.
I searched for Samsung keyboard, found the package and disabled it. So simple !
No more Samsung keyboard, which compared to Swiftkey is very basic, absolutely not attractive and made only for Chinese girls with very thin fingers.
I'm still playing with adb shell ....
"pm list packages" doesn't show anything similar to Samsung Keyboard. Please, what is the name of this damned service!?
Q4bert said:
I'm still playing with adb shell ....
"pm list packages" doesn't show anything similar to Samsung Keyboard. Please, what is the name of this damned service!?
Click to expand...
Click to collapse
com.sec.android.inputmethod
I have a almost perfect solution for the wear os call bug. i have created an app which has to be installed on the phone. When your phone receives a call the app will keep trying to send notifications one after the other to the watch forcing the watch to wake and start ringing. of course the notifications will be automatically cleared once the watch is woken up. it seems to work reliability enough.
heres the link : https://gofile.io/?c=7DIfyo
Install the app on the phone and give it the necessary permissions.
Please refer to this thread if you are going to post somewhere else.
I would like to try it but all the link is doing is opening random adds and not going to any download . I' m a computer technician . I ve finnally found a way to bypass it , after opening adds 100 times
---------- Post added at 10:23 PM ---------- Previous post was at 10:05 PM ----------
I just tried , but I can't make it to install . I get to the screen where it say that no special permissions are required , and then to the not installed screen . I'm running a stock android pie xiaomi mi a2
Axel85 said:
I would like to try it but all the link is doing is opening random adds and not going to any download . I' m a computer technician . I ve finnally found a way to bypass it , after opening adds 100 times
---------- Post added at 10:23 PM ---------- Previous post was at 10:05 PM ----------
I just tried , but I can't make it to install . I get to the screen where it say that no special permissions are required , and then to the not installed screen . I'm running a stock android pie xiaomi mi a2
Click to expand...
Click to collapse
my apologies, i have built the apk using debug key, i have rebuilt the apk using a release key. i have updated my original post.
Tested on my LG Watch Style. Works well, thanks!
Looks like it's working . At least I receive the notification every time now . I also found a fix for the missed call notification dismissing on phone when the call feature on watch is activated ( don't know if everyone has the same ) . If I disable phone's app notification in wear os app on phone , the missed call notification is present both on watch and phone ( previously they appear on both but after a second the watch was dismissing the one on phone).
Let's share those two fixes because they mitigate 2 enormous bugs in wear os
Awesome.. it's works on my ticwatch s.. thanks..
Also now I tried to force disable phone app from doze on watch with this command:
adb shell dumpsys deviceidle whitelist +com.google.android.apps.wearable.phone
everything seems to work with the app present now in the battery optimization under development options as unavailable . After the first start , then everytime it s faster to notify a call
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
I even uninstalled mobvoi systema apps via this comand:
adb shell pm uninstall -k --user 0 your.app.name.goes.here
even if disabled from watch , this seems to free up more ram . Be carefull on your watch
---------- Post added at 05:45 PM ---------- Previous post was at 05:03 PM ----------
Let's try it for 2 or 3 days ... It's super fast now with your APK + my tweak to phone app doze . I have to try it without your app because I think the main problem on wear os is the fact that the system doze the phone app
Axel85 said:
Also now I tried to force disable phone app from doze on watch with this command:
adb shell dumpsys deviceidle whitelist +com.google.android.apps.wearable.phone
everything seems to work with the app present now in the battery optimization under development options as unavailable . After the first start , then everytime it s faster to notify a call
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
I even uninstalled mobvoi systema apps via this comand:
adb shell pm uninstall -k --user 0 your.app.name.goes.here
even if disabled from watch , this seems to free up more ram . Be carefull on your watch
---------- Post added at 05:45 PM ---------- Previous post was at 05:03 PM ----------
Let's try it for 2 or 3 days ... It's super fast now with your APK + my tweak to phone app doze . I have to try it without your app because I think the main problem on wear os is the fact that the system doze the phone app
Click to expand...
Click to collapse
That's interesting. I'll try that in my watch and post the findings here. And I have already removed all the mobvoi apps from the watch.
anton.fernando said:
That's interesting. I'll try that in my watch and post the findings here. And I have already removed all the mobvoi apps from the watch.
Click to expand...
Click to collapse
Since yesterday I'm trying the watch without your fix on phone . It's still working and it's super fast . I don't know what made a big change. I'm sure removing phone app from doze list is a game changer , but also unistalling all mobvoi apps from adb instead of only ticsystem + all the other from watch , released about 50 megs of ram
Axel85 said:
Since yesterday I'm trying the watch without your fix on phone . It's still working and it's super fast . I don't know what made a big change. I'm sure removing phone app from doze list is a game changer , but also unistalling all mobvoi apps from adb instead of only ticsystem + all the other from watch , released about 50 megs of ram
Click to expand...
Click to collapse
I tried disabling the app from doze mode. It worked for a couple of hours and the stoped working.i guess once the app has been removed from ram by the os due to low ram it seems to stop working.
What I have found though is that my apk+your solution seems to work best. As when the app is removed from ram my apk would force the device to wake up which would make it realise it's getting an incoming call thereby making the phone app run again and stay in the ram.
anton.fernando said:
I tried disabling the app from doze mode. It worked for a couple of hours and the stoped working.i guess once the app has been removed from ram by the os due to low ram it seems to stop working.
What I have found though is that my apk+your solution seems to work best. As when the app is removed from ram my apk would force the device to wake up which would make it realise it's getting an incoming call thereby making the phone app run again and stay in the ram.
Click to expand...
Click to collapse
For me this problem is not present , maybe because of the heavy debloat I've done ? I have 170 to 140mb of free ram . I continue testing , and keep your APK to reinstall if needed . Thank you , your solution is great , because I have to not mess with tasker or other similar workarounds that never worked for me .
After some days of testing , my solution + your apk is the best . Now I receive the calls on watch 100% the times in 2 or 3 seconds in the worst cases
Deleted
Deleted
Do we need to use adb to remove doze or "Dont Optimize" will help?
adb shell dumpsys deviceidle whitelist +com.google.android.apps.wearable.phone
Work like a charm on my Watch Style, good job it's perfect
anton.fernando said:
I have a almost perfect solution for the wear os call bug. i have created an app which has to be installed on the phone. When your phone receives a call the app will keep trying to send notifications one after the other to the watch forcing the watch to wake and start ringing. of course the notifications will be automatically cleared once the watch is woken up. it seems to work reliability enough.
heres the link : https://gofile.io/?c=7DIfyo
Install the app on the phone and give it the necessary permissions.
Please refer to this thread if you are going to post somewhere else.
Click to expand...
Click to collapse
Do u mind to share the source.
anton.fernando said:
I tried disabling the app from doze mode. It worked for a couple of hours and the stoped working.i guess once the app has been removed from ram by the os due to low ram it seems to stop working.
What I have found though is that my apk+your solution seems to work best. As when the app is removed from ram my apk would force the device to wake up which would make it realise it's getting an incoming call thereby making the phone app run again and stay in the ram.
Click to expand...
Click to collapse
Edit: My info is incorrect. Adding apps to the doze whitelist overrides any memory optimisation (source: https://developer.android.com/about/versions/pie/power)
You can try to change the memory optimisation priority of the phone app so that it is not removed from RAM;
Code:
adb shell am set-standby-bucket com.google.android.apps.wearable.phone active
Source:
https://www.reddit.com/r/TicWatch/comments/f2mymx/ticwatch_pro_incoming_call_delay/
anton.fernando said:
I have a almost perfect solution for the wear os call bug. i have created an app which has to be installed on the phone. When your phone receives a call the app will keep trying to send notifications one after the other to the watch forcing the watch to wake and start ringing. of course the notifications will be automatically cleared once the watch is woken up. it seems to work reliability enough.
heres the link : https://gofile.io/?c=7DIfyo
Install the app on the phone and give it the necessary permissions.
Please refer to this thread if you are going to post somewhere else.
Click to expand...
Click to collapse
The link is not working, Do you have an alternate link please?
ruknaednihs said:
The link is not working, Do you have an alternate link please?
Click to expand...
Click to collapse
Try this.
Sul mio TicWatch PRO 3 LTE, non accuso Nessun Ritardo nell'attivazione della suoneria sull'orologio durante una chiamata in arrivo sul telefono ...
..anzi vibra prima l'orologio e poi squilla il telefono ...:freddo:
Apprezzo pero' il lavoro dell'amico Anton Fernando ...Bravo