2012年2月24日金曜日

ドコモ・NEC・パナソニックモバイル・富士通、全ての通信方式に対応可能なモデムを共同開発

 NTTドコモ、日本電気、パナソニック モバイルコミュニケーションズ、富士通の4社は24日、「GSM」「W−CDMA」「HSPA+」および「LTE」の、すべての通信方式に対応可能なモデム技術を開発完了したことを発表した。

 通信制御に関する機能をつかさどるLSIのエンジニアリングサンプル性能評価を経て、同日、主要ネットワークベンダとの接続に必要な、全試験工程を実施・完了したとのこと。通信方式はすべて3GPPによる標準規格に準拠し、特にLTEについてはドコモが採用しているFDD方式、中国等で採用が予定されているTDD方式ともに対応している。

 今回の開発によって、これまで多くの場合、端末内に2つ搭載する必要があったLSIを1つに集約することが可能となる見込み。これにより、通信時や待受け時の消費電力を、従来比で最大20%低減することが可能となるほか、搭載LSI数を減少させることで、端末の価格低減にも寄与すると見られる。

 4社は、このLSIを採用して、4社を含む合弁会社を通じた国内外への販売展開を検討していく。また、次世代の通信規格であるLTE−Advancedへの対応を含む拡張開発を続ける計画だ。

 なおNTTドコモ、日本電気、パナソニック モバイルコミュニケーションズ、富士通の4社は、LTE対応の通信プラットフォーム「LTE-PF」においても共同開発を行っており、2009年に開発を完了させている。

2012年2月23日木曜日

無料Wi-Fiサービス「セブンスポット」

最近、セブンイレブンでiPhoneを立ち上げると、Wi-Fiに接続されることにお気づきの方も多いのではないでしょうか?それはおそらく、先日セブンネットショッピングが開始した無料Wi-Fiサービス「セブンスポット」です。昨年12月より東京23区でサービスを開始しました。

セブンイレブンの他に、イトーヨーカ堂、西武、SOGO、デニーズで使えるとのこと。

セブンネットショッピングのIDで利用可能
セブンネットショッピングのIDがあれば無料で利用することができます。

アクセスは

1回につき最大60分
1日につき3回まで

という制限がつきますが、スマートフォンからだけでなく、PCからでも利用できるのは便利だと思いました。(私はiPhoneでしか接続したことはありませんでした)

コンビニで活用するシーンはなかなかあまり思い浮かびませんが、デパートやファミレスで食事やお茶をしている際に、PCで作業することもできると思います。(ちなみに、都内でもイートインスペースのあるセブンイレブンもあるので、そういう場所だったらいいかも)

60分という制限がつくため、長時間のノマドワークには適していませんが、すきま時間にメールの閲覧や資料の修正などちょっとした仕事には十分活用できるのではないでしょうか。

GoogleがついにRDBMSサービスの提供を開始!

 2011年11月、Googleは「Google Cloud SQL」というサービスの提供を始めました。リレーショナルデータベース管理システム(RDBMS)の機能をインターネットを通して提供するサービスです。はやりの言葉で言えば、「クラウド環境で動作するRDBMS」ということです。

 本稿執筆時点では、このような形でRDBMSのサービスを提供している例は少なく、すでに有料サービスを提供しているマイクロソフトの「Microsoft SQL Azure Database」やアマゾンの「Amazon Relational Database Service(Amazon RDS)」が先行しているような状況です。

 先行する2社と比べると、Googleはサービス提供を始めたばかりです。そのせいか、Google Cloud SQLは現在、"Limited Preview(限定プレビュー)"という扱いになっており、一部のユーザーのみに無料で公開しています。利用するには申し込みが必要で、申し込んでしばらくたつと、招待のメールがやってきます。まだ、多くのユーザーに対応するほどのハードウェアを準備していないのかもしれません。ハードウェアなど、受け入れの準備ができたところで招待状を送っているということも考えられます。

 Google Cloud SQLは、オラクルのMySQLを基にしたサービスであり、MySQLとほとんど同じように扱えます。Java言語を利用して、JDBC(Java Database Connectivity)経由でGoogle Cloud SQLに接続することも可能です。

スマホアプリ開発における6つのポイント

 企画から運用まで、格段階でまず何を考え、どういう点に留意するべきなのか、そしてフィーチャーフォンとスマートフォンではどいうった点が違ってくるのか、全力案内!の経験を通じて同氏が得たノウハウの発表である。

 【1】企画のポイント

 企画の際にまず考えるべきことは、「そのサービスによって、誰に、どうなってほしいのか」「なぜ、それが必要か」という点である。そのためには、自身がユーザーになり切ることや、ユーザーに一番近い立場の人の意見を聞くことが重要とのこと。

 「全力案内!」の場合には、iPhone版を開発する際に、さまざまな機能のアイデアがあったが、実際の初期リリースでは5つのフィーチャーのみに絞って実装を行ったという。その中には、フィーチャーフォン版ですでに提供されていた「ナビ機能」も含まれていなかった。「全力案内!」のコンセプトを実現するために、最も重要な機能のみに絞って実装し、スモールスタートで磨き上げていったそうだ。

 【2】仕様・設計のポイント

 仕様・設計の段階では、まず実機を買い、そしてそれを使い倒すことが何よりも先決である。そうすることで、その機種の特性や問題点、ユーザーの利用シーンなどが見えてくる。「特に、ユーザーの日常において、どこで使ってもらえるかを考えることは極めて重要だ」と北村氏はいう。この段階で、フィーチャーフォンとスマートフォンでは、さまざまな前提が異なってくるという。

  • フィーチャーフォン
    • 操作性の前提
      • 物理キー中心の操作
      • 片手で使える
    • 見た目の前提
      • 画面サイズがある程度限られている
    • プラットフォームの前提
      • SUID認証
      • マイメニュー登録
  • スマートフォン
    • 操作性の前提
      • タッチ中心の操作
      • 両手で使う場合もある
    • 見た目の前提
      • 画面サイズが多様
      • Androidでは画面密度の違いもある
    • プラットフォームの前提
      • GPSやセンサ、Wi-Fiなどが使える
      • APIによる課金
      • アプリ間連携が可能
      • マルチタスク

 フィーチャーフォンからスマートフォンへの移行の場合、現実的にはUIやサービス仕様は再構築が必要で、特にスマートフォン特有の操作性を考慮することや、フィーチャーフォンの機能をどこまで実装するのかを明確にすることなどが重要とのことである。

 【3】開発・テストのポイント

 開発・テストの段階では、特に1人当たり複数台の実機が必要となる。実機がなければ分からないことが、たくさんあるからだ。

 そして、実機を使って開発するうえで大事なポイントは「節電」である、と北村氏は強調した。バッテリへの影響はアプリの評価に大きく影響する。特に「全力案内!」の場合は長時間続けて使われるケースもあるため、センサを繋いでの実測とバッテリ計測アプリを併用しながら開発を進めたという。

 また、フィーチャーフォンとスマートフォンではライフサイクルが大きく異なるので、その違いにも注意する必要があるとのこと。

 テスト段階では、特にGPSや各種センサ、Bluetooth、SDカードなどといったデバイス固有の機能へアクセスする部分は入念にチェックする必要がある。可能であればターゲット機種ごとに確認するのが望ましいという。

 また、課金系のAPIについては、通信キャリアによって課金遷移が異なるので、注意が必要とのことだ。

 【4】デプロイのポイント

 デプロイの段階では、アプリのサイズに気を付ける必要がある。スマートフォンの場合、大容量アプリの配布も可能だが、ユーザーの通信環境や端末容量を考慮しなければならない

 SDカードによるインストールを許可しない場合には、端末の内蔵メモリを圧迫する可能性もあるので、最終的にアプリがどれだけのサイズになるのかをアナウンスする気遣いも必要とのことだ。

 【5】リリースのポイント

 iPhoneの場合、App Storeでの配布には審査が必要で、場合によっては差し戻されることもあるので、それを前提としたスケジュールを組まなければならない。

 その一方で、審査に入って以降は差し戻しや旧版へ戻すことはできないので、その点にも注意が必要となる。

 【6】運用のポイント

 Webサービスの場合、「リリースすれば完成」というわけではない。安定した運用がサービスの評価を大きく左右する。スマートフォン特有の問題としては、マーケット側のスケジュールなどがアプリの販売などに大きく影響してくる点が挙げられた。

 例えば、App Storeでは一斉に価格変更が行われたケースもある。そのような事態に対応するため、マーケットのアナウンスや開発者向けメールは注視しておかなければならない。その他、利用者統計情報などを参考にマーケットを動きを把握することも重要だと北村氏は指摘している。

スマホ3大OS同時開発は、どこまで可能なのか

 ブリリアントサービスのかわかみひろき氏、八木俊広氏、原昇平氏の講演「Android, iOS, Windows Phone向けにアプリを同時開発せよ」では、Android、iOS、Windows Phoneの3つのプラットフォーム向けに「デブサミ用のTwitterクライアント」を受託開発するという案件を想定した発表があった。

 対象が3つのプラットフォームということで、まず考えるのはクロスプラットフォームのツールを使っての開発だろう。ところが、PhoneGapを利用してプロトタイプを作ってみたところ、一部のプラットフォームで期待した通りの動作にならないという問題が発生した。

 また、要件定義を正しく行わなかったために、そもそも発注元はプラットフォームごとの特色を出すことを望んでいたという事実が後になって発覚した。つまり、そもそもクロスプラットフォーム開発が向かない案件だったわけだ。

 これが物語の出発点である。では、この複数プラットフォーム向けの開発案件を成功させるためには、どうしたらいいのか。先の失敗からネイティブ開発が適していると結論付けたうえで、開発の各工程において注意するべきポイントが紹介された。

 まず、開発前に確認しておくべきこととして、次の8つの項目が挙げられた。

  1. 【OSのバージョン】すべてのバージョンでは対象が広すぎて互換性の確保が困難
  2. 【端末の種類】同上
  3. 【サポートする言語】スマートフォンの場合、販売チャンネルがワールドワイドになる
  4. 【タブレットはどうするか】画面が大きいためUXが異なる
  5. 【テスト端末の確保】自前で用意する必要があるのか
  6. 【公開予定日】審査期間も考慮
  7. 【暗号化の有無】コンテンツ保護やユーザー情報の管理をどうするのか
  8. 【納品の仕方】ソース+アプリの納品なのか、マーケット公開までやるのか

 UIデザインを考える際には、最初に必要な画面を洗い出して構成を決める。そのうえで、次の4点を意識してデザインすることが重要だという。

  1. プラットフォームごとのUI部品の違い
  2. ハードキーによる操作感の違い
    • iOSはホームボタンのみで、その他の操作はすべて画面上で行う
    • AndroidとWindows Phoneにはホーム以外のハードキーがある
  3. 画面遷移の違い
    • iOSはナビゲーションバーとタブ
    • AndroidはActivity
    • Windows Phoneはパノラマとピポット
  4. 画面解像度やスクリーンサイズ、画面密度(Android)の違い

 これらを考慮すると、画面仕様はプラットフォームごとにまったく違ったものになることは明らかだ。

 実際に開発を行う段階では、最低限次の6つのリソースを用意する必要があるとのこと。

  1. 【アイコン画像】プラットフォームごとにサイズが異なる
  2. 【スプラッシュ画像】同上
  3. 【文字列リソース】プラットフォームごとに形式が異なるほか、サポートする言語の数だけ必要
  4. 【画像部品】解像度ごとにそれぞれ必要
  5. 【メディアリソース】動画や画像のサイズ制限が異なる
  6. 【マーケット用リソース】マーケット公開の用意が必要

 テストおよびマーケット配信のための準備としては、次の6つのポイントを考慮する必要がある。

  1. 取得しなければならないアカウント
  2. アカウント取得に掛かるコストや有効期限
  3. アカウント取得にかかる時間
  4. 公開のための審査と審査機関
  5. リジェクトの可能性や、その影響
  6. アプリの容量

 その他、講演では冒頭の想定案件に対する開発を実際に行い、プラットフォームごとに微妙に異なる動作や実装方法の違いにどう対処するかといったTipsも紹介された。

 クロスプラットフォーム開発のメリットに注目が集まっている昨今だが、現実的には、まだ課題が多いことや、開発要件を満たすために(そして、プロジェクトを成功に導くために)何を意識すべきかなど、複数プラットフォーム向け開発のためのヒントが示された発表だった。

HTML5でスマホアプリ開発、ホントのところ

 ディー・エヌ・エー CTO室 紀平拓男氏の講演「スマートフォンにおけるHTML5実装の最先端」では、スマートデバイスにおけるHTML5関連技術の状況が紹介された。スマートデバイスにおけるHTML5関連技術はネイティブアプリに匹敵する状況まで習熟してきているという。

 まず紀平氏は、HTML5のCanvas要素に言及。JavaScriptのAPI経由で任意のドット描画が可能になったことに触れ、Flashで開発されたゲームとCanvas要素を活用して開発されたゲームのデモを示し、遜色ないレベルに到達していることが紹介された。デモを見る限り、違いを見つける方が困難だったといえる。

 また、 ApplicationCacheやlocalStorageなどの機能を取り上げ、アプリ開発に重要となる機能が用意されている点も紹介された。

 かといって、HTML5がパーフェクトな代替技術かといえば現状はそうでもなく、いくつかの弱点があることも指摘。特に「3D、音楽、速度といった内容で弱い面がある」と紀平氏。

 まず3Dについて、スマートデバイスではOpenGLが利用できないという。OpenGLをHTML5で活用するためのWebGLはFirefox for mobileのみがサポートしており、広く利用できる状況にはない。

 音楽はタイミング調整が極めてシビアであるうえに、同時に音が鳴らせないなどなにかと制限がきつい状況にある。

 また、そもそも描画速度が遅かったり、JavaScriptの実行そのものが遅かったり、ネイティブアプリにはかなわない面があるという。

 紀平氏からは実際の開発経験から、開発のポイントなども紹介された。CanvasレンダリングはiPhone/iOS 4の方がAndroidよりも遅いため、iPhone/iOS 4で快適に動作するように開発するようにしているという。

 特に、iOS 4はdrawImageが遅く、キャッシュを活用するなどして、いかにdrawImageの回数を減らすかが重要になるというアドバイスもあった。なおiOS 5では、この問題は解決しているという。

 また、処理の関係から「Canvasの上にさらにDOM要素を載せるといったことはしない方が良い」(紀平氏)といったアドバイスもあった。

 CSS3は基本的にGPUサポートで実行されるため、サクサク動作するが、同時に動作する物体が増えると急激に重くなること、AndroidではWebブラウザやデバイスごとに互換性問題が出ること、アニメーションなどに問題があるという点についても言及があった。1枚もののアニメーションで同時に動くものが少ない場合には、CSS3が活用できるが、それ以外のケースではCanvasの方が効果的という説明もあった。

 紀平氏からはJavaScriptの速度に関する開発経験も発表が行われた。evalクロージャを頻繁に生成している場合には、JITが逆に動作を重くすることがあるが、この問題はツールレベルで検出しやすいため対処が容易だという。

 どちらかというと、JavaScript最大の遅さ原因はGC(ガベージコレクション)にあると指摘されていた。GC対策に万能薬は存在せず、よく知られた手法を確実に適用していくことで改善できるという。

 また、発展形として、把握しにくい実機におけるメモリ使用量の確認方法なども紹介があった。開発経験上、1回のJavaScript処理におけるメモリ使用量は100Mbytes以内になるようにすると問題が発生しにくいという

Yahoo! JAPANのスマホ向けHTML5対応とは

 現時点におけるYahoo! JAPANのサービスのHTML5対応は、スマートフォン/スマートデバイスが先行している。その理由としては、PCに比べてWebブラウザが限定されていることからSLA(Service Level Agreement)が維持しやすいことや、下位互換性を考慮する必要性があまりないこと、HTML5の機能を活用できる要件が整っていることなどが挙げられた。もちろん、スマートフォンの爆発的な普及もそれを後押ししている。

 講演では、特に「Yahoo! JAPANトップ」「Yahoo! JAPANサービス」における2つのHTML5対応についての紹介があった。まず、Yahoo! JAPANトップにおいては、下記のポイントに留意してUIを設計しているという。

  • 親しまれた既知のデザインを再利用することで直感的に使えるようにする
  • デバイスの特性を知る
    • 画面サイズを考慮
  • ボタン文言を統一
  • タッチジェスチャーを前提にUI配置を考える
  • HTML5の主要なテクノロジについて理解しておく
    • できること、できないことを把握

 現在、Yahoo! JAPANトップで利用されている主要なHTML5の機能とそのポイントとしては、次のようなものが挙げられた。共通機能などは「YUI App Framework」として共有・集約しているとのことだ。

  • localStorage(ローカルストレージ)
    • 各種履歴や設定の保持に使用
  • 構造化データの保持にはJSONを使う
  • バイナリデータはBase64
  • タッチイベント
  • History API
    • 「戻る」ボタンを利用できる
  • サポートしないプラットフォーム向けにはYUI App Frameworkで対応
  • GeoLocation API
    • 約24時間ごとに位置情報取得の警告を行う
    • APIで緯度経度から住所に変換
  • CSS3
    • CSS Transformで複雑な描画処理をスムーズに行える
    • CSS Gradientで高解像度ディスプレイでも滑らかな表示が可能

 Yahoo! JAPANサービスでは、多数のサービスに対する開発を支援するため、共通の開発支援システムやテンプレートシステムが用意されており、その中でHTML5対応をはじめとするスマートフォン向けのデザインや開発のサポートを進めているという。ここでは、HTML5のマークアップやWeb Storage、CSS3、GeoLocation API、Canvas、オフライン機能などが活用されているとのこと。

 スマートフォン向けの開発では、特に全体として品質を保ちつつ、最新の機能への対応を進めていく必要がある。そこで、スマートフォンの特性を考慮したUI規定の明確化や、実装のためのガイドラインの明確化を行い、全体の品質の確保に務めている。

 また実装に対しては、スニペットなどのツールによるサポートや、実装パーツの共有社内ポータルによるデバイス情報の共有などによって、開発の効率化を進めている。それに加えて、HTML5をはじめとする新しい技術を使った試作と研究を積極的に行っているとのこと。

Safariで意図せずGoogleのCookieがセットされる問題、MSも斜め上から非難

SafariはサードパーティCookie(閲覧しているWebページのドメインとは異なるドメインが発行するCookie)をデフォルトでブロックするようになっているのだが、Wall Street Journalが「GoogleはSafariが本来ブロックするはずのサードパーティCookieを特殊なコードを使って有効にしている」との旨を報じている。

WSJの記事では技術的な内容についてはあまり触れられていないが、EngadgetWSJのブログ記事によると、Safariは通常はサードパーティCookieをブロックするが、フォームを用いてユーザーが情報を送信した場合は例外としてサードパーティCookieを受け入れる仕様になっているそうだ。問題のコードはIFRAMEとJavaScriptを使って不可視のフォームを自動的に送信するというもので、これによりSafariはその後GoogleによるサードパーティCookieを受け入れてしまうようになるという。

Googleはトラッキングのためにこれを用いていたわけではなく、広告にGoogle+の「+1」ボタンを埋め込むためだけに使っていたと主張している。送受信されるCookieは「Googleのサーバーと一時的に通信を行うためだけに利用し、送信される情報は匿名のものでトラッキングに利用するようなものではない」と述べている。しかし、これによる副作用でその後GoogleのサードパーティCookieが受け入れられるようになり、その結果Safariのユーザーはトラッキング用のCookieも受け入れてしまうという。

技術的な内容について詳しくはmala氏がまとめているが、フォームの送信でサードパーティCookieがブロックされない件はGoogleのエンジニアによってバグとされ、WebKitレベルでは修正されているという。

この問題を受け、20日にMicrosoftもIEBlogで「GoogleはIEでもプライバシ設定を迂回している」と非難している。IE6以降はデフォルトでサードパーティCookieをブロックするようになっており、「P3P」という規格に準じた形で設定されたサードパーティCookieのみ受け入れるようになっているそうなのだが、「機械可読でないP3Pポリシーが設定されたサードパーティCookieは受け入れる」という仕様になっていたため、簡単に迂回できてしまうそうだ。Engadgetが詳しく解説しているが、このP3P規格はすでに時代遅れとなりほとんど使われていないとのこと。ちなみに、Facebookなどもこの迂回手段を使っているそうだ。

