yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Good Point!

You have come up with the compelling reason to stay on 6.0!

I suppose I could flash the clean ROM and then wait 72 hours or so and then add programs one at a time waiting 72 hours or so between adding them to see which program in combo with the others already added causes the problem.

I do use several 6.1 programs like the Diamond Comm Manager and the Opal Volume Control that might be causing the issue.

Here is a complete list of programs I have installed on top of the HTC ROM:

Microsoft .NET CF 3.5

PHM Registry Editor

Mort's Mortscript

HTC Task Manager for ROMeOS (ver 2.1.34563)

HTC End Key 1.0.30736.1

Google Maps (Latest version.)

Enlarge Start Menu by TLR

HTC Volume Control (Opal XDA-Team)

T-Mobile Softkey Applet (Not used, just not removed yet)

Microsoft MSVC_US_PPC_1.6.19214.bengalih

Meschle backlight fix

Jimmy's GreenBatteryFix (5)

Chartcross GPS Fix

J.S. Advanced Configuration Tool (3.3)

The EquinoXe Wizard ReTOUCHED (Phone Skin)

emunutz HTC Home Customizer (1.0bv5)

HTC HTC Home (2.1-n2a)

Taurus Bulba Tilt keyboard fix (I have a Tilt, this will be on any HTC ROM)

Let the sleuthing begin.... I'll flash the original HTC ROM/Radio this morning and add they keyboard fix and we'll see what happens over the next 72-96 hours at a minimum. We'll see if I can survive without the "remove hidden proxy" for the test period.

Anybody have any other suggestions?
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
From the Beginning

OK, I've reflashed the ROM in my signature block again. Start the stopwatches! On Monday morning, assuming no NSI over the weekend, I'll start adding programs.

I currently have installed besides the ROM:

Taurus Bullba Tilt keyboard fix

I've also got both Bluetooth headsets working with the phone. (Not so fast, the Bluetooth turned itself off after the first call I made with it.)

From the list in the post above, I'm taking suggestions on which programs to add to see which ones might make the NSI happen first. I'd much rather find the culprit sooner as opposed later.

My suggestions for the first program to add are:

1. Diamond Comm Manager

2. Opal Volume Control

3. MSVC

It is my feeling that these three programs are the most likely to cause NSI. If anybody else has any suggestions or different reasoning, I'm all ears...err...eyes on this forum. :)

I can wait until Tuesday AM to see if I get NSI on the unadulterated stock HTC ROM. That gives us 96 hours to debate how I should proceed and I am very open to suggestion!
[Tilt, TyTN II, MDA Vario III General] nikagl:
Ok, here we go.

The following I have running too:

I do not use:

In my next post I will list all stuff I auto install (using Sashimi), including a small explanation...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
What I Can Install

Nika,

Thanks! Whew, at least there are a few things I can safely install.

I doubt the HTC Task Manager version difference matters, so I will install the one I have.

I have FDC, was going to try it, so now I might as well install it.

I'll look for the Comm Manager and dialer. Hopefully they will fit my needs.

Do you change ANY phone settings customization in Advanced Configuration Tool? Thinking about it I might have messed with those settings. I won't touch them this time!

Again, thanks for speaking up!
[Tilt, TyTN II, MDA Vario III General] nikagl:
Hey you, now you messed up my two posts!! Only 30 seconds delay, and you get just in between my two posts, lol.

Yes, I set almost all Advanced Config settings, but all through the registry keys mentioned before. It's gonna be too difficult too dig out exactly which, but really - most of them are touched, so I doubt any of them cause this issue...
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
ALL???

Nika,

Are you running ALL of that on the HTC ROM? Wow. I thought I was a long way from minimalist, but I don't think I've ever had that much stuff installed on my phone, even when it worked! ;)
[Tilt, TyTN II, MDA Vario III General] nikagl:
Yessir, took me many month to gather, test, play, etc....and better: it's fully auto-installed using Sashimi, only thing I need to do with new ROMs is check what is already on the ROM and remove that from the Auto folder because upgrading... :D
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Here's What is Running Now

It is Saturday, it is snowing and about 10F out this morning, so what the hey, why not let everybody know what I did last night for solving this problem.

Based on Nika's input, there are several programs I thought I could add safely to the stock HTC 6.0 ROM.

Here is what I am running now:

