I've made a small module that broadcasts an intent when the "OK, Google now" trigger phrase is recognised. The intention is to listen for the intent with an app such as Tasker and do your own voice interface from there. This module stops all native Touchless Control functions, so you have to handle any commands you want on your own. The screen does not turn on if it was off and internet connectivity is not required.
There are two beeps I haven't been able to track down yet, though one can be disabled via the Touchless Controls settings.
Xposed Repository
http://repo.xposed.info/module/com.hawkjm.okgooglenowtriggerintent
I'm not well versed in tasker, could you help me make a tasker action to here the ok Google now phrase then open the app utter and start listening
Sent from my XT1056 using xda app-developers app
charlie-n said:
I'm not well versed in tasker, could you help me make a tasker action to here the ok Google now phrase then open the app utter and start listening
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
First, you need a profile. It'll need an event for Intent Received, with com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER in the Action field.
Next, you'll need a task to command utter. I'm using autovoice, so I'm not terribly up to date on utter. They've got instructions and examples in this thread:
http://forum.xda-developers.com/showpost.php?p=34339449&postcount=2155&nocache=1&z=7169357333332300
Hello, I've been using the "Google Now API" module for xposed framework with the tasker autovoice plugin. How is this module different exactly? The way I described, touchless controls is left intact and functions exactly how it would otherwise, but a command is given through autovoice to tasker, and Google now opens and does a search on whatever command you entered. What is different with your module?
Thanks in advance...
This module basically hijacks the touchless controls trigger so you can do your own voice interface. My use case is :
-say "Ok, Google now"
-Tasker launches AutoVoice recognition
-I say something like "Start my car"
-Tasker handles the request and starts the car
My goal was to allow this to happen completely in the background, and with the screen off. This doesn't disturb anything else I might be doing on the phone, nor does it activate the screen. Also, it uses onboard recognition is available, and so is a bit faster then having Google Now do the recognition.
I've tried something very simple and it won't work please correct this if I'm wrong.
1. Open tasker
2 create profile /system/intent received
3. Typed com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER into the action field.
4. Hit back
5. Enter task menu pops up, and I click new task.
6. I give the task a name, then I click + to add action. I select App/ load app/ calculator.
7. I go back to main menu and make sure profile is active.
8. I go to home screen and say "ok Google now" I hear a beep. No action happens.
Does any one see anything wrong
Sent from my XT1056 using xda app-developers app
Lately, I've been needing to add steps to get Tasker to act as expected. Once you've completed your profile and task, completely exit Tasker, making sure to hit "save first." Then, if needed, deactivate and reactivate Tasker's monitor by long-pressing the little gear in the left corner. I usually run a little task that pops a toast then to make sure it is active. In most cases, just the full exit and save is sufficient.
If that doesn't work, check in Tasker's log to see if it is seeing the intent. If no, check your logcat for the intent being broadcast.
I fixed it, I had to install secure settings app to wake screen then launch the app I wanted, utter had so Manu more commands
Sent from my XT1056 using xda app-developers app
Is "Secure Settings" required for this to happen? Does Tasker need to be made an Administrator?
**Edit**
Looks like SS is required
This post should be way more populated, the possibilities of this plus tasker are endless
Sent from my XT1056 using xda app-developers app
Is this module designed for KK or is it compatible with JB. I can't seem to get any logs in the tasked app. Will check logcat.
You should also check out with caioketo is doing in his thread http://forum.xda-developers.com/showthread.php?t=2623063, seems pretty similar to this and they are still trying to retain Google Now functionality if you want.
I'm going to try this out as soon as I get to my aunts phone. She got the x because moto advertised it for seeing impaired. I ended up having to use tasker and autovoice to make it speak back to her but it uses so much battery. Thanks for doing this! I will be back with my results.
Just installed this, brilliant!
Commands that needed autovoice are executed immediately, if I needed Google now I just have an autovoice tasker triggered command for running the voice search app (too bad it seems we can't easily transfer a command from autovoice to gnow, but I now have instant autovoice, and one more step for Google now voice search, » ok Google now, search, "speak command")
Tapatalk - Moto X XT1058
Cyphir said:
Is this module designed for KK or is it compatible with JB. I can't seem to get any logs in the tasked app. Will check logcat.
Click to expand...
Click to collapse
I wrote for and tested on a kitkat device. Unfortunately, I don't have a moto JB on hand to check it on.
Check the Xposed logs for errors if you don't see anything in the logcat or Tasker logs. Let me know if you find anything.
cocchiararo said:
Just installed this, brilliant!
Commands that needed autovoice are executed immediately, if I needed Google now I just have an autovoice tasker triggered command for running the voice search app (too bad it seems we can't easily transfer a command from autovoice to gnow, but I now have instant autovoice, and one more step for Google now voice search, » ok Google now, search, "speak command")
Tapatalk - Moto X XT1058
Click to expand...
Click to collapse
I looked in to dumping audio to Google Now as Touchless Controls does, but it needs stringent app permissions. It might be doable from inside TC, but I'm not sure if you can record audio at the same time you're doing voice recognition. If not, you'd just end up wasting time. (saying stuff twice) I'm likely to try and elaborate on this module over time.
hawkjm73 said:
I wrote for and tested on a kitkat device. Unfortunately, I don't have a moto JB on hand to check it on.
Check the Xposed logs for errors if you don't see anything in the logcat or Tasker logs. Let me know if you find anything.
I looked in to dumping audio to Google Now as Touchless Controls does, but it needs stringent app permissions. It might be doable from inside TC, but I'm not sure if you can record audio at the same time you're doing voice recognition. If not, you'd just end up wasting time. (saying stuff twice) I'm likely to try and elaborate on this module over time.
Click to expand...
Click to collapse
I show a error in the xposed framework whenbI have this module active
Code:
java.lang.NoSuchMethodError: com.motorola.audiomonitor.bc#a(float,com.motorola.audiomonitor.t)#exact
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:208)
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:155)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:167)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at com.hawkjm.okgooglenowtriggerintent.AudioTrigger.handleLoadPackage(AudioTrigger.java:71)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:202)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:527)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1300(ActivityThread.java:148)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1311)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5167)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)
at dalvik.system.NativeStart.main(Native Method)
Cyphir said:
I show a error in the xposed framework whenbI have this module active
Code:
java.lang.NoSuchMethodError: com.motorola.audiomonitor.bc#a(float,com.motorola.audiomonitor.t)#exact
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:208)
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:155)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:167)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at com.hawkjm.okgooglenowtriggerintent.AudioTrigger.handleLoadPackage(AudioTrigger.java:71)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:202)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:527)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1300(ActivityThread.java:148)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1311)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5167)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
Your apk is an old version, try updating it with the latest version, or, it could be 2 versions (one KK and other JB).
caioketo said:
Your apk is an old version, try updating it with the latest version, or, it could be 2 versions (one KK and other JB).
Click to expand...
Click to collapse
I have the most up to date TC.apk for my phone. I am still running JB.
Cyphir said:
I have the most up to date TC.apk for my phone. I am still running JB.
Click to expand...
Click to collapse
From that error, I suspect there are two different versions of Touchless Controls, one for KK, and one for JB. Their classes have changed tether dramatically as they update. Can you send me your TC apk? I'll see if there are matching classes.
hawkjm73 said:
From that error, I suspect there are two different versions of Touchless Controls, one for KK, and one for JB. Their classes have changed tether dramatically as they update. Can you send me your TC apk? I'll see if there are matching classes.
Click to expand...
Click to collapse
I will upload it later today when I an home. In the mean time, the apk in TitaniumBackup is named Touchless Control 3.15.0.1
You may be able to find it online before I get a chance to upload it.
Related
THIS DOC IS NO LONGER ACTIVELY MAINTAINED!
Sorry for this, but real life took over and managed to take so much of my time up that I’m no longer able to verify and test stuff on my own. Besides, since Android Wear 6 a lot of things changed and I’d have to test all of these apps again.
Greetings dear Android Wear users!
Today I got my LG G Watch and I'm just amazed by the capabilities of that watch so I thought I'd create a list of all working sideloaded apps.
For everyone who doesn't know: Sideloaded Apps are .apk files installed directly to the watch via ADB.
Since Android Wear is technically the same and the specs for every watch are also kind of in the same range this list will most likely apply to your own Android Wear watch too, even when it's not an LG G Watch.
Please report any weird behaviors here with the keywords mentioned below to make things easier for me to search and add to the list.
--------------------
Useful Links:
Apps2Wear - Directly install APKs onto your watch via your SmartPhone
How to Sideload Apps onto your Android Wear device (YouTube)
Easily download any APK file directly from the Google Playstore
Easily launch apps from your watch
Un/Install Android Wear apps (Google Docs)
--------------------
The list of all sideloaded apps working on Android Wear can be found on Google Docs (to make things more simple for me to update).
------------------------------------------------------------
CLICK HERE TO SEE THE LIST (Google Docs)
Will be updated over time
------------------------------------------------------------
Want to help?
If you want to help making this list bigger and better please write the following keywords into your reply/report so I can find things easier and faster:
"Tested & Working" - App install works and application is running and starts without a force-close.
"Tested & Crashing" - App installed but crashes/force-closes at start up.
"Tested & Report" - App installed and runs fine but is unusable (e.g. GUI is too big, example would be Temple Run 2)
This makes my work a whole lot easier and my thankfulness for you even bigger
And now: Have fun testing!
Can you make to work the SwiftKey and WhatsApp in a smart watch?
iannolsen said:
Can you make to work the SwiftKey and WhatsApp in a smart watch?
Click to expand...
Click to collapse
Probably not SwiftKey (minuum is probably best suited to wear anyway), and definitely not WhatsApp. If you look at the guide by Corbin Davinport on pushing APKs to android wear, he says that he found that apps that require internet connection do not work. Therefor, WhatsApp wont be able to directly connect, as you would design the app so that it works through the devices Bluetooth connection to connect to the internet. However, I believe the developer of Wear Messenger has an app that lets you access WhatsApp through text messages, which then allows you to use WhatsApp from wear messenger.
The second point of this post is directed at OP,
In the google docs, it lists "Don't tap the white tile" as partially working and intermittently crashing in certain game modes. Once again referring to the guide by Corbin, the crashes arise whenever the app try's to show an ad. If you go into the settings and disable banner ads and only allow popups, you can get to the end of the game without the app crashing. It probably will crash at the end though if it tries to show an ad as this tries to connect to the internet, and that causes apps on wear to crash. One would probably be able to fix this by decompiling and recompiling the application to remove ads.
thejonnyd said:
Probably not SwiftKey (minuum is probably best suited to wear anyway), and definitely not WhatsApp. If you look at the guide by Corbin Davinport on pushing APKs to android wear, he says that he found that apps that require internet connection do not work. Therefor, WhatsApp wont be able to directly connect, as you would design the app so that it works through the devices Bluetooth connection to connect to the internet. However, I believe the developer of Wear Messenger has an app that lets you access WhatsApp through text messages, which then allows you to use WhatsApp from wear messenger.
The second point of this post is directed at OP,
In the google docs, it lists "Don't tap the white tile" as partially working and intermittently crashing in certain game modes. Once again referring to the guide by Corbin, the crashes arise whenever the app try's to show an ad. If you go into the settings and disable banner ads and only allow popups, you can get to the end of the game without the app crashing. It probably will crash at the end though if it tries to show an ad as this tries to connect to the internet, and that causes apps on wear to crash. One would probably be able to fix this by decompiling and recompiling the application to remove ads.
Click to expand...
Click to collapse
Hey, thanks for this tip! Will correct it as soon as I'm in the office again
That guide I know, even know the guy who made it. I'll probably create a tiny little program which will make pushing, installing and initializing the connection easier.
Sent from my Xperia Z1 Compact via XDA mobile app
EpicLPer said:
Hey, thanks for this tip! Will correct it as soon as I'm in the office again
That guide I know, even know the guy who made it. I'll probably create a tiny little program which will make pushing, installing and initializing the connection easier.
Sent from my Xperia Z1 Compact via XDA mobile app
Click to expand...
Click to collapse
That would be incredibly handy if you made that, I am surprised no one has so far.
Maybe one to add to the list would be Es3, its handy having a file manager on the device.
thejonnyd said:
That would be incredibly handy if you made that, I am surprised no one has so far.
Maybe one to add to the list would be Es3, its handy having a file manager on the device.
Click to expand...
Click to collapse
Well I tested ES File Explorer (if you mean that) and it's pretty well useable actually but some parts would require a back-button sadly. Means via ADB faking a key input.
Sent from my Xperia Z1 Compact via XDA mobile app
EpicLPer said:
Well I tested ES File Explorer (if you mean that) and it's pretty well useable actually but some parts would require a back-button sadly. Means via ADB faking a key input.
Sent from my Xperia Z1 Compact via XDA mobile app
Click to expand...
Click to collapse
Yep thats what I mean, strange that that happens, I haven't had any issues with needing to get back. Swiping from the centre of the screen to the right has gone back for me in all of the menus :s
Anyway to get c25k free or Nike running app working?
I will let you use many more apps on your wear device
hi,
for information i'm the developer of a companion app for android smartwatch.
SWApp Link
https://plus.google.com/u/0/communities/108675494963196634299
https://play.google.com/store/apps/details?id=com.preiss.swapps.link
Since yesterday i'm working on adapting it for wear.
Besides it's own feature, it has a specific feature that could make many more apps working on wear: it has a remote clipboard feature that allow to set the clipboard on the wear device from your phone.
They are many apps that don't work on the wear because they need text entry: this would allow you to type the needed text on your phone and paste it in those apps.
Cyril
cyrilp said:
hi,
for information i'm the developer of a companion app for android smartwatch.
SWApp Link
https://plus.google.com/u/0/communities/108675494963196634299
https://play.google.com/store/apps/details?id=com.preiss.swapps.link
Since yesterday i'm working on adapting it for wear.
Besides it's own feature, it has a specific feature that could make many more apps working on wear: it has a remote clipboard feature that allow to set the clipboard on the wear device from your phone.
They are many apps that don't work on the wear because they need text entry: this would allow you to type the needed text on your phone and paste it in those apps.
Cyril
Click to expand...
Click to collapse
Wow, awesome! This would make such things far easier
Sent from my Xperia Z1 Compact via XDA mobile app
"Tested & Crashing" All in one Gestures
"Tested & Crashing" All in one Gestures
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures
tonydd said:
Anyway to get c25k free or Nike running app working?
Click to expand...
Click to collapse
Nike wouldn't side load but c25k free did but never worked. Still looking for comparable running app.
Nokia Here maps works offline on watch, but only Sony smart watch has GPS atm. And change of density required to be able to start navigation.
I tested Terminal emulator and it is working well with minuun keyboard.
So far I have the following sideloaded and working on an LG G Watch
NES-FC Lite (NES Emulator)
QQplayer (video player WITH BLUETOOTH SOUND!)
ES File Explorer
Astro Bluetooth Module (to transfer files from phone->watch)
v1_Bluetooth_Arduino (to control my garage door connected to an arduino/BT Shield)
wolfebaine said:
So far I have the following sideloaded and working on an LG G Watch
NES-FC Lite (NES Emulator)
QQplayer (video player WITH BLUETOOTH SOUND!)
ES File Explorer
Astro Bluetooth Module (to transfer files from phone->watch)
v1_Bluetooth_Arduino (to control my garage door connected to an arduino/BT Shield)
Click to expand...
Click to collapse
Thanks! Added
cyrilp said:
"Tested & Crashing" All in one Gestures
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures
Click to expand...
Click to collapse
Added but can you please tell me which Watch you used?
EpicLPer said:
Added but can you please tell me which Watch you used?
Click to expand...
Click to collapse
sure: LG G W R
Just got my LG Watch G and I tested all sorts of apps after installing the "Ghoma rom", below are some of the apps not on the list I tried.
Tested & Working
Retry
https://play.google.com/store/apps/details?id=com.rovio.retry&hl=en
Game complains about missing Google Play Services but if you "ok" the prompt the game will load and seems to be fully playable. The built in "ad" button that opens a ad to view and earn coins does not work. You must earn coins the hard way in game.
EDIT: The game seems to be usable once every boot, in my case I had to reboot the watch to play the game again.
Tested & Report
Speedtest.net
https://play.google.com/store/apps/details?id=org.zwanoo.android.speedtest&hl=en
The app loads but doesn't do anything because there isn't system wide internet access.
Tested & Crashing
Youtube
https://play.google.com/store/apps/details?id=com.google.android.youtube&hl=en
Crashes and fails to load anything.
Keepass2Android
https://play.google.com/store/apps/details?id=keepass2android.keepass2android&hl=en
There are two versions of this app, regluar and offline. I tested the regular one and it crashes and fails to load anything.
8-ball Pool
https://play.google.com/store/apps/details?id=com.miniclip.eightballpool&hl=en
Crashes and fails to load anything.
NHK World TV Live
https://play.google.com/store/apps/details?id=jp.nhkworldtv.android&hl=en
Starts to load but crashes complaining about internet access.
Starbucks
https://play.google.com/store/apps/details?id=com.starbucks.mobilecard&hl=en
Crashes and fails to load anything.
ICE
https://play.google.com/store/apps/details?id=com.queader.ice&hl=en
The game doesn't even seem to try loading, no crash message. But it causes the screen to rotate till it silently crashes in the background.
Angry Birds Friends
https://play.google.com/store/apps/details?id=com.rovio.angrybirdsfriends&hl=en
Loads to a black screen and just sits there. Required putting the watch to sleep with the palm gesture to exit.
2FA apps
Was disappointed to see these crash on start:
Google Authenticator
RSA SecureID
Not really surprised, but it would have been nice
babelmonk
Few hours ago @explainAndroid posted article on xda main page onto how to use android's hidden RUN_IN_BACKGROUND permission to restrict app's background behavior. I made an app for that.
Here's link to original article: https://www.xda-developers.com/freeze-app-background-processes-without-root-android-nougat/
Here's link to app's github: https://github.com/MrBIMC/RunInBackgroundPermissionSetter
Here's link to reddit thread about app: https://www.reddit.com/r/Android/co...en_run_in_background/?st=j570s1rf&sh=675cc4d6
Here's link to xda labs: https://labs.xda-developers.com/store/app/com.pavelsikun.runinbackgroundpermissionsetter
Omg it created multiple threads. Sorry. Trying to remove duplicates now.
Submit this to XDA Labs as well! Don't worry about a crappy icon or whatever. I've made apps in Tasker and have posted them to Labs hehe. As long as people find it useful feel free to submit!
@MrBIMC
Thanks for the app!!
Is possible add hours of the days of week when selected apps run or doent run in background?
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Nice app!
Will charging disable this?
Can u make the app work without rooting, just using adb, where the permission through adb for this app is granted once and then it can be used to limit background permission of other apps
excellent mate.
we should post a tutorial... not everyone will understand the potential ramifications of disabling everything
I will try to test this out! Though, I kinda like the old icon compared to the new one, it seems like it's not properly cropped. Additionally, could you add an option to show system and user apps only? Maybe a toggle to ignore apps all at once or vice versa too?
No chance for Marshmallow?
Does this have the same functionality as in lineage os ROMs app ops where you can disable background processes?
As someone is undoubtedly going to ask it, I'll ask it for them. How does this differentiate to apps like greenify @MrBIMC? Do they both limit background processes? Anyways, the all looks very interesting, thanks!
This looks great!
Do the settings stick after reboot?
arjuntsgowda said:
Can u make the app work without rooting, just using adb, where the permission through adb for this app is granted once and then it can be used to limit background permission of other apps
Click to expand...
Click to collapse
No.
From the Github page:
Anyway, this app is for those who don't want to mess with adb shell and input commands manually and prefer to just click on app name to enable/disable it from running in the background. Sadly, android apps are not allowed to implicitly edit permissions of other apps, so this application requires root to overcome it.
Click to expand...
Click to collapse
Al Gore said:
No chance for Marshmallow?
Click to expand...
Click to collapse
No.
From the Github page:
Anyway, this app is for those, who don't want to mess with adb shell and input commands manually and prefer to just click on app name to enable/disable it from running in the background. Sadly, android apps are not allowed to implicitely edit permissions of other apps, so this application requires root to overcome it.
Click to expand...
Click to collapse
jordirpz said:
@MrBIMC
Thanks for the app!!
Is possible add hours of the days of week when selected apps run or doent run in background?
Click to expand...
Click to collapse
This would be really cool. Best way to implement that I think would be to add Tasker plugin functionality to the app to allow Tasker flows to toggle the permission, which would have the benefit of being able to change it for any reason (such as low battery).
DEVILOPS 007 said:
As someone is undoubtedly going to ask it, I'll ask it for them. How does this differentiate to apps like greenify @MrBIMC? Do they both limit background processes? Anyways, the all looks very interesting, thanks!
Click to expand...
Click to collapse
If I understand both correctly... Greenify forces apps to hibernate when you turn your screen off (or manually tell it to), but the app can still wake itself back up for a variety of reasons, such as receiving push notifications, location updates, or any other unnecessary reason like Facebook, lol. This app overrides a hidden permission in Android 7+ that tells the system to not allow the app to run in the background, which means it will not be able to wake itself up.
hassan_1000 said:
Does this have the same functionality as in lineage os ROMs app ops where you can disable background processes?
Click to expand...
Click to collapse
according to the reddit comments its the same. but maybe the Developer can confirm this
xdauser7 said:
according to the reddit comments its the same. but maybe the Developer can confirm this
Click to expand...
Click to collapse
Am Developer. Can confirm, toggle "limit background activity" in LOS14 is the same as this app. At least that's what reddit tells me as I haven't checked myself.
Wow. Looks promising. I was too lazy to run ADB manually xD
So lets see if I can screw something up with disabling almost everything
MishaalRahman said:
Submit this to XDA Labs as well! Don't worry about a crappy icon or whatever. I've made apps in Tasker and have posted them to Labs hehe. As long as people find it useful feel free to submit!
Click to expand...
Click to collapse
Ditto
neonixxx said:
This would be really cool. Best way to implement that I think would be to add Tasker plugin functionality to the app to allow Tasker flows to toggle the permission, which would have the benefit of being able to change it for any reason (such as low battery).
If I understand both correctly... Greenify forces apps to hibernate when you turn your screen off (or manually tell it to), but the app can still wake itself back up for a variety of reasons, such as receiving push notifications, location updates, or any other unnecessary reason like Facebook, lol. This app overrides a hidden permission in Android 7+ that tells the system to not allow the app to run in the background, which means it will not be able to wake itself up.
Click to expand...
Click to collapse
thanks, makes sense about Greenify... do you or anyone know the difference between this and Brevent?
dimm0k said:
thanks, makes sense about Greenify... do you or anyone know the difference between this and Brevent?
Click to expand...
Click to collapse
I actually tried Brevent for the first time a few weeks ago. According to the app itself, aside from not requiring root, it's supposed to monitor when you hit the back button or remove an app from recents, and then actually kill the app process when you do, despite if the app has some background process that it intended to keep running. Basically lets you manually control when an app is killed in a quick and intuitive way, but for me personally, it didn't seem to work as expected for some reason; background processes seemed to keep running after.
Also Brevent, being a non-root solution requires you to connect the device to a PC and run some ADB commands to give it permission every time you reboot. It has an experimental root mode that doesn't require this.
*****UPDATE APRIL 5, 2018 - This guide will activate the FULL Google Assistant!***** USE THIS GOOGLE APP AS OF DECEMBER 8 2018, https://www.apkmirror.com/apk/googl...oogle-app-8-33-6-21-arm-android-apk-download/
Many of you probably recall my last guide on getting 'ok Google' to work. Well Sort of: How to guide: Enable 'ok Google' to work from ANY screen. You may also recall it was a bit of work to get it working and the downside was the modifications didn't hold after a reboot, assuming the system didn't shut the service down first. So I put the project on hold until I could figure it out.
Well it's been 6 months and I am happy to report I have found a permanent solution which will activate the FULL Google Assistant on ANY non-rooted or rooted Amazon device. All we will do today is make a few small edits within the settings of FireOS. The modifications WILL survive reboots!
If you are using Alexa, you will Have to disable it and install the latest version of the Google App located at this link. Make sure to also have Google Play Services installed.
****WARNING: THE FOLLOWING APPLICATION IS VERY POWERFUL. MAKING THE WRONG EDITS CAN RESULT IN A POTENTIAL, UNRECOVERABLE BRICK. I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICES.****
1. You can download Settings Database Editor, install it and make the edits within that application (not recommended) or you can follow along with me and we'll use ADB. But if you do choose the application, you need to grant it the proper permission. Please plug your tablet into your PC and open an ADB window and type the following line below:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
2. Open Settings Database Editor. You will see three choices at the top: system, secure and global. Please, ONLY select 'secure'.
3. Scroll all the way to the bottom and you will see:
Code:
voice_interaction_service
voice_recognition_service
4. Tap on voice_interaction_service. A window will pop up that says 'edit setting'. Delete any text currently in the window if there is any and type the text below into it with NO SPACES:
Code:
com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
OR use ADB:
Code:
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
5. Tap on voice_recognition_service. A window will pop up that says 'edit setting'. Delete any text currently in the window if there is any and type the text below into it with NO SPACES:
Code:
com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
OR use ADB:
Code:
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
6. Scroll all the way back to the top of Settings Database Editor. At the very top of the list, tap 'Add new setting'. For the first entry type:
Code:
assistant
and tap 'save changes.' Now type in in the second entry:
Code:
com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
and save changes.
7. In the list, locate the setting
Code:
alexa_enabled
and tap on it. Change the number from a 1 to 0 and save changes.
That's it. You should be done! Now reboot your tablet using ADB:
Code:
adb reboot
8. Now it's time to configure your Assistant. Open the Google App. > Tap three lines on bottom right corner > Settings > Voice > 'Ok Google Detection' > Set the preferences to your liking. You will have to train your voice model so make sure you do that first. When done, tap back twice. Make sure your search language is set to English and your search region is The United States. See the next step as to why.
9. Go here and download the Google Assistant APK, install it and open it. You will get a message saying your device isn't compatible with Assistant, but that's ok. Installing the APK will ensure your tablet receives the proper upgrades when Assistant is made available for 5.0 devices.
I hope everyone enjoys this! I am so excited to get this working
Thanks, great job! I can confirm it works great on Fire HD 8 OS 5.6.0.1. I even think the microphone is more responsive with this method. Yes, Google Assistant is somewhat more limited on Lollipop, but it's still useful anyway.
I used the Settings Database Editor app. It's not "scary" if you follow the directions. It makes me wonder what more can be done to this little tablet to make it more "root-like" with Settings Database Editor and ADB.
Thanks!
wcarlson40 said:
Thanks, great job! I can confirm it works great on Fire HD 8 OS 5.6.0.1. I even think the microphone is more responsive with this method. Yes, Google Assistant is somewhat more limited on Lollipop, but it's still useful anyway.
I used the Settings Database Editor app. It's not "scary" if you follow the directions. It makes me wonder what more can be done to this little tablet to make it more "root-like" with Settings Database Editor and ADB.
Thanks!
Click to expand...
Click to collapse
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Awesome bro.
I'm using fire 8 in India, they have disabled Alexa based on location. If I change my Amazon account location to US, I get Alexa. But, changing back the location to India, disables Alexa again. Alexa option won't be visible in the settings menu.
Do you think, is there anything I can edit in settings app to get Alexa?
---------- Post added at 05:18 AM ---------- Previous post was at 05:18 AM ----------
DragonFire1024 said:
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Click to expand...
Click to collapse
Can't wait
DragonFire1024 said:
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Click to expand...
Click to collapse
That would be awesome, as I couldn't find much other info at all about this app and its uses.
There also seems to be a whole bunch of AOSP settings hidden in the software you obviously can't use, such as mobile networks, GPS, and the LED notification light.
Tweaks I have done so far:
Toggle either full or partial immersive mode in certain apps
Remove lockscreen ads (doesn't work in 5.6)
Nothing else I tried yet I couldn't already do in the regular settings app.
DragonFire1024 said:
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Click to expand...
Click to collapse
You never fail to impress
This worked for me but some functionality is missing. If I say "Okay Google, set a timer for [x] minutes." It will just do a Google search for those words. It doesn't automatically open up the Clock app and start the timer. This is with the default Clock app disabled and the Google Clocl app installed.
autobulb said:
This worked for me but some functionality is missing. If I say "Okay Google, set a timer for [x] minutes." It will just do a Google search for those words. It doesn't automatically open up the Clock app and start the timer. This is with the default Clock app disabled and the Google Clocl app installed.
Click to expand...
Click to collapse
In the past few weeks I learned that unless the app is actually uninstalled, the system still recognizes it as an app. THis will be as close to the assistant as we get, until it's rolled out to all of Lollipop devices. Also, without Gapps being part of /system/priv-app, a lot of the functionality won't be possible. However, I do see to recall the voice assistant working for the alarm, or basic system functions. It could be possible, that Google stopped that function to lollipop devices or it's just simply mucked by one, or Amazon patched it as well.
Assistant now fully working
Been checking daily whether launching the assistant shortcut would work. Yesterday night it went from assistant not available on this device to Google assistant is not your chosen assistant. After following this guide and rebooting now I have full Google assistant with home control etc!
xperia709 said:
Been checking daily whether launching the assistant shortcut would work. Yesterday night it went from assistant not available on this device to Google assistant is not your chosen assistant. After following this guide and rebooting now I have full Google assistant with home control etc!
Click to expand...
Click to collapse
Does this include the full assistant you get in 6.0+?
Sent from my Samsung Galaxy S4 using XDA Labs
I also just got the full Google Assistant yesterday afternoon. It appears to be the same as what's on 6.0+ tablets.
lakitu47 said:
I also just got the full Google Assistant yesterday afternoon. It appears to be the same as what's on 6.0+ tablets.
Click to expand...
Click to collapse
This is great. It looks like they likely finally rolled it out to Lollipop devices. Let's hope it isn't another mistake!
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Does this include the full assistant you get in 6.0+?
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Yup, the full assistant experience. I have google's clock, play music, spotify installed, works with all of them just like on normal 6.0+
Bet they're enabling server side for all tablets now 5.1+ and above, even though the page still says 6.0+ on google's site. Wake word seems to work with screen on but not off. Still so much better than alexa. You also lose the long press home to activate, tried using a nav button app on xposed but that ended up breaking the framework and I almost couldn't use the tablet.
xperia709 said:
Yup, the full assistant experience. I have google's clock, play music, spotify installed, works with all of them just like on normal 6.0+
Bet they're enabling server side for all tablets now 5.1+ and above, even though the page still says 6.0+ on google's site. Wake word seems to work with screen on but not off. Still so much better than alexa. You also lose the long press home to activate, tried using a nav button app on xposed but that ended up breaking the framework and I almost couldn't use the tablet.
Click to expand...
Click to collapse
There are a few edits in the framework that fix that and allow for the home button to long press to the Installed assistant app. I forget where though. When I get home I'll look through my notes and find it once I set this up again. With root it's a fairly easy fix.
Sent from my Moto E4 using XDA Labs
Confirmed. Appears the FULL assistant is now available using my original methods. However it requires only the first 2 ADB commands to get everything working. This also works on Fire Launcher which makes this even more glorious.
I haven't had luck with this for the 8" HD as far as the full functionality goes. Now that Alexa works hands-free for it, I don't see it as a big deal but it works great for the 10", though
dondraper23 said:
I haven't had luck with this for the 8" HD as far as the full functionality goes. Now that Alexa works hands-free for it, I don't see it as a big deal but it works great for the 10", though
Click to expand...
Click to collapse
Tested it in HD 8 and worked perfectly. Haven't tried it on my HD 10 yet.
Side note: I've tried this on other 5.1 devices, not from Amazon, and it doesn't work. So this is likely a fluke from and update to the Google app. The other suggestion would be to try the beta APK. I started on a fresh FireOS 5.4.0.0 and downloaded play services and Google beta APK. Not sure if that makes a difference or not. None the less, get it while you can if you can
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Tested it in HD 8 and worked perfectly. Haven't tried it on my HD 10 yet.
Side note: I've tried this on other 5.1 devices, not from Amazon, and it doesn't work. So this is likely a fluke from and update to the Google app. The other suggestion would be to try the beta APK. I started on a fresh FireOS 5.4.0.0 and downloaded play services and Google beta APK. Not sure if that makes a difference or not. None the less, get it while you can if you can
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
I'm sure I just did something wrong then cuz all I was getting was a google search everytime I tried to get it to work with the 8HD. I'll give it another go on Sunday
keep getting this error at step 1... wish there was a bat or something I could download for this
C:\platform-tools>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Bad argument: java.lang.IllegalArgumentException: Unknown package: by4a.setedit22
lovemesomeandroidyo said:
keep getting this error at step 1... wish there was a bat or something I could download for this
C:\platform-tools>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Bad argument: java.lang.IllegalArgumentException: Unknown package: by4a.setedit22
Click to expand...
Click to collapse
To use ADB, you MUST have USB debugging enabled in developer options.
If you're using Windows, make sure you use Command Prompt (cmd.exe) instead of PowerShell.
Open a command prompt window in the location of the Platform Tools. Type in "ADB shell" first, then wait for it to connect. You may need to allow debugging from your computer on your tablet from a pop-up dialog. Then type in the rest of the command starting at "pm grant" after [email protected][device codename].
I hope I'm starting this thread in the right section, if not apologies in advance.
I updated the apps on my Samsung Note 4 a few days ago and found all my Google voice search requests being directed to Google assistant, which is slow and useless if all you want to do is search the internet. I have Nova launcher installed and all their Google search widgets and actions are also being redirected to Assistant.
Seems this issue is related to this development:
https://www.androidpolice.com/2018/...s-voice-search-completely-switches-assistant/
If I open the Chrome browser on the phone the Google Voice search action is still working when you press the mic icon in the address bar, they obviously can't terminate the service there.
My question is how can I get back a widget or homescreen shortcut to trigger a vanilla voice search(I'm assuming via Chrome) without the assistant barging in and making my life a misery?
If anyone can also point me to the best way to find a solution, hacking something together?
Am I the only one that is disappointed to see the demise of Voice search??
Bulletinabluesky said:
I hope I'm starting this thread in the right section, if not apologies in advance.
I updated the apps on my Samsung Note 4 a few days ago and found all my Google voice search requests being directed to Google assistant, which is slow and useless if all you want to do is search the internet. I have Nova launcher installed and all their Google search widgets and actions are also being redirected to Assistant.
Seems this issue is related to this development:
https://www.androidpolice.com/2018/...s-voice-search-completely-switches-assistant/
If I open the Chrome browser on the phone the Google Voice search action is still working when you press the mic icon in the address bar, they obviously can't terminate the service there.
My question is how can I get back a widget or homescreen shortcut to trigger a vanilla voice search(I'm assuming via Chrome) without the assistant barging in and making my life a misery?
Click to expand...
Click to collapse
Have you tried the Google Now launcher? Some devices can enable Google Now to use "Ok Google" from any screen.
My wife uses it, when she says "ok Google", it comes to attention, then she calls '"Assistant" to attention, then she can make requests to initiate any action that she wants such as: a Google search, open or close apps, send and read texts by voice command, make calla by voice command, etc...
The Google Now launcher does use more battery though.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried the Google Now launcher? Some devices can enable Google Now to use "Ok Google" from any screen.
My wife uses it, when she says "ok Google", it comes to attention, then she calls '"Assistant" to attention, then she can make requests to initiate any action that she wants such as: a Google search, open or close apps, send and read texts by voice command, make calla by voice command, etc...
The Google Now launcher does use more battery though.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi Droidriven, thanks for the reply that may be a work around but I can't drop Nova launcher.
I also have no need for "Ok Google" voice activation, all I need is a homescreen shortcut that when pressed directly opens the Voice search mic and listens for your voice and then immediately thereafter shows the Google search results. I tried using Nova Actions to try find the voice search command within the Google apps but as yet I haven't found it yet.
Even though Google has removed easy access to Voice search it must be possible to hack together a shortcut because the direct voice search functionality is still in the Chrome app. I'm hoping that one of the Devs on XDA may have pity on me and help to cobble something together
Bulletinabluesky said:
Hi Droidriven, thanks for the reply that may be a work around but I can't drop Nova launcher.
I also have no need for "Ok Google" voice activation, all I need is a homescreen shortcut that when pressed directly opens the Voice search mic and listens for your voice and then immediately thereafter shows the Google search results. I tried using Nova Actions to try find the voice search command within the Google apps but as yet I haven't found it yet.
Even though Google has removed easy access to Voice search it must be possible to hack together a shortcut because the direct voice search functionality is still in the Chrome app. I'm hoping that one of the Devs on XDA may have pity on me and help to cobble something together
Click to expand...
Click to collapse
Read this, try the instructions in the last post, if you haven't already tried.
https://forums.androidcentral.com/lg-g6/858333-help-voice-search-toggle.html
Sent from my LGL84VL using Tapatalk
Droidriven said:
Read this, try the instructions in the last post, if you haven't already tried.
https://forums.androidcentral.com/lg-g6/858333-help-voice-search-toggle.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, unfortunately that won't help because I have been using Nova to make the Voice shortcut on the home screen but after my recent updat of the Google apps those shortcuts that were previously activating a Voice search now are forced to activate the Google Assistant.
With the latest updates Google is obviously redirecting all legacy requests for a Voice search to the Assistant, which sucks balls
:crying:
Bulletinabluesky said:
Thanks, unfortunately that won't help because I have been using Nova to make the Voice shortcut on the home screen but after my recent updat of the Google apps those shortcuts that were previously activating a Voice search now are forced to activate the Google Assistant.
With the latest updates Google is obviously redirecting all legacy requests for a Voice search to the Assistant, which sucks balls
:crying:
Click to expand...
Click to collapse
Uninstall the updates and revert back to the versions that you had before the update, then don't update the apps unless the older versions no longer work correctly.
Also, on my device, I have a Voice Search icon in my app drawer that I can drag to home screen to do what you are trying to do. Do you have this? If not, see if there is a Voice Search app that can be installed from PlayStore, it may install over the existing voice search and show the icon in app drawer like it does on mine.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Uninstall the updates and revert back to the versions that you had before the update, then don't update the apps unless the older versions no longer work correctly.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That would work for a while but seeing it's googles core apps that are doing it not really feasible, I've tried doing something like that in the past and it's a real pita. I need a solution that will work now and going ahead, it is possible.
Bulletinabluesky said:
That would work for a while but seeing it's googles core apps that are doing it not really feasible, I've tried doing something like that in the past and it's a real pita. I need a solution that will work now and going ahead, it is possible.
Click to expand...
Click to collapse
I edited my previous post to add more info.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I edited my previous post to add more info.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Unfortunately that Voice search shortcut which you are referring to, and it is a native Google shortcut, now also defaults to the Assistant and doesn't trigger a voice search like it used to.
Bulletinabluesky said:
That would work for a while but seeing it's googles core apps that are doing it not really feasible, I've tried doing something like that in the past and it's a real pita. I need a solution that will work now and going ahead, it is possible.
Click to expand...
Click to collapse
Also, yes, sometimes workarounds are a pita, but we have to learn to go ahead and settle for what we can get in the now until we can get another solution figured out, even if it isn't specifically what we want at the time. There is nothing that says you have to permanently settle for the workaround, you might find an alternative that is better than the workaround, but you can at least get some kind of functionality at this time but continue the search for a better solution.
Sent from my LGL84VL using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
Bulletinabluesky said:
Unfortunately that Voice search shortcut which you are referring to, and it is a native Google shortcut, now also defaults to the Assistant and doesn't trigger a voice search like it used to.
Click to expand...
Click to collapse
Try finding a way to disable/remove assistant. I don't have assistant and I'm using the current Google apps, but I'm on 7.0, not 8 or 9.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Also, yes, sometimes workarounds are a pita, but we have to learn to go ahead and settle for what we can get in the now until we can get another solution figured out, even if it isn't specifically what we want at the time. There is nothing that says you have to permanently settle for the workaround, you might find an alternative that is better than the workaround, but you can at least get some kind of functionality at this time but continue the search for a better solution.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That is true but I need something that will be futureproof, whether I roll back the google apps now or not I still need to find a way around this issue. Hoping to hunt down an existing app that can do it
Hey everyone. I found this APK dump for the pixel watch one reddit. I got the pixel UI APK and it installs fine. When I set it as the default home app though it just crashes. I'm hoping if I provide the apk one of you more experienced users can perhaps mod this APK to work with our watches.
Link?
File?
APK Name?
Memo to me...
Google Pixel Subforum seems here:
Google Pixel Watch
forum.xda-developers.com
Link to APks I saw first time in this Thread...
Official List of Sideloaded Apps and Workarounds For Wear OS (Tested on Galaxy Watch)
SIDELOAD LIBRARY COMPATIBLE WITH WEAR OS 3 TESTED ON GALAXY WATCHES All Smart Watches Can Probably Benefit From This Guide Special thanks to everyone who has contributed to testing and providing feedback on various apps and versions. Thanks to...
forum.xda-developers.com
Best Regards
adfree said:
Link?
File?
APK Name?
Click to expand...
Click to collapse
Reddit Link for Pixel Watch APK
com.google.android.wearable.sysui.apk
Is file name for apk
After some Google Search...
No idea if different Version(s)...
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Edit 1.
Attempt from dump... "backup"...
Code:
D:\Android\ADB>adb install com.google.android.wearable.sysui.apk
Performing Streamed Install
Success
Edit 2.
I see only 2 ugly Icons... both nothing open...
Is this what you mean with crashes?
Short tested on GVI3...
Best Regards
adfree said:
After some Google Search...
No idea if different Version(s)...
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Edit 1.
Attempt from dump... "backup"...
Code:
D:\Android\ADB>adb install com.google.android.wearable.sysui.apk
Performing Streamed Install
Success
Click to expand...
Click to collapse
I found a link on APKPure it's the same version number as the dump from the pixel watch. Will probably have to be modded since it's crashing when trying to make default home app.
...when trying to make default home app.
Click to expand...
Click to collapse
How?
Btw... If I search for text string:
Code:
com.google.android.wearable.sysui
Inside old EVA8...
Then 2 GW4 files found:
Code:
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\framework\framework-res.apk
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\priv-app\ClockworkWcs\ClockworkWcs.apk
Best Regards
adfree said:
How?
Click to expand...
Click to collapse
In watch setting click app then default
adfree said:
Btw... If I search for text string:
Code:
com.google.android.wearable.sysui
Inside old EVA8...
Then 2 GW4 files found:
Code:
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\framework\framework-res.apk
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\priv-app\ClockworkWcs\ClockworkWcs.apk
Click to expand...
Click to collapse
Okay there's also APK from the dump that matches clockwork maybe that is needed
Sorry, I will check this ... then sleep or other stupid tests:
Phone by Google - Apps on Google Play
Reliable phone calls with spam protection, caller ID and more helpful features
play.google.com
Code:
D:\Android\ADB>adb install com.google.android.dialer.apk
Performing Streamed Install
Success
adfree said:
Sorry, I will check this ... then sleep or other stupid tests:
Phone by Google - Apps on Google Play
Reliable phone calls with spam protection, caller ID and more helpful features
play.google.com
Code:
D:\Android\ADB>adb install com.google.android.dialer.apk
Performing Streamed Install
Success
Click to expand...
Click to collapse
The Google dialer is already available in the watch play store
This is first time I found working Dialer for GW4...
Only Phone go or something similar... I was able before...
How to fire Secret Codes?
I can not * #
?
adfree said:
This is first time I found working Dialer for GW4...
Only Phone go or something similar... I was able before...
How to fire Secret Codes?
I can not * #
?
Click to expand...
Click to collapse
It could be your region does not have it available for gw4 in play store. However I'm in US an I was able to install it from there.
Also you can scroll down when you are in the dialer to see *#
I hope someone can port it too.
Yo, I'm the dude who dumped the Pixel Watch APKs on reddit. I've also tried tinkering around with getting the Home APP running on my GW4, but I'm not having any luck so far. I believe both com.google.android.wearable.sysui.apk and com.google.android.wearable.app.apk from the dump are responsible for the Home-Screen Experience. However as you said, if selected as the Home app on the GW4, the Sysui app just keeps crashing over and over.
Here's some notable things I found in the logcat during those crashes:
Code:
WindowManager: Permission Denial: addWindowTokenWithOptions from pid=2394, uid=10145 requires android.permission.STATUS_BAR_SERVICE
WindowManager: Permission Denial: addWindowToken() from pid=2394, uid=10145 requires android.permission.MANAGE_APP_TOKENS
ActivityManager: Permission Denial: Accessing service com.google.android.wearable.app/com.google.android.clockwork.wcs.service.notification.NotificationService from pid=2394, uid=10145 requires com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE
ServiceConnection: Failed to bind connection 'NotificationClient#com.google.android.wearable.app#com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE', no permission or service not found.
ServiceConnection: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
AndroidRuntime: FATAL EXCEPTION: WcsSdkWorkerThread
AndroidRuntime: Process: com.google.android.wearable.sysui, PID: 2394
AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
I've tried my best to grant the missing permissions using pm grant but that didn't change anything so far... Kind of at my wits end here.
By manually granting all the grantable permissions that the apks request, I was able to get it so far as to say 'Getting started...' before crashing over and over, but no luck in getting to the actual Pixel Watch home screen on my GW4
Quad_Plex said:
Yo, I'm the dude who dumped the Pixel Watch APKs on reddit. I've also tried tinkering around with getting the Home APP running on my GW4, but I'm not having any luck so far. I believe both com.google.android.wearable.sysui.apk and com.google.android.wearable.app.apk from the dump are responsible for the Home-Screen Experience. However as you said, if selected as the Home app on the GW4, the Sysui app just keeps crashing over and over.
Here's some notable things I found in the logcat during those crashes:
Code:
WindowManager: Permission Denial: addWindowTokenWithOptions from pid=2394, uid=10145 requires android.permission.STATUS_BAR_SERVICE
WindowManager: Permission Denial: addWindowToken() from pid=2394, uid=10145 requires android.permission.MANAGE_APP_TOKENS
ActivityManager: Permission Denial: Accessing service com.google.android.wearable.app/com.google.android.clockwork.wcs.service.notification.NotificationService from pid=2394, uid=10145 requires com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE
ServiceConnection: Failed to bind connection 'NotificationClient#com.google.android.wearable.app#com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE', no permission or service not found.
ServiceConnection: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
AndroidRuntime: FATAL EXCEPTION: WcsSdkWorkerThread
AndroidRuntime: Process: com.google.android.wearable.sysui, PID: 2394
AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
I've tried my best to grant the missing permissions using pm grant but that didn't change anything so far... Kind of at my wits end here.
By manually granting all the permissions that the apks request, I was able to get it so far as to say 'Getting started...' before crashing over and over, but no luck in getting to the actual Pixel Watch home screen on my GW4
Click to expand...
Click to collapse
Theory here is we most likely can't provide these permissions through ADB because they're system permissions provided by default on the Pixel Watch but don't exist on the GW4 (For all we know), which is why we're getting this error when we try to give them.
Code:
C:\Users\Test\Desktop\platform-tools>adb shell "pm grant com.google.android.wearable.app com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE"
Exception occurred while executing 'grant':
java.lang.IllegalArgumentException: Unknown permission: BIND_WEAR_CORE_PRIVILEGED_SERVICE
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(PermissionManagerService.java:1470)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1429)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2287)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:249)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:22522)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4730)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4523)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
The only possibility would be someone tries to give these permissions with a rooted watch.
Maybe, you can try
Cartesian8445 said:
Theory here is we most likely can't provide these permissions through ADB because they're system permissions provided by default on the Pixel Watch but don't exist on the GW4 (For all we know), which is why we're getting this error when we try to give them.
Code:
C:\Users\Test\Desktop\platform-tools>adb shell "pm grant com.google.android.wearable.app com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE"
Exception occurred while executing 'grant':
java.lang.IllegalArgumentException: Unknown permission: BIND_WEAR_CORE_PRIVILEGED_SERVICE
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(PermissionManagerService.java:1470)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1429)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2287)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:249)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:22522)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4730)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4523)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
The only possibility would be someone tries to give these permissions with a rooted watch.
Click to expand...
Click to collapse
Maybe it can be done by editing the app itself, I don't know...
Apparently the WearOS System UI is available on Google Play now?... Not sure if this is the same version as found on the Pixel Watch, however it's marked as 'incompatible' with the GW4
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Quad_Plex said:
Apparently the WearOS System UI is available on Google Play now?... Not sure if this is the same version as found on the Pixel Watch, however it's marked as 'incompatible' with the GW4
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Click to expand...
Click to collapse
Same .apk name, "com.google.android.wearable.sysui", probably posted on the play store so they can update it easier
Cartesian8445 said:
Same .apk name, "com.google.android.wearable.sysui", probably posted on the play store so they can update it easier
Click to expand...
Click to collapse
It's the same package, yea, but I'm not sure if it's the exact same version as the one I dumped before.
Quad_Plex said:
It's the same package, yea, but I'm not sure if it's the exact same version as the one I dumped before.
Click to expand...
Click to collapse
Yes, I was able to past the link for the play store version in APK pure and found that it is the same version on the dump.