Thursday 25 July 2013

Samsung Galaxy S III explodes, injures 18 year old girl









An exploding cellphone is no joke. A Samsung Galaxy S III exploded in the pants of 18 year-old Fanny Schlatter, and as you can see, it did plenty of damage to her thigh not to mention the handset. Now, we've seen people claim that their phone exploded out of nowhere only to find out later that the device was put in the microwave to cover up the fact that it had been dropped in the toilet first. Looking at this situation, one can see that this isnot the case here.


There isn't much information on what caused the explosion, but the victim's paints had to be cut to prevent her from sustaining further damage. If you have a sensitive stomach, you might not want to view the damage in the slideshow below. On the other hand, if blood and guts are your thing, we have a new pin-up for you.

The explosion took place at the girl's place of employment and Samsung Switzerland said that it is investigating and will probably send the phone back to Korea for a an examination.

                 "Once we have been able to contact this person, we will launch a thorough investigation to shed light on the accident and, in this context, what is left of the phone will probably be sent to Korea. [Samsung submits its products to ] rigorous quality controls."-Mirjam Berger, spokesperson, Samsung Switzerland



Here are the images:



Source: Phonearena



Android 4.3 to bring virtual surround sound to the Nexus 10





During yeaterday's announcement for the new Nexus 7, Google mentioned that the device would feature "virtual surround sound" which Hugo Barra claimed would sound as though you had a 5.1 stereo system. Well, it turns out that the feature isn't due to the hardware in the new Nexus 7, but rather the software of Android 4.3.

The changelog for the updated Google Play Movies & TV app says that in addition to adding support for the Chromecast, it adds "support for virtual surround sound on the new (2013) Nexus 7, and on the Nexus 10 running Android 4.3". So, obviously once the Android 4.3 update rolls out to Nexus 10 users, they will also be getting the new virtual surround sound. 

Android 4.3 to bring virtual surround sound to the Nexus 10



  
Of course, this also indicates that apps will have to update to take advantage of the virtual surround sound, so even after you get Android 4.3 on your Nexus 10, it may not change anything in other apps. It also seems to indicate that other manufacturers may have to do something on dual-speaker devices to enable the virtual surround sound with their Android 4.3 updates. 

Source: Phonearena

Wednesday 24 July 2013

Nexus 4, Nexus 7 and Nexus 10 get Android 4.3 today

Google officially announced the latest version of Android operating system, 4.3, at its event today. The newest version of Android is a minor upgrade over the currently present Android 4.2 Jelly Bean OS and brings restricted profiles, a few other minor features along with a bunch of performance enhancements.
As one can expect, the Android 4.3 Jelly Bean OS will be first available on Samsung Galaxy Nexus,Nexus 4Nexus 7 and Nexus 10. What might come as a slightly surprise is that you won't even have to wait a day - the update will start rolling today.
After the roll-out to the Nexus line-up, the latest Android release will be seeded to the Google Play Editions of Samsung Galaxy S4 and HTC One. We got no time frame for that, but we were promised it will be happening soon.
The Android 4.3 Jelly Bean software update will be available over-the-air (OTA) so keep an eye for that notification.



Source : GSMarena



Android 4.3 unveiled with improved multi-user support