I have also installed my preferred background and the "Glossy Black Bars". Still pretty clean other than the HTC stuff that installs with the ROM. Hopefully I can make it to Tuesday/Wednesday next week with no missed calls and then we can start adding suspect programs and maybe narrow the search if the phone has NSI again. (Of course it is possible that the problem may have already been solved with the Comm Manager switch.)

(Off topic!)Nika, I noticed you run Advanced Config and Kaiser Tweak both. I am aware there are some better options in Kaiser Tweak (which I prefer to use) than Advanced Config gives. Are there plans to add all the Kaiser Tweak options to Advanced Config or are we going to keep on needing both programs?
[Tilt, TyTN II, MDA Vario III General] nikagl:
Good luck Jim, and keep us posted! :)

I should be able to port most tweaks to Advanced Config - just haven't spent much time to do it. Let me know what tweaks you want, and I'll look into porting them.

In the past I had the following issues with AC2.1 as opposed to KaiserTweak:

Delete keys (some options are disabled by deleting keys only, like HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms -> TcpMaxDataRetransmissions)

Set multiple keys (see my example before for enabling vibrating buttons in dialer)

Make more categories (I had difficulties to place certain features under a category, so I added them to Miscellaneous)

Use double quotes in registry keys (for instance for the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"Wireless"

Also be able to manually modify values that have a list of preset values (not part of KaiserTweak, but might be nice)

Btw. I had ported the following already and afaik Julien has added them to 3.3:

Set Date format

Calendar Event Text

Fullscreen Mode Windows Media Player

Cleartype Landscape

Cleartype PocketIE

Title Bar - Clock Settings

Backlight LockLevel

Suggest Words

Show ALS Page

Show 3G Long Prefix

Volume Change Beeps - Loudest

Volume Change Beeps - Quietest

Volume Change Beeps - Standard

Bluetooth Receive Files

Enable/disable HSDPA

Proxy AutoDetect

Encode photos in portrait mode

Capture Key Delay

Key Delay

Capture Key Delay Time

Finger Pressure

Lock position Spb Mobile Shell

Scroll, Zoom and Rotate in HTC Album

Wifi Certificate Message

TCP Connect Resends

TCP Data Resends

TCP Window Size

And the ones that remained due to the above restrictions were:[/COLOR]

Dialer Button behaviour

XT9

Wifi standby mode

Bitpool (as the advised setting would be to delete the key!)

SampleRate

TCP Data Resends

Backlight On Tap

3MP Panorma Shot (ie. 6MP Camera)

Low Battery Notification

Date Display

Wireless Today

Music Tab

Saved Audio

Saved Video

Saved Images

Empty Start Menu

Default QuickGPS Settings

Voice Speed Dialer as 6th HTCHomePlug icon

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Kaiser Tweak Port Request

The real biggie is the Text Messages "Sent" notification. Kaiser Tweaks options are much better than the On-Off of Adv Config.

The Bluetooth Sample Rate 48000 (Advised) indication is good like Kaiser Tweak has.

The Camera "Rotate Bug" fix needs ported, if it is still required.

Having the "Advised" showed on the Notifications in Adv Config like Kaiser Tweak has.

Calendar Event Text tweak needs to get ported.

I think that is it!

Thanks to all the other thread readers for letting Nika and I go off topic for a bit.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Back on Topic!

Nika, and all,

From the other thread aalexandrou started:

Schap's 4.3 series ROMs are 6.0 ROMs! This coupled with my own experience makes me more afraid that the problem is not just 6.1 related.... aalexandrou can't just downgrade to 6.0. He's already there!

I am wondering there isn't a wonky bit of software in 6.1 that is cool, and compatible with 6.0 that is cooked into ROMs that is causing this.

I hope my minimalist, slowly adding software technique finds the problem. It is clear the problem is growing. I can't just buy a new phone because the problem exists on the Fuze as well.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
72 Hours, No NSI.

All,

I am at 72 hours since reflash, and 48 hours since installing Nika's "safe" programs and what should be a "safe" phone skin. So far, no NSI. I am going to make some serious effort to "break" the configuration today by using the phone as a music player via the Motorola headset and making and receiving several calls via Bluetooth.

I am still looking for input from the experts on which potential trouble causer to install tomorrow morning from the two suspects below:

1. Opal Volume Control

2. MSVC

Since there has been trouble on AT&T stock ROMs that come with MSVC installed, I am thinking perhaps that might be the best place to start. The HTC ROM does not come with MSVC and since MSVC seems to interact with just about everything, I'm thinking that might be a likely place to start. However, I am no expert on any of this and anybody with more of a clue who has input and suggestions, please pass them along. I really value your input!
[Tilt, TyTN II, MDA Vario III General] nikagl:
I'd put my money on MSVC too, although that does not explain why 6.1 ROMs without MSVC have the NSI bug as well...
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
ROM Base?

Would be interesting to see if the 6.1 ROMs that do not have MSVC installed were based on AT&T ROMs? I can't recall, did you run a stock HTC 6.1 ROM or a cooked one?

I am pretty certain the Hyperdragon ROM I ran was AT&T based. So was eOS if I recall correctly, but all had MSVC. It would be interesting to see if we can find an HTC based ROM that never got corrupted by MSVC to reproduce NSI.

I'm leaning toward installing MSVC tomorrow morning. If I can break 6.0 with MSVC, then I'll reflash and add the rest of my apps without MSVC and see if it breaks. If not, then we can establish MSVC as at least part of the 6.0 cause and add avoiding MSVC in your 6.0 ROM as fix. It would be nice if Bengalih was on the forum with his MSVC knowledge.

Also, looking at my MSVC version, the one I have is recommended in the other forum for 6.1. I'll install the 6.0 recommended version instead tomorrow. Maybe the wrong version was causing the problem.
[Tilt, TyTN II, MDA Vario III General] nikagl:
I've used his Raw Rom (BRR), see Bengalih's forum:

http://www.winmo-experts.com/viewtopic.php?f=14&t=16

But that had the issue too. It did not have MSVC, but did have the Cyberon Voice Command, which I never used (and does not link into the OS as much as MSVC afaik).

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] denco7:
Haven't posted, but been keeping up. Haven't posted because I am going on 9 days without a NSI and I don't want to jinx it.

