Xiaomi Note 3 Pro 2/16GB
Hi,
i am currently on a nightly cm13 build. before i had the same issue on the snapshot build.
Used also different kernels but with the same results.
Issue is shown in the video below.
https://www.youtube.com/watch?v=HI43XX0WIpY
This happens probably once a day and only when i am waking up the phone from deepsleep with the fingerprint sensor.
The screen keeps being black for a second when this happens. When i turn off the screen and wake it up again, everything is fine.
What do you think, hardware or software issue?
EDIT: Just found out, that it could be potentially a LiveScreen issue on cm13
EDIT2: No, LiveScreen is not the problem
I'm also facing this issue. Are you using any custom kernel?
I'm using the Blaze kernel.
Yes, was using Blaze kernel as well but i tried different others as well.
I am now on Exodus ROM without these issues.
Seems to be a cm bug.
I've had the issue also while charging my phone last night.
CM13 with Redon kernel.
Scared the sh*t out of me...
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
MiripRedmoon said:
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
Click to expand...
Click to collapse
i know its long time ago, but could you repair the device?
screen glitches
same problem, flickering and mistyping too. Please anyone resolve, this has happened after the latest update
I had this issue, rom and kernel reinstall solved the problem. Maybe something is cached/crashed or both (the phone acted weird other ways too, random apps crashed and so on), before reinstall wipe cache, dalvik, data and system, then install the latest versions of the rom and kernel you want to use. Don't forget to flash firmware.
Since I did this everything is fine.
Related
hey folks,
i have encountered an annoying problem that has made using the s2 quite an unpleasant experience recently.
I bought my s2 about 4 months ago. after 2 weeks or so i switched to miui (galnet) and have stuck to miui ever since. later i switched to langthangs releases as well as siyahs kernels (loving both, major props to them).
around mid of december, my phone suddenly started to crash. up till then i had a couple of freezes here n there, maybe once or twice a months. but since then, even though i did not change anything, my phone has been crashing more often, like 5-10 times a week. updating kernel and rom didnt help.
i experience two types of crashes:
a) freeze: phone just stops working. i have to take out the battery to reboot
b) reboots: phone just reboots out of the blue. sometimes it reboots 3-4 times in a row, like after the first reboot the phone does nothing for 2-3 minutes, then reboots again and so on
i am not sure if that helps, but most of the time the freezes occur while using the internet, the market and playing games. reboots occur randomly, even if the phone is not used at all.
i haven't done any overclocking, just undervolting using voltage control. but i had been using the reduced voltages for weeks, long before the crashes started to occur. and yes, i did try switching back to the stock voltages.
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Anyone else having the same experience?
Is there a way to check if -maybe- the ram/rom is defect? If nothing helps, i think i ll have to flash a stock rom and submit a warranty claim
I would go on a limb saying its MIUI's fault. Wich version of Syiah are you using? Try to reflash different version, I found that 2.6.2 is stable. Also the new one 2.6.6 wich I'm currently testing is stable to, other ones were kinda buggy.
Also are you undervolting or UC'ing ?
If all else fails flash different ROM, after testing many of them I found the latest Criskelo to be stable as a rock.
The only way to really tell is to flash back to a stock rom and see if the freezes/reboots still occur...
Sent from my GT-I9100 using Tapatalk
well, i have tried different roms. and yeah, i am undervolting and underclocking (200-1000).
but isnt it strange? i have been using miui for months without any problems, and baaam ... suddenly the phone starts crashing? i mean at the time the freezes and reboots started to occur, i had been using the same system (kernel,rom,setting,apps) for weeks without any problems.
i ll try going back to stock. if that doesnt help, ill send it in.
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
dabrain23 said:
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
Click to expand...
Click to collapse
Yep, hence you flashed original firmware the dredded(by some) yellow triangle will dissapear.
It will reapear as soon as you root your device.
that last sentence was supposed to be "if i flash stock via odin ..."
ok. ill try that and report back.
BUT
if flashing a stock rom helps, the problems much likely lies with the custom rom. but if so, why did they work perfectly fine until recently?
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Logic says that is the answer .
jje
u think so?
the phone just slipped out of my hand a couple of times, but it never fell on the floor (lets say 30cm or more).
and why would sth like that cause freezes like that? i mean my sisters ace has a totally shattered glass and its still working perfectly fine.
anyway, backing up all my stuff and trying a stock rom tmr
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Seems like your system files might be corrupted. Wipe system partition from fastboot or cwm then reflash your rom. Any time I had weird stuff happen on a rom, I wipe the system then it goes away. Hope this helps you get rid of this issue. Good luck!
Sent from my MB860 on CM7.2.0 Stable
Doesn't work, just wiped system, cache and dalvik, then flashed rom and sod's still happen.
I have also tried flashing several radios, all with sod's. Any suggestions?
wakelock
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
affiatic said:
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
Click to expand...
Click to collapse
So you've had SODs since you got the phone? Wakelock seems to work, but kills the battery.
For anyone who does NOT have SODs what modem/radio are you using?
Yes had them since I got the phone. Wakelok fixed it for me. Battery life is not horrible. It still last me like 14 hrs moderate use. I have tried radios and everything else I could thing of. Think mine is hardware related. That is why I am sending it in. I was surprised to find out it was still under warranty
I've just noticed that when mine shuts down, it gives a green notification first, then when I try turning the screen it, it reboots.
Unfortunately, my phone is out of warranty, I bought it used
SODs still happen in airplane mode.
Try wakelock and post if that fixes it.
Call Motorola directly. I bought two used. Had the same problem. They replaced them both with new units.
Motorola Android Department
1-800-734-5870
Just don't say anything about buying it used.
Good luck.
As posted above, wake lock works but uses battery.
I live in Canada and am out of warranty, would I still be able to call?
It's worth a try. You have nothing to lose.
Sent from my MB860 using xda premium
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
javinavas said:
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
Click to expand...
Click to collapse
Is there something specific about 35C, and are you sure it is exactly that?
I have installed 2.3.6 Bell and I still get reboots, anyone have a link to stock 2.2.1 Bell SBF that I can try?
sometime 35 sometime 36.. but above that temp.. sod kills me.. under that temp phone runs smooth..
I'm a system enginner but I haven't program in years.. I'm thinking seriously in create just a services to read temp and launch a wake lock when temp reache some level..
I'm pretty sure I will help lot of people but aint sure when i can start doing some work
dancom96 said:
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Click to expand...
Click to collapse
my phone would not actually reboot but in went into SOD (sleep of death) so every time this has happened to me i installed a new kernel or reinstalled the one i had.........always rectified the issue.
Same issue
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
jediknightbrodie said:
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
Click to expand...
Click to collapse
Tried several of them, this seems to happen on stock 2.3.6 as well.
I flashed a stock sbf to return to stock. Still had the sleep of death. Reboots after and during phone calls, and touch screen problems. I believe it is hardware related.
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
MaxPresi said:
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
Click to expand...
Click to collapse
Same problem here,
Try wiping dalvik Cache about 10 times ..it worked for me ...
I also had this problem ...but it got solved becaz I had a backup of good runing rom without SOD
Can you turn the phone on if it shuts down or do you have to remove battery? I had the problem only on Neutrino rom, but I didn't do a clean install so I thought it was that
I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix, with some of them the phone not started.
But I do not have this problem with the new kernel (3.1.10) .. or with CM9 nor the CM 10.1 Epinter. The problem with this kernel is when it heats up very much, the screen tearing.
And no, I do not need to remove the battery ... if I hit once as if I turn on the screen, he turn on himself.
I've tried to save the logcat with the application Catlog and put him to save every 1 line, but not the right ... he save the log a few minutes before turning off.
As the 3.1.10 kernel works, I believe that is not a hardware defect.
My memory is: 0x00EF (0xBEEF)
TegraTevision: A03 prime
Tegraparts: mbr: 1100:100:800
thanks ...
Hi may I ask if you resolved this problem as I have it to. Thanks
lisaamybeth said:
Hi may I ask if you resolved this problem as I have it to. Thanks
Click to expand...
Click to collapse
The post just above yours has a solution... read it.
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
lisaamybeth said:
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
Click to expand...
Click to collapse
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
lisaamybeth said:
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
Click to expand...
Click to collapse
In the post that I replied to, you only stated that you had issues with CM10.1/3.1.10 kernel, which is why my post was worded the way it was. you didn't specify that it was also with GB based ROMs as well. The only thing that makes sense at this point is a board/hardware related issue. As I briefly said in my last post, we all have different board revisions. We all won't see the same results. Thats why you see people talking about having screen tearing issues when others have no issue. I suspect its the same in regards to this issue.
Please see the screenshot of the screen flicker.
This problem tho resolved through a reboot but Is it normal behavior or should I be worried and buy some other phone?
I have been using this phone over a year now. These screen flickers come time to time on my device almost once in a month. Is it a known issue with this device?
Any opinions
Zack208 said:
Please see the screenshot of the screen flicker.
This problem tho resolved through a reboot but Is it normal behavior or should I be worried and buy some other phone?
I have been using this phone over a year now. These screen flickers come time to time on my device almost once in a month. Is it a known issue with this device?
Any opinions
Click to expand...
Click to collapse
I would look at these options first
(1) Rom ( Change roms if it happens it with other roms then rom ok)
(2) Kernel (Change kernel if it does it with other kernels then kernel ok)
(3) Battery (Change battery if does it with other battery then that is not the problem)
(4) Hardware ( Service issue return to repair)
I have seen quite a few post's suggesting a new battery could solve it perhaps that is worth a try
It happened for me, but i solved it with reinstalling with stock ND5 rom with full wipe and then installing boeffla 5.3, no issues till then, i am now on latest beta and still no issues.
Hello,
I got XPERIA Mini Pro a couple weeks ago. It was on stock firmware with android 4.0.4. It's warranty ended a long time ago but the phone was still in a very good shape. I really like trying custom ROMs from different developers as I did on my previous XPERIA X10i. So I chose Unofficial CM11 from LegacyXperia with KitKat for start. I unlocked bootloader without any problems. Flashed kernel with flashtool, then flashed ROM with kernel's build-in recovery. It worked fine although sometimes It hung when I wanted to wake my phone and I had to pull battery out. It happend occasionaly and I though I can live with that. But after a couple days proximity sensor as well as front camera gone. I tried whiping cache, factory reset, pulling battery out for about 20 seconds, flashing ROM again, even flashing stock firmware again. Nothing helped. I did research and it appeared that this is common problem with mango after android 4.2. I think. OK, I thought I can live with that. I returned to CM11 but after a while problem with hungs on wake up started to annoy me. I decided to try the highest cyanogenmod for mango on stable stage of development, not nightly like CM11. It was CM9.1. Again, it worked fine and in fact, it was stable. But after a while I noticed that not only front camera and proximity sensor are gone but ALL OF MY SENSORS died. I tried a couple of things like before (whipe, reset, flash etc.). Tried going back on stock. Tried apps from market which test and reset sensors. Every one I tried said my phone does not support sensors. Accelerometer is crucial for me as I use SleepAsDroid app every day. I flashed CRDROID (based on CM11 but much much more stable) which I use till now. Tried doing research on Internet but I found nothing. Tried hitting my phone and dropping It (that helped a lot of people), tried heating battery by overloading processor (that helped a lot of people too). Nothing helped. Tried repleacing files responsible for sensors with the ones from stock firmware. Now test programs show that I have working light sensor but it does not change it's values at all. I accepted the fact that I won't restore my sensors but I must ask:
Is there anything more I can do? Did I missed something?
Is the only way to fix my problem buying a new motherboard? It appears strict hardware problem, right?
Please help, any suggestion will be much appreciated.
Best regards