Any fix for keyboard missing keypresses? - HD2 General

Even when typing at normal medium speed I find the keyboard will completely ignore/miss a letter or two at fairly regular intervals. I've tried editing the registry to lower the initial delay value down all the way to 1ms, but the issue still occurs. Is there a known cause/fix for this? Thanks...

try either of the last two cabs found here
http://forum.xda-developers.com/showthread.php?t=604831

g2tl said:
try either of the last two cabs found here
http://forum.xda-developers.com/showthread.php?t=604831
Click to expand...
Click to collapse
Thanks.. I took a look and the issue I'm having seems to be a bit different from what those cabs address. Rather than oversensitivity or extra unintended keypresses, my screen/keyboard will semi-frequently (every 20th word or so) just momentarily become unresponsive and completely miss about two letters of keyboard input.
It's like the keyboard just locks up for about half a second and doesn't even display the little popup letters over the keys at all, and when it un-freezes it doesn't "catch up" or realize that two more letters were typed in the meantime. so if you were trying to type the word "keyboard" you would very likely end up with something like "keoard" as the two missing letters are just skipped completely.
Normally the sensitivity of keyboard and touchscreen in general is very very good and I only have to touch very lightly to get a response. 19 times out of 20 this is the case with typing on the keyboard no problem. Just every here and there semi-regularly a couple of letters will invariably get skipped, again without even displaying the popup boxes over the keys, and I'm not even typing particularly quickly either.
Are there any cabs for this issue..?

Just following up to my thread here from almost a year ago. I've tried multiple roms from XDA, as well as registry tweaks and fixes, and still cannot solve the problem. Does anyone NOT experience this problem, ever..? If you don't, could you please tell which ROM you're using, and what (if any) registry edits you've used?
It is completely impossible for me to type any medium-length sentence on my HD2 without at least a couple of letters/keystrokes being missed and ignored entirely. Every time. I'm willing to try anything but I desperatelty need help, as this one glitch renders an amazing high-end smartphone totally unusable for me...

What ROM are you using now? I am running the T-Mobile 3.14 ROM and I have similar priblem with my keyboard but not near as bad as you say you do. I have not tried tbe reviztry tweek hou mentioned previously in this thread.

T-Macgnolia said:
What ROM are you using now? I am running the T-Mobile 3.14 ROM and I have similar priblem with my keyboard but not near as bad as you say you do. I have not tried tbe reviztry tweek hou mentioned previously in this thread.
Click to expand...
Click to collapse
Currently I have Dutty's ROM installed but I've tried multiple other ones including Energy, Elegancia, Laurentius etc, and the problem is always there, so I don't think it's the fault of any of the ROMs. Either I just have a bad unit, or all HD2's do this to some extent and the vast majority of owners just consider it an acceptable quirk and don't bother complaining about it.
The touchscreen on my HD2 is extremely responsive and fast in all other scenarios, and even when typing most of the time, so I dont think it's defective per se. It just seems that with a good degree of regularity the phone/OS decides to completely "pause/freeze" for a half second or so before resuming normal operation. So brief an instant that it isn't noticeable under any other cirumstances except typing on the keyboard, where it's long enough to eat up anywhere between 1-3 keystrokes depending on entry speed.
It's really a shame, because the Leo is in many ways the most powerful, super awesome smartphone I've ever used, but because of this one utterly intolerable bug it sits on my shelf totally unused, currently in favour of my Sony Ericsson Aspen which is far less powerful, but at least reliably useable for typing.
I'd be willing to buy another HD2 if I really thought it was my specific unit that was responsibe, but right now I have no dependable way of knowing that.

Have you tried other keyboard applications?

I found this cab in my sd card.
I remember it worked in my Topaz.
Give it a try.

