yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] cheep5k8:
[MENTION=1610074]beardymcgee[/MENTION]

I was able to restore original performance in v4-RC1. It doesn't seem to be much ahead of the Ars test reference, but is at least, if not slightly better, than the reference test. Now just need to test for stability again.
[Pixel C Android Development] beardymcgee:
cheers, testing now :)

also thanks for the commit logs, Ive been enjoying trying to follow/understand your commits.

Great learning experience
[Pixel C Android Development] cheep5k8:
[MENTION=1610074]beardymcgee[/MENTION]

I think this is of most importance to you, but also everyone else:

I've discoverd a sort of mixed bug: If you switch the governor away from interactive, then back to interactive, the /sys nodes for interactive will get re-created, but owned to root (instead of to system as happens in init.dragon.rc).

The consequence is that the Pixel C's PowerHAL module will not be able to access them properly, and stuff like e.g. boostpulse will not work any longer!

I'm gonna fix that at some point before the v4 release, but until then: watch out! ;)
[Pixel C Android Development] beardymcgee:
Yeah, I'm going to avoid tinkering with gov tweaks for now, don't think its really doing much as it stands
[Pixel C Android Development] Avencore:
I reflashed my pixel with the latest factory image and rerooted it with your kernel and now the reboots when watching youtube seem to be gone [emoji2] . Although now I can see the occasional video breakups mentioned already by others. I guess my pixel used to reboot when those happened earlier. I checked and have min freq set to 204mhz. I'm on version 3RC4.

Gesendet von meinem SM-G928F mit Tapatalk
[Pixel C Android Development] JoeDat:
Randomized Wifi MAC address

First, really nice work on this kernel. Those wifi issues were painful, and they're virtually non-existent with this kernel. Helluva job!

Having a weird issue tho. It appears that my Wifi MAC address is changing on each reboot. The last 3 octets are different on each start up. I only know this because I use MAC filtering.
[Pixel C Android Development] cheep5k8:
Hey, first, thanks for the feedback! I'm gonna take a look. I presume that I left some debugging option enabled in the WiFi driver, I'll try to locate it and disable it (for v6.2-RELEASE, v6.1-RELEASE just got ready before I had the chance).

EDIT: I sort of noticed this too: it would explain why my access point assigns the Pixel C a different IP address at each boot when I have it configured not to do so. Makes sense now!
[Pixel C Android Development] wangsiyu:
Which is the branch of MXB48T stock/rooted kernel on https://github.com/md5555/android_kernel_google_dragon?
[Pixel C Android Development] cheep5k8:
The stock/rooted image is not based on any branch; it is just the stock kernel image with a modified ramdisk.
[Pixel C Android Development] wangsiyu:
Is the branch "chromeos-3.18" stock source code？
[Pixel C Android Development] cheep5k8:
Wangsiyu, not neccessarily. You can probably build chromeos-3.18 and run it on the Pixel C, but the stock kernels are built from individual release tags (e.g. "MXB48T"), at least, from my experience, more or less.
[Pixel C Android Development] JoeDat:
So, after nearly a day of usage, just wanted to provide an update on my wifi experience.

The improvement is highly remarkable. I'm consistently showing higher signal strength on both my 2.4ghz and 5ghz networks (using Elixir 2). And, consequently, I'm experiencing a higher transfer rate (down and up).

I am still occasionally dropping connectivity. But, the circumstances are interesting. According to the Wifi monitor in Elixir, the strength of the signal is typically between 50% - 60%, then suddenly drops to 0%. This is different than my experience on the stock kernel, where it would be more of a gradual strength drop to 0% This makes me wonder if there is possibly an OS/ROM software dependency that also may need to be tweaked as well.

I'm not a developer, so I could be completely off-base on the ROM comment. :)
[Pixel C Android Development] cheep5k8:
I'll look into it. BTW the kernel also fixes less visible issues like massive amounts of out of order IP packets that occur in the stock kernel. But anyway, thanks for the report. I'm not yet done with fixing the WiFi, we'll get the last issues fixed as well :)
[Pixel C Android Development] Avencore:
I'm happy to tell you that on v6.1 also the video stutters are gone. Thanks a lot for the great work. Very much apppreciated.

