[P3600 ROM Development] narshorn:
Thanks for sharing them here. I will try to answer best I can

This might due to volume control itself, not the dialer in fact. I agree that on trin, the dialer is slow because it eats considerable resources - even with smaller weight graphics, still a lot. Maybe the dialer behavior can be speedup a little using this reg setting that disable any VT related entries, as we don't support it anyways:

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE]
"bSupportVT"=dword:00000000

I agree that volume control has something buggy too; I mean, I use it only in "Simple mode" because it seems to work better with no "double setting confusion" behavior. I also noted that, being on speaker mode, volume can be changed to the max, but then at max-scale there is a small audio crack and the volume returns definitlvely too low. And any new attempt to change it afterwards seems to fail, it only displays full scale graphics and no go for the sound. Maybe there are some more sound settings from Mega OEM that we miss. That's what I investigate by now.

Interested people can try those reg settings which do "simple_mode" & test_tweaks, then report for behaviour (see attached, import .reg in my .zip directly & soft reset), it enables handset/headset volume handling and seems to fix the volume crash, for me now at least ! :)

Volume_Overlay_fix.zip ? Tested this morning, it disables the use of MDPL.dll (from OEM) by Volume_Overlay, as this crashes the volume right away, I mean, audio crack and then vol. is "unmovable" - It also enables MultiIncallSetting, and EnablesHSVolume too. HeadSet seems sound volume in headphones via the usb jack, HandSet seems to be the internal speaker volume (this last one using it in Speaker mode, not normal GSM "close to the ear" mode). Hope I'm clear on this. Tell me if not.

These are OEM & package customization reg settings that we actually miss in the kitchen. Please users, test and report. Could help getting rid of the problem while the kitchen will be out :)

I might add the new miscrosoft lockscreen too, because of link between it and the notifications system. For the Locked Screen issue. Still in test phase though.

See the previous replies here on MailAccountRepair.

And also, turning off then on the phone once all settings restored can help, instead of using soft reset

I don't think Manila is responsible for lost settings, etc and I might let out a titanium test version though :) Icke doesn't seem so interested in Titanium, so I have to force myself ... :p

I've never had that strange behaviour since new rom is out.

However this "no wake up & being late at work" had been reported on older roms since WinMo 6.5, and even for the ones not having the new Mega packages even.

I guess you need to not change the settings "SoundAlarmAlways" in microsoft UI and also maybe use volume in "simple mode". It always rang to wake me up in the morning since :)

For the new "fancy" HTC apps to set Ringtones, Vibration, and Alerts settings; remember they just command the registry settings that the Microsoft common UI settings manage (by the standard interface). Both command the same things, so I don't think there could be errors in it. Just, for volume, MS UI increments only 0, 20, 40, 60, 80 and 100%, but HTC adjust permits here to get also the 6, 13, 26, 33, 46, 53, 66, 73, 86, 93 % in between. Maybe here it can bug with the "simplest" MS increments writereg settings. I am rather surprised that we could get more than 5 volume steps (+ muted = 0) in WinMo 6.5 though :)

You are right, the hardware itself was designed with WinMo 5 in mind ... ;) you don't sound too harsh, but maybe now you see the difficult part of cooking essence, especially when trying to keep an old device "up_to_date", it always creates new problems, some may be solved, some not. Knowledge and discernment is a long thirsty path to get done, and reckon you don't know everything and want to learn each day, humbly, is perhaps better than pretend knowing everything. This is the purpose of this thread: show you some insights that end-users never see ordinary. So you can get deeper in the system and understand how things work, so you can be really close to your device to use and understand it. So, if a setting breaks, you might be able to fix it yourself. I highly hope so :) Here's the thing.

We can't do that :( Or perhaps, using an older version of ArcsoftMMS, or restoring the "enable at boot but hidden". Boot times little increased, Arcsoft not showing but open in bckgnd at idle, so after it opens very quickly. Tell me all, if you need the reg tweak, disabled by now.

Thanks :)

Thanks once more. We use the IME_EzInput_Western_2_1_19171325_00 with IME_Engine_Western_2_1_19171325_00. The last versions for QVGA, IME_Engine_Western_2_1_19191429_00 & IME_EzInput_Western_2_1_19183030_00 use more ram, and fonts are also different, so I kindda don' like it too much :cool:

Brds,

nAr