Develop Bugs

Marshmellow update problems

So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks

Make sure 'card previews' turned on from the android wear app, other wise your experience with the faces sounds buggy! A factory reset would help on that.

Factory reset doesnt work, this also happens to me since the update, looks like this is a firmware problem.

Damnit, I wish I didn't update.
Battery is also noticeably worse.

airjordan223 said:
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Click to expand...
Click to collapse
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!

antknee2016 said:
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
Click to expand...
Click to collapse
Can you found a way to fix it?
Enviado desde mi SM-N920I mediante Tapatalk

The first issue is because the watch now comes on in ambient mode first. Even if you don't use ambient mode. It sucks. Luckily i use Watchmaker for my watch face so I went in and made all the parts (hands date etc...) to be visible in ambient mode.
I have noticed that if I wait a couple of seconds the notification does appear on my watch screen but it is after the vibrate, not immediate. I thought it wasn't showing up at first too. Still, I wish it was quicker as I look right away.
Sent from my SHIELD Tablet using Tapatalk

I went back to using Facer for my watchface and the delay is gone.
Also did they completely remove the restart option? Now it's just power off, and then press and hold the side button.

I'm experiencing both issues as you do on 6.0.1.
Also yes, reboot option is gone from update.

The renamed reset with "unpair from watch". Not gone, just to mess with us.
Sent from my SHIELD Tablet using Tapatalk

frenziedfemale said:
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Click to expand...
Click to collapse
Reboot is not reset...

I've also noticed that theater mode does not work after the mm update (unrooted, ota). I usually set it to theater mode at night to avoid burn in and just because I don't want it on all night. Now, it looks like it's blacked out, but when I wake up, the charging screen is lit up. Anyone else getting this?

I have the exact same issue after the update. Theater mode will not keep the display off if the watch is being charged. Off the charger, it works as expected. Quite an annoying bug.

If I turn ON the theatre mod with double press the power button before I put the clock on the charging dock, after that screen continue charge with screen off.
For me it's work.
Can anyone try it?
Sent from my D6503 using XDA Free mobile app

Just tried that - doesn't work for me. Screen turns off but once I put it on the charger, it comes back on after a few seconds. I'm watching it and it's still on a few minutes later.

Same here. Screen always turns back on

I'm getting the first bug the OP mentioned havn't noticed the second one though.
However the first bug is annoying enough, hopefully there'll be a quick patch.

Little patience, update to Marshmallow is great.
Here's what I mean with screen off when charge:
So in the morning until you take it out of the dock and go to work.
Sent from my D6503 using XDA Free mobile app

still on 5.0.1
man i just boughjt it 2 days ago and battery sucks,now i am trying to update cause i heard batter improved,but i cant ,watch start download but take too long and then show me a message charger to update blah blah but phone is charger is over 90 percent i have reset phone and uninstalled app many times this is ridiculous now i know why motorola was giving away this pos when yopu buy the 64gb moto x pure edition arrrrgggg

Srandista said:
Reboot is not reset...
Click to expand...
Click to collapse
Sorry I read wrong...but wouldn't you just use the power off option and then turn back on to reboot?

1.4 Update- What's New?

Guys who have sideloaded this, can you please tell what seems changed and what's new so that we can jot down a Changelog here?
Sent from my Nexus 6P using Tapatalk

The charging screen is now set to 12 or 24hr depending on the system time.

The watch makes noises now
Sent from my PLK-AL10 using Tapatalk

My vibrations SEEM stronger, or is that just me wanting them to be?

gunnyman said:
My vibrations SEEM stronger, or is that just me wanting them to be?
Click to expand...
Click to collapse
thats what she said...

Is there any keyboard for writing message now?
Send from my Nexus 6p AOSP build with f2fs support.. feel the speed

No keyboard. Device slightly laggy, bluetooth connection drops at times. After several restarts of watch and HP, slightly smooth.

