Develop Bugs

Issues...

These are issues I have. I am running 2.3.3 OTA, unrooted.
1. Bootloop, factory reset fixed.
2. When I manage applications, if I click on an app, it reroutes me to a different one, so I often uninstall the wrong app.
3. Touch screen sometimes fails, reboot fixes.
4. Clock app disappeared, the factory reset mentioned earlier fixed it.
These just really annoy me.

AgalychnisCallidryas said:
These are issues I have. I am running 2.3.3 OTA, unrooted.
1. Bootloop, factory reset fixed.
2. When I manage applications, if I click on an app, it reroutes me to a different one, so I often uninstall the wrong app.
3. Touch screen sometimes fails, reboot fixes.
4. Clock app disappeared, the factory reset mentioned earlier fixed it.
These just really annoy me.
Click to expand...
Click to collapse
Hmm. The only issues I've had are related to system apps randomly being uninstalled. It is definitely frustrating, especially when my phone app disappears.

I have had the same issues. Contacted Verizon and they sent me a x2. I really miss sense but do not miss the issues. This happened on all 4 of the inc2's Verizon sent me.

Droid 3 tomorrow if I can! 3 phones in two weeks: Inc, Inc2, Droid 3! New record!

Nvm, going for a new inc2. Also, now my google account is gone and I can't add it back. This is causing market not to open. LOL. Can you say lemon?

Everthing that happened to to happened to me
Sent from my ADR6350 using XDA Premium App

My volume will.be.all the way up even alarm volume but all my alarm does is vibrate
Sent from my ADR6350 using XDA Premium App

Really hope the next one is better.

It sucks to hear you having all these problems. I too just got the Dinc2 coming from the original Dinc. I am having none of the issues you are having, updated latest gingerbread OTA, non-rooted. The only problem i had was a lagging touchscreen when using a certain cable charger combo, but once i switched cables everything was fine.

AgalychnisCallidryas said:
These are issues I have. I am running 2.3.3 OTA, unrooted.
1. Bootloop, factory reset fixed.
2. When I manage applications, if I click on an app, it reroutes me to a different one, so I often uninstall the wrong app.
3. Touch screen sometimes fails, reboot fixes.
4. Clock app disappeared, the factory reset mentioned earlier fixed it.
These just really annoy me.
Click to expand...
Click to collapse
I'm having the same issues as well. It's annoying but better than issues I've had with other phones.

Seems to be on a phone by phone basis. Imma try Inc2 #2 lol.

Hope you have good luck. I went through 4 before I had enough.

HTC responds to me:
"Dear **** *****,
Thank you for taking the time to contact HTC, ****. We are sorry to hear about the issues you have experienced with your HTC Incredible 2 after the recent update. We will gladly assist you with this inquiry.
With regards to the clock/alarm feature missing, this is something we are aware of and we are working on a resolution. Currently, we do not have an ETA as to when this fix will be available.
With regards to the other issues you were experiencing, these are not known issues at this time. For the failure to load issue, the only thing we could offer for that is to preform the factory reset. With regards to the market app, we could suggest you clear the data from the app by going to menu>settings>applications>manage applications>all(at the top)>market>clear data. Once the data is cleared we would ask you to restart your phone and try again.
It is entirely possible that the update did not apply correctly during the setup process causing the issues you have experienced. This could be why the factory reset has corrected these issues at this time.
If you run into any of these issues again, we would suggest that you try your phone in safe mode before jumping to a factory reset. This will disable third party apps and drivers from launching when the phone is powered on. You will still be able to make and receive calls, text messages, email, and use the internet.
To put the Incredible 2 into Safe Mode, use the following steps. Be patient with these steps, you may not get it into Safe Mode on the first attempt.
With the phone powered off, remove the battery for 10-20 seconds and re-insert it.
Press the Power key on your device
When you see the white screen with "HTC" on it, press & hold Menu key until OS loads.
"Safe Mode" text will appear on the lower left of screen to advise that you are in safe mode,to get out of safe mode just restart the phone.
If the issue was not happening while the device was in safe mode, this would indicate some kind of conflict or interference from a third party application. You would need to rule them out by uninstalling the apps until you find that the phone is working normally again, and then avoid using that app or combination of apps.
We deeply regret any inconvenience this has caused you, ****. As always, we are here to answer any technical questions or concerns you may have between 6am to 1am EDST, 7 days a week for your convenience, or by phone at 1-866-449-8358.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number *****************.
Sincerely,
Angela
HTC"

[Q] Device becomes unresponsive after several minutes of use.

Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN

The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.

KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium

Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.

Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium

Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.

Any news? Was it the battery issue?

Crazy Touch Screen Not Responding Bugs with my G3

So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot

I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk

@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.

deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2

Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).

^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.

Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.

@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?

I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96

Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.

This is happening when the screen is on right? Or is the screen turning off and then not turning I again?

You need to keep Knock feature on, someone already said this. That's why your screen is freezing.

Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug

icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...

Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...

Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...

icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?

Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.

Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.

Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!

Help! Ambient mode seems to freeze watch.

Have had the Huawei Watch for a few days and it seems to have a deal-breaking bug. Frequently, after the watch has been in ambient mode for a while, it won't come out of it. If I touch the screen, the ambient display gets brighter, but that's all. No response from swiping or button presses. Sometimes, after a very long pause (a minute or so) it'll come back to life, but usually I have to hold the button until it restarts. Anyone run into this before? Ideas? Any help is greatly appreciated.
Using it with a Nexus 6. Android wear version 1.3.0.2176821.
Thanks!!!
Sent from my Nexus 6 using XDA Free mobile app

Forgot to mention that the time sticks at whatever time it freezes and so it doesn't even tell the correct time. Sigh.
Have tried a factory reset. Didn't fix it.

Sounds like it's maybe in need of replacing. Like any new product release, there's bound to be a certain percentage of failures. Depending on how you look at it, you're either really lucky, or really unlucky

Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.

gyromiterob said:
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
Click to expand...
Click to collapse
I have absolutely same issue. In ambient mode it freezes from the first day I bought this watch. Thank you for investigation and info.

got my hwatch and experienced the ambient mode freeze. to unfreeze, i enter and exit theater mode. it works. but now i'm never sure if the ambient time i'm glancing at is accurate or not...

Similar problem with an HTC M8. I'll try the theater mode to see if that helps. I still can't trust the time any more.

+1 on the Huawei Watch freeze. Sometimes after 15 minutes, sometimes after several hours. It has frozen with ambient mode disabled and with wrist gestures disabled as well.
Sent from my LG-V500 using Tapatalk

Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?

brizey said:
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
Click to expand...
Click to collapse
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.

lukhof said:
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
Click to expand...
Click to collapse
Good to hear you got it fixed!

how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks

maximus96 said:
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
Click to expand...
Click to collapse
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.

lukhof said:
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
Click to expand...
Click to collapse
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.

maximus96 said:
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
Click to expand...
Click to collapse
None of them had red-tint issue. It seems this is not related with the freezing ambient mode.

Thanks, that solve my problem as well.

Happening to me too. Was using 3rd party skymaster watch face.

Got a replacement from amazon and it hasn't froze yet in the past two days of using it. The last one froze several times a day

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?