Registry Wizard for Himalaya - MDA II, XDA II, 2060 ROM Development

Hi all,
I have asked Nicodekker if it is possible for us to use the source for his Registry Wizard application (I am aware you can download it in the first post, but I want to know if I and others have permission to change it).
The Application is described in the following link:
http://forum.xda-developers.com/showthread.php?t=255225
Using the source, I would like to make a Registry Wizard for Himalaya specifically, probably based on the registry of WM6.1 (C_Shekhar) with 30.53mb page pool, as this is the newest Rom, and as it is possibly the last to run well on ours phones, I imagine it will be the most long-lasting Rom as well.
So with this thread, I would like to start a list of registry hacks that are either:
A) Included in all WM6.1 registries (so as not to stuff our phones up with a registry change that doesn't exist).
B) Is not included in all WM6.1 registries, but IS included in the Himalaya's WM6.1.
C) Cannot be changed using the built in software already in the phone IE You NEED a registry editor (or this registry Wizard program) to change the setting.
As people suggest them, I will start making a list (edited into this first post), and eventually (though not in the immediate future, as I need to get VB2005) put them into a workable program, if given nicodekker's permission. That is of coarse, unless someone else (like Ather or C_Shekhar) beats me to it! Which would be just as awesome, as one way or the other, we would still have an awesome application!

Reserved...possibly for list.

Related

Make your X01HT a WM6 Device (for Gaijins)

