no2chem nueROM Thread - 3.16.651.0 update
 

THIS IS A WORK IN PROGRESS. FLASHING THIS ROM MAY/WILL RUIN YOUR DEVICE.

Files are available to insert to your kitchen. Use baseKit 4004. Please only use the baseKit if you know what you're doing, the use of basekit isn't supported.

Current Public Version: v0.40 alpha build 4004 OS_ONLY

Known issues: None at this time.

Features:
Most OEM customizations removed
Clean
*NEW!!!* Based on Sprint 3.16.651.0
Increased Performance
!!! GPS WORKING !!!

What's new in version 0.40:
CE OS 5.2.1622
Build 18128.0.4.4
Sprint 3.16

This is a base rom for 3.16, which is running quite smoothly at the moment. YOU WILL NEED THE NEW BOOTLOADER TO LOAD THIS ROM!. I've kept the CE OS which is apparently the same version as the one on the Polaris, and it runs quite well. I have not changed the pagepool, so you'll have to do that yourself if you want. You'll also have to install your own touch/dialer skin if desires. Some basic reghacks have been applied as well.

Be sure to also check out my new sprint minutes plugin at http://forum.ppcgeeks.com/showthread.php?p=169929

Because of a personal emergency that has come up, I will not be able to update the rom as regularly as I would like. Please post any requests in this thread and I will try to do my best to accomodate them, provided that it does not involve adding applications to the rom. IF you find out how to fix something, please post it so I can fix it in my next release.

As usual, you can find the rom on the FTP.

ftp://up.ppcgeeks.com/Titan/Users/No2Chem/
user ppcgeeks, password ezupload

Nice to see you are back into ROM development. You can use Paul's dialer with the touch mod rather than the one from the Vogue. Looks pretty much identical.

EDIT: NM, I see that you did include the dialer I mentioned.

no2chem,
I love this!! Thank you!
What radio did you include with this? I ask because so many other folks complain about 2.16 and some versions not playing nice together.

There is no radio included, this is an OS only nbh.

Please don't flame me for asking, but has the D-Pad lockup problem been resolved with this rom. I'm very interested in trying it.

no clue. I actually haven't been able to reliably reproduce the d-pad lockup issue so...

EDIT: I.. reproduced it. I'll be looking into this...
EDIT2: Interesting, I can fix it by pressing the red end call button....
EDIT3: I tried replacing keybddr.dll with the one from alltel, didn't fix it... if anyone has a clue how to fix it, let me know...

I know that this is a common problem with the 2.16 Rom. Interesting.

no2chem,

i beleive the dpad issue and the lockups are both attributed to nk.exe from 2.16. Any chance of a 2.14 based XIP? I think (hope) this would fix the few remaining issues.

Thanks for this update though, anxious to try it!!

also, for a cleaner mms fix, feel free to borrow my browser.dll, which will falsely report IEMobile 6.12 in order to render sprint pages correctly with a Sprint:PPC6800 user agent string.

this rom fixes the lockups associated with 2.16? I thought I could live with it because I need my alarms to work properly but from the time I went into class this am til now (5) hours, I've reset my mogol 10-15 times, the last of which had 4 unread text messages taunting me from my locked up screen which are now lost.

does this rom lock up at all? if not im trying the wm5 rom.

Okay, I am gonna give this ROM a try. Will post results this evening.

I like this one.. gonna flash my phone w/ it momentarily.. Thx no2chem.

dcd, I remember you asked me about this earlier, and I'll try releasing a XIP with nk from the alltel rom. I wonder if this will reintroduce the alarm issue as well...

Although, to be honest, it seems weird that the issue would be with nk, unless it had to do with how interrupts are handled ... Actually, now that I think of it, maybe it is an issue with how interrupts are handled. When they fixed the alarm, maybe they broke the dpad...

But I also had lockup's with the Alltel rom when I was using BT. I guess maybe with the new drivers this might not be the case?

.02

Did the dpad lock up, or did something else lockup?

ya know, i hadnt thought about it, but im sure you're right that this would reintroduce the alarm issues. i guess atm were stuck choosing between the lesser of 2 problems. ill take another stab at xip porting tonight and maybe this time, i can save you the time :)

