yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Alxoom33:
The night-light did not work, the doze apk did. However, by deleting both add-on apk's and deleting data/resource-cache I was able to get [MENTION=4867279]cheep5k8[/MENTION]'s two apk's to work, by activating them one at a time, first night-light and then Overlays.apk and clearing data/resource-cache each time as you have suggested.
[Pixel C Android Development] followmsi:
Confirmed .. made a mistake and did not enable "Night Mode" :(

<bool name="config_nightDisplayAvailable">false</bool>

Now in v2 :

<bool name="config_nightDisplayAvailable">true</bool>

Here is the correction .. doze_night-light_overlay-v2.apk

As it loks like .. the system ui (doze_systemui-overlay.apk) is not required at all.

Topic overlay closed ! :)
[Pixel C Android Development] ~El Julio~:
Confirmed working. Night mode ok, Ambient Display too.

However, Double-tap doesn't work & Lift to wake option isn't present.
[Pixel C Android Development] followmsi:
Confirmed .. the second mistake :)

doze_night-light_overlay-v3.apk

But as you say .. double-tap is not working .. I guess it's related to kernel.

The overlay itself is working .. also on latest builds and kernels.

But all the features are maybe not working as intended or like on other devices.

Cheers
[Pixel C Android Development] ~El Julio~:
All is there now. Working as expected for night mode & ambient display.

[MENTION=4867279]cheep5k8[/MENTION] had "ranted" about lack of access to proximity sensor & also double-tap a while back. Can't remember what it was due to but there seemed to be only one solution in order to being able to use these things, and it involved tearing the tablet open in order to "toggle a switch"... Hence the legit "rant" ;)
[Pixel C Android Development] ~El Julio~:
Sorry for OT but since it's still related to enabling "hidden" features, I had discovered that we can enable the Pixel animated home button by quiting Android Auto (gotta get it via other apps repos than the play store since it's "incompatible" (in truth : "useless") with our Cs).

I don't know what gets triggered nor how (I guess it acts on some flag(s)) but that might be something we can integrate in an eventual v4 if it is doable that way.
[Pixel C Android Development] Alxoom33:
The pixel animated home button has been working for me on this and prior versions of 7.1.2. But I never enabled Android Auto on my tablet. Why would you use Android Auto on the Pixel C?
[Pixel C Android Development] ~El Julio~:
Another weird thing on my end then. I've never had the animated button working by default. To be precise, I always have the basic plain white "disk" as default home button (without the outer circle)

I just did out of curiosity to see how it would behave (and it's indeed useless) and found out it enabled the animated home button (with it's outer circle) upon quiting it. So I keep it installed just to do that.

I don't get why I don't have it enabled by default though..
[Pixel C Android Development] Alxoom33:
Probably because you did not enable google assistant when you updated. That's what the animated home button is for.
[Pixel C Android Development] ~El Julio~:
My locale is set to French so I can't get it (yet?), but if I get you right, you're saying that Google Assistant is working on the C ? (I thought Google decided not to enable it on tablets..) I'll test setting my locale to English and test that then.
[Pixel C Android Development] Alxoom33:
No, not saying that. You have to enable Google Assistant by tweaking the build.prop.

There is an XDA thread on just that.

---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------

NO! Not enabled by Google. You need to tweak the build prop.

ro.opa.....=true to enable Google Assistant. I forget the exact command, but there is an XDA thread on enabling Google Assistant.

---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------

Nice work! Night Light and Ambient Notifications functions enabled with a single apk. Night Light activated automatically after sunset.

Great work! Thank you.
[Pixel C Android Development] ~El Julio~:
I had already read about that build.prop tweak, I also used to use Assistant enabler xposed module back when I still was using marshmallow in late 2016 but it never worked in landscape mode so I decided I'd wait for Google to enable it (in vain).

