Archive

Posts Tagged ‘samsung’

Thread is a New IP-based Wireless Protocol Leveraging 6LoWPAN and 802.15.4 Standards

July 21st, 2014 2 comments

Wi-Fi is a neat way to connect devices to Internet, but it has two main inconveniences: relatively high cost and power consumption. Luckily there are standards that addresses the cost and power consumption issues. Radio chips based on IEEE 802.15.4, a standard which specifies the physical layer and media access control for low-rate wireless personal area networks, are common place and found in many existing devices relying on higher level wireless protocols such as ZigBee, ISA100.11a, WirelessHART, and MiWi. AFAIK, Zigbee is the most popular of the aforementioned protocols, but is hindered by the requirements of the license for commercial products (annual fee), Zigbee membership requirements conflict with many open source license such as GPL, and the standard suffers from lack of interoperability and IPv6 support, and power requirements that are too high for some applications. So a consortium of seven companies namely ARM, Big Ass Fans, Freescale, Nest, Samsung, Silicon Labs, and Yale Security, have come together to start working on “Thread”, a new wireless protocol leveraging 802.15.4 standard and existing transceiver chips,  that is legacy-free, and is based on 6LoWPAN (Low Power IPv6 connectivity), and UDP protocols.

 

Thread_Wireless_Protocol

Thread specifications are currently work in progress, but it will be a low power IP based open protocol supporting mesh networking (Up to 250 devices), that is both secure and user-friendly, and provides fast-time to market thanks to existing radio silicon. It will be used in various products such as electric appliances, access control, climate control, energy management, lighting, as well as safety and security devices. Two products companies are part of the group Nest and Big Ass Fans, so thermostats and fans based on Thread are likely to be available soon. Nest V2 actually comes with a 802.15.4 capable SoC (Ember EM357) that used to be disabled, but “is already being used successfully in Nest products today” thanks to a simple firmware upgrade, although I’m not sure if this is the case internally, or on customer’s premises.

The Thread Group is now looking for new members, and companies that are interested in Thread can join the consortium as a Sponsor (with more voting rights), or Contributor member. There’s no individual membership at this stage.

Via Semiwiki

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Google Releases Android Wear SDK, LG G Watch and Samsung Gear Live Smartwatches Are Now Available

June 26th, 2014 1 comment

I’ve just covered what’s new in Android L?, and I’m going to focus on Google I/O 2014′s announcements related by Android wear starting with hardware with LG G Watch ,and Samsung Gear smartwatches, followed by some details about the first official release of Android Wear SDK.

LG G Watch

LG_G_WatchSpecifications:

  • SoC – Qualcomm Snapdragon 400 @ 1.2 GHz
  • System Memory – 512MB RAM
  • Storage – 4GB eMMC
  • Display – 1.65” IPS display (280 x 280)
  • Connectivity – Bluetooth 4.0 LE
  • Sensors – 9-Axis (Gyro / Accelerometer / Compass)
  • IP Rating – IP67 dust and water resistant
  • Battery – Li-ion 400mAh
  • Dimensions – 37.9 x 46.5 x 9.95 mm
  • Weight – 62.5 grams

LG G watch will run Android Wear (as it’s the subject of this post), and it currently available on Google Play for $229 (US only?) with shipping scheduled for early July.

Samsung Gear Live

Samsung_Gear_LIveSpecifications:

  • Processor – Unnamed 1.2 GHz processor (Samsung Exynos?)
  • System Memory – 512MB RAM
  • Storage – 4GB Internal Memory
  • Display – 1.63” Super AMOLED (320 x 320)
  • Connectivity – Bluetooth 4.0 LE
  • Sensors – Accelerometer, Gyroscope, Compass, Heart rate monitor
  • IP Rating – IP67 dust and water resistant
  • Battery – Li-ion 300mAh
  • Dimensions – 37.9 x 56.4 x 8.9 mm
  • Weight – 59g

