Database Users

Kernel source

Latest YotaPhone2 Kernel Sources - If you are developing for the YotaPhone 2 the latest kernel sources are now available in the form of a 100Mb download direct from their server. If you have been waiting for them, you can pick them up now! http://ow.ly/3145oN
Sent from my YD201 using Tapatalk

adamo86 said:
Latest YotaPhone2 Kernel Sources - If you are developing for the YotaPhone 2 the latest kernel sources are now available in the form of a 100Mb download direct from their server. If you have been waiting for them, you can pick them up now! http://ow.ly/3145oN
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Yeah, that is the kernel source alright. I guess there was enough requests for it after all.
Now we just need to make it better. We have the technology.

We need a cyanogenmod rom
Sent from my YD201 using Tapatalk

Great news indeed. About a week ago I've requested XDA's OEM relations manager Jerdog to contact Yota, and today he sent me a message that they finally obliged. His action together with some social media attention and requests through other channels probably all added up.
I've put it on github: https://github.com/SteadyQuad/android_kernel_yotaphone2
There's still a lot of work to do however, it's not plug-and-play. As far as I can see there's no kernel config included, so that might take time to figure out. I'm not an experienced kernel dev, but I'll give it some attention to see how far I get with it. Anyone else interested to help out here?

Wish that I could help, but this is not something were I'm able to add value... :/
Best of luck to you and any other that may go down that road.

what about the progress
now?
Sent from my YD206 using XDA Free mobile app

Does anyone have a mirror for the original tarball?

SteadyQuad said:
Great news indeed. About a week ago I've requested XDA's OEM relations manager Jerdog to contact Yota, and today he sent me a message that they finally obliged. His action together with some social media attention and requests through other channels probably all added up.
I've put it on github: https://github.com/SteadyQuad/android_kernel_yotaphone2
There's still a lot of work to do however, it's not plug-and-play. As far as I can see there's no kernel config included, so that might take time to figure out. I'm not an experienced kernel dev, but I'll give it some attention to see how far I get with it. Anyone else interested to help out here?
Click to expand...
Click to collapse
Config is in arch/arm/configs and seems to already be set up with the EPD display, so likely the same that Yota is using:
https://github.com/SteadyQuad/android_kernel_yotaphone2/tree/lollipop5.0/arch/arm/configs
Do you still have the original tarball?

Amplificator said:
Config is in arch/arm/configs and seems to already be set up with the EPD display, so likely the same that Yota is using:
https://github.com/SteadyQuad/android_kernel_yotaphone2/tree/lollipop5.0/arch/arm/configs
Do you still have the original tarball?
Click to expand...
Click to collapse
Can't find the original tarball. Sources on Github are pretty close though (I think I only missed some firmware files on very first commit). You probably found it already, but Yota seemed to have adapted the standard arch/arm/configs/msm8974_defconfig file for yp2, which contains amongst other things the Epson EPD driver:
Code:
CONFIG_FB_EPSON_S1D13522=y
CONFIG_EPSON_13522=y
It's been some time, but I remember after some small tweaks (on github) the kernel actually built and booted.
I've never managed to get into contact with Yota directly, but if you're planning development work, maybe you should ask them for an updated tarball, might have updated EPD firmware, CVE fixes and other updates .

SteadyQuad said:
Can't find the original tarball. Sources on Github are pretty close though (I think I only missed some firmware files on very first commit). You probably found it already, but Yota seemed to have adapted the standard arch/arm/configs/msm8974_defconfig file for yp2, which contains amongst other things the Epson EPD driver:
Code:
CONFIG_FB_EPSON_S1D13522=y
CONFIG_EPSON_13522=y
It's been some time, but I remember after some small tweaks (on github) the kernel actually built and booted.
I've never managed to get into contact with Yota directly, but if you're planning development work, maybe you should ask them for an updated tarball, might have updated EPD firmware, CVE fixes and other updates .
Click to expand...
Click to collapse
I sent Yota a mail, so let's see if they care to share

Cool, It would be awesome to get some lovin' on this device....

Yota responded:
Unfortunately, nowadays our company does not provide access latest kernel sources for Yotaphone 2.
Click to expand...
Click to collapse
So apparently they don't care :-/

Amplificator said:
Yota responded:
Unfortunately, nowadays our company does not provide access latest kernel sources for Yotaphone 2.
Click to expand...
Click to collapse
So apparently they don't care :-/
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"GPL license terms don't apply to us, and please stop building a loyal community around our devices!" :silly:

