Archive for July, 2009

PostHeaderIcon How would you change Apple’s iPhone 3GS?


Some might argue it's the most subtle update in the iPhone family thus far, but Apple's iPhone 3GS still seems to be moving the sales meter, regardless. The latest and greatest iPhone officially hit the market a few weeks back, and even though Apple claims that demand is still far outpacing supply, we're of the belief that most everyone who wanted one has managed to snag one by now. During our time with the unit, we definitely didn't find too many reasons to upgrade from the already solid iPhone 3G, but given that you probably did anyway, we're eager to hear how things have turned out. Did you upgrade from a prior iPhone to this? Are you joining the iPhone family for the first time? What gripes have you found impossible to ignore? Are you still up in arms about AT&T's inability to provide MMS / tethering service? Are you, like us, completely roiled by the unit's lack of multitasking abilities? Go ahead and let it rip in comments below -- we're guessing Apple has about 11 months or so to take your opinions to heart.

Filed under: Cellphones

How would you change Apple's iPhone 3GS? originally appeared on Engadget on Sat, 01 Aug 2009 00:31:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

PostHeaderIcon How would you change Apple’s iPhone 3GS?


Some might argue it's the most subtle update in the iPhone family thus far, but Apple's iPhone 3GS still seems to be moving the sales meter, regardless. The latest and greatest iPhone officially hit the market a few weeks back, and even though Apple claims that demand is still far outpacing supply, we're of the belief that most everyone who wanted one has managed to snag one by now. During our time with the unit, we definitely didn't find too many reasons to upgrade from the already solid iPhone 3G, but given that you probably did anyway, we're eager to hear how things have turned out. Did you upgrade from a prior iPhone to this? Are you joining the iPhone family for the first time? What gripes have you found impossible to ignore? Are you still up in arms about AT&T's inability to provide MMS / tethering service? Are you, like us, completely roiled by the unit's lack of multitasking abilities? Go ahead and let it rip in comments below -- we're guessing Apple has about 11 months or so to take your opinions to heart.

Filed under: Cellphones

How would you change Apple's iPhone 3GS? originally appeared on Engadget on Sat, 01 Aug 2009 00:31:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

PostHeaderIcon It’s the Feds! FCC quizzes Apple, AT&T and Google about Google Voice apps

Filed under: Apple Corporate, iPhone, App Store

