Develop Bugs

Does your phone have a delay when turning the display on?

I noticed that there would sometimes (50% chance) that there will be a noticeable 1 second delay when pushing the power button and when the display actually turns on. It's annoying because sometimes i'll want to check the time, and i'll push the button as i'm taking it out of my pocket only to be met with a black display still.
i tried turning off the pattern lock thinkng that was it but still having the same problem.
i'm completely stock.

No delay here...when I press the power button, my display comes on instantly.

tracerit said:
I noticed that there would sometimes (50% chance) that there will be a noticeable 1 second delay when pushing the power button and when the display actually turns on. It's annoying because sometimes i'll want to check the time, and i'll push the button as i'm taking it out of my pocket only to be met with a black display still.
i tried turning off the pattern lock thinkng that was it but still having the same problem.
i'm completely stock.
Click to expand...
Click to collapse
This had already been discussed id you remove your sdcard the delay will go away.
Sent from my SPH-D710 using Tapatalk

***** here about the 2 second loss of time in your life.. http://forum.xda-developers.com/showthread.php?t=1265716

Did you really just say 1 sec???? Lol really. If your Checking the time I doubt 1 sec is that annoying!
Sent from my SPH-D710 using xda premium

alnova1 said:
***** here about the 2 second loss of time in your life..
Click to expand...
Click to collapse
Still thread ****ting on every topic about the delay?
Its obvious why the delay doesn't bother you; you already have too much time on your hands.
Otherwise, it's an obvious flaw in the phone. Why don't you let other people worry about their own lives and how many seconds are wasted.

craigbailey1986 said:
Did you really just say 1 sec???? Lol really. If your Checking the time I doubt 1 sec is that annoying!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
1 second is annoying when YOU'RE used to the display coming on instantly.
thanks for the link, i'll check it out.

yes its terrible anyone have a fix to this yet

If it's because of the SD card, trying increasing the SD Card Read Ahead Buffer. It can be built into the kernel or changed with a few market apps, or even a script. It'll also make photos/videos/anything from the SD card load faster.

fadetobolivia said:
Still thread ****ting on every topic about the delay?
Its obvious why the delay doesn't bother you; you already have too much time on your hands.
Otherwise, it's an obvious flaw in the phone. Why don't you let other people worry about their own lives and how many seconds are wasted.
Click to expand...
Click to collapse
Aren't we touchy! As long as people keep making threads about it , yes I will still state my opinion on the matter just like you are...have a good day sir.

alnova1 said:
***** here about the 2 second loss of time in your life.. http://forum.xda-developers.com/showthread.php?t=1265716
Click to expand...
Click to collapse
That's what I was thinking, who cares. Now that I check mine has the same thing, I never noticed and I really don't give a **** to try and "fix" this.. lol

Sean-El said:
That's what I was thinking, who cares. Now that I check mine has the same thing, I never noticed and I really don't give a **** to try and "fix" this.. lol
Click to expand...
Click to collapse
Amen brother...

Isn't this forum built for people who want to get the most of their devices? If everyone just decided things were 'good enough' you wouldn't have devs here writing custom kernels and ROMs. If the issue doesn't bother you then don't bother posting in the thread. And if you absolutely must, don't be a douche about it.
OT: I noticed it too. This is my first smartphone, but it stood out. I assumed it was normal. It's not huge, but I definitely wouldn't mind a fix that didn't require abandoning my SD card.

Sycobob said:
Isn't this forum built for people who want to get the most of their devices? If everyone just decided things were 'good enough' you wouldn't have devs here writing custom kernels and ROMs. If the issue doesn't bother you then don't bother posting in the thread. And if you absolutely must, don't be a douche about it.
OT: I noticed it too. This is my first smartphone, but it stood out. I assumed it was normal. It's not huge, but I definitely wouldn't mind a fix that didn't require abandoning my SD card.
Click to expand...
Click to collapse
Agreed, especially since it's a 32GB card and it's transferable between phones...

Screen lags reminds me of pre-pay gas purchases.
The last 2cents always take forever to complete.