SteadyQuad said:
"GPL license terms don't apply to us, and please stop building a loyal community around our devices!" :silly:
Click to expand...
Click to collapse
Exactly.. I sent a follow-up mail with a friendly reminder of the GPL license and some other "plz gib" attempts, but the response felt more like this:

So apparently they don't care :-/
Click to expand...
Click to collapse
Actaully Yota Devices cares about community
And shares the latest kernel:
https://srv-fs1.yotadevices.com/public/file/28nVYCsjTUGwylIFgokCqA/kernel_sep21.zip
(direct link)

andpotugin said:
Actaully Yota Devices cares about community
And shares the latest kernel:
https://srv-fs1.yotadevices.com/public/file/28nVYCsjTUGwylIFgokCqA/kernel_sep21.zip
(direct link)
Click to expand...
Click to collapse
How did you get it? An old KGB buddy or something?
And thanks for the pm

How did you get it? An old KGB buddy or something?
Click to expand...
Click to collapse
No KGB involved, comrade
It seems that YotaDevices is monitoring threads on XDA sometimes.

andpotugin said:
No KGB involved, comrade
Click to expand...
Click to collapse
..if you say so
But thanks for the link.. it's good to know that K... Yota is watching

Amplificator said:
..if you say so
But thanks for the link.. it's good to know that K... Yota is watching
Click to expand...
Click to collapse
You're welcome!
And keep in mind: not Yota (mobile carrier), but Yota Devices (SW team)

So, how hard is it to merge this old pile of sources into a newish CM13 branch? I've compiled a linux kernel before but never did any more involved stuff than that - Anyone with prior experience or a decent written guide on how to adapt CM to a device around?

New Security Update

Today I received a patch including security updates for the Factory Unlocked version, probably the Stagefright fix, but don't you think that's a lot just for a security fix? Google's patches were very small (less than 100MB) compared to that, anyone has additional information about this update?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DeadPotato said:
Today I received a patch including security updates for the Factory Unlocked version, probably the Stagefright fix, but don't you think that's a lot just for a security fix? Google's patches were very small (less than 100MB) compared to that, anyone has additional information about this update?
View attachment 3457832
Click to expand...
Click to collapse
Just checked for the update and my factory unlocked version M9 is currently downloading the file. Does seem like a large file size to simply contain "Android System Security Fixes".

StilsonCanyon said:
Just checked for the update and my factory unlocked version M9 is currently downloading the file. Does seem like a large file size to simply contain "Android System Security Fixes".
Click to expand...
Click to collapse
Agree, fun fact? Or the fix released for OEMs and Google doesn't work at all or the app developed by Zimperium doesn't.
After I finished the update ran the app and guess what?
To be sure I deleted the app cache and data, and then after getting the same result uninstalled the app, restarted phone and installed the app once again, the result was the same.
Since I was curious I installed the app on my Nexus 10, which got the patch from Google and it also says is vulnerable.
Is there another reliable way to check it out?

DeadPotato said:
After I finished the update ran the app and guess what?
View attachment 3458090
Is there another reliable way to check it out?
Click to expand...
Click to collapse
I see the same result - first is vulnerable and the rest are not. Hmm. Don't know what to say or what else the update contained...

Was it all 7 before the patch?
7th exploit came later and wasn't part of Google's original patch.

Electronic Punk said:
Was it all 7 before the patch?
7th exploit came later and wasn't part of Google's original patch.
Click to expand...
Click to collapse
The result was the same before and after the patch. There was a time when there was no patch at all and the Zimperium app detected the phone as not vulnerable, then they found an additional exploit and added it to the list, making the result appear as vulnerable. Then this patch came today, and we're at the same place, with that first one being marked as vulnerable.

DeadPotato said:
The result was the same before and after the patch. There was a time when there was no patch at all and the Zimperium app detected the phone as not vulnerable, then they found an additional exploit and added it to the list, making the result appear as vulnerable. Then this patch came today, and we're at the same place, with that first one being marked as vulnerable.
Click to expand...
Click to collapse
Well, might not even relate to Stagefright, but another security issue patched before public disclosure -- that does still happen sometimes!