Android 4.3 has officially been announced – it's been in the wild on Google Play Edition devices for a while, but the unveiling was put off for today. So, what's new? Well, 4.3 is a minor upgrade so it brings minor improvements and refines the user experience, rather than delivering game-changing features.
Multi-user support was introduced in 4.2 and it's updated in 4.3 with the new restricted profiles. A restricted profile can limit what content and apps can be used – even limit in-app stuff like what levels of a game can be played.
The suite of stock apps has been updated - Hangouts now officially replaces Talk and Keep is available out of the box. The Drive, Chrome and Maps applications have been revamped too.
The way Android handles notifications has been changed too. For one, you can view your notification history. Also, third party apps have access to notifications, which will help smart watches and apps that sync notifications across devices.
There are plenty of changes under the hood too. OpenGL ES 3.0 is now supported (Google presented impressive improvements in 3D game graphics) and the graphics stack should be faster overall. For games, Google unveiled the Google Play Games app, which lets you keep track of what your friends are playing and a leader board of achievements in the game.
The "master key" exploit patch has been incorporated into Android 4.3, of course.
Bluetooth 4.0 with Low Energy mode (low power usage and longer range for low-bandwidth accessories like those fitness tracking gadgets) is now supported in stock Android. Before, each maker had to roll its own drivers. Also for Bluetooth, AVRCP 1.3 is supported, meaning the phone can stream metadata about the currently playing song to the wireless speakers (or your car's stereo).
Wi-Fi can be kept on at all times to determine your position, even when you toggle it off.
A new hardware-based encryption for DRM has been added so content providers will be more willing to stream high-quality content. A new Netflix app is among the first to make use of this and streams 1080p video (it's now available in the Play Store).
An Android 4.3 update will be available on Nexus devices from the Galaxy Nexus up (4, 7, 10, you name it). Samsung Galaxy S4 and HTC One Google Play Edition will get the update soon, too.



Source : GSMarena

Friday 19 July 2013

Steps to install Mac 10.9 beta, (Mavericks)


Steps to install Mac 10.9 beta Mavericks

Step 1:
                Check for your Mac device, so that your device supports Mavericks.
                The Mac OS X v10.9 Mavericks supports the following Apple Macs devices:
·         iMac (Mid-2007 or later)
·         MacBook (13-inch Aluminum, Late 2008), (13-inch, Early 2009 or later)
·         MacBook Pro (13-inch, Mid-2009 or later), (15-inch, Mid/Late 2007 or later), (17-inch, Late 2007 or later)
·         MacBook Air (Late 2008 or later)
·         Mac Mini (Early 2009 or later)
·         Mac Pro (Early 2008 or later)
·         Xserve (Early 2009)
(if your computer uses an Ivy Bridge processor, be sure to use iBoot for Ivy Bridge)
Step 2:
                 Download the Mac 10.9 Beta (Developer preview  1) from this link
Step 3:
                Make a bootable disk, steps as follows,
o    Attach the USB drive to the Mac and launch Disk Utility
o    Choose the USB drive from the left side menu, click the “Partition” tab, select “1 Partition” from the drop down menu, and then click the “Options” button to select “GUID” as the partition type, click “OK” then click “Apply”
o    Launch Terminal to show hidden files and relaunch the Finder using this defaults command string:
defaults write com.apple.Finder AppleShowAllFiles TRUE;\killall Finder;\say Files Revealed
o    Go to the /Applications/ folder to locate the “Install OS X 10.9 Developer Preview.app” file
o    Right-click and choose “Show Package Contents”, then open “Contents” and open “SharedSupport”

o    Double-click to mount “InstallESD.dmg”
o    Open the mounted ‘OS X Install ESD’ image, and right-click “BaseSystem.dmg” choosing “Open” to mount the image (BaseSystem.dmg is invisible by default, thus why invisible files must be made visible in the earlier step)

o    Go back to Disk Utility, then select “BaseSystem.dmg” from the sidebar and then click the “Restore” tab
o    With “Source” set to “BaseSystem.dmg”, set “Destination” to the USB drive by dragging the USB drive into the box, then click “Restore” to begin – confirm that contents of the drive will be erased






o    When finished, go to Finder and navigate within the newly created USB drive to System > Installation > and delete the file (alias) located here named “Packages” – keep this window open


o    Go back to the ‘OS X Install ESD’ mounted drive, and drag & drop the “Packages” folder into the /System/Installation/ directory you just deleted the Packages alias from, let this large folder copy

o    Once that Packages folder is finished copying to the drive, the USB drive is now ready to be booted from which it can install OS X Mavericks from.

               
               
Step 4:
                Yess!!! Boot from bootable disk. Steps needed?
                Here are they……
o   With the USB drive attached, reboot the Mac and hold down the Option key
o   Select the orange drive, labelled “OS X Base System 1″ from the boot menu
o   Proceed with the installation as usual






o   Enjoy OS X Mavericks!

` IT DOESN’T STOP THERE!!!!
You can also dual boot it along with OS X (10.8 r 10.7 r whatever you have installed!!)


Setting up a dual-boot environment for OS X Mavericks and OS X 10.8 (or even 10.7 and 10.6 if you’re still running an older version of Mac OS X) is easy and allows for a fresh installation of Mavericks to test and develop with. Because the original OS X installation remains untouched, it’s also the safest way to give Mavericks a trial run, which is perfect for running the Developer Previews or if you’re just not sure you’re ready to run OS X 10.9 full time yet.
You don’t need another hard drive to be able to do this, instead you utilize unused space on the existing drive to create a new partition that runs the alternate OS. This process can be completed from a Mavericks boot drive if desired, and using such an USB installer tends to prevent any potential errors with Disk Utility (more on common errors you may encounter at the very bottom of this article), but it is not necessary.

Be sure to back up the Mac before modifying the partition table, the easiest way to do that is by starting Time Machine immediately rather than waiting for the scheduled backup to take place. Let that complete before beginning.
o   Partitioning & Installing OS X Mavericks for a Dual Boot Mac
o   Launch Disk Utility, from /Applications/Utilities/
o   Select the hard drive from the left side menu, then choose the “Partition” tab
o   Click the [+] plus button to add a new partition, size it to at least 12GB and name it something logical, like “Mavericks”, then click “Apply”


o   Quit out of Disk Utility when finished.
o   At the installation menu, choose the “Mavericks” partition you created as the destination drive, then choose Install (you may need to click “Show All Disks” for the partition to show up)
o   OS X Mavericks will install and, when finished, will boot directly into 10.9.
To switch booting between OS X versions, restart the Mac and hold down the Option key, then choose whichever partition you wish to start up from. You’ll notice the initial boot menu does not display the OS X version, which is why it’s important to name the partitions something fairly explanatory, like “Mavericks”. You can also change the bootdisk by going to “Startup Disk” within System Preferences and selecting the OS X partition to use, the preference panel option will display the OS X versions for each partition.




Tuesday 9 July 2013

Google Play Edition HTC One And Samsung Galaxy S4 Ship From U.S. Play Store Today

There are people out there who are fans of stock Android, but not of the Nexus hardware. For those folks, this is a big day. Today, July 9th, is the ship date for the Google Play Edition HTC One and Galaxy S4. If you got an order in early, your inbox could be graced by that shipping notice at any moment. Oh, the anticipation!
nexusae0_HTC_One_3V_transparent_v21 nexusae0_gs4_hardwarehome_final_thumb
These device were one of the more shocking developments from Google this spring. We didn't get a new version of Android, but we certainly got a new method of distributing it. The Galaxy S4 wasannounced at I/O 2013, and the HTC One a few weeks later. The warm fuzzy feeling was dulled a bit when it was made clear the OEMs were handling the updates – not Google. There also won't be any Google factory images for the devices. Still, stock Android on killer hardware.
55-49103-gs4_google-1371829473
These phones are essentially the same hardware you'd get from the carriers, but they're unlocked and unburdened by carrier restrictions. The GS4 will work on AT&T and T-Mobile 3G/4G everywhere. The HTC One will work on AT&T 3G/4G in all markets, however T-Mobile is a little sticky. The One will work on 4G and 2G everywhere it's available. T-Mobile's AWS HSPA+ is not supported, but anywhere the carrier has re-farmed that AT&T spectrum you will get 3G.
The Galaxy S4 is $649.99, and the HTC One is going for $599.99. Shipping is included, and they should start heading your way soon. As a reminder, these are US-only devices for now.




Source: Android police

Tuesday 2 July 2013

Vanilla build ROMS for S4 i9505 and HTC One !!!!!!!!!

The first repackaged Google Play edition firmware for the HTC One has landed. It comes to us from XDA Senior Member bigxie, and is based off of a system dump captured by Jerry Hildenbrand. This version has been pre-rooted with busybox installed, and it remains Odexed. To get the goods on your own HTC One, you first have to own a GSM HTC One (Unlocked, T-Mobile, or AT&T variety). The install procedure is just a simple flash through a custom recovery, though you also need to do a factory reset if you’re coming from any other ROM.
Several builds were also released for the Galaxy S 4 coming from various XDA Forum Members, including jamal2367janjanm3dd0g, and HazAnwar. They all appear to be derived from the I9505GUEUAMFD dump, but some appear to be more functional than others. The choice is also yours regarding Deodexed versus Odexed. Similar to the HTC One build, flashing is just a few clicks away through your custom recovery.
Itching to get this on your own device? If so, head over to the HTC One thread  or any one of the Galaxy S 4 threads (jamal2367janjanm3dd0gHazAnwar) to get started



Source: XDA