[Q]SOLVED! Big problem on all 4.2 roms can't make or receive calls! - HTC Desire S

Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.

My radio is 3831.19.00.110

ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.

paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...

No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.

Also have the same problem on jelly bean fire
Sent from my HTC Desire S

Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!

I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".

sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it

Flashing a new radio did not fix the problem please somebody help!

ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.

Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1

NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.

ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.

Ok will do that now
Sent from my HTC Desire S

NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.

ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2

I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.

sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.

sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?

Related

[Q] Screen won't stay off!

I can't turn my screen off. When I press the power button it goes off for 0.5 to 3 seconds and comes back on. I was using Axura when it first happened, but then I restored an older CM rom and I'm having the same issue. Has anyone else had this problem? I'm sure I don't have to add that it isn't ideal for battery life ..
cavved said:
I can't turn my screen off. When I press the power button it goes off for 0.5 to 3 seconds and comes back on. I was using Axura when it first happened, but then I restored an older CM rom and I'm having the same issue. Has anyone else had this problem? I'm sure I don't have to add that it isn't ideal for battery life ..
Click to expand...
Click to collapse
Are you plugged in when it is happening? If so, have you tried to turn off the "Always stay on" setting?
I had this happen to me. It turns out it was a faulty power button. Its a hardware issue. I had to return my phone because I was still in the 30 day window, if you're outside of that you need to send it in to samsung.
Sent from my Nexus S using XDA Premium App
Thanks for the replies.
Strangely enough the issue disappeared as quickly as it appeared about 6 hours after it began! I tend to agree that it's a hardware problem, but as long as it's not happening constantly I'm going to live with it (due to the fact that as an Australian living in Spain with a NS from the US I don't imagine a warranty claim would be easy).
A hardware problem wouldn't be my first assumption if I was on a custom ROM and/or had lots of apps installed.
If it happens again, I'd get a logcat recorder app or adb logcat session running on the phone and see what exactly it says goes on just before the screen wakes each time.
Oh ok. I tend to assume it's a hardware problem due to the fact that it happened on completely different roms. But the way that bug causing "artifacts" are sometimes left behind when changing roms doesn't give me confidence in that assumption. I really don't understand it.
I'll definitely give the logcat a go if it comes back. Thanks.
hi,
i am bringing back this thread from a few months back because it was the only one i found that showed the same problem.
i installed alogcat and attached a log file here. can anyone see if there's anything in the log that would be a software reason as to why it's waking itself? also, it doesn't shut itself off while this is happening. the screen will stay on indefinitely. i've had the phone for 6 months and this has become a new problem i would say in the last 3 weeks. i don't want to have to send it to samsung for a few weeks.
thanks for any assistance

New issue? On/Off button seam to "flicker"?

