Develop Bugs

issue with the game Cordy in controlling

maybe this is the multitouch issues people are talking about, but i've tried other games with similar controls and i had no issues, so i'm assuming it's just cordy, but i'm hoping someone here can double check with me before i go send the company an e-mail.
when i try to play, if i'm holding back, i can't jump. no matter how many times i press the jump button if i'm holding back it simply will not work.
also many times holding forward and pressing back sometimes causes you not to jump.
i've tested it on my asus transformer, and my nexus one, and both work, the nexus one not so much but it still does.
so i'm assuming that it's either a multitouch issue with the phone, or just an issue with the app and ICS, which is what i'm hoping since i've tried other games with controls in the same spot and they worked just fine.

just want to bump this, but come on? can no one take 5 minutes out of their day and download a free app and test this?
here i'll make it even easier, the market link
https://market.android.com/details?id=com.silvertree.cordy

I also have this issue, sometimes multitouch doesn't workd (OR i run left/right OR i jump), i think is the classical multitouch bug (if i switch from cordy to multitouch tester i can see the bug, and when you are in cordy simply lock and unlock the screen to remove the bug).

matteventu said:
I also have this issue, sometimes multitouch doesn't workd (OR i run left/right OR i jump), i think is the classical multitouch bug (if i switch from cordy to multitouch tester i can see the bug, and when you are in cordy simply lock and unlock the screen to remove the bug).
Click to expand...
Click to collapse
thanks for the reply! i just tried it and it worked. also loaded back into it again and had no issues from the start. very strange bug, but glad it has an easy fix for when it happens.
thanks!

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to

Your hands are really dirty or really dry. Try moisturizer or something.

Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.

Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.

@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.

I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.

I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.

I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.

My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.

I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus

gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.

I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk

Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...

I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA

I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.

I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0

Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.

TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!

[Q] Short swipes not recognized?

I've been having this issue since JWR66N, and it persists to JSS15Q as well: In most games (Temple run 2 and Squarescape for example), when I swipe on the screen for a short distance (which is normal what I usually do on phones since it doesn't require much movement of the finger), the game won't recognize the swipe and so won't execute the action (ex: jump or slide for Temple run 2, or move in the swipe direction for Squarescape). Longer swipes are recognized normally though.
The thing is, when I enable pointer location in dev menu, the trails are displayed correctly after each swipe, meaning the swipes got recognized by the nexus, but not transferred to the games. Thus I don't think this is related to multi-touch issue or other popular touch issues many people seem to have.
Since this is my first time using an android tablet, I'm wondering if this is normal, or some kind of defect on my unit. I have used many phones, android, ios and windows phone, and also ios tablets and never has any device failed to recognize these kind of swipes in games.
So, any idea why this is happening?
//PS: this happens consistently, not just randomly. And it happens when the nexus is very cool and still have a lot of free memory also (Squarescape is a very light game)

Ehhh... anyone?

Master619 said:
Ehhh... anyone?
Click to expand...
Click to collapse
I have this problem as well. It is related to the touch screen issues that most people experiences prior to the update. I suppose there are still things Google needs to patch up.

[Q] Intermittent Touch Input Issues

Right now my wife and I both have the note 8.0 (I used to have the note 10.1 until it slid off my roof on the interstate), and there have been a periodic issue with it not responding to touch input.
Intermittently, and at random intervals, the touch input just stops responding. It doesnt delay response or respond incorrectly, it just acts like it never recieved the touch input at all. Playing games, searching on google, typing an email, using s note, etc. It can happen anywhere and anytime.The game or application continues to run, the only hiccup seems to be the touch input not being recognized. Usually, it only lasts for a few seconds, 1-5 I would estiamte.
I have tried a number of settings changes, and even a master reset, and the issue persists. I have a few thoughts on the matter, but don't seem to be able to resolve it.
Has anyone else been experiencing this?

phoenixbennu said:
Right now my wife and I both have the note 8.0 (I used to have the note 10.1 until it slid off my roof on the interstate), and there have been a periodic issue with it not responding to touch input.
Intermittently, and at random intervals, the touch input just stops responding. It doesnt delay response or respond incorrectly, it just acts like it never recieved the touch input at all. Playing games, searching on google, typing an email, using s note, etc. It can happen anywhere and anytime.The game or application continues to run, the only hiccup seems to be the touch input not being recognized. Usually, it only lasts for a few seconds, 1-5 I would estiamte.
I have tried a number of settings changes, and even a master reset, and the issue persists. I have a few thoughts on the matter, but don't seem to be able to resolve it.
Has anyone else been experiencing this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2338394
Its a known problem, an update to 4.2.2 seem to have fixed it. But if you are using the AT&T LTE model(Like me) or Rogers then you'll have to wait for the update which god knows how long the carriers will take. Personally I am trying to see if I can isolate the issue.

