yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Alxoom33:
Unicorn blood? Cool, is that a Harry Potter reference?
[Pixel C Android Development] followmsi:
CONFIG_LOCALVERSION="-unicornblood-dragon-n"

This way you see who did the most work ;)
[Pixel C Android Development] NYCHitman1:
Nope. I've never read or seen any of the Harry Potter books/movies. It's just what we call all of our kernels in DU -- "unicornblood"
[Pixel C Android Development] followmsi:
Made a new kernel .. to combine all the existing sources into one kernel. :)

I have merged all kernels together now ..

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-staging

Update.ZIP_dragon_tegra-3.18_KERNEL_v170427_unicorn-xceed-followmsi.zip

We have a new LOCALVERSION as well :)

CONFIG_LOCALVERSION="-unicorn-xceed-followmsi-dragon-n"

Compiled on linaro 6.3.1 this time .. but makes no difference.

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU !

- Due to the universal installer this kernel works on STOCK, AOSP and LineageOS !

- PureNexus needs to be tested.

Just installed it on Ressurection Remix .. working fine.

Enjoy :)
[Pixel C Android Development] Alxoom33:
Awsome! What version of Xceed did you use? I think [MENTION=4867279]cheep5k8[/MENTION] is up to 9.40. Is this kernel different from the latest Xceed kernel that you and [MENTION=4867279]cheep5k8[/MENTION] collaborated?
[Pixel C Android Development] cheep5k8:
Hey guys,

Just wanted to say: I'm not against these experiments in any way personally! Buuut. One word of caution:

I think if you combine multiple kernels it's possible that specific changes made in one kernel might potentially "break" something in another kernel, i.e. it doesn't work any more the same way.

All I'm saying is: go ahead with kernel merging if I have anything to say in that, but please do not complain to me about this kernel if you e.g. don't get the great Deep Sleep on your tablet as on xceed. ;)
[Pixel C Android Development] followmsi:
9.38 .. last version on github.

This kernels merges DU and xceed together.

Testing it since yesterday .. works fine so far.

Will test a bit ..
[Pixel C Android Development] followmsi:
Yes.. you break one change with the other change ;)

For now it's looking good.

Battery life seems to have improved ... still checking.

WiFi looks different for me .. also still testing.

But you have started with "your" driver first ..I will be waiting.

Maybe we can compile without uncommenting the flag below .. at some point. ;)

# CONFIG_ERROR_ON_WARNING=y

Looking forward ..

Thanks
[Pixel C Android Development] cheep5k8:
Ok guys, I just wanted to say that I kinda appreciate the builds and forking, but also I've put in some substantial knowledge and work into the recent changes which result in this incredible battery life, and I would like to ask to keep credits to me intact where applicable. I don't wanna be a princess or drama queen, it's just that I think that this kernel is really on another level from previous Dragon kernels, and that's what intended and worked for. I understand that it's open source and everyone can do what they want with the code, but we also need to respect each other's time and insights and work on a different channel than git.

Not saying this is already happening full-on but I'm getting wary when the first, and only thing someone asks me when I returned and published 9.00 is "are you going to publish the source".

Thanks.
[Pixel C Android Development] NYCHitman1:
I asked you if you were going to publish the source due to your WiFi driver changes, which I was curious to experiment with. Personally, I have no WiFi issues so it was more out of curiosity.

Side note: I'm not just some random person lol.
[Pixel C Android Development] cheep5k8:
Not truly random, no ;) and I understand that if xceed has some features that people want and another kernel has others, that some would want a kernel that has all of these features combined. But I'm saying that the recent changes I've made which lead to the fantastic battery life were brought by my own skills and knowledge and a lot of time spent (even if over a short amount of days), and I just think it deserves a bit more recognition than simply asking for the source. I don't mean that you guys should perform a ritual dance before forking the kernel on github, but, I mean, I mean you gotta understand what I mean, right? Because I don't think we're in a place where you just do what you can do, because if you can do it and no one stops you then that's what you did i.e. history simply proves you correct.

For example, you could have just said that you're interested in the WiFi changes while asking for the source, instead of just asking for the source[1].

[1] https://en.wikipedia.org/wiki/Courtesy

