Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Googles G1 kommt am 2 Februar -
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 55
Mittwoch, 21. Januar 2009
Strict Standards: Non-static method nggallery::get_option() should not be called statically in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line
10
Nun kommt das Android Smartphone G1 auch bei uns in Deutschland auf den Markt. Am 2. Februar soll es soweit sein. Es wird wie schon zu seiner Zeit das Apple Iphone nur bei T-Mobile zu haben sein. Da T-Mobile die Exklusivrechte für das G1 in Deutschland hat.
Auf der T-Mobile Webseite kann man das G1 bereits vorbestellen. Die Tarife und damit verbundenen Preise finden Sie unten auf dem Bild. Wie man dort auch sieht gibt es das G1 in Weiß und Schwarz. Bei der Auswahl eines der verfügbaren Vertäge sollte auf das Datenvolumen geachtet werden, da das G1 Mobile im Hintergrund immer wieder Daten aus dem Internet zieht und es somit ohne einen entsprechenden Datentarif schnell teuer werden kann. Das Android G1 gibt es auch für 450€ ohne Vertragbindung.
Der wesentliche unterschied zum Apple Iphone ist die integrierte Tastatur. Dadurch ist aber auch das Gewicht vom G1 wesentlich höäher als beim Iphone. Einen Datenvergleich gibts hier: Iphone gegen G1
Das G1 Handy kommt zwar mit einem intergierten GPS zur positions Bestimmung daher, aber es wird keine Navigationssoftware mitgelifert und somit muss man sich entweder eine beschaffen oder mann kann auch eingeschränkt mit Google Maps zurecht kommen.
Quellen und weitere Berichte:
http://www.golem.de
http://www.pocketbrain.de
http://blog.telefon.de
http://blog.tameco.de
http://www.insidepda.de
http://www.magejo.de
http://www.fscklog.com
http://www.silicon.de
http://jars.de
Tags: Android, februar, g1, t-mobile
Veröffentlicht in Alte Themen | Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Android Browser wieder wasserdicht -
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 55
Dienstag, 04. November 2008
Strict Standards: Non-static method nggallery::get_option() should not be called statically in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line
10
Vor zwei Wochen hatte die Sicherheitsfirma Independent Security Evaluators (ISE) eine Sicherheitslücke im T-Mobile G1 Android Browser gefunden. Dies war wohl vor dem offizellen Verkaufsstart am 22.Oktober.
Die Firma hatte Google und die öffentlichkeit über die Sicherheitslücke informiert und das passte Google garnicht, so kurz vor dem Start. Nun gibt es ein offizelles Update für das T-Mobile G1 mit dem die Sicherheitslücke behoben wurde. Durch diese konnte , wenn man eine Webseite mit dem Android Browser aufruft, fremder Code auf das Smartphone gelangen und so z.B. Userdaten ausspioniert werden.
Quelle: pocketbrain.de
Tags: Android, g1, google, sicherheit, t-mobile
Veröffentlicht in Alte Themen | Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Android Market - Statistik -
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 55
Samstag, 01. November 2008
Strict Standards: Non-static method nggallery::get_option() should not be called statically in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line
10
Nun gibt es seit einiger Zeit das Smartphone Betriebssystem Android und damit auch das Software Portal Android Market und es wäre doch mal interessant, wieviel und was dort herruntergeladen wird. Von seiten des Android Konzortiums gibt des dazu keine Auskünfte. Jedoch wurden wir im Blog von Medialets fündig. Das Unternehmen ist ein Mobiles Advertiser Netzwerk, jedoch konnte ich nicht herraus finden wo genau diese Daten herkommen. Aber interessant ist es alle mal und deshalb hier die Higlights der Statistik:
- Es wurden 164 Programme gedownloaded und das, zwischen 667.000 und 2.9 Millionen mal.
- Pac Man und und ein Wetter Kanal Generator wurden am häufigsten herruntergeladen.
- Seit dem Launch sind drei mal so viele Programme wie beim Start hinzugekommen.
- Nach einer Woche ist das Download Volumen um 80% gestiegen
Alles andere gibts auf der Seite http://www.medialets.com/blog/2008/10/31/android-market-unleashed/
Tags: andoid, market, statistik
Veröffentlicht in Alte Themen | Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
OpenMoko - Android Smartphone -
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 55
Freitag, 31. Oktober 2008
Strict Standards: Non-static method nggallery::get_option() should not be called statically in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line
10
Die Gerüchteküche brodelt, laut dem Blog Androidguys.com arbeitet das Opensource Projekt OpenMoko schon einige Zeit an einer FreeRunner Version mit dem Mobile Betriebssystem Android von Google. Die Entwicklung soll schon weit vorangeschritten sein und erste offizielle Meldungen soll es schon im November geben.
Das neue Smartphone soll wahrscheinlich den Namen GTA02 erhalten undvon den technischen Daten vergleichbar mit dem Modell FreeRunner sein. Bisher hat OpenMoko fast keine Marktanteile, jedoch wenn Sie das neue Mobile schnellst möglich auf den Markt bringen dann könnte dies sicher ein paar Prozent im Heiß umkäpften Smartphone Markt bringen. Denn bisher gibt es lediglich das T-Mobile G1 mit dem Android Betriebssystem.
Na mal schauen, also das FreeRunner Smartphone konnte mich nicht wirklich begeistern.
Tags: Android, freerunner, gta02, openmoko
Veröffentlicht in Alte Themen | Keine Kommentare »
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line
55
T-Mobile G1 Android Emulator -
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 41
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 50
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 52
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 54
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d193375463/htdocs/ppcps/blog/wp-includes/functions.php on line 55
Dienstag, 07. Oktober 2008
Strict Standards: Non-static method nggallery::get_option() should not be called statically in
/homepages/26/d193375463/htdocs/ppcps/blog/wp-content/plugins/nextgen-gallery/nggfunctions.php on line
10
Auf der T-Mobile Webseite gibt es nun einen G1 Android Emulator, mit diesem kan man das Smartphone mit dem Google Betriebssystem Android online testen. Und es gibt eine animierte 360Grad Ansicht des Smartphones. Bei dieser kann man das Mobile drehen und auch die Tastatur interaktiv herraus schieben. Eine nette spielerei um sich das T-Mobile G1 etwas näher anzuschauen. Dabei ist mir auch aufgefallen das es nur eine Kamera auf der Rückseite gibt. Jetzt fragt Ihr euch bestimmt was daran komisch ist. Es ist Merkwürdig 
oder einigartig weil das Mobile mit UMTS die Möglichkeit der Videotelefonie bietet und normarlerweise bei allen anderen Modellen mit UMTS auch auf der vorderseite eine Kamera für die Videotelefonie vorhanden ist. Und dies das mir einzig bekannte ohne diese zweite Kamera. Ich finde dies aber sinnvol da man eh bei der Videotelefonie ein Headset oder die Lautsprecher funktion nutzt und es von daher wenig sinn macht eine zweite Kamera einzubauen.
Zurück zum Emulator, dieser ist leider sehr langsam und ab und an garnicht zu erreichen da einfach zu viele Leute auf die Webseite zugreifen wollen um einen ersten Blick auf das erste Android Smartphone zu werfen. Bei mir hat das Laden ca. 5min gebraucht, also nicht nervös werden wenn es etwas länger dauert. Auf jedenfall wird man für das warten belohnt, denn wenn man mit dem warten fertig ist presentiert sich das Smartphone mit dem Android Betriebssystem in seiner vollen pracht und man kann wirklich einiges Testen. Z.b. wird auch das eintreffen eines Anrufs oder einer Kurzmitteilung simuliert. Aber schaut Ihn euch selber an, hier der Link zum T-Mobile G1 Android Emulator.
Tags: Android, emulator, g1, google, htc, t-mobile
Veröffentlicht in Alte Themen | Keine Kommentare »
-