Just installed and having no issues whatsoever
I also installed Mogul Big Button and 10 button Comm Manager as well MMS and a couple of other programs and no hangups, D pad or BT issues.
Very Stable
Great ROM

I wasn't having the issue with your rom I was just stating the issues I was having with the Alltel rom. Just thinking that the Alltel lock up issue might come back if you were to go down that route.


Sorry for the confusion.

Just to chime in. I haven't tried this Rom yet but I've tried your other Roms and I did have the d-pad lockup issue and it was always on a 2.16 rom/mix. It may just be coincidence but that's been my observation. You guys are doing a great job so I know you'll figure out something. My preference would be to have the Alarm issue vs. the d-pad issue...(I don't use the alarm anyway). Thankx guys.

maybe I should do a little write-up on how to port xip. essentially:

don't dump with rommaster (manually extract the rom)
to do this, first nbsplit, then on payload...
run imgfsfromnb. write down the imgfs start location.
open os.nb.payload with hex editor. go to the imgfs start location, and delete to end. go to the beginning of the file, and search for FE 03 00 EA (unconditional branch to 00 03 FE), and find the second / last occurance. (this is the second xip).
delete everything from the beginning to just before the second branch.
save this as your xip.bin

open xipport. press dump xip.bin. move stuff around, checking the maps between the donor xip and your xip. when you're done, press realloc p, and write maps. if any area shows !!!, fix it. (usually, modify realaddress[r] in imageinfo.txt, where r is the xipregion).

technically, you might need to check the nk.exe pointer in S000 of nk.exe, but i think realloc p fixes that (maybe). if you're worried, from the old map of the xip (not from the donor, but your device), search for the rom_00 header, look at where it starts, check if it matches with the new map If it doesn't you'll have to do this: if the old start address is 8ABCDEF9, search S000 of nk.exe for F9 DE BC 8A (just an example), because of the endianess of arm. replace with new start address, be sure to reverse it as well.

once you're done, write xipout.bin, and write it to os.nb.payload at the right xip2 address (for the titan, its 3200000) (sleepy and not sure if i put the right amount of zeros, but the default is 3100000, so change the 1 to a 2.)

hopefully everything boots up after this. I've used this technique to change everything except nk.exe... which is device dependent, so you'll have to do other stuff...

http://www.airscanner.com/pubs/fogieDC11.pdf is a good reference for arm assembly opcodes

you know that the dialer and 10 button comm manager are built into the rom, right?

dude you seriously rock. im at work so ill have to go over this later but thanks so much this is great info.

no2chem, I had bluetooth shut off on its own after about 2 hours of PDA operation. I didn't connect to any BT devices in that time. The blue light keeps blinking but when I go into the BT settings, the two check boxes on the mode tab are unchecked. No dpad issues so far.

Edit: another shutoff, several instances of the dpad lockup (which I agree is fixable by hitting the red button), and no auto-connect with my BT device (which is the only thing I care about, I know you guys have different goals).

Edit 2: FWIW, I tried the Qwest ROM for a couple of days and didn't have any BT turnoffs or dpad lockups.

Thanks for your work,

- Ray

ROM without Big Button Dialer..if possible!
 

no2chem, everything works great so far! I have not experienced any issues so far. As a note, I am using Radio 1.47 and have the Roam settings to 'Automatic' not Sprint Only. Even with that, no issues with Bluetooth drop or DPad freeze.

But I have one question, since you made the ROM completely plain, how come you included the Touch/Big Button dialer? This dialer is preventing me from correctly changing it to some other dialer (i.e. buttons out of place and no numbers on the buttons). I can turn off the Big Button dialer skin from the registry HKLM\Security\Phone\Enabled --> 0 But that makes that ugly little window appear above the dialpad which shows call log and Contacts.

I think you should leave the Big Button dialer out and keep the original WM6 dialer and make it a very plain and simple ROM which is fully customizable for some people like me who may not like the Big Button dialer. I would really appreciate it if you acknowledge this request.

I'm working on the BT issue - expect to see it fixed soon.

I'll take your advice into consideration. The reason I put the big button dialer was because I thought that it would be easily replaceable, and that the original wm6 dialer was hard to use anyway.

looks like I forogt to move over the vogue bluetooth registry. expect to see a new release later today.

Yeah, I've been toying with some of the builds that use the vogue BT files, and, well, this doesn't seem to have the drastic volume improvements that it did. I was actually wondering if this was really the Touch Bluetooth after all.

I guess you didn't port everything over properly!

Well, I've noticed that this rom is much snappier, despite the 4mb pagepool. I played with it this afternoon, but found that the BT shut off twice during short phone calls, and even while playing A2DP music.

I also noticed that when I paired with my car stereo, instead of displaying "hands free" and "wireless stereo" like it should, it said: "Input Device" and "Handsfree".

Strange that wireless stereo would suddenly become an input device!

It did work though. At least, until shutting off.

Curiouser and Curiouser...

Yeah I would really appreciate it and so would other people, I'm sure. The Big Button dialer is easier to skin but still carries the same blocky base (as far as I know). I'm attaching a cab for a skin that I personally like using...as an example. It should be the Vista Strands dialpad with the standard WM6 buttons. Everything including 911 and ## codes work.

Hmm is this me or something else.. I can't seens to find an option to turn on the flash light in the new camera software.. and with this version, the slide/turn function in HTC Album doens't seens to work either... correct me if i'm wrong about this.

Hmm, ill have to take a look at this. In other news. the bluetooth lockup isn't because of nk.exe, i just flashed my rom with alltel kernel, still getting dpad lockups...

Hey no2chem! A little anxious to try your updated ROM...was expecting it by this morning as per your post. Hope to see it soon (with the standard dialpad :) hopefully) Everything else is PERFECTO...for me at least.

