I am having a question.
Recently, my Lenovo k3 note was updated to the marshmallow 6.0 via twrp.
After the update everything works fine and there is no lag or overheating issues.
The problem is that, when the phone wakes from sleep mode it remains​ black screen, until i manually press the power button to get the phone into sleep mode and wake it up again by pressing​ power button.
Does anyone else have this same issue or if it is just a bug of the new update of Official Lenovo.
Related
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
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).
Good day!
I recently re-flashed my Zenfone Go 5 Lite using a offical Asus ROM due to a bootloop issue.
After initial setup, ZenUI launcher says that it's not responding (returns an all-black screen with only status bar accessible). I can get away with it by restarting the phone.
However my main concerns are the following:
- After restart, WiFi doesn't turn on even though the switch toggles
- When I put the phone in sleep mode (locking the phone), it doesn't wake up by pressing the power button neither with the double tap gesture. I had to force restart it by holding the power button for about 10 seconds to access the home screen again
What could be causing this problem? Is it a software issue or a hardware one?
Any help or feedback will be deeply apperciated. Thanks!
I have a Moto G5s plus and am using a Pixel Experience Plus custom rom (latest stable). It's not rooted.
The problem I have is that the phone is working absolutely fine and never freezes while working and goes without lag. Only when I lock it, I sometimes am unable to wake it up with either the fingerprint scanner or power button. It takes a reboot (long pressing power button) for it to work again. This happened on the stock rom also and hence I decided to use a custom rom.
The phone does not overheat during this but does during charging. I don't know if these are related but that's all the info I have.
Hello friends,
My situation:
Out of the blue my phone stopped responding to the wake-up action. Every time I lock it, I have to restart for the screen to turn on again. The power button is working just fine, since I can go to recovery mode and use it to select options there. I even installed a somewhat wrong version of the TWRP recovery that would not boot to the main OS, but the power/lock button would work just fine in recovery, putting the phone to sleep and waking it up. I reverted the instalation after so I could boot to the main OS ( Android 10). I tried reinstalling(from an official image of the rom) the full rom, incluing everything from OS to Bootloader, and could not make the wakeup action work again. Once my phone is on, if I lock it, I have to force a restart to turn the screen on again. I even tried sending a direct command to the OS using adb shell input keyevent KEYCODE_POWER and KEYCODE_WAKEUP to no success. Even tough I made sure other common events like opening the camera (KEYCODE_CAMERA) were working when the screen was on, and I bet it was working when the screen was off too, but it would not wakeup the screen and I would not be able to see the camera view finder.
My phone is a Samsung galaxy A30, model SM-A305G, currently in Android 10.
I think I described the problem good enough, but If anyone have a problem understanding it, just let me know and I try to explain it better.
Can anyone help me out here? I tried a lot of things to not success.
Thanks!
I have the exact problem you described, did you find any solution ?
Shalesh said:
I have the exact problem you described, did you find any solution ?
Click to expand...
Click to collapse
flash official ROM with Odin or with twrp
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Shalesh said:
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Click to expand...
Click to collapse
very strange
I made furher research about the issue and here is what i've found.
Some videos mentioned same problem in similar samsung models and they stated that changing the daughterboard that connected to motherboard via screen flex resolved the issue. Other videos reflowed the connector in the motherboard side of the flex.
Also phone not responding the adb power commands while in sleep but responding fine when awake got me thinking there is a problem with a some kind of awake pin of screen. Probably there is a short or a missconnection in that pin. That's why solutions in the videos work I think.
It is definitelty not a software issue because it happens in every official or custom rom except in twrp (which does not put screen into sleep mode according "mScreenState" info)
It is not a hardware issue related to power button. Power button works perfectly fine in recovery, download mode and when awake.
Its a hardware issue that probably about the connection that sends wake up signal which maybe from motherboard side of the connection or maybe daughterboard side.
Not a real solution but I found a app called touch protector which has an option that you can disable the touch and set screen brightness to 0%, basically means normal off state for the amoled screens.
I set double click of volume down to sleep mode for touch protector. Maybe with some keymap editing someone can set powerbuttons function to not real sleep but touch protector's sleep. This will be best software solution.
In the hardware side if the problem is daughterboard it can be swapped easily but reflowing smd connecters in motherboard could be risky for me and I don't want to open the never opened device for not solving the problem.