Showing posts with label Android Development. Show all posts
Showing posts with label Android Development. Show all posts
Friday, 21 December 2012
Friday, 21 December 2012
- 1 Comment
The adb utility supports several optional command-line arguments that provide powerful features, such as copying files to and from the device. The shell command-line argument lets you connect to the phone itself and issue rudimentary shell commands. Figure 4 shows the
adb shell command against a real device connected to a Windows laptop with a USB cable.Using the
adb shell command
Within this shell environment, you can:
- Display the network configuration that shows multiple network connections.
Wednesday, 19 December 2012
Wednesday, 19 December 2012
- 0 Comments
Android botnet sends SMS spam through Android phones
In a new twist, spammers have built a botnet that sends SMS spam through infected Android phones, shifting the potentially pricey cost of sending spam to victims.
The trend, spotted by security vendor Cloudmark, poses a new challenge for operators. Victims whose phones are sending the SMS spam often do not know their phone is infected, and they could have their account suddenly shut down by their operator if abuse is detected.
"I think they [operators] are still working out how to deal with this," said Andrew Conway, lead software engineer with Cloudmark, which makes antispam products for operators.
Monday, 3 December 2012
Monday, 3 December 2012
- 0 Comments
Memory Management Security Enhancements
Android includes many features that make common security issues harder to exploit. The Android SDK, compilers, and OS use tools to make common memory corruption issues significantly harder to exploit, including:
Android 1.5+
- ProPolice to prevent stack buffer overruns (-fstack-protector)
- safe_iop to reduce integer overflows
- Extensions to OpenBSD dlmalloc to prevent double free() vulnerabilities and to prevent chunk consolidation attacks. Chunk consolidation attacks are a common way to exploit heap corruption.
- OpenBSD calloc to prevent integer overflows during memory allocation
Android 2.3+
- Format string vulnerability protections (-Wformat-security -Werror=format-security)
- Hardware-based No eXecute (NX) to prevent code execution on the stack and heap
- Linux mmap_min_addr to mitigate null pointer dereference privilege escalation (further enhanced in Android 4.1)
Wanna know Android versions Nicknames
| Code name | Version | API level |
|---|---|---|
| (no code name) | 1.0 | API level 1 |
| (no code name) | 1.1 | API level 2 |
| Cupcake | 1.5 | API level 3, NDK 1 |
| Donut | 1.6 | API level 4, NDK 2 |
| Eclair | 2.0 | API level 5 |
| Eclair | 2.0.1 | API level 6 |
| Eclair | 2.1 | API level 7, NDK 3 |
| Froyo | 2.2.x | API level 8, NDK 4 |
| Gingerbread | 2.3 - 2.3.2 | API level 9, NDK 5 |
| Gingerbread | 2.3.3 - 2.3.7 | API level 10 |
| Honeycomb | 3.0 | API level 11 |
| Honeycomb | 3.1 | API level 12, NDK 6 |
| Honeycomb | 3.2.x | API level 13 |
| Ice Cream Sandwich | 4.0.1 - 4.0.2 | API level 14, NDK 7 |
| Ice Cream Sandwich | 4.0.3 - 4.0.4 | API level 15, NDK 8 |
| Jelly Bean | 4.1.x | API level 16 |
Starting with Cupcake, individual builds are identified with a short build code, e.g. FRF85B.
The first letter is the code name of the release family, e.g. F is Froyo.
The second letter is a branch code that allows Google to identify the exact code branch that the build was made from, and R is by convention the primary release branch.
Android Security
Overview:
Android is a modern mobile platform that was designed to be truly open. Android applications make use of advanced hardware and software, as well as local and served data, exposed through the platform to bring innovation and value to consumers. To protect that value, the platform must offer an application environment that ensures the security of users, data, applications, the device, and the network.
Securing an open platform requires a robust security architecture and rigorous security programs. Android was designed with multi-layered security that provides the flexibility required for an open platform, while providing protection for all users of the platform.
Android was designed with developers in mind. Security controls were designed to reduce the burden on developers. Security-savvy developers can easily work with and rely on flexible security controls. Developers less familiar with security will be protected by safe defaults.
Android was designed with device users in mind. Users are provided visibility into how applications work, and control over those applications. This design includes the expectation that attackers would attempt to perform common attacks, such as social engineering
Development Process for Android
applications Layout:
This is the layout which explains us how to develop an Android Application.Hope all those who want to develop an Android Application will follow above layout...............
User InterFace Layout Below Read more..!:)
User InterFace Layout Below Read more..!:)
Developer Tools
The Android Developer Tools (ADT) plugin for Eclipse provides a professional-grade development environment for building Android apps. It's a full Java IDE with advanced features to help you build, test, debug, and package your Android apps.
Free, open-source, and runs on most major OS platforms.
To get started, download the Android SDK.
 |
| Android SDK and AVD Manager |
Android Emulator:
 |
| Android Emulator |
Full Java IDE
- Android-specific refactoring, quick fixes, integrated navigation between Java and XML resources.
- Enhanced XML editors for Android XML resources.
- Static analysis tools to catch performance, usability, and correctness problems.
- Build support for complex projects, command-line support for CI through Ant. Includes ProGuard and app-signing.
- Template-based wizard to create standard Android projects and components.
Subscribe to:
Posts (Atom)
