I9300XXDLG4 – Galaxy S III Android 4.1.1 Jelly Bean TEST firmware | SamMobile

I9300XXDLG4 – Galaxy S III Android 4.1.1 Jelly Bean TEST firmware | SamMobile

Download http://hotfile.com/dl/167223841/a094765/I9300XXDLG4_NO_CSC_NO_MODEM.zip.html

We Of SamMobile received the first firmware for the Galaxy S III based on Android 4.1.1 Jelly Bean.
This is the first firmware after many rumors about Jelly Bean for the Galaxy S III.
We already tweeted that Samsung is busy with this kind of update.
The update by KIES and OTA (over the air) will start at the end of this month begin next month.
Because there are many die-hard Samsung fans we want to give you the chance to test the first Jelly Bean rom by Samsung.

This is an PRE-RELEASE version so not official from KIES.
We want to give you a BIG warning when you want to test this firmware!
You will lose your warranty so please do not try this when you are not 100% sure!

The firmware: I9300XXDLG4 is based on Android 4.1.1
The build date is July 31 2012.

We have found a few visible changes.- A new clock (in line with JB vanilla) in the notification bar.
- A function called “Dormant mode”
- Google Now is accessed by touching the Google Search widget
- A couple of new Live Wallpapers
- “Palm swipe” lets you take a screenshot
- Reboot into “safe mode” (maybe just in test release)
- There’s probably more new features that we haven’t discovered yet. Please share your findings!

We also had some troubles, for instance the internal SDCARD got formatted and some apps can’t be installed due to problems with smdl2tmp1.asec (which can’t be found at all). These problems could also be local to the specific device. A good suggestion is to make backup of everything prior flash

Inside the download package you only will see the PDA code.
We have no CSC or MODEM file of this firmware. So please make sure you know what you do! It is possible to flash this on a csc and modem from ICS.

You can find the firmware by OPEN Europe in the download section
We reported this firmware with WARNING code because this is a LEAK and not an OFFICIAL KIES release!

ADVICE of SamMobile is wait for 15 days to get the official updates by KIES or OTA!!!!

But for developers this might be the key for a full working rom they are developing.

Flash instructions.
- Make sure to have an ORIGINAL rom before attempting to flash. (could brick if not)
- Unzip the file
- Open Odin 1.85
- Restart phone in download mode (Home+power+vol down)
- Connect phone and wait until you get a yellow sign in Odin
- Add CODE_I9300XXDLG4_11164_REV00_eng_mid_noship.tar.md5 to PDA
- Make sure re-partition NOT ticked
- Start flash, sit back an wait a few minutes.
- Once the phone have booted, you’ll probably get into a boot loop.
- Remove the battery and put it back again.
- Boot into recovery mode (Home+power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA!)
- Reboot. and you are good to go! (hopefully)

Screenshots:

asterisk cdr view- Simple and fast viewer for asterisk CDRs / recordings

asterisk-cdr-viewer - Simple and fast viewer for asterisk CDRs / recordings. - Google Project Hosting

asterisk cdr view
Simple and fast viewer for asterisk CDRs / recordings. v.0.9.5
Asterisk regexp support ( like _XNZ. ) for source / destination numbers.
PHP without any additional dependencies.
Easy to install and use.
CSS based.
User / Admin mode
Plugins support for custom reports.
ASR report

What Packages Do I Need? compile asterisk dependencies

What Packages Do I Need?
compile asterisk dependencies

What Packages Do I Need?

Most Asterisk configurations are composed of three main packages : the main Asterisk program (asterisk), the Zapata telephony drivers (zaptel), and the PRI libraries (libpri). If you plan on a pure VoIP network, the only real requirement is the asterisk package, but we recommend installing all three packages; you can choose what modules to activate later. The zaptel drivers are required if you are using analog or digital hardware, or if you’re using the ztdummy driver (discussed later in this chapter) as a timing source. The libpri library is optional unless you’re using ISDN PRI interfaces, and you may save a small amount of RAM if you don’t load it, but we recommend that it be installed in conjunction with the zaptel package for completeness.
In the first edition of this book, we recommended that you install the additional asterisk-sounds package. This was a separate compressed archive that you would download, extract, and then install. As of Asterisk version 1.4.0, there are now two sets of sounds packages: the Core Sound package and the Extra Sound package. Since Asterisk supports several different audio formats, these packages can be obtained in a number of different sound formats, such as G.729 and GSM. The reason for all of the different formats is that Asterisk can use the sound format that requires the least amount of CPU transcode. For example, if you have a lot of connections coming in on VoIP channels that are running GSM, you would want to have the GSM version of the sound files. You can select one or more sound prompt types in the menuselect screen (discussed later in this chapter). We recommend that you install at least one type of sounds file from both the Core Sound package and Extra Sound package menu items. Since we may make use of some of the Extra Sound files throughout this book, we will assume you have at least one of the formats installed.

Linux Package Requirements

To compile Asterisk, you must have the GCC compiler (version 3.x or later) and its dependencies on your system. Asterisk also requires bison, a parser generator program that replaces yacc, and ncurses for CLI functionality. The cryptographic library in Asterisk requires OpenSSL and its development packages.
Zaptel requires libnewt and its development packages for the zttool program (see the section called “Using ztcfg and zttool” later in this chapter). If you’re using PRI interfaces, Zaptel also requires the libpri package (again, even if you aren’t using PRI circuits, we recommend that you install libpri along with zaptel).
If you install the Software Development packages in CentOS, you will have all of these tools. If you are looking to keep things trim, and wish to install the bare minimum to compile Asterisk and its related packages,Table 3.1, “List of packages required to compile libpri, zaptel, and asterisk” will prove useful.

In the following table, the -y switch to the yum application means to answer yes to all prompts, and using it will install the application and all dependencies without prompting you. If this is not what you want, omit the -y switch.
If you just want to install all of the above packages in one go, you can specify more than one package on the command line, e.g.:

# yum install -y gcc ncurses-devel libtermcap-devel [...]

Table 3.1. List of packages required to compile libpri, zaptel, and asterisk

Package name	Installation command	Note	Used by
GCC 3.x	yum install -y gcc	Required to compile zaptel, libpri, and asterisk	libpri, zaptel, asterisk
ncurses-devel	yum install -y ncurses-devel	Required by menuselect	menuselect
libtermcap-devel	yum install -y libtermcap-devel	Required by asterisk	asterisk
Kernel Development Headers	yum install -y kernel-devel	Required to compile zaptel	zaptel
Kernel Development Headers (SMP)	yum install -y kernel-smp-devel	Required to compile zaptel	zaptel
GCC C++ 3.x	yum install -y gcc-c++	Required by asterisk	asterisk
OpenSSL (optional)	yum install -y openssl-devel	Dependency of OSP, IAX2 encryption, res_crypto (RSA key support)	asterisk
newt-devel (optional)	yum install -y newt-devel	Dependency of zttool	zaptel
zlib-devel (optional)	yum install -y zlib-devel	Dependency of DUNDi	asterisk
unixODBC; unixODBC-devel (optional)	yum install -y unixODBC-devel	Dependency of func_odbc, cdr_odbc, res_config_odbc, res_odbc, ODBC_STORAGE	asterisk
libtool (optional; recommended)	yum install -y libtool	Dependency of ODBC-related modules	asterisk
GNU make (version 3.80 or higher) [a]	yum install -y make	Required to compile zaptel and asterisk	asterisk
[a] It is a common problem among new installs on some Linux distriebutons to see GNU make versions of 3.79 or lower. Note that Asterisk will no longer build correctly unless you have at least version 3.80 ofGNU make.