[Q] Holding open BT connection? MSVC? WinMo 6.1? - Touch Pro, Fuze ROM Development

I've had this condition with most of the newer (since Mid-December) Rom's on my FUZE so I'm not sure if it's a WinMo 6.1 issue, MSVC, or newer BT driver issue.
The Issue that I had was Bluetooth and MSVC and notifications. With 2 separate devices, a Samsung WEP200 and Parrot CK3300. Once MSVC spoke a notification, MSVC would crash and hold open the BT connection. I've had this situation randomly with most ROMs. Turning off the BT device will kill the immediate connection. Until you turn on the device again and the phone detects it and automatically establishes the connection. At this point MSVC crashes and occasionally the phone app crashes as well, only fix is to reboot the phone.
Different Roms seem to react and/or have the problem triggered differently. Some are triggered by MSVC notifications and some are Roms just have the problem inherent immediately upon 1st BT connection.
Roms I've used WITHOUT the issue:
OEM AT&T
Arp's RRE 3.1
Roms I've used WITH the problem:
Monx's ROMeOS 1.51(Dec 5) Random, could go days w/o the issue.
Arp's RRE 4.0 to 4.4.5SE
Elite RC2
Elite RC3
Anyone have any ideas?
THANKS!

Update that I noticed today, for some reason Arp's RRE 4.4.5 Rom that I reloaded again last night for testing see's my Parrot kit as "wireless stereo headset"
This make sense to anyone?

I think this is belongs in the Raphael general section. or software

Related

Trion keeps Crashing/Freezing = Missing Calls & Overslee

Hey
I'm hoping someone out there will be able to help me solve this problem or I may be saying goodbye to my Trion sooner than I would like.
So here's the problem:
While I am sleeping my trion keeps LockingUp!
This has happened a few times and each has been quite costly, either I oversleep and am late for important appoitments or I miss a number of very important phone calls.
I have tried using differnt ROMS but the problem persists. It happened to me a couple times while using the new I-mate rom so I switched to the new Dopod ROM and it happened again! I'm going to try the TYTN rom now... ugh!
Info Regarding my current setup:
Dopod ROM: 1.23.707.4
Programs:
MSN Messenger
MSN PPC 2003
TCPMP
Cyberon
Aidem MP3
Fit4cat Hermes v1.0
Fit4cat Settings changed from default:
Enable wireless plugin + show pluggin = ON
Remove Wireless Manager Icon = ON
Mount Ext. ROM = ON
Improve A2DP "High" = ON
- and that's all I've enabled. A weird thing I notice with the wireless pluggin is that at times on the Today screen it will just show my bluetooth status and neglect to show the WIFI status; at times the BT icon is right aligned as if the WIFI was still there but invisible and at other times the BT icon is left aligned indicating the WIFI icon is not even there.
That's about it for now. Any help resolving the main FREEZING/CRASHING issue would be GREATLY appreciated.
Thank You!
I have had the same problem. Hard reset and ran software freefor a few days, and same problem. Flashed to imate, and same problem. Flashed back to original HTC, and problem gone. I don't know what it was/is, but I feel your pain. We have almost no software in common, so whatever it is I think the problem is within the ROM itself or common Ext_Rom files. I never ran without Ext_ROM may start there.
this problem I had for about 3 weeks, I am currently using the new dopod rom and I have had no problems at all. It is a software problem issue and as roms develop issues will go I would flash either the new HTC rom or dopod rom as I had no problem with either of them I installed the dopod as it is quicker for me.
the same to me with imate rom, and some time when i press the center/enter button it show the sound volume panel
must go to Tytn rom tonight

Problems w/ WM6 and/or Prophet Touch VIII

Hi All,
I've been using Gullum's Prophet Touch VIII ROM for a couple of weeks now, and for the most part, it's performed very well. However, I do have a few problems (sorry about cross-posting this, but I thought that some of these issues may be related to WM6 and/or the touch interface in general, rather than Gullum's ROM):
1) The screen seems to become misaligned very easily, and I have to regularly align it again.
2) Screen taps/drags are very unresponsive. I usually have to click firmly (with the stylus), and pause briefly before I can then drag. Otherwise, the UI doesn't register the drag.
Could this issue (and no. 1) be related to the "flow" or "touch" interface? If so, I'd rather have responsive click/drag, so is there any way to disable the touch interface?
3) The speaker often goes into mute/vibrate mode. I've noticed that this seems to happen more often when I'm connected to ActiveSync, but that could just be a coincidence.
I wonder if this is related to the HTC "auto" profile? I'm not using auto, but just "normal". As a related issue, is there any way to edit the settings for these profiles?
4) Battery life. The batter life seems to be very poor. I see that other people have had this problem with the Touch VIII ROM as well, so at least it's a known issue. Some people say to remove HTC camera 4.11, but I don't think that software is part of the VIII ROM. Also, for the record, I don't use or have enabled wifi, bluetooth, or gprs.
Thanks for any help that can be offered on any of these issues.
Try Korand 2.6 WWE , it is the most stable dan fast ROM

MSVC problems with new ROM?

Anyone else having problems getting MSVC to respond to questions on the new ROM? With the new Sprint stock ROM and MSVC v1.6.17913, it doesn't answer me when I ask it a question. If I don't say anything, I get the default "thunk" sound when it times out, so it's acting as if it does answer me when I say something, but nothing comes through my headset. Phone calls work fine through the headset though.
I loaded my OEMs with DCD's 2.3.2 kitchen before I knew it had a problem, and got the same results with MSVC, except that it also turned off all sounds on the phone, just like the reported one call issue. A soft reset fixed the sounds until I tried to activate MSVC again.
I'll try DCD's 3.0.x kitchen when it's ready, but I'm beginning to suspect that MSVC needs to be updated to work with the new ROM.
MSVC seems to be working fine so far with the 3.0.0 kitchen.

