No vulkan support for m9 - One (M9) General

Ya a bad notice on the new Nougat update... check reddit for more info, i can't post links :crying:

What the hell. The Nexus 6p with the exact same chipset has Vulkan

Yes, alas. I don't believe it'd be better anyway if we had it, meaning the bugs we'd face with the drivers otherwise.
Still, +shame on Google+ proudly announcing their nougat = vulkan support -- not having discussed the matter with at least most prominent market players in advance. As to the QC, they never promised anything I gather.

Never again htc
Wyslane z mojego M9 przy uzyciu Tapatalka

piterdemon said:
Never again htc
Click to expand...
Click to collapse
Do buy Samsung then, there's full vulkan support for Nougat, s7 & edge.

Check out S.Team M9 rom thread. The dev announced a new HTC 10 Nougat rom port with vulkan support ?

Sooo, Snapdragon 801 devices "couldn't" receive official nougat because the SoC can't support Vulkan and it's required to pass CTS, and then wild M9 appears and receives official Nougat without Vulkan support and nothing happens. Yeah...
Sent from my HTC One M9 using Tapatalk

Related

Android 7.0 Update

So I Saw the news on AA and I don't know but it said here that most of the Motorola devices will receive Android 7.0. My confusion is that: will Moto X play receive 7.0 as well?
http://www.androidauthority.com/android-7-0-update-679175/
I guess we are out of luck on this one. I got my X Play in January. It came with Lollipop, but I could almost immediately upgrade to Marshmallow. Security level was "December 2015". Last April we could upgrade to March 2016 and since then there is no release except one for India. Since then Google has released updates :
April : https://source.android.com/security/bulletin/2016-04-02.html
May : https://source.android.com/security/bulletin/2016-05-01.html
June : https://source.android.com/security/bulletin/2016-06-01.html
July : https://source.android.com/security/bulletin/2016-07-01.html
August : https://source.android.com/security/bulletin/2016-08-01.html
Each of these updates contains at least one (but up to eight) updates which are marked Critical.
I think any manufacturer has reasons to deploy these updates. Since it requires a lot of effort I'm not expecting an OTA each month, but it would be nice to see an OTA every 2-3 months. No news from Motorola is bad news for me. It seems they move on to the next series of devices.
After 5 months "your device is up to date", I've had it. My phone has been unlocked last week, and it now runs one of the custom ROMs found here. It has the July update, and I am expecting an OTA update for my ROM soon.
An 2015 phone without 7.0? No way. I hope we will receive it in 2017.
Enviado desde mi XT1563 mediante Tapatalk
asing said:
I guess we are out of luck on this one. I got my X Play in January. It came with Lollipop, but I could almost immediately upgrade to Marshmallow. Security level was "December 2015". Last April we could upgrade to March 2016 and since then there is no release except one for India. Since then Google has released updates :
April : https://source.android.com/security/bulletin/2016-04-02.html
May : https://source.android.com/security/bulletin/2016-05-01.html
June : https://source.android.com/security/bulletin/2016-06-01.html
July : https://source.android.com/security/bulletin/2016-07-01.html
August : https://source.android.com/security/bulletin/2016-08-01.html
Each of these updates contains at least one (but up to eight) updates which are marked Critical.
I think any manufacturer has reasons to deploy these updates. Since it requires a lot of effort I'm not expecting an OTA each month, but it would be nice to see an OTA every 2-3 months. No news from Motorola is bad news for me. It seems they move on to the next series of devices.
After 5 months "your device is up to date", I've had it. My phone has been unlocked last week, and it now runs one of the custom ROMs found here. It has the July update, and I am expecting an OTA update for my ROM soon.
Click to expand...
Click to collapse
Well.... crap, I really hoped that it'll get 7.0, so many features to try out.
luchardi said:
An 2015 phone without 7.0? No way. I hope we will receive it in 2017.
Enviado desde mi XT1563 mediante Tapatalk
Click to expand...
Click to collapse
hope so.
No worries, CM13 will keep this phone running
Sent from my XT1562 using XDA-Developers mobile app
it's official? we were off 7.0 ??
Enviado desde mi XT1563 mediante Tapatalk
My humbled opinion is that we will get android 7 for sure. Lenovo support moto devices minimally with 2 big system updates and our moto got just one (marshmallow) yet. So I am quite optimistic if you ask me...
We can only speculate until they officially announce about if they will release or not.
Pretty sure the phone can support 7.0
At least SD615 is on the list of 7.0 supported SoCs, so fingers crossed:
https://en.m.wikipedia.org/wiki/Android_Nougat#Unsupported_and_supported_processors
minimale_ldz said:
At least SD615 is on the list of 7.0 supported SoCs, so fingers crossed:
https://en.m.wikipedia.org/wiki/Android_Nougat#Unsupported_and_supported_processors
Click to expand...
Click to collapse
huh? "According to a prominent source, Qualcomm is not releasing updates to the graphic drivers on the Snapdragon 200, 208, 210, 212, 400, 410, 412, 600,615, 800 and 801 chipsets"
Benjamin_L said:
huh? "According to a prominent source, Qualcomm is not releasing updates to the graphic drivers on the Snapdragon 200, 208, 210, 212, 400, 410, 412, 600,615, 800 and 801 chipsets"
Click to expand...
Click to collapse
Someone made a bad joke, 615 was on supported devices list when I linked it, so no worries
Here's another surce. According to it SD615 supports Vulkan 1.0:
https://en.wikipedia.org/wiki/Vulkan_(API)#Compatibility
minimale_ldz said:
Here's another surce. According to it SD615 supports Vulkan 1.0:
https://en.wikipedia.org/wiki/Vulkan_(API)#Compatibility
Click to expand...
Click to collapse
Aaahhh i already found it, but you where first to post it
but if found another wiki page about the Adreno
As you can see the Adreno (graphical chip) of the Moto x play is supported(405) which is included in the Snapdragon 615
So there is hope for android 7
All 2015 moto x series are getting android N
I think N will be 64 bit.

