battery life

Unfortunately I spoke too soon. After un-pairing and re-paring the battery drain seemed to have disappeared. Today however it seems to be back. Maybe it has to do with one of the other apps that have not been updated for iOS 9 and watchOS 2. I will repeat the entire process but will not install any of the watch apps that have not been updated yet. I will report back if that seems to help.

You're right about apps that haven't been updated for the new OSs being the issue I think - others have also reported the same problems.

Have you synced your photos or music to your watch? I have also many apps now on my watch that aren't updated. It seems that this is not the problem. But I have not synced back my photos and playlist. Maybe this is the problem with the battery drain. Because a normal unpair has not worked. But since I resetted the watch and the content the battery drain is gone.

I had a bad battery drain after GM Install. My battery was still real bad after impairing the watch from my iPhone 6plus running ios9 GM. I still had a heavy drain on my watch battery. I read a post about apples Now Playing app. I had it as a glance for playing PodCast. I took it off of my glances and since then 2 days ago my battery has been just fine. I believe that app is always on looking for the next command draining my watch battery. Just a heads up something to look at there may be other glances pulling power also. I took my watch off the charger and placed it next to it for a few hours and lost 24% with no use that has gone since taking the app out of glances.

I see this in my iPhone logs every 30 seconds when my iPhone is locked.

Sep 14 12:15:39 iPhone securityd[4630] <Error>:  s3dl_query_row decode genp,rowid=10598 failed (-25308): Error Domain=NSOSStatusErrorDomain Code=-25308 "ks_crypt: e00002e2 failed to 'od' item (class 9, bag: 0) Access to item attempted while keychain is locked." UserInfo={NSDescription=ks_crypt: e00002e2 failed to 'od' item (class 9, bag: 0) Access to item attempted while keychain is locked.}
Sep 14 12:15:39 iPhone securityd[4630] <Error>:  securityd_xpc_dictionary_handler identityservices[5768] copy_matching Error Domain=NSOSStatusErrorDomain Code=-25308 "ks_crypt: e00002e2 failed to 'od' item (class 9, bag: 0) Access to item attempted while keychain is locked." UserInfo={NSDescription=ks_crypt: e00002e2 failed to 'od' item (class 9, bag: 0) Access to item attempted while keychain is locked.}
Sep 14 12:15:39 iPhone identityservicesd[5768] <Error>:  SecOSStatusWith error:[-25308] Error Domain=NSOSStatusErrorDomain Code=-25308 "ks_crypt: e00002e2 failed to 'od' item (class 9, bag: 0) Access to item attempted while keychain is locked." UserInfo={NSDescription=ks_crypt: e00002e2 failed to 'od' item (class 9, bag: 0) Access to item attempted while keychain is locked.}
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] No protection identity, not returning message protection data
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 1   IMFoundation                        0x00000001918a5424 IMLogBacktraceToDepth + 80
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 2   identityservicesd                   0x000000010002bd2c identityservicesd + 64812
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 3   identityservicesd                   0x0000000100116bec identityservicesd + 1027052
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 4   libdispatch.dylib                   0x000000019b3597b0 <redacted> + 24
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 5   libdispatch.dylib                   0x000000019b359770 <redacted> + 16
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 6   libdispatch.dylib                   0x000000019b36575c <redacted> + 864
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 7   libdispatch.dylib                   0x000000019b35d274 <redacted> + 464
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 8   libdispatch.dylib                   0x000000019b36762c <redacted> + 728
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 9   libdispatch.dylib                   0x000000019b36734c <redacted> + 112
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 10  libsystem_pthread.dylib             0x000000019b56d478 _pthread_wqthread + 1092
Sep 14 12:15:39 iPhone identityservicesd[5768] <Warning>: [Warning] 11  libsystem_pthread.dylib             0x000000019b56d028 start_wqthread + 4

I've also noticed this sometimes...

Sep 14 12:43:36 iPhone identityservicesd[5797] <Warning>: [Warning] sqlite3 error in _Bool CSDBRecordStoreSaveWithPreAndPostCallbacksAndTransactionType(CSDBRecordStoreRef, CSDBRecordStoreSaveCallback, CSDBRecordStoreSaveCallback, CSDBRecordConflictPolicy, CSDBSqliteTransactionType, CFErrorRef *): disk I/O error
Sep 14 12:43:36 iPhone identityservicesd[5797] <Warning>: [Warning] sqlite3 error in _Bool CSDBRecordStoreSaveWithPreAndPostCallbacksAndTransactionType(CSDBRecordStoreRef, CSDBRecordStoreSaveCallback, CSDBRecordStoreSaveCallback, CSDBRecordConflictPolicy, CSDBSqliteTransactionType, CFErrorRef *): disk I/O error
Sep 14 12:43:36 iPhone identityservicesd[5797] <Error>: Error saving record store: CSDBRecordSQLite/10

...and this...

com.apple.xpc.launchd[1] (com.apple.identityservicesd[5768]) <Notice>: Service exited due to signal: Segmentation fault: 11

...which upon further inspection is crashing at...

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000080
Triggered by Thread:  7

Thread 7 name:  Dispatch queue: _IDSEncryptionQueueDefault
Thread 7 Crashed:
0   Security                       0x000000018b22d83c SecOTRSAppendStartPacket + 48
1   identityservicesd             0x000000010010c164 0x100010000 + 1032548
2   identityservicesd             0x000000010010c164 0x100010000 + 1032548
3   identityservicesd             0x000000010010ae60 0x100010000 + 1027680

Activity ID:             0x00000000001aefee
Activity Name:           SecItemCopyMatching_ios
Activity Image Path:     /System/Library/Frameworks/Security.framework/Security
Activity Image UUID:     5A8D7CEB-BC5B-3F5A-AE96-7B7A4DCC123F
Activity Offset:         0x00034284
Activity Running Time:   0.376114 sec

After turning off my Apple Watch, I don't see these logs anymore. (I do see wifid spitting out lots of com.apple.identityservices.error logs periodically though.)

I unpaired my watch and paired it again (restoring from backup, not a new device like advised) and the logs have stopped for now.

Hopefully these logs are of use to someone at Apple.

Im finding that battery life is good until I try to use directions on Maps, which no longer works. When I try to set up directions on the phone, they dont get sent to the watch, and when I try on the watch, it just says "loading" and never stops. When this happens, the battery drain is extremely bad.

+1

Actually Max, The solution was not to unpair and setup as new watch. It was to Reset the watch by Erase All Content and Settings, then repair once completed and restore from the last backup. This has made a substantial improvement to battery drain on a number of users watches including mine. Still not quite as efficient as the last beta prior to the GM, but much improved on the less than half a day battery life we were getting after the upgrade to the GM.

I got a full day of battery yesterday with around 14% remaining after 15 hours.

worked for me even without setting up as a new device. So simply unpairing, pairing, and restoring from backup did the trick for me.

Instead of forcing the GM update to the watch, I let it notice on its own time (about 12 hours after I put the GM release on my phone) after the push was done, I wore the watch all day today (from 7 am) and now 13 hours later I still have 43% remaining. That battery life includes a 30 minute walk, a few calls via the watch (when I'm home, it's easier to answer the watch than fish for and answer the phone), and a regular amount of glances and notifications.

Honestly, it's the best battery performance my watch has had period.

Ok so that fixed it for me. When I re-paried the Apple Watch to my iPhone I choose not to install any of the 3rd party apps. All that was installed was the default apps that come with the phone. After a full days use I still have 67% battery life. That is definitely the best battery life I've ever had with the Apple Watch. I will only install the watch apps after they have been verify iOS 9 ready. Hope this helps others.