yashsingh1/xdaforums huggingface dataset:
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
Hey everyone! I'm starting a ROM build for the Wear24 over here! I'm looking for some help, and whether you're a developer or not you can chip in.

I'm trying to avoid cracking this thing's casing open as long as I can. I know it's inevitable, but I use it as my work watch. Thus, I'm looking to have someone extract the images for me (boot, system, recovery and vendor) using dd. If anyone is willing to do this, you just need root and adb access. Here's a guide.
[Wear OS Q&A, Help & Troubleshooting] QkTreasures:
Any good news yet?
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
Not looking good. No one seems to want to tell me how to extract proprietary blobs. I've got a vague idea but still messing around a bit. I'm looking into building source trees, going to contact some other watch developers to see how exactly they're building (since... Wear OS is closed source)

There's a lot of confusion right now, but I'll work it out. Still no one has provided me the images I've requested
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Does anyone on here have the initial TWRP backup images? I'm fairly certain these will have the partitions you need. I'd help you out but my Wifi ADB transfer Rate is horrendous, and it's very difficult to hold the USB connection with the 4 pins long enough to move such a long file. I do remember as I was trying to do this for the group back when TWRP was first loaded, that someone had the images you need.
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
I'm looking at TWRP images from my bullhead right now. Changing them to .tars allows me to view their contents, but the structure is different from stock fastboot files. I don't know if dd would change this file structure, as to my knowledge it just copies the structure as is.

TWRP catalogs the partition the way you see it when it's mounted on your system. Conversely, fastboot files use the same structure I've seen in APK archives (assets, res, etc). I don't know if the tools developed for what I need the images for will play well with TWRP's interpretation, but I'm going to try something now and see how it goes.
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
Don't know if you're still active, but is there any way you can upload this to GitHub?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Pretty much all the bootloops we're fixed by flashing that supersu and rooting. Try that in TWRP.
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
Heh, XDA's quote system screwed up! I didn't post most of that :) Edited.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Yeah it sounded familiar! Yeah that guy did.most of initial legwork in March. Send him a pm
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Hey! Here is the device configuration github repo:

https://github.com/mkorenko/android_device_quanta_dorado

Good luck with the rom! :)
[Wear OS Q&A, Help & Troubleshooting] oscarillo:
Was the signal better with the original bands?

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

Are you still using the wear24?

If yes, how is been working without the original bands?
[Wear OS Q&A, Help & Troubleshooting] probstc:
It worked well while I used it without the original bands. I swam with it and the seals held, and the WiFi and Bluetooth continued to work well. When I got myself another Wear 24 with the black band, I put the original salmon pink bands on the rose gold watch (after removing the silicon seals), and gave it to my wife. It continues to work well and she is very happy with it.
[Wear OS Q&A, Help & Troubleshooting] al74:
I'm hoping to use this watch as a call and text only watch for my kids.

Anyone checked if the phone will make and accept calls using T-Mobile/Fi sim cards? I can manage without the data as long as calls and texts will work.

Also, trying to open the back, I see four very very small screws, 2 each on the top and bottom of the back. I couldn't find a small enough screwdriver for these. Are they really screws or can I ignore them and pry open the back?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Not yet, possibly never. LTE Bands are locked to Verizon. While unlocking bands is possibly, I've rarely seen it done.
[Wear OS Q&A, Help & Troubleshooting] al74:
Has this been confirmed? My understanding was that VZ no longer locks its phones. Why would this watch be any different?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
The LTE bands are locked to 13, which only Verizon can use. The Sim card locking, bootloader locking are not the issue here.

---------- Post added at 07:54 PM ---------- Previous post was at 07:47 PM ----------

First Page of this Forum discusses the LTE bands issue. I'd read through this thread before posting, as it will answer all your questions.
[Wear OS Q&A, Help & Troubleshooting] al74:
But later on it seems that someone managed to get their FI data sim working with the only issue seemed to be inability to define the APN. That's why I thought voice and text may work.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
I see, page 8 with Marcsoup using a DATA ONLY Fi SIM. I can say I didn't have the same results when I threw mine in, and this was prior to root. Mine did not show "Project Fi" as his did. Marc, did you end up modifying the APNs after Rooting?