Sycobob said:
Isn't this forum built for people who want to get the most of their devices? If everyone just decided things were 'good enough' you wouldn't have devs here writing custom kernels and ROMs. If the issue doesn't bother you then don't bother posting in the thread. And if you absolutely must, don't be a douche about it.
OT: I noticed it too. This is my first smartphone, but it stood out. I assumed it was normal. It's not huge, but I definitely wouldn't mind a fix that didn't require abandoning my SD card.
Click to expand...
Click to collapse
This is your first smartphone and it stood out to you? I have had 15 smartphones and would have never noticed it until someone mentioned it. Like I said, I don't see this as an issue so I will speak my peace as you can to..we agree to disagree and just because we don't see it your way doesn't make us a douche....sorry for the loss of time in your life I'm...oh ****!...I missed the Andy Rooney farewell on 60 minutes because I couldn't get the time on my phone because it came up 2 seconds too late!

alnova1 said:
This is your first smartphone and it stood out to you? I have had 15 smartphones and would have never noticed it until someone mentioned it. Like I said, I don't see this as an issue so I will speak my peace as you can to..we agree to disagree and just because we don't see it your way doesn't make us a douche....sorry for the loss of time in your life I'm...oh ****!...I missed the Andy Rooney farewell on 60 minutes because I couldn't get the time on my phone because it came up 2 seconds too late!
Click to expand...
Click to collapse
It's not a HUGE issue, but it is something that should be fixed.
In fact, just to move things forward, I tried increasing the SD Read Ahead Buffer with an app "SD Card Booster" or some name like that, which doesn't decrease the speed of the screen coming on, but does drastically cause photos and other things to load faster when you, say, open the Gallery. That was expected though. We used to increase it on the OG Evo.

Ive owned a few smartphones noticed ET lag after 3rd wake up.
First thing I thought of was Sprint Blackberry curve 8330-M.
It did the same thing drove me crazy lol

I tell you what...take your phone back to Sprint and tell them you have a 2 second lag and see what they say...maybe you can get a new phone...its obviously a defect...

alnova1 said:
I tell you what...take your phone back to Sprint and tell them you have a 2 second lag and see what they say...maybe you can get a new phone...its obviously a defect...
Click to expand...
Click to collapse
Its not hardware defect....its software related thus Sprint will push you out the door no new phone in hand with chuckles from rep.
Will update to fix issue come?
Never! so those that think samsung gives a care you better think twice.
Oh I forgot,
My HP Ipaq 6515 had wake up lag with SD card as well

Several sensors have failed in less than 24hours

Hello guys
I received my phone yesterday and it was working nicely but today when I realized, I saw that several sensors weren't working.
After several hours of wiping, flashing roms, RUU's, and so on... my phone is defective 99.9% sure.(NOT!)
I've downloaded the app "Sensor List" by Idea Matters, and it shows me 9 sensors, but the only ones working are the proximity and light sensors.
The first two pictures are from my phone, the other three are from a friends HTC ONE X that is working properly.
The difference is clear enough...lol! Can this be a software related issue?
The ones from him say Panasonic and all of mine say MPL.
BTW: both of our phones were made in Taiwan according to the invoice.
His is white, mine is grey
Tks
EDIT: SOLVED WITH THE STUPIDEST POSSIBLE THING EVER... after all of the trouble, simply went to task manager and did a kill all tasks, working perfectly.
If it happens to you guys, consider simply turning the phone off and on again.Don't do a simple reboot.

Have you tried this?
http://forum.xda-developers.com/showthread.php?p=24513824
You can test almost all sensors without installing 3rd party apps.

yup the magical number is still 20% defect rate
color and build country seems unrelated also the chinese seems more affected
20% is not acceptable...

tks mate but it just stays there "put the device on a plane surface", and it doesn't do anything

hamdir said:
yup the magical number is still 20% defect rate
color and build country seems unrelated also the chinese seems more affected
20% is not acceptable...
Click to expand...
Click to collapse
damn...

