still flickering problem on .15 - logcat

[MysteriousDiary]

Hi,

since a few weeks now I've my transformer prime. First I had the .11 firmware, since today i've the .15 on my prime as well.

Pretty randomly it happens to me that my screen begins to flicker and the game becomes unresponsive - usually only within games. If i quit the app via multitasking button and start it again it usually just takes 1-2 minutes until it happens again. The only real solution is a restart.

got a short logcat, to me it looks like there is something wrong with the nvidia driver (?).

D/NvOsDebugPrintf(23496): NvRmChannelSubmit: NvError_IoctlFailed with error code 12
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)
D/NvOsDebugPrintf(23496): NvRmChannelSubmit failed (err = 196623, SyncPointValue = 7963782)

Does anyone have the same issue? So far this happened on pretty much games to me, so it doesn't seem to be a problem with the game itself. Developer options are set to standard, so force gpu rendering is off.

 

[Col.Kernel]

It is more prone to happen at the desktop for me than to start in a game.

Most of the time going into a game will correct it. A restart will not correct it.

I'll grab a logcat next time it happens.

 

[a Mandroid]

Are you rooted? Can you check what scheduler is being used using atp tweak (find it in development thread), and try switching it to no-op if its not that already.

If not rooted, try disabling force gpu rendering in settings>development options and then do a cold boot using vol down and power btn.

 

[MysteriousDiary]

Are you rooted? Can you check what scheduler is being used using atp tweak (find it in development thread), and try switching it to no-op if its not that already.

If not rooted, try disabling force gpu rendering in settings>development options and then do a cold boot using vol down and power btn.

Thanks for the reply. I'm rooted, but never used that tool you mentioned before. once i started the app cfq was selected, switched to no-op now and will try to reproduce the flickering.

what's the difference between cfq and noop?

 

[namebrandon]

I'm pretty sure I saw something about this being related to GPU memory being used up.. It seems androids OS-level task manager (which gracefully exits unused apps from memory when memory is low) doesn't watch GPU memory, only system memory.

Check open apps when this happens, and kill off anything GPU intensive / related that's running, and switch back to the app you want to use and see if it gets better.

 

[MysteriousDiary]

I'm pretty sure I saw something about this being related to GPU memory being used up.. It seems androids OS-level task manager (which gracefully exits unused apps from memory when memory is low) doesn't watch GPU memory, only system memory.

Check open apps when this happens, and kill off anything GPU intensive / related that's running, and switch back to the app you want to use and see if it gets better.

Thanks, will keep an eye on it.

@Mandroid
Happened again. Will do a cold reboot now and then see if it happens again. Maybe it really has to do with the GPU Memory or so. Sometimes I don't have it for days, and then when I play a bit more, which doesn't happen that often, I get this problem again until I reboot the device.

 

[di11igaf]

I'm pretty sure I saw something about this being related to GPU memory being used up.. It seems androids OS-level task manager (which gracefully exits unused apps from memory when memory is low) doesn't watch GPU memory, only system memory.

Check open apps when this happens, and kill off anything GPU intensive / related that's running, and switch back to the app you want to use and see if it gets better.

The gpu usually has memory dedicated to it that the system can't touch. It could be not quite enough, but this may be able to be increased in kernel.

 

[namebrandon]

The gpu usually has memory dedicated to it that the system can't touch. It could be not quite enough, but this may be able to be increased in kernel.

That's what I was thinking.. I just ordered my prime today.. do we have source already from ASUS for ICS?

 

[buxtahuda]

That's what I was thinking.. I just ordered my prime today.. do we have source already from ASUS for ICS?

Nope, don't think so.

Some time a long time ago, YouTube glitched for me. Never happened again..

Fast-forward to update .15, and on the second day I started to get some fuzziness all along the left side. Rebooted, everything was fine.

Last night, for about 10 minutes while streaming some Music (which started skipping... why?) the screen absolutely went berserk. It was amusing in a very soul-clenching way. The notification area would just flash in and out, and was missing much more than it was there. Then if I disabled my trackpad, the whole bottom-bar would wiggle. Portrait mode caused most of the screen to go static. Undocking didn't do anything, and using XDA premium just about stopped the bar wiggling (I would guess any app would have done the same, but who knows..).

After a minute of just letting it sit there, everything went right. Then I started killing off apps from the last few days, just for good measure. Haven't seen an issue since.


I'm thinking that even how the Prime is handling system memory could be a little off. But I'll watch all you to draw a conclusion

 

[MysteriousDiary]

Hm, it happened again too me and this time my multitasking bar was almost empty.

took a short videoclip of it. the quality is pretty bad and unsharp, but you can see how the screen is flickering. At this state I can't do anything in the game, but Android is still responsive.
http://www.youtube.com/watch?v=fOkdm8o8gg8

 

[demandarin]

Hm, it happened again too me and this time my multitasking bar was almost empty.

took a short videoclip of it. the quality is pretty bad and unsharp, but you can see how the screen is flickering. At this state I can't do anything in the game, but Android is still responsive.
http://www.youtube.com/watch?v=fOkdm8o8gg8

I had the flickering or screen jumping happen on some games initially. wasn't related to update as it happened several updates back. this only happened in some graphic heavy games. reboot solved it and never has happened again since. I think it was more of a compatibility issue with ICS than anything else.

 

[Blairware]

This was why I rolled back to .14

Well, one of the reasons. The other was a pathetic attempt to get back the best, but of course still unusable GPS performance to date, on .14.

Only had flickering/static screen events perhaps 2 or 3 times, but wanted to check out the "load any version" method (works like a charm)

Haven't had any issues, and wasn't bothered by update notifications until today.Anyone want to tell me how to blow off an update, permanently?