Shut off MSVC a couple of weeks ago, had a few NSI after, but they seemed to go steadily down to nothing.

If I was to have one educated/uneducated guess, I would choose MSVC.

The 6.1 I started having problems with was AT$T with MSVC in it.

I then upgraded to Hyperdragon III Blackstone. and the problems continued.

I don't think that the HD III roms are AT$T based , because Sakajati cooks them from roms dumped from phones that are not available from AT$T. Blackstone, Jade, Opal and Raphael ( not Fuze) .The last two roms I flashed both contained MSVC.

Even though I am thoroughly enjoying my respite from NSI, if you want me to load MSVC agin and see what happens I will.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Makes me think more and more that my 6.0 problem may have been due to the "wrong" version of MSVC. :( But maybe researching the interaction of the 6.1 version of MSVC with Windows Mobile 6.0 and it causing NSI may help us find what the root cause is....

Adding MSVC to the mix tomorrow could prove interesting.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
If You Want

If you want to risk it, it might help speed the process. I'm looking at at least a week to check to see if both versions of MSVC cause the problem on 6.0, or if having the mismatched one did it.

I am now considering installing the mismatched version first to try to replicate NSI sooner rather than later. If that is successful, then the next step would be to see if a simple removal of MSVC and a reset solves the problem without having to flash a clean ROM. The next step after that would be to install the correct version of MSVC and start again.

If you choose to install, you can check the back half of this process on 6.1 by installing the correct version of MSVC for 6.1. You can download Bengalih's from here. If the problem recurs in short order, I'd pull MSVC and soft reset and see if that fixes the problem over time like it appears to have happened for you.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
MSVC Installed

All,

Having completed more than 72 hours with no NSI and some serious attempts to cause it to happen with GPS use, hours of Bluetooth use for music and calls, and just about anything else I could think of, I just installed MSVC again. :eek: At least this gave me the opportunity to install and begin learning to use Sashimi which I am beginning to opine is better than UC for easing the pain of installing a new ROM which I will most certainly do once we get the NSI issue licked.

I installed this version of MSVC:

MSVC_US_PPC_1.6.19214.bengalih

Bengalih indicates this is a 6.1 version and I am running 6.0. This is what I had installed before when I had NSI on 6.0, so I am hoping that we can isolate my 6.0 NSI to this incorrect installation.

If I am successful, however, I need to know how to proceed. One way or another I know I can get my phone back to a no NSI state, but I'd prefer to be able to give someone smarter than I what information they need to see how this version of MSVC causes NSI on 6.0. That might give us the clue on what is causing NSI on 6.1. Smart folks, let me know what I need to give you from my installation (registry copies, etc....) to let you begin dissect the problem. I don't have the programming skills/knowledge to even begin to know where to look, let alone know what I would be looking at....

All, please hope this version of MSVC does what I think it will do and causes NSI on 6.0. If it does, I think we can give people like BennTech and Nika at least a place to start and hopefully a much simpler task to find the cause of NSI.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
30+ Hours

So far it has been 30+ hours with MSVC and no NSI on 6.0.

I have kept a log of calls and phone configuration and have tried Benn's method of replicating NSI and nothing.... Maybe it fixed itself somehow??? :D
[Tilt, TyTN II, MDA Vario III General] denco7:
I am going on 11 days without NSI .With me and you and Benn, if it wasn't for Nika, I often suspected this was an AT$T thing.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Me too....

I've thought the same, but I also wonder if there wasn't some software change in how the various networks interact with each other that caused some sort of incompatibility in 6.1 and/or perhaps MSVC.

All these calls are switched around and connected by computers. I wouldn't doubt that some software "upgrade" somewhere messed up the actual connections and simply blocked the voice.

It'll be nice if I can go back to 6.1. I miss the integrated threaded SMS. Was chatting with the wife today and I realized it was a major pain in the rear to not have the conversation available.
[Tilt, TyTN II, MDA Vario III General] denco7:
Ha... Ha....:p Don't you wish you had threaded sms at the dinner table? Listening to your wife go on and on about work 'til she finally says "what do you think ?" And you realize you have not heard a word she said for the last ten minutes.:)
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Shhhh....

