hi there,
since today I'm experiencing problems with my status bar scrolling down automatically, but just very shortly, a few milliseconds, but sometimes several times consecutively. In 90 percent of these "popups" the status bar disappears again after a few more milliseconds. this behaviour occurs while I'm surfing or messaging - in ordinary use. I did not drop the phone or went swimming with it.
This issue hindersthe every day use, does anybody experience the same problem? is this maybe due to a defective display?
modell: d5803
android: 6.0.1
kernel: 3.4.0-perf-gc14c2d5
build: 23.5.A.291
greetings
Related
Since a while now i've been having wierd issues with my T.
It happens on all ROMs and kernels so it's NOT a ROM issue.
I'm running CM10.1 (Experimental build) now.
Issue #1:
Chrome keeps randomly FC ing or better explained, randomly shuts down and disappears. Kind of like a crash to desktop in windows.
Issue #2:
Clock widgets randomly stop refreshing and will only refresh when touched.
I'm currently using the app ''3d flip clock and weather'' but CM's clock does the same.
Issue #3:
Keyboard randomly minimizes / disappears during typing.
It will not come back by clicking in the text area again, it will automatically come back after a period of time (10 secs to 1 minute) or will come back when closing all apps to homescreen and opening the app i was typing in again.
These all sound like RAM issues to me where for some reason the phone runs out of RAM or something...
Little help please?
Please provide a logcat.
Sent from my LT30p using xda premium
Yeah I am guessing it is a RAM issue (lack of ram) because my LMT process kept restarting when multi tasking, so I kept losing navigation.
Usually when I reboot the phone it's fine for a day or two but then it starts to act up again and the only way to fix it is to reboot the phone.
Maybe I should just start rebooting it every 2 days orso.
Hello,
I own the watch for about 1 year, and recently I faced issues with it,
The upper notification menu stays on the screen and start flashing in glow lightning, sometimes it's half screen, or just 2 lines from the top.
I think it's a burn-in but not sure, it appears only after leaving the watch without use (usually at night, and i can see the problem appearing in the morning).
It disappearing alone after playing with the watch for couple of minutes (turning off,on...)
*I'm running on LeeDrOiD latest rom
**can't post pictures cause i'm a new user....
Does anyone faced this issue, or have a solution for this ?
Thanks Ahead
Yes, a lot of post for this common issue.
it stop after a while and maybe related on the face used and on the time where the screen stay off.
Thanks, the problem seem to have been fixed after flashing the original stock rom.
hi , everyone.
i discovered by a spanish forum a glitch on the notification bar area.
when you disconnect the wifi and the mobile data, the notification bar becomes unuseful and automatically retracts.
it keeps like this until you activate again the data or wifi, my phone is a l09 rebranded to L29C636B162
lets check if someone else has this problem.
up
You should send a bug report to Huawei asap to get it fixed. It seems like this phone is full of bugs.
Have you experienced any other issue with the phone?
Same here. But I noticed it has to do with Whatsapp. When i force close Whatsapp everything is ok.
Hi,
i am new in android,
i bought my first android phone (xiaomi mi9) a month ago, using it about 3 weeks,
in this 3 weeks it not ringing/wake up me 5 times.
I have setup clock (using google clock), but it not sometimes ringing, if i searching about, somebody says me, it can be caused by miui battery saver setting, there is miui optimalization before,
i switched it to no restriction mode and it look like it helps, but not.
Today I have setup clock to 6:00 and 7:00:
- at 6:00 it not ring, nothing happend
- i wake up by myself at 6:06
- move same clock to 6:15, it ring, snooze it 10 minuts, it rings
- at 7:00 it rings
what can be the reason for clock not ringing sometimes? thank so much for any ideas.
Lubos
2f731b0c66 said:
Hi,
i am new in android,
i bought my first android phone (xiaomi mi9) a month ago, using it about 3 weeks,
in this 3 weeks it not ringing/wake up me 5 times.
I have setup clock (using google clock), but it not sometimes ringing, if i searching about, somebody says me, it can be caused by miui battery saver setting, there is miui optimalization before,
i switched it to no restriction mode and it look like it helps, but not.
Today I have setup clock to 6:00 and 7:00:
- at 6:00 it not ring, nothing happend
- i wake up by myself at 6:06
- move same clock to 6:15, it ring, snooze it 10 minuts, it rings
- at 7:00 it rings
what can be the reason for clock not ringing sometimes? thank so much for any ideas.
Lubos
Click to expand...
Click to collapse
Hi!
Maybe you have battery saver on until 6 am?
I had similar issue and solved it by changing the times of battery saver.
Maf
Enviado do meu MI 9 através do 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.