Related
Hello i'm new to the nadorid world but this is bassically what i'm stuck with:
i know that andorid devices use a TCP conection to mobile-gtalk.l.google.com or mtalk.google.com on port 5228 this is continuos conection to recive incoming push data and if other data i do not know.
Emulators like andy do a conection to that url and por from the Oracleheadless virtual box they use to run android. Bluestacks connect to it from the exe file HD-Networking.exe.
This bring me to an interesting point bassically a client app can be created on a computer to recive incoming push from our devices too with. i tried to see what is the protocol or how to do this but i have not found any documentation on the subject the closes thing to any like that is this post that is veru old i can´t post links yet but just google for faking-the-green-robot-part-1 )
i want to know if any of you guys know or have an idea of how to monitor the push channel of a phone or emulator to learn the protocol and implement it on an app or if there is a place i can look to learn that.
i want to create something similar to bluestack runnign natively for specif android app but i need to be able to recive push notifications in some way.
if only way is using a virtual box i'm open to it but also i do not know how to read the notification from it.
thanks in advance.
I have a 2013 model LG Google TV G3 55GA6450 that was recently gifted to me. Whenever I try to configure it to use the built-in tuner as my video source, I encounter "Unfortunately, VideoInputSetup has stopped"
According to this G+ thread, the error has to do with Google no longer supporting the local channel / programming lineup service thus causing the app to crash, and making the TV unusable as there is no other way to enable the TV Tuner input option without the app.
I have already tried force closing the 'VideoInputSetup' app, clearing its cache, etc. Also tried were a factory reset and using a custom launcher shortcut to launch the different functions of the app. Nothing has worked so far. I am willing, (with help) to extract the app and send it along to whoever and see if they can fix. Or to help any other steps / process to fix the issue.
Optionally, if someone might be willing to help me root and/or upgrade the device to newer Android TV, that would be awesome
I'm having same ANNOYING problem! This guy says he managed to root the TV but not sure if it will help. You need to go to the article since I can't post a url
forum.xda-developers.com/android/help/lg-google-tv-rooted-t2811945
Any fix?
Anyone find a fix to this yet?
deeluk said:
Anyone find a fix to this yet?
Click to expand...
Click to collapse
Negative. I was able to find a way to manually add channels to the tuner, but it is currently useless without a way to enable the tuner for Input selection.
Thanks! Could you share the manual process to add channels? Right now, I have a fancy wall paper, would at least like to watch the morning news. Thanks in advance!
deeluk said:
Thanks! Could you share the manual process to add channels? Right now, I have a fancy wall paper, would at least like to watch the morning news. Thanks in advance!
Click to expand...
Click to collapse
This will only work if you already have the "Buil-In Tuner" option available under Inputs.
You will need an app to launch custom shortcuts, I am using QuickShortcuts. Some custom launchers can also do this.
In the shortcut app, find the Settings application under "Activities". Expand it and then scroll through the activities until you find "Manual Tuning" (com.android.settings/com.android.settings.lge.channel.ManualScanActivity) and select that and finish setting up the shortcut to it. Launch the shortcut and add the channels you want.
and is there anything that we can using inseed to do this manually? It is working but there is a bad pop up saying "no paired devices found" and I can't change channel.
Thanks
Awesome, it works! It's clunky, but I can see a few channels now. Really hope someone has a hack through a rooted approach.
Do you know if anyone are working to root the GA7900 or other GTV3?
deeluk said:
Awesome, it works! It's clunky, but I can see a few channels now. Really hope someone has a hack through a rooted approach.
Click to expand...
Click to collapse
I've tried decompiling the VideoInputSetup apk to see if I could manually change anything in the part that keeps crashing, but I wasn't able to recompile it afterwards.
And I've tried everything else I can think of as a work around for those like me with LG's that can't even see the manual tuner in the input options, but to no avail ?
Correct, the manual function for the tuner is not available. I am writing to LG every week to get this done. know it is a lost of time ...
Your inquiry has been submitted for review and we are waiting for feedback so we can communicate it with you as soon as possible. We will also be including the observation you have suggested to improve future LG products. We assure you that these are being reviewed by LG management periodically and being utilized as valuable inputs for consideration in our products and services innovations.
Sorry, I can't help much than that
After a few calls with LG support, and asking for escalation, I learned that a converter box is the workaround. I have coaxial from cable provider. The converter box should have an hdmi output. Any suggestions on which product/model works well?
After accidentally rescanning for channels, I've bricked my TV for the broadcast channels. I've tried to use Teamviewer, Remodroid, but I can't find proper instructions to connect remotely to possibly fix the problem. The exploiteers website seems promising (www exploitee.rs) but not much information for my LG GA6450...
Anyone with update root instructions or ways to get Manual Tuner to work.? I've tried the manual tuner method but no channels are showing up.
I ran into this same issue and had several frustrating calls with LG support that went nowhere. I was lucky enough to stumble on some other suggestions and found a workaround. While not perfect, I can actually use the TV again. I hope this helps others in a similar situation. Follow the steps below and do not deviate (trust me I got really close to bricking my TV figuring this out):
From settings navigate to "Applications".
Scroll over to "All" and then down to find "Live TV" and open it.
Click on "Disable".
Exit back to settings and then to "Channels" (you'll see the options are now enabled).
Auto scan for channels (or if you've already done this manually tune to a channel).
Exit back to settings and back to "Applications".
Scroll over to "All" and then down to find "Live TV" and open it.
Click on "Enable".
Turn the TV off and then back on. (You'll notice you can change the channel, but after android has finished restarting it won't let you any longer).
To get around that, use the gesture button and click on the channel bar at the top to enable to guide below. You can now scroll up and down through channels, find the one you want and open to watch.
Note - If you press the "Home" button, you will no longer be able to get back to live TV. You will have to repeat the steps (on step 5, you can just manually tune). It's extremely frustrating that LG won't release an updated firmware to simply re-enable the tuner and I'm very disappointed with the way they have handled this situation (as well as how they interact with faithful customers).
Those who have been lucky to upgrade to Wear 2.0 have probably noticed the removed Do Not Disturb toggle synchronization between wearable and phone. Some like it, some not. I didn't like it, so I made an app that does the sync. Currently it only works one way: wearable -> phone. With some hacking, sync is working both ways.
You can find the application in Play Store.
Source, builds and setup instructions are available in github and licensed under Apache 2.0.
Installation instructions for Watch -> Phone sync:
Install phone application and wearable application from on-watch Play Store
Launch application on Phone
Click "Grant Permission" button
Enable Do Not Disturb access permission for application
Make sure all 3 checks in the application pass
Installation instructions for Phone -> Watch sync:
Setup watch ADB
Execute:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.NotificationService
Enable state broadcast in Watch Setup wizard
Currently synchronization phone -> watch is only possible by assigning permissions in ADB. Wear OS doesn't provide management settings. As this is not officially supported - it may not work for everyone or the next Wear version.
I love that something like this is now made, but I have a question. What is the first screenshot in the Google Play Store link for? I thought this was only for DND?
I'd like to install it and find out myself, but my ZenWatch 2 still hasn't received the update.
If your watch isn't updated, then the sync should work out of the box. As for the screenshot, I tried to show that the toggle in the watch will sync to the toggle in the phone. I'm not a designer.
Wonderful little utility. Thank you very much.
Fingers crossed to get phone > watch allowed.
I have a few apps that toggle DND via Tasker on my phone, and having it trigger the watch too would be sweet.
Good news and bad news.
The bad: notification access and all the management is unavailable in Wear. So there will not be an official way to make this work (source).
The good: you can grant the permission in ADB. I tried it and the app can actually switch DND on and off (source).
Having to run a single ADB command will probably not stop the brave people of XDA! So synchronization should eventually come to the watch, just give me some time to fix the current bugs.
Bonus news: AudioManager can be used in android <6 for sound modes. Haven't looked into that yet.
Thanks for this app, I miss the functionality!
Sync from phone to watch is implemented and functional! v1.5 is being pushed to the Play Store. You just need to enable broadcast from phone in setup wizard and execute this command in the watch:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.HackService
raimondas.rimkus said:
You can find the application in Play Store
Click to expand...
Click to collapse
Hello!
Not work on Huawei Mediapad X2 (android 5.1.1).
I know: "only Android 6+ is supported"... But, maybe, android 5.1 can be added to?..
Thank you!
If it can help, I can access Do Not Disturb on android 5 through Tasker.
But it is called "Interrupt Mode". It can be found here: http://tasker.dinglisch.net/userguide_summary.html search for "Interrupt Mode".
raimondas.rimkus said:
Those who have been lucky to upgrade to Wear 2.0 have probably noticed the removed Do Not Disturb toggle synchronization between wearable and phone. Some like it, some not. I didn't like it, so I made an app that does the sync. Currently it only works one way: wearable -> phone. With some hacking, sync is working both ways.
You can find the application in Play Store.
Source is available in github and licensed under Apache 2.0.
Installation instructions for Watch -> Phone sync:
Install phone application and wearable application from on-watch Play Store
Launch application on Phone
Click "Grant Permission" button
Enable Do Not Disturb access permission for application
Make sure all 3 checks in the application pass
Installation instructions for Phone -> Watch sync:
Setup watch ADB
Execute:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.HackService
Enable state broadcast in Watch Setup wizard
Currently synchronization phone -> watch is only possible by assigning permissions in ADB. Wear OS doesn't provide management settings. As this is not officially supported - it may not work for everyone or the next Wear version.
Click to expand...
Click to collapse
Thank you so much.
Sent from my ONEPLUS A3003 using Tapatalk
Works perfect!! Thanks!
raimondas.rimkus said:
... As for the screenshot, I tried to show that the toggle in the watch will sync to the toggle in the phone. I'm not a designer.
Click to expand...
Click to collapse
me neither, but maybe this could help?
I'm just curious. What's the difference between this version available in the Play Store (source code available here) and your own? It looks to me as though that blunden may have forked your code.
That's how open source works, you are free to fork it or take it as an inspiration. His code isn't a plain copy paste, it looks like he even has sync to older android versions, which I didn't have time to do.
I can no longer sync both ways after the newest update, v1.6. I can only control DND from both devices from my watch. Anyone else having this problem with v1.6?
Sent from my SM-G955U using Tapatalk
thecarp1975 said:
I can no longer sync both ways after the newest update, v1.6. I can only control DND from both devices from my watch. Anyone else having this problem with v1.6?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
The first idea is that app got suspended after the update. Make sure watch app is updated and start the app on phone. I've added a check that will tell you if watch DND permission is granted. If everything passes, then there is probably something weird with the AudioManager. Previous version used the new NotificationManager, but it requires a running service for broadcast events. I've switched to legacy AudioManager that can use a stateless broadcast receiver.
[Edit:] Android 4.3+ support is being pushed. This needed a code refactoring, so bugs are probable.
okk
raimondas.rimkus said:
The first idea is that app got suspended after the update. Make sure watch app is updated and start the app on phone. I've added a check that will tell you if watch DND permission is granted. If everything passes, then there is probably something weird with the AudioManager. Previous version used the new NotificationManager, but it requires a running service for broadcast events. I've switched to legacy AudioManager that can use a stateless broadcast receiver.
[Edit:] Android 4.3+ support is being pushed. This needed a code refactoring, so bugs are probable.
Click to expand...
Click to collapse
Yeah, all three permissions were granted. You wouldn't happen to have the APK for the previous version?
Sent from my SM-G955U using Tapatalk
V1.5 attached.
I would still prefer if you could make a logcat and I could fix the problem for the rest of the people. Just do these steps:
Connect phone to ADB
Enable DND, Disable DND on phone
Enable DND, Disable DND in watch
Run: adb logcat -d > bug_phone.txt
Repeat with watch connected to bug_watch.txt
PM the logs and I may try to fix it. It's not the first time android APIs don't work in specific phones.
Just a quick FYI. Version 1.6 works fine here. Nexus 6 / Pure Nexus 7.1.1 / Magisk root. Huawei watch AW 2.0 7.1.1 stock.
I can start DND from either watch or phone and the other device enables.
It works when I start Sleep as Android; SaS enables phone DND and that enables DND for AW 2.0, then Tasker via AutoWear triggers theater mode on my watch. One step goodness! :victory:
Hi guys,
I wanted to share my experience, how to disable vibrations on the Amazift. Sorry if some already posted it, but I couldnt find it.
First connect the device and open an console with adb.
Then open the shell on the watch:
Code:
adb shell
After that verify the name of the launcher package
Code:
pm list packages
There you should find a package called com.huami.launcher - this is the package we want to disable vibrations:
Code:
cmd appops set com.huami.launcher VIBRATE ignore
If you want to enable the vibrations again use:
Code:
cmd appops set com.huami.launcher VIBRATE allow
Since I want to have vibrations if I get a phone call, I installed the watch droid app on the watch, wich doesn't get changed at all.
Feel free to post questons, and I hope that I could give something back to this awesome community!
Thanks for this tutorial @Bainhorious !
That's exactly what I was looking for. Super simple but seems like none of the apps can offer the option to get notifications without vibration (I've tried the Mi app, Tools & Amazfit and also the Notify & Fitness).
Before I try your solution, I need, in addition to the vibration for incoming calls, I also need vibration for the Hangouts app. Do you think the "watch droid app" or even the Mi app would provide vibration for these 2 apps only? Thanks once again.
PS: my watch is the Amazfit Bip
Yes, as I have described above, you separately disable for every app the vibrations. So then just leave hangouts and watch droid out.
Thanks for replying.
Are you talking about the Bip? Because I don't think it is possible to install watch droid app on the Amazfit Bip.
Newbie question: do I need to unlock the bootloader or something like that? Or I can just connect the watch to my computer via USB and write the codes via ADB?
Man, this process work on Amazfit Bip? My Bip stop to Vibrate without, and I don't make it back =/
Unfortunately I don't think it works for the Bip, at least no one has tried
Bainhorious said:
Hi guys,
I wanted to share my experience, how to disable vibrations on the Amazift. Sorry if some already posted it, but I couldnt find it.
First connect the device and open an console with adb.
Then open the shell on the watch:
Code:
adb shell
After that verify the name of the launcher package
Code:
pm list packages
There you should find a package called com.huami.launcher - this is the package we want to disable vibrations:
Code:
cmd appops set com.huami.launcher VIBRATE ignore
If you want to enable the vibrations again use:
Code:
cmd appops set com.huami.launcher VIBRATE allow
Since I want to have vibrations if I get a phone call, I installed the watch droid app on the watch, wich doesn't get changed at all.
Feel free to post questons, and I hope that I could give something back to this awesome community!
Click to expand...
Click to collapse
Thanks for this! btw. "cmd" didn't work for me, but "command" worked
I think it should be
Code:
appops set com.huami.watch.launcher VIBRATE ignore
in the current version
Bainhorious said:
I think it should be
Code:
appops set com.huami.watch.launcher VIBRATE ignore
in the current version
Click to expand...
Click to collapse
Yep, this also :good:
I'm assuming ADB refers to Android Debug Bridge?
For someone who isn't that savvy with the above, would you recommend doing this? This is a feature that I miss coming from a pebble time and I want to do this but the instructions above will probably mean that I get lost in the process. Is the above process to be done with the amazfit app or while the watch is connected to a pc?
Sorry about the basic questions.
I suppose there is no app that can disable vibration, right? At least, not amazfit tools, which I tried...
Does this still work on Android Pie? Certain apps still vibrate annoyingly so despite the granular notification control that Pie has introduced.
**Let me start off by saying that I have not had a chance to verify but I do not have the error that NFC is not enabled anymore.**
Requirements -
1. Android Pay (Google Pay will not work on my watch although I read a post by someone who says it works on theirs)
2. Tasker installed on phone
3. Autowear Plugin to Tasker installed on phone and watch
4. A PC with adb installed
Step 1: Enable Developer Options on Watch
Step 2: Turn on ADB Debugging and Debug over WiFi
Step 3: Open command prompt or powershell in the folder where you have adb (hold shift and right click)
Step 4: In powershell, type adb connect 198.162.X.X:5555 (use the actual IP of your watch). Press Enter. The watch will prompt you to accept the connection. Select Always Allow.
Step 5: Type adb shell pm grant com.joaomgcd.autowear android.permission.WRITE_SECURE_SETTINGS. Press Enter. It may take a minute or two but if you don't receive an error, it worked.
Step 6: Open Tasker on your phone. Select Tasks. Hit the + sign in the bottom right. Select Plugin -> Autowear -> Secure Settings. When the new window opens, click the pencil next to Configuration. Set Command to Execute to &CONNECTED&. Click Custom Setting. Setting Type is Global, Name is <NFC>, Input type is Toggle, and Value is 1. Once all those are set, click the back arrow to get back to the AutoWear Secure Settings page. Click the checkmark at the top to save the settings.
Step 7: In powershell on the pc, type adb install com.google.android_apkmirror.com.apk. Press Enter. It should say Success once it finishes.
Step 8: On your phone, under the Task Edit screen (where you should be if you did not exit out from step 6) click the "Play" button on the bottom left. You should get a green dot next to the word configuration at the top.
Step 9: Open Android Pay on the watch. It will take you through the setup and tell you to finish on your phone. Once you finish adding a card, it should show up on the watch. "To pay with your watch, you need to turn on NFC" will show up and blink a couple of times then go away. It should show your card with "Hold to terminal.." above it.
This is something I threw together real quick to get the word out. Like I said in the beginning, I have not tried it at a terminal yet. As soon as I do, I will repost with results. Also in the near future, I will streamline the process, add a command to Tasker to keep NFC on always, and hopefully pay without opening the Android Pay app on the watch (Simply have the watch unlocked). I have attached the Android Pay apk below. If anyone tries this and uses the watch at a terminal, please post results.
I had a feeling a developer would find a way. I wonder why google pay isn't working for you and why Android pay says it needs NFC when it is already enabled. Have you tested to see if it does indeed enable it?
developer209 said:
I had a feeling a developer would find a way. I wonder why google pay isn't working for you and why Android pay says it needs NFC when it is already enabled. Have you tested to see if it does indeed enable it?
Click to expand...
Click to collapse
I am in no way a developer. Just trying some stuff out. I tried to Pay with the watch and it did not work. Hopefully someone with some knowledge and experience will see something here and guide us in the right direction to get this working.
That could mean one of two things, either the watch's NFC is not actually on or Android pay is not transmitting the signal.
This does not actually enable NFC. I tried paying with Google Pay and it did not detect anything. I don't think NFC can be enabled without root and adding some files that are missing.
Sent from my Nexus 6P using XDA Labs
Verizon promised to add pay and turn NFC on I say we hold them to it as owners of their watch discontinued or not this is as advertised.
https://www.verizonwireless.com/support/knowledge-base-209381/
Is it possible that kernel doesn't include NFC drivers? Kernel sources here contain the NFC drivers, but are they on the device?
Hi,
Added a tag to Title to avoid confusion.
I really appreciate the kind of topics you post here. Thanks for sharing information that is actually helpful. Good day!
Not working for me so far. I'm going to try it again at a McDonalds kiosk, but I found something of relevance...
It appears no NFC service is registered on my Wear24, so if there's no service to call... there should be no way to enable NFC. Note that I'm on AW 2.15
Log proving no service exists: https://textuploader.com/dvc7s
The only way to fix this is with a whole new ROM update, be it by the community or Verizon.
Anything going on?
Now that we have got the new wearOS 2.0 and nothing from Verizon coukd we pretty much say that the odds of getting Google Pay working on this watch are almost none?