I've been having a very strange, but rare, problem when running 3D games. It seems to only occur with certain kernels. I have no idea what else could be causing it. It has happened to me only three times since I got my Vibrant in Sept, but it's pretty scary.
What happens it's kinda hard to describe and even harder to reproduce. When I play any relatively heavy 3D game the phone performs flawlessly then randomly freezes completely. The soft-key lights still react to touch and turn off normally, but I'm unable to restart by holding down the power key for 15 seconds, leaving no choice but to do a battery pull. While this is happening, the screen (frozen in the game) starts to present very bright thin horizontal transparent white lines. These lines will keep appearing until they cover the whole screen. In the end it looks like the screen had lost all colors except shades of green and the rest has turned white.
This has never happened with 100% stock, stock+Voodoo kernels, Bali, or Overstock (didn't OC). It has happened, if I remember correctly, with Dragon (didn't OC), some other kernel I can't remember, and, just now, with DragonMODz SSSJ (OC'ed at a mere 1.1GHz). Maybe it's a problem with OC-able kernels only? Maybe it has to do with uncapped FPS? Maybe it's a simple problem that is all over the forum, but I couldn't find it?
Any help/suggestions will be appreciated. Thanks in advance.
I think it happened to me too but im not sure... what rom are you using??? And i'd suggest you to use trigger wit the kernel called BULLET flash those and your phone is goin to be super fast... i play 3D games on my phone and i dont have any issues so far so i'd suggest u to flash both kernel and rom and your phone should b faster....
Sent from my GT-I9000 using XDA Premium App
I'm currently on Trigger with stock KB5+Voodoo kernel. I've tested it with hours of Asphalt 6 and Gangstar 2 and didn't have any problems so far. I'm still not sure what causes the problem, so I'm not gonna go adventuring with OCable kernels just yet.
Related
Hey,
Idk if its jus my phone but in every android build ive tried..there always this problem. tried searching but nothing :S
when i try to wake the phone....the hardware keys light up but the screen doesnt wake up for like a few seconds...sometimes even like 10secs :S:S:S other times its really quick.
Ive tried disabling auto brightness, even used setcpu to check if it was clocked too low and set the sleep profile at really high jus to check..but same problem :S the screen jus doesnt come on right away.
It works perfect in winmo but android has this problem
ive even tried changing the winmo rom...but nothin. same problem.
Right now im running: mdeejay FroYo sense 3.1.
Radio : 2.12.50.02
any help!!???
I have noticed this too, although mine only sits there for half a second to 2 secs, never had the patience to wait 10s, just start mashing the power button!
Any fix would be greatly appreciated!
I think your problem is more than likely due to a slow SD card I put the same build I use on a buddies phone and he had some cheap walgreens SD card. The only other thing to get around that is to use setCPU and raise the processor speed during sleep. Unless you are still running one of the earlier builds where this problem still was an issue.
Sent from my HD2 using XDA App
My Vibrant is currently running stock KB5.
About every two days or so, I will be using the phone, and the colors on the screen will suddenly wash out, screen goes to max brightness, whatever is on the screen at the time stays up, and there will be two or three horizontal thin lines on the screen. The Menu, Home, Back, and Search keys all light up. The touchscreen and all buttons, including the power button, become unresponsive. Screen will not timeout. Only way to get out of it is to remove the battery and reinsert. If I am in the middle of a phone call, I am still able to continue speaking on the phone.....but can't hang up, adjust volume, etc.
I haven't tried any other ROMs since KB5 was released, so hard to say if another ROM would solve the issue. Don't flame me for sticking with KB5. I don't need my phone to do a lot....really just use it for calls, music player, Sirius, Google Maps/GPS, light web browsing. I'm not really opposed to running another ROM, I just found it to be a pain in the butt to be constantly switching ROMs as they are updated.
Anyone else experience this problem? Hardware or driver problem? If anyone else did have this problem, did switching to another ROM solve it for you?
Pig Vomit said:
My Vibrant is currently running stock KB5.
About every two days or so, I will be using the phone, and the colors on the screen will suddenly wash out, screen goes to max brightness, whatever is on the screen at the time stays up, and there will be two or three horizontal thin lines on the screen. The Menu, Home, Back, and Search keys all light up. The touchscreen and all buttons, including the power button, become unresponsive. Screen will not timeout. Only way to get out of it is to remove the battery and reinsert. If I am in the middle of a phone call, I am still able to continue speaking on the phone.....but can't hang up, adjust volume, etc.
I haven't tried any other ROMs since KB5 was released, so hard to say if another ROM would solve the issue. Don't flame me for sticking with KB5. I don't need my phone to do a lot....really just use it for calls, music player, Sirius, Google Maps/GPS, light web browsing. I'm not really opposed to running another ROM, I just found it to be a pain in the butt to be constantly switching ROMs as they are updated.
Anyone else experience this problem? Hardware or driver problem? If anyone else did have this problem, did switching to another ROM solve it for you?
Click to expand...
Click to collapse
thats usually what happens when I OC too high or dont have enough voltage =3 is it just plain KB5, no mods right?? if so it shouldnt be doing that =/
ECOTOX said:
thats usually what happens when I OC too high or dont have enough voltage =3 is it just plain KB5, no mods right?? if so it shouldnt be doing that =/
Click to expand...
Click to collapse
No mods whatsoever. Completely stock, not rooted.
Today ever since lunch my vibrant has had a reddish tint? its like red with a little bit of blue and its really annoying me. i tried reflashing cyanogen mod but that didnt do anything! i havent wet it or anything so im confused as to why tis is happening. its like a slight red tint.
Go into voodoo control app. Towards the bottom select on gamma hack and choose default 2.3.3
Sent from my T959 using xda premium
It didnt work. but thanks for trying to help
No problem.
Sent from my T959 using xda premium
it randomly got red. and kinda has a blue outline . its hard to explain. its mainly noticable when playing games and watching videos
Ventus_zx said:
it randomly got red. and kinda has a blue outline . its hard to explain. its mainly noticable when playing games and watching videos
Click to expand...
Click to collapse
Maybe you set your phone to 3D mode
Ok, joking aside that's really strange. Try backing up, then using odin to go back to stock. Once on stock see if your phone still has this issue. If it does you may have a hardware problem. If it's gone, try re-flashing Cyanogen.
yeah i did all that before posting this. and i thought i accidently put it in some 3d mode lol. so i guess it is a hardware problem. damn it. i just got this phone...
How recently did you get it? Is it under warranty?
I got it saturday and im not sure. my dad sent it to me.
Flash back to cm7, put on a voodoo color kernel and use the voodoo control app... then ggo into rgb multipliers and lower your red, maybe your blue.. play with those till you acheive perfection
.. i spent some time until my screen became perfect, witb snow whites and vibrant colors now i get satiafied by just looking at my phone every day
Sent from a cell tower to the XDA server to you.
could i do all that using miui?
Hey guys,
I've been having an issue with AOSP roms where my display will just stop updating, Previously on one of Neo's ROM, and currently on CounterShrike 2.1. The screen doesn't turn itself off; it stays on, but freezes and doesn't change. I have to hit the power button to turn the display off and on again and it will work normally again for awhile.
It actually still accepts input when the display freezes. If I press the home button while it's frozen, it will be back on the home screen when I hit the power button off and on. If I'm in a list and scroll with my finger while it's frozen, it will be further down in the list when I hit the power button off and on.
I thought this was related to the proximity sensor bug but when I follow shrike's guide in the FAQ for setting up Chad's proximity sensor calibration, it already is showing 'FAR' when I first load the app and I don't need to adjust the high threshold. I think the sensor is fine.
Anyone have any other tips I can try? Everything works fine under CleanROM DE but AOSP is so much faster I'd really like to try and nail the issue down.
Thanks!
EDIT: I've attached a logcat. Two times I recorded the timestamp when it frozen, around 00:45 and 01:11. But I don't really know what to be looking for in the log cat.
thank god I'm not alone with this! I get this crap with any aosp based rom. I sent logcats to a few and nobody can't figure it out yet. sometimes it freezes but the display bleeds and fades itself off simultaneously
This is just an accepted problem with any AOSP ROM.
If you read the OPs they all mention graphics issues.
If you have been following the JellyBean stuff, they can't get any graphics to work at all.
GrayTheWolf said:
This is just an accepted problem with any AOSP ROM.
If you read the OPs they all mention graphics issues.
If you have been following the JellyBean stuff, they can't get any graphics to work at all.
Click to expand...
Click to collapse
really? the OP's for rage and aokp mention nothing about freezing or graphics being glitchy
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
a.mcdear said:
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
Click to expand...
Click to collapse
That is probably not an AOSP issue.
GrayTheWolf said:
That is probably not an AOSP issue.
Click to expand...
Click to collapse
Yeah, I sorta agree.. but I never had noticed it until I started using CM9 ROMS.
Actually though, ever since the ICS leaks something has been a little off about the Rezound touch screen, even on Sense ROMs..
Sometimes when you swipe horizontally one direction quickly, it starts to go and then jerks back and actually scrolls the other way. Worked fine in GB for the 2 months I ever used it on this device....
a.mcdear said:
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
Click to expand...
Click to collapse
This is true. I've stated this issue months back, sweat or a drop of liquid makes our screen act funny.
Sent from my ADR6425LVW using xda app-developers app
freezing occurs regardless, no moisture involved
What cpu governor and i/o scheduler are you using, do you know?
I've noticed freezes/slow response with either noop or deadline i/o scheduler. The powersave governor or turning cpu speed down too far can also cause freezing.
Occasional Graphical flickering in GUI elements does seem to be an issue with cm roms on multiple devices. I've had success turning on settings - developer - force gpu rendering to reduce flickering, YMMV.
Sent from my Rezound using Tapatalk 2
brenuga said:
What cpu governor and i/o scheduler are you using, do you know?
I've noticed freezes/slow response with either noop or deadline i/o scheduler. The powersave governor or turning cpu speed down too far can also cause freezing.
Occasional Graphical flickering in GUI elements does seem to be an issue with cm roms on multiple devices. I've had success turning on settings - developer - force gpu rendering to reduce flickering, YMMV.
Sent from my Rezound using Tapatalk 2
Click to expand...
Click to collapse
I forget exacts but it's with whatever is default when first flashed. the logcats at the time didn't mention anything about the CPU itself but graphics and HDMI errors with different invalid sound outputs as well
I experience this on multiple AOSP rom's! My phone was fine with sense based rom's but AOSP freezes. Sometimes it doesn't freeze at all, sometimes it's multiple intervals close together. This leads me to believe that it's something in the AOSP rom's themselves and not bad hardware, too many people have it with the same symptoms. Yet sense works fine.
Head scratcher (to put it very lightly).
least I'm not alone on this one. can't be hardware otherwise same issues on sense. anything that's not custom like the kernel or aosp works fine
I agree that I don't think it's necessarily the hardware itself. I think it could be some sort of threshold parameter HTC sets that differs just slightly from CM9 (threshold in what exactly I don't know), but that some of us have hardware that gets tripped up on it and others don't.
I initially thought it was an issue with the CPU (I've always been using the stock speed and governor after the initial flash) but it doesn't matter if I'm doing something really light or really intensive. It also doesn't seem to matter if I'm using stock apps vs. apps I've downloaded either.
I have 2 days off from work so I'm going to flash back to the latest CounterShrike and grab a log cat every single time it freezes up. At the end of the two days, I'll compare every single instance and try to find some correlating event.
Hopefully I'll find something!
God Damn this is really annoying!
Just had to get that of my chest. I'm reading threads and scrolling every few seconds and I just had a few lockups in a row. It's so frustrating because every other aspect of the Rom works perfectly! I don't understand. No amount of kernels I try fixes the issue. Volts don't affect it, cpu speed doesn't affect it. It's enough to make me want to go back to sense just to not have to deal with it. I don't want to
winston856 said:
God Damn this is really annoying!
Just had to get that of my chest. I'm reading threads and scrolling every few seconds and I just had a few lockups in a row. It's so frustrating because every other aspect of the Rom works perfectly! I don't understand. No amount of kernels I try fixes the issue. Volts don't affect it, cpu speed doesn't affect it. It's enough to make me want to go back to sense just to not have to deal with it. I don't want to
Click to expand...
Click to collapse
yeah sadly I went back to sense. dark tranquility gives me phenomenal battery until the mean time with functional video chat. it's not often but I would like to give up video calls for aosp. even with everything I want removed from sense it's still bloated memory wise.
good luck with getting logs. I sent to most devs here and they were stumped
Got a replacement phone coming in the morning, we'll see if I experience the same issue or not.
I tried all sorts of things, and it happens to me.
Went back to Sense with included dsb kernel.
Funky kernel has the issue on sense for me though.
Sent from my ADR6425LVW using Tapatalk 2
I didn't have much luck identifying something in the logs winston856 I'm considering getting a replacement as well. Let me know how you make out.
Ok, I'm posting this here cuz I'm not sure if it's in this ROM or in the S3 no matter what ROM. I can't even find ANY reference to this, nor anyone who even knows what the hell I'm talking about, so here goes....
My S3 seems to have a 'butterfingers' feature. It has had it for as long a I remember... If I fumble around like I'm gonna drop it, it locks out all the touch buttons until I press power and cycle the screen off and back on. (Not the power, just the screen. It's NOT FROZEN, it simply disables the touch screen and menu/back) It was never a problem until I tried to load btcontroller. The fast movements of gaming trigger the damn thing every 30 seconds or so of play. Also does it on emu's like NES and such. It's damn frustrating to try to play a game and have the 'controller' randomly lock itself out! I was running wickedv7, and just went to wickedv9.1, no change.
Is this a feature or a defect? Is it in every ROM, or just in Wicked? Can I turn the bloody thing off? WTF? Thanks...
that's a defect
Try flashing stock Rom and see if you still have problem...if yes, then probably hardware, if no, then almost certainly software