[TUT] Beginners guide to Windows Mobile (prepare for cooking) - Windows Mobile

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.

Related

[MOD][SENSE2.5TAB] SenseUtil (Tab Control File Editor) [10 Aug 2011 New Release]

Project Open
Compiled Cab file attached to this post.
Code-Plex Page (source available):
http://senseutil.codeplex.com
{
"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"
}
======================
Project Status
======================
Initial development is completed.
The application does all the items defined in the Manifest!
Ideas and feedback are very welcome, particularly for the GUI (which is more functional than anything else).
Graphics etc are welcome, then I can add graphical controls etc and state icons.
Added example shortcuts
Shortcuts for use with installing and uninstalling tabs. See Shortcuts section of the manual below.
Release 10th Aug 2011 (meltwater_SenseUtil (9433).cab) - Thanks to mike2nl for gathering the extra tab details and corrections!
+Added (shortcuts & resource files):
1a9fc010_manila \windows\HTC\today.mode9
2c417551_manila \windows\HTC\GGorizont\GGorizont.mode9
04ca8df7_manila \windows\HTC\GPSTracker\GPSTracker.mode9
34C172FA_manila \windows\HTC\Manilatv\favorites.mode9
037D6881_manila \windows\HTC\GameFifteen\GameFifteen.mode9
0C3A0700_manila \windows\HTC\programlauncher.mode9
2CAADFCD_manila \windows\HTC\manilaradio\manilaradio.mode9
+Corrected document tab shortcut
+Language title files (6f286a05_manila_en-us_titlefixed.txt is template for others)
+Language title files added to cab (although most require translations etc)
Code:
[B]Release 22nd Feb 2011 (meltwater_SenseUtil (6952).cab) - 680views[/B]
+ Added fix for "Unable to update file"
+ Using Release instead of Debug build
[B]Release 26th Jan 2011 (meltwater_SenseUtil (6328).cab) - 189views[/B]
Code is the same, but added CabFile to package (with Shortcuts) and HQ icon for application.
- Cab will always install to Device "\windows\SenseUtil" regardless of user selection.
[B]19 Jan 2010 (SenseUtil_6026.zip)[/B]
Changed default position to after home tab.
Added shortcuts for more tabs.
[B]18 Jan 2010 (SenseUtil_6007.zip)[/B]
Updated softreset message for commandline updates.
[B]17 Jan 2010 (SenseUtil_5973.zip)[/B]
------------------
Added shortcuts.
Added option to reset device following command-line modification of tab control file (with prompt so user can wait to see if sense restarts without reset).
[B]2 Dec 2010 (SenseUtil_5021.zip) - 246+140views[/B]
------------------
Initial Release
Cab (thanks to Captain_Throwback).
======================
Additional Work
======================
Missing Available Tabs:
===============
If there are any missing tabs from the available tabs list, then send me the details so I can generate a resource file.
Extra Features (To Do):
==========
At some point I will update the app to read the configuration keys (if available) and generate the file using the order defined there (plus re-generate the keys to keep disabled tabs disabled).
Graphics:
======
If anyone is interested, I can add icons to help determine the states of the tabs...just need some graphics!
Possible State Icons for tabs:
Tab Installed & Present - in the tab control file & on the device (Installed Fine)
Tab Not Installed & Present - not in the tab control file but on the device (i.e. Available to add)
Tab Installed & Not Present - in the tab control file but not on the device (!Warning State! Sense will probably fail to run)
Tab Not Installed & Not Present - not in the tab control file or in on the device
Also the icon could indicate if the source is from XML file or the tab control file (only applies to the installed ones - not installed ones will always be xml).
====================
User Manual
====================
I'll try to update this with new information as and when I get time, hopefully the app isn't too difficult to understand.
Control Sense Page:
============
This page controls sense...
[Start Sense]:
If sense is not selected in the Today Plugin, this adds and triggers sense to start.
[Stop Sense]:
If sense is running, or set in the Today Plugin to run, this will remove it and trigger it to close.
[Restart Sense]:
This will cause sense to restart (by removing and adding it from the Today Plugin).
Note: Any changes to your Tab Control File (26948339_manila) are ignored.
[Reset Sense]:
The same as [Restart Sense], but will also cause it to re-build by removing the ManilaFull.xml file.
Note: If you have changed your Tab Control File (26948339_manila) any changes will be re-built in this process.
[Full Reset Sense]:
The same as [Reset Sense], but will also delete the configuration registry keys (this is required when you add/remove tabs for them to initialise correctly and for them to show up in the Tab Re-arrange page within the Sense Settings Tab).
Note: Any tabs disabled via the Sense Settings Tab will be re-enabled!
[Soft Reset]:
This simply restarts your device, quite often sense will not re-start correctly without at least one reset.
Tab Control File [Update]:
If you have generated a new Tab Control File (26948339_manila), this option will replace your existing file (creating a timestamped backup within the SenseUtil folder) and [Full Reset Sense].
Tabs (Loaded) Page:
============
On start up, this page shows the contents of the Tab Control File (26948339_manila).
[Build]:
Once you have made adjustments to the list, you can build a new file (which you can then view using a suitable text editor and check if you wish).
Tab Source [#]:
This toggles the source of the tab data:
Default=Your original Tab Control File
File=The loaded xml resource file
Note:
If the tab is not available (the xml file does not exist) then the source will not change. Also if you delete and re-add a tab which was in your tab control file, it will not be able to be set back to Default - you will need to Reload the data fresh.
Remove [-]:
Removes the tab, the tab will no longer be installed.
Shift Up [^] and Shift Down [v]:
Allows you to adjust the default positions of the tabs.
Tabs (Available) Page:
============
This page will show you the tab's which are available (loaded from the Resource Folder xml files).
When you select an item, you will be able to see if the tab's keyfile is Present On Device or not, this provides an indication of if the files required for the tab are on the device
Note: Only the keyfile is checked - there will be additional files required for the tab/sense to function.
Various details about the tab are also available, if a custom tab links to the tab's development and release pages should be provided.
Add Tab [+]:
Allows you to add a tab to your Tab Control File, if the tab is not detected as Present On Device you will be warned that Sense probably will not start (you will need to install the correct tabs files on your device).
Add All [+All]:
This will add all the tabs which are detected as Present On Device but not currently in the Tab Control File.
Note:
Only the keyfile is checked - there will be additional files required for the tab/sense to function. So be sure you have correctly installed all the required files for a particular tab.
Settings Page:
============
Provides various options for the app.
Register to Today Softkey:
[Set Action/Contacts)]​
Only recommended if you use the app a lot as it provides an easy way to start up/control sense if it has not loaded.
[ ] Advanced View:
This allows you to see all the data which the app collects about the installed/available tabs and uses to do what it does. Useful for debugging issues with the resource files or problems with the app itself.
[Reload Files]:
This will read in your Tab Control File again, and reload all the resource Xml files (for the available tab list).
Note: Any changes you've made to your Tab Control File in the app will be discarded.
Command Line Options:
============
SenseUtil add 6B54437C_manila
- Adds the specified tab, leave other tabs as they are
SenseUtil renew
- Replaces all tab details with data from the xml files (leaves any not found in the xml files as they are)
SenseUtil addall
- Adds any tabs which are not in the tab control file but found on the device (checking for the key mode9 file), the other tabs are left as they are. New tabs are added at end before settings tab.
SenseUtil addallnew
- As above, but other tabs are replaced with details from the xml files (leaves any not found in the xml files as they are)
SenseUtil remove 6B54437C_manila
- Removes the tab if installed on the device
Shortcuts:
========
By using the shortcuts, it is assumed that SenseUtil is installed to device location:
"\Windows\SenseUtil\"
Code:
i.e For FbTab:
Add Shortcut:
54#"\Windows\SenseUtil\SenseUtil.exe" add 51B6F88A_manila
Remove Shortcut:
57#"\Windows\SenseUtil\SenseUtil.exe" remove 51B6F88A_manila
For other tabs, look up the xxxxxxxx_manila file in the resource section and replace 51B6F88A_manila (note: the 54# and 57# need not change since the length should remain the same). Or post a request and I'll upload suitable shortcuts!
Note:
1. Before using the shortcut you must install the correct files for the tab in the correct location (if files are not present the tab will not be added).
2. System may need Soft-Reset (turn off and on again) for sense to restart correctly (you will be prompted to wait and see if sense starts).
3. The order set by the settings tab will be reset by this process.
Code:
[SIZE="5"]===============================
Application Manifest - What I Planned To Achieve
===============================[/SIZE]
The plan is a simple program which reads the tab control file (file 26948339_manila) and allow you to add/remove tabs using a simple xml file to provide the correct info.
MoonNah's ([url]http://forum.xda-developers.com/showthread.php?t=670116[/url]) B_L_Group_FixStartManila_2.5.cab is an excellent tool which simply re-generated the list based on the files it found within the windows dir, worked well except there was no indication that is was successful or what it had done.
I think it would be quite simple to extend the idea a little further by creating an app with a gui which then searched it's local folder for xml files. The xml files will be named to match the key mode9 filename for each tab:
i.e. RSS Tab = \windows\htc\people\RssFeed.mode9 = 6B54437C_manila
[B]So there would be a xml file called 6B54437C_manila.xml which contains the data for the tab:[/B]
[CODE]<Page Order="X" Name="rssfeed.page" PackageName="HTC" Title="[[IDS_RSSTITLE]]">
<ComponentReference Name="page" Mode9Path="HTC\People\RSSFeed.mode9" Component="SummaryAllPage" SmartComponent="true"/>
<ComponentReference Name="icon_normal" Mode9Path="HTC\Manila\RssFeedicon.mode9" Component="RssFeed_Off"/>
<ComponentReference Name="icon_selected" Mode9Path="HTC\Manila\RssFeedicon.mode9" Component="RssFeed_On"/>
<ComponentReference Name="icon_preview" Mode9Path="HTC\Manila\RssFeedicon.mode9" Component="RssFeed_Preview"/>
</Page>
So the app would look for each of the xxxxxxxx_manila files in the windows directory and then allow the user to add/remove any tabs which are present on the system. This would also allow users to totally disable any "problem" tabs more effectively than via the config keys.
The xml files could also have a full list of required files (which could also be checked), perhaps a link to obtain the latest release, the app could then be released with xml files for all current tabs and any new ones so users can easily see what is available and obtain them.
The app would also handle the disabling and resetting of sense so that the changes are correctly made.
Also the app could support command line option to install a specific tab if present (not making any changes to the others), which can then be used by cab files.
Note: Software is able to set today screen softkeys for easy use, but a proper soft-key manager is available here if you decide you want to set them to something different:
http://forum.xda-developers.com/showthread.php?t=388281
I will have a try at making the app myself but my time is very limited so any help will be greatly appreciated. But I do think that such a program would be very useful for those who have problems editing their tab control file (file 26948339_manila).
Let me know what you think?
======================
Language Title Fixes
======================
Custom Tabs (like RSSTab/Facebook Tab display IDS value on 1st run)
This is because the translation file used for the tab titles is separate to the tab's own language file.
I will update senseUtil to allow the users to update the files using a shortcut, but until I've completed and tested that, I've included a zip file of the required files.
CAB INSTALL:
Install meltwater_LangTitleUpdate_v01.cab. - 155views
Reset sense.
MANUAL INSTALL: - 149views
Unzip and copy the files into your devices \windows\ directory, and then reset sense.
Please let me know if you have any problems or if you have updates for the contained translations (I've only updated the ones I've already got translations for).
[/CODE]
======================
Language Title Fixes
======================
Custom Tabs (like RSSTab/Facebook Tab display IDS value on 1st run)
This is because the translation file used for the tab titles is separate to the tab's own language file.
I will update senseUtil to allow the users to update the files using a shortcut, but until I've completed and tested that, I've included a zip file of the required files.
Updated language files are contained within the SenseUtil cab file, please update the file language files and post them here (they will get included in the next cab).​
Great idea meltwater. This will help rookie cooks like me
TIA
illi said:
Great idea meltwater. This will help rookie cooks like me
TIA
Click to expand...
Click to collapse
Well my thinking is, if we can make the "black art" a little "lighter" then it opens things up for novice users (like I was once) and brings fresh ideas and talent in.
Ok, I've created an outline project in CodePlex, I will start putting in some basic stuff and see how I get on.
Time is limited for me, so if someone else is interested in working on this too then they are welcome. The source is easy to download, and I will happily add you to the project if you wish to upload your progress directly.
Excellent idea! ThumbsUp for this
1st Release!
Ok, I've put some starting stuff in (attempting to control sense).
Need some people to test it, I think there is an issue with starting sense again although not sure what. Soft-reset and it will comes back (assuming you've not changed anything else).
Sense Control Tab:
Start Sense - Clears the entry in the Today page for HTCSense
Stop Sense - Sets the entry in the Today page for HTCSense
Restart Sense - Does Stop and then Start with a delay in the middle.
Reset Sense - Same as Restart Sense but deletes the ManilaFull.xml file (which will cause sense to re-initialise - file will be regenerated)
Full Reset Sense - Same as Reset Sense but also clears the configuration keys (required when you add/remove a tab)
Settings Tab:
Allows you to register the app with the Today page softkeys (gives easy way to get sense running again!).
CAUTION: Only set to restore the defaults on my phone (LSoftkey=Action Page RSoftkey=Contacts).
Keys effected by this setting are:
HKCU\Software\Microsoft\Today\Keys\112
HKCU\Software\Microsoft\Today\Keys\113
Find the latest code in codeplex: http://senseutil.codeplex.com
Tester
I can try to test the app if you want.
Using Jackos ROM with Sense 2.5.20181527.0
But I flash relatively often so I'm able to test it on some different versions.
Could you point me out what I should do now (what to download, what to pay attention on)?
Hey meltwater!
I see you've gotten tired of manually updating people's Tab Control files .
Great idea - I wish I had some programming knowledge so that I could help. Unfortunately I do not. How difficult would it be to learn? What software would I need?
Skrobel said:
I can try to test the app if you want.
Using Jackos ROM with Sense 2.5.20181527.0
But I flash relatively often so I'm able to test it on some different versions.
Could you point me out what I should do now (what to download, what to pay attention on)?
Click to expand...
Click to collapse
Excellent!
So far it only has the basic sense control buttons in, so it would be help to check that they work correctly. My testing has shown that it sometimes has issues with starting sense, but that could be down to my sense setup (it's not very stable due to CHT and my own development work...).
At the moment, I seem to also have some issues with the softkey settings (but I'm happy I can continue testing that, issues with permissions etc I think).
From the codeplex changeset package (the zip file you download) you will only need the SenseUtil.exe (later on anything in the \Debug directory as files are added).
Captain_Throwback said:
Hey meltwater!
I see you've gotten tired of manually updating people's Tab Control files .
Great idea - I wish I had some programming knowledge so that I could help. Unfortunately I do not. How difficult would it be to learn? What software would I need?
Click to expand...
Click to collapse
Well more accurately... tired of some users...although having an easy way to reset sense etc will be very handy. Plus does seem to be the number 1 cause of issues.
It is a good as project as any to learn how to program on (nice mix of changing the registry, reading files and standard .net forms). You will need something like Visual Studio 2008 Professional though (you can get 90 day trials quite easy - let me know and I'll find you one).
I'm quite happy to help guide you (or anyone else interested) as far as I am able (although my code should not be taken as a prime example of how to code - it's not my trained area of programming).
OK, it's time for first impression
From the Sense control tab everything seems to be working cool. I tried each option in the first tab several times and Sense always started without problems.
I have one question though. After the first time I made a Full Reset (with the config keys) this button was inactive anymore. I recon that the keys are already deleted. But shouldn't they be redefined during Sense next start?
And I confirm the matter with softkeys. The first time I wanted to assign SenseUtil to right softkey, the "Unexpected error" appeared (right after I confirmed I was sure) and I had to kill the app. However the second time each left and right softkey worked.
But the Set (Action/Contacts) button never worked. There is always Unexpected error when I tap "OK" in the message box. Below I present the details of the error.
Code:
SenseUtil.exe
ObjectDisposedException
w System.ThrowHelper.ThrowObjectDisposedException(String objectName, ExceptionResource resource)
w Microsoft.Win32.RegistryKey.EnsureNotDisposed()
w Microsoft.Win32.RegistryKey.EnsureWriteable()
w Microsoft.Win32.RegistryKey.SetValue(String name, Object value, RegistryValueKind valueKind)
w SenseUtil.Settings.SetSoftKey(Int32 selkey, String text, String url, Boolean confirm)
w SenseUtil.SenseUtil.buttonRegDefaultSoftKey_Click(Object sender, EventArgs e)
w System.Windows.Forms.Control.OnClick(EventArgs e)
w System.Windows.Forms.Button.OnClick(EventArgs e)
w System.Windows.Forms.ButtonBase.WnProc(WM wm, Int32 wParam, Int32 lParam)
w System.Windows.Forms.Control._InternalWnProc(WM wm, Int32 wParam, Int32 lParam)
w Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain)
w System.Windows.Forms.Application.Run(Form fm)
w SenseUtil.Program.Main()
I hope this all helps. I would also like to learn programming, but it needs more time than I actually have...
Skrobel said:
OK, it's time for first impression
From the Sense control tab everything seems to be working cool. I tried each option in the first tab several times and Sense always started without problems.
I have one question though. After the first time I made a Full Reset (with the config keys) this button was inactive anymore. I recon that the keys are already deleted. But shouldn't they be redefined during Sense next start?
And I confirm the matter with softkeys. The first time I wanted to assign SenseUtil to right softkey, the "Unexpected error" appeared (right after I confirmed I was sure) and I had to kill the app. However the second time each left and right softkey worked.
But the Set (Action/Contacts) button never worked. There is always Unexpected error when I tap "OK" in the message box. Below I present the details of the error.
Code:
SenseUtil.exe
ObjectDisposedException
w System.ThrowHelper.ThrowObjectDisposedException(String objectName, ExceptionResource resource)
w Microsoft.Win32.RegistryKey.EnsureNotDisposed()
w Microsoft.Win32.RegistryKey.EnsureWriteable()
w Microsoft.Win32.RegistryKey.SetValue(String name, Object value, RegistryValueKind valueKind)
w SenseUtil.Settings.SetSoftKey(Int32 selkey, String text, String url, Boolean confirm)
w SenseUtil.SenseUtil.buttonRegDefaultSoftKey_Click(Object sender, EventArgs e)
w System.Windows.Forms.Control.OnClick(EventArgs e)
w System.Windows.Forms.Button.OnClick(EventArgs e)
w System.Windows.Forms.ButtonBase.WnProc(WM wm, Int32 wParam, Int32 lParam)
w System.Windows.Forms.Control._InternalWnProc(WM wm, Int32 wParam, Int32 lParam)
w Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain)
w System.Windows.Forms.Application.Run(Form fm)
w SenseUtil.Program.Main()
I hope this all helps. I would also like to learn programming, but it needs more time than I actually have...
Click to expand...
Click to collapse
Good testing thank you!
The config keys are only generated when you rearrange the tabs, plus I only set the enable/disable of the buttons on start up of the app and following a press.
I think I've corrected the exception, but still not 100% sure about the keys (it is enough to make it work though).
Currently reading up on xml, long over-due I learned how to use it properly! Will have a new version in a few days hopefully.
Ok read through all the material I found on xml, (a good tutorial http://www.csharpkey.com/csharp/xml/Lesson01.htm) will now find out how much isn't supported in compact .net. Fortunately no real surprises, how I've been dealing with xml has been fine (although missed a few tricks). There's also some open source solutions around which I may look into (but for this it's probably fine keeping it simple, it's more suitable for the work I'm doing with RSS feeds).
Ok, new release!
Just put in loading of the xml files which contain the tab information which can be added. Should give a good idea of how things will work!
Will add options to filter the list etc.
Will read the tab control file next, then see if I can add/remove tabs!
meltwater said:
Ok, new release!(...)
Click to expand...
Click to collapse
OK, I downloaded, unpacked, loaded on my phone and.... realized that I have Sense 2.1 currently so I won't test it at once.
But just for your info, the Stop/Start sense, and Restart works even with Sense 2.1.19202517.0
Of course in the "Tabs Loaded" I have nothing, and in "Tabs Available" everywhere I see Not Present On Device. I could only test the overall behaviour of the app but this hasn't changed much. Still the "Set" button gives me the unexpected error, so I'm useless this time.
As soon as I will flash something with Sense 2.5 I will test it immediately and report back (this unfortunately won't happen until at least tomorrow).
Sorry...
Skrobel said:
OK, I downloaded, unpacked, loaded on my phone and.... realized that I have Sense 2.1 currently so I won't test it at once.
But just for your info, the Stop/Start sense, and Restart works even with Sense 2.1.19202517.0
Of course in the "Tabs Loaded" I have nothing, and in "Tabs Available" everywhere I see Not Present On Device. I could only test the overall behaviour of the app but this hasn't changed much. Still the "Set" button gives me the unexpected error, so I'm useless this time.
As soon as I will flash something with Sense 2.5 I will test it immediately and report back (this unfortunately won't happen until at least tomorrow).
Sorry...
Click to expand...
Click to collapse
If you still have 2.1 on, does it use the tab control file in the same way?
i.e. What is the 26948339_manila file like (can you post it?).
"Tabs Loaded" does nothing at the moment anyway, not reading the file yet. The update was to put in my current work in progress.
"Tabs available" I guess the filenames are different for sense 2.1, but can't see why we can't have a set of xml files for 2.1 as well if it works in a similar way. So far I've only created files for the ones on my system and a few which I've had before, I know there are a few missing to add.
Interesting the "set" button gives an exception, thought I'd covered that on my device (will look into it).
Cheers.
meltwater said:
If you still have 2.1 on, does it use the tab control file in the same way?
i.e. What is the 26948339_manila file like (can you post it?).
"Tabs Loaded" does nothing at the moment anyway, not reading the file yet. The update was to put in my current work in progress.
"Tabs available" I guess the filenames are different for sense 2.1, but can't see why we can't have a set of xml files for 2.1 as well if it works in a similar way. So far I've only created files for the ones on my system and a few which I've had before, I know there are a few missing to add.
Interesting the "set" button gives an exception, thought I'd covered that on my device (will look into it).
Cheers.
Click to expand...
Click to collapse
Here's the Tab Control file from Manila 2.1.1920.2517. It seems to contain similar information, but it contains a LOT more . . .
NOTE: This is from the VGA ported version, but I'm sure the differences are minor (if at all) . . .
Captain_Throwback said:
Here's the Tab Control file from Manila 2.1.1920.2517. It seems to contain similar information, but it contains a LOT more . . .
NOTE: This is from the VGA ported version, but I'm sure the differences are minor (if at all) . . .
Click to expand...
Click to collapse
I would guess that 2.1 does not have the _page.xml files, since that is what the manilafull.xml file looks like, a combination of the tab control and each of the related _page.xml files! Looks like the mode9 files don't include any of the path info beyond the HTC bit, hence why the filenames are probably different.
I'll not worry too much about it for now, interesting though.
Will upload my latest, simply because I'm calling it a night... Populated Tab(Installed) page with some data from the TabControl File - note the buttons will stay disabled (only put in for layout). Oh and the url links on the Tab(Available) aren't enabled yet either.
Update on codeplex now.
This is my WVGA control file for comparison. I haven't heared about any custom tabs for Sense 2.1 so I didn't thought you would be interested in it at alll.
@meltwater:
sorry to say that, but i have all the time when i start the version 4851 an error popup. Please see the screenshot:
mike2nl said:
@meltwater:
sorry to say that, but i have all the time when i start the version 4851 an error popup. Please see the screenshot:
Click to expand...
Click to collapse
See if the version before that works (since the exception is referring to InitialiseTabLists() which hasn't changed). I added a function before InitialiseTabLists() in the latest, which loads up the sense tab control file (but doesn't seem like it is that). Anyway, will check that there is suitable checking of things to avoid the exception, still building the basics.
Hopefully next time should be able to have a go at matching the tabs found in the file with the ones loaded, then generate a new file.
Cheers
meltwater said:
See if the version before that works (since the exception is referring to InitialiseTabLists() which hasn't changed). I added a function before InitialiseTabLists() in the latest, which loads up the sense tab control file (but doesn't seem like it is that). Anyway, will check that there is suitable checking of things to avoid the exception, still building the basics.
Hopefully next time should be able to have a go at matching the tabs found in the file with the ones loaded, then generate a new file.
Cheers
Click to expand...
Click to collapse
No stress please i can wait , because i skinning the RSS tab.

WM65 (English/German) OS Builder Kitchen + ROMs for Typhoon based on Aleut's WM65 ROM

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!

[GUIDE] Android Dictionary!!

I was going through another site & came across a Terminology Guide. I couldn’t find something similar here so just wanted to take it upon myself to create a well organized post providing abbreviations & terminology so that any one, Master or Newbie, can have a quick reference guide to all things droid. I myself do not know everything but I do know some things & I believe with some help from the moderators & contributing members of xda-developers, we can throw together a one-stop-shop for all the droid info.
[FONT=&quot]A special thanks to [/FONT][FONT=&quot]Sam Fisher [/FONT][FONT=&quot]at[/FONT][FONT=&quot] droidforums [/FONT][FONT=&quot]for the inspiration[/FONT][FONT=&quot]!![/FONT]
Thanks to My_Immortal, OmegaRED^ & Spaarc for their suggestions & information shared!
________________
ADK: Android Development Kit, What people use to develop anything for the Android such as ROM's
The ADK (Android development kit) is divided into 3 parts
1. Android SDK (Software development Kit): used to make easy programs which only require touch & some sensors , e.g. Games
2. Android NDK ( Native Development Kit): this is used to Create apps which require Hardware or Use the native binaries & libraries of Android , eg. Camera , CyanogenMod Settings, Oxygen Settings , etc.
3. Android PDK ( Platform Development Kit): As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk, etc) & most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
& Also use NDK to edit the system apk's etc. to make it stable
adb: Android Debug Bridge, a command-line debugging application included with the SDK. It provides tools to browse the device, copy tools on the device, & forward ports for debugging. If you are developing in Eclipse using the ADT Plugin, adb is integrated into your development environment.
AOSP: Android Open System Project, usually you will see this term when referring to a program or ROM. This will mean that the program or ROM was taken from Google & does not contain any modifications done by the phone Manufacturer or the phone service provider. This is Android the way Google intended.
Application Programming Interface (API): An interface used by applications to communicate with each other. An API is a library that may include specification for routines, data structures, object classes, and variables. APIs are particularly useful in extending a platform.
Apps2SD: A method of storing items and Cache on the device’s microSD card, allowing you to run apps on external memory.
Boot Animation: A term for a graphical representation of the boot process of the OS. Boot animation can be a simple visualization of the scrolling boot messages in the console, or it can present graphics or some combination of both. Boot animation is not necessarily designed for marketing purposes, but can enhance the experience of the user as eye candy, or provide the user with messages to diagnose the state of the system.
Baseband or Radio: In communications & signal processing, the baseband describes signals & systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loader/SPL: In literal terms, boot loader is code that is executed before any Operating System starts to run. The concept of boot loaders is universal to virtually all Operating systems that include operating systems on your PC, laptop, Smartphone, & other such devices. Boot loaders basically package the instructions to boot operating system kernel & most of them also have their own debugging or modification environment. As the boot loader kicks off before any piece of software on your device, it makes it extremely processor specific & every motherboard has its own boot loader.
Boot Loader/SPL (Unlocked): A locked or unlocked boot loader is what gives you access to “root.” “Root” is another big word in the Android community. If you “root” a device, it means you have “super user” access or “administrator” access to the operating system that runs on your phone. Root access of your Android device gives you the ability to flash ROMs.
One of the most popular ROMs was created by a team called the CyanogenMod(CM), & their current rom is CM7, which is built on Android 2.3 Gingerbread. What this means is that if you have a phone that has an unlocked boot loader & root access, you can flash the CM7 ROM to your phone with a couple more steps. This also means that you can get access to most of the features in the latest version of Android that is commercially available, without having to wait for your manufacturer or carrier to give you an official update.
Boot Loop: Simply means something is preventing the phone from completing it's boot cycle & is stuck between the boot animation & the unlock screen, creating a looped animation. This is often fixed by either reloading a NAndroid, or Reflashing a ROM from the xRecovery/ClockworkMod Recovery/Flashtool.
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight)
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one & only reason for phones being bricked. You cannot brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into SE for repair.
How do I know the phone is hard-bricked? A hard-bricked phone cannot boot into boot loader, recovery, or into normal operation modes. You cannot connect to a hard-bricked phone via adb or fastboot. You can only see one screen on the phone & it will be the first splash screen.
Bug or Software Bug: An Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better & smoother running than others because developers have taken the time to input "perfect" code (read put in a lot of hours & hard work)
Busybox: A single multicall binary that packages the functionality of most widely used standard Unix tools, BusyBox provides a fairly complete environment for any small or embedded system.
Canvas: A drawing surface that handles compositing of the actual bits against a Bitmap or Surface object. It has methods for standard computer drawing of bitmaps, lines, circles, rectangles, text, and so on, and is bound to a Bitmap or Surface. Canvas is the simplest, easiest way to draw 2D objects on the screen. However, it does not support hardware acceleration, as OpenGL ES does. The base class is Canvas.
COMPCACHE: (compressed caching) is, in short, virtual swap, setting aside a certain percentage (usually 25%) of your RAM as 'compressed' swap. Compcache compresses the data that would normally go to swap, then moves it back into RAM, and reverses the process when moving it out of the 'compressed' swap. However, this is a classic space-time trade-off. You effectively get more RAM from the compression, but it is slower than 'normal' RAM due to the CPU time required to compress and decompress the swapped pages.
ClockworkMod: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Custom ROM: A custom ROM can range in definition from some custom code modifications to make Android run better on a device, all the way to changing the homescreen, background services, and default software.
Many software experts collaborate together in communities to build the fastest or most feature filled ROM’s. The most popular today are CyanogenMod (which supports over 70 devices!), AOKP (a lightweight ROM with plenty of customization options), and Android Revolution, a heavyweight ROM which often focusses on looking great. Just because these Android builds are made by ‘ordinary people’ and not highly paid developers at HTC or Samsung doesn’t mean they are full of bugs or risky to use. In most cases the software built by communities is ten times better. Release cycles are much shorter, fun features can be put in, and anyone can contribute an idea to the development.
DALVIK: An open source, register-based virtual machine (VM) that’s part of the Android OS. The Dalvik VM executes files in the Dalvik Executable (.dex) format, a format that is optimized for efficient storage and memory-mappable execution & relies on the Linux kernel for additional functionality like threading & low-level memory management. The virtual machine is register-based, and it can run classes compiled by a Java language compiler that have been transformed into its native format using the included "dx" tool. The Dalvik core class library is intended to provide a familiar development base for those used to programming with Java Standard Edition, but it is geared specifically to the needs of a small mobile device.
Dalvik Cache: A program cache area for the program Dalvik. Dalvik is a java based virtual machine that is the basis for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. It's similar to the prefetch files in Windows.
DDMS: Dalvik Debug Monitor Service, a GUI debugging application included with the SDK. It provides screen capture, log dump, and process examination capabilities. If you are developing in Eclipse using the ADT Plugin, DDMS is integrated into your development environment.
Deep Sleep: A state when the CPU is off, display dark, device is waiting for external input.
Density-Independent pixels (dp): A virtual pixel unit equivalent to one physical pixel on an average, “medium” density 160 dpi screen. On higher ppi screens, dp’s are scaled to retain a constant size (px = dp * (dpi/160)). For example, on a 200 dpi screen, the dp would take up 1.25 physical pixels.
Dots per inch (DPI, or dpi) is a measure of spatial video dot density, in particular the number of individual dots that can be placed in a line within the span of 1 inch (2.54 cm).
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file & put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) & to deodex services.jar, you need to deodex everything.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Drawable: A compiled visual resource that can be used as a background, title, or other part of the screen. A drawable is typically loaded into another UI element, for example as a background image. A drawable is not able to receive events, but does assign various other properties such as "state" and scheduling, to enable subclasses such as animation objects or image libraries. Many drawable objects are loaded from drawable resource files — xml or bitmap files that describe the image. Drawable resources are compiled into subclasses of android.graphics.drawable.
Fastboot: Protocol used to update the flash file system in Android devices from a host over USB. It allows flashing of unsigned partition images.
FC/FC’s: Short for “force close,” meaning an app that has crashed.
Flash: Rewrite the software/firmware on your phone using a computer to "flash" or completely rewrite the memory (ROM) of your phone. This is done using ODIN.
Flash Memory: a program technology that can be electrically erased & reprogrammed
Flashtool: It is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS or PCC. From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares). That is the core of Flashtool and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable.
Flashing: The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD Cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Hard Reset: The act of resetting your phone to its “factory” state. A hard reset erases all user data, logins, and passwords. This process may or may not erase the contents of the internal storage and/or microSD card as well.
JIT: The Just-in-Time Compiler, released with Android 2.2, it’s a method of greatly speeding up apps in Android. The JIT compiler analyzes an app’s code and converts it, allowing the app to run faster. It does all this while the application is running, hence “just in time.” The JIT compiler for Android functions with a very short “warm up” time; it doesn’t take very long to analyze the code before it starts working.
Kernel: The main component of Android operating system.
It is a bridge between applications & the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware & software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors & I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms & system calls.
Operating system tasks are done differently by different kernels, depending on their design & implementation.]
Launcher: Collectively, the part of the Android UI on the home screen that allows you to launch apps, make phone calls, etc. It is built into Android, or can be purchased in the Android Market.
Manifest File: An XML file that each application must define, to describe the application's package name, version, components (activities, intent filters, services), imported libraries, and describes the various activities, and so on. See The AndroidManifest.xml File for complete information.
Nine-patch / 9-patch / Ninepatch image: A re-sizeable bitmap resource that can be used for backgrounds or other images on the device.
Nandroid or Nandroid Backup: A file typically created in the custom recovery program, such as xRecovery, that is a carbon copy of whatever state your phone is in before a drastic change is made. The file then can be moved onto or off of the SD card for later use in case something should go wrong in the ROM or Update, or a Boot Loop occurs
ODIN: It is the program you can use to flash phones.
e.g. : 'Odin Multi-Downloader v3.95' is used to flash the Samsung Galaxy. It's usually included in firmware packs.
OEM: Original Equipment Manufacturer, the people who actually put together electronic hardware. Also refers to any equipment original to the phone, or produced by the company for the phone
OpenGL ES: A cross-platform API for full-function 2D and 3D graphics on embedded systems. Android provides OpenGL ES libraries that you can use for fast, complex 3D images. It is harder to use than a Canvas object, but better for 3D objects. The android.opengl and javax.microedition.khronos.opengles packages expose OpenGL ES functionality.
OS: Operating system, I.E. Windows Vista, LINUX or MAC or Android
OTA: Over-the-Air; method T-Mobile, & some other phone companies, uses to update Android phones. The new versions of Android are developed by Google & then released to OEM's, Sony Ericsson in our case. The OEM then writes drivers that enable the new software to work on the phone's hardware. They also develop any specialized UI (user interface), like Timescape & Mediascape, or other software they want to include. Once this is complete, they turn it over to the cell phone company, (e.g.)Tmobile, who then have to do the final checks to make sure the update works, & then distributes it over there data network using their cell transmitters.
Overclocking (OC): Speeding up the CPU past the factory presets to achieve a faster & more responsive device (prolonged run can be injurious to your device, so be careful.
Partition: The phone’s internal memory (not the SD Card) is solid-state (flash) memory. It can be partitioned much like a normal hard drive can be partitioned. On an Android device, the Bootloader exists in its own partition. Recovery is another partition; radio, system, Cache, etc. are all partitions.
Here are the standard partitions on an Android phone:
/misc – miscellaneous…
/boot – bootloader, kernel
/recovery – holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system – operating system goes here: Android, etc.
/cache – cached data from OS usage
/data – user applications, data, settings, etc.
The below partitions are not Android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio – the phone’s radio firmware, controls cellular, data, GPS, bluetooth.
/wimax – firmware for Sprint’s flavor of 4G, WiMax.
Recovery Mode: A small separate operating mode you can boost your device into, used for device administration. Two popular custom recovery modes for our device are xRecovery and ClockworkMod.
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen to icons to custom boot animation.
Root: Common word associated with giving a user "super user" access to their phones programming & other various aspects that would normally not be possible, also known as "Jailbroken" for iPhone's, "Administrator Rights" in Windows OS.
Shell or SSH: The shell is the layer of programming that understands & executes the commands a user enters. In some systems, the shell is called a command interpreter. A shell usually implies an interface with a command syntax (think of the DOS operating system & its "C:>" prompts & user commands such as "dir" & "edit"). secure shell or ssh is a network protocol that allows data to be exchanged using a secure channel between two networked devices
Soft Reset: The act of rebooting your phone, whether intentionally or otherwise, same effect as when you remove and replace the battery.
SQLite: An embedded relational database management system contained in a relatively small (~275 kB) C programming library. It is multitasking concerning reads. Writes can be done only one-at-a-time. It is a popular choice for local/client storage on web browsers. It has many bindings to programming languages. It is arguably the most widely used database engine, as it is used today by several widespread browsers, operating systems, embedded systems among others
Stock: Simply means an unaltered state, such as when you first purchase your phone from Verizon/Your Service Provider or when you repair your phone using PC Companion or SE Update Service(SEUS)
SU: "Super user", or root permissions
SWAP: is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programmed to write out very specific information, making Android's Memory Manager more efficient that swap.
Theme: A set of icons, backgrounds & app trays that change the aesthetics of the overall look of the Android & its applications. It has a set of properties (text size, background color, and so on) bundled together to define various default display settings. Android provides a few standard themes, listed in R.style (starting with "Theme_").
TWRP: TeamWin Recovery Project – or TWRP for short – is a fully touch-based custom recovery that was initially developed for Nexus devices, but has since been made available for countless other smartphones and tablets as well, in form of both official and third-party builds.
TUN/TAP: Refers to a network TUNnel, operates within layer 3 packets, or ip packets. Packets sent by a system via a TUN/TAP device are delivered to a user-space program that attaches itself to the device. A user space program may also pass packets into a TUN/TAP device. In this case TUN/TAP device delivers (or "injects") these packets to the operating system's network stack thus emulating their reception from an external source.
Underclocking(UC): Slowing down the CPU mainly to limit battery usage
Undervolting(UV): Basically keeping the clock speed same (or overclocking it) & reduce the voltage at each cpu cycle.
Updater Script: A scripting language called Edify for all Android OS since “Donut.” Updater Script is used with recovery mode, to perform a wide range of functions on files and permissions.
xRecovery: A recovery program based on the ClockworkMod Recovery sources used to apply updates, ROMs, or create a back up or restore a backup file
Zipalign: An archive alignment tool that optimizes the way a .apk is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and system much faster. Execution time is minimized for zipaligned applications, resulting is less RAM consumption when running the .apk.
File Types:
.dex: Compiled Android application code file. Android programs are compiled into .dex (Dalvik Executable) files, which are in turn zipped into a single .apk file on the device. .dex files can be created by automatically translating compiled applications written in the Java programming language.
.sbf: Summation Briefcase File
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened & inspected using common archive tools. Each Android application is compiled and packaged in a single file that includes all of the application's code (.dex files), resources, assets, and manifest file. The application package file can have any name but must use the .apk extension. For example: myExampleAppname.apk. For convenience, an application package file is often referred to as an ".apk".
.tar: Similar to a zip file(derived from tape archive), a tar file archives multiple files into one file
.tgz: TGZ files (gnu-zipped .tar file) are commonly used as install packages for Slackware Linux.
pheeeeww!!This took sometime!!
Well this is all I can think of off the top of my head but as I think of more I will edit them in here & I encourage the mods to put things that I either forgot or just simply am not aware of. Also I request fellow user to suggest any terms frequently used & not added or any discrepancies found, kindly PM me!!
Thank you & happy hacking/flashing!!
_____________________________________
X10 LED States:-
--------------------------------------
W-LOD: White LED of DEATH.
--------------------------------------
Sometimes a R-LOD is similar to a W-LOD but the LED is red instead.
Usually results in a Reboot, or a Freeze or a Crash
-------------------------------
Flashing R-L: Red LED.
-------------------------------
Led flashes RED 3 times.
Indicates Requirement for Charge
--------------------------------
G-LS: Green LED Steady.
--------------------------------
LED goes Steady GREEN while USB is plugged in.
Flash Mode Entered/Fully Charged.
CPU : -
----------------------------------------
Central Processing Unit: -
----------------------------------------
It's pretty much the heart of your device pumping data through & from all the attached devices the Kernel & Modules is its soul & it's OS is it's skin & flesh.
-----------------------
Core Clock Speed: -
-----------------------
It is the actual clock speed that the CPU is running at. "Not the multiplied speed."
It's good to remember a CPU's performance is also effected by its memory's speed.
Similar rules exist for the GPU (Graphics Processing Unit).
Nice effort! Thanks!
Although, you got the Kernel thing wrong:
kloud_ said:
Kernel: The govenor of the CPU usage and Battery output, one can upload certain Kernals to achieve greater performance speed of their device at the cost of some battery life
Click to expand...
Click to collapse
Kernel: It's the main component of Android operating system.
It is a bridge between applications and the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors and I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
Operating system tasks are done differently by different kernels, depending on their design and implementation.]
My_Immortal said:
Nice effort! Thanks!
Although, you got the Kernel thing really wrong:
Kernel: It's the main component of Android operating system.
It is a bridge between applications and the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors and I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
Operating system tasks are done differently by different kernels, depending on their design and implementation.]
Click to expand...
Click to collapse
Thanks for correcting me... got a bit distracted and thus the blunder. My bad.
Have edited the term
Good work thaks
Sent from my GT-I9000 using Tapatalk
Brilliant. Prefect for newbies. I wish there was something like this when i started lol.
Sent from my X10 TripNMiUI-1.8.19 using XDA App
kylec said:
Brilliant. Prefect for newbies. I wish there was something like this when i started lol.
Sent from my X10 TripNMiUI-1.8.19 using XDA App
Click to expand...
Click to collapse
better late than never!!
Nice work Bro, great idea, wants a sticky
colossus said:
Nice work Bro, great idea, wants a sticky
Click to expand...
Click to collapse
thanks Smarts or Colossus!
vERY nice guide
The ADK (android development kit) is divided into 3 parts
1.Android SDK (Software development Kit) : used to make easy programs which only require touch and some sensors , eg. Games
2.Android NDK ( Native Development Kit) : this is used to Create apps which require Hardware or Use the native binaries and libraries of Android , eg. Camera , CyanogenMod Settings , Oxygen Settings , etc.
3.Android PDK ( Platform Development Kit) : As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk , etc) and most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
And Also use NDK to edit the system apk's etc.. to make it stable
That's some knowledge from my side
spaarc said:
vERY nice guide
The ADK (android development kit) is divided into 3 parts
1.Android SDK (Software development Kit) : used to make easy programs which only require touch and some sensors , eg. Games
2.Android NDK ( Native Development Kit) : this is used to Create apps which require Hardware or Use the native binaries and libraries of Android , eg. Camera , CyanogenMod Settings , Oxygen Settings , etc.
3.Android PDK ( Platform Development Kit) : As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk , etc) and most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
And Also use NDK to edit the system apk's etc.. to make it stable
That's some knowledge from my side
Click to expand...
Click to collapse
Thanks Spaarc.
Will add it right away! Thanks once again
This could be called "AndroidDictionary for noobs"
Infinity Ytinifni S. Sent from Xperia X10i-modded.
X10 Led States:-
----------------------
W-Lod: White LED of DOOM.
--------------------------------------
Sometimes a R-lod is similar to a W-lod but the LED is red instead.
Usually results in a Reboot, or a Freeze or a Crash
R-R-L: Red Rolling LED.
-------------------------------
Led flashes RED 3 times.
Indicates Requirement for Charge
G-LS: Green LED Steady.
--------------------------------
LED goes Steady GREEN while usb is plugged in.
Flash Mode Entered and or Fully Charged.
Cpu's. Central Processing Unit:-
----------------------------------------
It's pretty much the heart of your device pumping data through and from all the attached devices the Kernel and Modules is it's soul and it's OS is it's skin and flesh.
Core Clock Speed:Is the actual clock speed that the CPU is running at. "not the multiplied speed."
It's good to remember a CPU's performance is also effected by it's memory's speed.
Similar rules exist for the GPU.
This place was so color less i figured i would bring some.
haha
thanks for the post OmegaRED^
thanx pretty usefull info out there.!!
Definetly a Sticky. Thanks very much!
Now I know what a "WLOD" is. I had no idea before.
Karl
i though WLOD is stand for White LED of death....just like blue screen of death for windows (but who cares...it still got same meaning anyway )
anyway...nice thread....should request for sticky
Arnold.Alexius said:
i though WLOD is stand for White LED of death....just like blue screen of death for windows (but who cares...it still got same meaning anyway )
anyway...nice thread....should request for sticky
Click to expand...
Click to collapse
Thanks... it stands for death but I liked the way it sounds so didn't change what OmegaRED^ had suggested!
A few corrections.
OTA: Over The Air.
tar: Tape ARchive - archive consisting of multiple files that has not been compressed.
tgz: compressed tarbol (tape archive) usually with gzip.
shell: the standard command language interpreter.
ssh: secure shell - provides secure encrypted communications between two untrusted hosts over an insecure network.
This was an easy explanation for all noobs, like me. Thanks
ynkamat said:
This was an easy explanation for all noobs, like me. Thanks
Click to expand...
Click to collapse
You're welcome!
Warm Regards
kLouD
Sent from my X10i on J's CM7 & DooM's v4 kernel using XDA Premium App