Xperia Z3 won't get Android N

http://blogs.sonymobile.com/2016/08/23/sony-xperia-and-android-7-0-nougat/
Sadly our device can't get Android N :crying:
[edit] http://www.phonearena.com/news/No-Nougat-for-your-Android-phone-You-might-want-to-blame-Qualcomm_id84543
snailpon said:
http://blogs.sonymobile.com/2016/08/23/sony-xperia-and-android-7-0-nougat/
Sadly our device can't get Android N :crying:
Click to expand...
Click to collapse
Well, just as I thought. I have some hope on developers here, but considering how little work has been done with AOSP and CM I can't expect too much
ridiculous they were teased with devolved Android n
Sent from my D6603 using XDA-Developers mobile app
Me too.. I will probably sell my D6603, Sony just disappointed me.
Anyway I'm open to suggestions
codeluca said:
Me too.. I will probably sell my D6603, Sony just disappointed me.
Anyway I'm open to suggestions
Click to expand...
Click to collapse
Personaly I would go with OP3 or nexus devices. Good specs and developer friendly.
I like OP3 and Xiaomi mi5 but I would miss the SD card... I would consider Huawei P9 or LG G5, but these have poor developer support. Any alternative?
Gesendet von meinem D6603 mit Tapatalk
Thank you Sony for making me absolutely sure that I'll never ever buy a Sony phone again.
Zox09 said:
Thank you Sony for making me absolutely sure that I'll never ever buy a Sony phone again.
Click to expand...
Click to collapse
I have hope for the community, we'll make it through with better sources and faster updates than what Sony had to offer us. Hopefully official Cyanogenmod comes our way.
TheAvengingTITAN said:
I have hope for the community, we'll make it through with better sources and faster updates than what Sony had to offer us. Hopefully official Cyanogenmod comes our way.
Click to expand...
Click to collapse
I would have hope if it wasn't for the fact that we don't have an official CM13 yet. All the builds of the CM12.1 are even nightlies and don't offer the audio and camera quality that Stock has. Let's be real, Sony sucks at open sourcing and the community can't do magic
Sure it sucks, but why is anyone surprised? The Z3 launched September of 2014, almost two years ago.
You really can't blame Sony, two years is pretty standard for updates. Even Google only gives two years of guaranteed updates for the Nexus line.
iirc the concept developers are trying to release the kernel sources, which would allow the devs on xda to build better roms.
Sent from my D6603 using XDA-Developers mobile app
The Z3 is an really nice device. Sad to see that Sony say goodbye to us. I hope customs ROMS can help.
I have Android Nougat 7 Preview 4 running on my Xperia Z3 (and it spontaneously reboots 24 times a day which is a major problem that hopefully the real version will fix). I mean how can they NOT release a real version of Android Nougat?
Well the user base did come together and made Sony change their minds about Xperia M2 and lollipop update... At first it was cut out after which Sony later decided to roll out lollipop for that model...
Sent via Xperia Z3
I think z3 shouldn't use mm or lollipop rom. Because the device will be very hot and it'll make touch screen died. I know someboby have to replace thier touch screen.
Sony cant release N for z3. Google/ Qualcomm removed msm8974 support from aosp N kernel. Sony would have to revert these commits which is the legal issues that the concept Dec was talking my about on g+
Silent8Strike said:
Sure it sucks, but why is anyone surprised? The Z3 launched September of 2014, almost two years ago.
You really can't blame Sony, two years is pretty standard for updates. Even Google only gives two years of guaranteed updates for the Nexus line.
Click to expand...
Click to collapse
Meanwhile, Apple released the last iOS 9.3.4 on the iPhone 4S, released in 2011.
Talk about standards. SMH.
kansasboy001 said:
Sony cant release N for z3. Google/ Qualcomm removed msm8974 support from aosp N kernel. Sony would have to revert these commits which is the legal issues that the concept Dec was talking my about on g+
Click to expand...
Click to collapse
This means no device with Snapdragon 800/801 will get N.
That's disappointing considering it was working fine on Dev Preview 3.
brianpee said:
This means no device with Snapdragon 800/801 will get N.
That's disappointing considering it was working fine on Dev Preview 3.
Click to expand...
Click to collapse
I imagine it was a decision by Qualcomm to force people to get new phones so they sell more chips. And I bet we don't see and 801 devices get official N. Only 805 and later
moonwalker1 said:
iirc the concept developers are trying to release the kernel sources, which would allow the devs on xda to build better roms.
Sent from my D6603 using XDA-Developers mobile app
Click to expand...
Click to collapse
That's mean if kernel sources is out, we can build Android 7 rom without Unlock Bootloader?