Gesendet von meinem SM-G928F mit Tapatalk
[Pixel C Android Development] Boal:
Does anyone else get pretty high battery drain in the form of "Miscellaneous" taking the top spot in the battery consumption list? I had this for a short while now, but I'm not sure when it started. No idea if it's related to the kernel, but I thought I'd ask. Right now I'm at 19% remaining battery and the top consumer is Miscellaneous with 32% ahead of the display with 25%.
[Pixel C Android Development] sniperfox47:
I just double checked all my devices and it's showing up this way on them too. I don't think it's a kernel thing, if anything it seems to be a mashmallow thing from where I sit. Curious what makes up that Misc. section.
[Pixel C Android Development] Boal:
That's odd. My Nexus 5 with MM does not have this issue. So, does that mean no one else except the two of us has observed this? In that case I may try the stock kernel again for a while to see if it changes anything.
[Pixel C Android Development] bill3508:
Ive seen this issue on the Nexus 6 and 6p, not mine personally but folks on the Aosip were complaining about it. It seems random also.
[Pixel C Android Development] cheep5k8:
This should be gone on the 6.x kernels, at least I haven't observed it again. I restarted from scratch and proceeded more sensibly regarding modifications. However, I'm not 100% sure this is an issue with the kernel, but like I said I haven't observed it with the restart 6.x kernels.
[Pixel C Android Development] Boal:
Ok then, thank you for the response. Then I guess I will try dragon-boot-encryptable-rooted-MXB48T-02102016-1.img for a while and see if that changes anything. That is the latest 'stock' version, right?
[Pixel C Android Development] cheep5k8:
Yep, correct.
[Pixel C Android Development] r_nation:
I apologize in advance, is there a workaround for the keyboard not updating?
[Pixel C Android Development] cheep5k8:
I don't have the keyboard, didn't notice my kernel breaks something with the keyboard.

Can someone confirm this? Guess I'll have to bite the dust and buy that damn bloody keyboard... :confused:
[Pixel C Android Development] cheep5k8:
These are my battery stats after 1.5 days off the charger on xceed 6.7-RELEASE; no "Miscellaneous" :D

Battery life is quite good actually, 1.5 days standby with 2+ hours of screen time. Anyone has a comparison with stock with similar usage? ;)
[Pixel C Android Development] r_nation:
I rooted my c straight out of the box and this notification has been persistent since. Today I ran home on my lunch to flash 6.7 and right before going into fastboot all my "google" apps starting updating(maps,gmail,drive,etc then keyboard) but was up automatic update not the notification one so was thinking it would finally be fixed. Flashed 6.7 and unfortunately notification came back..
[Pixel C Android Development] cheep5k8:
Which notification?
[Pixel C Android Development] r_nation:
keyboard firmware app in the notification saying there is an update for the keyboard..after choosing to install the update it just keeps coming back. Thought I just fixed it through tinkering with the update permissions but it came back.

---------- Post added at 10:46 PM ---------- Previous post was at 10:31 PM ----------

Just wasn't for sure if it was something I'm personally not doing right, I'm not blaming your kernels whatsoever. Btw all your kernels have gave me amazing battery life looking forward to testing 6.7
[Pixel C Android Development] beardymcgee:
Didn't have an issue when your initial mods for T, but could have changed since?
[Pixel C Android Development] amigo80:
The keyboard is working fine with your kernel, also did a the keyboard update with your kernel no problems for me. So far no reboots and I have ok wifi, not as good as my nexus 6p, but alot better then when I got it.

Thx alot for all your hard work
[Pixel C Android Development] cheep5k8:
Also no reboots on 6.x, which I'm quite happy about because that was a real mess.
[Pixel C Android Development] acrickie:
My keyboard updated fine as well and has been much better since the update. If I remember correctly, I rooted, updated to the T release and updated to this kernel all at the same time with no issues.

Also I don't have any "Miscellaneous", in my battery stats either.
[Pixel C Android Development] cheep5k8:
Look... This isn't really about blame. We just need to be sure that it is in fact my kernel that causes the issues you experience, so I've asked for confirmation. So far there's at least one reply where the poster said there are no issues with the keyboard with xceed so you'd need to be more specific or make a partial diagnosis of the issue yourself since I myself don't have they keyboard and it seems to be fine for others. :cool:
[Pixel C Android Development] Boal:
Hm, I gave 6.7 one last try, but I'm already at 7% misc with battery at about 75%. Let's see now if something changes with stock. If not, I may have to look elsewhere. One thing I can already say about stock is that it supports bandwidth monitoring again, which 6.7 unfortunately does not (i.e. this would always show 0, no matter what).
[Pixel C Android Development] beardymcgee:
[MENTION=4867279]cheep5k8[/MENTION]