android dictionary

i found this in xperia x10 general section maybe we should have the same thread in our general section
[source] xperia x10 general section from kloud_
I was going through another site & came across a Terminology Guide. I couldn’t find something similar here so just wanted to take it upon myself to create a well organized post providing abbreviations & terminology so that any one, Master or Newbie, can have a quick reference guide to all things droid. I myself do not know everything but I do know some things & I believe with some help from the moderators & contributing members of xda-developers, we can throw together a one-stop-shop for all the droid info.
A special thanks to Sam Fisher at droidforums for the inspiration!!
Thanks to My_Immortal, OmegaRED^ & Spaarc for their suggestions & information shared!
________________
ADK: Android Development Kit, What people use to develop anything for the Android such as ROM's
The ADK (Android development kit) is divided into 3 parts
1. Android SDK (Software development Kit): used to make easy programs which only require touch & some sensors , e.g. Games
2. Android NDK ( Native Development Kit): this is used to Create apps which require Hardware or Use the native binaries & libraries of Android , eg. Camera , CyanogenMod Settings, Oxygen Settings , etc.
3. Android PDK ( Platform Development Kit): As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk , etc) & most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
& Also use NDK to edit the system apk's etc.. to make it stable
adb: Android Debug Bridge, a command-line debugging application included with the SDK. It provides tools to browse the device, copy tools on the device, & forward ports for debugging. If you are developing in Eclipse using the ADT Plugin, adb is integrated into your development environment.
AOSP: Android Open System Project, usually you will see this term when referring to a program or ROM. This will mean that the program or ROM was taken from Google & does not contain any modifications done by the phone Manufacturer or the phone service provider. This is Android the way Google intended.
Baseband or Radio: In communications & signal processing, the baseband describes signals & systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loader/SPL: In literal terms, boot loader is code that is executed before any Operating System starts to run. The concept of boot loaders is universal to virtually all Operating systems that includes operating systems on your PC, laptop, Smartphone, & other such devices. Boot loaders basically package the instructions to boot operating system kernel & most of them also have their own debugging or modification environment. As the boot loader kicks off before any piece of software on your device, it makes it extremely processor specific & every motherboard has its own boot loader.
Boot Loader/SPL (Unlocked): A locked or unlocked boot loader is what gives you access to “root.” “Root” is another big word in the Android community. If you “root” a device, it means you have “super user” access or “administrator” access to the operating system that runs on your phone. Root access of your Android device gives you the ability to flash ROMs.
One of the most popular ROMs was created by a team called the CyanogenMod(CM), & their current rom is CM7, which is built on Android 2.3 Gingerbread. What this means is that if you have a phone that has an unlocked boot loader & root access, you can flash the CM7 ROM to your phone with a couple more steps. This also means that you can get access to most of the features in the latest version of Android that is commercially available, without having to wait for your manufacturer or carrier to give you an official update.
Boot Loop: Simply means something is preventing the phone from completing it's boot cycle & is stuck between the boot animation & the unlock screen, creating a looped animation. This is often fixed by either reloading a NAndroid, or Reflashing a ROM from the xRecovery/ClockworkMod Recovery/Flashtool.
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight)
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one & only reason for phones being bricked. You cannot brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into SE for repair.
How do I know the phone is hard-bricked? A hard-bricked phone cannot boot into boot loader, recovery, or into normal operation modes. You cannot connect to a hard-bricked phone via adb or fastboot. You can only see one screen on the phone & it will be the first splash screen.
Bug or Software Bug: An Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better & smoother running than others because developers have taken the time to input "perfect" code (read put in a lot of hours & hard work)
Busybox: A single multicall binary that packages the functionality of most widely used standard Unix tools, BusyBox provides a fairly complete environment for any small or embedded system.
COMPCACHE: (compressed caching) is, in short, virtual swap, setting aside a certain percentage (usually 25%) of your RAM as 'compressed' swap. Compcache compresses the data that would normally go to swap, then moves it back into RAM, and reverses the process when moving it out of the 'compressed' swap. However, this is a classic space-time tradeoff. You effectively get more RAM from the compression, but it is slower than 'normal' RAM due to the CPU time required to compress and decompress the swapped pages.
ClockworkMod: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Dalvik: An open source, register-based virtual machine (VM) that’s part of the Android OS. The Dalvik VM executes files in the Dalvik Executable (.dex) format & relies on the Linux kernel for additional functionality like threading & low-level memory management. The virtual machine is register-based, and it can run classes compiled by a Java language compiler that have been transformed into its native format using the included "dx" tool.
Dalvik Cache: A program cache area for the program Dalvik. Dalvik is a java based virtual machine that is the basis for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. It's similar to the prefetch files in Windows.
DDMS: Dalvik Debug Monitor Service, a GUI debugging application included with the SDK. It provides screen capture, log dump, and process examination capabilities. If you are developing in Eclipse using the ADT Plugin, DDMS is integrated into your development environment.
Deep Sleep: A state when the CPU is off, display dark, device is waiting for external input.
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file & put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) & to deodex services.jar, you need to deodex everything.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Drawable: A compiled visual resource that can be used as a background, title, or other part of the screen. A drawable is typically loaded into another UI element, for example as a background image. A drawable is not able to receive events, but does assign various other properties such as "state" and scheduling, to enable subclasses such as animation objects or image libraries. Many drawable objects are loaded from drawable resource files — xml or bitmap files that describe the image. Drawable resources are compiled into subclasses of android.graphics.drawable. For more information about drawables and other resources.
Fastboot: Protocol used to update the flash file system in Android devices from a host over USB. It allows flashing of unsigned partition images.
Flash: Rewrite the software/firmware on your phone using a computer to "flash" or completely rewrite the memory (ROM) of your phone. This is done using ODIN.
Flash Memory: a program technology that can be electrically erased & reprogrammed
Kernel: The main component of Android operating system.
It is a bridge between applications & the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware & software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors & I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms & system calls.
Operating system tasks are done differently by different kernels, depending on their design & implementation.]
Manifest File: An XML file that each application must define, to describe the application's package name, version, components (activities, intent filters, services), imported libraries, and describes the various activities, and so on. See The AndroidManifest.xml File for complete information.
Nine-patch / 9-patch / Ninepatch image
A re-sizeable bitmap resource that can be used for backgrounds or other images on the device.
Nandroid or Nandroid Backup: A file typically created in the custom recovery program, such as xRecovery, that is a carbon copy of whatever state your phone is in before a drastic change is made. The file then can be moved onto or off of the SD card for later use in case something should go wrong in the ROM or Update, or a Boot Loop occurs
ODIN: It is the program you can use to flash phones.
e.g. : 'Odin Multi-Downloader v3.95' is used to flash the Samsung Galaxy. It's usually included in firmware packs.
OEM: Original Equipment Manufacturer, the people who actually put together electronic hardware. Also refers to any equipment original to the phone, or produced by the company for the phone
OpenGL ES: Android provides OpenGL ES libraries that you can use for fast, complex 3D images. It is harder to use than a Canvas object, but better for 3D objects. The android.opengl and javax.microedition.khronos.opengles packages expose OpenGL ES functionality.
OS: Operating system, I.E. Windows Vista, LINUX or MAC or Android
OTA: Over-the-Air; method T-Mobile, & some other phone companies, uses to update Android phones. The new versions of Android are developed by Google & then released to OEM's, Sony Ericsson in our case. The OEM then writes drivers that enable the new software to work on the phone's hardware. They also develop any specialized UI (user interface), like Timescape & Mediascape, or other software they want to include. Once this is complete, they turn it over to the cell phone company, (e.g.)Tmobile, who then have to do the final checks to make sure the update works, & then distributes it over there data network using their cell transmitters.
Overclocking (OC): Speeding up the CPU past the factory presets to achieve a faster & more responsive device (prolonged run can be injurious to your device, so be careful.)
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen to icons to custom boot animation
Root: Common word associated with giving a user "super user" access to their phones programming & other various aspects that would normally not be possible, also known as "Jailbroken" for iPhone's, "Administrator Rights" in Windows OS.
Shell or SSH: The shell is the layer of programming that understands & executes the commands a user enters. In some systems, the shell is called a command interpreter. A shell usually implies an interface with a command syntax (think of the DOS operating system & its "C:>" prompts & user commands such as "dir" & "edit"). secure shell or ssh is a network protocol that allows data to be exchanged using a secure channel between two networked devices
SQLite: An embedded relational database management system contained in a relatively small (~275 kB) C programming library. It is multitasking concerning reads. Writes can be done only one-at-a-time. It is a popular choice for local/client storage on web browsers. It has many bindings to programming languages. It is arguably the most widely used database engine, as it is used today by several widespread browsers, operating systems, embedded systems among others
Stock: Simply means an unaltered state, such as when you first purchase your phone fromVerizon/Your Service Provider or when you repair your phone using PC Companion or SE Update Service(SEUS)
SU: "Super user", or root permissions
SWAP: is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap.
Theme: A set of icons, backgrounds & app trays that change the aesthetics of the overall look of the Android & its applications. It has a set of properties (text size, background color, and so on) bundled together to define various default display settings. Android provides a few standard themes, listed in R.style (starting with "Theme_").
TUN/TAP: Refers to a network TUNnel, operates within layer 3 packets, or ip packets. Packets sent by a system via a TUN/TAP device are delivered to a user-space program that attaches itself to the device. A user space program may also pass packets into a TUN/TAP device. In this case TUN/TAP device delivers (or "injects") these packets to the operating system's network stack thus emulating their reception from an external source.
Underclocking(UC): Slowing down the CPU mainly to limit battery usage
Undervolting(UV): Basically keeping the clock speed same (or overclocking it) & reduce the voltage at each cpu cycle.
xRecovery: A recovery program based on the ClockworkMod Recovery sources used to apply updates, ROMs, or create a back up or restore a backup file
File Types:
.dex: Compiled Android application code file. Android programs are compiled into .dex (Dalvik Executable) files, which are in turn zipped into a single .apk file on the device. .dex files can be created by automatically translating compiled applications written in the Java programming language.
.sbf: Summation Briefcase File
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened & inspected using common archive tools. Each Android application is compiled and packaged in a single file that includes all of the application's code (.dex files), resources, assets, and manifest file. The application package file can have any name but must use the .apk extension. For example: myExampleAppname.apk. For convenience, an application package file is often referred to as an ".apk".
.tar: Similar to a zip file(derived from tape archive), a tar file archives multiple files into one file
.tgz: TGZ files (gnu-zipped .tar file) are commonly used as install packages for Slackware Linux.
pheeeeww!!This took sometime!!
Well this is all I can think of off the top of my head but as I think of more I will edit them in here & I encourage the mods to put things that I either forgot or just simply am not aware of. Also I request fellow user to suggest any terms frequently used & not added or any discrepancies found, kindly PM me!!
Thank you & happy hacking/flashing!!
_____________________________________
X10 LED States:-
--------------------------------------
W-LOD: White LED of DEATH.
--------------------------------------
Sometimes a R-LOD is similar to a W-LOD but the LED is red instead.
Usually results in a Reboot, or a Freeze or a Crash
-------------------------------
Flashing R-L: Red LED.
-------------------------------
Led flashes RED 3 times.
Indicates Requirement for Charge
--------------------------------
G-LS: Green LED Steady.
--------------------------------
LED goes Steady GREEN while USB is plugged in.
Flash Mode Entered/Fully Charged.
CPU : -
----------------------------------------
Central Processing Unit: -
----------------------------------------
It's pretty much the heart of your device pumping data through & from all the attached devices the Kernel & Modules is its soul & it's OS is it's skin & flesh.
-----------------------
Core Clock Speed: -
-----------------------
It is the actual clock speed that the CPU is running at. "Not the multiplied speed."
It's good to remember a CPU's performance is also effected by its memory's speed.
Similar rules exist for the GPU (Graphics Processing Unit).
Tnx for the info. This very useful specially to us noobs....
Sent from my E15i using xda premium
Everyone browse this forum must read this at least one time!!!!!!!!!!
Sent from my X8 using xda premium
AOSP: Android Open System Project, usually you will see this term when referring to a program or ROM.
Click to expand...
Click to collapse
AOSP is Android Open Source Project
posted via Tapatalk 2 Beta
Thanks for sharing.
Sent from my E15i using Tapatalk

