Posts

Privacy Policy

Privacy Policy Privacy Policy Murali M built the Kamsali app as a Free app. This SERVICE is provided by Murali M at no cost and is intended for use as is. This page is used to inform website visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service. If you choose to use my Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that I collect is used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which is accessible at Kamsali unless otherwise defined in this Privacy Policy. Information

What is the directory structure of android AOSP root tree?

Image
  This is short version of what you will find when you download the Android source. I will leave out some minor directories and dig deeper into a couple of the important ones. Basically what you will get (based on the (Kit Kat - 4.4.4), in alphabetical order: Bionic   - the C-runtime for Android. Note that Android is not using glibc like most Linux distributions. Instead the c-library is called bionic and is based mostly on BSD-derived sources. In this folder you will find the source for the c-library, math and other core runtime libraries. Bootable   - boot and startup related code. Some of it is legacy, the fastboot protocol info could be interesting since it is implemented by boot loaders in a number of devices such as the Nexus ones. Build   - the build system implementation including all the core make file templates. An important file here is the envsetup.sh script that will help you a lot when working with the platform source. Running this script in a shell will e

How To Run Compatibility Test Suite (CTS) ?

Image
How does the CTS work? The CTS is an automated testing harness that includes two major software components: The CTS test harness runs on your desktop machine and manages test execution. Individual test cases are executed on attached mobile devices or on an emulator. The test cases are written in Java as JUnit tests and packaged as Android .apk files to run on the actual device target. Pre-Requirements : Linux System  Mobile or Emulator with User Build. Download   latest CTS. Download   CTS Media files. Download   Android SDK for Linux and keep it ready.  Setup the System for CTS: 1.Create 3 folders in your system root directory.  CTS CTS_Media ADT 2. Extract and  Copy   downloaded CTS files into the   CTS   folder which you have created now . It will have below folder structure             android-cts                 repository           plans                        results           testcases                        host_confi

NFC : Reading a MiFare Classic 1K from Android Devices

Image
Ever since Near Field Communication was embedded on mobile phones, loads of new ideas and business proposals made people very busy. So does the Android platform with its API's supporting NFC. Nexus S looks like a state of the art - good starting point if one wants to get past the monotonic Nokia's piece of the cake. I just want to share with you my experience on reading a MiFare Classic tag using the Nexus S..and the Android platform.  You need to have : A MiFare Classic 1k Tag - ( hopefully you know the keys for its Blocks :=) ) Android SDK and IDE Preferable a Nexus S (Make sure if the Android version is 2.3.3 and above). Some Basics about the card: MiFare classic cards store data in its Sectors. In MiFare classic 1k card there are 16 of them. Each Sector contains 4 blocks.  You can store 16 bytes in each block. Making about 1024 bytes of storage space..that explains the 1K part of the card. You can perform common tasks like reading, writing data on these blocks, authent