Keep in mind the DATA SIM doesn't do texting or phone calls. So you would still need to use some VOIP / Internet Texting software on the watch for that. Otherwise you would need a Voice SIM from Google Fi, which is like $15/mo + taxes. Again this is if we figure out all the rest.

I still think we need to unlock the other LTE bands in the Qualcomm 2100. Most of the people on here are more excited about NFC Pay, but if you need any help working on this let me know via PM.
[Wear OS Q&A, Help & Troubleshooting] al74:
I have a voice and data sim from FI. I guess I'll take my chances and will open the back to try it out. Will report back to let you all know.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Good luck! Let me know what you find.
[Wear OS Q&A, Help & Troubleshooting] al74:
No luck.

I tried FI (talk and data), T-Mobile and ATT sims and none could registered to the network.

On the other hand, the APNs were updated automatically and I could select the correct APN for the relevant network. It also showed the correct number for the sim.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
I think we are still LTE Band Locked on 13, as its the only Enabled Band on the Wear24. If you have a SIM card from one of the carriers on this list that support LTE Band 13 in the USA, that would likely work.

https://www.signalbooster.com/pages...quencies-of-cell-phone-carriers-in-usa-canada

Otherwise look into downloading QPST to reprogram which bands are unlocked. - https://www.xda-developers.com/remove-band-restrictions-qualcomm/
[Wear OS Q&A, Help & Troubleshooting] al74:
Thanks for the info. I will try Tracfone and will update once I have the sim.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Here's an image of Network Signal Guru running on Wear24. Only shows Band 13. You may read many articles on how this app can UNLOCK bands, but in reality it can only disable unlock bands. Not useful to what we want.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Posting this again. I've entered USB Diagnostic mode (via ADB), and have connected my watch to my computer's USB. Using QPST I'm connected (with a status of Entering CDMA). Finally, I have READ the Phone into RF NV Manager. Not sure how to use MzTools to set the bands. Let me know if anyone can help and if I'm on the right track.
[Wear OS Q&A, Help & Troubleshooting] yochananmarqos:
PSA: Kellen @ Droid Life just said he got the Wear OS 2.0 update on his Wear24:
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Got mine too, it did not break root.
[Wear OS Q&A, Help & Troubleshooting] yochananmarqos:
Did it come as a system update or Play Store update?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
System .

---------- Post added at 06:43 PM ---------- Previous post was at 06:26 PM ----------

Here are screenshots.

[IMG="About Version"]https://lh3.googleusercontent.com/KBodEQpf2Xnr9DxjHp2OJudPobLgc_Gg3ofp4wJ5uHM1s8OROpGJuAtOII2qM3OO_9T_LV3T1g0BYI2R5IKPB02dtE70OrrPc8VAyKiC773EmeHlYC63yGs9f6aUur2Zs2DLSpgfx3hCB15vJ0Eu7HTRcbwC3TXGqSsPKChptWK8UwUHTBZ-XJihjl5s34clCnhXATaeAl1v5oUNLS7z3b-rQ65x4CTZNO7hMpZgYUEB85QIKk4WLEfMyN8XNpIGN_YSisHa1f42ByuFqPoxY1ZpydtWgamOyi8fcHACDFqKuCzMcMbv4KXOX4g2NBxvkp4O-tVqtnG_wtcJvPvM6_WbXIJbPGaz4-ui0bP8Oc7cs4Hz3ZLCW3k7SZi7tniI1WjEHUDl7BYGyLT8q8ZD4vbxUI_7vMGxpnH6uoiKX1uNce2HD-6Bi1CzKjddr8XTPSFYnMiqQimuBJZgmFycE_sM05Gj_me2mQGVpJz9-MeL1Lx__NmVANLZ3sfpakB8q-jrg0YCR5OPn1WrAHifD4m-eQCgFPuV6aAFmnSkqpaljw9rt4EJSlUpfs29FGxYY4r57SsAu0Zgb6MVRCxgQVIjyQt4YlRe0vNovDnLssA7CDkyh2B1OdGO3fK2_TDs=s400-no[/IMG]

