Flash etiketine sahip kayıtlar gösteriliyor. Tüm kayıtları göster
Flash etiketine sahip kayıtlar gösteriliyor. Tüm kayıtları göster

18 Şubat 2012 Cumartesi

Android Flash Player 10.1 Download


Most Poular Android Apps. Flash Player is a runtime plug-in for your device browser that enables a FULL web browsing experience on your device including access to your favorite videos, games and interactive content. Having Flash Player on your device gives you freedom to access the same immersive content you experience on a desktop PC anywhere, anytime.


The Full Web experience with Flash Player enables consumers to get more from their devices:
Uncompromised browsing without empty boxes .
Access to rich content, instead of being limited to stripped down m-sites (Most m-sites offer the option to navigate to their full sites).
A more immersive, richer experience for games, video, and productivity anywhere.

By clicking Install I agree to the License Agreement terms at http://adobe.com/go/eum. Manage your privacy settings at https://settings.adobe.com/flashplayer/mobile.

Package: com.adobe.flashplayer

DOWNLOAD

Recently changed in this version

Flash Player (10.1.106.16) impacts new users only and is not a mandatory update for existing users. It SHOULD NOT be installed on devices/tablets with the NVIDIA Tegra 2 super chip including the LG Optimus 2X, Dell Streak 7 and Motorola ATRIX. The pre-installed version of Flash Player is optimized for Tegra 2. Future updates will include these optimizations. If you are unsure as to whether your device includes the NVIDIA Tegra 2, please consult your device owner s manual.

More Documents


Designed for mobility

To make it possible to deploy SWF content on smartphones and other mobile devices that have limited processing power and memory availability compared to PCs, a tremendous amount of work has gone into to making Flash Player 10.1 ready for mobility . This work includes performance improvements, such as rendering, scripting, memory, start-up time, battery and CPU optimizations, in addition to hardware acceleration of graphics and video. Improvements in memory utilization and management, start-up time, CPU usage, and rendering/scripting performance benefit PCs as well as mobile devices.
Flash Player 10.1 also introduces new mobile-ready features that take advantage of native device capabilities endash including support for mobile input models and accelerometer input -- bringing unprecedented creative control and expressiveness to the mobile browsing experience.
SWF Focus Mode 
Flash Player 10.1 integrates seamlessly with Mobile Browsers that support Touch & Gestures through the use of SWF Focus Mode. The first tap over an embedded SWF will set Focus and allow drag events to go to Flash (if the content contains a listener for the event). This will enable users to interact with Flash content as needed, but still pan and zoom around the page as normal.
Mobile Text Input 
Flash Player 10.1 provides support for use of native device virtual keyboards with TextField support if no physical keyboard is detected. A virtual keyboard is automatically raised and lowered in response to focus changes on text fields when editing text on mobile devices supporting a virtual keyboard to enable unobstructed and intuitive text editing. The focused text field is centered in the visible region of the page and appropriately zoomed/scrolled to ensure it is not obscured by the virtual keyboard. Upon screen rotation, incoming calls, or other system events, any already existing text input is retained. The virtual keyboard works with TextField but does not currently work with the Text Layout Framework or other Flash Text Engine text.
Easier Full-Screen Mode Activation 
Because of the smaller screen real-estate on mobile devices, Full-Screen Mode will significantly enhance the user experience for media, game play, and other rich content. A new HTML Parameter, FullScreenOnSelection, will enable developers to allow their users to launch Full-Screen Mode with a single tap over the content.
Long-Tap to Full-Screen Mode 
Users can now long-tap on any SWF and select Full-Screen Mode. The HTML Parameter AllowFullScreen is disabled for this feature, so that a user can activate Full Screen Mode for any SWF on mobile devices.
Optimized SWF Management for Mobile 
Flash Player 10.1 optimizes SWF loading and playback for mobile CPU and memory limitations to provide a better user experience. Instances are loaded or deferred based on SWF priority, visibility and available memory and CPU resources to enable more immediate browsing experiences without waiting for every SWF on a page to load. Developers can indicate SWF priority through a new HTML parameter, hasPriority. Deferred instances are loaded after the HTML page load is complete, and off screen and invisible instances are started when they become visible. Flash Player will also automatically pause SWF playback it is not in view or the foreground application, for example when a call is received or alarm goes off, to reduce CPU utilization, battery usage and memory usage.
Sleep Mode 
The Flash Player timer slows down when the mobile device goes into screen-saver or similar mode to reduce CPU and battery consumption on mobile devices. The timer returns to the default setting when a wake-up event is triggered. There is no interruption in audio/video playback. Incoming phone calls pause Flash Player.
Adaptive Frame Rate 
Flash Player will monitor and lower the SWF frame rate to provide greater processing power for rendering, which can improve content usability and conserve CPU utilization on resource constrained mobile devices. If the frame rate drops below the threshold, Flash Player will drop frames to achieve the defined default frame rate of the SWF.

