Archive for the 'Mobile' Category

Android in a pre 1.0 version available

Published
by
joesonic
on August 19, 2008
in Mobile and Programming
. 0 Comments

Google recently released a pre 1.0 beta version of the Android SDK.

“This is the first release of the Android SDK that is formally on the path to Android 1.0.”

This let assume at first handset devices are comming soon.
As Google clarifies this is the first serious version of on the way to Android 1.0. Previous releases were considered very early looks at the SDK. This release should be fully compatible with Android 1.0 and all applications build with this release should run on final Android 1.0 devices.
The differences between this release an the final release are expected to be small and no major API changes are planned.

This beta SDK contains a large number of bug fixes and improvements form the early SDKs.

Some important changes include:

* new standard applications like arlam, calculator, camera, music, photo and messages where added.
* inprovements of the developer tools, e.g., preview of the XML layout.
* changes and impreovements withing the API
* new “Home” screen.

The relase notes, change overview and API Delta Report give a complete overview about all changes and extenstion of the SDK.

Now some issues from these documents related to “GEO”:

Location (Geo)

* The android.hardware.Sensors class has been replaced by android.hardware.SensorManager and android.hardware.SensorListener.
* The SensorManager class now notifies SensorListener objects of sensor changes, rather than firing Intents. The registerListener and unregisterListener methods are used to add and remove listeners.
* There is a new constant SensorManager.STANDARD_GRAVITY that may be useful to interpret accelerometer values.
* A method LocationManager.getProviderNames() has been added that
* returns the names of all providers, including ones for which the caller lacks permissions.
* The LocationManager class now notifies LocationListener objects of location and status changes, rather than firing Intents.
* The requestUpdates method has been renamed to requestLocationUpdates and now takes a LocationListener object rather than an Intent.
* A new requestStatusUpdates method has been added, also taking a LocationListener object.
* The removeUpdates method now takes a LocationListener object.
* The LocationManager.request*Updates methods must be called from a Looper thread, such as the main thread of an Activity. Additional method variants have been added that take an explicit Looper argument to allow for use outside of a main thread.
* A number of constants have been added to the LocationManager class.
* The LocationProviderImpl class has been removed.
* The Address class has several addtional fields and accessors in or order to better describe real locations.  Several incorrectly named methods have been renamed.
* The Geocoder class contructor now requires a Context parameter.
* The Location class now includes information on the estimated accuracy of a fix. It has new reset() and set() methods.

MapView

* New required MapView attribute: android:apiKey. Just like the traditional Google Maps API, you will be required to provide an authentic API key for your Android application. For now, the value of this can be an arbitrary string, like “myapikey,” but will need to be changed in order to work on actual devices. A process for acquiring a key is coming soon.
* MapView.toggle* replaced with set*. DeviceType removed from all Overlay methods.
* OverlayController removed, replaced with direct access to the Overlay List, with MapView.getOverlays(). The recommended practice is to use the new ItemizedOverlay class to manage map Overlays.
* Adds support for “map pin” child view that marks a given geo-location on the map. Such a view would stay in the correct place as the map is scrolled and zoomed:
* MapView child views can now be positioned relative to the Map or to the View.
* MapView child views can now be aligned relative to their position point.
* MapView no longer has a showMyLocation attribute; all methods referring to location are removed from MapActivity, MapView, and MapController. The new way to display location on the map is by creating a new MyLocationOverlay, enabling it, and adding it through the OverlayController.OverlayController.doZoom() is removed.
* MapController.setFollowMyLocation() no longer accepts a zoom.
* MapView.PixelCalculator was moved out into its own class PixelConverter, and its methods were renamed and changed to
* use android.graphics.Point objects instead of int arrays.
* Point renamed to GeoPoint

Google Maps

* New Maps menu alphabetic shortcuts This adds four invisible menu items:
menu+I - zoom in
menu+O - zoom out
menu+J - previous result
menu+K - next result
* Add a new style attribute to enable/disable MapView’s My Location feature. By default it’s disable meaning no extra location based permissions are required for developers wanting to write a Maps based app.
* Move Overlay.PixelCalculator -> MapView.PixelCalculator and added a MapView.getPixelCalculator.
* A new GestureDetector to help detect common gestures.
* The OverlayController, MyLocationOverlay and MapController classes are changed to final

Release Notes
http://code.google.com/android/RELEASENOTES.html

Overview of Changes, m5 to Android 0.9 SDK
http://code.google.com/android/migrating/m5-0.9/changes-overview.html

Test: Samsung SGH-i900 Omnia with GPS

Published
by
joesonic
on August 11, 2008
in Mobile
. 2 Comments

The SGH-i900 Omnia is Samsung’s newest Windows Mobile Smartphone with a size of 112 x 58 x 13,6 mm. Highlights of the phone are:

  • 5 MP camera with auto focus
  • 8 GB or 16 GM internal storage space and MicroSD card slot
  • HSDPA and WLAN
  • GPS chip
  • 240 x 400 pixel display with 65.536 colors (size: 43 x 70 mm)
  • Windows Mobile 6.1

