[Q] Display shaking and dead - Atrix 4G Q&A, Help & Troubleshooting

Hello people,
I flash the ROM "CM 10.1 (Android 4.2) for Atrix" with the new kernel today and at the beginning everything worked fine.
But after a few minutes setting up the phone, the screen started shaking a moment until the display turn off (turn off but the phone is still working as if the touch also responds and physical keys are lit). When locking and unlocking the phone, the screen returns to normal.
I realized that the longer I leave it off, the longer it takes to give this bug, after turn on the screen again.
The brightness is at maximum and the phone is not too hot.
At least the phone stopped rebooting but play or do anything else is impossible (I can only make calls) because of this bug.
Any idea why this is happening?

Related

[Q] Unsolvable Problem - Display stays on / awake

Hi all,
I'm having a problem with my sgs2 that I'm unable to solve.
The problem is that sometimes, not always, my phone does not enter sleep by itself. Infact it doesn't lock itself either.
Also, again sometimes, if I have a missed call alert or text the display lights up but then stays lit sat at the lock screen.
I've done some testing. I have tried different roms and tried the stock Samsung tom without modifying any settings and the problem remains.
If the phone is in my pocket then it can be a while before I notice. Today this happened for about an hour before I checked my phone. The phone was hot and the battery level had significantly dropped.
I've also noticed that with sound and vibrate switched off, sometimes when receiving a call the phone vibrates for 1/10 of a second. Everytime this has occurred the screen has stayed on after lighting up for the call.
I have wiped the user area on my phone but note this did not delete my music and pictures. Is this correct?
Any ideas? I'm really stumped and it's ruining the phone for me.
Thanks.
To see what apps/processes are causing the device to wakeup from deep sleep download and install Better Battery Stats and see under Partial Wakelocks.
http://forum.xda-developers.com/showthread.php?t=1179809
Regards.

[Q] Problem when my phone is recovering from Sleep mode

Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service

Screen trouble on cm 10.1

Hello.
Got a problem with my i9100g with CyanogenMod 10.1 nightly (04/06 i believe) installed. I was using this ROM for 1-2 days, and now the display stopped working. The thing is, the sensor is still enabled, so if i reboot the device, i can unlock it by swiping the lock by memory, and the phone responds with vibrating. The buttons' lights are working, and the reboot/battery pulling off does not help. I cant even get to recovery/download mode, since the display doesnt show anything.
add: even the Samsung logo does not appear when i turn the phone on.

[Q] Unusual S3 lock screen problem

Hi all,
I have a Samsung Galaxy S3 GT-I9305T rooted and running Android 4.3 with Touchwizz.
The problem I am having is that the screen will not turn off and pressing the power button will not lock the phone. Holding the power button will bring up the device options menu (power off, restart etc) indicating that the button itself is still functioning.
Restarting the device will boot to the lock screen, however the screen still wont turn off and after unlocking the phone once, you can no longer lock the phone.
In the phones settings, under battery it shows that it doesn't even register the screen as being on or the phone being awake (see image) however the phone is still completely functional aside from the issues stated above.
This problem occurred after accidentally dialling emergency services from the lock screen while watching a video on my computer and absent mindedly spinning my phone in my fingers. As soon as I saw it was dialling I cancelled the call and took the battery out. When I started the phone I noticed the screen wouldn't turn off and the phone wouldn't lock.
Hoping I wont have to do a factory reset, if anyone has any ideas or suggestions, they'd be greatly appreciated.
Thanks
Have same problem with my Alcatel Onetouch Fierce 2. Fairly certain it's from this Kingroot in my case. However I don't know enough to prove this. I started using apps to lock the screen for me but they started not working as well.

Telephone is turning screen backlight off when under sun

I have a Xiaomi Redmi Note 9S which has the following behaviour: it works normally until the moment it goes under the sun, then (apparently only) the backlight of the screen is turned off and never turns on again until I restart the smartphone, where it works normally until the very moment it "detects" a bright light like under the sun, then the screen goes black. When this happens, sometimes you can still see the shape of what was on screen, but most times it only goes totally black.
When the screen is black, the telephone keeps working normally (music keeps being played, receives calls, vibration responses keep working, etc...(confirmed it using scrcpy and all is working normally)), only that the backlight is turned off and it keeps totally black. During the night, i.e. with artificial light, the telephone works normally (I was able to replicate the error using a strong flashlight above the telephone, the screen also went black the very moment I turned it on).
What I tried to resolve: restarted many times, disabled every auto brightness (also one that I think is a Xiaomi MIUI only, sunlight detector, something like this) settings that are in the configuration menu, restarted using vol up + power button. Factory reseted the smartphone. Disabled pocket mode before and after factory reset.
Any idea how to proceed? What is killing me is that it seem to be a software issue, like, why the screen don't turn on back after a while, but every time you restart it, or why the phone works all night long (i.e. there no strong light on it)?
How to capture the telephone log (logcat perhaps?) and be sure of what is the exact event that is disabling screen? Maybe I can manipulate it to prevent from happening, or to make screen goes back to normal after a while, as I work as a software developer.

Categories

Resources