Can I tinker with governor again? :D

Or does powerHAL still get messed up on change?
[Pixel C Android Development] cheep5k8:
[MENTION=1610074]beardymcgee[/MENTION] :

The problem is that if you change the governor away from interactive (or have an app like Kernel Adiutor set it at boot, even if it sets it to interactive) then all the /sys nodes for cpufreq/interactive will get re-created, but with the wrong permissions so stuff like boostpulse isn't working then anymore.

Well I think I've already explained it once, no need to explain again, sorry ;)

But in any case it's not fixed in any way, it will require fixes in multiple places. So you can tweak interactive, just make sure you don't change the governor at all. I will eventually get around to fix this, but not yet.
[Pixel C Android Development] cheep5k8:
I hope I can eventually fix the bandwidth data access; there is probably something missing or disabled in the WiFi driver. I'll keep it in mind the next time I get to it.
[Pixel C Android Development] cheep5k8:
No, wait. I think I've disabled a handful of networking configs in the kernel which I thought to be useless, and must have disabled something relevant for traffic monitoring. That, and maybe something in the WiFi too. I'll keep an eye open.
[Pixel C Android Development] r_nation:
Ok so I just finally got it to update thank god. I apologize for the post, and appreciate the feedback!
[Pixel C Android Development] beardymcgee:
So just to confirm if I make only make Governor tweaks to interactive without changing governor type I'm good?

sorry misread that the first time, all good. back to tinkering for me
[Pixel C Android Development] cheep5k8:
OK, I'm gonna relock my bootloader and then try to unlock again, don't see many other options.
[Pixel C Android Development] tw1tch175:
Tried that too, it unlocks fine but doesn't change anything.
[Pixel C Android Development] cheep5k8:
OK, that's unexpected. It's very late now where I live, but I'll start looking into it in depth tomorrow, also from the perspective that the Pixel C is actually a ChromeOS device.

Don't worry we'll get this resolved.

On a positive side note I found a temporary fix for the crashing and reboot problem:

- mount /vendor read-write ("mount -o remount,rw /vendor")

- make a backup of the file /vendor/lib64/hw/keystore.dragon.so

- once you placed that backup somewhere safe, remove that file (it's essentially a driver that talks to the TLK imp!ementation)

- "mount -o remount,ro /vendor"

- reboot

Android will then fall back to its own key storage which seems to work fine.
[Pixel C Android Development] cheep5k8:
I've posted a request to the ChromiumOS discussion group, but we'll probably only hear back from there on Monday. I'll look into it thoroughly tomorrow; my Pixel is now semi-locked as well...
[Pixel C Android Development] tw1tch175:
Soft brick is supposed to be fastboot without system access, this is backwards....
[Pixel C Android Development] dkryder:
are you using the j or k build? when i updated to k build the bootloader became Google_Smaug.7132.260.0 if you can still boot system do a reset if you can from settings.
[Pixel C Android Development] cheep5k8:
But won't this just tell the recovery to format /data?
[Pixel C Android Development] cheep5k8:
I've read the board's fastboot code and it seems that while the bootloader is unlocked, flashing an image is disabled through a flag in the nvram. This is not exactly good news but I'm looking now into accessing the nvram.

EDIT: We have to go through the TPM (Trusted Platform Module). Good news ist that it's supported by the Android Linux Kernel of the Pixel C, and accessible, but we need specialized tools to do that, which I'm trying to build right now.
[Pixel C Android Development] dkryder:
i was under impression it would replace modified boot with stock one also but i could be wrong.
[Pixel C Android Development] cheep5k8:
For whatever reason flashing SuperSU tripped the underlying (parts of) ChromeOS of the Pixel C's security measures and disabled flashing through a flag in the nvram. We need to reset that flag going through the TPM.

Really nothing else short of maybe a ChromeOS factory image install, going through the USB recovery, will fix this issue.
[Pixel C Android Development] dkryder:
perhaps reach out to chainfire to see if 1] this is the case 2] if he thinks it can be reversed?
[Pixel C Android Development] cheep5k8:
The security tripping was unexpected. I flashed many boot images, I even had the Coreboot bootloader tell me that "The OS is damaged...", but I was still able to flash.