You just got your X01HT and would like to use the latest WM6 ROM in English with your Softbank account ?
Here is a quick guide, gathering information that has been exchanged and spread accross many threads on this forum (Searches can be fastidious, I know that well...)
I have been reading this forum a lot, keeping on asking questions to everybody, so it's time I contribute a bit to help by describing step by step how I switched my Japanese WM5 Softbank X01HT to a WM6 English device
This post is target at Gaijins who want an English WM6, but still want to be able to use Japanese with it. For a Japanese MUI or ROM, I guess Asukal will probably publish something
***EDIT: for a 100% Japanese ROM, you can now have it here: http://buzzdev.net/index.php?option=...ge=2#msg-30597 ***
I was first willing to cook a ROM including all these, in order to spare some space on my HERMES. I had already cooked an "intermediary" one when Tadzio issued his method to make a "shrinked" OS ROM that would allow you to use the spare space from the ROM
Since this, no point in adding all these mods in my ROM
First: making flashing safe
Download Hard-SPL-V2 from the great Olipro to avoid bricking your device. Here: http://forum.xda-developers.com/showthread.php?t=296722
Install it
Then, get your ROM.
Download the_passenger ROM shrink version of LVSW 20070320 ROM (More space available) and install it (Read threads about flashing ROMs if you are not familiar with that...)
http://www.megaupload.com/?d=8YJATBPG
Install the Softbank AP Settings for your internet connection. You really WANT that. Big thanks to itamae without whom we'd be stuck on first of April this year... (Or I'd still be using WM5)
http://forum.xda-developers.com/showthread.php?t=298031
Now you need a Registry editor
I am used to PHM Regedit. You can find it there for free:
http://www.phm.lu/Products/PocketPC/RegEdit/
To map properly your Softbank Keyboard, do the following registry modifications:
[HKEY_LOCAL_MACHINE\Software\Oem\Qwerty] "Layout"= 30411 (Hexadecimal base)
[HKEY_CURRENT_USER\keyboard layout\Preload] "Default"= e0010411
[HKEY_CURRENT_USER\keyboard layout\Preload\1] "Default"= e0010411
More details here: http://forum.xda-developers.com/show...keyboard+x01HT
To allow the video Call key to appear on your phone keypad, modify the registry as follows:
[HKEY_LOCAL_MACHINE\Security\Phone\Skin] Enabled = 1
Optional: getting rid of useless trayapp (It looks nice... but it Slows down the Hermes and you can replace it with better apps)
Delete TrayApp key from [HKEY_LOCAL_MACHINE\init]
Fix the disappearing micro SD (Doesnt really work for mine... But could work for yours...)
[HKLM\System\StorageManager]"PNPUnloadDelay" = dword:8196 (Decimal base)
[HKLM\System\StorageManager]"PNPWaitIODelay" = dword:8196 (Decimal base)
More details here: http://forum.xda-developers.com/showthread.php?t=294324
Now time to have your Hermes speak Japanese
Japanese fonts
Use the excellent work from Asukal, that you can find here:
http://www.asukal.jp/WM5/LetsJapanNo5.zip
I did have a problem with it: once I executed it, I could not sync with my Exchange server (Quite a pain for my push email account...)
Asukal found the solution: edit the registry, and change
[HKEY_LOCAL_MACHINE\Software\Mobem\CE-Star] "MyNLS" = "\windows\wince.nls"
Japanese input
Not using for myself, but these work perfectly (I tried):
http://www.asukal.jp/WM5/BagojsINPUT.zip
Silent mode switch
You're going to be missing the Softbank unique way of switching to silent mode (Only available in Softbank ROM)
The way to go around this is by using Vibra
Details available here: http://forum.xda-developers.com/show...ighlight=vibra
Download here: http://forum.xda-developers.com/atta...7&d=1164714506
MMS
Softbank's MMS System is a pain because it's incompatible with "classic" MMS systems...
You can download Softbank's software... But... it's slow, big, bulky, ugly, etc... If you dont mind missing the emoticons, you should go for MMSLite
Regedit, Look for Arcsoft. Delete all references to Arcsoft (Sometimes need to be done in several times, some entries being in use if you have by mistake launched MMS Composer once since your flash of the OS...)
If you dont do these eletions, MMSLite will actually not install...
Downlaod and install MMSLite
http://forum.xda-developers.com/atta...2&d=1170599400
It should work perfectly !
I you have enough courage (And ONLY after having installed Hard-SPL 1.11 !!!), you can try flashing your radio
You dont have to... but the latest 1.38 does seem to grant an improved battery life
http://forum.xda-developers.com/showthread.php?t=297925
Now you're done, you have a great phone with a faster OS, more storage space, improved battery life, that works perfectly with Softbank AP, can use Softbank proprietary MMS system, and can read and write Japanese
After, there are lots of other things you can do, like mounting your Extended ROM to gain extra space, Unlock the SIM, etc, etc... But it is not the purpose of this thread. Have fun reading the forum, it is well documented in other threads
Have fun !!
Post duplicated, use this one in WM6 forum:
http://forum.xda-developers.com/showthread.php?t=298919

how to modify HTCCPL reg key and .cpl???

