That's what is being called now, where you get a momentary line across your screen, or the page jumps by itself for no reason.
At first, it was only just an annoyance, but now it has become a pain in the neck, starting today. What was a bit too often occurrence had today become a noticeable problem.
It is happening no matter what rom, Application or an page I'm on. I can be reading something, when the page will for no reason jump to where it was before for a moment, then come back to its previous position. I am even finding that if I am responding to a post and am quoting it, the cursor will jump up in the quote while I am typing, causing me to mess up the quote and having to back out of the response all together and start over. What's more what was happening infrequently is now becoming a few times an hour.
So I am wondering if anyone is experiencing this increase in the problem lately, and has anyone had any luck in finding a solution?
Sent from my SGH-T999 using XDA Premium HD app
Kamau54 said:
That's what is being called now, where you get a momentary line across your screen, or the page jumps by itself for no reason.
At first, it was only just an annoyance, but now it has become a pain in the neck, starting today. What was a bit too often occurrence had today become a noticeable problem.
It is happening no matter what rom, Application or an page I'm on. I can be reading something, when the page will for no reason jump to where it was before for a moment, then come back to its previous position. I am even finding that if I am responding to a post and am quoting it, the cursor will jump up in the quote while I am typing, causing me to mess up the quote and having to back out of the response all together and start over. What's more what was happening infrequently is now becoming a few times an hour.
So I am wondering if anyone is experiencing this increase in the problem lately, and has anyone had any luck in finding a solution?
Sent from my SGH-T999 using XDA Premium HD app
Click to expand...
Click to collapse
It is a well known CM 10.1 issue. Not sure which nightly this started occurring on but the fact is they are nightlies. Any known issues will be fixed. As far as the issue increasing is concerned, it's happened to others but for some not at all. Some occur with these 3.4 kernels so it can also depend on the kernel you're running. Keep track of your kernel thread. The fact is ALL devices even if it's the same model may handle things differently. You're just gonna have to stick it out as more nightlies come through, hopefully fixing this ghost screen increase for you and other users.
Sent from my Nexus 4 using xda premium
I was using reddit is fun for a couple hours today and did not encounter the issue (with nightly 4/14). Was terrible with previous nightlies. Terrible as in every damn time I scrolled the page. If you haven't tried 4/14, or the soon to be 4/16, that's your first step.
LuxigiBull23 said:
It is a well known CM 10.1 issue. Not sure which nightly this started occurring on but the fact is they are
. Any known issues will be fixed. As far as the issue increasing is concerned, it's happened to others but for some not at all. Some occur with these 3.4 kernels so it can also depend on the kernel you're running. Keep track of your kernel thread. The fact is ALL devices even if it's the same model may handle things differently. You're just gonna have to stick it out as more nightlies come through, hopefully fixing this ghost screen increase for you and other users.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was thinking about trying a different kernel, but the last rom I flashed other day had a different one in it, and it did the same thing.
Thanks for the info though. I was just wondering about the increase because it seems to get worst each time I flash. Basically though I was just putting info out there in case it could be helpful.
Aerowinder said:
I was using reddit is fun for a couple hours today and did not encounter the issue (with nightly 4/14). Was terrible with previous nightlies. Terrible as in every damn time I scrolled the page. If you haven't tried 4/14, or the soon to be 4/16, that's your first step.
Click to expand...
Click to collapse
I'm not on a nightly. I'm running a stable Deviant Xone, but I am more than sure it's not the rim since I have heard of the same issue on other roms.
Thanks anyway. As I do flash other roms, I will keep that in mind.
Related
Okay I don't know if this is a bug in every Android version that still hasn't been fixed or is it an app that's causing it.
What happens is when I would be using an app like for example Google talk. I would try opening YouTube it would open calculator. And if I try opening messaging it would still open calculator. No matter which app I'd open it would open the wrong app. And I either have to kill all apps or restart my phone
I had this issue only my G2, my Nexus S, Anyone else having this?
Can't recall if I had it on my Sensation or not...
Sent from my Galaxy Nexus using xda premium
This has never happened to me. Are you completely stock?
Sent from my SGH-T989 using xda premium
I have had a similar error on multiple versions of android where you hit the back button and it starts to cycle through several different apps.
Yup happens to me on a few occasions. It just cycles like axion said
If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium
I've seen this once on my Galaxy Nexus only, never on a Nexus S, of GS2. A reboot seemed to resolve the issue. I've not seen it again since.
joshnichols189 said:
If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium
jonathan3579 said:
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.
thequinox said:
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.
Click to expand...
Click to collapse
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium
Happened to me too. Usually helps to get rid of all alps in multitasking menu.
jonathan3579 said:
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.
krohnjw said:
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
Click to expand...
Click to collapse
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210
Lowtrash said:
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210
Click to expand...
Click to collapse
No, I've just backed down the stack. I am curious as to the trigger for the behavior though as it is a rather uncommon occurrence.
krohnjw said:
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.
Click to expand...
Click to collapse
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that? To add to that, if a device pre-ICS did have this problem... Would it not be considered defective? *Keeping in mind that most people don't have the problem.* I have absolutely no issues no matter the number of apps I have open. So is my device defective because everything opens as it should? As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...
jonathan3579 said:
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that?
Click to expand...
Click to collapse
Where do you see this claimed to have happened on any pre 4.0 rom?
I had this issue only my G2, my Nexus S, Anyone else having this?
Click to expand...
Click to collapse
jonathan3579 said:
I have absolutely no issues no matter the number of apps. As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...
Click to expand...
Click to collapse
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....
krohnjw said:
Where do you see this claimed to have happened on any pre 4.0 rom?
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....
Click to expand...
Click to collapse
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.
Yep I know what you mean, happens to me on Google Music.
Th easiest solution I found was to force stop the app that's bugged out.
I've had this too. Swiping away the app I'm trying to open and the one it is opening instead has fixed it for me.
jonathan3579 said:
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.
Click to expand...
Click to collapse
Defective software I have no issue with - that's a harsh classification for a bug, but not incorrect.
Your statement of "Return it" followed by "most of us do not have these issues" seemed to imply a belief that the physical unit must be defective (in comparison to a unit that did not experience this issue) rather than a behavior or set of behaviors causing as software issue as most users do not experience this. Thereby returning would resolve the issue.
Given the symptoms present when this occurs I can't imagine this to be true i any way, shape or form. Especially given that this bug has existed since 4.0 hit AOSP and on builds for the Nexus S as well (hence why it's absurd to blame this on a singular hardware fault of a single device).
I am interested in reproducing the issue, or capturing a logcat the next time it occurs (it only seems to happen when I am in the car unfortunately) to see if the WindowManager of ApplicationManager are supposedly starting the proper activities or the issue might lie with the package manager.
I've had this happen when i open a lot of apps without closing them and use the multitasking button to switch between apps.
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
waltcoleman said:
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
Click to expand...
Click to collapse
Any special wi-fi config? (That's the culprit in my case.)
garwynn said:
Any special wi-fi config? (That's the culprit in my case.)
Click to expand...
Click to collapse
No...never installed the hotspot hack, did have foxfi installed, but did not reinstall after reloading ff18.
im also having the same problem as well, and the problem has became worse and worse,what started off as once or twice a day,is now at least occurring every 10 min.I think im about to downgrade right now to stock gingerbread and see what happens
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
rocket321 said:
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
Click to expand...
Click to collapse
U can always unroot back to el29(gingerbread)i was having the same problems and now i can enjoy my phone
Sent from my SPH-D710 using xda premium
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
R0CKSTAR3N3RGY said:
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The power button seems to be a common cause of random reboots and that's what I'm leaning towards now as no other software fix has resolved the problem. Supposedly Sprint ordered me a replacement to swap out phones. I'd definitely recommend trying a different Kernel if on FF18 and if that doesn't fix it, try rolling back to EL29.
I know CM10 has been made "stable" on this device but I just have a few questions regarding it. My wife has been using the nightlies since the first previews were available and I'm not sure if our issues are common or something I am doing wrong.
She is currently on a nightly from a few days ago but these issues have persisted for about a month. I have done a full wipe and flash multiple times and we still have the same issues.
Skype: She can't barely here the other user and the other user hears nothing but static. I have tested with multiple other users. I have wiped data for Skype and reinstalled it, still has the same issue.
Force Close - Many apps. Happens randomly and it's not the same apps every time. I feel it is an OS issue and not an app issue.
Speakerphone is randomly activated by default. She usually has to tap the mic button a few times (deactivate, reactivate, deactivate) in order to get it switched to the handset.
Depending on what nightly she flashes the caller on the other end gets echo. It hasn't been happening with recent flashes but every couple weeks it pops up again for a nightly and then disappears.
I understand there are many issues due to Samsung not releasing sources, etc, just want to verify I am not alone. I have looked through the forums and see some people have some of the issues from time to time but I am hoping for some verification.
Thanks for everything.
I noticed the same thing a few days ago on Skype but didn't think much of it at the time.
Just checked again and sure enough I'm having the same experience you are with static.
Flashed back to stock and the problem disappears.
Must be a problem with CM10.
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
The issue existed before Stable and it exists in Stable. I just tried [ROM] AOKP(Jellybean 4.1.2)Task & Ktoonsez (11/18) and the issue with Skype exists there as well. If anybody knows of a AOKP or CM build that doesn't have any issues I would swap over. I have been wiping and flashing roms like crazy lately and I we really can't stand stock samsung rom. I may end up selling the phone and picking up something different, it's quite frustrating. Last time I buy a Samsung phone, that's for sure. They basically **** on devs.
DarthDerron said:
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
Click to expand...
Click to collapse
I see you have the same phone as my wife. Any chance you have time to test Skype on your current rom? If so thanks in advance, I appreciate it.
Sent from my LG-E973 using xda app-developers app
Thanks guys. Just going to return her to stock and sell it. Going to find a device with better support from manufacturer.
Sent from my LG-E973 using xda premium
Well, it's been about 4 months since I upgraded to this phone, and I've had the same issue, whether it be on ICS (stock, Lifeless, Imperium) or on JB (stock, Lifeless, Imperium)-haven't flashed CM. The issue is, and as far as I can tell, at random, my media sound (YouTube, music, videos-no matter the player) quits on me, up until a reboot, after which it's fine until the next random time it happens. Sometimes I'll go several days with no problems, and other times it'll happen, and then 2 minutes after a reboot, happen again. I've done a little troubleshooting, and haven't had any leads. So, I wanted to put this out and see if there is anyone else having a similar issue, or if maybe something is just up with my specific device.
Sent from my LG-LS970 using xda app-developers app
I am not saying this is the cause but on rare occasions the audio hardware/controller will start to fail. Out of the thousands of phones I've worked on I've seen this only a handful of times. Another cause is a fault in the LG software itself but I would expect to see more reports of this issue if that was that case.
I suggest flashing over to CM and see if you can duplicate it. If so then the audio hardware is suspect. If not, then yet anther LG software bug has shown up.
Lokifish Marz said:
I am not saying this is the cause but on rare occasions the audio hardware/controller will start to fail. Out of the thousands of phones I've worked on I've seen this only a handful of times. Another cause is a fault in the LG software itself but I would expect to see more reports of this issue if that was that case.
I suggest flashing over to CM and see if you can duplicate it. If so then the audio hardware is suspect. If not, then yet anther LG software bug has shown up.
Click to expand...
Click to collapse
I just thought it was strange that it's happened on both OS's and all the ROMs, so I'd leaned toward it being my device. No permanent issues, mostly just an annoyance. Since I rely on my phone for work and such, I've been hesitant on flashing CM. It also hasn't gotten worse or better over time. The most random thing I've experienced on a phone. Oh well, it's not enough of a problems to have to deal with Sprint to try and get it replaced. Mostly just wanted to see if anyone else had experienced it.
Sent from my LG-LS970 using xda app-developers app
Since I've been seeing and experiencing issues with the screen going out and having to use the five to six finger touch to get it to work right, I'll just make this thread about it. Any fixes? I'm on CM12.
I'll post here simply as a voice to confirm I've seen the issue. Touching 5 fingers to the screen immediately fixed it for me the time or two I've seen it personally. Not frequent by any means for me, but somewhat maddening when it does occur haha
Edit: When I've seen the issue, it always seems to be post-call
ohlin5 said:
I'll post here simply as a voice to confirm I've seen the issue. Touching 5 fingers to the screen immediately fixed it for me the time or two I've seen it personally. Not frequent by any means for me, but somewhat maddening when it does occur haha
Edit: When I've seen the issue, it always seems to be post-call
Click to expand...
Click to collapse
Same here. I was hoping it would get baked into the roms or something since it's a ongoing issue.