Hi all,
I just started having severe battery drain issues on my DHD this morning (~17% drained in 1.5 hours)
I installed Watchtower to check if there were any rogue processes that were eating up my CPU time. I noticed that this process called "isl29028_wq" was using about 30% of my CPU constantly, but I can't seem to figure out what it is, since nothing shows up on Google.
The only apps I installed recently were Layar and Google Goggles, which I've already removed.
Does anyone know what this process is?
Thanks!
Google says, "isl29028" without "_wq" is a low power ambient light and proximity sensor...
http://www.intersil.com/products/deviceinfo.asp?pn=ISL29028
Maybe is its driver running wild?
Now that you mention it, I have noticed Android System using the sensor quite frequently. I wonder if this is the cause of my poor battery.
This probably HTC's ****ty workaround for the mis-calibrated proximity sensor. First time I have ever seen it so severe.
I suggest going for a custom kernel and using my DHD Proximity Sensor Recalibrator app to to fix your issue (in app section).
Edit: Could also be light sensor related. Same chip.
leppie said:
This probably HTC's ****ty workaround for the mis-calibrated proximity sensor. First time I have ever seen it so severe.
I suggest going for a custom kernel and using my DHD Proximity Sensor Recalibrator app to to fix your issue (in app section).
Edit: Could also be light sensor related. Same chip.
Click to expand...
Click to collapse
Thanks for the suggestion, but I haven't really encountered any proximity sensor related issues during calls. I also forgot to mention that I'm using Android Revolution 2.0.11, which I believe uses Apache's kernel.
I'm going to poke around somemore and see if theres an app thats causing my sensor to go wild.
When this happens again, run the following:
Code:
adb shell dmesg > dmesg.log
and attach it to your post.
That could help us see what happens.
leppie said:
When this happens again, run the following:
Code:
adb shell dmesg > dmesg.log
and attach it to your post.
That could help us see what happens.
Click to expand...
Click to collapse
I tried running that command through USB, but the log simply says "demsg: not found".
EDIT: I just flashed ARHD 2.0.12, which uses an updated kernel. Let's see how it goes.
Hello!
i am having this issue by a couple of weeks, two days ago i found that process was continuously using 30-50% of cpu and my phone was very laggy...
i was unable to find a solution, anyone has a tips for me?
@@dgco86: did you find a solution? I wiped my handheld but after logged in with my google credentials, Market installed all my previous application automatically, so i don't know if this issue is app related or not...
Please help me, i really don't know how to solve the issue... Maybe changing my phone?
An update:
i tried EVERYTHING, such as wipe, factory reset, i follow the procedure found here to full reset the device, but i am still having this damn issue... isl29028_wq takes 30-70% of cpu randomly and gives my phone laggy and block also automatic brightness.. the only way to solve (temporary) the problem is to give a short call to someone, after have closed it everything comes back to work! But after a while, issue comes again...
Ah, i forgot to tell you that i am running a stock version of Android updated to the last version via OTA
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
Soo.. it started a while ago, i switch roms alot and i am very cautious when it comes to kernels and i try to flash the right one every time but with the S-ON limitations it has been some kind of confusing
to be exact, i flashed the pokemon rom with the kernel impeded through fastboot
and the proximity sensor is not working (not turning the screen off during calls)
and i flashed bricked, faux and franco's kernels and still its not working
and no its not physically damage because i had IC rom before it and it was working fine
does any one know what is going on, what i might be missing or something i could try
anything will be helpfull
Cheers
i installed an app called AndroSensor and it said for the proximity sensor check "faliur to start" and then after a while "waiting for event"
if that might help
and the light sensor is "waiting for event" too
well i solved it.. i dont know what actually happend but here is what i did
first i tried to flash the new franco kernel along with its modules and it didnt work (didnt boot)
so i thought to try not just the stock boot image (as it is provided in the pokemon flasher) but also the stock modules (as i dont own a widnows i cant just run the script file)
i unzipped the franco modules, replaced it with the stock modules and repacked it, flashed the stock boot.img in fastboot, flashed the repacked modules from the recovery and i got the proximity and the light sensor working again
could you please help me, my proximity sensor is not working at all...and i dont know why, i changed the kernel and the modules and it havent come back..., the light sensor is working well
I have the same Problem. Light Sensor is working. Proximity Sensor suddenly stopped working. There is no reaction when i use z-device test. The weird thing is, it passes the HTC function test and the red light turns on when i try to get a reaction of it in z-device test. It seems to work somehow but is not reacting to movement. I hope there is a fix for that. I don't want to send it in for the 6th time.
So it seems that my proximity sensor is not broken. It just needs very high brightness values to work. So in a dark room it won't work. Is there a way to calibrate the proximity sensor?
Even I have the problem of non-operation of the proximity sensor and light sensor lenses. After various tests and seen several videos, I realized that the problem is in contact with the sensor to the motherboard. Pressing close to sensors, close to the camera (back) everything returns to normal ...
Sorry for my English ...
I know this is an old thread, but I'm having the same problem as guistanca. Thought it was broken, but squeezing the phone made it burst back to life... dodgy?
Same problem like giustanca and peedub, any ideas,? It is hardware issue or it can be fixed by some software modification?
Ik have the same problem sinds a month, pressing the screen on the upside wil help to get the sensor to work again.
For me it's a hardware faillure i think.
Exactly my situation but when I press screen on the upside it help but just for I whine, few second and sensor didnt work again. I will wait for new official Jelly update 4.2. and if problem will be still remain, probably I will send my One X to service.
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.