Is it now working in landscape mode ? (If not, that on top of changing locale to English and having to tweak build.prop every month is a no-go for me. Guess I'll wait for Xposed for Nougat)

Anyways, I'm glad I've discovered an odd way of getting the animated home button which is still a nice touch with now on tap.

Can't figure out what it is actually doing causing it to appear upon closing AA but that's definitely something to investigate.
[Pixel C Android Development] Alxoom33:
While you can activate Google Assistant by either saying "OK Google" or by long pressing the animated home button in landscape, Google Assistant switches to portrait, requiring you to read sideways or turn the tablet on its side. However, even with these limitations, I choose to keep it active on my devices. Never like to use xposed, as it poses a serious security risk.
[Pixel C Android Development] followmsi:
Not sure about required "hardware" changes for double tap .. etc.

https://www.androidheadlines.com/20...n-why-no-ok-google-or-double-tap-to-wake.html

Within the device tree ..

sensors: Disable Proximity sensor

https://android.googlesource.com/device/google/dragon/+/fa9da43394e93092740e42d8e47bf919d36f3390^!/

Why disabled ?

Cheers
[Pixel C Android Development] ~El Julio~:
I think the double tap to wake should at least be available/usable when the C is plugged in. That would really be convenient for desktop usages.

The proximity sensor being disabled thing is kind of weird : I remember having used KinScreen proximity sensor related options once, a while back (before june last year then, according to the commit's date in your second link [edit: it is dated 2015.. then I don't know how I could have been able to use it partially..]) when on Marshmallow -with topjohnwu's systemless Xposed v86.5- but just couldn't make any use of it because of the bad "calibration" it seemed to suffer from : 2 little feet distant from it was enough to have it reacting as if it were covered.. and once screen was off, it simply couldn't be used anymore.

Maybe that was a misconception which triggered that behavior hence they decided to simply disable it entirely. Just a guess..
[Pixel C Android Development] cam30era:
[MENTION=5480152]followmsi[/MENTION],

Interesting thread by [MENTION=4867279]cheep5k8[/MENTION] regarding "openness" of ChromeOS and DTTW...

https://xdaforums.com/pixel-c/general/pixel-c-rant-developer-perspective-t3301632
[Pixel C Android Development] Evans_jd:
Just updated PureNexus build and trying to reinstall Xceed.

I keep getting

Error Opening '<path to .img>' (Not a directory)

Tried all 3 downloads for PureNexus.

I had the same when I first installed the kernel but damned if I can remember how I got past it!

any clues?

---------- Post added at 10:16 PM ---------- Previous post was at 09:57 PM ----------

Ignore

was trying to flash in TWRP rather than via Fastboot.

All sorted
[Pixel C Android Development] r_nation:
Hmm i had no issues updating PureNexus and flashing xceed via twrp.
[Pixel C Android Development] zezayer:
Try installing "ultimate rotation control" from the play store. (other rotation apps are available, but this has worked wonders for me)

Fixes landscape assistant along with every other portrait only app.
[Pixel C Android Development] Alxoom33:
I used Rotation Manager control, in the past when I was having rotation issues with my Samsung S4. I uninstalled it years ago. Well, after seeing your post, I tried it and it worked surprisingly well on my Pixel C!

I forgot about the advantages of custom rotation control until your kind reminder. Thank you very much [MENTION=2268424]zezayer[/MENTION]!

https://goo.gl/photos/YD2jsRqHLYXDuS577
[Pixel C Android Development] GenMatrix:
[MENTION=4867279]cheep5k8[/MENTION]

What changed from 9.38 to 9.40? I've had three pixels , returned two because they stuttered terribly using moonlight. I tried kernel 9.40 and experienced the same stutter when using moonlight. Flashed 9.38 and for the first time in across 3 different pixels c's I don't have that dropped frames that I experienced prior.

I nearly choked in sheer joy. I love this device and am super curious as to what with the wifi could have impacted it.
[Pixel C Android Development] cheep5k8:
I didn't only change the Wifi. And yes, as others noted it is worth a closer look at what changed between 9.38 and 9.40.
[Pixel C Android Development] gtaadicto92:
Hi, does this work on the new Android O developer preview?
[Pixel C Android Development] cheep5k8:
Perhaps. I'll take a look.
[Pixel C Android Development] Alxoom33:
I don't think it will boot. I suggest that you wait for an O custom kernel version. The stock Google Kernel works well enough.
[Pixel C Android Development] y2kbugleung:
Excuse me. Does it work only on ASOP (no CM based ROM), right?

Does it work with Magisk?

Thanks.
[Pixel C Android Development] Alxoom33:
Good question. But to answer it you need to provide context, namely the Android version that you are asking about.
[Pixel C Android Development] y2kbugleung:
-deleted-
[Pixel C Android Development] followmsi:
[MENTION=3741818]y2kbugleung[/MENTION] [MENTION=4100646]Alxoom33[/MENTION]

Yes, the kernel should work on all ROM's for the dragon device.

Pls use the lazyflasher version to install ..

https://www.androidfilehost.com/?w=files&flid=175127

Yes, the kernel is also compatible with Magisk.

Tested with Magisk v12.

If you need to reinstall Magisk you may need to use stock boot.img for clean ramdisk installation.
[Pixel C Android Development] y2kbugleung:
Oh, by the way, I have noticed your username.

