Related
Here I have a bunch of boring ROMs for your StarTrek. I call them boring because they are devoid of any personalization, customization, or 3rd party apps other than what comes with a shipping ROM. These ROMs are OS only, will not change your initial splash or radio (but it does change the operator splash). A text file ReadMe.txt in the download contains brief instructions on how to flash this ROM. Apparently the 3.06 IPL/SPL in QTEK ROMs is broken and cannot recover via MicroSD so I would recommend updating to 4.01.0001 prior to flashing any of these ROMs, although that in itself can be risky (see below for download). Enjoy, and flash at your own risk!
Details
5.2.1711 (Build 18170.0.5.1) Core OS (SYS) is ported from T-Mobile Shadow Feb. '08 update.
OEMAPPS and OEMOPERATORS are straight from CWS 4.1.502.5 ROM. It has the latest camera and apps.
OEMDrivers specific to StarTrek are the latest, from 4.1.502.5 ROM. Some common libraries are from TMO Shadow ROM.
OEM Edition for AT&T 3125 - The same old, boring, Cingular-branded ROM you're used to, only ported to WM6. My objective with the Boring Edition is a ROM that's indistinguishable from what an OEM would put on a shipping device. This is based on Cingular ROM v4.1.502.5 with many changes made throughout to work with the WM6 core, but hopefully the changes are transparent. It comes with all the bloatware and apps that came with the original Cingular ROM. If you want lots of storage and free RAM, this is NOT the ROM for you!
Adobe Reader LE 2.0 (new, from TMO Shadow, replaces original ClearVue PDF)
Office Mobile (new, replaces original ClearVue Office suite)
Windows Live/Live Messenger (new, replaces original MSN Messenger)
Microsoft Voice Command (replaces Cyberon Voice Dial)
English-only xT9 (new, from HTC S730 "Wings", dated Sep 7, 2007, replaces older T9)
Esmertek Java (new, from TMO Shadow update, replaces discontinued Tao Intent Java)
Cingular bloatware, customization, setup, and theme
Clock/carrier block of Cingular theme changed to standard WM6 style (I liked the bigger clock).
SecurityOff (required, because some apps can't install with it on)
Clean ROM WM6 - Similar to the above (same drivers), but lacking Cingular customization and bloatware. Does NOT have Microsoft Office or Adobe Reader. This will leave more storage available for 64MB devices like QTEK 8500 or iMate Smartflip. As this is an unbranded ROM, you will need to manually set up your GPRS and Proxy connections.
Windows Live/Live Messenger (new)
English-only xT9 (dated Sep 7, 2007)
Esmertec Java
Cyberon Voice Dial
SecurityOff (required, because some apps can't install with it on)
Neo Edition Clean WM6 ROM - Same as above, only added Neo theme from the T-Mobile Shadow. No other customizations.
CREDITS
Thanks to pArtizAn (Erofich), Alex[DFR], Strik3r, and Chymmylt for use of the WM6 XIP in early versions of my ROMs. Without it, my first ROM would have been delayed 2-3 weeks.
Known Bugs - Applies to all versions.
Analog Clock 2 and Analog Clock 3 on external display don't look right. NOT a WM6 bug because the original Cingular WM5 has the same problem!
Possible xT9 can't backspace on some websites bug.
Roll your own! Here are the SYS, OEM, and ROM folders for the Clean Edition ROM. Add this to your favorite kitchen. RUU included.
For experienced ROM builders only!
Download Clean Edition Kitchen files
Other Updates
These are from the latest Cingular ROM, newest for STARTREK that I'm aware of. I have tested these and they worked fine on my phone but I am not responsible if you take the risk and they damage your phone! Flash at your own risk!
Download IPL/SPL 4.01.0001 CAUTION: Flashing IPL and SPL could kill your phone... permanently!
Download Radio 4.1.13.34_02.79.30
Download Radio 4.1.13.46_02.97.90
Prerequisites
Your device must be CID unlocked! See this thread.
Please report any bugs with a detailed explanation of how to reproduce them.
Change Log
Mar 6, 2008 - OEM version, single press of RECORD button activates Voice Command. Should support BT activation now. All clean versions now use the same animated HTC splash. Shows HTC logo on outside screen instead of blank (thanks Erofich). I figured how to port XIPs so all ROMs now use my own XIPs ported from scratch. Added Neo and WM6.1 editions.
Feb 21, 2008 - Fixed Vibrate in Profiles bug, possibly fixed Microsoft Live can't connect bug, updated some files (no longer have to press OK after cold boot setup), newer OS build (18170.0.5.1), newer Esmertec Java, Sim Manager, changed Cyberon Voice Dial to MS Voice Command on Boring version.
Feb 18, 2008 - Changed Tao Intent Java to Esmertec Java, T9 to xT9 on all versions. Added download links to latest radio and IPL/SPL.
Feb 16, 2008 - Added kitchen files for Clean Edition.
Feb 15, 2008 - Added Clean Edition. Changes to Boring Edition: T9 problem fixed, Start menu now allows scrolling (no need to press More), SecurityOff to fix programs can't install problem.
Feb 13, 2008 - Original Release of Boring ROM.
Click to expand...
Click to collapse
Extras
Clean ROM a little too clean? Here are some add-ons in CAB form.
Adobe Reader LE 2.0 Build 288531 (from T-Mobile Shadow)
Neo Black & Blue Theme - Only works on ROMs with Neo integrated. Not just a simple color change, I tried to copy the mockup of T-Mobile Black. It looks almost identical to the mockup on my PC, but unfortunately the conversion from 16.7m to 65k colors results in some false contouring.
thanks man!!
does gprs work in this one?
GnatGoSplat said:
Boring ROM WM6 Cingular (AT&T) - It's the same old, boring, Cingular-branded ROM you're used to, only ported to WM6. My objective with the Boring ROMs is to make a ROM that's indistinguishable from what an OEM would put on a shipping device. This is based on Cingular ROM v4.1.502.5 with many changes made throughout to work with the WM6 core, but hopefully the changes are transparent. It comes with all the bloatware and apps that came with the original Cingular ROM. If you want lots of storage and free RAM, this is NOT the ROM for you!
XIP is thanks to Erofich's WM6.
5.2.1711 (Build 18165.0.5.0) Core OS (SYS) is ported from T-Mobile Shadow.
OEMAPPS and OEMOPERATORS are straight from CWS 4.1.502.5 ROM. It has the latest camera and apps.
OEMDrivers specific to StarTrek are the latest, from 4.1.502.5 ROM. Some common libraries are from TMO Shadow ROM.
Changes
Behind-the-scenes changes were numerous, but visible changes are minimal (although I did make a few):
Office Mobile replaces ClearVue apps. Most devices that used ClearVue in WM5 were changed to Office Mobile in WM6 so monkey see, monkey do.
Adobe Reader LE 2.0 from TMO Shadow replaces ClearVue PDF.
Clock/carrier block of Cingular theme changed to standard WM6 style (I liked the bigger clock).
Known Bugs
Analog Clock 2 and Analog Clock 3 on external display don't look right. NOT a WM6 bug because the original Cingular WM5 has the same problem!
OS only, will not change your initial splash or radio (but it does change the operator splash).
Download
Please report any bugs with a detailed explanation of how to reproduce them.
If there is much interest, I can make a cleaner, unbranded version of this ROM or a vanilla kitchen.
Click to expand...
Click to collapse
Will this work on i-mate SmarkFlip (out of box device without any hacks)
Yes, GPRS works, but I use T-Mobile so I had to add a connection to T-Mobile GPRS. It should work with Cingular/AT&T as-is.
It should work on a SmartFlip, but I'm not sure if you need to CID unlock first.
Downloading and installed...
Attempt 1: Read everything within the Word file. Installed right from the RomUpdate program in the root directory of your
WM6 update. Didn't work, so I will attempt what you have in the Readme text file in my next attempt....
Attempt 2: The Update Utility program says version 3.12.3.1 on the title while the pictures you have in the word file says
version 2.99. Also, when I go through to update ROM, it verifies my current Image version as 4.1.502.5,
I click Update and the next screen it indicates that it will be updating from my current version to the
new version of 1.00.000.0. Then, a minute or so later, I get the following message:
ERROR [270] : UPDATE ERROR Image file is corruprted. Please check your Update Utility.
Do you know how I could resolve this matter because you do not list error 270
within your troubleshooting material? Your UpDate program is not even the same version!
Vista Home, Cingular 3125 unlocked with current released Rom version. So, what am I missing here?
Sorry, I shouldn't have included the Word doc, it's the standard doc that came with the RUU and happened to be in the folder at the time.
Are you using SoftSPL? You MUST use the SoftSPL, it won't work to just run the RUU. The doc I wrote is ReadMeWM6.txt.
You also need to CID unlock according to the sticky thread.
kumar00455 said:
Will this work on i-mate SmarkFlip (out of box device without any hacks)
Click to expand...
Click to collapse
@kumar00455,
GnatGoSplat noted that this should work on any StarTrek, but there is something you should be aware of. In the past, it seems like a lot of people that have tried a Cingular ROM on a StarTrek that is not a 3125 model have not liked it, because they ended up with too little storage memory. This is because Cingular has loaded a ton of large crapware programs on their ROMs. Now, that isn't a big problem for the 3125, because it is actually different hardware from all other StarTreks - it has double the storage memory (128MB) all the other StarTreks (which have 64MB). Since GnatGoSplat has tried to make this just like a Cingular ROM, with all the added programs, you may find you have the same problem. However, I do think there is a thread here somewhere that talks about how to clean all the crapware off of a Cingular 3125 ROM and reclaim some storage memory.
@GnatGoSplat,
Thanks for putting this together - I think I will try it soon on my 3125! I would be very interested in a cleaned-up version and a kitchen as well. And of course, many thanks to Erofich and everyone else who worked on getting WM6 on the StarTrek. I thought we would never see this day!
Oh yeah, I forgot the 3125's have double the storage memory!
I'll make a slimmer, cleaner ROM as soon as enough people have tried this one to confirm it doesn't have any significant problems.
What apps are essential to keep in a cleaner ROM and which can go? What are typical apps that come on a Smartflip or 8500?
device PIN lock working?
Can anyone who has tried this ROM tell me if the security PIN lock works correctly without any problems? I sync my 3125 with my corporate Exchange server, and our IT people enforce a device PIN lock requirement through the Exchange server. So I have to enter a 6 digit PIN if the phone has been idle over an hour. Anyway, I'm interested in flashing this ROM, but if there is any problem with that functionality in this ROM, it would be a deal-killer for me... Thanx...
GnatGoSplat said:
Oh yeah, I forgot the 3125's have double the storage memory!
Click to expand...
Click to collapse
I do like your approach here, though. Start with something as much like the carrier ROM as possible until you know that it's pretty stable, then put it on a nice diet to make it lean and mean. Makes good sense to me...
GnatGoSplat:
i am in china. so i download this file so slow,can you send to me ?my e-mail:[email protected]
SoftSPL
Ok I'm where do i put the SoftSPL file and how do i use it. i tried putting it in Windows directory nothing. please help i really want to get WM6 on my 3125
guyver76 said:
Ok I'm where do i put the SoftSPL file and how do i use it. i tried putting it in Windows directory nothing. please help i really want to get WM6 on my 3125
Click to expand...
Click to collapse
Put it in the root of your device /not/ Windows. Start softspl.lnk as it says in the manual
I tried to use the program you directed the user to transfer. Everytime I clicked on it, I would get an error which stated that the link's program could not be found.
Don't get me wrong over here, I read the directions a few times and did everything you instructed. I am pretty good with directions and I am not one for doing things my own way. If I could help in anyway, just say something. I have alot of times on my hands and I am educated in matters, like, programming on my home desktop.
I made several attempts, I still get the same error, time and time again.
Are you trying to run the correct SPL? The one that looks like a square with a blue bar on top is the correct one. The one that looks like a piece of paper with the corner folded and a Microsoft icon in the center is NOT the right one.
Also, copy ONLY the files and NOT the whole folder. All these files need to be on ROOT folder of your device. If you're using ActiveSync, when you open your device icon, it defaults to My Documents so you have to go to My Device.
Okay, there we go. I copied the entire folder. Sorry. :O(
I'll make a new attempt in just a few.
UPDATE: I tried it, and now instead of an error, it just doesn't do anything. Sorry.
GnatGoSplat -
Thanks man, this ROM has been perfect so far. Just like my previous cingular rom with WM5. You did a superb job. This is just what I was looking for. Thanks Again!
I am waiting for the slimmer ROM since my device is teh European QTEK 8500. I am waiting impatiently
Churchill said:
I am waiting for the slimmer ROM since my device is teh European QTEK 8500. I am waiting impatiently
Click to expand...
Click to collapse
Its worth the wait!!
Thanks
Thanks for the reply i got it working now
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
Now introducing... the HyperCore Athena ROM Kitchen!
First, though, props to anchillus and his HyperCore kitchen. I took it, and made a few small modifications so that it's built for the Athena instead.
Feature Highlight:
Since this is a full-blown ROM kitchen, you can tweak your own ROM however you like. You can do anything that you've seen other people do with their ROMs! All that customizability is at your disposal.
Prepopulated with Windows Mobile 6.1 from the HTC Diamond (5.2.19915).
Prepopulated with applications from the HTC X7501, HTC X7510, and HTC Diamond.
Pictures are not being posted because you already know what Windows Mobile looks like - it's up to you to make it look pretty.
Installation:
Unzip. The "Core" folder goes in as C:\Core. The "HyperCore" folder can go wherever you like; the default HyperCore installer puts it on your desktop.
If you're on SPL 1.2, you'll need to copy an SPL 1.2 OS.nb on top of HyperCore\Build\ROM\OS.nb.
Instructions:
If you want to get your hands dirty right away without reading through the HyperCore instructions, here's the extremely quick version (if you already know how to handle a ROM kitchen):
Make changes in HyperCore\Build. SYS contains the base Windows Mobile 6.1 files, while OEM contains folders that HTC or you provide.
Once you've tweaked SYS and OEM to your heart's content, under HyperCore\Panel\Build, run BuildOS. You'll need to run [1] and [2] to build OS.nb in HyperCore\Build, and then [3] to convert OS.nb to RUU_signed.nbh.
Flash your ROM onto your phone.
...
...
Profit! (j/k)
If you encounter the endless customization loop problem, edit HyperCore\Build\OEM\OEM_Lang_0409\initflashfiles.dat, then find and remove the section for AutoRun.
Known issues/concerns:
The XIP is the XIP from AP 5.0 beta (build 19588.1.1.4, which was from the Sony X1 Xperia ROM). I've tried to generate a matching XIP for the ROM, but it won't boot. Anybody around here know how to create a good XIP?
There seem to be some issues with the Bluetooth OBEX service not being able to start. That's true of this ROM as well. It's able to send files to a PC without a problem, but it can't receive files (although it can copy them).
Even though screen rotation works both in the operating system and in HTC Album, HTC Album's screen rotation has the chance to screw up the operating system's screen rotation. A workaround is to use an application that can restart services (such as the FdcSoft Task Manager) to restart HTC Sensor Service (Athena).
Although the phone skin does work on 128 and 96 dpi, the speed dial application can act flaky and start drawing itself off-screen, which can trigger an error. One workaround is to dial a single number, then rotate the screen, which forces a redraw, after which it functions properly.
The VGA HTC Home plugin could be in slightly better shape. The TabSetting registry entry doesn't seem to work (or at least nobody's responded to me here yet), and the Profile tab shows a keyboard vibration option that, naturally, doesn't work.
The enlarged start menu has some icon overlap on 128 dpi.
The nifty System Status popup on 96 dpi seems to trigger just to the left of the connectivity indicator, while not triggering on the connectivity or signal strength indicators. It does work, just a little strangely on the other dpi settings.
Sym-A now generates the _ character instead of the $ character.
During phone calls, the number keypad is active instead of the alphabetic keyboard.
NOTE:
Much as with Athena Project Kitchen, this ROM kitchen is not to be used for releasing ROMs. It's for personal use only. We really don't need twenty-billion ROMs flooding this forum from everybody who wants that one little tweak.
Exceptions can be made for people who have demonstrated a solid history of producing ROMs. Ask if you feel like you have a strong case for why your ROMs need this kitchen. The current exception list: irus.
Download links:
Megaupload
RapidShare
Other file sharing site suggestions welcome.
Fixes/patches:
Attached to this post. Replace:
HyperCore\Tools\RUU\Athena_RUU.exe with the one from Athena_RUU.zip
Core\ACK\Settings.txt (Updated: July 20, 2008)
I'll be adding additional information to the next few posts over the next several days as time permits (and questions pop up).
P.S. The restriction about personal use isn't about elitism. It's about keeping the forum organized. I just don't want to see every other thread in the forum being a ROM release thread, and there's no reason to make sergiopi's job harder by making him keep track of dozens of minimally different ROMs.
Additional OEMs
NOTE: If you're add OEM packages with modules, you will want to run G'Reloc in your HyperCore\Build directory before you run BuildOS.
HTC EzInput 1.5.31226.0/HTC XT9 1.5.31232.0:
A keyboard designed for use with fingers. There are two large button keyboards (portrait and landscape versions), along with a phone keypad keyboard. The portrait/landscape keyboards swap automatically with the screen orientation. Only works properly in 192 dpi.
Megaupload
HTC LongPressEndKey 1.1.33562.2:
A nifty quick menu program that provides a number of convenient functions. A little less useful on the Athena due to, well, the lack of an end key, but potentially useful regardless. Not tested in other resolutions yet, but likely only works properly in 192 dpi.
Megaupload
Microsoft .NET Compact Framework 3.5.7283.00:
Required for running .NET Compact Framework programs. Meant to replace SYS\NetCF.
Megaupload
WkTask 1.1.7.3c:
A task manager that alters the taskbar to function more like that in traditional Windows, in addition to providing a battery bar and task launcher.
Megaupload
If you would like to change your extended ROM to add packages there for automated installation upon hard reset, you can use the extended ROM editor. You can then convert that with Dutty's NBH tool (available in the kitchen in HyperCore\Tools\Convert) and reflash.
Kitchen Tweaks/Suggestions
Additional OEM Packages:
It's quite possible to find OEM packages out there for quite a bit of software, in order to save yourself time in making your own. If you can't find one, though, there are a number of links on how to assemble your own OEM package - for example, there's a wiki article about making your own OEM package, which also has a bunch of links to existing OEM packages. Just be aware that most of the OEM packages you'll find out there are designed for 96 dpi, and thus may not work on the Athena the way you might expect - the Spb applications are a pretty good example of these, as they come with separate VGA resources.
Package Recommendations:
If you're going to make registry changes, it's usually a good idea to make a custom EM package to contain them. I would recommend using the UUID ffffffff-ffff-ffff-ffff-ffffffffffff, as that will force it to be the last registry file processed (ensuring that your registry entries "win" over those in any other OEM packages).
Package Dependencies:
PACKAGE_Diamond_Album_HTC_ALL can't function properly without PACKAGE_Diamond_HTCGesture, PACKAGE_Diamond_SensorSDK, and X7510_GSensor
PACKAGE_Diamond_VolumeControl depends upon resources in Diamond_LargeTitleBar
RealVGA_DPI_96 depends upon the *_DPI_96 directories in SYS
RealVGA_DPI_128 depends upon the *_DPI_128 directories in SYS
X7510_AudioManager refers to X7510_AudioBooster (menu option)
X7510_TouchFlo depends upon PACKAGE_Diamond_SmartTouch
PROVXML Changes:
If you want to change how your ROM thinks of itself, change HyperCore\Build\OEM\OEMVERSION\mxipupdate_OEMVERSION_100.provxml. ROMVersion is currently set to "Athena_6.1", but feel free to change that to whatever you like.
Registry Changes:
Here's a starter list of potential registry changes.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\MicroDrive\Internet Explorer\Cache"
"History"="\MicroDrive\Internet Explorer\History"
Move your Pocket IE cache and history to your MicroDrive.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MaxConnectionsPerServer"=dword:00000008
Increase the number of simultaneous connections Pocket IE makes to servers to 8.
Code:
[HKLM\Comm\Security\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}]
"AEFrequencyType"=dword:00000002
Prevent Windows Mobile from screen-locking while plugged in.
Code:
[HKLM\Software\Microsoft\Internet Explorer\Navigation]
"4-Way Nav"=dword:00000000
Have Pocket IE-based widgets scroll by screen, not by link.
Code:
[HKLM\Software\Microsoft\Today\Items\"Wireless"]
"Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
Enable the Today Screen Wireless plugin.
Code:
[HKLM\System\CurrentControlSet\Control\Power]
"WakeupPowerOff"=dword:0000003c
Go back to sleep faster when auto-waking (60 seconds).
Code:
[HKLM\System\GDI\GLYPHCACHE]
"limit"=dword:00008000
Increase the graphical caching. A good size has not yet been determined, although this is the value often recommended for QVGA devices (a VGA device likely needs more).
Code:
[HKLM\System\GDI\SYSFNT]
"CS"=dword:00001000
Increase font caching.
Code:
[HKLM\System\GWE]
"Animate"=dword:00000000
Disable window animation.
Code:
[HKLM\System\GWE\Menu]
"AniType"=dword:00000000
Disable Start Menu animation.
Kitchen History
To be filled in.
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
michyprima said:
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
Click to expand...
Click to collapse
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Sogarth said:
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Click to expand...
Click to collapse
okey...
But...i have my kitchen because previously there arent one...
I can download it for oem packages...
XIP and SYS porting Guide
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
sergiopi said:
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Click to expand...
Click to collapse
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
been waiting for a good kitchen for ages. thanks a lot. what build is actually included?
rory
Nice job sogarth, I was looking foward to this all week. i will be giving this a try today
eaglesteve said:
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
Click to expand...
Click to collapse
i am having the same problem is anyone else having this problem
irus said:
i am having the same problem is anyone else having this problem
Click to expand...
Click to collapse
Yep , same here!
michyprima said:
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
Click to expand...
Click to collapse
That's exactly why I haven't linked the first post only but the THREAD address, 24 pages of Q&A, links and files
I have the same problems with sogarth kitchen, the file could be corrupted
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Sogarth said:
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
Click to expand...
Click to collapse
Megaupload kitchen re-uploaded. Rapidshare kitchen in progress.
fards said:
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Click to expand...
Click to collapse
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Sogarth said:
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Click to expand...
Click to collapse
well it's about time they started using proper software then
I post this under the ROM dev for numerous reasons.
The Radio thread is scattered with confusing information about it.
You may wreck your phone by just copying it over the existing one.
There seems to be a requirement to be met by the ROM (patched NK.EXE if I recall right).
There seems to be a patch if NK is not patched by the chef.
Can one really explain what's behind that file and interaction with the Radio?
Admins, if you mind this post here either delete or move though I think it's ROM
related.
tyguy said:
I post this under the ROM dev for numerous reasons.
The Radio thread is scattered with confusing information about it.
You may wreck your phone by just copying it over the existing one.
There seems to be a requirement to be met by the ROM (patched NK.EXE if I recall right).
There seems to be a patch if NK is not patched by the chef.
Can one really explain what's behind that file and interaction with the Radio?
Admins, if you mind this post here either delete or move though I think it's ROM
related.
Click to expand...
Click to collapse
I can answer part of this.
The NK.exe must be patched to allow signed dll files to be added to the rom.
I have not heard of any way to get around the nk.exe patch. If there is Id like to hear it
It remains to be seen if the rilphone dll really makes much difference radio wise. However it does contain some carrier specific stuff in some cases. Da_G is more capable of explaining the technical details.
Thanks arupp I thought so too that there isn't a patch though one of the chefs had a comment on that
http://forum.xda-developers.com/showpost.php?p=3296537&postcount=794
I couldn't find it.
Thank you for starting this thread. I had searched everywhere for the Cmonex's autopatcher, but couldnt find it. Da_G also referenced it in the Radio thread here: http://forum.xda-developers.com/showpost.php?p=3229451&postcount=1012
so to patch or not to patch. That is the question.
Do i patch if i have a custom ROM?
Do i patch if i have the leaked version of the touch pro ROM official HTC (well almost) ?
Good thread thanks.
Found the thread Monx and Da_G referenced here: http://forum.xda-developers.com/showthread.php?t=384137
Post with patcher here: http://forum.xda-developers.com/showpost.php?p=2812111&postcount=23
Wtf??? i need to read the thread a few more times bc im still not sure what to do
Cmonex's autopatcher program is not really intended for the end-user, but more for the chef (it needs to be applied to xip.bin or os.nb.payload)
Her post says it might work directly on the .nbh before you flash it, but it's not guaranteed. I haven't tried it that way either - only directly on nk.exe inside the xip.
So, what you want to do is use the autopatcher directly on the .nbh - but again her post says it's not guaranteed to work.
Da_G thanks for chiming in!
So let me recap:
NK.EXE patch tool designed for chefs, not for Joe Doe users
No direct patch/fix for existing installation
Patch to be applied in ROM image NBH not Radio image NBH (---> hard reset)
Effects not really clear
From what I've read the rilphone.dll interacts with the Radio ROM and may be beneficial for reception and battery life but it's not proven that there will be a positive effect on the GPS for example (we all have lag ).
Furthermore, wrong ril... /Radio combo my make Radio unusable.
For GPS issues a NVRAM fix must be applied (early hardware boot-stage fix) which may not be even possible with the current ROM basis.
Conclusion:
Keep your hands off copying whatever rilphone.dll files are flying around in the Radio thread into your Windows dir and play it secure until the chefs figured it out BUT keep this post updated for general information.
Please tell me if I'm wrong.
tyguy said:
Da_G thanks for chiming in!
So let me recap:
NK.EXE patch tool designed for chefs, not for Joe Doe users
No direct patch/fix for existing installation
Patch to be applied in ROM image NBH not Radio image NBH (---> hard reset)
Effects not really clear
From what I've read the rilphone.dll interacts with the Radio ROM and may be beneficial for reception and battery life but it's not proven that there will be a positive effect on the GPS for example (we all have lag ).
Furthermore, wrong ril... /Radio combo my make Radio unusable.
For GPS issues a NVRAM fix must be applied (early hardware boot-stage fix) which may not be even possible with the current ROM basis.
Conclusion:
Keep your hands off copying whatever rilphone.dll files are flying around in the Radio thread into your Windows dir and play it secure until the chefs figured it out BUT keep this post updated for general information.
Please tell me if I'm wrong.
Click to expand...
Click to collapse
I can say the majoriity of custom roms have the nk.exe patched. If you dont know if your rom is patched ask your chef.
if you look at rilphone.dll in a PE viewer app, you'll see some references in the file to "AGPS". I think it's simply setting AGPS on or Off......or it might be more than that but I do see some references to AGPS in that dll (using the latest dll provided in the 5.05 release which is about 500kb in size)
I notice that my reception varies with different ROMs. I would say that I was getting the best reception with the 5.05 ROM and the 1.11.25.01 Radio. Then when I switched to some custom ROMs, things get a bit worse. The signal strength seems to vary more and I find the phone often switching between 3G and Edge or between Edge and GPRS/GSM. It keeps doing that even when I stay in the same place. I'll make a call with 5 bars of Edge and by the end of the call, be on GPRS when I didn't physically more. Or sometimes the phone will hang on to an HSDPA signal until I drop a call and never switch to Edge, which has 3 or 4 bars of signal strength once it finally does switch. I would imagine that all this switching to different signals is wasting battery too.
1) Could this be an issue with the custom ROMs rilphone.dll? I'm using EnergyROM 1.1a and 1.11.25.01 at the moment.
2) How can I know which radio version my ROMs rilphone.dll is designed to work with?
3) Does having that NK.exe patched allow me to just copy in a different version of the file with no adverse affects?
TheSopranos16 said:
I notice that my reception varies with different ROMs. I would say that I was getting the best reception with the 5.05 ROM and the 1.11.25.01 Radio. Then when I switched to some custom ROMs, things get a bit worse. The signal strength seems to vary more and I find the phone often switching between 3G and Edge or between Edge and GPRS/GSM. It keeps doing that even when I stay in the same place. I'll make a call with 5 bars of Edge and by the end of the call, be on GPRS when I didn't physically more. Or sometimes the phone will hang on to an HSDPA signal until I drop a call and never switch to Edge, which has 3 or 4 bars of signal strength once it finally does switch. I would imagine that all this switching to different signals is wasting battery too.
1) Could this be an issue with the custom ROMs rilphone.dll? I'm using EnergyROM 1.1a and 1.11.25.01 at the moment.
2) How can I know which radio version my ROMs rilphone.dll is designed to work with?
3) Does having that NK.exe patched allow me to just copy in a different version of the file with no adverse affects?
Click to expand...
Click to collapse
-----------------------------------------------------------------
Only NRGZ28 should be able to answer your ????
As he as mentioned in 1st page of thread "
This ROM is CE OS 5.2.20764 (build 20764.1.4.3) and the version is: 5.05.405.1 ,all from official Raphael ROM." using same build with which 1.11.25.01 radio is attached. Obviously it should have same DLL file if he has not altered it during cooking.......
Here's a bit more of a technical explanation for the whole thing:
rilphone.dll is the 'interpreter", or the "middle man" inbetween the Microsoft-desgined "Radio Interface Layer" or RIL - you can think of it as the Radio ROM speaks spanish, and Windows Mobile speaks english.. so when a program wants to do something involving the cellular radio, say, determining the signal strength to display the "bars", it issues a command to the RIL.. the RIL forwards this command to rilphone.dll, which interprets it into an AT Command. rilphone.dll then communicates through a standard serial port connection through SMD9: to communicate back and forth with the Radio ROM. Any responses are then translated again by rilphone.dll, and passed on to the RIL.
So, let's say a new command gets added to the radio. In this case we'll use a new command that was in fact added in 5.05, [email protected] - if the rilphone.dll is not updated, it is not aware of this new radio command, and will never issue it to the radio ROM. So you'd potentially be missing out on whatever that command does. Also, if a change is made to the required format of some other AT Command, the rilphone.dll will not be aware of this change and still be using the old format.
Carrier-specific rilphone.dll's also have features that generic ones do not (such as the 5.05 rilphone.dll in the htc-branded build most custom roms are using) - one such feature is CNAP support for Rogers - it seems support is built into all radio ROM's, but if rilphone.dll does not have specific support for CNAP, it never reads the caller name into the registry for display on the dialer. There are a number of similar carrier-specific features i've observed.
That should cover the function of rilphone.dll and the reason you'd want to keep it on-parity with the radio ROM... and in some cases why you'd want to use an older rilphone.dll (to maintain support for CNAP, etc)
Now on to the nk.exe patch -
nk.exe is the "boot process" for Windows Mobile.. it brings up hardware to initial values and displays the radio/protocol/build version info on the intial boot screen.. nk.exe controls such low-level things as the size of the page pool, certificate checking, etc.
This is where the nk.exe patch comes into play.. it replaces the code that checks certificates with a "No Operation" - so the system now trusts all code installed, regardless of if it has been signed by a trusted provider or not - this is a good thing, as you control all code being installed on the device, rather than the OEM, and one would presume at the point you want such checks removed, you know better than the OEM
Without the nk.exe patch, when you replace rilphone.dll, the system checks it against it's internal certificate store, finds that it's not signed with a trusted certificate, and refuses to load it. This is why replacing rilphone.dll on unpatched ROM's results in no radio function.
Once you have a patched nk.exe you can replace any trusted file in the system with an unsigned file and not have to worry about the checks - note you no longer need sdkcerts.cab either as this is intended to load onto your device's root certificate store, and then manually sign the files you're replacing with the sdk certificates, then it would be loaded up as a trusted file.. however this doesn't work on drivers that are loaded early in the boot process, as there are 2 "states" of the certificate store - one early boot state where the drivers are loaded, where it's using a pre-defined set of root certificates (specifically sysroots.p7b in XIP, which contains 17 certificates from trusted root providers) - the 2nd "state" of the certificate store is farther on in the boot process, after drivers and services are loaded - this is when it would load in the sdk certificates and allow you to load manually-signed drivers. But again this is too late in the boot process to allow sdkcerts.cab to work for Drivers and Services - which is why the nk.exe patch is needed.
Note that any files/modules cooked into ROM are automagically treated as trusted, regardless of nk.exe patching status or if the files are actually signed with a trusted authority - it's assumed by Windows Mobile if the file is cooked into ROM, it must be trusted.
Incidentally, I believe this is the reason HTC created the "BootLauncher" service - so that they could load up services signed with their own stuff after creation of the ROM (patches, hotfixes, etc). Basically BootLauncher loads up during the services stage, and waits for a pre-defined period of time before then loading it's own set of services (wait time and services to load are defined in the registry under HKEY_CURRENT_USER\Software\HTC\BootLauncher)
the autopatcher searches for a string to replace, so it might work on the .nbh.. the feeling i get from cmonex's post is that she didn't design or test it against that scenario, but it might work
Hope that sheds some light on the situation, and isn't too complicated!
Hi DA_g
Thank you Da_g for such a beneficial explanation....
I hope its going more complicated now..... as you have explained
"Carrier-specific rilphone.dll's also have features that generic ones do not (such as the 5.05 rilphone.dll in the htc-branded build most custom roms are using) - one such feature is CNAP support for Rogers - it seems support is built into all radio ROM's, but if rilphone.dll does not have specific support for CNAP, it never reads the caller name into the registry for display on the dialer. There are a number of similar carrier-specific features i've observed."
all radios have Carrier-specific rilphone.dll's so obviously all its not only with 1.11.25.01 (Raphael radio) all other radio's i.e, for example .16,.19,.28,.32,.20 if so obviously the results would be not stable for all the users with different ROM's and Radio's.......... Now the big ? rilphone.dll should be programed for different carriers to the specific radio
The way it seems to work from my observations is this:
Carrier X issues a "ROM Request" to HTC, specifying what support and configuration they require (such as CNAP support for rogers)
HTC then assembles the ROM to their specifications, using the latest drivers, etc, available at the time.
All radio rom's seem to include support for all carrier-specific options, they just need a rilphone.dll that is aware of the particular option to enable it.
So for us to get a newer rilphone.dll with rogers support (say, 5.05), rogers would need to issue a "ROM Request" to HTC, and they would need to fill it.. then we would have the rogers 5.05 rilphone.dll.
Using an older rilphone.dll has unknown effects (as it will not be aware of newer features in new radio version, etc) but so far has not shown to cause specific issues.
Hi DA_g
I need your help regarding this...how to edit rilphone.dll i am working as switch engineer for Ericsson india for GSM ...hope fully i would be able to understand some of the specifications present in this file.
Editing a .dll is beyond the scope of my ability to explain in a forum post, you need to do some research into reverse engineering and ARM disassembly..
Particularly, if this screenshot scares you: http://www.hex-rays.com/idapro/pix/idalarge.gif
You probably don't want to even get into it
Da_G said:
Editing a .dll is beyond the scope of my ability to explain in a forum post, you need to do some research into reverse engineering and ARM disassembly..
Particularly, if this screenshot scares you: http://www.hex-rays.com/idapro/pix/idalarge.gif
You probably don't want to even get into it
Click to expand...
Click to collapse
Ha ha ha really it is scary...............
But in my opinion individual Radio should be mapped to rilphone.dll with carrier specification with out this non of the radio would give best result .....
Depends on one using carriers with different frequencies for example.... i got tp with radio ver .28 (raphael) which is made for IDEA operator which uses 1800mhz freq, where power of the cell site & TP might be programmed vious according in rilphone.dll.....
i did SIM unlock.....Now i am using TP on Airtel operator which work on dual band 900 & 1800 so it is obvious that RADIO would not give me best results.
Results are vigorous ....dropped calls, voice break, poor coverage, poor battery performance,e.t.c................
So all ROM with associated with RADIO would work better on TP who uses specified Carrier...
Is there a way to get or create an universal rilphone.dll ?
Only someone with access to rilphone.dll source code could create a universal rilphone.dll.
Quite doubtful that HTC would be interested in doing this
aruppenthal said:
I can answer part of this.
The NK.exe must be patched to allow signed dll files to be added to the rom.
I have not heard of any way to get around the nk.exe patch. If there is Id like to hear it
Click to expand...
Click to collapse
I think you mean unsigned.
there is a way around... you import your own certificate into the device's trusted certs store and then sign the system DLL with your cert and copy it over... WM accepts this no problem and this is exactly how I used to do things.
After a recent scare when I dropped my phone I thought that was it - this time it really is
While flashing a different radio the flash started failing. Mtty revealed bad blocks and now I have a Nike sized brick on my hands that won't even power on, let alone boot.
It's been fun and I really appreciate everyone's help while rerom has been developing over the past couple of months.
I urge you to give NemanjaLO and d_train as much support as you can so that they can build the best ROMs possible for the Nike.
I've got to try to find my old Hermes now...
Au revoir,
Colin.
rerom build 23001
UPDATE:
I've upped a 16key 2G revision 2 which includes SmartLock in case anyone is interested.
I've replaced Backlight in Settings as it wasn't the WM6.5 version anyway.
Check the 23001 folder linked below.
P.S. just in case you hadn't noticed I reverted to netCF 3.5 with 21820 and 23001 as 3.7 doesn't include everything required.
-------------------------------------------------------------------------
Build 23001 is faster than 21820 and this new rom includes a few tweaks and I finally added Long Press End Key (don't know why I left it out).
All flavours are now available in the 23001 folder at 4shared.
rerom build 23001 - all varieties
Enjoy
rerom build 21820
Build 21820 now available including a few changes and fixes:
- Acrobat Reader now works (thanks to NemanjaLo for the info)
- A Java environment is now in there (JBed)
- All the stock themes are back
- The latest exe for Notepad is included
All flavours (16 & 20 key, 2G and 3G dialers) can be found in the 21820 folder at my 4shared account here:
rerom build 21820 - all varieties
rerom build 21815 - test build
Here's a test build of 21815 - just for 16key with 2G dialer for now.
Because of the issue with themes I've stripped out all the other themes except Classic Blue until it's completely sorted.
I've also added Shamasis' Notepad Mobile to the Office folder in the Start Menu - much lighter when you just want to do a quick text file (although I need to update the version of the exe to the latest)
re-rom 21815, 16 key & 2G Dialer
rerom includes:
NetCF 3.5
Mortscript cooked in
Nitrogen Media Player
Clauncher Titanium plugin (With device Lock pre-populated for easy access)
A mortscript to choose the exe launched when swiping up from the bottom of the screen
I have removed the music tab from Titanium in this build as the functionality is quite limited and, with the other tabs added, I wanted to reduce a bit of clutter.
The script I have added is placed in the StartUp folder so that you can configure your choice of app after configuring the phone. Just select an application to launch by an upward swipe. It pulls the current path from the registry (just for info) and will be removed from StartUp after you make a selection. You can change this at any time by running \Windows\swipe.mscr.
Note: cancelling the file selection with leave the script in the Startup folder to run on the next reset.
Colin.
Great listing.
Thanks
I've got just about everything sorted but I've managed to introduce a problem with messaging loading after boot and then hanging.
Got to try to pin this down.
I'd like to say thanks to the following:
jerpelea
nemanjaLO
rling
D_Train
twolf
ervius
showaco (Titanium weather) & Mnemonique for QVGA version with M2D icons
and everyone else that contributes to the Niki forum
reserved for updates
Small issues:
- missing IE shortcut;
- missing MSN Money widget (I already get used with it from other WM6.5 ROMs );
- in PhonePad when scrolling down the call history after couple of contacts the rest of them are with black contrast;
- in Weather widget I cannot set an European city (Bucharest for my case) if I don't know the location code (only by name like it works for HTC weather applet), I assume the zip code works only for US.
Other than that your "baby" works great (however I used it only for 2 h so I keep testing it), thanks a lot!
mishu said:
Small issues:
- missing IE shortcut;
- missing MSN Money widget (I already get used with it from other WM6.5 ROMs );
- in PhonePad when scrolling down the call history after couple of contacts the rest of them are with black contrast;
- in Weather widget I cannot set an European city (Bucharest for my case) if I don't know the location code (only by name like it works for HTC weather applet), I assume the zip code works only for US.
Other than that your "baby" works great (however I used it only for 2 h so I keep testing it), thanks a lot!
Click to expand...
Click to collapse
- missing IE shortcut is intentional as you just hit the favourites item on Today
- PhonePad - thanks hadn't noticed that, I'll look into it
- as mentioned in the first post - MSN widgets are removed from this rom (I may include them when I do a new version with an updated build)
- for weather you need to visit the accuweather website and do an international lookup - Bucharest is EUR|RO|RO010|BUCHAREST. Add that as the location code
Thanks for testing.
You are right, I missed the Favorites shortcut (used for IE launching) from the home screen because I deleted it as I want to keep this sceen as empty as possible. I think the MSN widget is more powerfull (includes a sattelite map) than the one included in the Titanium interface. Meanwhile I figured how to get the city code (I remember I read something in another thread and I search for it). Thanks again for your work and I'm looking for your next release!
The MSN widgets were originally broken in build 21202 (this can be fixed with updates SYS files) so I will probably include them in an updated build.
As the Titanium Weather is installed during config it can be uninstalled or you will be able to have both (one for quick reference and the other for detail)
I think the phonepad issues is a problem with the skin. I will test with a different dialer package and let you know.
Is this ROM working in French, and for Niki 100?
This is just WWE I'm afraid.
It is an English ROM, so if you need one in French you should look for a specific designed in French one (look in the thread title, it is mentioned there). It is working on Nikki100, I have one running this ROM without any problem.
RE-ROM v1.1 posted - check OP.
Well done. Nicely.
Downloading to test.
Thanks for the update
randomelements said:
RE-ROM v1.1 posted - check OP.
Click to expand...
Click to collapse
Great ROM! Works perfect so far, keep you updated with testing progress!
Thanks Mishu.
It's a shame none of the HTC dialers work with WM6.5 but the stock one does the trick.
V2.0 with build 21501 now available. Check OP.
Hi, bad news (at least for me) with your latest ROM . First, after running the first time after flashing (when the Customizing process was ended) the phone shut down instead of restart. I flashed twice this ROM and the same behaviour. What was worst the phone somehow stopped responding after configured it (in the way I do this with all the ROMs). I reset it twice but no luck. The USB connection wasn't working at all, luckily after I put it manually in the three-color screen I was able to flash back the 1.15 ROM which works ok. I don't know what is wrong with this build, however it seems I am the only one with this problems. Thanks again for your work!
Strange.
I've flashed it a few times and not had any problems. I'll have a look and try a rebuild.
Thanks for letting me know.