Database Info

[Q] Weird issue

Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
I realize the obvious solution is to stay with stock, but I was just curious if anyone else had experienced this and knew of a better solution (who wants to be on stock).
Thanks in advance.

That has happened to me before. Went away with a fresh flash and wipe of cache.

canadaboy37 said:
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
I realize the obvious solution is to stay with stock, but I was just curious if anyone else had experienced this and knew of a better solution (who wants to be on stock).
Thanks in advance.
Click to expand...
Click to collapse
You didn't restore system data when you flashed this, did you?

canadaboy37 said:
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
Thanks in advance.
Click to expand...
Click to collapse
Do you have any over/underclock settings applied? Are there are any voltage settings that you find?

cappysw10 said:
You didn't restore system data when you flashed this, did you?
Click to expand...
Click to collapse
The first time I flashed, I did that which I later realized to be a huge mistake. When this issue started, I flashed back to stock did a master clear and reflashed Cog, but the issue remains. Is there some step I missed in clearing out the old stuff?

This happens to me in swype occasionally. Super annoying bc it thinks I am taking my finger off the screen when I am not causing swype to be worthless. after a reboot it goes away
Sent from my SAMSUNG-SGH-I897 using XDA App

trekie86 said:
Do you have any over/underclock settings applied? Are there are any voltage settings that you find?
Click to expand...
Click to collapse
I haven't played with anything other than flashing Cognition onto the phone.
I'm going to try going through the whole thing again, but this time not reinstalling any old apps/data through Titanium Backup. I'll set everything from scratch and see if that makes a difference.

Multi Touch Bug

I am having a major issue with multi touch, and it happened on stock so I don't think it's the rom I'm running (CleanRom Dev).
If I let go of my second touch, the screen loses the first touch location. So, if I am playing Minecraft or Shadowgun, I'll use one touch to move forward, that works, then I'll use one touch to move the screen, that works, but as soon as I let go of that second touch, I stop moving; even though the first touch is still being held on the screen. This happens in any game I play, even with the HTC Gestures off.
I saw a couple other people were having issues with multi touch, but I'm wondering if this is a problem with the kernel or the device. I saw that h8rift mentioned that the kernel's multi touch is a hacky implementation.
Any information is appreciated,
Thanks.

Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Edit:
Issue keeps coming back a few minutes after rebooting.

thebest said:
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Click to expand...
Click to collapse
Yeah, same here. It took me forever to figure out that it was HTC gestures that was the culprit
Sent from my HTC One X

Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...

edit: already said

ThisWasATriumph said:
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
Click to expand...
Click to collapse
Hmmm, maybe this should be under CleanRom development then. I may not have had it on stock, I thought I did, but I wasn't on stock for very long

thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.

rohan32 said:
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
Click to expand...
Click to collapse
Good to know, I was just worried that my phone was jacked up D: lol

Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.

I use Holo Locker does that cause issues?

samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
Wow, that was the problem. Disabling Holo Locker, then turning the screen off and on resolved the problem. Weird....

samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
You're a genius! Holo Locker was causing the issue. Thanks so much.

Yeah I had that problem too, it was being caused by HTC Gestures. I just turned it off because I didn't ever see myself using them.

now me too..but..
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...

david244 said:
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
Click to expand...
Click to collapse
GOT IT. :silly::silly::silly:. (after alot of factory resets)
The trigger of the bug is If you select:
Personolize -> Lock screen style -> No lock screen
Try it.

you want to uncheck HTC Gestures. it is used for another purpose not what you think it is only used for when your phone is connected to tv.

[Q] Black screen

Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan

thebguard said:
Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
Click to expand...
Click to collapse
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms

REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!

REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.

orange808 said:
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
Click to expand...
Click to collapse
my Carbon rom is built differently than fattoad, cm, or omni...doesnt have lbcoders mpdecision touchboost amongst many other differences in its kernel
---------- Post added at 11:23 PM ---------- Previous post was at 11:16 PM ----------
thebguard said:
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
Click to expand...
Click to collapse
if its at 192mhz go to 384mhz....if at 384mhz try 192mhz...if either dont work bump it up to the next highest mhz

I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.

thebguard said:
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
Click to expand...
Click to collapse
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?

REV3NT3CH said:
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
Click to expand...
Click to collapse
The lowest option I had was 384mhz.
Flashing via CWM recovery: wiping data/system/cache/dalvik. Then CarbonRom and gapps. So clean wipe I think is what you are referring.

Sent you a zip to try via pm. Just let me know if it works.
Sent from my LG-VS980 using Tapatalk 4

