Hi everyone. I recently bought a Xiaomi Mi Max 3, my first Xiaomi phone. It got approximately 3 major updates and is now running MIUI Global 10.3.2.0 Stable. The other day I tried taking a photo of my phone and noticed a white dot next to the front facing camera. I tried to take another photo and noticed a constantly blinking light from the same spot. It's not the notification light, that's on the left side and is noticeable with the naked eye. This one however is on the right side (next to the camera) and is not visible to the naked eye.
Upon further research I found out that it might be what I initially thought it was; the proximity sensor. However from previous experience with my Samsung Galaxy S5 I've seen that the proximity sensor is only on during phone calls or if air gestures was on. But on my Mi Max 3 it's always on. The moment I turn the phone on it starts lighting up. I don't have auto brightness/face unlock on, and also tried to turn the proximity sensor off in call settings. But no luck. It even lights up when the screen is locked/off. I don't know if there's any settings causing this, but I tried turning almost everything proximity related off (pocket mode etc.) I have seen that other Xiaomi users have been having this issue too. I tried CIT and the proximity sensor seems to be working (0 to 5cm) but fails to calibrate.
So I had a few questions
1) Is this normal? Is it normal for the proximity sensor to be always on? I highly doubt it
2) Any way to fix this?
3) Will it consume a significant amount of battery power?
*If this really is an issue and not normal, I hope it'll get fixed with a software update because I don't think it's a hardware issue. I've read that people were having similar issues after update here
I don't know if the problem existed before the updates; noticed the light recently only!
Thanks
Attachment:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hello,
My N7100's a little too sensitive to rotation on the right. This just started happening 2 days ago, out of the blue. For the left side, I have to rotate my phone properly into landscape mode but to the right, even if it is tilted 1/8th of an inch e.g. while picking phone up, switching hands or left handed operation, it will suddenly rotate to landscape.
I have tried calibrating the gyroscope some 10 times but to no avail.
Any solution to this?
Thanks!
SOLVED: Read post #8
No one?
It's a bug in samsung touchwiz (4.1.2)..I have it too only solution I got was to use ultimate rotation control it will help or else if you can wait for samsung to fix it in 4.2.2
Here's the app link I hope it helps
https://play.google.com/store/apps/details?id=nl.fameit.rotate
Sent from my GT-N7100 using xda premium
@mufaddalezzi Thank you for your reply. However, my problem has not been solved by the app since it doesnt adjust the sensor.
My problem:
Phone thinks its tilted to the right while it is only 5-6 degrees to the right. I cant play games that require motion sensing such as Temple run because the character is running to the right with the phone being perfectly straight.
XDA, i need your help!
P.s: i tried restoring to an older nandroid backup from TWRP but to no avail
Tried. Calibration from the service menu at *#0*# under Sensors and again, no help. This wathe post that fixedit for someone else
http://forum.xda-developers.com/showpost.php?p=37539286&postcount=6
Heres a photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe it's a hardware failure(accelerometer or gyroscope)..that means you might need to change/replace it
Sent from my GT-N7100 using Tapatalk 2
Sure? I am not covered by warranty and would hate to sell my phone the gyro works fine its just that the calibration of it is wrong, the phone thinks it is tilted slightly to the right
I figured it out. For anyone else with this problem:
1) Boot phone into safe mode (Turn phone off and turn it back on. As soon as animation starts press and hold volume down button - It should say SAFE MODE in the lower left corner of the screen when turned on)
2) Reboot phone
Voila!
Mystery solved. Case closed.
Hey fellow OP5T owners,
I recently upgraded to BluSpark r106 (probably completely unrelated) on OOS 5.0.4 and today I noticed that my cam has a weird bug on the bottom of freshly taken pictures when holding the camera vertically (stock cam).
It does NOT happen when I am holding it horizontally, and sometimes it doesn't occur when you switch to the gallery fast enough after taking the photo.
It also does NOT happen in portrait mode at all, but when I'm holding it vertically in Pro mode and in normal auto Picture mode.
Video is not affected in any way.
To me, it looks like the processing of the picture gets messed up because the pictures come out fine in the gallery after taking the photo, and after a very short timespan, the artifacts pop up in the final picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm assuming you're using the standard, unmodified camera app that comes with OOS. If that's the case I would suggest you download any of the third party camera apps that are available in the Play Store and see if you can replicate the same problem. If the problem does not appear on another camera app, then it's almost 100% likely that is a software issue related to the camera app and the kernel might be a possible culprit.
If that's the case in your case I would wipe dalvik/cache and flash stock kernel and see if the issue is resolved.
Same issue with third party camera apps like Open Camera and the Nokia Cam that floated around here somewhere.
I'm now dirty flashing stock OOS 5.0.4, then check if it solves the problem and then go back to modifications.
Thanks for your input!
Edit: I tried it out twice now, both time same results, the issue is solved with a dirty flash of OOS 5.0.4 and Magisk, and is replicatable by flashing BluSpark r106.
It seems to interfere with the cam, especially when using touch to focus.
Same here. Thank you for your post! I was worried that it was hardware related.
Anyone knows if the A50 has a LED notification light? The S10 does not so I haven't got high hopes for the A50.
Hopefully A50 will get the ring light notification which turns ON while accessing front camera or face unlocking.
I read somewhere that samsung is working on S10 with same feature via OTA.
Let's see..
The A50 doesn't have an LED light for notifications, but it does have an option to enable camera flashing and/or screen flashing for notifications.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lambada24 said:
Anyone knows if the A50 has a LED notification light? The S10 does not so I haven't got high hopes for the A50.
Click to expand...
Click to collapse
No it has always on display for notifications though
sidnyc said:
The A50 doesn't have an LED light for notifications, but it does have an option to enable camera flashing and/or screen flashing for notifications.View attachment 4720413
Click to expand...
Click to collapse
Have you managed to make it work ? I tried several times without success
I'm a lot disappointed... Notification to AOD = small unmarked font. Notifications are difficult to see. And sometimes AOD has a little brightness. Why?
The screen Flickering is short. Cannot be set. And I still have a problem: Ringtone and SMS have a weak sound. There's no sound In your pants pocket. Samsung has disappointed me. Samsung Notification a lot of bad((.
Ante666 said:
Samsung has disappointed me. Samsung Notification a lot of bad((.
Click to expand...
Click to collapse
You are perfectly right
Tiny dot on display?
Tiny dot on top portion of display while charging .. it is so dim that only see if the display is locked and full black ...
It seems to be that its not a light but a infrared light
Buy a cheap ass xiaomi arm band, it can show you notifications and alert you with vibration.
Anyone know how to access front camara ring using java
Is there any way to forcefully enable AOD on Mi 10T? Via build.prop or tweaking MIUI itself; I just want to try this while my phone screen is off, that's all
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's a fun novelty, we should all admit.
I tried installing the Always on apk from the m10 on my 10T but nothing changed.
Then I changed my region to India (global rom) and the AOD option appeared in settings but when I applied it, nothing happened.
Always on displays are only available on OLED screens that can illuminate single pixels. LCD will never have always on displays so this thread needs closing.
BaconTrousers said:
Always on displays are only available on OLED screens that can illuminate single pixels. LCD will never have always on displays so this thread needs closing.
Click to expand...
Click to collapse
LCDs are never meant to have AODs, yes, I get the whole point out of it, but My point is, there are ways that other MIUI devices, i.e., RN9Pro curtana, with a lil bit of flashing some AOD Mods thru Magisk have proven that MIUI AOD can be enabled, what I'm trying to convey is that, os there anyone here, with the knowledge and enough curiosity that could help people like me to enjoy a bit stupid but fun way of "messing around" with the android framework, that's all. You don't need to "Close" this thread.
Honestly, ain't anyone here amazed by that MIUI AOD? It consumes power because we have an LCD panel, yes, but we can turn it off anytime. It's both the novelty and satisfaction that gave birth to this stupid but curious idea.
It's not that much of a novelty, i had aod 10 years ago on several phones... It just comes to the fact that you don't really don't need that
si think this is a good idea! probably all LCD displays know aod handling. It just doesn’t allow it because of the brutal reduction in energy use!
Iomarius said:
LCD 永远不会有 AOD，是的，我明白了全部要点，但我的观点是，其他 MIUI 设备，即 RN9Pro curtana，通过 Magisk 稍微闪烁一些 AOD Mods 已经证明了可以启用 MIUI AOD，我想传达的是，这里有任何人，有知识和足够的好奇心，可以帮助像我这样的人享受有点愚蠢但有趣的方式来“玩弄”安卓框架，仅此而已。您无需“关闭”此线程。
Click to expand...
Click to collapse
How do i start AOD？RN9pro
First off, I Love the phone. Hardware is great, Android 12 is mostly great but there are some weird things I've noticed that haven't really been an issue on previous phones pre-Android 12. I got rid of a OnePlus 8 pro for the Pixel 6 pro.
1: I have to use a Bluetooth to 3.5mm adapter (Bluetooth to auxillary input) on my car to Bluetooth to my stereo. Issue is, the adapter is ALWAYS on and when in range my phone is ALWAYS connected to that adapter. Android 12 gives you the option to quickly switch when you're playing music or watching a YouTube video in the volume slider menu but not say when you're playing a Facebook video, Instagram video or similar. The workaround has been to just completely disconnect Bluetooth which interferes with other devices like my Fitbit and such.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2: AOD doesn't come on when it's dark out. I usually get up at around 4am, and of course it's dark in my room. When it's pretty dark, not even pitch black AOD doesn't turn on. It's almost like the phone lacks a proximity sensor and relies souly on a light sensor for AOD. Another scenario was I was out with my family trick or treating tonight, in the suburbs where there was plenty of light and AOD still didn't come on when I pulled out the phone to check the time. Of course this isn't a huge issue, just an inconvenience
3: the lack of ability to set your own lock screen shortcuts. I don't use Google pay, nor do I control devices using the Google home app or shortcut.. it would be nice to set those to whatever I want. To add into that, I do have those both disabled but occasionally the Google home shortcut appears when I click the power button to turn the phone on. If I click it of and back on about 80% of the time it disappears.
I don't want anyone to take these as complaining, just thought maybe I'd chime in on some "issues" I've noticed.