Earlier today, the FCC (Federal Communications Commission) sent out letters to Apple, AT&T and Google, readable here [FCC's letter to Apple, to AT&T & to Google] asking each company about its involvement in the Google Voice app rejections. The agency is asking Apple to explain why the Google app was rejected and the third-party apps removed, if any VoIP apps have been approved, and whether there are general rules and regulations covering application approvals (something many developers would also love to know).

It's worth noting that none of the Google Voice apps are VoIP (voice over IP) applications in the traditional sense, as they rely on the cellular carrier's voice network to handle calls, so it's not clear if the FCC understands this or if the agency is heading down a blind alley on this particular topic.

To Google, the letter asks if any other Google apps have been accepted in the store (we know there are a few), whether Apple explains the rejection process or the reasoning behind the treatment of Google Latitude, if there are other ways to use Google Voice on the iPhone (again, a somewhat naive question, as the service works fine via touchtone commands and Mobile Safari), and lastly and most intriguingly, what the app approval process is for Android applications (should be a short answer: "C'mon in, the water's fine!").

Finally, the agency is asking AT&T how the carrier was consulted on this decision, if any VoIP applications are running on their network (again, missing the point, since GV ≠ VoIP -- more relevant that there are BlackBerry apps for Google Voice that are happily on AT&T handsets), and whether AT&T can provide a list of rejected applications on the store while detailing the role it plays in approving possible 3G-enabled services like Sling.

The FCC has given the three companies until August 21 to respond to their letters; while the overall scope of the questions betrays quite a bit of agency unfamiliarity with the workings of the Google Voice service and the App Store, any movement toward openness and clear answers is positive. Hopefully, these responses will offer some insight into the story of this whole mess that has given everyone such indigestion over the past week.

[via Engadget, links to FCC via BusinessWeek]

TUAWIt's the Feds! FCC quizzes Apple, AT&T and Google about Google Voice apps originally appeared on The Unofficial Apple Weblog (TUAW) on Sat, 01 Aug 2009 00:20:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Add to digg Add to del.icio.us Add to Google Add to StumbleUpon Add to Facebook Add to Reddit Add to Technorati

PostHeaderIcon It’s the Feds! FCC quizzes Apple, AT&T and Google about Google Voice apps

Filed under: Apple Corporate, iPhone, App Store

Earlier today, the FCC (Federal Communications Commission) sent out letters to Apple, AT&T and Google, readable here [FCC's letter to Apple, to AT&T & to Google] asking each company about its involvement in the Google Voice app rejections. The agency is asking Apple to explain why the Google app was rejected and the third-party apps removed, if any VoIP apps have been approved, and whether there are general rules and regulations covering application approvals (something many developers would also love to know).

It's worth noting that none of the Google Voice apps are VoIP (voice over IP) applications in the traditional sense, as they rely on the cellular carrier's voice network to handle calls, so it's not clear if the FCC understands this or if the agency is heading down a blind alley on this particular topic.

To Google, the letter asks if any other Google apps have been accepted in the store (we know there are a few), whether Apple explains the rejection process or the reasoning behind the treatment of Google Latitude, if there are other ways to use Google Voice on the iPhone (again, a somewhat naive question, as the service works fine via touchtone commands and Mobile Safari), and lastly and most intriguingly, what the app approval process is for Android applications (should be a short answer: "C'mon in, the water's fine!").

Finally, the agency is asking AT&T how the carrier was consulted on this decision, if any VoIP applications are running on their network (again, missing the point, since GV ≠ VoIP -- more relevant that there are BlackBerry apps for Google Voice that are happily on AT&T handsets), and whether AT&T can provide a list of rejected applications on the store while detailing the role it plays in approving possible 3G-enabled services like Sling.

The FCC has given the three companies until August 21 to respond to their letters; while the overall scope of the questions betrays quite a bit of agency unfamiliarity with the workings of the Google Voice service and the App Store, any movement toward openness and clear answers is positive. Hopefully, these responses will offer some insight into the story of this whole mess that has given everyone such indigestion over the past week.

[via Engadget, links to FCC via BusinessWeek]

TUAWIt's the Feds! FCC quizzes Apple, AT&T and Google about Google Voice apps originally appeared on The Unofficial Apple Weblog (TUAW) on Sat, 01 Aug 2009 00:20:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Add to digg Add to del.icio.us Add to Google Add to StumbleUpon Add to Facebook Add to Reddit Add to Technorati

PostHeaderIcon T-Mobile Mytouch 3G Review - PC World


Mobiletor.com

T-Mobile Mytouch 3G Review
PC World
The Apple iPhone 3G is taller and slightly slimmer than the myTouch. The phone's gentle curves are more than aesthetic touches: Its bottom tip has a more ...
Google Summons Android for Smart-Phone Attack: Rich JaroslovskyBloomberg
Hands-on review: T-Mobile's myTouch 3GYahoo! Tech
T-Mobile displays its strong sense of touchPRWeek

all 27 news articles »

PostHeaderIcon It’s the Feds! FCC quizzes Apple, AT&T and Google about Google Voice apps

PostHeaderIcon Teen devises a prayer app for iPhone - Kansas City Star


Teen devises a prayer app for iPhone
Kansas City Star
Allen Wright of Fair Oaks, Calif., has a model of the “A Note to God” application on his iPhone. His idea was selected from 20000 entries. ...

and more »

PostHeaderIcon The Daily Roundup: here’s what you might’ve missed

#saleschart {border:0px solid #333;border-collapse:collapse;}#saleschart td {padding:7px;border-bottom:0px solid #ccc;vertical-align:top;margin:0;line-height:1.3em;font-size:100%;}#saleschart th.bottomrow {border-right:1px solid #333;}#saleschart tr.features1 {border-top:1px solid #333;}#saleschart td.bottomrow2 {border-right:1px solid #333;}#saleschart th {font-size:100%;font-weight:bold;text-align:left;padding:4px;background:#f3f3f3;border-top:1px solid #333;}
iPhone OS 3.0.1 update released, fixes SMS vulnerability
Looks like Apple pulled the trigger on patching that nasty iPhone SMS vulnerability a little earlier than we expected. It's not some lightweight, either: you're looking at 280MB of love here, so get downloading, friends.

Take Back the Beep: how to disable voicemail instructions
Thanks to some helpful comments we've got instructions for Sprint, AT&T and Verizon for lopping off bits of the message, and, in Verizon's case, speeding up the talking.
TASER X3 video hands-on: watch out, baddies
the appeal of a "non-lethal" deterrent is understandable (and certainly preferable to the alternative variety).
Other news of import
Netflix Watch Instantly coming to Windows 7 Media Center
No hard release date yet or big surprises here as Vista owners got this access some time ago and Extenders still don't support Silverlight.
Nokia Surge review
Some might say that this is the most un-Nokia-like Nokia device produced in quite some time (if not ever), but remember, this one was custom made for US consumers and AT&T's audience

The Daily Roundup: here's what you might've missed originally appeared on Engadget on Fri, 31 Jul 2009 22:12:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

PostHeaderIcon Hallelujah! FCC Investigating Apple For Google Voice App Rejection [IPhone]

Detect language - Albanian Arabic Bulgarian Catalan Chinese Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician German Greek < / option> Hebrew Hindi Hungarian Indonesian Italian Japanese Korean Latvian Lithuanian Maltese Norwegian ALPHA Persian Polish Portuguese Romanian < option value = "ru"> Russian Serbian Slovak Slovenian Spanish Swedish Thai Turkish < / option> Ukrainian Vietnamese > Albanian Arabic Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician German Greek Hebrew Hindi Hungarian Indonesian Italian Japanese < / option> Korean Latvian Lithuanian Maltese Norwegian Persian ALPHA Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swedish < option value = "th"> Thai Turkish Ukrainian Vietnamese class=swap swap < / td> window.jstiming.load.tick ( 'br'), h = new _History () ; ctr = new _TranslateForm (new _LanguageSelector ( 'old_sl', 'sl_select','3 '), new _LanguageSelector (' old_tl ',' tl_select ','3'), 'old_submit', 'submit_button', h, 'source ',' result_box ',' dict ',' auto trans', '/ translation', '/ translate_t', undefined, 'http://209.85.225.132/translate_f', 'select_text', 'select_document', 'file_div', 'file', true, 'search', 'CLIR'); window.jstiming.load.tick ( 'prt') < img src = "http://www.google.com/images/zippy_plus_sm.gif" style = "margin-right: 0.33em; visibility: hidden" id = zippyicon> < input type = hidden name = hl value = "en"> < text input type = hidden name = langpair value = "en | en"> < td width = 49%> < td align = right> Google Home - About Google Translate 2009 Google

Translating … < / iframe> Detect language—AlbanianArabicBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHebrewHindiHungarianIndonesianItalianJapaneseKoreanLatvianLithuanianMalteseNorwegianPersian ALPHAPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwedishThaiTurkishUkrainianVietnamese > AlbanianArabicBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHebrewHindiHungarianIndonesianItalianJapaneseKoreanLatvianLithuanianMalteseNorwegianPersian ALPHAPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwedishThaiTurkishUkrainianVietnamese swap window.jstiming.load.tick(’br’);h = new _History();ctr = new _TranslateForm(new _LanguageSelector(’old_sl’,’sl_select’,'3′),new _LanguageSelector(’old_tl’,'tl_select’,'3′),’old_submit’,’submit_button’, h,’source’,'result_box’,'dict’,'autotrans’,'/translate’,'/translate_t’,undefined,’http://209.85.225.132/translate_f’, ’select_text’,’select_document’, ‘file_div’, ‘file’,true,’search’,'clir’);window.jstiming.load.tick(’prt’)Contribute a better translationThank you for contributing your translation suggestion to Google Translate.We'll use your suggestion to improve translation quality in future updates to our system.</ div> <div id=clir> </ div> </ td> </ tr> <tr> <td class=submitcell> <div style=float:left> <select name = sl id = old_sl tabindex = 0 > <option value="auto"> Detect language </ option> <option value="separator" disabled> - </ option> <option value="sq"> Albanian </ option> <option value="ar"> Arabic </ option> <option value="bg"> Bulgarian </ option> <option value="ca"> Catalan </ option> <option value="zh-CN"> Chinese </ option> <option value = "hr"> Croatian </ option> <option value="cs"> Czech </ option> <option value="da"> Danish </ option> <option value="nl"> Dutch </ option> <option SELECTED value = "en"> English </ option> <option value="et"> Estonian </ option> <option value="tl"> Filipino </ option> <option value="fi"> Finnish </ option > <option value="fr"> French </ option> <option value="gl"> Galician </ option> <option value="de"> German </ option> <option value="el"> Greek < / option> <option value="iw"> Hebrew </ option> <option value="hi"> Hindi </ option> <option value="hu"> Hungarian </ option> <option value="id"> Indonesian </ option> <option value="it"> Italian </ option> <option value="ja"> Japanese </ option> <option value="ko"> Korean </ option> <option value = "lv "> Latvian </ option> <option value="lt"> Lithuanian </ option> <option value="mt"> Maltese </ option> <option value="no"> Norwegian </ option> <option value = "fa"> ALPHA Persian </ option> <option value="pl"> Polish </ option> <option value="pt"> Portuguese </ option> <option value="ro"> Romanian </ option> < option value = "ru"> Russian </ option> <option value="sr"> Serbian </ option> <option value="sk"> Slovak </ option> <option value="sl"> Slovenian </ option > <option value="es"> Spanish </ option> <option value="sv"> Swedish </ option> <option value="th"> Thai </ option> <option value="tr"> Turkish < / option> <option value="uk"> Ukrainian </ option> <option value="vi"> Vietnamese </ option> </ select> <span class=langselect id=sl_select> </ span> <span class = "arrow" onclick = "ctr._swap ()">></ span> <select name=tl id=old_tl tabindex=0> <option value="sq"> Albanian </ option> <option value =" ar " > Arabic </ option> <option value="bg"> Bulgarian </ option> <option value="ca"> Catalan </ option> <option value="zh-CN"> Chinese (Simplified) </ option> <option value="zh-TW"> Chinese (Traditional) </ option> <option value="hr"> Croatian </ option> <option value="cs"> Czech </ option> <option value = "da "> Danish </ option> <option value="nl"> Dutch </ option> <option value="en"> English </ option> <option value="et"> Estonian </ option> <option value = "tl"> Filipino </ option> <option value="fi"> Finnish </ option> <option value="fr"> French </ option> <option value="gl"> Galician </ option> <option SELECTED value = "en"> German </ option> <option value="el"> Greek </ option> <option value="iw"> Hebrew </ option> <option value="hi"> Hindi </ option > <option value="hu"> Hungarian </ option> <option value="id"> Indonesian </ option> <option value="it"> Italian </ option> <option value="ja"> Japanese < / option> <option value="ko"> Korean </ option> <option value="lv"> Latvian </ option> <option value="lt"> Lithuanian </ option> <option value="mt"> Maltese </ option> <option value="no"> Norwegian </ option> <option value="fa"> Persian ALPHA </ option> <option value="pl"> Polish </ option> <option value = " pt "> Portuguese </ option> <option value="ro"> Romanian </ option> <option value="ru"> Russian </ option> <option value="sr"> Serbian </ option> <option value = "sk"> Slovak </ option> <option value="sl"> Slovenian </ option> <option value="es"> Spanish </ option> <option value="sv"> Swedish </ option> < option value = "th"> Thai </ option> <option value="tr"> Turkish </ option> <option value="uk"> Ukrainian </ option> <option value="vi"> Vietnamese </ option > </ select> <span class=langselect id=tl_select> </ span> <a href="" onclick="ctr._swap();return false;"> class=swap swap </ a> </ div> <div style=float:right> <span class=subbutton id=submit_button> </ span> <input type=submit id=old_submit value="Translate" tabindex=0> </ div> </ td> <td> < / td> <td id=dict> </ td> </ tr> <tr> <td colspan=2> <script> window.jstiming.load.tick ( 'br'), h = new _History () ; ctr = new _TranslateForm (new _LanguageSelector ( 'old_sl', 'sl_select','3 '), new _LanguageSelector (' old_tl ',' tl_select ','3'), 'old_submit', 'submit_button', h, 'source ',' result_box ',' dict ',' auto trans', '/ translation', '/ translate_t', undefined, 'http://209.85.225.132/translate_f', 'select_text', 'select_document', 'file_div', 'file', true, 'search', 'CLIR'); window.jstiming.load.tick ( 'prt') </ script> </ td> <td ALIGN=RIGHT> <span id = zippyspan onclick = "_rolldown ()">< img src = "http://www.google.com/images/zippy_plus_sm.gif" style = "margin-right: 0.33em; visibility: hidden" id = zippyicon> </ span> </ td > </ tr> </ table> </ form> <table id=suggesttable> <tr> <td colspan=3> <div id=thanks style="height:0px; display: none"> <span style = " padding: 2px; background-color: # ff9 "id = sug_thk> </ span> </ div> <form action =" / translate_suggestion "target = hidden_iframe method = post id = suggestion_form style =" height: 0px; overflow: hidden ; display: none "class = highlight onsubmit =" _submitroll ()">< input type = hidden name = hl value = "en"> <input type=hidden name=oe value="ISO-8859-1"> <input type = hidden name = value ="">< text input type = hidden name = langpair value = "en | en"> <input type=hidden name=gtrans value=""> <table id=suggesttable> <tr> < td width = 49%> <span style="float: right; font-size:smaller" id=sug_exp> </ span> </ td> <td width=2% rowspan=2> </ td> <td id = utranscell width = 49%> <textarea name=utrans wrap=SOFT dir="ltr" rows=5 id=suggestion> </ textarea> </ td> </ tr> <tr> <td> </ td> < td align = right> <input type=submit value="Contribute"> </ td> </ tr> </ table> </ form> </ td> </ tr> </ table> <div class=footer> <a href="http://www.google.com/webhp?hl=en"> Google Home </ a> - <a href = "http://www.google.com/intl/en/help / faq_translation.html "> About Google Translate </ a> <br> <br> 2009 Google </ div> <iframe name=hidden_iframe style="display:none"> </ iframe> </ div> <div id = "result_div" style = "display: none"> <div> <iframe id="annotation" marginheight="0" marginwidth="0" scrolling="no" frameborder="0"> </ iframe> </ div> <div class=small width="100%"> </ div> <div class=big width="100%"> </ div> <div id=process_div dir=> <p align=center> <font size = +1 face = arial, sans-serif> <a href="javascript:void(0)"> Translating …</ a> </ font> </ p> </ div> <div class = " main "> <iframe name="post_target" id="post_target" frameborder="0" onreadystatechange="_stateChangeIE(this, document.body.clientHeight)" onload="_stateChange(this, document.body.clientHeight)"> < / iframe> </ div> </ div> </ body> </ html>Google Home - About Google Translate©2009 Google

Translating…

PostHeaderIcon FCC Seeks Details on Google App Rejection For iPhone - New York Times


Reuters

FCC Seeks Details on Google App Rejection For iPhone
New York Times
By REUTERS The Google application is seen by some as a competitive threat to the voice services that come with the iPhone, which is carried exclusively in ...
Three Astronomy Apps for the IPhonePC World
Apple makes finding iPhone apps easierCNET News
Honeymoon Ends For iPhone As Realities Set InWashington Post
InformationWeek -New York Times -Washington Post
all 1,052 news articles »
Sponsors

 

Archives