Havent yet looked at the 4.2.2 and dint really know it was available. Havent had much time to do much with my devices in the last couple of months. My wife and I are both using the wifi only models.
I tend to believe the issue is primarily happening due to a slowdown on the system while processing certain sync functions or i/o functions. I tend to notice it more while connected to wifi and have also noticed at least one cloud sync error when the issue happened.

Strange edge lighting behaviour

So I have a really strange thing going on with edge lighting which is driving me crazy.
Whenever I play Elder Scrolls Blades the edge lighting appears but only in the bottom of the screen. As far as I been able to tell this only happens in this app though I can't be 100% sure.
Now what is strange other than it happens only in the bottom of the screen is that it keeps happening every few seconds, there is no notifications received and it happens, if I disable edge lighting it still happens, no matter to what effect I set the lighting it always happens in stock blue.
I can't possibly figure out what is this and I tried everything, any ideas would be appreciated.

Same thing here, in at least 2 games...
Thought it was related to spen, but it seems not...
Tried to disable Game Launcher but still got these random bottom screen notification pulse... And stock blue aswell. Got no clue atm

Thanks for letting me know I'm not the only one experiencing this. I tried literally everything and nothing seems to fix it. What's also weird is that the lighting comes in irregular intervals, sometimes just going crazy and sometimes appearing much less.

I have just discovered this issue appears in all games so it's a bigger problem then I originally thought. If disabling the game launcher does nothing then it makes it even more strange and annoying.

Yeah, same here, happens on basically all the games.
Maybe related to game booster?
Let's try to compare our setup : are you using any notification enhancement app? (like aodNotify)
Are you using your spen while playing?
But yeah, this random glow line **** is driving me crazy too!

Currently I am using aodNotify though I tried uninstalling it and the problem persists, I also have goodlock installed and the edgeslighting+, same thing with and without it. I am not using the spen, but I have tried just taking it out while the game is running and leaving it out for 5 mins, no change. I have disabled and enabled the stock edge lighting as well and the problem is still there. Nothing seems to effect it. Its ridiculous

i tried on mobile legend adventure, no problem on it, perhaps a scaling issue?

Will try to tweak full screen mode.
Increasing dpi doesn't change the weird thing, neither switching from Samsung stock launcher to Nova...
Also I'm using gestures based navbar, but I also tried with or without tips display, standard navbar... Still occurring.
Did you go from a scratch Note 10+ or used SideSync to switch? (I was coming from a Note 8)

I don't think it has anything to do with scaling, I tried setting the game on full screen and automatic, both giving the same results.
I used Smartswitch from Note 9.
Later today the camera effect from aodnotify started appearing in the game aswell (landscape mode), along with the edge lighting.?
I uninstalled aodnotify afterwards, found out there is a aodnotify Manager plugin which stays after uninstalling the main app.
Uninstalled the plugin aswell, opened edgescreen from the system app and cleared cache.
It was showing the app was using RAM with high frequency.
I don't have the time to check now does this fix the problem but will let you know once I do.
The only other thing left to do if this doesn't work is to clear edge screen data.

Will try this aswell, and restore all the notifications and edge lightning settings...

What I wrote above didn't work so I disabled the option for edge screen to show on top of other apps, so far this seems to fix the problem.

Unfortunately I was wrong and nothing above fixes the problem. I also wiped the entire edge screen memory, no effect. This is the weirdest thing I ever encountered in my years of Samsung phones and it's extremely annoying that there is no fix.

Strange, I don't have any issue.
Did you try with and without locking the screen orientation to see if edge lightning follows settings as it should?
I personally only use auto orientation.

I also use auto rotation and it happens the same way in landscape and portrait, the most annoying thing is that it happens really much, like 2-3 times in 10 seconds, or sometimes doesn't happen for few minutes then starts going like crazy, and as I said before there is no notifications or anything.

Same here, auto rotate on, only occurring during games.
I don't even know if I can debug which process is running these random edge notifications, without dig into tons of log files...
And if not, I guess I'll try to factory reset and re-sync again..

Its incredible that a factory reset seems like only possible solution left but I hope maybe some future update will fix it since I hate doing factory reset. Please keep me posted if you discover anything new.

Hating doing it aswell but this is too damn annoying..
If no clue, I'll go for a restore without restoring system settings... Maybe some notifications behaviors have been messed up
I'll keep you in touch for sure

Tried to wipe cache partition, still no clues...
Did this also got triggered in portrait mode game?
So confusing...

Yes it happens in all games no matter of the screen orientation. I really have no more ideas aswell

Got some news, another post is talking about this : https://forum.xda-developers.com/galaxy-note-10+/help/strange-blue-bar-games-t3963939
Seems related to the new game booster feature "temp and cpu monitoring"
Will try to disable this for a specific game and see...