Przedstawiciel PLAY LUBLIN

Od dziś wprowadzamy nowe ceny dla dwóch telefonów: HTC Titan   HTC Mozart   Cennik

W AppStore dostępna już jest aktualizacja aplikacji Play24 na iOS. Zostały naprawione 2 błędy: – dostępność aplikacji dla kont biznesowych – zapamiętywanie hasła

Q:  Jakie są zasady migracji z dotychczasowych taryf All Inclusive do taryf Formuła 4.0 i nowych taryf All Inclusive? W ramach Promocji Klienci, którzy zmienią swoją dotychczasową ofertę na Ofertę FORMUŁA 4.0 otrzymają: FORMUŁA 4.0 ZA 79 zł dla dla Klientów posiadających promocje bez telefonu, którzy mają aktywną / aktywują efakturę FORMUŁA 4.0 ZA 79 zł [...]

Was exited to see Sony’s blog post about updating all the 2011 Xperia smart phones to Ice Cream Sandwich? Well, the company itself has issued a warning blog post explaining how ICS differs from Gingerbread when it comes to performance and usability on relatively older hardwares (2011 Xperia Smart phones). The company won’t be notifying you about the update, neither will they provide OTA update to ICS is a clear proof that Sony is not interested with their 2011 Xperia users updating to ICS.

Sony advises that it’s not a bad decision to stay with Gingerbread as ICS is more intensive in terms of memory management and it requires more RAM and CPU to work flawlessly. Sony says that ICS was developed targeting a phone with a Dual core processor supported by 1GB RAM but sadly, all the 2011 Xperia smart phones run on a single core processor and a 512MB RAM. (It’s a mystery why they are still releasing phones like Xperia U and Xperia sola. We have already discussed this in our forums.) 512MB is ideal for Gingerbread but when it comes to ICS, the apps use relatively higher memory; for example the web browser uses 20-30MB more in ICS compared to Gingerbread. This is the case with almost all the apps running on ICS and hence it’ll be difficult for the 512MB ram to handle apps on ICS.

So when the phone runs out of memory (RAM), the activity manager will start to close processes according to priority. At first the background processes will be killed and lastly the foreground activity will be halted. The image below will give a clear idea of how android manages processes when it runs out of memory.

When running a memory intensive game, the background processes like dialer or the home screen app will be killed and later when the gaming session is over, the phone will seem to be laggy since all the closed processes needs a restart, which takes time and slows the system down. RAM shortage is the main problem in 2011 phones but they are also blaming slower interaction with the SQL database and hardware acceleration which can have negative effects on the user experience.

On the other hand, Sony also mentions the goodies of ICS; like the new holo theme, over a thousand modified icons, new wallpapers and application backgrounds, the activity manager with a completely new UI (swipe to close an activity), Face Unlock, new calender and contacts apps, visual voicemail etc.

So, it’s the end user who is to decide whether to go with ICS so that you avial the cool new features mentioned above or to stay with Gingerbread and thereby enjoy a relatively stable ROM (on 2011 Xperias).

Fore more information on this and about all the technical aspects the differ ICS from Gingerbread, visit the Sony Blog.

Source : Developer World

During Mobile World Congress I was lucky enough to taste an actual Ice Cream Sandwich (or two) at the Google booth, and you’ll all be able to experience this sweet software treat on our 2011 Xperia smartphones, starting with the first models from mid-April.

Our developers have been hard-at-work to ensure we’re on track and the highest standards are met to deliver you the best possible user experience on Xperia 2011 smartphones with the upgrade to Android 4.0 platform release.

The first Xperia models to receive the upgrade will be Xperia arc S, Xperia neo V and Xperia ray. For these first models, the rollout will start mid-April and continue over 4-6 weeks.*

Following on, Xperia arc, Xperia PLAY, Xperia neo, Xperia mini, Xperia mini pro, Xperia pro, Xperia active and Sony Ericsson Live with Walkman will receive their scoop starting from the end of May/early June.*

We’ll get back to you once the rollout begins to keep you in the loop with progress and to tackle any questions you might have – as I said, please don’t worry if your kit (customized software specific to your operator and handset) isn’t immediately accessible; they will be made available as soon as they’re ready to go.

The latest version of Android 4.0 is a very powerful OS, brimming with new features and functionality, but it also requires more resource from your smartphone and this may impact performance in some user scenarios. To ensure it’s suitable, and performs for your individual needs, my friends at Developer World have taken a closer-look at how Ice Cream Sandwich will change your 2011 Xperia smartphone – check it out here.

Because this update is a significant revamp of some of your phone’s features, we want to make sure you take a conscious and informed decision to upgrade, so that you continue to enjoy optimum experiences from your Xperia smartphone.

Therefore, we’ll only be making it available for download via PC Companion and Bridge for Mac (i.e. not over the air via 3G or WiFi), and you also won’t receive any update requests or notifications.

Again, we will get back to you with more information in mid-April when the rollout begins.