Somehow flashing SuperSU did this, but I don't think that SuperSU specifically had something to do with it, and I'm not sure that Chainfire will be able (or willing/have the time) to help out with this.

I'm rather hoping on some help from the ChromiumOS team at Google, perhaps even someone from the Pixel C team directly.

But either way, so far I know what I'm doing: we need to access the TPM and see if we can reverse the flag from within Android. I'm not saying that I know that it's possible, but it can very well be (i.e. so far I see no reason for it not to be).

Once we figure that out and in case we find out it won't work we will really need help from the original Pixel C team; but let's take it a step at a time! ;)
[Pixel C Android Development] tw1tch175:
Good thing I got the 64GB model since it looks like I might not be uninstalling apps for a while
[Pixel C Android Development] superchilpil:
I've noticed this device has multiple partitions. Ex. System, System A, System B.

Maybe supersu wrote to the wrong partition and set something off?

(bootloader) version: 0.3
(bootloader) version-bootloader: Google_Smaug.7132.260.0
(bootloader) version-baseband: N/A
(bootloader) product: dragon
(bootloader) secure: no
(bootloader) max-download-size: 0x10000000
(bootloader) partition-type:boot: ext4
(bootloader) partition-type:kernel-a: ext4
(bootloader) partition-type:kernel-b: ext4
(bootloader) partition-type:recovery: ext4
(bootloader) partition-type:kernel: ext4
(bootloader) partition-type:system: ext4
(bootloader) partition-type:system-a: ext4
(bootloader) partition-type:vendor: ext4
(bootloader) partition-type:vendor-a: ext4
(bootloader) partition-type:cache: ext4
(bootloader) partition-type:data: ext4
(bootloader) partition-type:userdata: ext4
(bootloader) partition-type:metadata: ext4
(bootloader) partition-type:lnx: ext4
(bootloader) partition-type:misc: ext4
(bootloader) partition-type:persistent: ext4
(bootloader) partition-type:system-b: ext4
(bootloader) partition-type:vendor-b: ext4
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-size:kernel-a: 0x2000000
(bootloader) partition-size:kernel-b: 0x2000000
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-size:kernel: 0x2000000
(bootloader) partition-size:system: 0xe0000000
(bootloader) partition-size:system-a: 0xe0000000
(bootloader) partition-size:vendor: 0x13000000
(bootloader) partition-size:vendor-a: 0x13000000
(bootloader) partition-size:cache: 0x19000000
(bootloader) partition-size:data: 0x62ef00000
(bootloader) partition-size:userdata: 0x62ef00000
(bootloader) partition-size:metadata: 0x4000000
(bootloader) partition-size:lnx: 0x2000000
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-size:persistent: 0x80000
(bootloader) partition-size:chromeos: 0x747c00000
(bootloader) partition-size:mbr: 0x200
(bootloader) partition-size:gpt: 0x4200
(bootloader) partition-size:RO_SECTION: 0x3f0000
(bootloader) partition-size:RO_VPD: 0x10000
(bootloader) partition-size:RW_SECTION_A: 0x580000
(bootloader) partition-size:RW_SECTION_B: 0x580000
(bootloader) partition-size:bootloader: 0x1000000
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) battery-voltage: 4294 mV
(bootloader) variant:
(bootloader) battery-soc-ok: yes
(bootloader) Bdev-size:mmc: 31268536320
(bootloader) Bdev-size:flash: 16777216
(bootloader) Gbb-flags: 0x0
(bootloader) Oem-version:RO: Google_Smaug.7132.226.0
(bootloader) Oem-version:RW_A: Google_Smaug.7132.260.0
(bootloader) Oem-version:RW_B: Google_Smaug.7132.260.0
all: Done!
finished. total time: 0.532s
[Pixel C Android Development] tw1tch175:
For the curious here's the getvar for "bricked" device

