BW WM7 Black and Blue Windows Phone 6.5 ROM Final

[Guest jaycarl]

So if I got my Omnia in July 2009, do I already have the newer digitizer? The phone responsiveness seems okay but I have not compared it to an older Omnia.

Does the digitizer wear out after a while and need to be replaced? I guess what I am asking is, are the old ones just wearing out and replacing them fixes that, or are the newer ones better to begin with?

Thanks

I don't think its a problem with the digitizer wearing out. The problem seems to be faulty or not as responsive first batch of Omnias that were sold.

I talked to a acquaintance at the carpool who bought her phone around April 2009 and her phone is just as responsive as mine (but mine is better since I use BW Rom of course).

[Guest MikeDaGeek]

I had the same problem and downloaded the samsung keyboard and it still not allow me to enter a number in google maps signin. I used "keyboard" from the list of keyboards and it was a tiny little keyboard. it allowed me to enter numbers in the signing.

Not sure whats up with that.

Were you successful with getting logged into Latitude?

I tried switching the keyboard in Start>Settings>Personal>Input ... but all we have is the one KB (Which I like) ... you DL'd the old samsung KB is that right?

[Guest blazingwolf]

Were you successful with getting logged into Latitude?

I tried switching the keyboard in Start>Settings>Personal>Input ... but all we have is the one KB (Which I like) ... you DL'd the old samsung KB is that right?

There are two keyboards in the ROM. The LG Incite keyboard and the standard keyboard by MS. To change keyboards tap and hold on the SIP button and when you let go the option screen will appear to choose the SIP you want.

[Guest MikeDaGeek]

There are two keyboards in the ROM. The LG Incite keyboard and the standard keyboard by MS. To change keyboards tap and hold on the SIP button and when you let go the option screen will appear to choose the SIP you want.

D-OH!! ... Click & Hold ... (Right Click) D-OH!!!

Got it ... and I'm in ... Thanks again BW!

[Guest flanker1743]

Hey BW,

Just flash your blue version today, looks absolutely fantastic! (My first flash, btw :-D). So far, so good. Upon the first two soft resets, I got an error message trying to launch some updater program (the name escapes me atm), but it hasn't reappeared since then. Other than that, things look really smooth! I'm excited to play with it some more. Thanks for all your hard work!

-D

[Guest kdkinc]

Hey BW,

I asked Bgill this question and now i'll ask you....

If you update to a new phone which one are you leaning towards ??? :)

[Guest flanker1743]

BW,

I ran into a problem. Could be I'm just new to the whole flashing thing or whatever, but I can't download MMS to my phone. It says there's one in the inbox but the connection fails every time I say to "download."

Any ideas?

[Guest blazingwolf]

Hey BW,

I asked Bgill this question and now i'll ask you....

If you update to a new phone which one are you leaning towards ??? :)

I'm still looking at the Omnia 2. If they get a hard SPL for the Imagio though it looks like a nice device.

[Guest blazingwolf]

BW,

I ran into a problem. Could be I'm just new to the whole flashing thing or whatever, but I can't download MMS to my phone. It says there's one in the inbox but the connection fails every time I say to "download."

Any ideas?

Is Verizon having any issues in your area? I just tested MMS on mine and it worked.

[Guest flanker1743]

Is Verizon having any issues in your area? I just tested MMS on mine and it worked.

I just got it. Apparently I didn't have the proper connection selected for downloading. Never mind, haha.

Everything is working pretty great. I've got a lot of texts so the messaging app is a little slow to close, but otherwise it's looking really nice.

:)

[Guest snapz54]

can we get a screenshot of the incite keyboard?

[Guest blazingwolf]

can we get a screenshot of the incite keyboard?

There's one in the thread already but I will see if I can find it and post it again.

Edit: Added to the first post.

Edited October 12, 2009 by blazingwolf

[Guest adamhos]

With the last two builds, on startup I always get a Morscript.exe Cannot start mortscript... error. Does anyone else get this, and is there a way to fix it?

[Guest jtmessimer]

BW I rocked your rockin republic since I got this phone so and loved it...just installed the black and it started to lag when I soft reset...task manager said the "LargeDisplayStart.Exe" was the culprit...has this already been addressed...Thanks for all your hard work!

[Guest blazingwolf]

BW I rocked your rockin republic since I got this phone so and loved it...just installed the black and it started to lag when I soft reset...task manager said the "LargeDisplayStart.Exe" was the culprit...has this already been addressed...Thanks for all your hard work!

Your the first to report any issue like this and I have never seen it. Under normal circumstances LargeDisplayStart.exe is not used unless you are using the volume control. What are you doing when you notice the problem? Soft reset only? That doesn't make sense as everything is cleared upon the soft reset.

[Guest ranlil]

I did the Blue on Saturday and I really love it! I do have a couple of issues though. Regarding the earlier posts where the broadband connection weren't there. I flashed it twice and it wasn't there. Easy to configure though. User name = [email protected] no password and remember to check the box to remember password.

On some bootups I get the massage that another poster saw where certain programs couldn't load check the task manager... etc. I'll try to get a screenshot next time. jtmessimer "With the last two builds, on startup I always get a Morscript.exe Cannot start mortscript... error. Does anyone else get this, and is there a way to fix it?"

