yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] BennTech:
WM6.5?

Hey, fellow NSI sufferers. Been outta the loop for a while & wanted to post a quick status.

After virtually no paying work for 3 months, I was suddenly accosted by several large emergency jobs: multiple clients with dead PCs, dying servers, new servers, switch to VMware ESXi and virtual servers, new office cabling, and a couple of computer forensic cases. (Yes, I wear many hats.) Would have been nice if these spread out instead of piling up all at once, but I guess I shouldn't complain about too much work in this crappy economy. ;)

Anyway, point is I've been horribly busy and haven't even had time for XDA, let alone debugging NSI. Quick perusal though and I see there's a WM6.5 out? When did this happen?!? Anybody try 6.5 to see if it has NSI?

Since I'm the only one who can faithfully reproduce NSI, I suppose I should flash and try. At the very least, it would be a lot easier for me than debugging NSI with IDA Pro. Can't do this any time soon, though, but maybe in 2 weeks...a week if I'm lucky.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
6.5 and NSI

I went to a "6.5" ROM about 10 days ago. It is the one in my signature block. Is it "official" 6.5? I don't know, but info screen on startup says it is.

There is definitely a difference in Bluetooth on the 6.5 ROM. It shows "Connected" and "Not Connected" paired devices and it seems in general to provide a much clearer Bluetooth connection.

Best of all, no NSI so far, but for some reason NSI seems to have mysteriously just gone away for many of the participants on this thread.

One bug in both "6.5" ROMs I have tried: Email provisioning doesn't work (it seems to have a "push" type of email system perhaps) and also, when you try to change the setting on email accounts, you can't. The only account that shows up is MMS/SMS.

Finally, probably as part of the above, if an email account is provisioned, tmail.exe initiates a constant data connection via GPRS/EDGE/3G/HSDPA, even during phone calls. This leads to a pretty quick drain on the battery and there is no way to stop it except to delete all email accounts from the device.

Otherwise, my 10 days with 6.5 seems to be a relatively good experience. I'd suspect the chefs who are working with 6.5, or what some are calling a "hybrid" of 6.1 and 6.5 will fix these bugs, but overall, right now it seems NSI free and I need the calls worse than I need email. ;)
[Tilt, TyTN II, MDA Vario III General] miownZ28:
Hi all,

I came across this thread 2-3 weeks ago because I had the same NSI with my Tilt. This was happening daily and just so happens my wife was the one on the other line almost everytime (she thought I was doing it on purpose) so I rrrrrealy had to fix it.

I saw that one of the probable causes was Voice Command, so I disabled the option under settings and disabled the PTT button since I had it assigned as Voice Command. Since then NSI is history. I am 100% sure it's Voice Command with 6.1, well at least in my case.

I am not an expert on this by any means, but I've learned alot from XDA since I bought my Tilt last year, so I hope this helps.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
MSVC

I have intentionally not installed MSVC on the 6.5 ROM I am running. With pretty much any cooked ROM a couple of finger presses on the screen can get me to a phone call with my Bluetooth headset, so I have deemed it "fun to have" and not "essential" which led to that decision.

I too think MSVC is a probably a culprit, that along something in the Bluetooth stack. Anyway, it is great to be able to answer my phone and not have to worry about silence. :)
[Tilt, TyTN II, MDA Vario III General] nikagl:
Dear all,

Yes...I'm still here...and I've still been playing with this problem for the past weeks, but just haven't had the time to update the thread...

What have I tried?

* Tested Garmin DK.10.Lite from 05/02/2009 to 16/02/2009

* Tested utopykzebulon_wm65 from 16/02/2009 to 17/02/2009

* Tested HyperDragon IV_Lite from 17/02/2009 to 22/02/2009

My personal preference is the Garmin ROM, but all of these ROMs had NSI's. The WM6.5 ROM is a real test ROM, very bad user interface (the new 6.5 interface which works horrible on the Kaiser), and both the Garmin and Hyperdragon are good ROMs but with the NSI (and therefore useless till we fix it in WM6.1 or higher ROMs).

I'm back to my old faithfull WM6.0 ROM, but instead of using the stock ROM I am using the "Schaps_WM6Pro_Kaiser_4.30_WWE_Full" with "KAIS_Radio_Only_1271532_CustomRUU" radio. This was the latest Schaps ROM I could find, the 4.31 turned out to be WM6.1 (with NSI!) despite the screenprints in that thread.

