Develop Bugs

[Q] Extremely Slow Screen Wake Up Delay?

Just picked up the phone today and noticed a long delay between pressing the power button and the screen waking up. When it is plugged in there is no delay at all. The delay occurs whenever the phone is disconnected from a power source. It is about a 2 second delay. Is anyone else experiencing this? Best Buy didn't have another unit and the Sprint store was useless and wouldn't unplug their demo unit to compare.
I saw a thread concerning the standard Galaxy S II, but nothing Epic 4G Touch specific.
Thanks.
*update*
Just to make things perfectly clear, here is a video of the delay time:
http://www.youtube.com/watch?v=vqJc_nYuwac
*older update*
Downloaded Soft Locker Free and it allows the phone to instantly wake with no delay by bypassing a deep sleep mode. I'm unsure about how detrimental this is to the battery, but at least it's a fix. I'd still like to know if all Epic Touch phones have the wake up lag, though.

mine is doing this too.. are you using a SD Card wallpaper? I am. not sure if thats affecting things.

I have not noticed any delays on mine.

I have noticed this as well. I'm using a stock wallpaper.
Sent from my SPH-D710 using xda premium

thedeadletters said:
Just picked up the phone today and noticed a long delay between pressing the power button and the screen waking up. When it is plugged in there is no delay at all. The delay occurs whenever the phone is disconnected from a power source. It is about a 2 second delay. Is anyone else experiencing this? Best Buy didn't have another unit and the Sprint store was useless and wouldn't unplug their demo unit to compare.
I saw a thread concerning the standard Galaxy S II, but nothing Epic 4G Touch specific.
Thanks.
*update*
Downloaded Soft Locker Free and it allows the phone to instantly wake with no delay by bypassing a deep sleep mode. I'm unsure about how detrimental this is to the battery, but at least it's a fix. I'd still like to know if all Epic Touch phones have the wake up lag, though.
Click to expand...
Click to collapse
You shouldn't do that, it will be detrimental to your battery. Deep sleep mode means that the processor is technically off, provided the phone doesn't have any tasks to run while the screen is off.
Its perfectly natural for your phone to wake up immediately when plugged in, because that's how samsung designed the galaxy's. No need to deep sleep when the phone's getting a charge.
By restricting your phone from sleeping (affectionately referred to as wake lock),your forcing your processor to run for nothing, most likely at 200mhz. When it's all said and done, I estimate you'll end up shaving off about 5 hours of battery life. Not worth it to me, just learn to deal with 1 sec it takes to wake up the phone.
On a lighter note, I find it amusing that you've installed an app that now makes the phone do something that is commonly known as a bug and a lot of people spend their time trying to squash. Lol.
Sent from my SPH-D700 using xda premium

squshy 7 said:
On a lighter note, I find it amusing that you've installed an app that now makes the phone do something that is commonly known as a bug and a lot of people spend their time trying to squash. Lol.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1LOL*10
The amount of threads I have read, the hundreds if not thousands of posts I have seen the hundreds of developers that have all chased wake-lock bugs are all disgusted right now. Thousands if not tens of thousands of man hours have gone into chasing the wake-lock bugs down on many many many devices....in roms, in kernels in conflicting apps. For years. Sometimes its simple, sometimes it's given up on completely.
You are right. Wow, just, wow.

daneurysm said:
+1LOL*10
The amount of threads I have read, the hundreds if not thousands of posts I have seen the hundreds of developers that have all chased wake-lock bugs are all disgusted right now. Thousands if not tens of thousands of man hours have gone into chasing the wake-lock bugs down on many many many devices....in roms, in kernels in conflicting apps. For years. Sometimes its simple, sometimes it's given up on completely.
You are right. Wow, just, wow.
Click to expand...
Click to collapse
Lol, I'm actually crying a little from laughter. The scenario you described was exactly what went through my head when I wrote that
EDIT: to the OP, this is all in jest, no offense meant. But seriously, don't wake lock your phone.
Sent from my SPH-D700 using xda premium

I've noticed it too, but it isn't too bad of a lag. Not snappy like the EVO 4G, but not a dealbreaker, not on this.

