Related
Hello All,
I'm hoping someone can help with this. I'm currently running X Note Build 15 on my Galaxy Note 3 SM-N9005, and it works very well. I saw yesterday that X Note Build 16 was available, so I installed it. Everything seemed to work fine, until I went into Settings and tried to change Lock Screen from Swipe to Password. After I'd entered the password for the second time, Settings just seemed to lock, and then I had a notification that the external SD Card was OK to remove - it had unmounted it! I tried again, and this time it seemed to work OK but Lock Screen still said Swipe - it had ignored the input.
I had a backup of Build 15 so I'm OK for the time being, but I'd very much like to know why this strange behaviour might be happening. Hope someone can shed some light.
Best wishes,
Mark
MFarthing said:
Hello All,
I'm hoping someone can help with this. I'm currently running X Note Build 15 on my Galaxy Note 3 SM-N9005, and it works very well. I saw yesterday that X Note Build 16 was available, so I installed it. Everything seemed to work fine, until I went into Settings and tried to change Lock Screen from Swipe to Password. After I'd entered the password for the second time, Settings just seemed to lock, and then I had a notification that the external SD Card was OK to remove - it had unmounted it! I tried again, and this time it seemed to work OK but Lock Screen still said Swipe - it had ignored the input.
I had a backup of Build 15 so I'm OK for the time being, but I'd very much like to know why this strange behaviour might be happening. Hope someone can shed some light.
Best wishes,
Mark
Click to expand...
Click to collapse
You would get better and fast replies by posting it here: http://forum.xda-developers.com/galaxy-note-3/help
Not all people replying to threads in this section own a note 3
Good afternoon,
I have Xiaomi RedMi 3 Pro with official MIUI 8 6.9.1 by miuios.cz (official Czech translated multilingual ROM) and I have a big problem - everyone can unlock this phone using unauthorised fingerprints that are not scanned and saved as trusted. I can unlock phone at the third attempt every time! And using almost every part of my body (yes, almost every part, trust me... ).
Fingerprint sensor can unlock authorised fingers too, it works, but sometimes other fingers or body parts can unlock phone too...
I did a FR after this update (wipe cache, dalvik, data) and didn't work. It is possible that I didn't notice this weird bug using older ROMs.
May I ask for your help? Fingerprint sensor makes my machine free-to-unlock for persistent thiefs and non-friendly persons Also, makes it like clear RedMi 3 (without PRO)
Thanx from Czech Republic.
Zekino said:
Good afternoon,
I have Xiaomi RedMi 3 Pro with official MIUI 8 6.9.1 by miuios.cz (official Czech translated multilingual ROM) and I have a big problem - everyone can unlock this phone using unauthorised fingerprints that are not scanned and saved as trusted. I can unlock phone at the third attempt every time! And using almost every part of my body (yes, almost every part, trust me... ).
Fingerprint sensor can unlock authorised fingers too, it works, but sometimes other fingers or body parts can unlock phone too...
I did a FR after this update (wipe cache, dalvik, data) and didn't work. It is possible that I didn't notice this weird bug using older ROMs.
May I ask for your help? Fingerprint sensor makes my machine free-to-unlock for persistent thiefs and non-friendly persons Also, makes it like clear RedMi 3 (without PRO)
Thanx from Czech Republic.
Click to expand...
Click to collapse
Normally after 3 attempts with a wrong finger, the unlock screen is displayed to be able to input the pass code or the pattern (In my case it's the pattern unlock screen).
So I'm wondering if you have correctly set a pass code or a pattern to unlock.
Xstephl said:
Normally after 3 attempts with a wrong finger, the unlock screen is displayed to be able to input the pass code or the pattern (In my case it's the pattern unlock screen).
So I'm wondering if you have correctly set a pass code or a pattern to unlock.
Click to expand...
Click to collapse
I think it was solved (I don't want to jinx it ) - the password (PIN) was set correctly, but in Settings was allowed 1 minute idle for unlocking without a password. I selected "no idle". That probably solved my problem
IMHO: Xiaomi needs to fix it, it is probably bug
Thanx a lot for your time!
It is actually not a bug. That feature is used so that users do not have to unlock the screen again in the selected amount of time, useful if they wanted to do something quick and removing the effort to unlock the phone by FP or any type of security. Cheers!
Sent from my Xiaomi Redmi 3 using XDA Labs
I've been seeking help over most big android forums, and I can't seem to get anymore help other than that, and it's utterly annoying.
So I got a redmi 5 plus over in my country which is Malaysia, and it has a unlocked bootloader, and the box that came with it is in Chinese, so I can only assume it's a imported device. And it's fine in the few weeks, after 3 weeks, my screen started to lose control. I can see the screen showing the image, but I can't make any touches on the device and it won't respond, and the only way to fix this is by locking the screen and unlocking it again. And it won't permanently solve the problem as well. It still occurs randomly between uses, and sometimes it just loses control with everything flashing on screen (emulated touches I assume), and I can't control it until I lock the screen and unlock it again. And I've tried disassembled it and reconnecting the screen ribbon cable and it still occurs. Any method of fixing it for good, it's been messing with my gameplay or normal usage and it's really annoying. Thanks for any help in advance.
What MIUI version are you on? My problems were fixed with the versions released this March.
sigma392 said:
What MIUI version are you on? My problems were fixed with the versions released this March.
Click to expand...
Click to collapse
I'm on 9.2.6.0 NGMIEK, but I can't go any further than that due to software issues.
YenChen Je said:
I'm on 9.2.6.0 NGMIEK, but I can't go any further than that due to software issues.
Click to expand...
Click to collapse
Try flashing the latest firmware files for the stable version of MIUI. There may be problems in your firmware partition.
sigma392 said:
Try flashing the latest firmware files for the stable version of MIUI. There may be problems in your firmware partition.
Click to expand...
Click to collapse
I' m currently stucked on a chinese global firmware, and I have to wait 250 hours before unlocking, so yeah.. and any more newer firmware on global will kill my phone..
My fone liked yours
When i use stock chine it does not happen... After i unlocked & used miui eu, sometime same yours...but i update always ( eu weekly) almost this phenomena sometime happen....
I think this problem is connection to rom it does not compatible with hardware
It happens to me also on global rom 9.2.3.0 NEGMIEK when turning off memory optimization on developer options. The issue goes away after putting it back to middle.
Touch display problem
I was fixing this problem with turn off the background and notifications of facebook lite app
in my country a lot of people facing this problem same
(me too)
I am on latest Rom 9.6.2.0 but have the same issue in MEI7
MI Redmi 5 Plus Touch not working issue
I am experiencing the same issue with my MI Redmi Note 5 Plus with MIUI Version: 9.6.2.0 (NEGMIFD) - Stable version.
I have checked the apps and removed unnecessary apps to make sure this is not because of the any app installed.
Please suggest me what can I do to fix this issue?
Thanks.
mirza_arslan_baig said:
I am experiencing the same issue with my MI Redmi Note 5 Plus with MIUI Version: 9.6.2.0 (NEGMIFD) - Stable version.
I have checked the apps and removed unnecessary apps to make sure this is not because of the any app installed.
Please suggest me what can I do to fix this issue?
Thanks.
Click to expand...
Click to collapse
The touch screen may not be completely unresponsive but may be slightly unresponsive or too responsive. To calibrate the touch screen, follow the following steps.
Dail *#*#64663#*#* in the phone application
Tap touch sensor
Long press the menu button
Tap touch calibration
Follow on screen instructions to calibrate the screen
Source: https://www.ifixit.com/Wiki/Xiaomi_Redmi_Note_Troubleshooting#Section_Incorrect_Touch_Sensitivity
Same problem! I have official Miui Global Stable. Please help!
Is there already a fix for this issue or people who already managed to fix it? I myself encountered this issue too on last weekend. On MIUI Global 9.2 | Stable 9.2.6.0.0(NEGMIEK) too.
Same problem
I have same problem on miui global 9.6.2.0 stable and the navigation bar not working any solution
YenChen Je said:
I've been seeking help over most big android forums, and I can't seem to get anymore help other than that, and it's utterly annoying.
So I got a redmi 5 plus over in my country which is Malaysia, and it has a unlocked bootloader, and the box that came with it is in Chinese, so I can only assume it's a imported device. And it's fine in the few weeks, after 3 weeks, my screen started to lose control. I can see the screen showing the image, but I can't make any touches on the device and it won't respond, and the only way to fix this is by locking the screen and unlocking it again. And it won't permanently solve the problem as well. It still occurs randomly between uses, and sometimes it just loses control with everything flashing on screen (emulated touches I assume), and I can't control it until I lock the screen and unlock it again. And I've tried disassembled it and reconnecting the screen ribbon cable and it still occurs. Any method of fixing it for good, it's been messing with my gameplay or normal usage and it's really annoying. Thanks for any help in advance.
Click to expand...
Click to collapse
warranty
I have the same problem and its now frequently happening. It pisses me off, specially when Im in a Moba Game..
Anyone fixes this issue? please share
Went further from inital stable stock rom (nougat) until stable 9.6.5 (oreo), same touchsreen issue still exist
Like @cyrusextra said, it affected to mobile gaming experience. I'm a FPS gamer and this problem is totally messed up
Any fix?
Any solution to this problem?
Hello all,
Last week, I broke my oneplus one's screen so I decided to try and revive an old oneplus X.
A month ago, this device was still running the latest available OxygenOS but I played around with the device at the time and decided to install Lineage 14.1. I used the following versions of TWRP and LineageOS:
- LineageOS-14.1 20181110-nightly-onyx-signed (was no longer available on the official LineageOS site)
- TWRP version 3.3.1-0-onyx
After installing LineageOS 14.1, I noticed that there were some glitches when using the phone and the UI would lagg very hard sometimes. Since my Oneplus One was still working fine at the time, I decided to not troubleshoot this any further and put the device away.
Unfortunately, last week I dropped my Oneplus One and broke its screen, so I immediately tried to fix the Oneplus X again. I figured this might have been an issue with the LineageOS 14.1 ROM so I browsed this forum for an android 9 build and found the builds by YumeMichi and by psychem.
First, I booted into TWRP and performed an advanced wipe with every option selected.
Then, I installed Yume's build using the latest version of the ROM and Yume's version of TWRP: "twrp-3.2.3-20190127-onyx".
This booted fine and looked very promising at first, however the glitching/lagging returned after a few hours of use.
Then I cleared everything again and tried psychem's version (11.08.2019 build, without MicroG). I did not change the TWRP version (still using Yume's TWRP). This would not boot but I solved that by flashing Yume's build again and then dirty flashing psychem's build on top of it. That worked fine, untill after a few hours, the lagging and glitching returned.
The past week I've been playing with the power settings and trying to find someone with a similar issue on google. No luck, unfortunately.
The, on 22/08, I noticed psychem released a new build (22.08.2019). I installed that one and at the same time enabled the option "Force use of GPU for 2D rendering" in the developer options. That seemed to do the trick. I was able to use the device for 2 days without any issues, until the glitching happened again yesterday evening.
Today I installed the 23.08.2019 build but that did not solve the issue unfortunately.
To clarify what I mean by glitching/lagging: the phone seems to work fine for 90% of the time. Everything works, the device is performing smoothly and the battely lasts more than a day, awesome.
But sometimes, the screen starts glitching, the interface is extremely laggy and the phone might even randomly reboot. This phone will then be glitchy/laggy andis unusable for an hour. Rebooting does not help, clearing caches does not help, ... The wierd thing is, the same behaviour is also present within the TWRP interface at that moment (so not only once android has booted), as you can see in this video I made. It as also present during the boot phase. But, after a certain amount of time (usually 20-60 minutes), all is fine again and the phone works perfectly.
Is there any change this is not a hardware issue and I might be able to save this phone? The only reason why I think this might not be a hardware issue is because the phone runs fine 90% of the time.
Thanks in advance!
latest build is the 23.08 build.
Try this Nougat RR 5.8.5, works great for me, no lags at all.
https://androidfilehost.com/?fid=6006931924117938132
psychem said:
latest build is the 23.08 build.
Click to expand...
Click to collapse
Thank you. I installed this one, however that did not solve the issue.
I am inclined to believe this might not be related to the ROM at all, since all the LineageOS 14.1 ROM and Yume's ROM also had the same issue and also the issue is present in the TWRP interface and during the boot cycle too.
Is there any driver/firmware/software/... that might be causing this instead of a hardware issue?
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
BuzzBradA said:
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
Click to expand...
Click to collapse
Thanks for the suggestions! I do not have Chrome and Gboard installed so that should be fine, but I have disabled the double tap to sleep/double tap to wake option yesterday. Since then I've not experienced any more glitching/lagging. If it returns I will disable the HW buttons and use on-screen buttons and report back.
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
acidiz said:
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
Click to expand...
Click to collapse
To put your mind at ease, try OOS and see if it occurs. Then you'll know for sure.
Edit: just saw your video, never seen that before.
Hello,
since I purchased my Redmi Note 10 (which came with MIUI Global 13.0.7, Android 12) I experienced some bluetooth issues which I hadn't with my previous phone (Redmi Note 7 with Android 10).
E.g.: I'm wearing a device (Dexcom G6) which sends every 5 minutes my blood glucose value to my phone via bluetooth; if I'm away for a while, the device doesn't reconnect automatically but asks for pairing again... and until I confirm I don't get new values. This could happen several times per day.
I've read a lot of people complaining about this behaviour (that seems related to Android 12); several workaround are suggested but nothing really solved the problem. I can provide more details if needed
Btw, the connection with Miband 6 is unstable too.
These issues are quite annoying and, as I said, I didn't experience them with my previous phone, so I'm wondering if switching to a custom rom can help me on this!
Hello,
Changing ROM can help, if the problem is software and related to MIUI for example.
As a last resort, I think it doesn't cost anything to try custom ROM, it is always possible to go back to the initial MIUI, if necessary.
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
spider1163 said:
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
Click to expand...
Click to collapse
Thanks for your reply!
Bascially, there are several apps well known in the diabetics community that can be used to read values from the device: xDrip+, Dexcom etc.
They all worked flawlessy on my old phone but with the Redmi Note 10:
- xDrip+ disconnects for 20 minutes after each reading (it should be 5)
- Dexcom asks for BT pairing now and then, sometimes even when I'm near my phone
Of course I disabled battery optimization.
These issues have been reported by users since Android 12 and not only on Redmi phones...
I tried to follow some suggestions:
- disable BT battery optimization: this was possible on Redmi Note 7 but I can't find such option on my Redmi Note 10;
- use apps like "Blue Car Tethering" that force BT tethering with paired devices; this improves the situation but doesn't solve it (with Dexcom I get fewer BT pairing requests, and with xDrip+ I get readings every 10 minutes);
- on "developer options": change "ACRCP Bluetooth" and "MAP Bluetooth" versions, but it didn't work even trying all possible combinations.
I'm experiencing problems with my Miband 6 too, that sometimes disconnects from its app; this didn't happen on my previos phone but it could be related to some bugs with the app itself.
My feeling is that, generally speaking, BT is more unstable.
Important: there are also users claiming not having issues with Android 12 at all, so maybe they are related to some manifacturer customizations; that's why I'm wondering if using a custom rom can help.
Sorry if I was too long but I tried to give more details.