Related
The Complete Guide For Galaxy 3 i5800/i5801
Index:
1) Android Basics
2) Galaxy 3 Features
3) Hardware
4) ROM Basics, Tutorials
5) Kernel Basics
6) Tools/Imp Download Links
7) Complete List of ROMs,Kernels for G3
8) FAQ
9) EPIC Fail Ideas for G3
Android Basics
1) Android Basics
Introduction:
Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Google Inc. purchased the initial developer of the software, Android Inc., in 2005. Android's mobile operating system is based on the Linux kernel. Google and other members of the Open Handset Alliance collaborated on Android's development and release. The Android Open Source Project (AOSP) is tasked with the maintenance and further development of Android. The Android operating system is currently the world's best-selling Smartphone platform.
Android has a large community of developers writing applications ("apps") that extend the functionality of the devices. There are currently over 200,000 apps available for Android. Android Market is the online app store run by Google, though apps can also be downloaded from third-party sites. Developers write primarily in the Java language, controlling the device via Google-developed Java libraries.
The unveiling of the Android distribution on 5 November 2007 was announced with the founding of the Open Handset Alliance, a consortium of 80 hardware, software, and telecom companies devoted to advancing open standards for mobile devices. Google released most of the Android code under the Apache License, a free software and open source license.
The Android open-source software stack consists of Java applications running on a Java-based, object-oriented application framework on top of Java core libraries running on a Dalvik virtual machine featuring JIT compilation. Libraries written in C include the surface manager, OpenCore media framework, SQLite relational database management system, OpenGL ES 2.0 3D graphics API, WebKit layout engine, SGL graphics engine, SSL, and Bionic libc. The Android operating system, including the Linux kernel, consists of roughly 12 million lines of code including 3 million lines of XML, 2.8 million lines of C, 2.1 million lines of Java, and 1.75 million lines of C++.
{
"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"
}
Version history
2.1 Eclair
Changelog:
Sync: Expanded Account sync. Multiple accounts can be added to a device for email and contact synchronization
Email: Exchange support, Combined inbox to browse email from multiple accounts in one page.
Bluetooth: 2.1 support
Contacts: Tap a contact photo and select to call, SMS, or email the person.
Messaging: Search all saved SMS and MMS messages. Auto delete oldest messages in a conversation when a defined limit is reached.
Camera: Flash support, Digital zoom, Scene mode, White balance, Color effect, Macro focus
Virtual keyboard: Improved typing speed, smarter dictionary learns from word usage and includes contact names as suggestions.
Browser: Refreshed UI, Bookmark thumbnails, Double-tap zoom, Support for HTML5
Calendar: Agenda view enhanced, Attending status for each invitee, Invite new guests to events.
System: Optimized hardware speed, Revamped UI
Display: Support for more screen sizes and resolutions, Better contrast ratio
Maps: Improved Google Maps 3.1.2
MotionEvent class enhanced to track multi-touch events
Live Wallpapers: Home screen background images can be animated to show movement
2.2 Froyo
Changelog:
System: Speed, memory, and performance optimizations
Additional application speed improvements courtesy of JIT implementation
Integration of Chrome's V8 JavaScript engine into the Browser application
Improved Microsoft Exchange support (security policies, auto-discovery, GAL look-up, calendar synchronization, remote wipe)
Improved application launcher with shortcuts to Phone and Browser applications
USB tethering and Wi-Fi hotspot functionality
Added an option to disable data access over mobile network
Updated Market application with batch and automatic update features
Quick switching between multiple keyboard languages and their dictionaries
Voice dialing and contact sharing over Bluetooth
Support for numeric and alphanumeric passwords
Support for file upload fields in the Browser application
Support for installing applications to the expandable memory
Adobe Flash support
Support for extra high DPI screens (320 dpi), such as 4" 720p
2.3 Gingerbread
Changelog:
System: Updated user interface design for simplicity and speed
Display: Support for extra-large screen sizes and resolutions (WXGA and higher)
Internet calling: Native support for SIP VoIP telephony
Virtual Keyboard: Faster, more intuitive text input, improved accuracy, better suggested text. Voice input mode
Copy/Paste: Enhanced. Select a word by press-hold, copy, and paste.
Near Field Communication lets the user read an NFC tag embedded in a poster, sticker, or advertisement.
New audio effects such as reverb, equalization, headphone virtualization, and bass boost
System: Improved power management with a more active role in managing apps that are keeping the device awake for too long.
Download Manager gives the user easy access to any file downloaded from the browser, email, or another application.
Camera: Access multiple cameras on the device, including a front-facing camera, if available.
Media: Support for WebM/VP8 video playback, and AAC audio encoding
System: Enhanced support for native code development
Audio, graphical, and input enhancements for game developers
Concurrent garbage collection for increased performance
Native support for more sensors (such as gyroscopes and barometers)
Switched from YAFFS to ext4 on newer devices
Android Architecture
FEATURES OF ANDROID
Handset layouts The platform is adaptable to larger, VGA, 2D graphics library, 3D graphics library based on OpenGL ES 2.0 specifications, and traditional smartphone layouts.
Storage SQLite, a lightweight relational database, is used for data storage purposes
Connectivity Android supports connectivity technologies including GSM/EDGE, IDEN, CDMA, EV-DO, UMTS, Bluetooth, Wi-Fi (no connections through Proxy server and no Ad hoc wireless network), LTE, NFC and WiMAX.
Messaging SMS and MMS are available forms of messaging, including threaded text messaging and now Android Cloud To Device Messaging Framework(C2DM) is also a part of Android Push Messaging service.
Multiple Language Support Multiple languages are available on Android. The number of languages more than doubled for the platform 2.3 Gingerbread. Android lacks font rendering of several languages even after official announcements[citation needed] of added support (e.g. Hindi).
Web browser The web browser available in Android is based on the open-source WebKit layout engine, coupled with Chrome's V8 JavaScript engine. The browser scores a 93/100 on the Acid3 Test.
Java support While most Android applications are written in Java, there is no Java Virtual Machine in the platform and Java byte code is not executed. Java classes are compiled into Dalvik executables and run on the Dalvik virtual machine. Dalvik is a specialized virtual machine designed specifically for Android and optimized for battery-powered mobile devices with limited memory and CPU. J2ME support can be provided via third-party applications.
Media support Android supports the following audio/video/still media formats: WebM, H.263, H.264 (in 3GP or MP4 container), MPEG-4 SP, AMR, AMR-WB (in 3GP container), AAC, HE-AAC (in MP4 or 3GP container), MP3, MIDI, Ogg Vorbis, FLAC, WAV, JPEG, PNG, GIF (though earlier versions do not support animated GIFs, BMP.
Streaming media support RTP/RTSP streaming (3GPP PSS, ISMA), HTML progressive download (HTML5 <video> tag). Adobe Flash Streaming (RTMP) and HTTP Dynamic Streaming are supported by the Flash plugin. Apple HTTP Live Streaming is supported by RealPlayer for Mobile, and by the operating system in Android 3.0 (Honeycomb). Microsoft Smooth Streaming is planned to be supported through the awaited port of Silverlight plugin to Android.
Additional hardware support Android can use video/still cameras, touchscreens, GPS, accelerometers, gyroscopes, magnetometers, dedicated gaming controls, proximity and pressure sensors, thermometers, accelerated 2D bit blits (with hardware orientation, scaling, pixel format conversion) and accelerated 3D graphics.
Multi-touch Android has native support for multi-touch which was initially made available in handsets such as the HTC Hero. The feature was originally disabled at the kernel level (possibly to avoid infringing Apple's patents on touch-screen technology at the time). Google has since released an update for the Nexus One and the Motorola Droid which enables multi-touch natively.
Bluetooth Supports A2DP, AVRCP, sending files (OPP), accessing the phone book (PBAP), voice dialing and sending contacts between phones. Keyboard, mouse and joystick (HID) support is available through manufacturer customizations and third-party applications. Full HID support is planned for Android 3.0 (Honeycomb).
Video calling Android does not provide native video calling support, but some handsets have a customized version of the operating system that support it, either via the UMTS network (like the Samsung Galaxy S) or over IP. Video calling through Google Talk is available in Android 2.3.4 and later.
Multitasking Multitasking of applications is available.
Voice based features Google search through voice has been available since initial release. Voice actions for calling, texting, navigation, etc. are supported on Android 2.2 onwards.
Tethering Android supports tethering, which allows a phone to be used as a wireless/wired hotspot. Prior to Android 2.2 this was supported by third-party applications or manufacturer customizations.
Screen Capture Android does not currently support screenshot capture. This is supported by manufacturer and third-party customizations.
2) Galaxy 3 Features
General
2G Network GSM 850 / 900 / 1800 / 1900
3G Network HSDPA 900 / 2100
Announced 2010, June
Status Available. Released 2010, July
SIZE
I5801
Dimensions 113.5 x 55 x 12.6 mm
Weight 113 g
I5800
Dimensions 113.5 x 55 x 12.9 mm
Weight 109 g
DISPLAY
Type TFT capacitive touchscreen, 16M colors
Size 240 x 400 pixels, 3.2 inches
Features - Touch Wiz 3.0
- Accelerometer sensor for UI auto-rotate
- Proximity sensor for auto turn-off
- Multi-touch input method
SOUND
Alert types Vibration; MP3, WAV ringtones
Loudspeaker Yes
3.5mm jack Yes
- DNSe (Digital Natural Sound Engine)
MEMORY
Phonebook Practically unlimited entries and fields, Photocall
Call records Practically unlimited
Internal 512MB ROM, 256MB RAM
Card slot microSD, up to 32GB
DATA
GPRS Class 10 (4+1/3+2 slots), 32 - 48 kbps
EDGE Class 10, 236.8 kbps
3G HSDPA, 3.6 Mbps
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi hotspot (Android 2.2)
Bluetooth Yes, v3.0 with A2DP
Infrared port No
USB Yes, v2.0 microUSB
CAMERA
Primary 3.15 MP, 2048x1536 pixels, autofocus
Features Geo-tagging, face and smile detection
Video Yes, [email protected]
Secondary No
SOFTWARE
OS Android OS, v2.1 (Eclair), upgradable to v2.2
CPU Samsung S5P6442 667 MHz processor
Messaging SMS(threaded view), MMS, Email, Push Mail, IM
Browser HTML
Radio Stereo FM radio with RDS
Games
Colors Black, White
GPS Yes, with A-GPS support
Java Yes, via Java MIDP emulator
- Orange Application Shop
- Orange Maps, Orange TV, Orange Push Email
- Contact Back & Restore, Orange Photo
- Digital compass
- MP4/DivX/XviD/WMV/H.264/H.263 player
- MP3/WAV/eAAC+ player
- Organizer
- Document editor(Word, Excel, PowerPoint, PDF)
- Google Search, Maps, Gmail, YouTube, Calendar, Google Talk integration
- Voice memo
- Predictive text input
BATTERY
Type Standard battery, Li-Ion 1500 mAh
Stand-by Up to 620 h (2G) / Up to 480 h (3G)
Talk time Up to 15 h 30 min (2G) / Up to 7 h 15 min (3G)
3) Hardware
Processor: Samsung S5P6442 (It is modified version of S5P6440)
General Description
SAMSUNG's S5P6440, AKA "Vega-L", is the first member of the "Vega" Series, which is our newest family of Application Processors. Each Application Processor in the Vega Series will maintain a high level of compatibility with each other in order to allow for PND Makers to design their entire line-up of products on a single SoC platform.
The S5P6440 will be Samsung's first AP designed solely for PND's with a strong emphasis on high performance while maintaining cost competitiveness.
In terms of performance, the S5P6440 is run by a powerful ARM1176 processor running at 533MHz, 667MHz with a 64-bit AXI bus.
Additionally, the S5P6440 features both 2D Graphics HW and OpenVG HW, thus providing exceptional graphics acceleration for mainstream PND products. We have also focused heavily on providing optimum IP's and interfaces in order to reduce the Bill-of-Materials of the system as a whole. As an example, the S5P6440 features upgraded NAND Error Correction HW to be able to support next generation MLC NAND Flash devices. The S5P6440 also supports serial LCD protocols via the MIPI DSI standard, which allows for lower cost, lower EMI and simpler integration.
Block Diagram
Features
ARM1176JZF-S 533MHz, 667MHz, 16KB/16KB L1 Cache with Java acceleration Engine
Memory Subsystem
- NAND Flash Interface with x8 data bus, with 1/4/8/12/16-bit hardware ECC circuit and 4KB page mode
- Mobile DDR Interface with x16 or x32 data bus (up to 333Mbps/pin)
- DDR2 Interface with x16 or x32 data bus (up to 333Mbps/pin)
2D Graphics Accelerator with BitBlit and Rotation
Vector Graphics Accelerator with dedicated Anti-Aliasing HW
1/2/4/8 bpp Palletized or 8/16/24bpp Non-Palletized Color-TFT support up to 800x480
Serial LCD I/F support with MIPI DSI
- Two data lanes and one clock lane
4 channel UART: 1 channel muxed with IrDA SIR/FIR
1 channel I2S
2 channel I2C interface support
3 channel MMC/SDHC/SDIO (or 1 ch HS-MMC & 1 ch SD/MMC/SDIO)
On-chip USB 2.0 OTG controller and PHY transceiver supporting high speed
Real time clock, 3 PLL's, timer with PWM and watch dog timer
8 channel DMA controller
12 channel 12-bit ADC (Touch screen interface)
2 channel SPI: 1ch muxed with TSI (transport stream interface)
Configurable GPIOs
Technical Documents:
The Only Technical Document that we have currently is the User Manual of S3C6410 RISC Processor. It is not exactly same as S5P6442 but can be used as a reference.
Download S3C6410 User Manual
TouchScreen: ATMEL mXT224(AT42QT602240)
General Desciption
A 224-node highly configurable touchscreen controller that is part of the Atmel maXTouch product platform. An optimal and scalable architecture enables smart processing of a capacitive touch image to accurately regenerate and report the user’s interaction with the touchscreen. Multi-touch performance identifies and individually tracks touches and allows a range of built-in gestures to be reported to the host processor. The IC provides position data of 12-bit x 12-bit resolution, as well as information on the size and angle of touch. Position data is reported at >250Hz, providing fast and smooth finger tracking, making it suitable for use with demanding applications such as handwriting recognition. Due to the high signal-to-noise ratio (SNR) of up to 80:1, the device works well with fingertip touch and can also be used with a conductive stylus. It is designed to work in demanding, rapidly changing environments. Only the touchscreen area is touch-sensitive, allowing design freedom to place the chip on the main board or adjacent to the sensor. The device is ideally suited to mobile phone-sized touchscreens and can also be used on screens of up to 7", supporting single-touch or two-touch with a larger finger separation.
Technical Documents
mXT224 Datasheet
TFT LCD PANEL: Samsung S6D04D1
General Description
S6D04D1 is a single-chip display driver IC for a TFT-LCD panel. Integrated on this chip are source drivers with built-in
memory, gate drivers and power sources. S6D04D1 can support a TFT-LCD panel up to a resolution of 240-RGB x 432-
dot graphics with 16M-color. S6D04D1 also supports various types of peripheral interface such as 80-series MCU
interface (8-/9-/16-/18-/24-bits data), 3-wire 9bit / 4-wire 8bit serial interface, and MDDI(Mobile Display Digital Interface)
S6D04D1 supports various types of RGB interface (24-/18-/16-/8-/6-bits data).
The Integrated on-chip functions that are described in this document include:
- Power saving: It reduces the overall power consumed in a TFT-LCD panel module.
- Internal GRAM:
- Internal DC/DC voltage converter
- MIE (Mobile Image Enhancement) functions
S6D04D1 features several power saving functions to reduce the overall power consumed in a TFT-LCD panel module:
S6D04D1 operates at low voltage and has internal GRAMs that can store 240-RGB x 432-dot 16M-color image data. In
addition, it has an internal DC/DC voltage converter that generates various voltages needed for driving the TFT-LCD
panel by using breeder resistors and the voltage followers.
Features
A single-chip TFT-LCD Controller/gate driver/source driver with built-in Graphic RAM
Supported Display panel resolution: 240*R/G/B (H) * 432 (V) , 240*R/G/B (H) * 400 (V) & 240*R/G/B (H) * 320 (V)
Integrated 2,488,320bit of graphic RAM (GRAM)
-GRAM configuration: 240 x 432 x 24-bits = 2,488,320bits
Supported Interfaces
-3-wire 9-bit data, 4-wire 8-bit data serial interface (for RGB parallel Interface)
-8-/9-/16-/18-/24- bit interface with 80-Series MCU (so called 80-Series)
-VSYNC I/F
-MDDI(Mobile Display Digital Interface)
Outputs
-Common electrode output
-Gate outputs
-Source outputs
Color Display mode
-Full color mode (Idle mode off): 16M / 260k / 65k colors
-Reduced color mode (Idle mode on): 8-colors (3-bit binary mode)
Color modes on the display host interface
-16-bits/Pixel: RGB= (565) using the 1,843k bit frame memory
-18-bits/Pixel: RGB= (666) using the 1,843k bit frame memory
-24-bits/Pixel: RGB= (888) using the 1,843k bit frame memory
Display features
-Partial display mode
Driving scheme: line inversion & frame inversion
MIE (Mobile Image Enhancement) functions
-Adaptive luminance/contrast enhancement function.
-Reduce the power consumption of backlight.
SE ( Sharpness Enhancement) functions
On-chip functions
-Voltage Boosters
-Adjustable VCOM voltage source generator
-An oscillator for display clock generation & Timing generation
-Factory default value (Contrast, Module ID, Module version, etc) can be stored inside IC
-MTP (Multi-time Programmable) Memory
-MTP initialization & program voltages are generated automatically from the built-in power circuit.
-Each 8-bits product ID1, ID2, ID3
-6-bits VCM Offset adjustment
-Each 5-bits for VML, GVD Offset adjustment
-1 bit for MTP writing protection
Voltage Supplies
-2.3V – 3.3V for VCI, supply voltage for Analog blocks
-1.65V – 3.3V for VDD3, Supply voltage for I/O
Output voltage levels
-2.5V to 5.0V for GVDD, Source output voltage
-AVDD, Power supply for driver circuit (Note 1)
-Maximum 6.0V for VCOM, Common electrode output voltage
-11.25V to 16.50V for VGH, Positive Gate output voltage (Note 2, Note 3)
--13.75V to - 6.75V for VGL, Negative Gate output voltage (Note 2)
CMOS compatible inputs
COG package
Operating temperature range: -40℃ to +85℃
Technical Documents
S6D04D1 Datasheet
4) ROM Basics, Tutorials
STOCK ROM
A stock ROM is the version of the phone's operating system that comes with your phone when you buy it.
Samsung letter code
AW-Hungary AZ-France BD-Cyprus, Greece BY-Greece CB-Poland CE-Benelux CP-Denmark, Finland, Norway, Sweden DB-Vietnam DC-Thailand DD-India DT-Australia DX-Indonesia, Malaysia, Philippines, Singapore, Vietnam DZ-Malaysia, Singapore JA-South Africa JC-Algeria, Morocco, Nigeria, South Africa, Tunisia JP-Arabic JR-Arabic JV-Algeria, Egypt, Iran, Iraq, Kuwait, Morocco, Nigeria, Oman, Pakistan, Saudi Arabia,South Africa, Syria, Tunisia, Turkey JW-West Africa JX-Algeria, Egypt, Iran, Iraq, Kuwait, Morocco, Nigeria, Oman, Pakistan, Saudi Arabia,South Africa, Syria, Tunisia, Turkey KA-Turkey ME-France MK-Serbia MS-France, Germany, Italy, Netherlands, Portugal, Spain, Turkey, UK MT-Switserland MY-Italy NH-Latvia PO-France PU-Russia UB-Brazil XA-Austria, France, Germany, Italy, Netherlands, Switzerland, United Kingdom XB-Denmark, Norway, Sweden XC-Portugal, Spain XD-Croatia, Czech, Hungary, Slovakia XE-Bulgaria, Estonia, Kazakhstan, Latvia, Lithuania, Russia, Ukraine XF-Bulgaria, Croatia, Romania XP-UK, France, Italy, Spain, Netherlands, Poland, Portuguese, Turkey XX-Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom XW-Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom ZC-China, Hong Kong ZH-Hong Kong ZS-China, Hong Kong ZT-Taiwan
Custom ROM
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way.
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, strip them of garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow.
Flashing
Flashing Process is basically, installing a new ROM/Kernel, Stock/Custom, via Odin.
Odin is a software used to flash ROM's to the phone in the Download Mode.
Odin used for Galaxy 3 is v4.252.
Steps to follow:
1) Install Samsung Kies
2) Connect phone to PC and let it detect and install drivers automatically.
3) Download Odin with ops file from here.
4) Extract them to some folder.
5) Run Odin as Administrator.
6) Odin will now open.
7) Put phone in download mode. (Vol Down + HOME + POWER)
8) Connect Phone to PC via USB and wait till Odin shows detected.
9) Select One Package.
10) Select .ops file and .tar file for flashing.
11) Press Start button.
12) Wait till the message box on odin shows the following message and phone reboots.
13) You have now successfully flashed new ROM / Kernel.
Rooting
Rooting is a process that allows users of cellphones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem, similar to jailbreaking on Apple devices running the iOS operating system, overcoming limitations that the carriers and manufacturers put on such phones.
Most retail devices running the Android operating system must be rooted in order to install custom versions of the Android system such as CyanogenMod. This is because in the stock configuration (unrooted), user-installed applications do not have direct access to the flash memory chip on the device and, thus, are not able to replace or modify the operating system itself. Rooting is also necessary for certain applications and widgets that require additional system and hardware rights such as for rebooting the phone, certain backup utilities, and other access to other hardware such as status LEDs. Rooting is also needed to disable or remove manufacturer-installed applications such as City ID. Rooting the phone typically also includes installing an application called Superuser that supervises which applications are granted root rights.
Steps to follow:
1) Download SuperOneClick - Download
2) Run SuperOneClick
3) Press on Root
4) It will show "Waiting for device"
5) Put your phone in USB Debugging Mode.
6) Connect to PC via USB Cable.
7) Press Yes, for the subsequent messages that follow
8) Done
Deodexing
WHAT IS AN ODEX FILE?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & DISADVANTAGES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Steps to follow:
1) Download xUltimate - Download
2) Run Main.exe
3) Press N to continue
4) Press Y to continue
5) You should get a complete menu
6) Connect phone to PC in USB Debugging Mode
7) Run Option 1
8) Run Option 2
9) Run Option 3
10) Run Option 4
11) You Will now have deodexed apps and framework files in done_app and done_frame folders.
12) Copy these folders where you have your adb setup.
13) Run the following Code
Code:
adb -d shell "mount -o remount,rw /dev/block/stl6 /system"
adb -d shell "stop"
adb -d shell "rm /system/app/*.apk"
adb -d shell "rm /system/app/*.odex"
adb -d shell "rm /system/framework/*.jar"
adb -d shell "rm /system/framework/*.odex"
adb -d push done_app /system/app/
adb -d push done_frame /system/framework/
adb reboot
14) Your phone should reboot successfully, and you now have a deodexed ROM.
Clean ROM
The following list of files you can delete to clean ROM
1) BuddiesNow
2) Dlna
3) DualClock
4) FlashSVGPlayer
5) HTMLViewer
6) InfoAlarm
7) InputEventApp
8) Layar-samsung
9) Maps
10) MobileTrackerEngineTwo
11) MobileTrackerUI
12) Protips
13) SamsungApps
14) SamsungWidget_CalendarClock
15) SamsungWidget_FeedAndUpdate
16) SamsungWidget_ProgramMonitor
17) SamsungWidget_StockClock
18) Street
19) UNAService
20) UnifiedInbox
21) VoiceRecorder
22) wipereceiver
23) WriteandGo
5) Kernel Basics
dhirend_6d said:
What Is a Kernel?
The UNIX kernel is the software that manages the user program's access to the systems hardware and software resources. These resources range from being granted CPU time, accessing memory, reading and writing to the disk drives, connecting to the network, and interacting with the terminal or GUI interface. The kernel makes this all possible by controlling and providing access to memory, processor, input/output devices, disk files, and special services to user programs.
Kernel Services
The basic UNIX kernel can be broken into four main subsystems:
Process Management
Memory Management
I/O Management
File Management
These subsystems should be viewed as separate entities that work in concert to provide services to a program that enable it to do meaningful work. These management subsystems make it possible for a user to access a database via a Web interface, print a report, or do something as complex as managing a 911 emergency system. At any moment in the system, numerous programs may request services from these subsystems. It is the kernel's responsibility to schedule work and, if the process is authorized, grant access to utilize these subsystems. In short, programs interact with the subsystems via software libraries and the systems call interface. We'll start by looking at how the UNIX kernel comes to life by way of the system initialization process.
System Initialization
System initialization (booting) is the first step toward bringing your system into an operational state. A number of machine-dependent and machine-independent steps are gone through before your system is ready to begin servicing users. At system startup, there is nothing running on the Central Processing Unit (CPU). The kernel is a complex program that must have its binary image loaded at a specific address from some type of storage device, usually a disk drive. The boot disk maintains a small restricted area called the boot sector that contains a boot program that loads and initializes the kernel. You'll find that this is a vendor specific procedure that reflects the architectural hardware differences between the various UNIX vendor platforms. When this step is completed, the CPU must jump to a specific memory address and start executing the code at that location. Once the kernel is loaded, it goes through its own hardware and software initialization.
Kernel Mode
The operating system, or kernel, runs in a privileged manner known as kernel mode. This mode of operation allows the kernel to run without being interfered with by other programs currently in the system. The microprocessor enforces this line of demarcation between user and kernel level mode. With the kernel operating in its own protected address space, it is guaranteed to maintain the integrity of its own data structures and that of other processes. (That's not to say that a privileged process could not inadvertently cause corruption within the kernel.) These data structures are used by the kernel to manage and control itself and any other programs that may be running in the system. If any of these data structures were allowed to be accidentally or intentionally altered, the system could quickly crash. Now that we have learned what a UNIX kernel is and how it is loaded into the system, we are ready to take a look at the four UNIX subsystems Process Management, Memory Management, Filesystem Management and I/O Management.
Process Management
The Process Management subsystem controls the creation, termination, accounting, and scheduling of processes. It also oversees process state transitions and the switching between privileged and nonprivileged modes of execution. The Process Management subsystem also facilitates and manages the complex task of the creation of child processes.
A simple definition of a process is that it is an executing program. It is an entity that requires system resources, and it has a finite lifetime. It has the capability to create other processes via the system call interface. In short, it is an electronic representation of a user's or programmer's desire to accomplish some useful piece of work. A process may appear to the user as if it is the only job running in the machine. This "sleight of hand" is only an illusion. At any one time a processor is only executing a single process.
Process Structure
A process has a definite structure (see Figure 19.1). The kernel views this string of bits as the process image. This binary image consists of both a user and system address space as well as registers that store the process's data during its execution. The user address space is also known as the user image. This is the code that is written by a programmer and compiled into an ".o " object file. An object file is a file that contains machine language code/data and is in a format that the linker program can use to then create an executable program.
Diagram of process areas.
The user address space consists of five separate areas: Text, Data, Bss, stack, and user area.
Text Segment The first area of a process is its text segment. This area contains the executable program code for the process. This area is shared by other processes that execute the program. It is therefore fixed and unchangeable and is usually swapped out to disk by the system when memory gets too tight.
Data Area The data area contains both the global and static variables used by the program. For example, a programmer may know in advance that a certain data variable needs to be set to a certain value. In the C programming language, it would look like:
Code:
int x = 15;
If you were to look at the data segment when the program was loaded, you would see that the variable x was an integer type with an initial value of 15.
Bss Area The bss area, like the data area, holds information for the programs variables. The difference is that the bss area maintains variables that will have their data values assigned to them during the programs execution. For example, a programmer may know that she needs variables to hold certain data that will be input by a user during the execution of the program.
Code:
int a,b,c; // a,b and c are variables that hold integer values.
char *ptr; // ptr is an unitialized character pointer.
The program code can also make calls to library routines like malloc to obtain a chunk of memory and assign it to a variable like the one declared above.
Stack Area The stack area maintains the process's local variables, parameters used in functions, and values returned by functions. For example, a program may contain code that calls another block of code (possibly written by someone else). The calling block of code passes data to the receiving block of code by way of the stack. The called block of code then process's the data and returns data back to the calling code. The stack plays an important role in allowing a process to work with temporary data.
User Area The user area maintains data that is used by the kernel while the process is running. The user area contains the real and effective user identifiers, real and effective group identifiers, current directory, and a list of open files. Sizes of the text, data, and stack areas, as well as pointers to process data structures, are maintained. Other areas that can be considered part of the process's address space are the heap, private shared libraries data, shared libraries, and shared memory. During initial startup and execution of the program, the kernel allocates the memory and creates the necessary structures to maintain these areas.
The user area is used by the kernel to manage the process. This area maintains the majority of the accounting information for a process. It is part of the process address space and is only used by the kernel while the process is executing(see Figure 19.2). When the process is not executing, its user area may be swapped out to disk by the Memory Manager. In most versions of UNIX, the user area is mapped to a fixed virtual memory address. Under HP-UX 10.X, this virtual address is 0x7FFE6000. When the kernel performs a context switch (starts executing a different process) to a new process, it will always map the process's physical address to this virtual address. Since the kernel already has a pointer fixed to this location in memory, it is a simple matter of referencing the current u pointer to be able to begin managing the newly switched in process. The file /usr/include/sys/user.h contains the user area's structure definition for your version of UNIX.
Diagram of kernel address space.
Process Table The process table is another important structure used by the kernel to manage the processes in the system. The process table is an array of process structures that the kernel uses to manage the execution of programs. Each table entry defines a process that the kernel has created. The process table is always resident in the computer's memory. This is because the kernel is repeatedly querying and updating this table as it switches processes in and out of the CPU. For those processes that are not currently executing, their process table structures are being updated by the kernel for scheduling purposes. The process structures for your system are defined in /usr/include/sys/proc.h.
Fork Process The kernel provides each process with the tools to duplicate itself for the purpose of creating a new process. This new entity is termed a child process. The fork() system call is invoked by an existing process (termed the parent process) and creates a replica of the parent process. While a process will have one parent, it can spawn many children. The new child process inherits certain attributes from its parent.
Process Run States
A process moves between several states during its lifetime, although a process can only be in one state at any one time. Certain events, such as system interrupts, blocking of resources, or software traps will cause a process to change its run state. The kernel maintains queues in memory that it uses to assign a process to based upon that process's state. It keeps track of the process by its user ID.
UNIX version System V Release 4 (SVR4) recognizes the following process run states:
Code:
- SIDLE This is the state right after a process has issued
a fork() system call. A process image has yet to be copied into memory.
- SRUN The process is ready to run and is waiting to be executed by the CPU.
- SONPROC The process is currently being executed by the CPU.
- SSLEEP The process is blocking on an event or resource.
- SZOMB The process has terminated and is waiting on
either its parent or the init process to allow it to completely exit.
- SXBRK The process is has been switched out so that another process can be executed.
- SSTOP The process is stopped.[/COLOR]
When a process first starts, the kernel allocates it a slot in the process table and places the process in the SIDL state. Once the process has the resources it needs to run, the kernel places it onto the run queue. The process is now in the SRUN state awaiting its turn in the CPU. Once its turn comes for the process to be switched into the CPU, the kernel will tag it as being in the SONPROC state. In this state, the process will execute in either user or kernel mode. User mode is where the process is executing nonprivileged code from the user's compiled program. Kernel mode is where kernel code is being executed from the kernel's privileged address space via a system call.
At some point the process is switched out of the CPU because it has either been signaled to do so (for instance, the user issues a stop signal--SSTOP state) or the process has exceeded its quota of allowable CPU time and the kernel needs the CPU to do some work for another process. The act of switching the focus of the CPU from one process to another is called a context switch. When this occurs, the process enters what is known as the SXBRK state. If the process still needs to run and is waiting for another system resource, such as disk services, it will enter the SSLEEP state until the resource is available and the kernel wakes the process up and places it on the SRUN queue. When the process has finally completed its work and is ready to terminate, it enters the SZOMB state. We have seen the fundamentals of what states a process can exist in and how it moves through them. Let's now learn how a kernel schedules a process to run.
Process Scheduler
Most modern versions of UNIX (for instance, SVR4 and Solaris 2.x) are classified as preemptive operating systems. They are capable of interrupting an executing a process and "freezing" it so that the CPU can service a different process. This obviously has the advantage of fairly allocating the system's resources to all the processes in the system. This is one goal of the many systems architects and programmers who design and write schedulers. The disadvantages are that not all processes are equal and that complex algorithms must be designed and implemented as kernel code in order to maintain the illusion that each user process is running as if it was the only job in the system. The kernel maintains this balance by placing processes in the various priority queues or run queues and apportioning its CPU time-slice based on its priority class (Real-Time versus Timeshare).
Memory Management
Random access memory (RAM) is a very critical component in any computer system. It's the one component that always seems to be in short supply on most systems. Unfortunately, most organizations' budgets don't allow for the purchase of all the memory that their technical staff feel is necessary to support all their projects. Luckily, UNIX allows us to execute all sorts of programs without, what appears at first glance to be, enough physical memory. This comes in very handy when the system is required to support a user community that needs to execute an organization's custom and commercial software to gain access to its data.
Memory chips are high-speed electronic devices that plug directly into your computer. Main memory is also called core memory by some technicians. Ever heard of a core dump? (Writing out main memory to a storage device for post-dump analysis.) Usually it is caused by a program or system crash or failure. An important aspect of memory chips is that they can store data at specific locations called addresses. This makes it quite convenient for another hardware device called the central processing unit (CPU) to access these locations to run your programs. The kernel uses a paging and segmentation arrangement to organize process memory. This is where the memory management subsystem plays a significant role. Memory management can be defined as the efficient managing and sharing of the system's memory resources by the kernel and user processes.
Memory management follows certain rules that manage both physical and virtual memory. Since we already have an idea of what a physical memory chip or card is, we will provide a definition of virtual memory. Virtual memory is where the addressable memory locations that a process can be mapped into are independent of the physical address space of the CPU. Generally speaking, a process can exceed the physical address space/size of main memory and still load and execute.
The systems administrator should be aware that just because she has a fixed amount of physical memory, she should not expect it all to be available to execute user programs. The kernel is always resident in main memory and depending upon the kernel's configuration (tunable-like kernel tables, daemons, device drivers loaded, and so on), the amount left over can be classified as available memory. It is important for the systems administrator to know how much available memory the system has to work with when supporting his environment. Most systems display memory statistics during boot time. If your kernel is larger than it needs to be to support your environment, consider reconfiguring a smaller kernel to free up resources.
We learned before that a process has a well-defined structure and has certain specific control data structures that the kernel uses to manage the process during its system lifetime. One of the more important data structures that the kernel uses is the virtual address space (vas in HP-UX and as in SVR4. For a more detailed description of the layout of these structures, look at the vas.h or as.h header files under /usr/include on your system.).
A virtual address space exists for each process and is used by the process to keep track of process logical segments or regions that point to specific segments of the process's text (code), data, u_area, user, and kernel stacks; shared memory; shared library; and memory mapped file segments. Per-process regions protect and maintain the number of pages mapped into the segments. Each segment has a virtual address space segment as well. Multiple programs can share the process's text segment. The data segment holds the process's initialized and uninitialized (BSS) data. These areas can change size as the program executes.
The u_area and kernel stack contain information used by the kernel, and are a fixed size. The user stack is contained in the u_area; however, its size will fluctuate during its execution. Memory mapped files allow programmers to bring files into memory and work with them while in memory. Obviously, there is a limit to the size of the file you can load into memory (check your system documentation). Shared memory segments are usually set up and used by a process to share data with other processes. For example, a programmer may want to be able to pass messages to other programs by writing to a shared memory segment and having the receiving programs attach to that specific shared memory segment and read the message. Shared libraries allow programs to link to commonly used code at runtime. Shared libraries reduce the amount of memory needed by executing programs because only one copy of the code is required to be in memory. Each program will access the code at that memory location when necessary.
When a programmer writes and compiles a program, the compiler generates the object file from the source code. The linker program (ld) links the object file with the appropriate libraries and, if necessary, other object files to generate the executable program. The executable program contains virtual addresses that are converted into physical memory addresses when the program is run. This address translation must occur prior to the program being loaded into memory so that the CPU can reference the actual code.
When the program starts to run, the kernel sets up its data structures (proc, virtual address space, per-process region) and begins to execute the process in user mode. Eventually, the process will access a page that's not in main memory (for instance, the pages in its working set are not in main memory). This is called a page fault. When this occurs, the kernel puts the process to sleep, switches from user mode to kernel mode, and attempts to load the page that the process was requesting to be loaded. The kernel searches for the page by locating the per-process region where the virtual address is located. It then goes to the segments (text, data, or other) per-process region to find the actual region that contains the information necessary to read in the page.
The kernel must now find a free page in which to load the process's requested page. If there are no free pages, the kernel must either page or swap out pages to make room for the new page request. Once there is some free space, the kernel pages in a block of pages from disk. This block contains the requested page plus additional pages that may be used by the process. Finally the kernel establishes the permissions and sets the protections for the newly loaded pages. The kernel wakes the process and switches back to user mode so the process can begin executing using the requested page. Pages are not brought into memory until the process requests them for execution. This is why the system is referred to as a demand paging system.
The memory management unit is a hardware component that handles the translation of virtual address spaces to physical memory addresses. The memory management unit also prevents a process from accessing another process's address space unless it is permitted to do so (protection fault). Memory is thus protected at the page level. The Translation Lookaside Buffer (TLB) is a hardware cache that maintains the most recently used virtual address space to physical address translations. It is controlled by the memory management unit to reduce the number of address translations that occur on the system.
Input and Output Management
The simplest definition of input/output is the control of data between hardware devices and software. A systems administrator is concerned with I/O at two separate levels. The first level is concerned with I/O between user address space and kernel address space; the second level is concerned with I/O between kernel address space and physical hardware devices. When data is written to disk, the first level of the I/O subsystem copies the data from user space to kernel space. Data is then passed from the kernel address space to the second level of the I/O subsystem. This is when the physical hardware device activates its own I/O subsystems, which determine the best location for the data on the available disks.
The OEM (Original Equipment Manufacture) UNIX configuration is satisfactory for many work environments, but does not take into consideration the network traffic or the behavior of specific applications on your system. Systems administrators find that they need to reconfigure the systems I/O to meet the expectations of the users and the demands of their applications. You should use the default configuration as a starting point and, as experience is gained with the demands on the system resources, tune the system to achieve peak I/O performance.
UNIX comes with a wide variety of tools that monitor system performance. Learning to use these tools will help you determine whether a performance problem is hardware or software related. Using these tools will help you determine whether a problem is poor user training, application tuning, system maintenance, or system configuration. sar, iostat, and monitor are some of your best basic I/O performance monitoring tools.
1) sar The sar command writes to standard output the contents of selected cumulative activity counters in the operating system. The following list is a breakdown of those activity counters that sar accumulates.
* File access
* Buffer usage
* system call activity
* Disk and tape input/output activity
* Free memory and swap space
* Kernel Memory Allocation (KMA)
* Interprocess communication
* Paging
* Queue Activity
* Central Processing Unit (CPU)
* Kernel tables
* Switching
* Terminal device activity
2) iostat Reports CPU statistics and input/output statistics for TTY devices, disks, and CD-ROMs.
3) monitor Like the sar command, but with a visual representation of the computer state.
RAM I/O
The memory subsystem comes into effect when the programs start requesting access to more physical RAM memory than is installed on your system. Once this point is reached, UNIX will start I/O processes called paging and swapping. This is when kernel procedures start moving pages of stored memory out to the paging or swap areas defined on your hard drives. (This procedure reflects how swap files work in Windows by Microsoft for a PC.) All UNIX systems use these procedures to free physical memory for reuse by other programs. The drawback to this is that once paging and swapping have started, system performance decreases rapidly. The system will continue using these techniques until demands for physical RAM drop to the amount that is installed on your system. There are only two physical states for memory performance on your system: Either you have enough RAM or you don't, and performance drops through the floor.
Memory performance problems are simple to diagnose; either you have enough memory or your system is thrashing. Computer systems start thrashing when more resources are dedicated to moving memory (paging and swapping) from RAM to the hard drives. Performance decreases as the CPUs and all subsystems become dedicated to trying to free physical RAM for themselves and other processes.
This summary doesn't do justice, however, to the complexity of memory management nor does it help you to deal with problems as they arise. To provide the background to understand these problems, we need to discuss virtual memory activity in more detail.
We have been discussing two memory processes: paging and swapping. These two processes help UNIX fulfill memory requirements for all processes. UNIX systems employ both paging and swapping to reduce I/O traffic and execute better control over the system's total aggregate memory. Keep in mind that paging and swapping are temporary measures; they cannot fix the underlying problem of low physical RAM memory.
Swapping moves entire idle processes to disk for reclamation of memory, and is a normal procedure for the UNIX operating system. When the idle process is called by the system again, it will copy the memory image from the disk swap area back into RAM.
On systems performing paging and swapping, swapping occurs in two separate situations. Swapping is often a part of normal housekeeping. Jobs that sleep for more that 20 seconds are considered idle and may be swapped out at any time. Swapping is also an emergency technique used to combat extreme memory shortages. Remember our definition of thrashing; this is when a system is in trouble. Some system administrators sum this up very well by calling it "desperation swapping."
Paging, on the other hand, moves individual pages (or pieces) of processes to disk and reclaims the freed memory, with most of the process remaining loaded in memory. Paging employs an algorithm to monitor usage of the pages, to leave recently accessed pages in physical memory, and to move idle pages into disk storage. This allows for optimum performance of I/O and reduces the amount of I/O traffic that swapping would normally require.
NOTE: Monitoring what the system is doing is easy with the ps command. ps is a "process status" command on all UNIX systems and typically shows many idle and swapped-out jobs. This command has a rich amount of options to show you what the computer is doing.
I/O performance management, like all administrative tasks, is a continual process. Generating performance statistics on a routine basis will assist in identifying and correcting potential problems before they have an impact on your system or, worst case, your users. UNIX offers basic system usage statistics packages that will assist you in automatically collecting and examining usage statistics.
You will find the load on the system will increase rapidly as new jobs are submitted and resources are not freed quickly enough. Performance drops as the disks become I/O bound trying to satisfy paging and swapping calls. Memory overload quickly forces a system to become I/O and CPU bound.
Filesystem Concept
Filesystem is the collection place on disk device(s) for files. Visualize the filesystem as consisting of a single node at the highest level (ROOT) and all other nodes descending from the root node in a tree-like fashion (see Figure 19.5) . The second meaning will be used for this discussion, and Hewlett Packard's High-performance Filesystem will be used for technical reference purposes.
Diagram of a Android' s hierarchical filesystem.
The superblock is the key to maintaining the filesystem. It's an 8 KB block of disk space that maintains the current status of the filesystem. Because of its importance, a copy is maintained in memory and at each cylinder group within the filesystem. The copy in main memory is updated as events transpire. The update daemon is the actual process that calls on the kernel to flush the cached superblocks, modified inodes, and cached data blocks to disk. The superblock maintains the following static and dynamic information about the
Click to expand...
Click to collapse
6) Tools/Imp Download Links
rickslick said:
Samsung USB drivers(no more kies) for 32bit and 64bit windows: Driver
Adb with ncessary dll : Click here
Flashing tools(odin+ops):click here
Click to expand...
Click to collapse
7) Complete List of ROMs,Kernels for G3
dhirend_6d said:
GINGERBREAD BASED ROMS : -
CYANOGENMOD 7 AND GINGERBREAD AOSP by Marcellusbe.
AOSP FROYO BASED ROMS : -
CYANOGENMOD 6.2 by Marcellusbe.
SAMSUNG FROYO BASED ROMS : -
1) G3MOD ROM by DharamG3 and G3Mod team.
2) KYRILLOS' ROM by Kyrillos13.
3) INDROID by Rudolf895, Arunmcops, Neeljinwala, Akash, Chirayu.
4) DUTCHMODS by Werker123.
5) DESTINY by Hodostamas.
6) KYORAROM by Hillbeast.
7) STYLOO' S AOSP STYLE ROM by Styloo.
8) LESTATIOUS ROM by The Dark Lestat.
9) GRIGORA ROM by RafayelG.
10) SUMEE ROM by Ash!sh.
11) STOCK DEODEXED ROOTED ROMS by DharamG3.
12) DHARAM' S ROM COLLECTION by DharamG3.
13) SAMSUNG STOCK FIRMWARES (WITHOUT BOOTLOADERS) by Kyrillos13.
14) IBREAD.NITESH by Niteshtak.
15) GREENMODS POX by Jazux, Akash, Pauri, s3th.g3ck0.
16) ATROM by Dpthakar.
17) SPEEDMOD ROM by Styloo and DharamG3.
18) RAFO' S ROM by RafayelG.
19) REAPER REVIVAL ROM by Jihaa.
20) APOCALYPSE by ARMVKDevs.
21) BURAK' S ROM by Burak721.
22) CYANOBROZZU MOD ROM by Superfancy97.
23) OUM ROM by Revant.
24) THE PEOPLE' S ROM by Shekhargreen.
25) GALACTIC BLUE ROM by Cdesai, Shubhamchamaria, Aarun.
26) PSYCHOTIK ROM by TotorLeTaureau
27) [KERNEL+ROM] APOLLO by Apollo5801
28) THE BLUE by Abhi0n0nakul.
KERNELS : -
KERNELS BY DHARAM AND TEAM G3MOD : -
1) G3Mod Kernels for Froyo.
2) G3Mod Kernels for CM 6.2.
All the kernels of G3Mod along with changelog and features can be found here.
KERNELS BY MARCELLUSBE : -
1) FuguMod 2.4 Beta 3 (JFS/REISERFS Supported), 800 Mhz Edition.
2) FuguMod 2.4 Beta 3 (JFS/REISERFS Supported), Standard Edition.
3) FuguMod 2.4 Beta 3, 800 MHz Edition.
4) FuguMod 2.4 Beta 3, Standard Edition.
5) FuguMod 2.2 Bleeding Edge Edition.
6) FuguMod 2.2 Standard Edition.
Link to all the above kernels here.
For features and changelog see here.
7) FuguMod Ultra.
KERNELS BY APOLLO5801 : -
Dual Boot kernel.
KERNELS BY GSAM101 : -
SAM' S KERNEL V0.1.
Click to expand...
Click to collapse
8) FAQ For G3
9) EPIC Fail Ideas for G3
hillbeast said:
Seeing nobody has posted any real epic fail ideas, I will post one: I saw a guy wanting to post iOS to our phone. Now I can understand an iOS skin, but why would we want an OS that can't even handle multitasking properly and replace the glory of Android with Steve Jobs' locked down nutjob OS?
Click to expand...
Click to collapse
Credits
1) Android Basics
http://www.wikipedia.org/
http://developer.android.com/index.html
2) Galaxy 3 Features
www.gsmarena.com
3) Hardware
http://www.samsung.com/
http://www.atmel.com
4) ROM Basics/Tutorails
Flashing - BraveBuddy
dharamg3 said:
Credits
rudolf895, jazux and sekhargreen for their tutorials and how-to's....
loads more too come...i will add as i add the context...
but thanks to all the developers doing the wonderful work for Galaxy 3
Click to expand...
Click to collapse
Damn this is going to be a long one because you reserved 10 posts good luck
jazux said:
Damn this is going to be a long one because you reserved 10 posts good luck
Click to expand...
Click to collapse
just wait and see..hoping to cover everything
dharamg3 said:
Credits
rudolf895, jazux and sekhargreen for their tutorials and how-to's....
loads more too come...i will add as i add the context...
but thanks to all the developers doing the wonderful work for Galaxy 3
Click to expand...
Click to collapse
Hi,
It is good to get all the stuff at one place.
Let me know if any help needed.
sekhargreen said:
Hi,
It is good to get all the stuff at one place.
Let me know if any help needed.
Click to expand...
Click to collapse
sure, you can give me links here on what all can be added...
you can call the topic: "the ultimate guide for the galaxy 3"
vonuzu said:
you can call the topic: "the ultimate guide for the galaxy 3"
Click to expand...
Click to collapse
let me start off...it will take time to make it the ultimate
Android Basics Added to start off...Much More To Come
NICE WORK! Im definetly going to mail the xda newswriter about this
done in week you are going to be in news, for sure
This subject topic will be the most significant added value to this forum:
For the new members (sometime old once) that are joining the G3 revolution (and this is happing here), there is a need to provide them the basics before they can dive into elements such as: Custom ROM's, Kernel's...etc.
Myself as a junior user and others will greatly appreciate this new introduced topic.
Hi,
I am not sure how to ask this question yet i scribble a few words. Kindly ask questions if you are not clear. Thanks in advance.
We are doing a custom device for a industrial project. The project involves maintaining stock and functioning of electronic products using the USB API. The USB device(Our Product) and the android phone will be placed and provided to the end-user in an assembly. The end user sees the whole thing as a PDA/Device for use in industry.
I need suggestions for the following:
- The android Phone which we use must contain the following according to the Devs.
Android Version 2.2 or Higher.
Android Gingerbread 2.3 or higher is preferred.
- Touch Screen (Resistive or capacitive)
- Resolution 320 X 480 Pixels (Minimum)
- Screen-size 3 -4 Inches
- GPS or aGPS
- G-Sensor
- WiFi (any b/g/n or all)
- Internal Memory 512MB or higher
- RAM 384 MB or higher
- Processor 500 MHz or higher
- Battery 5 hrs or more usage time
- Partially assembled units with Display, Battery and Board.
- the outer case is not required (Optional)
- Bluetooth, GSM.. etc are necessarily required but if present can be used for any future projects.
Is there any board/ assembly unit or may be a mobile phone without the fancy housing or casing which we can buy for our project?
The BeagleBoard and AllGo boards already have android support but are on the expensive side.
Any help would be really appreciated.
Mods kindly help me to make this questions little more clear to the respected community.
Thank you.
{
"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"
}
After months of advertising, the ICOO ICOU Fatty2 is now finally on sale. The entry-level price of the tablet (Wi-Fi only) is RMB 899 (USD 149), which is much higher than competitions like the Yuandao mini one (USD 119) and CHUWI V88s (USD 119), both of which have the same 7.9 inch IPS display. But the Fatty2 is pricier for a reason, the 5500mAh battery it features gives the slate an extraordinary 10-12 hours run time, and the Wi-Fi reception is the best I’ve experienced on a Chinese tablet!
Key Features:
◇7.9 inch 16M-color IPS display at XGA resolution (1024X768 pixels)
◇Weighs 310g, 198*134*7mm in size.
◇Rockchip RK3188 SoC., 1.6GHZ quad core Cortex-A9 processor, Mali-400MP4 GPU, 1GB DDR3 RAM
◇Stock Android 4.1 Jelly Bean
◇16GB of built-in-storage
◇2.0MP front facing camera; 5.0MP rear-facing camera
◇Stereo speaker
◇HDMI TV-out
◇Bluetooth V2.1
◇USB host
◇MicroSD card slot
◇Standard 3.5mm audio jack
◇1080p video playback
◇5500mAh Li-Po rechargeable battery, 10-12 hours battery life
Main disadvantages:
Too similar to the iPad mini
So-so Cameras
Pricier than alternative options
First Impressions
The one thing that sticks out most about the Fatty2 is how much it looks like an iPad mini. And I'm not talking about the interface and apps, but the weight and size of the tablet, which is so thin and weighs so little you'd almost think you were browsing the web on a piece of paper.
The ICOU Fatty2 may not have the Retina Display and 2GB of DDR3 RAM of many 9.7 inch Chinese tablet, but it still looks beautiful and is extremely responsive. This shouldn't come as a surprise. Most apps are designed to run on standard resolution, only a few apps actually support the latest superior graphics of the retina display.
The 7.9-inch ICOU Fatty2 is only slightly larger than many 7 inchers, thanks to the narrow screen bezel it uses. When I pick it up with one hand, it seems just right. While many of the 8 inch tablets beg to be held with both hands, it feels natural to hold the Fatty in one hand, even for a long period of time.
Retail Package
It seems ICOO determined to stick to this colorful packaging approach for its tablet products this year. Fatty2 is wrapped up in a paperback box which has 7 colors to it. I personally prefer more simplistic style taken by Samsung and many other internationally well-known manufactures, but I can’t say that this packaging isn’t attractive.
Again, ICOO has carried on its wonderful tradition with a slew of buddle fittings. You will find a 5V-2A charger, a USB data cable, an OTG cable and a pair of SONY earphones along with the fatty2.
Design and Build
The front of the tablet is dominated by a 7.9 inch IPS display, with very small bezel around it. At 198*134mm, it is even smaller than the popular Apple iPad mini (200 x 134.7mm), and only slightly bigger than the Nexus 7 (198.5 x 120mm) and Kindle Fire HD (196.7 x 133), both of which use a much smaller 7-inch display.
As for thickness, the ICOO ICOU Fatty2 is easily the slimmest tablet I have ever seen, at 7mm it is even thinner than the ultra-slim iPad mini (7.2mm) and Samsung Galaxy Note 8.0 (7.9mm). Although Yuandao has claimed the their so-called 6.8mm mini one is the thinnest tablet on earth, it is later proved to be just another lie, amongst many lies told by this unprincipled tablet maker.
All the connectors are hosted on the bottom edge. From left to right are a mini HDMI port, a micro USB port, a 2.5mm DC port, a 3.5mm audio jack, a tiny microphone pinhole and a MicroSD card slot which supports cards up to 32GB.
Again, ICOO has taken a simplistic approach with the hardware keys, only a power/standby key and a volume rocker will be found on the transition area between the right edge and the back. Personally, I dislike the arrangement that the power button is actually below the volume rockers. Moreover, I am really disappointed that, in portrait mode, the lower part of the volume rocker is actually volume +. I know this may be due to the fact that we more often use the tablet in vertical mode, but if a tablet is designed to be like an iPad, it should be arranged like an iPad.
The back of the slate is partially plastic, partially aluminum. This is, contrary to the button layout, a brilliant arrangement. The plastic can guarantee solid Wi-Fi reception, and the use of hairline metal can avoid the feel of cheapness. A 5MP auto-focus front facing camera sits comfortably on the upper left corner, and the only speaker gate is on the lower left corner.
Also, you can choose to purchase a magnetic protection cover or a Bluetooth keyboard for your Fatty2, both of which are at relatively low price (cover: $7, Keyboard: $17). When you open the cover, the Fatty2 magically wakes up. And while you close it, the Fatty2 automatically goes to sleep. I have only seen this useful function on the iPad series and some Windows tablet before. Its presence here on a low-price Chinese tablet is pretty surprising. The Bluetooth keyboard feels even more solid than the tablet itself, at just 7.7mm thick it can turn your Fatty2 into a super-slim ultra laptop in just a second!
Screen
The Fatty2 sports exactly the same display used on the iPad mini. The IPS display technology together with the 7.9” XGA display delivers seamlessly brilliant colors that redefines the best visual experience a tablet can offer.
The ultra slim 7.9” XGA display offers brilliant contrast ratio, the best color gamut and response time, making text or image-viewing extraordinarily crispy and vivid regardless the viewing angle.
http://image14.poco.cn/mypoco/myphoto/20130702/01/173385433201307020105472732452363556_005.jpg[img]
[img]http://image14.poco.cn/mypoco/myphoto/20130702/01/173385433201307020105472732452363556_004.jpg
There is nothing special about the resolution and some 7" tablets like the Nexus7 and the Kindle Fire HD even push the pixel density above 200 ppi. If you did the math already, you'd know the Fatty2 is far behind at 163 ppi. The Retina display of the new iPad is the standard-setter in tablets at 264 ppi, and you will always keep in mind the existence of the Google Nexus 10, which holds the tablet record of 300ppi. Hacing said that, the Fatty2’s display is still vivid enough for most users, packing an XGA resolution in such a small screen definitely brings much better visual experience than most of the computers.
Even when you put the Fatty2 next to the Samsung Galaxy Tab 7.7, which features a more expensive, more vibrant Super AMOLED Plus display, it still won’t be outshined. In fact, the IPS display the Fatty2 sports is likely to be more accepted by the majority of users as its color expression is more close to real.
Performance
The Fatty2 is powered by the 1.6GHZ quad core RK3188 Chipset, along with 1GB DDR3 RAM, which put up some incredible benchmark scores.
The 17,472 overall Antutu benchmark score handily beat the 16,734 notched by the Samsung Galaxy Note 8.0, and smashed scores achieved by the Allwinner A31 powered Onda V818 mini and Actions ATM7029 powered Ainol NOVO8 Dream.
It’s more or less the same story on the Quadrant Advanced. Again, the RK3188 powered Fatty2 scored higher points than the other 3 devices.
In the graphics-focused Nenamark2 test, the Fatty2 scored 55.6 FPS, higher than the category average. But the Allwinner A31 powered Onda V818 mini scored a much more impressive 58.9 FPS, thanks to its impeccable PowerVR SGX544MP2 GPU.
The An3D Bench XL also centers on the 3D capability of the device. But the Fatty2 turned the tide around this time, notching an incredible 37,018, blowing the other 8 inch competitions out of the water.
Vellamo is by far my favorite Benchmark application, the scores of certain device are very consistent, regardless of the version of the software. Although the Fatty2 was beaten by the more all-optimized Samsung Galaxy Note 8.0 in both HTML5 and Metal test, it still smashed the other two quad-core slates.
CF-bench also witnessed the Fatty2’s capability, the 15888 final score easily outshined its competitions.
Fortunately, the Fatty2’s real world performance cohere with its benchmark scores, at XGA resolution, it is truly the fastest tablet I have ever used, and I want to continue using it until the Quad Core A15 era’s here.
The stock web browser works fine enough, but I am more of a fan of Dolphin HD and Chrome. Even with more than a dozen of webpages opened in different tabs, the Fatty2 remained super responsive with no delay and lag at all. Most apps I have used on this device work perfectly, but with this resolution you will find a few of the apps specifically made for 16:10 screens appeared somewhat distorted on the Fatty2’s display, but I don't mind that as the screen and colors are incredibly amazing, and until you hold this in your hand it’s hard to put in writing just how beautiful it really is.
With 1GB of DDR3 RAM, the Fatty2 isn’t as strong as the PIPO M9 in multi-tasking, with lots of big applications running at the same time the smoothness could be crippled. By big applications I am not talking about the chatting apps such as Skype and ICQ, or even games like the “Angry Bird” and “Temple Run”, I am talking about real big apps such as “IRON MAN 3” and some Office applications. So, for anyone who’s not a psycho tester like myself, the Fatty2’s RAM is enough!
Although the Fatty2 isn't exactly the most incredible multi-tasker, it really shines in the game department. In both portrait and landscape modes, the tablet is easy to hold and control, making it a snap to play games where you need both thumbs on the screen. One-handed tapping and swiping is easy as well, thanks to the form factor of the unit. While you can appreciate the size of a 10-inch tablet for gaming, the 7.9 feels very good in your hands. Also, it had no issues with any of the games I opened up on it, ranging from “Temple Run 2” to “Fruit Ninja: Puss in Boots” to “Virtua Tennis” to that lone pre-loaded level of “Dead Space”. I even loaded the insanely graphic-intense “Need for Speed: the Most Wanted”, and quickly became obsessed with the fast racing and crushing. Despite the fact that these games can be processor intensive, particularly on a tablet, I had no issues whatsoever.
Movies and Videos play very well with the stock video player and there are several on the market you can use if you find videos that do not work on the stock player. In my actual test, I have no problem playing any local video file in my mobile disk. Even with a few 1080P videos which cannot be played through hard-decision decoding, you can use soft decode them smoothly, thanks to the extremely powerful RK3188 quad core chipset.
Audio
Sound-wise, while the HD videos really show off what this tablet is capable of, you'll want some headphones or an external sound solution. I am not saying the Fatty2’s speakers are bad, in fact, it is much better than most of the 7-8 inch tablets I have used in the audio department. But the single speaker still doesn't pack nearly as powerful an audio punch to match the visuals. Even at full volume, sounds like a whirring computer fan or a printer will easily drown out anything from the tablet.
Cameras
The cameras mounted on the ICOO Fatty2 aren't anything to write home about. Rear camera photos are decent, especially if you have enough light, and shooting video in 720 HD also can be seen as a bonus.
Of course, 5MP cameras on different Chinese tablets perform pretty much the same, and the Fatty2 isn’t really disappointing, it just cannot produce crisp HD photos that you would expect to go with this fabulous display. It is still worth using the camera on-board, especially because if you've ever seen someone holding up a full-sized iPad to take a photo or shoot video, you know how ridiculous they look. With this sleek 7.9-inch pad, it's much easier to get away with using it as a camera and not looking like you're a protester at a rally.
Connectivity
The Fatty2 is well equipped in terms of connectivity. There is a Micro USB connector for computer connection. There is a microSD card slot as well. The 16GB of internal storage helps too.
The Wi-Fi support includes a/b/g/n versions, with both 2.4GHz and 5GHz band compatibility. Wi-Fi Direct and DLNA support are also available. In my actual test, the Fatty2’s Wi-Fi reception is more than satisfactory, thanks to the M500 Wi-Fi module it features. This type of Wi-Fi Module is more often seen on those high-end smartphones. Below is the readings of Wi-Fi Analyzer on different spots and the comparison with readings of other tablets:
Also, the addition of Bluetooth is always a good thing, not only can u use it to transmit files without a data cable, u could also connect your tablet to those bluetooth input and audio devices:
Naturally, the Fatty2 supports USB on-the-go, and the adapter is already packaged in the paperback box along with the tablet. You can connect card readers, USB flash drives and other compatible devices to your tablet and access their contents through the file manager. Mice and keyboards are supported as well.
Unlike the iPad or Samsung Galaxy tabs, there is an independent mini HDMI port, all you need to do is to buy a $5 HDMI cable, and you can enjoy your tablet content on a much bigger screen.
Battery Life
The tablet is powered by a 5500mAh battery which, coupled with the power-efficient 28nm RK3188 SoC., is more than enough to make the Fatty2 one of the best tablets in terms of battery backup. In our battery test the slate achieved a score of 86 hours. This means that if you use the Fatty2 for an hour each of gaming, web browsing, and video playback every day, you will have to recharge it every 86 hours. And the tablet stood 11 hours, 55 minutes of online video streaming (30% of screen brightness, 50% of speaker volume), blowing the Beneve Miracle One’s 10 hour record out of the water:
In local video playback, the ICOU Fatty2 broke the long-held record by Samsung Galaxy Tab 7.7, and smashed the other 8-inch Android tablets I’ve tested:
Charging the tablet is relatively fast, with the buddle 5V-2A charger you only have to wait 3 hours for a full charge (0%—100%). Shutdown charging support not only guarantees the efficiency, but also gives the tablet a longer life span.
Verdict
The good:
1. The screen is truly impressive. Although the resolution doesn't match the iPad4 and Nexus10's Retina Display, it is definitely in the same ballpark and provides very crisp images.
2. The slim chassis and narrow bezel design make holding the tablet in one hand no longer that much of an effort.
3. The slew of ports and slots the Fatty2 provides for its users are truly wonderful, you no longer need to buy expensive adapters to enjoy functions such as HDMI or OTG.
4. The Wi-Fi reception of the tablet is amazing, arguably the best I have experienced on a Chinese tablet.
5. The 5500mAh battery paired up with the power-efficient RK3188 SoC. gives the tablet an incredible 10-12 hours’ run time.
The bad:
1. The price is the biggest barrier to fully enjoying the Fatty2. Although compared to the iPad and the bunch of Samsung tablets, it is incredibly cheap already, yet its major competition comes from other Chinese tablet makers: the Yuandao Mini One, the Chuwi V88s and CUBE U35GT are all $30 cheaper than the Fatty2.
2. The Fatty2 ships with Android 4.1 Jelly Bean and uses the stock user interface. Although ICOO has promised an upgrade to Android 4.2 and a delicately designed Metro Launcher, and there are already a few beta ROMs out there. However, without a clear date in sight who knows when the official ROM will arrive.
3. With the 7.9 inch display and similar-sized chassis, it is pretty much another iPad mini look-alike, and this can bring you some queerish stares and annoying questions.
Final verdict
The form and size of the Fatty2 feels perfect for a device you can grab to take with you for a long trip, a meeting, or a trip to the ballpark. It isn't as unwieldy as a 10-inch tablet, but the tradeoff is the screen loses real estate previously devoted to input. As a result, it doesn't feel like a serious business device, even if you paired it up with the Bluetooth keyboard, the lack of capable Office applications is still standing in the way of carrying this Android slate around for tight-scheduled business meetings.
What you will really find in the Fatty2 is a very pretty, functional media device. Android fans should consider this device if it fits their needs, but with other similar options in lower price ranges, you'll want to take a hard look at those needs and decide if it actually works for what you need it to do. For a casual entertainment unit, it works well. Any more than that, and you're going to find the capabilities stretched very thin.
With more Chinese tablets coming to the table every day, most now in quad-core configurations and with equally impressive screen options, the Fatty2 faces quick obsolescence unless it can compete. A price drop and software upgrade would be a big step in the right direction.
This review took me weeks to finish, why doesn't anybody care to read it?
Sent from my XT910 using xda premium
jupiter2012 said:
This review took me weeks to finish, why doesn't anybody care to read it?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
because it's too long.
Wow nice review, where did you buy?
vetro5 said:
Wow nice review, where did you buy?
Click to expand...
Click to collapse
Yes, and more importantly, where to buy at $149. USD. The prices I have seen via Google search point to $200. USD and upward, so far. I also tried eBay and even the Fatty 1 is $160. USD, and again, the Fatty 2 is over $200.
Quite impressed. Now want to see if there are any bugs and kinks, strange things etc, which you never know about from a smaller brand and a smaller user base.
Where i can get model like this (clone of iPad mini) but with:
- Android 4.1 (+)
- quad core processor
- 2gb of ram
- 16gb of storage
- GPS integrated (so i can use offline navigation software like Sygic or Mireo)
- the same screen size 7,85" or 7,9"?
I loocked MSI Primo 81, Yuandoa Vido mini one and Cube U55gt - but this models have not GPS
Is there any good china tablet with my spec?
sylver said:
Where i can get model like this (clone of iPad mini) but with:
- Android 4.1 (+)
- quad core processor
- 2gb of ram
- 16gb of storage
- GPS integrated (so i can use offline navigation software like Sygic or Mireo)
- the same screen size 7,85" or 7,9"?
I loocked MSI Primo 81, Yuandoa Vido mini one and Cube U55gt - but this models have not GPS
Is there any good china tablet with my spec?
Click to expand...
Click to collapse
Perhaps you should check the goopad android-sale.com
More specifically - http://android-sale.com/goopad-mini-3g.html
fortissimo said:
Yes, and more importantly, where to buy at $149. USD. The prices I have seen via Google search point to $200. USD and upward, so far. I also tried eBay and even the Fatty 1 is $160. USD, and again, the Fatty 2 is over $200.
Quite impressed. Now want to see if there are any bugs and kinks, strange things etc, which you never know about from a smaller brand and a smaller user base.
Click to expand...
Click to collapse
The retail price in China is RMB899, which is like 149 USD. But the price may vary in different countries, in relation with the taxations and transportation costs.
Hello,
Nice review thanks I wanted to buy this tab and now that I've read your review I want to buy it even more. But I have a question where did you bought it please ? I've founded it on many sites but I don't know any reliable sites where to buy it. I would be very pleased if you could tell me where you bought it. Thanks
Ramir0u said:
Hello,
Nice review thanks I wanted to buy this tab and now that I've read your review I want to buy it even more. But I have a question where did you bought it please ? I've founded it on many sites but I don't know any reliable sites where to buy it. I would be very pleased if you could tell me where you bought it. Thanks
Click to expand...
Click to collapse
I am Chinese, so i nought it on TAOBAO. I guess there are also a lot of online shop for oversea buyers.
jupiter2012 said:
This review took me weeks to finish, why doesn't anybody care to read it?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
With the Power button at the back of the tablet, is it very often that you turn off your screen accidentally?
Just bought one... hope wifi problems wont happen to mine by the way thanx for the review
Sent from my HTC Sensation using xda app-developers app
darkest_lightning said:
Just bought one... hope wifi problems wont happen to mine by the way thanx for the review
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Does anyone know where can we update the firmware ?
I have seen some info that there is Android 4.2.2 for fatty2 but i can´t find the rom to download
In this link from their site says that fatty 2 has android 4.2.2 ...
www.aoicoo.com/en/ProShow.asp?id=40
but to download roms it goes to a chinese site:
http://soft.aoicoo.com/
Could someone from China please help cause i cant understand chinese ....
Regards,
butcher
The Chinese post office site finally says my tablet is send so i'm waiting for it now :laugh:
I did some google translate on the link you provided and came up with a download for the fatty 2 and the fatty 2 2gb version.
but it seems to me like the only language in the update is simplified chinese... hope it 's not
the home page with lots of firmware directions:
http://translate.google.com/translate?hl=nl&sl=zh-CN&tl=en&u=http://soft.aoicoo.com/
the fatty 2 upgrade:
http://translate.googleusercontent....id=295&usg=ALkJrhjK0r_oqPfz-rvjutlU33jwZrd-yw
(downloading takes like forever, its half an hour now...)
hope this helps a bit.
let me know is if you update your firmware and have some other languages besides simplified chineese.
grtz
---------- Post added at 08:03 PM ---------- Previous post was at 07:15 PM ----------
just finished downloading the firmware and took a look inside the files with googletranslate.
looks like you can set it to English also.
readme file:
Fuzhou Rockchip Electronics Co., Ltd.
Unified production tools
User Instructions
2010-3-20
Document Revision History
The date of enactment Compiler version number / modify people modify the description Effective Date Remarks
1.0 2010-3-20 Cw edition
1.1 2010-10-12 LY increased error description
1.2 2011-06-28 LY configuration parameters to increase the data dial operation
1.3 2011-11-15 LY increased quickly check firmware mode
1.4 2012-03-02 LY increased common setup instructions
Directory
Overview 4
1 using the object 4
2 Component Overview 4
2.1 Tools directory structure 4
2.2 The configuration file used to set 4
2.2.1. Language Day 4
2.2.2. System section 5
2.2.3 Configuration 6 commonly used functions
3 Step 6 Use
3.1 modify the configuration file 6
3.2 Installing the Driver 7
3.3 firmware upgrade nine batches
3.3.1 Interface Introduction 9
3.3.2 Procedure 9
3.3.3 Error Messages Explained 9
4 Precautions 10
Outline
Unified production tools Rockchip Microelectronics Co., Ltd. is to improve customer productivity tools specifically developed . The tool is primarily used in factories in large quantities of the product firmware upgrade operation.
1 Using Objects
The need for large quantities of the product firmware upgrade factory.
2 Component Overview
2.1 Tools directory structure
config.ini
Tool configuration file that can be used to set the language and upgrade tools related properties , methods are detailed profile specific settings common settings .
Language
Language file storage directory , all currently supported language files are stored in this directory .
Log
Log storage directory , save the log normal upgrade process output and error information, log function can be modified in the configuration file to enable or disable items LOGFLAG recommended that you turn facilitate future error analysis.
RKBatchTool.exe
Production tools program
2.2 The configuration file used to set
Note: red for common setting items
2.2.1. Language Day
Kinds = 2 / / current number of tools to support all of the languages
Selected = 1 / / Specify the current tools used language
/ / Selected = 1 ( Chinese ); Selected = 2 ( English )
LangPath = Language \ / / language directory where the file
Lang1File = Chinese.ini / / Chinese language file
Lang1FontName = Arial / / Chinese language fonts
Lang1FontSize = 9 / / Chinese language font size
Lang1Tag = CHN / / Chinese language logo
Lang1CHNTitle = Chinese / / Chinese language selection Chinese display title
Lang1ENGTitle = Chinese / / English language selection Chinese display title
Lang2File = English.ini / / English language file
Lang2FontName = Arial / / English language fonts
Lang2FontSize = 9 / / English Language Font Size
Lang2Tag = ENG / / English language identification
Lang2CHNTitle = English / / Chinese language selection English Show Title
Lang2ENGTitle = English / / English Language selection English Show Title
2.2.2. System section
RKUSB_VID = 0x2207 / / RockUsb device VID, not set , venting can
RKUSB_PID = 0x290A / / RockUsb device PID,, do not set , venting can
MSC_VID = 0x0BB4 / / MSC device VID, not set , venting can
MSC_PID = 0x2910 / / MSC device PID, not set , venting can
FORCEFLAG = FALSE / / whether to adopt mandatory erasure, have not used
FORMATFLAG = TRUE / / if the user after the upgrade disc is formatted , format set TRUE , other values without formatting
DISKVOLUME = Rockchip / / formatted disk volume label for the specified user
COPYFLAG = TRUE / / upgrade directory or file is copied to the user's root directory , set TRUE copy, other values are not copied
DEFAULT_COPYDIR = / / copies the specified directory or file you want to copy the path
FORMATDATADISKFLAG = TRUE / / if the data after the upgrade disk is formatted , format set TRUE , other values without formatting
DATADISKVOLUME = Rockchip / / formatted disk volume label for the specified user
COPYDATADISKFLAG = TRUE / / upgrade directory or file is copied to the root directory of the data set TRUE copy, other values are not copied
DEFAULT_DATADISK_COPYPATH = / / copies the specified directory or file you want to copy the path
LOGFLAG = TRUE / / logging , set TRUE Enable logging , other values close the log function
SUPPORTLOWUSB = TRUE / / scan full speed usb device switch, set TRUE to scan Full speed usb device , other values are only scan high speed usb device
DEFAULT_FIRMWARE = / / default load firmware path , specify the default firmware path, the tool starts automatically when you open the default firmware
CHECK_MACHINE_MODEL = TRUE / / Firmware matching checking function ,
By setting CHECK_MACHINE_MODEL items, you can check before upgrading the firmware upgrade is allowed , permitted
Conditions to keep the value of the device firmware file MACHINE_MODEL parameter values match.
QUICK_CHECK_MODE = TRUE / / Quick check firmware switch is set to TRUE open the Quick checksum firmware functionality, but this feature is not complete parity there is a certain risk.
FW_VERSION_MODE = / / firmware version display format
DEC: Decimal display
Other: hexadecimal display
MISC_MODIFY_MODE = / / MISC partition to modify signs,
WIPE_ALL: erase userdata, cache and user area
WIPE_DATA: erase userdata and cache area
Other values are not modified by the original partition contents misc
MSC_WAITTIME = 30 / / Wait Msc device re-connection time ( unit: seconds )
RKUSB_WAITTIME = 20 / / Wait RockUsb device re-connection time ( unit: seconds )
2.2.3 configuration commonly used functions
Open Demo copy function:
Set FORMATFLAG = TRUE,
COPYFLAG = TRUE,
DISK_VOLUME = disk label
DEFAULT_COPYDIR = file or directory to be copied path
Android projects need to add a setting:
MISC_MODIFY_MODE = WIPE_DATA; prevent users after copying disk data recovery program to be erased
3 Use the procedure
modify the configuration file
Plug the device to be upgraded , if prompted to find new hardware , install the driver Rockusb
run the tool, select the firmware upgrade
3.1 modify the configuration file
Modify the configuration file , see the configuration file used to set
3.2 Installing the Driver
Before upgrading the firmware , turn off the player. Press and hold the upgrade button and simultaneously connect the device to a PC USB port. If you have not installed device drivers , it will pop up the following tips:
Select " Install from a list or specific location ( Advanced ) " and click Next.
Select the driver folder rockusb.sys
This completes installation of the USB device driver .
3.3 Batch firmware upgrade
3.3.1 Interface Introduction
3.3.2 Procedure
plug the device
Select the firmware
Verify that the device enters Rockusb state (Maskrom and Loader states belong Rock usb state )
upgrade or repair equipment
3.3.3 Error Messages Explained
" Failed to load configuration information can not be operated " because Config.ini file loading error , you can get from a publisher file to replace the correct Config.ini
" Failed to load firmware , you can not operate ! " No choice because the firmware or the firmware can not be read correctly lead , make sure that the firmware is correct
" other operations are running , please wait ! " As other operations currently in progress , please wait until the other end of the operation then
" device not found , unable to operate ! " Please confirm whether the device is connected, or whether Rockusb state
" creation process fails, you can not operate ! " Please restart the program before proceeding
" object create operation fails, you can not operate ! " Please restart the program , and then when the line operation
" does not support this type of equipment can not be operated ! " Please confirm whether the device into the Rock usb state , if the current state of the U disk , first switch before doing so
4 Precautions
batch upgrade multiple devices connected to the same HUB best on while upgrading equipment should not exceed four .
modify the configuration file , you need to re-run production tools
use of production tools , do not open other upgrades
production tools in the production process to the device automatically generates a UID unique code , the only code you need to ensure reliable, please use a computer equipped with a card production tools .
When Boot firmware version update , we recommend using the repair function to do the upgrade .
darkest_lightning said:
The Chinese post office site finally says my tablet is send so i'm waiting for it now :laugh:
I did some google translate on the link you provided and came up with a download for the fatty 2 and the fatty 2 2gb version.
but it seems to me like the only language in the update is simplified chinese... hope it 's not
the home page with lots of firmware directions:
http://translate.google.com/translate?hl=nl&sl=zh-CN&tl=en&u=http://soft.aoicoo.com/
the fatty 2 upgrade:
http://translate.googleusercontent....id=295&usg=ALkJrhjK0r_oqPfz-rvjutlU33jwZrd-yw
(downloading takes like forever, its half an hour now...)
hope this helps a bit.
let me know is if you update your firmware and have some other languages besides simplified chineese.
grtz
---------- Post added at 08:03 PM ---------- Previous post was at 07:15 PM ----------
just finished downloading the firmware and took a look inside the files with googletranslate.
looks like you can set it to English also.
readme file:
Fuzhou Rockchip Electronics Co., Ltd.
Unified production tools
User Instructions
2010-3-20
Document Revision History
The date of enactment Compiler version number / modify people modify the description Effective Date Remarks
1.0 2010-3-20 Cw edition
1.1 2010-10-12 LY increased error description
1.2 2011-06-28 LY configuration parameters to increase the data dial operation
1.3 2011-11-15 LY increased quickly check firmware mode
1.4 2012-03-02 LY increased common setup instructions
Directory
Overview 4
1 using the object 4
2 Component Overview 4
2.1 Tools directory structure 4
2.2 The configuration file used to set 4
2.2.1. Language Day 4
2.2.2. System section 5
2.2.3 Configuration 6 commonly used functions
3 Step 6 Use
3.1 modify the configuration file 6
3.2 Installing the Driver 7
3.3 firmware upgrade nine batches
3.3.1 Interface Introduction 9
3.3.2 Procedure 9
3.3.3 Error Messages Explained 9
4 Precautions 10
Outline
Unified production tools Rockchip Microelectronics Co., Ltd. is to improve customer productivity tools specifically developed . The tool is primarily used in factories in large quantities of the product firmware upgrade operation.
1 Using Objects
The need for large quantities of the product firmware upgrade factory.
2 Component Overview
2.1 Tools directory structure
config.ini
Tool configuration file that can be used to set the language and upgrade tools related properties , methods are detailed profile specific settings common settings .
Language
Language file storage directory , all currently supported language files are stored in this directory .
Log
Log storage directory , save the log normal upgrade process output and error information, log function can be modified in the configuration file to enable or disable items LOGFLAG recommended that you turn facilitate future error analysis.
RKBatchTool.exe
Production tools program
2.2 The configuration file used to set
Note: red for common setting items
2.2.1. Language Day
Kinds = 2 / / current number of tools to support all of the languages
Selected = 1 / / Specify the current tools used language
/ / Selected = 1 ( Chinese ); Selected = 2 ( English )
LangPath = Language \ / / language directory where the file
Lang1File = Chinese.ini / / Chinese language file
Lang1FontName = Arial / / Chinese language fonts
Lang1FontSize = 9 / / Chinese language font size
Lang1Tag = CHN / / Chinese language logo
Lang1CHNTitle = Chinese / / Chinese language selection Chinese display title
Lang1ENGTitle = Chinese / / English language selection Chinese display title
Lang2File = English.ini / / English language file
Lang2FontName = Arial / / English language fonts
Lang2FontSize = 9 / / English Language Font Size
Lang2Tag = ENG / / English language identification
Lang2CHNTitle = English / / Chinese language selection English Show Title
Lang2ENGTitle = English / / English Language selection English Show Title
2.2.2. System section
RKUSB_VID = 0x2207 / / RockUsb device VID, not set , venting can
RKUSB_PID = 0x290A / / RockUsb device PID,, do not set , venting can
MSC_VID = 0x0BB4 / / MSC device VID, not set , venting can
MSC_PID = 0x2910 / / MSC device PID, not set , venting can
FORCEFLAG = FALSE / / whether to adopt mandatory erasure, have not used
FORMATFLAG = TRUE / / if the user after the upgrade disc is formatted , format set TRUE , other values without formatting
DISKVOLUME = Rockchip / / formatted disk volume label for the specified user
COPYFLAG = TRUE / / upgrade directory or file is copied to the user's root directory , set TRUE copy, other values are not copied
DEFAULT_COPYDIR = / / copies the specified directory or file you want to copy the path
FORMATDATADISKFLAG = TRUE / / if the data after the upgrade disk is formatted , format set TRUE , other values without formatting
DATADISKVOLUME = Rockchip / / formatted disk volume label for the specified user
COPYDATADISKFLAG = TRUE / / upgrade directory or file is copied to the root directory of the data set TRUE copy, other values are not copied
DEFAULT_DATADISK_COPYPATH = / / copies the specified directory or file you want to copy the path
LOGFLAG = TRUE / / logging , set TRUE Enable logging , other values close the log function
SUPPORTLOWUSB = TRUE / / scan full speed usb device switch, set TRUE to scan Full speed usb device , other values are only scan high speed usb device
DEFAULT_FIRMWARE = / / default load firmware path , specify the default firmware path, the tool starts automatically when you open the default firmware
CHECK_MACHINE_MODEL = TRUE / / Firmware matching checking function ,
By setting CHECK_MACHINE_MODEL items, you can check before upgrading the firmware upgrade is allowed , permitted
Conditions to keep the value of the device firmware file MACHINE_MODEL parameter values match.
QUICK_CHECK_MODE = TRUE / / Quick check firmware switch is set to TRUE open the Quick checksum firmware functionality, but this feature is not complete parity there is a certain risk.
FW_VERSION_MODE = / / firmware version display format
DEC: Decimal display
Other: hexadecimal display
MISC_MODIFY_MODE = / / MISC partition to modify signs,
WIPE_ALL: erase userdata, cache and user area
WIPE_DATA: erase userdata and cache area
Other values are not modified by the original partition contents misc
MSC_WAITTIME = 30 / / Wait Msc device re-connection time ( unit: seconds )
RKUSB_WAITTIME = 20 / / Wait RockUsb device re-connection time ( unit: seconds )
2.2.3 configuration commonly used functions
Open Demo copy function:
Set FORMATFLAG = TRUE,
COPYFLAG = TRUE,
DISK_VOLUME = disk label
DEFAULT_COPYDIR = file or directory to be copied path
Android projects need to add a setting:
MISC_MODIFY_MODE = WIPE_DATA; prevent users after copying disk data recovery program to be erased
3 Use the procedure
modify the configuration file
Plug the device to be upgraded , if prompted to find new hardware , install the driver Rockusb
run the tool, select the firmware upgrade
3.1 modify the configuration file
Modify the configuration file , see the configuration file used to set
3.2 Installing the Driver
Before upgrading the firmware , turn off the player. Press and hold the upgrade button and simultaneously connect the device to a PC USB port. If you have not installed device drivers , it will pop up the following tips:
Select " Install from a list or specific location ( Advanced ) " and click Next.
Select the driver folder rockusb.sys
This completes installation of the USB device driver .
3.3 Batch firmware upgrade
3.3.1 Interface Introduction
3.3.2 Procedure
plug the device
Select the firmware
Verify that the device enters Rockusb state (Maskrom and Loader states belong Rock usb state )
upgrade or repair equipment
3.3.3 Error Messages Explained
" Failed to load configuration information can not be operated " because Config.ini file loading error , you can get from a publisher file to replace the correct Config.ini
" Failed to load firmware , you can not operate ! " No choice because the firmware or the firmware can not be read correctly lead , make sure that the firmware is correct
" other operations are running , please wait ! " As other operations currently in progress , please wait until the other end of the operation then
" device not found , unable to operate ! " Please confirm whether the device is connected, or whether Rockusb state
" creation process fails, you can not operate ! " Please restart the program before proceeding
" object create operation fails, you can not operate ! " Please restart the program , and then when the line operation
" does not support this type of equipment can not be operated ! " Please confirm whether the device into the Rock usb state , if the current state of the U disk , first switch before doing so
4 Precautions
batch upgrade multiple devices connected to the same HUB best on while upgrading equipment should not exceed four .
modify the configuration file , you need to re-run production tools
use of production tools , do not open other upgrades
production tools in the production process to the device automatically generates a UID unique code , the only code you need to ensure reliable, please use a computer equipped with a card production tools .
When Boot firmware version update , we recommend using the repair function to do the upgrade .
Click to expand...
Click to collapse
Hello darkest_lightning
Thanks for your awnser.
But one problem still resides. where is the Android 4.2.2 because the firmware version of Fatty 2 and Fatty 2 2G are of Android 4.1.1 ...
Maybe it´s bull**** of them in the english site that the fatty 2 can have Android 4.2.2
But many thanks for your post
Regards butcher
Got my fatty yesterday... must say i'm pretty pleased with it. It's fast, wifi s good, comes in english, nice screen and fully charged i used it for 3-4h and still has 65% battery left. There are some chinese apps and market on but you can hide them so they wont bother. Didnt do the firmware update yet but everything seems working well for now
Sent from my HTC Sensation using xda app-developers app
Article too long, I only saw a few pictures.
darkest_lightning said:
Got my fatty yesterday... must say i'm pretty pleased with it. It's fast, wifi s good, comes in english, nice screen and fully charged i used it for 3-4h and still has 65% battery left. There are some chinese apps and market on but you can hide them so they wont bother. Didnt do the firmware update yet but everything seems working well for now
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
darkest_lightning it comes with 4.1 ? or 4.2 ?
Regards,
Butcher
the_butcher said:
darkest_lightning it comes with 4.1 ? or 4.2 ?
Regards,
Butcher
Click to expand...
Click to collapse
Hi,
Butcher looks like it's 4.2.2
Grtz
darkest_lightning said:
Hi,
Butcher looks like it's 4.2.2
Grtz
Click to expand...
Click to collapse
Hi darkest_lightning
Well i think they let out the firmware of 4.2.2 because i downloaded this firmware from soft.aoicoo.com:
I installed one of this LOL don´t know witch one ...
2013-10-11 › [F 系列升级固件]Fatty2 多视窗软件363
2013-10-11 › [F 系列升级固件]Fatty2 多视窗软件362
and it is Android 4.2.2
Very nice by ICOO released the new firmware and it looks like 4.1.1 because surfing the net is smooth like hell
Regards,
Butcher
[REVIEW] Phablet/Console Much i5 (5" Quad-Core)
Note
Due to the limitations of this forum, i cannot put the full version of the review. THIS IS NOT THE FULL REVIEW ARTICLE
For the complete version of this review visit my blog .
Package contents(Unboxing y full description of the package contents)
When the package is opened, we found the following elements that, i understand, are part of any standard shipment for this product.
Much i5 Device
Quick guide
Guarantee sheet
MicroUSB cable
USB Wall charger
3550 mAh Battery
Serial number sticker
About first impression
My first impression of the device was so good. I really feel that the device materials and quality is distinct that other devices i tested.
There is lots of details that make a difference, from the device design, or the software included, or the customization made on the system, etc.
The first time you boot the device, you get a screen to register an iMuch account. This is not required really, but you can do these steps to gain access for Much services (note: most in chinese). In my tests, i remove my Much account, and i can use the device without problems.
(First boot)
There is a icon called Much Helper, that really is a quick guide to use the device, that is so interesting and helpful (this come in english), and show you in short steps the main features of the device and how to use.
Is really nice get a device like this that manufacturer take care about heir users, and provide ways to get familiar and comfortable with the device like this (and in english, a common language).
Another thing that i get may attention is that this device come with no much bloatware, and the games listed are to download from the google playstore (instead of a separated store with software from a non clear origin)
Most of this games are free, or demo versions.(and i thanks for it, because the system come with no unecessary software pre-installed)
Product information
According with the manufacturer, or searching info on web pages, we can found many sources of information about the device and sometimes these information may be not consistent (may be different from one web page to other), and this may cause some confusion for anybody that wants to get info about this product.
On this section i will post the info i get from the manufacturer (or is not possible, the web page that i consider more reliable), listing only the relevant points for a tech analysis of the product, and omit these points that don´t get any relevant info about the device (as many time we found on many pages, things such video capabilities, mail capabilities, etc, that really are software based features that we can install on the device, and not a real feature of the device itself)
CPU(RAM): MTK6589 quad-core 1.2GHz Cortex A7
GPU: PowerVR Series 544
RAM: 1G RAM LPDDR2
Internal: 4GB ROM
Screen size: 5"
Screen resolution: 1280x720
Screen Type: IPS Panel, Multitouch 5 points
Operating System: Android4.2 (Much Launcher)
Storage: MicroSD(TF) support 64GB storage expand maximum
Sensor: Nine-axis sensing (gyroscope, electronic compass, and gravity sensing), and light-sensitive sensing, close up sensing
Camera: Main camera of 8 MPx, digital zoom, auto focus, microspur support, Flash LED. Front camera of 0.3 MPx;
Network Function: support WCDMA 850M/2100M GSM 850/900/1800/1900MHZ, HSUPA(high speed uplink):up to 11.5 Mbps,HSDPA+( high speed downlink):up to 42.2 Mbps
Wifi: 802.11b/g/n
bluetooth: V4.0LE +EDR
GPS: with AGPS support
Buttons: 4 action buttons, 2 Shoulder buttons, 2 special buttons (configurable), DPAD and 2 analog sticks.
Video Play: Hardware decoding, maximum resolution up to 1280x720P, H.264, MPEG4, MPEG2, VC-1, H.263
Audio System: D-class amplifier , AAC speaker (2x0.5w)
Power Supply: 3550mAh Lithium battery
Charge: dual interface charge, (Bottom) Micro USB charge interface 1A charge, (Top) Micro USB charge interface 500mA charge maximum.
TV-Out: Mini HDMI interface (support 1080P)
USB: MicroUSB OTG 2.0
Dual standard SIM card(WCDMA/GSM) + MicroSD(TF) card
size: 184.0x88.0x14.7mm
Antutu X Benchmark
Summary:
RAM Operation: 1089
RAM Speed: 502
CPU integer: 1819
CPU float-point: 1242
2D graphics: [720x1280] 646
3D graphics: [720x1280] 3294
Storage I/O: 832
Database I/O: 515
CPU frequency: 1209 MHz (x4)
Multitask: 2661
Dalvik: 780
Total: 13380
ClockWorkMod Recovery (Custom Recovery)
Android have a special mode called Recovery, that is used many times to recover the device if this have problems to run properly, but there exist an alternative Custom Recovery that add a lot of new functionality and tools, and one of the most popular is one called ClockWorkMod Recovery.
There is a full functional version of this recovery that run on this device.
One of the most important features of this custom recovery, is the NANDROID generation, a way to generate a full backup of the nand (where the operating system resides) to a directory, and can be used as a recovery point for the device in case of semi-brick, or simply if you want to get a clean firmware on it.
Take note that this backup (nandroid) is a image of the NAND, this means, there will be stored all your configs, users, passwords, accounts, etc. Is a good idea to get a clean firmware insatlled on the device, and install and configure all your base programs (file admins, cloud services, google account, etc) and then get a nandroid for your personal use. When you get back to this image/backup, you will get a clean and configured system, saving lot of time on basic configurations and installing basic software.
The installation of CWM on this device is easy. For this, i follow the next thread on XDA forum:
How to install CWM on most rooted mtk devices
This method is based on Rua1 tool (a russian guy that develop a specific MTK took), and i will try to explay step by step.
First, you need the drivers ADB installed on the system. If you don´t get yet, then download and install PDANet (for windows, there is the 4.12 installer).
Then install PDANet, and when the program ask for connecting the device (USB), connect your Much.
Program will install drivers (if ask to you, select "other manufacturer" for generic drivers)
When you get installed this program, then go and download "MTK Droid Root & Tools | MediaTek Android Smartphone" ver 2.4.8 (from this thread on XDA)
Run the program. If the antivirus or firewall warning about a unknown thread, ignore it.
The program will run adb and connect with your device. No matter if you set root for ADB and Apps in System Settings, the program will inform that the device is not fully rooted. (there is a yellow rectangle)
Press ROOT button.
When finished, the rectangle will be green
(I will do a copy paste from XDA thread, because is well explained what you must to do)
Click on the tab 'root,backup,recovery' and select 'to use boot from phone' then click on 'recovery and boot' and shortly after a dialogue box will appear asking if you want to 'make cwm recovery automatically' click yes
System start to generate the CWM version.
Is possible that the tool show a dialog with a warning "ATENTION! There is a probability to damage the boot block!". Select "Yes"
Android Games
Asphalt 8: Airborne
(Using Tincore to control the game)
Jet Set Radio
Bard´s Tale
Dead Trigger
N.o.v.a. 3
Using HDMI TV Out, External controller (PXN8633 Wireless controller with USB receiver) and Tincore to map the controller to screen.
Modern Combat 4: Zero Hour
Using HDMI TV Out, External controller (PXN8633), and Tincore for mapping.
Ravensword
Grand Theft Auto Vice CityUsing External Controller and Tincore for mapping.
DraStic (Nintendo DS)
Zelda Phantom Hourglass
PPSSPP (Playstation Portable PSP)
Lego Indiana Jones 2
Mame4Droid Reloaded (Arcades)
Garou: Mark of Wolves
Marvel vs Capcom
Retroarch
Arcade (MAME) - Ultimate Mortal Kombat 3
PSX - Tekken 3
N64Oid (Nintendo 64)
Bad Fur Day
(Gameplay)
About Battery
Some words i must to say about this point. This device is the first handheld gaming console that i forgive to take care constantly about battery level. In fact, using as a normal smartphone and as a gaming console, is a heavy use for me, more than my normal smartphone (i like to use a Motorola Razr), and my phone, only as phone, battery is not longer than Much device.
I don´t know how many hours it can be working, but i´m sure is enough for most of users that want a good duration.
Check the following screenshots:
These 3 screenshots was taken when i get in home, in night (well, really when i remember to take these screenshots)
The most important of these screenshots, are that the device was working as normal usage, with WIFI enabled, one SIM card enabled, and most time (when i´m in train or bus) with Bluetooth enabled (for bluetooth audio), with all normal options for a smartphone standard enabled (GPS, Vibration, etc), and most important, playing normally, and the battery, well, you can see the images. For this reason i can mention that i forgot to check constantly the battery level, to calculating how many time i can play, or anything.
And of course, the battery is replaceable, then if you really need more battery duration, simply buy another battery pack, and carry with you to replace when you go out of power.
Final words
Apologize for the mistakes i did writing in english. As many of you know, this is not my natural language, but i did my best to try to bring to you a readable and understandable article that, sincerely, i hope is useful.
And remember this is not a full article review. It is only a Summary.
Zalu2!
Deen0X
re-install MUCH I5
Hello,
I have one Much I5. This device was bricked somehow and I need to re-install it. I made all the instruction on your blog but after pressing Vol- android screen suddenly disappear and I can only see ireadygo screen and I could not do anything else. Could you help me to re-install this device may be from pc ?
Thank you & best regards,
Device Info HW
version: 5.8.3
Device Info HW is a hardware and software information app for Android devices.
App trying detect components of your smartphone to provide complete information about device's hardware.
Now detection is supported for lcd, touchscreen, cameras, sensors, memory, flash, audio, nfc, charger, wi-fi and battery; if that possible for your device.
I think app is interesting and useful for users and developers who build kernels or android.
App has a quick navigation, fresh design. Also supports dark, black theme (in PRO version or 2 week in free)
You can switch by tab or use navigation panel. Many items are clickable and you can go to another tab or menu.
On recent devices reading some information is blocked.
App trying provide maximum information as possible. If you have root, app can read more (switch in settings)
Components
LCD - model. For recent android detection require root.
Also you can check the colors in lcd test.
Touchscreen - show model, also you can check how much fingers are supported in multi-touch test.
Camera - hardware info (model, vendor, resolution) and software info by API.
If can't detect camera model, sometimes available a list of supported cameras.
Detailed info about SoC in you device
CPU : model, cores, clusters, family, abi, governor, frequency
GPU : model, vendor, opengl, frequency, list of extensions
Click on the clock speed to open CPU monitor
System: complete info about your firmware build.
Memory: type lpddr and for some devices operating frequency.
Flash: chip and vendor emmc or ufs (scsi).
You can go to the memory tab and see usage of memory and storage.
Battery: base info and for some devices available extra info:
- Discharging speed is current consumption
- Charging speed is charge current minus current consumption
- Power profile - encoded by manufacturer for calculate consumption
* Kernel profile
* Model
Thermal: temperatures by thermal sensors
Sensors: availability of basic sensors and tests for them
Applications: you can quickly find apps and see info about it, also provided system apps
Drivers: you can find other chips used in your device.
Partitions: list of partition and their sizes.
PMIC: list of power regulator voltages which applied to the components.
Wi-Fi: info about connection
Bluetooth: supported features
Input devices: list of input devices.
Codecs: decoders and encoders, drm info
USB: connected devices by otg
Extra options:
- Show i2c address of the chip
- Open engineering menu for mtk and xiaomi
- List of CPU codenames for Qualcomm, mtk, HiSilicon
Devices database
You can find info for other devices, compare and check similar drivers. It available on web page: deviceinfohw.ru
Also you can upload your device info. See to the Info Center.
PRO VERSION
• Theme
Supports all a light, dark and black theme, choose what you like.
In the free version, black available 2 weeks for the test.
• Report
You can create a report with information about the device.
It will be saved in file HTML or PDF format.
You can open it or send to email by share button.
See example:
deviceinfohw.ru/data/report_example.html
• Copy text
Copy text by long press in info lists.
• New design of battery tab with charge / discharge chart
• Device list
List of i2c, spi devices.
It's useful when available many chips or they uncategorized.
Also this supports development to improve app.
Note:
Not for all devices can read drivers info, it's depend on soc, vendor. If you want help, then upload your device info.
If you want translate app for your language or have interesting ideas or found bugs, write me to email or forum.
Requirements :
- Android 4.0.3 and above
Permissions :
- INTERNET is required for upload device info. It's use only for manual upload.
- CAMERA is required for getting camera software characteristics for old camera api.
- ACCESS_WIFI_STATE is required for info about wi-fi connection.
Google Play:
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw
{
"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"
}
Awesome App. Well Done!
Tested on more than 10 Mediatek Devices, no issues found. I'll start to upload all my device's hardware info to your database as soon as possible.
Nice App Sir Keep Up The Good Work! :highfive:
Hey OP! Thank you very much for this app :good:
Version 3.0.5. Now we see in the Camera tab
I would like to that looked so
Please, if possible....
Good work bro
New version 3.3.1 released.
- Support samsung exynos platform: detect cameras, wi-fi (tested on galaxy s7)
- Improved cluster detection.
- Added audio chips and nfc detection.
- Improved components detection.
- Added Net tab with wi-fi info.
- Fixed crash on some 7.0 devices.
- Bugs fixes.
good app
New version 3.5.0 released.
- Begin support Huawei HiSilicon platfrom. Display detection (need root).
On some devices available all supported cameras.
- Improved components detection.
Fixed display detection on some devices samsung, htc (qcom).
Improved sensor detection for 2 in 1 chips (acc + gyro) .
Improved components detection for samsung devices.
- Added new tab Input devices
On mtk available touchscreen model and fw version (tested on goodix).
- New app icon.
* Who has samsung with 4.2.2 with crash or bug write to me for test. (Navigation View class not found on this devices)
New version 4.0.0 released.
1) Added battery charge / discharge speed.
a) For 5.0+ via Android API
b) For mtk special variant. Tested on mt6752, mt6589.
Discharging speed is current consumption. Ids = Ic
Charging speed is charge current - current consumption. Ics = Icc - Ic
2) New navigation panel.
3) Battery experimental.
mtk
Added battery profile from kernel. According to my data, in most cases it differs on +-5% from real capacity of the factory battery.
qcom
Added battery profile from kernel and battery model. Tested on msm8992.
4) Improved components detection.
5) Spreadtrum
Added detecting lcd id (need enable root in settings)
Exmple: ID066108 it means id 0x066108, found name is s6d77a1a01.
In camera tab added list of supported camera models.
6) Samsung
Exynos
Added detecting lcd id (need enable root in settings)
Exmple: ID_0x404024 it means id 0x066108, found name is S6E3FA0.
Detect camera models for spreadtrum, qcom, marvell pxa, broadcom. (need test)
7) Qualcomm
Added list of supported camera models.
8) List of system apps. Open from apps tab from last item.
List of OpenGL ES extensions.
9) Fix codepages in some lang.
10) Fix bugs and crash on some devices.
11) Device Info HW+ (PRO)
You can create a report with device information.
Saving in html file format. See example:
http://www.deviceinfohw.ru/data/report_example.html
4.2.1
- Huawei on qcom: improved support.
- List of supported cameras with vendor and resolution.
- Samsung on exynos: added gpu freq.
- Qualcomm: added lcd panel without root from sysfs.
- Engineering menu moved to navigation panel + miui cit.
- Updated components detection and fixed errors.
- Updated sensors tab (using Sensor Test 1.4+).
- Build with new sdk.
- Begin spanish and polish localization by Radek Strycharz.
- i2c device list groupped by bus [PRO]
ANDR7E said:
4.2.1
:
:
Click to expand...
Click to collapse
Awesome...
Can you add switch to show free RAM from /proc/meminfo?
hyperion70 said:
Awesome...
Can you add switch to show free RAM from /proc/meminfo?
Click to expand...
Click to collapse
Added it and swap/zram size too.
Maybe total ram will be correct for phones with fake ram size.
ANDR7E said:
Added it and swap/zram size too.
Maybe total ram will be correct for phones with fake ram size.
Click to expand...
Click to collapse
OP, thank you very much for the update 4.5.0.
New version 4.6.3
Version 4.5.0
- New material tab bar.
- Screen Test (lcd color, multi-touch, touch drawing)
- Cpu Monitor (press on clock speed)
- Dark theme support (2 week or PRO)
- Updated components detection.
- Optimizations.
- RAM from kernel (meminfo) + swap
- Some fixes for HiSilicon cpu detection.
Version 4.6.3
- Added partition info for some platforms.
- Added new lcd color tests.
- Added tab with USB devices
- Updated components detection.
- Asus qcom: try detect cameras.
- HiSilicon: added gpu freq.
- HiSilicon: try detect cameras (with root).
- CPU operating time (click to core count item)
- System: device features: list of the features enabled in firmware.
- System: extra sys info (click to system build fingerprint item)
(modem mtk, vm mem size, some vendor info)
- Try fix opengl bug for some devices.
- Try deep detect mt6757 P20 series => P20 / P20 series / P25 / P25 series
P.S.
Who want help translate app to own language, I provide strings resources https://github.com/andr7e/DeviceInfoHW_translations/
Partitions + Project (Nvidia Tegra 4)
ANDR7E said:
New version 4.6.3
Version 4.6.3
- Added partition info for some platforms.
Click to expand...
Click to collapse
I have just downloaded version 4.6.4.
Thank you very much for the partition info on Nvidia Tegra 4 (Toshiba Excite Pro AT10LE-A-). Can you improve it with names (like on MTK) and a switch to enable the traditional view too, please?
The information below will help you doing that. There is a link to two partition screenshots of this tablet in our XDA thread.
[Q] How Root Toshiba Excite Pro AT10LE-A-108
https://forum.xda-developers.com/showpost.php?p=74227484&postcount=39
So, here is partitions info of this tablet (attached file in black)
And their names (attached file in black)
According to Nexus 7 development thread, these are common names on Tegra tablets:
APP -> system
CAC -> cache
LNX -> boot
MDA -> encrypted userdata
MSC -> misc
PER -> per device calibration
SOS -> recovery
UDA -> userdata
USP -> bootloader
We are trying to unlock the bootloader of Toshiba Excite Pro AT10LE-A (Nvidia Tegra 4 device). There is a protection by the sealime.ko security module blocking some partitions. To defeat sealime.ko we need all the information available on partitions.
Another request is the Project information that is missing on Nvidia Tegra 4 devices. It has valuable information on LCM, modem, etc. Can you include it, please?
Thanks and best regards!
YuriRM said:
I have just downloaded version 4.6.4.
Thank you very much for the partition info on Nvidia Tegra 4 (Toshiba Excite Pro AT10LE-A-). Can you improve it with names (like on MTK) and a switch to enable the traditional view too, please?
Click to expand...
Click to collapse
Partition names are also supported. How it works:
1) Get partition block path from /proc/mounts by key system or cache
If finded it printed in log
2) Get mapping list like on your screenshots (some devices need root)
I see on toshiba tegra3 source, tegra4 didn't find.
LCM can't detect, in driver only set settings and init work.
https://github.com/pio-masaki/kerne.../arch/arm/mach-tegra/board-tostab12AL-panel.c
great.
add a option to show some sensor info on notification/notification icon may be useful
Tegra 4 Technical Reference Manual
ANDR7E said:
Partition names are also supported. How it works:
1) Get partition block path from /proc/mounts by key system or cache
If finded it printed in log
2) Get mapping list like on your screenshots (some devices need root)
I see on toshiba tegra3 source, tegra4 didn't find.
LCM can't detect, in driver only set settings and init work.
https://github.com/pio-masaki/kerne.../arch/arm/mach-tegra/board-tostab12AL-panel.c
Click to expand...
Click to collapse
I hope this helps!
Regards
Tegra 4 Technical Reference Manual
https://developer.nvidia.com/embedded/tegra-4-reference
The Tegra 4 Technical Reference Manual ("TRM") is a technical document of over 2,600 pages targeted at those working on open source or other low level software projects that use or target the Tegra 4 processor. The TRM focuses on the logical organization and control of Tegra 4 Series devices. It provides information for those modules that interface to external devices, or those that control fundamental chip operations. The modules detailed in this document provide an overview, any necessary programming guidelines, and a register listing for that module. Internal functional units such as video and graphics hardware acceleration are controlled by NVIDIA provided software and not documented.
NVIDIA provides access to the Tegra 4 Technical Reference Manual to registered developers only. To become a registered developer, please sign up for our Embedded Registered Developer Program.
If you are already a Registered Developer, you can download the TRM from our Download Center.
Table of Contents
Introduction
Address and Interrupt Map
Interrupt Controller
Arbitration Semaphores
Atomics
Clock and Reset Controller
CL-DVFS
Timers
Multi-Purpose I/O Pins and Pin Multiplexing (Pinmuxing)
Power Management Controller
Real-Time Clock
Boot Process
Host Subsystem
GR2D
GR3D
Encoder Pre-Processor (EPP)
Keyboard Controller
CPU
Flow Controller
Memory Controller
AHB
APB
USB Complex
Audio Hub (AHUB)
Display Controller
MIPI-DSI (Display Serial Interface)
Serial Transport Stream DTV Controller
High-Definition Multimedia Interface HDMI CEC MIPI-CSI (Camera Serial Interface) MIPI D-PHY Calibration for CSI and DSI Video Input (VI) SD/MMC Controller MIPI-HSI (High Speed Synchronous Serial Interface) I2C Controller UART and VFIR Controller Serial Peripheral Interface (SPI) Controller
One Wire Battery Controller
PWM Controller
Thermal Sensor and Thermal Throttling Controller
ANDR7E said:
tegra4 didn't find.
Click to expand...
Click to collapse
Tegra 4 device - Tegra Note 7
https://github.com/Shaky156/Tegra-Note-7/blob/master/arch/arm/mach-tegra/board-aruba-panel.c
https://github.com/Tegra4
Tegra 4 Device tree, kernel and vendor binaries for Gigaset QV1030 aka. Quanta FG6Q
https://fg6q-dev.github.io/
https://www.notebookcheck.net/Gigaset-QV1030.114384.0.html
https://www.notebookcheck.net/NVIDIA-Tegra-4-SoC.87052.0.html
Sent from my takee 1 using XDA Labs
YuriRM said:
Tegra 4
Click to expand...
Click to collapse
I wrote about your toshiba device, tegra 4 source is available. LCD model name is not set, only lcd params.