Related
We’re starting our Android 5.0, Lollipop upgrade from today for Xperia Z3 and Xperia Z3 Compact.
You’ll see the upgrade hit first devices in the Nordics and Baltics, continuing to further markets, for more Xperia Z Series products, starting in around two weeks time* – we’ll share the latest here, as it happens.
After blending Google’s first Lollipop release with our Sony software, some of the goodies include;
Fresh, streamlined looks – based on Google’s material design, but retaining our minimalistic approach to interface and application design
New look notifications and lock screen – with fully customizable settings, so you only get the information you really need
Multi user profiles and guest mode – making it easy for family and friends to use your device, or the creation of dual environments for work and play…
Android for Work – not only are business-ready Xperia smartphones and tablets unique devices for work – with waterproof form factors, great battery life and productivity features – they will now also be part of the Android for Work ecosystem
Better storage control and customisation – with the option to easily move applications from internal memory to SD card – giving you more control over your content, particularly useful for devices with slightly less space
Click to expand...
Click to collapse
http://blogs.sonymobile.com/2015/03...lollipop-rollout-xperia-z3-xperia-z3-compact/
Has anyone recieved the update yet
Look in the main 5.0 thread. Plenty of people have received it, region specific
Thread closed
Is not the place to ask questions, and there are already enough threads about lollipop ?
Android 5.0, Lollipop rollout: Xperia Z3 & Xperia Z3 Compact from today 16.03.2015
As promised way back in October 2014, Sony is now starting to roll out an upgrade to Android Lollipop for users of its existing Z3 and Z3 Compact devices.
Announced today in a blog post, it says that other Z Series products will start to get the upgrade in about two weeks. For now, it’s only Z3 and Z3 Compact devices for users in Nordic and Baltic countries, but a wider European release is expected shortly after.
the upgrade hit first devices in the Nordics and Baltics, continuing to further markets, for more Xperia Z Series products, starting in around two weeks time* – we’ll share the latest here, as it happens.
After blending Google’s first Lollipop release with our Sony software, some of the goodies include;
•Fresh, streamlined looks – based on Google’s material design, but retaining our minimalistic approach to interface and application design
•New look notifications and lock screen – with fully customizable settings, so you only get the information you really need
•Multi user profiles and guest mode – making it easy for family and friends to use your device, or the creation of dual environments for work and play…
•Android for Work – not only are business-ready Xperia smartphones and tablets unique devices for work – with waterproof form factors, great battery life and productivity features – they will now also be part of the Android for Work ecosystem
•Better storage control and customization – with the option to easily move applications from internal memory to SD card – giving you more control over your content, particularly useful for devices with slightly less space
Be sure to follow the blog and @SonyMobileNews for all the latest as our rollout continues.
*Timing and availability may vary by market and/or carrier
Source> http://blogs.sonymobile.com/2015/03...lollipop-rollout-xperia-z3-xperia-z3-compact/
Please search, there is a lollipop ? thread already
Thread closed
The Sony Xperia Z2 and Z3 devices are both amongs one of Sony's best smartphones ever that they has released. By signing this petition, we will all let Sony take action and update our precious Z2 and even Z3 devices to Android Nougat!
But what about Vulkan API support???
Anything is possible, and we will prove to Google and Sony that having the minimum requirements for software to work correctly, is plain garbage, and that Vulkan API can be left out for them, because it's not like the Vulkan API is a necessity for Nougat in order to run correctly.
ANYMORE QUESTIONS WILL BE BROUGHT UP FROM THE COMMENTS ONTO THE OP AND ANSWERED HERE.
SIGN THIS PETITION NOW!: http://bit.ly/2eEwqN5
Thanks!
I Just Want A Stable 7.0 Build For Z2
Man i think this is impossible. Qualcomm completely left the development of the SD800/801 and if Sony update our devices without permission of Google, they will be in a big trouble. To me, this is impossible.
You are totally right Little Snevil. I also think that official update it's impossible because Qualcomm processor.
Enviado do meu D6503 através de Tapatalk
Well, MAYBE it is possibile to get android 7.0 on snap 801. Just look http://www.techtimes.com/articles/1...coming-soon-geekbench-benchmark-hints-yes.htm
This is sad, but change.org never has been listed by Google or Sony, like happen with z1 and marshmallow, Xperia L and kit kat, Xperia sp and kit kat. The true is Google and Sony never listen to users, only look the sales, and for those is better for him sale the new and forget the old
what i can say in that?
@Brandon Nel
Having a petition is a good idea, and I am not against it.
But there are two questions I would like to raise before proceeding to sign the petition:
1. Our Z3 and Z2 has been released for 24 and 30 months already, this already exceed the normal aftermarket support for Android devices (usually it goes among 18 to 24 months). Although you might say there has been rule breakers recently (for instance the Xperia Z that has almost 36 months of follow up upgrade), but however there are also some far below standard devices (eg Xperia C, which has no android upgrade since release). After all, Qualcomm, Sony and any other companies still have to make money for R&D and make a living, right? So I am thinking that shouldnt we live with what we are having now (AOSP 7.0)?
2. Shouldnt Qualcomm the company you should challenge against? Vulkan and OpenGS are featured in the chipset which is manufactured by QC, not Sony!
We should petition Qualcomm & Google instead of Sony.. Sony tried their best to bring Nougat through their Beta program for Z3.
But due to the lack of chipset updates from Qualcomm and the Vulkan API requirement set by Google, so many devices have been abandoned from the update even though they are fully capable to run N. This includes Z2 & Z3.
So in this case, either Qualcomm has to release update to our chipset or we have to force Google to remove mandatory Vulkan API requirement.
i need to pls make stable nougat..........................
artsfreaky said:
i need to pls make stable nougat..........................
Click to expand...
Click to collapse
Then sign the petition and prey
Sent from my Sony D6503 using XDA Labs
Paste a link to the petition on Twitter Sony and Sony News
//This is purely an opinion, might be treated as sarcasm, but it is an opinion
1. Nougat is bad for me, it is uglier and security is even worse because of getting more strict.
2. It is nearly impossible to push this through, because now you need to actually HAVE that VulkanAPI support in order to get a cert from google to use gapps(Noone will use Vulkan straight away, because of fragmentation, but well, three billion devices run java, now three billion devices will have to run Vulkan as well and if not, they'll die)
Any effort is worthwhile haha. This should be shared in the Z3 forums!
Well, Sony published AOSP for Xperias. This might mean something, maybe they will be able to somehow get that cert.
Did you see this :
Sony is not to blame for leaving the Xperia Z3 off the Android Nougat list
http://www.xperiablog.net/2016/08/3...ng-the-xperia-z3-off-the-android-nougat-list/
All devices with SD 800/801 will not updated to Android N 7.0 , Because of Qulacomm .
Alaa | Google Android said:
Did you see this :
Sony is not to blame for leaving the Xperia Z3 off the Android Nougat list
http://www.xperiablog.net/2016/08/3...ng-the-xperia-z3-off-the-android-nougat-list/
All devices with SD 800/801 will not updated to Android N 7.0 , Because of Qulacomm .
Click to expand...
Click to collapse
Not because of Qualcomm, but because of Google. They made Vulkan obligatory for getting certs. No one is going to use it from day one of Nougat anyway, because fragmentation, they want to push APIs, but Nougat isn't like 99% of Android right now. Although it might be handy when it reaches higher shares due to Vulkan's performance.
Hello
Asking all developers to start a discussion on what the minimum API level is that you support, and have you decided to drop support for older APIs and if so what the reasons are. The reason for starting this discussion comes from the frustrations caused by having to support older API levels. Yes it's important to support as many users as possible - not everybody has access to the latest and greatest devices / Android versions, my own day to day device is a Samsung Galaxy S6 with Android 6.0.1. Although I have access to a device with Android 7.1 and one with Lollipop. However there is only so far back you can go in terms of support before development starts to get frustrating and in the end the question has to be asked if it is really worth it.
Please first take a look at https://developer.android.com/about/dashboards/index.html for the latest device stats.
For some background, I'm the developer of this app http://forum.xda-developers.com/android/apps-games/quick-gallery-photo-editor-t3394976 and https://play.google.com/store/apps/details?id=com.mobato.gallery. Currently min API 16 is supported, but I am thinking of making this 19 (KitKat), or dropping JellyBean support all together and just supporting Lollipop onwards. I will aim to explain why.
Recently I have added SD Card support. Anybody who has implemented proper SD Card support in their apps knows how frustrating this can be, especially with the new permissions required from the user in Lollipop onwards as part of the storage access framework (this is so bad that I even made a tutorial with screenshots showing the user how to grant access the SD Card, I have seen real users get confused by the SAF permissions activity). On KitKat it is impossible to write to the SD Card unless the device is rooted. This resulted in lots of negative reviews for apps when this limitation was introduced. Prior to KitKat all that was required was the write access permission to be declared in the application manifest. As you can see there are three different scenarios to write code for and test (pre-KitKat, KitKat and Lollipop onwards) which adds to development time/costs and bug fixing can become extremely cumbersome having to do full regression tests. However KitKat is still very popular. Since I don't even own a KitKat device it's impossible to test this scenario, let alone a rooted version (emulators only go so far).
Here are some additional facts:
KitKat devices account for 24% of checkins to Google Play
The 24% of KitKat users combined with older API levels (down to API 2.2) account for a whopping 39.3% of users checking in to Google Play.
Memory management for bitmaps just isn't great prior to Lollipop (lots of OOM can occur even with careful memory management as I have seen from crash reports).
JellyBean 4.4.4 got released in October 31, 2013. That's just over 3 years ago. In the world of mobile, that's equivalent to an entire period of geology such as the Jurassic Period.
JellyBean is discontinued according to https://en.wikipedia.org/wiki/Android_version_history
Fact: most of the bad reviews for my app are coming from users with low-end devices running older versions of Android, Lollipop onwards users generally leave more favourable reviews.
So in conclusion I am thinking about dropping support for KitKat and older at some point unless anybody believes it is worth supporting still? The question is how likely are those users ever going to make in-app purchases, although from a perspective of just showing adverts it might be worth it.
Please share your experiences with your apps and contribute your ideas.
g313 said:
Hello
Asking all developers to start a discussion on what the minimum API level is that you support, and have you decided to drop support for older APIs and if so what the reasons are. The reason for starting this discussion comes from the frustrations caused by having to support older API levels. Yes it's important to support as many users as possible - not everybody has access to the latest and greatest devices / Android versions, my own day to day device is a Samsung Galaxy S6 with Android 6.0.1. Although I have access to a device with Android 7.1 and one with Lollipop. However there is only so far back you can go in terms of support before development starts to get frustrating and in the end the question has to be asked if it is really worth it.
Please first take a look at https://developer.android.com/about/dashboards/index.html for the latest device stats.
For some background, I'm the developer of this app http://forum.xda-developers.com/android/apps-games/quick-gallery-photo-editor-t3394976 and https://play.google.com/store/apps/details?id=com.mobato.gallery. Currently min API 16 is supported, but I am thinking of making this 19 (KitKat), or dropping JellyBean support all together and just supporting Lollipop onwards. I will aim to explain why.
Recently I have added SD Card support. Anybody who has implemented proper SD Card support in their apps knows how frustrating this can be, especially with the new permissions required from the user in Lollipop onwards as part of the storage access framework (this is so bad that I even made a tutorial with screenshots showing the user how to grant access the SD Card, I have seen real users get confused by the SAF permissions activity). On KitKat it is impossible to write to the SD Card unless the device is rooted. This resulted in lots of negative reviews for apps when this limitation was introduced. Prior to KitKat all that was required was the write access permission to be declared in the application manifest. As you can see there are three different scenarios to write code for and test (pre-KitKat, KitKat and Lollipop onwards) which adds to development time/costs and bug fixing can become extremely cumbersome having to do full regression tests. However KitKat is still very popular. Since I don't even own a KitKat device it's impossible to test this scenario, let alone a rooted version (emulators only go so far).
Here are some additional facts:
KitKat devices account for 24% of checkins to Google Play
The 24% of KitKat users combined with older API levels (down to API 2.2) account for a whopping 39.3% of users checking in to Google Play.
Memory management for bitmaps just isn't great prior to Lollipop (lots of OOM can occur even with careful memory management as I have seen from crash reports).
JellyBean 4.4.4 got released in October 31, 2013. That's just over 3 years ago. In the world of mobile, that's equivalent to an entire period of geology such as the Jurassic Period.
JellyBean is discontinued according to https://en.wikipedia.org/wiki/Android_version_history
Fact: most of the bad reviews for my app are coming from users with low-end devices running older versions of Android, Lollipop onwards users generally leave more favourable reviews.
So in conclusion I am thinking about dropping support for KitKat and older at some point unless anybody believes it is worth supporting still? The question is how likely are those users ever going to make in-app purchases, although from a perspective of just showing adverts it might be worth it.
Please share your experiences with your apps and contribute your ideas.
Click to expand...
Click to collapse
You're right about bitmap memory management (I had an infinite System UI FC on CM 11 when I got too many notifications (from YouTube, by the way)
Sent from my GT-S7580 using Tapatalk
i want to run marshmallow apps on jellybean 4.1.2
g313 said:
Hello
Asking all developers to start a discussion on what the minimum API level is that you support, and have you decided to drop support for older APIs and if so what the reasons are. The reason for starting this discussion comes from the frustrations caused by having to support older API levels. Yes it's important to support as many users as possible - not everybody has access to the latest and greatest devices / Android versions, my own day to day device is a Samsung Galaxy S6 with Android 6.0.1. Although I have access to a device with Android 7.1 and one with Lollipop. However there is only so far back you can go in terms of support before development starts to get frustrating and in the end the question has to be asked if it is really worth it.
Please first take a look at https://developer.android.com/about/dashboards/index.html for the latest device stats.
For some background, I'm the developer of this app http://forum.xda-developers.com/android/apps-games/quick-gallery-photo-editor-t3394976 and https://play.google.com/store/apps/details?id=com.mobato.gallery. Currently min API 16 is supported, but I am thinking of making this 19 (KitKat), or dropping JellyBean support all together and just supporting Lollipop onwards. I will aim to explain why.
Recently I have added SD Card support. Anybody who has implemented proper SD Card support in their apps knows how frustrating this can be, especially with the new permissions required from the user in Lollipop onwards as part of the storage access framework (this is so bad that I even made a tutorial with screenshots showing the user how to grant access the SD Card, I have seen real users get confused by the SAF permissions activity). On KitKat it is impossible to write to the SD Card unless the device is rooted. This resulted in lots of negative reviews for apps when this limitation was introduced. Prior to KitKat all that was required was the write access permission to be declared in the application manifest. As you can see there are three different scenarios to write code for and test (pre-KitKat, KitKat and Lollipop onwards) which adds to development time/costs and bug fixing can become extremely cumbersome having to do full regression tests. However KitKat is still very popular. Since I don't even own a KitKat device it's impossible to test this scenario, let alone a rooted version (emulators only go so far).
Here are some additional facts:
KitKat devices account for 24% of checkins to Google Play
The 24% of KitKat users combined with older API levels (down to API 2.2) account for a whopping 39.3% of users checking in to Google Play.
Memory management for bitmaps just isn't great prior to Lollipop (lots of OOM can occur even with careful memory management as I have seen from crash reports).
JellyBean 4.4.4 got released in October 31, 2013. That's just over 3 years ago. In the world of mobile, that's equivalent to an entire period of geology such as the Jurassic Period.
JellyBean is discontinued according to https://en.wikipedia.org/wiki/Android_version_history
Fact: most of the bad reviews for my app are coming from users with low-end devices running older versions of Android, Lollipop onwards users generally leave more favourable reviews.
So in conclusion I am thinking about dropping support for KitKat and older at some point unless anybody believes it is worth supporting still? The question is how likely are those users ever going to make in-app purchases, although from a perspective of just showing adverts it might be worth it.
Please share your experiences with your apps and contribute your ideas.
Click to expand...
Click to collapse
i want to run marshmallow apps on jellybean 4.1.2 by decompiling particular app and editing its manifest.xml then change the minsdkversion to 16. is it possible? i tried it by decompling the file but i havent found any minsdkversion in manifest file after decompiling the apk.i downloaded an app called solid explorer and there is an option in it to open the apk file but that apk is not decompiled.so i took compiled apk ,i opened compiled apk file and then to manifest file after opening it i can see the minsdk version and other platform versions remember that was compiled apk file.
please tell me how to do this.
I guess we are done for security updates. It has been right at 2 years. Sad thing is, this is still a great little phone. I am not in the mood to root and tinker with issues. I wished there was a stable ROM out there to use. I wished that LineageOS would pick this little jewel up. Oh, well. It has been a good 2 years of a small, but very informative community of X Compact users.
I am still searching for a small phone replacement since Sony does not make small phones anymore. Post here if you have any recommendations.
Cheers!
del
I feel you. I think I've said it before on this forum, but I really don't get why there isn't a lineageos build for this phone. Lots of sony xperia phones have official lineageos builds and there even is an unofficial build for this device (so it's not exactly impossible to build).
That being said, I generally prefer omnirom and luckily they are supporting this device. I've been on omnirom 8.1 for ages and haven't encountered a bug yet, so imho it can definitely be considered stable. Right now I'm using a self-built omnirom 9.0 (security patch level 5 november 2018) as a daily driver and for a pre-official build it is already pretty stable. Sony's 'Pie' software binaries (which thankfully they still provide) are still in beta, so coupled with the omnirom team efforts the stability will only increase.
Bottom line for smartphone manufacturers: Just provide what is needed for the open source community to flourish, it'll cost you next to nothing and will pay you back in goodwill many times over.
Next upcoming problem is the lack of support for the Project Treble in Xperia X series devices which at least may cause significant delay in releasing ROMs based the newer Android versions or in the worst case might result in stopping their development as the successor - XZ1 series - supports it. I hope developers will follow the Z5 series path as there already is LineageOS for these. And hopefully some Xiaomi devices path as there are devices which now have unofficial support of the Project Treble.
BTW, we should also thank to the Google for an unwise cycle of releasing new Android version every year which accelerates fragmentation significantly as its main reason seems to be to persuade people to buy newer devices with latest version of Andoid OS on board.
harryharryharry said:
Lots of sony xperia phones have official lineageos builds and there even is an unofficial build for this device (so it's not exactly impossible to build).
Click to expand...
Click to collapse
I suppose more recent Sony smartphones have been sold in significantly lower quantities than older ones (I read many times about Sony's smartphones poor sales numbers) and it might be the reason of a smaller community gathered around those newer devices.
Software security updates stopped?
If Sony stops providing software updates after 2y, it means those of us with a Sony Xperia X Compact (F5321) are unable to add Work e-mail accounts as the Microsoft Intune app requires an Android software update dated May 2019.
This silly policy by Sony is preventing me from adding my work O365 account to the device and means I am very unlikely to buy another Sony mobile phone ever again as its usable life is 2 years max. I am actually quite raging because I like the phone -this is beyond stupid from Sony.
RTV_1974 said:
If Sony stops providing software updates after 2y, it means those of us with a Sony Xperia X Compact (F5321) are unable to add Work e-mail accounts as the Microsoft Intune app requires an Android software update dated May 2019.
This silly policy by Sony is preventing me from adding my work O365 account to the device and means I am very unlikely to buy another Sony mobile phone ever again as its usable life is 2 years max. I am actually quite raging because I like the phone -this is beyond stupid from Sony.
Click to expand...
Click to collapse
use browser.
intune sucks anyway.
RTV_1974 said:
If Sony stops providing software updates after 2y, it means those of us with a Sony Xperia X Compact (F5321) are unable to add Work e-mail accounts as the Microsoft Intune app requires an Android software update dated May 2019.
This silly policy by Sony is preventing me from adding my work O365 account to the device and means I am very unlikely to buy another Sony mobile phone ever again as its usable life is 2 years max. I am actually quite raging because I like the phone -this is beyond stupid from Sony.
Click to expand...
Click to collapse
This device has pretty lackluster support even in the dev community as well. All it's really got going for it atm but fortunately we have Lineage 17.1 and Project Treble. I recommend flashing a new rom if you don't want to switch phones.