I will give the cab a shot tonight when I am back at home, thanks. I have indeed tried alternate keyboards such as Resco and a few others, with no change or improvement, so I don't think it's the HTC IME keyboard specifically at fault either. My guess is that the whole screen is becoming unresponsive for that half second or so, not only the keyboard. It's just that it's only noticeable/irritating enough to be an issue when typing, because I have to constantly stop and go back to re-enter letters that were ignored along the way. It's a real dealbreaker for me on an otherwise outstanding device.
Do I take it correctly that you yourself never, ever encounter this issue when typing on your own HD2? Again for the record, it's not a matter of my typing too lightning fast for the Leo to keep up with. Even typing at moderate/regular speed (2-3 letters per second) the missed key issue occurs regularly.

I tried the cab but no luck unfortunately... I really wish I knew whether it was a problem with my specific unit or a model-wide issue that just doesn't get mentioned that often.

Is there anyone reading this, who has an HD2, and does NOT ever encounter this issue of typed letters/keystrokes being missed? Is there anyone out there who can say that their HD2 catches every keypress, every time without fail?
If this is true and applies to you, please respond and let me know! If there are units out there that are totally free of this problem, then I will not give up hope, and will try to replace mine. But I need at least a confirmation or two that some human on the planet somewhere has an HD2 that does not experience this problem...!

Related

HTC HERO awfully slow when texting

