Bluetooth issue with wm 6.5 and sense 2.5 - Windows Mobile Software Development

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

Related

Am I the only one having Keyboard problems with WM2005?

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.

Unsolved problems with WM 5 for SX66

Can some one summarize the unsolved / pending problems with WM5 upgrade on SX66 Cingular version?
No reply recd so far shows that no one has clear picture of whats working and whats not working.. so sad ... or people dont find time to compile the list.
I wanted this list to be prepared so that one decides when to switch over to WM 5.
Any feedback?
This is why people browse the forums. Kinda unfair to ask someone to compile a bunch of items for you when all you have to do is read. I agree it would be nice but still unfair.
I have an idea, read the forums, make your list, and post it for the rest of people who may come to this site.
Point is, there is no set list. It varies by device and by user and is dependant upon a number of factors....
I have no experience on implementing WM5 on SX66 and thus as asked by you can not work on the list of pending problems and publish to others.
I am not that enterprising that I jump into the update without caring what will happen to my device.
To me it looks that only few problems are pending and rests have been already resolved.
Not to be argumentative...
This is a developer's site... research, test, provide feedback on the results... basically try to contribute to the community.
If you're not enterprising enough to help with testing, maybe you should put together a list based on the main "resolved WM5" thread, and possibly maintain. People would be more inclined to provide feedback...
If you want a stable code for your SX66, use the 1.40c rom which is pretty baked. If you want WM5, it will definitely require a little beta-tester bleeding.
:wink:
I have WM5 on my sx66. I am having no problems except for the ones that everyone is having on all the phones.....
1. Bluetooth disconnecting after so long.
2. Bluetooth disconnection after pressing power button.
3. "G" in today bar always showing even with no connection. (Did not happen in 2003se)
That's it.
Biggest problem unsolved problem for me is the wmodem application to use the phone as a modem connection for a pc.
rschell and jsosow : Thank you very much for such a positive reply.
As for the abovementioned 'G' icon in the top bar there is a registry change / cab file that can remove that annoyance.
I don't have bluetooth disconnection problems so much as when I hit the power button to put the device in standby (and really stretch out the battery) it turns bluetooth off. I've just made it a habit of re-setting my PZP standard profile when I turn it back on and need to make a phone call. Annoying yes, dealbreaker no.
Performance is a little wonky at times. I have the 530mhz overclock.cab developed here, and while it is good, sometimes it can choke a little. You have to turn off some of the sound effects to get it running at a decent speed.
Hopefully there is another WM5 'leak' we can use to get this puppy up to production quality, as of right now its very close!
Where is the "G" fix? I seemed to have missed it.
BT problem fix
BT fix for WM5
http://forum.xda-developers.com/viewtopic.php?t=31779
The only other problem is, e-mail accounts are deleted if you remove the battery.

So we can bring on WM6 - but why?