how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
chriskay said:
how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
Click to expand...
Click to collapse
Some in reg, some in provxml Check your PM for more detail, friend !
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
chriskay said:
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
Click to expand...
Click to collapse
I'm not sure what you are talking about, but I do like the word "original".... If you are done, is it worth sharing?
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyfa does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
chriskay said:
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyda does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
Click to expand...
Click to collapse
yups, you can still run some application from extende rom.
At windows folder, you will find config.txt . You have to give some command on it.
The command there, is just a RST ( Reset ) . But If you give a command first, it will install some cabs. It all command from AutoRun
This is some command
LOCK: Enable
CAB: \Extended_ROM\TCPMP.CAB
CAB: \Extended_ROM\Cabs\ABCD.CAB
LOCK: Disabled
RST: Reset
the command will install TCPMP.cab and ABCD.cab
share at XDA is always a good one.
With Cloudyfas ROM, there is a provxml file that sets the keys for AutoRun to somewhere in the windows directory. You will have to remove/alter that for autorun from the storage card.
The point of AutoRun is to allow you to install cabs etc before the user can really use the ROM. UC is to provide users with a faster way to set up the ROM. The two can and should co exist.
so if i got it correctly: putting the common command lines of the extended rom autorun PLUS the command lines of sdautorun into this single config.txt file would make the device boot and install from both locations one by one?
so, what are your recommendations about the registry key:
[HKEY_LOCAL_MACHINE\Comm]
"TurnRadioFlag"=dword:0
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
leave it or kill it??
edit: decided to remove it due to its complete redundancy. it is uc already... now i am close to finishing.
edited edit: put it back in. i think it won't hurt and maybe someone still needs it.
cheerio.
One of Cloudyfas ProvXML files overwrites that, so it is completely redundant!
It's called mxipupdate_zz_oemoperators_102_CheckAutorun.provxml
You can look at it and see what it does.
The two AutoRun files (SDConfig.txt and Config.txt) are separate files that run independently. The point of UC is User Customization. All you need to do is make sure SDAutoRun.exe is in \Windows and that the last line of your config.txt file is
Code:
EXEC:\Windows\SDAutoRun.exe
That is all that is needed for it to run.
ok. removed the redundant entries. i was just thinking there might be some way of a "dual boot". but actually this is rubbish. so i leave it as uc as it is.
The point of UC is that the two are seperate. Everything can be achieved with just one of the two systems, but with UC, you (the chef) can install cabs, and the user can install tweaks etc.

I like, I dislike in the AP4 ROM.....

