[G2 Original Android Development] :
Two things here... and don't feel personally attacked or anything I tend to come off abrasive and for that I apologize. These are things that a lot of people do. I like to post from time to time to remind people of them.

1. A little googling shows a fairly significant number of people having issues with both of these items across many Roms on many devices. For the Moto 360, it's mostly AOSP and CM based Roms. Apparently, most stock roms work decently with it. For Netflix, this is a VERY common issue which oddly can come and go on a device with no changes on the user's side... not anything specific to Mahdi Rom or this device family. I only mention this, because they'd probably be more suited to their own threads (if there isn't already one) for each item rather than being posted across multiple ROM dev threads (this is ofc my opinion, not an XDA rule I don't believe) as it's possible that more people are having this issue with the wristband and possibly just aren't running Mahdi.

2. This is a development thread not Q&A or Tech Support. If you're reporting an issue as it looks like was your intent, there should be logs attached (kmsg and logcat) otherwise there's nothing that anyone can really do besides possibly sympathize. The logs enable the devs to actually see what's going on under the hood, so to speak. I'm unsure if you're able to, but if something's working on one rom/stock/etc but not on this one... providing the logs from both under similar conditions may be helpful. IE: turn on bluetooh, sync the device, let it run for X amount of time until it syncs on the working rom, then disconnect it and pull the logs. Flash the rom with an issue, and repeat the same steps, with a somewhat similar duration then pull the logs. Sometimes this provides additional information for exactly what point the failure is occuring in the process, just be sure to identify which log is which.

Also, just a general note: Dr87 has said in the past that he doesn't develop this ROM directly... He's a device maintainer ie: ensuring that the ROM in it's current state is running to it's designed ability on this device, without device specific issues. The ROM developers maintain a Google+ page where issues that aren't specific to this device family should probably get reported. That said, if there are logs attached that look like it's a device issue (bluetooth not handshaking fully when it should for instance) or perhaps a framework issue (this could be some of the netflix issue potentially)... The logs allow the device maintainers to diagnose/fix the issues if it's device specific. They also allow them to pass along relevant parts to the upstream maintainers to fix issues with the android base itself.

I imagine that if you look at your logcat while the wristband is in its loop... it's probably constantly trying to handshake which would keep both devices running at full transmit power on their bluetooth constantly, explaining your battery drain. This has to do with it getting past it's searching stage where 1 device is transmitting and the second is listening, since you see the wristband on your phone. They would then be going into their handshake with both devices transmitting and receiving until they've synced. Once they've synced, both devices go into listening modes and only transmit in response to a recieved transmission, which greatly reduces their battery drain. You'd basically never be making it to the third part of that. But without logs that's just speculation. I also imagine that there will be some error in there toward the end of the sync process indicating why they won't complete the sync.

Also, Netflix runs fine for me on VS980 with the 9-20 build but I'm also running Furnace kernel. Have you tried clearing the data/cache for it? Are you running ART or Dalvik? Though, my phone did reboot when I exited netflix because of an ADSP subsystem failure (YAY LOGS!). Though, since I'm also running Viper4Android... It's not really worth reporting, since it's likely caused by V4A.

Here's an example though of the log, this is from my /proc/last_kmsg though since it's after reboot. (Dr87 please ignore, this is likely specific to furnace or V4A)

[13891.616778 / 10-08 01:28:51.519] PM: early resume of devices complete after 1.241 msecs
[13891.617647 / 10-08 01:28:51.519] uei_irrc_resume
[13891.624074 / 10-08 01:28:51.519] bcmsdh_sdmmc_resume Enter
[13891.624080 / 10-08 01:28:51.519] bcmsdh_sdmmc_resume Enter
[13891.625165 / 10-08 01:28:51.519] max17048_get_config : config = 0x621e
[13891.625821 / 10-08 01:28:51.519] max17048_get_status : status = 0xff
[13891.627308 / 10-08 01:28:51.529] max17048_work : Raw SOC : 0xbaa2 / vcell : 0xd30
[13891.627358 / 10-08 01:28:51.529] max17048_set_alsc_alert. with 1
[13891.627848 / 10-08 01:28:51.529] [Touch D] [touch_resume 5658]
[13891.629343 / 10-08 01:28:51.529] hdmi_tx_panel_event_handler: event = 8 suspend=0, hpd_feature=1
[13891.629776 / 10-08 01:28:51.529] tspdrv: resume.
[13891.742546 / 10-08 01:28:51.639] * DPM device: mmc1 (no driver) 111135
[13891.747069 / 10-08 01:28:51.649] PM: resume of devices complete after 130.266 msecs
[13891.760342 / 10-08 01:28:51.659] Restarting tasks ...
[13891.766773 / 10-08 01:28:51.669] QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 11
[13891.766785 / 10-08 01:28:51.669] QSEECOM: qseecom_ioctl: failed qseecom_receive_req: -512
[13891.766807 / 10-08 01:28:51.669] QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 10
[13891.766816 / 10-08 01:28:51.669] QSEECOM: qseecom_ioctl: failed qseecom_receive_req: -512
[13891.770160 / 10-08 01:28:51.669] done.
[13891.770200 / 10-08 01:28:51.669] [LGE][MMC][mmc_rescan ( ) START!] 0
[13891.770225 / 10-08 01:28:51.669] [LGE][MMC][mmc_rescan ( ) START!] 1
[13891.770245 / 10-08 01:28:51.669] PM: suspend exit 2014-10-08 05:28:51.676870092 UTC
[13891.978735 / 10-08 01:28:51.879] Fatal error on the ADSP!
[13891.978805 / 10-08 01:28:51.879] ADSP subsystem failure reason: :Excep :0:Exception detected
[13891.978862 / 10-08 01:28:51.879] subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = SYSTEM.
[13891.978924 / 10-08 01:28:51.879] Kernel panic - not syncing: subsys-restart: Resetting the SoC - adsp crashed.
[13891.979032 / 10-08 01:28:51.879] [<c010d274>] (unwind_backtrace+0x0/0x138) from [<c09dc5fc>] (panic+0x94/0x208)
[13891.979117 / 10-08 01:28:51.879] [<c09dc5fc>] (panic+0x94/0x208) from [<c016b77c>] (subsystem_restart_dev+0xd8/0x204)
[13891.979194 / 10-08 01:28:51.879] [<c016b77c>] (subsystem_restart_dev+0xd8/0x204) from [<c0139618>] (adsp_err_fatal_intr_handler+0x3c/0x44)
[13891.979273 / 10-08 01:28:51.879] [<c0139618>] (adsp_err_fatal_intr_handler+0x3c/0x44) from [<c0208f14>] (handle_irq_event_percpu+0x58/0x2b0)
[13891.979348 / 10-08 01:28:51.879] [<c0208f14>] (handle_irq_event_percpu+0x58/0x2b0) from [<c02091a8>] (handle_irq_event+0x3c/0x5c)
[13891.979421 / 10-08 01:28:51.879] [<c02091a8>] (handle_irq_event+0x3c/0x5c) from [<c020ba64>] (handle_level_irq+0xac/0xfc)
[13891.979492 / 10-08 01:28:51.879] [<c020ba64>] (handle_level_irq+0xac/0xfc) from [<c02088dc>] (generic_handle_irq+0x20/0x30)
[13891.979571 / 10-08 01:28:51.879] [<c02088dc>] (generic_handle_irq+0x20/0x30) from [<c0130c30>] (smp2p_gpio_in_notify+0x14c/0x2a8)
[13891.979656 / 10-08 01:28:51.879] [<c0130c30>] (smp2p_gpio_in_notify+0x14c/0x2a8) from [<c01c8628>] (notifier_call_chain+0x44/0x84)
[13891.979733 / 10-08 01:28:51.879] [<c01c8628>] (notifier_call_chain+0x44/0x84) from [<c01c872c>] (raw_notifier_call_chain+0x18/0x20)
[13891.979808 / 10-08 01:28:51.879] [<c01c872c>] (raw_notifier_call_chain+0x18/0x20) from [<c012fc40>] (smp2p_interrupt_handler+0x1f4/0x420)
[13891.979884 / 10-08 01:28:51.879] [<c012fc40>] (smp2p_interrupt_handler+0x1f4/0x420) from [<c0208f14>] (handle_irq_event_percpu+0x58/0x2b0)
[13891.979954 / 10-08 01:28:51.879] [<c0208f14>] (handle_irq_event_percpu+0x58/0x2b0) from [<c02091a8>] (handle_irq_event+0x3c/0x5c)
[13891.980024 / 10-08 01:28:51.879] [<c02091a8>] (handle_irq_event+0x3c/0x5c) from [<c020beac>] (handle_fasteoi_irq+0x98/0x160)
[13891.980095 / 10-08 01:28:51.879] [<c020beac>] (handle_fasteoi_irq+0x98/0x160) from [<c02088dc>] (generic_handle_irq+0x20/0x30)
[13891.980172 / 10-08 01:28:51.879] [<c02088dc>] (generic_handle_irq+0x20/0x30) from [<c010761c>] (handle_IRQ+0x50/0xb8)
[13891.980243 / 10-08 01:28:51.879] [<c010761c>] (handle_IRQ+0x50/0xb8) from [<c010050c>] (gic_handle_irq+0x7c/0x124)
[13891.980289 / 10-08 01:28:51.879] unwind: Unknown symbol address c010050c
[13891.980325 / 10-08 01:28:51.879] unwind: Index not found c010050c
[13892.980893 / 10-08 01:28:51.879] Rebooting in 5 seconds..
[13897.983025 / 10-08 01:28:51.879] Going down for restart now
[13897.983923 / 10-08 01:28:51.879] Calling SCM to disable SPMI PMIC arbiter

No errors detected
UTS_VERSION