So I flashed DK28 this morning and have run into a major issue. Everything works wonderfully for a while it seems. But it the screen shuts off for approximately fifteen minutes or more, the phone seems to become totally unresponsive. The power button does not wake it and when I slide open the keyboard, nothing seems to happen (phone doesn't lock and keyboard backlight doesn't light up). I'm forced to do a battery pull and reboot.
I have never experienced this with any other version of the Froyo or Eclair ROMs. I've tried both wiping and reflashing (both the DK28 modem and ROM).
Anyone else having this issue? Anyone know why this might be?
Related
I'm running Black 2.5 as my ROM, but it's happened on all ROM's, including the Cingular stock WM5 rom. The keyboard just stops working. It comes back sometimes on it's own a few minutes later, and always after a soft reset, but what causes it?
Does this happen to anyone else, and is it a hardware issue, or a software issue?
Does happen to me sometimes. Had one this morning. Not only k/b, but the scroll wheel as well.
Keyborad not responding
Hello,
Have same problem after flashing rom.
I thought that maybe I did it wrongly but also my friend discover this issue.
From time to time external keyboard not responding and on-screen keyboard is working but DEL key is also dead.
Also other buttons like green/red phone keys not respondig.
Sometimes problem disapper automaticaly sometimes I have to reset phone.
Any solution?
Has anyone found information on this problem? I have had my 8525 for about 6 months now and this has happened to me on the original shipped ROM as well as both Black 2.5 and 3.0.1.
It happens usually during texting, and like stated previously, sometimes it comes back on its own, and sometimes it takes a soft-reset to get it working again. I am able to finish the typing using the SIP before soft-resetting.
I haven't paid attention to whether or not the scroll wheel stops working or not. I'll keep an eye out for that. Also I can't figure out what's triggering this problem. It seems very random.
I would start to think it's a hardware problem since I have seen it on 3 different ROMs, but so many of us are experiencing the same issue.
Happens on my Vario 2 sometimes. I've put it down to me using the keyboard whilst the CPU is bogged down too much, and it just doesn't 'see' the interrupts coming from the keyboard I/O controller, and then it loses its sync.
I usually just soft reset at that point, because I can't be bothered to wait and see if it comes back
I have it sometimes when using IM and PIE. Closing PIE and waiting a couple of minutes usually brings it back.
I started noticing a few days ago that when my phone is in stand-by, and I turn it on, pressing the power button, it takes longer than usual to wake up, like 5 seconds.
I don't remember this happening before. Last time I upgraded the ROM was back in November. I have VP3G 3.62.3, and everything was always working fine. I also use Slide2Unlock, and at first I thought this was causing the lag, because of a memory problem, maybe it was taking too much memory to be loaded, or something like that could have changed. But no even if I disable slide2unlock and use it normal, it still happens. I even re-loaded the ROM, without anything else (the lite version), but no matter what, when I turn the phone off (make it sleep), whenever I try to turn it back on, the lag is always there.
Anyone else experiencing this? Do you know of any cause or solution?
Thanks very much.
My phone does the same thing, but it's no big deal. Occassionally I'll hit the button twice thinking I didn't hit it right the first time, but it's really not a big deal.
Sounds normal, but there are some cooked roms that are quicker then others depending on addons (the TNT rom is one of them for me). If you have not already, try using 'startclean', 'hibernate' and 'cleartemp' apps daily to free up memory, cache, etc...
I've been getting very strange/unwanted touchscreen issues for a while now. It seems to happen randomly and for hours at a time. When I press the power button to wake the phone and turn the screen on, I can't even drag the unlock slider to unlock the phone. It takes numerous wake/sleep power button presses until I can get the screen to respond to my finger. Sometimes I'll be typing and it will go crazy and highlight buttons back and forth quickly, usually two or three letters almost always off to the left side of the screen. When this happens I am unable to get it to stop or register any other screen presses. I have to press the power button and then press it again to wake it and I'm stuck at the unlockable lock screen. Only after repeated attempts does it finally get through and the problem will go away for a while, only to come back later.
I have used the program 'Dotty' to track the touch points and I noticed that it will sometimes show a multicolored touch point off to the left of the screen and it will jump around, and it won't detect any other new touch points.
Soooo I think my screen touch sensor is messed up somehow. Does anyone else have this happen? Seems to have started when I flashed the kernel to get rid of the 30 fps cap. I have recently flashed Fresh 3.1.0.1 and still have this problem, different kernel with that rom correct? I'll try to get a video up sometime to show this in action...
Yes, I've been having the exact same issue. I even did a hard reset, with the assumption that it was an app. My plan was to add them back slowly until I got the issue, the problem was it happened as soon as the phone rebooted on the reflash. I have no idea what the issue is, but its very frustrating.
I'm running 2.2 stock...
Some people have reported touch screen problems with netarchy's kernel. There is usually a revision to correct this problem for people who are experiencing it. I suggest you carefully read over the OP in that thread and determine what kernel is right for you. There is usually a version specifically for Fresh users also.
MIGHT i ask what widgets are you running??
i talked about it before when running the pre-official ota rom.
it was my htc music widget (half sized one) i had running on the home screen.. caused lag like a mofo, couldnt swipe most of the time, capacitive buttons wouldnt react, pressing the app drawer button wouldnt respond till 5 seconds later...
AS A MATTER OF FACT.
im running fresh 3.1.0.1 + latest kernel + music widget on home screen.. LAAAGGG like before. removing it makes things snappier again.
YEP. Its happening again.
when i ran the STOCK Official rooted rom, with music widget on home screen didnt produce this lag and poor touch input, even with kernel it didnt produce this problem.
Mine is fine, no screen problems!!! stock rooted rom!!
Just installed blackhole rom 1.4 with goldenstorms theme. And noticed an wierd problem, but didnt see anyone else post about it.
My soft keys are staying lit if the phone screen times out. They will remain on till unlock the phone.
I tried installing the soft key mod for 10 seconds, and it works except for when the screen times out and it locks and goes black, then they stay on forever. Its not a huge deal but it is quite a battery drain.
Any have any ideas or solutions?
That's backlight notification. You can download a cw flash to disable thru jt's section in rom manager if you don't like them.
Empirical testing has shown BLN to be not much of a drain. But you can switch it off.
Sent from my Voodoo-powered Fascinate via XDA
thanks everyone for the help. Its not a terrible drain, but i still didnt like it. And since i flashed blackhole it does appear that my battery is slightly shorter lifespan.
For whatever reason DK28 causes my touchscreen to randomly stop working. Stock DI18 does not have this problem at all.
I would just go back to DI18 permanently until the 'official' froyo comes out from Samsung, but I need the froyo gmail app for work over the holiday. This means I'll be using a phone, that while stable in every other respect, will randomly stop responding to touchscreen inputs. I fix it by putting phone in standby and waking it back up. This usually allows me to use it for a while longer.
Anyone else have this problem, or possibly know what might be the cause of it?