hey XDA's People, and especially HOX owners/users
I started this thread as disscussion about the incoming call touch screen freeze bug, as there's a common problem reported by severel HOX users in different threads out here in XDA, sometimes while receiving a call and the device still ringing the touch screen freezes, not the whole device but only the touch screen, it can be quickly solved but turning the screen on and off quickly. and if you are lucky you can catch the call
but still very annoying bug, reported on almost every rom and kernel here, but though no one have discussed it for a fix, no one knows for sure weather it's a hardware or software problem.
upon my personal experience i believe it's hardware, as i tried most of the rom's out there for HOX, AOSP and Sense (ARHD, VIPER, CM10.1, ICJ, RENOVATE, TRIP'S, INSERTCOIN), and the problem occured with all weather on the short run use or the long run, so it can't be software, knowing that i always full wipe (sys, data , cache, dalvik) before flashing and always flash the boot.img included in the zip i flash, and sometimes went to formatting sd card.
however alot of people didn't experience this bug, so we are back to the important question, Hardware or Software, if we could determine that we may be able to find a fix for it
what's Your opinion ??
lsrume concern
7OOKA said:
hey XDA's People, and especially HOX owners/users
I started this thread as disscussion about the incoming call touch screen freeze bug, as there's a common problem reported by severel HOX users in different threads out here in XDA, sometimes while receiving a call and the device still ringing the touch screen freezes, not the whole device but only the touch screen, it can be quickly solved but turning the screen on and off quickly. and if you are lucky you can catch the call
but still very annoying bug, reported on almost every rom and kernel here, but though no one have discussed it for a fix, no one knows for sure weather it's a hardware or software problem.
upon my personal experience i believe it's hardware, as i tried most of the rom's out there for HOX, AOSP and Sense (ARHD, VIPER, CM10.1, ICJ, RENOVATE, TRIP'S, INSERTCOIN), and the problem occured with all weather on the short run use or the long run, so it can't be software, knowing that i always full wipe (sys, data , cache, dalvik) before flashing and always flash the boot.img included in the zip i flash, and sometimes went to formatting sd card.
however alot of people didn't experience this bug, so we are back to the important question, Hardware or Software, if we could determine that we may be able to find a fix for it
what's Your opinion ??
Click to expand...
Click to collapse
I encounter this problem occasionally - maybe on every 5th or 6th call - since I switched to the ViperX Rom a few months ago.
I don't recall having the problem with the stock Rom so I had assumed it was a ViperX bug.
7OOKA said:
hey XDA's People, and especially HOX owners/users
I started this thread as disscussion about the incoming call touch screen freeze bug, as there's a common problem reported by severel HOX users in different threads out here in XDA, sometimes while receiving a call and the device still ringing the touch screen freezes, not the whole device but only the touch screen, it can be quickly solved but turning the screen on and off quickly. and if you are lucky you can catch the call
but still very annoying bug, reported on almost every rom and kernel here, but though no one have discussed it for a fix, no one knows for sure weather it's a hardware or software problem.
upon my personal experience i believe it's hardware, as i tried most of the rom's out there for HOX, AOSP and Sense (ARHD, VIPER, CM10.1, ICJ, RENOVATE, TRIP'S, INSERTCOIN), and the problem occured with all weather on the short run use or the long run, so it can't be software, knowing that i always full wipe (sys, data , cache, dalvik) before flashing and always flash the boot.img included in the zip i flash, and sometimes went to formatting sd card.
however alot of people didn't experience this bug, so we are back to the important question, Hardware or Software, if we could determine that we may be able to find a fix for it
what's Your opinion ??
Click to expand...
Click to collapse
After a lot of discussions and opinions, it is almost confirmed that kernels with s2w (sweep2wake) implemented, cause this bug..try any kernel without s2w and you'll be fine
Sent from my HTC One X using xda app-developers app
Sadman Khan said:
After a lot of discussions and opinions, it is almost confirmed that kernels with s2w (sweep2wake) implemented, cause this bug..try any kernel without s2w and you'll be fine
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
happened with ARHD running stock kernel
could be really hardware issue but try to format all and flash all again and try another kernel
Haven't had this problem for a while. I disabled s2u (sweep to unlock) and haven't had the problem since.
Also never experienced it on AOSP roms..
One-X-master said:
could be really hardware issue but try to format all and flash all again and try another kernel
Click to expand...
Click to collapse
tried all of that, sometimes it seems gone, but always comes back, not for me only
7OOKA said:
tried all of that, sometimes it seems gone, but always comes back, not for me only
Click to expand...
Click to collapse
Then i guess it is a hardware issue..i never had ot on stock kernel or AOSP :/
Sent from my HTC One X using xda app-developers app
I have been struggling with this for a while. It's not hardware. Stock rom plus kernel didn't have this.
Typically I xm n ncs kernels it happens to me if I keep s2w off,if I keep it on, no problem. But keeping it on cause 2hrs+ of power_key wakelock, so I don't like keeping s2w on. So I had to choose between charging my phone a lot or having incoming call bug.
You can solve it using alexv's kernel. He has 4 types of kernels,old s2w and new s2w, with and without bln. For me the new s2w with bln works best. No more incoming call bug if s2w off, but wakelock still there if s2w is kept on.
Sent from my nexus
It's the touch issue with custom kernel.
The problem is this: Keep the 2 fingers on the screen (while phone off), get somebody to call you and you can't pick it up! There is a problem with s2w when your body (The leg) touch the touchscreen while there is somebody is calling you!
Solution: Keep the phone on ur pocket the other way (screen outside, back touch leg) then you will be fine!
psycho2097 said:
I have been struggling with this for a while. It's not hardware. Stock rom plus kernel didn't have this.
Typically I xm n ncs kernels it happens to me if I keep s2w off,if I keep it on, no problem. But keeping it on cause 2hrs+ of power_key wakelock, so I don't like keeping s2w on. So I had to choose between charging my phone a lot or having incoming call bug.
You can solve it using alexv's kernel. He has 4 types of kernels,old s2w and new s2w, with and without bln. For me the new s2w with bln works best. No more incoming call bug if s2w off, but wakelock still there if s2w is kept on.
Sent from my nexus
Click to expand...
Click to collapse
And trip doesn't have this issue too
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
And trip doesn't have this issue too
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
Oh I tried his tegra 4 kernel too. IMO, its very battery hungry, plus doesnt allow LP OC, so didnt like it dat much....maybe I will try it again.
psycho2097 said:
I have been struggling with this for a while. It's not hardware. Stock rom plus kernel didn't have this.
Typically I xm n ncs kernels it happens to me if I keep s2w off,if I keep it on, no problem. But keeping it on cause 2hrs+ of power_key wakelock, so I don't like keeping s2w on. So I had to choose between charging my phone a lot or having incoming call bug.
You can solve it using alexv's kernel. He has 4 types of kernels,old s2w and new s2w, with and without bln. For me the new s2w with bln works best. No more incoming call bug if s2w off, but wakelock still there if s2w is kept on.
Sent from my nexus
Click to expand...
Click to collapse
let me try to get this straight, on xm and ncx u have it when u turn s2w off, but with alexv happens when s2w is on, am i getting this right?
for me it happened alot with xm and ncx with s2w on, so that's weird
also since when u r using new alexv's, sometimes the problem seems to be gone with new rom or kernel, but after a while it comes back
trongnghia2411 said:
It's the touch issue with custom kernel.
The problem is this: Keep the 2 fingers on the screen (while phone off), get somebody to call you and you can't pick it up! There is a problem with s2w when your body (The leg) touch the touchscreen while there is somebody is calling you!
Solution: Keep the phone on ur pocket the other way (screen outside, back touch leg) then you will be fine!
Click to expand...
Click to collapse
Yeah i forgot to say that i used to do that to solve the problem xD
Sent from my HTC One X using xda app-developers app
7OOKA said:
let me try to get this straight, on xm and ncx u have it when u turn s2w off, but with alexv happens when s2w is on, am i getting this right?
for me it happened alot with xm and ncx with s2w on, so that's weird
also since when u r using new alexv's, sometimes the problem seems to be gone with new rom or kernel, but after a while it comes back
Click to expand...
Click to collapse
Clarifying, I dont like s2w, it causes massive power_key wakelocks on my device. I like to turn s2w off. But doing that causes incoming call bug in xm n ncs kernels. in alexv's kernel, no bug. but even there i have the damn power_key wakelock when s2w is on. I have been using this kernel for around 2-3 weeks, no issues.
psycho2097 said:
Clarifying, I dont like s2w, it causes massive power_key wakelocks on my device. I like to turn s2w off. But doing that causes incoming call bug in xm n ncs kernels. in alexv's kernel, no bug. but even there i have the damn power_key wakelock when s2w is on. I have been using this kernel for around 2-3 weeks, no issues.
Click to expand...
Click to collapse
so weird, cause i had the bug with ncx and xm with s2w on, i even had it with ncx before he added s2w to his kernel
trongnghia2411 said:
It's the touch issue with custom kernel.
The problem is this: Keep the 2 fingers on the screen (while phone off), get somebody to call you and you can't pick it up! There is a problem with s2w when your body (The leg) touch the touchscreen while there is somebody is calling you!
Solution: Keep the phone on ur pocket the other way (screen outside, back touch leg) then you will be fine!
Click to expand...
Click to collapse
seems to be true
I had a problem when the phone took out of my pants pocket. about 10 times per year of use.
Sombody knows why s2w in responsable of so many power_key wakelocks (possible that every time something touches the buttons/screen the power_key send a wakelock, so it can be related the the call touch bug)? This keeps the phone awake a drains a lot of battery.
"It's just a ride!"
alenbernardis said:
Sombody knows why s2w in responsable of so many power_key wakelocks (possible that every time something touches the buttons/screen the power_key send a wakelock, so it can be related the the call touch bug)? This keeps the phone awake a drains a lot of battery.
"It's just a ride!"
Click to expand...
Click to collapse
maybe, but im sure the freeze with incoming calls not 100% related to s2w, as i said before it happened to me with non s2w kernels before, anybody else had it without s2w?
Don't be so quick to blame the custom ROMs/kernels. Just had the same issue today on a totally stock phone, not even unlocked! Came here to see what it can be and found this thread.
Related
Hi. I am experiencing an annoying issue.
The problem exists in both CoreDroid and CM7 with battery drain fix kernel, but I am not sure if that's a software problem.
Every time I boot up the phone, my g-sensor works very well, but, when I turn off the screen and turn back on, the sensor died. Just "halted", the values just being constant.
It seems the accelometer failed to "wake up" after turning off the screen.
Anyone knows why?
Thanks in advance.
Sent via psychic transmittion.
I've had g-sensor problems on all kernels based on the latest HTC kernel source.
Can't say for sure but I think it's something to do with the BMA150 rotation driver.
Going to back to a kernel based on old HTC source and all problems are gone.
Yep, I flashed another kernel and the problem is solved. DEV should have a look on the sensor driver. The kernel with problem seems failed to turn the sensor on again.
Sent via psychic transmittion.
What kernel did you try instead?
I think the devs know about the bug, but not every user is affected by it so I'm not sure if it's a priority to fix it.
I flashed "[CM7]Performance Enhanced...."kernel by hrkfdn.
Then the problem is gone. The stock kernel from CM7 is fine too.
Sent via psychic transmittion.
Hi, I'm having a problem with my Desire, whenever I am phoning someone or recieving a call the phone screen stops working and shuts off, plus none of the buttons work. I have to remove the battery or get the other person to end the call in order to get it working again. The speaker still works though. Any things I should do before I restore. Oh and I am rooted running the latest Acesmod Rom.
Sent from my HTC Desire using XDA App
So you cannot turn on screen by just pressing power button? Turns the screen immediately off when you receive / make call or only when you hold near it your ear?
All the buttons are unresponsive. And no I'm not holding it up against my ear. Thanks for trying to help though.
Sent from my HTC Desire using XDA App
Nevermind I've fixed it. I found a post that said to try blowing between the screen and ear piece. And to my suprise it started working again.
Sent from my HTC Desire using XDA App
Sorry to bring this old thread up again, but I believe I have a similar problem and don't find a solution: sometimes my desire freezes or crashes, I'm not sure, but I can't wake it up from standby and there's no reaction to the buttons either.
I know from my girlfriend that she tried to call me in that state and to her it seems that I'm not picking up, which is why I think that only the screen freezes.
Also when it is not in standby and I get a call, the screen sometimes freezes and I can't get any reaction of it.
In both cases, only removing the battery helps.
I've encountered this problems in 2 custom roms, at first Reflex S 2.1.7 and now Redux2. Here are some specs:
Rom: Redux2-31.08-TEST
Android: 2.3.5 rooted
Recovery: Amon Ra, have to look up the version...
Radio: 32.56.00.32H_5.17.05.23
Kernel: 2.6.35.13-stable [email protected] #1
Screen should be SLCD, but how can I check to be sure?
Stock partition layout, S-On, PVT4, I did not change the h-boot...
sd card: 16gb sandisk: 1 gb ext3 for app2sd+ and dalvik cache, rest fat
To flash redux i wiped data, cache and dalvik cache
Does someone know how I can fix this? Or how I can find out if an app is causing the problem? Or if blowing between screen and earpiece really should solve the problem, why this occurs?
I really love my Desire now that I have som much more space than on stock Froyo, but if it's so unreliable for calling I will have to revert back...
Cpu setting...??
Sent from my MT15i using Tapatalk
taaviu said:
Cpu setting...??
Click to expand...
Click to collapse
For Redux:
ondemand, 245-998, did not change that since flashing. Freezes happened with both lower cpu when screen off (screenstate scaling) turned on and off.
Don't know for Reflex, if it was even possible to change anything I never did, so it was the standard...
lunovis said:
Or if blowing between screen and earpiece really should solve the problem, why this occurs?
Click to expand...
Click to collapse
Maybe a chunk of dirt/filth gets stuck in the groove there and tricks the proximity sensor into thinking the phone is always close to something so it turns off the screen as it's meant to.
As for the issues you're having, I have a PVT-4 Desire as well and I've often found that I get odd little issues with otherwise solid ROMs that most folks dont seem to suffer from. I usually wind up doing a complete wipe/format and reinstall the ROM to ensure nothing has been left over from an older or other ROM that's causing issues and that normally fixes most my problems.
azraelb said:
Maybe a chunk of dirt/filth gets stuck in the groove there and tricks the proximity sensor into thinking the phone is always close to something so it turns off the screen as it's meant to.
As for the issues you're having, I have a PVT-4 Desire as well and I've often found that I get odd little issues with otherwise solid ROMs that most folks dont seem to suffer from. I usually wind up doing a complete wipe/format and reinstall the ROM to ensure nothing has been left over from an older or other ROM that's causing issues and that normally fixes most my problems.
Click to expand...
Click to collapse
Well, I don't think the problem is related to that, because a friend of mine has the same problems, and has no PVT4 Desire...
could a slow SD Card or an app cause the problem?
Noticed something strange for the first time , screen is laggy and not responsive while charging the phone , I think it maybe is the kernel as its the first time to notice this , It happened after flashing franco-r6 kernel and iam using insert coin 6.3.1 Rom
Is this normal ?
Sent from my HTC One X using XDA
You flashed a ROM, You're not stock therefore you need to consult the dev of that Rom about the issue.
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Is it still present ? What did u do about it ?
Sent from my HTC One X using XDA
Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Yep I get this issue at times as well. Especially when I've left it to charge for a while and try to perform a pattern unlock. Happens about twice a week or so. Screen returns to normal after 10 seconds or so. Weird.
+1 this happens on stock roms all the time. it's intermittent, and often can be temporarily fixed by switching the screen off then on again.
I'm about to send my phone in for repair because of this problem. I actually have a dead patch on the screen which is intermittent. If I go to Developer Options > Pointer Location, and then trace my finger around the screen, I can see the patch where it's not picking up the input. Also sometimes the phone behaves erratically and can become completely unresponsive and flicks back and forth between home screens. Turning the screen off and then on again fixes it temporarily.
i am having a strange issue. Running Virgin Rom Google Edition 4.4.4.
Every time I am on the phone, screen turns black as expected. Yet, when I hang up, the screen doesn't turn on. Very often I cannot wake up the phone by pressing any button. After about a minute or two, it becomes responsive again, and I am able to turn the phone on.
When looking at Better Battery Stats, ProximitySensor is the biggest battery hug. In fact it runs for as long as the accumulated time of the phone calls I have mad or received.
In other words, it doesn't turn itself off when I am on the phone.
I tried blowing the compressed air through the top speaker and headphone jack with no improvement.
Is this hardware related or software related?
i tried other roms on this phone and don't remember having this issue.
I like using the AOSP based rom. If this is software related, can someone recomend another AOSP rom that works well and stable, and is as quick as snappy as the virgin rom I am using?
Any help, suggestions would be highly appreciated.
Thanks
That's an issue with aosp/cm ROMs, only in touchwiz it works as it should. It's also normal for it to be on while you are in a call. You can try opening the phone and blowing in it instead of just from the outside
I am confused by what you write.
You are saying there is an issue with aosp/cm roms. . Yet, you are also saying that it is normal for the proximity sensor to be constantly on while on the phone. Then if it is normal, than what is the issue with aosp rom? Does the proximity sensor stay on as well in TW roms?
Please clarify what you mean.
Thanks.
serio22 said:
That's an issue with aosp/cm ROMs, only in touchwiz it works as it should. It's also normal for it to be on while you are in a call. You can try opening the phone and blowing in it instead of just from the outside
Click to expand...
Click to collapse
Sorry I meant the issue with it not waking the phone up is the problem with aosp/cm ROMs. Proximity sensor needs a wakelock to detect when you move the device away from your ear so it can wake the phone up.. Wakelocks are not always bad
serio22 said:
Sorry I meant the issue with it not waking the phone up is the problem with aosp/cm ROMs. Proximity sensor needs a wakelock to detect when you move the device away from your ear so it can wake the phone up.. Wakelocks are not always bad
Click to expand...
Click to collapse
I dont know about it being a wakelock problem. I used to have this problem with the google play edition rom on my s4, where the screen will not come back on during a phone call, I got a air duster can and blow out the speaker above the screen. Samsung put the proximity sensor right behind the speaker for when you hold the phone up to your head and it get dirty easily.
Could you recommend a good TW rom that is light on resources and quick in real use?
Those are the aspects that attracted me to aosp roms in the first place.
retfeg said:
Could you recommend a good TW rom that is light on resources and quick in real use?
Those are the aspects that attracted me to aosp roms in the first place.
Click to expand...
Click to collapse
I generally don't recommend ROMs but Warpdrive is the lightest tw ROM I have ever used, its super debloated and fast, but I found there was home button lag at first, but this is because s-voice was removed and you can't easily disable the 'open by double taping home button' feature which is what makes it lag, so I installed S-voice myself, disabled the feature and the lag was gone
Haven't really found much about this issue but sometimes this gesture doesn't work, even after just barely putting the device to sleep. All the other gestures(flashlight, camera,music) work perfectly but the wake feature is hit or miss kinda thing.
Can amplify or something similar cause this issue?
Yes, same thing happened to me sometimes. Usually happens when I holding the phone on my hand or just pull it out of pocket, probably it's because the Pocket Mode turned on.
You can "force"-enable that feature into the kernel using for example Kernel Adiutor. It fixed the problem for me.
I also experience this issue when I take out the phone from my pocket. In this case, I need to do the double tap around three times to get it working. But in every other cases it is working without any issues.
Maybe we should report it on OP Bug report.
néonaloj said:
You can "force"-enable that feature into the kernel using for example Kernel Adiutor. It fixed the problem for me.
Click to expand...
Click to collapse
How do you happen to do that? I'm a complete noob when it comes to messing with the kernel