yashsingh1/xdaforums huggingface dataset:
[Pixel C Q&A, Help & Troubleshooting] degraaff:
I believe the delayed response is due to the keyboard going into a power saving state after a certain period of inactivity. It usually takes around 3 or 4 seconds for the keyboard to "wake up" and respond to my key input. It's indeed rather annoying...
[Pixel C Q&A, Help & Troubleshooting] shadowx360:
Hey guys, any update here? Noticed that mine lags particularly bad when battery drops below 40%. Battery drain is real bad, and the tablet is often warm after leaving it idling all day.
[Pixel C Q&A, Help & Troubleshooting] gburns53:
Mine too

I've had problems with my Tablet since 8.1 (I think) I only use it moderately bedside so it could have been 8.

It's just slow. Try sliding the home screen and animations stick. Everything is slow. Apps load like this is a cheap 5 year old phone. I did do a factory reset but did nothing since it updated to 8.1 still. Think rolling it back is only way, and that's not fun as I understand I have to hook it up to a PC with some software.
[Pixel C Q&A, Help & Troubleshooting] elitistphoenix:
Same happening here. Don't even chrome enabled.
[Pixel C Q&A, Help & Troubleshooting] nean.0:
I had the same problem. Suddenly, but not really directly related to the Android 8 upgrade, the tablet became very very slow. There was indeed some correlation to the battery charge (as reported elsewhere). Eventually I also ended up with the Invalid Pattern Death (productforums.google.com/forum/#!topic/Nexus/ImQsmQ8-8JA).

So I decided to downgrade to Android 7 (mmikowski.github.io/pixelc-revert-nougat/).

This was three weeks ago. So far the tablet is as good as it was before the problems began. Not sluggish anymore, not sensitive to battery charge. Hopefully it will last.

I actually did a similar reversal on my old Nexus 10 (downgraded to Android 5) and was able to make it usable again. I guess this is the same old problem as we have experienced for years with Windows machines just getting slower and slower with each update. The hardware is only able to cope with updates for a couple of years, after that the newer code updates exceed the capabilities of the old processor.
[Pixel C Q&A, Help & Troubleshooting] ShinOrochiX:
Mine is running completely fine although I bought it running Android 8.1 out of the box, I have not experienced any lags nor the pin problem. The keyboard is also fine, like the other guy said it goes into power saving mode after a while which requires some time to start back up again but only takes a few seconds.

I am quite pleased with my tablet considering that I got it for a good price and it was second-hand. Mind you I'm a light user I don't do many heavy tasks.
[Pixel C Q&A, Help & Troubleshooting] BMP1244:
Excellent, thanks for the share. I just installed the March update for mine, seems to be running great still. I've been lucky enough not to have the issues a lot of people have been seeing with theirs. Hoping it stays that way. Lol. Well definitely be doing this once performance takes a hit or Google stops sending monthlys for it.
[Pixel C Q&A, Help & Troubleshooting] CityC:
I found out why (at least mine) Pixel C gets laggy. Turns out that closer to 20-25% of the battery remaining, the voltage from the battery gets to 3.8 Volts. However when the battery is full the output voltage gets to 4.22 Volts. That's very strange since the battery is designed to output 3.8 volts... Also, I've found out that if you use a non-pixel c charger, the battery doesn't charge properly. It charges very very slow and the voltage stays at 3.8 volts even when the battery is 100% charged. In my case, I was using a Oneplus 6 charger which outputs 3 amps, and the Pixel C would take a whole night to charge. Yesterday I used the Pixel C charger and the battery charged properly, and now at 100% it outputs again the needed 4.2 volts. Hope that helps.
[Pixel C Q&A, Help & Troubleshooting] MrKaage:
Hello,

I have the same problem with my Pixel C.

Does pixel C run stablely with LineageOS 16 and the new kernel even after a long time?

In addition, I am relatively new to Custom Rome. Could you send me the links to the kernel and the ROM?

Do I have to pay attention to anything else?
[Pixel C Q&A, Help & Troubleshooting] Ulunyth:
Hi,

Thank you for this tip !

I did the same, but with the latest Lineage 17.1 (Android 10). Here are the links :

1 - TWRP : https://dl.twrp.me/dragon/twrp-3.3.1-0-dragon.img.html

2 - Lineage : https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg ("lineage-17.1-20200113-UNOFFICIAL-dragon.zip")

3 - OpenGApps : https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm64/

4 - Kernel : https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn ("tegra-3.18_kernel_10_dragon_v191220_unicorn-xceed-followmsi.zip")

Enjoy !
[Pixel C Q&A, Help & Troubleshooting] geekdaddy:
Running lineage 15.1 with microg and had this problem. Flashed the unified oreo kernel and problem solved!
[Pixel C Q&A, Help & Troubleshooting] googlemakesbrokenjunk:
My Pixel C has suddenly become afflicted with the "My cores are all locked at 204MHz" issue. For me it starts when the battery reaches around 70% charge and it's so crippling.

I read the advice here but was too wimpy to go with a higher ROM than 8.1 and decided first to try downgrading to Android 7.1.

One thing I found really difficult was getting fastboot to work because "fastboot devices" wasn't showing any devices. Somewhere on the internet I discovered that when your device is in fastboot mode, it actually has DIFFERENT hardware identifiers than when it is in normal mode.

The android_winusb.inf in the official google distribution and also the "15 second" distribution also doesn't contain any hardware identifiers for my device so I had to add them manually before Windows 10 could detect and install the drivers for fastboot *sigh*

I also discovered that when trying to use "fastboot flash" the operation always failed. I found (on the internet again) that before you can flash you need to "fastboot oem unlock" before it will succeed.

Finally I couldn't manage to get the 7.1 ROM to load because of some other nonsense where the latest fastboot has some new feature that prevents it (ARGHHHHH). After more searching I found that I had to download an older platform tools (v27) and using that... FINALLY I managed to write the 7.1 ROM to the device.

It has been a long ad very tiring road but now hopefully my Pixel C will perform how it is supposed to. I've posted mostly because I couldn't find this kind of troubleshooting information (in one place) anywhere myself and hopefully it might save some other Pixel C owners the frustrations I encountered :)
[Pixel C Q&A, Help & Troubleshooting] Ultraman1966:
This solved everything that I wanted to fix, I was so annoyed that wipes and different ROMs couldn't make a difference. Thanks!
[Pixel C Q&A, Help & Troubleshooting] robertocarlus:
Following this with the various listed files in their latest version. Working well, just have the odd now and then reboot. All else is good.
[Pixel C Q&A, Help & Troubleshooting] Everio9000:
I own the Pixel C since launch day in 2015. It was smooth and fast first years but after this years it becomes laggy and slow.

