Sometimes my LG Thrill doesn't process multi-touch input correctly, especially when I play games.
For example, on Shadowgun, since the movement control is on the left and the firing button is on the right, sometimes I can't move and fire simultaneously and wen it happens, it's persistent.
I'm running CM7 6/17/12 but has always been a problem for as long as I can remember during the ownership of this phone.
Anyone else experiencing this or probably an isolated issue?
Thx folks.
I've experienced something different:
When I touch down to swipe left or right, the screen shakes back and forth. Nothing a battery pull doesn't solve.
usually when that happens to me, I use a task manager to kill background apps and that fixes it for me.
Sent from my LG-P925 using xda app-developers app
Related
Ok so i am trying to determine what my problem is.. here are the symptoms. When i try and end a call i sometimes have to press multiple times or deliberately press and hold the end button and sometimes it doesn't respond pretty much at all. Also i am using go launcher and when i press icons that are in the dock bar they have the same issues. I also have similar issues when i text it's really annoying so is anyone else have similar issues?
Sent from my VS910 4G using XDA App
Same here. I've noticed that to hang up it takes a deliberate double tap. Also, the screen will sometimes become inoperable requiring a reboot. This has happened three times since first getting it. One note if that out happened twice stock, and once with decrapped 1.1
Any body else seen this?
Sent from my VS910 4G using XDA Premium App
I haven't seen it anywhere else, but I have seen the double tap on the end button to end a call. Seems to happen frequently. A "feature?"
Either way, it's annoying.
Running Go Launcher as well.
To me, it seems like it takes the screen a really long time to wake up from being off, in all cases - for example, dial voicemail and put the phone to your ear. When you get the prompt to put in your PIN, take it away and the screen comes on, try to punch the dialpad button immediately and it just won't work. I tried it as I was writing this and had to triple tap the button.
Same thing with the lockscreen (still on the stock lockscreen for now). The screen will wake up and it takes a second or two to even start to register finger swipes. It's really annoying...
Speaking of phone lockup, I received a call a few days ago and the phone froze - I couldn't answer the call, or do anything, all the while the phone just kept ringing. Had to pull the battery. I'm still on the stock ROM.
Me too! I had a call and it froze. Battery pull as well. Also, forgot to mention I am using open home launcher.
Sent from my VS910 4G using XDA Premium App
Yep it's a bug either in LG's function to turn on and off the screen in Android, or the kernel drivers that enable/disable the touchscreen. There is about a 1 second delay to it.
I discovered this lovely bug while porting the AOSP lockscreen mod.
I'll run some more tests to see whether it's an android bug or a kernel bug. I'm betting it's android (something like the screen being turned on before the touch controller has had time to reinitialize itself, or something more complicated like a race condition of some kind...)
Either way, with cm7 around the corner, I don't think it's that big of a bug
thecubed said:
Either way, with cm7 around the corner, I don't think it's that big of a bug
Click to expand...
Click to collapse
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
AndroidCraig said:
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
Click to expand...
Click to collapse
Since he is the one working on getting it ported over, I think he has the best idea, and the only rule of cm is no asking for etas ;-)
Sent from my VS910 4G using XDA Premium App
I know there was a thread about this somewhere on here before, and I did a search but nothing came up.
Has anyone else have this come up in BetterBatteryStats? I remember there was a way to decrease the amount used by going to settings>sound and unchecking touch sounds and screen lock sound. I've had this unchecked for a while, but I still get a partial wakelock about this, and right now its showing 1 hr 9 min, about 204% ! Does anyone know what else could be caused by this? I haven't been listening to music, not watching anything, haven't even played any games today
Um, anyone? I still have this problem
Sent from my GT-N7000 using xda premium
Yes I do also and on most ICS..Havent figured it out yet either.
Did you also disable dial-pad touch tones?
They used to make AudioOut wakelock for me too..
Yea I have that unchecked as well. Every since I learned about this wake lock about 2 months back, I now keep all these settings disabled. But i recently in the past week or 2 kept checking betterbatterystats again and this always comes up at the top. During the day, i dont watch anything, if I play a game, im usually in class and always have the volume off (for media and games)
It would be good if someone figured this out
Sent from my GT-N7000 using xda premium
dr. xp55 said:
I know there was a thread about this somewhere on here before, and I did a search but nothing came up.
Has anyone else have this come up in BetterBatteryStats? I remember there was a way to decrease the amount used by going to settings>sound and unchecking touch sounds and screen lock sound. I've had this unchecked for a while, but I still get a partial wakelock about this, and right now its showing 1 hr 9 min, about 204% ! Does anyone know what else could be caused by this? I haven't been listening to music, not watching anything, haven't even played any games today
Click to expand...
Click to collapse
Did you install any program to boost volume like Volume + etc? They have profiles which Can cause wake locks, the sad part is poorly written programs Can cause wake locks even when profiles are off, I am not suggesting any program in particular but we wary of any betas. In my SG 2 I had to do a Nand Restore as even after deleting a program to increase volume had those wake locks. Surely keep all vibrations and haptic feedback off.
Sent from my GT-N7000
Ui
Princeomi said:
Did you install any program to boost volume like Volume + etc? They have profiles which Can cause wake locks, the sad part is poorly written programs Can cause wake locks even when profiles are off, I am not suggesting any program in particular but we wary of any betas. In my SG 2 I had to do a Nand Restore as even after deleting a program to increase volume had those wake locks. Surely keep all vibrations and haptic feedback off.
Sent from my GT-N7000
Click to expand...
Click to collapse
Hmmm, that could be it. I've installed dsp manager before couple times, even after flashing different roms, whether it was already loaded into the rom or I installed it as a stand alone. I'm currently, on liquid smooth and it wasn't in the rom, and I actually haven't installed it again. But obviously I've done full wipes and such where needed. So I don't know if that's still the issue.
What about haptic feedback on the keyboard presses?
Edit: I don't know know if removing haptic feedback on the keyboard helps for this issue, but i can certainly type better and faster now . I've always had hf on, on the keyboard. But i guess it's just a distraction. Hopefully this helps with the wake lock too
Sent from my GT-N7000 using xda premium
dr. xp55 said:
Edit: I don't know know if removing haptic feedback on the keyboard helps for this issue, but i can certainly type better and faster now . I've always had hf on, on the keyboard. But i guess it's just a distraction. Hopefully this helps with the wake lock too
Click to expand...
Click to collapse
It helped me when I had the same problem as you.
I had a very odd experience with my tablet last night. After a few hours of non-use, I picked it up to begin reading. Went to adjust the brightness level and pulled down the settings bar. I noticed the bar was behaving strange, like as soon as I pulled down, it would snap right back up. There was also a flicker at the bottom of the shade. Unable to access anything there, I went into my app drawer to do something else. As soon as I went in, things got even stranger. Apps began opening themselves. Two games in particular, Gunman Clive and Lep's World 2. I would watch as the game opened by itself, then once inside the game, I would hit quit. The app, would immediately re-open.. This happened several times over. After the first app stopped doing that, it began opening the second app. Tried closing that one several times the same way and watched it re-open the same way. I decided to go further in Lep's World once it opened again. I watched as the character began jumping(but, not walking) on his own. Exited this app. Next my Kindle opened up the settings for LMT launcher on it's own. It did this same thing with these 3 apps, almost as if something(or someone) has compromised by tablet. I could physically see the buttons being pushed for these apps and it was not being pushed by my finger.
Fed up, I attempted to restart via Quickboot. Just as soon as I opened Quickboot, instead of me having a chance to pick one of the boot options, it would pick Hot Boot for me. This happened a couple of times, but finally I was able to do a full reboot. After the full reboot, My Kindle started up normally and there seems to be no sign of anything like this happening since.
Has anyone ever heard of anything like this before? Please tell me I'm not hacked. I'm running hashcode's CM 10 with Nova Launcher if that makes any difference.
Sounds like your digitizer went nuts
Sent from my GT-P3110 using xda app-developers app
Try installing this app and enabling screen touches. At least then you can see where the Kindle is touching itself (as weird as that sounds:what: ). Just a thought.
http://forum.xda-developers.com/showthread.php?t=2124384
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
I have a problem that's almost identical to something similar. My settings bar behaves strangely and I get the flicker at the bottom of the shade. My apps start behaving strangely. It seems to happen about once a week. I believe it happens after my apps have been automatically updated. To solve my problem I run Clean Master app and select the memory boost and junk folders tiles. After the cleaning the problem goes away until it happens again.
Was your device connected to a wall charger when misbehaving? With some power adaptors it detects more than a touch for every real touch, which could explain the weird behaviour you described.
Sent from my Amazon Kindle Fire HD using Tapatalk 4
I have had similar problems in the past and, odd as it may seem, my issue was a dirty screen. You see, I noticed that several "touches" were occurring on a particular area of the screen, the area taken up by the d pad in minecraft pe. I believe that the accumulation of fingerprints and skin oils was enough for the screen to recognize a touch. It still happens from time to time and always stops when I clean my screen. I've found that a little bit of purel and a soft napkin work great. Good luck!
As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off
I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you
Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....
This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.
I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.
My Galaxy Tab S2 seems to lag for a couple of minutes when I first go to use it. This is after I've left it just on the side for a few hours or overnight (not from boot-up).
When I try to open an app it freezes then a few seconds later it does what it was supposed to do then it freezes again. I force close all but this doesn't really help until I've done it a few times.
I wasn't sure if this was something to do with the built in auto Wifi off so switched that off and it seemed to improve it slightly but it still happens. I tried using some auto WiFi off apps instead but they didn't even work.
After this first couple of minutes it then works fine. I uninstalled all apps and it was ok but it wasn't before long it came back. It wasn't particularly noticeable after any specific app.
Is there a way to analyse what is causing this lag in the background?
I'm experiencing the same problems. I wonder what could be causing this?
Sent from my SM-N976V using Tapatalk
I've noticed this for a long time. If you use a system monitor you will notice that the Disk reading will be at 100% for some minutes, leaving the tablet unresponsive.
I don't know how to identify which apps are doing the reading.
Kromitvs said:
I've noticed this for a long time. If you use a system monitor you will notice that the HD reading will be at 100% for some minutes, leaving the tablet unresponsive.
I don't know how to identify which apps are doing the reading.
Click to expand...
Click to collapse
First thing I do now is kill all running apps but still get some lag. A persistent app apparently.
Sent from my SM-T813 using Tapatalk