Related
2/3/09 Update
I have updated the pocket freeware program with the help & permission of the Freewarepocketpc.net site.
I am looking for 1) feedback & suggestions, 2) testers, 3) B4PPC developers to help out - I want this to be a program that is useful and maybe even be something that could turn into an "App Store" someday (limited to what freewarepocketpc.net, of course)
[Description]
I've started another project over at Basic4PPC - this is called "Pocket Freeware" The goal was to create a client that would let you scroll through the software titles at Freewarepocketpc.net and install them directly onto your PDA.
Project url: http://www.basic4ppc.com/forum/open-source-projects/3487-freewarepocketpc-net-client.html
Released under the GNU General Public License
Current version: D.13 (developer's release)
Install instructions: unzip & copy to PDA. Program will create any directories and files that it needs. (this is a developer's build. future public releases will have a cab)
Attached: PC and Pocket versions (zip)
Features
1. View applications by New, or by category (edit categories.txt file to customize what categories you want)
2. View application detail - if app was installed by "Pocket Freeware" it will have checkmark and show both installed date and latest available date.
3. Download & install
4. Pocket PC and PC versions
Future or still in development
1. View list of what has been installed from freewarepocketpc.net with this app (and check for updates!)
2. Landscape mode (not implemented due to my laziness and focus on features)
3. View listings on freewarepocketpc.net's shareware site
4. More robust downloading (working with site owner)
5. Save settings (currently hard coded, some you can change during run-time)
6. Clean-up details page (artistic, I am not)
7. Your feature here?
Instructions & hints
1. Checking an unchecked box in the details page will download and install the app
2. Clicking on the image in the details page will enlarge the image. Click on image again to minimize.
3. Little "X" in right hand corner of details page will close the details & return to listing
4. Double click (or press enter on dpad) to select application to view details. I may add the detail launch on the main page image in a future release
Sounds like a great idea.
Hey, I was trying to download this program. What has happened to it digitaldon37?
knownboyofno said:
Hey, I was trying to download this program. What has happened to it digitaldon37?
Click to expand...
Click to collapse
The owner of the PocketFreeware site had some concerns with it, so I decided not to continue it. However I have been trading e-mails with them so something may come out of it.
I have a screen shot posted on my wiki: campusbbs.freehostia.com
Yea, I saw that... too bad cuz I flash from time to time and don't have a back of a file. Anyway thanks for the info.
New Developer's Release .12 - complete rewrite
2/3/09 Update
I have updated the pocket freeware program with the help & permission of the Freewarepocketpc.net site.
I am looking for 1) feedback & suggestions, 2) testers, 3) B4PPC developers to help out - I want this to be a program that is useful and maybe even be something that could turn into an "App Store" someday (limited to what freewarepocketpc.net, of course)
See main post for details.
The PC version works ok; the ppc one, instead, not: the upper part (where in pc there is the app list) is blank, and i can only see the description of the first item (as now PockeTwit) and its image. Nothing else. The lower part (WVGA-VGA) is also blank.
Device: HTC Touch HD, rom 1.13 ITA
bbonzz said:
The PC version works ok; the ppc one, instead, not: the upper part (where in pc there is the app list) is blank, and i can only see the description of the first item (as now PockeTwit) and its image. Nothing else. The lower part (WVGA-VGA) is also blank.
Device: HTC Touch HD, rom 1.13 ITA
Click to expand...
Click to collapse
Thanks. I'm using an external library for some of the controls (ie the listbox that doesn't show on your pda) and thought they would size properly.
The HTC Touch HD has a screen size of 480x800 - I'll check the code to make sure it handles this.
UPDATE: I made some changes on how controls are sized and tested this in the 240x320, 240x400, 480x640, and 480x800 emulators. They seem to be working correctly now.
Pulled the links again? All I see on the basic4ppc thread appears to be source code? and no link to anything here either. Dead project?
lotherius said:
Pulled the links again? All I see on the basic4ppc thread appears to be source code? and no link to anything here either. Dead project?
Click to expand...
Click to collapse
Joel2009 has taken the source code and started a new project thread: http://forum.xda-developers.com/showthread.php?t=513503
>> Please note that there is now a newer version derived from this ROM available.
This original one may still meet users' needs if you do not require the additional features which have been included in the more recent edition. <<
Here is a new custom but relatively ‘clean’ WM6.5 UK-oriented ROM based on the current Toshiba / Orange release (TG01WP_5005000167.tsw). Original build CE OS 5.2.21876 (Build 21876.5.0.72).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contains:
Style:
Win 7 style opening Splashscreen optimised to the TG01
Win Phone style animated Shutdown splashscreen
Colour Icon Taskbar with Windows 7 Orb [Based on GFreek’s with many own amendments and new icons]
Classic Blue Theme
System:
Custom Start Menu structure and Folder Icons
Power Off shortcut
.net Framework 3.5 [Based on Arag0n85’s implementation in the original debranded ROM]
Audio Test (5.1 channel identifier)
Preset Registry Settings / Tweaks
- Power
- ClearType
- UK Regional
- SIP
- Wireless G active
Apps:
MS Office Mobile 2010
Google Maps
Arcsoft PhotoBase
Pictures & Videos
Camera with Muted Shutter Sound [To turn off Shutter completely use Novembre5’s .cab]
Video Editor
Windows Media Player
Games: Bubblebreaker, Solitaire
Memory:
Storage: In Use – 38 MB Free – 224 MB
Programe: In Use – 118 MB Free – 87 MB
Removed:
Orange everything
Video Player
Toshiba ‘Blinds’ UI
All remaining MS Themes [All available to install to taste if desired]
MSN Money, Weather Widgets [Available here: View attachment Money.zip, View attachment Weather.zip]
Acknowledgements:
Cedesmith for the development of TGTool, without which this and every other ROM would not be possible.
arag0n85 for great patience as I learned to take baby steps and began to understand.
Farmer Ted for giving the key to unscrambling Start Menus.
GFreek for the original colour Taskbars from which this version is derived.
adzman808 for helpful injections of common sense.
virgilp for the original app behind the Screen Off function
TinTin for the original app behind the Standby and Soft Reset functions
Installation:
1. Download and unzip the ROM below
2. Copy SDDL+ to the root of your uSD Card
3. Create a directory \prg on the uSD Card
4. Copy the ROM .tsw file to uSDCard\prg
5. Run Sddl+ from \Storage Card
6. Further information is available here.
=================================================================
20 Jul - Update on GPS Lock
Along with some user reports, I have also had the GPS lock and then drop after 30 seconds. I now believe that the A-GPS is the issue. Possibly dependent on the server address you put in. I am now running with A-GPS deactivated (a simple registry setting) and find that the normal GPS works beautifully.
Please run the attached AGPS_Off.cab which will change your AGPS FixMode to 0 instead of 2. Or if you wish to just edit the registry, it is:
Code:
HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOneDevice
RegDword=0
To reverse, simply change back to '2' with a suitable registry editor.
Start Menu | Settings | Screen Calibration Icon
Has been identified as missing (stock WM icon shows instead). To rectify, please download the attached file and simply copy to the \windows directory. After a soft reset it will then display correctly. This will be changed permanently in a future ROM update.
Updated Version available at 9 July10:
UK / Europe
TG01_KPW100707.005.tsw Radio Version 5001.0300.76
Chinese / Far East
TG01_KPW100707.005.tsw Radio Version 5005.1600.05
Changes
- Added custom Power control section to Start menu incorporating:
o Power Off, Soft Reset, Standby, Screen Light Off
o Power Settings control panel access
o Hidden Hard Reset (area below the Power Settings icon)
- Reworked some StartMenu Folder icons
- Rebuilt MMS application (corrupt .dll) and inserted new Taskbar icons
- Deleted some further unnecessary files from the image
- Fully tested GPS operation following problems with withdrawn issue 100704.003
GPS Notes
This build has now been tested simultaneously on three separate TG01s using Eficasoft GPS Utilities, Garmin Mobile XTand also Google Maps. It is noted to exhibit certain eccentric behaviours, but these are considered due to the interface between the navigation applications build and not this particular ROM edition.
- Individual TG01s may have slightly different GPS receiver sensitivities. One of my devices is noticeably quicker and more consistent at attaining and sustaining a lock with Garmin XT. However, using GPS Utilities, all of them show very similar charactaristics.
- I have used the following Settings:
o Settings | External GPS | GPS Program Port : GPD9, Hardware : (None), Access [Check] Manage GPS automatically
o Garmin XT - Use GPS Intermediate Driver
o Google Maps - Menu | Options | GPS Settings | My Location Settings [Check] Managed by Windows. Also Menu | Options | Use GPS [Check]
o NB. Google Maps and Garmin XT will run concurrently, but only if Google Maps is started first. In this case there is no requirement for GPS Gate or other intermediate application. This may however be needed for other navigation software. I have not tested with TomTom, iGo or any other applications.
- It is important to give the device an initial Location – the A-GPS can help here if you have a data connection active; also can be manually set in the navigation software. This may significantly shorten acquisition time.
- Solidity of initial lock seems to be important. If booted or soft reset in the car with a re-radiating antenna active (ie. Excellent signal) and allowed to sit for a few minutes, the satellite bars progressively get bigger after a while. This also seems to result in a stronger and more resilient lock and subsequent re-acquisition behaviour.
- If then moved indoors, I have then been able to sustain a lock well inside the house, both up and downstairs, including well away from windows. This is noticeably better at night than during daytime; probably something to do with the relative position of satellites and time of day.
- The sustained lock can be maintained for long periods (six or seven hours) without any break. Re-acquisition following a break seems to be prompt. Resumption of service from ‘Standby’ device state seems to be similarly quick.
- After initial flash of the ROM, I found one TG01 instantly responded and acquired (indoors !), one took a few soft resets followed by the in-car high signal density scenario above and the third was more difficult – I ended up re-flashing the ROM and then a couple of S/Rs and the car treatment. But now all three seem to be running successfully and consistently. In case of dropping out and not appearing to want to re-acquire, the best advice seems to be do a Soft Reset, preferably in a high signal-strength environment.
Updated Version available at 18 Jun 10:
TG01_KPW100618.005.tsw
Changes:
- Added animated Windows 7 Boot sequence; fully reworked and optimised for TG01
- Added discreet ‘quiet’ Windows 7 Boot sound (-18dB from standard)
- Deleted some further unnecessary files from the image
Updated Version available at 11 Jun 10:
TG01_KPW100611.002.tsw
Fixed:
- Several Start Menu icons not displayed correctly
- Start_Settings icon replaced
- Battery % Registry fix applied
Superceded:
TG01_KPW100606.007.tsw
cool. i wait to download link
Installation:
1. Download and unzip the ROM below
2. Copy SDDL+ to the root of your uSD Card
3. Create a directory \(png) on the uSD Card ----------- prg ?
4. Copy the ROM .tsw file to uSDCard\(png) ----------- prg ?
5. Run Sddl+ from \Storage Card
6. Further information is available here.
eddgarms said:
Installation:
1. Download and unzip the ROM below
2. Copy SDDL+ to the root of your uSD Card
3. Create a directory \(png) on the uSD Card ----------- prg ?
4. Copy the ROM .tsw file to uSDCard\(png) ----------- prg ?
5. Run Sddl+ from \Storage Card
6. Further information is available here.
Click to expand...
Click to collapse
Many thanks for flagging the typo - now corrected
detail
Please add to thread's title radio version...
Thx
kevinpwhite said:
Here is a new custom but relatively ‘clean’ WM6.5 UK-oriented ROM based on the current Toshiba / Orange release (TG01WP_5005000167.tsw).
Contains:
Style:
Win 7 style opening Splashscreen
Win Phone style animated Shutdown splashscreen
Colour Icon Taskbar with Windows 7 Orb [Based on GFreek’s with various own amendments]
Classic Blue Theme
System:
Custom Start Menu structure and Folder Icons
Power Off shortcut
.net Framework 3.5 [Based on Arag0n85’s implementation in the original debranded ROM]
Audio Test (5.1 channel identifier)
Preset Registry Settings / Tweaks
Power
ClearType
UK Regional
SIP
Wireless G active
Apps:
MS Office Mobile 2010
Google Maps
Arcsoft PhotoBase
Pictures & Videos
Camera with Muted Shutter Sound [To turn off Shutter completely use Novembre5’s .cab]
Video Editor
Windows Media Player
Games: Bubblebreaker, Solitaire
Memory:
Storage: In Use – 38 MB Free – 224 MB
Programe: In Use – 118 MB Free – 87 MB
Removed:
Orange everything
Video Player
Toshiba ‘Blinds’ UI
All remaining MS Themes [All available to install to taste if desired]
MSN Money, Weather Widgets [Available here: View attachment 338389, View attachment 338390]
Acknowledgements:
Cedesmith for the development of TGTool, without which this and every other ROM would not be possible.
arag0n85 for great patience as I learned to take baby steps and began to understand.
Farmer Ted for giving the key to unscrambling Start Menus.
GFreek for the original colour Taskbars from which this version is derived.
adzman808 for helpful injections of common sense.
Installation:
1. Download and unzip the ROM below
2. Copy SDDL+ to the root of your uSD Card
3. Create a directory \prg on the uSD Card
4. Copy the ROM .tsw file to uSDCard\prg
5. Run Sddl+ from \Storage Card
6. Further information is available here.
[URL="http://www.megaupload.com/?d=TW7AFKQ0"]TG01_KPW100606.007.tsw[/URL]
Link and Download test Flashed and confirmed OK.[/Q
well done kevinpwhite,
i have downloaded the rom and installed it, it looks good so far , i will test over the next day or so then comment again. so far so good
Click to expand...
Click to collapse
bib*oops said:
Please add to thread's title radio version...
Thx
Click to expand...
Click to collapse
Done - it is the Italian Radio / front end.
kevinpwhite said:
Done - it is the Italian Radio / front end.
Click to expand...
Click to collapse
Thank you very much, sir!
Which version of 6.5 is this, 6.5.3 or 6.5.5?
TONYKENT said:
Which version of 6.5 is this, 6.5.3 or 6.5.5?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Windows_Mobile#Windows_Mobile_6.5
sorry, but that does not tell me if this rom is 6.5, 6.5.3 or 6.5.5 (start button at the bottom)!
I am speechless
It's Beauuuutiful!!
Me like it very much.
Keep the good work.
By the way anybody know how to have titanium scroll endlessly (might be a patent infringement??) as well the start menu?
TONYKENT said:
sorry, but that does not tell me if this rom is 6.5, 6.5.3 or 6.5.5 (start button at the bottom)!
Click to expand...
Click to collapse
[ROM][UK_ENG] ROM WM6.5 TG01_KPW - Radio Version 5001.0300.76
So it's a 6.5 rom with start on TOP (like official rom)
Thanks for the claification. Kevin, it appears that you have basically used the stock uk rom and tidied it up. What would be useful is to produce a 6.5.5 rom with the uk radio since this appears to be more reliable in terms of signal....by the way I am a Londoner!
TONYKENT said:
Thanks for the claification. Kevin, it appears that you have basically used the stock uk rom and tidied it up. What would be useful is to produce a 6.5.5 rom with the uk radio since this appears to be more reliable in terms of signal....by the way I am a Londoner!
Click to expand...
Click to collapse
Tony,
It is a hybrid of the stock UK and IT WM6.5 ROMs extensively 'cleaned' and with the various refinements mentioned in the original post. If you are after a WM6.5.x edition with a different radio it is quite a simple step to take one of the various fully 'cooked' offerings and splice together with the IT Radio. If you ask the original chef they may well be happy to provide, or you could try doing yourself - it is a good first step to learning how everything fits together !
Thanks Kevin, would you be able to make a 6.5.5 rom?
TONYKENT said:
Thanks Kevin, would you be able to make a 6.5.5 rom?
Click to expand...
Click to collapse
Tony, I'd suggest you try one of the already cooked WM6.5.5 ROMs - there are several available. Full details have been summarised by @Pere in this post.
Thanks Kevin, I am using Novembre's new clean rom but noone has combined a 6.5.5 rom with the current uk radio.
i thought he had already....?
Is the ROM you want not this one? Or am i getting confused between radio versions?!!
http://forum.xda-developers.com/showthread.php?t=693892
Download English:With StartUp and Shutdown Animation
Release 1 Clean Dynamic PagePool Radio 5005.1700.05 06/08/2010
Click HERE to download
Release 1 Clean Dynamic PagePool Radio 5005.1600.05 06/08/2010
Sadly no...
The 1600.05 radio is a foreign version. I am trying Novembre5's new 1600 instead of 1700.
The newest UK radio is Radio Version 5001.0300.76
Puzzled with all the buzzwords and your head is spinning?
Still want to learn a little about the strange world of Chefs and cooking?
Even are tempted to ask some questions but have not dared yet with all the geeks around here?
Here is a little nutshell-guide for you to lift you up:
The windows mobile operating system is composed of several parts (and this in several regards not always aligning) and it is helpful to understand the basic architecture to evaluate your problem against that.
This is not a detailed guide, it will not link to any sophisticated tools and it will not solve your problems right away. I just try to supply a little nutshell approach (simplifying some things - don't flame me for this if you know better) to put things in the right order.
After reading (and understanding) you are hopefully enabled to search for the right answers in the vast pool of wisdom around the web. You should also be able to tell apart the tales from the facts (on some level at least) and - if you need - ask the right questions and not immediately be ignored as a noob.
You see below a map that allows you to locate the various terms to the right places.
I will then elaborate a little on each of these in hierarchical order.
Code:
ROM file (usually packed into an update service pack containing also the update SW)
Parts:
- IPL
- SPL
- OS
partitions:
- USPL
- XIP
- Generic(MS) and OEM parts -> XIP porting
- packages (*.dsm + *.rgu)
- files and modules
- IMGFS
- Generic(MS) and OEM parts -> the usual ROM Cooking is here
- packages (*.dsm + *.rgu)
- files and modules
- languages
- T9
- *.mui.*
- *.provxml + lang_db
- ExtROM
- GSM/Radio
- Boot-Splash
ROM parts and Partitions:
Let us first look at the flash memory of the device. This is handled from the SPL (secondary program loader) during boot (passing control to the OS) and flashing where the different parts that are present in a ROM file will be written to the places of flash memory of the device.
The well known parts of a flash ROM are:
the IPL (Initial Program loader),
the SPL (secondary Program Loader) - a powerful on-board pre-OS program that is the gate-keeper for all further actions
the OS (Operating System),
the Radio (GSM),
the initial boot-splash
and others like ExtROM which is just a FAT partition for storing post-first-boot configuration and installation programs - depending on the device.
There are some more parts in the device memory for security reasons that hold the IMEI, SIM-Lock data and possibly other data that can be used for forensic analysis.
Shipped (vendor or operator original) ROMs usually contain ALL parts of a ROM so that you do not depend on a previous ROM to get a usable device.
Interesting for cooking is only the OS part of the ROM.
This holds ALL parts that make the difference between the windows mobile OS versions. Some cooks have added their own splash screens as ROM parts (additional to the ones that are displayed when to OS boots later), for some ROM flashing it is also required to replace the SPL (temporary or permanently) allowing the flash of non-signed ROMs or at least make it believe that you are allowed to do that (Super-CID).
Sometimes it is useful to step up to the latest Radio version to exploit features that this offers.
But again: Cooking is only about the "OS" part of the ROM! Only the OS part is usually replaced by flashing new cooked ROMs.
This OS part is structured into "partitions". So you can look at the OS part as something like a hard-disk in your PC that can also have partitions with different file-systems serving different purposes. For the OS part of the ROM the sequence of partitions is the
ULDR (look that up yourself) which is usually not needed and can often be removed or minimized,
then the XIP (historically "eXecute In Place")
then the IMGFS (Image file-system)
and some additional partition, e.g. for the ExtROM.
XIP and IMGFS make up the Windows Mobile OS and are subject to "cooking".
XIP and IMGFS:
In the boot process the SPL passes control to the nk.exe (Native Kernel) in the XIP and it will load the early drivers and services that allow to reach a certain minimal OS service level to access the IMGFS for further boot.
The IMGFS itself holds all the rest of files and modules to start the OS to that level where the user can use it.
OEM and the rest:
The HW of most mobile devices is special in one or the other way. Dedicated drivers are needed to abstract the HW dependent parts to a level that the Operating system can interface with them in a standardized way. All these are summarized under "OEM parts" (Original Equipment Manufacturer) while all other parts are from Microsoft and are supplied in a generic way.
You can suspect that all OEM parts have to be compiled taking the HW specifics into account, while the generic parts can be taken as is (binary) and both will be assembled to a final ROM production.
This separation of OEM and "the rest" makes "cooking" and "porting" possible at all. If this architecture was not designed by Microsoft, then there was no cooking in the kitchen
OEM parts stay usually unchanged through all cooking and porting activities, so that also means that a WM5 device will keep all the OEM parts even if the OS version is WM6.5. OEM parts are in both, the XIP (nk.exe and some OEM modules) and the IMGFS. You will especially not gain any advantage of the enhanced memory allocation scheme if your device does not have a native 6.5 kernel (nk.exe).
OEM may also add applications to their devices that exploit special HW options of the device (e.g. the camera application) or that are the result of an effort to make their devices unique (like HTC's Homescreen).
Kitchen separate on top-level into SYS and OEM folders but the allocation of packages (see own chapter) to either one or the other is not uniform. Some add the OEM drivers (i.e. the true HW dependent parts) in the SYS folder, others (newer) kitchen put them also under the OEM top-level.
Packages and ROM Protection:
To keep the various parts of a ROM well organized, Microsoft has created an environment that allows to produce ROMs in an easy way. This is not accessible to us ROM hackers, but the remains of the packaging tools in the ready assembled original ROMs have inspired many hackers and chefs to utilise the same methods.
They created tools to de-compose original ROMs and also to use the same methods for creating new ROMs. Over time these tools have become very sophisticated and may even offer more options than original MS tools (I guess). As all this is a shared activity with many contributors, it is important (in my view) to keep sharing what you discover.
In original ROMs you find many files like <some-strange-number-letter-combo>.rgu and also <*>.dsm. These are the remains of the packaging process that has created the ROM. They are NOT needed on the device itself! However have those files allowed to understand the process of building a ROM.
These <some-strange-number-letter-combo> elements are called GUID (Globally Unique Identifier) and are identifying packages. The DSM (Device Side Manifest) file identifies all components of a package (their name, status, properties, size, build properties and much more) while the RGU (Registry Update?) file identifies the changes that are made to the standard registry hive for that package.
So ultimately one method of ROM "protection" that some kitchen offer and that some chefs are using is to remove all the *.dsm and *.rgu files before they build the IMGFS. The resulting ROMs still have all files that are needed for the ROM to run, but they cannot be decomposed to packages (the .dsm files are missing) again and during re-build the *.rgu files are missing to update a standard hive file (e.g. of a new base ROM from MS).
Files and Modules:
Logically the smallest parts are files, which is common to all operating systems. There is one specialty however in the WM-OS and this is so called "modules".
They are basically memory-fix located executable files which can be loaded faster than normal executable files. As their memory location is fixed in the production process, all those modules must not overlap their memory. The process of realigning a new set of modules to the available memory locations is called "re-location" or "re-allocation". Tools like mreloc, G'reloc, wmreloc, extreloc or within OSBuilder take care about this in the production process.
You recognize modules that they are folders in the kitchen with the name of the module and some files inside that make up their content. These modules later "look like" files in the \windows folder of your device but they are still modules which are just hidden from your visibility by the filesystem presenting the data to you.
Even worse for easy understanding is that you seem to be able to "overwrite" such files on your device later, but you do not actually overwrite them. You create a file with the same name in the FATFS that is linked to the IMGFS where the ROM is stored. The copied file takes precedence over the original one in ROM. This works for many files in ROM, but NOT for those who are loaded before the FATFS is active (e.g. after cold-boot the FATFS is empty or during early boot-phase when the XIP partition is loaded).
Languages in a ROM:
While it was usual in older times to have multi-language ROMs, this habit seems to vanish with newer devices and several vendors produce country specific ROMs only. However does Windows Mobile offer all options to have many languages present in a ROM. The places that need adjustment are multi-fold, however only some need real attention usually.
Luckily the country specific details of time/date/number/currency and alike are stored in a common database and are present in all devices no matter which user interface they have (afaik the nls file). Also the naming of the settings options (e.g. "Short Date Format") are present in all languages already. There is no need to adjust this usually.
The text entry system (T9 or its successors) is handled by a dedicated package and new languages can be added quite easily. The languages here are independent of the language settings for the UI, so you can have a device with only WWE (World Wide English) on the GUI but still have your local language supported e.g. for sending text messages. Mind that usually all language databases must be of the same (matching the T9 executables) version to work properly. You cannot pick an arbitrary language file from another T9 enabled device.
The programs or dll that are constructed to support multiple languages have in many cases <program/dll-name>.mui.<nnnn>.* files where the "mui" indicates "multilingual user interface" and the <nnnn> the relevant 4 digit number of your language (0409 is US English, 0407 is German and so on..). Usually there are dedicated packages in a ROM that supply all necessary changes to the registry so that this language is supported when you switch to it in the regional settings.
Applications that a chef has added to a ROM may need separate methods to add a language, most are not having an automated approach or are only supporting their own native language. You could still work on the binary file directly, either in a structured approach by de-composing the executable into its resources (e.g. with resource hacker) and add/change strings there or even directly hex-editing the file itself. Mind that you MUST NOT insert or delete any byte - you must OVERWRITE existing strings only. You also have to take care that on a smartphone with certificate security switched on you must remove the existing certificate (if any) and re-sign the file again.
The settings themselves are a special system of menus (*.cpl.xml) on a smartphone that manipulate registry data or other values of the device. For that purpose the settings are using the already existing "Service Provisioning" method that can as well be used via WAP or with other means.
To make that provisioning in some way a little user-friendly, there is a process to define names and options for changing such data - finally they are stored in a database on the device.
Now when you call the settings menu, the system reads the elements that shall be changed and also the linked information (label, limits, representation) from that database to present this on the screen.
So if you like to have more parameters in the settings menus or if you want to make your own panels for settings or tweaks, then you have to deal with adding your information to that database.
This is done with *.provxml files. These files are treated on the device (so not during cooking where the *.dsm and *.rgu files are used) and they are handled on different occasions (first/cold boot, sometimes also on other occasions). This is also why a "first boot" of a ROM is taking much longer then subsequent boots. So if you want to find out which additional settings-options are in your ROM, parse all *.provxml files for your country string (you remember "0409"?) and add relevant parts for the language you want to add.
This is tricky though: the files are stored in UTF-8 format without the UTF-8 header. If you save them in the wrong encoding they will not work any longer! I use the free notepad++ editor (http://notepad-plus-plus.org/) that handles them well.
The final part in this story are the settings panels themselves (usuall in the OEMMISC folder: *.cpl.xml). Also here some labels are defined in a language specific way - just add what you need per language following the obvious pattern that is given in the files already.
[*]Now that I see the above, I noticed that the smartphone homescreen is also an XML file - so also there the labels and options can be set in a language specific way. Look up the *.home.xml files if the language you want to deal with is present in these files. Usually the MS defined homescreens have very many languages already inside, so you may not need to change anything here. As mostly nobody cares about smartphones any longer and even less about old-style homescreens - this may have no need to be mentioned.
[*][added 2012 02 24]: Hardly documented (but widely used) and very useful is that the registry supplies an automatic NLS dependent branching of values. So if you have a value like HKxy\path1\path2\myvalue and you want to have two different data for it, each depending on the selection of the active interface language, then supply the value like:
HKxy\path1\path2\0409\myvalue=<English string>
Example (from SYS\Base_Lang_nn):
[HKEY_LOCAL_MACHINE\Comm\EAP\Extension\13\0409]
"FriendlyName"="Smart Card or Certificate"
HKxy\path1\path2\0407\myvalue=<German string>
Example (from SYS\Base_Lang_nn):
[HKEY_LOCAL_MACHINE\Comm\EAP\Extension\13\0407]
"FriendlyName"="Smartcard oder Sicherheitszertifikat"
Note that specialty cannot be seen when you access the registry with standard means (so via the device itself) later on anymore. You will just see the registry path of the current selected interface language. Tools that can read the created hives directly will show them.
Bottomline for dealing with languages:
know the number for your language and the one that is in a ROM
care for T9 libraries and make sure to use all of the same version
find the version matching *.mui.* files for the language to add
search all kinds of XML files (*.provxml, *.cpl.xml, *.home.xml) for the language number and make your changes
inspect the *.rgu of the language dependent packages and see if all items are set properly. Be inspired and create your own language dependent registry values.
When you move ahead in your strive to cook your own ROMs, you will notice that old style (batch file) kitchen give you control over what happens when as you are calling the dedicated tools for certain jobs directly.
Newer Kitchen have assimilated all work-flows in their own GUI, some still needing the tools that also the batch file kitchen use.
The latest breed of kitchen has most tasks built in. So you are completely left with the style that the master of that kitchen has implemented his understanding of work-flow logic. Sometimes it is hard to understand what belongs where (for a noob that you may be reading until here - it is hopeless anyway) - but as long as you understand the architecture you can have your own mind-map and put things together on your own.
If you like and have some old devices to play with, why not give it a start with any of my 3 kitchen for the good old Candy Bar smartphones which HTC had created?
WM65 (English/German) OS Builder Kitchen + ROMs for Typhoon based on Aleut's WM65 ROM
OS Builder Kitchen for Hurricane: WM6, WM6.1 and WM6.5 English + German
OS Builder Kitchen for Tornado: WM6, WM6.1 and WM6.5 English + German
You need to fix some battery stuff related to these old gems, look here:
[now without battery ] Replace Backup Battery in Tornado, Hurricane or Typhoon
mind that the cooked ROM from the kitchen above already contain the "without battery" part.
Measure and compare your battery capacity - easy, foolproof, comparable - any WM dev
If you like this tutorial and it has given you some more insight, please push the "Thanks" button at the bottom.
Nice post mate, this his all foundation in a nutshell-guide .
Thanks.
I agree, nice tut. No doubt, it will help many people!
I'be been reading all, wow, so detailed.
Nice job indeed, thank you.
Grtz,
Laurentius26
Great work. Simple and precise
added language dependent registry branches
Not many left who wish to cook anymore, so just to complete the language dependent items in my original post.
Hardly documented (but widely used) and very useful is that the registry supplies an automatic NLS dependent "branching" of values. So if you have a value like HKxy\path1\path2\myvalue and you want to have two different data for it, each depending on the selection of the active interface language, then supply the values like:
HKxy\path1\path2\0409\myvalue=<English string>
Example (from SYS\Base_Lang_nn):
[HKEY_LOCAL_MACHINE\Comm\EAP\Extension\13\0409]
"FriendlyName"="Smart Card or Certificate"
HKxy\path1\path2\0407\myvalue=<German string>
Example (from SYS\Base_Lang_nn):
[HKEY_LOCAL_MACHINE\Comm\EAP\Extension\13\0407]
"FriendlyName"="Smartcard oder Sicherheitszertifikat"
Note that specialty cannot be seen when you access the registry with standard means (so via the device itself) later on anymore. You will just see the registry path of the current selected interface language. Tools that can read the created hives directly will show them.
Final update: (diff from 20120408):
cleaned up some resource files (saving quite some space)
added icons to those which had none
made provxml tracing the same for all
added some small games (these eat the saved space from above)
added an option panel to setup the volume of VoiceTag (from my other kitchen)
made D3Demo an extra package
added the very latest NetCF 3.5 as modules in an own package
added a few more color schemes and backgrounds
patched the keyboard driver to not require a dedicated subdirectory "Keys" in \windows
patched the nk.exe to identify itself as "TYPH100" to allow better skin selection for remote access tools
renamed mtty to the correct name (was mmty.exe)
fixed the welcome.exe for the German Mui to correctly delete the welcome.lnk from autostart at first boot.
removed the _cabs folder form the kitchen. Get it from an older kitchen
Updated 2012 04 08: A new update to the kitchen folder. The older OS Builder stuff is moved to a dedicated subfolder. Now SDHC cards are supported and a later version of USBFN is bundled only with WM5torage (not recommended on Typhoon).
Updated: 2012 01 15: The old batch kitchen is moved to a dedicated folder in the Mediafire share. You find now a much improved OS Builder (see post 3) Kitchen as well as a set of ready-to-use builds to download. I have also updated the list of included programs below.
Here it is finally - another port of the batch kitchen I had once taken from Nitrogen for the Tornado and ported to Hurricane already - the simple kitchen for the Typhoon/Feeler/Amadeus.
The default settings were cooked to a ROM already, so you may want to try that first before you cook yourself (which is very easy, even for noobs).
It is completely localized for German keeping the English from Aleut's original WM65 ROM. He already had published a kitchen for that device here at XDA, however only as a side-note in an existing thread asking for WM65.
I have updated some applications to the last available version, added some OEM packages from the Tornado kitchen and merged some from the Ginza MS100 kitchen - also a device with QQVGA and a WM65 kitchen.
As this device has a limited ROM size of 27MB (x'1b00000), the tweaking of size and available applications was a major activity. All changes done to the original files are left in a separate folder in the kitchen.
The default settings for cooking are containing the following applications:
20MB base package (all options off in OSBuilder), leaving 7MB of additional ingredients to push in, my choice for you:
.NET CF 3.5 already on-board
T9 English and German
WM6.5 Menus (skinned) (selectable in the kitchen, not in builds anymore)
full Media Support:
Arcsoft MMS 3.5.2.15C
HTC Camera (as it always was)
Media Codecs (common filetypes, also midi works as ringtones)
Cyberon Voice Dial
WM-player supports the additional keys for the Amadeus (SDA Music)
More Entertainment:
Kevtris 2.0, a great Tetris clone with nice additional options (sliders, weird blocks etc.) - keeps your joystick busy. (*)
several Bluetooth profiles (updated from S740 aka Rose):
Bluetooth SAP (Sim Access Profile)
Bluetooth FTP Client (HTC BT Explorer)
Bluetooth A2DP included (with settings) but it only works on lowest quality due to HW limitations (removed now)
GPS Intermediate drivers (from WM5&6) including setup program. This allows to share one BT GPS receiver for several applications at the same time.
HTC Comm Manager. This allows to set the Radio really OFF if you have no or no valid SIM Card. After 3 minutes the radio gets back on otherwise even if shut off with MS-wrlsmgr. Once after 3 minutes off-time it stays off even after reboot. [Edit 20120324:] It is not necessary to have HTC CommManager do this - the normal MSWrlsmgr can do the same, provided that you do not leave it with "done" but keep it running for these 3 minutes in background.
Many other tools:
Total Commander 2.5ß3 (*)
WM5torage 1.9 [Edit 20120324:] The usbfn.dll which can handle the WM5torage driver is creating problems with parallel Music Playback and any USB connection (also AS via RNDIS or Serial) It seems that some I/O ports are used the same. You better avoid using that when cooking.
maniac's Autokeylock
MortScript 4.2 (*)
Easter Uninstaller (*)
Oxios Memory
Vito Copy/Paste
FEADIE (managing file extension for Internet Explorer) (*)
Modaco NoData
Clear Type Power Toy (adjust the Gamma for CT)
Mobile Config: an XML based registry tweaker (only in the kitchen)
Caller Location core (vibrate on connect)
Multi Flashlight
Safe Inbox Extender
* (in the non sliding panels build only)
The pagepool used is now 4MB to give a suitable performance (was only 2MB in previous setup - very slow). However you can adjust this with tools included in the kitchen if you want to change it. ROM size and Storage is fixed on the device, so you have 27.97 MB total storage and free are 24.64. Mind that packages you save from the ROM are not giving you gain in storage space, so keep the ROM filled to the 27MB with what you consider useful.
RAM is tight here anyway, best gain is if you don't use the sliding homescreen and disable the Camera Driver.
I have also added some options regarding key definition to the Tweaks settings. This allows to select the keyboard driver for Typhoon/Feeler/Amadeus and also to activate the additional WMP plugin for the Amadeus.
So finally here is the share to get all: http://www.mediafire.com/?3tt15dyp4mbuu
Please hover the mouse over the download links to see their description.
Finally you may want to look at the Beginners Guide for Cooking which you find linked in my signature - this give some insight of what is happening.
Some more info on available memory (RAM) which is really tight on this device. You can roughly save RAM in the following order:
> 2MB: Don't use the sliding panels homescreen. Unfortunately this is the nicest visible sign of WM6.1/6.5 - but if you just use the "Windows Standard" Homescreen there is more than 2MB gain in RAM!
> 1MB: De-activate the Camera driver, all SDA Business users (without camera anyway) should do that!
~ 500kB: De-activate the Date/Time save driver. If you don't mind setting the date/time by hand after battery removal or have the device connected to the PC anyway with AS.
I have not noticed a gain when de-activating the Carkit driver.
For clean conditions when testing, please always reboot the device after changing settings. I noticed that even unchanged settings will not produce identical values after reboot. Tests were done with clean reboot, full initialisation of the Homescreen and then starting Oxios Hibernate.
Nobody seems to care about this old stuff anymore :-(
Mediafire has logged 19 downloads of the built ROM and 15 of the kitchen, but not a single "thanks" in the thread - if you use it, just say thanks for my motivation, please.
Anyway I have migrated the kitchen to OSBuilder which has more tweaking options regarding Kernel parameters and also gives more other control over the build.
Is anyone interested in getting the relevant OS Builder package?
You need to install OSBuilder first and can then start cooking right away after you have the package that I could publish.
In the process of dealing with the very limited amount of RAM especially for the Typhoon I had to reverse on 2 things I did in the past for the sake of squeezing ROM and RAM space. Both have adverse effects to what is initially intended. I had published and discussed this in detail in this thread. So you must avoid the following:
Cutting down the Paging Pool to the bear minimum (so the device still boots). This gets you free RAM, true - but it will cut you off the space in RAM where the code of the programs goes! So a small paging pool will actually prevent that you can run many programs, despite of the free RAM. So it is advisable NOT to cut the paging pool below 4 MB in my experience.
Using UPX to squeeze ROM space. While it works to get more data stuffed to the ROM, the resulting executable will no more be able to utilize the paging pool for its execution. The whole code goes to the free RAM and not just the currently used part in the paging pool. So by saving ROM space (or filesystem space in general) with UPX you are wasting actually RAM a lot!
Because of 2.) above I have reverted to all original packages - so no UPX anywhere in the ROM build or any related package. I had to remove a few things from the default package selection, but nothing that cannot be installed later anyway. Due to non working A2DP I have also removed that again completely.
Another find related to fixing the problem that System Volume gets reset when changing the profiles, see here: http://forum.xda-developers.com/showthread.php?t=1407883
Kitchen Updated to OS Builder, new example builds included
To those who want to get the fastest and most advanced kitchen and builds available for Typhoon. You can pick from Mediafire:
a 7Z with 4 builds to flash the device with, 2 sorts with either English or German as default language (you can change in the regional settings anyway).
a 7Z with the OS Builder Kitchen setup. Install OS Builder first (See post 3 pointing to the OSB thread), unpack the kitchen to any folder convenient, then double-click on the .osb file to fire up the kitchen.
Cooking is pretty much self-explanatory - in the end you get a OS.BIN file that can be uploaded to the device via MTTY.exe. All tools are included in the kitchen 7Z and can either be used directly from the folder or via the Tools Menu in OSB.
I have added two folders to the kitchen. One for most of the packages in their original distribution files; so if these are not in your build, just in stall them manually. The other to trace the provxml execution - which is something you may never need to do.
For the packages to select, the OSB allows to group packages to switch-groups. One of the important switch groups is the one for .NetCF. This package is the most storage hungry and so there are several ways how to deal with this in the context of the 27MB limit of the ROM:
Include the whole package to ROM: this puts all to the imgfs which is compressed with LZX - and so the total cost is ~2.9MB
Exclude the whole package and gain ROM space for any other stuff to include. You should then also exclude all .NetCF dependant tools or install .NetCF later from a CAB to get them working again. As there is one basic program (the calculator) which depends on .NetCF I have replaced this with the old WM2k3 calc.exe in case you select this package - saving another 120k. So in total you gain 3 MB in the ROM. Mind however that a later installation will eat ~1.2 MB on the FATFS in the device (Program Storage) and another 5 MB on either SD card or again on FATFS - depending on what you choose to install it to.
Include only the files that go to the device mandatory anyway, but not on FATFS when installed later but on the IMGFS, hence compressed and eating only 750k in ROM. The rest of files (the 5MB *.GAC) go then to either FATFS on the device or to the SD card. You can select this in the kitchen when building the ROM. Later you must copy these *.gac files manually to the right place. The package with these files is in the _packages folder of the kitchen.
I have done the final works on that kitchen and will not further do anything to it. You find the updated kitchen in the mediafire share of the first post. Download the file "Typhoon-OSB-kitchen-20120306.7z" there. Recent fixes are:
MMS dialogs use a smaller resource file for 176x220
Kernelflags are set to ...02 now to keep the MMS dialogs readable when you change the folders
CallerLoc is replaced by a dedicated tool (with understandable dialogs) CallVibrate
Sliding Panel background is fixed (was offset on the top-bar)
Some more tools added and instructions how to get back to WM2003 if needed
Mind that the created builds fit for any Typhoon/Feeler/Amadeus as you can switch/reboot the keyboard drivers.
Have fun and give some feedback if you created your own builds.
Candy-bar forever
SDHC on Typhoon (and Hurricane)
Hard to believe - but it is there: SDHC support on the Typhoon
No magic actually but just good luck that the Tornado driver (which is actually one form the StartTrk) for SDHC works as well on the Typhoon and Hurricane (which share the same drivers in their original builds).
You need to re-cook to get this. Related modules are attached, including the advice what to do (just 3 modules and related .rgu entries).
To get SDHC support in a cooked new build for Typhoon and Hurricane, do the following:
1.) remove the 3 modules in the ..-original folder from your OEMDRIVERS folder
2.) remove the entries from the contained original.rgu from the one in your OEMDRIVERS folder
3.) copy the 3 modules from the ..-sdhc folder to your OEMDRIVERS folder
4.) copy the entries from the contained sdhc.rgu to the one in your OEMDRIVERS folder
re-cook and enjoy
Click to expand...
Click to collapse
I have not done much testing yet, but some obvious checks have worked well.
So if there is anyone out there still owning these oldtimers: time to get them off the drawer and put some fresh fuel in - Typhoon and Hurricane make perfect music players.
Latest updated (the real final one).
Uploaded a new complete Kitchen including SDHC support and new USBFN bundled with WM5torage only (see first post). I do not recommend to use WM5torge with Typhoon - it is too slow anyway, you better get the card out and fill it external from the device with an USB reader.
now the real final one
20121003 Update (since no new posts allowed anymore):
Just to let you know: The SDHC lets the device also read FAT32 formatted SDXC cards (e.g.64 GB). It even reads more than one partition (I have 2 on my Android) and mounts both of them (32k Cluster size used).
Not sure how well the performance will be when managing data there - but reading a large music collection should be ok
So after I sold all my Typhoon devices (except a few you just cannot sell due to their physical state) - the latest small update to the kitchen.
What I have changed (diff from 20120408):
cleaned up some resource files (saving quite some space)
added icons to those which had none
made provxml tracing the same for all
added some small games (these eat the saved space from above)
added an option panel to setup the volume of VoiceTag (from my other kitchen)
made D3Demo an extra package
added the very latest NetCF 3.5 as modules in an own package
added a few more color schemes and backgrounds
patched the keyboard driver to not require a dedicated subdirectory "Keys" in \windows
patched the nk.exe to identify itself as "TYPH100" to allow better skin selection for remote access tools
renamed mtty to the correct name (was mmty.exe)
fixed the welcome.exe for the German Mui to correctly delete the welcome.lnk from autostart at first boot.
removed the _cabs folder form the kitchen. Get it from an older kitchen
Hi all, just got my O2ZPhone II (Feeler) out of the pile of goodies, would like to use it for my second phone.
The OS on it is still wm2003, trying to go for this WM65 ROM, I found that the SPL is on 1.01.0139 on this phone, which I try to go for the 109 with no luck, and mtty report error in bootloader too...
Anyone any idea on how should I get this WM65 ROM flashed to this great phone?
Thanks.
If the phone is still original, then you have to go all steps which you find in either the kitchen-tools menu or the tools folder directly:
application unlock old OS (SDA Application unlock)
apply Super CID to the phone (lokiwiz.bat, "C")
load new SPL to the phone
create new ROM (get OS Builder from the referenced thread)
upload with mtty.exe
Steps 1-3 need to be done only once per device.
I would not use the old os.bin I had uploaded as the latest kitchen can produce better ones and you have the choice what to put in or out. The default settings deliver a running build (you may want to remove the "German default" though).
thanks tobbbie, for some reason I downloaded the wm61 one, and yes with your great instructions I was able to flash that to the device and now happy using it!
(Will try the kitchen during the weekend)
Great thanks!
枫影2.3.4ROM Made in China I have already Translated into English！！welcome everyone
Adaptation of models for the MOTO ATRIX all versions, such as the following:
ATT
China (including Hongkong, Taiwan)
The Republic of Korea
Canada
Australia
France
Britain
Italy
Singapore
Distinguish between simple version - the MOTO ATRIX series of only two version - International Version and the version of ATT, the list above, ATT is the ATT version, other all belong to the international edition.
Ha ha ~ ~ ~ ~ you are not wrong, is all versions, have been more tests, through the brush is so simple ~ ~ ~
But there are a few points I want the next state:
In 1, the version of MOTO official BELL version of 2.3.4 system, the latest version of the official.
In 2, I'm really sorry you, waiting for such a long period of time, my personal life is very busy with work, busy busy building completed, feelings, really busy, I'm sorry......
3, the use of the system need machine BL unlock, unlock the following information:
( 1) the International Edition ( most ): http: / / bbs.gfan.com / android-2002585 - 32771; ] ...
( 2) named Hong Kong Version ( the presence of a hard tile probability, so listed separately ): http: / / bbs.gfan.com / viewthread.php? T... 20284 ];
( 3) named Singapore Edition ( the presence of a hard tile probability, so listed separately ): http: / / bbs.gfan.com / viewthread.php? From = favorites t...
In addition, after my system in external a batch to install the recommended software and AD advertisement software projects, I hope everyone on my work can support, thank you!
PS: advertising software can be removed, the specific use of built-in RE manager, enter the / system / APP /, find all com. APK at the beginning of program, deleted, restart the machine, is so simple, if you are not willing to do, that also is not brush.....
My note:
I love to toss, especially in Android mobile phone, no matter what his models, as long as I like, I can put him in a good
System description:
[ ] take reading system
Version number: Maple Shade v3.4.4
System improvement:
1, No. 100 baseband, relatively the baseband signal and fever are quite considerable. ( due to the discovery of before China baseband and 2.3.4 system in compatibility problems, so this version to give up in the country such as baseband baseband, line officially launched the 2.3.4 to update the version is. PS : Celestial does not update.. ).
2, support for H +, you read that right, is the real H +, don't argue with me, have more tests to download faster than 6XX KB / S, not KBPS, this I know!
( H + distinction, due to geographical questions, UniCom of different regions to H + at different rates, for example, Changsha here, if you are old 186 card, the speed will be locked in the 3XX KB / S, if it is in Zhengzhou, faster than 620KB / S, if it is in Shanghai, faster than the 680KB / S, if Kunming, faster than the 1MB / S )
3, support operator custom [ default Chinese operators, if necessary, can go to / system / etc / spn-conf.xml automatically controlled to modify, and do not want to show, name blank can be ] ( last edition 3.4 I forget to maple shade modified reduction, this version fixes, you can freely modify )
4, support all Google official upgrade ( I was not in favor of ROM direct update Google applications, because it will lead to a new version will not be able to update! So please update the best, direct electron market update )
5, system settings - Voice: can be manually opened, closed, four big Jin'gang vibration; open, closed, SD card sound load; open, close button sound;
6, the system has Deodexed, and through the official GOOGLE SDK zipalign acceleration
In 7, ROOT perfect
In 8, the perfect Chinese SMS, MMS CDMA mutual
In 9, the operator APN information automatic setting
In 10, AGPS by default, give you the most awesome GPS positioning!!! Default 10 seconds [ ] preliminary positioning
In 11, China Unicom, China Mobile 's revised Chinese status bar logo
In 12, the default MOTO BLUR official regional [ if you cannot login account, please register again ]
13, remove the system comes with official procedures, some built-in celestial cannot use function, parts can be replaced with the official program application removal system cache, cleaning
14, continue to optimize the streamlined, kill the voice commands ( to use GOOGLE voice command instead), kill the input method, system flow.
15, authentic Chinese (Simplified Chinese, traditional Chinese, English special join ) the system more smoothly
16, to support the 3G / 2G network switching
17, to join the system browser can shield the spam address function
In 18, WEBTOP distortion correction, and support for WEBTOP, break out.
19, increase of HDMI function, break out.
20, change the HDMI output of 16 : 9 mode
21, speed up external SD card read and write speed, especially for high-speed SD card is very obvious! ( please use the SDTOOL tool to contrast after the upgrade and upgrade the former change! )
In 22, the built-in battery taskbar display accurate to 1%, program control, Chinese, can be set, this thing is very strong
23, adjust the base configuration, enhanced 3G signal receiving capability and network transmission rate
24, open set is installed inside the unknown source APK function, for the user to select mode ( simply can install the pirate )
25, cancel the network operator display hidden
26, support the follow-up version upgrade
Special update:
1 additional systems, automatic memory consolidation, is an excellent system for their own mode of management, not an additional third party software.
2, adjust the JAVA virtual engine for 64M mode, instead of the official 32M mode, more quickly.
3, support time localization, the default for the Beijing + 8.
In 4, the battery 1%
In 5, GTALK video chat support 3G, 2.5G, WIFI
6, optimizing kernel, run 3500 + ( OC kernel, please brush into the official kernel, default )
7, delete from official duty software, YouTube and some useful official software
8, repair lock screen (actually a software: phonesleep, this version 2.3 or later seemingly does not support 2.2 dedicated the lock screen. )
In 9, WEBTOP is the official version ( XDA MOD V2 version of the current brush is a bit of a problem )
10, optimize, accelerate fan speed and system effects switching speed, so that the smooth without delay
11, multi-touch default 4 ( thanks to michael0619 Research ) ( I found more than 5 points sometimes is not very stable, so to stable 4 touch )
12, brush machine fool simplification, automatic restoration of the international version of RAM loss problem
13, open the HDMI settings, open DESK settings, open the APN editor
14, open 32 color dynamic wallpaper support
15, support the volume keys to awaken
16, system support the hard solution MKV 1080P!!! ( if you do not believe, do try)
[ ] to measure
1, download the zip, unzip to C: \
In 2, when I provide drive, of course you drive too would not be
3, the system unlock BL ( above the unlock field notes and links)
In 4, the original system data backup, and to ensure that your built-in SD card available space at least 3G.
In 6, the compression package [ FengYingV3.4.4-AtrixMB860.zip ] files are copied to the built-in SD card under the root directory, please note, is built in the SD card!!!
7, turn off your mobile phone, press the volume down + power key = boot, until the display FastBoot, release the button, press the volume!
( if you have brushed my master R recovery system, please ignore this step )
( if you brush the custom RECOVERY system is not R master version, please replace the master version of R, because CWM 4.0.1 5 does not support the built-in version of the SD card brushing machine!!! Many brush machine success ERROR 7 this error is the problem!!! )
[ here is the master R version RECOVERY Download ] http: / / u.115.com / file / aqkfs7ed
Brush RECOVERY method, please refer to [ 1-3 ] brush machine step
8, plug the USB data line.
OK, is ready to finish.
[ Methods ] upgrade
( if you have brushed my custom recovery recovery system, please continue to ignore the step 1-3 )
( if you are a ATT version, the upgrade method is similar, but the file name is not the same, remember to separate )
1, enter C: \ moto-fastboot-win32 folder, double-click the [ Command Prompt ]
2, see the CMD page, enter the following command to brush into the recovery custom recovery system (note, if you unzip the file is not in the C: \, the command also need corresponding change; does not support Chinese )
Input:
Moto-fastboot flash recovery C: \ moto-fastboot-win32 \ recovery-en-0630-1029.img
RECOVERY recovery system into the brush finish; ( when you see the computer screen display similar XXX / s this information is said to have a good brush )
In 3, then the input moto-fastboot reboot, such as mobile phone automatic restart after entering a system, shutdown.
4, enter recovery mode ( press the volume down + power button to see the FastBoot, press the volume down, switch to an droid recovery, press the volume selection into )
( volume the next choice, the power button to determine )
5, into the recovery model, the corresponding selection:
( 1 ) the first choice of wipe data / factory reset, to empty the historical data (warning: if your recovery CWM-based version, empty when it will prompt you whether or not to empty the sd-ext data, choose! Otherwise your external data of the SD card will disappear! )
Upon completion, will automatically return to the home page
( 2 ) install zip from sdcard
( 3 ) choose zip from sdcard
Select internal SD card ( 4)
( in the external SD card, select external SD card, the useless)
( 5) choose the FengYingV3.4.4-AtrixMB860.zip package, determine, start brushing machine.
Wait patiently for the brush machine to complete, and then select go back has been rolled back to programs
Select the reboot system ( 6 )
6, clean system completed.
System version - FengYing-v3.4.4
Prompt.
In 1, GPS by default, please manually shut down can save electricity
2, if you don't like with advertising, please use the RE manager, enter the / system / APP /, all com. Love can be deleted.
( thank you for your support of my work, please delete before activation; personal recommendations deleted)
Special on how to save:
1, if you are not a developer, please shut down USB debug mode.
2, ibid, using the Android assistant, usually during shut down unnecessary background resident services.
3, setting - > battery management - > Settings: the most power ( when playing the game can be set to a general )
4, usually GPS goes situation, please remember to close the AGPS.
[ I found the differences, some friends, some friends said that energy saving electricity; but I think that if more than my instructions well, basically should be - power ]
Download address
MOTO ATRIX series of the latest drivers, all users please update ( currently in June 6th before the latest )
Http: / / u.115.com / file / bhaxhed8
-- -- -- --
The official U4_2.1.1 SBF bottom bag, please GOOGLE brush machine method, a lot of [ ] for people to spare
Http: / / u.115.com / file / aqpxa6uz
-- -- -- --
Moto-atrix-mb860-2.3.4 - v3.4.4 - Maple Shade released - brush pack!
Http: / / u.115.com / file / e65lnr5r
-- -- -- --
Moto-atrix-mb860-2.3.4 - v3.4.4 - ATT version of Maple Shade - released - brush pack!
Http: / / u.115.com / file / bhish38w
This ROM is made in China also it Built in English
please read it carefully,this ROM in china is very popular！
Has anyone gave this a try?
Sent from my MB860 using XDA Premium App
Screenshots?
I would be very careful when flashing this.
The reason being is that the author of this project has annouced a pull back of this version due to major bugs.
This will be updated soon and that will be the one I would flash, personally.
i wouldn't flash it because it's in the wrong damn forum =p
somethings fisheh
Sorry, but does that say there is mirroring in landscape mode through HDMI?
i cant make sense of most of it..... id like to see some screenshots! most likely wont flash though
Just googled his version number
I am interested in his HDMI 16:9 comment... did he get HDMI Mirror in Landscape?? IF so we need to find out how!!
Found some screens of this guys ROM...
Also a little more information that he did not post i the OP:
About OC core (OC kernel version update is expected on the 25th release):
The system comes with 2 cores and 2 OC native official kernel (thanks to XDA faux123 provided), are:
INTL-MBR-1100-GB-Kernel-0.1.2-ext4-sv.zip (RAM-1100 to adapt the sequence: a variety of optimization OC 1.1G kernel, CWM brush into the can)
INTL-MBR-d00-GB-Kernel-0.1.2-ext4-sv.zip (d00 of RAM to adapt the sequence: a variety of optimization OC 1.1G kernel, CWM brush into the can)
INTL-MBR-1100-original-kernel.zip (adapted for the 1100 series RAM: official native kernel)
INTL-MBR-d00-original-kernel.zip (d00 of RAM to adapt the sequence: the official native kernel)
Most people say why some ROM to run sub-3500 +, in fact, the role of these cores, but the negative effect is that power consumption increases, in fact, in addition to running at the different system fluency, I did not feel much different.
Therefore, the default is system's native kernel.
How to distinguish your phone is 1100 series or d00 series?See above Brush tutorial RAM hour repair parts, similar
On the lock screen, bright screen response speed adjustment instructions:
1, the default lock-screen, once again light up the screen time is about 250 milliseconds.
2, If you think this is slow, need be
3, using the [manager] RE modify / system / build.prop file, find: mot.proximity.delay = 250, modified = 100 to save, you can restart.
Brush on some friends unsuccessful Description:
1, check whether your RECOVERY R master version, and is 6-30 in English that day!
2, check the available capacity of your SD card if there is more than 3G?
3, check whether the copy to Brush package is built-in SD card?
4 Note: The system will automatically restore the machine RECOVERY master version of R, if you are CWM version, when you want to change the system, replace your own version of RECOVERY for the CWM.
Any brave souls willing to flash this and check for HDMI mirroring?
If it's there, maybe someone could pass it along to agrabren. He's got HDMwin working pretty stellar on the EVO 4G so this might be the big push we need to get it on the Atrix.
I'll give a shot,i just need to get this right. download the file with 3.4.4 version and flash it on recovery or install with rds or fastboot?
Sent from my MB860 using XDA App
aaron.a said:
i wouldn't flash it because it's in the wrong damn forum =p
somethings fisheh
Click to expand...
Click to collapse
cm7 its on general and a lot of people are using, give this ROM a shot too.
Sent from my MB860 using XDA App
Downloading from Chinese servers is slow.
slow? i get 8kbps, its more than slow! lol
Sent from my MB860 using XDA App
Actually getting around 80KB/s at points, might have this ROM by the end of next June
I have the file at home, got it last night took an hour to download ill upload it if you want me to tomorrow
Sent from my MB860 using xda premium
JaronBang said:
I have the file at home, got it last night took an hour to download ill upload it if you want me to tomorrow
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
we would appreciate if you did it
Sent from my MB860 using XDA App
Yeah ill do that, just hang tight ill have it up tomorrow.
Sent from my MB860 using xda premium
So I downloaded it. And I tried to flash it. And it aborted
Almost tried it but read that the link was pulled due to bugs. THanks for trying and posting though.