Develop Bugs

[Q] Glide freezing up

Hello,
I've been experiencing annoying freezing up issues with my second-hand Glide. In all cases, the freeze happens with the screen off and a race condition ensues discharging the battery (even when plugged into power). Searching around, I've seen a good number of references to this problem:
androidforums.com/samsung-captivate-glide/462710-freeze-ups-anyone.html
gsmarena.com/samsung_i927_captivate_glide-reviews-4071.php
comparecellular.com/cell-phones/galaxy-s-glide
but I have not been able to find any resolution. Sometimes I feel like this: xkcd.com/979 . In essence I'm trying to determine if this is a hardware fault or something which can be fixed by software. Seeing minimal Glide development does not help since there are very limited options for ROMs. Since this device did get a nod for ICS, there's still hope in that, but until then have to suffer.
Anyone seen a resolution other than exchange? Warranty?

Unfortunately, this is quite common but there are few users that did not had any freezes since day one of their Glides.
One issue is, you have your Google calendar sync and you have "Auto Sync" active. This leads for the Calendar to Sync improperly during sleep mode resulting in a sync loop, which makes the device unresponsive thus, wont wake up upon pressing power/lock key. Solution, uncheck the "Auto Sync" function in Settings, Manually sync everything, or uncheck the "Sync Calendar on your Google account.
The other thing which is very common, is leaving wifi on while charging. This results on the same issue above but the reason is not clear. I experience this one in 1 out of 5 chances, so I turn wifi off or set the wifi sleep policy to "when screen turns off" in Settings. Happens on stock and custom ROM(s), except when Cranium Kernel is flashed.
In conclusion, I never thought that these are hardware issues ATM, for my previous Samsung devices also have these, but is eliminated by updating firmware, or flashing a custom ROM.

Thank you for the suggestions. I will verify wifi sleep policy as well as disable calendar sync to see if it helps. And now that there is some activity regarding ICS for this unit, maybe I'll get to test a new ROM to see if it helps.
thanks again

Neither unsynching google+calendars, or the WiFi+charging solutions worked for me.
Is there any hope for those of us with no immediate remedy?
Has Samsung even acknowledged that this is an issue?
When do you predict us getting an ICS update that will solve the issue?
Its a damn shame since I'm ****in loving this phone so far, yet i can't even use it when I want to sometimes.

Well yeah....I can confirm. I reflashed my device and restore my apps...did not do any mods and whatnot. Used it for a day and charged it overnight, no internet. And bam! Sleep Death. Like i said, this is common, and does not think that this is a hardware issue for a lot is experiencing it. So for now, dont left your glide charging overnight, or if you will, download a night clock, or use the stock desk clock. You will have a clock beside you and will keep your device awake all night.

Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?

wLnston said:
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
Click to expand...
Click to collapse
The issue you addressed is so called "sleep death." A few weeks past, ATT announced that 10 of their devices will get ICS in less than a month (including the Glide). No word from Rogers when will they update their version of the device.

Unfortunately AT&T did not state when they would push the update as well they only named the devices that will get it.

Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?

wLnston said:
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
Click to expand...
Click to collapse
I believe Samsung is already knowledgeable about the issue....unfortunately, it is not that easy to make a software update just to solve 1 problem (on the contrary to the Captivate SGH-I897 with GPS issues on Eclair, ATT immediately released a FW update within less than 2 weeks to fix it). And, even though I said the Sleep Death is quite common, not all of the users have this, so again, maybe unless a considerable large number of users (or all users) experience this, they might look into it. So I also believe that Samsung (along with ATT/Rogers) will correct the issue on the next update. When? Heaven knows.
If you are experiencing the sleep death more than twice a day, without doing anything, or if you believe non of your installed programs is at fault, and you are still in your return period, I suggest you exchange your device. You might get a unit that is unaffected. My Sleep Death only occurs when I left the phone charging for extended periods of time, like charging overnight which I always do. As I've mentioned, I keep the device awake like installing a night clock application or activating the stock desk clock app.

Well I'm going to try turning on the night clock app this night and see if that stops the sleep death.
And I bought the phone second hand off craigslist. Even if its within the 90-day period, I doubt I'll get any warranty/return ability as I am not the original customer.

interesting problem, will this should hold me back from buying it when my friends will be in the states?

taiber2000 said:
interesting problem, will this should hold me back from buying it when my friends will be in the states?
Click to expand...
Click to collapse
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day (on the contrary of the OP's post). In fact, my last sleep death was 10 days previous....it's been reliable and does the job.

gabby131 said:
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day. In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
Click to expand...
Click to collapse
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.

dudejb said:
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
Click to expand...
Click to collapse
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).

i have a therory about that, as some other user mentaioned when they useed adracat kernel (that is OC) the problem is gone. maybe samsung uses a underclocked tegra2 prossesor and that tha problem.

gabby131 said:
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
Click to expand...
Click to collapse
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.