Watch out! You'll give away secrets to the feminine members of this board.... :cool:
[Tilt, TyTN II, MDA Vario III General] nikagl:
Ooooooo......I've had my first NSI since weeks! Yesterday and Today, and believe it or not, in both cases when my wife called!! So it seems it simply takes a long time to appear, maybe because I hadn't rebooted my machine in a while and do more often in the beginning (because of tweaking the phone after install in the first weeks), or because the phone-log starts to become longer? Only good thing is that in this case, the NSI did not require a reboot to be fixed. I waited a minute or so, called my wife again and all was ok (yeah, she still loves me despite the crappy phone, lol). Who knows these could also have been network problems, nevertheless I wanted to share my story... more news in the next days if/when I receive more NSI's...
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Good Luck!

Let's hope it was just a network problem. I'm on 48 hours, 32 calls with no NSI with MSVC installed. I just realized I haven't used "Airplane Mode" since MSVC was installed, so I might use it for a while today to see if that might affect things.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
96 hours and counting....

So far MSVC has had no negative effect on NSI as expected. I am writing this post from Hawaii using the phone as a modem. It has been put through it's paces the last couple of days as I do my job. Multiple entries into airplane mode, a three hour drive to work with Bluetooth earpiece hooked up, phone used a modem, multiple incoming and outgoing calls, Edge and HSDPA use...and not one occurrence of NSI.

The only oddity I noticed was about 20 seconds of the Bluetooth connection between the earpiece and phone being lost about 1/2 through the 3 hour drive. It reconnected itself with no effort from me. Otherwise the phone has performed flawlessly.
[Tilt, TyTN II, MDA Vario III General] denco7:
Okay, 14 days with no NSI, Going to reload MSVC today and let's see what happens this week.
[Tilt, TyTN II, MDA Vario III General] Larstein:
Back to NSI

My parade is officially being rained on... phone worked for 2 weeks - today, back to no ringing and unable to answer call.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Let's Call It....

Bummer, but I'd call that "mostly sunny" or "occasional showers". :) It was a daily, or even multiple times daily occurrence for me before

The issue definitely seems to be dying down. When this thread first started, there seemed to be a lot of folks with the issue. It was even very quick to happen when I first went back to 6.0. I'm well over a week now with no NSI with/without MSVC in 6.0.

Benntech, can you still make NSI repeat with your method on 6.1?

