Related
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.
I've just finished successfully flashing an unofficial WM6.1 ROM to my StarTrek (Cingular 3125) using only a microSD card (no data cable, no ActiveSync, no Windows) and the brilliant work found on this forum. I thought I would share the details of my success in the hopes that it will help the next person who stops by, since I myself found it difficult to find a definitive yes/no on the matter here.
Requirements:
HTC StarTrek
I had the Cingular ROM; Any should work.
microSD card
IMPORTANT: Your card MUST be using FAT32 for this to work. If it is not already so, back up its data and do this now. (Windows will show a FAT16 volume simply as "FAT".)
AppUnlock tool
The one linked at this post is good. http://forum.xda-developers.com/showpost.php?p=1146363
The ROM you wish to flash
I used the WM6.1 Standard ROM posted here by Erofich, since it is most appropriate for a Smartphone such as the StarTrek. You can also use the Professional version, though it is intended for use with a touch screen, so you will have to control a cursor with physical keys.
A computer you can use to extract and place these files onto the microSD card.
After you've obtained the listed files and have them extracted somewhere on your computer, copy the following files to your microSD:
SurrealNetworksAppUnlock.cab (Anywhere)
The entire SSPL directory from your extracted ROM download. (Anywhere)
RUU_signed.nbh, found within the RUU directory of your ROM download. (Rename this to STARIMG.NBH and place it in the top-most level of your microSD card, not inside a folder.)
Insert the microSD into the device (the door is located beneath the SIM card). Using the File Explorer (or Total Commander, if you have it), move or copy the three contents of the SSPL directory from your Storage Card to the top level (/) of your phone.
Find the SurrealNetworksAppUnlock.cab file on the Storage Card and run it. It should install like any other application, and you will notice a change to your Home Screen wallpaper.
Using File Explorer again, navigate to the top level (/) of your phone and run SPL.lnk (36 bytes, if this helps you distinguish which file to select). If all goes as expected, you will see a white screen, followed by a message telling you to press the top Volume button to proceed. Do this, and it will flash your new OS to the phone.
I hope I've offered a clear and helpful explanation of this process. Enjoy your now-renascent StarTrek!
Special thanks to Corian for helping me troubleshoot, to #xda-devs, and to all content authors involved here.
Funny, I was planning on re-flashing my 3125 via SD card, but I could not find where I left the instructions. I did it many times a few months ago while trying many ROMs, but I could not recall the exact procedure. Then I come to XDA-Devs to search for the info again and find your post sitting there right on top. Thanks, you saved me lots of time.
I'm currently using Erofich's (pArtizAn's) 6.1 standard ROM as well, but wanted to try out Erofich's PRO version for kicks, and maybe retry GnatGoSplat's clean ROM (I found I'm not using Mobile Office , which the Clean ROM leaves out.)
Ideally, I wish there was a way to install certain WM-Pro only applications on WM-Standard, so that I don't need to change to a touch screen centric OS just for a few applications.
BTW, anyone find and use the HTC Network Setup tool to configure the phone for use with U.S. AT&T service. I want to avoid having to manually set up the data settings.
Freakin awesome, works like a charm, now I can flash my phone with the broken charging/sync port. Many thanks...
Hello. I done all steps of this instruction, but can't flash because the message which invite you to press volume button does not appear...
You should repeat the instructions very carefully. Are you sure your SD card is FAT32-formatted, rather than just FAT (FAT16)?
BHSPitMonkey said:
I've just finished successfully flashing an unofficial WM6.1 ROM to my StarTrek (Cingular 3125) using only a microSD card (no data cable, no ActiveSync, no Windows) and the brilliant work found on this forum. I thought I would share the details of my success in the hopes that it will help the next person who stops by, since I myself found it difficult to find a definitive yes/no on the matter here.
Requirements:
HTC StarTrek
I had the Cingular ROM; Any should work.
microSD card
IMPORTANT: Your card MUST be using FAT32 for this to work. If it is not already so, back up its data and do this now. (Windows will show a FAT16 volume simply as "FAT".)
AppUnlock tool
The one linked at this post is good. http://forum.xda-developers.com/showpost.php?p=1146363
The ROM you wish to flash
I used the WM6.1 Standard ROM posted here by Erofich, since it is most appropriate for a Smartphone such as the StarTrek. You can also use the Professional version, though it is intended for use with a touch screen, so you will have to control a cursor with physical keys.
A computer you can use to extract and place these files onto the microSD card.
After you've obtained the listed files and have them extracted somewhere on your computer, copy the following files to your microSD:
SurrealNetworksAppUnlock.cab (Anywhere)
The entire SSPL directory from your extracted ROM download. (Anywhere)
RUU_signed.nbh, found within the RUU directory of your ROM download. (Rename this to STARIMG.NBH and place it in the top-most level of your microSD card, not inside a folder.)
Insert the microSD into the device (the door is located beneath the SIM card). Using the File Explorer (or Total Commander, if you have it), move or copy the three contents of the SSPL directory from your Storage Card to the top level (/) of your phone.
Find the SurrealNetworksAppUnlock.cab file on the Storage Card and run it. It should install like any other application, and you will notice a change to your Home Screen wallpaper.
Using File Explorer again, navigate to the top level (/) of your phone and run SPL.lnk (36 bytes, if this helps you distinguish which file to select). If all goes as expected, you will see a white screen, followed by a message telling you to press the top Volume button to proceed. Do this, and it will flash your new OS to the phone.
I hope I've offered a clear and helpful explanation of this process. Enjoy your now-renascent StarTrek!
Special thanks to Corian for helping me troubleshoot, to #xda-devs, and to all content authors involved here.
Click to expand...
Click to collapse
Dear sir,
Can it be done for my Dopod S300 using the above same method , mine is a original Dopod S 300 Malaysia Rom , CID is locked ? Please let me know before i try your method , thanks for your help and i wish you best regards ,
[email protected]
jimmunsw said:
Dear sir,
Can it be done for my Dopod S300 using the above same method , mine is a original Dopod S 300 Malaysia Rom , CID is locked ? Please let me know before i try your method , thanks for your help and i wish you best regards ,
[email protected]
Click to expand...
Click to collapse
I actually have no idea; What I've posted here is all the experience I have in this department.
Hope you get it figured out!
P.S.: Erofich has a new ROM posted in this subforum; You should check it out if you plan on flashing.
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'm happy to announce that, thanks to the awesome work done by the wing-linux project, it is now possible to run Android on the Startrek. Well, kind of.
Limitations
As of now, functionality is pretty limited on this hardware. The telephony drivers do work, and they automatically pick up many carriers like AT&T, but the most important apps for placing phone calls (Dialer and Contacts) will crash if you try to run them. This is a known issue related to the phone's lack of a touch screen. Audio playback is unsupported, though I've found that the microphone works during phone calls (which I've placed using commands via SSH). The external LCD only displays white.
Interestingly, Android is about as responsive as Windows Mobile on the device. There is no option (yet) to install the OS permanently; Instead, wing-linux installs to an easily-removable file on your SD card (required).
Instructions
Before you begin, make sure you have about 300MB of free space on the microSD card. (wing-linux requires installing to the microSD at the moment).
UPDATE (Nov. 10 2009)
The new wing-linux 0.4 release includes Startrek support! You can skip the list of instructions below and just install wing-linux normally. See their site for more information.
Download wing-linux (site) and extract it to your computer.
Follow the normal instructions for installing wing-linux, pretending that your phone model is the HTC Elf instead of the Startrek for now.
[*]After wing-linux is installed, browse to your microSD card using your computer and open the folder named "linux".
[*]Download the patched version of zImage, attached to this post.
[*]Replace the "zImage" file in the "linux" folder with the patched version you just downloaded. (This adds support for the Startrek's keypad to Android.)
[*]Open the file named "default.txt" and change the first line, from "set MTYPE 2372" to "set MTYPE 2487". (This tells Android that we're using a Startrek.)
[*]Save everything, place the microSD back into the phone, and start wing-linux again.
[*]After waiting a few minutes, you should have a fully navigable Android desktop!
Button Layout
I have attached a handy button diagram to this post, but the basic ones you need to know are:
Android's "MENU" button is the Startrek's "Home" button.
Android's "Back" button is the Startrek's right softkey (above the Hangup button).
Video Demonstration
Watch it in action at YouTube:
http://www.youtube.com/watch?v=DfTP2DKirUQ
Get Involved
If you're a linux hacker or an Android guru and you think you can help improve this project, come join us at the wing-linux dev forum/IRC!
thx¡*¡*i wait for you a long time¡*¡*¡*¡*
First ,thx.
it can install,and register into andriod .but it doesn't work,even for dialing and SMS
vikinghjf said:
First ,thx.
it can install,and register into andriod .but it doesn't work,even for dialing and SMS
Click to expand...
Click to collapse
Yes, I mentioned that. This isn't a final or polished release; it's just to play around with.
Works pretty good! none of the letter keys seem to work but , i did get the on screen keyboard to come up once but now i don't know what i did to get it to come up. I don't know how to remove widgets from the screen once i add one. Also how do i turn it off and get back to windows? Do i just have to pull the battery? Great job though! i can't wait to see if it will get fully functional!
Buckoni said:
Works pretty good! none of the letter keys seem to work but , i did get the on screen keyboard to come up once but now i don't know what i did to get it to come up. I don't know how to remove widgets from the screen once i add one. Also how do i turn it off and get back to windows? Do i just have to pull the battery? Great job though! i can't wait to see if it will get fully functional!
Click to expand...
Click to collapse
need much time
Buckoni said:
Works pretty good! none of the letter keys seem to work but , i did get the on screen keyboard to come up once but now i don't know what i did to get it to come up. I don't know how to remove widgets from the screen once i add one. Also how do i turn it off and get back to windows? Do i just have to pull the battery? Great job though! i can't wait to see if it will get fully functional!
Click to expand...
Click to collapse
Don't worry, I've observed all of the same things. And yes, I've just been popping off the battery cover to reboot for now.
BHSPitMonkey said:
Download wing-linux (site) and extract it to your computer.
Follow the normal instructions for installing wing-linux, pretending that your phone model is the HTC Elf instead of the Startrek for now.
After wing-linux is installed, browse to your microSD card using your computer and open the folder named "linux".
Download the patched version of zImage, attached to this post.
Replace the "zImage" file in the "linux" folder with the patched version you just downloaded. (This adds support for the Startrek's keypad to Android.)
Open the file named "default.txt" and change the first line, from "set MTYPE 2372" to "set MTYPE 2487". (This tells Android that we're using a Startrek.)
Save everything, place the microSD back into the phone, and start wing-linux again.
After waiting a few minutes, you should have a fully navigable Android desktop!
Click to expand...
Click to collapse
EDITED ... I understand !
Update: Now with less hackery!
The wing-linux project has released version 0.4, with Startrek support built-in. You no longer have to do the special steps outlined in the original post. Hooray!
Does the 0.4 update offer any more function than the last one? I'm downloading right now but, i thought i would ask.
Buckoni said:
Does the 0.4 update offer any more function than the last one? I'm downloading right now but, i thought i would ask.
Click to expand...
Click to collapse
Other than having Startrek support already included, it shouldn't be much different from 0.4pre. I think there is a file manager application, now.
Hi
I install the 0.4 version + startrek cab .
but when i active the icon in start menu , this massage appear :
cannot open script file \storage card\linux\default.txt
i explore this path with pc , and there is no file with this name .
what can i do ? can anybody share the content of default.txt file for me?
please somebody share content of " default.txt " for me .
ceramic said:
Hi
I install the 0.4 version + startrek cab .
but when i active the icon in start menu , this massage appear :
cannot open script file \storage card\linux\default.txt
i explore this path with pc , and there is no file with this name .
what can i do ? can anybody share the content of default.txt file for me?
Click to expand...
Click to collapse
I've the same problem.
I've tried to change default.txt to startup.txt that exist but doesn't work
Jaba
jabawack said:
I've the same problem.
I've tried to change default.txt to startup.txt that exist but doesn't work
Jaba
Click to expand...
Click to collapse
of course it can't be done .
contents of " default.txt " is different .
apparently , we must make the " default.txt " with notepad . but what's it's contents ? maybe a path that guide haaret for booting kernel .
COntent of default.txt
set MTYPE 2487
set KERNEL "zImage"
set INITRD "initramfs.cpio.gz"
set CMDLINE "debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel gsm-wizard.noreset=1 gsm-wizard.noload=1 4"
log "earlylog.txt"
bootlinux
----
Above is the content of the file, though I would suggest you to reinstall the whole cab as I don't have this problem after installation.
ghost_301 said:
set MTYPE 2487
set KERNEL "zImage"
set INITRD "initramfs.cpio.gz"
set CMDLINE "debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel gsm-wizard.noreset=1 gsm-wizard.noload=1 4"
log "earlylog.txt"
bootlinux
----
Above is the content of the file, though I would suggest you to reinstall the whole cab as I don't have this problem after installation.
Click to expand...
Click to collapse
Bingo !!!!!!!!
thanks . now it is installed !
booting is slow ( maybe for first time )
Glad it'd help you. Ya, booting is slow and you have to press red button (end call) when it loaded to a stage with the ANDROID, then you will only greet with the Android logo. Enjoy!
Hi everybody
so cool ! I wish full ability of android was accessible !!
more questions : can wing linux complete development of this project ?
I know some linux developers , can a linux expert remap keyboard or run other parts?
what about other packages like phone , bluetooth ? how we can have complete functionality of android on startrek?
can anybody answer?
MTYPE 2487 in default.txt
doesn't work with qtek 8500, must change to 2372.
With this change I can boot linux, but after setup, run the calibration utility, and startrek isn't a touchscreen device as you know. How can bypass this?
Hello everyone.
I know that there is already a big thread to discuss about Diamond2 clones, but I've decided to create my own thread, only focused on T5388++, to make it clean and organized as I like.
In this thread you'll find all my cooked ROMs. You should be able to get it from my T5388++ 4shared folder! You can bookmark this link. The password to access the folder is XDA-Developers.
Feel free to post your comments. I hope you like it!
EDIT: Don't you forget to donate for all my work. I've made some improvements over the official ROMs and you all know it. A lot of downloads of my ROMs have been made, but only a few people have donated. Remember that I do this in my spare time and a little contribution is highly appreciated.
Just for your information, in less than 2 months, there were more than 100 downloads of V1 ROM.
Available ROMs
Here you can find my custom made T5388++ ROMs. Please be sure to read this carefully in order to avoid unnecessary questions.
Removed from OEM:
*.mui files
ROMs download links:
Please check my 4shared folder link in the the first post.
Version History:
v1
Initial release, based on WM Build 23123 and OEM Drivers from official T5388++ C03.020.01 ROM
Includes HiSilicon Camera v1.1
HTC EzInput v2.1 (Build 2012.2024) and EzInput SIP Menu integrated
Microsoft default keyboard removed
Includes LockDevice to automatically lock the device after screen power off (more info)
WM LockScreen is enabled by default
Includes MortScript v4.3b15
Added a HTC Diamond2 sync icon (created by me) that appears in Windows Mobile Device Center
HTC GSensor SDK integrated (more info)
Disabled Start / OK softkeys and enabled text mode (more info)
v2
Based on WM Build 23144 and OEM Drivers from official T5388i C03.021.08 ROM
Removed HiMMITest and all it's modules
Includes ArcsoftMMS v5.2.8.45
Includes HTC Connection Setup v3.1 (Build 2011.1725) with the latest database for an easy MMS/GPRS network configuration
v3
Based on WM Build 28244 (WMD)
Includes TAN messages fix
Minor cosmetic fixes
P.S.: My ROMs can’t be flashed using the SD flashing method because I have removed IPL, RAMInit, USBLoad and XLDR in order not to flash those parts every time and avoid bricks. You have to use IDT flasher, which for me is the best solution.
* Reserved for future use.
** Reserved for future use.
Finally i uploaded this ROM ... and I'm pleased at first sight.
This man just have done great work. It's fast and clean and with good bonuses! Ultra FAST
I hope that i'll be able to donate few $$ soon.
I have question to the cooker : How can i boost to maximum screen sensitivity ?
The only 1 problem is described below by another good user:
And don't remember to fully charge before you begin
MicAlter said:
BTW what is the latest original ENG ROM?
I've found a list at "3w.htc-topaz.co.cc/files/index.php?dir=ChineseClone_Files" and flashed to S650WM653_20100412_C0302001_english.rar. I think that this may be the latest one, isn't it? Proofed don't know newer. It works on 5388++
Here I go:
Flashed from C03.001.01 ENG to your WM23135-ROM
Result: Restart Loop
[1] Flashing finishes without error
[2] After flashing ROM the device restarts itself
[3] Removed USB Cable
[4] Blue "Touch Diamond 2" is displayed
[5] New animated Windows Mobile Welcome-Screen is displayed
[6] Display goes black and device restarts
[7] goto [4]
Flashed from C03.001.01 ENG to C03.020.01 ENG
Result: Flashing successfull
[1] Flashing finishes without error
[2] WM is working properly
Flashed from C03.020.01 ENG to your WM23135-ROM
Result: Flashing successfull - BUT!!!
[1] Flashing finishes without error
[2] Now WM is starting without restart
Click to expand...
Click to collapse
Thanks a lot!
Thanks a lot bgcngm for all your hard work already so fast. I will try your new ROM next week. Good that you removed the boot firmware so all of us have less chance that the phone will becomes a brick
I would like to see the extendir version if I don't ask too much the Manila2D package for DUAL SIM
Have fun with cooking.
Thank you Eer.
I will work on the Extendir ROM maybe this weekend.
Right now I only wanted to release a normal one so that everyone can install without a problem. I had it running in my T5388++ for 3 days and haven't experienced a single SoD. I'm now starting to believe that the SoD's reported by some users are due to hardware problems... Additionally Wifi, GPS, GSensor, Bluetooth, Phone1/2 are fully working.
bgcngm said:
Thank you Eer.
I'm now starting to believe that the SoD's reported by some users are due to hardware problems...
Click to expand...
Click to collapse
That's NOT true! I had SOD on my T5388++ every day until i have flashed ROM from previous thread!
Well, if you are so sure about that, then you should have no SoD with my V1 ROM either. As I said, I have been running it for 4 days without experiencing any SoD.
First of all, thanks for your work. I think that SOD is a mixture of both, software and hardware, surely these are not all made mobile with the same components, causing problems of instability depending on models depending on hardware. I do not think the solution comes from a magical software, surely that one will be good for another will not.
These are all assumptions clear jejejeje.
I had just installed this ROM.
Common impression: it's VERY fast.
PS:
Today's item "Wireless" is still "squashed"
BIG666 said:
PS:
Today's item "Wireless" is still "squashed"
Click to expand...
Click to collapse
I guess that it will always be squashed. To be honest I haven't tried to fix it because I don't use the old Today anymore. As far as I understand, the plugin doesn't "work" properly with this WM build.
Just for curiosity, why do you enable the old Today screen? Don't you like Titanium?
bgcngm said:
I guess that it will always be squashed. To be honest I haven't tried to fix it because I don't use the old Today anymore. As far as I understand, the plugin doesn't "work" properly with this WM build.
Just for curiosity, why do you enable the old Today screen? Don't you like Titanium?
Click to expand...
Click to collapse
I don't like new WM6.5-Style "Today" (IMHO it suxx). I'd prefer to use more "ascetic" WM6.1-Style, with several items(plugins) on it: Date/Time, Wireless, SPB Weather, SPB Pocket Plus or Resco Today Plugin
bgcngm said:
...
P.S.: This ROM can’t be flashed using the SD flashing method because I have removed IPL, RAMInit, USBLoad and XLDR in order not to flash those parts every time and avoid bricks. You have to use IDT flasher, which for me is the best solution.
Click to expand...
Click to collapse
I flashed it using the SD method, successfully .
(Maybe IDT is better, but all of my machines use Win7 x64... which is not working with IDT. Flashing from Virtual XP under Win7 x64 was not option last time, so I was brave.)
ThoSi, can you tell me how were you able to flash the ROM via SD? When I tried it, I got a message telling that the file size was not correct. My microSD card is formatted as FAT32, but the size (4GB) may be the problem.
I'm also running Win7 x64 in my laptop, so I have to use XP Mode in order to flash via IDT. It fails a lot of times, that's why I choose to remove unneeded parts from the ROM.
bgcngm said:
I'm also running Win7 x64 in my laptop, so I have to use XP Mode in order to flash via IDT. It fails a lot of times, that's why I choose to remove unneeded parts from the ROM.
Click to expand...
Click to collapse
I have Win7x64. I'm using VMware with WinXP to run IDT without any problems.
bgcngm said:
ThoSi, can you tell me how were you able to flash the ROM via SD? When I tried it, I got a message telling that the file size was not correct. My microSD card is formatted as FAT32, but the size (4GB) may be the problem.
I'm also running Win7 x64 in my laptop, so I have to use XP Mode in order to flash via IDT. It fails a lot of times, that's why I choose to remove unneeded parts from the ROM.
Click to expand...
Click to collapse
Kingston micro-SDHC, 4 GB ,FAT32
Phone Off, Turn on with Volume Down button + Power button, then choose yes to upgrade. The ROM was renamed to K3img.bin in the root of SD card.
(I never had error with XP Mode (although sometimes hard to attach USB device to VirtualXP), just i had to lend one of my 2GB RAM, so I have low memory now - not running VXP)
BIG666 said:
I don't like new WM6.5-Style "Today" (IMHO it suxx). I'd prefer to use more "ascetic" WM6.1-Style, with several items(plugins) on it: Date/Time, Wireless, SPB Weather, SPB Pocket Plus or Resco Today Plugin
Click to expand...
Click to collapse
I believe it has nothing to do with this build, it will look 'squashed' on all VGA and WVGA devices? At least, I had the same sort of issues on my Touch HD when using plugin's that did were not specifically programmed to also support VGA.
bgcngm said:
...
v1
Initial release, based on WM Build 23123
Includes HiSilicon Camera v1.1
HTC EzInput v2.1 (Build 2012.2024) and EzInput SIP Menu integrated
Microsoft default keyboard removed
Includes LockDevice to automatically lock the device after screen power off (more info)
WM LockScreen is enabled by default
Includes MortScript v4.3b15
Added a HTC Diamond2 sync icon (created by me) that appears in Windows Mobile Device Center
HTC GSensor SDK integrated (more info)
Disabled Start / OK softkeys and enabled text mode (more info)
Click to expand...
Click to collapse
great job!
Maybe also integrate AAreset? I find Windows Mobile behaves a lot better with a daily scheduled reset (I have it at 06h30). I think it may be a good habit for all WM devices. Dump the exe's in /windows and a link in the system menu.
But why remove MS keyboard? Could you not just make it non-default?
PS: did you not also had MMS integrated before?
I had a bit of improvement with touch screen sensitivity with following adjustments:
I've found this in another thread but dll is the same so.. i think there is kind of
improvement - test and reply
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
Here i added two lines:
"TouchSensitivity"=dword:8 ; Touch screen sensitivity, max sens. = 1,
min sens. = 63 - of course 1
"PressureFilter"=dword:0 ; 0 - disable Pressure Treshold Filter, 1 -
enable Pressure Treshold Filter - of course 0
I didn't tested other values as long as i sensed improvement, you could.
I also checked this:
HKLM\system\GWE\touch\filter and change the value to 0. Wait 25sec and restart.