[BUG REPORT] SmartWatch doesn't wake up while tapping on it

[MSC3]

After last update my Smartwatch doesn't waku up while tapping on it. I can wake it up only with button. This problem exists while screen of watch goes off on a any widget. When screen goes off while displaying a time - i can wake up by tapping on it.

It is severe problem, i think it drains battery.

[machmanbt]

I have exactly the same issue

and so have loads of users that i have posted elsewhere

I really hope this does not become another liveview

Can someone from sony please acknowledge the Bug and let us know if they are looking into fixing it ?

Thanks

www.btwatch.co.uk

[MSC3]

Sony and acknowledgment of bug? You must be joking....

Sorry, but Sony never did that.

Please look at my posts...

[Johan]

Could you please send me your details in a PM, and will forward this for investigation.

Make a relevant topic and include the following.

Name:

Phone nr:

E-mail:

Country:

Operator:

Product(s):

IMEI nr:

Build number:

[Johan]

I got some new information about this see bellow.

Seven of the ten available clock types work with wake up by double tap on it. The other three do not work like that (Smart digital clock and the two Analog clocks below). In general the clocks with the movement detection don't work with double tap.

Please use one of the seven clock types when double tap is supposed to be used.

This has been reviewed to have a more consistent solution. But besides that it can be the case that the accelerometer needs a reset, which is done by pressing the key. This is the explanation why the double tap does not work constantly.

[machmanbt]

Thanks for the reply but we already know that info

The issue is that the seven clock types that are supposed to work with double tapping dont after the last update and as regards to the Accelerometer needing a reset that cant be correct as it does not work within minutes of the screen switching off and i have even tried it with the watch sitting on a desk and not moving. so the watch has not moved

Sorry but it worked fine before the last update so there is a bug which has been introduced somewhere.

I notice that in your reply you have not stated that this is being looked into

it sounds as if you are saying that Sony are happy with this.

Please do not let this become another Liveview where its just not supported and just left and also please read the feedback on the playstore and around the web where over 90% of the latest reviews state they have the same bug.

With all of the new Watches already released (Pebble, Metawatch) and the new Watches rumoured to be released Sony have a head start on them, Please Dont ruin it by not listening to us users

www.btwatch.co.uk

[MSC3]

Dear Johan,

Did you read my post carefully?

This problem exists while screen of watch goes off on a any widget. When screen goes off while displaying a time - i can wake up by tapping on it.

I'm using green one, "Dotknij dwukrotnie ekranu" means tap it twice,

This problem also exists on any other type, even accelerometer not working properly.

[MSC3]

After update to 0.1.B.1.3 problem still exists.

[machmanbt]

Same for me

The update has made no difference at all if anything for some reason it seems to disconnect more after the update

The watchfaces that require double tap do not work after a while

The watchfaces that sense movement stay on as if the watch is sensing movement

(and i have left it on a desk with no movement at all)

Its getting annoying now that Sony cant even fix their own mistakes

[3dphilp]

wish I hadn't updated my watch as it was working just fine.  Now the turn wrist to activate wont work, double tapping faces won't activate anymore, sense movement stays on even when i have watch on table, and facebook extras will not stay logged in.  Great job SONY!!!!! I forgot how bug riddled sonys firmware updates can be as I've been in Sony Professional Land for awhile now (production equip) and they do not have the same issues they seem to in in the consumer relm.

And I love how this moderater will leave a nonsesical answer and then mark the thread as "assumed answered".  Hey Johan...Have you heard the expression regarding ASSumptions?