So, in my case it's 100% proven to be caused by WM6.1 or 6.5 (yes, the new Hyperdragon has some other options in BlueTooth, but definately caused NSI) and solved in WM6.0.

Just to summarize again, here's what I experience with NSI's:

* When I have my first BlueTooth call it's fine

* My second call initiated by me directly after the first will be silent

* After disconnecting BlueTooth after having had a call on the BlueTooth system, all subsequent calls will be silent (both receiving and initiated by me)

* There's nothing I can do then soft-reset when my phone suffers from NSI - I've tried all suggestions in this thread and none work

With my WM6.0 phone the only issue I have is that directly after a BlueTooth call I need to wait about 30 seconds till my next call (both receiving and initiated by me) because it will end up on my phone instead of my carkit...

Would it be an idea to start gathering the BlueTooth dll's of each phone and comparing them? I have no coding experience, so I would know how to compare them...I've also looked for a way to rip certain files from a ROM but I wasn't able to find a way... any tips? Otherwise I would have to flash each ROM to rip the dll out...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] tommoore:
Found a fix for my no sound problem

Hello all

I have been following this thread for several weeks as I have been having the same problem with my TyTN II on Vodafone UK, i.e. the phone producing no sound at all until soft-reset.

The issue definitely appears to be to do with the bluetooth, and specifically in my case to do with the aftermarket handsfree kit in my car, a Parrot CK3100.

I have had similar problems in cars with manufacturer-fitted car kits (I change my car very frequently as part of my job so have tested this in numerous vehicles).

A few days ago I upgraded the firmware in my Parrot CK3100 and since then I have had not had any problems with sound, whereas I was getting them daily before. Nothing else has changed so I can only attribute the difference to be this new firmware.

Now, I know that a good proportion of car manufacturer bluetooth system are actually based on Parrot systems that are integrated in to the vehicle rather than fitted as aftermarket products. This is definitely the case in Peugeot, Citroen, Mitsubishi and possibly Volvo though I cannot be 100% sure.

It might be worth getting your dealer to see if there are any firmware updates for your manufacturer kit.

Myself, I'm just incredibly pleased that I can actually rely on my phone again!

Good luck

Tom

Edit: Sorry, forgot to state ROM version 3.28.405.0 WWE official HTC, radio 1.65.16.25
[Tilt, TyTN II, MDA Vario III General] nikagl:
Thanks Tom. This will work only when you have a upgrade available, which is not available in my case (JVC). Btw., as far as I could see from the Microsoft website this is also related to many other Windows Automotive / Windows Mobile combinations... it still puzzles me that Microsoft is not able to create two products that correctly work with eachother ;)
[Tilt, TyTN II, MDA Vario III General] tommoore:
Crazy isn't it.

I only mentioned it as I thought it might be a help to anyone who has a Parrot or Parrot-derivative bluetooth kit. Interestingly, in the release notes for the firmware upgrade it mentions "fixes to improve compatibility with Windows mobile phones"

I don't think the fault was with the Parrot kit at all because as you say this affects lots of different bluetooth products but it seems as though Parrot have identified what the problem was and put something in to their software to work around it.

Anything that makes things work is good!

Tom
[Tilt, TyTN II, MDA Vario III General] swanlm:
Hi, I'm of the firm opinion that there is a time-out happening in the bluetooth audio gateway resulting in the both the phone audio and bluetooth audio being muted. I have exactly the same experience as nikagl in terms of repeatability and also use the CK3100. Whenever I complete a call, the CK3100 synchronises the phonebook and if I try and dial whilst this is happening I get NSI. During the synchronisation the phone is very unresponsive and this is what, I believe, is causing the timeout. If I wait for the synchronisation to complete before making the next call, I don't get NSI. BTW the CK3100 has an icon on the display to show when its synching.

I'm trying to find a tool which shows me the status of the AGW software so that I can prove or disprove my theory, but certainly the ROMs that have had least NSI for me have been quickest in completing the synchronisation. If I could find a way of stopping the synching with the CK3100, I'd probably be able to prove my theory.

@tommoore: I'll definitely upgrade my CK3100 software and see if there is an improvement.

Cheers.
[Tilt, TyTN II, MDA Vario III General] nikagl:
Hi swanlm,