Mmbiが「スキマ時間」争奪戦に参戦

 会社の休み時間や、外出中のちょっと空いた時間など、「スキマ時間」の奪い合いが激しくなった。長らく、喫茶店やファーストフード店で暇つぶしするのが相場だったが、携帯電話の普及とともにスキマ時間を狙ったビジネスが広がった。

 携帯電話向けソーシャル・ゲームで成長したディー・エヌ・エーやグリーの時価総額は、フジテレビジョンや日本テレビ放送網を上回る。携帯電話で電子コミックを読む人も増え、日本は今や世界有数の電子書籍市場となった。

 2012年4月1日、NTTドコモやフジテレビなどが出資するmmbiが、スマートフォン向けの放送サービス「NOTTV(ノッティービー)」を始める。対応するスマホはドコモが発売する。月額420円を支払えば、バラエティーやニュース、ドラマなどの3チャンネルを視聴できる。番組編成を担当する小牧次郎常務は、「長時間見続けてもいいし、短時間でも楽しめる内容にする」と、スキマ時間への対応を明言する。

 スマホをはじめとする携帯端末向けの映像サービスには、既にNTTぷららの「ひかりTVモバイル」や、ドコモとエイベックス・エンタテイメントの合弁会社が提供する「BeeTV」などがある。

 スキマ時間に入り込む余地は少なくなってきている。それでもmmbiの二木治成社長は、「開始から3年後に500万人の契約者を獲得し、単年度黒字を達成したい」と強気だ。

 日本銀行が2011年12月に実施した生活意識調査によると、「ゆとりがなくなってきた」と回答する人が、半年前より1.2ポイント増えて51.6%に達した。経済的な理由が主な要因と思われるが、もしかしたらスマホの普及でスキマ時間が埋まり、余裕を感じにくくなっているのかもしれない。

タブレット端末使う主婦向けコンシェルジュ・サービス、イオン、NTT西、シャープが3月開始

 イオン、NTT西日本グループ、シャープは2012年2月22日、ネットショッピングや家族のスケジュール管理といった主婦の利用を想定した各種アプリケーションを専用のタブレット端末経由で提供するサービス「A touch Ru*Run(エータッチル*ルン)」を3月12日に開始すると発表した(写真)。イオンの縣 厚伸執行役ITグループ責任者は「家庭のリビングに、主婦の要望に応えるコンシェルジュの受付カウンターを設けるという発想で作り上げた」と語る。

 A touch Ru*Runの特徴は、主婦が日常的に使いやすいアプリケーションをタブレット端末にあらかじめ組み込み、すぐに利用できるようにしていること。例えばイオンのネットスーパーサービスを利用するアプリのほか、NTT西日本のグループ会社であるNTTメディアサプライが提供するスケジュール管理、家族間の伝言ツール、アルバムなどを統合した「くらしフルサービス」を搭載した。利用者が操作に戸惑った場合を想定し、遠隔操作で代行処理するサポートサービスもNTTメディアサプライがオプションとして用意する。

 また、タブレット端末の操作方法やサービス内容には主婦の声を取り入れた。マーティング会社であるハーストーリィプラス(広島市)のモニター会員30人に、2011年8月から2カ月余り試用してもらい、使い勝手についてのアンケートや座談会を実施。寄せられた意見を踏まえ、操作性はもちろん、画面を暖色系にしたり、かわいらしさを感じられるようにしたりといった感性面での改良も施したという。

 A touch Ru*Runを利用するには、専用タブレット端末の購入と、くらしフルサービスの契約が前提となる。端末の価格は液晶ディスプレイの大きさが7インチのタイプで3万9800円、10.1インチのタイプで4万9800円。くらしフルサービスの利用料金は、月額315円または年額3465円。端末は全国各地のイオンの店舗や同社のWebサイト経由で購入できる。

 端末の価格は競合他社の一般的なタブレット端末と比較しても割安とは言えず、サービスが普及するうえでネックとなる恐れもある。こうした見方に対し、縣執行役は「ネットスーパーで利用できるポイントを付与することなどによって割安感を打ち出す」と語る。詳細は未定だが、購入時に数千〜1万円程度のポイントを付与することを検討しているという。2013年度中にタブレット端末を30万台普及させることを目指す。

2012年2月22日水曜日

How to root IS01 or SH-10B

check BaseBand version, ( Setting->System->Device Information ), if your baseband is 01.00.07 or 01.00.09, follow the below instructions, if not, use tools from marijuana(see below).
1. Download z4root from google market, install it and run it. Your IS01 may go panic, if so, use the reset button on the back or remove the battery for a while, then restart your phone.
2. download and install Superuser.
3. Download is01root tool from mobilehackerz, (to save you from reading japanese, you may just click link here: is01root_002.apk), and install it.
4. run is01root, click the first option (Step1:rootxxxxx... xxx stands for Japanese) on the software. It will pop up a warning box, click the left button to agree to go on. then wait for a minute, another box with "suxxxx/sqlite_journals/is01root/xxxxx" come up, again, click the left button. Then, an error message pop up, just click the "Force close" button to close the software.
5. run is01root again, click "Step2:su xxxxx", then the left button, then ok button, the is01root quit again.
6. reboot you is01.
7. run is01root for the third time, click "Step3ath xxx", then, superuser will pop up, asking you for permission, allow it, is01root will quit again.
You phone is rooted! Every time you want to use root permission, you will need to run is01root first, and click the "step3ath xx" button once!

The other way, root IS01 with tools from marijuana
with this method, you don't need to run the is01rooter every time you want to get root permission:
Download root tools for your baseband version from:
marijuana .ddo.jp/is01/index.php?moddir=downloads
and follow the japanese instruction come with the tool. (Read this English introduce by a Japanese to get more details.)

How to write system partition
If you want to make any change to system partition, you need to mount the partition writable. It can be done easily by running /sqlite_journals/is01root/sysremount_atmyownrisk.sh script if you root your IS01 with is01root, or /sqlite_journals/root/tools/sysremount.sh if you use tools from marijuana to root you phone. After that, there will be a /system.rw folder, which is a writable /system partition. NOTE: making change to /system may damage your phone, so be carefully.

Android 端末 IS01 のカーネルを入れ替えてみた ? さよならデッカード LSM

http://www.gcd.org/blog/2010/12/682/#more-682

先週末 IS01 で root 権限が必要なアプリが使えるようになったばかりなのに、 そのわずか 4日後、スマートフォン@2ch掲示板に以下の書き込みがあり、 カーネル空間への侵入口が明らかにされてしまった。 一番乗りを果たした goroh_kun さんに敬意を表しつつも、 IS01 のプロテクトがこの程度だったことが残念でもある。 「root を取られても大丈夫な作りになっている」 と開発者が豪語し、 しかも IS01 の発売から 5ヶ月間も破られなかったのだから、 さぞかし鉄壁の守りなのだろうと思っていたのに、 こんな分かりやすい穴があったとわ... (負け惜しみ ^^;)。

【ROM焼き】au IS01 root2 〜わたくし達も未来へ〜

...

317 :goroh_kun:2010/12/01(水) 03:14:21 ID:LGLTLBmZ

自動起動仕込むところを大体見つけました。 
どなたか協力お願いします。

/data/の直下にlocal.propを置く
ここで、内容をoverrideできます。
サービス起動時のおダイナミックライブラリがある
サービスプログラムを探す。

getpropしてみると、

rild.libpathが/system/lib/libril-qc-1.soといかにも起動時に使っていそう。 
rildaemonから使われているプラグインと思われます。

そこで、
local.propの中身を
rild.libpath=/data/lib/libril-wrapper.so
rild.wrapper.cmd=/data/rootkit.boot.sh
rild.libpath2=/system/lib/libril-qc-1.so

で、このプラグインを/data配下から読み出されるようにして、
libril-wrapper.soにて、ダイナミックロード時に
自動実行したいプログラムを指定できるようにします。
で、自動実行したいプログラムをlibril-wrapper.soで実行後
本来のrild用のプラグインをロードして、rildに引き渡すようにします。

これでいけるのではないかと思っているのですが、やるよって方は
いらっしゃいますか?

rild.libpath プロパティは、 RIL (Radio Interface Layer) デーモン rild が参照している。 rild は rild.libpath の値をダイナミックライブラリのパス名として dlopen(3) に渡し、 dlsym(3) でライブラリ内の関数 RIL_Init 呼び出す。 つまり、 rild が起動される前に rild.libpath の値を書き換えておけば、 rild に任意のプログラムを起動時に実行させることが可能になる。

したがって守る側 (つまり開発者の立場) から考えると、 (1) rild.libpath が書き換えられないようにするか (2) 任意のプログラムの実行が脅威にならないよう、 rild 起動前に防御を固めてしまえばよい。

プロパティは、 以下の 4 つのファイルで設定できる。 どれか一つでも改変可能であれば、 (1) の方法は使えない。

  • /default.prop
  • /system/build.prop
  • /system/default.prop
  • /data/local.prop

IS01 の場合、 (たとえ root が奪取されても) /system ディレクトリ下は改変できないようになっている。 また、 /default.prop は initramfs 内のファイルなので、 改変しても再起動すれば揮発してしまう。 だから上記 4ファイルのうち /data/local.prop 以外は改変不可能。

Android では /system ディレクトリ下は read only でも構わないが、 /data ディレクトリ下は Android 動作中に書き換えることが前提となっている。 もちろん /data/local.prop だけは書き換え不可能にするとか、 あるいは再起動時に自動的に /data/local.prop を書き戻す、 という方法も考えられなくもないが、 そもそも論で言えば /data/local.prop は、 システムのプロパティをオーバーライドするための設定ファイルであって、 その本来の趣旨からいえば書き換え不可能にすることは望ましくない。

したがって守るなら (2) の方法が自然。 というか、 /data/local.prop で rild.libpath の値を変更されても、 rild はユーザ空間で動くデーモンなのだから、 本来は 「任意のプログラムの実行」 が可能でも脅威にはならないはず。

ところが IS01 の開発チームは致命的なミスを犯した。

IS01 の /init.rc から引用:

	...    on boot  # basic network init      ifup lo      hostname localhost      domainname localdomain  	...    	setprop net.pppbtdg.servIp 1.2.3.4  	setprop net.pppbtdg.clientIp 1.2.3.5  	setprop net.pppbtdg.portspeed 115200  	setprop net.bt.data.option 0 # 0 - eth0 ; 1 - gprs no dial required; 2 - gprs dial required    ## SHARP_EXTEND MotionEmojiFactory 2009.10.14 Add-Start         setprop ro.config.libmotionemoji libmotionemoji_impl.so  ## SHARP_EXTEND MotionEmojiFactory 2009.10.14 Add-End        class_start default    # 2009.10.06 sbc H.Nozaki Add  	setprop wifi.interface wlan0    # SC Shirakawa 2010/03/10 <- prohibit insmod after start-up   insmod /system/lib/modules/unifi_sdio.ko  setprop wlan.driver.status loaded  # SC Shirakawa 2010/03/10 -> prohibit insmod after start-up   write /proc/sys/kernel/modules_disabled 1    ## Daemon processes to be run by init.  ##  service console /system/bin/sh      console  	...    service ril-daemon /system/bin/rild      socket rild stream 660 root radio      socket rild-debug stream 660 radio system      user root      group radio cache inet misc  	...  

「on boot」 から始まる一連のブートスクリプトはデーモン類の起動前に実行される。 だから普通に init.rc を記述すれば 防御を完璧にした後に、 デーモン類を起動することになる。 そうしていれば、 デーモン類に多少のセキュリティホールがあっても問題にはならなかっただろう。

ところが、 何を血迷ったか sbc H.Nozaki さんは 「class_start default」 の後にスクリプト 「setprop wifi.interface wlan0」 を書いてしまった (2009年10月6日)。

「class_start default」 はデーモン類の起動命令である。 この行の後にスクリプトを書いても構わないが、 そのスクリプトとデーモンの処理と、 どちらが先に実行されるかはタイミング次第ということになる。 デーモンを起動する前に実行すべきブートスクリプトは 「class_start default」 の行より前に書かなければならない。

sbc H.Nozaki さんが書き加えたのは、 wifi.interface プロパティの値を 「wlan0」 に設定する処理で、 普通に考えればデーモン類の起動 「class_start default」 より前に書く方が素直だが、 wifi.interface プロパティを参照するタイミングはずっと後なので、 どこに書こうが大差ない。 なので特に問題視もされず、 そのままになってしまったのだろう。

しかしながら、 sbc H.Nozaki さんがこの変更を行なった結果、 2009年10月14日時点での init.rc は以下のようになってしまう:

	...    ## SHARP_EXTEND MotionEmojiFactory 2009.10.14 Add-Start         setprop ro.config.libmotionemoji libmotionemoji_impl.so  ## SHARP_EXTEND MotionEmojiFactory 2009.10.14 Add-End        class_start default    # 2009.10.06 sbc H.Nozaki Add  	setprop wifi.interface wlan0    ## Daemon processes to be run by init.  ##  service console /system/bin/sh      console  	...  

「## Daemon processes to be run by init.」 というコメント行があることも相俟って、 その直前までがブートスクリプトであるかのように見えてしまう。 実際は 「class_start default」 の前に書かなければならないのに。

その 5ヶ月後、 IS01 発表 (3月30日) の直前、 SC Shirakawa さんが IS01 のプロテクトの最大の要 「write /proc/sys/kernel/modules_disabled 1」 を、 「## Daemon processes to be run by init.」 の直前に書いてしまったことを誰が責められるだろうか。 まあ、 ちょっと見渡せばすぐ上に 「class_start default」 と書いてあるのが見えただろうから、 この行の意味を少しでも考えていたらこのようなミスは避けられたかも。

「write /proc/sys/kernel/modules_disabled 1」 を実行することにより、 それ以降カーネルモジュールをロード (insmod) することが禁止される。 すなわちカーネル空間へ侵入することが格段に難しくなる。 OS に脆弱性が無ければ (そんなことはまず無いが) カーネル空間への侵入は不可能と言ってもいい。

ところが既にデーモン類の起動命令 「class_start default」 は発行してしまった。 後は野となれ山となれ、 一斉に走り出したデーモン類において任意のコードが実行可能であれば、 insmod が禁止される前に、 そのデーモンに任意のモジュールを insmod させてカーネル空間への侵入が果たせてしまう。

dmesg で見るとこんな感じ:

	...  <6>[    0.008933] Memory: 232MB = 232MB total  <5>[    0.008960] Memory: 157824KB available (4828K code, 1499K data, 160K init)  <6>[    0.009273] Calibrating delay loop... 511.18 BogoMIPS (lpj=2555904)  <6>[    0.240166] Security Framework initialized  <6>[    0.240193] DECKARD LSM module initialized  	...  <6>[    8.061633] init: command 'setprop' r=0  <6>[    8.061666] init: command 'setprop' r=0  <6>[    8.061699] init: command 'setprop' r=0  <6>[    8.061739] init: command 'setprop' r=0  <6>[    8.061759] init: command 'setprop' r=0  <3>[    8.061773] init: service 'console' requires console  <5>[    8.086566] init: starting 'logd'  <5>[    8.088086] init: starting 'dgstmgrd'  <5>[    8.105699] init: starting 'servicemanager'  <5>[    8.108533] init: starting 'vold'  <6>[    8.109439] init: Created socket '/dev/socket/vold' with mode '660', user '0', group '1009'  <5>[    8.111886] init: starting 'usbmgrd'  <6>[    8.112773] init: Created socket '/dev/socket/usbmgrd' with mode '660', user '0', group '1009'  <5>[    8.163386] init: starting 'debuggerd'  <5>[    8.167306] init: starting 'fotad'  <5>[    8.170679] init: starting 'ril-daemon'  <6>[    8.171473] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'  <6>[    8.171753] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'  	...  <6>[   13.184319] init: command 'class_start' r=0  <6>[   13.184353] init: command 'setprop' r=0  	...  <6>[   13.653133] init: command 'insmod' r=0  <6>[   13.653179] init: command 'setprop' r=0  <6>[   13.653786] init: command 'write' r=0  

8.061759秒の 「init: command 'setprop' r=0」 が 「class_start default」 直前の
「setprop ro.config.libmotionemoji libmotionemoji_impl.so」 を実行したときの出力。 その後、 デーモン類を次々と起動し、 「class_start default」 の実行が完了するのは 5秒以上たった 13.184319秒時点。 「write /proc/sys/kernel/modules_disabled 1」 を実行してようやく insmod が禁止できたのは、 さらに 0.5秒もたってからで、 その間に rild はカーネル空間への侵入口を提供してくれた。

goroh_kun さんの発表からわずか 2時間後の 5:28 (なんちゅー時間だ)、 goroh_kun さん自身によって、 mtd0 (カーネルイメージ), mtd2 (リカバリイメージ), mtd5 (/system) を変更可能にするカーネルモジュール msm_nand_ex.ko が発表され、 これを rild に insmod させることによってカーネルイメージ等の改変が可能になった。

なので早速 (といっても平日は時間が取れないので週末になってから) カーネルを再構築してみる。 SHARP が公開している IS01 のカーネルを menuconfig してビルドする:

% make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig  	...  % make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-  	...    LD      vmlinux    SYSMAP  System.map    SYSMAP  .tmp_System.map    OBJCOPY arch/arm/boot/Image    Kernel: arch/arm/boot/Image is ready  	...  % cp -a arch/arm/boot/Image ~/tmp/IS01/kernel.bin  

当然のことながら、 にっくき (Android とりわけ Nexus の敵) デッカードを消す。 勢い余って CONFIG_SECURITY=n にした。 また、kernel/drivers/mtd/devices/msm_nand.c に、 「#define CONFIG_ANDROID_ENGINEERING 1」 を追加して MTD protect を丸ごと消してしまう (12/9追記: menuconfig でも CONFIG_ANDROID_ENGINEERING を設定可能なので、 msm_nand.c を書き換えるよりは menuconfig にて設定した方がよい)。 これで IS01 特有のプロテクトは全て無くなる。 ついでに CONFIG_SWAP=y を設定した。

--- config	2010-11-24 07:40:41.051499180 +0900  +++ .config	2010-12-04 10:30:27.037625342 +0900  @@ -1,7 +1,7 @@   #   # Automatically generated make config: don't edit   # Linux kernel version: 2.6.29  -# Mon Sep 20 04:09:00 2010  +# Sat Dec  4 10:30:27 2010   #   CONFIG_ARM=y   CONFIG_SYS_SUPPORTS_APM_EMULATION=y  @@ -36,7 +36,7 @@   CONFIG_INIT_ENV_ARG_LIMIT=32   CONFIG_LOCALVERSION="$(KERNEL_LOCAL_VERSION)-perf"   # CONFIG_LOCALVERSION_AUTO is not set  -# CONFIG_SWAP is not set  +CONFIG_SWAP=y   CONFIG_SYSVIPC=y   CONFIG_SYSVIPC_SYSCTL=y   # CONFIG_POSIX_MQUEUE is not set  @@ -430,7 +430,6 @@   CONFIG_DEFAULT_TCP_CONG="cubic"   # CONFIG_TCP_MD5SIG is not set   # CONFIG_IPV6 is not set  -# CONFIG_NETLABEL is not set   CONFIG_ANDROID_PARANOID_NETWORK=y   # CONFIG_NETWORK_SECMARK is not set   CONFIG_NETFILTER=y  @@ -492,7 +491,6 @@   # CONFIG_IP_NF_TARGET_ULOG is not set   # CONFIG_IP_NF_MANGLE is not set   # CONFIG_IP_NF_RAW is not set  -# CONFIG_IP_NF_SECURITY is not set   # CONFIG_IP_NF_ARPTABLES is not set   # CONFIG_IP_DCCP is not set   # CONFIG_IP_SCTP is not set  @@ -1661,14 +1659,9 @@   # Security options   #   # CONFIG_KEYS is not set  -CONFIG_SECURITY=y  +# CONFIG_SECURITY is not set   # CONFIG_SECURITYFS is not set  -# CONFIG_SECURITY_NETWORK is not set  -CONFIG_SECURITY_PATH=y   # CONFIG_SECURITY_FILE_CAPABILITIES is not set  -CONFIG_SECURITY_DECKARD=y  -CONFIG_SECURITY_DECKARD_SYSTEM_DEV_PATH="/dev/block/mtdblock5"  -CONFIG_SECURITY_DECKARD_CHROOT_PATH=""   CONFIG_CRYPTO=y      #  

カーネルの次は initramfs の改変。

/init.rc における防御の要をコメントアウト:

--- init.rc.org	1970-01-01 09:00:00.000000000 +0900  +++ init.rc	2010-12-04 11:24:53.943962272 +0900  @@ -361,7 +361,7 @@   insmod /system/lib/modules/unifi_sdio.ko   setprop wlan.driver.status loaded   # SC Shirakawa 2010/03/10 -> prohibit insmod after start-up   -write /proc/sys/kernel/modules_disabled 1  +#write /proc/sys/kernel/modules_disabled 1      ## Daemon processes to be run by init.   ##  

ついでに /default.prop も書き換えてより使いやすく ;-)