Don't wakelock the phone.

Voluntarily wake locking a phone? Haven't heard that before lol
Sent from my PC36100 using xda premium

Journeyjeans said:
I've noticed it too, but it isn't too bad of a lag. Not snappy like the EVO 4G, but not a dealbreaker, not on this.
Click to expand...
Click to collapse
Thanks for all the responses. My past Android phones (Evo and Evo 3D) didn't have any delay whatsoever, which is the origin of the original post. The power of the Galaxy S2 phones is pretty much legendary, which is why I'm surprised about this power saving feature. Reviews boast quick boot times, but I would argue that a regular wake time is much more useful and realistic to have. I do understand the basic premise that a powerful phone consumes more battery, but that didn't make any other dual core phone I've seen require this precaution.
Therefore, why is it that others forego this feature if it ultimately saves so much battery that Samsung has made it a default feature on their latest phones?

Updated the OP with a video. Please view and tell me if this is the norm.

I watched the video, mine is not that slow delay.

justwonder said:
I watched the video, mine is not that slow delay.
Click to expand...
Click to collapse
+1 return it
Sent from my SPH-D710 using XDA App

I wouldn't return it Hold tight for custom rom.
I'm sure tweak will be around the corner to improve wake up response

sling said:
I wouldn't return it Hold tight for custom rom.
I'm sure tweak will be around the corner to improve wake up response
Click to expand...
Click to collapse
Funny how mine has all my apps on it... (over 40) and a **** load of music... And for the life of me I cant get it go lag like that.... I had a refurbished evo 3d that did that... I called sprint.after factory reset and.a few battery pulls... Id just return it.
roms dont fix all bugs let alone one random wake lag problem and the op may have to deal with it as most of us dont have lag like that...
@op if you got it from a store id bring it in.... if a rep says its suppose to do that.... Tell them your older android phone didnt do it... Then ask to speak to a manager
Sent from my SPH-D710 using XDA App

Yeah... I had a feeling it was worse than it should have been. Though it's true a custom ROM could fix it, it would probably implement a fix similar to Soft Locker (which is obviously shunned for its battery draining ability). Also, I'd much rather have a device in proper working order to begin with. The Best Buy I got it from only had 2 on launch day, so here's hoping I find one that has it in stock.
Thanks for all the replies.

My delay is similar to the video. How does everyone else compare after seeing the video?
Sent from my SPH-D710 using xda premium

I had the same issue. Move the pic from ur sd card to ur internal. Open in using myfiles and set as lockscreen
Sent from my SPH-D710 using xda premium

Thanks. Stupid question but how do I move it. I only know how using root explorer on a rooted phone.
Sent from my SPH-D710 using xda premium

Xperia Ion price drop

Hey guyz..anyone have idea why did they drop the price of xperia Ion? Does it have bugs??
Sent from my LT22i using xda app-developers app

sid.8491 said:
Hey guyz..anyone have idea why did they drop the price of xperia Ion? Does it have bugs??
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
No its probably due to it not being a popular enough model so they are clearing stock. The phone is great.

Spectre51 said:
No its probably due to it not being a popular enough model so they are clearing stock. The phone is great.
Click to expand...
Click to collapse
should i sell my P in order to buy Ion?
Ion does not have much custom rom's developed i guess...

sid.8491 said:
should i sell my P in order to buy Ion?
Ion does not have much custom rom's developed i guess...
Click to expand...
Click to collapse
I think you should wait for the SP. Ion is also a great device but its an year old. So, further updates can be an issue
Sent from my Xperia S using xda premium

sid.8491 said:
should i sell my P in order to buy Ion?
Ion does not have much custom rom's developed i guess...
Click to expand...
Click to collapse
Ion without custom rom is faster than P with custom rom
Wait for the SP or buy an Ion.

. The phone is great.[/QUOTE]
+1

Att stopped selling the ion
Sent from my LT28at using xda app-developers app

