Samsung Wave 725 leaks out of the bada 2.0 SDK
While playing around with the bada 2.0 software development kit, the guys over at bada World stumbled upon an interesting discovery. Reportedly, one of the device emulators that came along with the software mentioned a yet-unannounced smartphone known as the Samsung Wave 725.
Now, this may be the first time when we hear about the alleged Samsung Wave 725, but we knew that its sketch reminded us of a bada device that we had seen before. Remember when three months ago Samsung of France revealed a couple of smartphones meant to run the company's proprietary software platform? Well, if we take a closer look at a rendering of one of them, it becomes pretty obvious that the handset bears a very close resemblance to the leaked Wave 725.
If it ever gets to see the light of day, the Wave 725 is expected to pack a 3.65-inch display with a resolution of 320 by 480 pixels, 5-megapixel main camera with a secondary front-facing shooter, Wi-Fi, Bluetooth 3.0 and GPS. Nothing much impressive, we know, but the bada 2.0 platform is where the real improvements over older handsets from the Wave lineup will be. The next major release of Samsung's mobile operating system is expected to bring a revamped user interface and support for multitasking.
More details about bada 2.0 and the smartphones that will adopt it should be out pretty soon as the platform is expected to debut within the next couple of months.
source: bada World (translated) via IntoMobile
Now, this may be the first time when we hear about the alleged Samsung Wave 725, but we knew that its sketch reminded us of a bada device that we had seen before. Remember when three months ago Samsung of France revealed a couple of smartphones meant to run the company's proprietary software platform? Well, if we take a closer look at a rendering of one of them, it becomes pretty obvious that the handset bears a very close resemblance to the leaked Wave 725.
The Samsung Wave 725 leaked from the bada 2.0 SDK
source: bada World (translated) via IntoMobile
Things that are NOT allowed: