Samsung intros twelve (yes, twelve) phones at IFA
Blackjack II gets its share of Win Mobile 6.1; almost
Knock Knock! It’s The Teddy Calling
LM801 is strictly for the avid adventurer
BlackBerry Pearl 8220 will not be cheap
FCC Approved Nokia 6650 for AT&T Users Atul | 14 min ago It isn’t a phone that would have people flocking the streets across US as soon as it hits t
FCC Approved Nokia 6650 for AT&T Users
Sony Ericsson W980, Samsung G810 and HTC Touch Diamond Win European Awards
LG KC550 Pink
BlackBerry Bold live pics
Android Market Announced for Android OS Applications
Rumor: BlackBerry Thunder is BlackBerry Storm 9530 for Verizon Wireless
DataViz Releases Documents To Go for Windows Mobile Pocket PC Devices
LG Decoy
MOTOZINE ZN5 Launches in India
Sony Ericsson G705 live pics
Nokia Ovi news: Global site is up, Sync on Ovi works!
Motorola W6 Availeble In USA
Xperia Launch Date Further Delayed
MOTO Q Global
au KDDI W63SH URBANO: mobile phone from Sharp for the Japanese cities
LG KF300 ( "LG Wine" )
iPhone Security Flaw to be Fixed
Nokia 7610 Supernova with TV output
The supernova is one of popular fashion mobile phone series. Nokia 7610 is the newest member and its completely different form Nokia 7610.
This stunning slide opening handset is a member of the fashionable Nokia Supernova range. The Nokia 7610 Supernova is a fashionable looking mobile phone which comes with Xpress On™ cover which allows the user to mix & match their covers to make a stunning colourful handset. The phone is available in white, lilac, red, blue & a grey colour. The 7610 Supernova comes with a themed coloured illumination feature which allows the user to change the colour of their laminated navigation key & theme of their wallpaper to suit & match their chosen coloured casing.
The media player is very important because it has a TV output. You can watch videos through your TV while playing the phone. And the music player has best quality output and you can control it easily with front media keys.
Nokia 7610 has good quality camera which has 3.2Mp resolution. You can improve picture quality with its dual LED flash.
more pictures
More features of Nokia 7610 Supernova
2 Inch 16.7 Million Colour QVGA Screen (320 x 240 Pixels)
Theme Colour Illumination (Navigation Key & Wallpaper)
Music Player with 2 Way Music Key
Size 98 x 48 x 15 mm
3.2 Megapixel Camera with Zoom & Dual LED Flash
Video Playback via TV Out Cable
XHTML Browser
Bluetooth® Technology
iPhone 3G Sales Surpass the Original iPhone
Orange is Reported to be Capping your iPhone 3G Speeds
Why you should update your iPhone 3G to iPhone 2.0.2 OS
Windows Mobile 6.1 update almost ready for Samsung BlackJack II
Pantech SKY IM-S730 Blue Wink released in South Korea
Sony Ericsson G502 Turned Red
RadioShack Now Sells Sprint’s Samsung Instinct Nationwide
Presenting the Winners of the Android Developer Challenge I
Since we started the first Android Developer Challenge late last year, we all have been eager to see who the winners of $275,000 and $100,000 would be. All 50 applications that emerged from Round 1 of ADC I showed great promise, and these teams have been working intensely for the past several months to polish their apps for the final round.
Similar to round 1 we sent laptops preconfigured with the judging environment, emulator, and all entries to each of our seven judges. In this round, each judge reviewed all 50 applications, took collaborative notes and gave initial scores. Then, all judges met together over conference calls to discuss and debate these applications, finally coming to consensus on which applications should receive $275,000 and which should receive $100,000.
We're pleased to present all of the winners and finalists in our detailed ADC gallery. Peruse and enjoy — there are awesome applications and unique uses of the Android platform. We would like to congratulate the winners and thank all the entrants for their hard work!
Android Market: a user-driven content distribution system
When we talk to developers, a common topic is the challenge of getting applications in the hands of users. That's why today I'm happy to share early details of Android Market—an open content distribution system that will help end users find, purchase, download and install various types of content on their Android-powered devices. The concept is simple: leverage Google's expertise in infrastructure, search and relevance to connect users with content created by developers like you.
Developers will be able to make their content available on an open service hosted by Google that features a feedback and rating system similar to YouTube. We chose the term "market" rather than "store" because we feel that developers should have an open and unobstructed environment to make their content available. Similar to YouTube, content can debut in the marketplace after only three simple steps: register as a merchant, upload and describe your content and publish it. We also intend to provide developers with a useful dashboard and analytics to help drive their business and ultimately improve their offerings.
I also wanted to share some early details to help with planning your efforts so that you can be ready as our partners release the first Android-powered handsets. Developers can expect the first handsets to be enabled with a beta version of Android Market. Some decisions are still being made, but at a minimum you can expect support for free (unpaid) applications. Soon after launch an update will be provided that supports download of paid content and more features such as versioning, multiple device profile support, analytics, etc. Below are some screenshots that illustrate some of the security features and workflow.
With the addition of a marketplace, the Android ecosystem is becoming even more robust. I am incredibly energized by the support and amazing content I've seen so far. We will share more details as they are available and I look forward to working with many of you in the coming months.
Vertu Signature 3G - With New Design
First Nokia N85 Promotional and Demonstration Video!
Nokia 6650 flip phone picked up by AT&T
Verizon’s UTStarcom XV6800 gets a Windows Mobile 6.1 upgrade
Learn Japanese on iPhone
Samsung F210 Reviews
CKing’s Epoq EGP-PP01, the world’s first projector-phone available now
ATT to Introduce New iPhone Data Plan for International Roaming
JuiceCaster Launches on Blackberry Platform
New HTC S740 Joining the Touch Diamond Family
Nokia N85 with OLED Display Screen Officially Announced
Nokia Unveils the Nokia N79 Multimedia Computer
Nokia to Release N96 for US in Q4 2008
T-Mobile G1 Engineering Drawing Available
Samsung Mobile Charging Station Reaches Newark Liberty International Airport
Samsung i780 business phone with windows mobile OS
The Samsung i- series is very popular because those phones have very different features than other Samsung phones. All of them runs with windows mobile OS or symbian OS. And they are business phones. Samsung i780 is another great business phone which has many specifications.
The Samsung i780 is 3G Smartphone which comes with easy to use business features & high performance technology. The handset is coloured black which suits this business focused 3G Smartphone. It is a good sized handset when considering all the built in technologies & features as it measures 115.9mm high by 61.3mm wide by 13.3mm deep. This desirable Smartphone comes with a large touchscreen which measures 2.6 Inches in size & provides up to sixty five thousand colours on a TFT type screen. The touchscreen has a high screen resolution of three hundred & twenty pixels by three hundred & twenty pixels.
i780 looks likes a blackberry phone. It has a QWERTY keypad. You can easily type your text messages and emails with it. It runs with MS Windows Mobile 6 Operating System. And mobile version of windows media player has included.
Samsung i780 is a 3G phone which has HSDPA technology. The HSDPA technology supports better internet connectivity to this phone. Also you can connect to internet with Wi-Fi technology.
The Samsung i780 has A-GPS navigating system. You can handle it easily because it has many user friendly features. Also the Google maps application included.
A-GPS navigator
Internet browser
QWERTY key pad
PwnageTool 2.0.3 brings jailbreaking to 2.0.2
Rumor: Sprint’s Red HTC Touch Diamond release date August 28th
Motorola i776 Brings The Antenna Back
iLuv intros iMM173 Dual Dock with Alarm for iPhone and iPod
Nokia N85 with OLED Display Screen Officially Announced
Nokia to Release N96 for US in Q4 2008
Nokia Unveils the Nokia N79 Multimedia Computer
HTC unveils Diamond-like S740 smartphone
Titanium LG Voyager
Motorola Blaze ZN4 and Rapture VU30 exposed in live pics
Sony Ericsson W350 Reviews
The mysterious Dirk Dagger and the Fallen Idol now on N-Gage
New Verizon Wireless Blitz with QWERTY Keyboard
LG Voyager Now in Titanium Edition for Verizon Wireless
MediaFLO USA Brings Expanded Live News Coverage to AT&T and Verizon Wireless Phones
M2E Power to Charge Your Mobile Devices via Motion Power
FCC Reveals Size of HTC Dream Andriod Phone
Some information on APIs removed in the Android 0.9 SDK beta
Earlier this week, we released a beta of the Android SDK. In the accompanying post, I mentioned that we had to remove some APIs from the platform for Android 1.0, and as a result they don't appear in the 0.9 beta SDK, and won't appear in 1.0-compatible SDKs. Today, I want to take a few minutes to explain why.
GTalkService
We were all really excited when the "XMPPService" (as it was called, at first) was included in the first early-look SDK. Once we brought in our security review team to examine Android, however, they soon realized that, as exciting as it is, the GTalkService has some fundamental security problems. Rich Cannings is one of our security researchers, and here's his explanation of the issues:
When I first read about GTalkService, I was both excited and scared. As a developer, I was interested in a feature that provided a simple interface to send messages between two Google Talk friends. The messages would appear on the receiving device as a standard Intent that was easy to handle. How simple and beautiful is that? Unfortunately, when I put my tin foil hat on, I recognized that things are a little more complicated than that.
We decided to postpone GTalkService's data-messaging functionality for the following reasons:
"Repurposing" Google Talk Friends
Google Talk friends are intended for a different purpose than that envisioned by the GTalkService. Your Google Talk friends can contact you at any time via IM. They can see your email address and often can see your real name. However, the idea of a Google Talk friend does not always line up with the types of people who may want to interact with via an Android application.
For example, imagine a really cool mobile Massively Multiplayer Online Roleplaying Game using GTalkService. You would have to add all the players to your Google Talk friends list in order to play with them. Next time you log in to Google Talk from your desktop or on the web, you would notice that you have many new "friends". You may not want to chat with these friends -- and perhaps worse, you may not want them to know what your real name or email is.
We do realize that Android users will want to interact with other Android users anonymously and for short periods of time, especially in gaming scenarios. Unfortunately, it turns out that using Instant Messaging is not really a good way to do that.
Verifying Remote Intent Senders
Intents were designed to send messages within the device. The Intent subsystem can conclusively determine who sent Intents only when the Intents originate from the same device that services the Intent. When Intents come from other devices, the Intent subsystem cannot determine what application sent the Intent.
This can lead to a variety of problems. At first, remote applications could send arbitrary Intents, meaning that your Google Talk friends had almost the same control of your device as you did. Even once that issue was resolved, we recognized that we could not trust the identity of the application who sent the request. We could only trust the identity of the user. So a "bad" application on your friend's device could send a message to a "good" application on your device which would negatively affect the good application.
In the end, we determined that the Intent system, as designed for local use, did not lend itself well to being the vehicle for a Remote Procedure Call (RPC).
Placing Too Much Security Burden on Developers
As originally designed, the GTalkService placed a significant burden on the application developer to avoid security flaws and perform user and relationship management. An Android application using GTalkService would be reachable from all of the user's Google Talk friends, and a flaw in that application could pose an inviting target to a malicious "friend" or automated malware. There are automated mechanisms that could be used to help protect vulnerable applications or stop the spread of malware, but the deployment of these technologies was not possible in time for the launch of the first Android handsets.
Although we would have loved to ship this service, in the end, the Android team decided to pull the API instead of exposing users to risk and breaking compatibility with a future, more secure version of the feature. We think it's obvious that this kind of functionality would be incredibly useful, and would open lots of new doors for developers. One of our top priorities after the first devices ship is to develop a device-to-device (and possibly device-to-server) RPC mechanism that is fast, reliable, and protective of developers and users alike.
As a final note, I want to point out that since the GTalkService was always a Google "value-added" service anyway, it was never guaranteed that it would be present on every Android device. That is, GTalkService was never part of core Android. As a result this change actually allows us the potential to build a new system that is part of the core of a future version of Android.
Bluetooth API
The 1.0 version of Android and the first devices will include support for Bluetooth; for instance, Android will support Bluetooth headsets. In the early-look SDKs, there was an incomplete draft of an API that exposed Bluetooth functionality to developers. Unfortunately we had to remove that API from the 1.0 release. To get the skinny on why, I contacted Nick Pelly, one of the Android engineers responsible for that functionality. Here's the story on Bluetooth, in Nick's words:
The reason is that we plain ran out of time. The Android Bluetooth API was pretty far along, but needs some clean-up before we can commit to it for the SDK. Keep in mind that putting it in the 1.0 SDK would have locked us into that API for years to come.
Here's an example of the problems in the API. Client code is required to pass around IBluetoothDeviceCallback objects in order to receive asynchronous callbacks, but IBluetoothDeviceCallback is meant to be an internal interface. That client code would break the moment we added new callbacks to IBluetoothDeviceCallback.aidl. This is not a recipe for future-proof apps.
To make things even more tricky, the recent introduction of the bluez 4.x series brings its own new API. The Android Bluetooth stack uses bluez for GAP and SDP so you'll see more than a passing resemblance to bluez's interfaces in Android. The bluez 4.x change requires us to carefully consider how to structure our API for the future. Again, remember that once we settle on an interface we need to support it for years going forward.
Rather than ship a broken API that we knew was going to change a lot, we chose not to include it. We absolutely intend to support a Bluetooth API in a future release, although we don't know exactly when that will be. This should include some tasty features, such as:
- Bindings to GAP and SDP functionality.
- Access to RFCOMM and SCO sockets.
- Potentially, L2CAP socket support from Java. (This one is under consideration.)
- An API to our headset and handsfree profiles.
On a personal note, Nick adds, "I would love nothing more than to start seeing some neat third-party applications and games over Bluetooth. In my opinion, Bluetooth is completely under-utilized on most mobile platforms and I'm excited to someday see what the developer community can do with Android."
I'm definitely bummed about these API removals. I was particularly looking forward to the P2P capabilities offered by GTalkService, but, as always, user security and privacy must come first. In all these cases, we'll work with the developer community to create some great APIs that balance these concerns.
MediaFLO USA Brings Expanded Live News Coverage to AT&T and Verizon Wireless Phones
Smartest of the smartphones coming?
Verizon Launches Blitz, New Affordable Messaging Handset
Motorola unveils new cell phone with integrated audio player:Motorola W396
Corporate America, Why You Need a Mobile-Optimized Site
If you want to survive the mobile space, I suggest you look into building mobile optimized website as an expansion to your full website. The reason is because while smartphones can now render full HTML pages, the experience is not going to match the way it was intended to be viewed on a desktop monitor. Mobile Safari and Opera Mini’s ability to zoom in-n-out of full web, to me, is just a intermediate solution, allowing consumers to be connected to a website. When you factor in the average desktop monitor today has a resolution of 1280x1024 whilst smartphones have 240x320, the experience can’t be great. It is only an intermediary solution for people familiar with a website’s navigation, if you visit a complicated website for the first time on your iPhone, even thou full web is enabled, you would have a hard time making sense of its intended site navigation.
Mobile websites are no longer the watered-down, boring little text site which used to be called WAP protocol. Today’s Mobile web can be designed to capitalize on a smartphone’s advanced web browsers; to take advantage of the ability to handle images, background colors, tables and even CSS (shading, DIVs, etc.). The trick is to provide most useful navigation and information on the limited screen real estate. If you are a retailer, maybe put the “new arrivals,” “top sellers,” and “sales” section right up front. If you are a publisher, put the “just in,” “local news,” and “world news” up front. If you are a manufacturer, setup your mobile home page by the main categories of your products so a consumer can research them on the go. With a mobile web, you will want to keep “mobility” in mind, store locator and ability to set user location (via GPS, WiFi or manual setting) will be prudent to smart mobile strategy. Brick and mortar stores should definitely play up the location and inventory card (and toss in the price comparison card, you’ve got a winner!). You can always give your audience the option to switch between classic or mobile websites, this way, you can ensure the information they are searching for can be obtained, one way or another.
Over the weekend, I was at a Crate and Barrel looking for a TV Stand for a TV I was planning to purchase. I ended up pulling up full HTML Pioneer’s website over an iPhone 3G and waited forever to navigate and find the TV’s spec sheet to determine if the stand is too small. If they had a mobile-optimized page, I can probably get right to the Plasma TV section faster because the page would be friendlier for my viewing and loads faster with only limited information provided. As in this example, having a full HTML browser did save the day, however, my experience would have been much better if Pioneer had a mobile-optimized site.
Sony Ericsson W760i Soon in Canada
HTC Dream Pictures and Prices
iPhone for Home Arriving Next Year?
Sony Ericsson F305 mobile phone for gamers
We have seen special kind of phones to specific category like music phones, fashion phones etc. but this is bit different because Sony Ericsson F305 is for gamers. They have supply many functions for better mobile game experience. Most important one is the gaming motion sensor. It sense gamer’s motion and supply best gaming experience. And the dedicated gaming keys have designed for best gaming experience. It is very easy to play games with these keys.
The F305 is a member of the Sony Ericsson F range which is a gaming focused mobile phone. The handset is a slide opening phone which comes with easy to use external keys as well as an internal keypad. The Sony Ericsson F305 comes in two colour options which include a polar white & a mystic black coloured casing which both have an elegant high gloss finish. The casing has smooth metal edges which add style to this stunning gaming handset.
Not only games, you can even play your favorite music with high quality. The media player has high quality walkman technology and gives you a quality sound output.
The standby time is very important for a game phone. According to that F305 has 700h standby time. The camera is 2Mp which allows you to take quality pictures. also a FM radio included.
more pics
More features of Sony Ericsson F305
Gaming Motion Sensor
Dedicated Gaming Keys
Style Up™ Covers
2 Inch 262k TFT Colour Screen (176 x 220 Pixels)
2 Megapixel Camera with 2.5 x Digital Zoom
FM Radio RDS
Bluetooth® Technology
700 Hours Standby
Clamshell BlackBerry coming soon:RIM Blackberry 8210 and Blackberry 8220
Motorola VE538 Series
Motorola announces W388 music phone for emerging markets
Few things that you need to know about the Nokia Tube
Samsung Tocco and Samsung G600 – Samsung’ s dazzling gadgets
Sony Ericsson's First 'Made In India' Phone Launched
Samsung Steel
Sony Ericsson W350 Reviews
Motorola Atila touch screen phone with Windows Mobile 6.1
KBB.com Goes iPhone Friendly
Today, KBB.com is committed to provide their information to you, in your pocket. The only thing is, unlike that greasy sales guy back in 1989, you'd be pulling the numbers out of your pocket via an iPhone/iPod Touch. (No offense to greasy car salesmen everywhere, perhaps you guys will be pulling car data out of your iPhone on the lot, instead of "checking" with a manager in that backroom where I know you were just stuffing your face with another donut).
I visited KBB.com on my iPhone, the first time around it pulled up the normal HTML website on mobile Safari. The folks at KBB asked that I try visiting iPhone.kbb.com if problem persists, but I never had to do that. The second try redirected me to the iPhone-optimized page. Overall, the core functions of what we've come to known for Kelly Blue Book are there, ie. new/used car make, model, trim, pricing and resell value. The site is designed with simplicity in mind and it has achieved that. There is the ability to set my location, however, I am not sure if at this stage, the iPhone-optimized site is taking advantage of that info. Which leads to my feedback: I wish after a vehicle has been searched for, KBB.com can provide 1). nearest dealerships and 2). the inventory of the said vehicle at each dealership. Additionally, the overall design of the iPhone site is not friendly with anyone who's got fat fingers. As you can see from the screenshots provided, the menu buttons are narrow; it gets a little narrower as you go deeper into the sub-menus (of models and trims).
Beyond that, I think KBB.com has made great effort in providing their service to consumers (first the internet, now mobile internet). I always applaud large companies taking their initiatives onto the mobile platform; these companies are the ones more likely to succeed in the new age, because by the time mobile net hits critical mass; they will be the "experts" of such practice. Kudos to Kelly Blue Book.
Motorola Releases Next Gen Push-To-Talk on CDMA 1x EVDO Rev A
LG Joins the 8 Megapixel Race, Introducing the LG KC910
Icono Concept Phone: It is about emotions and iconic gestures
SmartBerry: Now children have their own smartphones
Stunning Motorola Rapture VU30 shows its face
Smartest of the smartphones coming?
360 Touch Phone Concept: Slick looks and novel charging solution
LG Gaining Popularity in the US?
Orange Poland Fakes iPhone Lines
Samsung SCH-F639 TVC
Similarities and Differences between QuickPwn and ZiPhone
Jailbreak
Both utilities jailbreak.
Payload medium
Primary jailbreak payload is placed into iPhone memory for both jailbreaks
Differences
Technique
ZiPhone uses, as the root filesystem device, a pseudo-device that provides a window to an arbitrary section of memory. This memory is not allocated or otherwise reserved by the operating system and hence will be used by other random processes in other random ways and will become more and more corrupted with every CPU clock cycle. The only safe way to use this is to mlock all memory used by the jailbreak binary as soon as possible, and then use data previously uploaded to flash. Anything else will cause either the jailbreak binary to crash at random moments or cause random data to be written to flash. I am not sure why Zibri elected not to implement ZiPhone in a safer fashion.
QuickPwn uses the same mechanism that Apple uses to send its update ramdisk. This memory is both allocated and reserved. It will not crash at random moments, or give you repeating BSD root errors. This is the way the XNU kernel is designed to use ramdisks.
Longevity
ZiPhone hinges on a BUG in iBoot that was quickly fixed by Apple.
QuickPwn uses an iBoot FEATURE that Apple cannot remove without rewriting their own software and undergoing lengthy QA. Even if Apple did change the architecture, it would be straight-forward to simply mimic what they do and adapt to it. The reason QuickPwn can do this is because it relies on a hardware exploit to bootstrap into this phase. Apple cannot fix this problem without changing the manufactured hardware.
Elegance
ZiPhone modifies an existing Apple ramdisk and ships it as a complete set.
QuickPwn contains all-original code and features a very tiny bootstrapper that allows it to use libraries and code that's already on the iPhone.
Not only does ZiPhone's distribution of Apple's binaries violate copyright laws, it also takes up a large portion of room on the ramdisk that could be used for the payload. Keeping its existing algorithm, ZiPhone would never have been able to install Cydia, for example. The maximum feasible ramdisk size is 32 MB; Cydia takes 13 and Apple's library take up a significant amount. With some work, Zibri could possibly make it just under the 32 MB limit, but with the large number of files in Cydia, and the large size of the corruptible area of memory, corruption would be inevitable.
Some history / A personal note
Zibri claims to have "invented the ramdisk jailbreak". Even if this were true, it would have as much relevance to QuickPwn as the 1.0.2 jailbreak does: The techniques used are entirely dissimilar. Not a single step in the process is the same.
However, this is not even true. Before Zibri left, we already had a prototype ramdisk jailbreak in our SVN (which Zibri later leaked parts of). It was written by myself and stored under the very obvious name of "ramdisk-jb" and it contained a modified version of a launchd written by Turbo (who should be considered the father of the ramdisk payload). It basically untarred a SSH installation onto the rootfs. It was rudimentary, and required a lot of work to get up to production standards.
While it's obvious that Zibri has picked every bone of that SVN repository clean, I am puzzled why he did not learn from that example source code. It had mlock and it was written in proper C, unlike the rather make-do replacement of launchd with sh. Perhaps he did not understand the code.
A week before his release, we became aware that Zibri was going to write a ramdisk exploit. We considered racing him to it, but we were constrained by the fact that we had already publicized one working method of jailbreaking: The oft-loathed 1.1.3 soft-jailbreak, which we considered perfectly acceptable until the release of the SDK (we were not aware at the time the SDK release would take so long). In addition, 1.1.3 was a minor update and there was no reason people could not stay on 1.1.2 for awhile longer. The issue is that while a ramdisk jailbreak would certainly be easier and better, we would be burning this great exploit that allowed us to reliably decrypt ramdisks (which we had no other way of doing at the time).
Therefore, we chose not to build our own implementation and instead pursue Pwnage, a longer term project. It was ironic months later that Zibri came to flame us out about releasing the dual-boot method, accusing us of burning the exploit. It was amusing because it was so much lower value than the ramdisk exploit, which he was responsible for burning and really had no future prospects because of pwnagetool.
We are aware that the dual-boot method was the last remaining bit of non-public knowledge from our SVN that he had, and my belief was that the flame was caused by his soreness at losing his last chance at remaining relevant after the pmd ("ramdisk") vulnerability was patched.
Sony Ericsson XPERIA X1 scores came on Vodafone's site for October release
LG M-Sports Edition
Motorola Releases Next Gen Push-To-Talk on CDMA 1x EVDO Rev A
Samsung G810 awarded the European Photo Phone 2008-2009
iPhone (3G) Silicone Cases
Samsung i900 Omina coming to Russia as WiTu
AT&T to Welcome Nokia 2680 Slide
Samsung SGH-F400 reviews
Samsung Phones Feature Chinese Text Input from Zi Corporation
MetroPCS to Offer ZTE C79 Music Phone
SAMSUNG SGH-G810 Receives EISA Award
LG KC910 8 megapixel camera phone in works?
Samsung Phones Feature Chinese Text Input from Zi Corporation
Sony Ericsson K660i stylish fashion phone with 3G
Unlike Nokia, Sony Ericsson hasn’t launched many fashion phones. And they usually don’t publish phones with fashion label. But now they have launched K660i fashion mobile with cool features.
The Sony Ericsson K660i is modern & stylish looking 3G mobile phone which comes in a choice of two colour designs. The user can choose between a clean white coloured handset with lime coloured accents & a stunning black coloured handset with wine coloured accents. Both colour options come with metal details on the edging, which enhance the handsets design further. The user can view all their information & pictures on a 262k colour screen which is 2 Inches in size & is a TFT screen.
Sony Ericsson K660i is a 3G phone which works with HSDPA technology. And its web browser is very special because it allows landscape mode web browsing. I haven’t seen this feature in any other Sony Ericsson phones. The web browser supports HTML and RSS.
The built in instant messenger software is another thing. You can connect yahoo, gTalk, msn and many other IM services in one time with one window. K660i has a walkman music player which has good music quality. You can customaries the music quality with its built in equalizer. The camera is 2Mp but you can get clear pictures and record unlimited length videos. The internal memory of this phone is 30Mb but it supports up to 2GB SD memory cards.
Landscape web browser
2 Megapixel camera
full handset
More features of Sony Ericsson K660i
Landscape Mode Internet Browsing
Instant Messaging
3G HSDPA Technology
FM Radio RDS
TrackID™ Music Recognition Feature
2 Megapixel Camera with 4 x Digital Zoom
some useful links
latest mobile phone reviews
read latest mobile phone reviews
live internet TV
watch live gadget videos
GeekBrief.tv - Copy and Paste on the iPhone! For real!
MetroPCS to Offer ZTE C79 Music Phone
LG 10000 Launched For Reliance India Mobile
World’s First Diamond iPhone 3G
iFooty - The must have iPhone App for all Football Fans
Who’s up for an iPhone auction?
PMc magazine for the iPhone to be launched
Get BBC News on your iPhone with iBeeb
Nike+ iPhone application screenshots fake?
Mobiado's luxurious Luminoso Lucido is lovely
LG KF510 Reviews
Sony Ericsson W760 Reviews
LG KC550 Reviews
Sony Ericsson C702 Cyber-shot reviews
HP iPAQ 914c Business Messenger
AT&T and LG Introduce Invision Mobile TV Phone
Does anybody really know what smartphone market share is?
The source is Nielsen Mobile, formerly Telephia. The interesting thing about them is that they do much of the service quality monitoring for the operators, so they have much more direct access to mobile usage information than folks like IDC and Canalys, the people usually quoted for smartphone share.
Wired was focused on Palm's loss of market share, which is indeed striking (but not exactly news). But take a look at the chart again; there are a couple of other items that I think are more newsworthy.
The first surprise is that Nielsen shows Apple in fourth place in smartphone share. That's wildly different from what Canalys, the source usually reported, has been saying (link). Here's how they compare for Q4 2007:
What in the world is going on here?
I'm not sure, but I have some guesses. Canalys doesn't directly measure market share, it receives self-reported shipment reports from the manufacturers and then adds them up. That means Canalys measures shipments into the channel rather than sales, and it depends on the hardware companies to be honest.
Riiiight.
Nielsen Mobile doesn't explain on its website exactly how it measures share, but apparently it's using a mix of survey results and the usage data it gathers from the operators (link). So its numbers should reflect current usage of phones rather than shipments. If Nielsen is measuring installed base share, rather than share of current sales, that might explain the difference. Although in that case, share should not be changing as fast as Nielsen shows. So I'm still confused.
If anybody can shed more light on the source of the difference, please post a comment. I've also asked Nielsen, and will let you know if I hear anything.
The conflict in the numbers underlines how ridiculously useless the publicly-available third party sales numbers are in the mobile phone market, and how little attention the press is paying to the inconsistencies. Apple's share varies from 8% to 28%, and no one even notices. Hey, we got a pretty chart and it confirms what we wanted to say, so don't ask questions.
If you want more information on the problems with mobile market share tracking, I wrote a detailed post here (link).
I said there were two newsworthy things about the Nielsen numbers. Can you spot the second one?
That's right, since the iPhone was released, RIM has been gaining share. So much for the folks who predicted at the launch of the iPhone that it was going to take the smartphone market away from RIM. Instead, at least in the first round of competition, we see what you'd expect from a segmented market -- RIM appeals to some customers, Apple appeals to a different group, and both companies do well.
I can't wait to see what the numbers will look like in six months, after the iPhone 3G has been out for a while. Although probably Canalys and Nielsen will still disagree wildly on what's happening.
Popular Posts
- 199 iphone wall paper
- Scanbuy Announces Addition to Its Board of Directors
- Millions of Names Available for .Co Open Registration
- YouTube Mobile 3G Enhancements & Java Beta Launchd.
- What a wonderful Second Life!
- Google Wave: First impressions
- Nokia N8 + Bluetooth Keyboard + Mouse
- Developers unhappy over Oracle Android suit
- Caribou Coffee to Use Cellfire for Mobile Coupon Offer
- Catching up: 8 random things about me