yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Alxoom33:
Deleted, repat post.
[Pixel C Android Development] drewski_1:
Linaro is the toolchain used for the build. Pretty commonly​ used so shouldn't be an issue
[Pixel C Android Development] Alxoom33:
Thanks, reflashed 9.38 with SuperSU 2.79 SR 4 (which is a special test build just for Pixel devices) and booted up with no problems. I am not sure if I had a bad dl with 9.36 or it was a bad upload, but we are good now!

I reread your post. Yes, I am encrypted, so bootlooped with 9.36. Your changes for 9.38 fixed the bootlooping problem.

Thank you!
[Pixel C Android Development] JerrellWong:
Just flashed the kernel on my pixel c running purenexus booted successfully :D

Will test wifi , battery and stuff when I'm back home ?

Just to confirm again , when I wanna update , I just flash the updated boot image again right , then SuperSU
[Pixel C Android Development] smitel:
cheep5k8: For test I wanted to rebuild your kernel and replace the xpad module with https://github.com/paroj/xpad to make it support my Xbox One controller.

I think I'm mostly running into issues with the rebuilding. Do you use 'make bootimage' after replacing the kernel in your AOSP tree or something else?
[Pixel C Android Development] cheep5k8:
Yes, that is correct. I build the kernel first with make Image.fit, then put the kernel image in device/google/dragon-kernel, and run make bootimage.

You know that you have to run "source build/envsetup.sh" and "lunch" before running make bootimage? Just making sure. :cool:

At some point I want to integrate the kernel source into my AOSP tree like in PureNexus buuuuuuuuuuut2lazy4now ;)
[Pixel C Android Development] smitel:
I wanted to cheat and just use unpackbootimg to get the ramdisk and stuff from your kernel and then repack it with mkbootimg, but it doesn't seem to make a kernel 'CHROMEOS' but just a 'ANDROID' kernel.

I guess I'll just have to suck it up and pull down the AOSP tree. See you in a few hours. ;)
[Pixel C Android Development] cheep5k8:
A fast internet connection is definitely useful when dealing with AOSP ;)

Yeah, you would need to use futility (not as in futile..) to pack the kernel into a depthcharge boot image. You CAN find out how to do that, "real" Chrome OS boot images are also just Linux kernels inside. Check the Chrome OS developer site.
[Pixel C Android Development] smitel:
Thanks for the hints.

Or maybe you could try adding the newer xpad to your kernel?

I'm doing it because it's supposed to make the Xbox One controller natively working in Android.

The current version only supports the Xbox 360 controller.
[Pixel C Android Development] cheep5k8:
Oh, sure. Good idea. I'll look into it for the next build.
[Pixel C Android Development] 12paq:
Happy to report xceed-9.38-purenexus no force encryption on Pure Nexus 7.1.2 boots and runs great. :)
[Pixel C Android Development] cheep5k8:
:highfive:
[Pixel C Android Development] followmsi:
[MENTION=4867279]cheep5k8[/MENTION]

I have made a lazyflasher version of your xceed-9.38 AOSP kernel .. xceed-9.38_kernel-flasher-5.1-20170426.zip

This way we can test your new stuff on ResurrectionRemix & LineageOS as well.

I guess this version works on PureNexus too ..

Don't care about the ramdisk - just the binary is important ! ;)
[Pixel C Android Development] cheep5k8:
Cool, this is great! Thanks a lot. One of these days I'm gonna try a custom ROM too :laugh:
[Pixel C Android Development] cheep5k8:
Did you add the download link anywhere else than in this post? Perhaps we should make it more visible somewhere...

EDIT: I'll Just upload it to my AFH
[Pixel C Android Development] followmsi:
Not yet .. pls go for it.

Maybe xceed-9.39 will come as lazyflasher version (only) ? ;)
[Pixel C Android Development] Alxoom33:
Aren't you two playing nice together!

