|ROM|¯`·.¸¸.- Energy -.¸¸.·´¯ * |July 4| 21916|29022 * Sense 2021 + flavors

[PPCFreak]

NRG: 21916 rom Sencity March 30th.

Having a couple of issues:
1. Start Icon is showing what looks like an Android with the X at the bottom right corner.
2. Inbox Soft Right Key: Reply and Reply All. If I change the value in Registry, it does not take even after a restart. The soft left key still says and performs Reply All.

Trying the 21916 to see if this solves some of the phone call answering issues I was getting with 29017 Rom.....or if the hardware is starting to go bad.

Will test out the Bluetooth on this tonight.

Thanks for the great work.

[kyderr]

Originally Posted by NRGZ28

Hmm okay.. well that's better than nothing I guess.

next up, we'll try the verizon MR1 ROM BT stack as some members suggested.

Downloading the ROM now. Phone hung again on me. It seems after a few days, the ROM get's unstable...

I will let you know what happens....

[healthylaff]

Originally Posted by kozmo

While you have TP2 connected, go back to device manager>portable devices... uninstall TP2. Also, if you re-installed WMDC, uninstall it again, then restart computer and try again.

Originally Posted by JVH3

Reboot your computer. Reconnect. Should work.

This is a frequent problem with Windows Mobile Device Center.

A solution that has helped keep this from happening.

Unininstall Windows Mobile Device Center.

Reboot.

Download the latest version of Windows Mobile Device Center.

Reboot.

Problem will now happen much less frequently, if it happens at all.

Those were the first things I did! Here is what I've learned:

Like a dumbass, I should have tried a windows 7 system restore first... The registry got corrupted and I probably could have fixed it by restoring, but no, I had to be an IT sleuth (mostly because my phone was trashed, too, and I didn't reflash the ROM until a couple days ago).

Now, I've tried to uninstall/reinstall WMDC so many times that I don't have a restore point back to mid-March.

With Windows 7, WMDC is built right into OS--no need to install to sync with a TP2 (and I verified this on a friend's identical laptop, configured the same, who had never synced with any phone before), so there was a registry error created by the attempted sync with the new PocketQuicken PPC 2.5 install on the phone.

At this point, I think I need a registry guru to weigh in (again, it's a Code 19 Error):

• Can this be fixed?
• If so, how?
• Any registry repair programs going to do it?
• Am I going to have to reinstall Windows 7 (please tell me "no")?

TIA (hopefully my stupidity will prevent someone else from making these grave mistakes).

[NinjaDuck]

Wirelessly posted (Opera/9.80 (Windows Mobile; WCE; Opera Mobi/WMD-50433; U; en) Presto/2.4.13 Version/10.00)

Originally Posted by healthylaff

Those were the first things I did! Here is what I've learned:

Like a dumbass, I should have tried a windows 7 system restore first... The registry got corrupted and I probably could have fixed it by restoring, but no, I had to be an IT sleuth (mostly because my phone was trashed, too, and I didn't reflash the ROM until a couple days ago).

Now, I've tried to uninstall/reinstall WMDC so many times that I don't have a restore point back to mid-March.

With Windows 7, WMDC is built right into OS--no need to install to sync with a TP2 (and I verified this on a friend's identical laptop, configured the same, who had never synced with any phone before), so there was a registry error created by the attempted sync with the new PocketQuicken PPC 2.5 install on the phone.

At this point, I think I need a registry guru to weigh in (again, it's a Code 19 Error):

• Can this be fixed?
• If so, how?
• Any registry repair programs going to do it?
• Am I going to have to reinstall Windows 7 (please tell me "no")?

TIA (hopefully my stupidity will prevent someone else from making these grave mistakes).

if you provide the keys, I will send you what they look like on a working system or you could just take that approach yourself. Model success..

[healthylaff]

Originally Posted by NinjaDuck

Wirelessly posted (Opera/9.80 (Windows Mobile; WCE; Opera Mobi/WMD-50433; U; en) Presto/2.4.13 Version/10.00)



if you provide the keys, I will send you what they look like on a working system or you could just take that approach yourself. Model success..

Good idea, thanks!

How do I obtain the affected keys? You'll have to give me really concise instructions, as I'm very weak on registry issues.

.

[kozmo]

Originally Posted by healthylaff

Good idea, thanks!

How do I obtain the affected keys? You'll have to give me really concise instructions, as I'm very weak on registry issues.

.

Since this isn't ROM related, send me a PM and I will try to help you get this going.

[KIOWA69]

could install windows 7 over top of itself and i would think that would fix it, been a while since i have messed with windows since i mostly use os x nowadays.

[blunij]

Originally Posted by lovingHDTV

I just flashed 29017 sencity Mar 30 and tested it out on my Moto T215 bluetooth set.

I just flashed and did not install anything yet. The first call took 3 hangup attempts before it hung up. It did hang up though and I get a #777 message. I made several other calls from and to my cell and they all worked fine with the BT set hanging up properly with no additional #777 messages.

This is much better than anything before as I've never been able to hang up before.

I'm now adding all my cabs to see if they break anything

thanks,
dave

I wonder if the above is related to the below! I know one has to do with answering and the other has to do with hanging up...but the #777 error is a commonality. Below has been a workable fix for those who were having problems with answering calls:

Quote:
Originally Posted by akeaw3000
I read somewhere that this problem has something to do with changes the Advanced Configuration program makes. It seemed to happen to me when I set the data connection to disconnect after x minutes of inactivity. I created a registry edit [attached, see direct post] that works for me... it runs automatically from my XDA_UC folder. If you use Advanced Configuration, make sure to run this file afterwards. I found this fix to also help with MS My Phone connection issues I was having.
Note: Did not work on 01.Feb 28244 Standard ROM for some reason :/

Quote:
Originally Posted by Agentz919
Go into registry editor>HKEY_LOCAL_MACHINE>Comm>ConnMgr>Planner>Settings Now under the list look for the Name: SuspendResume and if it says anything other than #777 then change it to #777. Fixes the slider and answering phone... I have to do it all the time after i re-flash.

[frozenbutt]

I just grabbed the Apr 1st Titanium and will flash tomorrow. Hangup has always been an issue with my car's bluetooth so I will test that first thing and post results.

[Targitai]

It's a great ROM. But since it's only Coockie 2.0 - it's imposible to use it. Sense is hangs very often. So, may be will turn to 1.8.5?
PS. May be, that i do not use any carrier cab, becouse i'm from Moldova. And, if it posible, it would be great to see this ROM with rusian language (419). Many Many Thanks!

PPS. I'm sorry for my English.