Develop Bugs

[Q] isl29028_wq Process - What is it?

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

[Possible Solution] LPAPlayer wakelock not letting phone enter deep sleep

I posted this question in the correct thread for the ROM I'm using in my signature (also note I'm using the newest version of the KT747 kernel as well), but people are currently more interested in hearing themselves talk on that thread, calling people trolls when the "troll" is actually helping answer questions, and just waste space with non-development chit-chat.... So maybe asking it here will get an answer!
I'm getting a partial wakelock constantly from LPAPlayer, a low power audio player that supposedly gets installed or screwed up when you install AwesomeBeats, but I never had that installed and can't seem how to disable or fix the issue with LPAPlayer eating up the battery, making the CPU run at max while the screen is off....
Anyone got any ideas or suggestions? Thanks!

Bump... Same problem here with VZW s3 running stock rooted JB 4.1.1!
Sent from my SCH-I535 using xda app-developers app

Have you tried flashing clean from stock? And just to clarify, you have LPAplayer without installing the Beats audio equalizer?
Sent from my SGH-I747 using xda premium

crazililazn said:
Have you tried flashing clean from stock? And just to clarify, you have LPAplayer without installing the Beats audio equalizer?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
No I didn't come from stock but I did do a clean flash. And you are correct and having that wakelock without having installed beats
Sent from my SCH-I535 using xda app-developers app

travis.bridges10 said:
No I didn't come from stock but I did do a clean flash. And you are correct and having that wakelock without having installed beats
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe it was a bad flash? Have you tried reflashing since you noticed the wake lock?
Sent from my SGH-I747 using xda premium

crazililazn said:
Maybe it was a bad flash? Have you tried reflashing since you noticed the wake lock?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I've been on this since about 2 days after it came out never had a problem. The all of a sudden it started 2 days ago. I haven't installed anything new and haven't made any substantial changes. The only media players I use are play and Pandora.
Sent from my SCH-I535 using xda app-developers app

Just to add in to what Travis has been saying, and it all applies the same for me too, I just reflashed the device with the same ROM, but wiped everything first, including System.... Because these aren't official JB ROMs, I'm not spending too much time getting everything set up on the device right now, so when I wipe, I restore data from a previous backup, and while I'm sure that's not helping anything, there has to be a way to prevent LPAPlayer from using up so much battery!

KryptosXLayer2 said:
Just to add in to what Travis has been saying, and it all applies the same for me too, I just reflashed the device with the same ROM, but wiped everything first, including System.... Because these aren't official JB ROMs, I'm not spending too much time getting everything set up on the device right now, so when I wipe, I restore data from a previous backup, and while I'm sure that's not helping anything, there has to be a way to prevent LPAPlayer from using up so much battery!
Click to expand...
Click to collapse
Well one thing I know for sure is that we have the same exact nonofficial JB rom installed (lol) and that I do not have the LPAPlayer issue, nor could I find it installed. Travis says that he uses Google Play Music and Pandora, so maybe it has to do with one of the two. Try using Titanium and freezing these two apps and see if it fixes your battery drain.

I know it isn't Pandora, I don't use it or even have it installed on my phone.... I could see it having to do something with Google Music, I use that constantly while driving. Won't be in the car tomorrow so I'll freeze it tonight and see if anything gets better, one can only hope when no real solutions are being presented!

STILL having the issue, Pandora and GMusic are NOT the issue (as far as I can tell....)
Here's a guy having the same issues too, found that Awesome Beats was the recommendation, and never installed it either, still no resolution for him:
http://www.samsunggalaxys3forum.com...s3-help/7523-interesting-battery-problem.html
Looks like the only solution is to wipe and reinstall everything with TiBU, hoping that the issue isn't stuck in one of my user apps and just the data I'm restoring after every time I wipe....
EDIT - I MAY have found a solution! Those affected, please help me test this - those NOT affected, please check and see if your settings are different!
http://forum.xda-developers.com/showpost.php?p=25475691&postcount=4732
On there, it said to disable LPAPlayer, set lpa.decode=false in build.prop, under System, using Root Explorer, or similar. I like Root Explorer because when you select R/W at the top, press and hold on build.prop, select Open in Text Editor, you can hit the Menu button and Save and Exit while Root Explorer automatically saves the original as a backup, using .BAK. If you're unfamiliar with Root Explorer or need more instructions, let me know, I need others to test this OR see if your lpa.decode setting was already set to false! Mine WAS set to true before I edited it, rebooted, and now I'm testing to see if it works.... after 14 mins, I'm seeing a deep sleep of 5 mins so far, so it may have worked!!! There isn't any mention of any partial wakelocks from LPAPlayer right now either!