I can only agree with you that this might be related to the phone-book-syncing! In my case I had 800+ contacts (auto-synced from exchange) and when I cleaner my addressbook to less contacts (currently about 300) the time I need to wait is less!! Sadly enough neither my phone nor my carkit have an indicator where I can see the syncing process. What's I'd love is a tool with which I could disabled both the audio gateway and the phone book syncing, as I really don't need either of them (especially not when it causes these issues!!).

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] tommoore:
CK3100

I haven't had a problem since running the software upgrade on the CK3100.

I had the same problem with synchronisation after making a call, but interestingly sometimes with mine the sychronisation never actually finished and the only way to make the phone responsive again was to switch off bluetooth, wait a few moments, and then switch it back on again.

I generally found that if the sync was going to work, it took no longer than 30 seconds. If it took longer than that, it would continue for my entire journey during which time the phone would be unusably slow.

Worth noting that since the software upgrade on the Parrot I haven't had the sync problem either....

Tom
[Tilt, TyTN II, MDA Vario III General] swanlm:
Tom, had exactly the same issue with unending synching so glad to hear it's better on the new Parrot software. Still not had a chance to update this :( so can't comment yet for myself.

BTW, using the Hyperdragon IV Iolite ROM of 24/2 and not had NSI. But I've also been careful about the synching issue.

Cheers
[Tilt, TyTN II, MDA Vario III General] amarguli:
NSI in Polaris

I think that I have exactly the same NSI issue on my Touch Cruise with custom WM6.1 ROM. Sometimes (I suspect that this happens after receiving calls via BT) the sound disappears at all - no system sounds, no sound in phone calls, nothing. I reported this problem in Polaris forums but didn't get any response from other users. I was frustrated by this problem for a long time and pretty desparate to find a solution. Now after reading this thread I understand that at least I'm not alone and this gives me some hope :).

So is there any other solution except downgrading to WM6.0?
[Tilt, TyTN II, MDA Vario III General] JiggyNS:
I've been having this problem with my tytn as well now for over a week.

It started with me getting the boot loader screen after doing a soft reset. Today I've spent over 6 hours trying to fix the problem by flashing 4 different roms and probly more than 6 radios.

The latest flash was with a 6.0 WM rom (and the new radio) after seeing some of you having good results from doing so however, I am still stuck without any sound!!

I've noticed that I also cannot play songs or any sound files that I have on the phone and storage card! I know the problem isn't in the hardware since I can hear the swoosh sound that is made by AT$T's startup animation.

Anybody got any clue what I could do? I've read countless threads and tried searching but there hasn't been anything positive out of this day!
[Tilt, TyTN II, MDA Vario III General] amarguli:
The sound goes away immediately after soft reset or occasionally after making calls using BT?
[Tilt, TyTN II, MDA Vario III General] JiggyNS:
No blue tooth use. I never used BT. I boot the phone, the sound works on the boot-up animation, but anything after that is just silence. There is no sound when the phone rings, no sound effects, nothing.

This morning I found my phone off, even though it was on since last night, i never turned it off myself, and I couldnt turn the phone on. Plugged in the USB cable and all i see is the tri-coloured screen.

I have no clue what is going on.
[Tilt, TyTN II, MDA Vario III General] amarguli:
So your problem is not the same as mine, sorry but I can't help
[Tilt, TyTN II, MDA Vario III General] Vragor:
I have had the no sound issue every so often. Usually after using my Nuvi as a bluetooth headset in the car. But about a month ago, I also noticed that I could get the no sound issue if I just set the phone down after a call rather than manually hanging up the phone (hitting the end key) myself.

I did a few experminents and determined that letting the other side of the conversation terminate the call "seemed" to cause a problem.

I only spent about an hour fiddling with this problem because I'm only a casual cell phone user, and the problem didn't cripple my life.

But ever since that day (over a month ago), I've made it a point to hang up the phone myself rather than waiting for the call to terminate manually, and I have not had a repeat.

Now, with all that said, let me describe the exact symptoms so you can know for yourself whether my issue is the same as yours.

A call would come in. The screen would light, the vibrate would begin (I have vibrate on at all times). But no ringer could be heard.

I could answer the call, but I couldn't hear anyone on the other end.

I would check settings and verify that the phone was not set to vibrate only. I could change the volume control up and down but "ping" to indicate current sound level could be heard. I could mute and unmute the phone and it would not restore sound.