Even with always on display set to on, the watch face will periodically go black. Apparently because of doze... I would prefer to exclude the ambient watch face from this feature as I do not believe it is unreasonable to expect my watch face to be always on when it is set to always on.
If tilt to wake is not active you will need to touch the screen or press the crown button to bring the watch face back. Because of this I have now enabled tilt to wake so I only need to tilt my wrist to bring the watch face back when this occurs.

Landon4444 said:
Even with always on display set to on, the watch face will periodically go black. Apparently because of doze... I would prefer to exclude the ambient watch face from this feature as I do not believe it is unreasonable to expect my watch face to be always on when it is set to always on.
If tilt to wake is not active you will need to touch the screen or press the crown button to bring the watch face back. Because of this I have now enabled tilt to wake so I only need to tilt my wrist to bring the watch face back when this occurs.
Click to expand...
Click to collapse
Doesn't doze only activate if your watch is stationary? How often do you keep your wrist in the same position? or am I wrong? I want to keep showing off my watch faces! Haha

UrbanLagoon said:
Doesn't doze only activate if your watch is stationary? How often do you keep your wrist in the same position? or am I wrong? I want to keep showing off my watch faces! Haha
Click to expand...
Click to collapse
I believe it may have to do with the orientation of the watch. I read a related discussion on Reddit which suggested the screen off being activated by some period of time where the watch face is not facing the wearer.
This happened to me 4 times yesterday with tilt to wake off after the update. Each time I noticed it I had not been inactive although I was not continuously looking at my watch. The most disturbing incident was when I was doing dishes and cleaning up around the house after which I sat down to watch TV and noticed my watch face was off.
I finally turned the tilt to wake option back on and I have not noticed this since. When I wore my Gear Live as my daily watch I always left tilt to wake on but since getting the Huawei Watch I feel as though it is a bit more sensitive and tilt to wake activates more frequently. This was having a negative impact on battery life for me which is why I turned it off.
I will update if I notice it going off with tilt to wake active.

the time it takes to wake the screen is still too long for my taste. I raise my wrist so the watch faces me but it still takes over 1 second until it wakes up.

Landon4444 said:
I believe it may have to do with the orientation of the watch. I read a related discussion on Reddit which suggested the screen off being activated by some period of time where the watch face is not facing the wearer.
This happened to me 4 times yesterday with tilt to wake off after the update. Each time I noticed it I had not been inactive although I was not continuously looking at my watch. The most disturbing incident was when I was doing dishes and cleaning up around the house after which I sat down to watch TV and noticed my watch face was off.
I finally turned the tilt to wake option back on and I have not noticed this since. When I wore my Gear Live as my daily watch I always left tilt to wake on but since getting the Huawei Watch I feel as though it is a bit more sensitive and tilt to wake activates more frequently. This was having a negative impact on battery life for me which is why I turned it off.
I will update if I notice it going off with tilt to wake active.
Click to expand...
Click to collapse
Yeah.. I usually keep gestures off. Waste of battery to keep it on... But I guess I have to leave it on.. Today is my first day with 1.4 so let's see how it goes..

The speaker and phone works surprisingly well. Have any of you discovered any apps that use the audio? For example, glide is pretty cool because you can watch video messages on your watch and respond with an audio message. I am disappointed that Google now doesn't have the audio voice response.

The speaker is actually better than I expected. There is a youtube app in the play store that lets you play videos on the watch. I messed about with it last night, but the connection is pretty slow over bluetooth. The sound was surprisingly good however.

JeffroTull said:
The speaker and phone works surprisingly well. Have any of you discovered any apps that use the audio? For example, glide is pretty cool because you can watch video messages on your watch and respond with an audio message. I am disappointed that Google now doesn't have the audio voice response.
Click to expand...
Click to collapse
No way....lmao that's the reason speaker should work (along with calls ) you telling me you driving and ask Google a question only for it to reply back with no voice input? Can anyone else confirm this stupid nonsense ?
Sent from my SM-N910T using Tapatalk

Yeah I expected Google now to use the speaker. It's stupid that it doesn't.

Google maps isn't showing a map for me anymore. Anyone else?

The music app on watch doesn't work anyone has the same problem ?
And how can you send songs to the watch?