EDIT: Actually I think that especially because the bare rules allow anyone to do anything with the source, more or less, we shouldn't forget the human aspect and should not forget to communicate, because I think the notion of "communicating through code" (i.e. forking, creating patches, submitting them, making builds, etc.) is flawed and doesn't allow for the entire range of communication necessary to avoid misunderstandings.
[Pixel C Android Development] followmsi:
Whats going on ?

The main problem here: We have a different understanding of community.

https://en.wikipedia.org/wiki/Community :)

Like using the lazyflasher installer .. the community should have the benefit - not you and me.

I am searching for the best sources for the dragon device - for the community and not for my ego.

And not for my paypal account either !

Do you want to have a nice credit statement like I did for the DU kernel ?

No problem if this helps you ..

I have changed the LOCALVERSION - we all know where the new sources are coming from.

You did start your new activties with my cloned kernel .. my old commits are part of your commit history.

Did you inform me ? Don't missunderstand .. I am happy you used "my" sources as base.

Just measuring and comparing the different sources / kernels ..

On stock/du kernel I do have similar results like on your kernel too.

- 8 hours 100% is no problem either.

- My battery also last for 2 days with "heavy" usage.

- Wifi download performance seems to be even better

Still testing but sorry to say .. your kernel is not "another level" of dragon kernel !

By repeating some facts they become not automatically true.

Yes, you are doing good work and we all appreciate your work, but - unlike you said - you are a little drama queen right now :)

We have anyway a small dragon community .. for this reason we should work together !
[Pixel C Android Development] cheep5k8:
OK well. I wasn't saying I'm the only one doing great stuff - everyone here is, developers and users alike, regarding the small size of the community, like you said.

I think I might have gotten in a rush. A few days ago I was really annoyed at the constant WiFi wakelocks and set out to fix that issue and got into a frenzy where I basically slept and then worked all day on the kernel (almost). That probably isn't very good in the long run, so I will push xceed-9.40 and then take a while off developing the kernel. Probably not a year :angel:

Everyone feel free to pull the code and make builds etc. like it's meant to. I don't mean to, in sort of the opposite direction of what I was talking about earlier, impose or create the apparition of some kind of rule or requirement that would prevent anyone working freely with my kernel code.
[Pixel C Android Development] followmsi:
Yes, working 24h nonstop is never healthy ;)

Maybe you take a short break and come back soon .. with 9.41 onboard.

The community wants the xceed kernel .. and me too.

Peace !
[Pixel C Android Development] NYCHitman1:
I think you read a bit too much into my statement. I have zero plans or desire to fork your kernel. As I intimated previously, I was simply interested as an experiment. That has absolutely no bearing on whether or not any commit created by you (or anyone else) will get committed to my team's gerrit or github source. The odds are that it wouldn't seeing as I also indicated that I have no WiFi issues whatsoever.

If you're having a bad day or something, I'd recommend getting off XDA instead of picking arguments over such miniscule (albeit misinterpreted) statements.

At the same time, I find myself wondering if you actually know what protections are afforded in the GPL and/or XDA's stance on GPL violations/violators.

Link to GPL: https://www.gnu.org/licenses/gpl-3.0.en.html

If you're in this for the recognition or a pat on the back -- you chose the wrong device to support and you're doing this for the wrong reasons.
[Pixel C Android Development] cheep5k8:
No, I didn't. And I've probably worked longer under public peer review with the GPL than most people here, I'm fully aware of what it implies. But that doesn't mean that we should only communicate via pushes, pulls, merges, rebases and builds. But maybe I am having a bad day, so now I'll go to chill out a bit. Everyone have a nice weekend.

---------- Post added at 06:42 PM ---------- Previous post was at 06:28 PM ----------

PS: No developer for any device should come here with the expectation of back pats, not just for the Dragon.

Maybe I'm too out of touch with the community because of the year that I was gone. I'm not being sarcastic. And maybe the original days where I was the first guy to develop a custom kernel and take care of the wifi issues went to my head. Again, no sarcasm intended. So I'll take a couple of days off. Cya.
[Pixel C Android Development] Alxoom33:
You guys were doing so well, playing together in the same sandbox and building great dragon kernels. What happened?[emoji22]
[Pixel C Android Development] drewski_1:
I, for one, am glad to see you back and contributing to our device! :victory:
[Pixel C Android Development] followmsi:
I want to have a good kernel - and no discussions anyway.

It's strange that I have to write it at all - but this kernel below is not a provaction or anyting else !

I just used the time as my kids are playing in the garden - without me.