[IMG="Swipe Left to Google Fit"]https://lh3.googleusercontent.com/vov4ZBn46Osi1Vt0XnhnKdw6pPnukq8eEFeNwLH2kyfhu3nzGD4lVAxx1CSQh-hZnVyBVwmV0E98HuRj-luNdjwn8nV9944Bcj2OBACP1dLp2c4mMgl9hTuRJIb5qgG2N8c52WOG4HP_woFOLbncMTNHtq-4Uz0gH64U0Wt18MVAWMmqIcpDqXgnjWQ7Wfi0FYj1eCNQQBYt5DdCLJFUoYB5ZRbTwMHIVWCvx3HC0OqW1Zy2jAnKAj1GF7ge_FsHb-CJmxwnVMN-3XzPxLMMh_JLrqjxIfkhvU-20nW-13BtYzMGd5exCbmcdYsBunuXJEfO9tFA9slE9ZkAs-uR4qgmIUdP6uP1FM7_GwphQdji2Nu4WLKIvdXFWkD_1Iij6o_-awRdAaaHkVA8uRQVSUhlEkFRxQwqoDHC3lI3aG1sTDclZO_IBumd6uMESFtktklBAkTKI7ByXMyuz3-vlnm6XCsfjXA5snStQB_g-zIEeLQk7B0htdE8S3KhIBiveXsBukTRgb5gSRPxp4-fw-lR0sDh_JDy9ojpVBfAjLoLsw9MreYYdZneXkFaV_uwlgCHyGJjhsa6JXbfhYd41DEHmx0v3uj1ZBlDjDCryle1c8GhlFoIHqvMx1o0n83m=s400-no[/IMG]
[Wear OS Q&A, Help & Troubleshooting] yochananmarqos:
Those version numbers are exactly what I have. So they didn't change at all after the update? What version of Wear OS do you have?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
This was the Wear OS 2.0 System Update (not the 2.16 Play Update), however the About Versions Area doesn't show the Wear OS version like on other watches. Click System Update and it will show up.
[Wear OS Q&A, Help & Troubleshooting] trevork:
I just got the new update as well!

I tried everything, checking for updates via watch, rebooting, etc. Finally I uninstalled Wear OS from my phone, powered off phone and watch, powered back on phone then watch, clicked check for updates. It still said "System is up to date" but then I checked notifications and the update was there. Clicked reboot on the watch and tada, new UI.

Note: previous to update as well as post update, all version numbers show exactly what bensdeals screenshot showed.
[Wear OS Q&A, Help & Troubleshooting] yochananmarqos:
Sounds like the update check on startup when you rebooted the watch happened to pull it. Uninstalling Wear OS from your phone made no difference since your phone was off when you turned your watch back on.
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
Everyone, the "Wear OS 2.0" update doesn't have anything to do with the Wear OS redesign we're all receiving. It will not increment your version number or make any changes to your system partition. It is neither a Play Store update nor an OTA -- rather, it's a phone-to-watch update, and all it does is flip some flags on in the Wear OS folder of the data partition. I know this, as a Reddit user forced the flags on his ZenWatch 3, and I did so as well, so I received the SysUI update a day earlier than users without an unlocked watch.

This also means we're all still on Nougat, and that won't be changing anytime soon -- changes to the system partition would require cooperation from Verizon/Quanta, which we all know isn't happening.
[Wear OS Q&A, Help & Troubleshooting] QkTreasures:
Because they hate us!! LoL [emoji3][emoji847][emoji848] #MeanPeopleSuck
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
I mean, I can't blame them. The high price point made the watch crash and burn, and there's no reason for them to maintain it.
[Wear OS Q&A, Help & Troubleshooting] trevork:
Anyone who still has not received the update, give this a try -