Forgot to add details
Electronic Punk said:
Well, might not even relate to Stagefright, but another security issue patched before public disclosure -- that does still happen sometimes!
Click to expand...
Click to collapse
That's the most odd thing about it, it's confirmed to be related to Stagefright fix even by HTC
http://www.htc.com/us/support/htc-one-m9/news/
I contacted the app developers yesterday, but didn't got a reply yet.

What version was the last developer release?

Still no sign of a 2.10/2.11 RUU file? Please, if anyone could organize i'd be so glad..

@Electronic Punk 2.11.617.15

DeadPotato said:
@Electronic Punk 2.11.617.15
Click to expand...
Click to collapse
So no version change then.

Electronic Punk said:
So no version change then.
Click to expand...
Click to collapse
Just in case I wasn't clear, it went from 2.8.617.4 to 2.11.617.15, yes version changed but not major version though

Dev Edition/WWE RUU
medoc.murner said:
Still no sign of a 2.10/2.11 RUU file? Please, if anyone could organize i'd be so glad..
Click to expand...
Click to collapse
RUU has been out since August 26th...
This software upgrade available for your HTC One provides the following key enhancements:
· Stagefright patch
Download here from HTC
RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11.617.15_Radio_01.01_U11440601_76.03.50611G_F_release_445910_signed_2.exe

effortless said:
RUU has been out since August 26th...
This software upgrade available for your HTC One provides the following key enhancements:
· Stagefright patch
Download here from HTC
RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11.617.15_Radio_01.01_U11440601_76.03.50611G_F_release_445910_signed_2.exe
Click to expand...
Click to collapse
I see ATT in that link, but I also see MR, NA, Gen, and Unlock. I have the M9 Developer Edition. Would that be the same? Cause if you go to HTC's support site, the latest M9 Developer Edition RUU is an old one.

wwjoshdew said:
I see ATT in that link, but I also see MR, NA, Gen, and Unlock. I have the M9 Developer Edition. Would that be the same? Cause if you go to HTC's support site, the latest M9 Developer Edition RUU is an old one.
Click to expand...
Click to collapse
Yes, I think that's the same. I've changed my M9 to an developer edition and used the same RUU (for att, na, generic and developer). 2.11.617.15 is latest version.
tapatalked..

wwjoshdew said:
I see ATT in that link, but I also see MR, NA, Gen, and Unlock. I have the M9 Developer Edition. Would that be the same? Cause if you go to HTC's support site, the latest M9 Developer Edition RUU is an old one.
Click to expand...
Click to collapse
k1moe said:
Yes, I think that's the same. I've changed my M9 to an developer edition and used the same RUU (for att, na, generic and developer). 2.11.617.15 is latest version.
tapatalked..
Click to expand...
Click to collapse
The dev edition is the exact same hardware as the AT&T version and it has the name in its link URL... but they don't have the same software released. The World Wide Edition (WWE) and Dev edition share the same software.. the link I posted above is for those.
The AT&T RUU link is: http://dl3.htc.com.s3.amazonaws.com...01_72.02.50602A_F_release_446474_signed_2.exe
Latest for ATT is 2.6.502.18 with stage fright fix.
Also, for those that care, T-Mobile will be releasing their M9 stage fright update mid month.. it will also come with Android for Work.

Change.org -- Project treble for the OP5t -- Sign now!

Hey xda,
It might be a good idea to sign this, we are heading towards 300 signatures in less than 2 hours,
Let's do this!
https://www.change.org/p/carl-pei-w...ium=email&utm_campaign=share_email_responsive
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

With project treble rom development will become easy AF (we hope!). Please sign, it's an important improvement for our phone.

Can Treble feature be added to a phone after the choice is made not to support it right off the bat? I thought the treble setup requires two different partitions that need to be part of the factory original file structure of the phone.
Sent from my Nexus 6 using Tapatalk

Huawei did it with the Mate 9, so it should be possible for OP, too.

jackennils said:
Huawei did it with the Mate 9, so it should be possible for OP, too.
Click to expand...
Click to collapse
Yes but their 8.0 update already supported treble.
Guys I wouldnt be to excited about this. Here are a few reasons.
1. OEM will still be in charge of sending out updates. Which we all know will not change
2. This does 0 for custom rom development at all. Most devs have already stated they will not support it or even bother with it.
3. The petition means less then nothing really.
4. The Mate 9 update is broke and doesnt work nearly as well as they are claiming in the portal post. (If you go to thread you will see that it is still unstable and requires tons of work to make it work right)
5. Even if you did flash an aosp rom with Treble, you would lose all OEM features.