And I want to get back my old download speed :)

tegra-3.18_kernel_dragon_v170429_unicorn-xceed-followmsi.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU !

Changes:

- use stock bcmdhd wireless driver - android-7.1.2_r0.1

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2017-04-29

Enjoy your weekend ... PEACE !
[Pixel C Android Development] cam30era:
[MENTION=5480152]followmsi[/MENTION], Thanks. And you get to do it again Monday... ;)
[Pixel C Android Development] followmsi:
The result of using stock driver again .. back to normal. ;)

Just on my setup with my router .. etc. .. this may differ in your environment.

Cheers
[Pixel C Android Development] Alxoom33:
Thank you! Have a great weekend.
[Pixel C Android Development] cam30era:
[MENTION=5480152]followmsi[/MENTION],

FWIW: [MENTION=4544860]osm0sis[/MENTION] Android Image Kitchen now works fine with ChromeOS. See post #1167.

> https://xdaforums.com/showthread.php?p=71218371&highlight=chromeos#post71218371

I just used it (very easily) unpack boot.img, make "encryptable" fstab, and repack and sign. Took about 30 seconds.
[Pixel C Android Development] followmsi:
Cool .. always more and more support for Pixel C ;)

https://github.com/osm0sis/AnyKernel2/commit/092a3b38809317fc67df68eecdb217a3c72d9aa0
[Pixel C Android Development] followmsi:
As it's a really cool tool ... here the last kernel binary (Image.fit) as AnyKernel2 version now :)

tegra-3.18_kernel_dragon_v170429_unicorn-xceed-followmsi-AnyKernel2.zip

Forked the AnyKernel2 repo and made a new "dragon" branch including all the required stuff (futility ..etc.)

Removed the ramdisk, patch and modules folders as we just want to replace the kernel binary only.

https://github.com/followmsi/AnyKernel2/tree/dragon

Just replace the Image.fit with your own version and zip the complete folder !

You may change the "anykernel.sh" script for your own setup.

Enjoy easy kernel flashing powered by [MENTION=4544860]osm0sis[/MENTION] :)
[Pixel C Android Development] nigelhealy:
May's image out
[Pixel C Android Development] followmsi:
Android 7.1.2 Monthly Release (N2G47O, May 2017):

Update.ZIP_PixelC_Ryu_system-vendor-boot_N2G47O.zip

Waiting for the new sources :)
[Pixel C Android Development] nigelhealy:
Boots right back into recovery. Trying to debug now.

---------- Post added at 02:02 PM ---------- Previous post was at 01:41 PM ----------

So the system-vendor update by itself does not boot. There is something in the prior kernel not working with the new system-vendor. I went back to system-vendor N2G47D and it worked. I'll wait for new kernel to go along with new system-vendor and try again.
[Pixel C Android Development] followmsi:
The update.zip contains stock boot.img from May.

Did you install Supersu at last step ?

Which kernel are you installing ?

A complete boot.img ?

More details pls !
[Pixel C Android Development] nigelhealy:
Was on Update.ZIP_PixelC_Ryu_system-vendor-boot_N2G47D.zip, supersu, tegra-3.18_kernel_dragon_v170429_unicorn-xceed-followmsi-AnyKernel2.zip. That was working.

When applied Update.ZIP_PixelC_Ryu_system-vendor-boot_N2G47O.zip it would not boot, back into recovery. Then flashed it again and tegra-3.18_kernel_dragon_v170429_unicorn-xceed-followmsi-AnyKernel2.zip and it would begin booting, then back into recovery. Then flashed it again and supersu, and would boot, went back to recovery.

So then simply Update.ZIP_PixelC_Ryu_system-vendor-boot_N2G47D.zip, tegra-3.18_kernel_dragon_v170429_unicorn-xceed-followmsi-AnyKernel2.zip, then supersu. Then worked as before I started.

So there's something changed in the kernel we need to wait for.
[Pixel C Android Development] followmsi:
If you just install the new "O" update.zip and supersu only.

Then reboot into system .. does it boot ?

If this is not working we have 2 possible problems ..

- the update.zip is not working as it should.

- supersu does not work on latest may security patch level.