Great to see.?
[Pixel C Android Development] YevOmega:
[MENTION=5480152]followmsi[/MENTION] [MENTION=4867279]cheep5k8[/MENTION] Thank you guys so much!
[Pixel C Android Development] smitel:
Ha! A few posts before yours I discussed my issues with repacking the kernel. Lazypatcher brilliantly solves this, yay!

dragon:/ # uname -a
Linux localhost 3.18.50-10567-g9cd705b #1 SMP PREEMPT Thu Apr 27 09:31:26 DST 2017 aarch64

Now running my own rebuild of xceed on my Pixel C. Awesomesauce!

[MENTION=4867279]cheep5k8[/MENTION]: replacing the xpad.c with the version from https://github.com/paroj/xpad makes my Xbox One controller working on Android as hoped. :D
[Pixel C Android Development] followmsi:
Have added the xpad.c yesterday ;)

https://github.com/followmsi/android_kernel_tegra/commit/bcc3187e51d5961aefd3f675b688ebacd40dc959
[Pixel C Android Development] cheep5k8:
Great! :D
[Pixel C Android Development] cheep5k8:
OK, so, on suggestion by [MENTION=6556954]smitel[/MENTION] I'm researching using the original actual bcmdhd WiFi driver (not from the chromeos kernel tree but the actual Android one), while keeping my other changes related to to it.

As it turns out, GSCAN is apparently at least meant to be a scanning offload feature; I don't really see how that can even work seeing that it doesn't happen in the firmware, but alas. So I thought, at least I can give it a try.

I'm still testing, and the results look.. interesting at least. Deep Sleep is almost the same as with my version of bcmdhd, and WiFi strength and transfer rates seem to be comparable, but it seems that deep sleep can vary a lot, while it does not so with my driver.

I'm gonna keep testing this through the day and then see what the best course of action might be regarding the driver.
[Pixel C Android Development] cheep5k8:
OK, I'm aborting the test now.... I'm pretty sure that for the forseeable future I'm going to stick with my driver.

The Android bcmdhd does:

Seem to offer no benefit regarding scanning or scanning offload (deep sleep is not by much, but definitely worse than with my bcmdhd, and connectivity/finding APs is not improved in any way)

Often disconnects when the tablet is in screen off and/or suspend; this happens with my driver too, and used to be frequent, but I managed to get this under control as well, and is rather rare now

Deep Sleep is, on average, comparable to my driver, but there are spikes now and then where deep sleep sinks down to about 25%, whereas with my driver it's constant at about 85% (on my Tablet; should be similar for you)

All in all while GSCAN might be, technically, missing from my driver I do currently not see that it offers any benefit in any way; in fact, it seems to make matters worse.

It might be that I wasn't entirely correct about GSCAN in my other post in Pixel C General, but I still think that the main use is gathering AP data for Google's location service, even if indirectly so, and adding GSCAN to the driver only makes Deep Sleep worse.

So for the time being: nope ;)
[Pixel C Android Development] cheep5k8:
Also, I would like to pull back on the statement a bit that leaving GSCAN out is a "political decision".

The history is that when I ported nvidia's bcmdhd driver, I didn't even realize that something was missing. It was only later that I found out that GSCAN is not implemented.

However, upon further research while actually attempting to port GSCAN to nvidia's bcmdhd driver I realized that the most likely purpose for this is in aiding Android to create a mesh of APs around you for Google's location service, even if indirectly (i.e. it is not stated as such in the GSCAN source code in the driver or something).

So I was a bit overenthusiastic about that and made that post in Pixel C General. But, I don't want to make this kernel be influenced by any kind of political agenda. This is really not about flipping off Google or something like that. I still think their AP scanning is invasive, but leaving out GSCAN in my/nvidia's bcmdhd, or rather, not porting it there from Google's driver should be a purely technical decision, and that's what it was before I went a bit overboard with that other post.