26/04/08 Update: some "i dislike" solved, check AP4 FAQ for solutions, Tips and Tricks
I am trying to open this thread to help AP cookers to have a single point to check for pro and cons in AP4, avoiding to post BUGS here.
Please explain WHY you dislike something
I've tested it for a while and:
I LIKE:
better battery life in my regular usage
the self portrait/landscape function
touchflo responce (after some tuning)
WM6.1 (SMS and IE)
Latest opera
Stability
I DISLIKE
The BIG htc home (to much home screen real estate used), and resources hungry too! (FULL SOLVED BELOW, 4th post)
The new USB Storage can't show the microdrive (PARTIALLY SOLVED BELOW, 4th post)
The slow keyboard responce (I've installed RESCO too, same delays) (FULL SOLVED BELOW, 4th post)
The comm manager without 3g enable/disable (good for battery saving purposes)
The flashing process, without any user control (I've copied the file unzipped during the installation process and i've dome some "reverse enigineering") I believe it could be done using a simpler command file, from command prompt windows, explaining step by step what is going on. Less "tricolours screen" and better debugging
sergiopi said:
I am trying to open this thread to help AP cookers to have a single point to chek for pro and cons in AP4, avoiding to post BUGS here.
Please explain WHY you dislike something
I've tested it for a while and:
I LIKE:
better battery life in my regular usage
the self portrait/landscape function
touchflo responce (after some tuning)
WM6.1 (SMS and IE)
Latest opera
Stability
I DISLIKE
The BIG htc home (to much home screen real estate used), and resources hungry too!
The new USB Storage can't show the microdrive
The slow keyboard responce (I've installed RESCO too, same delays)
The comm manager without 3g enable/disable (good for battery saving purposes)
The flashing process, without any user control (I've copied the file unzipped during the installation process and i've dome some "reverse enigineering") I believe it could be done using a simpler command file, from command prompt windows, explaining step by step what is going on. Less "tricolours screen" and better debugging
Click to expand...
Click to collapse
thanx for the opinions and feedback. for the slow keyboard response i would try the tweak that turns off the et9. its found in the main thread and will come in the new version of the config app.
the comm mananger was already in the x7510 rom so i just kept it as it is. i see though that it would be a good idea to add the 3g. i need to check if this comm mananger supports changing its function like the one i have in my polaris rom. then i could just have cmonex add a new tab to the config app where u check what options you like in the comm mananger.
i believe the usb to pc tool when turned on to mass storage mode lets you add to the microdrive.
the big htc home can be replaced with the smaller qvga one via the addons rar.
the flash process you would need to discuss with olipro/cmonex. i though believe its as simple as possible right now but i could be wrong.
A problem, for my important one, is that it occupies much memory. It is to say..., in my single country exist maps for GARMIN XT and if I install MANILA to him DIALER does not load GARMIN to me XT by lack of memory, if I install plugins to him in the TODAY does not load the GARMIN to me by lack of memory...
in the AP3 no....
Some Dislike Solved
1. Big HTC Home
go to http://forum.xda-developers.com/showpost.php?p=2053447&postcount=2
download addons.rar
unrar and install HTCHome_1025_721_ALL.cab
FASTER, also in portrait/landscape switching!
2. USB to Storage and Microdrive
Miletb suggest to change:
HLKM\Drivers\USB\FunctionDrivers\Mass_Storage_Clas s\DeviceName from DSK2:
to
DSK1:
it will work fine - transfer speed is also good
If you want storage card later you will need to change back to DSK2:
3. SLOW KB FEEDBACK:
PAWEL sugges to to change:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="eT9 IME"
"Ime File"="\\windows\\eT9ime.dll"
to
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Layouts\e0010409]
"Layout Text"="COMP IME"
"Ime File"="compime.dll"
this will fix 1)the suggestions dialog in sms/emails being missing 2)the accented characters 3)the slow Kb feedback
P.S. To reduce/cancel the TT landscape/portrait switching during driving, just tune the position of the gooseneck support. It is stable in my tests in landscape mode leaving the top 2 cm backward from the bottom (the top is closer to the windscreen). I drive a Nissan Pathfinder http://www.nissanusa.com/pathfinder/ and my tests were really HARD
sergiopi said:
[*]The flashing process, without any user control (I've copied the file unzipped during the installation process and i've dome some "reverse enigineering") I believe it could be done using a simpler command file, from command prompt windows, explaining step by step what is going on. Less "tricolours screen" and better debugging
[/LIST]
Click to expand...
Click to collapse
sorry but I doubt what you did can be called "reverse engineering"
exactly what is your suggestion anyway? is the way HTC wrote ROMUpdateUtility.exe not good enough for you? or what did you mean, please elaborate.
cmonex said:
sorry but I doubt what you did can be called "reverse engineering"
exactly what is your suggestion anyway? is the way HTC wrote ROMUpdateUtility.exe not good enough for you? or what did you mean, please elaborate.
Click to expand...
Click to collapse
Reverse engineering in simple words means to use tools to monitor the program execution, dump the memory used, the data flow trought the USB port, then to have a team analyzing all the info and trying to understand what's going on (and I have time, tools, and team)
I mean the process control. RUU is just a PART of the AP4 flashing process. If I want to flash AP4 again I can't do without flashing the SPL again.
You've built a new tool, NOT a plain RUU. AP3 new version is a plain RUU, AP4 IMHO is a batch process launching RUU, undocumented
I like to have a clear view of the processes, is hard to ask to HTC to show their processes, and you and olipro (and some others, POF is great too..) have done a good job in RUU reverse engineeering (RUU is a batch process too, from HTC...). I would like to have the AP4 .exe documented, having also the view of the .nbh and of the other tools used. May be others can build a new ROM to share, based on the new partitioned ATHENA!
The ATHENA flashed with your tool now is the WORST ATHENA in the world
1) no warranty, no way to go back
2) the only ROM available are AP3 and AP4. None can put a new ROM on it!
3) no official ROMs anymore
4) no "self cooked" ROMs anymore
PRACTICALLY SPEAKING IS NEEDED:
1) a simple tool to go back
AND/OR
2) a clear documentation of the changes done and the tools used
BTW I respect your good job, a tuned AP4 is a good ROM, and we are here to help ATHENA/AP4 to be the best device (and to play with knowledge)
3G button in comm manager solved
Just use schap's advanced configuration tool and ADD it Download it from here: http://forum.xda-developers.com/showthread.php?t=367043
I've removed the push e-mail button because the AP4 comm mgr default layout can have 6 buttons only, and I've added the 3G on/off.
The tool could be "device customized" shoul be nice to have an ATHENA version....
sergiopi said:
Just use schap's advanced configuration tool and ADD it Download it from here: http://forum.xda-developers.com/showthread.php?t=367043
I've removed the push e-mail button because the AP4 comm mgr default layout can have 6 buttons only, and I've added the 3G on/off.
The tool could be "device customized" shoul be nice to have an ATHENA version....
Click to expand...
Click to collapse
so i guess i have the comm mananger in there that u can set what items you want in it. hehe ok there will 100% be a 4.1 I think that will be finally what people wanted from 4.0 and i'll make this one a public beta first so we wont have any issues like 4.0
thanks for your post, I might have previously misunderstand your word usage of RE. so what did you do exactly?
because you people were so impatient we just released AP4 and a flasher, if you all had waited patiently, you'd have got it with extras, such as AP4 vanilla (not requiring new SPL), a standalone AP4 full feature rom (with special NBH header so only new SPL will accept it so no risks!!), and a downgrader utility.
but you will get those anyway just wait a bit more patiently.
until then, if you have an urgent warranty problem and *must asap* downgrade to stock ROM, just let me know in a PM.
also, you are a bit wrong about flashing the SPL again - the AP4 flasher checks if you already got SPL 3.50 on, if you do have 3.50 then it will not reflash the SPL (as that would be pointless as we can agree).
what kind of documentation do you need of the AP4 flasher?
here's what it does:
1. you run the athenaupdater exe, it seems to be waiting for something while it extracts itsutils (pmemdump and stuff)
2. the something is to determine if the Athena is running WM or is put in bootloader (if some moron doesn't read the excellent HowTo a link to which is included at the athenaupdater download) - it does it in the following way: attempts to push pmemdump to the athena, if that fails then after 1 min of waiting it'll error out and shows you the ****sticks message
3. if it finds the athena running WM then it also checks the bootloader version by reading a fixed memory location. then compares bootloader version to 3.50, if it is 3.50 then it won't flash the new spl, if it is not 3.50 (can safely assume it is below 3.50) then launches RUU which then launches SSPL (named version 3.15 and will only accept signed SPL's, signed by public htcdevs cert) as the enterbootloader.exe
otherwise just launches RUU with normal enterbootloader and the overwrite protection of the SPL 3.50 won't let the SPL in the big NBH flash.
4. the NBH flashes and the athena is supposed to nicely reboot to AP4.
if you cancel the process you can be left with corrupt wifi/modelid.
+1: for extra safety the NBH has the special header already so no moron can flash it to SPL 1.20 if they manage to quickly put the device in bootloader after the pmemdump check ran.
well I think that's it.
one last question, what was the note about no self cooked roms?
it is entirely possible, you can take the nk.exe module either from AP4 or from AP3newSPL (or use AP3newSPL as base if you are afraid of xip) and use that to make your rom compatible with the new SPL.
and there'll be a downgrade tool anyway.
sergiopi said:
The tool could be "device customized" shoul be nice to have an ATHENA version....
Click to expand...
Click to collapse
yeah why not, if someone tells me exactly what options from that config app I should port to my config app
cmonex said:
yeah why not, if someone tells me exactly what options from that config app I should port to my config app
Click to expand...
Click to collapse
May be the best solution could be to build XML config file with AP4 cheats and import it into the Shaps default tool.
There are may tweaks in the "basic" tool usefull for AP4 too. Comm manager buttons and many others.
You have a great knowledge about AP4 and about the tweaks used, the fine tuning could be done using the Shaps tool, customized with your XML file as explained
From Schaps
(...) But things changed since 2.x releases, now you can add your own tweaks or translate Advanced Config. by yourself using XML files!
(...)
XML configuration files are named AdvancedConfig_XXXX.xml where XXXX is Locale ID (English and French available at the moment). They contain list of registry tweaks organized by categories.
Here is XML configuration file structure, which is quite simple:
Code:
<advancedconfig>
<category name="Category name" icon="Icon index">
<setting key="Registry key path" name="Registry value name" type="Registry value type">
<title>Tweak title</title>
<description>Tweak description</description>
<values default="Default value">
<value data="Value data 1">Value description 1</value>
<value data="Value data 2">Value description 1</value>
</values>
<restrict>
<value key="Registry key path" />
<value key="Registry key path" name="Registry value name"/>
<value key="Registry key path" name="Registry value name" data="Value data" />
<value key="Registry key path" name="Registry value name" data1="Value data 1" data2="Value data 2" data3="Value data 3" />
<devices>
<model>Device model 1</model>
<model>Device model 2</model>
</devices>
</restrict>
</setting>
</category>
</advancedconfig>Supported value types : integer, string, file, folder.
<values> tag can contain predefined value data for the tweak, which will be displayed in a list in Advanced Config.
<restrict> tag allows you to display the tweak only if it satisfies all the conditions bellow. In this example: Registry key must exist AND Registry value must exist AND value data must equal to specified data AND value data must equal one of those 3 value data AND device model must be one of those 2 models.
Don't hesitate to ask me if something is not enough clear.
You can download here English and French XML configuration files of the lastest Advanced Config. release (2.1.0.0), which is available in this sticky: http://forum.xda-developers.com/showthread.php?t=317070.
Click to expand...
Click to collapse
cmonex said:
(..)
because you people were so impatient we just released AP4 and a flasher, if you all had waited patiently, you'd have got it with extras, such as AP4 vanilla (not requiring new SPL), a standalone AP4 full feature rom (with special NBH header so only new SPL will accept it so no risks!!), and a downgrader utility.
(...)
Click to expand...
Click to collapse
Thank you, for the complete answer and the really interesting schedule
I am patient, as I told in other 3ds, and as many of us I like to play with WM6 knowledge.
I will suggest just a change in the schedule: Downgrader first, Vanilla second and AP4.1 (I've seen a lot of interesting improvements suggested from other users) third
So far these are my finding,
I LIKE:
1. the HTC and Athena Project logo - beautiful
2. the self portrait/landscape function – a little jumpy therefore disable it
3. touchflo response – excellence now I can brake
4. WM6.1 – no comments
5. Latest opera though not as responsive as IE, still trying hard diplomatically.
6. Stability – yes, as good as AP3
7. mic reception – great improvement compare to AP3, not sure is becuz of radio change, handfree call effortlessly
8. speed and memory – no issue so far with all my favorite sw running.
9. splash screen – beautifully done
10. HTC home – best with “ HTCHome_1025_721_ALL
11. AP 4.0 HTC X-Button – wonderful to kill background sw
12. WOW HD Setting – greatly improve audio quality in speaker and earpiece
13. GPS fix – better than before, could be due to radio version
14. Bluetooth - discovered range improved with my S705, never from AP3 or radio 1.50
sergiopi said:
Thank you, for the complete answer and the really interesting schedule
I am patient, as I told in other 3ds, and as many of us I like to play with WM6 knowledge.
I will suggest just a change in the schedule: Downgrader first, Vanilla second and AP4.1 (I've seen a lot of interesting improvements suggested from other users) third
Click to expand...
Click to collapse
we're considering this suggestion already
...and fourth is AP5! (yes we already have new interesting plans for that but shhhh for now )
sergiopi said:
1. Big HTC Home
go to http://forum.xda-developers.com/showpost.php?p=2053447&postcount=2
download addons.rar
unrar and install HTCHome_1025_721_ALL.cab
FASTER, also in portrait/landscape switching!
2. USB to Storage and Microdrive
Miletb suggest to change:
HLKM\Drivers\USB\FunctionDrivers\Mass_Storage_Clas s\DeviceName from DSK2:
to
DSK1:
it will work fine - transfer speed is also good
If you want storage card later you will need to change back to DSK2:
3. SLOW KB FEEDBACK:
PAWEL sugges to to change:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="eT9 IME"
"Ime File"="\\windows\\eT9ime.dll"
to
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Layouts\e0010409]
"Layout Text"="COMP IME"
"Ime File"="compime.dll"
this will fix 1)the suggestions dialog in sms/emails being missing 2)the accented characters 3)the slow Kb feedback
P.S. To reduce/cancel the TT landscape/portrait switching during driving, just tune the position of the gooseneck support. It is stable in my tests in landscape mode leaving the top 2 cm backward from the bottom (the top is closer to the windscreen). I drive a Nissan Pathfinder http://www.nissanusa.com/pathfinder/ and my tests were really HARD
Click to expand...
Click to collapse
Awsome
Would someone organise this in the wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena_AP4_FAQ
is4 said:
Awsome
Would someone organise this in the wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena_AP4_FAQ
Click to expand...
Click to collapse
Wiki updated with GPS best setting, PAWEL's Ftouchflo cab and et9 fix, CMONEX's AP4 installer info, HTC home fix and some others....
I will suggest to READ and WRITE the wiki....
READ and WRITE the wiki
sergiopi said:
Wiki updated with GPS best setting, PAWEL's Ftouchflo cab and et9 fix, CMONEX's AP4 installer info, HTC home fix and some others....
I will suggest to READ and WRITE the wiki....
Click to expand...
Click to collapse
thanks sergiopi
I appreciated your recent postings about the htc home alternatives and the trick about refinding a lost microdrive
I also recommend to others to READ and WRITE the wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena_AP4_FAQ
Can't help myself
This thread is one of the most useful (meaning: if the info's not in here I have found it from what is here) about a ROM I have ever read.
More than that, I saw lots of potential for heated defensiveness, but somewhere that energy got sucked up (I hope it got burned off in the right place). I can't tell you how personally edifying it was for me to read such a grown-up and intelligent conversation in this forum.
I'm glad I have a x7501. Thanks.

HyperCore Athena ROM Kitchen

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

Some ROM cooking questions or tips

Hello all!
I have a few things I'd last to ask, maybe someone could point me in the right direction (I searched for them). I've cooked several several ROM's now, and want to get into more advanced tweaking.
I want to continue:
Learning about how to implement registry tweaks before installation
Learning how to set a default theme (tsk) for ROM
Learning how to map functions/buttons (start menu, ok button, other WM functions) to the keypad (via registry?)
Thank you pros!
Learning about how to implement registry tweaks before installation - provxml
Learning how to set a default theme (tsk) for ROM - depends on what you use for autorun
Learning how to map functions/buttons (start menu, ok button, other WM functions) to the keypad (via registry?) - yes reg settings
Check this tutorial for cooking in reg settings; with the newer kitchens, you put the reg keys into the app.reg files instead of .rgus, but it's all the same idea. There's another tutorial in the same forum on cooking in files, and it's also well worth reading.
To find reg settings, it's easiest to first dump your registry, then make a change that will appear in the registry, then dump the registry again. Copy both reg files to your desktop and compare them with Windiff or Beyond Compare, and find out where changes occurred (ignore stuff like the time). If you want reg settings for cabs you've installed, then I'd suggest using sk tools and opening the 'installed programs' tool. Do a deep scan, and check out all of the registry settings for the program. You can also use SK Tracker to pretty much find anything you want; it's similar (but better) to the windiff method, except it does it on your ppc and it also finds changed in files and databases that occur when you make settings changes to your device.

Categories

Resources