The camera is intuitive to use and in combination with GPS a geo-tagging function is provided. The only drawback here is that it is difficult to enable and disable this function.

The touchscreen seems to be better than in the previous models form Samsung but is still sometimes difficult to handle. Especially at the borders the precision is not so good.

If you want to buy the Samsung i900 only because of the integrated GPS, this is not recommended. In the test after starting the navigation software it last about 5 minutes until the actual position is located. Additionally Route 66 Mobile Navigator 8 has not the best usability among navigation software. To plan a route or change settings the user has to click on a strange icon in the button left corner. To find an address the user enters city and street directly in the search box. This is different to TomTom or Navigon devices, where you have separate fields for city and street.

Standard functionality like navigation, route planning, favorites management and POI are available. There is also a link to the address book of the mobile phone.  Traffic infos, travel guides and color profiles, maps and voices can be downloaded directly to the phone. Of course there are fees for these additional services.

A standard routing lasts about 10 seconds, rerouting only 2 or 3 seconds.

[via golem.de]

Written and submitted from Home, using my 802.11g WiFi network.

Cadastral map for transmitters (Sendekataster)

Published
by
joesonic
on July 30, 2008
in GeoWeb, Mobile and Web
. 2 Comments

The forum of mobile communication in Austria has launched a cadastral map for Austria which locate radio- and cellular radio transmitters in Austria. This service is supported by the Austrian federal agency of traffic, innovation and technology (Bundesministerium für Verkehr, Innovation und Technologie) and the telecommunication regulation authority with the objective to give citizen an overview about the positions and information of transmitters. A web map service inform users about this. The map was developed by WIGeoGIS and uses TeleAtlas data.

Link: http://www.senderkataster.at

Written and submitted from Home, using my 802.11g WiFi network.

What’s the matter with Android?

Published
by
joesonic
on July 17, 2008
in Google and Mobile
. 0 Comments

The developer community of Android criticizes the information policy of Google. Currently the SDK has several bugs (e.g, Geocoding, and Media Player), but Google is waiting with a new release of the SDK. The last Update goes back in February, since then no new version of the Android SDK was announced.

Citation from the Petition:

In order not to lose many highly encouraged developers, I think its time to release some news about the development process of the SDK. Maybe let us know why we have to live with these long release-cycles.

With an online Petition the programmes would force Google to announce a new version.

Several developers are thinking to adapt their applications for other frameworks like the iPhone SDK, Windows mobile, Symbian or OpenMoko. I’m looking forward to see Googles reaction.

Petition: http://www.anddev.org/petition/

[via: derStandard]

Written and submitted from Home, using my 802.11g WiFi network.

Nokia Completes Its Acquisition of NAVTEQ

Published
by
joesonic
on July 10, 2008
in Mobile
. 0 Comments

Nokia announced today that it has completed its acquisition of NAVTEQ, a leading provider of digital map information.Powered by NAVTEQ’s maps data, Nokia will add context - time, place, people - to web services optimized for mobility.

Statements of Nokia and Navteq:

“Nokia and NAVTEQ together make a powerful combination, and customers will benefit as the transaction enables NAVTEQ to accelerate its expansion into new regions and introduce innovative new content. This is an industry poised for further growth and NAVTEQ will play a major role in the field,” said Olli-Pekka Kallasvuo, President and CEO, Nokia. “The addition of NAVTEQ comes at the right time for Nokia’s business, allowing us to create the leading location platform just as context-aware and location-based Internet services expand rapidly into mobile communications devices.”
Judson Green, President and CEO of NAVTEQ, said: “Nokia has a deep understanding of the requirements for the industry. As part of Nokia, NAVTEQ will further invest in its map and content capabilities and make our products and services easier for all our customers to use and access.”
“NAVTEQ’s map data already play an important role in Nokia Maps service, which brings downloadable maps, voice-guided navigation and other context-aware web services to people’s pockets. Now that the acquisition has been completed, this role will become even more important as context-aware Internet services grow,” added Niklas Savander, Executive Vice President for Services & Software, Nokia.

The transaction is valued at approximately $8.1 billion.

About NAVTEQ

NAVTEQ is a leading provider of comprehensive digital map information for automotive navigation systems, mobile navigation devices, Internet-based mapping applications, and government and business solutions. NAVTEQ creates the digital maps and map content that power navigation and location-based services solutions around the world. The Chicago-based company was founded in 1985 and has more than 3,600 employees located in 187 offices and in 39 countries. NAVTEQ maps are available in 73 countries today and are distinguished by their detailed inclusion of over 260 road network attributes essential to dynamic, turn-by-turn route guidance and navigation.

With the deal Nokia Maps will be strenghtend. Nokia Maps covers over 200 countries, with over 70 of them navigable. Nokia Maps 2.0 has improved its optional Car Navigation, enhanced its pedestrian navigation, added multimedia city guides, offers satellite images, and is sporting a redesigned user interface.

Nokia Press Release

Navteq Press Release

Written and submitted from Home, using my 802.11g WiFi network.