--- default.prop.org	1970-01-01 09:00:00.000000000 +0900  +++ default.prop	2010-12-04 11:24:59.013753953 +0900  @@ -3,5 +3,5 @@   #   ro.secure=1   ro.allow.mock.location=0  -ro.debuggable=0  -persist.service.adb.enable=0  +ro.debuggable=1  +persist.service.adb.enable=1  

ビルドしたカーネル kernel.bin と、 initramfs を cpio で固めた ramdisk.bin から、 mkbootimg コマンドを使ってブートイメージ boot.img を作る:

senri:/home/sengoku % fg %su  # find . | cpio -o -H newc > ~sengoku/tmp/IS01/ramdisk.bin  591 blocks  # suspend  senri:/home/sengoku % cd ~/tmp/IS01/  senri:/home/sengoku/tmp/IS01 % ls -l kernel.bin ramdisk.bin  -rwxr-xr-x 1 sengoku wheel 5312864 Dec  4 10:40 kernel.bin  -rw-r--r-- 1 root    root   302592 Dec  4 10:44 ramdisk.bin  senri:/home/sengoku/tmp/IS01 % mkbootimg --kernel kernel.bin --ramdisk ramdisk.bin --cmdline "console=ttyMSM2,115200n8 androidboot.hardware=qcom" --base 0x20000000 -o boot.img  

ただし IS01 のブートイメージは、 Android Donut 標準の mkbootimg が作るブートイメージとは若干差異があった。 IS01 のブートイメージでは、 ramdisk_addr が 0x03000000 ほど後ろへずれていて、 かつ padding が 2048 バイト区切りではなく 4096 バイト区切りになっていた。 なので、 以下のようなパッチをあてる:

--- system/core/mkbootimg/mkbootimg.c.org	2010-11-27 09:46:55.000000000 +0900  +++ system/core/mkbootimg/mkbootimg.c	2010-12-04 10:13:46.381056328 +0900  @@ -71,7 +71,7 @@           -static unsigned char padding[2048] = { 0, };  +static unsigned char padding[4096] = { 0, };      int write_padding(int fd, unsigned pagesize, unsigned itemsize)   {  @@ -143,7 +143,7 @@           } else if(!strcmp(arg, "--base")) {               unsigned base = strtoul(val, 0, 16);               hdr.kernel_addr =  base + 0x00008000;  -            hdr.ramdisk_addr = base + 0x01000000;  +            hdr.ramdisk_addr = base + 0x04000000;               hdr.second_addr =  base + 0x00F00000;               hdr.tags_addr =    base + 0x00000100;           } else if(!strcmp(arg, "--board")) {  @@ -229,10 +229,10 @@       }          if(write(fd, &hdr, sizeof(hdr)) != sizeof(hdr)) goto fail;  -    if(write_padding(fd, pagesize, sizeof(hdr))) goto fail;  +    if(write_padding(fd, pagesize*2, sizeof(hdr))) goto fail;          if(write(fd, kernel_data, hdr.kernel_size) != hdr.kernel_size) goto fail;  -    if(write_padding(fd, pagesize, hdr.kernel_size)) goto fail;  +    if(write_padding(fd, pagesize*2, hdr.kernel_size)) goto fail;          if(write(fd, ramdisk_data, hdr.ramdisk_size) != hdr.ramdisk_size) goto fail;       if(write_padding(fd, pagesize, hdr.ramdisk_size)) goto fail;  

Android Donut 標準と異なる点はまだあって、 IS01 のブートイメージは UBI (Unsorted Block Images) 上にある。 なので ubinize コマンド (mtd-utils に含まれる) を使って 「UBI 化」 してからフラッシュに書込まねばならない。

senri:/home/sengoku/tmp/IS01 % ls -l boot.img  -rw-r--r-- 1 sengoku user 5623808 Dec  4 10:48 boot.img  senri:/home/sengoku/tmp/IS01 % ubinize -o ubi.img -p 128KiB -m 2048 -O 256 ubi.cfg  

IS01 のブートイメージでは、 VID header offset として 256 を指定する必要があるので、 ubinize コマンドに 「-O 256」 オプションを指定している。 また、 ubinize は設定ファイルを引数に与える必要があるので、 以下のようなファイル ubi.cfg を作って ubinize を実行する。

[boot]  mode=ubi  image=boot.img  vol_id=0  vol_size=200MiB  vol_type=dynamic  vol_name=boot  vol_flags=autoresize  

こうしてできた IS01 ブートイメージ ubi.img を、 adb push して IS01 に送り込み、 IS01 上で flash_image コマンドを使ってフラッシュへ書込む:

senri:/home/sengoku/tmp/IS01 % ls -l ubi.img  -rw-r--r-- 1 sengoku user 6029312 Dec  4 10:48 ubi.img  senri:/home/sengoku/tmp/IS01 % adb push ubi.img /sdcard/tmp/  1937 KB/s (6029312 bytes in 3.038s)  senri:/home/sengoku/tmp/IS01 % adb shell  $ su  # cat /proc/mtd  dev:    size   erasesize  name  mtd0: 00b00000 00020000 "boot"  mtd1: 00500000 00020000 "cache"  mtd2: 00b00000 00020000 "recovery"  mtd3: 00180000 00020000 "splash"  mtd4: 00b40000 00020000 "ipl"  mtd5: 10000000 00020000 "system"  mtd6: 00300000 00020000 "log"  mtd7: 06420000 00020000 "userdata"  mtd8: 00b00000 00020000 "boot_wr"  mtd9: 00b00000 00020000 "recovery_wr"  mtd10: 10000000 00020000 "system_rw"  # flash_image recovery_wr /sdcard/tmp/ubi.img  # exit  senri:/home/sengoku/tmp/IS01 % adb reboot recovery  

すでに goroh_kun さんのカーネルモジュール msm_nand_ex.ko を insmod してあるので、 書込み可能な boot_wr および recovery_wr パーティションがある。 ブートイメージは boot_wr と recovery_wr どちらにも書込むことができるが、 まずは実験として recovery_wr へ書込んだ。 boot_wr (と system_rw) さえ変更しなければ、 失敗しても文鎮化は避けられる。 つまり何か問題が起きても、 リセットスイッチを押せば boot パーティションから起動する。

adb reboot recovery すれば recovery パーティションから起動する。

12/9 追記: IS01 を工場出荷状態に初期化する操作を行うと、 recovery パーティションから起動して初期化処理を行うらしい (未確認)。 つまり recovery パーティションに書き込んだイメージが期待されている処理 (つまり初期化処理) を行わずに、 通常のブートイメージの処理 (つまり IS01 の通常の起動) を行うと、 再び初期化処理に入ろうとして recovery パーティションから再起動させて無限ループに陥る恐れがある (憶測)。
もちろん、 「初期化」 しても書き換えたブートイメージは元には戻らないわけで、 いったん boot / recovery を書き換えたら、 決して 「初期化処理」 は行うべきではないし、 「初期化処理」 以外にも recovery パーティションを使用する処理があると思われる (おそらく、ケータイアップデートなど) ので、 実験目的での recovery 書き換えの後は、 なるべく速やかに元のイメージ (あるいは同等の処理を行うイメージ) に書き戻しておくほうが無難。

前述したように /default.prop を書き換えて 「ro.debuggable=1」 にしたので、 使い勝手が向上している ;-) 例えば、 以下のように 「adb root」 が可能になっている。

dmesg すると、 以前は 0.240193秒あたりに出ていた 「DECKARD LSM module initialized」 という出力が消えているのが分かる。 さよならデッカード!

senri:/home/sengoku/tmp/IS01 % adb root  restarting adbd as root  senri:/home/sengoku/tmp/IS01 % adb shell  # dmesg  <5>[    0.000000] Linux version 2.6.29-perf (sengoku@senri.gcd.org) (gcc version 4.3.5 (GCC) ) #3 PREEMPT Sat Dec 4 10:40:33 JST 2010  <4>[    0.000000] CPU: ARMv7 Processor [510f00f2] revision 2 (ARMv7), cr=10c5387f  <4>[    0.000000] CPU: VIPT nonaliasing data cache, VIVT ASID tagged instruction cache  <4>[    0.000000] Machine: SHARP DECKARD  	...  <6>[    0.008700] Memory: 232MB = 232MB total  <5>[    0.008720] Memory: 157952KB available (4792K code, 1480K data, 160K init)  <6>[    0.009040] Calibrating delay loop... 511.18 BogoMIPS (lpj=2555904)  <4>[    0.240286] Mount-cache hash table entries: 512  <6>[    0.240753] CPU: Testing write buffer coherency: ok  <6>[    0.242906] net_namespace: 444 bytes  <6>[    0.243606] NET: Registered protocol family 16  <6>[    0.245393] socinfo_init: v2, id=30, ver=2.0, raw_id=640, raw_ver=2  <3>[    0.245406] qsd8x50_cfg_smc91x: invalid machine type  <6>[    0.245433] Max ACPU freq from efuse data is 998400 KHz  <6>[    0.246006] ACPU running at 768000 KHz  <6>[    0.246020] 5 scaling frequencies supported.  <4>[    0.267433] bio: create slab <bio-0> at 0  <5>[    0.268873] SCSI subsystem initialized  <6>[    0.269166] msm_i2c_probe  <6>[    0.269206] msm_i2c_probe: clk_ctl 317, 369230 Hz  <6>[    0.273240] Bluetooth: Core ver 2.15  <6>[    0.273493] NET: Registered protocol family 31  <6>[    0.273506] Bluetooth: HCI device and connection manager initialized  <6>[    0.273526] Bluetooth: HCI socket layer initialized  <6>[    0.275353] NET: Registered protocol family 2  <6>[    0.275533] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)  <6>[    0.275873] TCP established hash table entries: 8192 (order: 4, 65536 bytes)  <6>[    0.276046] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)  <6>[    0.276126] TCP: Hash tables configured (established 8192 bind 8192)  <6>[    0.276140] TCP reno registered  <6>[    0.276320] NET: Registered protocol family 1  <6>[    0.276713] checking if image is initramfs... it is  <6>[    0.278820] Freeing initrd memory: 292K  	...  # dd if=/dev/zero of=/data/swapfile bs=1048576 count=64  64+0 records in  64+0 records out  67108864 bytes transferred in 11.703 secs (5734330 bytes/sec)  # mkswap /data/swapfile  Setting up swapspace version 1, size = 67104768 bytes  # swapon /data/swapfile  # free  free                total         used         free       shared      buffers    Mem:       158576       155480         3096            0         1184   Swap:        64620            0        64620  Total:       223196       155480        67716  #   

ついでに有効にした SWAP が使えるようになっている。 フラッシュの損耗を考えると、 常用はしないほうが無難?

Root化

注意!root化をした場合、SBの保証を受けられなくなる可能性があります。 実際にSBで受け取ってもらえてもHTC側で改造が認められて修理を受け付けてくれなかったケースが数度報告されてます。 また、root化に失敗した場合、あなたのDesire HDが壊れて使えなくなる可能性があります。この記事の内容には誤りが含まれている可能性があります。root化は 自己責任 で行ってください。

2.37.762.2の時点でS-OFF且つ、rootedであることが前提です。
Root化
1-1.適当な場所にtacoroot.binを配置する。(ここではC:\に置く)
1-2.コマンドプロンプトで"cd C:\"と入力し1.で配置したフォルダへ移動。
1-3."adb push tacoroot.bin /data/local/"→"adb shell chmod 777 /data/local/tacoroot.bin"を実行。
これでDesire HDにtacoroot.binの配置は完了。

2-1.tacorootでtemporary root取得 ⇨adb shell /data/local/tacoroot.bin --setupの後、リカバリモードに移行するが
すぐに再起動してadb shell /data/local/tacoroot.bin --rootを実行。その後adb shellを実行しrootが取れていることを示す # が表示されていることを確認。
(この時起動ループ状態になるがadbは普通に繋がるので気にしない。)
2-2./system を rw で再マウント ⇨busybox mount -o remount,rw /system
(busybox: not foundの場合 ⇨mount -o rw,remount /dev/block/mtdblock3 /system)
2-3./system/bin/su のパーミッションを6755へ変更 ⇨chmod 6755 /system/bin/su
2-4.tacorootをundo ⇨/data/local/tacoroot.bin --undo
2-5.勝手に再起動してroot復活!
(起動ループから抜けてroot化していることを確認。)
手順(android2.3)

android2.2の時点でS-OFFしていなければ、root化できません。 一度2.2へダウングレードしてS-OFFしてからアップデートしなおしてください。
Root化
1.ホーム画面から、MENU → 設定 → アプリケーション の、「不明な提供元」にチェックを入れる。
2.GingerBreak-v1.xx.apkをダウンロード。xda-developersから最新のバージョンを入手できる。
3.SDカード内に、GingerBreak-v1.xx.apkをコピーする。
4.ESファイルエクスプローラなど、SDカード内が参照できるアプリを使用し、GingerBreak-v1.xx.apkをインストールする。
5.Android Terminal Emulatorを起動。
6.$マークが出たら、rmdir /data/local/tmpと入力し、エンターを押す。
7.その後、mkdir /data/local/tmpと入力し、エンターを押し、exitと入力し終了させる。
8.GingerBreakを起動し、「Root device」をタップする。終了したら自動的に再起動する。
(エラーが出るかもしれないが、とりあえず再起動してみる。出なかった場合は自動的に再起動する。)
9.再起動後、アプリの中に「Superuser」があれば成功。
手順(android2.2)

Root化
1.Visionary+をネット(マーケットにはないので)よりDL。
2.Visionary+をインストール。
3.Android Terminal Emulator(マーケットより)DL、インストールする。
4.設定→アプリケーション→開発→USBデバッグモードにチェック。
5.Visionary+を起動。
6.Set system r/w after rootにチェック。
7.Temproot Now!をタップ。
8.Temproot適用後、Attempt Permroot Now!をタップ。
9.勝手に再起動されれば、root化完了。
(途中にsuper userとか許可するか聞かれるから許可を押す。)

S-OFF
1.DHD-v0.6-tempfix.zipをネットよりDL、解凍しておいて
2.解凍したら(DHD-dumbフォルダ、DHD-smartフォルダ、RTFM.txt)があるから「DHD-smart」を「DHD」にリネームする。
3.リネームした「DHD」フォルダをSDカードのルートに入れる。
4.Android Terminal Emulator(以下 Terminal)を起動。
5.「su」と入力しエンター。
6.「sh /sdcard/DHD/check」と入力しエンター。
7.ごちゃごちゃ文字が出てきて、OKなら「sh /sdcard/DHD/backup」を入力って出るから入力エンター。
8.また、同じように聞かれるから「sh /sdcard/DHD/hboot」を入力エンター。
9.これでS-OFF完了。

ROM Managerでのバックアップ取り
1.ROM ManagerをマーケットよりDL、インストール。
2.ROM Managerを起動。
3.ClockworkMod Recoveryを導入をタップ。
4.「HTC Desire HD」を選ぶ(一個しかないけど)。
5.現在のROMをバックアップをタップ。
6.再起動されメニューが表示されるのでボリュームボタンで「backup」を選び、電源ボタンで決定。
7.まだあったかもだけど、backupとか選んでけばROMのバックアップが作成される。

Hidden SSID Enable for Android

http://en.androidwiki.com/wiki/Enabling_Hidden_SSID_Hack
Enabling Hidden SSID Hack
To connect to a hidden SSID, the phone must have WifiConfiguration.hiddenSSID set to true. Currently there does not seem to be a way to enable this through the phone UI, but there is a workaround thanks to stewart.wayne.scott. Note that "MySSID" should be the name of the Hidden SSID.
Essentially you need to run the following code on your phone. At the moment there is no premade APK that does this, so it requires creating a program with the Android SDK, compiling it, and running it on the phone.
private WifiManager wifi = (WifiManager)getSystemService(service);
List<WifiConfiguration> config = wifi.getConfiguredNetworks();
for(int i = 0;i<config.size();i++) {
if(config.get(i).SSID.contentEquals("\"MySSID\"")) {
config.get(i).hiddenSSID = true;
wifi.updateNetwork(config.get(i));
wifi.saveConfiguration();
}
}
Note that I have not run the above code myself, and cannot vouch for it. If somebody generates such a program and is willing to share the full APK or code, there would be many grateful individuals.
--Chrismurf 17:33, December 10, 2008 (UTC)

I've coded this up and it doesn't seem to help.
NOTE: This hack works with networks that are already been known.

--mohaine 10/19/2009
There is an app in android market: "HiddenSSID Enabler", which works for me. Before running it a SSID must be stored in the cellphone
--owiec 11/05/2009
The APK for the "HiddenSSID Enabler" application can be downloaded here:http://rapidshare.com/files/359303559/jp.sourceforge.soopy.hidden.ssid.enabler.apk
See also: Related Android Bug
http://code.google.com/p/android/issues/detail?id=1041
Reported by chrism...@gmail.com, Oct 23, 2008
My Production T-Mobile G1 is unable to connect to a Wifi AP with a hidden
SSID and WEP enabled. The phone is initially on a "G" (non-wifi) network.

- Steps to reproduce the problem
* Go to Wi-fi configuration under settings
* "Add a Wi-Fi network"
* Enter SSID and WEP key (as hexadecimal, or ASCII, tried both)
* Save, wait for SSID to show up in list of Wi-Fi Networks
* SSID eventually shows up, says "Remembered, Secured with WEP" and has
high signal strength
* Click on SSID, choose "connect"
* Network will immediately drop to bottom of the list, and say "Not in
range, remembered"

- What you think the correct behavior should be.
* One of two cases:
* device connects to network successfully and lets me browse
* I entered WEP key wrong multiple times, or there's a MAC address issue,
or other error, and a 'Toast' or other alert tells me so.
Comment 1 by defconoii, Oct 24, 2008
i confirm this issue
Comment 2 by siamc...@gmail.com, Oct 25, 2008
i also confirm.
Comment 3 by joseph.o...@gmail.com, Nov 5, 2008
I likewise confirm this issue
Comment 4 by samyra.s...@gmail.com, Nov 10, 2008
I also am seeing this issue.
Comment 5 by chasgowing, Nov 10, 2008
I confirm this issue. This was not an issue when I first got my G1 and wonder if
there's been an update since (and hope it wasn't the MS Vista programmers who
slipped in that change).
Comment 6 by Heta...@gmail.com, Nov 12, 2008
I confirm this Issue
Comment 7 by chasgowing, Nov 14, 2008
I may have a clue. I added Locale form the Android Marketplace and configure
default to NOT have wifi on, but configured the "At Home" location to have wifi on.
The reasoning in my mind was that the T-Mobile signal is pretty bad at home.

