Known bugs in official Android 6.0 marshmallow - X 2014 Q&A, Help & Troubleshooting

These are the bugs which I found
option to expand volume control disappears after some time.
After exiting some games like simcity buildit the notification volume resets to a low volume level.
moto display fails to activate some times right after switching off the screen.
Anybody facing these issues with your official unrooted build.
Please let me know...
Thanks in advance guys !

I'm having issues with Inbox by GMail never showing any notifications

Related

Phone not muted by Android Wear

Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
I have same problem. It's bug?
finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
Yes. I am facing this problem too! Seems like a compatibility bug with Android Lollipop. Might be due to the implementation of the 'Notification Priorities'.
Hope some updates come up soon to fix them!!
I'm running 5.0.1 on my HTC One M7 GE. The mute works with 5.0.1. It's a "priority" mode setting. Where the phone does not ring, but certain notifications may make a sound if they are priority and could be lowered.
Glad it's not just me then. Hopefully it'll be address in 5.1/5.0.1
Fixed in the latest Android Wear app. Version 1.0.5
Also seems to be OK on Lollipop 5.0.1 on the watch! Yay
Hum ... I still have the problem. Mute seems alright for notifications but not for phone ring.
I have Nexus 5 on 5.0 (LRX21O), Gear Live on 5.0.1 (LWX48P) and Wear App 1.0.5..1630507.
Also, I'm using Wear Aware app for being notified on watch if phone is missing, but starting with Lollipop, I have 5 ou 6 false alert each day.
I was working perfectly with KitKat.
May be it is the Wear aware app. I'll try another one.
Maybe 5.0.1 on phone will fix this when it will be available.
For now, our nexus 5 only have 5.0 (https://developers.google.com/android/nexus/images)
Anybody found a solution for this?
I have a possible work around but need help with tasker.
I set up a profile for when connected by bluetooth so that the ringer is off and vibrate is off but because off lollipop it does not work. Think it's the do not disturb option.
In my phones setting-lg g3- i can create a vibrating pattern that is a split second long and really weak.
What i need help with is how to recreate this in tasker. I.e is there a way of changing vibration strength in tasker and pattern.
If so we will be able to create this work around until a offical option is available.
Merry Christmas
Phil
Update;
Couldn't find a way of doing it through tasker despite asking on the relevant forums and hours messing around. Think tasker needs a few tweaks to allow these options to work on lollipop.
Although i found a app that works. I can set a rule to put my phone on silent but the watch still vibrates and visa versa when not connected.
https://play.google.com/store/apps/details?id=com.fancy01.myprofiles
Hope this helps, I'm going to do a few more rules for Wi-Fi, location etc using this app.
Cheers
Phil
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Firefyter said:
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Click to expand...
Click to collapse
The link in my post above yours is to a profile managing app that does what is required. I'm not sure if the free version works as i can't remember but paid one does.
I created a profile that mutes ringtone, no vibrate with a rule that activates the profile when connected to bluetooth device.
It switches notifications on the watch to priority so don't change that as it will make the phone start ringing/vibrate.
Work around that works
I have the same issue. Here what I do.
Android watch is connected and set to mute apps
Tap the volume rocker (for me nexus 6) and you'll see it says muted. For my work day I leave it on all.
Tap the bell icon and the phone will be put on vibrate. It's working great for the moment.
Best work around I have found.
The issues has returned for me on the latest version of the Wear app....

Anyone has Notification vibration problem?

I'm using Galaxy S6 Active in Korea
Of course, i unlocked, and updated to 5.1.1
(i used 5.0 just few days, i can't remember how long did it maintain)
Now my phone seems to treat the vibrate profile as silent.
text message vibrations is Okay(i'm using google messenger, not basic sms app, not google hangout)
But, Call notification,FB,Gmail....and so on, all of feature which has vibration noti feature do not work now.
Actually i already did device reset once. at that time, i could get vibration notification.
but few days later, back to present state.
i googled, and i got some people who were experienced like me.
but they said various opinions about this problem such as battery saving mode, 5.1.1 updating...etc.
plus no oned replied "i fix it!"
I constantly use the vibrate profile and this is very problematic not having the phone actually vibrate because I am missing notifications a lot now.
Is anyone else having this issue? Does anyone know how to fix this?
plz give me your comment
I read, I think on Android central, that this occurs when power saving mode is on after updating to 5.1.1. This didn't happen on the previous software.

Oxygen OS 4.0 BUGs

Right after updating my OP3T (clean flash) to Nougat I started to encounter some recent apps screen bugs. Sometimes the first tap on recents button doesn't make the recent apps appear - although the touch is registered and confirmed by the haptic feedback. The second bug I come across is that when I tap onto the clean all button in recents, it sometimes disappears and the apps don't get closed. To exit the screen I have to use home/back button, the whole recent apps screen freezes btw and it doesn't react to scrolling.
Any tips?
EDIT
Another bug I noticed is the quick settings lag while swiping down the notification bar and different LED color (while charging for instance) than set in settings.
Click to expand...
Click to collapse
Are you rooted? Try a factory reset and see if it persists.
I've got the same bug with the recent button.
OOS 4.0 updated through OTA, rooted. Had the bug before i rooted too.
nhshah7 said:
Are you rooted? Try a factory reset and see if it persists.
Click to expand...
Click to collapse
njoythegame said:
I've got the same bug with the recent button.
OOS 4.0 updated through OTA, rooted. Had the bug before i rooted too.
Click to expand...
Click to collapse
Nope, I'm not rooted (trying to live without root, already 3 days pretending I can make it xD). Just wiped the whole phone after updating.
Another bug I noticed is the quick settings lag while swiping down the notification bar and different LED color (while charging for instance) than set in settings.
this already happened on 3.5.4, truly annoying.
I said this on another thread but 7.0 when I was using it on the 6P was quite laggy and buggy, 7.1.1 was a big step up in performance. I'm seeing similar issue on the 3T I did on the 6P on 7.0. I really hope OP update their base to 7.1.1.
These issues can only exists in OnePlus phones for months or years.. OnePlus is for hardware and not software.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
At least I'm not the only one to encounter it :/
...

Incoming call screen not opening

This issue of incoming call screen not opening just started a few days ago. I get a ringtone and vibration, but whatever screen I happen to be on stays the same. As a workaround, I enabled a notification in the notification shade from which I can answer or decline. I've tried every possible fix I can think of, even doing a factory reset as a last resort, but the problem persists. Neither Motorola nor Google has a clue. Any help would be greatly appreciated!
I should note that I am running stock Android 7.0.
i installed gapps and it worked for me(but with twrp - unclocked bootloader)
Bsherb said:
This issue of incoming call screen not opening just started a few days ago. I get a ringtone and vibration, but whatever screen I happen to be on stays the same. As a workaround, I enabled a notification in the notification shade from which I can answer or decline. I've tried every possible fix I can think of, even doing a factory reset as a last resort, but the problem persists. Neither Motorola nor Google has a clue. Any help would be greatly appreciated!
I should note that I am running stock Android 7.0.
Click to expand...
Click to collapse
I haven't ran 7.x for about six months so I don't remember if this is an option but try going to Settings --> Apps --> Phone and see if Phone is set as the Phone app. Also,is there a reason why you haven't updated to 7.1.1? There were a lot of bug fixes and improvements from 7.0 to 7.1.1.
This topic is obsolete (for me anyway) since I have a new phone. But to answer your question about version number, official support for the Nexus 6 ended shortly after Nougat arrived. Thanks!
Google updated the N6 to 7.1.1 before ending support [emoji39]
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Bugs post Oreo update (Indian version)

Moto key isn't working for me,
Lags on placing calls.... Takes almost 5 second to place the call..... Anyone facing same problems?
Any solutions guys?
did you do a hard reset yet? (return to factory settings)
you should always do it after a big update, to prevent bugs and slowdowns.
Everything working for me. I did a factory reset
pietpietersen said:
did you do a hard reset yet? (return to factory settings)
you should always do it after a big update, to prevent bugs and slowdowns.
Click to expand...
Click to collapse
Tried it out.... phone calling issue resolved... But still Moto key isn't working
after reset calling issue is fixed but moto key is still not working
moto key is asking for an upgrade and the link to upgrade it needs permission !!! .And i request for it but nothing works !!
I got no bugs after the update and is running well without a reset. Waiting for root to arrive on this
Smart Lock is not working
There is a bug when you press the volume rocker up or down and the notification level will display on top which will stay there unless you tap the screen or turn off the display.
This is annoying as hell when watching videos (especially landscape) coz I still need to tap the screen for it to go away.
Are you guys encountering this issue as well?

Categories

Resources