[INFO] "New User Guide Terms Android"

we decided to extend this guide in more threads, to give new users the chance to read more easily
Hi! I saw that many (myself initially) fail to understand the discussions of various topics of modding on this and other forums because of certain terms that are now characteristic of speech in any argument.
-Android operating system for mobile devices based on Linux kernel. Android is an open source project developed by the Open Handset Alliance (OHA). Google was the first company to work on Android and HTC has designed and implemented the first Android phone.
-ADB (Android Debugging Bridge): application via command line (command prompt, DOS), is used to flash rom, make changes to the system, backup, install applications (using the command: adb push nomeapp.apk / system / app /), copy files from your device to PC (via the command: adb pull / path / inside / of / Android / filename nome_file_destinazione) and more. ADB is a tool included in the SDK of Android that allows you to manage your phone simply by connecting it via USB. For programmers, ADB is also used to execute commands on a virtual machine Android. detailed instructions.
- Apk (short for Android Package): is the file format used to install the Android software (it works similar, more or less, that is for Windows. Exe). Renaming the extension of this file. Zip you can open it with any operator of compressed files.
-App or Apps: abbreviation of the term application or applications
-App2sd (A2sd): procedure inherent in many Roma coocked, to move applications installed, or install later, the memory card instead of phone memory. to use it you must have an ext2 or ext3 or ext4 on the memory card. part of the application (the Dalvik cache) is still stored in the smartphone does not reduce the speed of execution. app2sd this is not to be confused with the various applications on the market, as those of the market allow the movement or storage of only applications that allow it.
-Bootloader (FASTBOOT): phone mode (while connected to USB mode with usb debug enabled) through which you can do many things, including obtaining root permissions, flash ROM, make backups, pushare files, remove files etc. ... the bootloader mode varies from terminal to terminal, refer to those sections for how to go into bootloader on your device.
-Brick (brickare, brickato): literally (translated in Italian) "BRICK". making the cell like a brick, a something of unusable if not as paperweights.
-Digital compass: The digital compass is able to detect the direction in which the device is pointing. This information can be used together with an appropriate mapping software to assist in navigation to unknown places.
-BusyBox: BusyBox is important because it lets you install it on your Android poteziare with many basic Linux commands. In fact, some powerful programs, such as Titanium backup and others, use busybox to carry out the instructions. In virtually a few kb there are so many beautiful little programs. guide: using titanium or backup.
-Cache: a temporary memory in which data are stored as may be eliminated without compromising the functionality of the system.
-Digital certificate: encrypted code issued to two or more parties by an authorized organization, and used to verify the identity of those parties by exchanging their public keys.
-Cupcake: Android 1.5 or relaise first official operating system pounces April 13, 2009
-Encryption: Procedure for the encoding of a systematic bit stream before transmission, aimed at avoiding that the contents can be decrypted by third parties.
Dalvik-Cache: cache used by the system to increase the execution speed of programs.
USB-Debug: mode of Android that is (turning the feature on your device via menu / settings / apps / Development / Debug USB) to allow the system to undergo special modifications.
Direct-Push Technology: Direct Push technology (push e-mail capabilities), developed by Microsoft, lets you receive new e-mail messages on their device, they are not received by your mailbox Inbox or Exchange Server. Items such as contacts, calendar and tasks are immediately updated on the device if they are changed or added on the Exchange Server.
-Emulator: it is found in the SDK and is a software that allows you to emulate (simulate) an android device. usually serves to developers (developers) to test applications.
-Digital Signature: A digital signature assures the recipient about the identity of the person who sent the file, and the absence of alterations made ​​after signing this.
-Firmware: Software comlpleto the phone, android rom often contains (the only operating system) the radio (software designed to handle all communications) and hboot (the part on the base, and boot management and partition of the phone) . The format depends on the parent company that issues them and shall be flashed through the tool or program.
-Flash (flash, flashed): install, installed.
-G. E. often written or GE (Google Experience): There are those phones that have the OS (see ROM for a definition) fully developed by Google without any addition or customization by the manufacturer that sells the device (for example the number of mobile Nexus is entirely GE). This designation often means that these phones are the first to receive updates of new versions of Android, because there being no additional software, as well as those developed by Google, the release is much quicker.
Another (more common) is that With Google.
Are those phones that despite having some customization software by the manufacturer, are fully compatible with the Google software and services with Android.
-GPRS: GPRS (General Packet Radio Systems - Radio systems for generic packages) is a data service for mobile devices. It is available for the devices that meet the GSM standard.
-GPS: GPS (Global Positioning System - Global Positioning System) is a radio navigation system based on satellites that allows the DENTIFICATION of a geographical position through a triangulation of points. The GPS is used on mobile devices for applications software for navigation.
-GSM: Short for Global System for Mobile communications (Global System for Mobile Communications), is the platform for mobile computing worldwide.
-HSDPA: HSDPA (High-Speed ​​Downlink Packet Access) is a technology for mobile devices that allows higher data speeds than traditional networks. Often referred to as 3.5G for faster downloading.
-HSPA: HSPA (High-Speed ​​Packet Access - High Speed ​​Packet Access) is a technology for mobile devices that improves the speed at which you can send and receive information on their mobile device. HSPA technology is used in 3G networks.
HSUPA: The HSUPA (High-Speed ​​Uplink Packet Access - access to packages for the high-speed) is a technology for mobile devices that provides (along with HSDPA) the possibility of having connections with fast download and upload very high by optimizing use of bandwidth.
-HVGA: The HVGA (Half-size Video Graphics Array) indicates a particular display resolution of 480 x 320 pixels.
-hboot: the part on the basis of partition and boot management and the phone
-Kernel: is the essential part of any operating system. Without going into technicalities, it manages hardware (drivers and other information about the hardware, for example). Android uses a modified Linux kernel and is entirely open source (ie source code is freely available and modifiable).
- Launcher: It 's the software that handles the desktop (icons, widgets, wallpapers etc..) Android operating system. In essence, is what appears when you access the phone after the unlock screen, called Lock Screen (see below) if it is enabled.
Android allows for excellent customization Lacuncher. Although all versions of Android will already have a default, it is possible (when this option is not blocked by the manufacturer) install as many as you want from those in the Market. Launcher The best known of those owners are not ADW Launcher, Launcher Pro, Helix Lancher.
Most producers customize more or less heavily, their phones (as long as they are not GE, see above), and modification of the launcher is usually the most common personalization. Motorola for example sviluppaMotoBlur (non-removable, and includes an additional set of changes including the Launcher), the HTC the Sense (removable; this also includes modifications to the deepest only launcher which also include the framework), Samsung TouchWiz the (removable) etc..
The change of Lacuncher makes it very often no longer available widgets developed for another Launcher.
-Leak Leaked or (escaped): this refers to the ROM or firmware that (strangely) escape to the Mother House, and is circulated on the net. are semi-official, in the sense that they are developed directly from 'manufacturer, but are not officially released (and therefore not fit to restore the guarantee of a device).
Screen-Lock or unlock screen: is the screen that appears after turning on and / or whenever you press the on / off the phone. Used to not press the keys when not using the phone. It requires a combination of specific touches, or gestures to be "removed"
-Nandroid (found in the recovery as amended): application that creates an image of the entire operating system, like norton gost and true image for windows.
-ODEX: type of compression that is used to free up memory and speed up your system. ODEX unzip the file compresses everything and creates a file. ODEX dall'apk deleting the file. dex then you end up with after launcher.apk and launcher.odex (so 'you have saved so much space and improved
the speed reading application). rom the ODEX can not be changed the subject.
-OTA: Over The Air - system that allows applications to receive updates directly from the network or system
Ext2/ext3/ext4-partition: partition on the memory card (which usually can be made using modified recovery) used to install applications on this media instead of filling up the phone memory. the ext is a type of file system used on Linux and is seen as part of the Android smartphone's internal memory. to partition the SD card in the sections and guides for your device.
-Profile A2DP: Advanced Audio Distribution profile (Advanced Audio Distribution) is a specification that refers to how two Bluetooth devices can transmit and receive streaming high quality audio. The A2DP allows the transfer of a unidirectional stream audio in stereo with two channels, such as music from one phone to a headset.
-Pull: used command in command prompt (eg adb pull / path / inside / of / Android / filename nome_file_destinazione) copy to your PC for a file or folder in the Android system.
Radio-or banda or baseband (not the FM radio): software designed to manage all the communications device (phone, wifi, bluetooth, gps, etc. ...
-Recovery: a kind of mini operating system that is used to retrieve the cell from critical situations (brick, malfunction, etc. ....), do nandroid backup, perform the wipe, flash rom coocked and file format. Zip. The Recovery is properly called Recovery Mode and means the recovery mode in which you can perform actions such as, installing updates, format the phone, format and partition the SD and more. Updating the recovery.img (you can also do without the root) with a different and we have modified provisions advanced features without having to do other steps.
-RSS: RSS (Really Simple Syndication - Guild simple): indicates an Internet protocol used to distribute information that is updated frequently, such as a blog on the Internet, audio or video broadcasts or news headlines.
-Rom: the operating system. coocked roms are usually in. zip and go through recovery flashate
Coocked-Rom: cooked rom, created by chefs (who put together parts of rom applications, modifications, patches and so on) composed and enriched with new features
-ROOT (I take verbatim from androidpedia): What is root? In Unix-like operating systems is denoted by the root user with the highest privileges, ie, system administrator, also known as super user or superuser. (Cited in Wikipedia). Android being a linux system, then the user is root, which allows you to have total control of the phone. What a privilege we have to have root permissions? We have TOTAL control of the telephone. rootare the procedure for your device varies from terminal to terminal, consult the relevant sections to find out how to make your root device ..
G-sensor (gyro): The G sensor detects the position and movement of your device. It helps to orient the display to view both vertically or horizontally depending on how you hold the device. The G-sensor can be used in games to control the actions and other applications that require a movement to be able to be activated.
-SDK (software development kit): Software development kit, which we find in the tools folder that contains the file ADB. You can download it from for all platforms (Windows, Linux, Mac OS).
-S.O. (operating system): see ROM. In fact ROM and SO tend to coincide but while the first term is used to indicate the contents of any memory or the memory itself (it is in fact for Read Only Memory), the second indicates more specifically at a very specific piece of software and not any content that a memory can accommodate.
-Streaming: The term indicates the transmission of streaming audio or digital video using the Internet.
-Superboot: method to become the superuser (root-administrator) of your smartphone, with which you can make changes to the system, such as flash ROM, modify system folders etc. ...
-Tap (capped, plugged): equivalent of left-click on PC, then click in, clicked. TAP LONG = equivalent to right click on pc
-Thetering (wifi, bluetooth and usb): Mode is a connection between the phone is another device (mostly PC), through which you can take advantage of the internet's first, and basically use it as a modem, the second ( which as I said before can be a PC or another phone yet). May be predominantly via USB connectivity, bluetooth or wifi phone.
-Tablet is a tablet device that differs from a smartphone to the screen size (usually greater than the 5 "and for its strong propensity to navigation and document management. It usually does not incorporate a module for telephone calls (one exception is the Galaxy Tab), but often have a data connection via 3G or 4G as well as the WIFI.
Google has developed a special version of Android, called HoneyComb (3.X) for release in 2011. Nevertheless, there are Tablet with Froyo.
-VGA The VGA (Video Graphics Array) indicates a resolution of the display of 640 x 480 pixels.
-WCDMA: The WCDMA (Wideband Code Division Multiple Access) is a protocol for the transmission of data in a 3G cellular network.
-WVGA: The WVGA (Wide Video Graphics Array) indicates a display resolution of 480 x 800 pixels.
Wipe Dalvik-CACHE: reset the system cache. amended by recovery takes place.
Wipe-DATE (factory reset): hard reset (reset phone to factory settings, deletes all data and applications in your phone, no memory card). some recovery in the wiping the data format factory, not a complete hard reset, but a reset of all data in your phone, for a complete hard reset you should also wipe the system and boot from the recovery of the advanced settings or proceed with the procedure manual keystroke! how to do the hard reset via keyboard shortcut see the guides in their respective sections of your smartphone.
-ZIPALIGN: A form of compression that is used to speed up execution of applications. zipalign unzip the file and aligns the compressing apk file limit so 4byte 'Android takes up less ram to read and read more' quickly and then recreates the file. apk ^ ^
If you know other terms that do not understand, this thread is yours.
P. S. I hope to be helpful
I know all of this personally but this is a very useful guide for noobs and should be made a sticky.
jonny68 said:
I know all of this personally but this is a very useful guide for noobs and should be made a sticky.
Click to expand...
Click to collapse
+1
Sticky plz
Sorry but:
-Bootloader (FASTBOOT): phone mode (while connected to USB mode with usb debug enabled)
Is wrong. Bootloader and fastboot are not the same. Also USB debugging mode is an android thing, when you are not booted into android (eg into fastboot or bootloader) then usb debugging mode is not used
rootSU said:
Sorry but:
-Bootloader (FASTBOOT): phone mode (while connected to USB mode with usb debug enabled)
Is wrong. Bootloader and fastboot are not the same. Also USB debugging mode is an android thing, when you are not booted into android (eg into fastboot or bootloader) then usb debugging mode is not used
Click to expand...
Click to collapse
This.
And debug has to do with adb not fastboot.
Sent from my GT-I9300 using xda premium
if you have to add terms or tips, write

Categories

Resources