I hope you can kinda forgive me for being a bit excited and I want to assure you that if GSCAN would offer any benefits, purely technical and/or from a UX perspective, to you, I would implement it, but currently, it doesn't look that way (see post above).
[Pixel C Android Development] cheep5k8:
OK guys. I made a different decision:

I'm going to implement GSCAN in "my" (nvidia's) driver, based on the Android driver's code, and improve it, so that we retain all benefits that we have so far, and additionally have, at least technically (I still have my doubts), the scan offloading.

:D
[Pixel C Android Development] r_nation:
Happy to report, after two days of use on PN 9.38 i've had no wifi drops(: battery life is significantly improved as well. I can get around 4.5 hours of heavy gaming w/viper4android enabled..GREAT JOB
[Pixel C Android Development] smitel:
I think there are 2 parts to the 'gscan' stuff.

* (Enhanced) Preferred Network Offloading

* Wifi Localization Services

ePNO allows Android to provide the WiFi firmware with a list of interesting SSIDs, to allow the WiFi firmware to independently probe for networks and send an event when something interesting happens.

Instead of needing the AP to wake up from sleep to poll the WiFi.

So this would allow the CPU to sleep more.

However, this functionality is not enabled in Android: https://android.googlesource.com/pl...erver/wifi/scanner/HalWifiScannerImpl.java#50

https://android.googlesource.com/pl...fi/+/7ce0f144104c68da40c196c16f73e2d0bcc50cc7

With regards to WiFi Location Services, it lets the firmware collect signalstrength data of the SSIDs around you, to help localization.

I haven't really been able to trace how this is used in Android.
[Pixel C Android Development] cheep5k8:
Very cool! Thanks for the report! :D
[Pixel C Android Development] Reuben_skelz92:
Random question. Is there any way for a developer to create a mod it enable night mode on stock? I would like stock rooted but the only thing that makes me have to use PN etc is the lack of night mode on stock
[Pixel C Android Development] cheep5k8:
Yeah sure. Here you go. Just put the attached apk into /vendor/overlay (check the file permissions!) and reboot.
[Pixel C Android Development] r_nation:
Random question #2.. I have a Alfa 1000mW AWUSO36H wireless adapter and the pixel dosen't recognize it. Would it be possible to integrate wireless adapter support? I have no idea of the complexity this would involve...
[Pixel C Android Development] Reuben_skelz92:
That easy haha
[Pixel C Android Development] cheep5k8:
I'll check if there's a driver in Linux 3.18
[Pixel C Android Development] cheep5k8:
9.40 lazyflash

Hey guys,

Following [MENTION=5480152]followmsi[/MENTION] ;) I've released 9.40 as a lazyflash ZIP only. It should work on PureNexus as well as AOSP/Stock and other ROMs.

Changes are:

* Use updated xpad.c driver

* Include support for mac80211 RTL8187 USB WiFi cards

Because of that last option, the kernel is now almost twice as big. Don't be alarmed. A lot of additional drivers had to be compiled into the kernel for this option. Let's see if it even works. Paging [MENTION=7095878]r_nation[/MENTION]: please give it a whirl and report back. In case it doesn't work anyway I'll know that I can remove it again.

The release is in the "xceed-lazyflasher" section on AFH.
[Pixel C Android Development] r_nation:
I apologize, i've never lazyflashed i haven't a clue how to do it...
[Pixel C Android Development] followmsi:
Using TWRP only ...

https://twrp.me/devices/googlepixelc.html

It will replace your kernel binary (Image.fit) only.

No changes are done to the ramdisk (if the scripts are removed from the sources).

If you had SuperSU installed before .... you still have it.

If you have changed DM-verity .. it's still unchanged.

Again .. we change the kernel only !

Hope this helps ...

EDIT:

Installation:

1. Boot into TWRP

2.*Install*the Kernel .Zip*file

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

---------- Post added at 22:35 ---------- Previous post was at 22:34 ----------