Maybe we don't need an official treble, seems op5 and maybe op5t has the proper hardware to support it non-officially.
Keep an eye here for info:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development

zelendel said:
Yes but their 8.0 update already supported treble.
Guys I wouldnt be to excited about this. Here are a few reasons.
1. OEM will still be in charge of sending out updates. Which we all know will not change
2. This does 0 for custom rom development at all. Most devs have already stated they will not support it or even bother with it.
3. The petition means less then nothing really.
4. The Mate 9 update is broke and doesnt work nearly as well as they are claiming in the portal post. (If you go to thread you will see that it is still unstable and requires tons of work to make it work right)
5. Even if you did flash an aosp rom with Treble, you would lose all OEM features.
Click to expand...
Click to collapse
Could you provide a source for the point 2? Thanks in advance

Why it's not going to happen, petition or not:
OmegaHsu @oneplus.net said:
Project Treble requires a storage partition, by which the Android framework and vendor image are separated. However, because partitions were not required of Android N and previous versions of Android, all of our current devices do not feature a partition. According to our tests, if we were to modify the partition layout via OTA there is a risk that devices will brick during the partitioning. We feel this poses too great a risk for our community of users, which is why we have decided not to implement Project Treble on current OnePlus devices.
Click to expand...
Click to collapse
Source

I'm in, we need 2,058 more people.

x111 said:
I'm in, we need 2,058 more people.
Click to expand...
Click to collapse
Read the post above yours.
Sent from my ONEPLUS A5010 using Tapatalk

i guess we have to close the thread.

Really? Why can't we keep pushing and discussing it? First of all, oneplus could have easily implemented a second partition given that Oreo was already out of for months when the 5t was released. So this is excuse sounds a bit lame to me. Second, why not providing us with the vendor files so that developers can find a partitioning implementation that users use on their own responsibility?

No Treble support was well known before release. Not sure I understand why folks purchased it if they wanted Treble support.

The more thoughtful petition should be....
OnePlus plz give support of our 5T to android Q

RijuSarkar13 said:
The more thoughtful petition should be....
OnePlus plz give support of our 5T to android Q
Click to expand...
Click to collapse
I guess treble support won't be coming with whatever reason they have given about partition.
We should ensure that we get android Q atleast

I'm happy with the nougat build why think so much ahead?

Ranop11 said:
I'm happy with the nougat build why think so much ahead?
Click to expand...
Click to collapse
Because the lastest Android version is 8.1 lol we are three updates behind. While I'm not entirely pressed about Oreo (8.1 is nice I'll admit) OP could've AT LEAST shipped with 7.1.2
Sent from my ONEPLUS A5010 using Tapatalk

frozl said:
Really? Why can't we keep pushing and discussing it? First of all, oneplus could have easily implemented a second partition given that Oreo was already out of for months when the 5t was released. So this is excuse sounds a bit lame to me. Second, why not providing us with the vendor files so that developers can find a partitioning implementation that users use on their own responsibility?
Click to expand...
Click to collapse
Their software pipeline is definitely more than a few months long. I'd bet the Nougat build was already a ways into development before Oreo came out, and at that point starting over would have been silly.

So what? I don't care what software I'm on, if it's stable, battery life good, and there's not much change is android oreo, **** guys you are like bunch of kids, if it works why change?

I think our best bet right now is hoping someone will develop a 5T ROM with hacked in Treble Support so we can then use the upcoming unified Treble Updates. Not much hope we'll see any support from OnePlus and they are getting slower and slower with their Updates...

Oneplus withdraws the OOS 5.0 Oreo Update

Hi All Oneplus has withdrawn the OOS 5.0 Oreo Update. Since lots of community members had complained regarding the issues such as heavy battery drain, Auto fill not working, PIP not working, Random reboot(rarely), etc. Oneplus has withdrawn Oreo update. Even i faces some issues after updating to OOS 5.0, however after a factory reset every seems to be working fine and OOS 5.0 is pretty stable. I had also contacted the oneplus support regarding this concern they confirmed that, It is true and the OOS Devs are working round the clock fix the issues and make the OOS 5.0 more stable release a fresh Oreo update. They also confirmed the as of now there no issues in running OOS 5.0 on your 3(T) if u are not facing any issues.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't forget to smash the thanks button :laugh:

Azaruddin said:
Hi All Oneplus has withdrawn the OOS 5.0 Oreo Update. Since lots of community members had complained regarding the issues such as heavy battery drain, Auto fill not working, PIP not working, Random reboot(rarely), etc. Oneplus has withdrawn Oreo update. Even i faces some issues after updating to OOS 5.0, however after a factory reset every seems to be working fine and OOS 5.0 is pretty stable. I had also contacted the oneplus support regarding this concern they confirmed that, It is true and the OOS Devs are working round the clock fix the issues and make the OOS 5.0 more stable release a fresh Oreo update. They also confirmed the as of now there no issues in running OOS 5.0 on your 3(T) if u are not facing any issues.
View attachment 4352892
Do forget to smash the thanks button :laugh:
Click to expand...
Click to collapse
No.

casual_kikoo said:
No.
Click to expand...
Click to collapse
Its True @casual_kikoo you have to accept this.

Azaruddin said:
Its True @casual_kikoo you have accept this.
Click to expand...
Click to collapse
What ?
I didn't accept anything, I'm just tired of people like you, who are begging for their "Thanks" counter.

I wouldn't trust the support team at OnePlus. They're really lax at their job, and they'll say anything to end the RMA ticket. There have been no such alerts on OnePlus forums, and a withdrawal of an update would be a subject that would be heavily discussed there.
Azaruddin said:
Don't forget to smash the thanks button :laugh:
Click to expand...
Click to collapse
Yes, we'll thank you for a topic that is of no importance to us. (sarcasm)
Update: Flashed OOS 4.5.0, and I stil was able to download the 5.0 update via the built in Update Phone menu. So, no withdrawal has taken place.

casual_kikoo said:
What ?
I didn't accept anything, I'm just tired of people like you, who are begging for their "Thanks" counter.
Click to expand...
Click to collapse
Thanks @casual_kikoo for the polite response.

Azaruddin said:
Thanks @casual_kikoo for the polite response.
Click to expand...
Click to collapse
You're welcome.

thes3usa said:
I wouldn't trust the support team at OnePlus. They're really lax at their job, and they'll say anything to end the RMA ticket. There have been no such alerts on OnePlus forums, and a withdrawal of an update would be a subject that would be heavily discussed there.
Yes, we'll thank you for a topic that is of no importance to us. (sarcasm)
Update: Flashed OOS 4.5.0, and I stil was able to download the 5.0 update via the built in Update Phone menu. So, no withdrawal has taken place.
Click to expand...
Click to collapse
Thanks @thes3usa for your appreciation, this motivated me a lot.

Open Beta 19 is still up at http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_19/
I would suggest that if a company were to "withdraw" a piece of software the first thing they would do would be take it down from their website.
I'm not sure this claim has a great deal of credibility based on the evidence seen so far.

thehappyotter said:
Open Beta 19 is still up at http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_19/
I would suggest that if a company were to "withdraw" a piece of software the first thing they would do would be take it down from their website.
I'm not sure this claim has a great deal of credibility based on the evidence seen so far.
Click to expand...
Click to collapse
He clearly mentioned the Stable version, not the Open Beta version in OP

thes3usa said:
He clearly mentioned the Stable version, not the Open Beta version in OP
Click to expand...
Click to collapse
Ahh yes. So he did.
Here's the link to that. http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_5.0/

thehappyotter said:
Open Beta 19 is still up at http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_19/
I would suggest that if a company were to "withdraw" a piece of software the first thing they would do would be take it down from their website.
I'm not sure this claim has a great deal of credibility based on the evidence seen so far.
Click to expand...
Click to collapse
@thehappyotter before replying please open your eyes and read the post clearly

Oxygen os 5.0 for 3t it's still available for download!

Azaruddin said:
@thehappyotter before replying please open your eyes and read the post clearly
Click to expand...
Click to collapse
I best get "smashing the thanks button" then :laugh:

thehappyotter said:
I best get "smashing the thanks button" then :laugh:
Click to expand...
Click to collapse

Oreo Soak test released for Moto Z Play

Oreo Soak test arrived for Moto Z Play! HHmmmmm http://droidvendor.com/oreo-soak-test-build-opn27-67-released-for-moto-z-play/

Yeay, we'll get O in about a month...

