How is Lenovo's performance regarding releasing official bootloader unlock method and kernel sources??
Related
Hi community,
just asked myself if the developers can build a nougat s7 edge rom based on the just released source code
or do they have to wait until samsung releases a s7e touchwiz nougat rom and then develop a custom rom, based on samsung's nougat rom?
It just came to my mind when i saw the information, that the source code of nougut was published.
Thank you very much, guys.
// Edit: @ xda: Please change to Standard Thread. Sorry for this circumstances.
We have to wait for Nougat based release from Samsung for S7/S7E/Note7.
Hello,
As I know Qualcomm has not made corresponding graphics drivers for the new Vulkan API for Snapdragon 800 and 801. So S5 can't have Android 7.x Nougat. If it is true how it is possible that we have CM/Lineageos 14.x for S5? Did developers write their own graphics drivers? What about performance comparing to official 6.0.1 Marshmallow?
best regards,
da1k
da1k said:
Hello,
As I know Qualcomm has not made corresponding graphics drivers for the new Vulkan API for Snapdragon 800 and 801. So S5 can't have Android 7.x Nougat. If it is true how it is possible that we have CM/Lineageos 14.x for S5? Did developers write their own graphics drivers? What about performance comparing to official 6.0.1 Marshmallow?
best regards,
da1k
Click to expand...
Click to collapse
We don't need to use the Vulkan API to run CM14.X/LineageOS, therefore there is no need to write new drivers Vulkan is only required when a manufacturer wants to ship android nougat to their device officially. Performance wise, official 6.0.1 marshmallow will always be the best when compared to AOSP because Samsung has some closed-source drivers that can only be used on official stock ROM.
Saber
Saber said:
We don't need to use the Vulkan API to run CM14.X/LineageOS, therefore there is no need to write new drivers Vulkan is only required when a manufacturer wants to ship android nougat to their device officially. Performance wise, official 6.0.1 marshmallow will always be the best when compared to AOSP because Samsung has some closed-source drivers that can only be used on official stock ROM.
Saber
Click to expand...
Click to collapse
Blood is worth bottling... Thank you very much
Any hope that we will get officiall support for custom roms like LoS,RR or Mokee. Also i read that Xiaomi needs to update kernel source but Redmi 3(ido) that runs lollipop has stable nougat official custom roms with only lollipop source from Xiaomi.
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
lat94084 said:
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
Click to expand...
Click to collapse
1) We just got Oreo on Quark. I think you should learn to use that first.
2) That Quark Oreo thread you referenced was started in August 2017. When did Quark get Oreo? July 2018.
It's now August 2018, and you are asking for Pie. So, look for Quark Pie in July 2019.
3) Also, like before only @bhb27 can code the necessary kernel for any Quark Pie. It's not who "wants" it, it's WHO can actually do it. Maybe @bhb27 wants to just work on his new Oreo kernel and ROM for awhile. Maybe he wants a different phone...
4) If you read the other thread you say this is based on, discussing it didn't really help bring Oreo any faster to Quark. It still all depended on @bhb27 actually doing the work, and doing it right. See point #2.
_______
Just so I don't have to type everything over from the first thread, read this. In your mind just substitute "Pie" every time "Oreo" is mentioned, and substitute "Oreo" when "Nougat" is mentioned. SAME EXACT SITUATION A YEAR AGO:
AUGUST 24, 2017
jeffkahlo777 said:
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Click to expand...
Click to collapse
ChazzMatt said:
It will take @bhb27 coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@bhb27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @bhb27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @bhb27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @bhb27 did the work to let Nougat ROMs use that kernel.
Will be the same thing with Oreo. But @bhb27 still has to code it to work smoothly with Oreo.
Also, there is no more CM. We now have LOS as the "base". @bhb27 does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @bhb27 will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)
@bhb27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.
The kernel will be the foundation of any Oreo ROMs and it will all depend on @bhb27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @bhb27 is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.
Click to expand...
Click to collapse
lat94084 said:
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
Click to expand...
Click to collapse
Hope @bhb27 works on Android 9 pie as well.
once more Thanks @bhb27 your knowledge and Hard work never cease to amaze me :good::victory::victory:
I think it best to focus on android Oreo.
Hi. in the official site sony check this the most recently information for our device
https://developer.sony.com/develop/open-devices/latest-updates
specially:
Software binaries for AOSP Android 10.0 – Kernel 4.14 – Tone (latest)
Software binaries for Xperia™ XZ, Xperia XZs and Xperia X Performance. To be used with the Android™ Open Source Project (AOSP) for Xperia devices.
maybe somebody have any information for respect.
¿Android 10 in our device? ¿is possible?
Android 10 is out you can download it from the pie thread. But it is in very early stage so you have to take that in mind.
Bugs are similar with the pie builds btw.
I've tried to build AOSP for the F8331. In my opinion, when Kernel 4.14 is offered by Sony, it should be possible to build AOSP.
But when I start envsetup.sh a device list appears - but without F8331.
Anyone here who has already found a solution?
oguzbatu said:
Android 10 is out you can download it from the pie thread. But it is in very early stage so you have to take that in mind.
Bugs are similar with the pie builds btw.
Click to expand...
Click to collapse
How could I flash it on my phone?
I already have bootloader unlocked, twrp, magisk
XZs Dual SIM