Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Samsung Galaxy S5 blinking yellow screen

Hello

 

I have a problem with my samsung galaxy S5, The problem is when i turn it on (or wake it up) it screen flashes yellow and then goes black, stragely the screen still reacts to me touching it. But ofcourse, i cant do anything cause i cant see anything. Anyone has the same problem and got it fixed? 

Link to comment
Share on other sites

Link to post
Share on other sites

Hmm thats a new one. I have an S5 that I work with and the biggest issue I have had with it really was the fact that the charger flap broke off so easily. The rest was easily fixable software issues. That sounds like your display isn't properly connected or has been damaged. Has the device taken any falls or damage recently? A video of the devices symptoms might help a bit 

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

I think i found out the issue myself

Í went to developer options and forced it to use 2d GPU acceleration or something like that

after a bit of testing it seems to work.

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Not-Miepje said:

I think i found out the issue myself

Í went to developer options and forced it to use 2d GPU acceleration or something like that

after a bit of testing it seems to work.

If that helped then the GPU on the SoC is likely going through failure, I would take time to consider a new device as on a phone, GPU failure is non repairable

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

I think it isnt faling, but when i tried doing some things in the dev options, i might have unchecked the box for 2d GPU acceleration. Because it now works perfectly fine!

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, Not-Miepje said:

I think i found out the issue myself

Í went to developer options and forced it to use 2d GPU acceleration or something like that

after a bit of testing it seems to work.

wait did you enable Force GPU rendering where the GPU will render 2D graphics rather than the CPU? If so then I have no clue what could be causing it

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Not-Miepje said:

I think it isnt faling, but when i tried doing some things in the dev options, i might have unchecked the box for 2d GPU acceleration. Because it now works perfectly fine!

That box is by default unchecked, thats how it is on my S5

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

Well

my phone is in dutch so i dont know the englisgh word but dutch = GPU weergave forceren that roughy translates to Force GPU view

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Not-Miepje said:

Well

my phone is in dutch so i dont know the englisgh word but dutch = GPU weergave forceren that roughy translates to Force GPU view

That sounds about right. On my device that box is unchecked by default and it works perfectly. I see no issue in leaving it checked so if it works it works, but something is definitely wrong so I reiterate, ya might want to look into the possibility of a new device. But for all I know it could be a simple kernel issue that, with this fix, wont harm the device. But its hard to tell. Again if it works it works

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

20 hours ago, Vengeance1020 said:

That sounds about right. On my device that box is unchecked by default and it works perfectly. I see no issue in leaving it checked so if it works it works, but something is definitely wrong so I reiterate, ya might want to look into the possibility of a new device. But for all I know it could be a simple kernel issue that, with this fix, wont harm the device. But its hard to tell. Again if it works it works

Ok, It worked for a day.

A DAY

It isnt working anymore.

Link to comment
Share on other sites

Link to post
Share on other sites

11 hours ago, Not-Miepje said:

Ok, It worked for a day.

A DAY

It isnt working anymore.

Have you rooted the device before and if so what, if any, modifications did you make?

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

12 hours ago, Vengeance1020 said:

Have you rooted the device before and if so what, if any, modifications did you make?

None

Link to comment
Share on other sites

Link to post
Share on other sites

On 10/31/2017 at 8:08 AM, Not-Miepje said:

None

hmm, then some sort of hardware issue or possibly and issue with the kernel (unlikely but possible). Maybe try a factory reset from recovery? IF that doesnt work then having it repaired might be a good idea, but I cant say whats damaged

Main system "Kethlon":

Core i7 3820 - Intel Desktop Board DX79TO - 32GB 1600MHz DDR3 RAM Dual channel - EVGA GTX 1050 Ti SSC - EVGA 550 B3 - PNY 120GB SSD (boot),WD Blue 1TB (Mass Storage)

See profile for full specs

 

Primary Laptop "Vengeance":

HP HDX16 1370US - Intel Core2Duo P8700 - 4GB DDR2 800MHz RAM Samsung - HGST 1TB 7200RPM (Windows 7, Linux, MacOS 10.11.6) - Nvidia GT 130M 1GB DDR2

 

Downed Laptop "Xarasky":

MacBookPro3,1 - Core2Duo T7700 - 4GB DDR2 RAM 667MHz - Nvidia 8600M GT 256MB VRAM - 640GB HDD (MacOS and Windows)

 

Testing laptop #1 "Leonard":

HP 15 F387WM - AMD A8 7410 APU - 8GB DDR3 Samsung RAM 1600MHz - AMD Radeon R5 graphics (1GB VRAM partitioned out of physical RAM) - 500GB WD Blue mobile drive

Link to comment
Share on other sites

Link to post
Share on other sites

On 4-11-2017 at 8:39 PM, Vengeance1020 said:

hmm, then some sort of hardware issue or possibly and issue with the kernel (unlikely but possible). Maybe try a factory reset from recovery? IF that doesnt work then having it repaired might be a good idea, but I cant say whats damaged

Well, A week ago i did a factory reset. It still didnt work. I have decided to just buy a new phone. Thanks for your time. (Btw the new phone is the iPhone 6)

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×