Sharing is Caring - Caring is Helping - Helping is Sharing
{
"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"
}
Purpose of this thread is to share some useful basic information as gathered using my (rooted) HTC Desire HD, and is meant as non posting/replying reference only thread.
Thanks to all who've posted useful info, helped me with all my questions and contributed their knowledge and skills with the community.
Special thanks to Mike1986 and all ARHD team members for showing skills, respect, patience and humor.
and
BIG respect for all great people I've met on various forums and sites for making great Android ROMs, MODs Themes, Apps, Scripts etc. and for all the posts containing useful and friendly information.
Kernel: "abbreviations"
Governors:
Radio: Preferred Network types and info
RUU (ROM Upgrade Utility):
Android Partitions:
Android: Anatomy and Physiology
CID: Carrier ID (+ some codes)
GLOSSARY
Code:
[B]2G[/B]
The second generation of mobile telephony systems uses digital encoding. 2G networks support high bit rate voice, limited data communications and different levels of encryption. 2G networks include GSM, D-AMPS (TDMA) and CDMA. 2G networks can support SMS applications.
2.5G
2.5G extends 2G systems, adding features such as packet-switched connection and enhanced data rates. 2.5G networks include EDGE and GPRS. These networks support WAP, MMS, SMS mobile games, and search and directory.
[B]3G[/B]
The third generation of mobile systems provides high-speed data transmissions of 144Kbps and higher. 3G will support multimedia applications such as full-motion video, video conferencing and Internet access.
[B]4G[/B]
As of the end of 2009 it was consensus that 4G would designate Mobile Network technologies beyond 3G and its extensions "3,5G" (HSPA) , "3,75G" (HSPA+). These would logically include WiMax and LTE. In the beginning of 2011 carriers in the US started to misuse the term, advertising their HSPA networks as 4G press coverage on thisismynext Officially, the term 4G has been defined by the ITU to include LTE-Advanced and WirelessMAN-Advanced (WiMax2), none of witch are deployed anywhere still. GSMA PR
802.1X
As the IEEE standard for access control for wireless and wired LANs, 802.1x provides a means of authenticating and authorizing devices to attach to a LAN port. This standard defines the Extensible Authentication Protocol (EAP), which uses a central authentication server to authenticate each user on the network.
802.11
The IEEE standard for wireless Local Area Networks. It uses three different physical layers, 802.11a, 802.11b and 802.11g.
802.11a
Operating in the 5 GHz band, 802.11a supports a maximum theoretical data rate of 54 Mbps, but more realistically it will achieve throughput somewhere between 20 Mbps to 25 Mbps in normal traffic conditions. In a typical office environment, its maximum range is 50 meters (150 feet) at the lowest speed, but at higher speed, the range is less than 25 meters (75 feet). 802.11a has four, eight, or more channels, depending on the country. WLAN products based on 802.11a technology are rapidly coming to market in 2003, making them more affordable and widely available.
802.11b
Most WLANs deployed today use 802.11b technology, which operates in the 2.4 GHz band and supports a maximum theoretical data rate of 11 Mbps, with average throughput falling in the 4 Mbps to 6 Mbps range. In a typical office environment, its maximum range is 75 meters (250 feet) at the lowest speed, but at higher speed its range is about 30 meters (100 feet). Bluetooth devices, 2.4 GHz cordless phones and even microwave ovens are sources of interference (and thus create poor performance) for 802.11b networks. Minimizing interference can be difficult because 802.11b uses only three non-overlapping channels. 802.11b products have been shipping in quantity for several years so you will find that products are plentiful and affordable.
802.11e
802.11e provides Quality of Service (QoS) support for LAN applications, which will be critical for delay-sensitive applications such as Voice over Wireless IP (VoWIP). The standard will provide classes of service with managed levels of QoS for data, voice, and video applications.
802.11g
The 802.11 task force is still developing 802.11g, and it is expected to be ratified as a standard by mid-2003. 802.11g offers the throughput of 802.11a with the backward compatibility of 802.11b. 802.11g will operate in the 2.4 GHz band but it will deliver data rates from 6 Mbps to 54 Mbps. Like 802.11b, it will have up to three non-overlapping channels. 802.11g uses orthogonal frequency-division multiplexing (OFDM) modulation as does 802.11a, but, for backward compatibility with 11b, it also supports complementary code keying (CCK) modulation and, as an option for faster link rates, allows packet binary convolutional coding (PBCC) modulation.
Its "backward compatibility" with 802.11b means that when a mobile 802.11b device joins an 802.11g access point, all connections on that access point slow down to 802.11b speeds.
802.11h
This standard is supplementary to the MAC layer to comply with European regulations for 5GHz WLANs. European radio regulations for the 5GHz band require products to have transmission power control (TPC) and dynamic frequency selection (DFS). TPC limits the transmitted power to the minimum needed to reach the furthest user. DFS selects the radio channel at the access point to minimize interference with other systems, particularly radar. Pan-European approval of 802.11h is not expected until the end of 2003.
802.15
This IEEE working group addresses the standard for WPANs. It has four active task groups.
802.15.1 had the job of delivering the standard for low-speed, low-cost WPANs and is based on the Bluetooth spec.
The 802.15.2 task group is developing the recommended practices on how 802.11 WLANs and 802.15 WPANs can co-exist in the 2.4 GHz band. It is mainly working on the interference problem between Bluetooth and 802.11.
The 802.15.3 task group is delivering a standard for higher speed WPANs from 10 Mbps to 55 Mbps at distances less than 10 meters.
The 802.15.4 task group is preparing a standard for simple, low-cost, low-speed WPANs. Data ranges from 2 Kbps to 200 Kbps and uses DSSS modulation in the 2.4 GHz and 915 MHz ranges.
.apk or APK's
An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened and inspected using common archive tools
.tar
Similar to a zip file, a tar file archives multiple files into one file
.tgz
TGZ files are commonly used as install packages for Slackware Linux.
ActiveSync
This program by Microsoft is what we all use to connect to our computers at work or at home. It allows contacts, tasks, emails and Calendar events to be synchronised with Outlook as well as such things as media and favorites. In Windows Vista this has been replaced by the Windows Mobile Device Center. In addition ActiveSync allows browsing of the device in Windows Explorer and programs can be installed via an 'InstallShield' type package installer. AES - Advanced Encryption Standard.
Security issues are a major concern for wireless LANs. AES is the U.S. government's next-generation cryptography algorithm, which will replace DES and 3DES.
AKU
Adaptation Kit Update - Starting with Windows Mobile 5 Microsoft began a policy of updates similar to that of the desktop windows. Rather the replacing the whole OS some functionality may be added. For example AKU 2.0 introduced push mail. These updates are distributed through the OEMs and are given to the consumer in form of ROM updates. Note that OEM may choose not to create an update with the latest AKU for their devices. Getting an AKU for your phone is like getting the SP2 (Service Pack 2) for your Windows Xp.
AP - Access Point.
Wireless devices, such as laptops or PDAs, connect to a wired LAN via an AP, which is a hardware device or a computer's software that acts as a communication hub. APs provide heightened wireless security and extend the physical range of a wireless LAN.
Application Unlock
Most Windows Mobile phones only allow you to load applications that have an acceptable digital signature. If you try to edit the registry or load an application it will give you an error. Application Unlocking removes this barrier and allows you to install any application or edit the registry to your liking.
Bluetooth
A wireless technology developed by Ericsson, Intel, Nokia and Toshiba that specifies how mobile phones, computers and PDAs interconnect with each other, with computers, and with office or home phones. The technology enables data connections between electronic devices in the 2.4 GHz range. Bluetooth would replace cable or infrared connections for such devices.
Bootloader
The bootloader is the first thing to load once you turn on the device, this does the job of booting up the device hardware and loading various items into memory before the ROM starts in the device. The bootloader is also responsible for enabling the flashing of new ROMs and other components such as the Radio and the Ext_ROM. Two modified bootloaders for the Hermes are HardSPL and SSPL.
To enter the bootloader, press and hold the OK and POWER buttons while inserting the stylus into the reset hole on the bottom of the Hermes.
BREW - Binary Runtime Environment for Wireless
Developed by Qualcomm, BREW is an open source application development platform for wireless devices. BREW developers can create portable applications that work on any CDMA handset. Applications include SMS, e-mail, location positioning, games and Internet radio.
When first introduced, BREW was solely for CDMA handsets. BREW has since been enabled for GSM handsets and expects to add TDMA handsets. BREW and J2ME are competing head-to-head for the wireless application development market.
CDMA - Code Division Multiple Access
A digital wireless technology that uses a spread spectrum technique to scatter a radio signal across a wide range of frequencies. CDMA is a 2G technology. WCDMA, a 3G technology, is based on CDMA.
CDMA has multiple variants, including CDMA 1X, cdma2000, CDMA2000 1X, CDMA2000 1xEV-DO and cdmaOne.
CID
The CID (Carrier ID) of the device is a setting which determines which carrier ROMs should be allowed to run on the device. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have SuperCID which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted.
CID Unlock
Load any carrier ROM (in any language) on the device.
CLDC - Connected Limited Device Configuration
CLDC outlines the basic set of libraries and Java virtual machine features that must be present in each implementation of a J2ME environment.
Cooked
Refers to ROMs which have been modified and optimised by users to offer better performance than a carrier ROM
CustomRUU
CustomRUU is an RUU (Rom Upgrade Utility) which has support for ALL SPL versions including HardSPL and SSPL.
Dalvik (cache)
Dalvik cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the bases 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.
De-Odex
Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
EDGE - Enhanced Data GSM Environment
A 2.5G technology that enhances GSM. EDGE increases transmission speeds on GSM networks and enables the transmission of large amounts of data at 384Kbps. With EDGE, mobile operators can deliver multimedia and other broadband applications to mobile phones.
EPOC
EPOC is an operating system developed by Symbian for small, portable computer-telephones with wireless access to phone and other information services. EPOC is based on an earlier operating system from Psion, the first major manufacturer of personal digital assistants (PDAs). The term is no longer in use and is now referred to as Symbian OS.
Ext_ROM or ExtROM
The Ext_ROM (or Extended Rom) is a dedicated part of the ROM memory that is (by default) hidden to the user. This area typically includes cab files that are loaded upon Hard Reset. Also, if the author of a ROM wishes, the flashing process can preserve the Ext_Rom. This space is frequently used by carriers, or others creating ROMs, to store cabs that load settings onto the phone.
Firmware
This is a piece of software that is stored in a device to make it function. It is, unlike ordinary software, usually semi-permanent and resides in a non-volatile storage area which is unaffected by "hard resetting" a device. The term usually refers to low-level code that controls individual hardware components such as a radio rom.
Flash
Term meaning to write something (usually a ROM image) to a non-volatile chip. The term originates from original chip writers (EPROM blowers) which used to write to a chip by fusing tiny areas in the chip making individual links either short circuit or open circuit.
GPRS - General Packet Radio Service
GPRS is a radio technology for GSM networks that adds packet-switching protocols. As a 2.5G technology, GPRS enables high-speed wireless Internet and other data communications. GPRS networks can deliver SMS, MMS, email, games and WAP applications.
GPS
This stands for Global Positioning System. It is technology whereby your device communicates with satellites in orbit around the planet to determine your location within an error margin of a few meters.
GSM - Global System for Mobile communications
GSM, a 2G technology, is the de facto European standard for digital cellular telephone service, and it is also available in the Americas. GSM is the most widely used of the three digital wireless telephone technologies (TDMA, GSM and CDMA), and it supports voice, data, text messaging and cross-border roaming. The SIM (Subscriber Identification Module), a removable plastic card that contains a users data, is an essential element in a GSM network.
GSM operates in multiple frequency bands, GSM 900, GSM 1800, GSM 1900. When GSM is working on a radio frequency of 1800 MHz, it is sometimes referred to as DCS 1800, GSM1800 or PCN.
H.323
H.323 is the standard for interoperability in audio, video, and data transmissions, as well as Internet phone and Voice over IP. The standard addresses call control and management for point-to-point and multipoint conferences, as well as gateway administration of media traffic, bandwidth, and user participation.
HardSPL
This modified bootloader allows a much safer flashing process to take place since it reduces the chance of permenently bricking your HTC based device. It also removes the need to CID Unlock the device since it ALWAYS reports SuperCID when flashing.
Hard Reset
Similar to a soft reset, by performing a hard reset you completely wipe your device and restore it to the position it was in when you first turned the device on after it was purchased or after a new ROM is flashed.
HDML - Handheld Device Markup Language
Handheld Device Markup Language is used to format content for Web-enabled mobile phones. HDML allows Internet access from wireless devices and is derived from HTML. Openwave created this proprietary language, and it can only be viewed on mobile phones that use Openwave browsers.
HDML was created before a WAP standard was defined. It uses Openwave's Handheld Device Transport Protocol (HDTP) instead of WAP. HDTP - Handheld Device Transport Protocol.
This protocol is optimized for HDML. It presents the HDML to the HDML interpreter in an appropriate format.
Heimdall
is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy S device
IDEN
A specialized mobile radio network technology that combines two-way radio, telephone, text messaging and data transmission into one network.
IPL
Initial program load - usually paired with Secondary Program Load (SPL), is the boot loader of your phone, much like the BIOS is the boot loader for your PC. Note: IPL/SPL are highly hardware dependent, flashing the wrong IPL/SPL is much more serious than a flashing the wrong ROM. It may be noted that, sometimes a ROM package also contains the IPL/SPL which will be flashed into your phone. Hence be extra careful what you are flashing.
J2ME - Java 2 Micro Edition.
Java 2 Platform, Micro Edition (J2ME) is the edition of the Java platform that is targeted at small, standalone or connectable consumer and embedded devices, such as cellular phones and personal digital assistants (PDAs). The J2ME technology consists of a virtual machine and a set of APIs suitable for tailored runtime environments for these devices. The J2ME technology has two primary kinds of components--configurations and profiles.
Java
Industry standard object-oriented language and virtual machine, invented by Sun Microsystems and formally released in 1996. Some phones support downloading of Java applications over the WAP connection. Sun's Java specifications include many Java APIs and platforms, including the JavaPhone API and PersonalJava platform.
Kang
The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Kernel
The central or core software component of most operating systems. Its responsibilities include managing the system's resources (the communication between hardware and software components) and can provide the lowest-level abstraction layer for resources (especially memory, processors, and I/O devices).
Messaging
SMS (Short Message Service) is a feature available with some wireless phones that allows users to send and/or receive short alphanumeric messages.
Picture Messaging allows users to send and receive picture messages along with text. Users can choose from several preset and/or received pictures stored in their phones. Some phones also contain a picture editor.
Chat Messaging lets users "talk" using SMS messages.
MMS (Multimedia Messaging Service) is a new standard that is being defined for use in advanced wireless terminals. The service allows for non-real-time transmission of various kinds of multimedia content, such as images, audio, and video clips.
MexE - Mobile Station Application Execution Environment.
Mobile Station Application Execution Environment is a framework to ensure a predictable environment for third-party applications in GSM or UMTS handsets. MExE does this by defining different technology requirements called "classmarks." MExE classmark 1 is based on WAP, classmark 2 on PersonalJava and JavaPhone, and classmark 3 on J2ME CLDC and MIDP. Other classmarks may be defined in the future. MExE specifies additional requirements for all classmarks, for instance a security environment, capability and content negotiation, a user profile, user interface personalization, management of services and virtual home environment. A handset can support multiple classmarks.
Microbrowser
Also called a mini-browser. Software built into a wireless device that allows users to access and display specially formatted Internet content, such as stock reports, news, and sports scores using a handset device.
Mobile Information Device Profile (MIDP)
Set of Java APIs that is generally implemented on the Connected Limited Device Configuration (CLDC). It provides a basic J2ME application runtime environment targeted at mobile information devices, such as mobile phones and two-way pagers. The MIDP specification addresses issues such as user interface, persistent storage, networking, and application model.
Nandroid or Nandroid Backup:
A file typically created in the custom recovery program, such as 4EXT Recovery, that is a carbon copy of whatever state your phone is in. The file is typically stored on the SD card for later use in case something should go wrong in a ROM or Update, or a Boot Loop occurs
.NET Compact Framework
The .NET Compact framework is a smaller version of the .NET Common Language Runtime, optimized for the deployment of mobile applications running on resource-constrained devices such as PDAs. .NET CF supports only devices running Microsoft operating systems-specifically, Windows CE 3.0 (used in Pocket PC 2000 and Pocket PC 2002 platforms).
OBEX - Object Exchange
Object Exchange is a set of protocols allowing objects such as vCard contact information and vCalendar schedule entries to be exchanged using either IrDA or Bluetooth. Symbian OS implements IrDA for exchange of vCards, for example between a Nokia 9210 Communicator and an Ericsson R380 Smartphone, and vCalendar.
OS
Operating System - the platform software for your phone, much like Windows 7 for your PC. Upgrading the OS is like, in PC terms upgrading from Windows Vista to Windows 7.
OC - OverClocking
Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer
PAN - Personal Area Network
Allows devices to work together and share information and services. Using technologies such as Bluetooth, Personal Area Networks can be created in public places, in the home, in the office, in a car. This network enables everyday devices to communicate wirelessly. For example, a PAN allows users the ability to wirelessly synchronize with a desktop device to access e-mail or the Internet.
Protocol
Similar to `Radio`. Both terms refer to the radio protocol stack, which is the software which handles communications with the mobile network.
QoS - Quality of Service
Quality of Service is a measure of network performance that reflects the network's transmission quality and service availability. QoS can come in the form of traffic policy in which the transmission rates are limited, thereby guaranteeing a certain amount of bandwidth will be available to applications. Or QoS may take the form of traffic shaping, which are techniques to reserve bandwidth for applications but not guarantee its availability.
Radio
The radio stack is responsible for the phone functionality of the device. This includes GPRS, GSM, UMTS, and GPS operations. The version you use depends on who your carrier is as users have reported versions working better on one carrier than the other.
ROM - Read Only Memory
The ROM holds the Operating system and other components such as the bluetooth and wifi stacks. The ROM is accompanied by the Radio, Ext_ROM, SPL and IPL. Carriers such as T-mobile or Vodaphone taylor the ROM to their specifications and version numbers do not carry the same meaning across different carriers. IF the carrier you use supports the device well they will usually release regular ROM updates.
Root
Common word associated with giving a user "super user" access to their phones programming and other various asspects that would normaly not be possible.
RTM
Release to manufacturing or Ready to market.
RUU
The RUU (Rom Upgrade Utility) is the program which runs on the pc when a new ROM is flashed.
Sense
HTC Sense is a user interface, based on the TouchFlo 3D user interface, developed by HTC for mobile devices running Android and Windows Mobile. HTC Sense is a “design experience, an architecture that is all about how people use the device, making their content personal to how they use the device.” However, HTC has confused the issue by calling HTC Sense a user interface in press releases about the launch of the HTC Hero in India. Announced June 24, 2009, the first phone running Android to feature HTC Sense was the HTC Hero, and the first Windows Phone to feature HTC Sense (an updated TouchFlo) was the HTC HD2, announced October 6, 2009.
SIM - Subscriber Identity Module
Cellular systems using GSM technology employ SIM modules to store user provisioning information. Non-volitale storage for contact information is also available on these modules. This is also commonly used in the form `SIM unlock`. Some phones are locked to the specific telco from which you purchase your phone, eg you can't use a locked O2 phone using a Vodaphone SIM/smart card. To use SIM card from other telco, you need to SIM unlock your phone. Note: In general, the phrase 'unlock your phone' usually refers to SIM-unlock, not CID unlock.
SIM Unlock
Use any carrier's SIM in the device.
SIP - Session Initiation Protocol
SIP is the real-time communication protocol for Voice over IP (VoIP), and it has been expanded to support video and instant-messaging applications. SIP performs basic call-control tasks, such as session set up and tear down and signaling for features such as hold, caller ID and call transferring. Its functions are similar to Signaling System 7 (SS7) in standard telephony and H.323 or Media Gateway Control Protocol in IP telephony.
With SIP, most of the intelligence for call setup and features resides on the SIP device or user agent, such as an IP phone or a PC with voice or instant-messaging software. In contrast, traditional telephony or H.323-based telephony uses a model of intelligent, centralized phone switches with dumb phones.
SOAP - Simple Object Access Protocol
SOAP is a way for a program running in one kind of operating system to communicate with a program in the same or another kind of an operating system using HTTP and XML.
Soft Reset
Soft resetting the device will lose all the data currently in RAM and any unsaved information, much like pressing the reset button on your pc. A soft reset is the first thing to try if your device has stopped responding.
SPL
Secondary Program Loader. Refer to `IPL` or `Bootloader` for further information.
SU
"Super user", or root permissions
SuperCID
By CID unlocking your device the value of the CID is changed to 'SuperCID'. This allows the flashing of ANY ROM to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
UMTS - Universal Mobile Telecommunications System
The 3G mobile telephone standard in Europe, standardized by ETSI. It supports a theoretical data throughput of up to 2 Mbps. Initial trials began in 2001, and it should be rolled out in most of the world by 2005.
UV - UnderVolting
Undervolting is the process of lowering the voltage supplied to the processor in order to achieve lower temperatures and/or saving battery
VoIP - Voice Over IP
VoIP is a set of technologies that enables voice to be sent over a packet network. While few corporations use VoIP today, its usage for messaging is expected to explode in the coming two years.
Users can communicate using VoIP as easily as they do with today's PBXes and public phone network. By leveraging the existing data network, companies can save significant amounts of money by using VoIP for toll-bypass, which is particularly important for multinational corporations. VoIP will also speed the adoption of unified messaging by transmitting voice, fax and e-mail messages. VoIP is also known as IP telephony.
Over the next several years, companies will deploy VoIP in conjunction with 802.11 wireless LANs, enabling workers to have WLAN-based mobile phones when in the office.
VoWIP - Voice over Wireless IP
Combining VoIP with 802.11 wireless LANs to create a wireless telephone system for offices is an emerging market segment. VoWIP enables businesses to leverage their wireless LANs to add voice communications, enabling companies to deploy and manage voice and data over a single wireless backbone.
From a network perspective, VoWIP applications require some reservation of bandwidth to support the real-time nature of voice. Proprietary standards like Spectralink Voice Priority (SVP) are today's solution; however, the IEEE is developing the 802.11e standard for quality of service as a long-term solution.
NOTE:
Thread is under construction, so please accept my appologies regarding not finished/updated posts or typo's
No claims can be made regarding content that I share. Consider this thread as "my private reference"
Kernel: "abbreviations"
A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel on top of the existing one, effectively overwriting it.
A quick and brief overview of some kernel "abbreviations" I've found ..
OC 1.6 - Over Clock max 1,6GHz
OC+1.9 - Over Clock max 1,9GHz
2WCR - Two Way Call Recording support - now you can record incoming and outgoing calls (takes the audio direct from the chipset line in/out)
NCR - No Call Recording support
BFS - Brain **** Scheduler is a task scheduler - major performance increase over stock CFS (Completely Fair Scheduler) -> is not recommended for ROM with Sense
VIO - V(r) Input/Output scheduler - controls data input and output (memory card, disk, etc..) - stock kernel has CFQ
SLQB - a low level memory allocator/manager
MIUI - kernel for MIUI ROM
CFS - Completely Fair Scheduler
CIFS - Common Internet File System (is a virtual file system for Linux to allow access to servers and storage appliances compliant with the SNIA CIFS Specification)
TUN - VPN support
VR - I/O scheduler (better than NOOP)
NOOP - The NOOP scheduler is the simplest I/O scheduler for the Linux kernel.
VDD - Voltage Drain Drain (refers to the positive operating voltage of a field effect semiconductor device.)
NLS - National Language Support
Governors:
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies.
- ondemand -> Available in most kernels, and the default governor in most kernels.
When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative -> Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand.
Conservative provides a less responsive experience than ondemand, but can save battery.
- performance -> Available in most kernels. It will keep the CPU running at the "max" set value at all times.
This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
- powersave -> Available in some kernels. It will keep the CPU running at the "min" set value at all times.
- userspace -> This lets programs that runs on the OS decide the CPU frequency.
- interactive -> The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle.
When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
- smartass -> Is an improved version of interactive governor (Best explanation i've found paraphrases to: based on interactive, but better.)
(smartass is a "double" governor (near interactive - awake mode, near conservative (but not the same) - sleep mode), so when you use it in sleep mode, actually you use only a "half" of it.
- smoothass -> (improved smartass)
- brazilianwax -> Very agresive version of smartass
- interactiveX -> Tweaked Interactive governor by Imoseyon by adding more features like suspend/wake profile
- ondemandX -> Tweaked and ported from 2.6.38 base Ondemand governor by Imoseyon by adding more features like suspend/wake profile
It's got its own sleep profile built in, so it doesn't play well with the OC daemon ..!
- smartassV2 -> smartassV2 is generally based on the implementation of interactive with some major changes and the addition of a built in sleep profile (behaves a bit differently when screen is off vs. on).
The smartassV2 improves the very naive scheme which the first smartass had.
- lagfree -> lag free, but not that battery friendly as ondemand
Note: as far as I could find it, smartass2 = smoothass. Original it was called smartass2, but the name has been changed into smoothass.
* wake_min_freq = setting -> minimal frequency for device while it's awake
* wake_max_freq = setting -> maximal frequency for device while it's awake
* sleep_min_freq = setting -> minimal frequency for device while it's sleeping
* sleep_max_freq = setting -> maximal frequency for device while it's sleeping
* wake_governor = governor for device while it's awake
* sleep_governor = governor for device while it's sleeping
Radio: Preferred Network types and info
GSM => GSM(2G), GPRS(2.5G), EDGE(2.75G), UMTS(3G), WCDMA(3G), HSDPA(3.5G/3G+) HSUPA(3.75G) {Cell Carrier examples: AT&T and T-Mobile}
CDMA => CDMA(2/3G) EV-DO(3G) WiMax(3/4G) {Cell Carrier examples: Verizon and Sprint}
HSPA+ Evolved High Speed Packet Access (84 Mbit/s in the downlink and 22 Mbit/s in the uplink)
H: HSDPA High Speed Downlink Packet Access (Category 8 - 7.2 / Category 10 - 14,0 Mbit/s in the downlink)
H: HSUPA High Speed Uplink Packet Access (Category 6 - 5.76 Mbit/s in the uplink)
3G: UMTS Universal Mobile Telecommunications System (384 kbit/s -> (max 2 Mbit)
E: EDGE Enhanced Data Rates for GSM Evolution (384 kbit/s)
G: GPRS General Packet Radio Service (52 kbit/s)
GSM Global System for Mobile Communications (14.4 kbit/s)
Remark:
The ROM has a file called "build.prop" with various important settings in it.
One of these settings is "ro.ril.hsxpa=2", this means you (might) have/use a HSDPA/HSUPA network (also called "HSPA") with high speed downloads and uploads, and this setting gives you the "U" in the radio name found in "Settings - About phone - Software information - More - (Baseband version)"
Code:
ro.ril.hsxpa indicates hsxpa support of the target network:
#
# Network parameters
#
#ro.ril.hsxpa : inidcates hsxpa support of target network :
# 0 - UMTS r99
# 1 - HSDPA
# 2 - HSDPA/HSUPA
#
#ro.ril.gprsclass : inidcates GPRS class of target network :
# Class 2 : 3 slots : 8 - 12 kbps upload / 16 - 24 kbps download
# Class 4 : 4 slots : 8 - 12 kbps upload / 24 - 36 kbps download
# Class 6 : 4 slots : 24 - 36 kbps upload / 24 - 36 kbps download
# Class 8 : 5 slots : 8 - 12 kbps upload / 32 - 40 kbps download
# Class 10 : 5 slots : 16 - 24 kbps upload / 32 - 48 kbps download
# Class 12 : 5 slots : 32 - 48 kbps upload / 32 - 48 kbps download
#
#ro.ril.hsdpa.category :
# Cat 1 = 1.2 Mbit/s
# Cat 2 = 1.2 Mbit/s
# Cat 3 = 1.8 Mbit/s
# Cat 4 = 1.8 Mbit/s
# Cat 5 = 3.6 Mbit/s
# Cat 6 = 3.6 Mbit/s
# Cat 7 = 7.2 Mbit/s
# Cat 8 = 7.2 Mbit/s
# Cat 9 = 10.1 Mbit/s
# Cat 10 = 14.0 Mbit/s
# Cat 11 = 0.9 Mbit/s
# Cat 12 = 1.8 Mbit/s
# Cat 13 = 17.6 Mbit/s
# Cat 14 = 21.1 Mbit/s
# Cat 15 = 23.4 Mbit/s
# Cat 16 = 27.9 Mbit/s
# Cat 19 = 35.3 Mbit/s
# Cat 20 = 42.2 Mbit/s
# Cat 21 = 23.4 Mbit/s
# Cat 22 = 27.9 Mbit/s
# Cat 23 = 35.3 Mbit/s
# Cat 24 = 42.2 Mbit/s
# Cat 25 = 46.8 Mbit/s
# Cat 26 = 55.9 Mbit/s
# Cat 27 = 70.6 Mbit/s
# Cat 28 = 84.4 Mbit/s
#
#ro.ril.hsupa.category :
# Cat 1 = 0.73 Mbit/s
# Cat 2 = 1.46 Mbit/s
# Cat 3 = 1.46 Mbit/s
# Cat 4 = 2.93 Mbit/s
# Cat 5 = 2.00 Mbit/s
# Cat 6 = 5.76 Mbit/s
# Cat 7 = 11.5 Mbit/s
#
#Not speed related, but still nice to have :
#ro.ril.enable.3g.prefix : adds the 3G prefix to the operator name.
# ro.ril.enable.dtm : Only set this to 1 if your network allows simultaneous
# transfer of Circuit switched (CS) voice and Packet switched
# (PS) data over the same radio channel (ARFCN).
Preferred Network types:
WCDMA preferred - Automatically switches between G/E/3G/H based on the best/strongest signal available and is supported by all providers.
Has high battery usage since it constantly scans the network for the strongest signal to switch.
GSM only - Only uses G/E and never switches to 3G/H. Should have minimal battery usage.
(there is a problem with GSM only on some older networks... so if data is used, you can miss calls, thus GSM auto (PRL) is the safest setting)
WCDMA only - The GSM phone is capable of using only 3G data communication. When the 3G signal is too low you get nothing at all.
Only uses HSDPA and will not switch to G/E/3G even if the HSPDA signal is too low. Use this only if you use your phone in a area with good coverage. Should have moderate battery usage.
GSM auto (PRL) - Automatically switches between G/E/3G/H based on the PRL (Preferred Roaming List) for a provider on your phone.
Not supported by all providers and may not be supported in certain regions. Should have moderate battery usage since it uses a predefined list to switch.
CDMA auto (PRL) - The CDMA phone is capable of using both 2G and 3G data communication and when signal strength is low 2G is favored more.
CDMA only - The CDMA phone is capable of using only 2G data communication. When the 2G signal is too low you get nothing at all.
EvDo only - The CDMA phone is capable of using only 3G data communication. When the 3G signal is too low you get nothing at all.
GSM/CDMA auto (PRL) - Some phones are equipped with both GSM and CDMA capabilities. This setting appears to just have the phone attempt to stay connected to the data communication type that works the best.
Unknown - If none of the above fit or the phone is acting weird as far as connecting to the carrier, you will see your preferred network type is set to this
General NOTE:
If not known how to get a preferred network type, dial *#*#4636#*#* , this brings you in the "Testing" menu, select "Phone information" and scroll down to "Set preferred network type: "
Always be careful with switching to "PRL" as device issues might occur if "PRL" is not supported by your network provider !!
RUU (ROM Upgrade Utility):
A) RUU Update - Flashing Android RUU Update Using HBoot
- First you need the RUU.exe that you intend to install.
- Run the RUU as Administrator.
- Tick the 'I understand the caution indicated above...' box, and click next.
- At this point do not go any further!
- Navigate to C:\Users\xxxxx\AppData\Local\Temp (xxxxx is your user name , and ... AppData is a hidden folder)
- You should see one or two folders like this example: {E328FA5C-81C2-4B70-96AE-D5418A9A5B75}
- Go into the folder with "dotnetinstaller.exe".
- Open the next folder. (like this example: {50F2F878-636A-496F-A7CB-544C067E0C4B}
- Copy "rom.zip" into another folder (outside of temp).
- At this point just Cancel and quit the ROM Update Utility.
- Rename the "rom.zip" to "PD98IMG.zip" and put it on to the root directory of your MicroSD card in your phone.
- Shut down the phone.
- Press the Power button + Volume down button at the same time and hold them untill you get to HBOOT (white screen with skateboarding android).
- Wait for the HBOOT to parse the zip file.
- Follow the on-screen instructions and boot into newly flashed device.
B) RUU Update - Install through PC
Download and install the latest HTC Sync and restart your computer.
- Download and run the 1.15.405.1 Test RUU as Administrator. (This one is known to find the Android DHD)
- Get to the "1. Connect the Smartphone to the USB Cable" step. (but no further !!!!)
- Go to the C:\Users\xxxxx\AppData\Local\Temp directory, and find the folder with dotnetinstaller.exe and inside the next folder find the rom.zip
- Delete this "rom.zip" (which is the 1.15 version !!) and replace it with the "rom.zip" copied out earlier!!! -> See A) RUU Update - Flashing Android RUU Update Using HBoot !!!
Back to the RUU installer ...
- Now click through the next buttons.
- The RUU Utility should now be set to update. You will see the version number of the rom at the final step.
- Click update...
Android Partitions:
Android uses several partitions to organize files and folders on the device. Each of these partitions has a distinct role in the functionality of the device.
Standard internal memory partitions on Android phones and tablets:
/boot
/system
/recovery
/data
/cache
/misc
Hardware specific partitions:
(They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.)
/radio
/wimax
SD card partitions:
/sdcard
/sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices.
Purpose and contents of each of these partitions:
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the bootloader and the kernel. Without this partition, the device will simply not be able to boot.
Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the bootloader. This includes the Android user interface as well as all the system applications that come pre-installed on the device. (Sense, boot animation, busybox, etc)
Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/radio
The phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax
Firmware for Sprint's flavor of 4G, WiMax.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
Android: Anatomy and Physiology
Google IO's "Android: Anatomy and Physiology" .pdf
CID: Carrier ID (+ some codes)
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from Vodafone (Vodafone is the ‘carrier’), your phone will only accept Vodafone ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
Code:
SuperCID 11111111
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-PTB BSTAR502
Brightstar-SPA BSTAR301
Chunghwa-Taiwan CHT__601
CT HTCCN702
CU HTCCN703
DCM DOCOM801
DOPOD DOPOD701
Era T-MOB009
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-Singapore ????????
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Turkey HTC__M27
HTC-WWE HTC__001
Hutch-Australia HUTCH001
O2-DE O2___102
O2-UK O2___001
Open-Channel HTCCN701
Optus-Australia OPTUS001
ORANGE-AT ORANG113
ORANGE-BE ORANG012
ORANGE-CH-FRA ORANG203
ORANGE-CH-GER ORANG104
ORANGE-ES ORANG309
ORANGE-French ORANG202
ORANGE-PL ORANGB10
ORANGE-PO ORANG008
ORANGE-SK ORANG006
ORANGE-UK ORANG001
Rogers ROGER001
SMC-Voda-HK SMCVD001
StarHub-Singapore ????????
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMA T-MOB102
TMCZ T-MOB004
TMD T-MOB101
TMH T-MOB007
TMHR T-MOB006
TMMK T-MOBL11
TMNL T-MOB003
TMSK T-MOB008
TMUK T-MOB005
TMUS T-MOB010
TWM-TW HTC__621
VIRGIN-UK VIRGI001
VODA-Africa-South HTC__016
VODA-Australia VODAP021
VODA-Germany VODAP102
VODA-Greece VODAP006
VODA-Ireland VODAP019
VODA-Italy VODAP405
VODA-Mobilkom VODAP120
VODA-Netherland VODAPE17
VODA-New-Zealand VODAP022
VODA-Portugal VODAPD18
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-SFR VODAP203
VODA-Spain VODAP304
VODA-Swisscom-DE VODAP110
VODA-Swisscom-FR VODAP212
VODA-Swisscom-IT VODAP416
VODA-Swisscom-WWE VODAP015
VODA-TR VODAPM27
VODA-UK VODAP001
reserved for future usage 8
reserved for future usage 9
reserved for future usage 10
No questions, No comments Please
This is a refference only thread.
Thanks
Related
I've got a ppc-6601 (harrier) from Sprint and I'm trying to develop a program to use the location information - hopefully gps coords. Any idea on how to get that info? The program will basically be a location connector - converting phone location info to nmea sentences so any mapping program out there will be able to use the location info. The big question is, how do I get that info from the phone?
Is this a HTC product?
I once looked a (if I remember correctly) Swiss product that was able to show th current location based on the cell-info from the gsm radio.
The trouble seems to be that you need a map calibrated with gsm cell-info.
Remember: you wount get a more detailled specification of the location than approx. 200 metres.
I believe it's built by HTC, but branded by Audiovox. Sprint uses cdma, so the usual gsm location stuff isn't gonna work. Sprint uses the qualcomm/snaptrack technology - gpsOne. Sprint/Qualcomm got a java api out there for MIDP 2.0 phones, but I'm not sure if it'll work w/ ppc phones. This api gives you alot of info - including gps coords. http://www.shaftek.org/blog/archives/000139.html
So any ideas?
The carrier must have a location server online, currently Sprint and Verizon's LBS servers are not ready for point-to-point relay of LBS data.
An Australian based company has managed to extract this info from windows ce devices. From their web site (www.locatrix.com) it also seems as though this kind of service is supported on all mobile phones.
Pretty cool I thought.
HickHack said:
An Australian based company has managed to extract this info from windows ce devices. From their web site (www.locatrix.com) it also seems as though this kind of service is supported on all mobile phones.
Pretty cool I thought.
Click to expand...
Click to collapse
Uh, no. That program relies on tracerouting your IP address, and, if available, using their proprietary LBS API that if you want to route into GPSOne, you get to do on your own.
No, it doesn't use traceroute. I've got an i-Mate device here on Vodafone determining location to within 100m. The external API is for other/desktop applications (such as CRM, field management, mapping etc) that may wish to display the device's location.
Friends of mine have also tried their clients for Blackberry and Symbian OS with similiar results...
HickHack said:
No, it doesn't use traceroute. I've got an i-Mate device here on Vodafone determining location to within 100m. The external API is for other/desktop applications (such as CRM, field management, mapping etc) that may wish to display the device's location.
Friends of mine have also tried their clients for Blackberry and Symbian OS with similiar results...
Click to expand...
Click to collapse
Well, on the GSM side it has more options (I was referring to the Harrier and CDMA), such as locating the location of the tower and using signal fade information to make a best-guess estimate. Depending on where you live, and how close towers are spaced, it can get pretty close.
The New BT STACK(BCHS) has Release at 31 May 2006 , Can anybody find the setup file ?
the old BCHS ver.107 ( 1107 ) , See:
O2 MINI NEW BLUETOOTH STOCK.
The New one is ver.1740 , Description :
Release Description BCHS 15.1.0
Thanks !!
ps: Sorry !!! It's " Stack " , Not " Stock " ...
The Release File contains:
The 15.1 serie contains the following new features:
- The Phone Book Access Profile has been added
- The device side of the HID-profile has been added
- In the AV, FTC, OPC, BPP, CM and SC it is now possible to cancel an
action started by:
AV_CONNECT_REQ
FTC_CONNECT_REQ
OPC_CONNECT_REQ
BPP_CONNECT_REQ
CM_SDC_SEARCH_REQ
CM_SDC_UUID128_SEARCH_REQ
SC_BOND_REQ
Besides the new features a number of bugfixes has also been addressed in this release.
Below a short description of the content of the bugfixs that has been solved in this release is listed.
Release 15.1.0
--------------
Introduction
------------
The 15.1.0 release contain a number of bugfixes and improvments as liste
above.
And more old Release.......
link doesnt work....
Link brings up error "you dont not have the authorization to download this content"
I am very interested in seeing this!
It is a stack, you ...!
Hey Chatty,
i'm interested to see whether or not this updated version of the bluetooth stack (that i'm already using) has any of the bugs fixed that the original had.
If you looked at the old stack and the amount of attention it got maybe you should just let people follow what interests them and if you dont like it ... DONT READ IT!
People have the right to read what they want and say what they want! But they should be able to do it with out have someone personally attack them, ESPECIALLY IF THAT PERSON HAS NOTHING CONSTRUCTIVE TO ADD TO THE CONVERSATION!
Anyway
enjoy your night Chatty and relax a little!
we love ya anyway
Nice edit Chatty!
The Release File :
The 15.1 serie contains the following new features:
- The Phone Book Access Profile has been added
- The device side of the HID-profile has been added
- In the AV, FTC, OPC, BPP, CM and SC it is now possible to cancel an
action started by:
AV_CONNECT_REQ
FTC_CONNECT_REQ
OPC_CONNECT_REQ
BPP_CONNECT_REQ
CM_SDC_SEARCH_REQ
CM_SDC_UUID128_SEARCH_REQ
SC_BOND_REQ
Besides the new features a number of bugfixes has also been addressed in this release.
Below a short description of the content of the bugfixs that has been solved in this release is listed.
Release 15.1.0
--------------
Introduction
------------
The 15.1.0 release contain a number of bugfixes and improvments as liste
above.
Bugfixes
------------------
D-0095 Fixed problem in ./common.h with endian dependend macro's for
bytestream manipulation. The macros have been made endia
independent.
D-0307 Linux: Using BCHS in the Linux Kernel mode, the scheduler did
not correctly clean up the timed event queue upon shutdown.
D-0419 Linux: Using BCHS in the Linux User mode, the scheduler did
not correctly clean up the timed event queue upon shutdown.
D-0578 Linux: In the Linux kernel port, it must be possible to
specify an alternate panic handler, such that special
platform/application specific handling can be performed
instead of the default BCHS sched_panic() function.
D-0717 Linux: The Linux userspace USB driver must support the new
kernel-driver interfaces for Reset and EnterDFU.
D-0797 Linux: The Linux kernel USB driver supports a
non-documented customer-supplied "extra" interface to augment
the standard USB driver
D-0804 Linux: It is now possible to setup maximum number of
outstanding ISOC frames in the USB driver at runtime, instead
of having to define it at compile time.
D-0805 Linux: The Linux kernel USB driver is slow due to inefficient
URB usage pattern and too many payload copying.
D-0863 Linux: The Linux kernel driver will sometimes crash when being
unloaded.
D-0879 Linux kernel: Crashes/oopses have been seen to occur when
loading/unloading the USB driver multiple times.
D-0888 Linux: If the Linux kernel BSL (PAN) network interface was
loaded, but not configured (ie. not connected), the module
would crash on unload/unregister.
D-0901 Linux kernel: The USB driver must support the UsbDrv_Reset()
API call required by the USB interface.
D-0904 Linux kernel: The USB driver keeps too much track of the
outstanding URBs.
D-0959 All demo applications: Added "-A <bluetooth-address>" command
line argument for all demo applications. This option can be
used to skip device inquery in the demo application.
D-1017 Linux: The verify_area() Linux kernel API function has been
deprecated since at least Linux version 2.6.11 and completely
removed from at least version 2.6.14. The function access_ok()
should be used instead.
D-1082 Fixed problem in ./common.h with endian dependend macro's for
bytestream manipulation. The macros have been made endia
independent.
D-1100 OBEX/Common: Corrected miscalculation of unicode string length
D-1107 Linux USB: Fixed a problem in the Linux USB driver where a
transfer buffer was allocated based on a predefined value
instead of the value defined by the device
D-1155 BPPS: Support for mandatory features has been completed,
including status and referenced object channel has been
included.
D-1235 Linux USB: Fixed a problem in the Linux USB driver where URB's
could be leaked.
D-1238 Linux: The USB-driver can now handle a warm-reset so it is
possible to use USB ROM devices.
D-1239 Bootstrap: now possible to also use bootstrap when using USB.
A new Library is created for use with USB. The library name
is bccmd_boot_strap_usb.lib for windows and
libbccmd_boot_strap_usb.a for Linux. The old
bccmd_boot_strap-library still contains the serial boot strap
implementation.
D-1254 HFG: Disabling of status indicators using the AT+CMER is now
implemented.
D-1259 HFG: The actual status indicator values are now stored in the
HFG separately for each connection.
D-1265 Linux: The default BCHS sched_panic() now generates a kernel
stack dump when using the Linux kernel BCHS port.
D-1269 In BCHS version 15.0.0 the OBEX profiles writes the total file
size erroneous. This has now been fixed
D-1277 PAN DEMO: updated to prompt user for passkey instead of using
a fixed value.
D-1284 SBC: An overflow could occur in the decoded SBC sound
D-1432 samples, if the sound was played with maximum amplitude at the
time of encoding
D-1293 OBEX/FTC,OPC: The FTC and OPC profiles has had a general code
cleanup.
D-1297 OBEX/OPC: The prim->bodyType in the opcPutReq library function
is only assigned a value if the bodyType in the lib call is
not NULL. I.e. the bodyType contains garbage when arriving in
OPC profile resulting in a crash when OPC pfree it. This has
when fixed so the library set it to NULL.
D-1298 BPP: Could not initiate two requests on different channels at
the same time. This is now fixed.
D-1299 HFG: If the connection was disconnected during a service
search, it was not possible to initiate any further connections
from the HFG since service search resources were not released.
D-1300 Build: Problem compiling without
EXCLUDE_EXCEPTION_HANDLER_MODULE but with ENABLE_SHUTDOWN has
been solved.
D-1305 JSR82: Cancelling an inquiry through the JSR-82 layer led to a
delayed access violation in some cases, because a timed event
was not cancelled. The timed event is now removed when an
inquiry is cancelled.
D-1306 HFG: Fixed problem with Ring request
D-1310 OBEX/FTP: The FTP client API have been updated so the Get and
Put signal describes the new interface
D-1313 Linux: It is now possible to use bootstrapping when running in
the Linux User to kernel mode split.
D-1329 Changed the page scan mode to HCI_PAGE_SCAN_MODE_MANDATORY.
D-1339 Build: The WIN macro has been replaced by the build-in _WIN32
D-1340,D-1341 macro for windows builds. WIN is no longer needed.
D-1344 AV: Avoided AV forcing link to active in case of sniff request
by remote device.
D-1345 DUNC demo app.: Added menu item for hanging up a call and
updated the AT command call setup sequence
D-1350 SC: The SC module does not called sc_db_write() if the peer
device updates a link link which already exits. This has been
fixed so the sc_db_write() function is called when the link
key is updated.
D-1351 SC: If a peer device initiates a connection while the local
device is in high security mode, the class of device parameter
in a SC_BOND_IND msg is zero. A fixed has been made so this
parameter is valid in this situation.
D-1357 BCCMD: Removed memleak in SetPcmChannel
D-1360 VDP-Demo: SD_IFACEQUEUE added to tasks.c
D-1361 VDP-Demo: Alignment set to 8 byte
D-1364 Optimized the HID parser.
D-1365 HFG: When an incoming connection from a headset is initiated
at the same time of a connect request from the application it
is possible that both connections will fail.
D-1367 VDP demo: In order for properly interfacing the external video
library demuxing functions, BCHS libraries and the demo
application must be built using the same alignment as the
external library alignment. Instructions on how to do so has
been added in the demo description.
D-1371 HFG: Fixed handling of AT+CHLD=? in profile and Demo app.
D-1372 VDP Demo: ScPasskeyResSend updated to use proper result format.
D-1373 JSR82: An ill-behaved, threaded Java program could cause rfcomm
packets from the JSR-82 layer to arrive out-of-order. A message
queue has been added to handle this.
D-1374 VDP-Demo: If multiple media packets were sent in the same l2cap
packet then a temporary buffer was freed, causing an error.
This pfree has been removed.
D-1376 OBEX/OPC: If the OPC put an object which need to be spilt up in
multiple OBEX packets, the OPC is some cases keeps sending the
OBEX headers(name, type length).
D-1379 DUNC demo app.: Added response to port negotiation.
D-1380 CM: Under rare condition the Connection Manager could restore
its local queues when it is not allow to. The consequences of
this are that it can send more than one signal to the lower
layer and in worst case a dead lock could happen.
This has been fixed.
D-1381 JSR82: The inquiry procedure of the JSR-82 layer requests names
for all found devices. This has been changed to only request
names when requested from application layer.
The inquiry is now usable for selectService implemented in
upper layer.
D-1382 TCS: The SDP record of the TCS GW contained an incorrect value
of the protocol descriptor list. This incorrect value
(UUID TCS-BIN) has been changed to the correct value
(UUID TCS-BIN-CORDLESS)
D-1389 BPP: Removed potential memory leak when sending document to
printer, by pfreeing printContent.
D-1410 JSR-82: The inquiry procedure may cause a segmentation fault
if no device names are fetched during this. The event
responsible is now properly cleaned up.
D-1411 HFG-Demo: Cleaned up the handsfree demo application and removed
some macro re-definitions.
D-1416 OBEX/OPC: If the OBEX clients (FTC, OPC, BIPC) is release while
setup an OBEX connection their could go into a state where it
has not possible to make a new OBEX connection. This has now
been fixed.
D-1417 OPC: Removed potential memory leak when putting an object to
the server, by pfreeing the object received by the application.
D-1418 OPS: If an OBEX PUT packet includes a type header the OPS
profile did write an invalid byte into the OBEX PUT packet,
which made the rest of it invalid. This has now been fixed so
an invalid byte is not put into the OBEX PUT packet.
D-1420 HFG: HfgAtCmeErrorSend has been added to the Hfg-lib file.
D-1421 HFG: Library function HfgAtCopsSend now returns the correct
structure.
D-1423 BPP: Added description of docTypeLength and printContentLength
in API.
D-1424 HF: Fixed compilation problem when ADVANCED_HF was deined and
new SCO interface is used.
D-1426 BPPS: Activation issue for the BPPS profilemanager solved.
D-1428 BCSP: Fixed problem in BCSP where it was not possible to
initialise BCSP multiple times.
D-1429 Linux kernel: The USB driver should adjust the SCO packet size
after the VOICE_SETTING in usr_config.h.
D-1435 DUNC: Corrected 'maxMsgSize' assignment in the DUNC_STATUS_IND
primitive
D-1438 Handsfree: Fixed interoperability issue with some car kits that
does not follow HFP specification
D-1440 HFG: Fixed problem with incoming and outgoing connection at the
same time
D-1444 AV: Update of the AV API document so it now also states that
the AV profile supports video streaming
D-1445 AV: The description of the roleType parameter in the
AV_STATUS_IND message was wrong. This has been corrected so
the description matches the parameter
D-1446 HIDH Demo: The second parameter of the
HidhConnectAcceptReqSend(...) call in the HIDH demo is invalid.
D-1447 Handsfree: Updated default values for eSCO connections.
D-1456 AVRCP: Update of AVRCP API description, particularly connection
establishment issues.
D-1457 Build: It is now possible to compile BCHS with the
EXCLUDE_BCHS_L2CA_MODULE and/or EXCLUDE_BCHS_RFC_MODULE
compiler defines.
D-1463 BCHS: BCHS has been updated to support RFCOMM so it may be used
together with the 21d Firmware version
D-1467 AVRCP: Prevented forcing connection out of low power mode when
low power was changed by remote device
D-1473 Build: Problem compiling without
EXCLUDE_EXCEPTION_HANDLER_MODULE but with ROM_BUILD_ENABLE
has been solved.
D-1476 HFG: Transmission of callheld status indicator from the HFG is
added.
D-1477 HFG: Fixed the supported features written in service record.
D-1478 BPP-Client: Added description of
BPP_CONNECT_IND and BPP_CONNECT_RES which was missing in the
API documentation (bchs-api-023_obex_bpp_client_api)
D-1482 HFP: PICS document has been updated
D-1488 Corestack: Fixed an issue where the max_frame_size field of an
RFC_START_CFM contained the locally requested value and not the
negotiated value.
D-1489 TCS-Demo: Fixed the GW part of TCS demo application. The GW did
not respond with an alert message due to an imporperly set
variable.
D-1491 FTS: Added low power mode control.
D-1494 HFG: Updated HFG to mutually exclude RING and audio connections
for HSP according to ESR1 E2112.
D-1500 JSR82: For short local names, the JSR-82 layer would read
outside of the string, due to an incorrect cast. The name is
now copied properly.
D-1501 BPP: Made sure that BPP can be activated in NULL state.
D-1502 BPP: Only perform one SDC attribute search during BPP connect.
D-1503 BPP: Fixed problem with handling channels disconnecting in
random order in BPP.
D-1505 The following two compiler defines is added to usr_config.h:
PAGE_SCAN_TYPE
INQUIRY_SCAN_TYPE
These defines allow the customer to select which Page Scan Type
and Inquiry Scan Type BCHS is using.
D-1506 SAPS: Added Bluetooth address of remote device for incoming
connections to the SAPS_CONNECT_IND.
D-1507 BPP: Removed possibility of getting an incorrect structured
OBEX packet on the BPP Object Channel.
D-1509 TCS: Added support for the Samsung SIT105EW access point in the
terminal part of TCS
D-1515 HF: Updated API document with some missing lib. functions.
D-1516 CM: Added more error code mappings from HCI-error codes to
BCHS error codes.
D-1518 Optimized the HID parser
D-1519 HFG: Updated API document with some missing lib. functions.
D-1521 JSR-82: L2CAP connections may leave remaining data when Java
application is closed. This caused new connections in a new
Java application to fail. This data is now cleared.
D-1524 BPP: Corrected the security setting for BPP Object Channel to
none.
D-1525 Obex/Push App: Removed the references to C-code files in
profile_mangers etc. directories and insert the use of
libraries instead.
D-1526 BPP: Corrected the requested max OBEX packet size for BPP Job
and Status Channel.
D-1527 BPP: Added description of channelId and ConnectionId to
documentation of BPP_DISCONNECT_IND.
D-1530 BPP: Added extra security so BPP only accepts incoming Object
Channel connections from a connected printer.
D-1532 HFG: Fixed handling audio request when signals are crossing
D-1533 SC: The cod is zero in the SC_PASSKEY_IND and SC_BOND_IND in
the scenario where:
A successful bond has been made between dev 1) and dev 2).
If dev 2) debonds dev 1) and dev 1) afterwards initiate a
connection to dev 2) then dev 2) will initiate a new bond
sequence against dev 1) and in this case the SC_PASSKEY_IND
will popup with a cod=0 at dev 1).
This has been fixed now by adding a read to the SC_DB if cod=0.
D-1534 HFG/HF: Fixed error in SCO negotiation if application specified
eSCO parameters
D-1535 Changed default sniff mode parameters to 40 in order to follow
the BT spec.
D-1544 BIP: Optimized the BIP code and removed some bugs.
D-1545 AV,FTC,OPC,BPP,CM,SC: A new feature was been made which allowed
the application to cancel a:
AV_CONNECT_REQ
FTC_CONNECT_REQ
OPC_CONNECT_REQ
BPP_CONNECT_REQ
CM_SDC_SEARCH_REQ
CM_SDC_UUID128_SEARCH_REQ
SC_BOND_REQ
D-1547 OBEX/SYNC: Who header length corrected from (10 to 9) in the
obex-sync-server.
D-1548 The compiler define DEFAULT_LINK_SUPERVISION_TIMEOUT has been
added to usr_config.h.
This allows to adjust the default link supervision timeout for
all new ACL links created.
D-1550 OBEX/SYNC: Who header length corrected from (10 to 9) in the
obex-sync-server.
D-1552 SBC:When the SBC decoder decodes an audio signal, encoded with
max amplitude, the output signal occasionally drops to zero at
the peak values. This has been fixed now by fine tuning the
final scaling boarders.
D-1555 BPP: Fixed converter error in BPP related to getEvent,
getJobAttributes, and cancelJob, so it does not forget the
number zero.
D-1559 BCHS: Removed the use of put_message_in, put_message_at and
cancel_timed_message. These functions are planned to be removed
from the BCHS scheduler in the future (date of removal has not
been fixed yet)
D-1560 FTC: In BCHS 15.0.4 FTC always request the link to go to
ACTIVE mode even if it is already in this mode. This has been
change so FTC only request to go to ACTIVE mode if the link is
not in this mode.
D-1561 BPP: Now possible to cancel a job without getting a
disconnection in BPP.
D-1563 CM: In the situations where a peer device releases its L2CAP
connection before it has been configured, the connection
Manager (CM) could go into a state where it keeps rejecting
incoming connection attempts. This has now been fixed
D-1565 TCS: Lib functions has been updated to use bchs_msg_transport
which makes it more easy to split applications from BCHS.
D-1566 Linux: The library: sc_db-file was not built for Linux. This
has now been fixed.
D-1571 HIDD: The device side of the HID profile has now been
implemented conforming to the specifications.
D-1573 Handsfree: Memory leak when a AT command is not encoded as it
should has been fixed.
D-1576 API document updated with additional description, including
examples of how to use library functions.
D-1577 API documentation is updated with additional information on new
library functions and example on how to use all library are
added.
D-1578 PAN: Now only possible to build PAN for HCI and not RFC,
because PAN is only to be runned on HCI-builds.
D-1579 JSR-82: If the JSR-82 layer received a disconnect from the
remote device on an L2CAP connection while sending data,
it could enter a state where it would stop responding to any
signals sent to it. This issue has been cleared up.
D-1581 Handsfree: The body and the data fields are now switched so
that the contents are according to the API document.
D-1583 Handsfree: Length value of the body and the data fields is now
corrected so that the 0-terminations is also included.
D-1584 HFG: Format changed for CIND response, so that the call_setup
element is closed properly.
D-1585 HFG Demo App: OK is now send after HFG demo app has all +CLCC
results to HF.
D-1587 SDP: The SDP layer now does full comparison for 128bit UUIDS,
allowing searches for non-bluetooth (e.g. JSR-82 Java)
applications.
Note: This fix has only been applied to HCI builds.
D-1588 AV: When unregistering the service record when running as
SINK the wrong service record was used. This has now been fixed
D-1595 BCSP: Added init of timer ID to avoid cancelling already
expired timers
D-1597 HF: Fixed problem with string handling for +CLCC. and +CNUM.
D-1600 obex/fts: The connection-ID was wrongly set to 0xFFFFFFFF when
a connection was terminated. This has now been fixed so the
correct connection ID is returned.
D-1605 Handsfree: In the unsolicited +CLIP message send form the HFG a
needed space is added after the ":" so that the message now is
+CLIP: xx, where xx is a number.
D-1606 Handsfree: In different unsolicited message send form the HFG a
needed space is added after the ":" so that the message now
is +CLIP: xx, where xx is a number.
D-1608 Handsfree: The support AT-functions are corrected so that they
are according to the AT specification format.
D-1611 Handsfree: The errors in the function HfSendHfCmeeInd have been
corrected. It is not able to handle a space after :
(example:+CME ERROR: 32) and the digits send in the error code
are not mixed up any more so that a received code is send
corecltly to the app.
D-1613 Handsfree: Implemented signal interface is corrected so that
COPS function will work in HF and HFG API is updated for
HFG_COPS_RES.
D-1614 Linux kernel: The USB driver should have the functionality to
bring the interface into DFU mode.
D-1615 Changed default sniff mode parameters to 40 in order to follow
the BT spec. in the
bchs-api-005_connection_mgm_api documentation
D-1618 HF: Function HfSendClccInd is now able to handle space after :
D-1620 Linux: The userspace part of the USB driver does not support
entering DFU mode or USB reset.
D-1622 Phone Book Access Profile is implemented according version 1.0
of the specification.
The profile has two modules:
PAC is the client side e.g. Car kits
PAS is server side e.g. Mobile phones.
D-1628 BCHS has now been updated to support the BC3MM AV-router
v1.2.2 solution.
D-1630 SPP: Made API for changing low power mode on SPP connections
D-1632 SBC: The SBC decoder has undergone a minor optimization round
to improve the general decoder MIPS performance.
D-1634 CM: If the Connection Manager(CM) receives an incoming L2CAP
connection while the local message l2cap_connect_accept_req is
stored on a local queue, the CM will reject the incoming L2CAP
connection.
This has been changes so if a l2cap_connect_accept_req message
is stored the incoming L2CAP connection is also stored. In this
way the CM will not reject it.
D-1636 BPP: A cancel connect attempt can no longer result in a
BPP_CLOSE_SEARCH_IND.
D-1637 BPP: Made sure that the abort timer is cancelled if a
disconnection happens simultaneous.
D-1641 BPP: Fixed problem with uninitialised memory when using Object
Channel.
D-1642 FTS now sends CmModeChangeReq (for LINK_STATUS_CONNECTED)ONLY
once on rx of CM_DATA_IND while NOT in LINK_STATUS_CONNECTED
and obex is connected.
D-1644 FTS now sends CmModeChangeReq (for LINK_STATUS_CONNECTED)ONLY
once on rx of CM_DATA_IND while NOT in LINK_STATUS_CONNECTED
and obex is connected.
D-1647 Linux: The Linux userspace UART driver now correctly perform
the pthread shutdown sequence.
D-1648 In BCHS 15.0.5 FTC will request the link to go to ACTIVE mode
even if it is already in this mode. This only happens if FTC
receives a FTC_CANCEL_CONNECT_REQ in connected state.
This has been change so FTC only request to go to ACTIVE mode
if the link is not in this mode.
D-1649 Linux USB: A memory leak has been found in the Linux userspace
USB driver in the UsbDrv_Rx() function, where the rx-queue
element itself was not freed after the data has been send to
the stack.
D-1655 Linux user: The USB driver does not use the correct pthread
shutdown sequence.
D-1659 PAC: Added handling for low power mode and cancel connect.
D-1664 HIDH: solved free of non allocated data
D-1665 SPP Demo App: mapping between client and instance number made
more intuitive
D-1672 SAP: Updated Service record for SAP server to be compatible
with WinCE devices
D-1673 FTC: FTC accidently uses more than one timer to control
lowpower. This has been fixed so FTC only use one timer to
control this.
D-1674 HIDH: When calling HIDHConnectReqSend(..) with SdpInfo as a
NULL pointer undefined Memory access is read. This has now been
fixed.
D-1677 HFG: New signal "HFG_STATUS_INDICATOR_SET_REQ" is created to
enable the application to update the actual status indicator on
all link at the same time and in any state of the HFG.
D-1679 AV: Av app. will now receive a negative connect confirm also
when a cancel connect arrives too late to make actual cancel -
when the connection establishement is done but has not yet been
reported to app.
D-1680 An incorrect offset calculation that caused searches for more
than one 128 bit UUID to fail has been fixed.
Note: This fix has only been applied to HCI builds.
D-1681 HIDH: When HIDH luses the connection and should automatically
reconnect. If the reconnect fails, a HIDH_CONNECT_CFM is send
to the application instead of a HIDH_DISCONNECT_IND. This is
Fixed.
D-1682 HIDH: A problem in the HIDH package fragmentation routing which
did not work for packages larger than the MTU size has been
fixed.
D-1685 OBEX: Optimize the OBEX profiles so the clients release the
connection and the servers send a response code with error, if
the peer device sends an OBEX packet larger than agree on.
D-1688 TCS: Doing shutdown the tcs_deinit function did not pfree the
payload in a CM_L2CA_CONNECTIONLESS_DATA_IND_T message, causing
a potential memory leak. This has now been fixed.
D-1691 HIDH: Problems with Connect Accept and Reconnect Flag and
Virtual Cable Flag are True and Normally Connectable Flag is
False. This has been fixed.
D-1694 HIDH: Fixed a memory leak in HIDH which occured when packages
bigger that the MTU size was send. The user payload was then
not free'ed. This is now free'ed.
D-1704 OBEX documentation: Added connected state to the sequence
overview diagram.
D-1740 CM: In BCHS 15.0.6 TCS_IFACEQUEUE were hardcoded into the
Connection Manager (CM). If TCS_IFACEQUEUE were removed from
the bchs_task.h bchs could not compile.
This has now been fixed.
quite list there! will be interesting to see what the possibilities for the magician shall be!
Thanks for the heads up and i look forward to reading more
now to wait for the cab file...
The most important question for me: Will the modem work now?
Good!
Only two questions:
1) When it can be downloaded? From where?
2) That HUGE list of improvements it's really confusing. What is this new stack going to do respect the previous? It's worth install it?
Really thanks to people like wensonlau that discover interessant unpgrades to the magician
Cheers, MocciJ
still no working download to this hotly anticpated release?
What a pity... no one got access.
Was hoping this would make my Magaician work better with my Pioneer Bluetooth head unit....damn dissapointed it hasn't emerged.
UP
where?
I didn't say, I uploaded it. I just meant to put this thread to the top.
Can Anybody please tell me if this works fro Prophet (Xda neo), too ?
I have some Problems with my HT-820....
@meisterlampe2000: just try the older version and you'll know. Or just read the thread about the old version. How to find it? Use the SEARCH function!
SO kind of you !
I`ve read everything now, didn`t expect a different answer from you !
I hope to find a Link to that new Stack soon - Would be nice to listen to Music withoput interruptions.
THX
I think we need to start a thread to start investigating how to improve our data speeds on the networks we have (besides the PRL updates and VZ roaming that works for some people). A lot of ppl don't get 4g speeds where they live and get weak 3G speeds despite having strong connections.
I've done some research and I've found data hacks for other types of smart phones and I just wonder if any of these concepts could translate over to the Evo in some way, shape, or form:
Windows Mobile registry tweaks:
http://forum.ppcgeeks.com/showthread.php?t=110288
http://forum.ppcgeeks.com/showthread.php?t=63811
Notes: Obviously Android does not have a registry system like Windows based systems, but might these settings corrolate to other system files?
Palm Pre ##data# Tweaks:
http://forums.precentral.net/palm-p...6242-increase-speed-your-evdo-connection.html
Notes: I haven't been able to find the buffer settings they refer to in any of the ## command menus
G1/Hero (GSM) Data Tweaks to build.prop:
http://forum.xda-developers.com/showthread.php?t=595108
Notes: Again all of these tweaks are for GSM networks but might have comparable settings in CDMA
Thoughts?
252 views, not one post?? Maybe this should be in android development?
Intel / Infineon XMM6260 & X-GOLD 626 Modem Hack-Pack Release!
After several unsuccessful months of trying to get my phone (application) to
talk AT-commands with the baseband processor (BP), I've had to learn a lot of
hardware and internal Android and OEM based tricks and secrets. Although this
have not been enough to make anything of practical use, it is definitely worth
sharing. If not at least some more talented people may be able to continue
where I have left of...
Now, it should be immediately stated that there is nothing revolutionary
in here, apart the Infineon manual for tuning your GSM modem, using the
AT CLI and GTI sequencer. This is something that could potentially be very
useful for better understanding the advanced features that the modem
platform incorporates. However, it is also a sure way of making a an
expensive brick out of your phone! You have been warned...
Brief Modem Description
The XMM6260 is the "platform" that consists of:
The X-GOLD 626 baseband processor
The SMARTi UE2 RF-transceiver DSP
The 3GPP Release 7 HSPA+ protocol stack with:
Downlink: Category 14, Uplink: Category 7
The X-GOLD 626 baseband processor (labelled "PMB 9811") is communicating
with the DSP RF-tranceiver chip called SMARTi-UE2 (labelled "PBM 5712 A1"),
using a communication interface that corresponds to the MIPI DigRF-3G
(V.3.09) standard. Through this protocol the BP can control some or all
aspects of the RF DSP.
Alternative Names
Infineon IFX6260
Intel IMC6260
Intel XMM626
Some other devices using this platform:
Code:
- Lava XOLO X900 [Phone] FCC ID: ???
- Lenovo K800 [Tablet/Pad] FCC ID: ???
- LG-P920 (LG ?) [Phone] FCC ID: BEJP920
- LG-P925 (LG Optimus 3D?) [Phone] FCC ID: BEJP925
- Huawei E369 (3G Hi-Universe) [USB 3G Modem] FCC ID: QISE369 (Russian distrubutor: Merlion)
- Huawei MU733/MU739 [PC/CE Module] FCC ID: QISMU739
- Samsung Galaxy Nexus (I9200) [Phone] FCC ID: ???
Other devices that may (!?) also contain the X-GOLD 626:
---------------------------------------------------------
- LG Optimus 4X HD [Phone] FCC ID: ???
- HTC One X [Phone] FCC ID: ???
- Huawei Ascend D Quad [Phone] FCC ID: QIS ???
- Huawei E392 (E392u-511) [LTE Multi-mode USB stick] FCC ID: QISE392U-511
- Huawei E353 (E352s-6) [HSPA+ USB stick] FCC ID: QIS ???
Hack-Pack Content
Code:
- Pictures/Diagrams:
- XMM6260 colored pinout map
- XMM6260 mounted in a Samsung Galaxy S2
- SMARTi UE DSP RF-tranceiver chip mounted in the SGS-2
- IPC xxxxxx stuff
- Infineon PhoneTools testing program
- Raw 1byte greyscale PNG of modem.bin from XXKI1
- PDF files/documents:
- ITA-RF-Adjustment-GSM (XMM6260 Specification)
- Infineon MIPI-HSI Product Brief
- X-GOLD 616 Product Brief
- Fairchild FSA9280/88A USB/UART switch/MUX datasheet
- Similar Modem AT sets/documents:
- AT_Command_Set_3GPP-TS-27007-940.pdf
- AT_Command_Set_AMOD_HSPA.pdf
- AT_Command_Set_Gobi.pdf
- AT_Command_Set_Motorola_XM7200S.pdf
- AT_Command_Set_Teltonika_TM3.pdf
- AT_Command_Set_iWOW_TR-900.pdf
- Text Files:
- 3GPP 27.007 AT-list
- XMM6260 official AT-set
- XMM6260 internal AT-set
- XMM6260 homebrew specifications
+ X-GOLD 626 Modem pinouts
+ MUX pinouts
+ AP connections (SGS2)
+ AP relevant info
- Strings of modem.bin (stock firmware image: [B]XXKI1[/B])
- Strings of drexe
- Strings of rild
- Strings of libril.so
- Strings of libsec-ril.so
- GT-I9100 stock (GB 2.3.4) binary files:
(Taken from: PDA:[B]XWKI4[/B], Phone:[B]XXKI1[/B])
- libKiesDataRouter.so
- libril.so
- libsec-ril.so
- libsecril-client.so
- drexe
- rild
- Android hardware hacking binaries (tools):
- dbus-monitor
- dbus-send
- hciconfig
- hcidump
- hcitool
- i2cdetect
- i2cdump
- i2cget
- i2cset
- ipcfilter
- ipcdump
- ipctool
- procmem
- showmap
- showslab
- strace
- tcpdump
- viewmem
+ various other content
Download Here! (57.72 MB)
The modem firmware referred to and studied can be
found here (Modem.bin.7z) or here, under "XXKI1".-------------------------------------------------------------------------------
DISCLAIMER:
All the material in this collection was found on internet by
appropriate Google-Fu and/or by laborious manual creation.
Nothing is stolen or reversed, so I am not held responsible
for the origin or problems affiliated with the use of these
documents, programs or other binaries.
-------------------------------------------------------------------------------
If you are a developer or other corporate official of Intel or Infineon:
Please contact your superiors and ask them to release the proper
datasheets and documentation of these products to the public.
Why? Because:
It would significantly increase the sales of your hardware, by promoting
a much more open approach to hardware development. There are currently
more than 10 open-sourced and open-hardware smartphone projects around
the world, who would benefit from the use of a more modern baseband than
what is currently and openly available.
.
It would significantly promote your hardware in front of your competitors,
as your company would be the first one to open up your documentation to the
public. Thus increasing public technical knowledge of your hardware, which
would ultimately lead to you having an easier time to find qualified
developers that cost you less!
.
It would significantly reduce the cost and time for firmware development,
while increasing the firmware code-quality and compatibility, as you
would be able to benefit from the large community and knowledge from
other professional developers as well as hardware-hackers.
(Yes, there are several bugs found in your firmware, but since there is
no way to report and discuss these with your developers, they will
continue to cost you money and head-scratching for all developers
having to deal with your platform.)
.
Your competitive advantage due to 1-3, would promote new and better
future hardware developments, that would not only benefit your
company/business but also society as a whole.
.
Its simply the right thing to do!
The thread where all this become crisply relevant is this one:
[A][SGS2][Serial] How to talk to the Modem with AT commands
There you will find all documents which I have found to date, which
is essentially none. At least nothing that can be of ANY practical use.
UPDATE: [2012-04-17]
As soon as I get a chance I'll update the HackPack (HP) with new data regarding the MUX
and some other hardware used in the SGS2. This data, as presented within HP, is simply wrong!
Reserved 2 me 3
Awesome info I was also thinking looking at the ServiceMode application in the SGS2 could provide interesting information. BTW, do you know if the X-GOLD has a diagnostic mode similar to the one usually found in Qualcomm modems?
xd.bx said:
Awesome info I was also thinking looking at the ServiceMode application in the SGS2 could provide interesting information. BTW, do you know if the X-GOLD has a diagnostic mode similar to the one usually found in Qualcomm modems?
Click to expand...
Click to collapse
Thanks! The ServiceMode app is mostly interesting because its code actually reside inside the Modem firmware, where the java app is acting as a wrapper. I'm not familiar with the Qualcomm modems, could you elaborate on what that "diagnostic mode" does? (The x-gold firmware is FULL of various modes. Just depends on what you want to do, and to get the proper documentation on how to use it!)
Just found ... a bit older, but still very interesting
http://hwplatform.googlecode.com/svn/trunk/Infineon/
RNC States from libsec-ril.so
Hi
Very valuable information! Does anyone have an idea about how to get the information displayed from serviceMode programatically? Looks like most of it is being polled directly to the libsec-ril.so. In my case I'm interested in obtaining information about the RNC states on the handset
Thanks for this information
Thanks for the info E:V:A. I did quite some figuring out about the Radio/DSP unit of the Nokia DCT3 back in the day and also the GSM protocol (anyone remember Project Blacksphere / OpenGPA?).
Things have likely come a long way since then. One thing that is clearly different is that the baseband processor is completely isolated from the application processor. In the DCT3 there was one ARM processor that drove both the user interface and parts of the GSM protocol, and connected to a DSP for the low-level radio stuff.
I wonder how other things have changed with 3G. I may get back in the game. This will give me an headstart
Memory map and boot process
It appears that modem.bin consists of multiple partitions that are loaded separately at bootup of the device, reflecting the modem boot up sequence in libsec-ril.so:
Code:
Offset Size Address Description
0x000000 0x00f000 0x00800000 PSI
0x00f000 0x019000 0x60000000? EBL
0x028000 0x9d8000 0x60300000 Main image
0x9ff800 0x000800 Used for verification (buliding ReqSecStart command)?
0xa00000 0x200000 0x60e80000 NV data (file contains default data)
0xc00000 0x000200 Unused?
Offset is offset in file, address is flash/ram offset on device. Whereabouts about the EBL are a bit unknown, address 0x60000000 is based on a guess the others are sure.
Also I did an attempt at constructing the run-time memory map of the device, based on static analysis but as I've not found a way yet to actually probe it there are quite a few question marks.
Code:
Device memory map:
0x00000000 RAM/ROM? (what is here?)
0x00080000 PSI bootloader *RAM*
0x40000000 Flash (what is flashed here?)
0x60000000? Code (EBL)
0x60100000 Flash
0x60300000 Code (Flash)
0x60e80000 NVram data (Flash)
0xe0000000 Peripheral mapping for memory-mapped I/O (256MB)
0xffff0000 Memory (initial stack)
As for I/O devices in peripheral mapping, my understanding is still very limited and based on the bootloader only. I have a longer list of addresses from static analysis, but as I can't yet label anything it is pointless to publish. As usual, the upper bits (how many? 8?) select which peripheral, the lower bits (20?) select a port within that peripheral.
Code:
0xe4d00164 ? status bits
0xe4d00384 ? status bits
0xe8000070 ? status bits
Entry points:
Code:
Offset Address Description
0x000000 0x00080000 Boot loader
0x00f400 0x60000000? EBL
0x1a8000 0x60480000 Main stack
I'm trying to run this in QEMU and created a basic environment, but as my understanding of ARM kernel space (interrupt handling, timers, etc) is very limited, it currently gets stuck in a loop waiting for some other thread (or interrupt handler) to update an address.
just thought it might be of interest and help - http---en.samaanet.com/?p=2390
direct link:
http://en.samaanet.com/?p=2390
Polarfuchs said:
direct link:
http://en.samaanet.com/?p=2390
Click to expand...
Click to collapse
That's a direct rip-off of my XDA thread!
Any more posts with such links will be removed!
How should I know, I just posted the link as "service" because the user above me could't post links.
I've been informed that the download link doesn't work. i will upload again as soon as I have time...
Really interesting stuff you have got here.
One thing I've been searching for a while now: I own a Galaxy Nexus, which has a XMM6260 modem. Samsung had on their stock ROM a feature in service mode where you can check the power modes of the 3G data connection. Since the Galaxy S2 has the same modem, thus it should be possible to get that feature.
I'm interested in this stuff because my Galaxy Nexus likes to drain like crazy on the 3G network that I use and I suspect that it has to do with the 3G data power modes. 3G+wifi is extremely efficient in power use but 3G+mobile date is al big battery hog.
I hope you post a working link soon, than I can start reading this stuff.
Seems like this might be the best place to ask this... I also asked in the "fun with AT commands" thread so my apologies up front for the spam.
I'm looking for a fastboot friendly radio baseband I can flash with a 4.2.1 friendly RIL. This may be more than what I actually need but I've got a full telephony build of the Nexus 7 3G going and while SMS and MMS are fully functional I'm getting a CME ERROR: 4 when I try to do voice dialing and don't see anything coming in via logcat on an inbound call.
The mobile plan I'm using is full voice capable and verified as functional.
Doing a strings of the included RIL (libxgold-ril.so) shows all the necessary voice functions listed (although I guess this could be a false positive if it is interface based).
The modem mounts up on /dev/ttyACM0 and I'm able to do all the basics with radiooptions, except voice dialing and answering of course.
Any pointers / advice / direction would be greatly appreciated... coming up to speed real quick in this area.
XGold626 One X Pinout
I have removed my BB CPU and here is the pinout if it helps anyone
How to start?
I'm a rookie so is anyone can provide a step-by-step tutorial about how to send AT commands to the baseband processor directly? Right now I only can use i2cdetect to list i2c channels, but how to do next?
Thanks,
Andong
XGold 626 Reversing
witchspace said:
It appears that modem.bin consists of multiple partitions that are loaded separately at bootup of the device, reflecting the modem boot up sequence in libsec-ril.so:
[snip]
Click to expand...
Click to collapse
Hi!
Nice work. I'm working on reversing the xgold626 baseband as well. Specifically, I'm looking at the NELK2 baseband for my GT-i9300.
Perhaps we could join forces? Anyone else working on reversing the xgold626 baseband is welcome to contact me as well.
I'm reachable at: je at clevcode.org, or on my ircd (irc.clevcode.org, port 7000, SSL, nick je).
Cheers,
Joel
witchspace said:
It appears that modem.bin consists of multiple partitions that are loaded separately at bootup of the device, reflecting the modem boot up sequence in libsec-ril.so:...
I'm trying to run this in QEMU and created a basic environment, but as my understanding of ARM kernel space (interrupt handling, timers, etc) is very limited, it currently gets stuck in a loop waiting for some other thread (or interrupt handler) to update an address.
Click to expand...
Click to collapse
clevcoder said:
Specifically, I'm looking at the NELK2 baseband for my GT-i9300. Perhaps we could join forces? Anyone else working on reversing the xgold626 baseband is welcome to contact me as well.
Click to expand...
Click to collapse
Yep, that is very interesting. Send me PM if there are more interest in pursuing this further! What's the primary interest of doing this?
Hi!
Hopefully you have heard of a new security hole called POODLE in SSL.
If not, click here!
How can you secure your Windows Phone? Here's the answer!
You need:
A interop unlocked Windows Phone
A registry editor on your phone
Follow those steps:
Start Internet Explorer on your Phone and navigate to https://www.ssllabs.com/ssltest/viewMyClient.html
You will see what protocols are supported by your browser. close Internet explorer (hold back key and close, not just minimize)
Fire up your registry editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
Change the value SecureProtocols to 32. Create this value if it doesn't exist.
Start Internet Explorer again and navigate to the page mentioned in Step 1. Look for supported protocols, it should display only SSL 3.0 - IT WERKS! Close IE again.
Now set the value SecureProtocols to 2688. This enables TLS 1.0/1.1/1.2 and disables SSL 2.0/3.0.
Start Internet Explorer again and navigate to the page mentioned in Step 1. Look for supported protocols, it should display TLS 1.0, 1.1, 1.2 AND SSL 3.0. Because the server is configured to downgrade to SSL 3.0, if TLS isn't supported. This may change in the future (hopefully).
Possible Values for SecureProtocols:
SSL 2.0 - 8 - 0x0008 (not supported on many websites, not recommended)
SSL 3.0 - 32 - 0x0020
TLS 1.0 - 128 - 0x0080
TLS 1.1 - 512 - 0x0200
TLS 1.2 - 2048 - 0x0800http://forum.xda-developers.com/#
2688 = 128 + 512 + 2048 = TLS 1.0 + TLS 1.1 + TLS 1.2
Tested on a Samsung ATIV S GT-I8750 using IO Explorer and WPHTweaks.
Thanks to
-W_O_L_F- and WindowsMania.pl for their excellent cutom ROMs
Jaxbot and Jessenic for the WPHTweaks App
contable for the IO Explorer App
and everyone involved in the great Windows Mobile and Windows Phone development and hacking community
and every member of XDA of course
Best regards,
Mr nUUb
EDIT: visit poodletest.com, it displays different images for SSL and TLS.
EDIT 2: Opera mini (beta) is not vulnerable.
Great guide. However, if the phone will still downgrade to SSL3 - that is, if you can't turn *off* SSLv3 - then you aren't safe. That's about half of the point of POODLE; it's possible to force most browsers and servers to downgrade to the obsolete protocol by just closing any connection attempts that report support for a newer version.
EDIT: Make darn sure you do *not* leave that option set to 32 (0x20, SSLv3 only)! That will not only leave you insecure, it will make the phone not work with any server which is configured to be TLS-only (and many will, in the wake of POODLE).
By the way, on "normal" Windows, this data is stored in the per-user registry hives (HKCU). My phone doesn't have the relevant registry value in either location, but it does have the registry *key* under HKCU, so you can (and possibly should) set it there instead of in HKLM.
I haven't tried this yet, though, so test it.
GoodDayToDie said:
Great guide. However, if the phone will still downgrade to SSL3 - that is, if you can't turn *off* SSLv3 - then you aren't safe. That's about half of the point of POODLE; it's possible to force most browsers and servers to downgrade to the obsolete protocol by just closing any connection attempts that report support for a newer version.
EDIT: Make darn sure you do *not* leave that option set to 32 (0x20, SSLv3 only)! That will not only leave you insecure, it will make the phone not work with any server which is configured to be TLS-only (and many will, in the wake of POODLE).
Click to expand...
Click to collapse
The phone won't dongrade to SSL 3.0. Qualys SSL Labs only show the highest supported encryption protocol. Because TLS is supported, they say SSL 3.0 is supported as well.
I edited my first post. Visit http://www.poodletest.com/, to check wether your browser sill downgrade to SSL or not. Make sure you refresh the page after you restarted your browser.
And you are right, NEVER EVER leave this option set to 32. And never set it to 2560, as this will disable TLS 1.0 and enable TLS 1.1/1.2.
Not even MS supports those encryption protocols, they really use TLS 1.0 - even if TLS 1.0 is slightly insecure and could be exploited (which practically never happens).
Poodletest is a good site for this, yes.
So, I set it in the user hive and it works, but it's a pain to do it using SamWP8 Tools because the way that the tools write to the registry uses a driver running under a different user than the DefApps user that normal apps (including IE) run as. Therefore, its concept of "current user" is different. You can use HKEY_USERS and specify the user explicitly - on my phone, the DefApps user is S-1-5-21-2702878673-795188819-444038987-2781 so the whole path to the key is
Code:
S-1-5-21-2702878673-795188819-444038987-2781\Software\Microsoft\Windows\CurrentVersion\Internet Settings
. However, be aware that this will be different on different phones, as a part of each user's SID is machine-dependent and will be different for every phone (should even change when you do a hard reset). You can find the correct SID from the Webserver app - just poke around in HKEY_USERS - but that's a pain HKLM is probably the better approach, if it works.
Thanks again for looking this up and posting instructions!