MiPad 4 - Touch bug at after boot - Xiaomi Mi Pad 4 Questions & Answers

Hi everyone, I'd like to ask you a question. I have a Mi Pad 4 and every time, after booting, the touch screen does not appear to respond immediately to the commands on the lock screen. I have to press the screen randomly to make it work. Once the touch starts, the tablet works perfectly.
Can you tell me if I'm the only one with this problem?
Thanks!

I do too. The screen would hang up when boot. I have to turn off the screen and on again for it to work.
And anyone have auto shutdown bug? Mine will auto shutdown when enter deep sleep and battery is below 15%, even when plugged in. Nothing happen above 15%.

Never_Sm1le said:
I do too. The screen would hang up when boot. I have to turn off the screen and on again for it to work.
And anyone have auto shutdown bug? Mine will auto shutdown when enter deep sleep and battery is below 15%, even when plugged in. Nothing happen above 15%.
Click to expand...
Click to collapse
Fortunately I'm not the only one with this problem/bug.
Regarding the DeepSleep and the shutdown I have never try to verify it. Usually when the tablet is 30% I recharge it.
I'll try to test that.
Currently I have the HavocOS 2.8 ROM and I don't know if the deepsleep is set in the same way. But ill will try and I let u Know.
If someone else has our problems please reply this thread.

Yes after boot I have to pick up the tablet and move to unlock the screen faster.
Maybe its a feature?
It appears in TWRP too

paul-planlos said:
Yes after boot I have to pick up the tablet and move to unlock the screen faster.
Maybe its a feature?
It appears in TWRP too
Click to expand...
Click to collapse
I don't know, I thought it was just my problem, but apparently I'm not the only one. Even with TWRP and custom rom happens

Related

Please help T7373 Touch pro 2

