I saw this. My interpretation is that Samsung changed how WFS structures the manifest file so that it complies with the latest info in the WFF guide. WFS creates the manifest itself; it doesn’t let users tweak it.
If you really need control over the manifest, you could extract the watchface.xml produced by WFS and create a WFF project using it. But you’d then need to rebuild the project outside of WFS (eg, using gradle).
@neeldedkawala you can create a Android App Bundle (aab) and extract it. You can access the manifest file from there.
@imrulanwar836 How can I extract the aab file, would that be encrypted and then how can I import that into android studio as project to update manifest in there
@neeldedkawala Are you sure you really want to do this? What change to the manifest do you need to make?
I want to change this line : "uses-feature android:name=“android.hardware.type.watch”
in the manifest with this line : uses-feature android:name=“android.hardware.type.watch”
android:required=“false”
@neeldedkawala rename tha file like this:
something.aab → somthing.zip
extract it. Make your changes. I would suggest making a copy of your work first.
yes it would be better to make a copy of the project first.
This still seems like a strange requirement. It sounds like developing a watchface that doesn’t require a watch. I’m wondering if the apparent need is attributable to trying to publish something to the wrong channel in the Google Play Console, or not completing the Wear OS stuff.
I don’t think I got back to you on this. I had no idea I could skip the “…turn off bluetooth…” step. The original post I found here back when I first started this journey said you must turn off bluetooth.
Anyway, now that I am leaving bluetooth ON, I am no longer experiencing the problem of WFS dropping the connection to my watch. So, russellcresser, thank you again for all the many times you’ve helped me out!
I am so Glad you got it in the end . I do hope it was not me that said Blutooyth off . But sometimes you have to try everything . I am sending Faces to two different watches . ( GW5 and GW6 ) . I got a bit sticky just now swapping from one IP number to the Next . After a couple of failed goes I reboot Laptop and Watch . Then get it straight away . I accept I will have to type the numbers in each time . I am happy to do that igf the bonus is the files are on my PC . Enjoy . Let us see what you are doing some time .
This is what I am working on . The moon gadget was shown me by Peter who gets on here and it has a Digital time and date shown with a Tap on the face . The Tide gadget is experimental but works for my location . If anyone is interested I can post it here although it would be a little off Topic . Perhaps in a New Topic , Makers Sharing Faces might suit .
.
No, it wasn’t you who said turn bluetooth off. 
Wow, that’s really interesting! Can the same thing be done with the sun, to show golden hour and blue hour (something photographers use for outdoor photography)?
I’m afraid what I’m working on is not technically brilliant like yours! I’ve been learning how to use styles. I’ve created faces with multiple background colors, multiple faces, multiple date windows (not sure what they’re officially called), and multiple analog hands. Here’s how a few of them look when setting them on my phone. BTW, I wondered if these designs with so many selections would require more memory, but the plugin gave them green checks!
[copyrighted and possibly copyrighted images removed]
Sadly we can not switch stuff on and off exactly at sunrise and sunset . We do not have that data . We can get the numbers from Comps but we can not use those numbers in our work . But near enough is good enough . Twilight is usually a couple of hours . A lot of people fake day night from 6 am to 6 pm. Just keep a check on the size of the images . 720 x 720 px is fine for most stuff . If you had an animation running there could be 48 images in there . That us what puts the memory up . Maths is not an issue . My technicality is achieved with trial and error . Plenty of the latter . I think you can still put a face on our watch even if it does not pass the memory test . You just can not publish it on the store .
BTW . The Aqua Jewel looks Lovely . Thanks for showing your work .
OK . So we do have a Tag that toggles ( 0 or 1 ) for SR SS . If you put this in the Opacity Field for the colour of the layer it will switch on at sunrise and off at sunset . The data comes from the Weather Station Information . So you will have to be connected for it to work . The data will come via Bluetooth from your Phone . Remember to Zero the Default setting for the opacity .
([WTHR_IS_DAY]*100)
I have the same exact problem with having to reconnect every single time I click run on device with my Watch Ultra, but my 6 Classic stays connected for as long as WFS is open. This is definitely a GW7 issue with WFS 1.8.10.
FYI, I did get improvement based on input from @russellcresser. He said he was NOT turning off Bluetooth on the watch to set it up for Run on Device. So I stopped doing that and now I stay connected for more runs. Still lose connection more often than on previous version, but improved.
It’s getting old, that’s for damn sure. I do most of my testing on the 6 Classic because I’m tired of typing in all those numbers every single time I sync the Ultra.
I’m not in to adding extra steps like turning off Bluetooth, that’s should not even be a thing.
The only time I do not have type in the Ports and Paring numbers is if I do another Run witlin a Minute or so . I think it is a small price to Pay . A method using the Command Prompt has been suggested if you want to go there . I am running on GW5 Pro and GW6 . Happy to type the numbers .
I do a hundred or so syncs a day, the price for me is big my friend.
OK . I am a Hobbyist . Different story what you are doing . You should Get on to the Command Line Modification .
Im trying to find that. Im an old school command line guy anyway.
About half way up the topic . The guy is a Key Responder .
.
This is a long shot, but I wonder whether the issue with unreliable connection to the watch could be due to adb getting confused about which device it should be using. When the problem arises, the command adb devices -l could be used to list the devices that adb knows about. If more than one device is listed (eg, due to more than one watch/phone/emulator/AVD), this is a possibility.
There is a way to specify a default device for adb to use, but there’s no point trying this unless there are indeed multiple devices listed.
