Related
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.
This has been happening randomly for a few months. I can go days when notifications are fine and they come through on my phone immediately. Then, for no reason, there are days when no notification show at all until I wake my phone.
They're clearly being blocked and my phone only attempts to pull them in when I wake it. Like a doze setting
It all started around the time Marshmallow 6.01 landed on the phone.
All battery saving optimisation settings are off.
All notifications are set to on.
I have tried EVERY app that I can find to set the Google heartbeat interval to a lower time. None solve the issue.
Factory reset doesn't fix it.
I have (always on) fiber internet so idle timeout settings on the router cannot be to blame for killing the Google heartbeat check.
I have tried it on mobile data only and it is the same
Other people online have had the same issues on other Samsung devices but I can't find anyone suffering from this on the Note 5.
Could it be an issue (somehow) with my Google account, since all notifications have to be pushed through this?
Worried that if I get a new phone I'll still have the same issue.
Any help would be appreciated.
are u using greenify??? what android u have 6.0.1 ??? did u try on smart manager / battery / to not optimize app u want get notification????
N920c/64g/cc n7 port v3/ arise sound/ doulby /xposed greenify+powernap+amplify
Not got Greenify.
Not enabled any power saving at all.
All apps are set to notify
Either the phone is blocking notifications randomly, or my Google account is.
So I had this before and eventually sorted it..... But now I'm back to delayed notifications a lot of the time if screen is off, usually until I open the app in the case of WhatsApp for example.
I have:
Gone through all notification settings, even enabling "priority notifications" app by app,
ensured data always on is enabled
Even used adb to disable power genie and yet I out my phone down for half hour, come back open WhatsApp bingbingbing messages come through.
I'm on 9.0.0.236
Anyone actually found a working solution to this.
Did read someone was told by Huawei to do "reset all settings" but that's seems a tad counterproductive aswell as a pain in the ass
Sent from my CLT-L09 using Tapatalk
So got it down to being a issue with closing apps in sleep as WiFi stays on, but after phone is left for 15 minutes or so got mate to WhatsApp me and only one tick until I opened app.
How can this be possible when I've gone through every conceivable power saving/battery/app control option I can find or mentioned online?
Must be a fix for this, can't just be every Huawei owner accepts no notifications lol
Sent from my CLT-L09 using Tapatalk
Reset all settings should bring the notifications back. Not factory reset just the settings! Worked for me!
Tried that, it continued, however at work today while in mobile data didn't seem to have any issues, may have been as I have a widget running for music all day that has a one hour timeout before it closes. Maybe keeps device from deep sleep?
As usual Huawei forums no help at all. Lots of people with a problem and Huawei dancing round the issue
Sent from my CLT-L09 using Tapatalk
Try to enable/disable Wi-Fi+, it works good for me, but I saw people complaining about it.
Settings -> Wireless & networks -> Wi-Fi -> 3 dots at the top right corner -> Settings -> Wi-Fi+
System power saving settings:
Settings -> Battery -> App launch -> Disable "Automatic management" for apps you like.
Settings -> Battery -> More battery settings -> Enable "Stay connected when device sleeps".
Data saving settings:
Settings -> Wireless & networks -> Data usage -> Data Saver -> Disable
Already done all those and more apart from wifi+ that's not an issue. It seems to be on both WiFi and mobile data. Possibly been a bit better now but hard to say if it's it's not just down to using a music app at work that's always awake, maybe preventing deep sleep.
Or just hauwei firmware takes a few days to learn regular apps to allow notifications in some super hidden menu as I have only recently forced a downgrade and rebrand of my device. Remember it did this first time I updated to pie but seemed to sort itself out
Sent from my CLT-L09 using Tapatalk
finally found someone that have same issues for 6 months!
access the *#*#426#*#* click the dots advance, click events
if there is Close err:28 things then we have same problem in wifi only,
and in advance there should be Heartbeat waiting ack alarm with minus number bug
Im on Mate 20 Pro, done anything only GCM Fix Notification on Google Play Store can fix this temporary, or switch mobile network
or just Buy another phone
This issue hasn't shown its face since 9.0.0.168 for me. Even then it was only for a few days after update. It was over zealous power and data management underneath emui
Sent from my CLT-L09 using Tapatalk
After several days of reading posts that 10.2.27.0 EEA was available, I finally tried to upgrade just now.
Checked on the phone. No update available.
Went to official ROM depository en.miui.com. The latest they have is still 10.2.26 EEA.
Ended up doing the download at miblog.co. But when I installed it failed at validation saying this is beta and I need a beta authorized Xiaomi account to be able to install it.
... So did they rollback the ROM distribution?
My guess is that with the major problems during the latest Mi 9 SE update they stopped all roll outs until they have figured out the problem. Also for other Mi9 devices.
I flashed the update via TWRP and its not so good to use. Have some connection problems with it. Hopefully they fix the issues soon and deliver it new.
I am positively surprised about the .27 update. It fixed all my battery standby drain issues. Got a much better runtime now, 2 days when fully charged
Thank God i didnt install the update. The update appeared like week ago and then suddenly disappeared. I was waiting for some reviews, because my phone is running great on .26 update,although there are still some minor bugs.
I have exactly opposite experience to the Dada124's. 10.2.26.0 was very gentle to the battery, while 10.2.27.0 drains it like crazy. Yesterday it went down from 68 % to 18 % in 3 hours - 1hour watching video, 1hour surfing web and 1hour listening to an audiobook. No wonder they pulled it. Hope they fix it with next update, because this is beyond ridiculous.
I don't have battery issue with .27
Bluetooth volume is now synced with my earbuds, there is direct control.
My alarm still don't show up on the lockscreen in the morning, it's annoying to unlock the phone to deactivate it. Am I the only one with this problem ?!?
Gokh said:
I don't have battery issue with .27
Bluetooth volume is now synced with my earbuds, there is direct control.
My alarm still don't show up on the lockscreen in the morning, it's annoying to unlock the phone to deactivate it. Am I the only one with this problem ?!?
Click to expand...
Click to collapse
I have only good things to say about the .27 update. Slightly better battery life, pocket mode (yay!), better volume handling with different Bluetooth devices (no too lows or too highs) more devices turning up as aptX or better codecs instead of the basic SBC.
gerhard_wa said:
...pocket mode (yay!)...
Click to expand...
Click to collapse
No option too turn on/off pocket mode, and screen still wake in pocket
bioly87 said:
No option too turn on/off pocket mode, and screen still wake in pocket
Click to expand...
Click to collapse
I cannot make it turn on if the upper part of the screen is covered. No need to turn off pocket mode. I tested the pocket mode very intensively and at no time however much I try or tap the whole screen or the fingerprint reader will it go to the lock screen anymore!
Gokh said:
I don't have battery issue with .27
Bluetooth volume is now synced with my earbuds, there is direct control.
My alarm still don't show up on the lockscreen in the morning, it's annoying to unlock the phone to deactivate it. Am I the only one with this problem ?!?
Click to expand...
Click to collapse
No you're not. I thinks it's a bug in the clock app. Workaround ist to schedule the DND mode to end in the same Minute Like your Alarm is ringing.
I have .27 on two Mi 9s, and both are experiencing problems:
- Battery drain
- Connection problems, both 4g/LTE and Wi-Fi
- Pocket mode, if exists, is enabled by default, because there is no switch on/off.
- Multiple issues with Android Auto
At least they fixed the AI button - it does pull Google voice assistant directly now.
lusp00ky said:
I have .27 on two Mi 9s, and both are experiencing problems:
- Battery drain
- Connection problems, both 4g/LTE and Wi-Fi
- Pocket mode, if exists, is enabled by default, because there is no switch on/off.
- Multiple issues with Android Auto
At least they fixed the AI button - it does pull Google voice assistant directly now.
Click to expand...
Click to collapse
It is similar to me
Hey, they launched 10.2.28.0 EEA!
Updating to 10.2.28.0 EEA right now.
No 28 for my mi 9 running 27 so far. Does anyone have a direct link?
nupi said:
No 28 for my mi 9 running 27 so far. Does anyone have a direct link?
Click to expand...
Click to collapse
OTA incremental
https://bigota.d.miui.com/V10.2.28....PFAEUXM-V10.2.28.0.PFAEUXM-0e3ced5073-9.0.zip
Thanks. No obvious difference to 27 yet
I updated to 10.2.28, no issue.
Except how can we confirm pocket mode? As someone said above, there is no on/off options. Is it enabled by default?
Sent from my MI 9 using Tapatalk
mynameismada said:
I updated to 10.2.28, no issue.
Except how can we confirm pocket mode? As someone said above, there is no on/off options. Is it enabled by default?
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
Cover the upper part of the screen with one hand and tap the fingerprint scanner fast for some time. Does this make the lock screen show then pocket mode doesn't work for you. It's on by default. It works well for me.
Skickat från min MI 9 via Tapatalk
This isn't very easy to describe, but I've noticed this "bug" for a while. I managed to workaround it by not updating the Phone app (as it appears the bug was introduced with the 24th Feb 2021 update for the Phone app). However, with the April (whole phone) software update, it's forced the Phone app to also update to a newer version which has this bug.
I'd be grateful if someone could see if they can reproduce this bug as follows:
-Ensure you are using the built-in Samsung Phone app as default
-Ensure the version of your Phone app is at least "12.1.10.28" (my current version is "12.1.10.41")
-Ensure your phone is off charger
-Ensure your phone is in standby for at least 1 minute (and ensure it's not being woken up during this period due to receiving messages or other notifications)
-Call the phone, and don't pick-up. Once the phone is "ringing", you can hang up
-Observe that no missed call notification is shown on the AOD or the lockscreen - this is the bug
-Wake the phone and get to the homescreen - you'll now see the missed call notification pop up at the top. If you put the phone back in standby, you'll also now notice the notification on AOD and the lockscreen
I can reproduce this bug following a factory reset, and also in Safe mode. Therefore, I'm thinking this should be a universal bug, but I'm hoping at least one other person can reproduce this. I've tried searching in other forums/threads but no one seems to be reporting this. I'd have thought this would be extremely widespread and many would have noticed this by now, hence why I'm posting to ask. Thanks in advance to anyone who tries to reproduce this.
Couple of observations/clarifications from the original post:
-If the phone isn't in standby for at least around 1 minute, then all works fine and the missed call notification shows up on AOD and lockscreen
-If the phone is charging, there is also no issue
-Phone app with older version numbers to above have no issue
-As described in the original post, navigating to the homescreen following a missed call appears to "trigger" the notification to display
Given all the above, it makes me wonder if something is putting the "Missed call" notification mechanism to "sleep". I suspect the only hope is for the Phone app to update to correct this bug.
i tick all the above boxes and i can confirm there is no missed call icon on the AOD, there is only a missed call notification on the notification bar
matty100147 said:
i tick all the above boxes and i can confirm there is no missed call icon on the AOD, there is only a missed call notification on the notification bar
Click to expand...
Click to collapse
Thanks for trying and confirming the issue for AOD! Can you also confirm it doesn't show up on the lockscreen?
Yes, once you enter into the phone and on the homescreen, the missed call notification shows up on the notification bar (as if entering the homescreen is required to trigger the notification). From there (as long as you don't clear the notification), the notification then displays as it should everywhere else (including on the AOD and lockscreen).
By the way, can you please report the exact version number of your Phone app?
By the way, I managed to get someone else on Android Central forums to reproduce this, and he's using a Snapdragon US version. So it's almost certainly a universal bug.