yashsingh1/xdaforums huggingface dataset:
[LG Watch Urbane] mh7:
Finally Updating
[LG Watch Urbane] sudaltsov:
What firmware do you have on m8?
[LG Watch Urbane] diegodbm:
Hi,

How, in the name of LG, do I do a factory reset!!!

Enviado desde mi Nexus 6P mediante Tapatalk
[LG Watch Urbane] cuongphatbc:
i use stock 6.0.1 for m8 sprint. i try up fw ruu for sprint m8.
[LG Watch Urbane] sudaltsov:
Please keep us posted!
[LG Watch Urbane] kaiser_tytnii:
Same problem, what's your phone? Mine is a nexus 4

I went as far as factory resetting both and no luck
[LG Watch Urbane] sudaltsov:
HTC M8. The firmware is Google Play Edition (nearly vanilla 6.0)

So this issue is not even HTC-specific. I hope LG will come up with some comments on that...
[LG Watch Urbane] kaiser_tytnii:
Wonder if it's a unique combination of problem with 6.0+ phone and 6.0.1 urbane and 1.4 Android wear app

Or it could just be Android wear app acting up

Anyone else using 6.0+ phones here?
[LG Watch Urbane] 2x4:
I am, nexus 5x 6.0.1 and lg urbane 6.0.1 and android wear 1.4, no issues here
[LG Watch Urbane] infra_red_dude:
I have the same issue. Nexus 4 ,6.0.1 custom ROM. Watch won't pair. In fact watch will repeatedly try to pair after factory reset and generate multiple pairing keys but pairing never succeeds.
[LG Watch Urbane] sudaltsov:
I tried to do the factory reset from RECOVERY mode on the watch - no result.
[LG Watch Urbane] kaiser_tytnii:
Exact same as me, we should raise this to LG or Google?
[LG Watch Urbane] sudaltsov:
Already sent to LG, with link to this thread
[LG Watch Urbane] DanielMalmgren:
I'd like to add myself to the list of people having trouble after the upgrade. I got it on my Urbane yesterday. Before the upgrade everything worked perfect, now the bluetooth is

very

unstable. I mean, 95% of the time I've got the little strikethrough cloud on my watch. I've got no reboots though.

I have a Xperia Z5 Compact, running Android 5.1.1.

I guess there is no way of downgrading? I was very happy with my watch until yesterday...

/Daniel
[LG Watch Urbane] jedi.6:
I have the same problem with my lg urban and watch my HTC One M8.

I was updated on the android watch, she logged out regularly, I did a factory reset and since longer possible to connect Bluetooth.
[LG Watch Urbane] geofflyons:
HTC M8 with Android Wear 6.0.1 on the LG Urbane. I was seeing more disconnects than ever since the update so I reset the watch. Now it refuses to connect! The pairing key looks OK but it's rejected immediately.