Developer Productivity

Global Error Handler 
The new global error handler enables developers to write a single handler to process all runtime errors that weren t part of a try/catch statement. Improve application reliability and user experience by catching and handling unexpected runtime errors and present custom error messages. When using the global error handler in a SWF running in the debug player, error pop-ups will not be shown. The Global error handler is disabled in the current build, but will be available in a future refresh of Flash Player 10.1.
Globalization Support 
New ActionScript globalization APIs allow Flash Player to use the values chosen in the operating system preferences to process text and lists and present information based on location context, without any knowledge of locale requirements. Choose a specific format independent of the currently selected locale on the operating system. Locale specific information and processing can include: date, time, currency and number formatting; currency and number parsing; string comparison for sorting or searching for text; and upper/lower case conversions.
Enhanced Browser Integration 
Flash Player 10.1 offers enhanced conformance to consistent browser usability guidelines, ensuring optimized user experiences.
Out-of-Memory Management 
Flash Player 10.1 prevents out-of-memory browser crashes by shutting down instances where a SWF attempts to allocate more memory than is available on the device. When a SWF tries to allocate more memory than is available on a device, Flash Player 10.1 adds logic to shut down Flash Player to prevent the browser from crashing. Users will receive notification to restart the SWF, or will see a notice to refresh the page if all instances must be shutdown. In the former case, Flash Player displays a Click-to-Play icon in place of the SWF. In the latter case, Flash Player displays an insufficient resources warning.

Expanded options for high quality media delivery

Flash Player 10.1 includes a number of media quality of service improvements and is ready to take advantage of upcoming Adobe media servers that will provide new ways to deliver rich media experiences and create new business models. With new HTTP streaming capabilities, Content Providers can use their standard HTTP infrastructure to stream media. Streaming performance is also enhanced with improved support for live events, buffer control and peer assisted networking.
Peer-Assisted Networking (requires Stratus on Adobe Labs)
The RTMFP protocol now supports groups, which enables an application to segment its users to send messages and data only between members of the group. Application level multicast provides one (or a few) -to-many streaming of continuous live video and audio live video chat using RTMFP groups.
HTTP Streaming 
HTTP streaming enables delivery of video-on-demand and live streaming using standard HTTP servers, or from HTTP servers at CDNs, leveraging standard HTTP infrastructure and SWF-level playback components. The addition of HTTP streaming will enable expanded protocol options to deliver live and recorded media to Flash Player. 
Note: Content protected using Adobe Flash Accessö99 is not supported in Flash Player on Android 2.2.
Stream Reconnect (requires FMS 3.5.3 server)
Stream reconnect allows an RTMP stream to continue to play through the buffer even if the connection is disrupted, thereby making media experiences more tolerant of short term network failures and enabling non-disruptive video playback. When a connection is re-established the stream resumes playback. Developers can add re-connection logic in ActionScript to re-establish server connection and resume streaming without any disruption in the video.
Smart Seek (Requires FMS 3.5.3 server)
Smart seek allows you to seek within the buffer and introduces a new "back" buffer so you can easily rewind or fast forward video without going back to the server, reducing the start time after a seek. Smart seek can speed and improve the seeking performance of streamed videos and enable the creation of slow motion, double time, or instant replay experiences for streaming video.
Buffered Stream Catch-Up
Buffered stream catch-up allows developers to set a target latency threshold that triggers slightly accelerated video playback to ensure that live video streaming stays in sync with real time over extended playback periods.
Fast Switch (previously called Dynamic Streaming enhancements) (requires FMS 4 server)
The Dynamic Streaming capability introduced in Flash Player 10 and FMS 3.5 is enhanced to improve switching times between bitrates, reducing the time to receive the best content quality for available bandwidth and processing speed. Users no longer need to wait for the buffer to play through, resulting in a faster bitrate transition time and an uninterrupted video playback experience, regardless of bandwidth fluctuations.