I tried some Custom ROMs and else but nothing changed. Finally I read this thread and follow flash Lineage 17 and Tegra 3.18 Kernel and it seems back to the speed and smooth of first years.

I'm very happy now : )
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
Seeing the different people having issues installing magisk and passing safetynet running Oreo trying to do it using TWRP, I've decided to post this guide to help simplify the process for some and allow magisk to install and pass safetynet successfully.

Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.

Original credits and thanks go out to topjohnwu and his original guide found at: https://xdaforums.com/honor-view-10/development/magisk-root-honor-view-10-mate-10-pro-t3749280

Prerequirements

Must be running Andriod Oreo

Unlocked Bootloader

Copy of your Update.app

Huawei Update Extractor (download in attachments) to extract and get your ramdisk.img

Instructions

***Recommed to use via fastboot method...

If your device does have TWRP support with decryption, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:

Install latest Magisk Manager from the Official Thread: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.

If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments

If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.

Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:

fastboot flash ramdisk patched_boot.img

Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
Reserved
[Huawei Mate 9 Guides, News, & Discussion] Addymore:
This method is working good.... Have been using it since.....!
[Huawei Mate 9 Guides, News, & Discussion] toto2011:
Thanks a lot Man! It works! After of so many tries!
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
Glad it helped you out and worked.
[Huawei Mate 9 Guides, News, & Discussion] Cavi_:
Great guide, thank you! Worked like a charm. The stock ramdisk.img for L29C567B360 is attached.
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
Great to hear that. Thanks for posting that. I will add it to the OP.
[Huawei Mate 9 Guides, News, & Discussion] toto2011:
Why modules didnt appear in my magisk modules?
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
Hmm, that's a strange one. Can you go to settings in magisk and post some screen shots?
[Huawei Mate 9 Guides, News, & Discussion] toto2011:
Yeah! So strange!
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
There is the problem... Uncheck the box beside Magisk Core Only Mode. Should solve the issue.
[Huawei Mate 9 Guides, News, & Discussion] toto2011:
Thanks a lot man:) It works
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
No problem. Yep, I installed that module too. Only if viper worked. Lol
[Huawei Mate 9 Guides, News, & Discussion] toto2011:
I flashed the p20 pro cmera module but after rebooting nothing change in the cmera setting...
[Huawei Mate 9 Guides, News, & Discussion] Wirmpolter:
Yeah, I did not notice any changes either with mine so not sure if there is something we missed then. Maybe we have to remove the camera app first before installing it. I don't know for sure
[Huawei Mate 9 Guides, News, & Discussion] toto2011:
the one posted at ******.com he got like these
[Huawei Mate 9 Guides, News, & Discussion] rogconnect:
How could get the stock ramdisk.img for L29C567B367?