casca said:
damn...
Click to expand...
Click to collapse
it will clear out in few weeks I'm sure but yea damn

hamdir said:
yup the magical number is still 20% defect rate
color and build country seems unrelated also the chinese seems more affected
20% is not acceptable...
Click to expand...
Click to collapse
total understatement!!!!!

This is not what I was hoping to hear :/

hamdir said:
yup the magical number is still 20% defect rate
Click to expand...
Click to collapse
Did you know that 84.175% of all internet polls about defect rates were complete nonsense, and didn't return anything even slightly close to the real-world figure?
It's true, I swear. I read it on an internet poll. ;-)

hamdir said:
yup the magical number is still 20% defect rate
color and build country seems unrelated also the chinese seems more affected
20% is not acceptable...
Click to expand...
Click to collapse
Never in this world do they have a 20% failure rate. A straw poll on XDA doesnt equate to real life figures, nor do any internet polls as such.
20% failure rates would be picked up at the factory without a doubt. 20% is a damn high figure.
Generally 1% failure is the norm , so at most if things really are bad it'll be at 5%. Never 20%.
Slim

hamdir said:
it will clear out in few weeks I'm sure but yea damn
Click to expand...
Click to collapse
what do you mean by clear out?

Omg... This is the weirdest thing ever...
After having unlocked, relocked, and unlocked the bootloader again...flashing the ruu, flashing several roms, restored factory defaults, restoring through the phone fastboot menu and so on...
Nothing was able to get my sensors working (g-sensor,compass,gravity...).only proximity and light sensor kept working.
The fix after all of my failed attempts was as simple as going to the phones task manager and doing a "kill all tasks".
This is the freakiest and weirdest gadget related issue i have ever seen.
3 letters...
Wtf!
Sent from my HTC One X using XDA

casca said:
Omg... This is the weirdest thing ever...
After having unlocked, relocked, and unlocked the bootloader again...flashing the ruu, flashing several roms, restored factory defaults, restoring through the phone fastboot menu and so on...
Nothing was able to get my sensors working (g-sensor,compass,gravity...).only proximity and light sensor kept working.
The fix after all of my failed attempts was as simple as going to the phones task manager and doing a "kill all tasks".
This is the freakiest and weirdest gadget related issue i have ever seen.
3 letters...
Wtf!
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
More than likely all you've found is a bug in the test program.

Don't know dude...but after all i have done, the solution was freakin weird...
Sent from my HTC One X using XDA

hamdir said:
yup the magical number is still 20% defect rate
color and build country seems unrelated also the chinese seems more affected
20% is not acceptable...
Click to expand...
Click to collapse
you base that on what? What we se on forums are what usualy are called "vocal minority". That is the people that yells most are often the ones heard.
I dont think HTC has more problems then other new high-end devices like xperia.

audioslim said:
Never in this world do they have a 20% failure rate. A straw poll on XDA doesnt equate to real life figures, nor do any internet polls as such.
20% failure rates would be picked up at the factory without a doubt. 20% is a damn high figure.
Generally 1% failure is the norm , so at most if things really are bad it'll be at 5%. Never 20%.
Slim
Click to expand...
Click to collapse
It's a defect rate being measured in the poll not a failure rate.

rory88uk said:
It's a defect rate being measured in the poll not a failure rate.
Click to expand...
Click to collapse
Arguably, the poll isn't measuring anything at all. You can vote more than once, vote if you don't own the phone, vote incorrectly on purpose or because you don't actually know what is a phone defect or a third party software issue, and of course as stated already people with problems are vastly more likely to answer than those without.
The poll is completely meaningless...

[Help][50% SOLVED] LTE = random heavy battery drain aka "plummet"