In fact, the signal at home is so bad that sometimes Locale can't even tell where I
am. I configured different colored wall papers for different locales, and sometimes
I get home and see the "home-colored" wallpaper and then later see the "default-
colored" wallpaper. I got to thinking about that while trying my wifi at home again
and realized I had the default-colored wallpaper. I turned off Locale ("Locale
disabled" button in Locale itself), and could connect for a bit.

My theory is that Locale may have been turning my wifi off and on in its confusion.

Then again, when I turned off my phone and back on, the wifi icon in the
windowshade / notification bar was gone, but maybe it will reconnect. Anyway,
there's at least a complicating affect coming from Locale for me.
Comment 8 by chrisgrenness, Nov 17, 2008
I confirm problems connecting to my home wifi network with hidden SSID (but no
encryption), and I *think* the problems started after the RC30 upgrade.

BUT, after I altered my access point to have i broadcast SSID I thought problem was
solved, my G1 found the network and connected. This was yesterday. Today it's back to
"not in range, remembered" although I'm literally a few feet away from my access
point and other computers have no problems picking up the signal.
Connecting to the WEP encrypted network at work is no problem, though.
I will try to turn on WEP encryption at home as well to see if that has something to
do with this.
Comment 9 by taoshen1...@gmail.com, Nov 19, 2008
Confirmed, with hidden SSID with WPA2 also. Security is paramount.
Comment 10 by stewart....@gmail.com, Nov 28, 2008
I confirm this issue.

You can't connect to a Wifi network unless you broadcast the SSID. Perhapes there
could be a "Connect" button next to forget and change password on a network in the
"Wi-Fi Settings" page. Doing an auto connect might hurt the battery if it polled that
SSID all the time.
Comment 12 by stewart....@gmail.com, Nov 29, 2008
More Info!

I don't don't have access to the android code but I managed to fix it on my phone!

WifiConfiguration.hiddenSSID need to be set to true for the wifi config of the hidden
network. Everytime I enabled my wifi it found my wifi regardless of broadcasting the
SSID or not. Look up hiddenSSID in the docs and you'll see what this works.

I guess either the "add network" code needs to check this during addition or there
needs to be a checkbox to set and unset it.

There is some code below for a workaround for those that are brave. Use at your own
peril and the SSID that is stored is stored with quote surrounding it for some reason.

private WifiManager wifi = (WifiManager)getSystemService(service);
List<WifiConfiguration> config = wifi.getConfiguredNetworks();
for(int i = 0;i<config.size();i++)
{
if(config.get(i).SSID.contentEquals("\"MySSID\""))
{
config.get(i).hiddenSSID = true;
wifi.updateNetwork(config.get(i));
wifi.saveConfiguration();
}
}

Comment 13 by PanamaPa...@gmail.com, Dec 10, 2008
Hate to sound ignorant because I know you guys are coders..
I have done a little bit of code dabbling myself...
Just wondered how I would use the code posted here by stewart.wayne.scott to solve
this problem. This is my exact problem on my G1 and I would love to fix it.

Please hold the flames...just looking for a little help.

Thanks,
Paul
Comment 14 by chrism...@gmail.com, Dec 10, 2008
There's not a good explanation available at the moment, besides that you need to run
that code. I've put up a wiki page at
http://en.androidwiki.com/wiki/Enabling_Hidden_SSID_Hack with a bit more
information.Maybe further discussion can take place there to keep bugzilla traffic
down? Sorry I can't be much help, good luck Paul!
Comment 15 by Pillsbur...@gmail.com, Dec 24, 2008
I am also having this problem. Every other device in the house works fine. This is
not an issue with the router.

I have tried several methods, all of which failed miserably.

The network access for Tmobile here is very slow, so I was hoping to use the wireless
we have.

I will continue trying and if I find anything, I will report it.
Comment 16 by neandert...@gmail.com, Jan 14, 2009
I have the same problem with WEP wifi networks (with open networks i don't have any
problem) and sometimes i can fix it restarting the router, but a few days later the
problom appears again
Comment 17 by plun...@gmail.com, Jan 24, 2009
For what it's worth, I see this behavior in both the WiFi and the GPS hardware if I
have Locale installed with conditions to control either of these pieces of
hardware. Uninstalling Locale and rebooting fixed the problems I was having.
Comment 18 by plun...@gmail.com, Jan 24, 2009
Sorry for the double-post. By "this behavior in both the WiFi and GPS hardware," I
mean spotty connectivity. With Locale installed, my GPS usually located me
somewhere in Saudi Arabia as opposed to Southern California. I should probably also
add that I have a non-broadcast SSID on WEP and the device connects fine, as long as
Locale is not installed and Power Manager's "monitor" is not turned on.
Comment 19 by jhucke...@gmail.com, Jan 26, 2009
Has any headway been made on this? Fails for me using WPA2 with a hidden SSID, as
well.
Comment 21 by stevenwo...@gmail.com, Feb 4, 2009
I can confirm that Wifi will not detect a hiddent SSID when in range.

Regarding Locale; if Locale cannot determine your location then you may have
unexpected results. I recommend Locale users test Locale's ability to detect your
location prior to depending on it for managing connectivity. A good way to do this
is to define your locations, and set locale to only notify you via a status update
when you enter those areas. Then test it by manually enabling and disabling location
options (Wireless, Wifi, GPS) to determine what the minimum requirements are for
Locale to accurately 'follow' you.

Once you know the minimum location settings to allow Locale to be accurate, use these
settings as your default. This will help to prevent Locale from essentially blinding
itself.
Comment 22 by alsutton.com, Mar 17, 2009
Confirmed on a G1 running TC5-RC9 (i.e. latest UK update).

Turning on the SSID broadcast fixes the problem, turning it off after the G1 has
connected doesn't cause any problems, but once that's done turning off and on Wifi
again fails to connect.
Comment 23 by nemo...@gmail.com, Apr 2, 2009
Further information and speculation.

Out of the box, the G1 could not see my hidden SSID, which is to be expected. I made
it visible, connected with the G1, then hid it again. Everything worked fine for WEEKS.

Then I toggled WiFi "power" using the Tricorder application. Since then the G1 cannot
see my remembered SSID. Other people are reporting issues with 'Locale'. I suspect
that any switching of WiFi connectivity by an application will trigger this problem.
Comment 24 by shahzadd...@gmail.com, Jul 2, 2009
Has anybody actually tried out this hack from chrismurf?

http://en.androidwiki.com/wiki/Enabling_Hidden_SSID_Hack
Comment 25 by alsutton.com, Jul 2, 2009
I've tried that code and it doesn't work on my G1 which has the cupcake firmware.
Comment 26 by tomas.mysik, Jul 15, 2009
Exactly the same for me (G1 CRB43) - standing next to hidden wifi but "Not in range" so
cannot connect.

Please, allow to force to connect or any other way, thanks.

Comment 27 by yglodt, Jul 21, 2009
I tried the "Hidden SSID Enabler" from the Market, but still was unable to connect.

At work there is only a hidden network, I cannot connect as of now.

Is there no other workaround? Or, what about an OS update to fix this, sorry to say,
shameful issue? (which is open and even officially unconfirmed since soon one year)
Comment 28 by m.kre...@gmail.com, Aug 4, 2009
I can confirm this. Android fails to connect to hidden SSID even if I use "Hidden
SSID Enabler". This is really critical issue, please fix it...
Comment 29 by VivARobe...@gmail.com, Aug 6, 2009
I had this problem too where wifi wouldn't connect to saved profile if ssid wasn't
being broadcast - I used "Hidden SSIS Enabler" and it didn't work straight away,
however I left wifi on and connected (manually) to my network, then turned my phone
off and on again and now it's connecting straight away with no problems....
Comment 30 by jbq+legacy@google.com, Aug 21, 2009
(No comment was entered for this change.)
Labels: Component-System
Comment 31 by jbq+legacy@google.com, Aug 27, 2009
(No comment was entered for this change.)
Labels: -Component-System Component-Device
Comment 32 by jbq+legacy@google.com, Sep 18, 2009
(No comment was entered for this change.)
Labels: Subcomponent-Wifi
Comment 33 by y2kbugvi...@gmail.com, Sep 28, 2009
I also have this problem.

Using WEP+Hidden SSID, it does connect eventually and seems to last.

Using WPA2+Hidden SSID, it never connects. Trying Wifi helper and Hidden SSID enabler
did not fix it =(

Mind you, if I was to unhide the SSID, it would work right away...

I'm also impressed... over 1 year and no official acknowledgement of an issued
affecting many people in the exact same way? Strange.


Comment 34 by John...@SKY.com, Oct 2, 2009
I have the same problem, my Hero will only connect if the SSID is visible.
Comment 35 by colib...@gmail.com, Oct 30, 2009
Got solution for my D-Link DIR-655 router, might be useful for others.

By default my AP works in mixed b/g/n 802.11 mode, in this case Hero can't connect to
Hidden SSID, then I changed it it b/g mode only. Bingo! Now Hero loves my WPA2+Hidden
SSID.
Comment 37 by bigntall...@gmail.com, Nov 4, 2009
Relatedly if you use a hidden but open SSID, Android frequently doesn't notice it and
continues using the cell towers instead. I've had to forget and re-add a hidden but
open SSID to have Android try and connect again.
Comment 38 by ian.mor...@gmail.com, Nov 4, 2009
@kynancheng "Hidden SSID Enabler from Android Market does not seem to help - says it
cannot find the SSID"

I found I had most luck with that app if I put the SSID name into straight after
entering the wireless network manually. So, try these steps:

1) remove hidden network from the list of remembered networks
2) Download and install Hidden SSID enabler
3) Re-enter the Wireless network details
4) Connect to the network
5) Enter the network name into Hidden SSID enabler

That seemed to fix my problems, hope it's of help to you too.
Comment 39 by kexian...@gmail.com, Nov 11, 2009
I have the same problem with bigntallmike's: android won't connect my hidden but open
SSID.
Comment 40 by kurtz...@gmail.com, Nov 11, 2009
My Droid has the same behavior. It gives me the "unable to connect" msg if my SSID is
hidden. My route has WPA personal. It connects if SSID is broadcasted but loses the
connection immediately once I hide SSID.
Comment 41 by rjsch...@gmail.com, Nov 12, 2009
Confirmed.

Verizon Droid with Android 2.0 still has this issue. Once the SSID is hidden it will
not connect.

Security first, will not broadcast my ssid just to connect my phone.

Too bad this issue is not getting any attention from development as this is a rather
annoying bug.
Comment 43 by ian.mor...@gmail.com, Nov 12, 2009
@kynancheng

Interesting you can't connect at all.

I'm now without an Android phone for a while, so it's hard for me to test.

Some people reported that the Tricorder app helped them with this issue. But I don't
think it does anything significant enough to make your phone connect when it
currently won't.
Comment 44 by jaysonsm...@gmail.com, Nov 12, 2009
As a workaround, have any of you that are having issues downloaded "Hidden SSID
Enabler" (pname:jp.sourceforge.soopy.hidden.ssid.enabler) from the
market? I've used it for over a year, and I can generally connect to
my hidden SSIDs without any issues. There are occasions where I will
need to disable / re-enable wifi for it to pick up the router, but
they are fairly rare.
Comment 45 by rjsch...@gmail.com, Nov 12, 2009
Tried the hidden SSID app, not working even after enabling/disabling WiFi a couple of
times.

Funny thing is, my router is actually handing out an IP address to the phone but for
whatever reason droid refuses to accept it and finish the connection process. It just
comes back with "unsuccessful".
Comment 46 by ginge...@gmail.com, Nov 19, 2009
same problem, my wireless is an 802.11 PEAP network with non-broadcast ssid. Just says
NOT IN RANGE
Comment 47 by snc...@gmail.com, Nov 25, 2009
The status of the issue is still new after one year? I think this should be a very high
priority problem affecting all versions.
Please give us some kind of workaround or instructions or anything.

This is an urgent issue!
Comment 48 by snc...@gmail.com, Nov 25, 2009
Sorry, the AP configuration had been modified at the time I bought my android and they
forgot to tell us. The issue isn't exists here, I can connect to a hidden wpa personal
AP (Linksys WAP54G) without any problem.

Works like a charm, connects very fast!


Comment 49 by dragan.m...@gmail.com, Nov 25, 2009
My G1 (Android version 1.6) connects fine to Belkin router if SSID is hidden (did not
work before version 1.5 with any AP; didn't test it when I updated Android to 1.5
though).

It had problem connecting at first (hidden SSID shows up then hides in AP list then
shows then hides...then I manually add SSID and it connects somehow) but now works as
a charm, connects every time automatically.

If someone still have this problem try to turn on WiFi then manually add hidden
SSID/password and click on it in the APs list (repeat this 3-4 times).

Best regards,
Dragan
Comment 50 by diosbabo...@gmail.com, Nov 28, 2009
it works on my HTC Tattoo android 1.6
Comment 51 by philippe...@gmail.com, Nov 30, 2009
Hi All,
it doesn't work with my motorola dext (android 1.5).
i have tried any method explained above, without any success.
Is anybody has an other idea?
Comment 52 by ian.mor...@gmail.com, Nov 30, 2009
By the way, it's very interesting to note that I have an iPhone at the moment (for
testing, it's ghastly). However, try as I might, I can't get it to connect to my hidden
wifi either. It sees the network, it just cannot ever connect to it.

Seems like a common problem.
Comment 53 by dvs...@gmail.com, Nov 30, 2009
@colibri2
Thanks for this information! When I changed my mode from Auto to B&G Mixed only the
Droid connected to the hidden SSID. It does seem to take it a bit to "find" it when I
turn wireless on, but at least it does work!
Comment 54 by james.fi...@gmail.com, Dec 6, 2009
Why is anyone hiding the broadcast (actually only turning off 3 of the 5 beacons)
and making life difficult for yourself AS WELL AS opening up to a man-in-the-middle
attack? Hiding an SSID Broadcast is not smart at all. You will be found. Be secure
and leave the SSID ON and use WPA2, anything else can be broken too easily.
Comment 55 by joseph.o...@gmail.com, Dec 6, 2009
But you may have no option-- your employer or some other entity could be managing an
access point and decide to make the SSID hidden for reasons that are beyond your
knowledge or control. All moralizing aside, it is reasonable to expect Wifi clients to
be able to connect to hidden SSIDs.
Comment 56 by ian.mor...@gmail.com, Dec 6, 2009
"Why is anyone hiding the broadcast (actually only turning off 3 of the 5 beacons)
and making life difficult for yourself AS WELL AS opening up to a man-in-the-middle
attack?"

What is it with people assuming that we're ONLY using hidden SSID for security. The
problem is related to having BOTH encryption and a hidden SSID.

It's reasonable to expect wifi devices to handle this. My PCs are all fine with that
situation, it's just phones that seem to struggle.
Comment 57 by sdague, Dec 8, 2009
The hidden ssid enabler doesn't work for me. Android 1.5 HTC Hero (Sprint) trying to
connect to a WPA2 enterprise tls hidden network.
Comment 58 by jeffdickman, Dec 11, 2009
This is basic functionality the phone should have. Ubuntu has it, FreeBSD has it...
my old iPhone could do it. Linux in general figured out wireless support quite some
time ago - this should be included by a 2.0 version!


Comment 59 by mikev1...@gmail.com, Dec 13, 2009
I can confirm this issue on the Droid. It was driving me nuts! WAS driving me nuts. I just
installed the hiiden SSID app and it worked. I am one happy camper
Comment 60 by timk...@gmail.com, Dec 16, 2009
Droid can't connect to hidden SSID's.
Comment 61 by timk...@gmail.com, Dec 18, 2009
Don't make me broadcast my SSID! Fix this please.
Comment 62 by connelly...@gmail.com, Dec 20, 2009
Who set this as a medium priority? This is a basic function of any WiFi device! This
fault was identified more than a year ago AND it is still not solved? Unbelievable!

This is just another nail in the coffin for Android. I cannot begin to express how
annoyed I am about this major Android FAIL!

I was recently given an IPOD Touch as a gift. It took all of 20 seconds to connect it
to my WiFi network (with hidden SSID). Meanwhile, nothing (not even the hidden SSID
enabler) will allow my HTC Magic Android (OS 1.5) to connect. This is useless!

Virtually EVERYTHING about the Android is half-assed! Especially when compared to the
competition!

Perhaps the Android team should hire some Apple employees to show them how to
properly build a smart phone and support structure!
Comment 64 by bgourlie@gmail.com, Jan 7, 2010
Issue confirmed on Android 2.1, Nexus One. I don't even have the option of
broadcasting SSID to connect, this is a workplace network. HiddenSSID enabler does not
work. Please fix!
Comment 65 by tierne...@gmail.com, Jan 7, 2010
My Hero works fine with hidden SSID. I got a new router today and couldnt get the
phone to connect. I've since disabled WCN2.0 on the router and the phone connected
straight away.
Comment 66 by doll.ste...@gmail.com, Jan 13, 2010
I confirm this on Droid Eris (VZW) ver. 1.5. Can not connect to a hidden SSID with WPA2
. If I turn on the SSID broadcast, works great. Hidden SSID Enabler not working either.
Guess I broadcast from now on.
Comment 67 by derongal...@gmail.com, Jan 18, 2010
Nexus can't connect to wireless network at work which doesn't broadcast ssid...
Comment 68 by kReVvy@gmail.com, Jan 22, 2010
confirmed on nexus one
only way for me to use my wireless is to set SSID as visable in my router
Comment 69 by rodolphe...@gmail.com, Jan 26, 2010
I had the same problem connecting to an hidden ssid (WPA) with my tattoo : running
the code describe in comment 12 solves the problem. Hidden SSID Enabler is not
available for tattoo in the market, so i have to write some code!
Comment 70 by cantorbr...@gmail.com, Feb 9, 2010
Confirmed on a two new Droids purchased 2/8/2010. The problem is the hidden SSID.

Has nothing to do with any other settings, including WEP, WPA, key types, MAC
address filtering, etc.

This is basic Wi-Fi functionality. The fact that is doesn't work out of the box is
pretty lame from the original developers. Sorry to be nasty about this, but really
now. Droid Doesn't.
Comment 71 by lkachem...@gmail.com, Feb 12, 2010
Confirm the same problem on my new Nexus One with android 2.1 + update
Comment 72 by joe.fuehrer@gmail.com, Feb 18, 2010
Can confirm this issue on Milestone :-(
Comment 73 by petyrstr...@gmail.com, Feb 18, 2010
I swear that this worked prior to version 1.5. Does anyone have an old G1 firmware load
they could try?
Comment 74 by kent.m.s...@gmail.com, Feb 19, 2010
Can confirm inability to connect Droid Eris to hidden SSID WPA2 network. Unhide, and it
connects just fine.
Comment 75 by d...@lumpkin.me, Feb 21, 2010
Same for Nexus One SSID hidden + WEP. It will connect initially upon manual entry.
It will connect again when I toggle the wi-fi. But I can sit at work for 8 hours 5
feet from the wi-fi and it will never auto connect and join the network.
Comment 76 by arik%wic...@gtempaccount.com, Feb 26, 2010
Droid User...
WPA2/AES
802.11G

SSID is broadcasting
+Connect to LAN, Gets DHCP/Internet connection works.

SSID IS NOT Broadcasting
+Connects to network enough to get DHCP.
-NO Local Network or Internet Access.
Comment 77 by Piotr.K...@gmail.com, Mar 3, 2010
Today I've found out how to connect to hidden SSID WPA2 network. You just need to set
it up normally (ssid name and wpa2 password) and on the networks list push "menu" and
select "Search". After a short while You are connected ;)
Comment 78 by yglodt, Mar 4, 2010
I can confirm that what Piotr suggests in comment #77 works.

It's on a Samsung Galaxy using their unofficial 1.6 Firmware.
Comment 79 by jerom...@gmail.com, Mar 6, 2010
There definitely is a Problem here.
On my Nexus one, connecting to a hidden network works just fine for the first time
I'm connecting to a NEW Network. But it misses to reconnect after getting back into
range.
The suggested solution of Comment #77 is not working for me.

The only thing that works is to disable and enable WIFI in the settings activity.
Disable/Enable from the widget won't work.

But whatever solution works for you, this should work automatically for any device
that uses wifi and support hidden ssids.
Comment 80 by zoltan.s...@gmail.com, Mar 17, 2010
I can confirm on Samsung Spica with Android 1.5 and 2.1 :(
Comment 81 by pos...@gmail.com, Mar 23, 2010
http://en.androidwiki.com/wiki/Enabling_Hidden_SSID_Hack
Follow the way mentioned in above link, it works well to me with Acer Liquid.
Comment 82 by ion...@gmail.com, Mar 31, 2010
I can confirm #77 worked for my Droid running 2.1

Note that the menu item is "scan" on the droid rather than "search".
Comment 83 by joecornf...@gmail.com, Mar 31, 2010
I confirm on the Nexus one too, looks like is most defiantly software.
Comment 84 by blair.ho...@gmail.com, Apr 5, 2010
still broken. wasn't fixed by the recent nexus one android update. totally stupid
that this should still be a problem after all this time. if it connects once, it
should connect always. someone screwed up bad and is refusing to own up to it.
Comment 85 by sidmat...@gmail.com, Apr 7, 2010
Motorolla Droid, Android 2.1
For the longest time I couldn't connect to hidden SSID with WPA2 key, but I could
connect if it was broadcast SSID.

I did download the hack from #81, but had no success.

I changed the name of the SSID and set it to hidden, and deleted the previous SSID
from the droid.

Re-entered the new hidden SSID with WPA2 key in the droid... and it connected! Web is
working as well. I left the range of the router for a while, came back, and it
reconnected again... I guess I can't answer the "why" of why it connects now. Did the
#81 hack help? Don't know.
Comment 86 by derongal...@gmail.com, Apr 14, 2010
HTC Desire can connect and stay connected to Hidden SSID...

It also has wireless key option.


Comment 87 by Whi...@gmail.com, Apr 15, 2010
My HTC Desire can't connect on hidden SSID... ;(((
Comment 88 by deece...@gmail.com, Apr 15, 2010
The ability to connect to hidden ssid should be able to be accessed from the network UI.

With my Nexus 1, I had to enable the hidden ssid and connect normally. After the
network was saved as a favorite connection, it reconnects all the time without issue,
as soon as I am in range.
Comment 89 by Whi...@gmail.com, Apr 16, 2010
I'm a complete newbie... and can't make it work...

I already tried to remove my SSID from th phone...
Then "HiddenSSID Enabler" told me the SSID doesn't exist...
Then I add the SSID from the wifi parameters... and when I click on enable in
"HiddenSSID Enabler"... Nothing seems to happen...

If the SSID is switched to visible.. it connects... and prompt for WPA key the first
time...
If the SSID is invisible... it doesn't prompt the WPA key and tell the network is
offline...

Any step by step for rookie will be appreciate...

Cheers
Comment 90 by janeeliz...@gmail.com, Apr 21, 2010
Im a new user on the HTC Legend on Android. I am also a programmer, but not in the
phone sphere. I have had the phone for about a week, and I find it crazy that
issues such as this are in a product that has gone live. Never name with googles
name on it.

I found the HiddenSSID Enabler fixed my issue, but as users we shouldnt have to fix
things like this. My old Blackberry Pearl could do this out of the box....
Comment 91 by jspi...@gmail.com, Apr 22, 2010
This was working on my Nexus One, but recently, for some reason I ran into this issue
also. When I sent the wireless router to hid the SSID the phone drops the WiFi
connection immediately. When unhide it, it picks it up right away.
Comment 92 by janeeliz...@gmail.com, Apr 22, 2010
to #91: Yes thats exactly the issue I faced. Its not a problem with your router,
its the phone. I fixed this on my HTC Legend by:
1. leave your current settings on the phone (which connects to your wifi when the
ssid is not hidden) as they are, and leave your wifi ssid as hidden
2. download the hiddenssid enabler application from the android market
3. run it, and enter your ssid id into it
4. now when you turn on the wifi on your phone, it should automatically

Hope it works for you

Comment 93 by nicolas.raoul@gmail.com, Apr 22, 2010
I have an old HTC Magic with Android 1.5
Some days it connects, some days it won't connect, or takes a very long time before
connecting.

To #92: Did not help. The Hidden SSID Enabler application has no effect on my phone.

There really should be a "Connect" button near the "Forget" and "Cancel" buttons.
Should I ask my company to make their network less secure, just because of a silly
bug that has been known since October 2008 ?!
Comment 94 by sood.a...@gmail.com, Apr 24, 2010
On my Nexus One, I can connect to hidden SSIDs, provided I am not running into
another problem

http://code.google.com/p/android/issues/detail?id=1698

If I turn on SSID on the router, the WiFi list allows me to reconnect by re-trying
connection. Dealing with a hidden SSID only makes that problem worse, as the phone
doesn't offer you to retry the connection (only resolution with the above bug +
hidden SSID is to reboot the phone, sometimes a few times).
Comment 95 by abaw...@gmail.com, Apr 24, 2010
Set-up:
- Linksys 610N B/G/N modem and Belgacom B/G modem
- HTC Legend with Android 2.1 + latest updates