May I know what is the difference between your kernel and XCEED?

https://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591

I see you have added more CPU governer and I/O scheduler options.

I have found that my device is very lag when splitting screen, using Youtube and Telegram at the same time, and typing in Telegram.

Stock kernel seems to be fine.

I am still confirming this issue.
[Pixel C Android Development] LifeAsADroid:
Thanks for this work.

Is there somewhere I can get the stock kernel to flash back to my device? I'm having an issue with the tablet sticking on the boot screen (four colored dots spinning and spinning) and wanted to check if the stock kernel would fix the issue.

If it is on the same android file host page as listed in post 1, I'm having trouble finding it.

Thanks.
[Pixel C Android Development] cam30era:
Download the factory image, unzip it, extract the boot image, then fastboot flash boot.img.
[Pixel C Android Development] Alxoom33:
When you flash SuperSu isn't the stock boot.img saved in

/data?

Take a look for yourself!
[Pixel C Android Development] EvansJD:
Less deep sleep since update

Since updating Pure Nexus and re-flashing SuperSU and Xceed I dont see my device in Deep Sleep as often as before.

I see "Awake(Screen Off)" percentage much higher.

I've re-flashed and still get around 65% in Deep Sleep no matter how long I leave it

Have not installed any new apps.

Any ideas?
[Pixel C Android Development] followmsi:
"My" kernel is a merge of xceed, dirty unicorn and stock google sources using "my" kernel config for compilation.

Hope this helps.

All ways of systemless rooting are changing the ramdisk (inside boot.img).

To have a clean start pls flash the stock (unmodified) boot.img of your ROM.
[Pixel C Android Development] drewski_1:
what do your Wakelocks look like?
[Pixel C Android Development] EvansJD:
Does this help?

Not sure how to read tbh
[Pixel C Android Development] Bless1:
Has development for this kernel stoped? Just curious cause I like your work and haven't seen anything posted in a while.
[Pixel C Android Development] Avalun:
With the nocrypt thing i will lose all my data, right? Interestingly the test-boot-image works fine. with the encrypted stuff
[Pixel C Android Development] superchilpil:
Figured out my 404 issue. Just had to access your site through https instead of http.

Got it to boot, and SU works properly now!

ran ectool and got the same result

WP is enabled.
[Pixel C Android Development] dkryder:
a few observations from overnight.

although i can uninstall apps and the settings/system does not crash, i also get a FAIL with bootloader with "unable to verify image" messages. so i think i need a fix of sorts.

when i run ectool i get what cheep5k8 does . i get no tcsd.socket in ./run from running ./tcsd. it appears to run, no errors/messages and no tcsd.socket. tpm_version gives me:

/sdcard/pixel.fix/vendor/bin/tpm # ./tpm_version

WARNING: linker: ./tpm_version: unused DT entry: type 0xf arg 0x463

CANNOT LINK EXECUTABLE: library "libtspi.so.1" not found

so obviously i have some kind of path and/or linking issue i could not resolve.

tpm_nvread gives similar result/outcome:

/sdcard/pixel.fix/vendor/bin/tpm # ./tpm_nvread -i 268435457 -s 20

WARNING: linker: ./tpm_nvread: unused DT entry: type 0xf arg 0x480

CANNOT LINK EXECUTABLE: library "libtspi.so.1" not found
[Pixel C Android Development] dkryder:
i think this fastboot full cap flag might have something to do with it. needs to be set in GBB & VbNvStorage it seems. that is if i'm on a right track.

discovered it in a linked code page from yesterday by doing a find on the error i'm seeing.

https://chromium.googlesource.com/c...hcharge/+/master/src/fastboot/fastboot.c#1441

if (VbVerifyMemoryBootImage(&cparams, &kparams, kernel, kernel_size) !=
VBERROR_SUCCESS) {
/*
* Fail if:
* 1. Device is locked, or
* 2. Device is unlocked, but full fastboot cap is not set in
* GBB and VbNvStorage.
*/
if ((fb_device_unlocked() == 0) ||
((vbnv_read(VBNV_DEV_BOOT_FASTBOOT_FULL_CAP) == 0) &&
(fb_check_gbb_override() == 0))) {
fb_add_string(&cmd->output, "image verification failed",
NULL);
return FB_SUCCESS;
} else {
/*
* If device is unlocked, required full fastboot cap
* flag is set and yet image verification fails, try
* passing the original image to vboot_boot_kernel.
* "fastboot boot" can simply pass a kernel image
* without any signature in unlocked mode with full
* fastboot cap set.
*/
kparams.kernel_buffer = kernel_base;
kparams.kernel_buffer_size = image_size;
}
}
[Pixel C Android Development] phhusson:
Can you give the result of:

