Begining from miui v6 till nowadays on miui v7 there is a problem that device stops interact with touches, only sensor buttons works. The problem doesn`t connect with any factors.
To solve this problem you should lock the device, than unlock and after that operation you can use the device until the problem will appear again.
This is a problem for miui v6 android 4.4.4. The solution of it is to change kernel. You can change it to more older miui v6 4.9.2 kernel and the screen will works well, but this solution is not capable to miui v6 and v7 on 5.0.2
This is an often problem and doesn`t have any other solutions.
Pass on this link and confirm the problem, the more votes, the better for all accidents holders mi2s this problem.
http://en.miui.com/thread-176998-1-1.html
To somehow managed to fix this problem?
Related
Hi Guys,
I am using Xolo q700i [only rooted, Stock ROM]
Since yesterday, I am facing a very strange problem. My Orientation Sensor and Accelerometer are not working. That means AutoRotation goes for a toss and not to forget any game.
I found that I could salvage the problem by using Android Sensor Box, then opening up the Orientation Sensor, then going back and opening up the Accelerometer. This somehow solves the problem, but it's just a temporary solution.
The Orientation Sensor and Accelerometer goes for a toss again after few minutes - 20-30 mins is what I've observed.
I have tried factory reset, but the problem persists.
Anyone can suggest any reason and any remedy?
Thanks
Try to Flash Custom Rom or Flash Q700i rom via SP flash tool.....if You have already on that rom flash it again flash tool......if u face the problem again then its hardware issue contact service center (unroot your phone)..
Dude this problem persists a lot on the stock rom(mite be a bug)... nothin to do with Root... Check with a custom rom that worked for me!!!!!
Sent from my Note3 (rom) using XDA Free mobile app
Hi all,
I am having this problem in CM 12.1 , like the screen goes black while a call is initiated.The screen wont turn up untill the call is disconnected.
I tried different nightlies , even the latest one , but problem is still there. my baseband version is DDUHOA1
Does the modem have any role in this issue? Or is it a hardware issue ?
The proximity sensor works fine on stock rom or any other roms that i have installed so far, including cm based other roms like GearCM ,Euphoria. But on official cm 12.1 the issue pops up..
please help..
johnbabu said:
Hi all,
I am having this problem in CM 12.1 , like the screen goes black while a call is initiated.The screen wont turn up untill the call is disconnected.
I tried different nightlies , even the latest one , but problem is still there. my baseband version is DDUHOA1
Does the modem have any role in this issue? Or is it a hardware issue ?
The proximity sensor works fine on stock rom or any other roms that i have installed so far, including cm based other roms like GearCM ,Euphoria. But on official cm 12.1 the issue pops up..
please help..
Click to expand...
Click to collapse
this is due to proximity sensor happens to me all the time if u have xposed installed then download sensor disabler in xposed download section that will stop black screen on calls hope that helps u
ireaper4592 said:
this is due to proximity sensor happens to me all the time if u have xposed installed then download sensor disabler in xposed download section that will stop black screen on calls hope that helps u
Click to expand...
Click to collapse
Thanks for the reply ,
I installed Xposed . and then Sensor Disabler. Turned off Proximity sensor as you said
but no luck . The issue is still there.
I ve seen this adressed but upgrading to Flyme 6 does not solve the problem for me. Proximity sensor works occasionaly then not. With sensor utility it works like 5 times out of ten. I tried all G versions of Flyme 5, Flyme 6, chinese betas, problem still persists.
Does anyone have an idea or had a similiar issue. Thnx
tommyboy7 said:
I ve seen this adressed but upgrading to Flyme 6 does not solve the problem for me. Proximity sensor works occasionaly then not. With sensor utility it works like 5 times out of ten. I tried all G versions of Flyme 5, Flyme 6, chinese betas, problem still persists.
Does anyone have an idea or had a similiar issue. Thnx
Click to expand...
Click to collapse
If you update to new firmwares with clear data ticked then this will not happen, if you update with clear data ticked then Flyme 6 has an option to calibrate the proximity sensor and sccelerometer under the settings app. (Settings>Accessibility if i'm not wrong). Try doing it, if that doesn't help too then it most definitely is a hardware issue.
My phone is gionee f103(not pro) and rooted . For installation of custom rom,I followed the instructions in this guide and installed the zip from TWRP. It installed without any issues. But when I rebooted, the device got stuck in bootloop. I was not able to use either recovery or factory mode. Please tell me , what do i now , please.......
hello friends,
I am using custom rom in which my fingerprint working fine for some days but suddenly some day it disappeared .Unable to found fingerprint option anywhere in my zuk z1 device.I tried clearing credentials and unmarking android device manager etc and tried flashing with another customer roms still no solution at all. I am using lineage os 7.1.2 custom rom currently .if anyone have solution please help me in this.
thank you .
srk2521 said:
hello friends,
I am using custom rom in which my fingerprint working fine for some days but suddenly some day it disappeared .Unable to found fingerprint option anywhere in my zuk z1 device.I tried clearing credentials and unmarking android device manager etc and tried flashing with another customer roms still no solution at all. I am using lineage os 7.1.2 custom rom currently .if anyone have solution please help me in this.
thank you .
Click to expand...
Click to collapse
One possible solution is to flash zui 2.5. If that won't work a hardware fault can be the nearest problem as your problem is known and leads to that.
thanks strongst sir,I tried flashing zui and i am getting add fingerprint option but while doing fingerprint clicks for setting fingerprint lock my sensor not detecting my finger clicks.So i think it might be hardware problem .
srk2521 said:
thanks strongst sir,I tried flashing zui and i am getting add fingerprint option but while doing fingerprint clicks for setting fingerprint lock my sensor not detecting my finger clicks.So i think it might be hardware problem .
Click to expand...
Click to collapse
As I mentioned, the faulty fp hardware a widely known problem of the zuk z1
The global trouble with all nougat firmware
Hi guys. I amn't alone, I met 10-15 users at 4pda with such problem.
We have the bug at all nougat roms by any devs with different trees...
The sleep of death.
Personally I notice it after/during mobile internet using, but I'm not sure. For long time at home(for a week, for example) with WiFi I have no troubles. But if I am anywhere without WiFi and use 3g(don't have LTE in my country), my phone "sleeps" for some times during just one day... It isn't powered off as it's needed 10-15 seconds of button pressing to turn it on at least.
As the ROM and developer has no meaning I guess that here are the errors in the kernel. @fir3walk says that here are many bugs in our nougat tree and perhaps the trouble is involved in last_dmesg... Or some system force stopes, dozes work improperly.
Not many users have this trouble but it exists an a fact. So it would be great to detect an error and try to fix it. Perhaps not in nougat, at least in new Oreo(I haven't tried it yet so no information about this bug there). We have many ROMs, they are updated for some times a week, new roms are rolling out... But the bug stays still.
If someone else has such problem, write here. Perhaps somebody has any ideas and together we will be able to find solution...
So, all the devs who can detect an error, write us... Any tests, information, logs, etc.
P.S. By the way it is impossible to write logs of powering off(deep sleeping) via logcat or another's. If I run the logging I have no "sleepOFdeath".
It is really global trouble so let's try to fix it together.
I'm sorry for your trouble.
Lets start by figuring out which device is in question
I have a 3s prime and never saw this issue.
So do you have a 3s or 3x or 3s prime?
Hello OP, can i ask if you installed that MIUI Ported ROM based in nougat? Because when i installed it (twice) y faced this issue in every rom that i flashed afterwards, then decided to clean-flash miui fastboot rom and the problem was solved.
Maybe that's your problem.
i face it in rr rom but no in dnd rom
Guys did anyone here with the sod, flash global stable/developer in edl mode?
leyD said:
Hello OP, can i ask if you installed that MIUI Ported ROM based in nougat? Because when i installed it (twice) y faced this issue in every rom that i flashed afterwards, then decided to clean-flash miui fastboot rom and the problem was solved.
Maybe that's your problem.
Click to expand...
Click to collapse
Hello. No, I didn't try miui based on nougat.
But other users say that they notice such trouble at miui(7 android) as well.
So it isn't the cause...
Also about my phone:
Redmi 3s, 2/16, 2016030, FPC, aa1 motherboard.
bekcicandrej said:
Guys did anyone here with the sod, flash global stable/developer in edl mode?
Click to expand...
Click to collapse
Will try to flash via miflash, as I faced no problems before this SOD at 7.1.2. Always flashed my phone via twrp.
By the way, guys, my 3s sleeps well on nougat, but it isn't econom in active mod.
For example, I have made a record at our device at 6.0.1 version - 17.5 hours of screen. Nougat isn't so optimized by now... 10-11 as maximum.
Dmytox said:
Will try to flash via miflash, as I faced no problems before this SOD at 7.1.2. Always flashed my phone via twrp.
By the way, guys, my 3s sleeps well on nougat, but it isn't econom in active mod.
For example, I have made a record at our device at 6.0.1 version - 17.5 hours of screen. Nougat isn't so optimized by now... 10-11 as maximum.
Click to expand...
Click to collapse
17.5 h of SOT on what ROM?