Hey ya all
Ive tried to google for this issue but haven't found anything. I got it yesterday evening, about 1-2 hours after OTA update to 2.3.4.
So what happens is when I hit the on/off button to turn of the screen, it sometimes goes black for about half a second and then turns back on. Same when I try to wake it, goes light and then goes dark. So it seams like a dubbleclick almost.
Sometimes I've also got the issue that my Home button just keeps making screen shots, took me a while to figure out thats conected to the power button. How am I supposed to take a screenshot? Could it be a simple hardware issue where the button gets stuck? I've tried to remove the backcover and clean up, but it all seams fine for my untrained eye.
How are you holding the phone when this happens? This same thing happens to me sometimes if I kind of wrap my hand around it when I pick it up. I unconsciously hit the volume button like half a second before I hit the power button, and the volume button wakes the phone & then the power button turns it right back off.
It can happen whatever way Im holding it im afraid, and it has only occured since last night. Lets see if someone else got this after 2.3.4 or if its just a wierd coincidence.
And also, as I said, it seam to bug out my screenshot function.
That's not a coincidence, happens to me as well.
My guess is that's because of the new screenshot feature (hold Power+Home). Can anyone hazard a guess as to how to turn it off?
Well, guess it's a good thing it aint then, hopefully it'll get fixed.
No one else with this issue? It anoyys me alot
I have this issue, but it only happens if I press the button too fast or something. I don't know how to explain.
happens to me too
Randomly enough, just tried the screenshot function and it said saved to Camera folder but it's not there. What app is used to take it? Someone said it was MySketcher but I don't know
I spoke to HTC support sweden today and they didnt seam to be aware of this issue atleast. Keeps happening to me about 30% of the times i hit the button.. I dont think its hardware issue but didnt care to factory reset the phone yet.. Anyone of you with the issue has other than stock rom? Did it only happen after you upgraded to latest firmware? Ive only had it since 2.3.4.
I'm getting this exact same issue since upgrading to 2.3.4. I have a stock ROM too. It's really annoying, press the on/off button and it doesnt always turn it off, it does exactly the same as what the op says.
Also getting it take screen shots when I press the home button.
isak888 said:
Hey ya all
Ive tried to google for this issue but haven't found anything. I got it yesterday evening, about 1-2 hours after OTA update to 2.3.4.
So what happens is when I hit the on/off button to turn of the screen, it sometimes goes black for about half a second and then turns back on. Same when I try to wake it, goes light and then goes dark. So it seams like a dubbleclick almost.
Sometimes I've also got the issue that my Home button just keeps making screen shots, took me a while to figure out thats conected to the power button. How am I supposed to take a screenshot? Could it be a simple hardware issue where the button gets stuck? I've tried to remove the backcover and clean up, but it all seams fine for my untrained eye.
Click to expand...
Click to collapse
well for same issue i got my power button changed...now its fine... i had this issue and was mad... so after change its gud... itz mostly coz of overstressed power button...c ur power button is fine... in recovery also it must b mis-behaving?
Edit : i am on 2.3.4 stock as of now
lalitsehgal21 said:
well for same issue i got my power button changed...now its fine... i had this issue and was mad... so after change its gud... itz mostly coz of overstressed power button...c ur power button is fine... in recovery also it must b mis-behaving?
Edit : i am on 2.3.4 stock as of now
Click to expand...
Click to collapse
Was abit tricky to understand you, well anyway, so you had it repaired then? Id love to avoid that, hate being without the phone. But maybe thats the only solution.
Thanks for your input.
Yea I'm not so sure if this is a software thing. I haven't experienced this during regular use, but I have experienced a double-press effect while in Clockwork Mod. If I press the button on the leftmost part and do it slowly, I can get a double click without actually clicking it twice. Scares the crap out of me when I'm flashing roms and kernels.
So maybe something is up with the power button itself? Too sensitive maybe?
same issue here, was afraid it was my button. first i thought it was crt animations that were causting it. i have to go in to build.prop and turn off power+home screen shots because half the time i hit home it take a screenshot. not sure what's up with the power button.
have the issue on both bulletproof and eaglesblood, both 2.3.4
Happens to me as well and drives me absolutely insane.. The problem is definitely hardware.. I got a replacement back cover under warranty and after two weeks the problem is back just as bad.
To somewhat remedy the screen off/on flicker, i use 'screen off and lock' for long press of search button.. Not the same I know, but at least it doesn't flicker back on.
As for recovery, you can use home/menu for up/down, back for back and search for select.. I find this light years easier than having to ninja push the power button to avoid a double press.
I wish there was some way to fix the damn button tho.. I don't understand how HTC screwed it up so bad.
Sent from my HTC Sensation Z710e using XDA App
Having the same problem. Is the problem with the back cover or the phone itself? I looked at the button underneath the case and it looks bent. I was thinking maybe a tiny piece of paper inside would help, if it does, I'll report back
EDIT: playing with the button with the case off shows no problem. It has to be the way the case interacts with the button
EDIT 2: A piece of paper doesn't completely relieve the problem but does make it much harder to reproduce, and in my opinion, it's much nicer to press now
EDIT 3: Thicker paper=issue solved. I'll send HTC an email about it not reaching the button all the way, maybe they can do a recall on affected backings
Flippy125 said:
Having the same problem. Is the problem with the back cover or the phone itself? I looked at the button underneath the case and it looks bent. I was thinking maybe a tiny piece of paper inside would help, if it does, I'll report back
EDIT: playing with the button with the case off shows no problem. It has to be the way the case interacts with the button
EDIT 2: A piece of paper doesn't completely relieve the problem but does make it much harder to reproduce, and in my opinion, it's much nicer to press now
EDIT 3: Thicker paper=issue solved. I'll send HTC an email about it not reaching the button all the way, maybe they can do a recall on affected backings
Click to expand...
Click to collapse
I dont understand exactly what you did, but id be glad to know!
isak888 said:
I dont understand exactly what you did, but id be glad to know!
Click to expand...
Click to collapse
I ripped off a little piece of paper from a paper cd case about the width of the button inside, I then folded it until I found the perfect thickness and set it on top. I just carefully put the backing back on. It pushes the power button up about double what it was. I'd take pics but all it is is a piece of paper sitting on top XD
Sent from my HTC Sensation 4G using XDA Premium App
Got an email back from HTC saying they'll use the information for "future devices"
Sent from my HTC Sensation 4G using XDA Premium App