Fixes and Enhancements in Flash Player 10.1.92.8

Adobe Flash Player 10.1.92.8 includes security enhancements described in Security Bulletin APSB10-16.

Fixes and Enhancements in Flash Player 10.1.92.10

AdobeFlash Player on Android 2.2 supports the same H.264 profiles as Flash Player on desktop platforms. On Android, the hardware H.264 decoder is used when the hardware decoder is available (not already in use) and capable of decoding the H.264 video stream; the software decoder is used in all other situations.

Fixes and Enhancements in Flash Player 10.1.95.2

Adobe Flash Player 10.1.95.2 includes a fix for an issue with H.264 video playback that caused audio to play back at slow speeds on certain devices.

Features, Fixes and Enhancements in Flash Player 10.1.105.6

Adobe Flash Player 10.1.105.6 includes security enhancements described in Security Bulletin APSB10-26.
Features:
Screen Orientation Lock:
Content authors can now choose to lock content displayed in Full-Screen mode to a single orientation.  This will prevent content from being scaled and rotated when the user rotates their screen.
International Language Support for Input Text and IME:
Flash Player now supports the entry of international text for Input Text and IME.   This feature also introduces a number of general usability enhancements to improve western text entry on devices with on-screen keyboards.
Fixes and Enhancements
Audio:
öb7         Loading WAV files via HTTP no longer causes the browser to hang.
Input:
öb7         Improvements to touch accuracy correct instances where small objects were not correctly responding to touch events.
öb7         When a user clicks on a TextField when in Full Screen mode, Flash Player will exit Full Screen mode to facilitate text entry.
Rendering:
öb7         Values for stage.fullScreenHeight and stage.fullScreenWidth are now correctly updated when the screen orientation changes from landscape to portrait.
öb7         Crashes related to playing content while zoomed in have been resolved.
Video:
öb7         Improved Hardware Video Decoding Support:
        - All H.264 encoding profiles are now supported on the HTC Nexus One
        - All H.264 video except 720p is supported on TI OMAP 3630-based devices (Motorola Droid 2, Droid X
        - H.264 baseline video is now supported on TI OMAP Motorola Droid
öb7         Multiple optimizations improve video playback performance and quality on Android 2.2 devices
öb7         Locking the screen orientation to portrait mode during video playback now works as expected.

Known Issues and Limitations

General:
  • When an URL containing & or % is saved to a SharedObject file redirectSO.sol all of the parameters after these characters are stripped off. (1909140)
  • CSS styles should not cascade across sandbox boundaries. (2261815)
  • startDrag and stopDrag do not work when the target is a 2D child of a 3D parent. (2200972)
  • POST requests with no body reverting to GET. (2223288)
  • XML.appendChild does not function correctly when published as SWF10; works fine as SWF9. (2340839)
  • Last SWF Loaded sets scriptTimeLimit. (2500755)
  • [FP-1569] AS3 Timeline: Child Sprite ADDED_TO_STAGE event is fired twice. (2300936)
  • AS3 Timeline: First frame of Movie Clip animation played twice when created and added to stage with ActionScript. (2520095)
  • [FP-4423] onEnterFrame gets called more often than necessary. (2614589)
  • Automation APIs are only available on Windows and Android platforms. On unsupported platforms, runtime errors may appear when these APIs are called. 
  • When searching for objects (not strings) in Dictionary objects using the 'in' operator, if the object is not found in the Dictionary object, it will be searched for in the delegate objects. With 10.1, the toString operator will be called on the Object if not found in the Dictionary. This can cause problems with Proxy objects who need to define the callProperty function or it will generate a RTE. A simple example that failed silently in 10.0 but throws an error in 10.1:
    • var p:Proxy = new Proxy();
    • var d:Dictionary = new Dictionary();
    • trace (p in d);
    • Error: Error #2090: The Proxy class does not implement callProperty. It must be overridden by a subclass. 
    • at Error$/throwError()
    • at flash.utils::Proxy/http://www.adobe.com/2006/actionscript/flash/proxy::callProperty() 
    • at Untitled_fla::MainTimeline/foo() // at Untitled_fla::MainTimeline/frame1() 
Accessibility:
öb7         The Flash Accessibility API is not supported on Android 2.2.
Audio/Video:
  • AAC Decoding uses Android's native AAC Decoder.
    • This licensing requirement imposes a number of limitations on the types of AAC streams that can be decoded, which differ from desktop versions of Flash Player.
    • Only Mono and Stereo AAC Streams are supported on Android 2.2.
    • Flash on Android 2.2 supports the following AAC profiles: AAC-LC, HE-AACv1, and HE-AACv2.
    • Android 2.2 supports the following AAC sampling rates: 48000, 44100, 41000, 32000, 24000, 22050, 16000, 12000, 11025, 8000
    • The recommended sampling rate for Flash audio is 44,100 Hz because it is the internal format used by Flash's sound mixer. Flash must convert other sampling rates to 44,100 Hz before playback.
  • Browser may not always resume video playback automatically when interrupted by a phone call.
  • Platform-specific driver issues sometimes cause crashes during video playback.
  • Playing multiple videos simultaneously will not perform well.
  • When changing phone orientation and entering/exiting full-screen mode during video playback, playback may pause briefly.
  • Pausing progressively downloaded video for more than 2 minutes may cause video to restart from beginning when resumed.
  • Video embedded in a SWF does not always resume from pause.
  • The Android 2.2 player will not support preloading large videos completely through NetStream. The video preloading size is limited by the circular buffer size (currently 8MB). If the video exceeds the buffer size and the content depends on the video being fully downloaded before playback starts, the content will never start.
  • The .v files created by Adobe Media Encoder CS5 cannot be called by onXMPData. (2603890) 
Browser Integration:
  • You cannot scroll the browser window if a Flash-based TextField has focus.
  • Loading Local Files is not supported on Android 2.2.
Context Menu:
  • Context Menus are not supported on Android 2.2.
Input:
  • Opening the software keyboard causes the HTML content to scale down to the remaining available size in the window.
  • Alt and Caps Lock Keys do not send KeyDown or KeyUp events from Soft Keyboard.
  • On touch screen devices, the mouse position is moved to Infinity when the user's finger is not touching the screen.
  • Tab Focus is not supported in Flash Player on Android 2.2.
Installation:
  • Upon installation, a mismatch between new Java libraries and the version of Flash running in memory can cause a crash. Navigating to a page without Flash will cause the player to unload, and the next instance of Flash that is loaded will be the updated player.
Memory Management:
  • Flash Player attempts to determine and place priority on the most important SWFs on a page; however, depending on the contents and construction of a given HTML page, this is not always possible to do correctly without hinting from the content itself. In some instances, Flash Player will mistake ancillary content as the primary content and switch everything else to Click to Play when encountering a low memory situation. 
Media:
  • Camera and Microphone support is not included in Flash Player on Android 2.2.
Performance:
  • Rendering 3D objects with large numbers of vertices will not perform well.
Printing:
  • Printing is not supported in Flash Player on Android 2.2.
Rendering:
  • Flash Content is always displayed on top of all HTML content, including pop-ups.
  • Overlapping Flash Content may not consistently render at the same depth.
  • In some instances, black flashes appear on SWF content when scrolling.
  • Perlin Noise and Displacement Map bitmap filters will perform poorly on mobile devices.
  • Several successive pinch-zooms in a single direction can cause Flash Content to not render.
  • PixelBender Shaders are Not Supported on Android 2.2 but may be partially enabled.
  • Occasionally, SWFs are incorrectly positioned at the upper-left corner of the screen.
  • Flash Content in Transparent WMODE will obscure content below it.
  • The number of concurrent Flash instances is limited to 30 on Android 2.2.
  • Flash Content is always rendered in Medium quality mode.
Text:
  • Font fallback support is not supported for Thai, Hebrew and Bengali.
  • [FP-1982] appendText when appending from another text field does not append in the correct location when the source string contains "n". (2341522)
  • Classic Text: Large font sizes are not drawing correctly on stage on in exported SWF Movies. (2483664)
  • Scale text with Free Transform scales text incorrectly goes beyond text boundary and is cut off and too big. (2486588)
Android Flash Player 10.1 Download

17 Şubat 2012 Cuma

Mobile Odin Pro, flash has never been easier.





Many who read this blog know what it is ODIN. For those who are unaware, ODIN is a tool with which we can install any operating system Android. Or more commonly known in the Android community, allows us to flash our device Android.

This means that with this program you from installing an updated version of Android (and earlier) to install any cooked ROM, ie, any Android made ??by the community.
Well now Chainfire has brought to light Odin Pro Mobile. This tool not only allows you to install any ROM or upgrade your operating system Android, but also allows us to do from the interface of the application without the need to download the ROM.

As you can imagine, this tool greatly facilitates the task of flash our devices. Since we'd get rid of Internet search Android version you want to install to your device.
It also incorporates a system that truly free people a lot of headaches, it is EverRoot, which we kept our Root privileges, but we install an official release.
At the moment the application only supports a small number of devices:
Samsung S2 Galaxy (GT-i9100)
Samsung Galaxy Note (GT-N7000)
Samsung Galaxy S (GT-I9000)
Samsung Galaxy Tab 7 (GT-P1000
Although Root is mandatory and that the number of supported devices is very small (Chainfire promises to extend the list of compatible devices), this tool is very useful and greatly facilitates the task of flashing your device Android.
The issue you have available in the Market at a price of 1.99 ö80.




ODIN furniture - complete firmware flash directly from the device itself!ODIN mobile is the choice of the device firmware flasher. Just throw the firmware files on your (internal or external) SD card, launch mobile flash ODIN away.! The appliance must be grounded in order to use ODIN mobile!If you use the EverRoot, Mobile firmware ODIN mess while the flash. Verify that the new firmware leak? No need to lose the mess!Currently supported devices:- Samsung GT-i9100 Galaxy S2- Samsung Galaxy GT-N7000 Note- Samsung GT-I9000 Galaxy S * NEW *- Galaxy Tab 7 "GT-P1000 * NEW *More devices to come!Flash Mobile ODIN does not add a custom kernel, or flash meter for the yellow warning triangle appears.For discussion, see the forum thread XDA-Developers.com: http://forum.xda-developers.com/showthread.php?t=1347899----- ----- MANUALFlashing Mobile ODIN is easy. You start by counting approx. The app will check your system has all the app should continue (as root). It can lead you to install an additional package (free) market.Now you should see the main screen ODIN Mobile. That section of the list. By clicking on the section to select a file on an SD card flash for that partition. Do not worry about selecting the wrong file - ODIN Mobile does not disappoint. Separate files (named for the section) as well. Tar e. Tar.md5 files are supported.ODIN's office you may be used for "PDA", "phone" and "SCC" buttons. All three of these buttons have been replaced with "Open file ..." button. This button opens the file you can choose from the SD card, and find all partitions that can flash on the inside of this file. So if you choose one. Tar file containing the nucleus and the modem, the kernel and partitions Modem set up to use it. Tar flashing.Now, we have chosen what you want to flash, if you have the Pro version you can never go to the root. options for you to ever root root when firmware is flash. Never again can not be! Click here for the applications you want to inject the firmware is flashed.Now we all made the selection and EverRoot partition configuration, we "Flash Firmware". ODIN Phones gather all the information needed and perform the flash. Before starting, however, will check the battery level is above 50%, and if this offer is valid for checking MD5 of files you selected will blink. Hopefully it will restart in recovery mode, and the firmware you selected.----- ----- Device SupportSee discussion on the forum XDA-Developers.com (http://forum.xda-developers.com/showthread.php?t=1347899) for more information on how to get your unit load.Mobile Odin Pro, flash has never been easier.

Samsung Galaxy Nexus: voice commands, battery, Flash Player and benchmarks


Let's start with one of the features that Android 4.0 Ice Cream Sandwich, which is currently exclusive to Galaxy Nexus, wanted to improve over previous versions, we are talking about the voice command, namely speed of dictation of texts.

This feature, also present on Gingerbread, has been improved in this version of 'Google OS, resulting in exceptionally accurate.

Here's a video test done in English, performed by SlashGear, which shows how the speech recognition app will be able to easily handle the language with great precision. (Voice recognition requires a data connection to communicate with Google servers).




Who knows if the application will respond with the Italian with the English language as well.



Another aspect of the new Samsung Galaxy Nexus has done much to discuss the Android community has been the battery, which with its 1,750 mAh could not withstand the power consumption of the smartphone.

Through an anonymous user who could play with the Galaxy Nexus has become aware of the issue that affects all holders of smart phones, which is that battery life is that the new Google smartphone Experience seems to offer many hours of use even under intense. This is not a real test done on the battery, but certainly the information we give you the rest of the article will begin to make us understand what we can expect from the battery: we discover these details.
The Galaxy Nexus seems to have been used intensively for about 5 hours and almost 14 minutes, just do not know very well how intense was this use. What we see is that, looking at the percentages in the screenshot below, you can guess how the display has been turned on for a long time, since it is a huge display and in addition to 720p, consumption can be considered quite low.

After some tests for an anonymous user, who American stressing his Galaxy Nexus (perhaps 1,850-mAh battery), has released the first "test" personal battery life, more than anything else gave us some important information.

After extensive use of 5 hours and 14 minutes (do not know how intense), we can see by the screen as the display with a resolution of 720p, while not enough has been turned on by consuming too much battery.

In fact not only the display would help to conserve battery power but also the LTE 4G network, which consumes lots of battery definitely more than our 3G network. Maybe with a little less than the amperage battery and a network of U.S. smartphone much less expensive in terms of autonomy, our equipment could last longer.

In short, after just over 5 hours of intensive use the Galaxy Nexus is found with 45% of the battery, if the heavy usage goes up to 10 hours we will definitely need a fast charge.

Most likely under normal use, the Galaxy Nexus should not struggle to get to the next day or so we hope.



Last but certainly not least, the "problem" for the Samsung Nexus Galaxy is the absence of the Adobe Flash Player, which currently can not be downloaded either from the 'Android Market.

Although Adobe has already said not to release newer versions of Flash Player for mobile devices, but we still hope that the development team is working to release a final version that is compatible with Android 4.0 Ice Cream Sandwich before closing its doors permanently.

Rooms were also some attempts at forced installation of applications on Gingerbread or Froyo, as not compatible with Android 4.0.



Last view on the Samsung Nexus Galaxy was made ??by the children of AndroidCommunity, who, when they have smartphone, performed the first test benchmarks.

The Quadrant, a popular app on the official market running these tests, reported 2140 points for the Galaxy Nexus, which exceeded the threshold of 2000 points at the top has led to testing.

Unfortunately, however, still failed, even remotely, to approach the same benchmark results obtained by variation of T-Mobile's Galaxy S II, which would reach the beauty of 3915 points.

Obviously, as we have said many times, we can not take these results as the pure truth about the performance of Android devices. And we must also consider the fact that Android 4.0 ICS is a new operating system and as such can not be tested on their knowledge application based on OS "old"; also because ICS operates in a completely different hardware that is available .

After these news have changed his mind on the Samsung Nexus Galaxy? (Previous tests are obviously personal trials we do not know how and when they were made).


Samsung Galaxy Nexus: voice commands, battery, Flash Player and benchmarks

Samsung Galaxy Nexus: voice commands, battery, Flash Player and benchmarks


Let's start with one of the features that Android 4.0 Ice Cream Sandwich, which is currently exclusive to Galaxy Nexus, wanted to improve over previous versions, we are talking about the voice command, namely speed of dictation of texts.

This feature, also present on Gingerbread, has been improved in this version of 'Google OS, resulting in exceptionally accurate.

Here's a video test done in English, performed by SlashGear, which shows how the speech recognition app will be able to easily handle the language with great precision. (Voice recognition requires a data connection to communicate with Google servers).




Who knows if the application will respond with the Italian with the English language as well.



Another aspect of the new Samsung Galaxy Nexus has done much to discuss the Android community has been the battery, which with its 1,750 mAh could not withstand the power consumption of the smartphone.

Through an anonymous user who could play with the Galaxy Nexus has become aware of the issue that affects all holders of smart phones, which is that battery life is that the new Google smartphone Experience seems to offer many hours of use even under intense. This is not a real test done on the battery, but certainly the information we give you the rest of the article will begin to make us understand what we can expect from the battery: we discover these details.
The Galaxy Nexus seems to have been used intensively for about 5 hours and almost 14 minutes, just do not know very well how intense was this use. What we see is that, looking at the percentages in the screenshot below, you can guess how the display has been turned on for a long time, since it is a huge display and in addition to 720p, consumption can be considered quite low.

After some tests for an anonymous user, who American stressing his Galaxy Nexus (perhaps 1,850-mAh battery), has released the first "test" personal battery life, more than anything else gave us some important information.

After extensive use of 5 hours and 14 minutes (do not know how intense), we can see by the screen as the display with a resolution of 720p, while not enough has been turned on by consuming too much battery.

In fact not only the display would help to conserve battery power but also the LTE 4G network, which consumes lots of battery definitely more than our 3G network. Maybe with a little less than the amperage battery and a network of U.S. smartphone much less expensive in terms of autonomy, our equipment could last longer.

In short, after just over 5 hours of intensive use the Galaxy Nexus is found with 45% of the battery, if the heavy usage goes up to 10 hours we will definitely need a fast charge.

Most likely under normal use, the Galaxy Nexus should not struggle to get to the next day or so we hope.



Last but certainly not least, the "problem" for the Samsung Nexus Galaxy is the absence of the Adobe Flash Player, which currently can not be downloaded either from the 'Android Market.

Although Adobe has already said not to release newer versions of Flash Player for mobile devices, but we still hope that the development team is working to release a final version that is compatible with Android 4.0 Ice Cream Sandwich before closing its doors permanently.

Rooms were also some attempts at forced installation of applications on Gingerbread or Froyo, as not compatible with Android 4.0.



Last view on the Samsung Nexus Galaxy was made ??by the children of AndroidCommunity, who, when they have smartphone, performed the first test benchmarks.

The Quadrant, a popular app on the official market running these tests, reported 2140 points for the Galaxy Nexus, which exceeded the threshold of 2000 points at the top has led to testing.

Unfortunately, however, still failed, even remotely, to approach the same benchmark results obtained by variation of T-Mobile's Galaxy S II, which would reach the beauty of 3915 points.

Obviously, as we have said many times, we can not take these results as the pure truth about the performance of Android devices. And we must also consider the fact that Android 4.0 ICS is a new operating system and as such can not be tested on their knowledge application based on OS "old"; also because ICS operates in a completely different hardware that is available .

After these news have changed his mind on the Samsung Nexus Galaxy? (Previous tests are obviously personal trials we do not know how and when they were made).


Samsung Galaxy Nexus: voice commands, battery, Flash Player and benchmarks
Android Phone Driver-Android Driver