The only thing that I found to restore sound was a soft boot.
[Tilt, TyTN II, MDA Vario III General] Chall5477:
Hey peeps. I'm having a NSI of course with my tilt. I will have sound on my phone untill I get call. I will have sound on that first call. After that no sound on the entire phone. I will reset and will be fine untill after I get a call. It happens every time with out fail. I'm on ATT, and I started with a AT&T 6.1 rom. Worked fine when I got. I'm running HardSPL 3.29> I have tried Phoenix 2.3.21109 rom, T.I.R. v3.0 - BLUE WOLF - WM6.1, Duttys DualTouch v4, SimpleOSv3 and SimpleOS Manila(have tried most of the radios for all). I'm going to try Dutty's WM6.1 Hybrid v2 5.2.19716/5.2.19700 to see if that works unless someone alreadys has. If that doesn't work i'm going to a 6.0 rom. OK now i am a NOOB to the whole PDA customizing, but not to computers. If this was a desktop would it be safe to say that it would be a driver or reg issue. Was wonder if a cab file would be the way to fix this. Thanks for hearing me out. I hope that my ? is not to noobish and i'm not beating a dead horse.
[Tilt, TyTN II, MDA Vario III General] Chall5477:
OK i just tried dutty's and it works. no problem with anything yet. the only difference was that the rom and the radio flashed together. with all the other ones i had to flash a radio. maybe a sign:). i don't know enough to know that.
[Tilt, TyTN II, MDA Vario III General] three2008:
Hi Guys..

Has anyone found any bug foxes for the BT issue???.. any radio's or cooked roms that are compatible???

ALl the best
[Tilt, TyTN II, MDA Vario III General] MeirXDA:
I'm not sure if this has been mentioned before but when this happens to me can fix it by starting MSVC and saying "cancel".
[Tilt, TyTN II, MDA Vario III General] nikagl:
Dear all,

I've been running WM6.0 ROMs since a few weeks now and experience no NSI since the downgrade. I did try some WM6.1 and WM6.5 and the NSI appeared immediately. The only issue now is that the BlueTooth is disconnected when I place a call within a minute after another call. It automatically reconnects after a minute or so, so I'll just have to accept that... Maybe we'll have some 6.1 or 6.5 ROM in the future that works, but honestly, I've given up hope...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] amarguli:
No fix yet, but I found a sort of workaround. When NSI happens I run several times the small utility called BTAudioToggle.exe that routes all audio to BT or internal speaker and this restores the sound. Unfortunately this works only when my BT headset is connected.
[Tilt, TyTN II, MDA Vario III General] denco7:
Checking in, hadn't had a NSi call since Dec 14, flashed many roms ( 6.1 and 6.5 ) and radios since, have mostly been flashing Abusalza's PDA Corner Roms. Not a problem since Dec.

Until two days ago, flashed Abu's new Ultimate V.3 rom, that day, I had two NSI calls, oh crap ! Looked at the changelog and sure enough, he had cooked in MSVC, the same thing I had narrowed it down to previously.

Immediately flashed to his V.2 and have not had an NSI call since. Just thought that I would pass that along to all of you.
[Tilt, TyTN II, MDA Vario III General] swanlm:
hi i'm also on PDA Corner and always install MSVC. I only get NSI very rarely and I know what causes it (namely using VC directly after a call while my carkit is still syncing). So for me this has not been an issue for a few months now.
[Tilt, TyTN II, MDA Vario III General] nikagl:
In my case I don't use VC at all, but have 300+ contacts which causes the phone to sync longer and therefore easier causes the NSI. Running WM6.0 makes it workable, as it does not cause NSI, but only to end the bluetooth connection (call ends up on handset instead of carkit)...
[Tilt, TyTN II, MDA Vario III General] curwiler:
Adding my experience to the fray, no solutions to offer however.

I am running Hyperdragon III Dec 03 Blackstone OS 5.2.20757 Build 20757.1.4.0. Before this I had the NATF v5 installed as well as the ROMeOS and eOS 888 builds, and I had frustrating issues with silence when calling or being called.

So far with the Dec 03 HDIII, it seems that's gone away, but I'm still left with the PITA bluetooth volume drop to zero issues as well as other bluetooth frustrations. Anyway, perhaps some of you can try HD Dec 03 and see if it helps or not.