i bought my ion through sonystore with att 2 year contract for $50. i gotta say..... it's such a piece of sh*t. the only good is that it looks like a professional business phone, and it feels very solid. the rest are just terrible. it has the most (not one of the most) terrible battery life among every smartphone after updated to ics (but on gb it's actually not bad). its camera can barely focus and the picture color is absolutely off (yellowish to be exact, so if you have a white gf, she may look like an asian gf, and i am seriously not joking). a lot of browser, games, facebook, and other apps withdrawals (means that it suddenly closes itself without any notification) while USING these apps, but this issue is in ics only. its wifi/cell signal isn't that great either, drop calls and slow wifi is often. I have tried software repairs for more than 10 times, and here are the major complains (there are more issues) i have about this phone
i mean seriously sony? being a big fan of you since the walkman age and this is what you become? GG. i have to bear with this phone for another 1.5 years. wish i had chosen another phone.. even the non-innovative but reliable iphone
sorry for being emotional, but if you can bare with all these bugs, go for it. if not, i recommend wait for its jelly bean reviews and see if these are fixed

Try factory reset. I never faced that problems and i havent heard of them before.
There are also some mods for stock ics, try them out.

I will say I love my Ion but my at version has been having allot of issues recently. For a long time it was very stable but the last few months I get allot of random reboots and system freeze. It does it on all firmware versions even on stock ics. To me it seems to be hardware related. It would be silly to buy this phone now with newer ones coming out. Sony does seem to have a good thing going and even though I plan to get a Z I want to see what else they put out before I do. The new rumor is the Z will drop on T Mo soon.

Ion is getting Jellybean update...what else we needed, right :beer:
Sent from my LT22i using xda app-developers app

The thing is P is very good phone, does not have single bug and we can see the display clearly due to its awesome White Magic Technology.
I'm afraid Ion would not have good display and it would have bugs as people are reporting here.
Sent from my LT22i using xda app-developers app

My first ion I had multiple issues with so I called att and they sent me a replacement ion.. After a few months with the replacement, I started just having constant issues again such as constantly losing signal and I am in a strong signal area... So I would always have to stay connected to wifi to even use data stabily.. I have done factory resets etc... Anyway I called att about it on Tuesday and they are now sending me the TL as a replacement. I have a feeling a jelly bean update would really help out the ion... But hard to say.. I will just have to enjoy my TL.. It seems like an awesome device too.
Sent from my LT28at using Tapatalk 2

Yea after seeing Sony and ATT have dropped the Ion I was wondering if i may get a TL hmmm. In my area we have one spot with 4g and I have been bouncing in and out of it allot recently. So I really think the LT28at has a radio issue seeing as when it switches back and forth is when data gets stuck. Also there is the garball issue when answering or trying to make a call sometimes. Reboots fix it but only till it does it again. Every once in a while I get a random reboot. Guess I will just need to talk to ATT.

zackspeed said:
Yea after seeing Sony and ATT have dropped the Ion I was wondering if i may get a TL hmmm. In my area we have one spot with 4g and I have been bouncing in and out of it allot recently. So I really think the LT28at has a radio issue seeing as when it switches back and forth is when data gets stuck. Also there is the garball issue when answering or trying to make a call sometimes. Reboots fix it but only till it does it again. Every once in a while I get a random reboot. Guess I will just need to talk to ATT.
Click to expand...
Click to collapse
Are you getting the garbled issue using the stock AT&T firmware?
Sent from my Sony Xperia™ Z

zackspeed said:
Yea after seeing Sony and ATT have dropped the Ion I was wondering if i may get a TL hmmm. In my area we have one spot with 4g and I have been bouncing in and out of it allot recently. So I really think the LT28at has a radio issue seeing as when it switches back and forth is when data gets stuck. Also there is the garball issue when answering or trying to make a call sometimes. Reboots fix it but only till it does it again. Every once in a while I get a random reboot. Guess I will just need to talk to ATT.
Click to expand...
Click to collapse
i believe your lt28at is using ics international firmware. switch back to any att firmware or gingerbread international firmware will solve the problem
well at least i don't have the garbled issue when answering/making call on any att firmware or on gingerbread international firmware

No it does not do the garbled thing on ATT firmware but the other issues persist. I am also starting to get allot of data drop issues. For no reason it will switch to E or plain 2g for no reason. Reboot and its fine again. Even on ATT firmware when it switches from LTE to 3g the system will hang or it will reboot. It is very odd.

