Hi, I have noticed a problem and I was wondering if others could check if their phones do it or if I need a replacement.
When texting on the hardware keypad the response is rather slow, but more importantly it gets the keypresses out of order! Specifically, the order that I pressed the space key (0). If I text slowly this is not an issue, but if I blast away then I can consistently observe it make the same mistake. Here is my test:
In XT9 mode, start a new text message and type 'it going' really fast. This key sequence is 48046464
If I am texting fast, my Touch Dual will consistently enter 'hug mini', which is 48406464
Note that the space is one place too late.
This happens all the time with any other word combinations, and is worse when the device is stressed. I have no other running programs, I have not flashed from the stock Orange ROM, I have tried a hard reset and I AM typing correctly
Oh, a point of interest, if I train myself to type double spaces then it works, and only single spaces are written! Of course if I slow down though I see double spaces.
So, anyone else (preferably with the Orange ROM but all answers appreciated) have this problem?
I have exactly same problem. It is very, very annoying..
I don't have the Orange rom, I have original swedish rom, but I have the same problem. the most annoying thing is that I can't type as fast as a can, because of the delay.
i just tried this, no problem here. also, the space on mine is the # key.
im using toms rom also.
i typed it out really fast. there was a slight delay till the words showed up but it showed up as what it was supposed to.
have u tried the HTC Update?
There's been notices that that problem was fixed (or at least didn't happened so frequently)
I tried downloading it from HTC e-Club, but no difference.
The hotfix didn't help me, but I have made progress to solving this problem. It seems that the stock Orange ROM is just rubbish, I reflashed with a custom WM 6.1 ROM and it is much better. If I stress the device by doing lots of things at the same time then I can still make the error appear, but texting is actually bearable now when playing mp3s.
It's a shame I haven't uncovered the root cause of the problem. I refuse to believe it is in the Windows Mobile core so it must be something HTC have done to it. Do they have a different SMS composer or something?
Ok so i got the newest stock rom for sweden... i havent modded that much but 1 common problem i keep getting is that when i got the sms application running and press the panels button the device hangs directly.... this is kind of annoying as i use the texting alot..
is this a common bug?
Nope
I just tried it a couple of times on my Xperia GENERIC UK R2A_10 with a whole host of buggy as hell today plugins running and it still switched just fine and no slower than ever.
Maybe it's been a slight translation error in your Swedish ROM that causes the problem.
Does it reproduce every time, and at what point in the SMS app exactly does it happen?
I rooted my phone when i first got it, and installed all the relevant stuff to get it runniong and it was certainly firing along well, until this new update came out and i installed a default image back on so that i could update to the 1.5 (german) now my phone seems to stick a lot and my home seems to want to force close a lot, could this be signs of big problems with my phone? Is there a way to return it to t-mobile factory default as i got it or what would anyone suggest?
Kind regards.
do not know about these errors but maybe you can wipe your phone and install one of the cupcake versions fron HTC/Google or The Dude or JF or Haykuro ...
just search a little bit in the DevForum here
I'm running JFv1.5 and am having similar problems. When I push the Home button the previous app is getting a "Force Close" prompt. It doesn't happen everytime, but it's still annoying.
Besides this issue all I'm seeing more memory lag, but both of these are workable situations. I can still access my apps and I have the additional use of the OSK and A2DP as well as better support for my 16GB sdcard.
In short: I've got fewer issues on 1.5 than I have on RC33 and reverting doesn't make sense unless I have more critical problems.
Hey all,
I just upgraded recently to JF V1.5 and I noticed that the onscreen dialpad does not respond to touch when a call is in process. I have to open the keyboard to input. Its annoying as hell.
I looked all through the settings to see if there was some option to enable/disable the screen during a call but I didnt see anything.
Is anyone else having this problem? Is it a known issue?
I too have had this problem. A reboot will generally fix it. Have you had any issues with calls coming in and Android core locking up?
In any case, I think that in at least in my case, the program "Owner" might be suspect. What do you have installed on yours? Perhaps we can compare and get this narrowed down.
Well the problem went away even without a reboot. It hasnt been consistent.
I havent had any lockups during calls though. The only apps I have installed are:
wifi tether
twidroid
last.fm
skype
where
pixelpipe
movie finder
jf updater
bank of america
beetag
thats pretty much it.
I'm getting the same issue. Of all those apps the only 2 I have are JF and Pixelpipe. I'll uninstall them and see.
It isn't consistently happening for me either but it is damn annoying when it does. I hope Magic users don't get it, without the keyboard you'd be stuffed.
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.