Just created a pre-rooted rom using nordic combined 23.5.A.0.570_R11D and flashed (locked bootloader method). But I have a couple of issues. One is that a few seconds after the phone boots up the screen goes blank and the only way to get a display again is to press the power button for a few seconds which makes the power menu and the home button appear. I'm then able to press the home button. Only seems to happen after reboot. Anyone else seen this? I didn't for one of the UK based roms as I was worried about bloatware / customisations by Vodafone or Virgin Mobile.
The other issue is with the alarm clock - when the alarm goes off the screen comes on but only shows the background wallpaper. Only way to stop the alarm is to hold power button to get power menu and reboot. I've managed to get around this by removing the 20.1.A.0.12 clock app that came with the rom and installing a 20.0.A.0.28 version from KK.
Hmm after another reboot after repairing the alarm clock with the KitKat version the blank screen's not appearing anymore so perhaps related.
Its hardware problem your screen needs to be replaced same happened on my Z3 D6603 and hopefully the warranty saved me
I flashed 4.4.4 then 5.0.2 but same problem so its not a software issue.
I'm facing the same problem the screen goes blank .Nothing work to fix it .I've flashed the phone with lolipop it goes back normal but after few hours it goes blank again.Any idea guys ?
XMoDuLeSx said:
Its hardware problem your screen needs to be replaced same happened on my Z3 D6603 and hopefully the warranty saved me
I flashed 4.4.4 then 5.0.2 but same problem so its not a software issue.
Click to expand...
Click to collapse
That's what I thought originally as it had just come back from repair after having the screen fixed but I've not had a problem since removing the clock apk.
Hi all,
I'm having this same issue. I've just updated my D5803 to Marshmallow 6.0.1, build 23.5.A.0.570. Ever since the update, whenever I reboot the phone, it shows a black screen, and I have to press and hold the power button to get the home screen icon to show. And when my alarm goes off, just the wallpaper shows. If I press and hold the power button, I can get back to the home screen, but there is no way to turn the alarm off, I have to reboot the phone - not so fun when I just want to hit snooze!
I find it hard to believe no one else has had this issue before this build was officially released? I'm considering going back to the previous version
Edit: Well, this is interesting. If I take the phone out of its case the alarm works fine, put it back in the case, doesn't work. Take it out, it works. Put it in, doesn't work.
Edit 2: So, I reverted to Lollipop 5.1.1 and the alarm and phone worked perfectly. Updated again to Marshmallow - same problems, black screen and alarm not working while in the case, but alarm works when not in the case. Seems pretty definitive to me that it's a Marshmallow problem!
Bug is still present on .575 update. The strange ting is, on my phone when I disable the smart cover(Settings -> Sound & notification -> Notification access) it stays off, and then the phone is working fine. On my colleagues phone's it's switches itself back on after a call. I have no idea why this is not happening on my phone. Can't find any relevant setting differences.
YoMarK said:
Bug is still present on .575 update.
Click to expand...
Click to collapse
Wonderful
Related
So I Wiped Then Flashed from CyangenMod 3.6.8.1 to 3.9.7 And went fast and smooth boot slow but expected due to flash .... apps still fully functioned except for power manager full it was force closed at start so uninstalled app and re-installed app ran perfectly fine..... all other process that I had done seem to be working flawlessly ....my main issue as of this moment is something I havent seen before....its when my phone is on standby at this point if my phone is closed and I hit home or menu my screen does not turn on but I can here my selections and my buttons light up so I have to slide my phone open then place it back into standby using power button to then hit home or menu so that my screen turns on .... this is the same to turn on phone if its closed screen is just a black light screen so it must be slid open to see anything on the screen such as the T-mobile G1 bootloader etc.......
anyone know what maybe the problem here?
I can provide a device log to anyone that maybe able to assit me
bump so no one has anyclue as to away to attempt to fix this issue? The problem is that the screen only comes on if I slide the phone open but when slid closed hiting menu or home the display does not come on but you can tell that the phone thinks its on due to the fact and can here my desktop shortcuts click as if I was switching from 1 to another ......... anyone?
Hi guys,
I recently got my Xperia Z back from repair. I had it in because when I pressed the power button to unlock it, sometimes the screen would stay black and I wouldn't be able to see anything, but I could still use the touchscreen.
So I got my phone back with a new LCD screen and it's been a week now and it hasn't had that problem at all, but I'm having another problem.
My phone is randomly controlling itself. When I unlock it, every once and a while it starts pressing all the buttons on the screen. Opening up the task manager, swiping left and right, opening up the camera, etc. Just going completely haywire.
So to fix it, I tried a factory reset, but that didn't work. Then I got a new update for android, and for about a day it worked perfectly but now it's back at it again and controlling itself, pressing all the buttons etc. I had an alarm set this morning and I couldn't even turn it off because of it.
It's completely stock, I haven't even tried flashing or rooting or anything like that, and I'm running Android 4.4.4. Model number is C6603.
Anyone know what could be causing the problem?
Wing126 said:
Hi guys,
I recently got my Xperia Z back from repair. I had it in because when I pressed the power button to unlock it, sometimes the screen would stay black and I wouldn't be able to see anything, but I could still use the touchscreen.
So I got my phone back with a new LCD screen and it's been a week now and it hasn't had that problem at all, but I'm having another problem.
My phone is randomly controlling itself. When I unlock it, every once and a while it starts pressing all the buttons on the screen. Opening up the task manager, swiping left and right, opening up the camera, etc. Just going completely haywire.
So to fix it, I tried a factory reset, but that didn't work. Then I got a new update for android, and for about a day it worked perfectly but now it's back at it again and controlling itself, pressing all the buttons etc. I had an alarm set this morning and I couldn't even turn it off because of it.
It's completely stock, I haven't even tried flashing or rooting or anything like that, and I'm running Android 4.4.4. Model number is C6603.
Anyone know what could be causing the problem?
Click to expand...
Click to collapse
there is some issue with touch calibration or some issue with the digitizer.
androidtweaker1 said:
there is some issue with touch calibration or some issue with the digitizer.
Click to expand...
Click to collapse
Well it happens before I even touch anything on the screen, so would that point to the problem being the digitizer?
I can't tell if this issue is with the specific ROM I'm using, or if it's just a Lollipop issue in general. During phone calls, the screen goes black (as it should) when I bring the phone to my ear, but now with Lollipop ROMs, most of the time when I pull the phone away, the screen stays black instead of coming back on. Normally, the screen would illuminate when I pull the phone away, but now it doesn't always work correctly. This is particularly annoying at the end of a call when I would normally touch 'end call', but now I have to wait for the caller on the other end to hang up before the screen comes on. Anybody else notice this?
I'm running gruesomewolf's GPE version 1 and I noticed it. I can usually just press the power button and the screen comes back on though.
A workaround
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Abdou.rk said:
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Click to expand...
Click to collapse
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
One more solution
coal686 said:
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
Click to expand...
Click to collapse
You can also enable DoubleTap2Wake by using a custom kernel.
Same problem on TMo m7
Last week I upgraded to Android 5.0.2 on my TMo HTC One m7.
Since then when I remove the device from next to my head during a phone call the screen stays black.
This means I cannot use a keypad to navigate a phone menu or to enter a PIN.
I can tap the power button to re-awaken the screen but it takes several seconds to come back - and sometimes stays dark.
This is a mild nuisance if simply trying to end a call but is a major issue if I'm trying to use an IVR (this device is, after all, a PHONE!)
I have run the HTC Function test on the phone and the P-Sensor test runs fine.
This is happening on MRA58R, stock, non rooted and rooted.
This happened on average two times a day. The screen became black when I exited out of an app, Audible this time but I had it happen to other apps also. Touches still registered, the notification center still worked, but I wasn't able to enter the homescreen via the home button, or settings through the notification center. I could bring up the power menu and shut down normally. Rebooting fixed it but it comes back.
I didn't have this problem on MRA58K. I thought it was a problem with root so I flashed my phone back to complete stock just today and the problem persists.
I can't post any images, but I uploaded screenshots to imgur. /a/tpx44
Hi guys
Just a quick one. Got a strange issue with the screen on my note 8 and just seeing if anyone has had the same issue or any idea on a fix.
Last week updated to the 9.0 beta and all seemed to be going well with no notable issues just a bit of lag here and there. However last night I turned my phone off and when I came to turn it back on this morning it started to boot as normal I entered my password successfully and it started to boot. As soon as the password registered and the unlocking pad lock appears it quickly shifts to the bottom right hand corner instead of the centre as normal. The phone continues to boot and from then on the screen just goes black and is unresponsive. The handset is on cause people can still ring, notifications still get received and all the hardware buttons make noise as if they are working. The screen will just not turn on. If I try doing a soft reboot with the power and volume down I can start the phone and the Samsung logo comes up as normal and the pin screen as normal but as soon as I enter my pin the same issue happens. If I hold the power button on its own to turn off the phone the multi menu (reboot, power off, emergency) all briefly appear but are enlarged and sitting on the right of the screen.
Any ideas guys, cheers.
Try reinstalling Oreo back onto it. It could be an issue with the Beta Version of Pie that you installed on your device.
The beta software is intended for this very purpose, you found a problem, then you report it to the releaser to be fixed, the creators of the software are the ones that will evaluate and improve the software, you see, it did not work for you, just try to reinstall it, if the issue persists, provide feedback to samsung, and flash a stable firmware
Possibly this bug Pie Beta + Secure Startup + WQHD = Black Screen?
It happened to me too. I installed over my existing UAE firmware with Indian one then the one ui update. After reboot got the same blank screen issue. I then did a factory reset and everything is back to normal for the last couple of days with improved battery life probably due to the reason that many region specific Samsung app like Samsung pay doesn't work.
So had a bit more of a play when I got chance and I managed to resolve the issue. Still being hit with the same problems for some reason I tried unlocking the phone again but sideways (don't ask not sure why) and the screen unlocked. From then on phone worked completely normal until next reboot. Same thing every time until I hold phone on its side and unlock with the fingerprint reader.
I've since reverted back to 8.0 and sent feedback over. I'm gonna try testing again weekend see if I have same luck.
Cheers for the replies guys, hope anyone else has this issue the comes across this.
you must disable secure start up
I had the same issue after updating to beta 1 with secure boot enabled. I wiped the phone and it started as it should, since I couldn't unlock the phone even with fingerprint. I noticed that the screen was only showing for few seconds the 1/4 of the image (unlock sim with PIN).