(bootloader) version: 0.3
(bootloader) version-bootloader: Google_Smaug.7132.239
(bootloader) version-baseband: N/A
(bootloader) product: dragon
(bootloader) secure: yes
(bootloader) max-download-size: 0x10000000
(bootloader) partition-type:boot: ext4
(bootloader) partition-type:kernel-a: ext4
(bootloader) partition-type:kernel-b: ext4
(bootloader) partition-type:recovery: ext4
(bootloader) partition-type:kernel: ext4
(bootloader) partition-type:system: ext4
(bootloader) partition-type:system-a: ext4
(bootloader) partition-type:vendor: ext4
(bootloader) partition-type:vendor-a: ext4
(bootloader) partition-type:cache: ext4
(bootloader) partition-type:data: ext4
(bootloader) partition-type:userdata: ext4
(bootloader) partition-type:metadata: ext4
(bootloader) partition-type:lnx: ext4
(bootloader) partition-type:misc: ext4
(bootloader) partition-type:persistent: ext4
(bootloader) partition-type:system-b: ext4
(bootloader) partition-type:vendor-b: ext4
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-size:kernel-a: 0x2000000
(bootloader) partition-size:kernel-b: 0x2000000
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-size:kernel: 0x2000000
(bootloader) partition-size:system: 0xe0000000
(bootloader) partition-size:system-a: 0xe0000000
(bootloader) partition-size:vendor: 0x13000000
(bootloader) partition-size:vendor-a: 0x13000000
(bootloader) partition-size:cache: 0x19000000
(bootloader) partition-size:data: 0xd76b00000
(bootloader) partition-size:userdata: 0xd76b00000
(bootloader) partition-size:metadata: 0x4000000
(bootloader) partition-size:lnx: 0x2000000
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-size:persistent: 0x80000
(bootloader) partition-size:chromeos: 0xe8f800000
(bootloader) partition-size:mbr: 0x200
(bootloader) partition-size:gpt: 0x4200
(bootloader) partition-size:RO_SECTION: 0x3f0000
(bootloader) partition-size:RO_VPD: 0x10000
(bootloader) partition-size:RW_SECTION_A: 0x580000
(bootloader) partition-size:RW_SECTION_B: 0x580000
(bootloader) partition-size:bootloader: 0x1000000
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) battery-voltage: 4203 mV
(bootloader) variant:
(bootloader) battery-soc-ok: yes
(bootloader) Bdev-size:mmc: 62537072640
(bootloader) Bdev-size:flash: 16777216
(bootloader) Gbb-flags: 0x0
(bootloader) Oem-version:RO: Google_Smaug.7132.226.0
(bootloader) Oem-version:RW_A: Google_Smaug.7132.239.0
(bootloader) Oem-version:RW_B: Google_Smaug.7132.260.0
[Pixel C Android Development] cheep5k8:
In some post above I posted a method how to modify /vendor (backup, then remove one file) which you can do from within Android and some Terminal app (e.g. Material Terminal), that fixes the Security settings crash as well as uninstalling apps, etc.

As for the current status: Building all these tools for controlling the TPM for Android is a bit challenging (I don't think this has been done by too many people before...) but I'm getting there!
[Pixel C Android Development] cheep5k8:
This is a ChromeOS thing, especially the RO, RW_A and RW_B thing.. I can post a link to an explanation on the ChromiumOS site later if someone is curious.
[Pixel C Android Development] dkryder:
yeah, i'd appreciate the link. do you think the variations in bootloader versions has anything to do with the issues? also, could variations , if any, in the fastboot package used be connected?
[Pixel C Android Development] phhusson:
I'm quite surprised of your problems. It looks like you are using an unsigned boot.img, but it is indeed signed.

Just in case, you properly signed, or you just took the header of the file from original boot.img?

If the later, it might be quite the same issue as https://code.google.com/p/chromium/issues/detail?id=572783

What commands did you use to sign? I assume the one in Android 6.0 build system?
[Pixel C Android Development] cheep5k8:
Yes, it is properly signed, it only has a modified ramdisk. Yeah it's built in an Android 6.0 tree.
[Pixel C Android Development] cheep5k8:
The problem is that for example in Kernel Adiutor, if you set custom values for interactive and enable to set them at boot, it will also forcibly re-set the governor at boot, effectively disabling touchboost, etc. So there's no good solution atm.
[Pixel C Android Development] beardymcgee:
Thought that might be the case, no tinkers for me then....

6.9 stable so far as well
[Pixel C Android Development] followmsi:
Confirmed ?

Thanks for all you work !
[Pixel C Android Development] Boal:
Alright, I still have misc battery usage on the stock kernel. I guess that excludes this kernel as a possible reason, good to know.