Hi all
I just got myself sent a Hermes the other day and I was looking around here, my favourite XDA resource, for nifty things I could do with it. One thing that seems to be all the rage is upgrading to WM6. Now, I'm all in favour of upgrading and the amount of information and material here is, well, staggering. Overwhelming even. But, for all I read, I miss one critical thing: why do we upgrade to WM6? What does it give us that WM5 doesn't?
All I see, at the moment, is a swankier interface and a faster operation. But neither of those are big sellers in themselves and don't justify the bricking and incompatibility risks. So, what's the big appeal that I've missed? I guess I'm looking for an excuse to do this
Lastly, as I mentioned, there's almost too much information about all this. i can follow the guides and tools for installation but one thing will vex me if I was to upgrade - and that's which ROM to use. Now I'm certain every one of you has a favourite and so I'm not looking for a definitive recommendation, but what the hot ones that I should look into at the moment? As I see it, the "XDA Live" and "Black" see pretty popular..
Cheers!
Three reasons for me.
1. TomTom doesn't occassionally freeze
2. Easier to set as a modem
3. More responsive menus, button presses, etc
By the way WM6 is more like WM5 second edition rather than a brand new system.
wywywywy said:
Three reasons for me.
1. TomTom doesn't occassionally freeze
2. Easier to set as a modem
3. More responsive menus, button presses, etc
By the way WM6 is more like WM5 second edition rather than a brand new system.
Click to expand...
Click to collapse
Pretty much says it all. I never soft reset anymore. More memory, faster than WM5, better tweaks, and has some things WM5 didn't cooked in to the ROM. As for the risk of bricking, that's an extremely low risk, very minimal actually, if you follow the guide and wiki.
and html email is not to be sneezed at.
Because we can!
Mobile Office 2k7 can read o2k7 native formats. You will never see this on WM5 unless some imgfs God with a lot of time on his/her hands ports it there....
Native SD card encryption is Huge. The A2DP stack is a thing of wonder too....
JasenR said:
Because we can!
Click to expand...
Click to collapse
exactly!!!!!!!!
My softbank x01ht came with WM5 and the only upgrade I did was the radio upgrade to 1.40.
May be it is my luck, but my x01ht seems really stable in its original ROM version (WM5 aku 2), I have never hard reset and the machine seems really stable. So my need to upgrade to WM6 to avoid system hang is not really existing.
Also, I use a lot of BUILT-IN functions such as Push Email, Wifi and Chinese support (my x01ht was flashed with a Hong Kong version 838 pro ROM before sold to me). If ANY one of such functions is WORSE in WM6 than in WM5, than WM6 is a no no for me. I can't stand any frequent freeze of the x01ht because I now depend solely on it for my daily phone/PIM use. If I don't have it working 100% normal, then I will lose many important phone calls.
I see WM6 really as an evolution of WM5. In WM6, MS has fixed many bugs that were in WM5, for example:
- Crappy A2DP
- WiFi now supports WPA
- HTML email
- Faster and more stable
- I'm sure MS has updated little things here and there to make WM6 more telco-standards (GSM, etc.) compliant
Well, are you still using Windows 95 on your PC?
My reasons for upgrading have been for (in order of importance) the speed, bug fixes, better memory management, the X button actually closing the app not just minimising it, Office updates, better compatibility and usability in the new Internet Explorer, etc.
When I bought my TyTN I was shocked by how slowly it responded to user input compared to previous Pocket PCs I'd owned.
After the developments that started occurring here a few months ago, there really was no turning back. I upgraded and now the OS is quick and very responsive. WM6 has been a godsend. The phone application also doesn't take 3-4 seconds to load when I press the call button to answer a call like it used to!
WM6 also has a much more polished look to it I think.
hold on, TomTom still freezes on mine with WM6 !
I still love it though (tomtom that is and wm6)
Let me know if this is solved will ya ?
ta
bb
I did it simply because WM5 was a little unstable and I love experimenting / playing with stuff like this.
A side benefit which I didn't know I would get is the LVSW version that I installed allows WPA2 & WPA2-PSK authentication on the Wi-Fi. That meant I could run my Hermes at the same security as my network and didn't have to modify my wireless router and other PCs.
There's probably still a few other good reasons that haven't been mentioned in this thread yet.
Cheers, Oggy.
Bug fixing, more speed,...
With WM5 I had issues like the phone applicatoin reacted too slowy on an incomming call. so i missed the call. Or sometimes it even didn't ring.
WM6 works in that point.
bingobob said:
hold on, TomTom still freezes on mine with WM6 !
I still love it though (tomtom that is and wm6)
Let me know if this is solved will ya ?
ta
bb
Click to expand...
Click to collapse
Did you install TomTom 6.03??? As of that version I never had freezes anymore...
I to have tomtom lockup and sloooooowwwww to get map directions. Please I miss my fast tomtom 6. I am using 6.03. I wonder if i did something wrong. I never had this problem with wm5.
What about support?
One benefit of wm6 is that the hackers, tweakers, rom cookers, and random slackers such as myself keep this hermes wm6 forum active (albeit sometimes unforgiving to newcomers). If you have a question about wm6 on a hermes, it is probably already answered here. Can as much be said for the wm5 forums?
Just works
Personally I was about to ditch my TyTN. The default OS was infuriatingly slow, buggy, and had me resetting several times per day. If I hadn't stumbled upon XDA-develoopers and started flashing WM6, I would probably be a Nokia user again... WM6 just works. I've flashed maybe 10 different versions now, also the radio, and it's completely worth it. No big risk of bricking if you do your homework first.
F*SH said:
... faster operation. But neither of those are big sellers in themselves and don't justify the bricking and incompatibility risks. So, what's the big appeal that I've missed?
Click to expand...
Click to collapse
I don't think anyone with half a brain has bricked their phone doing an OS only upgrade (especially if they read the wiki etc etc)... and you answered your own question... who doesnt want a faster device?
LazPL said:
Personally I was about to ditch my TyTN. The default OS was infuriatingly slow, buggy, and had me resetting several times per day. If I hadn't stumbled upon XDA-develoopers and started flashing WM6, I would probably be a Nokia user again... WM6 just works. I've flashed maybe 10 different versions now, also the radio, and it's completely worth it. No big risk of bricking if you do your homework first.
Click to expand...
Click to collapse
I feel the same way as LazPL in that I was about to stop using the phone.
What I hated most about WM5 was a lack of real integration between the phone and contacts funtions, eg.:
. If you chose a call from the recent call list you could not access the contact directly (eg. if you just tried calling someone on their fixed line and wanted to try their mobile, you could not just click on the recent call you just made and select a different type of number, you had to select the name again from the list). In WM6 you can do this
. If you saved an unknown number from your recent call list it would automatically create a new contact, instead of giving you the option to save it in an existing contact (and choosing what type of number it was) or creating a new contact. In WM6 you can.
For me these 2 were just basic everyday usability features that I can find in the cheapest phones, and totally unacceptable to be missing in a €600 device. On the basis of these 2 alone, upgrading to WM6 was worth it.
In addition, my original Orange ROM had some bugs that were just pathetic (although these could have been cured with a newer ROM, or perhaps were due to the original radio ROM - which I also upgraded - and not the OS):
. Calls to busy numbers started blaring the busy tone through the loudspeaker (very loud)
. Trying to answer a call waiting would freeze the phone and require a soft reset
Hope that helps.
Pastings WIFI keys!!!
I've not been able to paste a wifi key in my WM05 ROM somone told me it was security...
rubish i think M$ to implement the copy/paste code.
Modem -> Bluetooth PAN is HUGELY more stable, my connection used to drop all the time in modem mode, i can now sit for 2 hours on my laptop at coffee shops and surf the web, whithout paying silly 1 day WIFI pass prices!