jeffreii said:
UPDATE/CONFIRMED:
The plummet is back.
After 10 days of plummet-free use with LTE disabled, it has returned after less than 48 hours uptime following my re-enabling of LTE.
For me, I am quite convinced that some LTE bug - perhaps with switching back and forth to HSPA+ - is causing the plummet. Unless some very knowledgeable devs join this discussion and help to find the root cause, I only see two options to avoid this problem:
1) Disable LTE and live with HSPA+ speeds
2) Wait for an OTA update with a fix, assuming Samsung/AT&T know about it
Personally I am sick and tired of wasting my time diagnosing this. I have lost time and enjoyment of my device trying to keep a stable testing environment. I now know the general cause and solution and am satisfied with that.
Thanks to anyone and everyone who helped.
Again, here is the link to my method for disabling LTE:
http://forum.xda-developers.com/showthread.php?t=1826409
It's unfortunate that using HSPA+ only also disables 2G, but that's not really a problem for me in Miami.
Click to expand...
Click to collapse
Anyone who can help diagnose the cause of this would be my hero. Please read carefully the evidence I already have.
Scenario:
Battery life is great for awhile and then suddenly it will start plummeting for no good reason. It will continue to do so, even if the screen is off and the phone is unused with all tasks closed. It will not stop dropping fast unless I reboot it. Then battery life returns to normal/excellent..a day or so later it starts dropping fast again.
Things I've tried:
-Factory reset - reinstall only most common apps
-Exchanged the device at AT&T - same result
-Monitored with GSAM (Badass) Battery Monitor and Better Battery Stats. No culprit found.
Important notes:
-As per attached screenshot*, I have tested ways to stop the drain without a reboot. Turning off wifi does nothing. Turning off mobile data does nothing. Turning off the radio (airplane mode) is the only way to stop it - but once I turn airplane mode off, it continues to drop quickly. Only a reboot is a working temporary fix.
-The phone itself is reporting the "cell standby" as the major culprit. I am not sure if this is inflated due to the known bug in reporting that data.
-There is something quirky with the "mobile network signal" bar - I am in Miami where signal is strong almost everywhere. The steep decline occurs even at my apartment where I always have 4 or 5 bars of LTE signal. I am almost never in any area where there is no signal, despite what the line indicates.
Attached screenshots:
1 & 2) good battery life followed by a sudden and steep decline
3) the subsequent "test" listed in note # 1 above with the resulting plateau achieved by turning on airplane mode with the drop continuing when airplane mode was disabled
4 & 5) I then charged the device to full overnight and unplugged it in the morning. I let it sit unused for about 2 hours and the battery dropped 25%.
6 & 7) these screenshots are from normal excellent battery life scenario where the "plummeting" battery did not occur
Thank you so much for any help

Since turning on airplane mode stops it my guess is that its a bad radio. Only option would be to exchange it and tell them this is your second defective unit.

DudeWatsThat said:
Since turning on airplane mode stops it my guess is that its a bad radio. Only option would be to exchange it and tell them this is your second defective unit.
Click to expand...
Click to collapse
What are the odds of me having two units in a row with the exact same problem, which does not appear to be widespread?
The bad news is that I am past my 30 day exchange window.

jeffreii said:
What are the odds of me having two units in a row with the exact same problem, which does not appear to be widespread?
The bad news is that I am past my 30 day exchange window.
Click to expand...
Click to collapse
If you got that unit during your 30 days you should have 30 days for that unit and if you don't then go through manufactures warranty. Unless your willing to play around with roms to see if that solves it.
In terms of odds maybe your ATT store just got a bad batch either that or you have incredibly bad luck but I do know of one other person who had the same problem if I remember correctly.
Sent from my GSIII

DudeWatsThat said:
If you got that unit during your 30 days you should have 30 days for that unit and if you don't then go through manufactures warranty. Unless your willing to play around with roms to see if that solves it.
In terms of odds maybe your ATT store just got a bad batch either that or you have incredibly bad luck but I do know of one other person who had the same problem if I remember correctly.
Click to expand...
Click to collapse
My understanding of the return policy, as confirmed by the rep, is that exchanging your device does not reset the 30 days. I would have to go through the manufacturer warranty now, facilitated by AT&T. Much more hassle than just going to the store and swapping it out.
I received my first S III in the mail from AT&T Online. 30 days later I went to one of several local corporate stores and exchanged it. They were definitely not the same batch. This is probably not bad luck and I have heard from several others that they have this same problem...
My next step, after some more logs and troubleshooting, would be to factory wipe again and use the phone stock with no apps for up to a week to see if I can reproduce it. Sounds terrible but I'm willing to do it if it is necessary. Still hoping someone here on XDA can help me pinpoint the problem.
Thanks again for your response.