On your watch, go into Play Store and find Wear OS app

Uninstall Wear OS app

Once done uninstalling, its Play Store page should say “Update”

Tap “Update” to re-update the app

Once that finishes, notification to update to the new Wear OS should appear
[Wear OS Q&A, Help & Troubleshooting] prmbasheer:
Has anyone managed to take calls using the Wear24 yet? I can enable calls using the watch and can hear the other party. But when I try and speak over the watch, they are not able to hear me until I switch to my phone. Is that how it is for everyone?
[Wear OS Q&A, Help & Troubleshooting] yochananmarqos:
That didn't work for me. The staged rollout is pretty slow so far, it seems.
[Wear OS Q&A, Help & Troubleshooting] daniel910821:
I was tired of wait, so I did a factory reset yesterday and in first boot the watch showed the reboot notification.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Jared is 100% correct, you will not see an increment of your Watch's Android Version with the Wear OS update. Wear OS is just the interface that is on top of the Android OS on your Watch. Our Wear24 is still 7.1.1 and my other watch (LG Style Wear) is still at 8.0.0 as it was before this update. Correct me if I'm wrong, but it's good to get everyone on the same page here. With that in mind, what are the advantages of having Oreo or even Pie upgrades on the watch as the Android OS underneath Wear OS 2.0.
[Wear OS Q&A, Help & Troubleshooting] JaredTamana:
API differences and battery life improvements from what I understand. Has anyone got the Feed working yet? I've seen Wear24 users say yes but then later say no, leading me to believe the UI update might not be enough for that feature. I haven't got it working, either when I forced the flags or got the update officially.

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

Got it yet? If not you can force the flags: https://www.reddit.com/r/WearOS/com..._sysui3_feature_flags_on_my_zw3_heres/e6v57ag
[Wear OS Q&A, Help & Troubleshooting] yochananmarqos:
Yep, I had the notification when I took it off the charger this morning.

Yes, it works.
[Wear OS Q&A, Help & Troubleshooting] standef:
Google assistant does not work on my wear 24. OK google in personalization setting or not, still doesn't work.. Wear 2 installed with all updates. Of course mic doesn't work on phone, but replying with google assistant would save pulling out my phone. On Sprint network. Any ideas or settings I may have missed? VZW bloatware has been turned off.
[Wear OS Q&A, Help & Troubleshooting] Erofich:
Hi, try to follow the manual

https://xdaforums.com/moto-z-play/how-to/enabling-basebands-mzp-qualcomm-phone-t3684962
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Yeah, I've followed other more thorough guides/threads than that one. From my screenshots you can see I can pull the data into RF NV Manager fine, the issue is that the data in 1877 is not correct; or possibly not what we need to modify. (3G Bands)

[Bit_23] WCDMA Band II - US PCS 1900 band

[Bit_26] WCDMA Band V - US 850 band

I'm not able to pull in data from item 6828, which is where the LTE bands are.

If you are familiar with QPST / RF NV Manager / mzTool, and have successfully written LTE bands to a phone; please let me know about Item 6828
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Update

Having better luck with Higher Items (6828) with QXDM. I'll let you know if I have any success writing values soon.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Big update, I've been able to Successfully write to all items with QXDM, and the persist through reboot. I've been able to see all the new NON LTE bands I add in Network Signal Guru. I have not had any luck adding LTE bands yet, even using value "17592185995263" in 6828 and 6829 for ALL LTE BANDS.