mosys nvram vboot read

?
[Pixel C Android Development] cheep5k8:
Hello,

A few words from me since I feel that I have been sharing too littĺe information while trying to achieve the fix:

I have also extensively read the relevant code, have some answers from Pixel C developers on Google Groups, etc.

Yes, the fastboot_full_cap flag is not set in NVRAM. This is why I tried to access the NVRAM via the TPM. Alternatively we could set a flag in GBB as an override, but this is not possible while the hardware write protect is in effect. The HW Write Protect in the Pixel C is behind the Front Camera, to disable it you'll have to take off the display.

Quote Stephen from chromium.org:

I'm not so sure what the best course of action is, but it's awesome that everyone who tries to fix this issue is coming to the same conclusion.

BTW phhusson I had no idea you had ported mosys to Android (or that it even exists in the first place). That could really be it to solving this problem, rather than going through the TPM. How can I install it?
[Pixel C Android Development] phhusson:
Erf sorry, I had it on my chromebook, I stupidly assumed it was on Pixel C.

Though the binary on my chromebook is statically linked, so here it is: http://phhusson.free.fr/mosys
[Pixel C Android Development] cheep5k8:
Doesn't work for me, but I'm trying to compile it for Android right now.

EDIT: "smaug" is actually a supported platform for mosys in chromiumos mosys git!
[Pixel C Android Development] phhusson:
Just thinking: Doesn't building an eng build from AOSP compile those tools?
[Pixel C Android Development] brando56894:
Glad we're getting somewhere one this, my parents and I will be pissed if I (semi) bricked my $600 christmas present only after a week, won't be surprising with the way crap has been going for me this month hahaha

I believe it was termux.
[Pixel C Android Development] cheep5k8:
Eh, we're going to fix this one way or another, it will just take group effort and a little time.

As a last measure, I will flash a stock system image in TWRP, a stock kernel and finally the stock recovery (or use Flashify). Then relock bootloader, then unlock again. That will supposedly reset the full cap flag. But obviously once I start doing that, there is no way back so for the moment let's find maybe a different way.
[Pixel C Android Development] tw1tch175:
Mine actually needs to be RMAd for an unrelated HW defect (The screen is loose from the frame) if you want I can take the leap on this one.
[Pixel C Android Development] cheep5k8:
You mean restoring the firmware from TWRP and then relocking the bootloader? Well if you wanna do it, it would be good to know if that can work, then I'd do it in a heartbeat myself.
[Pixel C Android Development] brando56894:
Awesome!! Thanks for being the Guinea Pig for us. I'll let a few other people try this first to confirm that it works since I've been having really sh!tty luck lately hahaha
[Pixel C Android Development] cheep5k8:
YES BUT I HAVE AN EASIER WAY!!

Google devs just helped us all.

This assumes that root works for you. If not, go to the OP and complete the procedure to get root.

Then download fwtool: fwtool

This tool is meant to run ON ANDROID. That is, boot into Android, and copy it onto /sdcard. Then get a root shell (either through adb or a terminal app), and copy fwtool to "/su/bin", then run "chmod 700 /su/bin/fwtool".

Then, still in the root shell, run exactly this:

fwtool vbnv write dev_boot_fastboot_full_cap 1

That is it. You will now have fastboot access again.

Thanks a lot to Stephen and Furquan from the ChromeOS/Pixel C team!!!
[Pixel C Android Development] tw1tch175:
Did they make any mention of using a standard android boot.img in future updates?
[Pixel C Android Development] cheep5k8:
Nope, and I don't think it's really gonna happen, but we'll see...
[Pixel C Android Development] dkryder:
yeah, worked here. thank you for building the fwtool. went well. and also interfacing with the ones that could help.
[Pixel C Android Development] phhusson:
Nice to hear you finally got a fix, sad to hear it's unlikely to be fixed.

I guess this means someone will have to add a check in TWRP to prevent the device from rebooting if the boot.img is wrong...

Though possibly ChromeOS guys are more likely to accept PR than Android guys, to possibly someone could fix the bootloader.

