Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

I too have been experiencing problems with Windows Mobile Device Center on Vista while on the 4.x series ROM. I was on 3.9 previously and did not have an issue. It tries to connects, actually connects (WMDC show's its connected and Windows sees the device and can read the flash memory), but immediately disconnects. The phone thinks it's still connected but Vista does not see it any longer. I've got the latest and greatest WMDC and drivers from MS on a fairly fresh install of Vista. Have tried multiple cables/usb ports/etc with no luck. I've also tried connecting via BlueTooth with the same results as I mentioned above.

Otherwise everything else seems to be working fine for now. I'm on 4.1 and haven't moved to 4.2 yet due to the reported ringer issues.

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

3.9 is an excellent release, and it is a final release so it's flawless. 4.2 is not a final release so Mike will definitely make some modifications to it. Overall, 4.2 is pretty good with a couple minor bugs here and there but very useable.

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

Newbie Question Alert *** Old Pros, Look Away! http://forum.ppcgeeks.com/images/icons/icon12.gif

How does a user differentiate a "final release" release from a "not a final release" release? I LOVE 3.9 but 4.x scares the h-e-doublehockeysticks out of me! http://forum.ppcgeeks.com/images/icons/icon7.gif

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

funny! :)Mike puts it in the tag line as final. if not, it is still sort of a beta release. Honestly, I love 3.9 but 4.2 has the new youtube, s2a, and ie6 which kind of grew on me. I am not experiencing the ringer issue others are experiencing but i certainly don't doubt this is occurring. honestly you cant go wrong with 3.9 either. I truthfully bounce between them. for me, tf3d in 3.9 is slightly faster and there really arent any bugs so it is stable as can be. 4.2 is stable for me as well and that is my race horse at the moment.

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

LOL.
It's only final because Mike said it was the final release for that version (#3).
The 4.x releases are using some different internals and are still not as stable (so it seems) as the 3.9 release, but they are quite good. I've been using 4.2 since it came out and have had only minor issues, most of which I've fixed easily.

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

I Just want to say again that I think v4.2 is really great and I really want to use it. I think MightMikes ROMS are the best I have seen and the v4 series has not been out for a long time. I really liked v3.9 and v4.1 and think that anyone would do well using either. I will continue to use his ROMS and hope you all do as well.

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

You guys are really ripping me a new one with this 4.2 release LOL!

Alright guys, can I please ask a favour?

Would one of you kind people gather a list of things that are "broken" in 4.2 and post it here so i can hop in my workshop and start fixing everything?

Well to be honest it's one simple fix which would be the sys... I could easily bang out a 4.3 with a new sys and have you guys smiling, although I want to work on the other issues you guys may be experiencing.

Compile a list, post it, and I shall go ape**** on 4.3!

Cheers!

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

Thanks for the support and handholding with this newbie by explaining the release schema and all the feedback I have seen on the 4.x releases. I, too, love Mike's ROM's and just got lucky by grabbing his first. And 3.9 was the first one I flashed. My Diamond was less than a day old and I had never flashed a ROM, so you guys can imagine the pucker factor.

But it was a clean process, worked the first time and I have to say that an angel was guiding me when I went with Mike's 3.9 on the first shot.

So....Mike, a HUGE thank you for all your hard work!! Now get off your azz and get that next "final release" done!!! Your 3.9 spoiled me!!!! LOL

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

Hey Mike,

I have noticed in the threads the following:

1. ringer is not working for some. reports have been either shortly after flashing or after 24 hrs. some have hard reset and it worked for a while then stopped.
2. active sync not synching push email "as items arrive" after disconnecting from the pc. requires either comm manager reboot of Microsoft Direct Push or soft reset.
3. reports of voicecommand not working. I get an error as well "Error opening the shortcut or locating the target filename"
4. Bluetooth turning off for some.
5. stevedog asked "What regedit must I make to have the screen shut off once a call connects? I appreciate your help. Thanks"
6. new sprint tv not showing up in programs even after install, very strange. need to install old tv, then new sprint tv over top and it works but usually takes several attempts. been getting errors as well. I know Sprint tv, feel free to smack me!!
7. pixelpop and siptang mentioned "Diamond losing all sound output after disconnecting from a bluetooth connection. It happened to me a couple of times, but haven't seen anyone mention a fix."
8. Trident asked about this "Is there a way to change it so that Opera is the default browser when I tap on a link in an email or something?" right now it is defaulted to IE


that's what I have for you. some are not experiencing some of these while others most of them. Thanks man for your work.

Re: [January 17th, 2009] M I G H T Y R O M 4 . 2 [SYS OS 21109 Build 21109] [UC]
 

about the voice command make sure it is enabled under start/settings/personal/voice command but you have to soft reset afterwords for it to work

bluetooth issue"turns off" been there in many different roms as well with no successful fix although i am experiencing it less frequently with this ROM