Black Shadow IV Problem

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

Bluetooth Devices Lost

All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
BrianP6 said:
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
Click to expand...
Click to collapse
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
BrianP6 said:
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
Click to expand...
Click to collapse
This bug appears only when 2 or more devices get paired.
I've been trying everything, even abusalza himself suggested some module replacement. i'm working on replacing drivers and certain folders in sys in my kitchen but still nothing yet... so far not yet, but it's fixable, i just gotta figure it out.
Thanks Josh,
I guess you'd know this anyway, but for completeness and for the benefit of the whole forum.........
Even though the paired devices are no longer shown in the Bluetooth Devices window, and you can no-longer use your HTC to pair more devices, then so long as you carefully initiate the pairing from the other device, it will be recognised, PINs will be requested and devices configured appropriately. I have just done:
Audi A4 in car kit
Laptop via Internet sharing
Jabra earpiece
None appear on the Devices window, but all (so far) appear to work perfectly.
Cheers,
Brian.
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
austinsmartie said:
Has this happened to anyone else?
Click to expand...
Click to collapse
Yep, I have experienced everything you mentioned at one time or another, even the square characters showing up in the device list.
I have gone all the way back to test Faria R32 ROM. It's amongst the best I've found for A2DP with the S9's along with some of PDACorners early ROM's. The drawback are that it doesn't have the 1% battery increase .dll cooked in and also still exhibits the "numbers for character during a call" bug.
It does have nearly 31 MB of memory free after fresh install though. (using 4MB pagepool - default is 6MB)
austinsmartie said:
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
Click to expand...
Click to collapse
It frustrated me enough that I started building my own rom!
I released one version here that I have been running for quite some time with no issues in the bluetooth at all.
I need to tweak it a bit more to make it "polished" but it is very useable and stable. I just wanted to run it for a while to see how it is going to act over a longer duration before I continue to fool with it, and I have been rather busy here lately.
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
joshkoss said:
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Click to expand...
Click to collapse
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Hmmm - doesn't happen on my ROMs...
The suspect things I'd be looking at in SYS are:
Bluetooth
Bth_A2DP
Bth_HID
Try replacing those folders with known good ones and see if the problem still happens...
austinsmartie said:
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
Click to expand...
Click to collapse
No Magic potion! lol
I basically did what CRCinAU described. (His rom doesn't have the issue, and feels a bit faster than mine. But, I was looking to create "My perfect rom").
But I also replaced files in the redist folder with "bt" in their name, with files from a known working rom (anryl's 20755). Like I said I wanted to run the rom for a while, now I just need to go back and tweak and clean up some things in the rom before I make another release.
summary
stickybud said:
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Click to expand...
Click to collapse
it is a really odd issue and seems to only affect the hermes... Here is the deal, Some chefs when porting sys grab the cplmain.dll to get the build number and keep some other items in their kitchen sys for stability purposes... I have noticed in my experience when porting, if the cplmain.dll does not match some other components with the same build number it will cause this issue. usually resist, shell, os, folders have been containing these sensitive items. so in short, if the issue is occuring cplmain.dll in redist folder does not match other components in your sys causign the conflict.
edit, and oh. i've tried replacing all bluetooth which had no effect.
So to fix this, the chef needs to report sys correctly and recook the rom.

Categories

Resources