Related
I'm new to rooting, installed MIUI and loving it so far. My hw is 003. Everything is working so far but i have a few questions -
1. Do you use the default kernel or replaced it? I've seen screen tearing a few times and battery life could be better so I'm thinking of trying a different one. Read a number of threads in the root section.
2. Did you replace the lockscreen? I'm asking because I love its look, but if you enable security there's no slide to unlock and its not so useful.
3. How often do you update the MIUI build - I read it comes out every Fri, do they have major changes?
#3, the official build is done on friday, porting to individual phones is on/around sunday
1. I'm on the 1.1.28 build and using the kernel that came with it. Savage 1.6. It is by far the best kernel I have ever had the pleasure of flashing and I have no reason to use anything else. When I update to a newer build, I will most likely flash this kernel over it.
2. Still using stock lockscreen. I agree that the pattern lock could have been implemented better.
3. What elegantai said.
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
2. Never really noticed that before. Can you pull it down with a Sense ROM? It's been so long I can't remember. You can always hit the home key while in a call and pull the bar down from there.
ECrispy said:
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
Click to expand...
Click to collapse
I actually have the same problem with the app killing. Great feature yes but it always kills the app regardless of how long or short I press it lol. Changing the duration didnt seem to help.
Sent from my PC36100 using XDA App
_MetalHead_ said:
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
.
Click to expand...
Click to collapse
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
ECrispy said:
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
Click to expand...
Click to collapse
That's odd, it works perfectly for me. What MIUI build are you on?
_MetalHead_ said:
That's odd, it works perfectly for me. What MIUI build are you on?
Click to expand...
Click to collapse
Latest - 1.2.11
I dunno, maybe it's a bug with that build.
from my observations the back tap close program happens only when a program is lagging. if you dont have too many things going on at once it shouldnt be a problem
yeahh it is a problem occasionally for me. I normally skip and flash every other week. This week im gonna flash again though, because it seems slow.
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
Has anyone tried using this option? I tried it and in an hour my phone kept on freezing multiple times. Might be some issue..
I had no issues using double tap.
I am also using this option since the phone came to me. Ad i had no issues
Sent from my iPhone using Tapatalk
Only issue that I have with it is that it works maybe 70 percent of the time.
simpleyoona said:
Has anyone tried using this option? I tried it and in an hour my phone kept on freezing multiple times.
Click to expand...
Click to collapse
Been using it and double tap to dim with no problems. Works each and every time for me.
simpleyoona said:
Might be some issue..
Click to expand...
Click to collapse
I would look into that. :good:
I find it works great if you do it at there tap rate lol if you do it too fast or slow it doesn't seem to register all the time, but other then that no complaints.
Youssarian said:
Been using it and double tap to dim with no problems. Works each and every time for me.
I would look into that. :good:
Click to expand...
Click to collapse
tried it again, it froze again. happens when i double tap, dont unlock using code, lock screen again using fingerprint button, then now unlock using fingerprint button and putting in fingerprint :| can someone confirm?
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.
They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.
Just tap the lock, no need to swipe
Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.
skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.
kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine
Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk
No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
all good on ArrowOS, DT2W and sleep working great... i know it's possibly not what ur looking for... but it's a seriously good rom.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
Yes, this happens also for me
I'd assume this would also be an issue on the Global rom?
If so, we can bring it to Poco's attention via Poco community forum.
Otherwise, we'd have to bring it to Xiaomi's attention on the Mi community forum.
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
this any good? or there's others if you search playstore....
this one maybe
(as a possible temporary solution, i mean)
EDIT: sorry, i read ur post as a touch sensitivity issue. have re-read, don't think those apps are of much use
Interestingly, don't have problems with double tap to wake, it works always, only with tapping for always on display to quick check time or notifications. Works 1 in 10 times. It's funny, tap, nothing, double tap ok.
Morak75 said:
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
Click to expand...
Click to collapse
same issue
Same issue, probably the biggest annoyance for me since I'm almost unable to use 10 second AOD tapping to conserve standby power.
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
blackhawk said:
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
Click to expand...
Click to collapse
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Nemix77 said:
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Click to expand...
Click to collapse
You be amazed how many have no clue or just don't think using of it.
It may be a settings glitch or again some sort of power management running amuck in the background. Play with it...
I posted the issue on Mi Community and Poco Community forum.
Not many people seem to use the double tab to wake feature with AOD set to 10 seconds.
I tried searching on Xiaomi and Poco both forums with keyword double tap and not a single thread for the Poco F3/Redmi K40.
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
I think youre right bro. If i time my taps perfectly and dont move position between taps, it works most of the time. Same goes for the AOD. Single tap works but it takes almost 2 seconds for the AOD to pop up which is pretty slow imo.
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Nemix77 said:
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Click to expand...
Click to collapse
Bro did you try single tapping and waiting for ~2 seconds?
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Nemix77 said:
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Click to expand...
Click to collapse
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
colosocool said:
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
Click to expand...
Click to collapse
Might depend on the device. Doesn't use much at all on my Samsung Note 10+.
With AOD touch to view active and phone/text running I use less than .5% @HR.
Never tried deactivating Double Tap on though... it's too useful.
More than likely it's not the culprit. Cloud apps and trashware like WhatsApp, FB, Google system apks are prime suspects.
Easy enough to test...