(this device definitely sounds like a lot of fun, I'm still wondering about the "dev screw" accessibility)

Now, would someone be courageous enough to test my superuser.zip ( http://superuser.phh.me/superuser.zip )? :D I have integrated chromeos signature in it, but I can't test...

Safe process would be to flash it, adb pull the new boot.img, pull recovery.log , restore the previous boot.img, use futility verify command on the host to check, fastboot flash the pull-ed boot.img, and only then try "just the flash"

If it works, [MENTION=4867279]cheep5k8[/MENTION] you might want to try to change ChainFire's supersu.zip based on it
[Pixel C Android Development] gggavin:
how does the kernel brush in？
[Pixel C Android Development] Alxoom33:
Not being updated. Look at [MENTION=5480152]followmsi[/MENTION] thread for latest Pixel C kernels.
[Pixel C Android Development] :
Hi. I was wondering if you have a way of fixing the "remote: unsupported command" only through fastboot. I have this problem and keep coming back to this when I try to find a solution. I have the latest drivers and I have tried unlocking and relocking the bootloader.
[Pixel C Android Development] Alxoom33:
This thread is not being updated.
[Pixel C Android Development] cheep5k8:
Hi,

If your bootloader is locked and "fastboot getvar all" shows that the fw switch is not unlocked then there's no chance to fix this other than undoing the hardware switch, which is the front camera flex (i.e. you would need to disassemble the Pixel)
[Pixel C Android Development] LONGXF:
Does this kernel support Setting GPU Frequency？
[Pixel C Android Development] Alxoom33:
This kernel has not been updated. It's features have been merged into [MENTION=5480152]followmsi[/MENTION]'s kernel a long time ago.
[Pixel C Android Development] LONGXF:
Thanks for your reply.:svetius:
[Pixel C Android Development] cuhead528:
Is there any other way to reset the write state in fastboot besides this ADB shell fwtool?

Mine (and many others) recovery partitions are already broken, seems like we have tons of dead devices.
[Pixel C Android Development] Alxoom33:
Is it that the recovery partition is broke, or simply that we lost TWRP and have stock recovery. I was able to sideload a DU rom that included gapps. However I can't load gapps for LOS. Also, when I wipe, lose all data including internal storage. It would be nice to be able to sideload a TWRP zip installer, like we have for TAIMEN.

If there is a way to flash a recovery img in stock recovery we would be golden!
[Pixel C Android Development] cheep5k8:
phh, I would try it but it's very late and before I attempt messing with the kernel again I really need to have my wits together. I'll try it tomorrow after work.. If you allow, I could make corrections if something should not be fully working and give them back to you. And thanks for the offer of basing SuperSU on it, I'll make the change as soon as we know it works!
[Pixel C Android Development] brando56894:
Thanks!! I believe this is/was/is going to be the device that ChromeOS and Android merge on. It seems to have a lot of the stuff a Chromebook would have (boot image, developer screw, 30 second boot warning, non-android dev tools)....but it runs Android.

[MENTION=1960538]PHH[/MENTION] the dev screw interests me also, but I'm not about to take the screen off of my brand new pixel haha if its anything like the dev switch on my HP pavilion (most likely is), then it pretty much allows open access to the device! You have to enable them on Chromebooks to install Linux and flash the bios on it so that it will boot other payloads other than ChromeOS. This could be a VERY interesting device to us! The question is: who wants to be the first to remove their screen and see what this baby can do? Hahahaha

ChromeOS Developer Mode
[Pixel C Android Development] ZiggSVO:
any quick safe way to make sure fastboot is fixed on your device after running the debug tool?
[Pixel C Android Development] brando56894:
Try and re-flash TWRP :)
[Pixel C Android Development] ZiggSVO:
Works great not sure why I didnt just bother with that lol
[Pixel C Android Development] cheep5k8:
Without flashing something you can run "fastboot getvar all", at the top of the list it should say somewhere "secure: no"
[Pixel C Android Development] oRAirwolf:
Thank you so much for this! Is the SU APK modified in any way? I ask because I own SuperSU Pro and was wondering if it is OK to install it.
[Pixel C Android Development] cheep5k8:
No, it's just the Superuser.apk from SuperSU 2.66 systemless. I think you should be able to install SuperSU pro from the Play Store and it should work (i.e. install the boot image, copy su.img to /data while in TWRP, boot into Android and install SuperSU Pro). Should work.

EDIT: BTW I'm "working" with [MENTION=1915408]phhusson[/MENTION] (I put that in quotes because I didn't get around doing it yet..) to make the installation easier, for both his Superuser as well as SuperSU; the result should be that you can flash the normal SuperSU in TWRP and it works like on any other device. But that is still a bit far off yet (I mean, not months, but it may take a bit to figure it all out)
[Pixel C Android Development] oRAirwolf:
Awesome thanks :D

My god having root is so nice. InversionUI + Adaway = happy Airwolf