had it about 2 months.
been great so far up till this week, when texting and typiung anywhere its slow as a badger...e x t rem el yyyy slow...........
takes forever..whys this??
havent upgraded firmware since buying it, should i?
should i delete my existing texts?
duno?
please advise...thanks!
ash213 said:
had it about 2 months.
been great so far up till this week, when texting and typiung anywhere its slow as a badger...e x t rem el yyyy slow...........
takes forever..whys this??
havent upgraded firmware since buying it, should i?
should i delete my existing texts?
duno?
please advise...thanks!
Click to expand...
Click to collapse
Does it also happen when you reboot youre phone? If not, you might be running out of memory. If there is a update availble for youre phone, its always adviced tot do a upgrade.
Yes when i reboot my phone i still have the same problem :-(
ash213 said:
Yes when i reboot my phone i still have the same problem :-(
Click to expand...
Click to collapse
Well, then i am not able to advice you further. Maybe as you stated you should clean-up some text-messages. Or do a factory restore or update. But the last two suggestions are really drastic. You loose all youre data.
Hope some other member is able to help you
Did you notice this issue after installing a certain application?
If push comes to shove try TouchPal.
Free app on market.
i have the same issue sometimes. even after the rom update, or even moreso.
many times putting in text will be laggy and i have to wait. this wasn't the case in the beginning so i'm wondering too what is causing this lags...
install a app manager (Taskiller) will do and post the list of running apps, I suspect there will be something running in the background that is the culprit.
yeah i sometimes get the same issue - especially annoying when typing and I press the space bar, and it doesn't register the spacebar.
Huey85 said:
yeah i sometimes get the same issue - especially annoying when typing and I press the space bar, and it doesn't register the spacebar.
Click to expand...
Click to collapse
I fixed this by re calibrating the keyboard to my finger.
I came on here tonight to ask about the very same problem and found this thread.
My version of the problem is slightly different:
Usually when I've just turned on the phone texting is OK. After a while it becomes very slow and laggy, I mean glacial. If, for example I receive a text and want to reply straight away I'll hit 'reply' and it will take several seconds for the text entry screen to appear. Then the keyboard is laggy, literally two seconds delay after hitting a key before the letter shows on the screen.
Sometimes though, it will start off slow, like I just said and then half way through the message normal response will be resumed.
I did have Touchpal installed but this became very, very slow. Reverting to the standard keyboard improved things but still very slow as described.
I thought maybe it's something running in the background slowing things up but how can I tell what's running? Is there a good app for monitoring running apps?
I've just installed taskiller.
Amazing how many bits and pieces are running really.... anyway, killing a few running programs has improved things just now.
I'll keep an eye on it.
hi yeah i had the same problem as you when i was using the modaco rom
but then i changed to the updated rom
HTC Generic 2.73.405.5 with radio 63.18.55.06EU_6.35.06.18
on this website... first post
http://android.modaco.com/content/h.../03-09-hero-roms-radios-in-update-zip-format/
and all was fine
You will have this problem with many phones... On the hero it does not lag that much imho, it just takes a while to load many messages, like 100 and above will take a while, and sometimes the keyboard takes a while to load, that is true and I can confirm the same thing here :/
xTuX said:
You will have this problem with many phones... On the hero it does not lag that much imho, it just takes a while to load many messages, like 100 and above will take a while, and sometimes the keyboard takes a while to load, that is true and I can confirm the same thing here :/
Click to expand...
Click to collapse
Well, when it is slow it is glacial on mine!
If it's misbehaving it can be five seconds from hitting the messages icon to actually getting anything on the screen, then a further five seconds after selecting the appropriate thread, then two or three seconds to get a useable text box to type into and then each letter takes a couple of seconds to register in the text box.
It's taken me a couple of minutes before now to actually get a two or three word reply sent off! Irritating in the extreme when you're really busy and just want to fire off a quick text.
I think you haven't updated to the lattest release of HTC for the Hero?
Then do so since it will fix your problems.
As people said here if it has to do with apps running in the background this is much better handled on Hero.
Android OS keeps all apps that you start in the background and begins to close apps if memory is getting short.
cheeriot said:
I think you haven't updated to the lattest release of HTC for the Hero?
Then do so since it will fix your problems.
As people said here if it has to do with apps running in the background this is much better handled on Hero.
Android OS keeps all apps that you start in the background and begins to close apps if memory is getting short.
Click to expand...
Click to collapse
Mine's the T-Mobile G2 variant which I'm keeping stock (for the time being). The latest HTC ROM update has not yet been released by T-Mobile!!!!!
The problem I constantly get is some keys registering as a long touch, so I get the secondary symbol instead of the letter I intended. I press the key as long as all the others, but the phone seems to hesitiate for a second, then insert the symbol instead of the letter.
Sausageman said:
The problem I constantly get is some keys registering as a long touch, so I get the secondary symbol instead of the letter I intended. I press the key as long as all the others, but the phone seems to hesitiate for a second, then insert the symbol instead of the letter.
Click to expand...
Click to collapse
I sometimes get this also, but only in combination with the slow behaviour described above. If the phone is performing at normal speed then the long press problem doesn't occur.

HTC Messaging keyboard... is it me or am I crazy?

So, here are a few of the things that happen to me with the HTC keyboard when I (try to) send SMS/MMS
(Biggest complaint) When I type fast, all the letters will get through, but the spaces won't register till the end (ie, the space char has lower priority than other chars?)
An example would be if I typed "Hello world, how are you?" really fast the result would be "Helloworld,howareyou ?"
General slow down when I am typing
Tactile feedback delay
skipped chars when typing fast
I figure since our phones have a 1Ghz processor and a multi-touch screen, simple IO wouldn't be a problem, but it seems like texting is faster and more fluid on my sister's feature phone than on my HTC HD2... I don't think it is right that with all that power, simply typing fast causes slow down...
Is it me? Or is this the norm?
p.s. I'm running on kumar's latest w/ HTC messaging (haven't tried the w/o HTC messaging) and I've experiened these problems txting people w/ 300-600 txts, people with 0-100 and in the blank or create new txt. But I mean, 600 txts isn't that much memory... why would it matter anyways?!
okay so I'm not alone....
I have this EXACT same issue. I had it with the stock ROM so I recently flashed and I'm using the Elegancia ROM and I love it, but texting still sucks.
Biggest problem, spaces never seem to register. Second biggest, when Im in geek mode cranking out long texts I have several misspelled words because it misses letters...
Is there an alternative MMS tool I should be using? For instance in the past I always used HandCent. Is that not the issue?
I love this phone but being happy with it has turned into a Part-Time job!!!
The newest Energy ROM has a new IME version (soft keyboard) and it totally improves the typing experience. The keyboard is now amazing for me and I can now type as fast as I want.
sms its horrible on t-mobile roms they need to fix it
4theU said:
okay so I'm not alone....
I love this phone but being happy with it has turned into a Part-Time job!!!
Click to expand...
Click to collapse
lol! SOO TRUE!!! But all things that make me happy are part/full-time jobs. Wife, phone, computer... I'm just glad I'm too poor to own a nice car!
jdwrrzmm said:
The newest Energy ROM has a new IME version (soft keyboard) and it totally improves the typing experience. The keyboard is now amazing for me and I can now type as fast as I want.
Click to expand...
Click to collapse
I haven't done an Energy ROM since the first one came out. I might have to give it a try. My biggest issue with the Energy ROMs was that it drained my battery really quickly (Hence the name Energy) Has that improved? I like Kumar because of the stock look and feel, but maybe to switch it up I'll give it a try
josemedina1983 said:
sms its horrible on t-mobile roms they need to fix it
Click to expand...
Click to collapse
YES! Exactly.... It isn't our fault and we shouldn't fix it. 2.13 did nothing AFAIK to improve SMS...
Well, I'm glad I'm not the only one! phew... makes me feel better actually
joe_coolish said:
I haven't done an Energy ROM since the first one came out. I might have to give it a try. My biggest issue with the Energy ROMs was that it drained my battery really quickly (Hence the name Energy) Has that improved? I like Kumar because of the stock look and feel, but maybe to switch it up I'll give it a try )
Click to expand...
Click to collapse
The battery life is not the ROMs problem actually, but the ROM does have more stuff in it so your phone does, more ...
The Radio ROM has more to do with battery life than the OS ROM does ...
I get more than a full day out of mine .....
I think my battery life is about the same with Energy, possibly even longer than stock.
noticed with energy rom after running it for one day after my full app setup that the keyboard lag which HAD disapeared, however noticed several times typing dramatically slowed down(until soft reset), it became so slow it was unusable.
However, I will say, upon every soft reset, typing is much much faster than stock, space bar REGISTERS BEAUTIFULLY, and can keep up with me.
On my 2.13 stock rom, thisissimilartogmw themajorityofmy textsappeared. before going back and editing
I think the tactile feedback is to blame for most of the slowdown. When I disable it, I can type much faster. Swype gets bogged down too, that's why I prefer full qwerty without tactile (haptic) feedback.
rufis said:
noticed with energy rom after running it for one day after my full app setup that the keyboard lag which HAD disapeared, however noticed several times typing dramatically slowed down(until soft reset), it became so slow it was unusable.
However, I will say, upon every soft reset, typing is much much faster than stock, space bar REGISTERS BEAUTIFULLY, and can keep up with me.
On my 2.13 stock rom, thisissimilartogmw themajorityofmy textsappeared. before going back and editing
Click to expand...
Click to collapse
Don't you think it's one of the apps slowing down the phone then? On the July 3rd version the only slow down I get is in the Windows messaging client itself, but it's never the keyboard.
an app causing this is very possible. I just dont want to go start blaming tcpmp or coreplayer for the slowdowns.
watcher64 said:
The battery life is not the ROMs problem actually, but the ROM does have more stuff in it so your phone does, more ...
The Radio ROM has more to do with battery life than the OS ROM does ...
I get more than a full day out of mine .....
Click to expand...
Click to collapse
I only used the first version of the ROM, and you can tell from the first couple of posts in the Energy ROM thread that users were experiencing hot batteries, quick battery drain, etc. I was one of those users. While you are correct about the Radio, the ROM also can affect battery based on default settings (ie, screen brightness). Those things can be changed and most relatively easily, some settings reside in the registry which is a little more time consuming. I just perfered to use another ROM.
Oh, and p.s. I like your avatar picture! It reminds me of an animated short I saw on tech TV's Animation show they use to play back in the day. Something about killer coffee beens and a party that was too loud... Good times!

[Q] Keyboard lag

I've got an HTC Hero, it's GSM, ever since new I've found the keyboard to be incredibly frustrating. There's quite serve lag in many apps, typing in forms in some webpages is nearly impossible. Even the built in apps like SMS have lag. It's worse in landscape mode too. Sometimes it'll even pause for half a second mid key press and register that as a long press on that key (although this might be scanning for wifi, because bluetooth audio seems to hitch at similar intervals unless I turn it off)
I've tried countless different 1.5, 2.1 and 2.2 ROMs, with and without Sense, some are slightly better but they all suffer from it.
I've Googled it and surprised to find I don't see any other complaints in the internet about it, finally I've decided to post a question here. I would be guessing hardware limitations, either digitiser or the processor is just too slow.
Would be keen to here other people's thoughts on this though, has anyone managed to fix it?
Edit: I should add that I have the vibration on key press off already.
jbrizz said:
I've got an HTC Hero, it's GSM, ever since new I've found the keyboard to be incredibly frustrating. There's quite serve lag in many apps, typing in forms in some webpages is nearly impossible. Even the built in apps like SMS have lag. It's worse in landscape mode too. Sometimes it'll even pause for half a second mid key press and register that as a long press on that key (although this might be scanning for wifi, because bluetooth audio seems to hitch at similar intervals unless I turn it off)
I've tried countless different 1.5, 2.1 and 2.2 ROMs, with and without Sense, some are slightly better but they all suffer from it.
I've Googled it and surprised to find I don't see any other complaints in the internet about it, finally I've decided to post a question here. I would be guessing hardware limitations, either digitiser or the processor is just too slow.
Would be keen to here other people's thoughts on this though, has anyone managed to fix it?
Edit: I should add that I have the vibration on key press off already.
Click to expand...
Click to collapse
No lags here. Have you tried using lower overclock if you tried Froyd, since it doesn't need overclock to get higher speeds. I run on stock speeds, and have no lag issues using any keyboard in particular.
How bad a lag are you talking about? The hardware should be more than capable.
EDIT: hold on, are you meaning the keyboard is laggy. I think this is just the keyboard itself. Try something like ultra keyboard or swiftkey?
Yeah, the keyboard is laggy, I can almost type twice as fast as it comes up on the screen when it's at it's worst (usually in a webpage typing in a form). I haven't tried either of those keyboards, but I've tried other keyboards including the standard 1.5, 2.1 and 2.2 ones with the same problem.
This is a Hero issue, Froyd is a good rom works to reduce the lag for me
With the new cronos 1.3.0 all lags are gone. I had this issue with all roms before too.
Sent from my HTC Hero

Anyone else Got Touch Lag?

Firstly hello to all my fellow Vega UK users!
For the price I think this device is great, but it does have it's issues.
Do any of you have the problem where the touch screen just seems to stop working? It'll kick in again soon enough, but it's frustrating as hell.
Also sometimes the task manager seems to appear by itself, but I can;t get it to appear when I need it?
I'm using Pauls Add-on ROM. (thanks Paul )
Logicalstep
I havn't had any major lag at all.
What do you mean by task manager? do you mean the one when you hold "home"?
I have found after a lot of use, with a lot of apps open that the system can lag. I guess this is due to system resources. Recommend installing ES Task Manager from the market to manage running tasks.
You mentioned the task manager appears by its self, do you mean the home screen selector? I found hitting the home button to many times makes this display.
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
adfrad said:
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
Click to expand...
Click to collapse
Yes believe so. due to non regulated power supply causes the screen to become over sensitive.
I get this issue too occasionally, vastly increased when plugged in, now and then when not.
I dont use the machine when its charging.
No real rhyme or reason to it occouring in my experience, id love to know of a cause, other than dirty screen.
Rgds
Lok
Yeah It's a bit of a strange one tbh.
Can;t say I have noticed the lag more when plugged in. I though the PSU was regulated, isn't it just a standard Switch mode PSU?
On the task manager, well obviously there is a task manager with Foryo and oon my Galaxy s I hold the hold button down and it appears, however there doesn;t appear to be a reliable way to do this on the Vega....or am I wrong?
Logicalstep
I never get any touch lag, but I'm not convinced "lag" is the word you want.
"lag" would indicate that the response is somewhat behind the touch action. Android versions below Gingerbread do suffer from that when the CPU is loaded but the Vega is better then most in that regard.
What it does suffer from a _lot_ it erroneous and missing touch events (especially when using a poorly smoothed PSU like the one provided) symptoms include:
1. Swipe gestures being terminated before you lift your finger.
2. Long press actions acting like multiple-presses.
3. (The most common for me) Finger up events failing to register (resulting is erroneous long-presses)
But none of these are "lag". I believe there are grounding problems in the Vega and thus how you hold the tablet and the humidity and static of the environment can change the reliability of the touch screen. It's been reported that having the Vega plugged into a desktop via USB increases the reliability of the display (at least when also charging) which lends credence to the idea that it's grounding related.
What I have noticed ín particular is that holding the tablet in landscape mode makes the keyboard ultra inaccurate. You must press much below the level you want. E.g., if you want to write a Q you hit the A key. It's a bit bothersome while writing...
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
CalumD said:
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
HunteronX said:
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
Click to expand...
Click to collapse
I gave if a try, seems to have made typing on the Vega a whole lot better!
Sent from my HTC Desire using Tapatalk
Confirmed over at modaco and by myself also.
Not 100pc improvement but a 90pc. Another essential app.
Goodstuff.
Rgds
Lok
Iv seen lag when I first turn it on but it goes away in couple of minutes, if its on standby it never lags.... cmon honeycomb!!!!
Sent from my HTC Desire using XDA App
The performance pack really reduces start up lag issues btw.
I've seen the device lag sometimes but since i installed pauls peformance pack the lag has gone away making the device so much better.
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
dopeh said:
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
Click to expand...
Click to collapse
Have you tried cleaning your screen and then using the calibration program posted on modaco?
zzleezz said:
Have you tried cleaning your screen and then using the calibration program posted on modaco?
Click to expand...
Click to collapse
Just tried it but doesn't seem to make any difference..
dopeh said:
Just tried it but doesn't seem to make any difference..
Click to expand...
Click to collapse
OK just to be sure...
Is the power supply plugged in? (Screws up the calibration in my experience)
Are you touching the screen while it calibrates?

[Q] Sleep/Charge death issue, think I've tried everything...

Hey guys!
I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.
Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...
--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.
--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.
--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.
--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.
--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.
--I have not uninstalled any system apps with ROM Toolbox.
--I have tried updating my CWM install version to 5.x.
--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.
Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.
The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:
1.) LBE has been perfectly stable on my Incredible 2.
2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.
3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.
4.) The SoDs don't seem to coordinate with the times that LBE blocks things.
5.) Uninstalling didn't make the issue go away.
However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.
Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.
Joey
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Have you ever felt that your device is overheating or lagging a lot ?
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Marvlesz said:
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
Click to expand...
Click to collapse
I do my best to walk all the beaten paths before I ask for help. If I'm going to ask everyone else to spend their time helping me out, the least I can do is demonstrate that solving the issue is worth my own time.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Click to expand...
Click to collapse
I've got five different batteries I rotate regularly. Two do admittedly need replacing, but the batteries all work perfectly in the WinMo handset. Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Click to expand...
Click to collapse
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Click to expand...
Click to collapse
The closest I had to that was a radio revision whereby the bootloader never got past the 'loading' prompt, but neither that, nor the MagLDR install, nor any of the radio installations I've tried have required a reflash due to a botched installation attempt.
Have you ever felt that your device is overheating or lagging a lot ?
Click to expand...
Click to collapse
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Click to expand...
Click to collapse
Not weird, perfectly understandable, and I'm pretty good with keeping my gear unsmashed
Hope it helps!
Joey
voyager529 said:
Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Click to expand...
Click to collapse
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
voyager529 said:
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Click to expand...
Click to collapse
From the redded part, I can understand that the issue started on Alpha, and soon thereafter it had affected Bravo.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Maybe an sdcard ? Have you tried booting android from sd? have you tried booting android from NAND without an sdcard?
voyager529 said:
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
lol, okay then, it's not the device overheating.
Let's narrow it down, your both devices started to have charging/screen issues. With a relatively close time from each other.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
You also said that: on Winmo, both devices ran fine and on Android both devices had SoD's .
This may mean, the ROM you are/were using is simply malfunctioning. Have you tried various ROMs or it is just one ROM ?
Sorry for being late, awaiting your reply
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
Click to expand...
Click to collapse
Ironically, Bravo (the one presently running Android) was warranty replaced less than a month ago due to an actual, legit unresponsive screen. The fact that the pattern is consistently "screen stops responding/SoD/CoD -> hot reboot -> phone resumes working perfectly", and has been on both phones, leads me to put that particular explanation towards the bottom of the pile. Rather selfishly, the supplemental reason to that is that T-Mo isn't going to honor a warranty replacement for an issue that only happens on an operating system that is an unofficial port, so if it is some bizarre hardware issue, it's gonna be mighty expensive to get the phone swapped.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Click to expand...
Click to collapse
I have a thought about that that I'll get to in a moment...
Have you tried booting android from sd?
Click to expand...
Click to collapse
No. good catch =)
have you tried booting android from NAND without an sdcard?
Click to expand...
Click to collapse
I always use the NAND methods, but data is a bit hard to store without an SD card. You have inspired me to do a MicroSD shuffle though. I'll give that a try.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
Click to expand...
Click to collapse
That is, in fact, the answer lol. Originally, Alpha ran Android and Bravo ran WinMo. This problem started, so I switched them around: Bravo was configured to run Android, and Alpha became the WinMo phone. Alpha, which would SoD with Android, has not done so in the weeks since it became the WinMo running handset. Bravo, now sporting Googleware, exhibited the same issues.
To answer your last question regarding whether it was the ROM, I tried the ICS ROM with stock kernel, Dormanix's kernel, Typhoon CyanogenMod (the most reliable in my experience), and HyperDroid. All of these ROMs did the same thing after the first day or two, but hadn't done so in the past: I used both the latest release and older releases that I've used and am 100% certain have worked for me, on my hardware, without fail. As such, this is starting to ratchet back to being a PEBKAC/ID10T issue, but I was never able to pinpoint anything specifically that would earn me a dunce cap. This morning though, I had a breakthrough...
Yesterday, I decided to ditch MAGLDR and opt for CLK instead. I must admit that I do greatly prefer MagLDR, but I was determined to try as many things as possible to get to the bottom of this. I Task29'd, got CLK in along with CWM Recovery, Flashed the ROM again, and started restoring apps from the Google Play Store. No reboots at this point, but then again, most flashes have worked wonderfully the first day. As an aside, I'm torn: I do like the greatly decreased boot time and increased internal storage availability, but MagLDR was much simpler to work with for frequent flashing chores. Oh well.
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Thus, I have foregone MagLDR, foregone ATK, and foregone pulling out stuff in ROMs I don't want. Also, I bought the GOTO lockscreen to help me get rid of the camera launching problem. So far, my system uptime is 6 hours, 14 minutes
Joey
voyager529 said:
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Click to expand...
Click to collapse
lmao !! xD
But that is weird. Why would your phone reboot when the app is frozen ? When you freeze an app, it disappears from the app launcher, but being available on the lockscreen may be the cause.
I don't think it's ATK, since I was on the SD versions of Android, I used to use ATK. And never had a problem. On the other hand, I did notice some random reboots on ICS after freezing some system apps with Titanium Backup.
That said, these reboots shouldn't occur when on typhoon, Hyperdroid or any non-ICS ROM, should they ?
I'm still confused about this "Originally, Alpha ran Android and Bravo ran WinMo. This problem started"
There is no way in hell, two separate devices, would face the same issue without any relation.
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
voyager529 said:
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
Click to expand...
Click to collapse
I don't know if it was just me not reading this whole thing properly (which it probably was, given the amount of information you're providing) but you never seemed to have actually answered the questions about bent battery pins. You mentioned that you are often swapping batteries which makes the battery pins vulnerable to being unintentionally bent out of shape, and they may not be making contact with the battery properly. I have no clue as to how this would really help you (maybe the reboots, not the screen issue), but it wouldn't do any harm to check it out
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Marvlesz said:
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Click to expand...
Click to collapse
Didn't see this earlier, but surely the question is 'why would you leave the HD2 on the world's worst OS?'
I'm disinclined to believe it's the battery pins for the following reasons:
1.) in certain cases, the screen is unresponsive, but the send/end buttons light up, indicating that power is indeed flowing.
2.) in certain cases, I've had the phone do a 'hot restart' (i.e. not going through the bootloader, just showing the boot animation) mid phone call or during other kinds of use. If it was a momentary disconnect, wouldn't it be doing a complete, cold restart?
As for why I'm using Windows Mobile, two reasons:
1.) Android has been giving me issues lately, as this thread clearly illustrates. For all the crap Windows Mobile 6.5 gets, it's been pretty stable, ALWAYS rings, is significantly less demanding on battery life.
2.) Its killer feature for me is that it enables text messaging through Exchange/Outlook 2010, something no other mobile OS presently provides. Additionally, it does all of the core phone functions I use (calls, texting, tethering, web browsing with Opera Mobile, Facebook notifications/caller ID sync, USB mass storage, video/music playback, Swype input, etc.). It might not have 100,000,000,000,000 apps, but the Sencity flavor of EnergyROM is extremely reliable.
Joey
voyager529 said:
If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
Even if you can't feel it overheating, try putting it in a cool place for some time until you can feel that the aluminium back cover is cold to touch, then do something which would normally cause a hot reboot or any other issue. An open window with a slight breeze is normally good enough to cool the phone down (so long as it isn't too sunny or hot obviously).
I guess you're right about WinMo being the most stable OS (although from what I've heard WP7 is very good as well) but I just couldn't live with it. Even if I started experiencing large issues I would do everything in my power to not use that OS again! Used it the other day on my friend's HD2 which he now keeps purely as an alarm clock and it's ghastly, I found it painful to use again.
voyager529 said:
I'm disinclined to believe it's the battery pins for the following reasons:
Click to expand...
Click to collapse
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Marvlesz said:
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Click to expand...
Click to collapse
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
voyager529 said:
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
Click to expand...
Click to collapse
Ah, OK thanks for clearing that up (I, like Marvlesz, thought you simply were refusing to check the battery pins for some odd reason). Did you try the fridge trick? I've read in many places that it works for some people, maybe it could help you too (although don't leave it in there for too long; I'm no expert but I would assume phones aren't designed for that ) and report back.
Just thought I'd follow up with everyone...
On April 22, I task29'd, MagLDR'd, and installed HyperDroid-CM7-Observant-Opossum -v5.9.0. Since then, my phone has been working properly.
Thus, I am chalking the whole ordeal up to one of three things:
1.) an issue with a backup of some kind.
2.) an issue with the internal memory that I managed to 'partition around' when I installed MagLDR again.
3.) an issue with ICS/kernel compatibility that was unique to my phones for some odd reason.
Regardless, for the past ten days, the only reason I've had to reboot the phone was due to a dead battery. Thank you everyone who watched this thread and helped me with my issue. I am greatly appreciative of your willingness and patience.
Joey

Categories

Resources