Problem:
- When modem is set to "Do not broadcast SSID" then no WiFi connection can be made

Test
- Turning SSID on enables phone to connect. But as soon as the SSID is turned off,
the connection is lost. NOT IN RANGE message
- Turning SSID on, establish the connection, disconnect, turn SSID off, try to
reconnect. Not working. REMEMBERED, NOT IN RANGE
- Turn modem to broadcast in G only (instead of B/G/N all at the same time or B/G at
the same time) results in the phone connecting immediately

Conclusion:
- Bug. This can be repeated on multiple modems.
- Other equipement (Sony and Clevo laptops with Intel 5300N modems, Apple iTouch)
works with the SSID hidden and the broadcast set to B/G/N

This needs to be fixed urgently as most wireless networks are mixed and many have a
hidden SSID.
Comment 96 by lazysunb...@gmail.com, Apr 24, 2010
I have the same problem with hidden SSID and WEP. Totally pathetic that this problem
has not been fixed. Just got my phone today and this is >RUBBISH AND UNACCEPTABLE
SITUATION< GOOGLE.
The tools from the market place did not help either :(

How the hell can this be a medium priority issue ?. Looks like it's been around for ages.

Google - what about giving a commitment to your customers to FIX this issue?!
Comment 97 by fudf...@gmail.com, Apr 25, 2010
Confirmed in HTC Desire, purchased today...
SSID not broadcasted with WPA.
Comment 98 by NDogadch...@gmail.com, Apr 26, 2010
Such trouble with PEAP security on HTC Desire!
Comment 99 by bleeter, Apr 26, 2010
Status 'New' and unassigned after more than 12 months?
Comment 100 by bra...@gmail.com, Apr 29, 2010
I can see a Belkin router (F5D7230-4) with hidden SSID but a Netgear router (WNR2000)
just shows as "Remembered"
A brief trial with a Linksys (WRTG54S) was also visible but only after first connecting
with SSID broadcast - and then SSID hidden
The Netgear router does not manage to connect with a hidden SSID at all.

Comment 102 by italodir...@gmail.com, May 3, 2010
I've got a HTC Desire and found to have resolved the issue by setting my Wirelsss
LAN to broadcast 11g only. (Previously had it broadcosting mix 11g,b,n and would
only work if SSID was visible) The major draw back with my fix is that it wont broad
11n speeds to any device.

Does anyone know if HTC Android 2.1 (Desire) recognises 11n ?
Comment 103 by bjbe...@gmail.com, May 5, 2010
HTC Desire running 2.1-update1 in Australia.
It appears the we are all having an issue with connecting to hidden SSID's with WPA2
security.
the app HiddenSSID appears to solve the issues for open/WEP/WPA networks, but not WPA2.

I am currently having this problem connecting with the my work router. it has .11g
but WPA2-PSK and TKIP encryption.
I've tried 99% of the above suggested solutions, but still no luck (my phone has been
'scanning' as per #77 for about 10 minutes so far unsuccessfully)

when I manually add the network there is no option to say it is a hidden SSID, or to
attempt to force a connection. just 'Not in range, remembered'.
Comment 104 by Matt.Whi...@gmail.com, May 12, 2010
I'm going to add my vote to getting this fixed (fingers crossed for froyo)
HTC Desire unlocked in the UK
Comment 105 by Joseph.L...@gmail.com, May 12, 2010
Experiencing this problem on the Motorola Droid.
I'm commenting to add to the number of customer cases.
Please fix!
Comment 106 by southpaw...@gmail.com, May 13, 2010
I originally had no issues. I added my wifi network info into the droid and enjoyed
wifi for over a week. I downloaded a few apps recently and "poof". Suddenly I get
the "Not in range, remembered" crap. Yes, if I turn on SSID broadcast it will work.
BUT it was working fine before without having to broadcast. WTF?? I went nuts trying
to figure if it was my WNDR3700 or phone. (sigh) Please put out 2.2 and fix this
already...
Comment 108 by javier...@gmail.com, May 14, 2010
Experiencing the problem with a Nexus 1 and with another Android based device.
Please fix!
Comment 109 by thacker....@gmail.com, May 18, 2010
I have the issue with the HTC Desire running Android 2.1, really annoying as is the one
serious bug with Android. Please fix this Google...
Comment 110 by asaly...@gmail.com, May 18, 2010
Confirmed on new Droid Incredible. Seriously Google, a year and a half plus?
Comment 111 by Colt.N.English@gmail.com, May 19, 2010
I have found the fix. According to my carrier (and I have confirmed it),
Turn of Network notification,
Delete the network and add it manually via the "Add Wi-Fi network" option. (This may
be optional?)
Turn off and back on WiFi. ( I have yet to check but I doubt it will reconect if I
leave the area and re-enter. )

The issue seems to be that WiFi doesn't broadcast probes to hidden networks when
looking for any free network.


WiFi Issue.png
37.7 KB View Download Comment 112 by bjbe...@gmail.com, May 20, 2010
I've found something interesting for the network I am trying to use.
We changed the wireless channel it was operating on. it was previously working on
channel 13. we changed this because we thought it had interference from another
router and moved it to 8. it works!

I haven't done extensive testing, but it appears the HTC Desire A8183 doesn't like
channel 13.. which is weird because its an Australian Channel for WiFi!

I will attempt this on another wifi network and see how it goes - or if anyone above
can do it on another handset?
Comment 113 by greml...@gmail.com, May 20, 2010
Confirmed on the Samsung Moment running official 2.1. I feel better that at least
it's not just me...
Comment 114 by sdka...@gmail.com, May 23, 2010
Confirmed on Samsung Moment running official 2.1 and Hiddenssid app. Still does not
work. Did not have this problem when running 1.5 w/ same router set at WPA. Works
fine if we broadcast, but this is not an option. Also, first time in an open network
setting w/ 2.1 tried out wireless. it connected fine. When I got home, it magically
connected to hidden ssid, but once it dropped (set to switch off w/ screen), it
would not reconnect. Family members' Hero HTCs running 1.5 also will not
detect/connect to our hidden ssid.
Comment 115 by sdka...@gmail.com, May 23, 2010
Re: comment 111 "fix" (text below)

This worked once. Could not duplicate. Only gets as far as showing my network w/
the mac ID and the method of encryption, but then WiFi switches to "disconnected"
After screen goes blank and I wake it up, WiFI reads "scanning" and hidden ssid is
back to "not in range, remembered" status. I have not tried this after rebooting my
phone. At this point, I don't accept this as a "fix" too inconsistent and too much
trouble. If my carrier (sprint) doesn't think this is important enough to address or
press Google for a fix, then I will continue to enjoy my unlimited EVDO/3G
connection on my existing data plan. (samsung moment w/ official 2.1)


>I have found the fix. According to my carrier (and I have confirmed it),
> Turn of Network notification,
> Delete the network and add it manually via the "Add Wi-Fi network" option. (This
>may
>be optional?)
> Turn off and back on WiFi. ( I have yet to check but I doubt it will reconect if I
>leave the area and re-enter. )
>
>The issue seems to be that WiFi doesn't broadcast probes to hidden networks when
>looking for any free network.


Comment 116 by revdbrink@gmail.com, May 24, 2010
It works also for me now on my HTC Desire with android 2.1
On my phone I removed my old wifi connection and disabled wifi.
On my router I disabled SSID and changed to channel 8.
On my phone again I add my wifi network manually by set the SSID, security, AND
SCROLL DOWN to set the password. Normally this is hidden behind your virtual keyboard.
Now my network is found and it all works. I don't know what did the trick exactly but
it works!
Comment 117 by yuha.m...@gmail.com, May 25, 2010
yes i got some problems with hidden SSID as well. the problems is that it connects to
my AP all fine when i enable the wifi from the android settings. ( phone is motorola
milestone android 2.1 )
but after some browsing the wifi connection drops saying not in range. and it doesn't
connect to it before turning wifi off and on again. my laptops have never dropped
like this from the same router.
distance is only about two meters to the router

Comment 118 by kustod...@gmail.com, Jun 7, 2010
Same problem with HTC Desire. Cannot connect to hidden wireless network. Haven't
tried HiddedSSID enabler yet.
Comment 119 by tpip...@gmail.com, Jun 9, 2010
Same here! Moto Droid, wpa with TKIP. Come on guys this is elementary stuff here! Thanks in advance!
Comment 120 by brooks....@gmail.com, Jun 13, 2010
Same problem overcome with Moto Droid (Android 2.1).

I originally couldn't connect to my known, WEP enabled, home AP if I turned SSID broadcasting off. I would get the "remembered, but out of range" message.

But BOTH available solutions mentioned above worked for me:

1. either do what is mentioned in Comment 111 above (turn off Network Notification).

or

2. download and run "HiddenSSID Enabler" app (by Jun SUZUKI) from the Android market.

Or you can do both.

Comment 121 by juliocgo...@gmail.com, Jun 13, 2010
I'm running 2.1-update1 on the HTC Incredible. I refuse to broadcast my SSID just to be able to connect my phone to my home network. I have tried the "HiddenSSID Enabler" app from the market, but as mentioned in some comments above, nothing happens when i push the button. The only thing that worked for me was to disable the "Mixed" mode on the router and broadcast in "B/G Only" mode, which I also refuse to do, because it basically cripples my entire network, making my "N-Router" an old B/G only. Google, please ASSIGN this to someone!
Comment 122 by Stephani...@gmail.com, Jun 13, 2010
Same issue as 121. Can we have a resolution for this please? I don't want to have to have to return to AT&T (love my iphone.) This is a deal breaker for me.
Comment 123 by james.gl...@gmail.com, Jun 17, 2010
Here's my setup:

Motorola Droid
TrendNet TEW-639GR (b/g/n) router with WPA-PSK2

Only workaround that works for me is broadcasting the SSID (which I agree sucks as a solution).

Once I connect with a broadcast SSID, the status of my network changes to "Remembered, secured with WPA/WPA2 PSK" - but still can't connect. "HiddenSSID Enabler" does nothing. Turning off Network Notification does nothing.
Comment 124 by tinlong0...@gmail.com, Jun 17, 2010
I have been able to get around this problem, and in the mean time figured out a piece of strange information.

Setup:

- Nexus One with Android 2.1-update1, stock, network notification turned off
- Netgear WNDR3700 router.

I have just acquired the Nexus One very recently, and immediately encountered this hidden SSID problem. The specified router has been set not to broadcast SSIDs. I have disabled network notification on my N1, and still not connecting. After seeing someone talking about the WPA/WPA2 security setting, I decided to give it a try, and tested some options.

In WNDR3700, there are 6 options of wireless network security:

- None
- WEP
- WPA (TKIP)
- WPA2 (AES)
- WPA/WPA2 (TKIP/AES)
- WPA/WPA2 Enterprise (must with RADIUS server)

Obviously, I would not be able to test the last option. I have tested "None" and "WPA", and the hidden SSID configuration works without any issue. I then tested "WPA2", and it still works, surprisingly. It was only when using "WPA/WPA2", then my N1 would not be able to connect.

I decided to set the router using WPA2 only, because all devices connecting to this router are fairly new, so there is no need to have WPA for falling back.

So, at least for WNDR3700, the "WPA/WPA2" setting would cause N1 not able to connect, although other devices have no problem.
Comment 125 by nate...@gmail.com, Jun 23, 2010
I can confirm this issue with the HTC Incredible and a WRT610N router.

I have tried my 5ghz setting at mixed or n only while changing my 2.4ghz setting between mixed and b/g only to no avail.

HiddenSSID Enabler does not work as a solution either.
Comment 126 by c4me...@gmail.com, Jun 24, 2010
Setup:

HTC Aria
TrendNet TEW-638APB (b/g/n) access point

----------------------
Security Mode WPA2-PSK
WPA Algorithms AES
----------------------
SSID hidden: Cannot connect to WiFi. Message- Not in range. Remembered.
SSID broadcast: Connects, no problem.



---------------------
Security Mode WPA-PSK
WPA Algorithm TKIP
---------------------
SSID hidden: Connects. Intermittently connection is dropped.
SSID broadcast: Connects, no problems.


Solution in #77 did not work for me.

Comment 127 by duncanbr...@gmail.com, Jun 25, 2010
Setup:

SE Xperia X10i running Android 1.6
Netgear DG834 b/g access point
Hidden SSID

same issue as everyone else - couldn't connect to a hidden network.

Have got the phone to connect by un-checking "Network Notification" in Wi-Fi settings and then manually adding my network. (Solution mentioned in #111.)
Comment 129 by admanb...@gmail.com, Jun 26, 2010
I was also having this issue until I came here and read a few of the recent posts carefully. If you notice, after selecting the security type, a TINY scroll bar appears. DON'T click the save button until after you have scrolled down and entered your password. I definitely made that mistake on a few networks that don't broadcast and now that I know to scroll down, I'm able to connect just fine.

I had many of the same symptoms that other posters above have had. So just be aware that the keyboard is obscuring the password entry and you might just be OK. Then we can chalk it up to a combination of hopefully something as simple as poor UI design combined with user error...
Comment 130 by eoduf...@gmail.com, Jun 30, 2010
#129 worked beautifully, unbelievable, have been having this problem on the HTC desire since march, and now hidden ssid is now working on my mobile. Thanks Admandnyc.
Comment 131 by Skipper....@gmail.com, Jul 2, 2010
Same problem as the rest; HiddenSSID on the Market does nothing. I'll try out the Network Notification thing and the "fix" in #129 (but I think I did that) when I'm near a network I know next. Broadcasting the SSID is not an option, nor is fiddling with the router as the only hidden SSIDs I connect with are friends' or work (and I refuse to ask friends or work to bend over backwards for my convenience just because of a poor design with the phone).

Moto Droid, 2.1 stock. I love this thing otherwise, but it's not good when I'm at my buddy's house who is a huge iphone fan and this silly bug allows him to denigrate Android products. Come on Google; you know how powerful firsthand marketing can be! You guys lost a potential convert due to this.
Comment 132 by martienb...@gmail.com, Jul 3, 2010
My Windows Mobile HTC has no issues with this... You just check a box 'This is a hidden network'. None of the solutions above worked for me. For me, it's not such a big issue (1.5 Mbs flat rate), but annoying it is!
Comment 133 by elind...@gmail.com, Jul 3, 2010
Confirmed on 2.2 on nexus one :/
Comment 134 by jgr...@gmail.com, Jul 4, 2010
After some experimentation with my ATT N1 running Android 2.2 I think the issue is related to a combination of hidden SSID and AES. I am able to reliably connect the N1 to my hidden SSID network if I force the encryption to TKIP. If the SSID is not hidden then I can force AES or TKIP encryption and I can still connect. I've seen some similar issues with Ubuntu 10.04 too but that may be a red herring. My router is a D-Link DIR-825.
Comment 135 by pbonew...@gmail.com, Jul 4, 2010
Same here - HTC Desire. Wifi has worked beautifully for the last five weeks since owning the phone. Since yesterday it has been pretty much useless. The phone seems to go through endless cycles of discovering and dropping the connection or displaying "not in range, remembered".

Maybe related to the HTC firmware update I made yesterday but I doubt it as the problem started before.
Comment 136 by nddea...@gmail.com, Jul 12, 2010
Suggestions of comment #111 solved my issue. Large hospital, multiple hidden network ssids, disable notification, restarted wifi, instant connection. LG Ally.
Comment 137 by alex.fal...@gmail.com, Jul 12, 2010
Problem confirmed with a Pandigital Novel with latest (July 2010) firmware on a wireless router I control. Enabled SSID broadcast long enough to connect the first time, re-disabled SSID broadcast. The Novel's been disconnected several times and reconnects fine every time since, so far. Won't help for people accessing routers they don't control, but might if you're having the problem right out of the box on your own network.
Comment 138 by zimodec...@gmail.com, Jul 12, 2010
Comment #129 - worked for me..it was just as simple to scroll down & add the password prior. I was definitely hitting "Save" w/o scrolling down and entering the password. It just worked!
Comment 139 by vivektan...@gmail.com, Jul 12, 2010
On an HTC Desire 2.1 none of the solutions above work. I have a hidden SSID at work which is open (do no issue of entering password or encryption). Hidden SSID app does not work (on my Desire or my friend's Nexus one). I tried unchecking network notification box & manually entering settings, no effect. Cannot change the channel or b/g instead of mixed since our IT guys wont let me do that. Since this is an issue on Desire as well as Nexus one (still on eclair awaiting OTA Froyo), I think this is an Android issue not an HTC issue. Will see if Froyo on my friend's Nexus one solves the problem. But this should have been fixed by Google. My ipod touch has no issues connecting to the same networks.
Comment 140 by steve.gase@gmail.com, Jul 14, 2010
I confirm. I have a broadcast wireless using DLink that works, and I have a hidden Netgear which doesn't.
Comment 141 by bjbe...@gmail.com, Jul 15, 2010
I can confirm this has well. HTC Droid Incredible cannot connect when SSID is not broadcast.
Comment 142 by alex.fal...@gmail.com, Jul 16, 2010
I have to retract my statement in #137. It seemed to be fine, but it only lasted the rest of that day. I've since played with it some more, and I can't reliably connect again over time unless I turn on SSID broadcast, which I simply can't leave on. And this keeps me out of a great many other networks I would like to use as well. Router's using WPA2/AES; I'd test with something else, but that means bringing down the network, which I also can't/won't do. Let's hope this gets fixed; it's such a strange problem to have, really; I mean even WinMo phones get it right, ya know? ;)
Comment 144 by lkhinto...@gmail.com, Jul 19, 2010
Using "Static" WiFi Network Settings (IP Address, Gateway, DNS) will resolve this problem. (2 Moto DROIDs)

Comment 145 by escuc...@gmail.com, Jul 21, 2010
Colt.N.English's fix worked for me. I deleted the network, hid the ssid, turned off automatic notification, manually added the ssid and no problems.

As a note I tried a static IP and that did NOT work for me. Who knows? These things seem to be rather unpredictable. We'll see if it's still connected in a few hours.
Comment 146 by Strecke...@gmail.com, Jul 23, 2010
I have a Droid X and I tried Colt.N.English's solution. It appears to be working, but the connection drops and sometimes it takes a while for it to connect. This issue definitely needs to be fixed. The average end user wont want to have to experiment with the settings.
Comment 147 by Buck...@gmail.com, Jul 28, 2010
Comment 111 worked for me. Thanks!!
Comment 148 by toddy...@gmail.com, Jul 28, 2010
To Comment 144 - sorry, no. The WiFi is said to be connected - however all activity that requires internet connection, would error: Connection Error. or Network lost.
Tried Comment 111, also not working. Have tried restarted the AP, the Wifi, and the phone, no luck.
The only solution is to enable SSID broadcast. WEP security on the AP.
Comment 149 by sewerkr...@gmail.com, Jul 28, 2010
Seems Comment 111 worked for me. HTC Magic (2.1)
How long.. we well see..
Comment 151 by jason...@gmail.com, Aug 2, 2010
HTC Legend (2.1)... Doesn't work
Anyone got their Legend to connect to a Hidden (Open) Network?
Comment 152 by jboll...@gmail.com, Aug 5, 2010
Confirmed on htc ion. Hard to believe the problem has been GOING ON SINCE 2008 and Google doesn't have it fixed yet. My iPhone connects to my hidden ssid with absolutely no problem whatsoever right out of the box.
Comment 153 by russjc...@gmail.com, Aug 7, 2010
I have the same issue on a Desire running 2.2 Can't quite believe this isn't fixed.
Comment 154 by v.mosen...@gmail.com, Aug 8, 2010
The solution in comment #129 worked perfectly on my HTC Legend.
Comment 155 by thungs...@gmail.com, Aug 8, 2010
Same also for WPA secured networks!
Comment 156 by michael....@gmail.com, Aug 8, 2010
Just got a HTC Desire from Telstra in Australia... initially had trouble connecting to my work WPA2-Enterprise network which is hidden.

Tried hidden SSID enabler app... no love. (Although I left this installed)

Tried the method in comment #77 and that worked :) I added the network manually, then chose "Scan" from the menu on wireless network setup screen. It then found the network and I was able to connect after entering my work domain user/password.

Not exactly an intuitive process... but at least I am connected.
Comment 157 by J7B...@gmail.com, Aug 13, 2010
Aside from the questionable security benefits of of hidden SSIDs another justification for there use is that a lot of older APs did not handle multiple SSIDs when setup to create multiple SSIDS on separate VLANs. Good luck convincing corporations who are using this implementation to change just for Android. I really think the UI should be handled better here. I know that it it took quite a while for MS WinMobile to handle this gracefully; but eventually they conceded that hidden networks where common enough that they needed to be handled _gracefully_.

Despite the fact that including hidden networks in the scan list generally increases the power requirements for updating the visible network list I would argue that the UI should be extended to handle them explicitly, due there prevalence; as was previously noted the APIs already supports this.

-JL
Comment 158 by chku...@gmail.com, Aug 15, 2010
"I have found the fix. According to my carrier (and I have confirmed it),
Turn of Network notification,
Delete the network and add it manually via the "Add Wi-Fi network" option. (This may
be optional?)
Turn off and back on WiFi. ( I have yet to check but I doubt it will reconect if I
leave the area and re-enter. )

The issue seems to be that WiFi doesn't broadcast probes to hidden networks when
looking for any free network."


This worked for me on my Incredible.

Thank you!

Comment 159 by johnmclu...@gmail.com, Aug 16, 2010
Confirmed. The HiddenSSID enabler didn't work for me (HTC Desire with 2.2).
Comment 160 by beow...@gmail.com, Aug 16, 2010
Fixed!

I had this problem on an HTC Desire running 2.2 Froyo and attempting to connect to a WPA-PSK secured network with a hidden SSID. Tried HiddenSSID Enabler as well as turning wifi on and off and several other workarounds here, nothing worked - the network would just say "Not in range, remembered" and then eventually disappear from the remembered networks list without ever attempting to connect.

Turns out that it was a problem with the interface all along!

WHAT I DID ORIGINALLY:
-Turn on Wi-Fi.
-Select "Add Wi-Fi Network". The Add Wi-Fi Network dialog appears, along with the keyboard covering the bottom half of the screen.
-Note that the visible fields are "Network SSID", "Security" and the Save and Cancel buttons.
-Enter the network SSID as normal.
-Select WPA/WPA2 PSK under Security.
-Note that the visible fields remain unchanged - Network SSID, Security, Save and Cancel are visible.
-Press the Save button.
-Expect to be prompted for WPA key. Not prompted for WPA key.
-Note that the resulting network entry does not connect and reads "Not in range, remembered" until it is auto-removed some time later.
- :( !!! Frustration, etc. Look for workarounds, gawk in fascination at such an elementary bug remaining in the Android codebase, consider complaining loudly et cetera.

WHAT I DID TO MAKE IT WORK:
-Turn on Wi-Fi.
-Select "Add Wi-Fi Network". The Add Wi-Fi Network dialog appears, along with the keyboard covering the bottom half of the screen.
-Note that the visible fields are "Network SSID", "Security" and the Save and Cancel buttons.
-Enter the network SSID as normal.
-Select WPA/WPA2 PSK under Security.
-Note that the visible fields remain unchanged - Network SSID, Security, Save and Cancel are visible.
-HIDE THE KEYBOARD!
-Note that a previously-hidden field has appeared, entitled Wireless Password!
-Enter the WPA key in the Wireless Password field.
-Press Save.
-Note that the wireless network connects successfully almost immediately and is subsequently remembered/auto-connected to when in range/everything else that one would reasonably expect.
-Facepalm at the Save and Cancel buttons being allowed to float up to obscure a critical field.

So, there you have it. The Save and Cancel buttons are obviously of a UI class that is allowed to float above the keyboard, but in this case it seems to have generated a great deal of needless confusion and trauma. Some of the problems reported under this bug may well be arising from simple user error thanks to this non-intuitive behaviour.

Consider opening a separate bug to prevent this float-and-obscure behaviour, please. People are going to think that Android can't do something as simple as connecting to a Hidden SSID, which is absolutely laughable and is a really really bad look.
Comment 161 by bertrand...@gmail.com, Aug 18, 2010
I, too, can confirm that the Moto DROID does have problems connecting to wireless networks that do not broadcast SSIDs that are transmitting above 54Mbps at the 2.4GHz frequency. In other words, it has a problem with Wireless-N or mixed (A-B-G-N) capable networks.

My Moto DROID worked fine on a Netgear WNDR-3700 NOT broadcasting a SSID at 54 Mbps, but once I upped the throughput on my router for the 2.4GHz band to 130Mbps or higher, then the DROID could no longer connect.

However, once I enabled broadcasting of the SSID at the higher speeds and selected my wireless network from the discovered networks list, then it worked fine! Weird.

So, wireless does work on a Moto Droid, but it seems the DROID has some things to learn / fix about wireless network protocols.

The question is, who will fix this.... Google or Motorola? Or is it really too late, as its could be a hardware issue - so, did they get this right with Droid 2?

This is one thing I am very disappointed on about products trying to offer WiFi access...they do not seem to comply with known / established standards, especially for products made in 2010! For crying out loud...get it right! LOL

Comment 162 by gintaras...@gmail.com, Aug 19, 2010
Got my 2.2 update this morning and I was hoping that 2.2 would fix the hidden SSID iddue.. no, I still cannot connect to a router with a hidden SSID.. I can conenct with a laptop, but not with the droid.. this is depressing. :( Why has no-one from the dev team had any input here?
Comment 163 by thefirst...@gmail.com, Aug 20, 2010
There is a program in the market to connect to routers with hidden SSID's, and it worked for me at first, but it not worked for me in a couple days.
Comment 164 by Etchego...@gmail.com, Aug 27, 2010
Hidden SSID enabler... not working for me with my Spica
Comment 165 by djinn.y...@gmail.com, Aug 29, 2010
I have the same problem... this apk don't work for me. I have hidden SSID on my work. connect WPA2 PSK. please help me
Comment 167 by gar...@gmail.com, Aug 30, 2010
Same problem, can't connect with hidden SSID and WPA2, can connect with Broadcast SSID and WPA2. LG Ally with Android 2.1.
I can connect with hidden SSID if I use 802.11B, G, or B/G. B/G/N and N didn't work, per comment 102 and 161.

Turning "Network notification" on/off per comment 111 did not make a difference in my case.
Changing Standard Channel on router from "Auto" to manually selecting Channels 8, 11, 1, and 2 in turn per comment 112, did not make a difference either.
Always had the password entered, although I noticed the onscreen keyboard can obscure the password box.
Pressing menu button from the "Wi-Fi" settings page mostly helped to initiate the reconnect if I had just changed the router to good settings and the phone wasn't retrying right away, although it usually retried pretty quickly.

Router is a Linksys WRT160N V2. (Uses Ralink chip instead of Broadcom chip like in V1 and V3, so no Tomato flash for me. =b Don't know if that matters here though.) I have a Droid 2 with 2.2 that was connecting fine with hidden SSID, WPA2, and B/G/N.

I only have G devices for now anyway, but this kinda sucks if I want to use N later. In which case, I guess I'll have to suck it up and broadcast. <grr>
Comment 169 by gar...@gmail.com, Aug 30, 2010
Wait, I just realized, the Droid 2 and LG Ally support 802.11N (fine, 802.11n). <facepalm> I guess I'm sucking it up and broadcasting. =b

Comment 171 by tagreb...@gmail.com, Aug 31, 2010
Two years and this issue has still not been resolved. :P

I am running Android 2.2 on a HTC Desire.
The issue is confirmed here as well, and the "sollution" presented in post 160:
http://code.google.com/p/android/issues/detail?id=1041#c160 is not the issue.

Having tried everything from changing channel, disabeling Wi-Fi Protected Setup, changing Cipher Type and more. No luck.

Android 2.2 cant connect to hidden wireless. It is a shame and embarrasing!

When SSID is broadcasted, it connects. I can then disable SSID broadcast as long as the phone is in range of the network and it will stay connected.

However, after having been connected to WLAN at work and coming home, it no longer can connect to WLAN with disabled SSID broadcast.

When disabling the Wi-Fi Protected Setup it actually finds the hidden network, but is unable to connect.

Comment 172 by dogsb...@gmail.com, Sep 1, 2010

My HTC Incredible with 2.1 connected to hidden SSID networks with no problem.

Not so after upgrading to 2.2. Probably a software developer at Google changed something to make the source "cleaner", or architecturally "better", and now adamantly refuses to put the necessary hack back to allow hidden SSID's to work again. It wouldn't be "cleaner" or "better" anymore.

I'm not holding my breath this will get fixed. Broadcasting your SSID is the only fix. Setup a MAC address filter on your router to prevent unauthorized connections. Hope for the best. Can't connect at work? Too bad.

Very disappointing Google... As someone else said it's pathetic.


Comment 173 by yock...@gmail.com, Sep 2, 2010
Have the same problem as everyone else.
Tried to connect to hidden SSID and got nothing then turned on SSID broadcast and i was connected.
HTC Desire with FrYo 2.2 and it did not work with 2.1 either so please fix this!
Tried the "hack" #71 was talking about but it did not work =/
Comment 175 by marcel.verpaalen@gmail.com, Sep 6, 2010
In the market there is another app that appears to be a bit more userfriendly and does the trick. I't callen WIFI manager (org.kman.WifiManager ), it can add new networks and there is a clear checkbox in the GUI for the hidden network
Comment 176 by skycak...@gmail.com, Sep 6, 2010
#175 does not work. i was pretty stoked to see a hidden SSID option in the GUI. however when you click it it basically tells you android sucks at connecting to ssid's and hence if you have had problems in the past connecting to hidden ssid's, this app will do diddly squat for you. i made the network, hid my ssid, filled in all the correct settings, wifi manager just said connecting, but never did. i then unhid my network and android connected to the network no problem using the same settings. I think its a problem in the code of android itself, and until that is changed, no app is gonna be able to fix this issue, regardless of what options it says it has. Google, get off your butt and fix this insanely annoying yet completely fixable glitch.

SGS GT i9000m bell. eclair 2.1update1
Comment 180 by Etchego...@gmail.com, Sep 8, 2010
I was doing some tests at home with my samsung galaxy spica, android 2.1..

- with SSID broadcasting off, WPA2 Personal security, and AES algorithms.. WIFI COULDN'T CONNECT
- with SSID broadcasting off, WPA2 Personal security, and TKIP+AES algorithms.. WIFI CONNECTED OK
- with SSID broadcasting off, WPA Personal security, WIKI CONNECTED OK
- with SSID broadcasting on, WIFI CONNECTED OK
Comment 181 by spuddae...@gmail.com, Sep 9, 2010
I liked Etchegoyen's testing in #180, which led me to try different network modes.

I had my Linksys WRT160N set to mixed mode (all of g,b & n). After switching to bg-mixed, however, my HTC Incredible (Android v2.2) was finally able to connect to a hidden ssid.

WPA2 Personal, TKIP&AES, SSID broadcasting disabled, BG-Mixed mode, MAC Filter::connected

*ack* finally.
Comment 182 by htc.desi...@gmail.com, Sep 11, 2010
HTS Desire is a sorry phone. Placement of the on/off button forces you to press the volume buttons no matter if you are a lefty or not. The buttons on the outside bottom are redundant and useless but most of all the Android OS 2.1 is not ready for prime time with innumerable bugs like wifi, vpn, erase or change your email and you have to reset the phone to do that, a sync program that syncs nothing and does not recognize windows mail, etc, the list is infinite. In short, it's a piece of trash with a manual. Buy an iPhone for the same price and you will never have any problems of this sort, besides the iPhone is totally intuitive, no manual to read, no guessing, everything is right in front of you and works perfectly, it's also impermeable to viruses.
Comment 183 by flapjack...@gmail.com, Sep 12, 2010
@htc.desire.droid

iPhone in the UK is AT LEAST £10 more per month. My Desire has no bugs with wifi or vpn, and considering I use google calendar my syncing works great too. For anyone that cannot bear to be forced into investing the premium Apple lifestyle, Android smartphones are a viable alternative. No OS is "impermeable" to viruses, not least those of Apple based on stolen linux kernel. I AM a lefty and have NO problems with any of the buttons.
p.s. When I hold my HTC normally, reception does NOT cut out... unlike some other i-related phones I can think of.


Comment 184 by mokdanie...@gmail.com, Sep 15, 2010
a workaround: download "hidden SSID enabler" from the android market.
Works like a charm!
Comment 185 by Etchego...@gmail.com, Sep 17, 2010
hidden SSID enabler not working for most of the people here
Comment 186 by jcarlos....@gmail.com, Sep 24, 2010
I have can test that the problem is present only with some ROMs. I've been using NeoPhyte Mod 1.8 (Froyo 2.2) and it connects without any problem to Wifis with WPA/WPA2 and the SSID hidden.

However, with other ROMs, like OpenDesire, CyanogenMod, etc, I get the same issue described here.

Perhaps it helps to find the solution.


Regards.

Comment 187 by ntp...@gmail.com, Sep 24, 2010
I can confirm #160 worked for my Desire running 2.2
Tnx!
Comment 188 by rachid.h...@gmail.com, Sep 26, 2010
Had this problem on my Desire running 2.2. Changing my router channel from 13 to 10 did the trick. I now have an instant connection to my hidden ssid.
Comment 189 by katherin...@gmail.com, Sep 27, 2010
I have this issue on my HTC Hero running official 2.1. It had this issue on stock 1.5. The Hidden SSID Enabler application does not work.
Router is a dual band abgn one, and changing from channel 6 to 10 on the bg band did not solve anything.
Comment 190 by brandon....@gmail.com, Oct 1, 2010
Confirmed on Nexus One running Android 2.2.1
Comment 191 by j.po.ahl...@gmail.com, Oct 4, 2010
I confirm for Sony Ericsson X10 mini pro
Comment 192 by elind...@gmail.com, Oct 8, 2010
Seconded confirm on Nexus One, running 2.2.1
Comment 193 by cjpark...@gmail.com, Oct 9, 2010
Confirmed on HTC Evo 4g.

The problem is definitely SSID broadcasting. That's the only change I made to my router before WiFi stopped working. My router is a D-Link DIR-655 and my settings are:

SSID broadcasting disabled
WPA2 PSK, AES only
B/G/N mixed mode

I like how so many people recommend things like changing the router settings to B/G only. Yeah like I'm really going to disable wireless N for my entire network just so my phone can connect. That's ridiculous. Yeah I also realize disabling SSID broadcasting by itself isn't much security but when combined with encryption it's what we in the industry call layered security. Every layer implemented to prevent unauthorized access is like another wall between your network and everyone else.

Bottom line is this is obviously a common problem which should be a number one priority. We shouldn't have to reconfigure our wireless networks just for one wireless device. I hope this problem gets fixed soon.
Comment 194 by Ralphy.S...@gmail.com, Oct 9, 2010
Got it working once I disabled N on my Netgear WNR3500v2, so running the router in B/G works fine but as soon as I enable N the phone can't connect.

HTC Desire, Android 2.2 without HiddenSSID app
Netgear WNR3500v2, WPA-PSK [TKIP] + WPA2-PSK [AES], B/G mode

While the Desire doesn't support the N standard one would think that it would be able to connect to a router that is broadcasting in all 3 modes even if it isn't broadcasting it's SSID.
Comment 196 by eharsh...@gmail.com, Oct 12, 2010
With 2.1 on my Droid I could connect easily to the (hidden SSID) network at my workplace. I used the Wifi at work to download the 2.2 update. Now, I cannot connect to the same network. I have no way to tweak any router settings. Phone has no cell service - received it at a convention so I only use Wifi.

I tried #111, no luck.

I will try the HiddenSSID app once I get home to download it, but I am not expecting it to work. Even if it does, I wouldn't be happy about needing to run a 3rd party app just to get functionality which 2.2 should already have.
Comment 197 by ivanandr...@gmail.com, Oct 12, 2010
WiFiConnector application available on the Markte solved my problems with the hidden SSID. Using HTC Desire with Android version 2.2.1, Mod version OpenDesire-4.0.34, baseband version 32.44.00.32U_5.09.095.30_2 and kernel version 2.6.35.6-OpenDesire.
Comment 198 by blazingt...@gmail.com, Oct 21, 2010
I can't even click connect :/
I'm running on an Android 2.2 port for my HTC Fuze.

My Fuze, when on Windows Mobile is able to connect to my place's hidden network :/ Why can't Android??? D:
Comment 199 by thomast....@gmail.com, Oct 27, 2010
Confirm same problem on my Motorola xt720, Android 2.1. Channel 6 can connect while I try to change to other channel, the SSID is not in range. Using SSID enabler solved the problem.
Comment 201 by coverlan...@gmail.com, Nov 6, 2010
Comment 160 by beowurk, Aug 16, 2010

Fixed!

I had this problem on an HTC Desire running 2.2 Froyo and attempting to connect to a WPA-PSK secured network with a hidden SSID. Tried HiddenSSID Enabler as well as turning wifi on and off and several other workarounds here, nothing worked - the network would just say "Not in range, remembered" and then eventually disappear from the remembered networks list without ever attempting to connect.

Turns out that it was a problem with the interface all along!

WHAT I DID ORIGINALLY:
-Turn on Wi-Fi.
-Select "Add Wi-Fi Network". The Add Wi-Fi Network dialog appears, along with the keyboard covering the bottom half of the screen.
-Note that the visible fields are "Network SSID", "Security" and the Save and Cancel buttons.
-Enter the network SSID as normal.
-Select WPA/WPA2 PSK under Security.
-Note that the visible fields remain unchanged - Network SSID, Security, Save and Cancel are visible.
-Press the Save button.
-Expect to be prompted for WPA key. Not prompted for WPA key.
-Note that the resulting network entry does not connect and reads "Not in range, remembered" until it is auto-removed some time later.
- :( !!! Frustration, etc. Look for workarounds, gawk in fascination at such an elementary bug remaining in the Android codebase, consider complaining loudly et cetera.

WHAT I DID TO MAKE IT WORK:
-Turn on Wi-Fi.
-Select "Add Wi-Fi Network". The Add Wi-Fi Network dialog appears, along with the keyboard covering the bottom half of the screen.
-Note that the visible fields are "Network SSID", "Security" and the Save and Cancel buttons.
-Enter the network SSID as normal.
-Select WPA/WPA2 PSK under Security.
-Note that the visible fields remain unchanged - Network SSID, Security, Save and Cancel are visible.
-HIDE THE KEYBOARD!
-Note that a previously-hidden field has appeared, entitled Wireless Password!
-Enter the WPA key in the Wireless Password field.
-Press Save.
-Note that the wireless network connects successfully almost immediately and is subsequently remembered/auto-connected to when in range/everything else that one would reasonably expect.
-Facepalm at the Save and Cancel buttons being allowed to float up to obscure a critical field.

So, there you have it. The Save and Cancel buttons are obviously of a UI class that is allowed to float above the keyboard, but in this case it seems to have generated a great deal of needless confusion and trauma. Some of the problems reported under this bug may well be arising from simple user error thanks to this non-intuitive behaviour.

Consider opening a separate bug to prevent this float-and-obscure behaviour, please. People are going to think that Android can't do something as simple as connecting to a Hidden SSID, which is absolutely laughable and is a really really bad look.
---------------------------
Not sure about a couple of lines in the 'fix' portion that begin with:
-HIDE THE KEYBOARD!
-Note that a previously-hidden field has appeared, entitled Wireless Password!

Not sure what is meant by 'hide the keyboard'. I tried literally hiding the keyboard on my daughter's flipout and then hiding the password (toggle on/off, etc) to no avail. Also would like to know more about the UI class that's allowed to float above the keyboard comment too. Gee, I almost wish I had leaned harder toward an Apple. My daughter has an Itouch that connects just fine to our hidden SSID wireless net. Also was very disappointed in a piece of advice on the motorola forum which advised me to just broadcast SSID since it doesn't do nuttin anyhow..

Thought I'd heard it all...

Appreciate this forum - if I can get this solved, I too will try to post solution.

Comment 202 by coverlan...@gmail.com, Nov 7, 2010
Amen Brother... I was growing tired of arguing the virtues of SSID broadcasting and the tremendous point is "we shouldn't have to do it". As a matter of fact, when competitors like Apple have it down pat, why can't the non-Apple competition get it right where we aren't requested to do ANYTHING to our wireless systems to accomodate the new addition. I've spent WAY more time than I should have had to on this issue and in my case, if Motorola would have conceded and advised "Yes Sir, Mr Customer, we're all over it and have your back on this - we guarantee your satisfaction", I would have been thrilled...

I'd like to know more about #160 on this thread - not sure what he means by 'HIDE THE KEYBOARD' but I'm intrigued and hopefully he weighs back in.

For those 'experts' advising to dump your hidden SSID in favor of broadcasting it, please stop telling people it's a waste - that advice is simply not true...

-----------
>Comment 193 by cjparker2, Oct 09, 2010
>Confirmed on HTC Evo 4g.

>The problem is definitely SSID broadcasting. That's the only change I made to my >router before WiFi stopped working. My router is a D-Link DIR-655 and my settings >are:

>SSID broadcasting disabled
>WPA2 PSK, AES only
>B/G/N mixed mode

>I like how so many people recommend things like changing the router settings to B/G >only. Yeah like I'm really going to disable wireless N for my entire network just >so my phone can connect. That's ridiculous. Yeah I also realize disabling SSID >broadcasting by itself isn't much security but when combined with encryption it's >what we in the industry call layered security. Every layer implemented to prevent >unauthorized access is like another wall between your network and everyone else.

>Bottom line is this is obviously a common problem which should be a number one >priority. We shouldn't have to reconfigure our wireless networks just for one >wireless device. I hope this problem gets fixed soon.

Comment 203 by alzuunTu...@gmail.com, Nov 17, 2010
Confirm: this is still broken. "Hide the keyboard" I found to mean that some interfaces obscure the password blank. The scroll bar is still there, though, (albeit thin) so it isn't completely hidden. Anyway, typing in the password still doesn't work on hidden networks.
Comment 204 by pekk...@gmail.com, Nov 20, 2010
"HIDE THE KEYBOARD" in Comment #160 means that on a phone with NO PHYSICAL keyboard, but on-screen keyboard instead (i.e. HTC Desire), you have a small on-screen button at the bottom left corner of the software keyboard that will simply remove the on-screen keyboard from the screen, revealing the whole screen. The on-screen keyboard on such phones is 'floating' on top of the screen, hiding a portion of it. (I am now referring to HTC phones, as this feature might very well be part of the HTC Sense UI extension on top of the Android generic UI).

I actually have a HTC Desire with Android 2.2, and had the exact same issue with hidden SSID. (Get the perversity: I have an Apple Basestation as my wifi AP.) The 'fix' in Comment #160 is in fact the solution for me.

When I clicked the 'hide the keyboard' button, I indeed have found the Wireless Password field that I obviously did not fill in earlier, and simply clicking the Save button without it did not connected me to my wifi network.

So, in case of the HTC Desire (and I assume all Froyo-compatible HTC phones) this is not a connectivity bug, but a UI flaw.

Comment 206 by ed.matu...@gmail.com, Nov 24, 2010
I am currently experiencing this problem with my Samsung Instinct. I am trying to connect to an unsecured network with a hidden SSID. One user with an iPhone can connect to the network no problem. Another with a Motorola Droid cannot connect. Yet another with a Samsung Galaxy can connect, but he has to remove and then re-add the connection each time.
Comment 207 by fthorl...@gmail.com, Nov 27, 2010
I am having the same problem with the EVO on a hidden SSID with no security. Was able to use it at Panera earlier today. Been playing around for hours and reading all these posts the trying everything. Why has this not been solved yet as it dates back to June of this year. PLEASE GOOGLE, give us a solution as I don't have 4G and need to do video uploads to QIK.
Comment 208 by katherin...@gmail.com, Nov 29, 2010
Running a HTC Desire with a Froyo rom on it - issue still present. Also had issue with HTC Hero in stock donut, stock eclair, and custom froyo.

Yes I have put in the SSID and password correctly - it is not a matter of not being able to see the password box.

This is highly disappointing - in this case, iPhones (and even symbian devices) do have a case where they can claim their phones are more technically capable than any Android device.
Comment 209 by roland.m...@gmail.com, Dec 4, 2010
Hi there, I am having exactly the same problems with an AP with hidden SSID at the office. I read some people talk about the Wifi Connector app, I guess it is this one: http://www.androidzoom.com/android_applications/tools/wifi-connector_kdba.html
I'd like to try it and see if my problem is solv
However, it can not be downloaded at the market at the moment ("Not found").
Can someone maybe post or upload the apk file somewhere?
Thanks!!
Comment 210 by JJHayes...@gmail.com, Dec 6, 2010
Same issue here...

HTC Aria on AT&T running Firmware 1.25.502.2 connecting to Netgear WNR3500L WPA-PSK [TKIP] + WPA2-PSK [AES]

None of the proposed solutions above are working. The only solution I have found is to turn SSID broadcasting on.
Comment 211 by gregtoka...@gmail.com, Dec 15, 2010
I use hiddenssid app, but i wish i did not have to. As long as I can set it to be a preferred network it should auto connect before trying all the other visible nets! (HTC Incredible)
Comment 212 by bobviole...@gmail.com, Dec 15, 2010
I have tried *every* supposed fix on this page with no luck (including Hidden SSID enabler and Wifi Connect in the app store) on my HTC Desire running 2.2

My network is WPA2 and it simply will not connect if the SSID is hidden. If I log into my router, and the only change I make is to enable the SSID broadcast, the phone sees the network and connects within a few seconds.

Please Google, for the love of God, get on this.
Comment 213 by billwit...@gmail.com, Dec 20, 2010
K, if anyone makes it this far down, I'll hope to set you on the right path

Find comment number 14 in this tread, follow the link in the comment and when you read the page, you will understand that all a FIX is doing is setting a 'Hidden SSID' flag in the settings for an 'existing' Wireless connection.

Now that you understand what the FIX does, you can go to 'market' and search 'hidden ssid enabler' and you will find a fix you can download. (Continue reading there's more to this...)

To make it work you must first 'Create the connection'. To do this, you must go to your wireless equipment setup and "Unhide" the SSID you want to connect to. Now your phone can see the connection and you can create the connection normally and it will work.

Once your connection is created and saved -- you can now go to your phone app - "Hidden SSID Enabler", Enter the SSID connection name to flag as hidden (name is case sensitive so you must enter exactly), click "enable hidden ssid" button (they should have put an acknowledgement, but they didn't - so trust that it is now flagged)

Now you can go to your wireless equipment setup and 'Re-Hide' your SSID for your wireless access as it was before.

All will continue to work.

This works for my Galaxy S phone, but if you understand the logic, I don't see how it would NOT work on any android phone that goes through the process listed above.

You can read comments regarding the app here if you would like http://www.androidzoom.com/android_applications/tools/hiddenssid-enabler_rxp_comments.html




Comment 214 by jdavidmo...@gmail.com, Dec 22, 2010
The process in Comment 213 by billwitmur worked for me -- for a while. Doesn't appear to have survived reboot.

My Droid Incredible (2.2) will connect to a hidden network, but it won't stay connected. Once the phone goes to sleep (yes, wifi sleep policy is set to "never"), the connection is lost and I have to "manually" reconnect (just go to list of available networks and after 5-6 seconds it connects to the hidden network).

I followed billwitmur's procedure and it worked all night last night for about 6 confirmed hours -- every time I picked up my phone, wifi was connected. I rebooted my phone this morning (to charge while off), and now it is back to the old behavior of not keeping the connection. I can't exactly log into the router and switch the SSID from visible to invisible every time it decides to lose the setting.

Google, this is a pretty easy fix! Just give us a tick-box to address the "hidden SSID" option when setting up the network! And make it persistent. That should take a programmer about 2 hours to gin up. Make it happen. This is embarrassing.
Comment 215 by gregory....@gmail.com, Jan 1, 2011
I had the issue with my hidden ssid on my htc desire (android 2.2)
so, i read this topic and found very useful info in comment #124. Thanks tinlong0529 !

i have Linksys-Cisco WRT160N router, with ssid broadcast off and security mode wpa2 "TKIP or AES". And exactly in this mode the problem is! Once i switched from "TKIP or AES" to AES my HTC desire conncted to my hidden network.
Comment 216 by smok...@gmail.com, Jan 2, 2011
I also have the problem on my Samsung Galaxy S Fascinate - ver 2.1 Update 1
Comment 217 by Michael....@gmail.com, Jan 4, 2011
Confirming, same thing on Optimus T, android 2.2. If I leave the range of a hidden ssid, when I come back in it does not automatically reconnect. I have to re-save the settings for the network, and then it reconnects (until I leave the area again).
Comment 218 by ari.rapt...@gmail.com, Jan 5, 2011
Confirming, HTC desire HD with froyo..

Comment #214 certainly worked for this problem..but in my case the apps won't let my wifi scan any un-hidden ssid, so certainly I'm not that satisfied with it.

And yeah like someone said before 3rd party apps install fix certainly like fixing bug with another bug
Comment 219 by a.robe...@europeandirectories.com, Jan 10, 2011
Hit the same problem with a ZTE-Blade (Orange San Francisco) on 2.1, attempting to re-connect to a remembered WEP network with a hidden SSID.
Comment 220 by hastaque...@gmail.com, Jan 12, 2011
Same problem, maybe some of the tricks posted here may work, but I think that it's embarrassing that android can't keep a connection with a wifi network with a hidden ssid.

Hope that google fix it soon.
Comment 221 by packetkn...@gmail.com, Jan 13, 2011
Nexus S running 2.3.1 stock has this problem against two Netgear routers I have access too but seems to connect fine to a corporate Cisco router. All non-broadcasting SSIDs. Same APs using BB Torch connects and stays connected fine.
Comment 222 by ja...@jmdassoc.com, Jan 14, 2011
FWIW, my BB Bold and iPhone connected fine to my Netgear wireless router. Now my last three phones (within the past year: BB Torch, G2 & My Touch) do NOT connect to my router no matter what I do (hidden/not hidden, open/protected, etc.)
Comment 223 by Raul.Ped...@gmail.com, Jan 17, 2011
I didn't read all comments in this thread so sorry in advance if someone already mentioned this. I have a HTC Droid Incredible that was running on an old D-Link router. I never had any problems re-connecting using a hidden SSID. Recently upgraded to a NetGear dual band router using WPA and began having this problem. Have the router set up with a separate SSID for b/g connections only. Droid would connect no problems when I broadcast the SSID but would not re-connect when it was hidden. Attempts to connect and create the connection manually while the SSID was hidden resulted in the same behavior.

On a hunch I then un-checked the check for open networks option, created and connected manually to my network with the SSID still hidden, and it now re-connects every time. I repeated this several times to make sure it was no glitch. I then re-enabled the look for open networks and it continued to re-connect each time. Again I deleted/forgot the network and repeated these steps to make sure it was repeatable. This might be specific to my router or phone but wanted to pass this along in case it helps anyone with this issue. I have a feeling there is a bug here with logic that normally detects hidden networks being skipped when the open networks option is checked or something along those lines.
Comment 224 by marc.tho...@gmail.com, Jan 20, 2011
Originally Posted by wormser
I found a real solution to not being able to connect to a hidden SSID. Try this first.

Check your router mode to see if it is in Auto, B or G only. Then change the mode on your router to B and G. I connected right away.

Eureka! For anyone using a router similar to my linksys, you wont find a setting for 802.11 b or g or n or whatever, but setting it to 54mbps is the same thing.
Comment 225 by mattshor...@gmail.com, Jan 28, 2011
Peas and Rice! this issue is more than 2 years old. this really should be sorted out.
anywhoo. my samsung galaxy 5 is doing something similar. our router is set up on broadcast SSID and has WEP. now i had this issue and i sent it away to get repaired and the company said they did a full software re-flash and did a "RF live test" and it met all criteria. now we got it back just 2 days ago and it worked swimmingly for 1 day and then i put it on charge overnight and in the morning it wouldn't comply. it was doing EXACTLY the same thing as before. then i restarted the phone. now things changed from here on, instead of dropping the connection then saying it couldn't see it, it said that it was remembered and all but it could still see it with the appropriate strength of the connection. it would be "obtaining ip" until it timed out. now is this completely a software fault or is it hardware? I need to know as we are trying very hard to get out money back from the company that sold us the phone and this information could be helpful.
cheers chaps
Comment 226 by djd...@gmail.com, Feb 9, 2011
google, wtf?
2 years for bug fixing is quite enough.
Comment 227 by andreas....@gmail.com, Feb 12, 2011
I agree and have the same issue with many others!!! I actually like Android but there are way too many issues that remain unchanged! Because of that Ibwas hoping for a great MeeGo OS (I mean Nokias Symbian didnt have a nice touch interface but the OS was almost bug free and everything just worked, if however too slow on many devices). But retarded Steven Elop had to smash my hopes.
Comment 228 by grsch...@gmail.com, Feb 13, 2011
I concur this issue should be fixed... but here is what I got to work for me after reading everyone else's posts:

Phone: HTC Desire, recent upgrade to android 2.2
Router: Linksys E2000 (recent upgrade from netgear non-N router)

I upgraded the router and to 2.2 within a few days of each other so not really sure if one or the other or a combination of the two is the problem since I didn't happen to check the phones WiFi after the router and/or phone change. I only noticed it when I went to use a network file browser on my phone and couldn't find my local network hard drive.

Router config:
SSID hidden
Network mode - mixed (because I have N and non-N devices)
Security mode – WPA2/WPA mixed mode

Simply wouldn't connect when manually setting up the SSID (and yes, had password and correct security type set on phone). Tried the tools mentioned: HiddenSSID, WiFi advanced configurator, Wifi scanners, etc. – nothing helped

Based on comment 167 of setting to fixed network mode (e.g. N only or B/G) and comment 169 that the phone does N (at least their phone), I decided to try N only on the router just to see if it would work. But when I did, the router said can't because the current security mode didn't support N only (see sec mode above).

I changed the security mode to "WPA2 Personal", left the network mode as mixed (so that I can use my N and non-N devices) and voila! My phone connected.

So it appears that it is the "WPA2/WPA mixed" security + "mixed" network mode + Hidden SSID causing this.

New router config:
SSID hidden
Network mode - mixed (because I have N and non-N devices)
Security mode – WPA2 personal (new setting)

Hope this helps!

(Hopefully I don't find that any of my devices can't use WPA2. If I do, I will go back to WPA/WPA2 mixed security mode and use the WiFi advanced configurator tool to try and force the phone to do WPA or WPA2 or may try comment # 213)



Comment 229 by hos...@runbox.com, Feb 21, 2011
hmm i have a galaxy tab that has had no problem connecting and disconnecting and reconnected to our hidden network using WAP. We are using a cisco AP at my work though i couldn't tell you which one.
Comment 230 by ruudh...@gmail.com, Feb 23, 2011
Same problem on Desire Z with Android 2.2 ...
Changing from mixed WPA/WPA2 to WPA2-only did not work. Hidden SSID Enabler in market did not work either. Setting protected mode on did not work. 802.11n-only did not work. Different wireless channels tested. Environment is relatively busy (lots of networks can be found) but all other networks are much weaker so the hidden one should stand out.

The router is a surprisingly stable and fast Belkin N. I hope to see this one fixed in Android 2.3 when HTC finally releases the update. If not: please fix it asap as a patch.
Comment 231 by adampsbr...@gmail.com, Feb 26, 2011
Same problem with my Desire HD(2.2) and GSM Hero(2.3). I've had to choose "up to 54mbps" for hidden SSID on my netgear router to work. Not ideal but it works.
Comment 232 by camille....@gmail.com, Feb 28, 2011
I have the same issue :(
Comment 233 by derekmit...@gmail.com, Feb 28, 2011
Confirm problem is still happening.

We had a Linksys Router (base model b/g; internal antenna) and had to swap it for a Netgear router. Wife has Droid Incredible and I have the Droid X. Droid X works with no problems. The Incredible is has the same issue as everyone else. When connected to the Linksys, there were no issues with either phone.

Tried the steps from comment 213 and 223, but neither fixed my issue.

Software: Android 2.2 )both phones)
Router: Netgear Wireless-N 150 WNDR1000 v2
Security mode: WPA2 personal
SSID hidden
Network mode: Mixed (b/g/n - up to 150 Mbps)

Comment 234 by elind...@gmail.com, Mar 5, 2011
Issue seems to be fixed on nexus one, android 2.3.3
Comment 235 by hamlinst...@gmail.com, Mar 20, 2011
I have this issue too

Comment 236 by Christia...@gmail.com, Mar 22, 2011
I have the same issue. Brand-New T-Mobile Motorola Charm running Android 2.1. My router is a Linksys Wireless-G and my network has a hidden SSID and uses WPA. I had been using an iPhone 4 that worked like a charm. I swapped for the Motorola Charm just because I wanted a physical keyboard. Now I can't use WiFi.. ((
Comment 237 by prathaba...@gmail.com, Mar 29, 2011
i have the same problem it says remembered secured with somethin then goes to the bottom sayin not in range, remembered grrr lg gt540
Comment 239 by denis.va...@gmail.com, Mar 31, 2011
I HAVE FOUND A WORKAROUND:

I have HTC Desire (2.2). My phone was unable to find fully setup home network with hidden ESSID. Switching security mode from WPA2 to WPA or from WPA to insecure WEP never helped.

However, as soon as I switched encryption from AES to TKIP it worked!!!

Although the workaround is found, lets us rephrase the bug: why on earth Android does not support Wi-Fi networks with hidden ESSID and AES encryption?
Comment 240 by rhashem...@gmail.com, Apr 9, 2011
wasted a good hour on this before i googled and found this forum. unbelievable that hidden ssid issue is still unresolved. android 2.2 on htc incredible.
Comment 241 by pavel.le...@gmail.com, Apr 9, 2011
Hello everybody,

I have the same problem. Hidden SSID - no connection. But, I have managed to go around and get it working for me.

This is my setup:

Htc Desire Z (according to htc.com with b/g/n WiFi adapter), Adroid 2.2
Htc Wildfire (according to htc.com with b/g WiFi adapter), Android 2.2 (upgraded from 2.1 using official update)

Previous router: Netgear WGR614 v7 (54Mbps b/g)
New router: Netgear WNR1000 v3 (150Mbps b/g/n; but only fully implemented and certified is b/g - based on manufacturer's info)

Situation:

when I was using old router I had no problem at all. WiFi setup was 54Mbps b/g, WPA2-AES, DHCP with static leases, hidden SSID - Both phones were working without any issue.

Then I had that great idea to change the router to a new one. My choice was as indicated above. I set it up in the same way as the old one. Hidden SSID, WPA2-AES, DHCP.

Then I discovered the problem: all WiFi devices were doing wery well except those two phones mentioned above. On both of them it was displayed: 'remebered, not in range' [network notification was disabled on both]. Passphrase and security mode was cheched 10 times and cross-checked with old router. All perfect.

Then I had an idea. I switched new router from 150 Mbps to standard 54Mbps; and Voila! done. Both phones connected instantly. After that I have checked how it works with secend possible option: 72Mbps - did not work, same as 150Mbps does not work.

So finally I decided to stay with 54Mbps. This enables me to use those two phones along with other devices.

This is how Netgear explains its modes:

Up to 54 Mbps. Legacy Mode, with a maximum speed of up to 54 Mbps for b/g networks.
Up to 72 Mbps. Neighbor-Friendly Mode, with a speed of up to 72 Mbps in the presence of neighboring wireless networks.
Up to 150 Mbps. Performance Mode, with a maximum Wireless-N speed of up to 150 Mbps.

Conclusions? I am not really sure.
- Is it an android issue (not fully up-to-date wi-fi protocols implementation)?
- Is it just the way routers manufacturers implement N protocol in their devices?

Hope it will work for you.
Comments?
Comment 242 by automove...@gmail.com, Apr 10, 2011
Hello,

I've had the same issue with HTC desire running Android 2.2 (FROYO). Previous router was a Netgear DGN2000 without issue.

Recently upgraded to a DrayTek Vigor 2820Vn and immediately had the same issue with not being able to connect to hidden SSID. I had tried every suggested workaround in these posts without success. Including trying to using 'Hidden SSID Enabler'.

After reading Comment 241 I though I'd try something different and set up a 2nd Wireless LAN (SSID) on the router, This is a feature of the router, not sure if it can be done on other routers/brands.

I downloaded 'WiFi Manager' from the Market place to assist in setting up network on phone.

https://market.android.com/details?id=org.kman.WifiManager

To my amazement it has worked with the following parameters;
Wireless LAN Mixed Mode g/n
Hidden SSID
WPA2-PSK with AES encryption

Now works and I've tested it by connecting/disconnecting from network, putting phone into flight mode and back on, phone on/off & router on/off. However I cannot I still cannot replicate this on the first Wirless LAN (SSID).

Hope that this helps.

Cheers and best of luck.


Comment 244 by R3t1...@gmail.com, Apr 10, 2011
I noticed in "WiFi Manager" that the channel was showing differently than the network was set. So I played around and tried several different channels. I was able to get it to work momentarily by changing the channel on the router to match the one that wifi manager said it was on. That didn't last though as it disconnected and wifi manager proceeded to show the wrong channel again (i later realized that Tomato takes quite some time to change channels, about the same amount of time as the connection was working). I am using Tomato Firmware + N-Only + Hidden SSID. The combination is nearly (can work momentarily) unusable but unhiding the SSID fixes it. I did try cutting the speed back but that had no effect. So I figured out that in 40mhz N mode the wifi manager displays the channel as the number between the two channels it uses. Upon reading up on the standard I found that European devices have a different scheme for this, so be sure that your device is set to the US region.

At one point I thought I had found a combination that worked but so far the only reliable solution I can find is to enable SSID broadcast. Disappointing.

LG Ally, 2.2.1, Hidden SSID Enabler, WiFi Manager, Tomato firmware on Asus NT-R16
Comment 245 by automove...@gmail.com, Apr 12, 2011
Hello All,

I posted comment 242, sadly I must report that despite working on the day once I took the phone to work and brought it back home it will no longer connect to the hidden network.

Strange that it was okay and now just won't work.

Come on Google it's not good enough my iPhone has it down pat!
Comment 246 by sobi...@gmail.com, Apr 14, 2011
this issue still on 2.3.....I tried sth. like hiddenssid enabler...
Comment 247 by peternic...@gmail.com, Apr 21, 2011
This defect needs addressing asap. The whole of my work place has a hidden wireless network that everyone can connect to except Android users. I haven't been able to connect once.
-Menu
-Settings
-Wireless & networks
-Wi-Fi settings
-Add Wi-Fi network
-Enter SSID
-Security (WPA/WPA2 PSK)
-Tap save
-Appears at the top of the list with message "Not in range, remembered". There is no connection. If I exit settings and go back into Wi-Fi settings, the SSID for the hidden network is gone.

HTC Desire Android 2.2
Comment 248 by mirrorim...@gmail.com, Apr 25, 2011
grr just flashed my W6.5 HTC HD2 to Android 2.2.3 - and lo and behold I can't connect to my broadcasting wifi point - Security (WPA/WPA2).
Same issue says it's not in range.
I even flashed it with two different versions and same thing each time.
Mine's not even hidden.
Comment 249 by shahulha...@gmail.com, May 1, 2011
wow. I changed to Android thinking it would be best... Now I dont have connection to wifi...

confirming the problem in HTC Desire HD with Android 2.2
Comment 250 by blackwat...@gmail.com, May 8, 2011
please try to upgrade this issue in HTC DESIRE HD me to cant connect the hidden network in my office
Comment 252 by skywonde...@gmail.com, May 15, 2011
Same with Suntoo E86 tablet. Connects to my access point, which is Asus RT-g32, but disconnects after a few seconds. Quote annoying. Tried everything from this topic but with no luck.
Comment 253 by Johansso...@gmail.com, May 22, 2011
To Peter in #247
Please note the password field as well when you add Wifi connection (is located below the security field)

I just found this bug after I stopped broadcasting SSID (ciso hw)
I got it back up by the following (all covered in posts above)

- I shut of Notification of open networks as given in #111
- After that I had to remove the Entry I already had since before I stopped the SSID broadcasting as it didn't reconnect to this (was greyed out)
- I then added a new entry (same as I just removed) Enter SSID, security AND !PASSWORD!

After that it connected again, and I have tried disabling/enabling Wifi and restarting the phone and it still reconnects fine..

Router: WPA/WPA2 PSK, AES
802.11 G network

Phone: Desire S, Android 2.3.3, Kernel 2.6.35.10
WPA/WPA2
Comment 254 by wow010...@gmail.com, Jun 4, 2011
re: Comment 228 by grsch...@gmail.com, Feb 13, 2011

The work-around solution described in Comment 228 worked for me with my Netgear WNR2000v3 router. Changing the router mode setting to "Up to 54 Mbps" instantly fixed my Android's connectivity problem. Hidden SSID, WPA-PSK [TKIP] + WPA2-PSK [AES] is working on my Samsung Moment phone.
Comment 255 by serg...@gmail.com, Jun 14, 2011
So is there going to be an update for this BUG ?
It is addressed for more than 2 year ... !?
Comment 256 by abdullah...@gmail.com, Jul 10, 2011
i also have that issue
Comment 259 by inertia2...@hotmail.com, Jul 14, 2011
Confirmed issue using Live Android x86 on Asus eeePc 901.

With hidden SSID on router using WPA2-PSK encryption I cannot connect.
Turn off hidden SSID and PC connects fine.

Live Meego 1.2 also has same problem on the 901 so assume it's a Linux driver issue related to the wireless hardware used in this PC.
Running same Live Android on a Asus eeePC 1005HA connects fine to the hidden SSID router.
Comment 260 by clayton...@gmail.com, Jul 16, 2011
Fixed for ME!

Having the same issue with an HTC Evo Shift. I'm running a Netgear router that's capable of running wireless - n. I tried the Hidden SSID app, didn't work. The only thing that worked was changing the mode in the router. Once I changed it to up to 54mbps (B or G) it connected and worked fine right away. Still not a great solution, but it works.

Comment 261 by droidd...@gmail.com, Jul 19, 2011
How has this not been fixed? Droid X disappointed.
Comment 262 by bd1...@gmail.com, Jul 23, 2011
Same issue, Sprint Samsung Epic. Was able to connect to my hidden SSID 802.11 network until installing the most recent Android update.
Kernel 2.6.32.9
Firmware 2.2.1
Comment 263 by giri.sa...@gmail.com, Jul 28, 2011
I have the same issue on two Android devices. At least I think it's the same issue. Here is what I have:

WiFi Setup:
Hidden SSID
WPA2 Security

Devices:
HTC Aria (AT&T & Android 2.2.2) - Connects and loses connection (not in range).
Dell Streak 7 WiFi (Dell stock & Android 2.2.2) - Connects and randomly drops out or shows not in range.
BTW:
Viewsonic G Tab (CM7 Android 2.3.4) - Connects just fine!
Samsung Captivate (CM7 Android 2.3.4) - Connects just fine!

Here is what I did that seems to have helped on both non-working devices:

Added the WiFi network manually. Entered the SSID and the corresponding password; I let it find the network and connect (and then disconnect of course!).
Then, I created a second WiFi network with the same SSID and selected it to have no security settings ("Open"). As soon as I did that, the devices connected to the correct network and stayed connected!

Result:
There are two visible entries listed under my networks with the SAME SSID, but just the one with encryption connects of course.

Don't ask me how I came up with that, but it's kept my wife's Aria connected for the last 8 months, and it seems to be keeping the Streak connected as well over the last two days. I also used to own a Velocity Cruz that had the same problem and same solution.

Obviously, there is something with the coding in that version of Android because I've seen the problem across multiple manufacturers and devices. I hope this helps anyone else with this!
Comment 264 by greenth...@gmail.com, Aug 9, 2011
Brand new Nexus S 4G. Same issue, cannot connect to hidden network with WPA2 security. Connects to visible networks just fine.
Comment 265 by chrisada...@gmail.com, Aug 29, 2011
Got solution for my HTC Desire S, might be useful for others.

By default my AP works in mixed b/g/n 802.11 mode, in this case HTC Desire S can't connect to Hidden SSID, I tried using all the apps that were talked about above with no joy, then I changed it it b/g mode only, channels didn't matter with me and set the signal to 20Mhz.

Comment 266 by victorfdezdb88, Aug 31, 2011
Okay happens the Same to me, theres even an option to connect to it in case the point isnt publishing its name... epic fail Google, you must fix this.

Got a Galaxy 3, i5800.
Comment 267 by mwoo...@gmail.com, Aug 31, 2011
me too. using Samsung Epic 4G. sees 17 other networks. Can't see the AP I'm standing next to, that I entered manually. my MacBook can use it fine. in fact, it's the one i'm using right now to enter this comment. cmon, Google. really?
Comment 270 by Dry...@gmail.com, Aug 31, 2011
The Android WiFi connection is atrocious. I have been experiencing problems since day one with my Nexus One.
When I'm at home on a WPA2 network, the connection is fine.
At school, or at the hospital, or anywhere else BUT home, the connection is bad, regardless of signal strength. It will cycle and cycle and never connect. Then finally it will connect, and stay connected fine, for a while. But eventually it will disconnect again and the adagio continues.
My iPod Touch connects fine wherever I go. Seems like Android would have this whole WiFi thing figured out by now! What are we up to, 2.3.4? Cmon people this is basic stuff!

"Medium" priority. Shouldn't the basic operation of a device be top priority? Get the base FUNCTIONALITY working and THEN figure out how to stream crappy movies or link to Facebook or whatever all the cool kids want these days. None of that stuff matters if the phone wont connect in the first place! Hence we're left with a bad user experience despite the number of features or capabilities.
Comment 271 by henderso...@gmail.com, Sep 8, 2011
I'd say that the reason that this is "medium" is because the b/g only fix seems to work. I changed my router over from b/g/n to b/g and it worked fine.
Comment 272 by heymatta...@gmail.com, Sep 9, 2011
Used 201's solution when I had this problem with my old Droid tryign to connect to my home WPA2-Personal protected network with broadcast SSID:

THE ONE THING I DID DIFFERENTLY HOWEVER WAS TO RESTART MY PHONE. IT DIDNT WORK UNTIL I RESTARTED!!!


Comment 160 by beowurk, Aug 16, 2010

Fixed!

I had this problem on an HTC Desire running 2.2 Froyo and attempting to connect to a WPA-PSK secured network with a hidden SSID. Tried HiddenSSID Enabler as well as turning wifi on and off and several other workarounds here, nothing worked - the network would just say "Not in range, remembered" and then eventually disappear from the remembered networks list without ever attempting to connect.

Turns out that it was a problem with the interface all along!

WHAT I DID ORIGINALLY:
-Turn on Wi-Fi.
-Select "Add Wi-Fi Network". The Add Wi-Fi Network dialog appears, along with the keyboard covering the bottom half of the screen.
-Note that the visible fields are "Network SSID", "Security" and the Save and Cancel buttons.
-Enter the network SSID as normal.
-Select WPA/WPA2 PSK under Security.
-Note that the visible fields remain unchanged - Network SSID, Security, Save and Cancel are visible.
-Press the Save button.
-Expect to be prompted for WPA key. Not prompted for WPA key.
-Note that the resulting network entry does not connect and reads "Not in range, remembered" until it is auto-removed some time later.
- :( !!! Frustration, etc. Look for workarounds, gawk in fascination at such an elementary bug remaining in the Android codebase, consider complaining loudly et cetera.

WHAT I DID TO MAKE IT WORK:
-Turn on Wi-Fi.
-Select "Add Wi-Fi Network". The Add Wi-Fi Network dialog appears, along with the keyboard covering the bottom half of the screen.
-Note that the visible fields are "Network SSID", "Security" and the Save and Cancel buttons.
-Enter the network SSID as normal.
-Select WPA/WPA2 PSK under Security.
-Note that the visible fields remain unchanged - Network SSID, Security, Save and Cancel are visible.
-HIDE THE KEYBOARD!
-Note that a previously-hidden field has appeared, entitled Wireless Password!
-Enter the WPA key in the Wireless Password field.
-Press Save.
-Note that the wireless network connects successfully almost immediately and is subsequently remembered/auto-connected to when in range/everything else that one would reasonably expect.
-Facepalm at the Save and Cancel buttons being allowed to float up to obscure a critical field.

So, there you have it. The Save and Cancel buttons are obviously of a UI class that is allowed to float above the keyboard, but in this case it seems to have generated a great deal of needless confusion and trauma. Some of the problems reported under this bug may well be arising from simple user error thanks to this non-intuitive behaviour.

Consider opening a separate bug to prevent this float-and-obscure behaviour, please. People are going to think that Android can't do something as simple as connecting to a Hidden SSID, which is absolutely laughable and is a really really bad look.
---------------------------
Not sure about a couple of lines in the 'fix' portion that begin with:
-HIDE THE KEYBOARD!
-Note that a previously-hidden field has appeared, entitled Wireless Password!

Not sure what is meant by 'hide the keyboard'. I tried literally hiding the keyboard on my daughter's flipout and then hiding the password (toggle on/off, etc) to no avail. Also would like to know more about the UI class that's allowed to float above the keyboard comment too. Gee, I almost wish I had leaned harder toward an Apple. My daughter has an Itouch that connects just fine to our hidden SSID wireless net. Also was very disappointed in a piece of advice on the motorola forum which advised me to just broadcast SSID since it doesn't do nuttin anyhow..

Thought I'd heard it all...

Appreciate this forum - if I can get this solved, I too will try to post solution.
Comment 273 by julie...@gmail.com, Oct 22, 2011
Fix this already, same issue here. hidden ssid, open wifi, can't connect. Getting "obtaining IP address" forever.
Comment 274 by chrisj...@gmail.com, Nov 14, 2011
I followed the advice of changing my wireless router down to slowest setting - "Up to 54Mbps" - and instantly the phone reconnected to it. It seems you have to choose between either having a hidden SSID or a fast wireless network - but not both!

I tried both HiddenSSID and Wireless Manager, but neither app helped in the least.
Comment 275 by kisme...@gmail.com, Nov 17, 2011
Hello Everyone...I got mine fixed. I had a T-mobile Mytouch 3G slide and it never had an issue connecting to my Hidden wireless network with WPA2. My wife still has her Mytouch 3G Slide and her phone has no issues. My HTC Sensation 4G has never been able to connect to my hidden SSID with WPA2. I noticed that the first letter in my SSID is capital, but i always type it all in lowercase in the phone. I tried typing the SSID with the first letter capitalized and it connected with no problem. I don't know if this will work for everyone, but it's worth a shot. Looks like the SSID is case sensitive?
Comment 276 by Omar...@gmail.com, Nov 24, 2011
Hi everyone i had experienced the same issue of being unable to connect over wifi using a hidden ssid.

Phone motorola razr (uk version of the droid razr) android version 2.3.5
router netgear dgn3000v2
-hidden ssid
-wpa2
-preshared key
-broadcasting @ 300 mbps 5ghz and 54 mbps @ 2.4ghz (802.11 b/g/n)...

Firstly i had noticed that if i enabled ssid at these settings then my phone would connect without any hick ups. As soon as i hid the ssid then my phone would display a disconnected status, and under advanced view it claimed the router was not in range. I became frustrated at this point whilst my nexus s was still able to maintain its connection. I've read that there was an "hiidden ssid enabler" app on the marketplace and it sounded exactly like what i wanted however i was a bit reluctant to use a third party app.

Now my fix allows me to connect over a hidden ssid network using wpa2 .....
it just required me to change the broadcast settings on the router from the above to ... broadcast 300 mbps @ 2.4 ghz only. This change still broadcast in the 11n channel
Comment 277 by hairud...@gmail.com, Dec 21, 2011
My Galaxy Y with Android 2.3.6 had the same issue.
Comment 278 by s.john.b...@gmail.com, Dec 23, 2011
HTC Explorer 2.3.5
Hidden SSID didn't work
Added 2nd network as per 263
Now connects to hidden SSID
Comment 279 by beelz...@gmail.com, Jan 3, 2012
Same problem with Samsung Galaxy S2 Skyrocket, Android 2.3.5. Could not connect to hidden SSID. Using WPA2. The workaround in Comment 263 to add a 2nd (duplicate) network entry with the same SSID, except set it to Open, makes it work. After adding that duplicate entry, it connects to the hidden SSID with WPA2.
Comment 280 by southi...@gmail.com, Jan 4, 2012
Sony Ericson Xperia X10 Mini Pro (U20i)
Android 2.1-update1
TP-Link TL-WR1043ND, firmware 3.13.4

Phone would only connect to router if SSID was visible.

Creating a duplicate entry with security set to Open did not work.
I didn't try any of the apps or scripts suggested above.

Two router settings changes fixed for me (neither worked on its own):

1. Force AES encryption, instead of Auto TKIP/AES.
2. Disable WMM (Wireless Multimedia Extensions).

AES shouldn't be a problem, but not yet sure about WMM.

Obviously this is only a fix where you have admin access to the router, & the changes don't affect other users.

Comment 281 by t...@treworld.com, Jan 13, 2012
I had the same problem on the Galaxy Nexus the other day. I thought it was my router at first, but it turns out it was indeed the phone's fault. It connected after I rebooted the phone.
Comment 282 by dennis.v...@gmail.com, Jan 27, 2012
While my HTC Legend with Android 2.2 on board didn't have this problem, my new Desire S with 2.3 refuses to see hidden wi-fi router. So I can confirm this problem.
Comment 283 by pepie...@gmail.com, Feb 15 (6 days ago)
Solution:
* go to router settings, make your SSID visible
* connect with phone, save network
* go to router settings, make your SSID invisible

Finish...
Next time, phone will connect to your hidden SSID


http://forum.xda-developers.com/showthread.php?p=18671906#post18671906
I have a XPERIA X10 mini, rooted, running Android 2.1 update 1.
At home I have setup a wifi network, that has a non-broadcasting SSID.

Though I have setup my phone to connect to this SSID, my phone will report the Access point as "not in range, remembered".

When the Router is configured to broadcast the SSID, my phone will automatically connect.

Here I will describe the steps I followed to enable my device to detect a non-broadcasting SSID.

1. ROOT your Android Mobile
2. Get a tool to browse through the system areas of android
I used Shell Commander (to complete it smoothly). I shall explain why, later.
3. Navigate to /data/misc/wifi/
In shell commander, you have a graphical folder navigation.
The command will be cd /data/misc/wifi
[You can skip the next step of taking backup]
4. For backing up, copy the file wpa_supplicant.conf preserving its attributes.
This is the reason I needed shell commander.
The command will be, cp -p wpa_supplicant.conf wpa_supplicant.conf.bak
5. Edit the entry for the non-broadcasting network in the wpa_supplicant.conf file.
The content will be as below.

ctrl_interface=wlan0
update_config=1

network={
ssid="No Broadcast SSID Main"
psk="SsIDMainPassword"
priority=17
}

network={
ssid="SSID2"
scan_ssid=1
psk="password2"
priority=14
}

network={
ssid="SSID 3"
scan_ssid=1
psk="password3"
priority=15
}
add scan_ssid=1 to the non-broadcasting entry


ctrl_interface=wlan0
update_config=1

network={
ssid="No Broadcast SSID Main"
scan_ssid=1
psk="SsIDMainPassword"
priority=17
}

network={
ssid="SSID2"
scan_ssid=1
psk="password2"
priority=14
}

network={
ssid="SSID 3"
scan_ssid=1
psk="password3"
priority=15
}
save the file.
6. Enable the Wireless in your mobile.

Having done this, the WiFi connection, corresponding to the edited entry, will be connected even if not broadcasted (provided the Access Point is indeed available).

Points to be noted while doing this.
1. The wpa_supplicant.conf file should retain all its attributes as is. While saving the file, if the permission group changes from "wifi" to "root", as it did for me, you will never be able to enable WiFi ever again. There is no way you will be allowed to set the user group for the file to "wifi", as such a group is stated to be invalid. In shell commander, I was able to retain the attributes, but had problems when I used ES-Explorer.
2. The double quotes (") around the SSID name and the Password are necessary. While saving in Shell Commander, the double quotes were not saved. I forced it to include quotes, by putting a backslash escape sequence (\").