Thanks for switching to lazyflasher .. makes the life easier for all of us :)
[Pixel C Android Development] r_nation:
Ok I flashed 9.40.zip, kernel version changed to 9.40 but unfortunately pixel dosen't pick up adapter:/ I wouldn't think pixel would require a specific y-cable..I REALLY appreciate your time and effort though, I'm very grateful(:
[Pixel C Android Development] r_nation:
Thank you kind sir.
[Pixel C Android Development] drewski_1:
Is this about the same as Osmosis' AnyKernel that a lot of kernel dev's use (which I thought also doesn't touch ramdisk)? Or better functionality?
[Pixel C Android Development] Alxoom33:
I changed permissions, same as other apk that you provided. I saw a toggle in Settings/Display that tints the display amber. Is that the action of the apk? Or is there something else?

Thanks,

---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------

Thanks, I placed apk in System/Vendor/Overlay and changed permissions. Just wanted to make sure what Settings that this apk affects?
[Pixel C Android Development] drewski_1:
why are you adding overlays willy-nilly, if you don't understand what they are supposed to do?
[Pixel C Android Development] Alxoom33:
I understand what they are supposed to do. I don't know everything that they do. So I asked.
[Pixel C Android Development] followmsi:
Kind of the same functionality .. but lazyflasher works with chromeos signed boot.img too.

Not sure about anykernel which is also very good.
[Pixel C Android Development] JerrellWong:
hi, sorry i noticed that there is a new folder called xceed lazyflasher, caan i just confirm that the 1 file there can be used on both purenexus and stock ? thanks for the great work :)
[Pixel C Android Development] cheep5k8:
Hey,

Yes, at the moment anyway. So far the xceed kernel works on both PN and Stock (AOSP), just the ramdisk is different. LazyFlasher solves that by reusing the existing ramdisk, so basically you can "just" flash it, unless you currently have a kernel that doesn't boot or bootloops. In such a case it'd be best to first install the respective stock kernel (PN or stock or other ROM's kernel) and then flash this ZIP (same really goes for any LazyFlasher ZIP kernel).
[Pixel C Android Development] cam30era:
I agree, [MENTION=1143630]osmosis[/MENTION] anykernel is very good. But it doesn't work with ChromeOS.

Edit: I stand corrected. Android Image Kitchen now supports ChromeOS.
[Pixel C Android Development] drewski_1:
sent you some beer money. enjoy your weekend!
[Pixel C Android Development] DaConcho:
Holy crap... Dirty Unicorns and Xceed.. I thought my battery meter wasn't reading correctly at first but nope.. Almost 24 hours of 0% battery drain.
[Pixel C Android Development] cheep5k8:
Hey,

Just FYI (mostly relevant for [MENTION=5480152]followmsi[/MENTION] I guess):

The xceed 9.40 build that I've uploaded is, as I noticed, actually different from 9.40 in git. In git, I've rebased 9.40 on followmsi's kernel (mostly just to test it, but it applied cleanly except for some configuration files) and I pushed it like that, however the build 9.40 does not contain these changes.

Sorry for the confusion.
[Pixel C Android Development] followmsi:
Thanks for the update !
[Pixel C Android Development] r_nation:
I flashed back to 9.38..for whatever reason 9.40 was making my tablet alot warmer when gaming and battery life for me personally is better on 9.38..xceed saved my tablet lol, thank you
[Pixel C Android Development] cheep5k8:
Hmm. Ok thanks, good to know. I'll check what changed between 9.38 and 9.40 (save for the rebase on followmsi's kernel which I'll probably revert for practical reasons, so it's easier for him to make the unified kernel).
[Pixel C Android Development] Alxoom33:
The ambient display layers all works with the May 7.1.2 patch. Unfortunately the night mode layers apk no longer enables night mode.?
[Pixel C Android Development] JerrellWong:
ambient display ? ? , Could you tell me how to get that on my dragon running purenexus , xceed 9.40
[Pixel C Android Development] drewski_1:
Settings->Display
[Pixel C Android Development] JerrellWong:
Are you on stock rom ? It's not here in pn
[Pixel C Android Development] Alxoom33:
You need to add the apk in Vendor/Overlays
[Pixel C Android Development] JerrellWong:
yea i cant see overlays in vendor
[Pixel C Android Development] cheep5k8:
Just create the path. "/vendor/overlay/". And then copy all overlay APKs that you want in there. :)