I get this battery drain maybe once a week, a friend of mine also gets it occasionally, It is very unlikely that our phones are from the same batch, because he got his 2 weeks before i got mine. It seems to be a more widespread problem than we think, and i hope samsung, or someone on XDA, can figure it out and fix it.

jeffreii said:
My understanding of the return policy, as confirmed by the rep, is that exchanging your device does not reset the 30 days. I would have to go through the manufacturer warranty now, facilitated by AT&T. Much more hassle than just going to the store and swapping it out.
I received my first S III in the mail from AT&T Online. 30 days later I went to one of several local corporate stores and exchanged it. They were definitely not the same batch. This is probably not bad luck and I have heard from several others that they have this same problem...
My next step, after some more logs and troubleshooting, would be to factory wipe again and use the phone stock with no apps for up to a week to see if I can reproduce it. Sounds terrible but I'm willing to do it if it is necessary. Still hoping someone here on XDA can help me pinpoint the problem.
Thanks again for your response.
Click to expand...
Click to collapse
Do that and remember to do a test using airplane mode if it doesn't loose battery while in airplane mode then there are two theorys then: samsung software bug that affects radio or hardware issue.
It also depends how many "several others" are, remember even 100 people are a minority compared to the millions of units sold.
Keep us updated so we can get to the root of the problem.
Sent from my GSIII

Here's another sample with a Better Battery Stats log attached as well.
I'm going to do another test tonight with airplane mode enabled + another BBS log.

jeffreii said:
Here's another sample with a Better Battery Stats log attached as well.
I'm going to do another test tonight with airplane mode enabled + another BBS log.
Click to expand...
Click to collapse
Whats your screen on time, battery stats indicated a deep idle of only 2hrs.
And damn your cell standby % is huge. When I had the cell standby bug it only rose to about 15%.
IMO that high cell standby is not normal even with the bug.

DudeWatsThat said:
Whats your screen on time, battery stats indicated a deep idle of only 2hrs.
And damn your cell standby % is huge. When I had the cell standby bug it only rose to about 15%.
IMO that high cell standby is not normal even with the bug.
Click to expand...
Click to collapse
I agree with you, I don't think it's normal even with the bug. Maybe OP should download fix or a rom with the fix if he doesn't want to use the warranty and see if it still tops the charts with the bug fixed.

jeffreii said:
Here's another sample with a Better Battery Stats log attached as well.
I'm going to do another test tonight with airplane mode enabled + another BBS log.
Click to expand...
Click to collapse
post your bbs log to the thread here : > Android Development and Hacking > Android Apps and Games > [APP] [30 Jul - V1.9.1] BetterBatteryStats adds battery history back to Android
http://forum.xda-developers.com/showthread.php?t=1179809
you will be helped there for sure.

This has happened to me on several ROMs, but it doesn't happen very often. It does seem to be radio related. The last time it happened, I checked the battery graph and the signal strength was solid green from exactly the time the battery started plummeting. Not sure if that means anything but it's another data point.

Firestar292 said:
I agree with you, I don't think it's normal even with the bug. Maybe OP should download fix or a rom with the fix if he doesn't want to use the warranty and see if it still tops the charts with the bug fixed.
Click to expand...
Click to collapse
Strange thing is the bug just reports the % wrong and applying the fix won't actually solve is drainage issues, although if he does apply it and still sees a high percentage its most probably the radio or he could apply it see normal cell % and we be back to square one.
bradld said:
post your bbs log to the thread here : > Android Development and Hacking > Android Apps and Games > [APP] [30 Jul - V1.9.1] BetterBatteryStats adds battery history back to Android
http://forum.xda-developers.com/showthread.php?t=1179809
you will be helped there for sure.
Click to expand...
Click to collapse
+1