This is one strange issue.... :(
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
Let's See....

C'mon in! The water's fine! :D
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
5 days, No NSI...

...so I'm going to add the Opal Volume Control.

Wish me luck! :D
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
NSI and Opal Volume Control

Installed the Opal Volume Control this morning. This evening I had an NSI...sort of. I kept doing the "Hello! Hello! Can you hear me?" for perhaps 20 seconds and magically after 20 seconds the other person answered as if my phone had been ringing! Conversation was normal for approximately 21 minutess.

So, I just called myself back after dinner, approximately 3 hours after pseudo NSI call and only call since pseudo NSI call. Phone rings, vibrates, and MSVC announces, but true NSI. Landline phone and Tilt both show connected, but absolutely NO VOICE!

dotFred's Task Manger says for CPU usage:

Idle Process ~81%

TaskMgr.exe ~13%

cprog.exe 0-~2%

shell32.exe 0-~5%

Ok, we've seen mention of this cprog.exe in other threads on other phones with similar problems associated with NSI.

As I'm writing here, I'm doing a soft reset and will call myself back. NSI should be gone.

In this call, with no NSI:

Idle Process ~84%

TaskMgr.exe ~15%

shell32.exe 0-~2%

cprog.exe 0-~1%

voicecmd.exe 0-~1%

gwes.exe 0-~1%

I did not notice Voice Command or gwes.exe being active in the NSI call.

I will be uninstalling the Opal Volume Control now. Let's see if a simple removal of the Opal Volume Control without reflashing a 6.0 ROM takes away NSI.
[Tilt, TyTN II, MDA Vario III General] djtheraven:
well i went back to stock 6.0 for the tilt and no nsi problems for the month....like i said its the bluetooth stack upgrade in 6.1....whether your using bluetooth or not, im telling you thats where the nsi comes from....of course 6.0 might have nsi once in a while, but thats windows... you cant tell me your pc never had to be rebooted...lol...trust me you guys want to fix nsi, look at bluetooth stack and compatabilty to devices...cant wait for 6.5 to come out maybe it will be fixed...until then i will use my flawless 6.0...
[Tilt, TyTN II, MDA Vario III General] nikagl:
Well, one search on google (windows mobile 6.1 bluetooth no sound) and I now know we're not alone:

http://social.microsoft.com/Forums/.../thread/57d13f5d-3c4b-433f-bedb-509203ad9ad2/#

No problem in WM5, issue in WM6.1 (no mention about WM6.0, but I am sure it will be better too :)).

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III General] nikagl:
And another cool thread:

http://social.microsoft.com/Forums/.../thread/dfc748af-2ad0-4d13-a16c-309ad28935eb/

We are not alone! :)
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
No Bluetooth Use and NSI 6.0.

I was hoping that uninstalling the Opal Volume Control would eliminate NSI on 6.0, but today I got a call that was NSI. It was one I had to reset the phone and return in a timely manner, so I didn't get to do any troubleshooting. Heck, this time I didn't use Bluetooth at all and I had NSI, so I'm wondering if there isn't a difference in the volume control between 6.0 and 6.1? That doesn't seem like something that ought to change, but I'm not Microsoft or HTC....

Unfortunately it looks like I'll have to reflash the HTC 6.0 I'm using to rid myself of NSI. I'll probably reflash this weekend or maybe Monday.

Question is, should I have waited longer on MSVC to have caused the problem, or should I leave MSVC off and just add in the Opal Volume Control to help point the finger there? I'm tending to think that MSVC is the culprit, so I'll add the Opal Volume Control on the reflash and see if I go NSI-free for a significant amount of time.
[Tilt, TyTN II, MDA Vario III General] denco7:
Haven't posted in a while because I am now on 24 days without NSI and have had nothing to add.

Restored MSVC back onto my Hyperdragon III rom with no change. Crazy, went thru a time when only every third or fourth call wasn't an NSI call. Removed MSVC and still received NSI calls, but seemed ( no actual ; factual data ) taper off until all of a sudden stopped. No change when I put MSVC back on.

Since then I have flashed to ansar's Seadragon rom ( check sig ) , this rom contains voice tags and not MSVC. Still no NSI.

Sorry I can't provide any clues as to why , but will update again.
[Tilt, TyTN II, MDA Vario III General] jpcrailjr:
WM 6.5

Based on the fact that I can't make either 6.0 or 6.1 to completely eliminate NSI, I have gone to the Hyperdragon IV Lite ROM based on WM 6.5....

What the hey! I might as well get NSI on it too. :D

Actually, there seems to be some Bluetooth changes in it, so we shall see how it performs.
[Tilt, TyTN II, MDA Vario III General] azuka:
For whatever it is worth let state here that a colleague at work who bought the HTC Touch Pro that came installed with 6.1 is already having the same problem we have been tackling here. The phone is just a few days old. So definitely it seems this is a WM6.1 issue.