You are now able to manually adjust date/time and time zone. This was actually the most important new feature for me and something that should have been available from the start. Android Wear is getting better but it still has a long way to go.

It has taken me almost a week to figure out how to get and make calls on it.
I had to be Johnny on the spot, as many times I only get 2 rings, and mine goes to voice mail. I see caller ID names or numbers only about 25% of the time. The watch seems to have about a 1-2 second lag, where it rings, but doesn't tell you WHO is calling, or a number.
I received a call today on it, driving down the road. Swiped right, answered it, and was able to talk to my son on it, for a bit. My impressions, you can hear ok, if the windows are rolled up, and your stereo is off/turned down. I would like it 2x as loud, maybe software will eventually get it there, but if there is much ambient noise, it's tough for me to hear.
That being said I have old, grew up on a farm ears, road a tractor, shot guns, etc, so my hearing is probably a 3/10 compared to you nubes. You may find the volume is fine, maybe even loud.
I had to download and install a LOUD ringtone, just so I could hear it ring. It was a longer than normal process involving Wear Media. I had to download wear media 1.4.6 from the developer to work with a Nexus 6P. It works, but didn't like my ring tone size of 1.2mb, it choked on that, but it would load 100-200KB no problems if they were mp3
I used it walking around the park last night. Same issue, very much traffic, and the wind blowing, and it's too hard for me to hear it. If you got off the main traffic, and out of the wind, it was just "loud enough".
I'm curious what your user experience has been, and whether you have stumbled across anything interesting about how your use has been?

[Solved] Galaxy A3 2017 - fingerprint scanner almost unusable

Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Edit 2: Best solution here: https://forum.xda-developers.com/showpost.php?p=72875604&postcount=18
If that does not solve the issue, also try this:
Edit: solution at https://forum.xda-developers.com/showpost.php?p=71964623&postcount=10

kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Click to expand...
Click to collapse
same here. Samsung makes the worst finger print scanners.
thinking of 4 scan for same finger see if that helps.
Huawei makes the best finger print scanners

kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Click to expand...
Click to collapse
That is not normal, my A5 works 9 in 10 on the first try.

Not a single error in my A3

Mine is totally unusable... any idea?

Well, it seems that I'm not the only one with this problem. Hopefully it can be fixed with an update.
I have to say that my thumb skin is a bit damaged (from doing work on cars, around the house, etc.) but this was never a problem with my S7 Edge. I tried a different finger with healthy skin and it does work a lot better, but still not 100%, it seems to me that the A3 sensor has real issues.

same Problem with my girlfriends A3.
Fingerprint scannner works in 1 of 4 times if youre lucky sometimes doesn't work at all.
She has already made 3 scans with 1 finger but didn't really help

Maybe send it back for warrenty repairs if a factory reset won't work'? I'm sorry but fingerprint sensor should work fine.

Chris.nl said:
Maybe send it back for warrenty repairs if a factory reset won't work'? I'm sorry but fingerprint sensor should work fine.
Click to expand...
Click to collapse
To be honest, I don't think this is solvable via warranty work. I am not sending my almost new phone back just to receive a refurbished piece of thrash. I am putting my faith into a firmware update. The funny thing is, I really like the phone even with this problem, it is very fluid and has even better battery life than the S7 Edge.

So here is a workaround I have found, for those having the issue:
- Instead of using the tip of the finger when adding your fingerprint, use the area just below the tip. In the attached picture, use the area marked with green instead of the one marked with red. It will then work 100%, it's amazing how fast and accurate it is. It's just not very smart like the S7/S8 and other phones and it probably has issues when the skin is not 100% perfect or maybe with pronounced geometric distortions like it is the case when using the finger tip.

Hi folks, a workaround for me was disabling the keep screen turned off, became much more accurate after that

I've got similar problem with always on display. When I turned it off everithyng is fine

I am having similar issues with my phone. I have tried using all three stored fingerprints as just my thumb and I still have trouble getting it to unlock. I do have Always On Display turned on, and I don't really want to disable it as suggested in this thread because it's an awesome feature. Samsung should be able to something as easy as a fingerprint scanner right. Hopefully this is simply a software issue that is patched