KryptosXLayer2 said:
STILL having the issue, Pandora and GMusic are NOT the issue (as far as I can tell....)
Here's a guy having the same issues too, found that Awesome Beats was the recommendation, and never installed it either, still no resolution for him:
http://www.samsunggalaxys3forum.com...s3-help/7523-interesting-battery-problem.html
Looks like the only solution is to wipe and reinstall everything with TiBU, hoping that the issue isn't stuck in one of my user apps and just the data I'm restoring after every time I wipe....
EDIT - I MAY have found a solution! Those affected, please help me test this - those NOT affected, please check and see if your settings are different!
http://forum.xda-developers.com/showpost.php?p=25475691&postcount=4732
On there, it said to disable LPAPlayer, set lpa.decode=false in build.prop, under System, using Root Explorer, or similar. I like Root Explorer because when you select R/W at the top, press and hold on build.prop, select Open in Text Editor, you can hit the Menu button and Save and Exit while Root Explorer automatically saves the original as a backup, using .BAK. If you're unfamiliar with Root Explorer or need more instructions, let me know, I need others to test this OR see if your lpa.decode setting was already set to false! Mine WAS set to true before I edited it, rebooted, and now I'm testing to see if it works.... after 14 mins, I'm seeing a deep sleep of 5 mins so far, so it may have worked!!! There isn't any mention of any partial wakelocks from LPAPlayer right now either!
Click to expand...
Click to collapse
Also started noticing this issue on my Sprint GS3, while playing Google Music, as that is the only music player I have, and have not installed any other apps, like Beats, or the like. Via Betterbatterystats I would see that anytime I'd play/use Google Music, LPAPlayer would keep the phone awake, even if I forced closed the Google Music app. Only way to stop it from keeping the phone awake was to reboot my phone, which was a pain since I use it to stream music all day. Anyone know what LPAPlayer is for, where it's located? I can't find much info on it. I'm going to try the above and edit the build.prop entry, as mine was set to true, and report what I get! Thanks!

r3ddawn said:
Also started noticing this issue on my Sprint GS3, while playing Google Music, as that is the only music player I have, and have not installed any other apps, like Beats, or the like. Via Betterbatterystats I would see that anytime I'd play/use Google Music, LPAPlayer would keep the phone awake, even if I forced closed the Google Music app. Only way to stop it from keeping the phone awake was to reboot my phone, which was a pain since I use it to stream music all day. Anyone know what LPAPlayer is for, where it's located? I can't find much info on it. I'm going to try the above and edit the build.prop entry, as mine was set to true, and report what I get! Thanks!
Click to expand...
Click to collapse
Yep, same issue I had too - someone must have edited the build.prop on us in a ROM or something to have that effect on different carrier's SGSIII's.... I've seen MUCH better battery life out of my phone since then, with the only wakelock coming in the form of Light Manager, but everyone who uses LightFlow / Light Manager for their LED notifications complain about poor battery life from wakelocks, so there's nothing I can do with that right now!
Glad I could help, definitely report back and let me know what you come up with when you change that setting and reboot!

KryptosXLayer2 said:
Yep, same issue I had too - someone must have edited the build.prop on us in a ROM or something to have that effect on different carrier's SGSIII's.... I've seen MUCH better battery life out of my phone since then, with the only wakelock coming in the form of Light Manager, but everyone who uses LightFlow / Light Manager for their LED notifications complain about poor battery life from wakelocks, so there's nothing I can do with that right now!
Glad I could help, definitely report back and let me know what you come up with when you change that setting and reboot!
Click to expand...
Click to collapse
Yup that was it, after the change and a reboot, I no longer have that issue. I am still searching to try to figure out why/what would have caused it, but the issue is fixed with the edit made, so I hope this helps others as well. Thanks again!