Currently have it set to Sprint Only and Bluetooth was turned off this morning when I got to work and checked.

Question... I want to install the latest rom you have on my P4000 (Telus)

But wish to what this is...

"ProvXML set default Internet Sharing connection to "Sprint PCS" "

Currently using on early version of the OS only Alltel rom that was released by colonel (i think).

I believe that means that Internet Sharing is by default, set to dial 'Sprint PCS' instead of 'Phone as Modem'

Anyone, correct me if I am wrong.

Yeah, you're right, it sets the default Internet sharing to phone as modem. I think if you rename the connection everything should be fine.

As I use this ROM more, I am running ino more and more Bluetooth issue with Sprint Only or Automatic. Again, i am using 1.47 Radio. I am also running into D-Pad issues and as you said, pressng the "end call" hard key re-enables the d-pad but it goes right back to freezing on the next screen.

I am gonna try the fix that somene had posted about changing some power settings and see if that helps. In the mean time, I hope you can have your ROM out tonight or tomorrow so i can test over the weekend. If you want, I'll post detailed test info later.

I've been working really hard trying to get down to the bottom of this, i've been replacing parts of the rom left and right. ... unfortunately I still haven't been able to fix it, and it would be senseless to release a rom with it still broken.

Trust me, I (or someone) figures it out we'll release something - we have a group of people trying to get to the bottom of this.

What I have down so far is that when the phone goes to a sleep state it doesn't restore everything back to normal (changing the power settings keeps the phone from going to sleep, which is why the "fix" works, but it hurts battery significantly). pushing the end call button fixes this. This no doubt has something to do with sprint's "fix" for the alarm....

Maybe this has been tried allready or maybe it ios a rediculous suggestion (I have no idea what I am talking about :) ) but what about replacing the files that control wake-up and standby on the Touch to the Mogul, are there too many hardware differences for this to work or is my lack of experience showing how windows mobile dumb I am :).

One of the best ideas i've heard of no2Chem, regarding the "alarm fix". Focus has been on fixing the BT, which may be the completely wrong "fix"... SCADS, off for more testing.

been running this for a couple of days.. seems to work extremely well, very snappy.. I get a freeze up occasionally when coming back from long periods of time (anything over 2 hours is what it seems like..) I love the touch camera, and the dialer is alright.

I am unable to align the screen manually. Other then that I have had ZERO issues with this Rom! Love it!!!!

Two questions:
1. Zach and Steps, have you guys been using Bluetooth at all? If so, how is the performance including drops?

2. Where is the Flash settings in the new Touch Camera App?