Does this issue manifest itself when you have the phone plugged in? Can you get a logcat of the issue? Throwing things at the wall and seeing what sticks may not be the best resolution here. There are ways of finding out the underlying cause.
mpdecision is not the cause here (That only affects the secondary core) nor is min frequency (You can override it in the HypnoToad images too, just set another governor (like say 'conservative). In FatToad it may look like it resets because Cyanogenmod doesn't display the second core in the performance settings, but changing it is sufficient for testing. The official CM 11 builds do not have the touch boost (which only affects things after the phone is awake, and merely sets the secondary core's frequency up to 1184 Mhz when you are touching the screen, but the affect on the percieved performance of the phone due to this is immense)
Deep sleep is likely closer to the main cause because that affects both cores, and if the system isn't receiving the proper signals to wake back up, this can happen. Throughout development on apexqtmo, we've run into similar problems, and it's always helped by getting proper documentation from those who are experiencing the issues.
TL;DR: Trying random things likely won't solve this issue. Getting all the information you can will help.

Thanks again for all the help. I don't usually ask for any but I could not find much on my issue (or maybe I wasn't searching correctly).
I think I did the logcat correctly. See attached.
The thing that popped was:
D/SurfaceControl( 791): Excessive delay in unblankDisplay() while turning screen on: 269ms
Click to expand...
Click to collapse
When I would hit the power button and screen would not turn on, this would be there. I'm not really good with understanding this stuff. Hopefully this leads us in right direction though!
Edit: sorry forgot to answer your first question Magamo. This issue happens no matter if it's plugged in or not.
Edit 2: I watched the logcat from adb for awhile and I guess the above happens no matter what. I don't see any differences between if the screen turns on or not.

It looks like you have a hardware rev we're not supporting in our current kernel (which is why it works on stock). PM me if you want to mail your phone to me for analysis

This happened to a new device i purchased. After lbcoder and nard trailed through my logs, I was prescribed to resell the device. Your symptoms sounds identical to what I was experiencing. JB stock kernal works. But custom roms which since delved into the new edited kernel doesnt work on such devices. Since re-sold the device. Be interested to know if yours gets fixed where mine didn't. Good luck

Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!

sorgo said:
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
Click to expand...
Click to collapse
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?

REV3NT3CH said:
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
Click to expand...
Click to collapse
Thanks for the reply. Yes the bootanimation and initial logo is telling enough about the cause of it. I must admit it's a hw problem. I tried to open/close the keyboard quicky instead of moving it slowly, but it occurs too. I'll try completely different rom with different kernel as the last chance
to hope for a sw issue.

I tried Omnirom with same result, but now I did a clean flash of the latest liquid and my impression is that this happens a lot fewer times than before. Maybe I just got the right velocity and force needed to open it gently I also installed just a few critical apps. Before I messed with Ultimate screen rotate etc.
But it now happens more when closing the keyboard. However, I'll rather buy new one, just ot have a backup of this great phone just in case.

http://www.cellulardr.com/samsung-t699-slide-flex/
Is this "the part" I need?
Do you have any experiences with this shop? It seems to me too much $40+shipping for that cable. Probably I'll just order another one from ebay, preferably new one and leave the current one for spare parts in the future.

Fixed today! You can see the state of the flex cable on the last picture in this post:
http://forum.xda-developers.com/showpost.php?p=56642402&postcount=35

Random system crashes and slow bootup (multiple custom ROMs)

I seem to have really strange issues with this phone.
I've tried both C-Rom and Cyanogen and both of them have these same issues.
When I first turn on the phone, it will run, but everything will stutter around at about 1-2 fps for about 2 minutes. I can confirm that this happens even with no 3rd party apps installed.
Secondly, half the time when I go to grab the phone and just check notifications and so on, I'll unlock it and try to press something and it'll be frozen. I have to wait about 2 minutes before I can do anything else on it. The only thing I can do in this time is lock the screen, but not unlock it. I can tell it frozen at a low level because I have a system setting in C-Rom to play a sound when the battery dis/reconnected and that doesn't play while it's in this state. Has anyone else been experiencing this? I've already completely wiped the phone completely once using the return to stock guide and these issues have not been resolved.

Had the same problem with stock ROM or tried with GPE? Might be a hardware problem...

fckland said:
Had the same problem with stock ROM or tried with GPE? Might be a hardware problem...
Click to expand...
Click to collapse
Are you still having these issues or did you find a fix for them? I have the Boost Mobile one, but are you suggesting that I could/should put the GPE ROM on here?

Isn't this a memory usage ( ram ) problem that's been mentioned?
Sent from my XT1032 using xda app-developers app

The first part (FPS issue) happens to me, whe the phone boots, the FPS go down, bad, but the phone works ok, if i put the stopwatch app (CM11) time runs normally but the screen refreshes every half second or more.
Now, the second problem, about the phone freezing whan it wakes up, never happened to me, but i have to recognize that i had a few (2 or 3) reboots just when i waked up the phone and one time it just freezed with the screen off.

No idea what this problem is? anybody able to offer advice?

I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated

It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk

Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?

nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that

hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol

ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen

OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks

One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk

ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.

Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.