I'm using FROYO x 2011.01.28 SYSTEM.EXT2 UPDATED
It can detect wifi but can't connect to it.
And the biggest problem for me is when i turned my phone off.
It's turn to green and turn to red after somebody called with screen off.
but if I don't let the screen off,I can call without problem.
anybody please help.Thank you very much.
siamboyecc said:
I'm using FROYO x 2011.01.28 SYSTEM.EXT2 UPDATED
It can detect wifi but can't connect to it.
And the biggest problem for me is when i turned my phone off.
It's turn to green and turn to red after somebody called with screen off.
but if I don't let the screen off,I can call without problem.
anybody please help.Thank you very much.
Click to expand...
Click to collapse
Is your access point secured with WEP? WEP is a known issue. Try to switch to WPA.
About your screen off, i don't get what the problem is, be more chronologic
afrizal_chen said:
Is your access point secured with WEP? WEP is a known issue. Try to switch to WPA.
About your screen off, i don't get what the problem is, be more chronologic
Click to expand...
Click to collapse
Ok First I let my phone to sleep(screen off with green LED )and when I call in, it shows red LED with screen still off.when I turn on screen ,It's show me lock screen with nobody call me.
I try to change Force_cdma=0 or delete it and it gives me same thing.
Thank you.
Now I changed sleep mode =2 and it's working.
siamboyecc said:
Now I changed sleep mode =2 and it's working.
Click to expand...
Click to collapse
That should have no effect whatsoever on wifi.
Also, if you're running a newer kernel with the PLL2 commit, you should be setting this to =1... You'll get much better battery life, and you'll be able to OC without SoD (at least not as many as previously )
siamboyecc said:
Ok First I let my phone to sleep(screen off with green LED )and when I call in, it shows red LED with screen still off.when I turn on screen ,It's show me lock screen with nobody call me.
I try to change Force_cdma=0 or delete it and it gives me same thing.
Thank you.
Click to expand...
Click to collapse
Force_cdma= should be set to 0 or deleted as your t7373 is a Rhod100 if i'm correct.
So your problem seems to be that you don't receive phone calls when your phone is in sleep mode? Make sure you run the newest kernels. I can't remember issues like this on my rhod100..
Maybe just try a clean build, delete data.img (rename if you don't wanna lose everything, backup!). Or try a different build to pinpoint your problem.
And the last thing, as you are running a froyo x build, this question would've fitted perfectly in that thread
Good luck!
Thanks everybody.

[Q] SGS2 screen stays on after notification while charging

Hi guys!
I noticed over quite a time, that while I leave my phone charging over the night, any random notofication will cause the screen to stay on until I wake up and manually turn it off.
On my galaxy s2 I have VillainRom 2.1.0 (Android 2.3.4) with ninpho's 2.0.4 kernel.
However I did notice the problem before with VR 1.4 and CF-Root kernel (didn't use anything else yet), so I figure it might not be related to this.
This is rather annoying, as I don't want any burn in effects on my screen, but there's a much worse part about it:
It's noch 100% limited to the time of being charged. If I remove the charger at 100%, play around a little with the phone and then go to sleep, some random notification (whatsapp/sms etc.) will still cause the phone to wake up and not go back to sleep mode.
What happens is, I wake up with a phone at 50% battery (at it's best!), or I don't even wake up because my phone is dead and therefore my alarm clock stays quiet..
I read about some people having this problem with their SGS1 and it might help to go to Settings -> Applications -> Development -> uncheck Stay awake.
SGS2 does not have this "stay awake" option (or I'm seriously stupid)..
Anyone an idea what I might want to try?
Best greetings, Alex
At that screen I have "Standby" and you need to have it unchecked. Also, what's your screen-off delay? You don't have any apps like screebl keeping you screen on, I assume?
prodygee said:
At that screen I have "Standby" and you need to have it unchecked. Also, what's your screen-off delay? You don't have any apps like screebl keeping you screen on, I assume?
Click to expand...
Click to collapse
I do not have this option. my screens stays on all the time.
You're problem sounds similar to mine.
http://forum.xda-developers.com/showthread.php?t=1224117
I have tested with a stock rom of which I made no input and had the same issue.
Hope we can solve our problems. Cheers
cjackway said:
You're problem sounds similar to mine.
http://forum.xda-developers.com/showthread.php?t=1224117
I have tested with a stock rom of which I made no input and had the same issue.
Hope we can solve our problems. Cheers
Click to expand...
Click to collapse
mine just started doing it. i have been running custom rom for awhile now.
apps recently installed:
words free
launcher pro 806
extended controls
impossible level game
I have uninstalled:
words free
impossible level game
my issue is still happening.
when unplugged screen turns off.
I can get a text, it will light up then turn back off.
when plugged in (charging)
display will not turn off unless i press the lock button.
if i get a text the screen turns back on and stays on unless i press the lock button again.
I have recently re-flashed, complete wipe of phone and factory reset wipe.
I still have the screen on when charging and no option to disable.
I need an option to disable the "stay awake"
As my fault occurs with the phone completely reset on a stock rom it must be hardware so I am going to return it and see what happens from there.
I have flashed CM7 and there is an option to turn stay awake off.
This option is removed in DarkyRom.
Finally figured out how to turn it on or off!!!!
install the app extended controls and add stake awake as a toggle.
Turn it off!!!
then remove app
FINALLY!

[Q] phone not powering down completely

have you guys noticed that when you power down the phone it does shut off but not completely. the reason i think that its not fully shut down is because the phone boots back up within seconds of powering on....also the up time and awake time have not been reset back to 0. this actually is the only way my phone goes to sleep. any other time when i just turn the screen off my phone won't really sleep (wake lock)..ive noticed this with the blackend rom and also infected rom...the way i found to fix the wake lock issue is to do a factory reset which fixes the problem until i have to charge the the phone which everyone knows that the phone won't sleep while charging. so have you guys experienced this? and also do you know whats causing the wake lock? ive searched the forums and cant find anything...thanks!!
Fastboot, in the power menu, turn it off.
ok turned off fastboot and this fixed the up time and awake time not resetting...still having the wake lock issue tho...any other ideas to fix this?
dubldare said:
Fastboot, in the power menu, turn it off.
Click to expand...
Click to collapse
Found this although it is not evo 3d specific it does go into detail about the wake lock issue and why it is apparent hope its of some use or at least explanation http://forum.xda-developers.com/showthread.php?t=1128135
if you guys are not experiencing the wake lock issue what baseband and pri version are you on? im on baseband 0.97.10.0530 and pri 1.16_003 and prl 21083
poktangju said:
have you guys noticed that when you power down the phone it does shut off but not completely. the reason i think that its not fully shut down is because the phone boots back up within seconds of powering on....also the up time and awake time have not been reset back to 0. this actually is the only way my phone goes to sleep. any other time when i just turn the screen off my phone won't really sleep (wake lock)..ive noticed this with the blackend rom and also infected rom...the way i found to fix the wake lock issue is to do a factory reset which fixes the problem until i have to charge the the phone which everyone knows that the phone won't sleep while charging. so have you guys experienced this? and also do you know whats causing the wake lock? ive searched the forums and cant find anything...thanks!!
Click to expand...
Click to collapse
When you reboot your phone, it does not turn completely off because you are rebooting the phone. It is a feature added by htc to speed up reboot speeds. When you reboot, it kills all apps and processes, goes to sleep, and boots up.
Turn fastboot off (menu>settings>power>fastboot) if you want it to turn completely off while rebooting.
To make the phone sleep while charging, go to
menu>settings>applications>development and uncheck "stay awake"
went to my setting and the stay awake while charging was unchecked already...actually i dont mind having wake lock while charging...just the wake lock with normal use...thx tho
Twolazyg said:
When you reboot your phone, it does not turn completely off because you are rebooting the phone. It is a feature added by htc to speed up reboot speeds. When you reboot, it kills all apps and processes, goes to sleep, and boots up.
Turn fastboot off (menu>settings>power>fastboot) if you want it to turn completely off while rebooting.
To make the phone sleep while charging, go to
menu>settings>applications>development and uncheck "stay awake"
Click to expand...
Click to collapse

[Q] Screen not locking

I got my AT&T Galaxy S3 on Saturday and have seen this issue a couple of times now. The issue is that sometimes the screen will not lock after the time I have set (30 seconds). Also, the touch key lights stay on forever until I lock the phone. When I unlock it the touch key lights stay on and the screen doesn't lock. The only way I've found to fix it is a reboot. I first noticed this when I received a text. I use goSMS and have it set to turn the screen on for 10 seconds when a text is received.
Has anyone else noticed this issue or know how to resolve it?
I'm also having the wifi disconnect/reconnect issue and the issue with the cell standby using a lot of battery.
The phone is rooted with the stock ROM.
geiswiz said:
I got my AT&T Galaxy S3 on Saturday and have seen this issue a couple of times now. The issue is that sometimes the screen will not lock after the time I have set (30 seconds). Also, the touch key lights stay on forever until I lock the phone. When I unlock it the touch key lights stay on and the screen doesn't lock. The only way I've found to fix it is a reboot. I first noticed this when I received a text. I use goSMS and have it set to turn the screen on for 10 seconds when a text is received.
Has anyone else noticed this issue or know how to resolve it?
I'm also having the wifi disconnect/reconnect issue and the issue with the cell standby using a lot of battery.
The phone is rooted with the stock ROM.
Click to expand...
Click to collapse
Yep, I am having the same issue.
http://forum.xda-developers.com/showthread.php?t=1761027
kirbo20 said:
Yep, I am having the same issue.
http://forum.xda-developers.com/showthread.php?t=1761027
Click to expand...
Click to collapse
Hmm, I did turn off the wifi power save mode using *#0011* because of wifi disconnect issues. I went in and turned it back on and rebooted the phone. I'll see if I still get the screen lock issue.

Question [Solved] Bootloop noticing after MIUI 14 Update

Firstly I wanted to clarify one thing that my phone worked okay after the update. I didn't realise it has updated until after a boot loop.
Just FYI The camera in my phone have been crashing randomly when taking pics and the pics weren't having the full resolution. It was 1280x720. This wasn't an issue for me and I ignored it for like 3-4 months.
So my redmi note 10 have had some random reboot issues lately which i didn't give much attention to. It wasn't frequent just rare random reboots. Few days back I noticed my phone rebooting while in use and it started to loop for a few times and when it loaded into lockscreen right after unlocking, the power button started to press automatically triggering the power option screen and then the emergency calls as well. It stopped after a few taps on the power button.
A day or two later it rebooted once again while the recorder was on and and this time it boot looped a few times and showed the lockscreen and crashed booting back once again. A few tries after that it booted up and I was able to use it for another day.
The very next day, it did the same. Started to boot and loop once again. But this time when the battery is sufficient enough or the phones cool and haven't been used for a while, it boots into lockscreen but freezes and crashes. At one occasion, it stayed just a few more seconds long enough to open the passcode screen but crashes before I could type anything. Then it loops once again and before even reaching the lockscreen, boots back into MI Android Powered screen right after the three dots blinking page. And randomly it boots into lockscreen as well. But once the battery is down or the phone is heated enough, it barely goes into lockscreen.
Booting into safe mode also shows the same. It sometimes boots into lockscreen but doesn't show the 'safe mode' text in the bottom.
Right now when I had kept my phone off for a while it booted into lockscreen twice and the screen dims immediately before freezing and crashing.
The third time it just went back to the MI Android powered logo right after the three dots blinking screen.
Guys please let me know do you think this is a hardware issue or a corrupt software update?
I know software update issue can cause bootloop but does it reach till the lockscreen? My phone consistently gets into the lockscreen when the battery is sufficient or the phones cool enough.
What last update did you perform?
carlos974 said:
What last update did you perform?
Click to expand...
Click to collapse
MIUI 14 which i didn't even realise until I checked the settings app one day after a boot issue
What version do you have?
For me see screenshot, works fine!
Backup your data and clean flash with Mi Flash Tool, you can then exclude any software problem
This issue have been resolved.
The issue was the CPU couldn't handle the heat once the device turned on and would reboot right after reaching the lockscreen and loops.
Thank you for all your suggestions, though.
Dheerajvirgo said:
This issue have been resolved.
The issue was the CPU couldn't handle the heat once the device turned on and would reboot right after reaching the lockscreen and loops.
Thank you for all your suggestions, though.
Click to expand...
Click to collapse
May I know how did you fixed the issue? I'm stock with same situation as you. Did you change any hardware?
Hey, my mi 10 5g has similar symptoms - random restarts + random switch on power button without pressing it...
all this came after upgrade from miui 13 to 14..I use this phone for 1,5 yr with no problems...
Phone get hotter also...
Is it related to bug?

Categories

Resources