Got my ion LT28h in feb 2013,
No issues since, Great device but battery could have been better..
hope JB updates solves it..

Had mine since July 2012. Only issue i've ever had was a battery bug, which others have posted about (percentage gets way off, but battery life remains normal). It happened again just recently, and i can confirm, in my case at least...booting the phone without the sim car...booting back down and starting it again with the sim card...completely fixes it. However, most posts mention all kind of calibrators w/ rooted devices, none of which did anything for me...its something to do with a simless start resetting something that i wasn't able to get to by any other means i tried.
AT&T is absolute shat in my area, has been that way since my first phone in 2001. My ion was no better with this, until recently i switched back to an international ICS, manually entered APN's...but flashed the .111 ATT baseband over it...my dropped calls have been cut well over half, it almost never happens...when before it would happen in my living room nearly daily. The baseband flash also removed the garbled call thing for me. I know there is some debate about how flashing a baseband does something 'weird', as it doesn't change the baseband version (but does apparently change some other deeper stuff)...all i know is this phone is working now like i'm on a completely different network than i used to be...
Not sure about the battery complaints...My year old Ion on ICS regularly out lasts my gf's TL w/ JB, with similar use (we occasionally trade, she likes the Ion's screen for video more). Only other things i notice is that the Ion is very slow to pick up a known wi-fi network, and gps, compared to the TL. The TL grabs gps in a basement within seconds. I can manually start the gps on my ion with gps status app, and control the agps state, but it will take minutes to get it indoors, and still isn't great outside. Same with wifi, my Ion can take 15 seconds to pick up my home network, but the TL grabs it in about 2 seconds consistently...might be a router thing, but it happens nearly anywhere i've tried.
So i've been happy with mine overall. The best 720p smart phone screen i've used so far, still love the 4 permanent buttons over the software options, and its been extremely reliable connection wise since the baseband thing. Its showing its age, but still plays games extremely well for the most part. Just wish it had better software support, but that goes with most hardware makers entirely.

I just picked up a new AT&T Ion from Craigslist for $50. I have been pleasantly surprised by this little gem and this is someone is has used the Nexus 4 and Galaxy S3. It runs very quick and Sony has done a very nice job with with the skin while introducing some unique applications.
The funny thing is it picks up signal better in my office that the previous phones.

Touch "gets stuck" on letters while typing

Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J

Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...

Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4

Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.

I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app

I get this issue when playing a game or typing.

pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.

Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.

Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly

This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.

That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4

player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.

OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:

danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates

I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app

sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.

danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.

So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?

danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.

Possible recent apps lag fix.

One thing I noticed with my phone that was laggy was the recent apps button. I fixed it by running art in developers option. Let it restart and let it do its android is upgrading apps. Once it does that let it boot up. Go back to developers option and change back to dalvic. Then it will restart and boot up again. After that check your recent apps button to see if it's quicker with no delay. Worked for me so let me know if it works for you.
Sent from the TermiNOTEr 4!

No change for me after doing that.
... sent from Tapatalk. Please excuse any typos ...

work for me

I only have about a half second delay from hitting the button until it shows up on screen. Is that really a problem? Lmao

Nitroglycerin said:
I only have about a half second delay from hitting the button until it shows up on screen. Is that really a problem? Lmao
Click to expand...
Click to collapse
It has been repeatedly posted by different users and on the other note forums as an issue for some. There's a post sonewhere on this forum claiming Samsung acknowledged the delay. A 1-2 second delay is annoying and unnecessary on a new flagship phone. Regardless it worked for me.

brittoking said:
It has been repeatedly posted by different users and on the other note forums as an issue for some. There's a post sonewhere on this forum claiming Samsung acknowledged the delay. A 1-2 second delay is annoying and unnecessary on a new flagship phone. Regardless it worked for me.
Click to expand...
Click to collapse
Don't have a delay anymore after doing this.
Sent from the TermiNOTEr 4!

I noticed this when I switched back to dalvic so that I can access my private mode files (doesnt work on art!). My device was faster overall on art and I can't wait for android L so I can use art exclusively.