Make sure you set the APK file permissions correctly. "chmod 644 <apk>" will do it.
[Pixel C Android Development] ~El Julio~:
Weird. It's the opposite for me. (Haven't tested on previous builds however)
[Pixel C Android Development] JerrellWong:
Okay thanks man , so I just create the path "overlays " inside the vendor portion and paste my apk there. I need to install it too right ?
[Pixel C Android Development] ~El Julio~:
A simple reboot should do.
[Pixel C Android Development] JerrellWong:
am i doing something wrong :p its not working
[Pixel C Android Development] Alxoom33:
Not on previous build, on the latest May 2017 release. Are you on O DP1?
[Pixel C Android Development] ~El Julio~:
Stable May 7.1.2 (N2G47O)
[Pixel C Android Development] cheep5k8:
hmm.. seems right to me. not sure what the problem is.
[Pixel C Android Development] Alxoom33:
OK, we are on the same build. For me the Overlay.apk is working fine, but the night Mode.apk does not function. Funny, since it worked on the April build and it also works on my Nexus 6, although that is a 7.1.1 build. Not sure why it's not working now. I have the 9.40 kernel and also tested it with [MENTION=5480152]followmsi[/MENTION]'s kernel. Same result.
[Pixel C Android Development] ~El Julio~:
Don't know if it's intended but both APKs are bearing the same package name, signature and UID. That might be the problem.
[Pixel C Android Development] Alxoom33:
No, one is called nitemode.apk and the other one is called layers.apk, or am I missing something?
[Pixel C Android Development] ~El Julio~:
I don't know where you got those file names from (mines are nightmode-overlay-dragon.apk & overlay.apk - original attached files​ names if it's of any relevance) but I was talking about package names which according to the solid explorer readings of both files' properties are the same. That might be only anecdotal though.

But given signatures & uid are identical to both too, I thought I'd tell since it's a first for me & I guess it would potentially cause a conflict resulting in one of those two not working. However, it seems JerrellWong can't get a one to work without this potential conflict thing going on so I suppose I'm wrong anyways.
[Pixel C Android Development] Alxoom33:
LOL!!! I know I had the file names wrong, but you got the general idea....I think the problem has to do with the update, since I had both working on the April build, although itt was with the 9.38 kernel.
[Pixel C Android Development] cheep5k8:
Yes, I posted two APKs which overlay the same package. The one I posted second only enables night mode, the previous one also some other options like Ambient Display. Installing both probably doesn't work too well (but going into detail, they just might work together because the second one changes one boolean that the previous one changes too.. what I mean is that the reason for it not working might be something else. Maybe.)
[Pixel C Android Development] Alxoom33:
Could all of these be combined in a single flashable zip without the potential redundancy?
[Pixel C Android Development] drewski_1:
edit: reread and am confused. need a beer :)
[Pixel C Android Development] drewski_1:
I have Ambient & no Nightmode.

Xceed 9.40 & followmsi's mixed kernel. Still on April 7.1.2

Both were working with 9.38 . . . Iirc :cool:
[Pixel C Android Development] Alxoom33:
Tried 9.38 with and without lazy flasher, with May patch 7.1.2 Stock, Rooted, still coulden't get nite mode working.
[Pixel C Android Development] drewski_1:
I just upgraded to 7.1.2 May update

Ambient still working. No go on night mode.

Stock kernel
[Pixel C Android Development] ~El Julio~:
In my case :