Not happy! I was able to pair the watch though to an older M7 without Android Wear installed. Very odd and even more frustrating! :(
[LG Watch Urbane] 2x4:
It won't Re pair after factory reset unless you also forget the device on android wear
[LG Watch Urbane] infra_red_dude:
Even that doesn't work. Nothing will pair the two now.
[LG Watch Urbane] kaiser_tytnii:
Second that
[LG Watch Urbane] geofflyons:
Always unpaired and/or forgotten but problem persists. It's a bug for sure!
[LG Watch Urbane] wease:
I took the update, seems like the trick is not to reset the watch. I am paired and did not reset the watch
[LG Watch Urbane] infra_red_dude:
Just for the record: A factory reset from recovery and adb sideload of the ota firmware update does not work either.
[LG Watch Urbane] DanielMalmgren:
May I suggest that everyone here file their own support ticket to LG describing the problem? It's important that LG realizes that this is not one or two users having problems but that this upgrade is seriously broken and makes the smartwatches not smart anymore!

I've fiddled around a bit. If I go into settings on my watch and click bluetooth and then devices, I get the question "turn on bluetooth, are you sure?" (just like bluetooth in reality were turned OFF in beforehand). After I confirm that, everything works fine between phone and watch for a while. It's like bluetooth is simply turned off after a while. Is this the same for the others of you?

Also another question: Do any of you use wifi on your watches? Does that work? I've never had it enabled, never saw the point. Just wandering if that might affect the problem...

/Daniel

edit: Weird. Bluetooth is still working fine, after more than three hours. When I tried yesterday I only got minutes. I wonder what's the difference...
[LG Watch Urbane] sudaltsov:
Actually bluetooth is on after the factory reset - because the PIN codes are the same. But that is not good enough for pairing, for some reason...
[LG Watch Urbane] Speedball030:
I also got problems with my watch after the system update, and couldn't pair it successfully with my phone (N4 PureNexus 6.0.1).

Contacted LG support in Sweden, and they asked if I had tried with another phone. Not thinking it would work, I tried to pair it with my Galaxy Tab2 (CM13 MM6.0.1) and that did work!

Retried (once more) to pair it with my phone, but unfortunately that didn't work.
[LG Watch Urbane] luizm.jr:
This worked for me until I rebooted the phone. Then the phone couldn't connect to the watch and a message asking to perform a factory reset appeared on watch screen.

Now if I try to pair the phone to watch I got an error message regarding the passkey.

Lg G Watch R with android 6.0.1

HTC One M8 with android 6.0 (ViperOneM8 5.0.1)
[LG Watch Urbane] infra_red_dude:
Some update: I could successfully pair my watch with an iPad. So pairing does work in the watch, just not with certain devices+ROM combos. I'm wondering if this has to do something with custom ROMs. Someone said it works with Nexus 5X stock and most of us facing issues might be on custom ROMs. Is this true?
[LG Watch Urbane] rbox:
I got my watch on Saturday. Synced it to my phone on the old os. Did the update. Wound up syncing and resetting a few times. Been running solid since no problems. I'm using a nexus 6 with cm13.
[LG Watch Urbane] geofflyons:
*** Issue seen on the following ***

Phone: HTC M8

ROM: Android Revolution HD 53.1 & Android Revolution HD 50.1

Status: Pairing always fails even though pair keys are the same. It's like Bluetooth fails for a second after. Apps removed, reinstalled. Caches/Data cleared on Google Services, Google App and Android Wear.

Watch reset and Phone reset & firmware upgrade made no difference.

Work done: Called LG Ireland, waiting a call back.
[LG Watch Urbane] infra_red_dude:
Thanks for the update! So it's not custom vs. official ROMs. Another theory: for those who have the watch working, are you folks rooted? My Nexus 4 is rooted and watch won't pair with me. Just wondering...
[LG Watch Urbane] rbox:
Both my phone and watch have root.
[LG Watch Urbane] Dazeon:
My Nexus 4 and Urbane are both unrooted and running the latest official stock images (5.1.1 and 6.0.1 respectively). They were paired prior to updating the Urbane to Marshmallow and are still working fine with one another after the update. I did not perform a factory reset following the update, nor have I created a new pairing.
[LG Watch Urbane] kaiser_tytnii:
most likely people who paired prior to 1.4 OS update would be fine... in this case, i dare not to ask anyone to unpair and pair again just to test...
[LG Watch Urbane] Speedball030:
Both my N4 and Samsung Tab2 have root.

Watch doesn't work with N4, but does work with Tab2.
[LG Watch Urbane] kaiser_tytnii:
is tab2 on 6.0.1?
[LG Watch Urbane] Speedball030:
Yup. They both are.

N4 on PureNexus, and Tab2 on CM13.
[LG Watch Urbane] rbox:
At one point I screwed up and wound up unpairing and that caused my watch to factory reset and i was able to pair again just fine.
[LG Watch Urbane] DanielMalmgren:
Ok, here's my experiences after a few days: The problem with the watch and the phone not connecting is not related to what I do with them, it's where I am. Does that sound strange? Well... When I'm at work everything is fine for eight hours straight. I get on the bus home and it disconnects. When I'm at home everything works perfect until I get on the bus to work and it disconnects. When I try to connect it again while being on the bus it just disconnects again within a minute.

My conclusion: After the upgrade to 1.4 the watch has become very much more prone to be disturbed by other bluetooth devices, and there are more chance of other people on that bus to have active bluetooth devices. I know there are others at work with active bt devices too, so there must be something more. I'll continue investigating. Anyone else who could confirm any of my strange sightings?

Just to be clear: What I mean with "disconnects" here is that it seems like the watch shuts down it's bt completely. The only way to connect is to go to settings->bluetooth->devices and when I do that the watch asks if I want to turn bt on.

/Daniel
[LG Watch Urbane] SynisterWolf:
after taking the OTA i had connection issues with my N6. i factory reset the watch and its working fine.
[LG Watch Urbane] infra_red_dude:
Latest update: I downgraded from FakeROM 6.0.1 on my Nexus 4 to stock 5..1.1 (rooted). Everything is working fine now. Unfortunately it seems it's the ROM (or the kernel?) that's messing up something. Guess it's no marshmallow for me on my phone, only on my watch!
[LG Watch Urbane] sudaltsov:
Does anyone having issues with 6.0 on HTC M8 have stock 6.0 on the phone? Not Google Play Edition, not any other custom ROM - just plain 6.0 from HTC (with Sense and all that)?
[LG Watch Urbane] dazultra2000:
xxx`
[LG Watch Urbane] splinter82:
Been having constant problems since the wear 1.4 update with my Htc One M8. First I was getting random disconnects, restarting the watch sorted those, but it was getting more frequent, so I decided to try unpairing and reconnecting the watch the the phone.

Bad idea.

Now I get error messages every time I try to pair - my phone says the Pin / pass code is incorrect, even though both screens are clearly showing the same number. I've factory reset the watch, wiped the phone, tried a couple of GPE and Sense ROMS on the phone, but I can't seem to get the two to pair.

The watch pairs perfectly with my partners Galaxy S6 and Galaxy Tab, so I know the watch is ok. Seems something in the phone isn't happy.

I'm going to go back to stock ROM today and try it with that.
[LG Watch Urbane] kaiser_tytnii:
Bluetooth has been wonky since I have marshmallow on my Nexus 4, wonder if it's the driver problem or kernel problem... Anyone here has 2013 nexus 7 to test it with? I wonder if we could get the 5.1.1 nexus 4 Bluetooth driver for marshmallow ROM than the Nexus 7 driver...

There is possible some differences in Bluetooth between nexus 4 and 2013 nexus 7 which makes Bluetooth wonky, my pure guess

Edit: stumbled upon this app... Not sure if it can help since it hasn't been updated since 2011... Don't have my watch with me to test as well...

https://play.google.com/store/apps/details?id=com.phk.bluetoothfixrepair
[LG Watch Urbane] infra_red_dude:
Thanks for this information! Because of the itch in me I gave it another shot, this time I went CM13 for Nexus 4. Watch works and pairs fine, rooted or otherwise on phone! There is something in the watch that doesn't like certain flavors of ROMs on my Nexus 4.

The sad part is that CM13 doesn't support enabling LTE on Nexus4 and also has lots of issues with Viper4Android. So I guess, it's back to Stock 5.1.1 for me. No marshmallow for my phone :(
[LG Watch Urbane] diegodbm:
Now, with the update, it is an useless piece of technology.

Can't send WhatsApp, Hangout, etc.

Enviado desde mi Nexus 6P mediante Tapatalk
[LG Watch Urbane] kaiser_tytnii:
Might as well doing this, not gaining much with mm anyway.... Doze helps but screen on battery life sucks on Nexus 4 on mm so net net nothing is gained...

Tap on now is just... Sigh...
[LG Watch Urbane] Speedball030:
I just flashed the latest nightly (2016-02-24) CM13 on my Nexus 4, exchanging the PureNexus ROM, and the watch is now working.
[LG Watch Urbane] kaiser_tytnii:
Got to be the Bluetooth driver....

EDIT: Confirmed working with CM13 and i am still a strong believer that it is the Flo driver that caused the problem with all the other AOSP ROMs... I have tested Chroma, Pure Nexus, Pure AOSP, etc... all same problem
[LG Watch Urbane] sudaltsov:
Switched M8 from GPE ROM to Stock Sense ROM. No difference. No pairing.
[LG Watch Urbane] kaiser_tytnii:
did you allow permission? There are permissions for doing those.

permission --> google services framework -->

enable ALL

---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------

did you do it by ruu or .zip via custom recovery? Sorry i can't help much since i do not own a M8.
[LG Watch Urbane] sudaltsov:
I took the backup from http://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 and used twrp to restore it.
[LG Watch Urbane] kaiser_tytnii:
Did you try these ruu? http://xdaforums.com/showthread.php?t=2729173
[LG Watch Urbane] sudaltsov:
No I did not. Why would I try Spring ROMs if I have European M8? And the stock ROM works ok... Except for the LG Urbane pairing:)
[LG Watch Urbane] kaiser_tytnii:
Sorry, thought u were using sprint, i guess i got confused with someone else. I suggest you trying ruu instead of those
[LG Watch Urbane] sudaltsov:
I do not think it matters how you install a ROM, as long as it is the same ROM.

Next answer from LG is even more funny. They advise waiting till Android Wear update on the phone. I replied that Bluetooth pairing happens before Android Wear actually kicks in, that is lower level.
[LG Watch Urbane] Speed-Star:
Hi.

Thanks for your Log sudaltsov. Having a HTC M8 & LG G Watch R and suffering the same paring problem.

I have to say, that I'm not an expert at reading debug log. But this should be the initial call with the paring request and the paring key 131440

01-01 00:09:12.923 1103 1140 I BluetoothBondStateMachine: sspRequestCallback: [B@98b81ed name: [B@c4ab822 cod: 5898764 pairingVariant 0 passkey: 131440

I belive the cod is then changed to a hexadecimal (decimal: 5898764 --> hex: 005a020c) value and compared. This should be the position, where things fail:

01-01 00:09:20.468 1103 1150 E bt_btif : bta_gattc_mark_bg_conn unable to find the bg connection mask for: 00:ee:bd:55:be:37
01-01 00:09:20.470 1103 1140 I bt_btif_dm: check_cod remote_cod = 0x005a020c cod = 0x00000580

Remote device (your Phone) reports a different paring code than the watch expects. Paring fails.

Please correct me if I'm wrong.

[MENTION=4315497]sudaltsov[/MENTION]:

Can you maybe provide a log were the paaring actually works? (With a different phone maybe?)

Then we could compare these logs.

Greetings

SpeedStar
[LG Watch Urbane] sudaltsov:
if I manage to find the working phone, I will do. But there are people in the thread who are more successful - may be they can share their logs?

About the pin codes - visually they match on the phone and the watch.
[LG Watch Urbane] carbunch:
I haven't been able to consistently run certain apps since the update. The screen just randomly turns off. There's also the removal of notification options and factory reset.
[LG Watch Urbane] diegodbm:
Thanks... It's a guy love now... ????

Enviado desde mi Nexus 6P mediante Tapatalk
[LG Watch Urbane] natefish:
Since I got the 1.4 update, my battery life is incredible. Used to barely get through a day (non-root) but I went to bed with 75% after heavy use. I'm guessing the doze feature is the hero. No issues with the pairing or other functions either. I even found a unicorn in my yard.
[LG Watch Urbane] ChrisCross82:
There is also a thread at Google, showing that also people with stock roms have the same issue:

https://productforums.google.com/forum/#!topic/android-wear/--At7VrHkOk;context-place=topicsearchin/android-wear/authorid$3AAPn2wQfoU-IfUdTS6zoSHxDo0zldY35ehOKnIlPuzqVuveh-RKKHsVFcxdriwlzmPdJuOnHMW5LH|sort:date|spell:false

I had a HTC M8 with Revolution HD 51 and paring after factory reset of the watch was not possible. Same with 53.1. Downgraded to Revolution HD 45 (Android 5) and now it work again.

The watch pairs with anything else (windows, android 5 etc.) but not with Android 6 anymore. Seems somehow Google messed it up in Android 6 and Wear 1.4.x . Quite strange, because i was able to initially pair on 27.01.2016 (here I upgrade to Anroid 6), but even with a fresh android 6 the watch will not pair. Very interesting how Google made this.
[LG Watch Urbane] sudaltsov:
I tried another phone with Android 5 (Samsung), the watch pairs OK. So it seems the killing combination is Android 6 and Android 6. Anyone got any updates from LG/Google?
[LG Watch Urbane] wease:
I am using my updated Urbane with my new Galaxy S7 Edge with no problems. . 6/6
[LG Watch Urbane] sudaltsov:
Specific to HTC m8 and Nexus phones?
[LG Watch Urbane] DanielMalmgren:
I've got the problem with my Xperia Z5 Compact. Running 5.1.1. So it's not specific to Android 6 and not to any specific phones.

/Daniel
[LG Watch Urbane] jedi.6:
I begin to despair ... not a google word on this issue despite there being more and more people who complain
[LG Watch Urbane] DanielMalmgren:
Yep, it's really ridiculous. I just want my phone working again the way it did before LG broke it, how hard can it be?

I got another answer from LG support today. I just can't seem to get past the first line idiots who don't read a word of what I'm saying but only tells me again and again that I should try fabric resetting my watch. Giving up on that road...

/Daniel
[LG Watch Urbane] sudaltsov:
Can anyone having problems try https://productforums.google.com/d/msg/android-wear/--At7VrHkOk/2drxvoqYDAAJ and report their experience?
[LG Watch Urbane] _RPHD:
I updated mine yesterday, and its been working fine! No dropping bluetooth issues or anything.

Stock S6 edge (Android 6) & Stock urbane
[LG Watch Urbane] DanielMalmgren:
This is weird. I upgraded my phone (Xperia Z5 Compact) to Marshmallow yesterday and it seems it solved my Urbane's bluetooth problems. Not a single disconnect for almost 24 hours. So while others seem to have problems only when their phones are 6.0 I have problems only on 5.1.1...

/Daniel
[LG Watch Urbane] jedi.6:
Looks like everyone does not have the same problems. I have no problem when I connect my watch to a phone in 5.1.1 but not in 6.0.

I have not tried in 6.01 because no rom available
[LG Watch Urbane] extremx:
I spent hours trying to get my HTC M8 with GPE 6.0 MRA58K.H11 to pair. It WAS paired... but it became unpaired and will no longer pair to my lg urbane. I thought for sure it was something on my phone as my wifes M8 would connect (stock m8 with the new marshmallow update) as well as my daughters S4 (5.1.1 i believe). "Incorrect passcode or PIN" every time.

Tried this -> root@htc_m8:/ # rm /data/misc/bluedroid/bt_config.conf I am curious, if someone out there with root on the watch could delete this file on the WATCH and try it...

Tried the another suggestion where you pair the watch to another phone, then try and pair it to the phone having issues, then wiping and trying again. No dice. I can't ever even see my phone from the bluetooth add option on the watch.

Wiped the phone with new version of GPE, no dice.

Posted here: https://productforums.google.com/fo.../--At7VrHkOk;context-place=forum/android-wear

I can provide logs and whatnot if it helps.
[LG Watch Urbane] JimSmith94:
I got the 1.5 update through the Play Store today.
[LG Watch Urbane] extremx:
I have the 1.5 update (1.50.2690526.gms) no change in connectivity. Still fails.
[LG Watch Urbane] sudaltsov:
The problem is obviously on lower level, Bluetooth. So no update of Android Wear can fix that, I am 99% sure.
[LG Watch Urbane] jedi.6:
I was happy to read a version 1.5 arrived but if it does not change : :(

What is the changelog for 1.5
[LG Watch Urbane] DanielMalmgren:
Just to clear out the confusion: Some people have got an update of the wear companion app on their phones to 1.5. This won't by any chance affect the problems with connectivity between phone and watch. An update of Android Wear could maybe affect the problem, but this update doesn't update Android Wear. All clear?

/Daniel
[LG Watch Urbane] JimSmith94:
It adds the ability to remove itself from Doze optimization, so that might help with connection problems.
[LG Watch Urbane] sudaltsov:
The Android Wear app on the phone starts working AFTER successful BT connection. So if there is no BT connection - does it matter of Android Wear app is Doze-optimized or not?...
[LG Watch Urbane] DanielMalmgren:
The addition is that it asks for to be removed. You can do that in earlier versions as well (as you can in all apps) by going into the battery optimization settings and adding the app there.

I don't think doze is the problem though. I had the problem when I had 5.1.1 on my phone which didn't even have doze...

/Daniel
[LG Watch Urbane] sudaltsov:
Downgrading watch till 5.1.1 using http://xdaforums.com/watch-urbane/development/guide-return-to-stock-g-watch-urbane-t3213603 helps. But I am afraid the watch will upgrade itself till 6.0...
[LG Watch Urbane] sudaltsov:
I was right. The watch upgraded itself overnight to 6.0.1. There is no way to keep 5.1.1 on the watch.

---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------

It seems there is a difference in BLE stack in 6.0 and 6.0.1. Is anybody here having that pairing issue with 6.0.1 on the phone? I am thinking about putting Blues ROM 6.0.1 on M8.
[LG Watch Urbane] jedi.6:
+1 The watch remained for 4 days with 5.1 update waiting. And that night , she updated herself :( I'll have to downgrade again .... because currently it constantly disconnects
[LG Watch Urbane] Itchiee:
My Note 4 was recently upgraded to MM and i have factory reset both watch and phone and don't seem to have nearly as many disconnects as i had with the previous version(s) of wear and android.

Now Google Fit on the other hand has been out of sync the past week and it's annoying. I still feel all this stuff is experimental at times and need some more polish...
[LG Watch Urbane] zKITKATz:
Guys, I think I have the answer. Try upgrading the firmware on your phone to the most recent version. I have a Verizon HTC One M8, so I used the one from here: http://xdaforums.com/showpost.php?p=62734094

Worked like a charm for me!
[LG Watch Urbane] sudaltsov:
For the people with M8 that seems to be the solution - upgrading the firmware to 6.x. See the last posts here:

https://productforums.google.com/fo.../--At7VrHkOk;context-place=forum/android-wear
[ZenFone 2 Q&A, Help & Troubleshooting] ondrej97:
Hi. Can someone make XenonHD rom? I think its fastest rom i've ever used (Optimus G, LG G3), and have RRO and good features.

.
[Android Q&A, Help & Troubleshooting] MaddMaxx636:
I am wondering if anyone knows how to tune the controls that are included in the Simple GPU Algorithm and Adreno Idler that are on custom kernels.

I am wanting to know what each thing does and what happens when you put the value higher or lower on each control .

Simple GPU Algorithm

Ram Thresold

Lazieness:

Adreno Idler

Down Differential:

Idle Wait:

Workload:

I want to know how to turn it for saving battery and or performance. Im trying to fine tune my settings to get longer SOT and less heat.
[ZenFone 2 Q&A, Help & Troubleshooting] Calico_NC:
Somehow I broke the white connector tab that attaches the digitizer to the left side of the motherboard. I've opened it 200 times before but this time the tab came loose from the motherboard completely. Does anyone have any experience with this issue.? Also the antenna port in the upper part of the motherboard just pulled off when i pulled up the connector so now that is completely unsoldered from the board. im starting to think this phone is done. any body have any recommendations? its basically just unsoldered connections..
[ZenFone 2 Q&A, Help & Troubleshooting] sirsomething:
Did you manage to find any solution?
[ZenFone 2 Q&A, Help & Troubleshooting] Calico_NC:
nope just forgot about it. Im now using my old HTC ONE.
[ZenFone 2 Q&A, Help & Troubleshooting] sirsomething:
****. Thanks