The new sources should arrive in the next time .. we will see.
[Pixel C Android Development] nigelhealy:
If I go into recovery and flash Update.ZIP_PixelC_Ryu_system-vendor-boot_N2G47O.zip and then flash SR3-SuperSU-v2.79-SR3-20170114223742.zip , then wipe dalvik/cache (why not) then reboot system, then I get no errors during flashing (other than the data-full message i've had for months without problems), and it shows Google logo, booting graphic, asks me to unlock, booting graphic, reboots, google logo, animation graphic, it then boots.

But my system-about is showing a kernel from Google from March 25th, so its overwritten your kernel. So, says to me I need to wait for you to update your kernel.
[Pixel C Android Development] followmsi:
Ok .. the update.zip is working - fine.

Good news.

Yes, this is normal .. as we use stock boot.img inside the update.zip.

Now you have a stock Google kernel ;)

Once you have booted into system with the Google kernel .. reboot into TWRP and install the anykernel.

What happens then ?

Bootloop ?

If this happens we indeed need to wait for the new kernel sources ..

android-7.1.2_r9 is the new version .. they started to push the new sources ;)

https://android.googlesource.com/kernel/tegra/+/android-7.1.2_r0.9
[Pixel C Android Development] nigelhealy:
So beginning with a working state, on Goog's March 25th kernel and May 5th security path with N2G47O, if i boot into recovery and flash tegra-3.18_kernel_dragon_v170429_unicorn-xceed-followmsi-AnyKernel2.zip then the flash says "done!" , reboot into system, google logo, animation, unlock, animation, boot! That's a surprise.

Now its May 5th security patch level, Followmsi Apr 29th kernel and N2G47O.

Weird it worked when done in that sequence (system-vendor-boot, supersu, boot, kernel, boot) but not system-vendor-boot, kernel, boot or system-vendor-boot, supersu, boot, kernel.
[Pixel C Android Development] followmsi:
Let SuperSU do his ramdisk modifications without installing Anykernel at the same time.

Have seen several issues .. too many ramdisk tasks at once !

Take a reboot in between and you see .. it works.

Now you can play with this kernel ... :)

tegra-3.18_kernel_dragon_v170502_unicorn-xceed-followmsi.zip

Cheers
[Pixel C Android Development] followmsi:
New May updates included ...

tegra-3.18_kernel_dragon_v170502_unicorn-xceed-followmsi.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU !

Changes:

- Latest Dirty Unicorn kernel changes

- Google May 2017 kernel updates - android-7.1.2_r0.9

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2017-05-02

Enjoy ... PEACE !
[Pixel C Android Development] nigelhealy:
[MENTION=5480152]followmsi[/MENTION] "The person sharing it has exceeded their sharing limit. Please try again later"

View attachment 4135951

Sounds like you should move to a less obtuse alternative
[Pixel C Android Development] followmsi:
It's temporarily ..

https://xdaforums.com/showpost.php?p=72129238&postcount=59

But anyway - very annoying - I will move soon .. started already.

Here you can find the latest kernel too ..

https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg

Bye bye .. onedrive :)
[Pixel C Android Development] nigelhealy:
Flashed it and works. Thanks.
[Pixel C Android Development] followmsi:
Yep .. like the Flo ROM too ;)
[Pixel C Android Development] Alxoom33:
Is it just me, or does it seem strange that the Patch level is May 5, 2017 but it was available on May 1?
[Pixel C Android Development] followmsi:
Supported Google devices will receive a single OTA update with the May 05, 2017 security patch level.

https://source.android.com/security/bulletin/2017-05-01

But yes .. it's a bit strange ;)
[Pixel C Android Development] timal:
Thank you for all your work !
[Pixel C Android Development] followmsi:
You're welcome ..
[Pixel C Android Development] Alxoom33:
Thanks, I guess they must have been ahead of schedule, or someone pressed the publish button a bit early.
[Pixel C Android Development] cam30era:
[MENTION=5480152]followmsi[/MENTION],

interesting article > https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Pixel C Android Development] followmsi:
Its every month like this ..

Sometimes before they released on Wednesday .. now it's Monday.

In June the relevant Monday will be the 5th actually - so it fits again ;)
[Pixel C Android Development] followmsi:
Thanks .. interesting indeed.

This is general verified boot signing for all (other) Android devices.

This is very similar to chromeos signing where we use development keys for signing, we on dragon are used to it ;)

The dragon bootloader is checking for the chromeos signing today.

The pixel XL bootloader will check for the Android keys now/soon .. since May, like Chainfire mentioned.

And for the flo/deb devices too ?