Search for the gsiff_daemon thread. It sounds like that may be your problem. I don't have the link handy but if you don't find it I'll dig it up for you.
Sent from my GT-P3113 using xda app-developers app

jcejohnson said:
Search for the gsiff_daemon thread. It sounds like that may be your problem. I don't have the link handy but if you don't find it I'll dig it up for you.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
I agree that its gsiff_daemon bug. I get it on occasion when streaming music through web. Even when I close it will drain the battery quickly. Do a search for that daemon and see if that shows up in battery stats. Usually shown as android system. When you hit refresh under battery stats it usually displays the gsiff name quickly.
Sent from my SGH-I747M using xda app-developers app

blue265 said:
I agree that its gsiff_daemon bug. I get it on occasion when streaming music through web. Even when I close it will drain the battery quickly. Do a search for that daemon and see if that shows up in battery stats. Usually shown as android system. When you hit refresh under battery stats it usually displays the gsiff name quickly.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
What is gsiff_daemon? I looked in the thread but the info is scattered.

DudeWatsThat said:
Whats your screen on time, battery stats indicated a deep idle of only 2hrs.
And damn your cell standby % is huge. When I had the cell standby bug it only rose to about 15%.
IMO that high cell standby is not normal even with the bug.
Click to expand...
Click to collapse
The BBS log was only 2 hours, 38m, as you can see from the extracted data below:
Since 2 h 38 m 8 s
Deep Sleep (): 2 h 24 m 59 s (8699 s) Ratio: 91.7%
Awake (): 13 m 9 s (789 s) Ratio: 8.3%
Screen On (): 40 s (40 s) Ratio: 0.4%
Firestar292 said:
I agree with you, I don't think it's normal even with the bug. Maybe OP should download fix or a rom with the fix if he doesn't want to use the warranty and see if it still tops the charts with the bug fixed.
Click to expand...
Click to collapse
Yeah I can see about downloading the fix but that is only a display issue and wouldn't help at all with my battery.
bradld said:
post your bbs log to the thread here : > Android Development and Hacking > Android Apps and Games > [APP] [30 Jul - V1.9.1] BetterBatteryStats adds battery history back to Android
http://forum.xda-developers.com/showthread.php?t=1179809
you will be helped there for sure.
Click to expand...
Click to collapse
I have posted several times in that thread and they tried to help but couldn't find anything...the main suggestion was to try a custom kernel...I'm going to post my latest logs there now though (and in this thread).
EDIT: Here's my new post in that thread:
http://forum.xda-developers.com/showthread.php?p=29716265#post29716265
21cdb said:
This has happened to me on several ROMs, but it doesn't happen very often. It does seem to be radio related. The last time it happened, I checked the battery graph and the signal strength was solid green from exactly the time the battery started plummeting. Not sure if that means anything but it's another data point.
Click to expand...
Click to collapse
I noticed the same thing with the mobile network signal bar being solid. I still don't understand why that bar has so many gaps where it appears to show the radio off when it's not...anyways I thought there was a correlation there but have since seen plenty of "plummets" without the solid green mobile network signal bar.
jcejohnson said:
Search for the gsiff_daemon thread. It sounds like that may be your problem. I don't have the link handy but if you don't find it I'll dig it up for you.
Click to expand...
Click to collapse
gsiff_daemon is not in my BBS logs...see the new logs I'm about to post.

Ok so I've been continuing my tests from above.
I first charged a bit and then turned off wifi since wlan_rx_wake was a biggie in my BBS log. You can see the log for that period below. Battery continues to plummet as it did before.
I then turned on airplane mode and started a new BBS log. The battery stopped going down. In fact it was one of those situations where the charger mis-reported the actual charge and in nearly two hours time BBS sees the battery as having gone up 1%. That log is also attached.
Also below are screenshots of this whole process where you can see the battery plateau created by airplane mode.
Perhaps we can compare these 3 log files to determine something? I am going to post them in the BBS thread as well.
Thanks again everyone I hope we can get to the bottom of this!