- "Unified" kernel after a factory reset

- Both APKs pasted & chmod'ed at the same time (the night mode one was actually the first to get pasted & chmod'ed)

A deletion of the overlay.apk followed by a reboot and then a retry with it still won't do. Night mode only for me.
[Pixel C Android Development] Alxoom33:
Well non of our tests seem to be conclusive. We can't know if it's the May 7.1.2 update or the 9.40 kernel, or the combination of two overlapping apk's. The only thing I know for sure is that Nite mode is not working for me.

---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------

Did you change permissions to 622 or 644?
[Pixel C Android Development] ~El Julio~:
644, of course.
[Pixel C Android Development] Alxoom33:
The reason I asked, is if you have layers/substratum installed, the apk permissions for all the layers are 622.

I officially give up.
[Pixel C Android Development] followmsi:
Have a try with this file ... night-light_overlay.apk

I have used it before on manta and flo .. but I have added NightView as part of the sources.

https://github.com/followmsi/platfo...mmit/624fd8d5fee9f920692514d40720cdca46d8d121

And pls remove the content of /data/resource-cache before your reboot with the new apk.

Dont forget the file permissions.

Just saw your problems and uploaded the file ... it's working for all devices - not only for dragon.

Tested successfully on nexus 10 before.

As I saw your problems I made a fresh test on AOSP 7.1.2 - May 2017 :)

Just have a try .. seems to be an interesting issue.
[Pixel C Android Development] Alxoom33:
I think that you linked the wrong files. Not .apk
[Pixel C Android Development] followmsi:
Pls have a look into the folder ... there is one file called .. night-light_overlay.apk :p

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

AND .. ? Does it work for you ? :)
[Pixel C Android Development] Alxoom33:
LOL! Your link brings me to a series of Rom zip files in a folder, not apk. I'll look at your downloads in your other thread.

Edit: That didn't work. Here is a screenshot of where the link brings me:

https://goo.gl/photos/YYqMLR8UhxcaDDEf8
[Pixel C Android Development] followmsi:
Starting the same issues with g drive now ?

For me its in ...
[Pixel C Android Development] YevOmega:
[MENTION=2489052]NYCHitman1[/MENTION] [MENTION=4867279]cheep5k8[/MENTION] Can I use Xceed on the latest DU?

Edit: Never mind. Decided to try and install it. Running great!
[Pixel C Android Development] Alxoom33:
Wierd, just for s&g's I tried another Google Drive account that I had and the apk was there. It did not work on my normal Google Drive. Not sure why.

---------- Post added at 11:11 PM ---------- Previous post was at 10:34 PM ----------

Tried it, did not work. Funny thing, when I tried to delete the overlay.apk the device bootlooped.

I think there may be a conflict between this and the overlays.apk that I previously installed.
[Pixel C Android Development] followmsi:
Did you delete the content of this folder too ?

/data/resource-cache

We change nightlight only, should not give a bootloop.

But I don't know the content of the other apk files you are using.

Cheers
[Pixel C Android Development] Alxoom33:
Yes, I did delete the content of data/resource-cache The other file overlays.apk, was one provided on this thread by [MENTION=4867279]cheep5k8[/MENTION] at post #816, first discussed at post #148.

The apk has been somehow integrated in the framework, and when I try to delete it by renaming the apk as .apk.bak causes the device to bootloop.

I think that the interaction between these two apk's is the root of the problem. But I don't have the know-how to confirm or make the appropriate modification.
[Pixel C Android Development] followmsi:
My last try on the overlay .. :)

doze & night-light merged into one .apk .. doze_night-light_overlay.apk

Pls clean your /data/resource-cache again and just use this .apk only.

Cheers

EDIT:

I like to play :)

Checked this doze feature .. it seems you need another overlay apk - but for systemui.

Here it is .. doze_systemui-overlay.apk

Pls use both .apk files for the doze stuff ..