borijess said:
Don't have a delay anymore after doing this.
Sent from the TermiNOTEr 4!
Click to expand...
Click to collapse
Yes, I was agreeing with you. Tried it and while the recent button was even faster on art, switching back to dalvic has definitely made a difference for me. Thank you for the tip.

brittoking said:
It has been repeatedly posted by different users and on the other note forums as an issue for some. There's a post sonewhere on this forum claiming Samsung acknowledged the delay. A 1-2 second delay is annoying and unnecessary on a new flagship phone. Regardless it worked for me.
Click to expand...
Click to collapse
Well, I'm glad it worked for you. Seriously.
Honestly though, if anyone is legitimately annoyed over a second or two delay, then your lives must be perfect in every other conceivable way. Sure, it's 2014, and I get it, but c'mon. A 1-2 second delay is nothing.

Took like 25 mins to change over to ART but this worked for me, thanks. The delay was annoying even in my far from perfect life.

I tried this and didn't see much difference between ART and dalvik. There was a lot more lag on ART for me and the recent apps still had a delay.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

Did nothing for me but worth a try

While I currently only have about a 1/2 second delay, I wonder if it will slowly creep back to being slow over time.
Also, how does it calculate what is recent? Is it a set time period or just a list of the last X apps used?

Likely last used. That's what it seems anyway
Sent from my phone using Tapatalk

didnt work for me
I have the Canadian rogers version and those steps did not work for me. Cannot wait for Android L update come Sammy push the update.

I have not had any lag with this button since the day I got it. A friend of mine who is on Sprint has a delay. Annoying? Yeah maybe a little but if your schedule is so tight that a 1 second delay is going to cause mass chaos, you really need to look at your schedule and your priorities.

Bassplayrguy said:
I have not had any lag with this button since the day I got it. A friend of mine who is on Sprint has a delay. Annoying? Yeah maybe a little but if your schedule is so tight that a 1 second delay is going to cause mass chaos, you really need to look at your schedule and your priorities.
Click to expand...
Click to collapse
:silly:
too bad there's no smiley for rolling my eyes... when someone upgrades to a new phone, you'd expect it to be faster. 1-2s isn't that bad "in the grand scheme" as you and a couple others illogically point out. the difference is pressing this button more than 10-20x a day, it starts to make you wonder what's wrong with this phone.
lastly, it's sad that you felt compelled to come into a thread and throw your judgement around on other people's lives. i could say i feel sorry for you that your life is so slow and lackadaisical that you're able to easy tolerate delays throughout your day. but i wouldn't do that.
onwards and upwards on your slow climb to nowhere :highfive:

slackercow said:
:silly:
too bad there's no smiley for rolling my eyes... when someone upgrades to a new phone, you'd expect it to be faster. 1-2s isn't that bad "in the grand scheme" as you and a couple others illogically point out. the difference is pressing this button more than 10-20x a day, it starts to make you wonder what's wrong with this phone.
lastly, it's sad that you felt compelled to come into a thread and throw your judgement around on other people's lives. i could say i feel sorry for you that your life is so slow and lackadaisical that you're able to easy tolerate delays throughout your day. but i wouldn't do that.
onwards and upwards on your slow climb to nowhere :highfive:
Click to expand...
Click to collapse
AGREED. I was searching for this exact problem when I found this thread. I only bought a Note 4 because I broke my Note 2, my thoughts were 'Well, I guess i'll have a faster phone?' even If its 700$... imagine my dismay to find the phone SLOWER than my previous one. my life is far from perfect, which is why spending an extra 400-500 for a note 4 over a note 2 means I expect speed. and you know this, maaaaaaaaan.

After disabling multi window the lag is almost gone. I think the lag is due to figuring out wich of the recent apps suport multi window. it's definitely a software optimisation issue as the galaxy s6 doesn't have this problem and it also supports multi window. I don't know if it is as complex as the multi window of the note 4. Try it and tell me if this helped. Sorry if this has already been posted, but honestly I didn't read all the posts in this thread

art question
Where is the art setting in developers mode? I looked over every button and can't find it.

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.