ANDROID 7.0 for Oneplus X?!

Flood the comments section with OnePlus X, let's hope that it catches the eye of one of the developers! xD
http://www.xda-developers.com/which-device-do-you-want-an-android-7-0-nougat-custom-rom-on/
Isn't it too early for this thread?, The community build of marshmallow has just been released and we still have more to explore. Anyway i hope some developer may start working soon and we can taste the flavor of Nougat. CHEERS. ?
The important fact is that the OPX might never get official Nougat releases due to Qualcomm ceasing support for their 800/801 SoC (they won't be getting OpenGL ES 3.1, which is needed for official Android 7.0 releases).
This is going to impact on over 50 android smartphones.
Source: https://developer.qualcomm.com/foru...-hardware/mobile-gaming-graphics-adreno/27936
shatteringlass said:
The important fact is that the OPX might never get official Nougat releases due to Qualcomm ceasing support for their 800/801 SoC (they won't be getting OpenGL ES 3.1, which is needed for official Android 7.0 releases).
This is going to impact on over 50 android smartphones.
Source: https://developer.qualcomm.com/foru...-hardware/mobile-gaming-graphics-adreno/27936
Click to expand...
Click to collapse
damn. Well, is there any way around this?
R3XER said:
Isn't it too early for this thread?, The community build of marshmallow has just been released and we still have more to explore. Anyway i hope some developer may start working soon and we can taste the flavor of Nougat. CHEERS. ?
Click to expand...
Click to collapse
Well, no it's not early. We have been using Marshmallow on OnePlus X thanks to our beloved developers since a long time now. We've given up hope on OnePlus, it's all on our developers now
I don't think the news about sd 800/801 being incompatible is true, because Nexus 5 has already received a 7.0 build (alpha) and Xperia Z3 also got dev previews. Both of these are sd 800/801 devices. And also the OnePlus One:
gavisharora said:
I don't think the news about sd 800/801 being incompatible is true, because Nexus 5 has already received a 7.0 build (alpha) and Xperia Z3 also got dev previews. Both of these are sd 800/801 devices. And also the OnePlus One:
Click to expand...
Click to collapse
Original post for that image?
Samarth_17 said:
Original post for that image?
Click to expand...
Click to collapse
Not a post, my friend sent it.
yup..z3 already got N dev preview..anyway it doesnt matter if opx dont get official N if we can get CM nougat from our dev ?
Sent from my ONE E1003 using XDA-Developers mobile app
meraj99 said:
Well, no it's not early. We have been using Marshmallow on OnePlus X thanks to our beloved developers since a long time now. We've given up hope on OnePlus, it's all on our developers now
Click to expand...
Click to collapse
The OP X is a phone with less a year. They should provide at least 24 months of support.
Abandoning the support isn't exactly what I (and other customers I suppose) was searching for (I bought the OPX at day one).
Letting the support to the developers isn't the solution, because the are not paid and everything they do is for free and with less instruments. All of us paid OP for supporting.
If they aren't supporting anymore OPX surely I'm not going to buy an other OP and probably neither an Android. every year we are here to reading and expecting if a phone would be upgraded to the newest version. If you buy a high end phone certanly this will get 24 months of support, but if you are going to buy a midrange, you are going to pray for some updates. All the phone makers are just making fun of us.
A comparison: iphone 4s launched in 2011 with ios 5 and its lust update was ios 9. 4 year of support!
be_are said:
yup..z3 already got N dev preview..anyway it doesnt matter if opx dont get official N if we can get CM nougat from our dev
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
The only reason Z3 got developer preview is because sony n google want to test Android 7.0 on SD 800/801 powered devices
I guess their attempt ended up as a failure and so Z3 has been excluded from Sony update tree for Android 7.0
dani.galla said:
The OP X is a phone with less a year. They should provide at least 24 months of support.
Abandoning the support isn't exactly what I (and other customers I suppose) was searching for (I bought the OPX at day one).
Letting the support to the developers isn't the solution, because the are not paid and everything they do is for free and with less instruments. All of us paid OP for supporting.
If they aren't supporting anymore OPX surely I'm not going to buy an other OP and probably neither an Android. every year we are here to reading and expecting if a phone would be upgraded to the newest version. If you buy a high end phone certanly this will get 24 months of support, but if you are going to buy a midrange, you are going to pray for some updates. All the phone makers are just making fun of us.
A comparison: iphone 4s launched in 2011 with ios 5 and its lust update was ios 9. 4 year of support!
Click to expand...
Click to collapse
It's not as if OnePlus is stopping support. They can't do anything since Qualcomm isn't going to update graphics drivers for SD800/801, which is necessary for Vulkan APIs, which in turn is necessary to pass Google CTS. No Google CTS = no more official update for those chipsets. So it's actually a consequence of Qualcomm's action.
The only way we'll get Nougat is in the form of custom ROMs by the hard work of devs. But again, just to be clear, none of the Nougat custom ROMs will have the Vulkan APIs, since it just isn't possible for 800/801 (afaik). That said, personally I don't really care about official updates since I've been running custom ROMs from the beginning, and I'm sure the good devs will bring us some Nougat love too
dani.galla said:
The OP X is a phone with less a year. They should provide at least 24 months of support.
Abandoning the support isn't exactly what I (and other customers I suppose) was searching for (I bought the OPX at day one).
Letting the support to the developers isn't the solution, because the are not paid and everything they do is for free and with less instruments. All of us paid OP for supporting.
If they aren't supporting anymore OPX surely I'm not going to buy an other OP and probably neither an Android. every year we are here to reading and expecting if a phone would be upgraded to the newest version. If you buy a high end phone certanly this will get 24 months of support, but if you are going to buy a midrange, you are going to pray for some updates. All the phone makers are just making fun of us.
A comparison: iphone 4s launched in 2011 with ios 5 and its lust update was ios 9. 4 year of support!
Click to expand...
Click to collapse
the developers do earn money. By hosting, ads, donation, etc. :3 but yeah, OP has disappointed us
primemonitor said:
It's not as if OnePlus is stopping support. They can't do anything since Qualcomm isn't going to update graphics drivers for SD800/801, which is necessary for Vulkan APIs, which in turn is necessary to pass Google CTS. No Google CTS = no more official update for those chipsets. So it's actually a consequence of Qualcomm's action.
The only way we'll get Nougat is in the form of custom ROMs by the hard work of devs. But again, just to be clear, none of the Nougat custom ROMs will have the Vulkan APIs, since it just isn't possible for 800/801 (afaik). That said, personally I don't really care about official updates since I've been running custom ROMs from the beginning, and I'm sure the good devs will bring us some Nougat love too
Click to expand...
Click to collapse
The Qualcomm story is only a justification for the OEMs, because if they want, they can force Qualcomm to update the drivers.
If the developers can make a S 800/801 working with Android N (see Nexus 5), why can't do it the OEMs?
I personally care about official updates because they can't sold us fully bugged phones and let us search for the solution.
The custom roms are a hobby, something that we like doing, but most of people even know of the existance of XDA.
---------- Post added at 07:41 AM ---------- Previous post was at 07:36 AM ----------
meraj99 said:
the developers do earn money. By hosting, ads, donation, etc. :3 but yeah, OP has disappointed us
Click to expand...
Click to collapse
Yeah but most of them can't live with that momey. They just cover some outgoings.
Yeah I first time oneplus buyer but disappointed
dani.galla said:
The Qualcomm story is only a justification for the OEMs, because if they want, they can force Qualcomm to update the drivers.
If the developers can make a S 800/801 working with Android N (see Nexus 5), why can't do it the OEMs?
Click to expand...
Click to collapse
Sure, devs can get Nougat working on 800/801 but again, they will NOT support Vulkan APIs, as I said before. Any custom ROM for 800/801 devices won't support Vulkan API, to my knowledge. And that is essential for to pass CTS, and hence for official updates.
As for OEMs, I won't claim to know if they can force Qualcomm or not. Maybe they can, and maybe they even should. That would be great for everyone definitely. But regardless, I don't think the blame (if there's any) is to be pinned on OnePlus. It's Qualcomm's refusal to update graphics drivers which will force OEMs to drop support.
dani.galla said:
The Qualcomm story is only a justification for the OEMs, because if they want, they can force Qualcomm to update the drivers.
Click to expand...
Click to collapse
Not true. Many say that Adreno 3xx (the GPU on SD800/801) simply does not have hardware support for OpenGL ES 3.1. The only possible alternative is software emulation of such hardware features (which is supposedly a very difficult goal and might expose users to buggy UX and/or to bad battery life). The original problem is OpenGL ES 3.1 (mobile library) came out in 2014, but its features are from OpenGL 4.3 and 4.4 (desktop libraries from 2012 and 2013) So its Qualcomm's fault for either not bothering with updating the 800/801 firmware or for not designing their GPUs to support the current OpenGL version at the time. In fact, ARM's 2012 GPUs support OpenGL ES 3.1 and AEP (both from 2014) and their 2013 GPUs support OpenGL ES 3.2 and Vulkan (from 2015 and 2016).
This ^^^
gavisharora said:
I don't think the news about sd 800/801 being incompatible is true, because Nexus 5 has already received a 7.0 build (alpha) and Xperia Z3 also got dev previews. Both of these are sd 800/801 devices. And also the OnePlus One:
Click to expand...
Click to collapse
I looked at a Nexus 5 ROM thread today. Lots of stuff was broken. Unless QC puts out official sources, Nougat is going to be a buggy affair for anything with an 800/1 SoC.
More news related to this :
http://www.androidauthority.com/android-7-0-snapdragon-800-801-712930/
I don't get the whole thing, but looks like its possible the problem might not be related to Vulkan. I guess we need to wait for the Android Compatibility Definition Document for Nougat to really know what the actual issue could be.
http://www.androidauthority.com/android-7-0-snapdragon-800-801-712930/
apparently, it isn't the VULKAN causing the problems. There are alternative ways around this. They just want us to buy newer devices

Do you think Z5 will get Android 8?

i saw at the beta android O got cool improvement
if not 8 i hope will get at least lastest version 7.1.2
No, I don't think so..
I am absolutely sure we will get android o.
Sent from my E6653 using Tapatalk
I don't think so either
Sent from my E6683 using Tapatalk
Absolutely not. The best you could hope for is 7.1.1 or 7.1.2.
no. probably android 7.1 android 8
never
No, sony is just retarded.
the best news will be Z5 WONT get Android 8.
Z5 with 3gb ram, the best build so far has been Android 6 - 32.2.A.5.11 , it was the last build on Android 6.
ever since on android 7, the device overheats and battery life is a bit shorter and ram usage is high.
YES i agree sony has ditched Z5 poorly after announcing that Z project has been discontinued and z5 was never properly distributed or marketed (atleast not in my country)
the same goes for the upcoming builds where they are focusing more on X series and when in Jan2017 X got android 7, z5 also prompted for an update to 7.
I will be downgrading my z5 to 32.2.A.5.11 and will keep it there for good!
It would be nice, let see what demands will it have
I too tried nougat, no go without xposed, sticking with rock solid marshmallow
Yes - there's a very active development community - OP never stated from $ony
Z2,Z3--> 6.0.1
Z3+,Z5-->7.1.1/7.1.2
Sony makes devices as pair...
You guys know that nougat was planned for z3, and it even had developer preview build, but google or qualcomm messed up with some drivers or requirements, so all snapdragon 801 devices didnt get nougat update.
Sent from my E6653 using Tapatalk
Official Android O? Sony tried to update the Z3 to Nougat (it would have gone 4.4 -> 7.0) and were only stopped by Qualcomm/Google/driver issues. No reason for the Z5 to not get 8.0
may be 8.0 requires Vulcan which z5 lacks ??????????????????
ytheekshana said:
may be 8.0 requires Vulcan which z5 lacks ??????????????????
Click to expand...
Click to collapse
*Vulkan
I think we won't get O as our update support ends soon, the 2 years of update support is soon on EOL and I'm sure Sony is waiting for that so they don't have to update anymore.
Well I have an Z5 Premium but the whole kitakami series (Z3+ to Z5) gets nearly same updates.
I would be happy if Sony wouldn't mess up FWs like they did with Nougat but well I'm sure they did that because This series should die to replace it with the messy X series.
So don't expect too much guys. You also don't need to expect so much that we get 7.1.2
When XZ1 and so on are released we also can say goodbye to our devices finally because Sony will dead patch them like they did with Z3 (look battery life between 5.1.1 and 6.0.1)
So my hope goes to OnePlus 5 for now
Your PDesire
I just bought this device a week ago. I'm not worried about not getting Android O. But rather worried about not getting a stable version of Nougat.
Sent from my E6683 using XDA-Developers Legacy app
zer0se7en said:
I just bought this device a week ago. I'm not worried about not getting Android O. But rather worried about not getting a stable version of Nougat.
Sent from my E6683 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Don't worry, latest Nougat (.33) is stable
nreuge said:
Don't worry, latest Nougat (.33) is stable
Click to expand...
Click to collapse
I'm not sure.I think it's still not stable...

No Android 8 Oreo for our Z4 tablets

In case someone has missed it, the Z4 Tablet is not on Sonys list with devices that will get the update. Since it is Sonys last tablet and still one of the best Android tablet I think it would have made sense to keep it updated.
It runs okay with stock 7.1.1 but some of the Oreo updates would be nice to have, like improved multi window support and picture-in-picture.
I guess there will be some custom ROMs to try out, but in this case I actually like Sonys UI better, with the keyboard support (shortcuts and start menu etc.).
dape16 said:
In case someone has missed it, the Z4 Tablet is not on Sonys list with devices that will get the update. Since it is Sonys last tablet and still one of the best Android tablet I think it would have made sense to keep it updated.
It runs okay with stock 7.1.1 but some of the Oreo updates would be nice to have, like improved multi window support and picture-in-picture.
I guess there will be some custom ROMs to try out, but in this case I actually like Sonys UI better, with the keyboard support (shortcuts and start menu etc.).
Click to expand...
Click to collapse
Source for the Z4 tablets not getting Oreo?
Aredubu said:
Source for the Z4 tablets not getting Oreo?
Click to expand...
Click to collapse
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Wow, that sucks.
Sent from my Pixel XL using Tapatalk
This is the latest tablet in Sony portfolio.
No Oreo = I will never again buy Sony device.
Howgh.
Without sources It's hard to make custom oreo rom. But it definately possible as it is with xiaomi redmi note 2, for example.
Since z5 itself it not getting oreo then it was obvious the tablet as well. If sony do as always then we will have AOSP release from them for this tablet and z5
Very disappointed ?
Sent from my SGP712 using XDA-Developers Legacy app
From what I understand there will be no BSP for Oreo on the 810 processor based SOC. It's tough to blame Sony for this one, IMHO this lands on Qualcomm.
No. It's Sony responsibility to push Quallcomm.
Most sony devices use mediatek now so probably Qualcomm no longer is a good partner for Sony
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
wag3slav3 said:
From what I understand there will be no BSP for Oreo on the 810 processor based SOC. It's tough to blame Sony for this one, IMHO this lands on Qualcomm.
Click to expand...
Click to collapse
There are phones with 810 SOC that has gotten Oreo already so that is false.
dape16 said:
There are phones with 810 SOC that has gotten Oreo already so that is false.
Click to expand...
Click to collapse
...such as?
knoxploration said:
...such as?
Click to expand...
Click to collapse
Nexus 6P and maybe others.
Any other examples?
I'm not sure which kernel is running on 6p on oreo, but on my nexus 5x (oreo 8.1) it's 3.10. This is a violation of google policy that for oreo kernel must be at least 4.4.
So i would suspect that 6p is an exception confirming the rule.
Sent from my Galaxy S8 using XDA Labs
awionetka said:
Any other examples?
I'm not sure which kernel is running on 6p on oreo, but on my nexus 5x (oreo 8.1) it's 3.10. This is a violation of google policy that for oreo kernel must be at least 4.4.
So i would suspect that 6p is an exception confirming the rule.
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
That's not really correct, according to Google's kernel version requirements:
- All SoCs productized in 2017 must launch with kernel 4.4 or newer.
- All other SoCs launching new Android devices running Android 8.0 must use kernel 3.18 or newer.
- Regardless of launch date, all SoCs with device launches on Android 8.0 remain subject to kernel changes required to enable Treble.
-Older Android devices released prior to Android 8.0 but that will be upgraded to Android 8.0 can continue to use their original base kernel version if desired.
Source: https://source.android.com/devices/architecture/kernel/modular-kernels#core-kernel-requirements
I think even the Pixel / Pixel XL is running Oreo on 3.18 kernels.
Its like when the snap 801 devices didnt get nougat all over again. Google are good at killing worthy devices. All 801 devices were perfectly fine and capable of running nougat but it was never offically supported. Its also like the Sony SmartWatch 3 how they killed that with no AW 2.0 update. It has nfc which can be used for Android pay but is now useless without AW 2.0. Also the SmartWatch 3 has WiFi and alot of other things some android wear 2.0 devices dont have. Google just keep killing our devices with less updates to make us buy new ones.
RJASSI21 said:
Its like when the snap 801 devices didnt get nougat all over again. Google are good at killing worthy devices. All 801 devices were perfectly fine and capable of running nougat but it was never offically supported. Its also like the Sony SmartWatch 3 how they killed that with no AW 2.0 update. It has nfc which can be used for Android pay but is now useless without AW 2.0. Also the SmartWatch 3 has WiFi and alot of other things some android wear 2.0 devices dont have. Google just keep killing our devices with less updates to make us buy new ones.
Click to expand...
Click to collapse
Why do you keep blaming Google for this? Google did update their own devices with the same chipset as Sony Tablet Z4 (Nexus 6P) or lower spec (Nexus 5X) to Oreo.
The Nexus and even Pixels runs 3.x kernels too so Google is not stopping Sony from updating the Z3+/Z4/Z5-series to Oreo!
Regarding the SmartWatch 3, again why blame Google for this? It has the Snapdragon 400 chipset which is compatible with Wear 2.0 (LG updated their G-watches with SD400 to Wear 2.0).
Instead it was Sony that stated something like "SwartWatch 3 runs better with it's current version of Wear". The same BS excuse that Sony and other OEMs often use when they abandon fully capable products.
Google can't force OEMs to update their devices, the just give them the tools to do it. Which in these cases Sony don't want to use.
According to xperiablog, SONY just sold 18300 Z4 Tablets. I am pretty sure the customer wants to use a current OS with security patches.
http://www.xperiablog.net/2018/01/26/french-police-make-huge-order-for-sony-xperia-devices/
DHGE said:
According to xperiablog, SONY just sold 18300 Z4 Tablets. I am pretty sure the customer wants to use a current OS with security patches.
http://www.xperiablog.net/2018/01/26/french-police-make-huge-order-for-sony-xperia-devices/
Click to expand...
Click to collapse
According to the article they will run a (modified) stock version of Android. The demo unit in the photo seems to be running Jelly Bean or KitKat!

Categories

Resources