Related
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Dr. Strangelove said:
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Click to expand...
Click to collapse
Few Tricks, Make sure you are not plugged in USB. Make sure you are not "fat fingering it." Some people use chopsticks to be sure. And Hold it for long after the Screen goes Black.
Believe me, I've already tried the things you said.
Although I successfully mananged in the past to hard reset my phone, I checked the threads and the following vid:
How To Hard Reset Kaiser:
http://www.youtube.com/watch?v=fZPzT_L2FZQ
Usually I am the problem, but this time I can't figure out what I'm doing wrong.
Just wondering:
Which part of the Phone (ROM) is in control of the Hard Reset part? (e.g.: Bootloader, Radio Rom, Regular Rom,...)
Use "Clear Storage". It does the same thing.
Also, JM is most likely correct. It is most likely an issue of how you are pushing the buttons. Make sure you hold only ythe soft keys first, using your fingernails, then push the reset tab on the bottom & hold it. Don't just push the reset & release, but keep it held down.
Based on your previous message about your phone being haunted - mine is too btw, I think it's because the soft buttons aren't being acknowledged by the OS - which implies some REAL big problems.
I took mine back to the T-Mobile store today where I got told that it needs to be sent back to their workshops to fix it... and then got told that "mostly they just send out a new phone".
My phone is exhibiting the following symptoms.
1) Green and Red phone buttons do not work.
2) Soft buttons do not work.
3) D-Pad and wheel work intermittently.
4) (and most strange) the back-space key on the slide out keyboard does nothing, and on the virtual keyboard it flashes (to suggest that the key is being pressed) but still does nothing.
I've tried to access the bootloader, and perform a hard reset. I'm now looking for the original T-Mobile ROM to install (which was why I went into the shop), as the issue around the backspace key implies to me that the issue is in the OS not in the hardware.
Jon
Thanks already for all the input.
I've been trying all weekend in every different possible way to perform a hard reset. Fat fingering is really no possibility anymore. I've used every possible tool I had (needle-nose pliers, chopsticks, pens,...) to eliminate fat fingering.
But nothing helped. Jon (a nice guy) might have given a possibly correct diagnosis for my problem. But it wouldn't explain why I still can get into the bootloader.
Problems since receiving my phone from repairs:
Backlight changed out of itself => performed Hard Reset
Phone pad pops up and seems to start dialing => flashed new ROM
Wakes up constantly after a few seconds from standby => performed Hard Throw against the wall
As you can see, my latest problem is that the phone automatically wakes up from standby after a few seconds. The weird thing: it only does this when I put it in standby, but it doesn't wake up if it enters standby by itself.
=> NOTE: This may support the 'fat finger'-theory: the Kaiser gets some sort of keyboard input due to faulty hardware. Therefore I cannot Hard Reset my device, because of the additional faulty input.
I've used the "Clear Storage" method to perform one of my hard resets, but this has to be solved. I will be sending the phone back for yet another repair.
Thanks again for your input everyone.
Problem found?
I think I found the problem:
I just noticed that the camera button is already pushed in halfway (like when you focus the camera before you take a picture). If I push the button gently, it immediately takes a picture without focussing (it does automatically focus before taking the shot, but not on my command).
Also, when I enter the camera app, it sometimes instantly focuses. Other times I cannot focus at all.
Hard reset is still no go.
Yet another thanks for your useful help.
Maybe found the solution?
Hi Guys...
I found that by tapping the base of the phone, it "unlocks" itself, thereby making it work. It's become *S*L*O*W* as hell, and I'm really tempted to ask them to take a look at it, but right now I need all the functions, so I'm holding off.
But, give that a try and see what happens!
Jon
Thanks for still answering my question. Go community!
Dr. Strangelove said:
...
I will be sending the phone back for yet another repair.
...
Click to expand...
Click to collapse
Last week I finally received a fully functional and working Kaiser (have been waiting for that since december...). I couldn't accept a disfunctional Kaiser coming back from repairs.
The problem did indeed seem to be the camare button that was stuck. I tried really hard to get it to unblock, but I didn't work. I must say, I didn't try your method (didn't think of it).
Still thanks a lot.
I am experiencing exact same issues on my Kaiser (Tilt), it randomly starts to type stuff in the phone application on its own and I can't do anything to stop it, I have replaced ROMs, SPLs, Radios, now using a shipped rom with shipped radio but still that problem comes up after a few days of usage and doesn't go away until I hard reset, anyone knows what I can do to fix it? it's probably out of warranty. I checked the camera button and it seems fine.
Okay, so to those of us who have problems with screen ignoring/being very slow with screen taps and/or buttons, read on.
I flashed ROMeOS ROM and started having problems where I would tap on something, and it would ignore it. I would keep tapping and tapping, but nothing happened. Sometimes, even hardware buttons were ignored, about 40% of the clicks. I never had that problem with Dutty's Diamond ROM or WM6 ROMs. Issue seems to be related to latest 6.1 builds... or so it seemed at the time.
After pulling out half of my hair, reflashing all kinds of ROMs, reflashing to latest HardSPL, etc etc... I almost threw my kaiser at the wall.
First I thought it's TouchFLO, then I thought that it's the latest 6.1 ROMs.. then I thought it's related to 3.56 HardSPL.. well eliminating those factors one by one DID NOT fix the problem. Right now I went 100% to stock ROM (one it came with) and AT&T's original SPL. I started having sound problems (w/e radio I tried did not work) so I flashed Hyperdragon Wm6.1 ROM.
About 90% of the problem is phone ignoring ANY kind of touchscreen taps/drags.
About 10% of the time its the hardware buttons that have the problem - for example I push "call" (or any other softkey) button, and nothing happens, while touchscreen could be working fine at that time. In about 10 seconds, hardware buttons would start working again.
Some information that was gathered from this thread and personal research:
It looks like problem is NOT related to the following:
- POWER. Connecting phone to AC power does not solve the problem. Subjectively, it may improve it a little.
- BLUETOOTH/WIFI. Problem persists with EVERYTHING disabled and phone being in Airplane mode.
- PARTICULAR 6.1 ROM. I had this problem on ANY 6.1 ROM I tested (and I tested all the way from AT&T almost-official WM6.1).. maybe that's why they didn't release it?
- OPERA browser. Some people never had Opera and they still have this problem (please confirm this!).
- SPB/WISBAR interface software. Although having Wisbar stuff does make it a lot worse for me.. and I still have the problem without SPB or WISBAR installed.
- S2U2 screen lock. Still had the problem w/o S2U2 installed.
- iGo 2006 or iGo 8. Many users with this problem never used iGo.
Problem MAY be related to the following (needs more research, please help):
- Original SPL versus HARDSPL 3.XX
- WM6.0 versus WM6.1 (I don't think I had any problems running original AT&T 6.0 ROM, but I did have sound (radio) problems, so had to flash 6.1). Several users report that WM6.0 is immune to this problem.
- A combination of running WM6.1 with latest HardSPL?
- Custom ROM VS Original ROM. Perhaps problem is in the tweaks to the registry.
- Simple things like overtime connection weakening in touchscreen connection to the mainboard. Whoever can open a Kaiser could try to replug/clean it and report back to us.
- Radio version. Should be easy to test, just need to reflash all kinds of older radios and see if problem persists.
Please make sure that you test your phone with some touchscreen intensive games/software a lot for AT LEAST 3-4 days. I had it happen several times where it would be fine after reflash for about a day or so, and then it would come back in full force.
BRICK?
In my case, running HTC WM6.0 ROM with HTC SPL DID NOT fix the problem, I can even say it made it worse. Touchscreen would respond to about 10% of the screen taps. Tap pressure doesn't make any difference.
Also, running AT&T stock shipped ROM with stock shipped radio and SPL did not fix it. I guess at this point, nothing will. Waiting for replacement tilt.
Hope nobody else will get it as bad as I did. All I can say is... make those relfashes count.
Hmm isn't Touch Flo one of the cool things with the Kaiser??? How do you navigate in programs now it's disabeled?
DarkDvr said:
Okay, so to those of us who have problems with screen ignoring/being very slow with screen taps - I think I've found a fix. Here's a little background:
I flashed ROMeOS ROM and started having problems where I would tap on something, and it would ignore it. I would keep tapping and tapping, but nothing happened. Sometimes, even hardware buttons were ignored, about 40% of the clicks. I never had that problem with Dutty's Diamond ROM or WM6 ROMs. Issue seems to be related only to latest 6.1 builds.
After pulling out half of my hair, reflashing all kinds of ROMs, reflashing to latest HardSPL, etc etc... I almost threw my kaiser at the wall.
So if you have similar problems - try using Shnaps' Advanced Config to disable the TouchFLO altogether.
Another thing that I've used is PocketMechanic to clean up the notification queue. After fresh install of HypreDragon (latest as of Aug 5), I had 46 duplicate notifications. Removing those seemed to ease the problem, but NOT fix it. Disabling TouchFLO seemed to finally fix it.
I hope this helps somebody. I'll update this thread if I keep having this problem..
Click to expand...
Click to collapse
Thanks for the head's up! I'll definately try that tomorrow (danish time).
Foxhunter123 said:
Hmm isn't Touch Flo one of the cool things with the Kaiser??? How do you navigate in programs now it's disabeled?
Click to expand...
Click to collapse
Never really caled for it, I use my hardware buttons (D-pad) to scroll, I find TouchFLO to be too unreliable... maybe it's just me, but nothing beats a hardware button which you actually "PUSH".
spip72 said:
Thanks for the head's up! I'll definately try that tomorrow (danish time).
Click to expand...
Click to collapse
Do you have the same problem?
Hello,
First off thak you for the post. Ive got two identical Tilts both with the exact same radio/boot/roms. One has this issue and the other doesnt. I will be disabling it on the one havong the issue and report back! Thanks much!!!
I was also having this problem. my biggest complaint was my keyboard was all over the place. Sometimes it wouldnt see key strokes at all, other times one key hit would register as 3 or 4.
Sent a few test messages and This seems to have helped.
THANK YOU!!!
My Kaiser was getting close to being flashed back to a WM6 rom or quite possibly embedded in a wall.
where do you find cab for touchflo? I was looking for that but could not find it.
tamkhanh said:
where do you find cab for touchflo? I was looking for that but could not find it.
Click to expand...
Click to collapse
seek and you shall find.
It's all over the place.
Try playing around with the TouchFLO sensitivity options in KaiserTweak
i upgraded to official 6.1 about two weeks ago...
i recently started having the "missed taps" problem...
i have a feeling that KaiserTweak has something to do with the issue...if memory serves, i don't remember experiencing the issue BEFORE i played with the "TouchFLO->Sensitivity" and "TouchFLO->Finger Pressure" options...i just launched KaiserTweak right now and its showing those values as set to defaults where as i could've sworn i changed them to the advised settings a day or two ago approximately when i started experiencing the issue...just a point to clarify, i was only playing around for no particular reason and my taps were not problematic before
i've just changed them to the advised settings and did a soft reset to see if these are the kind of settings that are forgotten after a soft reset...but they stuck...so i'm gonna observe this for a couple of days with the advised settings effective and see if they have reverted to defaults on first sight of the issue...i'll report back here if that happens because that would be a pretty strong correlation...almost enough to prove cause and effect
Well, problem is, last time I've used KaiserTweak was like a year ago, so my touchscreen problems cannot be linked to KaiserTweak. I don't even have it on my tilt.
Also, it's definitelly not a touchscreen itself, since this problem is application-dependent. Once again, S2U2 and Opera are immune to this problem. Windows' build-in apps (file explorer, bottom bar, etc) all suffer from it.
I've noticed this too, but I've found a slightly longer tap seems to make things reliable for me.. Instead of a quick 'jab' if I sort of touch it, it seems to be better.
and keyboard too I've noticed.. I mostly notice it with the hard keys rather than the keyboard, but I don't use the keyboard a lot.
I'll try looking for duplicate notifications, what else will do that besides MemMaid? I might reinstall it, it was handy. I previously found phoneAlarm would grow notifications over time, I suppose I need to watch for that anyway.
khaytsus said:
I've noticed this too, but I've found a slightly longer tap seems to make things reliable for me.. Instead of a quick 'jab' if I sort of touch it, it seems to be better.
Click to expand...
Click to collapse
True, if I keep pushing on the screen button, in about 5 seconds it will be clicked. But that's ridiculous, i gotta say.
I'll try looking for duplicate notifications, what else will do that besides MemMaid?
Click to expand...
Click to collapse
I use PocketMechanic - good stuff. Has lots of useful functions, including notification queue cleanup and analysis.
Just had another "seizure" - touchscreen would not respond AT ALL for several minutes. No matter what or how I tap - complete ignore.
After couple of minutes it started working again.
Interesting that S2U2 worked fine. Seems that windows just chooses to ignore touchscreen input.
I'm forced to return to WM6.0 ROM...
Please, anybody look into this.. phone is becoming to be unusable - I can't even enter a phone number.
DarkDvr said:
Do you have the same problem?
Click to expand...
Click to collapse
Yeah it's really bad here. I've tried all sorts of tricks, including:
Re-install 6.1
Re-install 6.1 with the recent radio update found on the e-club
Install SPL 3.56
Disable HTC today screen
Kaisertweaks - tweaks on and off
Disable radio completely (seems to help, but makes the device useless)
Disable activesync
Disable quickgps
For now, I've done 2 things that seems to help:
- Disable the HTC task manager - improves the responsiveness
- Kill the MSTLI.EXE process - improves on the number of freezes
But I still experience freezes, and it's really getting to me. I need a responsive device, not this c****
ASCIIker said:
i upgraded to official 6.1 about two weeks ago...
i recently started having the "missed taps" problem...
i have a feeling that KaiserTweak has something to do with the issue...if memory serves, i don't remember experiencing the issue BEFORE i played with the "TouchFLO->Sensitivity" and "TouchFLO->Finger Pressure" options...i just launched KaiserTweak right now and its showing those values as set to defaults where as i could've sworn i changed them to the advised settings a day or two ago approximately when i started experiencing the issue...just a point to clarify, i was only playing around for no particular reason and my taps were not problematic before
i've just changed them to the advised settings and did a soft reset to see if these are the kind of settings that are forgotten after a soft reset...but they stuck...so i'm gonna observe this for a couple of days with the advised settings effective and see if they have reverted to defaults on first sight of the issue...i'll report back here if that happens because that would be a pretty strong correlation...almost enough to prove cause and effect
Click to expand...
Click to collapse
My device is currently without kaisertweaks, and I still have the freezing issues.
DarkDvr said:
Well, problem is, last time I've used KaiserTweak was like a year ago, so my touchscreen problems cannot be linked to KaiserTweak. I don't even have it on my tilt.
Also, it's definitelly not a touchscreen itself, since this problem is application-dependent. Once again, S2U2 and Opera are immune to this problem. Windows' build-in apps (file explorer, bottom bar, etc) all suffer from it.
Click to expand...
Click to collapse
I concur, it is application specific. I tried to run the "Task manager" from Fdcsoft to see if it was related to a process eating up all the CPU. But the problem doesn't occur while the application is focused.
DarkDvr said:
Never really caled for it, I use my hardware buttons (D-pad) to scroll, I find TouchFLO to be too unreliable... maybe it's just me, but nothing beats a hardware button which you actually "PUSH".
Click to expand...
Click to collapse
TouchFlo is way too unreliable to me too.
DarkDvr said:
True, if I keep pushing on the screen button, in about 5 seconds it will be clicked. But that's ridiculous, i gotta say.
I use PocketMechanic - good stuff. Has lots of useful functions, including notification queue cleanup and analysis.
Click to expand...
Click to collapse
Oh wow, not a LONG PRESS, literally a 'touch' vs a 'tap'. What you describe would be seriously annoying.
Thanks for the suggestion, I'll look at it
This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...
Hello all,
My incredible s freezes, I would then need to press the power button (to put screen into sleep) and then wake it up then it's good again (not restarting).
Any idea whats this all about?
Did someone else have the same problem? what should i do next, how can i find out if its software problem or hw?
thank you all for the help
PS: i tried soft reset and hard reset, nothing helped, could it be that i need to change the touch screen DIGITIZER?
PS2: i was searching how to do a factory reset....
From the main home screen, tap menu
Tap Settings, then Privacy
Tap Factory data reset
Tap Reset phone
Enter your password if required, then tap Erase everything to confirm
in my Privacy menu i dont have Factory data reset, whats wrong with this phone? i just did upgrade, using Adroid 2.3.3, Sense 2.1, SW no 2.30.405.1
found out that the factory reset thing is in SD & phone storage menu
i did a factory reset but its still happening
help please
maybe a new display would fix this?
what else could i try before i spend money on this issue?
HBOOT: 1.13
RADIO-3805.06.03.03
Android 2.3.3 official ROM
should i try to S-off it and install a custom ROM?
im afraid that it might freeze and break
ripnix said:
maybe a new display would fix this?
what else could i try before i spend money on this issue?
HBOOT: 1.13
RADIO-3805.06.03.03
Android 2.3.3 official ROM
should i try to S-off it and install a custom ROM?
im afraid that it might freeze and break
Click to expand...
Click to collapse
Is it under warranty?
If so I'd bring it back, if not i'd go the custom ROM route.
The fact that you can turn it off/on again and the issue is fixed makes me think it is software related.
I agree with scoobysnacks, i would do the same
most probably software related. i normally use "keyboard from android 2.3" app from the market, back in those sense 3.0 days it worked brilliantly but when i flashed any sense 3.5 roms, the a and k keys become not very responsive. the result?
my texts turn into something li(k)e this. no (a)'s and no (k)'s.
in the end i changed to go keyboard and everything works well again
thank you guys for the advice
as i sad before i hard-reset the device, and the problem is still there, even more i noticed that in some cases the upper part of the display gets numb, doesn't respond to the touch/finger ... again after i turn off the display and back on it works... also when i write texts (horizontal aligned) the left part of the keys aren't working or it just pushes the wrong ones.... i tried to do the calibration thing, but no change
i installed go keyboard and no change,
i just cant write 'w', when i touch the W in the go-keyboard it will write E or Q
whats wrong whit it?
i did S-OFF, and rooted the IS, now ill have to find a quick/light ROM to run on it
any suggestions? for a stable/ light and quick ROM?
ill do this test and if still nothing works ill changed the display, right? any other suggestions?
i did it, i flashed a custom ROM, Android Revolution HD
problem still exists
some more details:
when i keep it in landscape position, and try to write a message
the keys: w d x , are not responding, so every time i try to touch them, a neighbor key activated
any other solutions? before i go and order a new touch screen digitizer?
please, any other solutions? before i go and order a new touch screen digitizer?
ripnix said:
please, any other solutions? before i go and order a new touch screen digitizer?
Click to expand...
Click to collapse
Wondering what will you get if you use swype keyboard..
perhaps touch screen digitizer really need a change then if all not working.
I've got the same issue. The freeezing happens in all screens, and requires the power button to be returned to operational state. This is on a stock IS 2.3.3 ROM.
next i will try S-off, rooting and custom ROM, and see what happens. I can't see how this would be a hardware (digitizer) issue as it comes and goes. Is a little frustrating, and since I bought it used, I have no warranty.
Same issue here too i thought i was alone with that issue, posted in trinity forum.
I'm getting some random lock-ups even sensitive buttons and touchscreen don't respond, It goes away going to sleep and going back, it's so frustrating while web browsing for example
Am I Alone with that issue, or this is sign my CPU is dying?
Click to expand...
Click to collapse
Let's fight together with that problem
Well, completely wiped and installed a new ROM, still the same freezing issue. I've oredered a new digitizer, so we'll see if that works.
New digitizer didn't work either. Gonna try a new kernal, after that, I give up!!
Hi amigo, I face the same problem, maybe this rom is not very stable.
Tried a different Kernel, and still the same issue. I've tried everything I can think of and this phone still seems to randomly lock-up.
Hey guys,
I don't know if anyone else has experienced this, but the back and menu buttons stop working suddenly. This has happened to me twice. A simple On and Off fixes this, but I wanna know if theres a proper fix for it? My phone is rooted with the stock ROM "KKA". Anyone else experienced this?
My phone is NOT rooted with the stock ROM "KKA" and suffers the same problem.
Mone rom is rocket v17 , i got the same problem 2nd time.AND screen didn't wake up.
I have had this issue once so far, rooted with official Arabic Rom. does anyone have a solution?
had to restart the phone to bring it back to normal.
Read on Androidnz blog that this happens sometimes using spen with button press for using menu features like pulling up menu or back button etc.
I'm rooted, standard ROM, rarely use the SPen (haven't got around to understanding what I can do with it). I've had the unresponsive Back and Menu button problems a few times - only solution I can find is to switch off and back on again.
Good to know that it's not just me, but it would be nice to find a solution.
Same issue. Stock rom. Happened to me just now and the stylus was not being used at all.
well i also have that problem. i also know others with this problem.in my case restarting the launcher helps.ofcourse if u have both home and back button not responding at the same time then its not possible.i get both of them not responding at the same time very very rare.at that time all i do is turn of the screen and wait a few minutes.thats all,every thing is normal again.oh one more thing i think its a good idea to keep more than one launcher installed and not making any of the default.it helps switch between them easier.switching between launcher always helps in these not respondig issues.