Thanks
[Huawei Mate 9 Guides, News, & Discussion] wancyber:
-Download your firmwares update.zip from http://pro-teammt.ru/firmware-database/

-Search for your firmware, example used below : MHA-L29C567B367.

-Click on the "filelist" next to your firmware, copy and paste the full links in new tabs to download 'update.zip'.

-Then extract update.app from update.zip. Download and Open Huawei Update Extractor, go to settings tab and disable both checksum.

-Open update.app in Huawei update extractor and extract ramdisk.img.
[Huawei Mate 9 Guides, News, & Discussion] R1SC:
where do i get Huawei update extractor?

---------- Post added at 09:57 AM ---------- Previous post was at 09:51 AM ----------

i see the download link here, its fir Microsoft Windows. what do i use on Linux?
[Huawei Mate 9 Guides, News, & Discussion] rogconnect:
Attached RAMDISK.img for MHA-L29C567B366.

https://mega.nz/#!Pfw1SLRT!-0YL-YkJb6uwsaWxMETgRAhEPtaLDv5EJ4RxtjyvV9o
[Huawei Mate 9 Guides, News, & Discussion] wancyber:
You can try this if you want.

https://xdaforums.com/mediapad-x2/development/tool-huawei-update-extractor-linux-perl-t3318880

Sorry for the late reply.

Btw, [MENTION=3331309]rogconnect[/MENTION] already provide ramdisk.img link for your mha-l29c567b367.

Thank him, not me. :)
[Huawei Mate 9 Guides, News, & Discussion] shane7691:
Is magisk 16 working fine in mate 9? And are magisk modules working?
[Huawei Mate 9 Guides, News, & Discussion] wancyber:
It's working fine with my mate 9. I'm using google dns, ar-lens enabler, busybox module. Unfortunately, p20 pro camera doesn't work for mate 9 (provide by ante0).

As far as i know, xposed module doesn't work yet for oreo mate 9. Already been discuss in this thread by LastStandingDroid.

https://xdaforums.com/mate-9/how-to/guild-mate-9-magisk-t3666540/page18

:)

*Update: in next build, i'm gonna try Face Unlock Module by Ante0. Mine is c636b362.
[Huawei Mate 9 Guides, News, & Discussion] shane7691:
Do update to us wen u try face unlock. Thanks
[Huawei Mate 9 Guides, News, & Discussion] wancyber:
I will, but maybe i'm gonna wait for a bit.

As i saw an update for c636, b371 which will include face unlock feature. :)
[Huawei Mate 9 Guides, News, & Discussion] sghens:
this method works for Emui, or only for aosp? Thanks in advance
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
This is the method I've used on AOSP and CarbonROM. I've not tried it on EMUI yet (don't see myself switching back any time soon, either), but I would guess that it would work without issues there, too.

Of course, if it doesn't, all you need to do is flash back over the stock ramdisk.img and all traces of Magisk should go away.
[Huawei Mate 9 Guides, News, & Discussion] wancyber:
I'm not sure with AOSP, but it should work with EMUI.

*btw, [MENTION=5066134]irony_delerium[/MENTION] said it works.

If you want to use twrp or alternativr way, you can try this:

https://xdaforums.com/mate-9/how-to/guild-mate-9-magisk-t3666540/post75751294#post75751294

:)
[Huawei Mate 9 Guides, News, & Discussion] sghens:
What module of lens work?

Works fine on Emui 8 thanks
[Huawei Mate 9 Guides, News, & Discussion] wancyber:
Did you mean which module i use for camera?

It's ar-lens. You can get it from here.

In the same thread with face unlock module.

It's very girly though. Haha

https://xdaforums.com/mate-9/development/port-unlock-mate-9-oreo-emui8-t3751640/post75808579

***update :

P20 pro camera module did work for some mate 9.

But not mine. It works for ante0.