I'll keep trying, please chime in if anyone has done this before.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
After a lot of playing around with QXDM, we only need to edit the Items 6828 and 6829 for LTE bands. Whenever I include Band 13 in the list of Bands to unlock; Band 13 is the only band listed. However when I exclude Band 13; I'm able to see the other bands. If anyone else is playing with this make sure to Write a Zero to these Items each time you want to change them or it will not take the new entry. Also make sure not to put anything in the second field for each item (ext). To ensure one Band isn't locking up the phone or causing an issue, I've just added the subset of Bands 2,4,12 (TMobile). I would assume Band 12 would have the most chance of working as it is also a 700MHz Band. Anyway, Image below shows the unlock bands, however I'm still yet to see a signal in Network Signal Guru.

[IMG="Unlocked LTE bands 2,4,12"]https://lh3.googleusercontent.com/Sp0Qhf1Iq8bgXJu1d-VOmas7iInYxO7RPN7Zoi7ZlgAroFNt3NlHdwysGrsHI7jJjs6IL10iyNyVqLKdWwR0JVDXxoDHPZCg0uOrvP4R7qtkf8SKucD0SaT5cl0rfl5moduxTfTpsVOg3sT5hmHCIfmgeJRGCqwmqoUpUj3f7lrY6IpCuFEjc7hhWqJpRspq4FKUGOsFd4co2hAvEUvQ4nY50TUtEQlXIW8IJwNHYv67wWi2bPudU8qvNAuNvbWYwITBTPBSS3QSVsOPuU7k3_44COQRqYAHUpuwxb6RUV6dVQKW-RFjhMFJ9UOCTIzq75v3JS5GQrig4REtHjd0onOSoLHPiFU4sqpnDDd_8f5iPbjX4JeoKJqCBl1rQZ2B-H2Hm0ykHiByTtVqm2qTu75vfniXCAQKNuITsDoGtOJd59RQ6HWZKrZaoyO9VdUOOcfmGp7IjHbCeMYjoUw1daoEKA5KC8kdlZEfuLrFjOK0oJjOei7vprTWSqMgwrFk5UEqHC0xTwyKQYdVALy8p9N2dcaQXQn9jXvACE2De_k-tmUfHFlcvAIoKo6a1DFTN51BwvmBZMbjIn7nW_t_120tpi12BpH2DsL4PmV0yBMC6NEMPLI5-aKqFeVYr1JY=w969-h1264-no[/IMG]
[Wear OS Q&A, Help & Troubleshooting] LuisRodriguezCalderon:
Hi, I have the last version of wear os. When I turn off and on my wear24 I have nice informations in Google assistant when i swipe. But after a moment nothing, just "good morning" . I need turn off and on to have information like time to my home or temperature or near places to me.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Just putting this up here for anyone that wants to add Google Fi APN via ADB. You will need root access.

1. Airplane Mode on

2. adb shell

3. su

4. content query --uri content://telephony/carriers --where "name='Project Fi'"

: No entry should exist

5. content insert --uri content://telephony/carriers --bind name:s:"Project Fi" --bind apn:s:"h2g2"

6. content query --uri content://telephony/carriers --where "name='Project Fi'"

: Remember _id

7. content insert --uri content://telephony/carriers/preferapn --bind apn_id:i:<_id>

8. Airplane Mode Off

I've tested this and it works.

Reference - https://android.stackexchange.com/questions/117125/how-do-i-add-an-apn-via-adb
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
OK, I'm at a stopping point here. There is apparently a lot more to do than JUST unlocking LTE bands. I was looking through the entire list of 70,282 NV items, and there are dozens associated with each LTE Band. The B13 items have data and the other LTE bands there have no data. Let me know if anyone can assist where to go from here.
[Wear OS Q&A, Help & Troubleshooting] jconnell:
This seems to be the best aggregation of data for the Wear24. Has anyone successfully added a leather band?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
The LTE/CDMA, Bluetooth, and WiFi antennas are inside the bands; any attempt I've seen to replace then have been plagued with very low wireless signal. Then there is the water resistance issue as each band have 4 pins that connect into the phone for those antennas.

