I got the following issue which has been confirmed by Samsung Service desk to be occur more often:
After power down (switching of) and start-up the screen stays blind//black. Phone seems to work (LED and sound notifications). Attaching to PC with USB phone is recognized as normal. Hard reset via power and volume down bottom (and home button) seems to work but still screen stays blind. Phone is now on its way for repair. Will keep updated once I got news.
Anyone else here has same problem? Cures? Root-cause?
no one?
I had the problem 4 months ago.
The screen went black a few times but always goes up after 10 minutes of pressing vol down + power button. But after a lot of time doing that, it finally went absolutely black like yours, and yes the phone was working cause I could hear my ringtone, see the led blinking and it vibrated sometimes.
Then they repaired it free of charge even if my knox was 0x1. I don't know if the issue is root related or not. I was rooted and on SuperMan Rom.
Hi thanks, for the reply. Mine is 100% original and being repaired currently. Not sure yet what the cause is but will share it once I got the feedback.
Cheers,
Steven
Update 28/11/2016: According to repair-shop it's the motherboard. Anyone else had issues like this?
Steven13 said:
Update 28/11/2016: According to repair-shop it's the motherboard. Anyone else had issues like this?
Click to expand...
Click to collapse
When I had this issue, they told it was an issue with the motherboard and the lcd panel and they changed both according to the reparation report.
Steven13 said:
Update 28/11/2016: According to repair-shop it's the motherboard. Anyone else had issues like this?
Click to expand...
Click to collapse
Not personally, but have read another one member at least, here having the same problem
Update 6-12: I'll get my phone returned this week. Apperently a faulty motherboard was the cause of this error. Samsung and it's official repair center where negatively in the news this week on a Dutch consumer program. Reason is not having enough OLED replacement screens so consumers are "forced" to buy a new one. [in Dutch: http://kassa.vara.nl/nieuws/reactie...eprocedure-van-beeldschermen-van-smartphones].
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.
Hello!
After locking the phone, it happens that sometimes the power button won't turn on the display.
The button is still working, because it is possible to start the Flashlight (long press power button) or open the camera app (double tap power button, can hear the sound).
I'm using the latest lineageos 14.1 version.
Does anybody how to fix this?
AwildPikachu said:
Hello!
After locking the phone, it happens that sometimes the power button won't turn on the display.
The button is still working, because it is possible to start the Flashlight (long press power button) or open the camera app (double tap power button, can hear the sound).
I'm using the latest lineageos 14.1 version.
Does anybody how to fix this?
Click to expand...
Click to collapse
rajat.arora said:
same thing happen with me from last 3 days. don't know what is the problem. but it wake in 1-2 minutes. .i can listen screen unlock sound. and lock sound but display is black.
Click to expand...
Click to collapse
Faulty display.
Not faulty display. Happened to me with oreo roms, nougat roms are ok.
Also with some themes applied too
rajat.arora said:
same thing happen with me from last 3 days. don't know what is the problem. but it wake in 1-2 minutes. .i can listen screen unlock sound. and lock sound but display is black.
Click to expand...
Click to collapse
I installed the official Oxygen OS and still have the same problem.
Mr.Ak said:
Faulty display.
Click to expand...
Click to collapse
I don't think so, because my display got replaced.
Destrocamil said:
Not faulty display. Happened to me with oreo roms, nougat roms are ok.
Also with some themes applied too
Click to expand...
Click to collapse
You ever thought why everyone else is using Oreo roms without display issues and you can't? Hmm,I see faulty display.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
AwildPikachu said:
I don't think so, because my display got replaced.
Click to expand...
Click to collapse
I'm afraid it is a faulty replacement then.
AwildPikachu said:
Hello!
After locking the phone, it happens that sometimes the power button won't turn on the display.
The button is still working, because it is possible to start the Flashlight (long press power button) or open the camera app (double tap power button, can hear the sound).
I'm using the latest lineageos 14.1 version.
Does anybody how to fix this?
Click to expand...
Click to collapse
As ridiculous as that may sound i think it's a problem with your button, you will have to desolder this and resolder a new one. I used to have the same problem, button didn't work like 2/10 at first, and that rate kept increasing. With use and tear it kept worsening. I bought soldering iron and replaced the button, it now works freakin' great.
Europe link: https ://www. ebay. com /itm/For-OnePlus-One-Replacement-Power-Button-Flex-Cable-OEM/152114356352?epid=685628822&hash=item236ab8e080:g:C20AAOSwLF1YB02h
just remove the spaces and you're ready to go!
If this was any helpful to you please make sure to click the thanks button .
filippos96 said:
As ridiculous as that may sound i think it's a problem with your button, you will have to desolder this and resolder a new one. I used to have the same problem, button didn't work like 2/10 at first, and that rate kept increasing. With use and tear it kept worsening. I bought soldering iron and replaced the button, it now works freakin' great.
Europe link: https ://www. ebay. com /itm/For-OnePlus-One-Replacement-Power-Button-Flex-Cable-OEM/152114356352?epid=685628822&hash=item236ab8e080:g:C20AAOSwLF1YB02h
just remove the spaces and you're ready to go!
If this was any helpful to you please make sure to click the thanks button .
Click to expand...
Click to collapse
Okay that sounds strange. I can give it a try.
Now that i see this Thread again, it's far more likely that your lcd just died or partially did. Although if it turns on sometimes like your state, "that sometimes the power button won't turn on the display" it may be a bad teared down soldering on either the power button on the lcd pcb. Get it to a repair shop and ask for a check, if you don't mine you cant open your back cover and remove the screws so you let the motherboard pcb exposed, with a high quality picture we should be able to see if the power button is the problem or not.
filippos96 said:
Now that i see this Thread again, it's far more likely that your lcd just died or partially did. Although if it turns on sometimes like your state, "that sometimes the power button won't turn on the display" it may be a bad teared down soldering on either the power button on the lcd pcb. Get it to a repair shop and ask for a check, if you don't mine you cant open your back cover and remove the screws so you let the motherboard pcb exposed, with a high quality picture we should be able to see if the power button is the problem or not.
Click to expand...
Click to collapse
The whole display part was replaced in a repair shop.
AwildPikachu said:
The whole display part was replaced in a repair shop.
Click to expand...
Click to collapse
aye, and? Mine was the same, it worsen upon the replacement, and within some days of usage, the flex cable had gotten damaged for good, the oneplus one replacement displays out there are crappy, mostly used, not well maintained, cheap ones, and they are not to be trusted.
filippos96 said:
aye, and? Mine was the same, it worsen upon the replacement, and within some days of usage, the flex cable had gotten damaged for good, the oneplus one replacement displays out there are crappy, mostly used, not well maintained, cheap ones, and they are not to be trusted.
Click to expand...
Click to collapse
I'm using a cheap replacement from ebay that I replaced myself,and I'm yet to see any issues with it.
most lcd have the problem. i got a lcd thrice now from different manufacturers had the same problem for some extent
digitizer works fine but lcd doesn't have good connection
My Nexus was also sometimes not waking with the power button. A custom ROM flash (Nexus4Ever) worked well, but still had the same problem. Probably related to this I would notice that when the phone did wake it was sometimes taking a few seconds to do it.
After some searching I found a solution under the lineageos forums -- search for BUGBASH-230 (can't post url here because this is a guest reply). Basically, you have to copy (copy them, don't move them) all tzapps files found in system/etc to system/vendor. It worked for me. There's no more delay in waking up and the problem has been gone for a week now. Before the fix it was occurring at least once a day. Try it.
I have same problem with you and this occcurd after change os nougat to Oreo 8.1 on my j7 prime
It's not the display
I have the same issue on my Nexus 7 with 14.1 installed. The mockingbird replies about it being a faulty display or power button are unfounded considering rebooting the device fixes the issue. Only seems to occur when it's been on for a while or has less than 30% battery.
Did anyone ever fix this? I see this on a few versions of Lineage. Disabling the lock screen in System Profiles settings avoids the issue, but then there's no lock screen!
Not The Display, exactly...
Just thought I would throw in my 2 cent observations. I have a Samsung Relay 4G (t699/apexqtmo). It worked flawlessly with its stock software / and official upgrade (I.C.S. & J.B). Once I upgraded to KitKat or Lollipop, the screen backlight would never turn on after waking the device on a single button push. The difference between these versions of android as it relates to waking the device can be found in changes to power management / wake locks code. I am not good enough to figure the ins and outs of this type of programming, but maybe this will give some hacker an idea of how to patch or work around this particular part of the firmware. Thanks!
Just upgraded form stock to LineageOS rooted and all....display wake up worked fine b 4 now i have this problem also it will sometimes eventually wake up but takes forever and many button presses
So, if anyone is till wondering about this, here is the information i believe to fix this bug, that is if anyone can integrate the change into CM KitKat and beyond for our sad old Relay. github.com/TeamApexQ/apexq/issues/24. Any chance this could be implemented through an apk?
Because I really don't want to shell out $$$ for an F(x)tec Pro
Hey Team,
For two weeks I was the proud owner of this phone model - Realme X50 Pro (RMX2075) - European version 12x256.
I woke up this morning (12 Sep 2020) and saw that the phone was turned off.
Before that, before going to bed, he worked and the battery was 100% charged.
At the moment, I cannot enable it by any combination.
Press and hold both Power and Volume Up buttons
Press and hold both Power and Volume Down buttons
Press and hold the Power button only.
The only back screen even during the charging. Just nothing.
Has anyone encountered such a problem?
Please advise what to do.
Thanks.
Never had this issue. Does your phone automatically update overnight? If so it might have tried to update and something disrupted it. Either way, I'd certainly contact realme as it doesn't look hopeful. Sometimes, phones like to switch off when there's too much or too little percent. Like when you run flat a phone it does that. Maybe leave it a day and see if there's still a persisting error.
bictu said:
Never had this issue. Does your phone automatically update overnight? If so it might have tried to update and something disrupted it. Either way, I'd certainly contact realme as it doesn't look hopeful. Sometimes, phones like to switch off when there's too much or too little percent. Like when you run flat a phone it does that. Maybe leave it a day and see if there's still a persisting error.
Click to expand...
Click to collapse
Yeap. The phone does auto-update during the night.
I also think there was a problem during the upgrade or something on the hardware side.
I will contact the service. There will be news, I'll let you know. Perhaps someone in the future will face the same.
Dabodar said:
Yeap. The phone does auto-update during the night.
I also think there was a problem during the upgrade or something on the hardware side.
I will contact the service. There will be news, I'll let you know. Perhaps someone in the future will face the same.
Click to expand...
Click to collapse
I keep auto-update turned off, it takes 5 mins to upgrade so I prefer to be able to upgrade in a controlled environment.
Hopefully realme will sort you out. Doubt it's a widespread issue and it's probably just that one off.