Related
Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
ArmanUV said:
Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
Click to expand...
Click to collapse
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
ragnarokx said:
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
CakraMas said:
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
Click to expand...
Click to collapse
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
ArmanUV said:
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
Click to expand...
Click to collapse
Because those sources are actually not released until google starts the ota update. They develop behind closed doors then release all new code at once with the ota. Some people dont like this but i dont think it matters prrsonally.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
5. Github has a diff function that can compare any two files and even merge the code together. So the devs likely use diff to check all new code and merge.
4. You can look thru all the commits to actually see the newest code changes to see whats important etc.
bk201doesntexist said:
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
Click to expand...
Click to collapse
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
ArmanUV said:
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
Click to expand...
Click to collapse
gerrit commits to the master branch are most of time submitted by people working outside of google.
yes, compiling from the master branch of aosp is slightly diferent than from compiling through release tags (4.0.3_r1, 4.0.4_r1.1).
tagged releases are the same as an OTA, except it doesn't have radio/bootloader images, since they're binaries. they don't change, ever. now the builds compiled from aosp master branch do change, even if it is only under the hood changes.
So... CyanogenMod is dead. LineageOS is taking it's place. The ROM is basically CyanogenMod but with changes to the name.
This is completely 'stock' from their source code, so this will encrypt your tablet, and will be prerooted (under Developer options in Settings)
Changelog is available at LineageOS Gerrit
There are no apparent bugs, but any bug reports will be welcome.
Gapps are available at opengapps.org.
Installation
Flash the latest 7.1.1 vendor image in fastboot (fastboot flash vendor vendor.img)
Download latest release from here
Install it in TWRP recovery
Install the downloaded opengapps package
XDA:DevDB Information
Unofficial CyanogenMod/LineageOS 14.1 for Nexus 9, ROM for the Nexus 9
Contributors
hazzer
Source Code: https://github.com/LineageOS/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 7.1.1 (NMF26F) vendor, latest bootloader
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2016-12-04
Last Updated 2016-12-29
Not quite the first CM14.1 for the Nexus 9, but appreciated you taking the time and effort to compile it in any case.
lmulli said:
Not quite the first CM14.1 for the Nexus 9, but appreciated you taking the time and effort to compile it in any case.
Click to expand...
Click to collapse
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
Check hashbang's cm14.1 builds on Android file host.
Can you please post the 7.1.1 vendor image?
Sent from my Nexus 9 using Tapatalk
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
Just go on Androidfilehost and type in flounder
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=profile&uid=95897840722645866
Right hand side.
@hazzer Root is broken on latest 12/05 build. It disappeared from the developer settings. It was functioning in 12/04 build.
tibere86 said:
@hazzer Root is broken on latest 12/05 build. It disappeared from the developer settings. It was functioning in 12/04 build.
Click to expand...
Click to collapse
Hi,
Sorry there was no note attached to the build about this. I purposely removed this so that I could pass safety net by default on the ROM.
If you would like root instead of Android Pay, you can try either SuperSU or Magisk with phh's superuser. If you use Magisk hide, you should be able to get root while passing safety net.
Again, sorry about not noting this, I'll make sure I do later today.
Hi,
If you take a look at the download page, I've now added the reason root was and still will be removed. I've also posted a link to the vendor image and latest bootloader. I would recommend downloading the bootloader from Google themselves if possible. The newest source code for the Nexus 9 device tree has been merged into my GitHub however hasn't made it's way into the latest build (20161205). It will be in 06's build.
Sorry about the poor communication regarding root and the likes
hazzer said:
Hi,
If you take a look at the download page, I've now added the reason root was and still will be removed. I've also posted a link to the vendor image and latest bootloader. I would recommend downloading the bootloader from Google themselves if possible. The newest source code for the Nexus 9 device tree has been merged into my GitHub however hasn't made it's way into the latest build (20161205). It will be in 06's build.
Sorry about the poor communication regarding root and the likes
Click to expand...
Click to collapse
Thanks for the info. Just wanted to let you know :good:
Rom is working great!! But i have one problem: I don't have a mobile signal. It just says "no carrier" (in german "Kein Dienst") and i can't set up mobile settings. What to do?
McFlypants said:
Rom is working great!! But i have one problem: I don't have a mobile signal. It just says "no carrier" (in german "Kein Dienst") and i can't set up mobile settings. What to do?
Click to expand...
Click to collapse
That's probably because this is built for the non-LTE version of the Nexus 9. I'm gonna try and add flounder_lte to my build system tonight. I'll post a build sometime tonight or tomorrow if that's okay?
hazzer said:
That's probably because this is built for the non-LTE version of the Nexus 9. I'm gonna try and add flounder_lte to my build system tonight. I'll post a build sometime tonight or tomorrow if that's okay?
Click to expand...
Click to collapse
Yeah, great!! I'll flash it immediately when it's online. Going to try the stock rom now to prove that it's your rom and not the device. We'll stay in contact
McFlypants said:
Yeah, great!! I'll flash it immediately when it's online. Going to try the stock rom now to prove that it's your rom and not the device. We'll stay in contact
Click to expand...
Click to collapse
Hi,
I'm a little late actually successfully getting an LTE version built, as the device tree hasn't been updated for CM14.1 yet. I'll make sure to mention you here when I've got one ready. Sorry for taking so long
Harry
hazzer said:
Hi,
I'm a little late actually successfully getting an LTE version built, as the device tree hasn't been updated for CM14.1 yet. I'll make sure to mention you here when I've got one ready. Sorry for taking so long
Harry
Click to expand...
Click to collapse
No problem, i am aware that it's your freetime you are spending here.
Btw LTE works on CM13 and stock rom, so it's definately not the device. I'm looking forward for your build but i don't need LTE on my nexus 9 the next 4 days. So don't stress yourself :good:
McFlypants said:
No problem, i am aware that it's your freetime you are spending here.
Btw LTE works on CM13 and stock rom, so it's definately not the device. I'm looking forward for your build but i don't need LTE on my nexus 9 the next 4 days. So don't stress yourself :good:
Click to expand...
Click to collapse
I've actually managed to get one built, if you want to take a look. It's below the flounder section. I don't have an LTE Nexus 9 to test, so you'll to let me know how it goes
hazzer said:
I've actually managed to get one built, if you want to take a look. It's below the flounder section. I don't have an LTE Nexus 9 to test, so you'll to let me know how it goes
Click to expand...
Click to collapse
It's fine! Runs smooth like the non-LTE-version but LTE works! Nice
I tried your builds for 13th and 14th of December (WITH LTE) and they all don't get a LTE signal. Also no sim-toolkit installed and no APN-Settings.
I stay with your first LTE-Build, it's fine!
@hazzer: Thanks for your work on the Nexus 9. Any plans to support the official flounder builds?
Stock Pixel 2 XL/Pixel 2 Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.112
Suitable for build(s): All August 2019 builds
Suitable for devices(s): Pixel 2 XL (taimen) | Pixel 2 (walleye)
I compiled the stock kernel for the Pixel 2 XL/Pixel 2 and applied the SafetyNet patch by sultanxda. The kernel name says wahoo, which is the unified kernel that works on both taimen (Pixel 2 XL) and walleye (Pixel 2) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post (check the Downloads tab). Older versions can be found HERE.
XDA:DevDB Information
Stock Kernel + SafetyNet Patch, Kernel for the Google Pixel 2
Contributors
iissmart
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-18
Last Updated 2017-12-11
I want to apply this patch to my Huawei P9, but obviously can't use this one kernel. How would I go about applying the patch to my kernel? What programs / apps are needed?
Updated OP with the 8.1.0 kernel for December 2017 builds.
Hey anyone else having issues with windows defender seeing this as a virus when trying to download?
iissmart said:
Updated OP with the 8.1.0 kernel for December 2017 builds.
Click to expand...
Click to collapse
Works like a champ! Thanks so much!
Updated OP with the latest kernel for January 2018 builds.
Jan Security Patch
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
rweddy1 said:
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
Click to expand...
Click to collapse
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.
iissmart said:
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.
Click to expand...
Click to collapse
I didn't even think about that, thank you very much! I am all good now.
Can the kernel zip be flashed directly from twrp on the phone rather than extracting and using fastboot?
I've updated OP with the mid-month update to r0.18.
Anyone know if ViperAudio works with this ROM?
xD3CrypTionz said:
Anyone know if ViperAudio works with this ROM?
Click to expand...
Click to collapse
It's a kernel. Try viper and let us all know.
----REDACTED----
xD3CrypTionz said:
Did not try stock kernel but I have elementalx kernel with the Viper4Android Magisk module v2.9.
Click to expand...
Click to collapse
I haven't tried no. I'm happy with the sound on my phone.
Updated OP for February 2018.
Updated OP for March 2018.
Anyone else seeing issues with fast charging with Patched Kernel?
I have a run a few test & looks like patched kernel is not charging as fast as sock.
See below:
Patched Kernel: Battery at 82% when plugged in
After 10 min @ 86% After 20 min @ 89%
Stock Kernel: Battery at 82% when plugged in
After 10 min @ 90% After 20 min @96%
Again testing was done with same charger, same apps running, etc.
Updated OP for April 2018. I believe there is a confirmed issue with fast charging in the previous kernels - please test with this one and let me know if it still exists.
Updated OP for May 2018.
It's finally released. Now we can expect improvements to all the custom ROMs :fingers-crossed:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPS28.85-13
Nice! Can't wait for the awesome devs to make stable custom Oreo and Pie ROMS. Been stuck with stock 8.1 but want to try other ROMs without messing up.
devvshukla said:
Are source code also contains Fastboot Images of stock ROM or they released it saparaty or someone has to build those images from stock. I'm having some problems related to Network there waiting for Fastboot images which can be flashed in locked device.
Sorry if its a stupid question, I'm not a developer.
Click to expand...
Click to collapse
It is only the kernel source code, required by GPL licensing. Nothing about it is flashable.
devvshukla said:
Ok. Regarding to Fastboot stock will Moto release it or we have to wait until some guy related to Moto leak it online?
Usually how much time we have to wait after the official OTA rollout.
Click to expand...
Click to collapse
Moto (Lenovo) does not release it, the only way we get it is leaks from Moto employees or authorized service center employees.
The GPL licensing days they must release the code with 30 or 90 (?) days after the public release... Basically they are just trying to keep within the GPL licensing terms & conditions. This happens after the software is "released".
devvshukla said:
Are source code also contains Fastboot Images of stock ROM or they released it saparaty or someone has to build those images from stock. I'm having some problems related to Network there waiting for Fastboot images which can be flashed in locked device.
Sorry if its a stupid question, I'm not a developer.
Click to expand...
Click to collapse
To answer you question, you can get fastboot stock roms from here. https://firmware.center/firmware/
It's too early to ask for 8.1 fastboot ROM
If and when they release it, would that be helpful for custom roms? Could u also shed some more light as to what exactly will b improved with full source code release? Many roms are alrdy stable.
rjherms said:
To answer you question, you can get fastboot stock roms from here. https://firmware.center/firmware/
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/ This has more specific versions.
devvshukla said:
Are source code also contains Fastboot Images of stock ROM
Click to expand...
Click to collapse
Here is the fastboot package https://forum.xda-developers.com/g5...stboot-flash-stock-oreo-t3848433/post77752702
For those familiar with Velocity Rom this is the kernel I build for it. Velocity hasnt been on XDA as a rule so Im sure not many are familiar. Velocity is my personal Rom Ive been building for years and have shared with all that are interested. This isnt and will never be an "official development project" but will always exist as long as I continue to develop Android roms.
Velocity is focussed on speed, stability, and efficiency and not on adding every imaginable feature. As this is my personal Rom it will have everything I deem useful to me and/or that doesnt compromise the goals of the project.
I dont add every conceivable governor, I/O scheduler, or other user tweakable options. In fact, I typically remove all the options and keep the best. This is designed as a plug and play kernel, not something to be changed. Its also not designed for other Roms.
Please do not ask for features, ETA's, or related. Again, this is my personal kernel for my personal Rom and will be shared accordingly. That said, I do encourage healthy, friendly dialog in my threads.
Flashing instructions
1) Reboot to bootloader
2) Fastboot boot 'bootimage_name'.img to make sure it boots with no issues
3) Reboot to bootloader again
4) Fastboot flash boot 'bootimage_name'.img
5) Buckle up for safety - optional of course
Changelog
Download
Source
This is basically a crosspost from the 3a XL forum. I only own the 3a XL but Im told this works fine on the 3a as well. There are both patched and unpatched boot.img's available depending on whether you want root or not. There is a lot more info over in the 3a XL thread if you have any questions.
New build up....see changelog. This was built from November security patch source and I havent tried it on the October build so ymmv if flashing on a build prior to November security.
New build up. See changelog for details. Also Sargo will now be getting its own builds vs sharing a Bonito one. Download links have changed in the OP.
ctfrommn said:
New build up. See changelog for details. Also Sargo will now be getting its own builds vs sharing a Bonito one. Download links have changed in the OP.
Click to expand...
Click to collapse
Are there some changes except for the name? I didn't realise and flashed the bonito build, but it works fine on sargo.
I_am_Groot! said:
Are there some changes except for the name? I didn't realise and flashed the bonito build, but it works fine on sargo.
Click to expand...
Click to collapse
No, the boot images are now built using the respective devices but for all intents and purposes its the same build. This change was mostly for allowing me to better keep track of downloads. Its possible there are minor differences based on device too but as they both work interchangeably I doubt its anything big, if at all.
New build up.....see changelog.
Anyone interested in (or willing to) flash and test kernels prior to releases please PM me. I can always use people to help especially as I start looking at more experimental changes/optimizations.
New build up. Substantial changes on this one.
ctfrommn said:
New build up. Substantial changes on this one.
Click to expand...
Click to collapse
Can this kernel can be flash with kernel tools?
caballon said:
Can this kernel can be flash with kernel tools?
Click to expand...
Click to collapse
Flashed it many times without problems in flar's EX kernel manager.
j-a-d-z said:
Flashed it many times without problems in flar's EX kernel manager.
Click to expand...
Click to collapse
What's the difference between the two kernels ?
cellatom said:
What's the difference between the two kernels ?
Click to expand...
Click to collapse
Don't know what the inside differences are, because I'm not a developer, but mvk seems faster for me and more battery friendly at the same time. So I use this kernel for now.
cellatom said:
What's the difference between the two kernels ?
Click to expand...
Click to collapse
I wont speak for Flar as I dont know him but from a code standpoint these are 2 very different kernels. My goals (as stated in the OP) are maximum performance without sacrificing efficiency and stability. I delve deep into the experimental and push things to their limits. So while both share the same (or similar) base the additions are very different.
Hi ctfrommn,
I'm seeing this error when trying to boot from the img. Tried 10.16-10.18 magisk and unpatched, sargo and bonito.
fastboot boot MVK_Sargo_v10.18_magisk_patched.img
Sending 'boot.img' (26872 KB) OKAY [ 0.723s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
Click to expand...
Click to collapse
When I flash the img and reboot the 3a goes to fastboot mode and shows "Enter reason: error boot prepare"
Any idea why?
h4m74ro said:
Hi ctfrommn,
I'm seeing this error when trying to boot from the img. Tried 10.16-10.18 magisk and unpatched, sargo and bonito.
When I flash the img and reboot the 3a goes to fastboot mode and shows "Enter reason: error boot prepare"
Any idea why?
Click to expand...
Click to collapse
If your on December update then Yea it won't boot
New build up. See changelog.......This works on both November and December builds.
ctfrommn said:
New build up. See changelog.......This works on both November and December builds.
Click to expand...
Click to collapse
Keep it coming
Anyone willing to give a comparison of this vs. other custom kernels that they've used?
Sent from my Pixel 3a using Tapatalk
New build time. I just spent the last month rebasing and rebuilding this. Everything was rethought, tested, and only kept if it objectively and subjectively improved either performance or efficiency. This is up to date with the latest AOSP and Linux kernel sources. This is built off January security but "should" work on older builds as well.
See changelog for changes and enjoy.