hi guys
you lock phone with power key or with widget (like screen off)?

After having the same problem I started turning my thumb much more (even almost fully vertical) during the scanning process. Now it works fine. DHNL

hi actually solved the problem what i did is that factory reset the phone, i schedule a weekly restart, i clean my scanner and i assigned all 3 fingerprints on to the same finger and it worked

Hi folks,
I am experiencing the same issue. I found some relief using a different finger. I have registered three of my fingersprints. For some weird reason only one of the three fingers works acceptably good, the other two are successful very rarely. I therefore recommend you to try with a different finger or several of them to find out which one better works for you.
Good luck !

I can confirm there is indeed a problem with SAMSUNG A5 2017 fingerprint system. The recognition rate can be extremely low in some condition (around 10% positive, meaning almost unusable). This seems to be a software bug
Here is a turn around :
If you record your fingerprint with the screen "always on" function activated , then the recognition rate is extremely poor.
if you unactivate this function during recording process, then the rate is ok (higher than 90%), even if you reactivate the always on function after recoring session
I guess this could be solved by Samsung in the latest firmware A5 (2017) update.
Gautier T., A5 owner

gautierT said:
I can confirm there is indeed a problem with SAMSUNG A5 2017 fingerprint system. The recognition rate can be extremely low in some condition (around 10% positive, meaning almost unusable). This seems to be a software bug
Here is a turn around :
If you record your fingerprint with the screen "always on" function activated , then the recognition rate is extremely poor.
if you unactivate this function during recording process, then the rate is ok (higher than 90%), even if you reactivate the always on function after recoring session
I guess this could be solved by Samsung in the latest firmware A5 (2017) update.
Gautier T., A5 owner
Click to expand...
Click to collapse
The trick seems to be working, thanks !!

kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Edit 2: Best solution here: https://forum.xda-developers.com/showpost.php?p=72875604&postcount=18
If that does not solve the issue, also try this:
Edit: solution at https://forum.xda-developers.com/showpost.php?p=71964623&postcount=10
Click to expand...
Click to collapse
updating to nougat fixes this.
you won.t need the workaround with AOD like on marshmallow

[Bug] Having strange bug with my Mi9 SE / making noises

It only happened twice for the past two weeks but it SOUNDS critical. Let me explain.
So I have double tap to wake on.
Sometimes when I double tap to wake the device it lights up and immediately goes dark again by itself, so I double tap again and it lights up again then turns it screen off by itself. I double tap to wake THIRD time and it wakes the device but also plays Geiger counter noise (like a radioactive detector) through the earphone for about 0.5sec ( sounds kinda like this ).
Unfortunately it happens at random so I can't reproduce it or send log.
Has anyone experienced this bug or it's just me? Is it a software bug?

Only experienced the Geiger counter noise through the earphone speaker once last week at night. I almost freaked out, cause it felt like a scene in a horror movie. Might have happened during or shortly after unlocking the phone - can't remember anymore.
dt2w activated (with fod).
Stock ROM - 11.0.4.0.

I had a similar problem. This remedy won't help but for me turned out that using my old phone's charger wasn't supplying the required amps.

asseroin said:
Only experienced the Geiger counter noise through the earphone speaker once last week at night. I almost freaked out, cause it felt like a scene in a horror movie. Might have happened during or shortly after unlocking the phone - can't remember anymore.
dt2w activated (with fod).
Stock ROM - 11.0.4.0.
Click to expand...
Click to collapse
Glad I'm not the only one. I thought I bought a faulty device. Seems like a software problem though which I hope it will be fixed once we get Android 10 update.
ricequeen4u said:
I had a similar problem. This remedy won't help but for me turned out that using my old phone's charger wasn't supplying the required amps.
Click to expand...
Click to collapse
I only use the original charger so it's probably not connected to that.

I also occasionally have problems with noises, I put it down to the screen overclocking with 75Hz.
Since I've been back to 60Hz, it hasn't been back yet.

Proximity sensor ignored partially?

I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?

I experience the same thing sometimes with stock rom

keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...