jeffreii said:
Ok so I've been continuing my tests from above.
I first charged a bit and then turned off wifi since wlan_rx_wake was a biggie in my BBS log. You can see the log for that period below. Battery continues to plummet as it did before.
I then turned on airplane mode and started a new BBS log. The battery stopped going down. In fact it was one of those situations where the charger mis-reported the actual charge and in nearly two hours time BBS sees the battery as having gone up 1%. That log is also attached.
Also below are screenshots of this whole process where you can see the battery plateau created by airplane mode.
Perhaps we can compare these 3 log files to determine something? I am going to post them in the BBS thread as well.
Thanks again everyone I hope we can get to the bottom of this!
Click to expand...
Click to collapse
I couldn't find anything between all 3 that is consistent and have enough % of use to screw up your battery.
I'm curious, what is your theory on what might be the cause?

DudeWatsThat said:
I couldn't find anything between all 3 that is consistent and have enough % of use to screw up your battery.
I'm curious, what is your theory on what might be the cause?
Click to expand...
Click to collapse
Thanks again for looking. Honestly I am assuming it's a bug deep in the software or something...either that or one of my apps.
First I thought it was an app. Then I thought it was hardware. Now I am just trying to re-evaluate and look at all of the evidence.
Part of me wants to just reboot every night and forget about it...

Spontaneous Reboot Syndrome?

Does your device suffer from SRS (spontaneous reboot syndrome)?
This one is strange and I can't say it wasn't happening before the latest update (to 4.4.2). Before 4.4.2 I was not yet a CUCS sufferer (Compulsive Uptime Checker Syndrome).
However last night I was reading a book with my tablet next to me when it made its booting chime and this made me pause. Placing a bookmark in the latest Dresden novel I picked up my tablet and saw the LG logo. It rebooted for apparently no reason. So now I suffer from CUCS (Compulsive Uptime Checker Syndrome). Trying to see if the device is rebooting at odd times throughout the day.
So if all of you running stock 4.4.2 could periodically check your uptime as well so we can collectively determine if it is just my device that is doing this, I'd appreciate the help...
So far my uptime is still climbing and I'm now over 24 hours. If it does continue to spontaneously reboot I will probably start with a factory reset

So you want others to suffer your fate of becoming a CUCS sufferer....?!

vimesUK said:
So you want others to suffer your fate of becoming a CUCS sufferer....?!
Click to expand...
Click to collapse
Laughs, no, but it is the only way I could come up with to check if it was rebooting when it wasn't being used... So I apologize if you too end up with CUCS!

muiriddin said:
Laughs, no, but it is the only way I could come up with to check if it was rebooting when it wasn't being used... So I apologize if you too end up with CUCS!
Click to expand...
Click to collapse
I'm no use to you, but your acronyms made me smile, thankyou
Sent from my LG-V500 using XDA Premium HD app

whoamigriffiths said:
I'm no use to you, but your acronyms made me smile, thankyou
Click to expand...
Click to collapse
Glad you found it funny, that was the second goal of my post the first being trying to see if anyone else had noticed the device seemingly rebooting for no reason. It has not happened again (yet). I guess my CUCS must be in remission since I didn't check uptime before I left for work this morning...

FWIW I noticed that mine had uptime of almost a week, until I rebooted it last night after I rooted it.
It might have been influenced from your Dresden book, as Jim Butcher paints such a vivid picture spurious magic is known to flow from the pages. I would contact the white council if it should happen again.

Well, I shut my G Pad down almost every night when I charge it, so I'm probably not the best judge. That being said, my Pad is on for 14 or 15 hours a day, and I've almost never had a spontaneous reboot.

woody1 said:
Well, I shut my G Pad down almost every night when I charge it, so I'm probably not the best judge. That being said, my Pad is on for 14 or 15 hours a day, and I've almost never had a spontaneous reboot.
Click to expand...
Click to collapse
I never shut mine down. For one thing in standby, without being plugged in, I do not see even 1% battery drain after 8 hours, so really see no reason to shut it down.