I doubt, as they will not change bootloader for all the "old" devices.

I hope so at least ;)

But for tools like supersu, as the main task is to unpack/repack boot.img this much more important.

Also for anykernel and lazyflasher .. both need to make changes.

To be able to repack proper boot.img for Pixel XL in the future.

If (general) OEM keys are not to be used anymore .. all the future boot.img are signed by [MENTION=4544860]osm0sis[/MENTION] instead ;)
[Pixel C Android Development] followmsi:
Time for a new kernel ...

tegra-3.18_kernel_dragon_v170512_unicorn-xceed-followmsi.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Dirty Unicorn kernel changes - thx to [MENTION=2489052]NYCHitman1[/MENTION]

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2017-05-12

Enjoy :)
[Pixel C Android Development] followmsi:
Just to let you know ..

Due to several reasons I have stopped the deployment of the monthly "Update.Zip packages" !

This thread will be used for the unified tegra-3.18 kernel only.

Thanks for your understanding.

Cheers
[Pixel C Android Development] Alxoom33:
Upgraded to Android O DP2. Google updated DP2 today, not sure why. However, when I flashed custom recover, either TWRP 3.1.0 or 3.1.1 I have not been able to reeboot system. Stays in a recovery loop, even if I reboot with adb. Also, when I flashed SuperSu 2.79 SR4 the tablet bootloops. Has anyone had better sucess with O DP2?

https://goo.gl/photos/ogCd4r5F746Xer3z7
[Pixel C Android Development] nigelhealy:
Since I flashed your current kernel my usually stable unit has been resetting itself randomly.

What can I send you to allow you to find what to fix?
[Pixel C Android Development] followmsi:
On previous kernel no problems ?

Do you see any pattern ?

Or just randomly ?

It seems there are issues if you close down a VPN session ..

Logcat and /proc/kmsg .. etc. for collecting logs.

But you need to find the right time to capture the logs.

Will have a look as well ...
[Pixel C Android Development] nigelhealy:
the

On the previous tegra followmsi kernel it was fine.

Next time it resets I'll try to paste here the last logs.
[Pixel C Android Development] followmsi:
The ?

More information required here ..

To catch kernel issues pls use a command like this ..

cat /proc/kmsg >> /sdcard/Download/kmsg.log

Pls use latest kernel from today ..

Thanks

EDIT: changed to path to sdcard :)

As we want to save the logs .. not loosing them on reboot.
[Pixel C Android Development] followmsi:
Time for a new kernel ...

tegra-3.18_kernel_dragon_v170524_unicorn-xceed-followmsi.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Dirty Unicorn kernel changes - thx to [MENTION=2489052]NYCHitman1[/MENTION]

- Revert L2TP update

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2017-05-24

Enjoy :)
[Pixel C Android Development] Alxoom33:
Thanks, has it been tested on Android O, DP2?
[Pixel C Android Development] followmsi:
No .. not tested and the O changes are not included - but kernel should still work.

Just have a try .. :)

What about rooting DP2 ?
[Pixel C Android Development] Alxoom33:
I have not tried rooting without the custom recovery yet, will give it a shot in the next day or so.
[Pixel C Android Development] followmsi:
https://xdaforums.com/showpost.php?p=72391239&postcount=355

Pls let me know your results .. quite interesting topic :)

Cheers
[Pixel C Android Development] followmsi:
Only 3 days later ..

tegra-3.18_kernel_dragon_v170527_unicorn-xceed-followmsi.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Kernel su-hide to address an important vulnerabilty

This is a security recommendation .. https://lineageos.org/Changelog-9/ )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2017-05-27

Enjoy :)
[Pixel C Android Development] drewski_1:
interesting.

so this would only be useful for LOS ROMs using their root solution to enable / disable root in settings?
[Pixel C Android Development] followmsi:
Yes, mainly for the lineageos supersu.

To make it invisible to other processes.

But for testing I did use magisk v12 only.

Magisk hide was disabled, installed new kernel via TWRP and rebooted into system to test play store quickly.

Netflix etc.. are not hidden to me.

Needs to be tested again .. and with Supersu too ..

As I understood the change is not breaking anything, just improving security ;)

EDIT:

Made another reboot and triggered some magisk supersu actions.

Started PlayStore again and now .. no Netflix app anymore.

I guess some cached magisk hide settings are the reason why it was working before.

Never test too quickly ;)