G.O.T. have a pre-release of the newest Motorola Firmware SHOLS_U2_36.0. I've been running this ROM for a couple of days now, it's stable and fixes almost all issues I've encountered with 2.1 on my milestone. This is NOT a hacked or custom ROM, it's a leaked official Motorola ROM. I've noticed that the following bugs are NOT fixed: 1. Camera bug which puts a small corruption on the right hand side of a wide screen photo is not fixed 2. Long press on Search with the keyboard open still doesn't work (works OK with keyboard closed). Everything else seems to work, no more random reboots, alarm clock functions correctly, etc I have nothing to do with this group or this release. I am just a happy user passing on the info. From their site: Firmware releases G.O.T.'s Blog We are proud to present to you the 2nd release of the new firmware for UK and Central Europe These are not any modified HK firmware files, but the specific Motorola firmware releases that will be released soon. G.O.T. only injected the vulnerable recovery from nadlabak directly in the SBF files. All other modifications require our G.O.T Open Recovery. Bugfixes in this release: The following known bugs have been fixed within this release. We have done some testing and can confirm these fixes: Media Player resumes and plays music without being user-initiated is fixed Spontaneous reboots did not occur during our testing. Wake-up Alarm and other scheduled events now work properly. Confirmed with the alarm tester the infamous nadlabak has created (many thanks for that) Issues that although WiFi is active the MS cannot connect to authorised APs fixed. Camera displays 7pixel-wide streak on the right hand side when in Widescreen Mode – not fixed Settings widget displays GPS enabled although Navigation and GPS fix no longer required – works as designed to alarm user that GPS functionality remains active in the background Notification LED only lights up when in standby mode (screen disabled) – works as designed We have tested and verified these within the G.O.T team and during our tests these bugs have no longer occurred. Since every MS is configured differently that does not mean that these may not occur in your particular configuration.