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,
Sometimes when i click Home button Middle-Bottom of the screen.
physical buttons's Backlight turning on but screen doesn't come up.
I have to try at least 5-6 more times for screen to show up.
What is wrong with my phone ?
It's just sometimes really annoying..
Thank you for reading.
Best Regards.
UP
Using the latest FW ?
From my sexy LT15i
Do you use any custom Rom/kernel?
Sent from my Xperia Arc using XDA
Seems like extreme lag to me. The next time it happens check with a program (like OS monitor) the cpu usage. The situation that you described happened to me once, the MtpApp process was using 100% cpu and i couldn't use my phone properly until i rebooted it.
I faced a similar issue on a Xperia Ray
Its hardware i guess, flashing stock didnt work for me
What i say is you should flash stock FW
Thank you for all those answers !
I'm using DoomKernel 2.32.9 ( I Guess it's 19v )
2.3.7 Modded GB Deluxe Edition ( http://forum.xda-developers.com/showthread.php?t=1533332 )
It was happening more before i started using Modded GB Deluxe Edition.
But it is still happening, and still a lot annoying..
Thank you for reading.
Best Regards.
If your using a program like SetCPU or no-frills cpu control make sure that the minimum clock frequency is not set to 122MHz. Try set it to atleast 245MHz. I tried setting the "screen off" CPU to the minimum on SetCPU before in the hope to get more battery life, but whenever I wanted to wake the phone there would be a 2-3 second lag before the screen showed up. I hope this helps.
I guess this will work.
remove your SD card, connect it to a PC & format it, Insert it back.
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
oojjii said:
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
Click to expand...
Click to collapse
Maybe you can try flashing the stock kernel to test? i tried flashing a non-stock kernel a few times before and results were mixed and never perfect for me (don't really know why). Sometimes it would randomly glitch and the screen would turn black for about 1/2 a second or something. Wifi would sometimes be intermittent despite flashing the modules for some as well.
I'm not experienced enough to fully understand but I'm thinking that it could be a regional thing? I mean, how signals differ between regions?
So.......
Did it work........
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.