KryptosXLayer2 said:
Yep, same issue I had too - someone must have edited the build.prop on us in a ROM or something to have that effect on different carrier's SGSIII's.... I've seen MUCH better battery life out of my phone since then, with the only wakelock coming in the form of Light Manager, but everyone who uses LightFlow / Light Manager for their LED notifications complain about poor battery life from wakelocks, so there's nothing I can do with that right now!
Glad I could help, definitely report back and let me know what you come up with when you change that setting and reboot!
Click to expand...
Click to collapse
I was getting wakelock from LPAPlayer too (on sprint gsIII). Yesterday was the first day i noticed the poor battery like. About two days ago for the first time, i installed lightflow just to check it out. I immediately uninstalled it cause i don't really have a use for the app. I just now looked in betterbatterystats and found it was LPAPlayer. Do you think that app is causing the issue then?

r3ddawn said:
Yup that was it, after the change and a reboot, I no longer have that issue. I am still searching to try to figure out why/what would have caused it, but the issue is fixed with the edit made, so I hope this helps others as well. Thanks again!
Click to expand...
Click to collapse
Glad to hear it!
smac7 said:
I was getting wakelock from LPAPlayer too (on sprint gsIII). Yesterday was the first day i noticed the poor battery like. About two days ago for the first time, i installed lightflow just to check it out. I immediately uninstalled it cause i don't really have a use for the app. I just now looked in betterbatterystats and found it was LPAPlayer. Do you think that app is causing the issue then?
Click to expand...
Click to collapse
It's possible, but probably not likely.... I know I had Lightflow installed as well and uninstalled it to use Light Manager instead (Lightflow was causing a separate battery drain not associated with LPAPlayer, from what I understand), but I think that's just coincidence that we both had it installed at one point and it changed the settings to enable LPAPlayer....

I am/was having the same issue. I only saw LpaPlayer giving my phone a partial wake after using Google Play Music. I changed the build.prop as suggested and it looks like that fixed the problem. Thanks

sorry for bumping a month old thread but i've noticed this issue as well. Google music would also freeze up on me. Rather annoying. Let's see if editing build.prop fixes it

KryptosXLayer2 said:
STILL having the issue, Pandora ROM rooted GMusic are NOT the issue (as far as I can tell....)
Here's a guy having the same issues too, found that Awesome Beats was the recommendation, and never installed it either, still no resolution for him:
http://www.samsunggalaxys3forum.com...s3-help/7523-interesting-battery-problem.html
Looks like the only solution is to wipe and reinstall everything with TiBU, hoping that the issue isn't stuck in one of my user apps and just the data I'm restoring after every time I wipe....
EDIT - I MAY have found a solution! Those affected, please help me test this - those NOT affected, please check and see if your settings are different!
http://forum.xda-developers.com/showpost.php?p=25475691&postcount=4732
On there, it said to disable LPAPlayer, set lpa.decode=false in build.prop, under System, using Root Explorer, or similar. I like Root Explorer because when you select R/W at the top, press and hold on build.prop, select Open in Text Editor, you can hit the Menu button and Save and Exit while Root Explorer automatically saves the original as a backup, using .BAK. If you're unfamiliar with Root Explorer or need more instructions, let me know, I need others to test this OR see if your lpa.decode setting was already set to false! Mine WAS set to true before I edited it, rebooted, and now I'm testing to see if it works.... after 14 mins, I'm seeing a deep sleep of 5 mins so far, so it may have worked!!! There isn't any mention of any partial wakelocks from LPAPlayer right now either!
Click to expand...
Click to collapse
Just want to say THANK YOU for this post. AT&T GS3 here stock rom 4.1.2 and rooted. This fixed the lpaplayer wakelock for me. I used Root Browser to change the setting and then restarted. Noticeable improvement in battery life as a result.

Random reboot - OP3 6.0.1 stock