Bluetooth Problems

I've had trouble getting BT to work since I flashed my phone from stock. I've got DCD 3.2.5 (started with 3.2.3), radio 3.42.30 (also tried 3.42.02) and SPL 2.47 from No2Chem. I've done hard resets and tested clean.
The symptoms have been consistently as follows:
Phone boots and BT light blinks. Comm manager shows it's active.
Bluetooth settings mode tab starts off unchecked.
Searching for BT devices takes a while then reports "Problem with Bluetooth hardware."
Starting BT from comm manager or check box in bluetooth settings mode tab takes a while and fails with no response.
BT worked fine before any flashing. I've found the following thread and seems similar but it's from a much older release. Any thoughts? Everything else is running really well including WiFi, GPS, data network, etc.
http://forum.xda-developers.com/show...371314&page=32
Any help would be greatly appreciated. Am I the only one having this problem?
Please
Anyone? Isn't there someone else out there with this problem?
im pretty sure that the hardware it's referring to is your headset, and not your phone. try pairing your headset with another phone or a game console or something. reflash 3.2.5 and use radio 3.42.50. if your phone pairs with something else, try pairing it to your 6800 again.
Bluetooth
kflipproductions said:
im pretty sure that the hardware it's referring to is your headset, and not your phone. try pairing your headset with another phone or a game console or something. reflash 3.2.5 and use radio 3.42.50. if your phone pairs with something else, try pairing it to your 6800 again.
Click to expand...
Click to collapse
Just trying to turn bt on causes these troubles. I haven't even tried pairing yet. Everything's been flashed and reflashed. Hardware reset as well... Only thing I haven't tried is to go back to factory.

Fix of TomTom 7 auto-power off problem with latest builds...

I had some problems with some of the latest (>20000) builds of Prophet roms when using together with TOMTOM 7.450 and an external bluetooth GPS antenna. It happened that, while running TomTom7 WITHOUT connecting my Prophet to a power source (i.e. my car's cigarette lighter plug) after 2-3 minutes the PDA auto-powered off. You can imagine the stress...
TomTom programmers managed to bypass the power management in order to prevent this annoying (and also very dangerous while driving) feature.
Unfortunately seems that latest builds' power management settings are completely ineffective at least with TomTom7. You can set the battery power management to NEVER OFF but it still will go down after a couple of minutes when running TOMTOM. All the latest roms that I've tried seem to be affected by this bug...
But maybe I've found a solution...
Use your favourite Registry Editor and check this:
HKEY_LOCAL_MACHINE\\System\CurrentControlSet\Control\Power\DisableGwesPowerOff
In my case it was set to 0.
I've changed it to 1 and voilĂ !!!
Seems that now everything works correctly:
1) TomTom Anti-AutoPowerOff is OK
2) OS's Battery power settings are OK
Hope I helped everyone who faced this annoying problem and I also kindly ask all the cookers to check this registry setting before releasing a new one.
Your,
Bodhi3
Bodhi3 many thanks for your information, I was having this problem and the only way that I found to solve it was to increase the sound in periods of time.
I will try it soon.
BR
Rui
It must depend on the build i am playing with a ROM build 21015 and this reg key doesn't exist but it uses Gwes i will look into this on my version thanks
curious did this work for anyone?
i tried it and no luck on build 7.915.9196
am starting to think its my ROM if more people are not having ths problem. i'll report back after i flash.
after trying everything possible and nothing working having blammed problems on bug in TomTom, it seems the problem was the ROM.
so i flashed a different ROM and can confirm TomTom is working fine and stays on regardless of power settings in OS
bodhi3 said:
I had some problems with some of the latest (>20000) builds of Prophet roms when using together with TOMTOM 7.450 and an external bluetooth GPS antenna. It happened that, while running TomTom7 WITHOUT connecting my Prophet to a power source (i.e. my car's cigarette lighter plug) after 2-3 minutes the PDA auto-powered off. You can imagine the stress...
TomTom programmers managed to bypass the power management in order to prevent this annoying (and also very dangerous while driving) feature.
Unfortunately seems that latest builds' power management settings are completely ineffective at least with TomTom7. You can set the battery power management to NEVER OFF but it still will go down after a couple of minutes when running TOMTOM. All the latest roms that I've tried seem to be affected by this bug...
But maybe I've found a solution...
Use your favourite Registry Editor and check this:
HKEY_LOCAL_MACHINE\\System\CurrentControlSet\Control\Power\DisableGwesPowerOff
In my case it was set to 0.
I've changed it to 1 and voilĂ !!!
Seems that now everything works correctly:
1) TomTom Anti-AutoPowerOff is OK
2) OS's Battery power settings are OK
Hope I helped everyone who faced this annoying problem and I also kindly ask all the cookers to check this registry setting before releasing a new one.
Your,
Bodhi3
Click to expand...
Click to collapse
Thanks for your fix i have made a cab file to automate the Job can you please test this and leave feedback all if it works we can add this fix to future Builds
I've tried the fix but it doesn't work when i start cab the system reboot and nothing happened.The rom is WM6.1 Build 21054 ...
Wap you are the best
Sidecar12

Categories

Resources