Hoping someone finds a definitive answer, but I'm not feeling very optimistic about it. Does make you want to go back to as early of a build as you can to see what gets "fixed."
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
I'm Having It.

I have two Tilts, my wife running stock AT&T Rom (Bloatware removed) 1.71.09.01 radio, and mine running eOS.888.FiRe with 1.71.09.01 radio.

Common item is the radio, but the thread shows quite a few radios having the problem. Things that make you go hmm.... ROM? Radio? Or something else?
[Tilt, TyTN II, MDA Vario III General] denco7:
Are we all on AT$T wireless ? I am.
[Tilt, TyTN II, MDA Vario III General] BennTech:
denco7, I'm on AT&T, too. Like I mentioned in #6, it's possible that the radio gets hosed, thus crashing PDA sound (still don't understand why some moron engineer/developer decided to intimately join the PDA audio with the radio ROM). If we're all on AT&T, it could be something screwy in their networks. Or likewise, as in #4, could be something specific to the Tilt version.

curwiler, I might give HyperDragon III a try after New Year vacation. I used to have the same Bluetooth problem you mentioned, but never knew it until I researched your "PITA Bluetooth volume drop" comment and found this other thread. LOL...this drove me crazy but I was too busy at the time to research it, then it magically fixed itself (or maybe I just quit using vibrate & Bluetooth so much). But now I've got this no sound problem with WM6.1. Plus my phone still locks up with 100% CPU usage after any phone/text activity when Bluetooth is connected--same as it's done since WM5 on my Wizard. <sigh>...I'd ditch these f*ing PDA phones if they weren't so damn convenient otherwise. :)
[Tilt, TyTN II, MDA Vario III General] nikagl:
I have the same issues, do not use AT&T (I have a Dutch provider called Telfort), and it only happens after I get out of the car (ie. disconnect BlueTooth), or start a call directly after another car (if I wait about 2 minutes, it's ok). I am sure it's related to BlueTooth, but have never had it happen with my headset. I have used numerous ROMs and numerous RADIOs and all of them have the issue... Btw, I do not use VoiceCommand...
[Tilt, TyTN II, MDA Vario III General] BennTech:
Well, there goes the specific carrier theory & probably Kaiser version, too. Should have known that based on posters' country flags & carrier pics. :)

I'm using Bluetooth. Everyone else in this thread Bluetooth users?
[Tilt, TyTN II, MDA Vario III General] nikagl:
Btw, my current nav is a JVC KW-NX7000 (detachable double-din screen!). Previous nav (Pioneer HD1BT and HD3BT, both got stolen) had issues too, but not loosing sound...
[Tilt, TyTN II, MDA Vario III General] denco7:
I have never used bluetooth headset, just use it to transfer files from my PC. I used it with 6.0 without a problem. And started having these "calls with no sound " problems before I ever used it on 6.1.

Flashed Hyperdragon III blackstone a few weeks ago, best rom I have flashed, but did not solve the sound problem.
[Tilt, TyTN II, MDA Vario III General] swanlm:
I'm using Dec 03 HDIII ROM and agree its great ROM. But, for me this has been the worst for this bug. You might want to try changing the Bluetooth Audio Gateway you're using. Change HKLM/software/microsoft/bluetooth/audiogateway/btagextmodule to /windows/oemagw.dll.

Doesn't completely solve the problem but seems to make it more stable. YMMV.
[Tilt, TyTN II, MDA Vario III General] Shub-Niggurath:
I posted a reply yesterday but it doesn't seem to have posted properly! Anyway, i dont use bluetooth (except for file transfer) and it is therefore off most of the time. I had a similar problem with my universal except it would tell you the radio had crashed and then reset after 30 seconds. I asked in the post that didnt show up if anyone had tried the radios from any of the other similar devices (nike/elf)? Do the radios from the newer models (ie. diamond) work with the kaiser? I'd give it a flash but im at work!
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Bluetooth?

I'll pay more attention to Bluetooth usage. I use my phone with two Bluetooth devices, BlueAnt earpiece and a Motorola Headset for calls and music. I rarely use them, maximum a couple of times a week.

Could this be a glitch in the Comm Manager? Perhaps when you turn Bluetooth off it causes the volumes to go mute?

Wish I had the tech/programming skills to explore this stuff....