Finally, with regards to our all new Sony Xperia S, which will be upgraded to Android 4.0 starting from the later part of the second quarter, we will get back with more detailed information on timing over the next weeks.

Talk soon, Ant.

*The availability and scheduling of this software upgrade and specific models upgradeable to Android 4.0 will vary by market and carrier requirements.

Ever thought about how Gingerbread (GB) and Ice Cream Sandwich (ICS) platforms differ on a technical level? In this blog post, we’ll describe some of the technical differences between GB and ICS, and what the differences in the user experience might be. This way you can decide if ICS is right for you, or if you prefer to stay on Gingerbread. Maybe you will prefer the new UI in ICS, or do you give a higher priority to the extreme stability of the Gingerbread platform? Read more after the jump!

Now as you might have seen, we’ve continuously kept you updated on our work with the ICS upgrade, and we started by telling you about what we do to get the latest software release from Google working on our Xperia™ smartphones in the article Ice Cream Sandwich – from source code release to software upgrade. Then we released ICS alpha and ICS beta versions of the coming software upgrade.

However, although ICS is new and compelling in many ways, we would like all of our users to make an informed decision when selecting what Android™ software to use. We are actually proud to say that our Gingerbread software is very stable and has great performance, so it’s not a bad idea to stay on this platform if your top priority is extreme stability. In that sense, Ice Cream Sandwich is more intensive, for example in terms of memory usage. As smartphones become more capable, our own applications, as well as the Google Mobile Services (GMS) applications, are becoming more advanced, which means that they require more CPU power, run more network activities and use more RAM. On the other hand, ICS brings a refined UI and some nice new features as described below.

Comparison of the look and feel in Gingerbread (left) and Ice Cream Sandwich (right).

New features in ICS
From a UI perspective, ICS is based on a new look and feel, the Holo theme. In order to accommodate the new look of Android, we decided to do an extensive touch up of our own assets, since the graphical assets of the Holo theme cannot be changed in any way as stated in the Android Compatibility Definition Document (CDD). New looks have been added in the platform layer as well as in the application layer. All in all, well over a thousand icons have been modified. In addition, we have deployed new wallpapers and application backgrounds, which harmonise more with the flatter graphical structures of ICS.

In ICS, the activity manager has a completely new UI, where all running apps are shown as thumbnails in a list. To close an activity, you can simply swipe it out of the list. ICS also introduces a face recognition app as a way to unlock the phone, called Face Unlock. Face Unlock uses the front-facing camera and advanced object recognition algorithms. It is included in our ICS upgrade for all phones that have a front-facing camera.

The contact list will show more information about the contacts, including updates from social networks. In the calendar, colour coding has been added and it is now possible to zoom. There is also support for a new type of voicemail that is more visual, offering transcriptions of voice messages.

When it comes to ICS, it’s a major upgrade of Android™, and there are a lot of things that have changed compared to the Gingerbread release. Some of these changes affect the performance and stability of the system, for example by using more CPU power and RAM. ICS was developed with Galaxy Nexus in mind, which is based on a TI platform with dual-core processor and 1GB RAM. We are now adapting ICS to run on our 2011 Xperia™ smartphones, which are all built on a Qualcomm platform with single core and 512 MB RAM. This means that in some cases, the resource usage in ICS impacts the performance of the system and the user experience might not be as good as when running on Gingerbread. The following sections identify some key areas where there is a big difference between ICS and Gingerbread.

Increased RAM usage
In general, it can be said that the RAM is the working memory in the phone, used by running processes in contrast to the flash memory, which is mainly used to store things. As you might understand, this is a simplified explanation and might not be entirely true in all cases. However, it can serve as a help to understand the difference between the RAM and the flash memory of the phone. To see how much RAM is currently used, go to Applications in the Settings app of your Xperia™ phone.

Now, let’s look at how the RAM is used. Our 2011 Xperia™ phones have 512MB RAM, while ICS was developed targeting a phone with 1GB RAM as mentioned above. Out of our 512MB RAM, about a third is used for functions that require a dedicated memory slot to operate fast enough. For example, this is the case for certain multimedia functions. The remaining space, which is at least 340MB, is reserved for the Linux user space, as required in the Android Compatibility Definition Document (CDD). Within the Linux user space, functions like the activity manager and Home screen app are running.

Another interesting thing is that many apps use slightly more RAM in ICS. For example, the web browser is quite intensive, and our measurements indicate that it uses 20-30MB more in ICS compared to Gingerbread. All in all, there are a lot of changes that together result in greater RAM requirement.

Illustration of the RAM usage.

When running low on RAM, typically with less than approximately 40MB left, the activity manager will start to close processes according to priority. At first, idle background activities are killed. The last thing to be closed down is the foreground activity. We have described this briefly in the table below. For more information, check out Android developers. (Please note that all figures mentioned about RAM usage are approximations and will differ depending on phone model and use case.)

Table showing different types of processes. When running out of RAM, the activity manager starts shutting down processes from the bottom and up, so that the last things to close are foreground and persistent activities.

