TopOfBlogs Softwares: Samsung S3650 Corby specifications and india price

Samsung S3650 Corby specifications and india price

Friday, September 11, 2009
Samsung Today officially unveiled new S3650 Corby touch phone after Samsung Jet and Samsung Star budget touch phones . Our first impressions on Samsung Corby is that its basically a phone well suited for ladies and young students . It looks more compact than Samsung star and is available in multiple colors .Samsung S3650 Corby specifications includes a 2 mega pixels camera ,2.8 inch QVGA capacitive touchscreen ,upto 8GB expandable memory , Bluetooth 2.1 with A2DP and 2G connectivity . Samsung S3650 Corby will be launched in Europe this month with initial pricing of 150 euro . Its really high when compared with the specs of LG cookie and Samsung Star 2G that offer 3 mega pixel camera at a lower rate than Corby .
Samsung S3650 Corby specifications :

Like any recent Samsung release , S3650 Corby also include on screen widgets to access web 2.0 social websites like YouTube,Facebook ,Twitter, Flickr, Picasa, Photobucket etc . Samsung Touchwiz user interface makes it easy to organize and arrange these widgets .Corby's 2.8 inches TFT touch screen comes with accelerometer sensor and inbuilt on screen keyboard .Li-Ion 960 mAh battery , FM radio with RDS , full function web browser ,GPRS class 10 are the other notable features of new Samsung S3650 Corby .This phone is black in color from front side ,and anything from Jamaican Yellow, Cupid Pink, Minimal White or Festival Orange on backside .Samsung S3650 Corby price in India :As per today's announcement Samsung S3650 Corby would cost more than 10000 INR in India . But considering the price of Samsung Star and Cookie we expect the price to fall below 8000 to near 7500 INR . At this point Corby will do a good business with it unique colorful looks and touch screen facility . google_protectAndRun("ads_core.google_render_ad", google_handleError, google_render_ad); google_protectAndRun("ads_core.google_render_ad", google_handleError, google_render_ad);

0 comments:

Post a Comment