Hi,
I have a OnePlus 3 which is about 7 months old now. I'm running stock 6.0.1 (OOS 3.2.7) with Xposed. ElementalX kernel and TWRP recovery (if that matters) ... I use Kernel Adiutor for a few misc tweaks (vibrator, LED, hostname) and AKT Profiles is set to Fusion Conservative - which limits GPU as well. I have been using various Xposed modules without any issue until the following happened.
I had installed Parallel Space - an app which allows dual WhatsApp capability. I started experiencing random soft reboots and shutdowns. So I uninstalled it. Then I cleared cache and ART cache. I also uninstalled a few apps that I had installed in the past month.
I am still experiencing reboots and I cannot pinpoint the cause. The reboots/shutdowns occur when the screen is off. Always when the screen is off.
I'm bad at reading logs, so can't figure out from the logcat either.
Anyone who can help me out, will be greatly appreciated! I will provide all logs as necessary.
[EDIT] Solution: Do not let any app make use of the proximity sensor to manipulate the screen. For example, apps which switch off the screen when flipped might be the culprit.

Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something

cl0g said:
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
Click to expand...
Click to collapse
Nope, no Magisk. Only Xposed.

Providing logs from logcat. Will provide anything else if required.

A few more logs containing fatal errors.

I thought the problem was solved by uninstalling this app called "Pixoff", but no, it still persists. Also, the LED is glowing orange, without any notification pending. During screen on as well as off.

Can you please flash stock ROM and check once if the same problem persists?

hrishikeshgramani said:
Can you please flash stock ROM and check once if the same problem persists?
Click to expand...
Click to collapse
That is what I'll have to do if changing settings or regular fixes don't work... But I don't want to jump to it right now because there's a lot of tweaks I'm running and they will be destroyed.
Also, it was running perfectly until last week. I have uninstalled all apps that I got in the last month. Cleared ART cache and normal cache. Haven't restored to factory settings yet.
I'm experimenting with disabling Xposed modules one by one, although I don't think it's a module problem - because I've had them since eternity.
What I have concluded is - I downloaded a rogue app from the Play Store which has left it's data and that is the cause of reboots... I might be wrong though.
Hence, I would really appreciate if someone would go through the logs and figure it out.

I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.

cl0g said:
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
Click to expand...
Click to collapse
Will do that next time, thanks!

Okay, so I figured this out. Proximity sensor is having issues. I had enabled "Proximity wake" in GravityBox and that was causing problems. Disabled it and Everything was fine as ever.
To verify that proximity sensor was at fault, I tried Pixoff's flip to Black screen feature - it uses the proximity sensor to figure whether device is in pocket or flipped... And yes, phone rebooted there too.
Phone is running fine as long as the sensor is used only during calls (to switch screen off)
But what I cannot understand is why this is happening in the first place! I mean, proximity sensors are supposed to be used in this manner only, right?
Nevertheless, if anyone wants to help, they are welcome. Otherwise my issue is solved.

ohio wake lock

Hello all
This week I enabled the permission that allows Better Battery Stats to check for wakelocks etc without requiring root.
Resrarted phone, let it do its magic and then checked results.
Ohio_wake_lock was the big culprit and phone would not enter deep sleep.
On googling I came across next to no answers and some vague mention to disable HTC Push Client.
I disabled the app from the settings and the wakelock has since disappeared and my device now enters deep sleep which it didn't before.
Hopefully this helps others out there. If anyone has extra information on this wakelock it'd be great.

rdmack said:
Hello all
This week I enabled the permission that allows Better Battery Stats to check for wakelocks etc without requiring root.
Resrarted phone, let it do its magic and then checked results.
Ohio_wake_lock was the big culprit and phone would not enter deep sleep.
On googling I came across next to no answers and some vague mention to disable HTC Push Client.
I disabled the app from the settings and the wakelock has since disappeared and my device now enters deep sleep which it didn't before.
Hopefully this helps others out there. If anyone has extra information on this wakelock it'd be great.
Click to expand...
Click to collapse
Hi,
I appear to have the same wakelock issue as you did. Im running lineageos and cant find any traces of htc push client in app drawer, system apps or through titanium backup.
Where did you actually find it?
Thanks in advance.

I got this problem. How to get rid of this.

Harrygsr said:
Hi,
I appear to have the same wakelock issue as you did. Im running lineageos and cant find any traces of htc push client in app drawer, system apps or through titanium backup.
Where did you actually find it?
Thanks in advance.
Click to expand...
Click to collapse
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399

andybones said:
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
Click to expand...
Click to collapse
Thanks for the reply. I ended up bringing the phone back to my carrier and showed them how fast the battery was draining even after reverting back to full stock HTC. It was still under warranty so they sent it off for repair and came back fixed. The repair company didn't specify what they had changed, it just said something like faulty part replaced but it's good as new now running lineage again :good:

Harrygsr said:
Thanks for the reply. I ended up bringing the phone back to my carrier and showed them how fast the battery was draining even after reverting back to full stock HTC. It was still under warranty so they sent it off for repair and came back fixed. The repair company didn't specify what they had changed, it just said something like faulty part replaced but it's good as new now running lineage again :good:
Click to expand...
Click to collapse
Is it really hardware problem? I am on leedroid and ohio wake lock started yesterday. I tried disable Htc Push Client, but not works. I also flashed Elite Kernel, but no change.
andybones said:
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
Click to expand...
Click to collapse
Thanks @andybones , I'll be very happy if @fagyi help me .

I had the Ohio_wakelock and OTG_wakelock at the same time causing no deep sleep.
Also, my 10 wasn't fast charging.
I changed the charge port and all issues went away.
Exkm can disable these wakelocks, but that doesn't fix the problem.

mcmorariu said:
I had the Ohio_wakelock and OTG_wakelock at the same time causing no deep sleep.
Also, my 10 wasn't fast charging.
I changed the charge port and all issues went away.
Exkm can disable these wakelocks, but that doesn't fix the problem.
Click to expand...
Click to collapse
Thanks for reply. My fast charging worked, but the charging didn't. I had to reconnect the cable to the phone several times. After that charging started worked.
I tried many firmwares and ROMs (Marshmallow - stock, Nougat - stock, purefusion, Oreo - stock, Leedroid, Pie - lineage, crdroid), but the result was the same.
I decided to return my phone, because i bought it in 21/9/2017. I needed my phone on my holiday, so I flash stock Oreo. After five days wakelocks came out. I don't know how, but now I don't have any wakelocks and my charging works without problems.

Grubmi said:
Thanks for reply. My fast charging worked, but the charging didn't. I had to reconnect the cable to the phone several times. After that charging started worked.
I tried many firmwares and ROMs (Marshmallow - stock, Nougat - stock, purefusion, Oreo - stock, Leedroid, Pie - lineage, crdroid), but the result was the same.
I decided to return my phone, because i bought it in 21/9/2017. I needed my phone on my holiday, so I flash stock Oreo. After five days wakelocks came out. I don't know how, but now I don't have any wakelocks and my charging works without problems.
Click to expand...
Click to collapse
My device is crazy. First two screenshots are from night, where wakelock drain my battery. Others are from today usage.

Grubmi said:
My device is crazy. First two screenshots are from night, where wakelock drain my battery. Others are from today usage.
Click to expand...
Click to collapse
that does look crazy
when I had the hardware issue, it was consistently sucking up battery whether day or night...
I still recommend replacing the charge port, may be an intermittent short in that PCB.

Unknown wakelock keeps pixel awake 100% of the time

Hello guys,
I have encountered this 9-0022 kernel wakelock ever since I purchased this Pixel XL, and it keeps my device awake all the time.
It persists no matter how many times I factory reset or flashed a different factory image.
Google shows no answer of what it is and how to block it.
Has anyone faced this problem?
Android version: 8.1.0 April, Stock

Purchase Ex Kernel manager and turn that wakeloke off threw kernel using that app

Right here!

petiolarissean said:
Purchase Ex Kernel manager and turn that wakeloke off threw kernel using that app
Click to expand...
Click to collapse
I did so, but the wakelock wasn't there.

Try service disabler its free
---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------
Have you tried customs roms and is it still doing it?

petiolarissean said:
Try service disabler its free
---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------
Have you tried customs roms and is it still doing it?
Click to expand...
Click to collapse
Yes I did and it persists.:crying:

thetrangdam said:
Hello guys,
I have encountered this 9-0022 kernel wakelock ever since I purchased this Pixel XL, and it keeps my device awake all the time.
It persists no matter how many times I factory reset or flashed a different factory image.
Google shows no answer of what it is and how to block it.
Has anyone faced this problem?
Android version: 8.1.0 April, Stock
Click to expand...
Click to collapse
You flash stock firmware, roms etc and reset, and problem persists? Have you considered that there's no feasible way to remedy this? As in, your phone has defective hardware?
Otherwise, it would have to be a phone hacked by CIA with custom hardware that is impervious to resets and firmware flashes.
Think about it...

Contact google and there pretty easy going and will go out of there way replace phone.Ive went threw 5 pixel and every time they have jump threw hoops to make me happy.Phone returned 3-5 days every time.

Maybe it's malware!?
Read this: https://www.google.de/amp/s/amp.reddit.com/r/Moto_Z/comments/5ox4ab/constant_wakelock/
Sent from my Pixel XL using XDA Labs

nabbed said:
You flash stock firmware, roms etc and reset, and problem persists? Have you considered that there's no feasible way to remedy this? As in, your phone has defective hardware?
Otherwise, it would have to be a phone hacked by CIA with custom hardware that is impervious to resets and firmware flashes.
Think about it...
Click to expand...
Click to collapse
That could probably right.
At first, my device kept showing a persistent notification "USB Supplying Power to attached device",
And I could not charge my device unless I reboot (then it will appear again later).
I googled & figured some people had the same problem and got it solved by cleaning the charging port
on the phone so I did the same.
It stills show up time after time, but now I can choose to "charge this device" from the popup & charge fine.
But the kernel wakelock, which I believe belongs to usb otg or something like that, still keeps my device awake 100% of the time, and drain the battery.
petiolarissean said:
Contact google and there pretty easy going and will go out of there way replace phone.Ive went threw 5 pixel and every time they have jump threw hoops to make me happy.Phone returned 3-5 days every time.
Click to expand...
Click to collapse
Appreciate your help.
Unfortunately, I live in a country where Google isn't available, and purchased this device from private vendor,
so there's no way I can RMA this now.
spezi77 said:
Maybe it's malware!?
Read this: https://www.google.de/amp/s/amp.reddit.com/r/Moto_Z/comments/5ox4ab/constant_wakelock/
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Maybe not.
It happens no matter what rom, kernel I'm on.
Since I had the persistent "USB Supplying Power to attached device" time after time,
it's likely that wakelock thinks I'm plugging something into the usb port all the time,
and keeps my devices awake.
I've cleaned the port with tooth pick, some alcohol & air duster but the wakelock hasn't gone away.

Caused by USB I've seen before in BBS thread, I think it's due to a poor USB port on the device contact Google to see your options

I agree @liam_davenport. I did a little digging through some xda threads and people claimed they had that wakelock if they plugged their phone in wrong, do to the USB port being sloppy. There is also something in our device tree called "tcpm logging" that is related to that number, doing a little research now to see what it is/does.

let me talk to my cousin,he works at google.Let me throw problem at him

thetrangdam said:
Hello guys,
I have encountered this 9-0022 kernel wakelock ever since I purchased this Pixel XL, and it keeps my device awake all the time.
It persists no matter how many times I factory reset or flashed a different factory image.
Google shows no answer of what it is and how to block it.
Has anyone faced this problem?
Android version: 8.1.0 April, Stock
Click to expand...
Click to collapse
I've only heard of this problem with people running Android P preview2. It seems using the finger unlock on back of phone, some people tap it when the screen begings to dim and taping fingerprint brightens screen. But what I was thinking, that doing that even without preview2 might cause similar effect.
So you could try disabling that feature might help. It seems that their connected somehow.

fiverings said:
I've only heard of this problem with people running Android P preview2. It seems using the finger unlock on back of phone, some people tap it when the screen begings to dim and taping fingerprint brightens screen. But what I was thinking, that doing that even without preview2 might cause similar effect.
So you could try disabling that feature might help. It seems that their connected somehow.
Click to expand...
Click to collapse
Didn't he say Android 8.1, stock? He flashed it many times?