OnePlus released the source code of OOS on github. Some nice news.
https://github.com/OnePlusOSS
Hmm, interesting news, thank for info :good:
This is badass!
Great news indeed.
Let's wait for an OPX device tree and vendor blobs
The github page has a 6.0.1 branch only.
Does this mean that this is a build for the oneplus 2 only?
Or does this also mean that devs can now build a 6.0.1 based oxygen os 3 rom for oneplus x as well using this before oneplus themselves do it??
Had a closer look... It just looks like it'll build AOSP... Not O2...
Ivtake the previous post back. This is awesome! We just need to get a device tree working and we can produce an unofficial port!
Now the path clears to custom oxygenOs:highfive:
Also it may mean timely access to sources, if we ever get mm
Unfortunately , I was right earlier... It is not open source O2
@crian RJDTWO is right. Confirmed by Helen yesterday. Can you change the title, please.
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
msfrox said:
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
Click to expand...
Click to collapse
Try MOKEE rom (History)...
https://download.mokeedev.com/?device=wt88047
What's the difference between history and release
msfrox said:
What's the difference between history and release
Click to expand...
Click to collapse
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
Nice thanks
History means stablest
Source: https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Got nearly 2 years of updates, but not quite.
On a related note, official XZ1 Compact website is up. I'm thinking about getting one for my wife to replace her Z5C, UFS sounds delicious.
The list of devices in the blog is not final and it is possible that we will see Oreo on our device.
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
cyberwytch said:
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
Click to expand...
Click to collapse
From memory, as long as the source is configured right it should be fine (Wifi drivers shouldn't be changing as its still the same hardware, same for screen and all) - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
nzzane said:
From memory, as long as the source is configured right it should be fine - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
Click to expand...
Click to collapse
Awesome sauce! I love your Lineage 14, can't wait to see what's next!
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
That's awesome news, I'll add "official" to the thread title for clarification.
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
I'm currently doing something similar for my laptop running Server 2016, and am slowly making it run like a Desktop OS, by enabling all the other stuff left out that I can find
---------- Post added at 16:25 ---------- Previous post was at 16:21 ----------
nzzane said:
...
Click to expand...
Click to collapse
which linux kernel is LOS running?
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18,
Click to expand...
Click to collapse
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
NeoBeum said:
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
Click to expand...
Click to collapse
Hmm, 'k; thanks. I'll do some more digging. But if true this would flatly contradict Google's own public statements (though I realize it's not like this would be a first for that kind of thing).
-- Nathan
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
Click to expand...
Click to collapse
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
NeoBeum said:
which linux kernel is LOS running?
Click to expand...
Click to collapse
3.10, CAF kernel
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
correct,
actually 4.4 kernel, it's only needed for newer SoCs
so we can go on with 3.10 kernel for now but we need to wait for (potential) CAF changes
GreyLeshy said:
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
Click to expand...
Click to collapse
well, there's still Linux mainline / vanilla upstream support for msm8994 since 4.10 kernel in a very rough state with terminal only (AOSP)
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
yeah I basically read it as qualcomm have bad after market support
zacharias.maladroit said:
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
Click to expand...
Click to collapse
I might have something interesting to build then and I can stop lounging around
any news for official aosp 8.0 release for z5?
Enviado desde mi SGP712 mediante Tapatalk
Hello community! I hope you are well, today I bring you the Kernel Stock of Motorola, prerooted and with some minimal improvements and optimizations (I will gradually optimize it even more).
The only requirements are to have the bootloader unlocked and debug usb enabled (I have not yet tested on any device with the bootloader closed, if anyone wants to try you can send me a PM).
I hope you like it, greetings and good luck!
XDA:DevDB Information
Stock Oreo Kernel 8.1.0, Kernel for the Moto G5S Plus
Contributors
EmiAndroid, None, None
Kernel Special Features: Minimal Optimizations
Version Information
Status: Testing
Stable Release Date: 2018-11-05
Created 2018-11-05
Last Updated 2018-11-05
EmiAndroid said:
Hello community! I hope you are well, today I bring you the Kernel Stock of Motorola, prerooted and with some minimal improvements and optimizations (I will gradually optimize it even more).
The only requirements are to have the bootloader unlocked and debug usb enabled (I have not yet tested on any device with the bootloader closed, if anyone wants to try you can send me a PM).
I hope you like it, greetings and good luck!
XDA:DevDB Information
Stock Oreo Kernel 8.1.0, Kernel for the Moto G5S Plus
Contributors
EmiAndroid, None, None
Kernel Special Features: Minimal Optimizations
Version Information
Status: Testing
Stable Release Date: 2018-11-05
Created 2018-11-05
Last Updated 2018-11-05
Click to expand...
Click to collapse
where is it?
davekaz said:
where is it?
Click to expand...
Click to collapse
Hello! I have asked you to delete this post, they have been published 3 times, here!
https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301
kernel stock oreo ?
Does It work fine on Pie ROMs? (Some Oreo kernels work on Pie ROMs too)
Installed this and lost WIFI completely. Nothing I did would bring it back. So I restored the regular stock kernel and rooted it the old reliable way with Magisk 19.3.
Hello everyone，I am using PiexlExperience rom now. And I also see there is a caf version rom supply.
So I want to know what is caf version? Does it better than normal version? And what should I do if I want to flash the CAF rom? Do I need to clear all my user data?
Thanks, I am really looking forward to hear something from you guys.
CAF stand for Code Aurora Forum, which is the forum that Qualcomm released their source code. Since it contains source code directly from Qualcomm, rom built with it usually more stable and more optimized.
About the rom flash, sadly I don't know anything, as I don't want to use Pie at all.
Never_Sm1le said:
CAF stand for Code Aurora Forum, which is the forum that Qualcomm released their source code. Since it contains source code directly from Qualcomm, rom built with it usually more stable and more optimized.
About the rom flash, sadly I don't know anything, as I don't want to use Pie at all.
Click to expand...
Click to collapse
Why you don't want to use pie, bro?
alexmason90 said:
Why you don't want to use pie, bro?
Click to expand...
Click to collapse
It's uglier than Oreo and a few small but annoying things like the expand volume button is gone, Gcam autofocus (don't know if it also happen on custom rom). Besides the new features in Pie like Adaptive Brightness is useless to me, as I never turn on Auto Brightness, and few people said that Pie has notification problem.
Never_Sm1le said:
CAF stand for Code Aurora Forum, which is the forum that Qualcomm released their source code. Since it contains source code directly from Qualcomm, rom built with it usually more stable and more optimized.
About the rom flash, sadly I don't know anything, as I don't want to use Pie at all.
Click to expand...
Click to collapse
Thank you for the reply. I think I can try the CAF version.
Try revanges rom
It's caf and awasome