Welcome. :)
[Huawei Mate 9 Guides, News, & Discussion] sghens:
I did not know her, thanks it works perfect in the 368(c432)

Although in reality my question was about Google lens Thank you
[Huawei Mate 9 Guides, News, & Discussion] daina:
Stupid question time...

I have Magisk installed, and root seems to work just fine (I have Ad-Away installed, yay!), but SafetyNet is not passing, boo!

Currently running latest phhusson RROS treble build (Weirdly, not sure NFC is working, either, come to think of it).

I need SafetyNet, for Google Pay and Snapchat, and whoever else decides SafetyNet is a good security blanket for their app. (Why, Snapchat, why?) The research I've done suggests that my Magisk implementation is broken, somehow. This doesn't surprise me, as I had a non-booting phone for most of Friday, until I wiped data.

I'm thinking I should:

a. Uninstall Magisk (I can do this from within Magisk, right?)

b. Factory reset, Wiping data in TWRP.

c. Immediately re-install/re-flash Magisk, so it can properly "seat" itself.

d. flash update_data_full_public.zip

update_full_MHA-L29_hw_usa.zip

e. reboot to bootloader and flash patched ramdisk (or I've had luck just flashing it in TWRP)

f. reboot

Will this work? Am I missing a reboot somewhere? Do those two files (update_data_full_public.zip and update_full_MHA-L29_hw_usa.zip) somehow complete my phone so that SafetyNet doesn't trip over something?

Thank you in advance. If I can get SafetyNet working, everything else is gravy. Thought I was going to stick with EMUI for the long-haul, but the ads drive me crazy, and nothing works as well as rooted AdAway (and I've tried them all-blokada, block-this!, and even the VPN I pay for, PIA)...
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
Is Magisk hide enabled? I know I've had that come up when I flash Magisk via twrp and then install Magisk Manager.
[Huawei Mate 9 Guides, News, & Discussion] daina:
Yep, and everything Google-related, as well. Even cleared all Google app/account data, necessitating WearOS reset (I have a Zenwatch 2), which also, weirdly, now will not sync with my main account (but that's another problem).

I'm thinking about a complete re-flash of the entire RROS, especially since RROS isn't showing NFC at all.

Maybe I'll start with the Lineage OS GSI, reboot, and then try re-flashing the RROS GSI again.
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
Yeah, I've passed (given up) on most of the GSI builds - I haven't gotten a SafetyNet pass out of any of them. I'm running the previous build of CarbonROM for the View 10 on my Mate 9, which is doing fine, I was running an AOSP 8.1 for Honor 8 Pro, which also did fine.
[Huawei Mate 9 Guides, News, & Discussion] daina:
Thanks, I'll try one of these. I have experience with CarbonROM, way back in the days of my OPO. As I recall, it was an excellent, no-nonsense, smooth little ROM... I love RROS (again, so much experience with it on my OPO), but I need to pass SafetyNet...

Cross your fingers for me.
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
If you go with Carbon, the April build (systemCarbon_...img) works, the most recent one (twrp flashable zip) gave me fits passing SafetyNet, and USB didn't work when Magisk was installed, so I rolled back. Just FYI.
[Huawei Mate 9 Guides, News, & Discussion] daina:
Here's a new one for you...

Decided to try and go back to stock, after Carbon flashing didn't go well.

Stock came up perfectly, until I decided to try and relock my bootloader.

Now, phone won't reboot, bootloader is locked, so is FRP. Keeps rebooting to erecovery, even though the very first thing I did after relocking was factory reset there.

Any ideas? Can't flash in fastboot, since bootloader is locked. erecovery not working...

Very sad.

Thanks again -have searched, with no success...
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
Dload?

Hisuite might be able to do something. (Don't count on it, though.)

Erecovery never seems to work for me, though it might work via FH.

And there's always the DC-Phoenix route. (Had to do this on Saturday after getting one of my phones in a state where fastboot came up, but I was stuck on a black screen.)
[Huawei Mate 9 Guides, News, & Discussion] daina:
Yeah, DC-Phoenix didn't work out so well. Ended up hard-bricking my Mate 9. Trying to find a local repair shop that'll do this: https://xdaforums.com/mate-9/help/solution-19-00-fix-hardbricked-huawei-t3750315 since I certainly can't (I'm not a hardware person).

DC-Phoenix' software instructions leave much to be desired (says this Technical Writer).

Thanks for your help.
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
They do leave a lot to be desired.

I'm not the biggest hardware person, either, but actually following the instructions in the linked post isn't too difficult. The biggest thing is getting the case open and hitting those test points: he uses wire, but I think a pair of really pointy tweezers works better.
[Huawei Mate 9 Guides, News, & Discussion] steven360:
Honor 7x BND-L24 Ramdisk

Hello you can add this to the original post if you want:

https://drive.google.com/drive/folders/1Pr9BF9srAsjzrR5tGKQewsiPh8J9y6Kh?usp=sharing
[Huawei Mate 9 Guides, News, & Discussion] daina:
All right, so my Mate 9 is back up and running, Stock EMUI (B369), thanks to [MENTION=5515724]hack4ever[/MENTION] and [MENTION=5066134]irony_delerium[/MENTION]. I might have a silly question.

When downloading from http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29&firmware_page=0, I think I chose this file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v136241/f1/full/update.zip, which is the Full OTA-MF. Is that the file I want to extract from? I just want to make absolutely sure, because I can't brick this again. My wife will kill me.

Weirdly, I think installing Magisk will be easier than trying to relock the bootloader. Gotta have my Android(Google) Pay!
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
Assuming that's the one that corresponds to the firmware you're on, yep, that's exactly the one you want. :)
[Huawei Mate 9 Guides, News, & Discussion] daina:
All right, doing my part.

MHA-L29C567B369 (Stock Ramdisk .IMG)

https://drive.google.com/file/d/129LgZdu38fErvWxOUTAJeCuJplOkh4zU/view?usp=sharing
[Huawei Mate 9 Guides, News, & Discussion] daina:
And... we have Magisk. Passing Safety Net. Added cards to Google Pay.

Weird bug where Manager launches, then closes again a second later -workaround is to launch directly into Downloads section (long-press on icon in launcher) - stays up like normal, then, and can even navigate around. Weird.

Works, though! Good instructions.
[Huawei Mate 9 Guides, News, & Discussion] soft-touch:
xposed-v90-sdk27-arm64-beta3.zip is working on Oreo 8.1
[Huawei Mate 9 Guides, News, & Discussion] mataflakitas:
Where the link ...?
[Huawei Mate 9 Guides, News, & Discussion] soft-touch:
Here https://xdaforums.com/showthread.php?t=3034811

Select "Oreo" from the first post to go to download link.
[Huawei Mate 9 Guides, News, & Discussion] karakatos:
I have a problem.. i was on carbon rom & it worked perfectly but then i went over to the new Havoc rom (dev said this method should work on this rom).. but i get the following error when patching the stock ramdisk.img:

...
patching ramdisk
repacking boot image
! unable to repack boot image!
Failed!
! Installation failed

Any idead?

thanks
[Huawei Mate 9 Guides, News, & Discussion] daina:
So... today, I got B371 (Face Unlock, yay).

Like the FOOL that I am, I hit install, without regard to any possible consequences. It installed fine, haven't tried Face Unlock yet, but then noticed an ad on a webpage (bad ads!). It was then that I noticed that I didn't have root anymore (AdAway grumbled). Dammit, Magisk got borked during the install.

So, I reinstalled Magisk, went through the whole patched_boot.img rigmarole, scared the entire time, but device booted back up just fine. I have root. Yay.

But the SafetyNet check doesn't work. Says "the response is invalid."

I'm guessing it's because I didn't completely uninstall Magisk before reinstalling it? When I first checked on it (still in my app drawer) after discovering the ads and not-root-having, it just prompted me to install the zip (and like I said, I *did* go through the whole patched_boot.img thing), and that's what I did.

Should I start over completely from scratch? Or... since I currently have a patched boot image, can I just uninstall from Magisk Manager, reboot, re-install Magisk Manager (pointing to the patched boot), and reboot. Does anybody think that would work? Rhetorical, really, because that's what I'll do tomorrow. I just want to get some opinions...
[Huawei Mate 9 Guides, News, & Discussion] irony_delerium:
Google changed the SafetyNet API so that it requires valid API keys to use now. Try another app, like this one I came across earlier:

https://play.google.com/store/apps/details?id=de.guenthers.safetynet
[Huawei Mate 9 Guides, News, & Discussion] daina:
Thank you!

I figured things were okay, after I tried to use Google Pay last night, and it went through without a hitch. Then, Snapchat functioned flawlessly, and looking at the digeridoo page, I figured maybe that it was just the API that hadn't been updated in the MM checker... (not sure if that's the correct way of verbalizing it...)

As long as GPay and root works, I'm happy.