Related
I've tried various different ROM images (including the excellent Dr.Gonzo), and I have this problem with all of them.
When I'm using the phone either with the keyboard in or out, the screen just switches off randomly. If I wait a few seconds (possibly the backlight timer length), then it comes back. Mostly... Othertimes I have to wait a lot longer, but it does always come back.
A reboot sometimes fixes it, but not always - does anything survive a reboot or battery removal?
Anybody else seen anything like this? I have seen a lot of threads about the screen staying on, but not off.
Of course, it could be a hardware fault, but because it's intermittent, it's hard to prove.
Mike
same problem
If you shake the phone can you re-produce this problem? I've never not heard of this being affected by software - you might also want to ensure you're not overclocking it.
Nothing is removed when you do a battery removal or reboot, ensure your connections are all tight and make sure the SIM pins are all making contact and the SIM door closes, apart from that it sounds like a possible bad LCD ribbon.
Shaking it doesn't reproduce the problem.
Once the phone has started doing this, it happens everytime you press a key.
Seems more like a memory leak to me since it always seems to happen after a while of web browsing/email use.
So actually, it looks like it might be a hardware fault.
I think it happens when the device gets warm. After a few minutes with the screen on, keyboard lit up, wifi on, the phone gets pretty warm and that's when the screen seems to go black. Leave to cool and all returns to normal.
Mike
Same issue here, but the screen does not acually go black/blank it just seems that the screen backlight does not turn back on from a standby like state, the phone itself functions but just not able to see whats going on on the screen.
(keyboard lights work fine and come on when expected)
Not sure about the heat theory as it happens (to me) most often right after a call, anything over 30-50 seconds and the backlight problem occurs, when it decides to work again is a matter of luck.
As said before because it's intermittent, it's very hard to prove.
Has anyone who has had this issue, fixed it with a hard reset ?
Very strange ... but also getting very annoying now!
i got the same thing. took it back to warranty and they said nothing's wrong with the phone but i still get this.
I experience the same problems.. it happens pretty random, but every time when you hit a key. I have set all timers to never but the problem is still there.
Running Gonzo 1.1 at the moment, upgraded from guava.. but that didn't solve the problem.
It is getting so annoying now that I am about to throw the s710 in the dustbin
I have had the same problem!
I have turn it back to my provider and no problem now.
i have the same problem with my VOX
apparently, i can still receive phone calls, and do whatever i want with the phone,
but the screen just stays black, its like if you have unplugged your monitor
since i dont have a htc center in my town or anywhere else nearby.
does anyone know a way on how to open the phone, change what need to be changed and correct the problem? im all up for testing if that would resolve this annoying problem :s
cheers everyone
there is a dismantling manual somewhere in this forum. search.
i don't think taking it apart would help you because this is not a physical fault that you can locate.
and i learned that mcel is the retail seller of vox in mozambique. they should be able to help you with service. else just send a mail to htc support and they will guide you.
yes, mcel are the retail sellers, but i tried to go there, and there are no specialists on htc's there,
the thing is, i didnt bought my htc from them, so i can't go there and change for another one
but tks anyway
no problem
but do try to contact htc support by email. they might suggest a way.
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
are you trying to say that by desabling the light sensor, the problem might go away?
i would also like to know if it possible to have the baklight on the lowest possible brightness forever, because it seems, on a low brightness the problem might go away
petlof32 said:
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
Click to expand...
Click to collapse
I also have this problem with the lightsensor turned off. And also at (as it seems) random moments.
well, even with the light sensor turned off, the problem persisted.
i got my phone to a repair shop of htc's, and they figured out the problem
my phone is now 100% thankfully, the repair man told that the problem was because of bad or malfunctioned circuits, he exchanged them with new ones, and the problem went away,
dont know wich circuits exactly, and he didnt want to tell me, but i suggest anyone having the same problem to try and do the same
probably its a hardware malfunction with these VOX,
its possible since so many times before i've heard about malfunctioned pieces coming out in large quantities for sale.
anyways, cheers everyone, and good luck Portugal in EURO!
I have the same problem. I just noticed that it usually happens when the phone is warm, so if you need to do something on my phone just... take some ice from fridge and put it on back of your mobile. I cant see any more solutions.
Please someone help us!
Update. Problem Solved
Just thought I'd update this thread I started.
I sent the phone back to my dealer (Grapevine in Poole,UK).
A week later, I got a brand new one back from the HTC repair centre.
So far, so good. Looks like the problem's solved.
Mike
Sam problem here,
i called with HTC and they sent them to there repair centre.
I am sorry to say, but I am not happy with my new phone !
Some serious problems with it.
1. sometimes when I push the powerbutton nothing hapens, and actualy I can see the phone is fuctioning (round button is flashing for new mail). After a few seconds I get the "famous" grey screen. Reboot is the only option.
2. sometimes I wake up and the phone has boot (I guess) somewhere in the night, because I have to give my accescode for the sim.
3. the "broken glass" isue is a problem and happens twice now
Think these are not small problems for a "Pro" phone.
Right now I don't have a riable and solid phone, and I think a pro phone should be that way .
Hope this things are fixed soon.
I wonder if this is a difference in roms or if you should return your touch pro. I've beating the hell out of my phone software wise to see how it will run and i haven't had a single problem yet. I haven't been charging it via the wall charger so maybe that has something to do with it but i doubt it.
Send it back! At least try that once, if you get the same problem again then either you are very unlucky, or there is a problem with all batches. I haven't had either of those problems once and got the phone the day it came out.
I only see one or two people complaining about these issues.
Steve
steveoidm said:
Send it back! At least try that once, if you get the same problem again then either you are very unlucky, or there is a problem with all batches. I haven't had either of those problems once and got the phone the day it came out.
I only see one or two people complaining about these issues.
Steve
Click to expand...
Click to collapse
I am thinking about it, to send it back. But I still hope it is a rom problem, like Bxsteeze said. Flashing another rom could help. Soon that is possible I will try.
If it doesn't help I send it back.(forgive my my English )
TBH i would do it the other way around. If flashing the ROM doesn't help because of a hardware fault and you have flashed another ROM, chances are you may not get the replacement you want.
especially as Olinex haven't finished the SPL Downgrader yet.....
DONT send it back ffs!!
We have just got HardSPL for the thing so you can actually try any ROM you wish, surely its worth the little hassle trying that first?!
I had the same "broken glass" like screen issue only once also when sitting overnight, but it wasn´t charging at all.
I have several other issue´s but it think it´s ROM related, and if it´s not i´m gonna send mine back aswel.
I've had issues 2 and 3 happen to me.
A couple of times now when trying to wake the device from an overnight charge in the morning I get no response, device locked. Soft reset and all is well.
Regarding the broken glass thing, that's definitely a software issue. Its TF3D having a spaz. If you disable it and then re-enable it, all is well.
Check out the issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
and here:
http://forum.xda-developers.com/showthread.php?t=420700
Hey if anyone doesn't want their Raphael. You could give it to me.
hardSPL ? Let the party begin
Problems
Hi,
Four problems i found so far.
First the broken glass effect. When the phone is ringing and i turn it on his screen the ringing stops and the 3dflo breaks. Or the screen turns grey.
Problem 2 After it restarts i get an device.exe issue.
Problem 3 volume of normal calling is very low. In a noisy room it is hard to understand the caller.
Problem 4 During a call several hick-ups. Also when the signal strength is max.
For know. It is a nice smartphone but some things need improvement.
Can I remind people there is an issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
I know a couple of pages got a bit OT about touch sensitive buttons etc but its back on track now. Log your issues in there guys so we can try and help each other better.
Syphon Filter said:
Can I remind people there is an issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
I know a couple of pages got a bit OT about touch sensitive buttons etc but its back on track now. Log your issues in there guys so we can try and help each other better.
Click to expand...
Click to collapse
And dont forget to add the info to the wiki.
My Touch Pro has had the 'wake up' problem (either refuses to without soft reset or shows me frizzed up screen), has frozen on me during basic setup (following a hard reset) and has given me several spontaneous resets.
It also keeps forgetting my wi-fi network exists.
I feel safe in saying that I have a faulty one, so I'm asking for a replacement.
I'm not sure how this is possible, but about once or twice a day, the back button on my S6 is pressed on it's own. It has happened when the device has been on the desk, I see the soft keys light up, the device vibrates like they've been touched and the app I was on went back, all while I was not even touching the device.
It's happened mostly when I'm holding the phone but not even close to touching the buttons, and once it happened and pressed the back button about 10 times in a row while I watched it.
The phone is completely undamaged, perfect condition, never touched water, not dirty at all, buttons are 100% clean. Happens while it's charging or on battery.
Has anyone else experienced this?
(My device was repaired by Samsung for a different issue, motherboard replaced, this only started happening after the repair)
i have, started like yours random. then it started happening more and more so when i was at the store waiting for someone i decided to factory reset ( factory reset twice while at the store) but it got worse. couldn't even get passed initial setup the phone just kept spamming back button so i just kept going back. luckily i already ordered a replacement s6 from tmobile since i was having some other issue with the phone. sadly the replacement s6 took over 7 days to get here. shipped through UPS and got to hawaii then for some reason UPS gave it to USPS for delivery. kinda sad that i ordered screen protectors 2 days after i ordered replacement phone and the screen protectors got here 4 days later through USPS. but other than that my NEW ( we all know its refurbished) galaxy s6 so far has no issues. even the no audio on calls is fixed.
also if you are going to order a replacement, be sure to let them know you have a GALAXY S6 and the date it was released. i say this because the 2 tmobile reps i talked to kept asking questions they say it was for them to determine if my galaxy s6 that was what 2 almost 3 months old at the time was still under warranty
My s6 was showing the same issue with the stuck back button.
It started randomly but than it went crazy and stuck. I wasn't even able to use it.
But 1 factory reset fixed it.
But yesterday the random stuck back button started again when the phone was on my desk and it was really hot (weather was hot as well as the phone). I turned it off for a while and apparently the issue stopped.
I'm not sure it's temperature, firmware, whatever related but I really don't want to factory reset it again.
No solution here, but it is happening to me as well
Solved
Hi i had the same problem aswell , i bought samsung s6 in Pakistan, after the update the back button kept pressing ghostly, i went to local samsung repair shop and the assistant reset something from the setting and then it was fine, i even asked him what you did and how you did? but he said it is secret lol very stupid. i could have post the solution if i know it, but i think it is very easy and something to do with setting. i am sure it is not hard/soft reset. i will post this on other forums to help other people.
thanks
having this problem with my phone too, i cant even get it to stay on the settings screen long enough to back up my stuff
edit: well i think i solved it. i tried clearing the cache, didnt work. then i did a hard reset, didnt work. then i went back and cleared the cache and did a hard reset at the same time and it seems to have worked.
+1 same problem. It happens mainly when the phone is on the move. Funny thing it happened 3-4 times while taking the metro (go figure) with the data on. Usually when I turn off the data, it reduces the amount of back press.
Normal reset doesn't solve the problem. It stops after a while, probably when the phone cools down. I can't seem to reproduce it, but I believe it has something to do with the data on.
I don't really want to factory reset so I'm going to write to samsung directly as the phone is brand new.
i am having same issue too.
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
Did anyone try loading a custom rom and got it fixed ?
I've had that issue with my first one. Took it back ASAP as it was DOA. Got a brand new one 3 days later as they didn't have any in stock. This one doesn't have any problems. Don't worry to mutch about it. Get it exchanged.
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
I have the exact same problem...did anyone contact the manufacturer and got a response on the matter?
I believe it may be an app setting messing with the system settings. My device did it once and wouldnt allow me to use my device. After factory reset it made it worse so i used twrp and wiped everything but my modem and flashed my stock firmware and it stopped and hasnt done it since
Sent from my SM-G925P using Tapatalk
faiding said:
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Hum that's interesting, thanks for your precious input on this.
I did contact Samsung who asked me to do a factory reset. It didn't change anything.
They redirected me to a Samsung office in Paris, not for repair but for a deeper factory reset... (not sure what they are talking about), but I haven't been there since due to lack of time.
However, I didn't experience the problem since the last update FXXU3QOKN so I'm keeping an eye on it.
Following "faiding's" comment, I'll probably pay them a visit for a replacement.
working "workaround"
workaround:
lower the speaker volume to ~75% in all settings (Media, ringtone, system, notifications, etc...)
Whats going on? why is it working?
some posts ago someone (user called "faiding") mentioned something about EMC leak, or at least he meant to, by mentioning a faulty insulation.
with that in mind i did some testing and found out that the closes radiating component it the speaker... and once you lower its emissions even thought the faulty insulation, the EMC leak is sufficiently low and the 'capacity short' is avoided.
Note: depending on how 'faulty' is your insulation (it varies from one phone to another depending on production line assembly) lower the volume until the issue stops accruing.
not full-proof but working
What worked for me is turn power saving on
possible fix
might be a coincidence, but this worked for me:
(I am a new user so i cant post a link but here is what you should do)
1. enter YOUTUBE
2. find this video: "Samsung Galaxy S6 Touch Screen Sensitivity Fix"
worked like magic for me
Repair tech
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
dslayer83 said:
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
Click to expand...
Click to collapse
Hi dslayer83,
I've the same problem with my S6
Could you solved the problem replacing the charging port?
It would be very important to me knowing how to repair the phone because I buyed it abroad. In my country Samsung does not cover warranty.
Up with this thread!
I had an S6 since January.. initially the problem was very random, maybe 1 or 2 times per day, sometimes would go crazy for a while
Then i had some time with no defect at all (a couple of weeks?) without doing nothing
This past week, the phone was feeling like the MENU button (what menu as in this phone there isn't any?) and that was very weird!
Today, it simply went completely crazy, and now is completely unusable... i can't actually swtich it off as the back key is pressed so quickly i don't have the chance of doing nothing!
EDIT: Managed to reboot and wipe cache... now it is useable, but still hits the button from time to time
Update... went unuseable again today.... factory resetting now...
If it works, shall we suspect is something software related?
Update: Not working... it started giving the phantom touches just after the factory reset then suddenly stopped
Worked fine for few hours, then started craza again
Now i have done a wipe and factory reset again, and still unuseable
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.
Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!
leemo89 said:
Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!
Click to expand...
Click to collapse
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.
Atrax2010 said:
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.
Click to expand...
Click to collapse
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!
leemo89 said:
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!
Click to expand...
Click to collapse
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.
Atrax2010 said:
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.
Click to expand...
Click to collapse
Thanks very much, I'll give that a go first!
If it fails where and you are close to me (Melbourne Aus) how would you like a project?
I share with you my personal experience.
The phone is amazing, is very fast, efficient, amazing sound, amazing screen.
I have the same problem with the volume up bottom but in my case it was caused for a fall incident, I took it apart and I discovered there is one flex connector that goes from the mother board and is shared with the volume bottoms, the power- fingerprint sensor, the camera bottom, the lower speaker and the lower microphone.
In fact due to that fall I am having problems with the volume up bottom as I wrote, the lower microphone, the lower speaker and sometimes the fingerprint function does not work.
I think is still worth having the cel phone, I`ll search for the flex to fix it up
I think most of the description Zagreb does of your case can be adjusted to the reality of what is happening, I think is necessary a technical checking of the hardware.
I'M sorry, of course I meant buttons and not bottoms!
Freezing, unresponsive ui and volume buttons not working properly.
I've had this same issue for a few weeks tried hard resets safe mode, etc, nothing helped. So after much frustration searching forums to no avail I set to and tried a deeper investigation into my own device, I accessed the dev options and looked at power hungry services. The most hungry was Xperia home so I stopped it and low and behold my phone hasn't locked up since, still volume buttons are mostly not working but I'm not locked out any more.
Same here,
First randomly reboot, after factory reset randomly system UI failed constantly , very annoying.
Indeed button up volume is not working (properly).
Someone found solution for this? I already purchased a new battery.
@Chernob0g : how you disabled/stopped Xperia Home so I in meantime can use my phone.
Replaced battery, looks better now.
Volume up still not working, but freezing looks solved.