I had a i760 that had WM 6 on it and as soon as VZW put out 6.1, I loaded it. Quite often the device would shut down and the only way to get it going again was to remove and reinsert the battery and restart it. VZW replaced the device and it had 6.0. When I flashed to 6.1, the new device did the same thing. So VZW let me get an Omnia (for $100 and new 2 yr). So far it has not had any real issues. Since flashing with Blue, now my Omnia does the same thing. Touching a key doesn't bring it back to life and removing and reinserting the battery is the only way to get it going again. It might not be your ROM as I haven't run the latest VZW ROM by it self before flashing to Blue.

Edited October 12, 2009 by ranlil

[Guest vipergts450]

BW if you remember, I posted that i noticed LargeDisplayStart.exe causing the lag and potential freezes a few months ago in the old ROM thread.

http://www.modaco.com/index.php?act=findpo...amp;pid=1053530

Your the first to report any issue like this and I have never seen it. Under normal circumstances LargeDisplayStart.exe is not used unless you are using the volume control. What are you doing when you notice the problem? Soft reset only? That doesn't make sense as everything is cleared upon the soft reset.

Edited October 12, 2009 by vipergts450

[Guest compnird]

Love your ROMS BW but I don't like the keyboard selection. I can't seem to get the original Samsung keyboard to load (have a cab for it but it never shows up). Fingerboard 2.1 works but I don't like it, tried a few other options but they never install properly.

Do you, or anyone out there, have a cab for the standard Samsung Keyboard? Preferably in black if that's even possible.

[Guest IronFox]

After a few flashes, I was able to get the blue version fully working properly. I installed a different theme but cant get the phone skin to work. I've used advanced config to change the phone skin to enable and the phone dialer wont work at all but work (with the old skin) if I change it back to disable. And ideas?

[Guest blazingwolf]

BW if you remember, I posted that i noticed LargeDisplayStart.exe causing the lag and potential freezes a few months ago in the old ROM thread.

http://www.modaco.com/index.php?act=findpo...amp;pid=1053530

That was on an older ROM. He is the first to mention it on this ROM.

Again, there should be no issue with it after a soft reset because it is not auto loaded in to memory unless something has been changed.

[Guest blazingwolf]

Love your ROMS BW but I don't like the keyboard selection. I can't seem to get the original Samsung keyboard to load (have a cab for it but it never shows up). Fingerboard 2.1 works but I don't like it, tried a few other options but they never install properly.

Do you, or anyone out there, have a cab for the standard Samsung Keyboard? Preferably in black if that's even possible.

The one hartv427 did is reported as working and the Shokka9 works.

[Guest blazingwolf]

After a few flashes, I was able to get the blue version fully working properly. I installed a different theme but cant get the phone skin to work. I've used advanced config to change the phone skin to enable and the phone dialer wont work at all but work (with the old skin) if I change it back to disable. And ideas?

That's because the Samsung dialer is not included in this ROM. If you want to go back to it then you will need to install it.

[Guest jonmeza]

Hi. First off, thanks BW for a really nice ROM. I'm new to the whole flashing biz, but the advice from all the posts and your initial instructions really made this an easier task than I thought it would be.

I flashed my phone with the latest ROM yesterday afternoon and explored the apps and features you cooked in there. Later I decided to sync up to My Phone, and bring back some of my own apps and programs saved as cabs on my storage card. Things were going smooth, and reinstalled all my programs. ( Inesoft Dialer, ThumbCal, Beejive IM, Bing, CleanRAM, Clear Temp, Facebook, Netflix, Panoramic MoTweets, SPB Radio, Total Commander, VS Painter Trial, and YouTube). Customized everything else the way I wanted it with SPB Mobile Shell 3.5

My only gripe left was the LG Keyboard. It's good but, I just got really used to the Samsung Keyboard and T9 phonepad. So...I had the bright idea of installing the Omnia Keyboard through a cab someone had linked to in the forums. Soft reset, and everything went down hill.

The first thing I noticed was Inesoft Dialer was giving an error at Startup. Soft reset again, and it locked at the Microsoft Phone boot screen. Waited a good while, soft reset again, same thing. At one point it actually made it to the AutoLock settings screen and the screen became unresponsive again. Several more soft resets, nothing. I thought I was getting somewhere when it finally made it to the WM 6.5 Home screen. I received boot errors for MS 3.5, Inesoft Dialer, AutoLock, and a general boot.exe error. I couldnt make it to the Hard Reset menu before it would lock up again. I tried connecting my phone to to my laptop with USB, and luckily was able to reload the ROM after several attempts at establishing a connection. Things are stable right now, but havent reinstalled anything other than My Phone and Total Commander, because another attempt with Inesoft Dialer gave me an error, although the program itself worked.

I don't know if it was the Samsung Keyboard that caused the lock up or if it was related to any of the programs giving boot errors. Has anybody here had anything similar happen, or been able to get an alternate Dialer or Keyboard working? SPB Mobile Shell 3.5?

Thanks for reading my story, LoL

[Guest compnird]

The one hartv427 did is reported as working and the Shokka9 works.

Thanks! The Shokka9 did the trick. I am now good for a bit. Thanks!

[Guest Dewain Robinson]

Blazingwolf,

What is the application that you put in that allowed the wifi router functionality? Can that be installed via a cab?

Thanks,

Dewain