I've not seen a sinple and successful solution. That doesn't cause wireless or water resistance issues.
[Wear OS Q&A, Help & Troubleshooting] QkTreasures:
So did you actually get calls, text & data then by adding Google Fi APN? Also do you still need to remove the back cover to root the watch? Thanks Ron [emoji3]
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Everyone will need to take the back plate off to get to root (as of now). As it's loaded via TWRP, which requires the bootloader unlocked, which requires access to the USB terminals inside the watch. No way around that.

The watch still ONLY Has LTE band 13 which is ONLY usable by Verizon and a few other prepaid carriers (using verizon), LTE Band 13 is not usable by Fi. I have successfully unlocked LTE Bands, however those bands have no configuration data set (NV). I think if we can extract the data from a qualcomm 2100 watch that has a Fi Band unlocked and active; then we can write it to the Wear24. Of the top of my head that would be from the LG Wear Sport or the Huawei 2 watch (LTE Band 2).

So in short, no one has used a non-Verizon SIM card in the watch to date, and discussed it online. However what we have done so far shows it is possible.
[Wear OS Q&A, Help & Troubleshooting] canadero:
Quick question and I'm very new to this, so forgive me if I'm misunderstanding the complexities. Up in Canada we have a carrier (Freedom Mobile) that seems to use LTE Band 13 with the same basic details as Verizon (at least according to a comparison of frequencies on Wikipedia.) Assuming the watch was unlocked and the proper APN details inserted, could this theoretically make and receive calls / messages with a Freedom SIM?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
If you root the watch, so that you can alter the APN; yes your watch's DATA should work on the LTE band 13.

Now, for calls and text; there are items I'm not so sure of.

1. Do you need your provider to support VoLTE for this to work?

2. The Phone app on the Watch is more like a bluetooth dialer for the phone. You would need to find a app that is a true phone (as I think it was with an earlier version of the OS).

3. Possibly the same for the Messages App, i.e. it just syncs from the watch and from what I can tell doesn't send direct. I can't confirm this, but it is something we need to determine.

Good luck!
[Wear OS Q&A, Help & Troubleshooting] canadero:
If you root the watch, so that you can alter the APN; yes your watch's DATA should work on the LTE band 13.

Now, for calls and text; there are items I'm not so sure of.

From Wikipedia, "Phones with Band 13 compatibility and VoLTE support can access Extended Range LTE." However it looks like the Wear24 only supports VoIPoLTE according to Reddit, so this might be a non-starter.

Interesting. So was the "official" value of the SIM card on Verizon just for mobile data?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
As far as I know it VoLTE is a layer on top of LTE. I'm no expert on this.. so I may be way off. There are many articles of the LG Wear sport working via VoLTE (same snapdragon 2100).

However you have to make sure your sim card is a true voice sim card, not a data only or some carriers call it a device card. At that point you are paying a lot of money monthly for something that doesn't really do what your phone will do well.

Just my 2 cents. However there is no harm in you trying it out with the Sim card from your phone.
[Wear OS Q&A, Help & Troubleshooting] bean07:
Forgive me if i'm going off topic.

I'm from Vietnam and I own an LG Urbane 2 W200V (Verizon Variant) which is also locked to band 13, if you have any data, updates please, tell me. I need to unlock my carrier's frequency.
[Wear OS Q&A, Help & Troubleshooting] NSD:
Just picked this up, have a few questions after reading through this thread (and a few others) a bit:

1. If I pop open the back and root it, use adb to send over my APN settings and use a sim from a carrier that supports LTE band 13, should data and calls on the phone work?

2. Any idea how I can actually use it to send SMS? I did the whole "don't use this carrier profile" in sim info but messages still don't send. I just get "you may be able to send a message after inserting a sim". Funny thing is that out of the box (with an older version of the OS) I used to be able to send them. Extra info: the google messages app is installed (I see it in settings) but doesn't show up in the launcher.

3. Is missing notifications on this thing normal? Say I have an unread hangouts message - it will be in the mini shade, but the watch won't tell me it's there 95% of the time.