Processes that are closed will obviously have to be restarted when the user enters the app again, which takes time and slows the system down. For example, when running a heavy game that uses all available RAM, the activity manager will be forced to kill all processes running in the background. This might include vital functions like the dialler and even the Home screen application. When you exit your game, there is a risk that the phone is perceived as slow, since the Home screen app will have to be restarted, just like every other activity you access afterwards.

Slower interaction with the SQL database
Another change in ICS compared to Gingerbread is that Google has moved a lot of the SQL handling from the native to the Java layer. In our internal studies, we have seen that read and write operations to the SQL database takes longer time, which slows down the apps. Many applications perform a lot of SQL operations when started, which greatly impacts the start-up time.

According to good practice, database operations or http requests should not be performed in the main thread. However, we know that there are quite a few applications that perform these kinds of operations directly in the main thread, which might cause them to hold up other operations. Also, when reading feedback on ICS software out on the market now, we’ve seen comments about people having problems with some applications and games.

If an operation takes too long, there is a risk of getting an Application Not Responding (ANR) as a result. An ANR occurs when an application doesn’t answer an intent, or responds to an input event, within a certain time limit. In case of intent, the time out is set to five seconds. For the input event, such as screen touch or button click, it’s ten seconds.

This can result in a user experience that is perceived as slower and less stable, due to longer response times and increased ANRs.

Introducing full hardware acceleration
Yet another change in ICS, is that the graphics hardware acceleration is on by default for all apps from API level 14. For apps at lower API levels, it can be turned on in the manifest with the attribute android:hardwareAccelerated=”true”. Hardware acceleration means that the GPU is used to render graphics, which enables a smooth user interface. However, it also results in at need to load additional graphic libraries for certain apps, which makes them use even more RAM.

When we performed internal tests on our applications, we saw that the Settings app consumed 1-2MB more RAM, and actually took longer time to start with HW acceleration, compared to without. Once the app is running, the UI is HW accelerated, but unless the app performs advanced graphics, the user will not see the difference.

Another effect of the hardware acceleration is that it can make the battery drain faster in some cases. An example of this is video playback, where the hardware acceleration requires every video frame to be run through the GPU, thus making the system use more power than it would have without HW acceleration.

As a developer, you should therefore evaluate if HW acceleration is required or not, as it comes with a cost in terms of RAM usage, start-up time and possibly even battery duration which can have negative effects on the user experience. You can read more about hardware acceleration in Ice Cream Sandwich on the Android Developers blog.

So, what will be your platform of choice? Will you go for the new features on ICS or will you prioritise stability and stay on Gingerbread? We hope this article clarifies some of the aspects to consider when making the decision. As always, we are eager to hear your opinion, so drop us a comment below and let us know! For more details on timing and practicalities on the ICS upgrade, check out this latest post on the Sony Xperia™ Product Blog.

More information

• Get the latest information about the timing for the ICS upgrade for Xperia smartphones on the Sony Xperia™ Product Blog.
• Learn how we work with ICS in our article Ice Cream Sandwich – from source code release to software upgrade.
• Have a look at the ICS alpha and ICS beta versions for unlocked Xperia™ phones.
• Check out the ICS beta for Xperia PLAY.
• Read about how a CPU works at Wikipedia.
• Learn more about RAM.
• Learn more about flash memory.
• Check out requirements on Android devices in the the Android Compatibility Definition Document (CDD).
• Visit Android developers for details on how processes are closed when running low on RAM.
• Read more about responsiveness and Application Not Responding (ANR).
• Learn about GPU at Wikipedia.
• Read more about hardware acceleration in ICS at the Android Developers blog.

PLAY i agencja Grandes Kochonos przygotowali kampanię przełomowej oferty FORMUŁA 4.0. Bohater i bohaterka każdego ze spotów przedstawiają nam FORMUŁĘ  4.0 w ofercie operatora sieci PLAY.  W FORMULE 4.0, płacąc stały abonament od 79 zł, otrzymujesz nielimitowane rozmowy,  SMS-y i MMS-y do czterech sieci: Orange, T-Mobile, Plus i PLAY. Towarzyszący bohaterom  znajomi w innych sieciach [...]

Właśnie ruszyła sprzedaż oferty Formuła 4.0. Już dziś możecie korzystać z nielimitowanych połączeń i sms do wszystkich sieci mobilnych w Polsce. Zapraszamy do salonów!   O 16.39 pierwszy klient podpisał umowę z taryfą Formuła 4.0 Twitter.com/RzecznikPlay

    Wszyscy czekacie na nasze stanowisko w sprawie dzisiejszego show Krótko: „Idealna kopia idealnej oferty! Play od 5 już lat zmienia rynek na lepsze dla polskich Klientów. Dziś dowiedzieliśmy się,  że robimy to tak dobrze, że aż kopiują nas globalni giganci tacy jak T-Mobile.” PS: Dodam, że nie zamierzamy przestać tego robić