Newest MightyRom - Headphone jack volume level switch NG

[ac0x]

Seems the latest MightyRom 6.5/2.5/5-1-2010 has lost the feature where you could switch between two volume levels by plugging or unplugging something in the headphone jack.

Is there a fix for this?

[afripino]

did you go to the settings tab in sense (manila), then sounds, then turn off "use single volume control" ? I'm running FF and it was in there.

[Wesley762]

Originally Posted by afripino

did you go to the settings tab in sense (manila), then sounds, then turn off "use single volume control" ? I'm running FF and it was in there.

Thanks, I had really liked the single volume control but did not think it was there.

[ac0x]

That just allows you to control system and ring volume seperately. Im talking about the phone volume level itself switching between one level and another simply by either having something plugged in or not in the 3.5mm headphone jack.

[blix1337]

can anyone create a simple cab/app that enables this feature?

[ac0x]

Originally Posted by blix1337

can anyone create a simple cab/app that enables this feature?

Or even a registy edit, or heck even a statement that it's from an HTC or MS provided system DLL that can't be changed for one reason or another.

I'm still wondering if it has to do with a fix to the "my headphone icon gets stuck forever" problem that sometimes happens on the TP2s...

[kavuday]

+1 for a request to bring auto volume switch back. It's not just MightyRom that has this feature crippled though, I'm using NRG's and have the same problem.

[ac0x]

Originally Posted by kavuday

+1 for a request to bring auto volume switch back. It's not just MightyRom that has this feature crippled though, I'm using NRG's and have the same problem.

This really makes me think it has to do with a later version of either WM or Sense...

OK then, for the record:

Windows Mobile 6.5: OS 5.2.21889 (21889.5.0.87)
Manilla version: 2.5.20121324.1

[Kliptik]

Originally Posted by ac0x

Or even a registy edit, or heck even a statement that it's from an HTC or MS provided system DLL that can't be changed for one reason or another.

I'm still wondering if it has to do with a fix to the "my headphone icon gets stuck forever" problem that sometimes happens on the TP2s...

I think the stuck icon is a hardware issue. i had it before and i couldnt get any sound to play except through headphones. after looking around online it seems the pin inside the jack is pretty fragile... i finally fixed it by inserting a different set of headphones and pulling them out... (weird i know)

now tho, my phone isnt recognizing my headphones are even plugged in... hoping i dont have to get a replacement...

on the volume changing, if someone knows the regedit (if there is one) i can CAB it up.

[ac0x]

Originally Posted by Kliptik

I think the stuck icon is a hardware issue. i had it before and i couldnt get any sound to play except through headphones. after looking around online it seems the pin inside the jack is pretty fragile... i finally fixed it by inserting a different set of headphones and pulling them out... (weird i know)...

I'm thinking it might be BOTH a hardware and software issue, and it's related something other than the pin inside the jack. The reason I'm saying this is that myself (and several others) have had the problem, have done hard resets, have played around many many times with the jack with no result, only to have it "magically" fix itself and stay fixed. If it WAS a problem with the jack, you'd expect it to STAY broken, or at least break again soon after once the pin went back out of whack again. The way it breaks and the way it resolves itself seems to point to some sort of internal issue that gets aggrivated by something, then UNaggrivated by something else. And if its a file ROM, a hard reset of course would just replace the same quirky file.

Its not beyond the relm of possibility that the volume level switch is what was aggrivating the problem. And instead of HTC fixing the hardware problem on existing devices, they just disabled the feature that was aggrivating it in the first place...