It looks similar to Samsung Gear 2 with Tizen, but this one runs Android Wear with Google Services, Google Now,  Google Voice, Google Maps & Navigation, Gmail, Hangouts, and you can recieve notification for SMS, E-mail, etc. It’s available for $199 on Google Play.

LG G Watch has a larger battery (33% more), a barely larger screen (1.65″ vs 1.63″0 but at lower resolution (280×280 vs 320×320), but the Samsung Gear Live features an Heart rate monitor which at first glance makes it a better deal.

If you’re wondering about Motorola’s Moto 360 rounded smartwatch, it will be available later. In the meantime, Android Community wrote an hands-on post.

Android Wear SDK and Apps.

Back in March, Google released Android Wear Developer Preview, and the company will release the first official release of the Android Wear SDK later today possibly via the Android L developer preview page, so developers can actually develop for Android (Wear) based wearables with a stable API to build user interfaces, control sensors, handle voice actions, and exchange data between phones and wearables.

Google also showcased a few apps optimized for Android Wear such as Eat24 that let’s you order food with your watch using a few swipes, and Lyft an leverages Google Now so that you can use a voice command to call a (ride-sharing) car, and rate the driver.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Meet Samsung Smart Bike fitted with an Arduino, a Rear Camera, Lasers and More

June 12th, 2014 1 comment

Samsung Maestros Academy has introduced a Smart Bike prototype integrating various “smart” components within its aluminum frame, such as an Arduino board connected to a Wi-Fi + Bluetooth module, a battery, four laser projectors, and a digital camera controlled by a Samsung smartphone.
Samsung_Smart_Bike

The camera is fitted at the back just under the seat, and allows the riders to have a real-time rear view image on the phone. The four lasers are used to create a virtual bike lane in case a real one is missing, and remind other drivers to keep a safe distance to your bicycle. The bike can also detect ambient conditions using the smartphone sensors, and modify its behavior. For example, it can switch on or off the laser beams depending on the brightness sensor data from the smartphone. Each bike also tracks daily routes of the riders using GPS, and can let local authorities know where bicycle traffic is most intense, and where they should build bike lanes.

For information is available on www.maestrosacademy.it/progetto-sbike.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Meet Samsung Z, the First Tizen Smartphone

June 2nd, 2014 No comments

After many delays, even rumors that Tizen was dead, Samsung has finally announced the very first commercially available smartphone running Tizen mobile operating system with the Samsung Z, right before the Tizen Developer Conference which will take place in San Francisco, on June 2-4, 2014.
Samsung_Z_Tizen_Smartphone

Let’s go through the hardware specs first:

  • SoC – Qualcomm SnapDragon 800 quad core application processor @ 2.3GHz
  • System Memory – 2GB RAM
  • Storage – 16 GB flash + micro SD card slot (Up to 64GB)
  • Display – 4.8” HD Super AMOLED (1280 x 720)
  • Camera -  8MP(rear), 2.1MP (front)
  • Cellular Network – LTE Cat.4 (150/50Mbps)
  • Connectivity – WiFi 802.11 a/b/g/n HT40, MIMO(2×2), Bluetooth 4.0 BLE, NFC, GPS / GLONAS
  • USB – micro USB 2.0
  • Misc – IR sensor
  • Sensors – Accelerometer, gyro, proximity, compass, barometer, Hall, RGB ambient light, fingerprint scanner, heart rate sensor
  • Battery – 2600mAh
  • Dimensions – 138.2 x 69.8 x 8.5mm
  • Weight – 136g

Samsung Z will run Tizen 2.2.1, and have some usual feature from Samsung such as Ultra Power Saving Mode, Download Booster, S Health 3.0, and color theme customization. The company claims Tizen delivers a “fast, optimal performance with improved memory management”, including faster boot time, and multi-tasking capabilities.

It will be interesting to see the performance difference, if any, between Android and Tizen, and how many applications will be installable via the Tizen store when it opens. The company will try to bring developers to the platform via a soon-to-be-announced “special promotional program” that will last one year, so  there may be more apps than expected at launch.

The device is scheduled for Q3 in Russia, with plans to expand to other markets later on. Further information may be available on Samzung Z product page.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Linaro 14.05 Released with Linux Kernel 3.15, Android 4.4.2, and Ubuntu Trusty

May 30th, 2014 4 comments

Linaro 14.05 has been released with Linux Kernel 3.15-rc5 (baseline), Linux Kernel 3.10.40 (LSK), Android 4.4.2, and Ubuntu has been switched from Saucy to Trusty.

More work has been done on big.LITTLE processing and ARMv8 support with notably completing bootstrapping with Debian 64-bit. New hardware platform have started to pop-up such as TI J6-Vayu which must be an evaluation board for Texas Instruments Jacinto 6 dual core Cortex A15 SoC for automotive application, as well as IFC6410, a Snapdragon 600 development board which got a Ubuntu LEB image. This month also marks the first release of Linaro GCC 4.9 toolchain.

Here are the highlights of this release:

  • Linux Linaro 3.15-rc5-2014.05
    • new Android topic (linaro-android-3.15-experimental) uses the resent AOSP code base
    • GATOR version 5.18 (same version as in 2014.04)
    • uprobes topic removed as all patches have been accepted into mainline
    • updated big-LITTLE-pmu topic from ARM LT
    • updated basic Capri board support from Broadcom LT (SMP support enabled for bcm21664 and bcm28155, mmc updates, more bcm590xx regulators enabled)
    • cortex-strings-arm64 topic (same as in 2014.02)
    • updated Versatile Express arm64 support (FVP Base and Foundation models, Juno (ethernet, USB)) from ARM LT
    • updated Versatile Express patches from ARM LT
    • updated Arndale_Octa/Arndale/Origen patches from Samsung LT
    • more HiP0x Cortex A15 family updates from HiSilicon LT. All the CPU cores enabled
    • new ftrace_audit topic from the Kernel WG (ftrace, audit and seccomp patches)
    • Big endian topic updated for 3.15
    • updated llvm topic. The “spinlock” commit is reverted to let armv8 kernel to compile
    • config fragments changes – uprobes: CONFIG_NAMESPACES and CONFIG_USER_NS enabled (for systemtap), arndale_octa: Enable Generic Phy support, arndale: Enable IOMMU/USB3/Generic Phy, vexpress: updated for 3.15 kernel (CONFIG_ARM_BIG_LITTLE_CPUFREQ enabled), THUMB2 disabled for arndale, arndale_octa, and origen to work around arch/arm/mach-exynos/sleep.S compilation error
  • Linaro Toolchain Binaries 2014.05
    • updated to latest Linaro TCWG releases, this is the first binary release based on GCC 4.9.
      • Linaro GCC 4.9 2014.05 includes performance improvements and bug fixes
      • Linaro Binutils 2.24.0 2014.05 features aarch64 improvements
      • Linaro GDB 7.7 2014.05
  • Linaro Android 14.05
    • built with Linaro GCC 4.8-2014.05
    • TI J6-Vayu member build has been setup (Evaluation module based on Texas Instruments Jacinto 6 for automotive application)
    • Android build system is using VPS build slaves, reducing the build time by 40% compared to the current EC2 slaves
    • Multinode job submission support is added to linaro-android-build-tools
  • Linaro OpenEmbedded 2014.05
    • integrated Linaro GCC 4.8 and 4.9 2014.05
    • integrated Linaro EGLIBC 2.19-2014.05
    • integrated Linaro binutils 2.24-2014.05
    • improved Linaro’s meta layer layout for 3rd parties usage
    • added toolchain benchmark image
    • update GATOR recipe to latest release and fixed build issues
    • improved python module support in images
    • upstreaming:
    • fixed separate build directory issues for mariadb, openldap, libmcrypt, netperf, fwts, php, tmux, gpm and rrdtool
    • updated recipes: acpitests, acpica, fwts, libhugetlbfs, pm-qa, systemtap and GRUB
    • enabled PM and RT tests in LTP
    • fixed GRUB build issue
  • Linaro Ubuntu 14.05 is released:
    • baseline migrated from Saucy to Trusty
    • added packages:
      • alsa-lib, added HDMI UCM profile for IFC6410
      • mesa, enabled freedreno gallium driver
    • updated packages: linaro-edk2, ARM trusted firmware, linaro-meta (added git to developer rootfs), xf86-video-freedreno (Add xorg configuration file), and linux-linaro 3.15-rc5 kernels.
  • ARMv8 Debian bootstrap effort is completed
  • Linaro U-Boot is updated to 2014.04 release
  • Linaro EDK2 CI is setup
  • Linaro kernels build support is added to Linaro OpenEmbedded
  • IFC6410 member build is delivered and released this cycle

You can visit https://wiki.linaro.org/Cycles/1405/Release for a list of known issues, and further release details about the LEB and community builds, Android, Kernel, Graphics, Multimedia, Landing Team, Platform, Power management and Toolchain (GCC / Qemu) components.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

ARM Cortex A15/A17 SoCs Comparison – Nvidia Tegra K1 vs Samsung Exynos 5422 vs Rockchip RK3288 vs AllWinner A80

May 21st, 2014 10 comments

We’re now starting to get quite a few players with ARM Cortex A15 cores on the market, as well as some with ARM Cortex A17. So a comparison table of different quad and octa SoCs might be a useful thing to do. I’ve put aside SoCs such as HiSilicon K3V3, and OMAP5, and focused on the four latest processors: Nvidia Tegra K1 (32-bit), Samsung Exynos 5422, Rockchip RK3288 and AllWinner A80. I haven’t included Mediatek MT6595 and Qualcomm SnapDragon 805, because the two companies mainly focus on smartphones and tablets (although it appears to be slowly changing for Qualcomm), documentation is usually difficult or impossible to find, and in the case of Qualcomm they use their own ARMv7 Krait cores.

rk3288_a80_tegra_k1_exynos_5_octaI’ve highlighted some features in green, in case a particular SoC appears to have an edge.

Rockchip RK3288 AllWinner A80 Nvidia Tegra K1 Samsung Exynos 5422
CPU 4x ARM Cortex-A17 @ 1.8 GHZ 4x ARM Cortex-A15 r4 @ 2.0?? GHz +
4x ARM Cortex-A7 @ ?? GHz
big.LITTLE Processing
Quad Core ARM Cortex-A15 r3 @ 2.3GHz + Cortex A15 r3 companion core 4x ARM Cortex-A15 @ 2.1 GHz +
4x ARM Cortex-A7 @ 1.5 GHz
big.LITTLE Processing
L1 Icache/Dcache 32KB/32KB 32KB/32KB 32KB/32KB 32KB/32KB
L2 Cache 1MB 2MB + 512KB 2MB + 512 KB 2MB + 512 KB
GPU ARM Mali-T764 PowerVR G6230 (64-cores) Kepler GK20a (192-cores) ARM Mali-T628 MP6
GPU API OpenGL ES 1.1/2.0/3.0, OpenVG 1.1, OpenCL 1.1 and Renderscript, Directx11 OpenGL ES 2.0/3.0, OpenCL 1.x, Directx 9.3 OpenGL ES 2.0/3.0/3.1, OpenGL 4.4, OpenCL 1.2, CUDA 6.0, Directx 12 OpenGL ES 1.1/2.0/3.0, OpenCL 1.1,OpenVG 1.0.1, DirectX 11, and Google Renderscript
Video Decoder 4K2K@60fps: HEVC
4K2K@24fps: H.264, MPEG-2, VP6/VP8, MVC
1080p: MPEG-4, Sorenson Spark, VC-1, RV8/RV9/RV10, and AVS
720×576:H.263
4K2K@30fps: H.264 and VP8
1080p60: MPEG 1/2/4. H.263, H.264, WMV9/VC1, etc…
1080p30: H.265/VP9
3D decoding @ 3840×1080@30fps
1440p – H.264 BP/MP/HP/MVC, VC-1, VP8, MPEG-2 and MPEG-4 1920×1080@120fps – MPEG-4/MPEG-2/H.263/H.264/VP8//VC1
8192×8192 – H.264 and VP8
Video Encoder 1080p30: H.264, MVC, and VP8 4K2K@30fps: H.264 and VP8 H.264
BP/MP/HP/MVC and VP8
1920×1080@120fps – MPEG-4//H.263/H.264/VP8
8192×8192 – H.264 and VP8
Memory (On-chip) 20KB BootRom, 100KB internal SRAM No data 64KB Boot ROM (IROM) No data
Memory Interfaces DDR3-1333/DDR3L-1333, LPDDR2-1066, LPDDR3-1066, up to 4GB
Dual channel async NAND flash, 8-bit, 60-bit ECC
Single channel async NAND flash, 16-bit, 60-bit ECC
eMMC v4.5
SD/MMC Interface (SD 3.0, MMC ver 4.5)
DDR3/DDR3L/LPDDR3/LPDDR2, Up to 8GB
Raw NAND with 72-bit ECC
eMMC v4.5
4x SD/MMC
DDR3L, and LPDDR3, up to 8GB
LPDDR2 might work but not tested by Nvidia
eMMC version 4.5
SDIO
LPDDR3/DDR3 – 2-ports 32-bit up to 933 MHz
LPDDR2 – 2-ports 32-bit up to 533 MHz
2x eMMC 5.0, 1x eMMC 4.5
8-bit SDIO 3.0,
4-bit SD 3.0
Display Interfaces Dual channel LVDS
2x Parallel and serial RGB interfaces: Up to 3840×2160 or 2560×1600
MCU LCD interface (optional)
4-lane MIPI up to 1080p60
4-lane eDP up to 4K2K@30fps
HDMI 1.4 and 2.0
Dual channel LVDS up to 1920×1080@60fps
RGB LCD up to 2048×1536@60fps
4-lane MIPI DSI up to 1920×1200@60fps
4-lane eDP up to 2560×1600@60fps
HDMI 1.4
LVDS up to 1920×1200@60fps
2x 4-lane MIPI DSI (Dual link: up to 3840×1920@60fps, single link: 2560×1440@60fps)
4-lane eDP up to 3840×2160@60fps
HDMI 1.4b up to 4096×2160@30fps
4-lane MIPI DSI up to WUXGA (1920×1200) @ 60 fps
1-port (4 lanes) eDisplayPort (eDP) up to WQXGA (2560×1600) @ 60 fps
HDMI 1.4a interfaces with on-chip PHY
Camera Interfaces 12-bit CCIR/Camera I/F up to 5MP
MIPI CSI2 I/F up to 14MP
8/10/12-bit raw data interface
Parallel and MIPI I/F sensor
5M/8M/12M/16M CMOS sensor
8/10/12-bit YUV/Bayer sensor
1x MIPI CSI
Up to 16MP @ 37 fps
2x 4x YUV / RAW / CSI
2-ports (4/4 lanes) MIPI CSI2 interfaces
Up to 16MP @ 30fps
14-bit Bayer sensor
USB 2x USB 2.0 Host
1x USB 2.0 OTG
HSIC
2x USB host
1x USB3.0/2.0 host / device
HSIC
2x USB 3.0
3x USB 2.0
HSIC
2x USB 3.0
1x USB 2.0
1x HSIC
Ethernet 1x GMAC (RMII/RGMII) 1x Ethernet MAC N/A N/A
TS Interface 2x IN, 1x IN No data 1x TS 1x TSI
SATA N/A N/A SATA 3.1 N/A
PCIe N/A N/A 5-lane PCIe with Gen1 (2.5GT/s) and Gen 2 (%.0 GT/s) speeds N/A
Audio I/F PCM/I2S, SPDIF PCM/I2S PCM/I2S, S/PDIF 1x PCM, 2x I2S, 1x S/PDIF
Other I/Os 3x SPI, 6x I2C, 5x UART, 4x PWM, 2x DMAC, 160 GPIO 4x SPI, 7x TWI, 7x UART 3x I2C, 2x SPI, UART, Up to 64 MPIO (Multi Purpose IO) 4x I2C, 7x HS-I2C, 3x SPI, 5x UART, GPIOs, 24-channel DMA controller
Antutu 4.x 35225
Hardware: Pipo P8 (res: 2048×1536)
41556
Hardware: AllWinner OptimusBoard?
43851
Hardware: Tegra K1 Reference Tablet?
38580
Hardware: Samsung Galaxy S5 (SMG900H)
Low Cost Development Board Currently not available, none officially announced. Announced: OptimusBoard, PcDuino8, Cubieboard A80. No price available. Nvidia Jetson TK1 for $192 None with Exynos 5422, but two with the similar Exynos 5420:
Arndale Octa for $179
Announced: ODROID XU-2 (Price not available)

First some general comments:

  1. As details are not always available, and I had to go through thousands of pages of documentation, it’s possible some information is incorrect or missing. So I’d be grateful if anybody points out mistakes in the table.
  2. In L2 Cache = xx MB + xx KB refers to the cache for the bit processors (A15) + the cache for the LITTLE processors (A7) or the companion core.
  3. The “Other I/Os” section is mainly for reference, as I’m sure parts are missing here.
  4. I haven’t addressed power consumption of the different SoC, since I don’t believe numbers provided by the SoC vendors are directly comparable.
  5. Antutu scores are interesting to get an idea of the performance, but we should bear in mind AllWinner A80 and Tegra K1 scores appear to have been achieved with development hardware, which may not have the same thermal constraints as the tablet and smartphone used with Rockchip RK3288 and Exynos 5422.

Based on this comparison table, Nvidia Tegra K1 really seems to have the best package in terms of performance, 3D and GPGPU APIs, and peripheral interfaces such as SATA and PCIe which are missing on all other SoCs. The downsides are video encoding is only supported up to 1440p, and there’s no Ethernet MAC. That means no 4K hardware video decoding, although an article from Anandtech mentioned the company demos 4K 30 fps using the Kepler GPU. The way to add Ethernet with Tegra K1 is to use an external Ethernet Control chip and connect it to the PCI Express port, as they did for Jetson TK1 development board. It’s also likely Tegra K1 is more expensive than all other three, but it’s very versatile and could be found in various type of products: tablets, mini PCs, laptops and so on. Linux and Android are supported, and since the company seem inclined to go open source, it’s likely any Linux based OS can be supported by the platform.

Rockchip RK3288 should be one of the more cost effective platform in the table, but trade offs includes 1MB L2 cache (vs 2MB for others), an 4GB RAM limitation, the lack of USB 3.0 interfaces, and lower overall performance. However it’s the only SoC that 100% 4K ready here with HDMI 2.0, HEVC decode at up to 4K @ 60fps, as well as Gigabit Ethernet. ARM Cortex A17 should also have lower consumption compared to ARM Cortex A15, but it’s unclear how it will compare against big.LITTLE solution. This will probably remain a gray area because power efficiency will highly depend on the payload. RK3288 has already been demoed on hardware running Android and Chromium OS.

AllWinner A80 has performance very close to Tegra K1, apparently supports VP9 (N.B: However, I had been asked to remove VP9 from an AllWinner A80 graphics once), supports 4K30 video decoding, USB 3.0. Apart from the lack of SATA and PCIe interfaces, and OpenGL 4.4 support, AllWinner SoC appears to have few drawbacks compared to Tegra K1, so we’ll have to see how it compares in terms of price versus Rockchip RK3288. The company has also announced support for 5 operating systems for A80: Android, Chrome OS, Ubuntu, Windows 8, and Firefox OS. So they must have worked with Imagination Technology to support the PowerVR GPU on these OS.

Samsung Exynos 5422 appears to be just short of AllWinner A80 and Tegra K1 performance, and the company has dropped some interfaces such as SATA, PCIe, LVDS, Ethernet MAC,  that makes it a little less versatile than other SoCs, and more targeted at tablets and smartphones. It’s the only SoC that supports both 8K encode and decode (H.264 and VP8 only), but lacks HEVC/H.265 hardware support. It’s also the only SoC to support eMMC 5.0, instead of just eMMC 4.5, which can potentially double the IO performance (400MB/s max instead of 200 MB/s).

References:

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Samsung Galaxy K Zoom Camera Phone Powered by Exynos 5 Hexa SoC

April 29th, 2014 No comments

After Samsung Galaxy S4 Zoom, Samsung has just introduced a new camera-specialized phone called the Galaxy K Zoom with a faster processor, an hexa core processor, which has not been named, but can only be Exynos 5260 hexa core big.LITTLE SoC, a larger 4.8″ display, and a better camera with a 20.7 Megapixel CMOS Sensor and a 10x Optical Zoom.

Samsung_Galaxy_K_Zoom

Let’s go straight through the specifications:

  • SoC – Samsung Exynos 5260 Hexa core processor with four Cortex A7 cores @ 1.3GHz,  two Cortex A15 cores @ 1.7GHz, and ARM Mali-T624 GPU
  • System Memory – 2GB RAM
  • Storage – 8GB Flash + micro SD slot up to 64GB
  • Display -  4.8″ HD Super AMOLED Display (1280×720)
  • Cellular Network
    • LTE – Cat4, HSPA+ 42Mbps, LTE 800/850/900/1800/2100/2600, HSPA+ 850/900/1900/2100, EDGE/GPRS 850/900/1800/1900
    • 3G – 5-band HSPA+ 42Mbps, HSPA+ 850/900/1900/2100,EDGE/GPRS 850/900/1800/1900
  • Connectivity – Wi-Fi: 802.11 a/b/g/n 2.4+5GHz, Bluetooth 4.0 BLE, NFC, A-GPS + GLONASS
  •  Camera
    • Rear camera – 20.7 MP 1/2.3 BSI CMOS Sensor, 10x Optical Zoom, OIS, 24-240mm, F3.1-6.3, AF Assist LED
    • Front camera – 2.0 MP
    • ISO – Auto, 100, 200, 400, 800, 1600, 3200
    • Continuous Shot – 3fps MAX with AF
    • Xenon Flash
    • SMART Mode, Expert Mode(P/M), My Mode
  • Video
    • Recording / Playback – Full HD (1920×1080 /60p)
    • Codec – H.263, H.264(AVC), MPEG4, VC-1, Sorenson Spark, MP43, WMV7, WMV8, VP8
    • Format – MP4, M4V, 3GP, 3G2, WMV, ASF, AVI, FLV, MKV, WEBM
  • Audio
    • Codec – MP3, AMR-NB/WB, AAC/AAC +/eAAC+, WMA, OGG (Vorbis), FLAC
    • Format – MP3, M4A, 3GA, AAC, OGG, OGA, WAV, WMA, AMR, AWB, FLAC, MID, MIDI, XMF, MXMF, IMY, RTTTL, RTX, OTA
  • Sensors – Accelerometer, Gyro Sensor, Proximity Sensor, Geomagnetic Sensor, Light Sensor
  • USB – 1x micro USB 2.0
  • Battery – 2,430mAh
  • Dimension -  137.5 x 70.8 x 16.6 (20.2) mm
  • Weight – 200g

This camera phone runs Android 4.4 Kitkat, features 28 SMART picture modes,  and supports Auto Focus/ Auto Exposure separation, object tracking, smile/blink detection, S Health Lite, an ultra power saving mode,  Google apps. and more.

There’s no information about price, nor availability yet. You may find more details on Samsung Galaxy K Zoom page.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter