So I tried out the new Lollipop builds floating around the VZW Dev forum (I tried every single build) and I'm having issues connecting to my G Watch. I have, since, reverted back to 4.4.4 LiquidSmooth to get it working again. It seems that 5.0 can see the watch via Bluetooth and the watch can see the phone, but the Wear app will not connect the two together. I haven't seen anything about this so far, but it's not likely that many people installing these ROMs are looking for compatibility with their smartwatch. I wanted to put it out there that, at least for my VS985 G3 and my LG G Watch, 5.0 won't connect the two. If anyone has had any luck with making a connection on a 5.0 ROM, please do reply and tell me exactly what you're using and what you did, because I have been eager to get 5.0 since Material Design and ART runtime was announced.
I know we have (or had) an issue with bluetooth calling devices, but since the watch works 100% on LS KK, I'm not sure what the issue could be here.
I've gotta factory reset my 360 any time I jump to another ROM. Can't speak for the G watch but the Moto 360 works fine on 5.0 so I'd assume you can. If that's the only thing keeping you off of 5.0 it'd be worth giving a reset a shot.
Need to reset you watch
I agree with dustinb17. Any time you move the watch to a new device or new rom, you have to reset the watch. It kind of makes sense in a way. its storing body vitals and such and it doesn't know that the phone is changing and not the person.
Related
Both the G3 and the G3 Vigor with Sprint stay paired to my Jeep's entry level 130 bluetooth U Connect system. However, the phone drops the connection and audio won't play at all or it will not route phone calls over the car's system. I tried basic trouble shooting, including wiping my U Connect's set up and also hard resetting the phone. But it is totally an LG issue. The HTC M8, Galaxy S5, Moto X, and iPhone 5 are all confirmed to pair normally and hold connection with no audio issues.
A basic Google search tells me I'm not nuts and others are having the same issue. Some blame the Optimus UI and others blame an old bluetooth stack LG uses. I work for a wireless retailer and I am trying to get as much information as I can to my LG field marketing specialist.
So any feedback or suggestions about this would help.
Nothing? Well, I guess I'll have to wait for the Lollipop update and cross my fingers.
mreniigma said:
Nothing? Well, I guess I'll have to wait for the Lollipop update and cross my fingers.
Click to expand...
Click to collapse
Are you rooted and bumped? Have you tried a different ROM? Any luck? Sorry to hear of your troubles. Perhaps contact one of the ROM devs in a Q&A thread or via PM and see if a fix or workaround is possible.
Sent from my Stump'd & Bump'd Sprint LG G3
Maybe someone can help, but Beelink use to work great until the latest update to Wear devices was released.
If anyone is like me, they would like to have there watch be able to switch between phones without having to do a factory reset on the device every time (I use an old phone for working out and not my everyday phone).
Can someone help and make an app, similar to beelink (which is unavailable now), that can bring this functionality?
That would be super handy with so many roms to try it socks having to pair the watch over and over.
I agree. Another reason why this would be awesome! Can anyone help???
Ya I'm seriously interested as well. Been changing roms so much this past week.
This is a way
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Two things I'd like to get peoples thought on:
1. Vimofit is an excellent weight lifting tracking app for androidwear. Once taught your favorite lifts, it will recognize what lift you're doing just by your arm movements and count your reps... unique idea and works VERY well... for MOST android watches. Its currently in public beta and I've shot a few emails back and forth with the devs and he said "Google stopped reporting data for one of the sensors we use on Moto360 since 5.1.1". That was for gen 1 moto 360, so i asked if things were going to be different with gen 2 and he said that motorola was reporting it was not working and (this was my favorite part) i should get a different watch because there are lots of other options. Ha unfortunately my friend one buys apps for the device not a 300$ device for an app. I can't believe there isn't anything they can do about it.
2. There doesn't seem to be any definitive release date for this device. The only thing I heard was wind of sept 15 (which has come and gone). However a ray of hope was that on best buys site if you try and pickup it up in store, it shows availability on sept 15. I think that's pretty neat.
For the record, I got a 360S yesterday and VimoFit is working just fine with it. Only did a small set yesterday but it recognized crunches and back extensions just fine. I dare say better than it did on the Gen1.
Also of note, and quite amusingly, on the way to the gym Vimo was updated noting that they got around the 360 issue. So it's very possible the same fix works on the new 360 models just as well as the gen1.
[Solved] VimoFit Working on 360 2 (2015)
[solved] 360 2, 46mm standard, not sport, received on Friday, can not get Vimofit to work so far. Sent a data log Vimo and they report that there is no data from the sensors. They are going to try to obtain a 360 2 this week to fix the issue. Major kudos to VimoFit for there quick response time and willingness to do whats needed to get this sorted out.
Kept playing with it, and this is how I got it to work.
I turned on debugging through MotoConnect, nothing came up though, I downloaded SensorBox for Wear and for some reason it was the first app that wouldn't push to my phone, so i connected the Moto to my Wi-Fi, (first time) and that was the bridge needed to get the app to push. Opened SensorBox, and all the sensor showed positive information on the different planes an graphs. Opened VimoFit back up and was now able to detect exercises.
Things to test seperately since I can't go back, and can't turn wi-fi,
-Debugging, Turned mine off and it still works,
-Wi-Fi
-SensorBox
-Dumb Luck
For what it's worth, I know there's a bug of some sort in the new gen of Moto devices where the sensors stop sending data to applications. System functions like tilt-wake and wrist gestures seem to still work fine, but most applications stop getting data from them. If you use WatchMaker, load up a face with gyro effects. If the bug is hitting, the gyro effects won't work. I've noticed it hits some but not all applications, but WatchMaker and Vimo seem to both be affected when it does hit. If Vimo isn't registering anything, give your watch a reboot and it should be fine. Or just reboot when you walk out of the locker room and you should be good to go either way.
I went through like 4 42mm Gen2 360s and they all had this issue. I got a 46mm yesterday and I haven't seen the issue pop up yet. I just checked a little bit ago, and this happened now on my 46mm as well. When speaking to the dev, he said he saw this come up on Huawei too. So it seems to be fairly pervasive. Both 42mm and 46mm see to track movements like a super champ as long as they're getting the sensor data. The dev on Vimo is one of the best I've worked with. He's pleasant and open to talk to, and he's very responsive.
I am experiencing this issue as well. Will there be a permanent solution to this? Rebooting it at least once a day is getting annoying. Or should I return the watch?
Hi guys if your reading this maybe you can help me. I have an appradio3 that I to be able to cast my screen onto. Now brief background, I used to be on Verizon limited data with a rooted note2 that I direct connected via HDMI. I now have mistakingly switched to att and now i have a new note7 that doesn't have anyway to connect directly to the deck since Samsung has taken it out. Now I've since read about using a Chromecast and casting that way. That's all well and good if and only if you have a Wi-Fi hotspot on your phone which I don't and i dont want to pay for the very limited hotspot plan for my phone to do that. Now I'm not opposed to rooting my note7 which I've looked into that but I've got an sm-n930a. And using the Sprint method doesn't work well for my model. Seen a video were a guy did get his tmoblie phone to root but the process was very lengthy. Or I'm not opposed to rooting if possible the Chromecast. I've got both the newer and the older version of that. I've looking briefly through the Chromecast threads and didn't see if once rooted that you could Wi-Fi direct to the CC. Like once your setting it up it Wi-Fi directs to your phone then switches to normal Wi-Fi. Is this possible??? Or if there's any other device that could get this to work with an appradio3 I'll totally try that.
Mojo7139 said:
Hi guys if your reading this maybe you can help me. I have an appradio3 that I to be able to cast my screen onto. Now brief background, I used to be on Verizon limited data with a rooted note2 that I direct connected via HDMI. I now have mistakingly switched to att and now i have a new note7 that doesn't have anyway to connect directly to the deck since Samsung has taken it out. Now I've since read about using a Chromecast and casting that way. That's all well and good if and only if you have a Wi-Fi hotspot on your phone which I don't and i dont want to pay for the very limited hotspot plan for my phone to do that. Now I'm not opposed to rooting my note7 which I've looked into that but I've got an sm-n930a. And using the Sprint method doesn't work well for my model. Seen a video were a guy did get his tmoblie phone to root but the process was very lengthy. Or I'm not opposed to rooting if possible the Chromecast. I've got both the newer and the older version of that. I've looking briefly through the Chromecast threads and didn't see if once rooted that you could Wi-Fi direct to the CC. Like once your setting it up it Wi-Fi directs to your phone then switches to normal Wi-Fi. Is this possible??? Or if there's any other device that could get this to work with an appradio3 I'll totally try that.
Click to expand...
Click to collapse
I'm guessing after the note 7 recall this issue has "solved" its self... I am curious what you did wind up doing. I have the same App radio 3. I used to mirror my S5 to the thing with a samsung hdmi adapter and had full bluetooth touch controlls. Ever since android started setting selinuix to enforced it has become an issue to emulate touch control from the app radio to the phone. Screen mirriroing alone didnt really make me all that happy since I couldnt make it do much without touching the phone. Do you by chance have any advise on this?
What phone did you go to after the Note 7?
Well unfortunately I've gone to an iPhone 7 plus. Which I'm a droid person at heart and it's been a hard switch. Mainly cause I like the ability to mod the droid over iPhone. That said though the iPhone can still hook up to the AppRadio once you've got the appropriate adapters. So right now I can mirror the phone and can watch YouTube videos on the deck. If watching a YouTube it'll allow the phone to go dark or browse for your next video. Still looking into loading videos on the iPhone than watching them on deck but haven't put to much effort into as of yet. The real bummer is that there isn't no support to mod the iPhone to use full touch screen like if you had a droid with the hdmi. I've actually posted on several iPhone forums with just the question and after 2 months have not gotten a response. I still have my note2 and could hook that stuff back up but I have no internet on it so I couldn't watch YouTube from it. And I know this is droid forum but if anybody can help with modding the AppRadio app for iPhone like they did for the droid I'd throw some funds your way, but I can't throw to much since winter time is slow work months for me.
So I bought 26 LG G4 h810 to organise VR Field Trips using Google Expeditions.
At first I managed to connect only 4 of them. I thought it's perhaps a router. This app relies on WiFi P2P btw. So I changed TP-LINK router worth like 60$ to Asus RT-AC 5300 which is quite high-end. Not much changed as yesterday I had trouble connecting even 2 devices together.
This morning I realised that G4s with Android 6.0 //I received 5 of such// are actually stable and work like a charm together. So I thought I finally have a solution - I'll upgrade the rest - flash with kdz through LG UP and I'm good to go. Well I'm not. The 3 upgraded phones act just the same as they did on 5.1.
It's a funny thing really, to see - 7 phones connected - 2 of them on v5.1,
I connect to this wi fi (5ghz btw) another 5.1 device one after the other, and some of the phones disconnect just one of the other 5.1 device in the network, some of them kick out all the 7 phones. As soon as I turn the wifi off on the newly connected 5.1 phone, all the rest connects back on together.
By kick I mean Expeditions app is reconnecting. Sometimes it goes as far as disconnecting wifi completely, but usually it's more like internet becomes unavailable. And that's btw a funny thing, cause Expeditions doesn't rely on internet connection - the router theoretically can be offline - however when the phones get to fight over wifi (when there are 3 android 5.1 LG G4 trying to connect), notification comes up "internet is unavailable" and with that Expeditions connections are lost aswell.
I spend whole days on it since like a week and am slowly getting frustrated so decided to write to ya not only read.
Yesterday I rooted 3 of the 5.1 phones to get rid of AT&T bloatware and unlock hotspots - it didn't change anything.
I think it's some sort of direction, the fact that 6.0 devices work as expected and 5.1 ones not, but the problem is so specific, that I can't really find relevant information online.
I also compared the working and not working phones today with antutu and antutu officer and it seems they are legit. Had doubt as I bought them refurbished from Aliexpress.
The wifi works perfectly on each of them seperately as I updated apps on them and experienced no issues... As long as I updated max 2 devices at the time.
Am thinking of interference of some sort, or like device id conflict or something... Will probably also try to rename the devices maybe something like confuses the router, I don't know. Please help.