Has anyone been able to figure out why the ATT roms are experiencing the numlock situation when on a phone call. This seems to be the only issue I have experienced on this ROM but is quickly becoming a showstopper.
Number keys stuck while in-call. Doesn't seem to be resolved yet per the Pro's
"8/04/2007 Originally Posted by schaps
Not yet, this problem also occurs on official WM6 ROMs so it doesn't help me to focus the problem.
But for sure this issue is not caused by the keyboard driver."
Put me in the list of people wanting a fix for this. I hope someone figures it out. I often like to text while using my bluetooth, and I don't enjoy having to pull out my stylus to do so.
Just wishing the talented developers some luck in figuring out the problem!
Add me to the list too ... i've looked all over but hadn't found the fix. I remember seeing it somewhere when doing my WM5 ROM upgrade (a long time ago).
Any progress on this?
I'm using Shamanix's Ultimate 1.0.
I don't need to send SMS while calling but I've got the device locked and if I need to check the Calendar during incomming call for example, I need to type my password. Would be really nice to type on QWERTY instead by stylus.
thx
This has been Fixed In More than One Rom....TNT,Vp3g's plus other Roms... I"m going to be Compiliing a List soon of Roms that do and Do not have this Fix.... Certain Schaps Rom also have this Fixed as well but not all...sometimes either he forgets or They Fix interferes with other things onthe ROM not sure....
I can definitely vouch that it works correctly in vp3g's rom.
Would be nice to know what is causing this and how exactly they managed to get it to work so we can fix this on our ROMs.
the fix is already there.
http://forum.xda-developers.com/showpost.php?p=1562185&postcount=63
Related
On messages especially sometimes if I type too fast (and I can type very fast ) it misses out letters or just pauses for ages.
Most of the time the first letter I type in a message gets repeated. Sometimes it just decides to repeat one letter as if the key was stuck down.
On top of this messaging and any application where the device is trying to bring up a user input component is SLOW.
Ive not seen these problems mentioned anywhere yet. Is it just me?
Lewis
No, I've got the same problem. But I don't use that keyboard all that much. The main point for me was to get a phone/PDA with WLAN built in, something I believe the 9090 was first with.
same here, it's very annoying..
with the mms app this doesn't happen, input is as fast as in 2003..
Yeah, it is a bit laggy, still acceptable for me.
isn't it possible to somehow replace the messaging module? i use the keyboard very often and this can get really annoying..
I cannot speak for everyone, but I have found a solution that works.
Apparently, the Messaging applet is not getting enough clock cycles to properly process the keyboard input.
For me, simply closing Internet Explorer does the trick. (go into Memory, and make sure it's not listed in Running Programs) Try it now.
If it still occurs, soft reset the phone, and then attempt to use Messaging. Does the problem still occur? Probably not.
Let me know if this solves the issue. I will look more into it when I get the free time.
I found the keyboard horribly slow. That's straight after resets of all kinds and definately no IE.
I have the repeating problem at times, and I never run IE or any other programs at the same time minimized. I use PocketPlus, so programs aren't minimized, they are closed.
that's no good for me, still slow..
just installed rom 1.60c in my gf's qtek 2020 and it's fast as hell! messaging too..dont understand this strange behavior on the BA..
About the keyboard repeating, you can reduce the repeat rate at the keyboard settings..
Keyboard Issue
Has anyone actually solved the problem with the messaging program?
I downgraded back to WM2003 SE because message writing was such a pain. I would like to have WM5 but if and when someone can correct the messaging application.
Any news?
Thanks
Lewis
updated my Blue Angel to WM5 today and found no problem with typing. TheGadgetGuy's probably right about the memory.
I used to have the problem if I would type to fast it would repeat a lot, example "test" would be "testtttttttttttttttttttttt", I found a way to fix it:
A lot of people have been complaining with the same problems with the thumbboard in WM2005, well I found a way to fix it. As you know if you type really fast like a lot of us do with the thumbboard it will repeat and get stuck on a letter, example "fix" turns into "fixxxxxxxxxxxxxxxxxxxxxxx" then you have to backspace it all. Well let's just cut to the chase, the way to fix it is goto your Start > Settings > System > Keyboard > and goto Repeat Settings, and turn them all the way off (To the left). Tah dah, enjoy .
^The text above is copied from Zevink.com
Had all sorts of problems with WM5, one of the most annoying was this keyboard lag... I type a lot of SMS with it so this made the device unuseable for me.
Happily went back to 2003SE
The blue angel is the biggest pyle htc ever released. That is what is wrong with the ba.
Thanks for that Mikee4fun ... not quite so helpful ...
The only hardware issue I can see with the Blue Angel is with the Radio (Both Bluetooth and WiFi) in that they both seem to be poor in range and BT unstable. That said, BT in particular, may still be a software issue as under WM5 it seems a whole lot more reliable ...
To say the BA is a Pyle (Pile?) based on the fact that an internal thrown together version of WM5 (Trust me, this is the case if you do a bit of Hex editing on a decrypted nbf file and see all the temporary bootloader code which has references to ALL HTC devices by codename) is lacking in areas is not really a solid deduction. From what I have seen of this version of WM5 which has arguably been created in weeks rather than months like version 2003SE, I would say that it is on the whole a very impressive software and hardware solution.
I only hope HTC take the decision to officially update the BA to WM5 in order to fully eliminate all the software bugs in WM2003SE as even the current version of WM5 seems to me a whole lot better than even the latest patched WM2003SE version.
I cannot see it would take them a great deal more engineering time to correct the few issues that remain such as speed tweaks and the odd driver / software update to release a very impressive WM5 version. As Maimach has already proven a number of issues were quite simple to fix (Well, for someone as clever as Mamaich anyway!!!) ...
I had poor keyboard performance (lag) - made me downgrade
Bebbo, I'm afraid that won't happen because of the wish to make people buy new hardware instead of upgrading the stuff they already have. Remember that the biggest selling point of the Wizard and Universal is the WM5. So can HTC create a good WM5? Of course! Will their customers (not us, the providers, Dangaard and Brightpoint) allow them to? Probably not.
Well about the only thing that worked on WM5 was bluetooth...
I get the damned memory error on WM2003SE.... :x
How annoying. I think I'm going back to WM2003se. WM5 isn't that great. It behaves alot like WM2003fe except buggy :S It's not worth all the hastle just for on screen soft keys.
Hey guys,
First post on the forum, so I hope I don't offend/irritate with my dumbass questions,
I successfully flashed to the Black Shadow IV rom yesterday. I installed all th e helpful cab files to restore my settings to the orange standard and got the skdcert fix for the voicemail quirk. All seems (seemed) to be running smoothly but I then stumble upon a problem.
I have found that I am resetting the device more than I should due to the fact that whenever I try to make a call, 5 times out of 10 the phone just crashes, all the buttons freeze up and the touch screen doesn't respond. On the odd occassion the buttons freeze but the screen still responds butr there's no way to drop the call. It just wont have it.
I upgraded to the Black IV shadow rom, but did not upgrade the radio which was out of the box at version 1.38.00.01. Could this be the root of the problem? I am running SPL- 2.10 Olipro.
Any ideas guys, you're the experts, I'm just a squirrel trying to get a nut.
Thanks in advance.
Gav
The 1.38 radio is pretty stable. However, if you are in the US, you might want to try upgrading it to the 1.40 radio which is AT&T optimized.
That ROM was released and is supported here: http://www.4winmobile.com/forums/htc-hermes/
Same happend to me too, I used Black Shadow IV for a week and now removed it, It is not stable.
My Jasjam hangs all the time and when conncting to PC.
Regards
Yeah, same. I used it for 3 days or so and crashed frequently. No additional programs installed either. BAD ROM
i've had nothing but a good experience with Shadow IV. ::shrug:: seems stable enough to me. it's never locked up on me and i've never had to reset except when i chose to to clear out the old memory once in a while.
as i mentioned in another thread, i have not installed any spb apps since they seem to have problems w/ WM6. i've had problems on a couple of different ROMs w/ the Spb apps.
could it be something that you've got installed and not the ROM itself? i had to do a little process of elimiation by installing basically one or two apps a day and seeing how it ran. things started going badly when the Spb apps were on there (Mobiel Shell, Time, Weather, Diary) so I haven't reinstalled them.
anyway, it could be something other than the ROM that is causing the instability.
regards,
mark
having multiple problems as well. cannot send text messages on cingular even after trying multiple fixes, frequent slowdowns, have had to soft reset at least once daily and also having problems with random lockups when charging. Going to reflash another rom.
having multiple problems as well. cannot send text messages on cingular even after trying multiple fixes, frequent slowdowns, have had to soft reset at least once daily and also having problems with random lockups when charging. Going to reflash another rom.
Am on Orange UK, and after running Black shadow for a while now I would rate it as the most stable ROM I have used. Admittedly I have only dabbled with some of the others, but have not felt the need to do more as am happy with what I have.
I did have an issue with SPB weather that others did not seem to have, but after romoving it, everything seems to be running fine. I soft reset every few days etc but I am happy with that.
Tis a bit strong to write BAD ROM with such certainty based on an individual experience, given that it works well for so many. Perhaps "This ROM did not work well for me" would be better.
Just a thought.
Sleuth255 said:
The 1.38 radio is pretty stable. However, if you are in the US, you might want to try upgrading it to the 1.40 radio which is AT&T optimized.
Click to expand...
Click to collapse
May be it is the radio rom, I have now installed radio 1.38 then Black Shadow IV and will try it for a few days and see how it works.
Also crash
Also crash and then back to Black 3.5 rom is Stable!
Still the same even with Radio 1.38, Crash when connected to PC and deep sleep in standby.
Use to have same problems while running CE-Star. Virtually permanently freezing on making/receiving calls, sending SMS and simple operations with the device.
After manualy setting chinese character set (thanks to XDA-Devs WIKI ) the ROM is extremely stable. Even trying to "destroy" the system with multiple operations (calls, internet browsing, sync, installing new soft, etc.) do not freezes it - very stable.
Suspect in your case you are using software which makes some changes to the system, consequently destabilizes the ROM
marttin said:
Use to have same problems while running CE-Star. Virtually permanently freezing on making/receiving calls, sending SMS and simple operations with the device.
After manualy setting chinese character set (thanks to XDA-Devs WIKI ) the ROM is extremely stable. Even trying to "destroy" the system with multiple operations (calls, internet browsing, sync, installing new soft, etc.) do not freezes it - very stable.
Suspect in your case you are using software which makes some changes to the system, consequently destabilizes the ROM
Click to expand...
Click to collapse
Hi,i am runing Black 3.0.1 and ce-star,like ou said freezing ,and my problem is when i use CE-STAR keyboard,it is Freezing too.where i can find the setting chinese charscter set?
thanks
Been running Black Shadow for 5 days, alongwith Radio 1.43, without any problem...
I've been running Black Shadow on T-mo US w/1.43 rom and I've had no problems.
I have been running Black Shadow since it was released and no problems so far.
chg1282002 said:
Hi,i am runing Black 3.0.1 and ce-star,like ou said freezing ,and my problem is when i use CE-STAR keyboard,it is Freezing too.where i can find the setting chinese charscter set?
thanks
Click to expand...
Click to collapse
Use WIKI and SEARCH funstion
You can go first to http://wiki.xda-developers.com/ and click on Hermes. After that use SEARCH function with keyword "chinese". Should get the following page:
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweak_Language_Chinese
I am using for few days Black Shadow with 1.43 Radio, able to read Chinese Characters thanks to the described in WIKI method and no problems. Personaly I installed A4 input method as it serves me at best. I didn't change the registry manualy, but used the cab, it works perfect. Simply follow the instructions.
The only issue is that when serving internet with IE Chinese sites do not apear properly. Suppose it is needed additional fixing of the fonts in IE. Do not have time at present to explore the issue, but suppose to deal with it next week. In case you find a solution for IE please share the method on this thread-- Thanks
PS. Have tested Micrsoft Input -- simply do not works. Causes a lot of problems and destroys totaly the standard inputs
All,
I have been running this ROM for just under a week and the thing has been 100% solid - not a single problem.
I also agree with a previous statement in this thread, that to refer to the ROM as "BAD" based on a single attempt is somewhat unfair! Maybe it is this sort of thing that has forced some of the more senior Hermes developers away from this site and on to another location. Ever thought about it that way?
It is just my opinion, but we (all forum users) should do one of two things if we "chose" to use someone elses development. They are,
Acknowledge (privately or publically) the time and effort that has gone into producing something. The best way to do that is by constructive feedback even if the experience hasn't been as you expected
Say nothing if you can't make it constructive!
To place a one liner in a response with a "throw away" comment is about as useful to either the developer or the other forum users as.........well,..................no I won't go any further because it's not constructive
For the record - this version of the Black release has rectified a localised issue I was having with my WLAN that other version had not resolved.
If you chose to use it - great, join in. If not, equally great. Good luck with your chosen selection of ROM.
Rant end
marttin said:
Use WIKI and SEARCH funstion
You can go first to http://wiki.xda-developers.com/ and click on Hermes. After that use SEARCH function with keyword "chinese". Should get the following page:
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweak_Language_Chinese
I am using for few days Black Shadow with 1.43 Radio, able to read Chinese Characters thanks to the described in WIKI method and no problems. Personaly I installed A4 input method as it serves me at best. I didn't change the registry manualy, but used the cab, it works perfect. Simply follow the instructions.
The only issue is that when serving internet with IE Chinese sites do not apear properly. Suppose it is needed additional fixing of the fonts in IE. Do not have time at present to explore the issue, but suppose to deal with it next week. In case you find a solution for IE please share the method on this thread-- Thanks
PS. Have tested Micrsoft Input -- simply do not works. Causes a lot of problems and destroys totaly the standard inputs
Click to expand...
Click to collapse
thanks a lot
Hello friends
I have Morna's 1.8 WWE Enhanced ROM (great ROM by the way) but I have noticed this flaw/bug on this and other ROMS in the recent past.
When I select SMS and begin to write my message after inputting the first word or first character (either directly or through T9) it just disappears after the screen blinks for a split second.
Therefore I have to just type in a "dummy" or "fake" character first before I type in my real message.
I have noticed these on the 2.03 ROMS. Its quite a problem especially since I sms a fair bit.
Does anyone have any solutions please?
Thank you.
Hey,
Yeah noticed the same problem on loads of the ROMS I've tried.
Currently I'm using Macadam (love it), Touch Input has this issue, however, when I switch to Shapewriter, which I prefer, the problem goes.
Give shapewriter a go?
I have had the same issue with every rom I've used for a while. It seems to be happening after the mass change to the 2.0x roms.
v2.xx ROM's...
I agree. I've only suffered this issue since using v2.xx ROM's. It doesn't happen every time I use the keyboard though, so what's actually causing it I don't know.
Has anyone noticed if a certain application is causing it, or is it a 'general' keyboard issue. It might be related to the messaging app and nothing else?
Yeah, I also experience this I'm running rstoyguy's ROM and have had this same issue wuth many different ROM's...
I am glad it not only me that has this problem.
I have only noticed it in the last round of roms that came out.
I have this problem too, even on the vanilla HTC ROM update (after I restored my SPB backup - didn't try sms before restoring)! At least this thread tells me I should go back to an older version ROM until someone manages to fix it!
I'm working with a Tilt2 running the stock euro HTC 6.5 rom
and I have an odd delay. once a call comes in and I either use
the "slide to answer" feature or if i just press the call answer button
there is a long...sometimes 10 second delay between my action and
the call actually connecting.
During this time i often miss calls and ive asked those who are calling me
what they hear and they say my phone goes silent for 10 seconds before i
answer. any ideas?
Someone else found this link, not me -- and I haven't tried it, but I have experienced similar (3 secs though and not often).
http://forum.ppcgeeks.com/showpost.php?p=458469&postcount=1
After doing this it does seem to pick up the calls a lot faster but now I'm getting a slew of various data connection errors. SOTI wont connect, my weather tab will not connect.
Thanks for the assist I'm going to try and find a happy balance between the two reg settings
Update: I was wrong initially about the reg edit fixing things. I had my wife call immediately after the edit and it seemed to fix it when I noticed the connection issues through various programs.
Well during work today I answered about 7 calls. The delay affected all of the and on all but 1 the call actually disconnected before it allowed me to speak. so i will be reversing the red edit to combat the connection issues.
So clarify a few questions I Got regarding this:
When the phone rings and I press the answer button or "slide to answer" the ringing does stop and the icon in the task bar shows a call connected. but for me and my caller we hear dead silence for 10 seconds until they either hang up or the call connections. Any ideas friends?
I'm having the same issue on my US AT&T Tilt 2. It is driving me crazy, the regedit did not fix anything for me either. Did you figure you this out at all?
Are you guys running stock or a custom ROM? I have had this issue in seven ROMS. In my case, it seems that my phone has to have the ATT Dialer to avoid this. Tried Energy Photon and Leo,Josh Koss, TPS, and Shadowline. All had this problem. I'm now on Fusion 6.0 with the ATT Dialer. Not one issue. Day before I flashed this one, I missed 19 calls at work because I couldn't get the slider to register. Tried TPC's latest last night(he uses the HTC Dialer), missed calls. Flashed ATT Stock no problem. Fusion is the only other ROM I found with an ATT Dialer.
It seems there is a conflict in the device when connecting.
Some things to try:
- remove the custom dialer (just use the WM6 dialer, but this will loose video calls)
- check if there is some call-recording software that kicks in
- does this happen when the device is off or also when it was already on?
I'm Using HTC's stock rom instead of the ATT rom. since I'm America I really would not be apposed to loosing video call from the dialer since Its not supported on my network but I'm really not sure how to change the dialer back to AT&Ts ...is this something that would have to be cooked into the rom because I cant stand AT&T's rom.
Flash a ROM that uses the AT&T dialer: problem solved.
Your options are: Stock AT&T, At0mAng, Arrupenthal, Twopumpchump roms.
So how do we go about getting a cab file of the AT&T dialer, video share and PTT packages that each individual user can apply as needed? Is this even possible and would it require uninstalling whatever dialer the chefs cooked in? I think it would be impractical to ask the chefs to make two versions of their ROMs (one for at&t tilt2 users and one for everyone else) as I have attempted to cook my own ROM and know how difficult it can be.
Thanks,
Stephen
hi
sorry. bad post
Ok here's my problem:
I make custom dutch roms for the Rhodium (touch pro 2).
I use the latest XIP/SYS builds (28009 at this moment) and I use manila/sense 2.5
(Almost) everything works great!
I also own a pioneer car-entertainment set (avic f900bt) which has a built in parrot bluetooth carkit.
Pairing goes perfect and I can transfer my phonebook and make calls.
The problem is that when I recieve a call and try to hang up the system hangs and needs a reset. My TP2 also hangs for a while after such an event and then after minutes goes back to the today screen.
At first I thought it was my carkit, but my wife's samsung and my brother in law's blackberry work fine.
Then I tried my own phone with the latest OFFICIAL 6.5 rom (dutch) and it worked great.
So I started to trial and error with different adjusted roms. I got it all working with the newest XIP/SYS builds. But the problem seems to lie somewhere in manila 2.5. I even got it working in manila 2.1 without any bugs
But with 2.5 I get the problems above. And I forgot to mention another bug:
- When I make a call or recieve a call I do not see a 'red phone' button to hang up which I do see with other phone's or roms without manila 2.5. So I have to end a call on my HTC instead of my carkit. And when I try after recieving a call it hangs as described above.
After 2 weeks of flashing and trying I give up...
I use the OEM from the latest official dutch 6.5 rom so those drivers can not be the issue. As stated before...It's all pointing to manila 2.5. But after flashing disabling manila does not fix the problem. So it must be somewhere in the cooking proces (Ervius VK 1.82)
Please one of you supreme chefs help me out here because it's frustrating me now and I want to get it working as it should.
Thanks a milion in advance!!
EDIT: to the mods; I did not know where exactly to post this after the re-organisation. So please move if neccesary.
Almost 170 views and no comments??
Please fellow cooks...I'm desperate...
Well i do think you already have an answer.
But the actual non existing pressure you feel from users that always want the latest no matter how buggy it might be
When MS started to "Leak" builds beyond 20000 (But before 21054).
I also started noticing Bluetooth pairings going haywire and acting differently.
As i don't care that much about what most "Flashers" think and tend to believe that the choices i make concerning cooking a rom are probably more founded in what is right.
I tend to stick to stable OS Builds. It's the New Age XDA dilemma, either dish out unpredictable New Builds, or make a ROM that in the first place Suits you and has the functionality You need.
In this case that would be an older SYS.
I think that also because of TP2 has now switched to different Bluetooth Stack and 2.1+EDR isn't helping.
And it might be that MS is actually working on getting up to speed and changing their own BT Stack, so HTC will not need to turn to WidComm for the BT Stack.
I do believe that there are a few Senior Cheffs and some Non Cheffs do probably know which other parts (besides the Obviously named Bluetooth related SYStem parts), might be related to dealing with Bluetooth Pairing and such.
Whatever solution there might or might not be, don't hesitate to make it hybrid.
Use the old fashioned method of dividing and conquering.
(Get a good supply off Coffee)
Start with Stable Release Build SYS replace 50% test. (leaving all obviously Bluetooth related Packages from Stable Build)
Replace the Next 25% Test etc, you know the drill.
And hopefully isolate the Packages from SYS that have related Files to Bluetooth.
Luckily there's already enough SYS packages you can rule out like enterprise, entertainment, Office and such.
I know it's not a cut and dried answer, but hopefully i can "Je een hart onder de riem steken" that your up against this alone ATM.
But consider this, how many time do you have at hand, and is it worth it putting a lot of time into it, only finding out MS fixes it in a few "Leaked" Beta Builds.
Who knows maybe this Bump does get a few others on to this thread that has already tackled this problem.
(Da_G is the most likely, that i know that might know other Bluetooth dependencies inside the SYS)
Cheerz,
PS: don't forget to enjoy the snow a bit.
Pairing with Avic f900BT
I too have the exact same problems. The phone is straight out of the box.
Any easy ansewrs as yer?
Magic3091 said:
I too have the exact same problems. The phone is straight out of the box.
Any easy ansewrs as yer?
Click to expand...
Click to collapse
I got it working on mine using the attached cab