Alee_Khan said:
Oreo Soak test arrived for Moto Z Play! HHmmmmm http://droidvendor.com/oreo-soak-test-build-opn27-67-released-for-moto-z-play/:D
Click to expand...
Click to collapse
Members are advised that the link provided is not secure (http vs. https) and may flag as such in your browser. Take care...

LenAsh said:
Members are advised that the link provided is not secure (http vs. https) and may flag as such in your browser. Take care...
Click to expand...
Click to collapse
I have updated it now

Alee_Khan said:
I have updated it now
Click to expand...
Click to collapse
Thanks, but it's still not secure. Not https.... browsers are blocking several elements too.

has anyone from here got it?

agree http without th s is dodgy

Also , as with any soak test, be aware that Motorola may release several builds to soak testers. Thus, missing one of those builds may mean you're ineligible to update via OTA unless you get hold of that missing patch or wait for the full fastboot Oreo stock ROM. Motorola will likely only assist if you're formally enrolled in the Feedback testing program and actually selected for the test.
Furthermore, I don't know if this build of Oreo has rollback protection, but it could be very risky to downgrade back to stock Nougat if you decide to flash this soak test (since it'll likely updated your bootloader). Taking an OTA might hard brick your device after the downgrade. If you've updated to Oreo too, the blankflash here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492 may fail to rescue your device unless we can get a Oreo blankflash leaked.
Of course, could always wait for the actual Oreo OTA update... Have fun, but be careful.

Good point echo92 and that's why I've polite refused when someone asked​ to leak test build.
Btw, don't expect much from Oreo.
Sent from my XT1635-02 using Tapatalk

Zeljko1234 said:
Btw, don't expect much from Oreo.
Click to expand...
Click to collapse
I'm awaiting Oreo since a long time, hoping for 2 big changes, both in filesystem:
1. Fix F2FS in kernel regarding loopback device, so that Magisk runs without hassle
2. Set timestamp is now always possible (because SDCardFS instead of FUSE), so that copy and move work fine without root
Part 2 was already confirmed by some Oreo user. It would be difficult for Motorola to do something so that this does not work.

I've asked already, how to check f2fs on stock/locked bl device?
Sent from my XT1635-02 using Tapatalk

Zeljko1234 said:
I've asked already, how to check f2fs on stock/locked bl device?
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
Unless Motorola releases the source code I don't think it's possible. You just know there is a bug when you see that it won't mount an image as loopback device

good clickbait xD

Artim_96 said:
Unless Motorola releases the source code I don't think it's possible. You just know there is a bug when you see that it won't mount an image as loopback device
Click to expand...
Click to collapse
I think Motorola is already using F2FS for this device. That's why it's running so well.
I swear I saw this somewhere.

TigerCourage said:
I think Motorola is already using F2FS for this device. That's why it's running so well.
I swear I saw this somewhere.
Click to expand...
Click to collapse
Of course they do since the beginning for /data. But I think the question was because of the bugs in their f2fs implementation. The worst bug is already fixed but was replaced by another bug. Both make it hard to use Magisk

Zeljko1234 said:
Good point echo92 and that's why I've polite refused when someone asked​ to leak test build.
Btw, don't expect much from Oreo.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
To correct my statement a bit. Oreo works pretty well, subjectively faster/smoother than Nougat, battery life is better or the same as before. I really like new audio codecs, sound is (again personally) much better
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Zeljko1234 said:
To correct my statement a bit. Oreo works pretty well, subjectively faster/smoother than Nougat, battery life is better or the same as before. I really like new audio codecs, sound is (again personally) much better
Click to expand...
Click to collapse
This is the feature that i'm more 'hyped'

W3ND31 said:
This is the feature that i'm more 'hyped'
Click to expand...
Click to collapse
Do you mean audio codecs? Then you are going to love this.
And yes, sound is definitely better.
Sent from my XT1635-02 using Tapatalk

Zeljko1234 said:
Do you mean audio codecs? Then you are going to love this.
And yes, sound is definitely better.
Click to expand...
Click to collapse
Pff cant wait until we get this official, or someone who leaks it ?

Zeljko1234 said:
To correct my statement a bit. Oreo works pretty well, subjectively faster/smoother than Nougat, battery life is better or the same as before. I really like new audio codecs, sound is (again personally) much better
Click to expand...
Click to collapse
You have 8.0?