dudejb said:
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
Click to expand...
Click to collapse
this is exactly what I am experiencing....and I can replicate this issue about 8/10 times....well this should hopefully be fixable via FW update (like my SGH-I896 from 2.1 to 2.2).
Yes I have CWMR installed and is very handy....I am now going back to flash OsiMood ROM for I think I already know what triggers the Sleep Death specially in stock ROMs....

Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!

wLnston said:
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
Click to expand...
Click to collapse
Some people have stated that once you install a Rooted Rom you will no longer get pushed the updated from your service provider. They stated this from Gingerbread 2.3.5 to 2.3.6
In order to go back to stock you have to somehow back up what you have before you flash anything or find it on the web. I am not sure about this but have heard of others doing this.
Your other option is use a ROM that someone cooks with ICS when it becomes available. I have heard of many people toying with getting this set up.

[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.

4.3 media server battery drain and weird stats. [fixed by itself]

So this just started happening once again on 4.3, I used to have this issue in 4.2.2 and it normally was either a corrupted image in my image gallery or a song or something in google play music, I used to be able to fix the battery drain by the media server by deleting the corrupted image or by clearing the cache in play music, now either of does things will not fix the battery drain.
I have been running 4.3 since day one, stock, rooted, clean install. The drain just started happening today out of nowhere I believe, maybe after some apps updated but about 7 apps updated today and I didn’t even check which ones, any idea how to track down what is causing this?
Something really weird that I noticed is that when the phone is pluged in the multimedia server active time stops going up but as soon as I unplug my phone the time starts running again draining the battery.
The other weird thing is that battery stats says I have about 40% of battery left and after a rebook it says I have 15% or something like that, this has happened twice already since 4.3 and it didn’t happened to me before 4.3.

Same issue... Resolved by turning off most options in sound settings, including keypad tones, charging sounds and screen lock sounds, then restarting.
Sent from the inner sanctum of my mind.

so this just fixed itself overnight, after trying many things and non of them working i just left the phone with my default config and charging overnight because of the weird battery stats, i wanted to make sure i had a full charge.
today i wake up and phone seems fine, no more mediaserver battery drain, i guess te phone was updating something or doing something weird, no apps updated, didnt change anything after making sure i still had the issue, nothing, it just fixed itself.

Has anyone had issues with the screen?? I used mmuzzys 4.3 and it ran smooth for awhile but crapped out on me. I used my backup and now have this going on. I turn the phone off and it kicks back on but not to the normal screen. Its a weird back light type of thing.

mrwh!te said:
Has anyone had issues with the screen?? I used mmuzzys 4.3 and it ran smooth for awhile but crapped out on me. I used my backup and now have this going on. I turn the phone off and it kicks back on but not to the normal screen. Its a weird back light type of thing.
Click to expand...
Click to collapse
Try another kernel. If that doesn't help, it's probably a Rom issue..
Sent from the inner sanctum of my mind.

Prasad007 said:
Try another kernel. If that doesn't help, it's probably a Rom issue..
Sent from the inner sanctum of my mind.
Click to expand...
Click to collapse
I tried a new kernel that didnt help so I did a factory reset and installed liquid fresh but it is still doing it. I may have to do a full wipe and and reload everything.

Another question. Does anyone have the code for actually turning the screen on and off? I'm thinking something screwed during my freeze fest. Any help will be great. Thanks guys

mrwh!te said:
I tried a new kernel that didnt help so I did a factory reset and installed liquid fresh but it is still doing it. I may have to do a full wipe and and reload everything.
Click to expand...
Click to collapse
this is a screen overheat issue, sometimes it can be permanent, just wait for everything to cool down before stock flashing your phone, it is usually due to wakelock issues / kernel issues

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?

FP_wakelock, Google play services battery drain and fingerprint unlock missing

I'll start at the beginning.
Around 4 months ago, everything with the phone was perfect, but then, I think after an update I did, it all went to ****. The battery started draining really fast, the fingerprint unlock function stopped working.
Let me explain what the issue with the fingerprint sensor is. One day the fingerprint unlock function stopped working, I tried wiping the sensor, wiping my fingers, but nothing. I thought that removing the fingerprint data and re-adding it might help, so I removed the old data, but when I tried to set it up again, the fingerprint scanner was not registering anything. After that I thought rebooting the phone might fix it, so I rebooted it, and boom , the fingerprint unlock option in the settings was not even there! I did a little research on the internet , and it turned out , that a lot of people have the problem of fingerprint unlock option missing from there settings, and there were all kinds of methods of fixing the issue, I tried some of them, and I managed to make it work again, but only for a short while, and then it stopped working again! After that I couldn't get it to work no matter what I did.
After that I said, **** it, I don't have the time to deal with this , I'll just not use the fingerprint unlock.
But then the ****ing battery drain started happening, I installed , Better battery stats , and it was showing that Google play services is the culprit, I tried everything there is on the net, from removing Google accounts and uninstalling Google play services updates, to doing a clean reinstall of the ROM. Nothing worked!
Finally I decided to move to another ROM, I installed Pixel-experience a few days back, and the fingerprint unlock option is still missing, but now I have another battery drain, in better battery stats it says fp_wakelock. Which If I'm not wrong is something connected to the fingerprint service?
So does anyone have an idea on how to end my misery or should I downgrade to Oreo?

shcxatter2 said:
I'll start at the beginning.
Around 4 months ago, everything with the phone was perfect, but then, I think after an update I did, it all went to ****. The battery started draining really fast, the fingerprint unlock function stopped working.
Let me explain what the issue with the fingerprint sensor is. One day the fingerprint unlock function stopped working, I tried wiping the sensor, wiping my fingers, but nothing. I thought that removing the fingerprint data and re-adding it might help, so I removed the old data, but when I tried to set it up again, the fingerprint scanner was not registering anything. After that I thought rebooting the phone might fix it, so I rebooted it, and boom , the fingerprint unlock option in the settings was not even there! I did a little research on the internet , and it turned out , that a lot of people have the problem of fingerprint unlock option missing from there settings, and there were all kinds of methods of fixing the issue, I tried some of them, and I managed to make it work again, but only for a short while, and then it stopped working again! After that I couldn't get it to work no matter what I did.
After that I said, **** it, I don't have the time to deal with this , I'll just not use the fingerprint unlock.
But then the ****ing battery drain started happening, I installed , Better battery stats , and it was showing that Google play services is the culprit, I tried everything there is on the net, from removing Google accounts and uninstalling Google play services updates, to doing a clean reinstall of the ROM. Nothing worked!
Finally I decided to move to another ROM, I installed Pixel-experience a few days back, and the fingerprint unlock option is still missing, but now I have another battery drain, in better battery stats it says fp_wakelock. Which If I'm not wrong is something connected to the fingerprint service?
So does anyone have an idea on how to end my misery or should I downgrade to Oreo?
Click to expand...
Click to collapse
Just give a shot to latest unbrick tool :good:

intoxicated.mad said:
Just give a shot to latest unbrick tool :good:
Click to expand...
Click to collapse
can you please elaborate, I have no idea, what you're talking about?

shcxatter2 said:
can you please elaborate, I have no idea, what you're talking about?
Click to expand...
Click to collapse
Look at this thread :good:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012

intoxicated.mad said:
Look at this thread :good:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
Bro, I don't know if you can read, but my phone is not bricked!
Jeez, I remember when xda was a place where you can actually get some kind of help, now you either wait two weeks for a single reply, or you get useless stuff posted on your thread. Good job everyone!

shcxatter2 said:
Bro, I don't know if you can read, but my phone is not bricked!
Jeez, I remember when xda was a place where you can actually get some kind of help, now you either wait two weeks for a single reply, or you get useless stuff posted on your thread. Good job everyone!
Click to expand...
Click to collapse
Hello,
Calm down. He can read but the best way and the easiest one is to make a factory reset or use a tool for bricked phones. There are so many reasons which can cause your problems. Try this tool and let us know if everything is ok now.
Backing to issues with the fingerprint scanner, maybe it is a problem with hardware... I had a problem with wi-fi and bluetooth on my OP3T and it looked like a software problem but it wasn't. Maybe you get wet the scanner... Maybe phone dropped....
Regarding battery drain, try a CPU spy app and let us know what deep sleep do you have on your phone. Also try to turn off the wi-fi and bluetooth scanning in localisation section. And try once again the CPU spy app.
Before you do anything make a backup of your data.
Cheers.

shcxatter2 said:
Bro, I don't know if you can read, but my phone is not bricked!
Jeez, I remember when xda was a place where you can actually get some kind of help, now you either wait two weeks for a single reply, or you get useless stuff posted on your thread. Good job everyone!
Click to expand...
Click to collapse
And i remember when xda was a place where people were actually respectful.
Have you tried to clean install OOS ?

XavNotFound said:
And i remember when xda was a place where people were actually respectful.
Have you tried to clean install OOS ?
Click to expand...
Click to collapse
How am I being disrespectful exactly?
As far as I can see, the other guy just left a vague reply which has no real meaning, when writing what he thinks I should do will take him 1 minute at most, and then you are asking me if I've tried a clean reinstall , when I've clearly mentioned it! Did you even read my post?

shcxatter2 said:
How am I being disrespectful exactly?
As far as I can see, the other guy just left a vague reply which has no real meaning, when writing what he thinks I should do will take him 1 minute at most, and then you are asking me if I've tried a clean reinstall , when I've clearly mentioned it! Did you even read my post?
Click to expand...
Click to collapse
Woops, i've seen the reinstall thing, but i didn't see that you clean reinstalled it
something that bothers me is that even if you installed PE or clean installed OOS, the fingerprint thingy was still missing, so it could maybe be an hardware issue
as for the play store, it should be ok when you install another ROM, or clean install OOS
maybe try to downgrade to oreo, as you stated in your post (backup your apps with titanium backup so it won't be too much of a hassle)

Any updates op?