Losing touch

sometimes when im typing away in a message on my phone, some parts of the phone turn into resistant areas making me press hard on my phone for a touch response to occur...so the phone turns from a capacitive touch screen, to a resistant one that requires a considerable amount of pressure from my fingers. Why!!! is this because of a rom im using? when i click the sleep button on and off the screen returns to normal, but this is so frustrating when im attempting to type long messages. any answers? thanks!!!
I had that issue once.. I tried calibrating the screen but it didnt help so I did a battery pull and it went back to normal.. Havent had the problem since then but im scared itll show its face again..
hah yeaa aafter posting this i havent had the problem, lol lets hope it doesnt come back!
OP are you using a gingerbread rom? it's a VERY VERY common/known issue in all gingerbread roms from gingerbeast to ARHD. I don't know if there's a fix in the works or if anyone cares to make one but i think everyone just flashes teh screen on/off to get around it.

htc sensation backlight aleays on even when phone is off.

as said above. my 4 soft buttons backlight are always on even when i shut off the phone.
im using arhd 6.8.0. when phone is off, a dim light is shown in the soft buttons. when i first installed the rom its very smooth. i tried hard resetting the phone but it still doesnt fix the problem.
its very annoying as it drains the battery even when phone is off. sometimes the backlight flickers adjusting the intensity of the light. help pls. thanks
rainversion13 said:
as said above. my 4 soft buttons backlight are always on even when i shut off the phone.
im using arhd 6.8.0. when phone is off, a dim light is shown in the soft buttons. when i first installed the rom its very smooth. i tried hard resetting the phone but it still doesnt fix the problem.
its very annoying as it drains the battery even when phone is off. sometimes the backlight flickers adjusting the intensity of the light. help pls. thanks
Click to expand...
Click to collapse
wats yo kernel? n hboot version n status?
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
ashkan-khatar said:
wats yo kernel? n hboot version n status?
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
Click to expand...
Click to collapse
im using sebastianFM kernel and 1.27 hboot. do you think if i backup to official ics, would it fix the problem.
help pls. thanks
up
rainversion13 said:
im using sebastianFM kernel and 1.27 hboot. do you think if i backup to official ics, would it fix the problem.
help pls. thanks
Click to expand...
Click to collapse
actually try a different kernel
see how it goes
but do first a nandroid backup just in case
rzr86 said:
actually try a different kernel
see how it goes
but do first a nandroid backup just in case
Click to expand...
Click to collapse
ok ill try that. but here's the thing. whatever app i use to turn off the backlight of the soft keys. it only dims it to the lowest level and doesnt completely turn it off.
when you look at your phone in a different angle, you can still see a very small light emitting in the soft keys part even when you shut off the phone. i tried reinserting the battery hut it doesnt fix the problem.
rainversion13 said:
ok ill try that. but here's the thing. whatever app i use to turn off the backlight of the soft keys. it only dims it to the lowest level and doesnt completely turn it off.
when you look at your phone in a different angle, you can still see a very small light emitting in the soft keys part even when you shut off the phone. i tried reinserting the battery hut it doesnt fix the problem.
Click to expand...
Click to collapse
Make a backup, do a full wipe in recovery, and reinstall the ROM you want fresh. If the propblem goes away then something is just screwy in your current ROm install and you may just have to set up a fresh install of it.
Skipjacks said:
Make a backup, do a full wipe in recovery, and reinstall the ROM you want fresh. If the propblem goes away then something is just screwy in your current ROm install and you may just have to set up a fresh install of it.
Click to expand...
Click to collapse
i hope your right that its just a rom problem because sometimes out of nowhere, all of a sudden when i shut off the phone, the backlights were completely gone(which is what i want to happen).
I'll post the results later. thanks.
by the way, when i used cpu spy it doesnt turn into deep sleep when the screen is off even if there is no apps running.
i left the phone for 6 hours screen off and charging. and only 8 minutes it turn into deep sleep state. the other remaining comes from my lowest speed which is 384. so im joping its just a rom problem.
rainversion13 said:
by the way, when i used cpu spy it doesnt turn into deep sleep when the screen is off even if there is no apps running.
i left the phone for 6 hours screen off and charging. and only 8 minutes it turn into deep sleep state. the other remaining comes from my lowest speed which is 384. so im joping its just a rom problem.
Click to expand...
Click to collapse
update! i tried installing another rom. it fixes one thing. when the phone is shut off, the backlight is completely gone. but when the phone is in sleep mode, it still has a very dim backlight on the 4 soft buttons. what seems to be the problem?
need help pls. anyone experiencing this same annoying issue?
rainversion13 said:
update! i tried installing another rom. it fixes one thing. when the phone is shut off, the backlight is completely gone. but when the phone is in sleep mode, it still has a very dim backlight on the 4 soft buttons. what seems to be the problem?
need help pls. anyone experiencing this same annoying issue?
Click to expand...
Click to collapse
Wait a minute...when you said the backlight stays on even when you shut off the phone I thought you meant like when you turn the screen off. Do you mean when you physically power off the device?
That's really screwy. If so, something is really REALLY messed up.
Try the following 3 things in this order from easiest to hardest.
1) Remove the SD card. Reboot the phone. See if the problem persists. If it goes away without the SD card, copy your files to a computer, format the SD card, and copy your files back. I give this a 10% chance of working but its quick to test it so why not try?
2) Do a full wipe. Flash a bone stock Sense ROM. Seen if the problem goes away. If it does, wipe again and install whatever you want.
3) Run a full ruu and return to completely stock. If the problem is still there your hardware is broken. If the problem goes away you will have to restart the rooting process. You will have to redo s off, redo superuser, etc. Then flat whatever ROM you want.
Try doing an full ruu back to bone stock. Reroot, and start over with a new ROM. You will have to go through the whole s off process again. But it might fix this. And form the sound of it you have somehow borked things that shouldn't have ever been touched.
Sent from my GT-P5110 using xda app-developers app
Skipjacks said:
Wait a minute...when you said the backlight stays on even when you shut off the phone I thought you meant like when you turn the screen off. Do you mean when you physically power off the device?
That's really screwy. If so, something is really REALLY messed up.
Try the following 3 things in this order from easiest to hardest.
1) Remove the SD card. Reboot the phone. See if the problem persists. If it goes away without the SD card, copy your files to a computer, format the SD card, and copy your files back. I give this a 10% chance of working but its quick to test it so why not try?
2) Do a full wipe. Flash a bone stock Sense ROM. Seen if the problem goes away. If it does, wipe again and install whatever you want.
3) Run a full ruu and return to completely stock. If the problem is still there your hardware is broken. If the problem goes away you will have to restart the rooting process. You will have to redo s off, redo superuser, etc. Then flat whatever ROM you want.
Try doing an full ruu back to bone stock. Reroot, and start over with a new ROM. You will have to go through the whole s off process again. But it might fix this. And form the sound of it you have somehow borked things that shouldn't have ever been touched.
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Well, when the phone is off, the backlight is already gone. So its ok now. The CPU spy also states that when I turn my screen off, it turns into deep sleep. That one is fixed too. But when I charge the phone and let my screen off, it doesn't go into deep sleep but it consumes the least frequency of the processor which is 192mhz I don't know if that is normal.
I think I have a hardware problem since I sent my phone to replace its microphone flex which includes the lights coming from the buttons. I'll try to send it back to the center since it still has warranty.
Thanks. I'll update you.
rainversion13 said:
Well, when the phone is off, the backlight is already gone. So its ok now. The CPU spy also states that when I turn my screen off, it turns into deep sleep. That one is fixed too. But when I charge the phone and let my screen off, it doesn't go into deep sleep but it consumes the least frequency of the processor which is 192mhz I don't know if that is normal.
I think I have a hardware problem since I sent my phone to replace its microphone flex which includes the lights coming from the buttons. I'll try to send it back to the center since it still has warranty.
Thanks. I'll update you.
Click to expand...
Click to collapse
Any update on this issue? My wife's phone has many screen problems, but one of the primary symptoms is that the backlight is almost always on in the lower left corner, even after removing the battery and reinserting it, before booting. When I charge it, the backlight gets brighter and I see dark pixelation across the screen. At times the screen has crapped out completely, and it usually appears dark, has some light flickering, blotching, and vertical lines. I'm wondering whether this is an LCD/backlight issue at all or another hardware issue. Don't want to buy an LCD if that won't fix anything. Some LCD/digitizer assemblies have a mic cable, though, so I'm curious about what you found out about that. Thanks

SOD (sleep of death)

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.

Categories

Resources