muiriddin said:
Glad you found it funny, that was the second goal of my post the first being trying to see if anyone else had noticed the device seemingly rebooting for no reason. It has not happened again (yet). I guess my CUCS must be in remission since I didn't check uptime before I left for work this morning...
Click to expand...
Click to collapse
I've seen probably a dozen reboots since I bought my gpad in December. Considering that I have tried every rom that has been produced for us and the fact I have settled firstly on CM11 Nightlies and now Infecteds CM11 Nightlies, I have to say I'm more than happy.
Especially when you take into account I tested both Demetris gpe rom and Kernel for him.
I've had a couple in the last week or so but again I am on Nightlies so I go into it expecting the odd issue.
Sent from my LG-V500 using XDA Premium HD app

I had my first spontaneous reboot last night since I bought it a few months ago. I dont know how long since I last rebooted it, but I know its been a while. Im on stock unrooted KK.

I can confirm at the very least that a spontaneous reboot for me does appear to be quite rare. Thanks to all who at least looked at their up-time as part of this and hopefully this syndrome has no long term lasting effects on us all! Enjoy the upcoming weekend!

Ghost Quick Scrolls, 8.1 issue?

Hi all,
I have recently been noticing ghost scrolls, where I would be slowly scrolling downwards, say, in the XDA app or reddit app, and randomly it would scroll quickly upwards when I lift my fingers. I was thinking this was a hardware issue so I got a replacement device on the way. However, I saw this https://www.reddit.com/r/GooglePixel/comments/7rczu2/scrolling_up_when_scrolling_down/.
Has anyone else been experiencing the same thing? I posted a vid and pic https://imgur.com/a/ny8fT. The second pic is touch input trace enabled in developer options, you can see there was a ghost long fast drag down to the bottom below the navbar.
Have been away from XDA for a while, please let me know if I am going against any rules about posting images hosted on other sites.

I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk

Devhux said:
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
yep, thats happened to me a few times before as well. Not twitter specifically, but in reddit I would click on a post, and somehow I would end up on some random other post like 2 post below it, and if I hit back once, I get to the post I originally intended to click on instead of the subreddit list.
So there must be some sort of ghost touches/scrolls on finger release, causing the unintended post to be queued up just before the intended one.
I'm surprised there hasn't been more people bringing up this issue (assuming this is indeed a software 8.1 issue and not an isolated issue in the touch panel).

Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk

Devhux said:
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.

ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it

elliwigy said:
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
Click to expand...
Click to collapse
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.

ethantarheels123 said:
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
Click to expand...
Click to collapse
prolly 8.1.. i got mine around december late nov. pretty sure its software related.. they had an issue with touch on the lockscreen right?

It seems like so many touch issues with 8.1 release. For this reason, I am still using 8.0.
https://productforums.google.com/forum/#!msg/phone-by-google/FfzV1578L8Q/1HcWw3CCAQAJ
https://issuetracker.google.com/issues/70344455

ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...

ayoraider07 said:
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
Click to expand...
Click to collapse
Replacement device has the same issue, so this is definitely a software bug. Hopefully Google fixes it soon in the next patch update.

Nexus 6P here. I started getting these ghost touches with the last security update. 8.1 is the problem, not a solution.

My mom has the same issue of touch on places she doesn't touch, on Pixel XL.
Could it be the same?
Here is a video about it that I took, just by scrolling in the settings screen:
https://drive.google.com/file/d/1JCsTuMDvMNHh0CO7sF7yoLFT26uNIhUp/
It's a bit hard to reproduce, but it occurs eventually.
Has anyone tried to use Android P, and see if it helps?
Anyway, I've reported about this here too:
https://forum.xda-developers.com/pi...h-pixel-xl-t3807188/post76879468#post76879468

Any fixes yet?
I know this is old, but I wanted to know if anyone found a fix for this. I eventually found an Oreo 8.1 Rom that I like and this is the only issue that's bothering me.